One thing first - an apology : I am no longer "fit"
enough to code what I'd love to see.
What would nice to have is a command named (let's say)
snmpdiscover. You'd enter "snmpdiscover -c public
192.168.1.255 oid" and this command would do an UDP
broadcast, then listen to ALL incoming answers until a
timeout occurs.
Why ?
Imagine a script to discover all SNMP capable printers
or computers or toasters - without the need to do this
one by one.
Logged In: YES
user_id=80318
That's basically what HP JetAdmin does, causing all that
nasty broadcast traffic ;-\
Since you cannot code this with a synchronous SNMP
session, you would have to use an asynchronous handler to
deal with all the returning PDUs.
I thought about this myself, but it's tough to code for a
newbee like me.
Stefan
Logged In: YES
user_id=271956
This is, in fact, thr problem. No that the local network is
flooded with broadcast packets - it's basically just one to
three, much lower netload than counting up and polling
every possible IP address. But - writing an asynchronous
handler is beyond me.
Jens
Logged In: YES
user_id=848638
Patch 1039232 ("multilple ipaddress or ip address range
support to snmpget") sort of accomplishes this. Make your
vote there ;)