IPv6 prefix delegated to router but no internet connectivity

Honestly, I'm not sure about much at this point. But the technicolor modem was simple to set up, not much to configure as far as I can tell.

Only thing I did was giving the modem's MAC address to the cable ISP and waited for some time. During this initial period while waiting for my ISP to register the MAC address, I did have a working internet connection (ipv4+ipv6), but capped to 1 mbit/s. After waiting 30 minutes or so, I presume that the modem got registered by the ISP, since the (slow) internet connection cut out and I got left with an ipv6-only connection. This is where I am today.

There is an administration web-interface on 192.168.100.1 on the modem, but for some reason access to this interface gets cut off once the modem acquires a link to the ISP. Only way for me to access this interface is to power the modem on while the coaxial is disconnected. Once I plug the coax back in, I get kicked out of the admin interface and the local ipv4 network disappears.

Yes, the three addresses are weird. Not sure why this is the case. They have been there from day one as far as I can tell.

There's no other routers present on the network. The complete setup right now is:
ISP --- (coax) --- [TC4400-EU] --- [Edgerouter X SFP] --- [Ubuntu laptop]

Your IPv6 address data looks sensible (with the exception of the many addresses that trendy mentioned), so the OpenWrt router clearly discusses with the ISP hardware and gets the address, prefix for delegation etc.

I tried pinging your addresses, but I do not reach you.
traceroute6 stops near you.

(The routing seems to vary according to the address selected. Apparently Telefonica has some fail-over strategy in providing addresses from several prefixes.)

root@router1:~# traceroute6 2a02:3102:8001:80e2:265a:4cff:fe16:6870
traceroute to 2a02:3102:8001:80e2:265a:4cff:fe16:6870 (2a02:3102:8001:80e2:265a:4cff:fe16:6870), 30 hops max, 72 byte packets
 1  *  *  *
 2  *  *  *
 3  2001:4600:10::20e (2001:4600:10::20e)  7.070 ms  7.007 ms  7.317 ms
 4  ti3001b400-ae100-0.ti.telenor.net (2001:4600:10::20d)  7.155 ms  6.946 ms  7.268 ms
 5  ti3163c360-lo0-0.ti.telenor.net (2001:4600:0:100::10)  39.234 ms  39.136 ms  39.123 ms
 6  ti3003c400-lo0-0.ti.telenor.net (2001:4600:0:100::29)  39.154 ms  39.276 ms  39.351 ms
 7  ti9006b400-lo0-0.ti.telenor.net (2001:4600::c)  38.954 ms  39.013 ms  39.044 ms
 8  *  *  *
 9  2a02:3001::22d (2a02:3001::22d)  40.050 ms  2a02:3001::280 (2a02:3001::280)  40.065 ms  40.233 ms
10  2a02:3001::1a2 (2a02:3001::1a2)  40.193 ms  40.112 ms  40.337 ms
11  dynamic-2a02-3102-8000-0101-0000-0000-0000-0002.310.pool.telefonica.de (2a02:3102:8000:101::2)  34.577 ms  34.587 ms  34.881 ms
12  *  *  *
13  dynamic-2a02-3102-8000-c000-0000-0000-0000-0043.310.pool.telefonica.de (2a02:3102:8000:c000::43)  36.661 ms  36.488 ms  36.532 ms
14  dynamic-2a02-3102-8000-c1c3-0000-0000-0000-0002.310.pool.telefonica.de (2a02:3102:8000:c1c3::2)  2068.659 ms  *  2139.882 ms
15  *  2058.217 ms !H  *
16  dynamic-2a02-3102-8000-c1c3-0000-0000-0000-0002.310.pool.telefonica.de (2a02:3102:8000:c1c3::2)  2072.173 ms !H  *  2062.315 ms !H
root@router1:~# traceroute6 2a02:8071:d00:0:265a:4cff:fe16:6870
traceroute to 2a02:8071:d00:0:265a:4cff:fe16:6870 (2a02:8071:d00:0:265a:4cff:fe16:6870), 30 hops max, 72 byte packets
 1  *  *  *
 2  *  *  *
 3  2001:4600:10::20e (2001:4600:10::20e)  7.115 ms  7.067 ms  7.267 ms
 4  ae64.edge1.Stockholm1.Level3.net (2001:1900:5:2:2::6045)  7.168 ms  ti3001b400-ae100-0.ti.telenor.net (2001:4600:10::20d)  7.124 ms  7.278 ms
 5  ti3001c360-lo0-0.ti.telenor.net (2001:4600:0:100::a)  39.129 ms  *  *
 6  *  *  *
 7  2a02:908::42:1 (2a02:908::42:1)  43.006 ms  43.105 ms  ti9006b400-lo0-0.ti.telenor.net (2001:4600::c)  44.056 ms
 8  FFMGW4.arcor-ip.net (2001:7f8::c89:0:4)  39.460 ms  2a02:8071:ff:36dd::2 (2a02:8071:ff:36dd::2)  2059.037 ms  *
 9  2a02:8071:ff:36dd::2 (2a02:8071:ff:36dd::2)  2060.924 ms !H  2a02:908::42:1 (2a02:908::42:1)  45.547 ms  45.306 ms
