My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
Would putting IPV6INIT=no in the ifcfg-em1 file make this stop trying to use IPv6, or is there some other way (this is with good old network, not NetworkManager).
Tom Horsley wrote:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
Would putting IPV6INIT=no in the ifcfg-em1 file make this stop trying to use IPv6, or is there some other way (this is with good old network, not NetworkManager).
Doubt it makes a difference, don't see one with my dhcp up or not. Try jt unless someone has a good reason why it should be up
Am 25.01.2013 01:51, schrieb Tom Horsley:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
Would putting IPV6INIT=no in the ifcfg-em1 file make this stop trying to use IPv6, or is there some other way (this is with good old network, not NetworkManager)
add "ipv6.disable=1" to the kernel params and IPv6 is completly off
Once upon a time, Tom Horsley horsley1953@gmail.com said:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
It looks like the F18 install writes out ifcfg-* files with "DHCPV6C=yes", which should probably not be set by default, especially since so few environments (even IPv6 environments) will have a IPv6 DHCP server. Comment out that line or set it to "no" and it should fix the slowdown.
I've filed this in Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=903907
On Fri, 25 Jan 2013 04:18:18 +0100 Reindl Harald wrote:
Am 25.01.2013 01:51, schrieb Tom Horsley:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
Would putting IPV6INIT=no in the ifcfg-em1 file make this stop trying to use IPv6, or is there some other way (this is with good old network, not NetworkManager)
add "ipv6.disable=1" to the kernel params and IPv6 is completly off
Isn't it net.ipv6.conf.all.disable_ipv6=1 ???
I've done it this way. Works.
Just curious, Frank Elsner
On Thu, 24 Jan 2013 21:22:39 -0600 Chris Adams wrote:
It looks like the F18 install writes out ifcfg-* files with "DHCPV6C=yes", which should probably not be set by default, especially since so few environments (even IPv6 environments) will have a IPv6 DHCP server. Comment out that line or set it to "no" and it should fix the slowdown.
Thanks! That's what I was looking for. I don't want to utterly eradicate IPV6, I just want it to stop looking for a V6 address.
On 01/24/2013 10:22 PM, Chris Adams wrote:
Once upon a time, Tom Horsley horsley1953@gmail.com said:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
It looks like the F18 install writes out ifcfg-* files with "DHCPV6C=yes", which should probably not be set by default, especially since so few environments (even IPv6 environments) will have a IPv6 DHCP server. Comment out that line or set it to "no" and it should fix the slowdown.
RA will be more common. That is what I have.
I've filed this in Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=903907
Robert Moskowitz rgm@htt-consult.com writes:
On 01/24/2013 10:22 PM, Chris Adams wrote:
Once upon a time, Tom Horsley horsley1953@gmail.com said:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
It looks like the F18 install writes out ifcfg-* files with "DHCPV6C=yes", which should probably not be set by default, especially since so few environments (even IPv6 environments) will have a IPv6 DHCP server. Comment out that line or set it to "no" and it should fix the slowdown.
RA will be more common. That is what I have.
+1
Belts and suspenders: check both.
The ISP's that give you IPv6 addresses (Comcast for one) will also use dhcp to give you a whole 64-bit network of addresses via DHCP-PD.
I'm curious how many of the people that are disabling their IPv6 actually have painless access to IPv6 and are ignoring it.
-wolfgang
On Fri, 25 Jan 2013 14:45:29 -0800 Wolfgang S. Rupprecht wrote:
The ISP's that give you IPv6 addresses (Comcast for one) will also use dhcp to give you a whole 64-bit network of addresses via DHCP-PD.
Yea, but unless the router you have comcast's cable modem plugged into supports v6, it doesn't really matter what comcast does.
Once upon a time, Wolfgang S. Rupprecht wolfgang.rupprecht@gmail.com said:
The ISP's that give you IPv6 addresses (Comcast for one) will also use dhcp to give you a whole 64-bit network of addresses via DHCP-PD.
That's typically to a router though, not a host.
I'm curious how many of the people that are disabling their IPv6 actually have painless access to IPv6 and are ignoring it.
I have IPv6 at my home, but with the more common config using RAs. If I don't disable the DHCPV6C option in the ifcfg-eth0 file, bringing up an interface with "traditional" network scripts (e.g. ifup) takes 66 seconds. With DHCPV6C=no, it takes 3 seconds (DHCP for IPv4). Given the very small percentage of environments that are using DHCPv6 today, adding over a minute per interface startup to the default config is wrong.
Oddly, it appears that nothing is taking the DNS information from the RAs and adding it to /etc/resolv.conf. IIRC that used to work with ifup (but maybe I'm remembering wrong).
On 1/25/2013 6:13 PM, Tom Horsley wrote:
On Fri, 25 Jan 2013 14:45:29 -0800 Wolfgang S. Rupprecht wrote:
The ISP's that give you IPv6 addresses (Comcast for one) will also use dhcp to give you a whole 64-bit network of addresses via DHCP-PD.
Yea, but unless the router you have comcast's cable modem plugged into supports v6, it doesn't really matter what comcast does.
My cable modem, I own my own, that is connected to my router, I own my own, are both more than five years old. Both of them are connected to Comcast, which supports IPV6.
So? If /you/ have a problem you have some other problem.
I dislike FUD. Really dislike FUD.
Tom Horsley horsley1953@gmail.com writes:
On Fri, 25 Jan 2013 14:45:29 -0800 Wolfgang S. Rupprecht wrote:
The ISP's that give you IPv6 addresses (Comcast for one) will also use dhcp to give you a whole 64-bit network of addresses via DHCP-PD.
Yea, but unless the router you have comcast's cable modem plugged into supports v6, it doesn't really matter what comcast does.
Many routers can be updated with firmware from openwrt / ddwrt etc.
I've never felt the need for one of these routers to be between my internal ethernet and the dsl or cable modem. The software on them usually sucks and the CPU is usually underpowered compared to a desktop machine running with two ethernets.
-wolfgang
Am 26.01.2013 07:52, schrieb Wolfgang S. Rupprecht:
I've never felt the need for one of these routers to be between my internal ethernet and the dsl or cable modem. The software on them usually sucks and the CPU is usually underpowered compared to a desktop machine running with two ethernets.
no problem if your system is not windows and always up to date if your OS is windows or even more worse MacOSX it would be pretty dumb connect it diretly to the net
On 01/25/2013 05:45 PM, Wolfgang S. Rupprecht wrote:
Robert Moskowitz rgm@htt-consult.com writes:
On 01/24/2013 10:22 PM, Chris Adams wrote:
Once upon a time, Tom Horsley horsley1953@gmail.com said:
My system at work seems to take a long time to start the network. I have this suspicion it is waiting for an IPv6 DHCP server to respond (which won't happen).
It looks like the F18 install writes out ifcfg-* files with "DHCPV6C=yes", which should probably not be set by default, especially since so few environments (even IPv6 environments) will have a IPv6 DHCP server. Comment out that line or set it to "no" and it should fix the slowdown.
RA will be more common. That is what I have.
+1
Belts and suspenders: check both.
The ISP's that give you IPv6 addresses (Comcast for one) will also use dhcp to give you a whole 64-bit network of addresses via DHCP-PD.
My ISP gave me a /48 allocation :)
I'm curious how many of the people that are disabling their IPv6 actually have painless access to IPv6 and are ignoring it.
-wolfgang
-
Bill Davidsen -
Chris Adams -
David -
Frank Elsner -
Reindl Harald -
Robert Moskowitz -
Tom Horsley -
Wolfgang S. Rupprecht