Automatic IPv6 due to broadcast

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Mon Apr 16 13:50:44 CDT 2012


On Mon, 16 Apr 2012 23:39:46 +0530, Anurag Bhatia said:

More a host config issue than a NANOG issue, but what the heck...

> I wonder if anyone else also had similar issues? Also, if my guesses are
> correct then how can we disable Red Hat distro oriented servers from taking
> such automated configuration - simple DHCP in IPv6 disable?

The *right* answer is, of course, to hurry up and deploy proper IPv6.

It sounds like the distro is shipping some apps that don't do happy-eyeballs yet - you
probably want to file bug reports about that.

(It's easy enough to disable IPv6 if you haven't deployed it - in
/etc/sysconfig/network-scripts/ifcfg-<interface>  add:

IPV6INIT=no

then ifdown/ifup the interface and you should be good to go.  Make sure you
remember to take that line out when you get around to deploying IPv6.

(The difference between this and Matthew Huff's suggestion is that this way,
it disables IPv6 on the interface, and leaves the ::1 loopback address in place.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20120416/b4da1825/attachment.bin>


More information about the NANOG mailing list