On Wed, 06 Apr 2005 07:08:58 -0700 Wes wrote:
WH> Fong> Does anybody know how to solve this problem? I guess, this probably
WH> Fong> is OS issue. But hope somebody had the same issue and knew the
WH> Fong> answer. I need to use IPv6 port but be able to query IPv4 too. 
WH> 
WH> You should specify each of the transports you want to listen on when
WH> starting the server.  EG, "snmpd udp4:161,udp6:161" (and adding tcp4
WH> and tcp6 if needed).

Actually, there is no 'udp4' token. I believe the way it *should* work is that
'udp' should open both, while udp6 would just be IPv6. To only allow v4 if v6
is configure would require using access control.

However, I'm pretty sure there is a Linux OS issue that prevents the agent from
listening on v4 and v6 by default. I remember seeing a patch go by that
probably needs to be applied for future releases...

-- 
NOTE: messages sent directly to me, instead of the lists, will be deleted
      unless they are requests for paid consulting services.

Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>

You are lost in a twisty maze of little standards, all different. 


-------------------------------------------------------
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
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to