Closed everloop2 closed 4 years ago
I've also seen this messages a lot on regular LAN-based uplinks, so nothing special to "DSL-Boxes". But will this change break getting dhcp-config on the interface?
But will this change break getting dhcp-config on the interface?
Got it ... it's stopping the dnsmasq dhcpserver to listen on this interface. @everloop2 can you PR this?
Btw. I'm quite sure this is caused by the "no-tunnel" images when ffuplink requests an address on this interface too (#624).
Based on this, shouldn't we also include "ffuplink_wan" to the notinterface list?
yep, ffuplink_wan also can/should be ignored.
created pull: https://github.com/freifunk-berlin/firmware-packages/pull/212 - did close due not woking - false command used: not uci set
https://github.com/freifunk-berlin/firmware-packages/pull/213 - working version: uci add_list
Firmware Version:
master: Freifunk Berlin Development 91b6ae0 -> think all others too
What is the problem?
syslog is spammed by:
daemon.warn dnsmasq-dhcp[2184]: DHCP packet received on br-wan which has no address
after bootup, (dunno if DSL_BOX related?)What is the expected behaviour?
dnsmasq should not care for br-wan / be quiet
workaround/solution:
insert: