28-05-2025 09:20 AM
I have two apparently identical EE sims in two apparently identical modems, with apparently identical settings, and with each modem being connected to an identical linux PC. Both PCs, by default, use IPv4v6 configuration.
Both systems are located in the same place.
One of these modems registers onto the network and receives both an IPv4 address which works fine
The other registers on the network and always obtains only an IPv6 address .Checking this IP, it is owned by BT/EE (as expected)
If I explicitly tell the second modem to request an IPv4 address, that modem doesn't get an IP at all.
However, I can't route any traffic over the IPv6 connection - even pings to public addresses fail. EE have checked and told me there is no block on the SIM itself - can anyone suggest anything else that might be going on here?
What seems very strange is that everything _seems_ identical....but one setup _always_ gets IPv4 (and works fine), the other does not....
28-05-2025 04:11 PM
Hi @dbrb2
It's a difficult one to pin down here, with the setups being the same. I can only suggest speaking with our Technical Support team to see if they can look into how they're connecting to the network.
Please keep us updated with what happens. It'll be interesting to know the reason they're working differently.
Chris
25-06-2025 10:28 AM
It looks like this might be resolved....
Speaking to a support agent they "pushed through a network refresh" - at which point I was able to route traffic again.
Is there any way to understand what might have triggered this, what a "network refresh" actually is, and whether there is any way I can do this myself if and when it happens again (it is not common, but happens from time to time)
25-06-2025 01:14 PM
I'm afraid ipv6 is difficult to get working. I went into my Tapo router and turned off ipv6 by giving myself a new profile. Samsung tech help gave me the idea, I just figured out how to do it.