25-06-2019 06:57 PM - edited 25-06-2019 06:58 PM
Does EE have a published plan with approximate milestones as to when their broadband network will have sufficient IPv6 implemented such that CGN can be removed at the subscriber side?
25-06-2019 07:27 PM
@jpcraig : Which EE BB network?
25-06-2019 07:32 PM
@jpcraig : CGNAT is not employed on EE's fixed Home BB network, only on the mobile network.
25-06-2019 07:37 PM
If that's the case then great.
However, I can't get inbound connectivity to work and my PPPoE router shows an RFC1918 address so I can't port forward on it. Port forwarding to the externally visible non-RFC1918 address doesn't work either. Thoughts?
25-06-2019 07:52 PM
What are the RFC1918 & non-RFC1918 addys, so I know what you are talking about?
25-06-2019 08:18 PM
My router's WAN address is 172.16.10.23 (non externally routable RFC1918) and my public IP address is in the range 184.108.40.206/n (unsure of mask). I get that by executing this is a bash shell:
echo $(dig +short myip.opendns.com @resolver1.opendns.com)
25-06-2019 08:30 PM
172.16.10.23 is your private local LAN IP of the thing you are trying to port forward, not the WAN. That's what you use in Port Forwarding.
25-06-2019 08:45 PM
Not true am afraid.
The LAN side of my router is RFC1918 and is in the 192.168.x.y range (my own IP range)
The WAN side is also RFC1918 and is in the 172.16.10.x range.
The WAN side is allocated by EE using a DHCP process after the PPPoE authentication occurs on the DSLAMs (or CHAPs routers; I can't remember which - point is that is a dynamic address that I receive from EE as my WAN address).
Here's the kicker: RFC1918 is not ever routable on the internet. All of them are dropped by internet edge routers so I can never address 172.16.10.x from anywhereelse on the internet.
My public IP (the 2.x.y.z address) is a secondary NAT that takes place in the EE network so that my traffic is publically routed. As far as I know this double NAT scenario using outbound source hide (overloaded) NATs (and subsequent PAT) is the essence of CGN and is why none of my inbound services work.
25-06-2019 10:52 PM - edited 25-06-2019 10:53 PM
Ah, I think I know what you are talking about now.
Yes, the default LAN IPs of EE routers are usually 192.168.1.x but I thought you had changed your DHCP range to 172.16.10.x which you can do, but you haven't. Which router have you? The EE Smart Hub offers a similar range.
The 172.16.10.23 IP is the Gateway onto the BT network (mine is currently 172.16.14.26). It is not assigned by EE by DHCP; it is defined by BT as the Gateway. There is no double NAT or CGNAT involved.
It is the 192.168.1.x IP of the thing you are trying to port forward that you use in Port Forwarding.
26-06-2019 10:26 PM
I use a Ubiquiti AP for local wireless which also serves the DHCP range of 192.168.1.0/24 locally to my home devices.
My PPPoE router is separate and is connected via a 1,000Mb/s ethernet switch to the AP.
The 172.16.10.x WAN address is provided directly over DHCP on the PPPoE WAN link by either Openreach (BT) or EE. I would tend to think that it comes EE as it's part of the CHAP authentication process.
I am trying to connect from the outside world to the 192.168.1.0/24 network. For that to happen I need my PPPoE WAN router to port forward the traffic internally. In essence port forwarding is static inbound NATing done on an overloaded static NAT that is routable from the internet.
172.16.10.x is not real world routable as defined by RFC1918. But when I try to route traffic to the 2.x.y.z EE address it fails. It never gets to the WAN port of my PPPoE router. Hence my suspicion is that CGN is in place. What else could it be?
26-06-2019 10:44 PM
There is no CGNAT on the EE Home BB network!
Lat's have some facts.
What router are you using?
Where do you see this 172.16.10.23 IP? Show me!
Other EE users, including myself, have managed to successfully Port Forward local servers & devices & addressed them remotely by the EE-assigned public dynamic 2.x.y.z IP (momentarily as it's liable to change at any resync - overcome by DDNS).
Please show me your Port Forwarding page that is not working for you.
by JAMESDNEVILLE yesterday