Asus not getting correct WAN-ip from Huawei XGS-PON

[Ac3200user]

Hi all,
I have a fiber-connection, with a Huawei XGS-Pon modem.
The lan is connected to the Wan-port of my Asus RT-AX86U.

My external ip-adress is 62.45.xxx.xxx
But my Asus says the Wan-ip is 100.97.xx.xxx

The Huawei fiber-modem should bridge it to the Asus, because it has no dns-server.
What am i doing wrong? Why is my Asus nog seeing my external ip-adress?

 

[ColinTaylor]

100.97.xx.xxx is a CGNAT address. The 62.45.xxx.xxx address is shared by multiple customers of your ISP.

Carrier-grade NAT - Wikipedia

en.wikipedia.org

 

[Ac3200user]

Thanks Colin. Problem is, my router is not accessible anymore. The "instant guard" app says: "Router needs external ip-adress".
How to configure that?

 

[ColinTaylor]

How to configure that?

You can't. You don't have a publicly accessible IP address.

Contact your ISP and ask them if they can assign you a public IP address rather than a CGNAT address.

Alternatively, you might already have a public IPv6 address. Does your ISP support IPv6?

 

[Digilog]

Thanks Colin. Problem is, my router is not accessible anymore. The "instant guard" app says: "Router needs external ip-adress".
How to configure that?

You need to call the ISP and have the modem bridged out if you can't access the modem.
Which might be the best choice so you can double check what you put into the router for the WAN connection.

 

[Tech9]

Access to settings won't change anything. The users can't fix this on their end. External WAN IP detection shows the ISP router WAN IP upstream, subscribers have private WAN IPs in double NAT. Exactly what @ColinTaylor says above and quite common situation in many places.

 

[Digilog]

Its about an hour call to the ISP to fix this.
Some customers can log into their modem, some can't. It depends on how the ISP set up the modem.
Some ISPs set this up this way on purpose if they don't have many outside IP addresses and only offer a bridge out to commercial customers that need an outside ip address.
But the only the ISP is going to have the answer to this.

 

[Tech9]

Again, private WAN IP or public WAN IP is not a modem setting.

The issue discussed here is between the modem and the ISP equipment, not between the modem and own equipment behind it.

 

[Digilog]

Again, private WAN IP or public WAN IP is not a modem setting.

The issue discussed here is between the modem and the ISP equipment, not between the modem and own equipment behind it.

correct because the ISP sets up the bridging in the modem. Usually the customer does not have access to the modem's management GUI. But even that, management of this might be account controlled too (by PPPoe or some other auth to connect). The ISP is the only one that going to have the answer to this.

 

[Tech9]

correct because the ISP sets up the bridging in the modem

No. The ISP sets up CGNAT at their equipment upstream. The ISP user device in router/gateway or modem/bridge mode - doesn't matter.

 

[Digilog]

No. The ISP sets up CGNAT at their equipment upstream. The ISP user device in router/gateway or modem/bridge mode - doesn't matter.

arguing for no reason is silly.

 

[Tech9]

Explaining why your suggestion (access to modem settings) is irrelevant. This thread question was already answered in post #4. There is nothing to argue about. Very common situation with very common (based on availability) solution.