inconsistencies in the interfaces on a Sophos SG 135 rev 2

[norse]

Hi all,

the other day I installed OPNsense 25.7 (later updated to 25.7.2) on a Sophos SG 135 rev 2. Everything went fine until I tried to connect to the web gui, which wouldn't be possible, since the network ports on the Sophos showed "no carrier", even when cables where plugged in (see picture x.jpg). Neither was it possible to connect via the WAN interface (after a pfctl -d).

LAN was configured to be igb0, and WAN to be igb1 (this assignment is also shown in the picture). The indicator lamps on the SG 135 showed both "Link" and "activity" for "eth0/LAN" and "eth1/WAN" when cables where connected.

I looked a while for problems with those two interfaces, but came to no solution until I found out that in reality igb4 had to be used for LAN and igb5 for WAN.

That raises 2 questions:

1. Why does OPNsense assign the tags/description "LAN" and "WAN" to igb0 and igb1 (and not to igb4 and igb5), when obviously those are not the correct ports for LAN and WAN?

2. Is there a way to rename the ports, so that igb0 is really LAN and igb1 is really WAN ?

Norse

[franco]

Hi,

I think it simply reset itself because you assigned an interface that is not available at boot.

Locking (meaning preventing) the reassignment of LAN/WAN is an easy check box change, but adding a volatile interface and assigning it is a bigger problem you ran into.


Cheers,
Franco