Hello, and I apologize in advance as I use Google translate to write my German!
I’ve just set up an Internet Box Plus and am running into this limitation where it looks like a /60 is being offered. I can only route traffic from the first assigned /64 and I need more than one /64 in my house.
It also doesn’t seem to support prefix subdelegation. I see a firmware 10.2. Do we have any idea when this will be out?
@MCFH: as you correctly determined, even with the latest firmware on the Internet box you can only use the first of 16 possible /64 networks. Likewise, prefix delegation or static IPv6 routes are not currently implemented. There is probably no demand for it at the moment. That’s a shame, but somehow it’s understandable that there isn’t much development in this regard.
Have you tried turning it off and on again?
Thank you for your confirmation - very disappointing. My ISP in the UK gives me a /48 with prefix delegation and a /64 on the WAN side and everything works with any hardware today!
When you say static routes are not implemented, what do you mean? I set a static route downstream in my /60 and all traffic flows fine, not from the second /64.
@MCFH: Static routes are references to networks that can be reached in a way other than via the default gateway. In Linux, for example, you can do this with the relatively self-explanatory command
ip -6 route add 2001:db8:abcd::/48 via 2001:db8:1234:5678::99
Of course, on a consumer router, something like this is configured in the GUI and not via a CLI command. There is already a corresponding option on the IB for IPv4 (Expert Mode->Network->Static Routes), but not yet for IPv6. Static IPv6 routes on a router with a potentially dynamic 6th prefix don’t make much sense either. Maybe IPv6@swisscom or someone from the IB team can give us some insight into future planning?
Have you tried turning it off and on again?
Gerade bemerkt:
C:\
slookup community.swisscom.ch
Server: internetbox.home
Address: 2a02:120b:2c2c:ed0:dafb:5eff:fe1c:cc70
Non-authoritative answer:
Name: d1qto3qhg8t8rr.cloudfront.net
Addresses: 2600:9000:20ad:7800:d:906a:69c0:93a1
2600:9000:20ad:9000:d:906a:69c0:93a1
2600:9000:20ad:5600:d:906a:69c0:93a1
2600:9000:20ad:e00:d:906a:69c0:93a1
2600:9000:20ad:5000:d:906a:69c0:93a1
2600:9000:20ad:b200:d:906a:69c0:93a1
2600:9000:20ad:c00:d:906a:69c0:93a1
2600:9000:20ad:c800:d:906a:69c0:93a1
13.32.176.10
13.32.176.71
13.32.176.254
13.32.176.40
Aliases: community.swisscom.ch
scs.lithium.com
C:\
Ist neu, oder? Gratuliere
Have you tried turning it off and on again?
@Anonymous what is the status of things (IPV6, RES customer segment) asks @Nallehau79
The point is that in the official Sony forums (regarding the PlayStation) this problem has recently been officially pointed out when there are Internet problems (latency problems, “lags”, input delays and the like) that are not related to the can be eliminated using usual troubleshooting.
That’s the only reason I became aware of it myself.
It’s quite possible that this is also the case in the Xbox forums (I’m not active there) and that’s why there will be more questions about it in the future.
We looked at it internally several times. There are simply no advantages currently over the current solution. This is a multi-year project that is already underway. Every system that is exchanged in the E2E chain is also native IPv6 ready. It’s the routers. The new BNGs are too. Data center connections are also being renewed piece by piece. The services (TV, voice, etc.), monitoring tools, management servers, etc, etc, etc. There are also security concerns, especially in the mobile sector, that must first be addressed.
Unfortunately, a very big deal. But we are constantly working on it and at some point it will be finished. That’s where I stand. Maybe something has changed in the last few weeks. But don’t think so.
