On Sat, 5 Dec 2009 14:59:53 -0800 Philip Guenther wrote: > On Sat, Dec 5, 2009 at 11:25 AM, rhubbell <rhubb...@ihubbell.com> wrote: > > I have disabled IPv6 in the kernel (via top-level GENERIC) but I can't > > see what other places it needs to be disabled for other applications. > > "Needs to be disabled" ...to accomplish what goal? Saving of disk > space? Elimination of code complexity? Ignoring of IPv6 packets that > are received? Something else?
I presumed that applications would be written so that if there's no support for a protocol family in the kernel that the app would be smart enough to avoid using that family. Doesn't seem unreasonable. > > Depending on what you're trying to accomplish, putting > up -inet6 > > in your /etc/hostname.* files may be sufficient. It seems that may help some but some apps are still not aware enough. > > > > Is it enabled per-application or is there some magic in a top-level > > Makefile somewhere? This IPv6 is like Whak-A-Mole. Or is it just so > > pervasive now that it cannot be disabled? I don't have a need to > > partake in the IPv6 "research" right now. > > Sounds like you would prefer if the presence of IPv6 wasn't making the > code more complex. If so, the answer is "no, it cannot be disabled in > that way." Thanks for the assist. To me it's simply I don't need IPv6, I don't use IPv6. I don't want to see any errors from applications that want IPv6. Why isn't IPX in the kernel and everywhere else? Or AppleTalk or .... Yes I know IPv6 is the "future". But I can wait. I've yet to see a good answer of why it's on by default in a lot of places. Is it to shake it out to find the issues? That's fine but to force it is not fine. It should be opt-in not opt-out just like most everything.