10  *  *  *
11  2a02:8071:ff:36dd::2 (2a02:8071:ff:36dd::2)  2062.095 ms !H  *  *
12  *  2058.513 ms !H  *
13  2a02:8071:ff:36dd::2 (2a02:8071:ff:36dd::2)  2111.164 ms !H  *  *
14  *  2051.985 ms !H^C
root@router1:~#
root@router1:~# traceroute6 2a02:3102:8001:80e2::191
traceroute to 2a02:3102:8001:80e2::191 (2a02:3102:8001:80e2::191), 30 hops max, 72 byte packets
 1  *  *  *
 2  *  *  *
 3  2001:4600:10::20e (2001:4600:10::20e)  7.001 ms  7.292 ms  7.194 ms
 4  ti3001b400-ae100-0.ti.telenor.net (2001:4600:10::20d)  7.108 ms  7.018 ms  7.016 ms
 5  ti3001c360-lo0-0.ti.telenor.net (2001:4600:0:100::a)  40.416 ms  39.047 ms  39.363 ms
 6  ti3004c400-lo0-0.ti.telenor.net (2001:4600:0:100::5)  39.227 ms  39.078 ms  39.197 ms
 7  ti9006b400-lo0-0.ti.telenor.net (2001:4600::c)  43.957 ms  44.024 ms  43.934 ms
 8  80.81.193.89xp.decix.fra.de.net.telefonica.de (2001:7f8::1a95:0:2)  44.854 ms  44.816 ms  44.609 ms
 9  2a02:3001::26b (2a02:3001::26b)  40.128 ms  2a02:3001::26a (2a02:3001::26a)  39.856 ms  2a02:3001::26b (2a02:3001::26b)  40.201 ms
10  2a02:3001::1a4 (2a02:3001::1a4)  44.730 ms  44.820 ms  45.236 ms
11  dynamic-2a02-3102-8000-0103-0000-0000-0000-0002.310.pool.telefonica.de (2a02:3102:8000:103::2)  39.811 ms  40.450 ms  40.597 ms
12  *  *  *
13  dynamic-2a02-3102-8000-c000-0000-0000-0000-0043.310.pool.telefonica.de (2a02:3102:8000:c000::43)  41.624 ms  41.583 ms  41.968 ms
14  dynamic-2a02-3102-8000-c1c3-0000-0000-0000-0002.310.pool.telefonica.de (2a02:3102:8000:c1c3::2)  48.184 ms !H  48.237 ms !H  47.856 ms !H
root@router1:~#

Have you checked if OpenWrt gets an IPv4 address? If the Technicolor is not in bridge mode, it should give out IPv4 as well.
Have you connected your PC directly on the Technicolor? Does it work?

Thank you for your persistence, really appreciate it.

Good that it looks sensible I guess. It seems like communication with the ISP does occur, but I still cannot access the rest of the internet.

I have power-cycled the router + modem once more, not sure if it would make any difference, but you could try pinging me once more while I make sure to leave it running.

