News IPv6 Support

[lunch_box]

Just keep in mind that because they say it's enabled doesn't mean that it's usable or in fact supported.
For me (on BT). I get assigned an IPv6 address and so do my devices but all IPv6 traffic is getting as far as the first BT network address and then is dropped. If you want to see futility in action you can see my thread over on the BT forums.

EEEKKK. Im not BT support, but your router-config:
WAN IPv6 Address 2a00:23c5:7603:eb00::1
WAN IPv6 Gateway fe80::ea4:2ff:fe3e:1
LAN IPv6 Address 2a00:23c5:7603:eb00::1/56Is wrong. Though shalt not have the same address on WAN and LAN. Maybe your CPE supports DHCP-PD 'not really'. Anyway, for LAN a /64 out of the delegated /56 should do. Try something with a working IPv6-Stack as CPE. Anyway ... one 'standard way' (like I implement it for my customers) is to hand out WAN-address via SLAAC (or DHCP/Single adress) and provide the DHCP-PD only for use on the CPEs lan Side(s). Its slightly OT, but as featuring-v6 is one of my pet-projects try:

1) if you can receive an /64 address via SLAAC (yes, you don't have a working v6 on the lan-side then). Your CPE shoud then have a v6-address on WAN, as well as a v6 default GW (and the CPE[not your computer] should be able to ping the later) if that works

2) configure the LAN-side for using the a (sub)network attained via DHCP-PD (over the WAN). The prefix for DHCP-PD should be different from the Prefix in use on your WAN-interface


For those wanting a test-for-IPv6 connectivity: <http://www.ipv6-test.com/>
Its pretty basic, has nice Red/Yellow/Green colourings and is understandable. But it's not fit for any debugging, it merely gives you hint where Problems arise from (given you already have a working v6 connectivity, that is).

 

[Voz]

EEEKKK. Im not BT support, but your router-config:
WAN IPv6 Address 2a00:23c5:7603:eb00::1
WAN IPv6 Gateway fe80::ea4:2ff:fe3e:1
LAN IPv6 Address 2a00:23c5:7603:eb00::1/56Is wrong. Though shalt not have the same address on WAN and LAN. .....

Thanks lunch_box. I've got to say that I really appreciate the deapth of your answer but I don't have a clue what you are saying

I'll drop you a PM rather than derail this thread but perhaps there's something here for a general off-topic/technical type thread discussion.

 

[wstephenson]

One comment about the new networking config dialog:

It shows the number of connections of each type, but is only accessible from the Main Menu. Presumably at that point with no game running and no p2p sessions, all most people will ever see is a connection to the Frontier server(s).

Would it not be more useful to enable accessing the dialog in a read only mode whilst in game?

 

[Ian Skippy]

One comment about the new networking config dialog:

It shows the number of connections of each type, but is only accessible from the Main Menu. Presumably at that point with no game running and no p2p sessions, all most people will ever see is a connection to the Frontier server(s).

Would it not be more useful to enable accessing the dialog in a read only mode whilst in game?

While useful, a small correction: when you leave the game back to the menu, the network settings show the stats of the session you just ended.

 

[wstephenson]

Thank you, that makes sense now.

 

[Voz]

EEEKKK. Im not BT support, but your router-config:
WAN IPv6 Address 2a00:23c5:7603:eb00::1
WAN IPv6 Gateway fe80::ea4:2ff:fe3e:1
LAN IPv6 Address 2a00:23c5:7603:eb00::1/56Is wrong. Though shalt not have the same address on WAN and LAN. Maybe your CPE supports DHCP-PD 'not really'. Anyway, for LAN a /64 out of the delegated /56 should do. Try something with a working IPv6-Stack as CPE. Anyway ... one 'standard way' (like I implement it for my customers) is to hand out WAN-address via SLAAC (or DHCP/Single adress) and provide the DHCP-PD only for use on the CPEs lan Side(s). Its slightly OT, but as featuring-v6 is one of my pet-projects try:

1) if you can receive an /64 address via SLAAC (yes, you don't have a working v6 on the lan-side then). Your CPE shoud then have a v6-address on WAN, as well as a v6 default GW (and the CPE[not your computer] should be able to ping the later) if that works

2) configure the LAN-side for using the a (sub)network attained via DHCP-PD (over the WAN). The prefix for DHCP-PD should be different from the Prefix in use on your WAN-interface


For those wanting a test-for-IPv6 connectivity: <http://www.ipv6-test.com/>
Its pretty basic, has nice Red/Yellow/Green colourings and is understandable. But it's not fit for any debugging, it merely gives you hint where Problems arise from (given you already have a working v6 connectivity, that is).

Just wanted to point out on this one that BT admited a misconfiguration in my local area that impacted many people. They fixed it yesterday and everything works perfectly for me now. They would not (or could not) say what was changed.