LAN Connections are Reconigzed as WAN's

Started by masterain, January 16, 2022, 11:29:40 AM

Previous topic - Next topic
January 16, 2022, 11:29:40 AM Last Edit: January 17, 2022, 12:26:50 PM by masterain
Hi,

I recently set my opnsense router at home, but I noticed that LAN connections are only recognized as WAN connections. For example, the internal Linux server shows the last login was my WAN IP, instead of my LAN IP address. My internal Adguard Home DNS server also only has one client which is my WAN IP.

When I check the firewall log, the rule was the default LAN rule. The traceroute also shows the actual route never went to WAN. I have attached my LAN firewall rules below.

Can anyone help me figure out what causes this problem? Thanks!

UPDATE: I find this problem only occurs when the connection is going through the LAN bridge. If two devices are under the same interface, the connection shows LAN IP address.

This looks interesting, could you provide a diagram of how your network devices are connected?

One thing to check is make sure in the System -> Single -> Gateways shows your main gateway has the correct Interface that is meant to be your internet WAN port. I think, depending on the nature of the internet connection, static IP, etc, opnSense may think it is helping by spawning gateway interfaces even on the LAN, especially as the LAN port moves from DHCP to a static IP. It's possible system does not destroy erroneous gateways.