OpenWrt seems to only get an ipv6 address. During the powering up of the modem, the local ipv4 administration subnet 192.168.100.1 of the modem is briefly visible on the status page in OpenWrt. However, 10-20 seconds later, once the modem has acquired a link to the ISP, the ipv4 network disappears.

This is how it looks once everything has settled in:

OpenWrt only sees an ipv6 connection upstream.

This is how the interfaces looks like:

Took another look in the administration interface of the Technicolor TC4400-EU cable modem, as far as I can tell possibilities to configure it is virtually non-existent. This video (in german) does an overview of the admin interface, relevant parts are between 1:25-3:40 min. Ignore the video host, but by quickly skipping through the video you can get a feel for the available settings in the interface.

As far as I can tell, there's not really much at all to actively configure more than changing admin/user passwords. Most things in the interface are only there to display statistics and other general information.

I have also tried connecting my computer directly to the modem, but to no avail. Still get no internet connection. This is how it looks like with my laptop connected directly to the modem:
image

If the computer is also not working, I'd suggest to contact your provider. I'd also suggest to try to connect some phone or tablet to the wifi of the Technicolor. Usually customer support of the providers get allergies when they hear that you are using l1n4x and OpenWrt and say they don't support it.

1 Like

On cable systems, the modem (CM) will maintain a bridge table for end-user device (CPE) MAC addresses that typically defaults to a single entry, so in essence a cable modem will learn MAC addresses on its LAN side but will by default only allow the first MAC address learned after each power cycle to be forwarded through the modem to the CMTS. So if you change the device directly connected to a cable modem, either change that device to re-use the previous' device MAC address or just try to reboot the modem after connecting the new device. See "MAC and Upper Layer Protocols Interface Specification CM-SP-MULPIv3.1-I24-221019" chapter 9.1.2.1 MAC Address Acquisition for more details.

Oh, okay! Thanks for the info, didn't know modems behaved like this. Will make sure to power-cycle the modem any time I change devices connected to it on the LAN side.

Unfortunately, this didn't seem to resolve my issues in not getting an internet connection, but thanks again for the input.

Yes, at this point I may have to contact the cable provider. I'm not so sure anymore that the connectivity issues are at my end.

The technicolor is a "pure" modem and as such it does not have any wifi built in, so unfortunately I cannot test any mobile devices without connecting an external access point. However, I doubt that connecting an AP to my local network will resolve my problems.

Just to test things, I removed my modem's MAC address registered at my cable ISP's website. Now I'm back at the crippled 1 mbit/s connection which has ipv4+ipv6. This is what OpenWrt's status page shows:

I have now (incredibly slow) access to the internet via ipv4, but ipv6 seems to still not work. Additionally, don't seem to get delegated any /59 ipv6 prefix anymore.

Running some quick tests:

root@OpenWrt:~# nslookup google.com
Server:		127.0.0.1
Address:	127.0.0.1:53

Non-authoritative answer:
Name:	google.com
Address: 172.217.16.206

Non-authoritative answer:
Name:	google.com
Address: 2a00:1450:4001:812::200e

root@OpenWrt:~# ping -4 -c 5 google.com
PING google.com (142.250.186.174): 56 data bytes
64 bytes from 142.250.186.174: seq=0 ttl=116 time=19.971 ms
64 bytes from 142.250.186.174: seq=1 ttl=116 time=18.859 ms
64 bytes from 142.250.186.174: seq=2 ttl=116 time=21.651 ms
64 bytes from 142.250.186.174: seq=3 ttl=116 time=20.364 ms
64 bytes from 142.250.186.174: seq=4 ttl=116 time=19.037 ms

--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 18.859/19.976/21.651 ms
root@OpenWrt:~# ping -6 -c 5 google.com
PING google.com (2a00:1450:4001:828::200e): 56 data bytes

--- google.com ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

