New customer IPV6

[MikeAK]

Hi,

Just signed up for EE broadband (FTTC, FTTP not available here yet). I should have asked if it supports IPV6 when ordering but forgot.

So doesit support IPV6 and what size prefix is delegated?

I have seen several contradictory posts some saying it doesn't and other saying it does following the merge wit BT.

As an aside I'm not impressed with the help system you can't ask a question, its all select from a list of options for comon queries and no option to speak to someone!

Thanks

Mike

[Neil-O]

Hi @MikeAK Welcome to the community and thanks for posting, yes New EE broadband supports IPV6, prefix /64.

Thanks

Neil

[XRaySpeX]

The contradictions you've seen arise from the fact that legacy EE BB doesn't support IPv6.

[MikeAK]

Hi,

Thanks Neil, are you sure it's a /64 on broadband, I know EE mobile gives a /64?

If so thats dissapointing, normally it's /48 or /56. With a /64 there is no ability to subnet for separate lan networks.

Regards

Mike

[andydaws]

Yes you are correct usually /48

But yes it does support IPv6 and yes it is only a /64 given out which you have no control over even IPv4 you can only set the IP lease range not DNS so you are stuck with the filtering they give you or you have to manually set every device

TCP [2a00:23c7:787:4c00:xxxx:xxx:xxxx:xxxx]:28922 [2607:f2d8:1:3c::3]:80

[MikeAK]

Hi again,

Got connected today. The IPV6 prefix is a /56.

I think people may be conused into thinking its a /64 due to the layout of the EE router pages which are "simplified" to say the least.

Anyway a /56 is fine, thats 256 /64s avaiable on the lan which is more than enough to me.

I have gone back back to using my old OPENWRT router as the user interface of the EE router doesn't allow me to do what I need.

Is a shame they have spoiled a router, which should be very capable according to the specs, with a completly dumbed down user interface!

Here's a screenshot of the wan interface on openwrt router.

[andydaws]

Well that is good gives some subnet options. On the EE router is overally simplified even the advanced options you only get to see the allocated LAN interface IPv6 (a /64 no control) nothing other than IPv4 on the WAN side certainly can not change anything not very good

Would be good to change at some time to pfsense to play with as familiar with that on BT business circuits

The catch will be digital voice and if I can put the EE router behind to still support voice

[GosforthUK]

I settled on /56 with my TP-Link Omada setup and it's working just fine...

however, tech support recommended using "no-address" as the network itself does not fully implement IPV6 and it's simply the same, as BT FF implementation (given it's on the same network perhaps_) means, the same as with IPV4, you technically speaking don't have public permanent/fixed IP

[planetf1b]

I'm too looking at switching to EE.

@Neil-O You mentioned above a /64 address was provided. I wonder if there is any confusion here. I am reading in several places that in fact the prefix allocation over pppoe is a /56. So for example using one's own router this can then be further delegated locally (multiple /64s for example). The actual provided EE router however only exposes a /64 to the lan.  In both cases the router itself will of course get an ipv6 address

@GosforthUK can you elaborate at all on 'no-address' (do you mean not to hardcode an address?)  or 'not fully implement' IPv6, or 'BT FF' ? My understanding is that the prefix allocation is dynamic (shame), so get the point about it not being a permanent public address, but what other limitations are you aware of / have you seen? 

UPDATE! Just read @mikeAK's post which suggests all is well with a proper /56 (I wish that information was clearly published officially be EE!) - I wonder also did you find the prefix fairly sticky or very dynamic? I can imagine a prefix change being a bit more painfull (though when my existing ISP changed me away from fixed all the systems (except a few hardcoded references) were fine)