SCIENTIFIC-LINUX-USERS Archives

August 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: SNMP scanner?
From:
Andrew C Aitchison <[log in to unmask]>
Reply To:
Andrew C Aitchison <[log in to unmask]>
Date:
Mon, 1 Aug 2016 09:07:30 +0100
Content-Type:
multipart/mixed
Parts/Attachments:
text/plain (985 bytes) 
On Sun, 31 Jul 2016, ToddAndMargo wrote:

> 2016-08-01 8:23 GMT+03:00 ToddAndMargo <[log in to unmask]>:
>       On 07/31/2016 10:15 PM, Jon Brinkmann wrote:
>             'nmap -sX 192.168.1.1-255 10.1-255.1-255.1-255 ...'?
> 
>
>       That is still scanning IP's over a range.  :'(
> 
> 
> 
> On 07/31/2016 10:42 PM, Eero Volotinen wrote:
> 
> Eh. Try scanning network: 192.168.1.0/25
> 
> Eero
> 
> That is still IP address dependent.  If there was two or three networks
> on the same interface, it  would only scan the network.

A broadcast ping
 	ping -b 255.255.255.255
might get you some useful information, but 
I think you are looking for a "sniffer" rather than a "scanner".
Since you don't know what addresses you are interested in,
you can't sacan them. You need to listen/sniff for traffic
perhaps encouraging it first, which is what the btroadcast does.

The interface will need to be in "promiscuous" mode,
the right tool will do that for you provided you are root.

ATOM RSS1 RSS2