the carrier.
-Original Message-
From: Petr Štetiar
Sent: Wednesday, 23 December 2020 12:27 am
To: Reuben Dowle
Cc: openwrt-devel@lists.openwrt.org
Subject: Re: [PATCH] dnsmasq: Ignore carrier status for bridge interfaces
Reuben Dowle [2020-07-16 00:10:43]:
Hi,
> This occurs
Reuben Dowle [2020-07-16 00:10:43]:
Hi,
> This occurs because netifd can incorrectly indicate carrier down on an
> interface through devstatus after issuing a carrier up hotplug event.
then it seems like this should be fixed in netifd.
> This patch ignores carrier status for bridge interfaces,
dnsmasq sometimes does not listen for DHCP at bootup on lan (see bug FS#1765).
This occurs because netifd can incorrectly indicate carrier down on an
interface through devstatus after issuing a carrier up hotplug event.
This patch ignores carrier status for bridge interfaces, as this does not
ref
: Ignore carrier status for bridge
interfaces
Reuben Dowle [2020-01-20 20:41:29]:
Hi,
> The information in this email communication (inclusive of attachments)
> is confidential to 4RF Limited and the intended recipient(s). If you
> are not the intended recipient(s), please note tha
Reuben Dowle [2020-01-20 20:41:29]:
Hi,
> The information in this email communication (inclusive of attachments) is
> confidential to 4RF Limited and the intended recipient(s). If you are not
> the intended recipient(s), please note that any use, disclosure,
> distribution or copying of this inf
dnsmasq sometimes does not listen for DHCP at bootup on lan (see bug FS#1765).
This occurs because netifd can incorrectly indicate carrier down on an
interface through devstatus after issuing a carrier up hotplug event.
This patch ignores carrier status for bridge interfaces, as this does not
ref
