[opensuse] IPv6 assignment delays on 42.2. 7minutes until global unicast
I read some weird bugs in the pest roughly speaking that opensuse leap, back then it had been 42.1, would only assign itself or be assigned an ipv6 global unicast address, after exactly 10minutes. I cant remember the bug or really find it any more and I think there was more to it than just bug, but some fundamental stuff touching all kinds of stuff, linux kernel networking stack, all that wicked stuff and all sorts of eerie stuff. Anyhow, these days I am seeing 42.2 delay with ipv6 in some soho lan with some standard isp and some standard cpe handing out ipv6 addresses. These addresses dont take 10minutes to arrive but still around 7minutes. As far as I understand the isp cpe, it doesnt do dhvp v6 on the lan, but some of these ipv6 router advertisement and neighbor discovery and all that which is the other way to assign oneself a global unicast, the non-dhcp-v6 way, dont ask me what it is called exactly. Anyone care to explain why this takes 7minutes, reproducible? the dualstack nat-ed ipv4 rfc1918 address and the fe80:xx address become set and assigned pretty much immediately when the interface comes up. Thank you for helping. Best regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/06/17 15:31, cagsm wrote:
I read some weird bugs in the pest roughly speaking that opensuse leap, back then it had been 42.1, would only assign itself or be assigned an ipv6 global unicast address, after exactly 10minutes.
The bug you are looking for might be bug 916956. However, the problem is no longer happening here. So perhaps your issue is different. Try disabling the firewall. Then reboot (with firewall disabled) to see if that solves the problem. If it is the same issue that I had, then that will "fix" it. Apparently the early stages of firewall startup were blocking router announcements on IPv6. But it is now working for me (with the firewall enabled). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
cagsm wrote:
I read some weird bugs in the pest roughly speaking that opensuse leap, back then it had been 42.1, would only assign itself or be assigned an ipv6 global unicast address, after exactly 10minutes.
I cant remember the bug or really find it any more and I think there was more to it than just bug, but some fundamental stuff touching all kinds of stuff, linux kernel networking stack, all that wicked stuff and all sorts of eerie stuff.
In my setup (radvd+dhcpv6), ipv6 works fine on 42.[12], but we have a fixed prefix.
Anyhow, these days I am seeing 42.2 delay with ipv6 in some soho lan with some standard isp and some standard cpe handing out ipv6 addresses. These addresses dont take 10minutes to arrive but still around 7minutes.
As far as I understand the isp cpe, it doesnt do dhvp v6 on the lan,
It does need to propagate the ipv6 prefix it has been given, at least. With that, the LAN devices can auto-config themselves.
but some of these ipv6 router advertisement and neighbor discovery and all that which is the other way to assign oneself a global unicast, the non-dhcp-v6 way, dont ask me what it is called exactly.
stateless address autoconfiguration
Anyone care to explain why this takes 7minutes, reproducible? the dualstack nat-ed ipv4 rfc1918 address and the fe80:xx address become set and assigned pretty much immediately when the interface comes up.
I think you'll have to do a tcpdump to see what's really happening. -- Per Jessen, Zürich (4.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
cagsm -
Neil Rickert -
Per Jessen