Dashboard not showing correct WAN public IP address using PPPOE

[machare]

I have version 24.7_5 running on a Qotom Intel processor hardware.  It has connected to the Internet via an  Huawei HG612 modem using PPPoE VDSL.  The connection itself works fine however:

The Dashboard shows the public IP address as 195.166.130.254 which is incorrect.

Please could this issue be corrected.  The router responds to pings to the correct public IP address assigned by the ISP which happens to be fixed. 

[dseven]

Is PPPoE being done by opnsense or Huawei? If Huawei is doing it, and NAT, opnsense's "WAN" IP address will not be your public one (which you might want to verify by visiting something like https://ip4.me/).

Without knowing more about your configuration, and what address you expect to see, it's hard to say, beyond guessing...

[machare]

The PPPoE is done by Opnsense.  The Huawei is just a modem that connects home  ethernet network to a VDSL telephone line.   

Opnsense dashboard showed  the correct public IP address before the upgrade to 24.7

The IP address is now shown as 195.166.130.254   which does not respond  to pings from  a device connected to my home network. 

If I ping the correct public IP address I get a reply.

[darkain]

displayed WAN IP is broken in general for me. I have a full native dual-stack WAN interface, and my WAN shows a link-local IPv6 address instead of my actual public IPv6 WAN IP.

It seems like the new widget is just guessing at random which IP address to list.

[franco]

First things first someone needs to tell me which widget we are talking about? Not to nitpick, but without a picture or precise reports this feels more like a rant than someone wanting to help get this fixed :)


Cheers,
Franco

[dseven]

If I ping the correct public IP address I get a reply.

How do you know that the reply is coming from your router and not someone else's? What do you get if you visit https://ip4.me/ ?

[Ed V.]

For me the widget is titled "Interfaces" and is one of the default widgets on the Lobby/Dashboard page.

I'm on 24.7_9 and can confirm that the widget only displays the link-local IPv6 addresses, though via command line I can see that public IPv6 addresses are assigned to devices, which is confirmed by https://ip6only.me.

[Patrick M. Hausen]

This is what the widget looks like on all of my firewalls, so we probably need some more specifics like e.g. the details of the WAN interface configuration in the UI, to have any idea what might be going wrong.

[Ed V.]

Here's my config.

[nodakbarnes]

Been using OPNSense for years and can confirm that I too have the same issue which appeared with the upgrade to 24.7.

Thankfully it is only a nuisance and does not appear to break DDNS (the actual public WAN IP is still picked up by os-ddclient).

I will be on the road today and test that my WireGuard connection is not affected (but since DDNS is reporting properly I suspect no issues).

Update: This does not affect my WireGuard road warrior setup thank goodness.

[Patrick M. Hausen]

With "request prefix only" to my knowledge you do not get a GUA on WAN.

[dseven]

I think we might be conflating issues here. The OP claims that they have a static *IPv4* address assigned by PPPoE, and that the WebUI is showing a different *IPv4* address. This seems quite different from seeing only a link-local IPv6 addresses (which may be a separate issue).

[franco]

With "request prefix only" to my knowledge you do not get a GUA on WAN.

This is correct. And this hasn't changed in ages. You might still get a SLAAC address, but it's not very trustworthy.


Cheers,
Franco

[franco]

I see what the issue is. It prints the first address, but not necessarily the primary address. Although the concept is a bit difficult especially with PPPoE. For IPv6 the widget is definitely inaccurate.

Can I get an ifconfig with the right and wrong address included?


Cheers,
Franco

[Patrick M. Hausen]

I think we might be conflating issues here. The OP claims that they have a static *IPv4* address assigned by PPPoE, and that the WebUI is showing a different *IPv4* address. This seems quite different from seeing only a link-local IPv6 addresses (which may be a separate issue).

Yes, sorry - wrong thread. There was another issue with someone seeing only a link-local address in the dashboard widget.