No Web_GUI if LAN is DHCP and GUI only on LAN

[ednt]

Hi,

for a special case (frr/bgp) we allowed GUI only on LAN, for the first setup we used DHCP on LAN, with an address from our management network.
I was not able to acces the GUI.
Ping was Ok.

On the console I can see that 443 listen is:
tcp4 127.0.0.1:443
tcp6 ::1:443

But not on the LAN address.
I think that the DHCP address was not available at web_gui start.
An uggly situation.
Ok, I solved it by using a fixed address.
But still, it should also work with a DHCP address on that interface.

[nero355]

But still, it should also work with a DHCP address on that interface.

IMHO that should always be a Backup Configuration and not the Primary Configuration.

However since we are talking about a Router here then there is only the Primary Configuration.

The Backup Configuration can be the Serial Console or some kind of IPMI/iDRAC/iLO-like solution...

[lmoore]

But still, it should also work with a DHCP address on that interface

I've set up a test system to trial the upgrade from 26.1 to 26.7.

For the purpose of testing, I set the LAN interface to use DHCPv4 - I have an IPv4 environment but no BGP.

The Web GUI is available every time OPNsense boots.

If your DHCP server is slow to respond, it may be the interface doesn't have an address when the Web GUI service starts, or, FRR/BGP is in some way affecting it as you wouldn't normally have DHCP assigned addresses on the internal interfaces of a router.

[Patrick M. Hausen]

Did you explicitly bind the UI to the LAN interface only (Listen address) or did you leave that setting at "All (recommended)"?