1
General Discussion / Re: Default route for LAN interface
« on: April 28, 2024, 02:39:06 pm »
Thank you for asking.
Everything worked fine for several days.
Today I added a route, wanted to add one single host, but typed 24 instead of 32 for the mask value. The host I wanted to add resides on the same subnet as the opnsense and its web gui.
After this change I no longer had access to the opnsense web gui.
So I used the console port to remove the route:
route del -net <host> <gateway> 255.255.255.0
I confirmed the removal:
netstat -4rn
In my opinion there should be entries for the LAN interface igb0 in the output list of netstat, but there is none. There are entries for localhost, WAN and VLAN interfaces, therefore my guess is to add entries for the LAN interface in oder to fix the current issue of not being able to access the opnsense web gui.
Unfortunately I am not familiar with console commands, so I don’t know how to do this. I even don’t know if this will be the only fix I have to do.
Everything worked fine for several days.
Today I added a route, wanted to add one single host, but typed 24 instead of 32 for the mask value. The host I wanted to add resides on the same subnet as the opnsense and its web gui.
After this change I no longer had access to the opnsense web gui.
So I used the console port to remove the route:
route del -net <host> <gateway> 255.255.255.0
I confirmed the removal:
netstat -4rn
In my opinion there should be entries for the LAN interface igb0 in the output list of netstat, but there is none. There are entries for localhost, WAN and VLAN interfaces, therefore my guess is to add entries for the LAN interface in oder to fix the current issue of not being able to access the opnsense web gui.
Unfortunately I am not familiar with console commands, so I don’t know how to do this. I even don’t know if this will be the only fix I have to do.