Messages

Thanks for the tip. 2.50 for a stable tunnel which does not break netflix etc doesn't sound bad.  I used to have a tunnel from tunnelbroker.net but it indeed does not work well with Netflix...

However, getting the problem with the native IPv6 connectivity fixed would be nice

Bonjour, sorry for writing this in English but my French is not good enough (yet).

Since around mid of May, IPv6 is not working anymore for me (in St Jean de Gonville, Ain).
I'm curious if anyone else has the same problem here... as a power user I'm really starting to miss IPv6.

In case someone from K-NET is reading here, I opened a ticket (K-NET#2020052685000915) about a month ago, but except
for a question whether the problem still persists (which I replied to a week ago), I haven't received anything else yet...

Below are some technical details (exactly what I also sent in the support ticket). But I believe just like the previous incidents
with the exact same issues it's some problem on the network side, since IPv4 is perfectly stable.


Outgoing traceroute from my router:

Code Sélectionner Étendre


root@router:~# traceroute6 cern.ch
traceroute to cern.ch (2001:1458:201:70::100:26), 30 hops max, 64 byte packets
1  2a03:4980::11:0:1a82 (2a03:4980::11:0:1a82)  3116.455 ms !H  3106.799 ms !H  3119.875 ms !H
root@router:~#



Outgoing traceroute from a host in my local network:

Code Sélectionner Étendre


[adrian@claptrap:~]> traceroute6 cern.ch
traceroute to cern.ch (2001:1458:201:70::100:26), 30 hops max, 80 byte packets
1  router.fr.aeum.net (2a03:4980:12:efef::1)  1.162 ms  1.141 ms  1.120 ms
2  router.fr.aeum.net (2a03:4980:12:efef::1)  540.960 ms !H  540.957 ms !H  540.976 ms !H



Traceroute from outside to my main IPv6 IP:

Code Sélectionner Étendre


[adrian@blackhole:~]> traceroute6 2a03:4980::11:0:1a82
traceroute to 2a03:4980::11:0:1a82 (2a03:4980::11:0:1a82), 30 hops max, 80 byte packets
...
9  cixp.ipv6.kwaoo.com (2001:7f8:1c:24a::6148:1)  0.941 ms  1.043 ms  1.028 ms
10  border1-sgp.kwaoo.net (2a03:4980::7:0:2)  14.358 ms  14.363 ms  14.383 ms
11  bifrost.k-net.fr (2a03:4980:0:6::5)  1.370 ms  1.207 ms  1.012 ms
12  * * *
...
30  * * *



Traceroute from outside to an IP in my IPv6 subnet:

Code Sélectionner Étendre


[adrian@blackhole:~]> traceroute6 claptrap.fr.aeum.net
traceroute to claptrap.fr.aeum.net (2a03:4980:12:efef::dead:b33f), 30 hops max, 80 byte packets
...
9  cixp.ipv6.kwaoo.com (2001:7f8:1c:24a::6148:1)  0.824 ms  0.809 ms  0.744 ms
10  border1-sgp.kwaoo.net (2a03:4980::7:0:2)  1.228 ms  1.326 ms  1.471 ms
11  bifrost.k-net.fr (2a03:4980:0:6::5)  1.146 ms  1.114 ms  1.121 ms
12  * * *
...
30  * * *



Nothing on my router config (openwrt) changed when the issues started occurring, except that I currently disabled the
wan6 network interface in order to fully disable IPv6 to avoid timeouts when clients try to use IPv6. Here is the config
I usually have for it (and which worked perfectly fine before)

Code Sélectionner Étendre


config interface 'wan6'
        option _orig_ifname '@wan'
        option _orig_bridge 'false'
        option proto 'static'
        option ifname 'eth0'
        option ip6prefix '2a03:4980:12:ef00::/56'
        option ip6gw '2a03:4980::11:0:1'
        option ip6addr '2a03:4980::11:0:1a82/96'


Looks like they are doing maintenance on the IPv6 infrastructure again....
I lost IPv6 connectivity yesterday evening (St Jean de Gonville, Ain); here's a traceroute from outside to my IPv6:

Code Sélectionner Étendre


...
9  e513-e-rbrrt-3-ne1.ipv6.cern.ch (2001:1458:0:13::2)  1.040 ms  1.008 ms  1.214 ms
10  cixp.kwaoo.com (2001:7f8:1c:24a::6148:1)  1.248 ms  1.046 ms  1.163 ms
11  border1-sgp.kwaoo.net (2a03:4980::7:0:2)  1.059 ms  1.243 ms  1.243 ms
12  bifrost.k-net.fr (2a03:4980:0:6::5)  1.240 ms  1.078 ms  1.445 ms
13  * * *
14  * * *
15  * * *


Most likely it'll work again in a few days - but it's still pretty annoying.

Thanks, that was exactly what I needed! It's working fine now

In case someone else is using OpenWRT, this is what I have in /etc/config//network now:

Code Sélectionner Étendre

config interface 'wan6'
        option _orig_ifname '@wan'
        option _orig_bridge 'false'
        option proto 'static'
        option ifname 'eth0'
        option ip6prefix '2a03:xxxx:12:ef00::/56'
        option ip6gw '2a03:xxxx::11:0:1'
        option ip6addr '2a03:xxxx::11:0:1a82/96'

Not sure if the _orig_* settings are needed; they were there before; I configured it via the LuCI web interface:
Interface: wan6
Protocol: Static address
Physical settings / Interface: eth0 (the one containing wan and wan6)
IPv6 address: 2a03:xxxx::11:0:1a82/96
IPv6 gateway: 2a03:xxxx::11:0:1
IPv6 routed prefix: 2a03:xxxx:12:ef00::/56

Sorry for asking in English, but my French is not very good (feel free to reply in French though, I'll probably understand enough)

I have a K-NET fiber connection in the Ain departement. The connection works fine, and when I contacted support about the IPv6 address they gave me this information:

Code Sélectionner Étendre

Subnet IPv6: 2a03:xxxx:12:ef00::/56
IPv6 WAN: 2a03:xxxx::11:0:1a82

Don't I need to know the gateway as well? I tried fe80::1 and 2a03:xxxx::11:0:1a82 as the gateway address, but it didn't work.
Of course I can contact them again next week but before doing that I want to make sure there's actually some information missing.

If someone is using K-NET's native IPv6 successfully on their router with OpenWRT, please let me know!