root@OpenWrt:~# traceroute -4 google.com
traceroute to google.com (172.217.16.206), 30 hops max, 46 byte packets
 1  ip-149-172-220-001.um42.pools.vodafone-ip.de (149.172.220.1)  7.934 ms  11.768 ms  9.492 ms
 2  ip-081-210-144-250.um21.pools.vodafone-ip.de (81.210.144.250)  8.026 ms  8.033 ms  12.341 ms
 3  de-str01c-rc1-ae-36-0.aorta.net (84.116.191.225)  14.695 ms  13.457 ms  15.275 ms
 4  *  *  de-fra04d-rc1-ae-10-0.aorta.net (84.116.140.205)  13.613 ms
 5  84.116.190.94 (84.116.190.94)  24.456 ms  14.896 ms  12.425 ms
 6  74.125.32.52 (74.125.32.52)  20.117 ms  20.402 ms  21.345 ms
 7  *  *  *
 8  142.251.64.180 (142.251.64.180)  21.363 ms  108.170.252.1 (108.170.252.1)  23.032 ms  142.250.213.212 (142.250.213.212)  21.005 ms
 9  142.251.241.77 (142.251.241.77)  21.087 ms  142.251.241.75 (142.251.241.75)  20.286 ms  108.170.252.18 (108.170.252.18)  21.163 ms
10  *  209.85.252.29 (209.85.252.29)  39.786 ms  108.170.236.249 (108.170.236.249)  22.034 ms
11  72.14.239.244 (72.14.239.244)  20.384 ms  fra16s08-in-f14.1e100.net (172.217.16.206)  22.923 ms  21.885 ms
root@OpenWrt:~# traceroute -6 google.com
traceroute to google.com (2a00:1450:4001:812::200e), 30 hops max, 72 byte packets
 1  *  *  *
 2  *  dynamic-2a02-3102-8001-00e2-265a-4cff-fe16-6870.310.pool.telefonica.de (2a02:3102:8001:e2:265a:4cff:fe16:6870)  3160.109 ms !H  *
 3  *  *  *
 4  *  *  *
 5  *  *  *
 6  *  *  *
 7  *  *  *
 8  *  *  *
 9  *  *  *
10  *  *  *
11  *  *  *
12  dynamic-2a02-3102-8001-00e2-265a-4cff-fe16-6870.310.pool.telefonica.de (2a02:3102:8001:e2:265a:4cff:fe16:6870)  3139.777 ms !H  *  *
13  *  *  *
14  *  *  *
15  *  3160.169 ms !H  *
16  *  *  *
17  *  *  *
18  *  *  3160.029 ms !H
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  3100.052 ms !H  *
25  *  *  *
26  *  *  *
27  *  *  3159.904 ms !H
28  *  *  *
29  *  *  *
30  *  *  *
root@OpenWrt:~# 

I'm not entirely sure how to interpret these results, but I get a stronger feeling that the ipv6 connectivity issues are not my fault, but my ISP's.

But please, anyone who knows more about this than I do, tell me if I have gotten anything wrong.

You are getting a response from a router of your provider that the host is not reachable. This looks to me like some filter from their side and you'd better contact them.

2 Likes

Will contact them, hopefully won't be too painful of an experience. Thank you all for your help and valuable input, I appreciate it a lot.

Yeah, it has looked the whole time that your settings look sensible, you do get IPv6 addresses etc., but no actual traffic gets routed.

Best to ask them.

1 Like

Wilco. Same to you, thanks for all the help. I've been very impressed by the quick and helpful responses here on this forum, big props to all of you.

Connecting directly to a PC is a good way to approach support since that takes out any issue of your third-party router. Since it will be exposed directly to the Internet use an impermanent OS such as a live USB boot.

What happens if you register your router's WAN port MAC address, instead of the modem?

Yes, I agree that bypassing the router would probably remove some points of contention with customer support. However, I also suspect that customer support will want ensure that the router/computer behind the modem supports DS-Lite, since it seems like that's the only way that my ISP provides an ipv4 connection.

O2's own forum with people using the technicolor TC4400 modem, but being told that their router must also support DS-lite. Since I'm not sure how to set up a working DS-lite config on my ubuntu laptop, or any live-boot OS, I think I might stick with the router connected during the support call.

However, some interesting things happened.

While I had the crippled 1 mbit/s connection, I took the opportunity to install the ds-lite package in OpenWrt. After re-registering my modem's MAC address on my ISP's website, nothing seemed to change compared to previously. Performed a handful reboots of both the router and modem, while also letting the modem be unplugged for 60+ minutes before plugging it back in, I still had a non-working ipv6 connection, same as before.

