WAN pppoe IP address different than my actual public IP address?

[frozen]

Hello, novice user here, using Bell Fiber internet in Canada.  I use OPNsense of course, completely up to date, and have think I've narrowed down my Dynamic DNS updating woes to the fact OPNsense is detecting the wrong IP address as my WAN IP!

What I mean is this

You cannot view this attachment.

If you see here, the IP is being reported as a 142.x.x.x address, which is being passed on to my Dynamic DNS client, and is unconnectable.
But when I open a terminal and do a 'curl ipinfo.io' for example, it displays my true IP which is a 78.x.x.x IP address

So I guess my question is, why?  And how do I fix it?

I need to pass on the 78.x.x.x IP to the Dynamic DNS updater, and simply choosing WAN isn't working

Thanks so much!

[frozen]

I've even tried different check IP methods like 'icanhazip' and it STILL is reporting the 142.x.x.x IP instead of the 78.x.x.x one

So confused!

[hharry]

It's more likely the pppoe interface is displaying the correct ip address as negotiated from IPCP, and that your ISP has another layer of SNAT'ing your PPPoE address to another address.

[frozen]

Okay and just to follow up, after more testing, so on OPNsense itself if I spawn a shell and 'curl ipinfo.io' it reports the 142.x.x.x address which does report as my correct city and all other details, but then if I simply receive a DHCP address and do a 'curl ipinfo.io' on the client -- it reports the actual correct 78.x.x.x IP!  The one that I need to be passed to my Dynamic DNS monitor.

Thanks again, sorry for the triple post

[frozen]

It's more likely the pppoe interface is displaying the correct ip address as negotiated from IPCP, and that your ISP has another layer of SNAT, nat'ing your PPPoE address to another address.

Thank you for the reply!

Oh dear, okay, well it seems that the only one listening to public incoming connections is the 78.x.x.x IP and NOT the 142.x.x.x IP reported in the monitor screen

I have a WireGuard server listening and it won't work when connecting to the 142.x.x.x internal IP, but works great when the 78.x.x.x IP is specified!

Thanks again for your time