I tested from our management application without giving udp6 and port number and it works fine. So, the requirement of giving udp6 is of "snmpget" and not the agents.
- Srini > -----Original Message----- > From: Wes Hardaker [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 05, 2005 10:54 AM > To: Srini Kode > Cc: [EMAIL PROTECTED]; > [email protected]; [EMAIL PROTECTED] > Subject: Re: IPv6 testing > > >>>>> On Fri, 25 Mar 2005 11:00:13 -0800, "Srini Kode" > <[EMAIL PROTECTED]> said: > > Srini> snmpget -v 2c -D All -c public > udp6:[fe80::205:30ff:fe00:2309]161 > Srini> sysDescr.0 > > Srini> This means the network management application must > give udp6 and > Srini> the port number number 161 also when they query. Is > this the standard practice? > Srini> Just like IPv4 why cannot we just have the ip address in the > Srini> request? > > Our applications require the usage of specialized strings for > determining which transport to us. Every management > application will likely do something different. > > Actually, I think you can drop much of the above as the port > number and the udp6 identifier portions will be figured out > if you don't include them. But this is from memory of how I > remember it being implemented. I haven't looked at the code > or tested it to make sure what I'm saying is the truth ;-) > > -- > Wes Hardaker > Sparta > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