However, then I took your idea and registered the MAC address of the WAN interface of my router, and it seems like DS-lite autoconfigured.


Good news, I guess?

However, I still don't seem to have any connection to the rest of the internet.

root@OpenWrt:~# nslookup google.com
;; connection timed out; no servers could be reached

root@OpenWrt:~# ping -4 -c 5 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:~# ping -6 -c 5 2001:4860:4860::8888
PING 2001:4860:4860::8888 (2001:4860:4860::8888): 56 data bytes

--- 2001:4860:4860::8888 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:~# traceroute -4 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
 1  *  *  *
 2  *  *  *
 3  *  *  *
 4  *  *  *
 5  *  *  *
 6  *  *  *
 7  *  *  *
 8  *  *  *
 9  *  *  *
10  *  *  *
11  *  *  *
12  *  *  *
13  *  *  *
14^C
root@OpenWrt:~# traceroute -6 2001:4860:4860::8888
traceroute to 2001:4860:4860::8888 (2001:4860:4860::8888), 30 hops max, 72 byte packets
 1  *  *  *
 2  *  *  *
 3  *  *  *
 4  *  *  *
 5  *  *  *
 6  *  *  *
 7  *  *  *
 8  *  *  *
 9  *  *  *
10  *  *  *
11  *  *  *
12  *  *  *
13  *  *  *
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

Running the same commands from my laptop connected to the router produces similar outputs.

Any thoughts on this? I was under the impression my ISP would be interested in the modem's MAC address, rather than the router's WAN MAC address, in order to establish a connection via coaxial cable.

Was thinking of calling my ISP this afternoon, will see what comes of it.

I don't have experience with DS-Lite, but with any tunnel I would expect anything involving ipv4 to die immediately if the ipv6 is not working.

I forget-- did it work to ping the nexthop IP which was link-local? This may be inside your modem or it may be at the other end of the cable. If the cable modem is a full bridge, the ISPs DHCPv6 server is going to see your MAC address on requests, not the modem's.

I also use a TC 4400 and get native IPv6, and IPv4 with ds-lite. I also get no IPv6 connectivity out of the box. I need to install the package ds-lite to get connectivity. I also need to manually declare some ISP routers as neighbors to get a stable connection. My router itself does not get IPv4 connectivity, which I consider to be a bug. You can read about my experience here: Troubleshooting packet loss

Edit: By the way, the modem TC4400 changes it's LAN ip from 192.168.100.1 to 192.168.0.1 after provisioning from the ISP. At least it did last time I checked and obtained this information. Right now it doesn't respond to 192.168.0.1 either.

192.168.100.1 is used for administrative and/or diagnostic access, I believe this is actually mandated in the docsis standards.
Switching to 192.168.0.1 indicates that the modem operates as router, no?

I'm not sure if I understand you entirely, but I believe the answer is no. If I ping the gateway link-local address showing on the status page in OpenWrt:

root@OpenWrt:~# ping -c 10 fe80::1239:e901:31a7:cf70%eth0
PING fe80::1239:e901:31a7:cf70%eth0 (fe80::1239:e901:31a7:cf70%3): 56 data bytes

--- fe80::1239:e901:31a7:cf70%eth0 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

That might explain why the DS-lite tunnel auto-configures when I register the router's WAN port with my ISP.

I have been alternating back and forth between registering the TC4400's MAC address and my router's WAN MAC address at my ISP's website, and while I do get ipv6 addresses and an /59 ipv6 prefix no matter which of the two MAC addresses I register, I only get DS-lite to populate when I register the router's WAN port.

Nevertheless, I am still at no point able to get an work connection to the internet, neither through ipv6 nor ipv4.

Unfortunately, even after installing the ds-lite package, I cannot get any internet connection, neither via ipv4 nor ipv6.

I found this medium post talking about scripting the setup of a ds-lite tunnel. The author talks about some issues to successfully route IPv4 traffic originating from both the local network and the router itself, and additionally that OpenWrt's implementation of ds-lite also has this problem.

It's possible I misunderstood the problem, but could this be related to your issue that your router by itself does not get ipv4 connectivity?