[BUG] changed LAN interface settings DHCP server is not reloaded.

[heypppoe]

My OPN box has a LAN bridge, after Enable link-local address, and save the interface settings, DHCP server on this bridge is not reloaded caused DHCP server cannot process client request.

with error: receive_packet failed on bridge0: Device not configured

[franco]

I don't quite get the report, sorry. The link-local option is in the bridge, not the interface settings?


Cheers,
Franco

[heypppoe]

I don't quite get the report, sorry. The link-local option is in the bridge, not the interface settings?


Cheers,
Franco

No, I mean, before the bridge link-local is disabled, after I enabled it and save the changes, the DHCP server running on the bridge is not reloaded, that caused the DHCP server is not handling client requests.

[franco]

Ok... but... are you talking about IPv4 or IPv6? Link-local only makes sense for IPv6, right?

But then the fact remains you are reloading a bridge or interface, but not a DHCP server?


Cheers,
Franco

[heypppoe]

Ok... but... are you talking about IPv4 or IPv6? Link-local only makes sense for IPv6, right?

But then the fact remains you are reloading a bridge or interface, but not a DHCP server?


Cheers,
Franco

Ok, sorry for the bad expliantion, yes I know link-local is an IPv6 thing, and yes the problem is I reloaded the bridge/interface, but shouldn't DHCPv4 server reloaded automatically? Manually reload the DHCPv4 server indeed resolved this issue, the DHCPv6 server is disabled.

[franco]

That's probably a side effect of recreating the bridge interface during editing it. Not much we can do here.


Cheers,
Franco

[heypppoe]

That's probably a side effect of recreating the bridge interface during editing it. Not much we can do here.


Cheers,
Franco

okay, but maybe a nice message print after modified the bridge interface would be helpful. Took some time to figure out this issue.

[franco]

It's a very specific use case where you create a bridge, also assign it and then also put an IP configuration on it in order to then run services on top. While you are right about the problem it is quickly dealt with from an administrative perspective and I don't see an easy fix. The problem is the bridge device. If it were a hardware device this cannot happen.

It's more of a reason why local port bridging is not the best idea and a good switch can be acquired cheaply. Actually any bad switch would do better.


Cheers,
Franco