Varun Chandramohan wrote: > Wes Hardaker wrote: >> I think it's time we move to turning on ipv6 by default if possible >> (which is the tricky part). Anyone have estimations of what snags we'll >> run into when trying to detect whether it's possible to do by default? > > What kind of problem do you see for this to happen? I > think we have almost all the mibs needed. Dont we?
We do have quite complete IPv6 support for Linux, but are still missing quite a lot for other platforms. The hard part, as Wes says, is in "trying to detect", i.e. in the detection logic to put into configure.in. There's some detection in place for some earlier IPv6 stacks, but none for Solaris/AIX/HP-UX/Tru64/IRIX (to name a few). They currently all require the user to decide whether his OS supports it and specifiy --enable-ipv6 if it does. I've put some effort into making at least this possible for various OS before 5.4. Furthermore, --enable-ipv6 currently enables both the UDPIPv6/TCPIPv6 transports *and* the (deprecated) mibII/ipv6 MIB module (but not necessarily the newer ones, AFAICS). We also need a consistent approach here. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
