On Fri, 20 Aug 2004 13:49:34 -0700 Fong wrote: FT> Currently if snmpd agent is launched on IPv6 transport, both IPv6 and IPv4 FT> addresses can access it. However, access control in snmpd.conf FT> distinguishes between IPv6 (eg. rwcommunity6) and IPv4(eg. rwcommunity). If FT> snmpd is launched IPv6, for IPv4 access, access control needs to be defined FT> in IPv6 format, which is rwcommunity6 ::ffff:x.x.x.x.
Interesting... so if snmpd is started with udp6, it will receive packets addressed to an IPv4 address (a.b.c.d)? Or just an IPv6 format IPv4 address (::fff:a.b.c)? FT> To me, if it is accessible for both IPv4 and IPv6, for IPv4, it should look FT> IPv4's access control(rwcommunity). It is certainly debatable. We'll have to wait and see what the everyone else thinks. FT> Attached are changes for making IPv4 to read IPv4 access control. FT> Also set SO_REUSEADDR for socket bind. This should be disabled by default, as it is in the ipv4 udp transport. -- Robert Story; NET-SNMP Junkie <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.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
