Hi Everyone, I made it work in the end for the tethering connection. Thanks for all the replies.
I went on the laptop and set IPv6 for the connection to Link Local Only as apple removed the off setting too. Everything now goes via IPv4 and I can now do my job again and connect to resources via VPN tunnels on IPv4.Not ideal, I know, but I cannot just drop IPv4 for now. Would be nice to have had an announcement from EE that they were doing this though…. Catalin Dominte From: "[email protected]" <[email protected]> Date: Monday, 19 November 2018 at 09:41 To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: RE: IPv6 default on EE I have pinged you off list for some info. From: uknof <[email protected]> On Behalf Of Catalin Dominte Sent: 18 November 2018 21:01 To: [email protected] Subject: [uknof] IPv6 default on EE Hi Everyone, I am having a bit of a problem with EE at the moment, since they deployed IPv6 in their network (which I think it’s good) I cannot reach certain destinations that are running on IPv4, because they go via IPv6 by default. EE are blaming a certain iPhone software feature, because they default to IPv6 since IOS 12 without offering a way to disable it and they say there is nothing they can do to fix this. Apple has a bit of a blame too, for not allowing users to change APNs which EE said I should do if I want v4 only. Also, when tethering from an apple laptop, seems the specific route is disregarded which is totally against normal routing paradigm and IPv6 default is enforced. However I explained to EE that I don’t want IPv4 only, but I certainly want an option to say what needs to go where, for certain corner case v4 compatibility scenarios, if they are to do this properly. Has anyone had the same experience? Would be curious to see how much IPv6 traffic EE does after the change, compared to IPv4. 😊. Catalin
