For up-to-date information and comments, search the EE Community or start a new topic. |
28-03-2021 02:38 PM
I've just got a new 5G Home router and discovered this issue too. Is there no hope to get a public IP address on our (very expensive) home router? I also run a web server from home and this looks like it is impossible with your (very expensive) 5G home broadband service.
28-03-2021 03:20 PM
Posted in the open:
@eyes2 wrote:
Hi XRaySpeX,
I see you've posted quite a bit about this. I used one of your threads to switch to IPv4 connection for my 5G Home Router. That allows the NAT to get better for gaming at least (mostly for my kids). However, it doesn't let me run my web server. I see from your other posts this is due to CGNAT run by EE. I've just spoken to their tech support by phone and they seem clueless. Do you think there is no hope for EE to change this? Or provide another solution?
I'll probably need to keep my much slower Sky Fibre (FTTC) connection too if they can't solve it, I can only get 30Mbps down with it. Wish we had FTTP here...
regards,
Stephen.
28-03-2021 03:28 PM
@eyes2 : As you've discovered the EE mobile network employs Carrier Grade NAT (CGNAT) resulting in a double NAT, which means that you don't get your own public IP address but share it with other users. So you can't be uniquely id'ed on the Net & therefore your LAN cannot be addressed from outside for unsolicited accesses. This is unlike fixed BB.
There is nowt you can do to avoid it. I cannot predict what EE might do in the future about it but I can't see them abandoning it considering the plethora of mobile devices connecting to their network. Other providers also employ CGNAT for the same reason.