Sorry for not specifying. This was observed on AA r39154 and r39928. Something I'm also looking into is whether olsrd (in my case v0.6.5-4) may be what gets confused, i.e. besides netifd. Especially since this problem only seems to occur at bootup on repeater nodes in an OLSR-managed mesh, not on the gateway nodes.
That is, I would see a repeater node respond to ping on its configured eth0 IP address for ~10sec briefly at boot and then go silent, suggesting something like a race condition at bootup. Adding the conflicting interface identifiers to /etc/config/wireless on a device that its already powered and out of bootup, and then issuing "wifi restart" does not trigger the failure. Pointing to a problem with bootup. On Thu, Mar 20, 2014 at 9:20 AM, Felix Fietkau <[email protected]> wrote: > On 2014-03-19 20:22, Ben West wrote: > > I believe I discovered that interfaces in /etc/config/network and > > /etc/config/wireless sharing the same identifier causes a collision of > > some sort that can disable all the device's network interfaces, i.e. > > such that it no longer even responds to ping on eth0. > > > > Possibly, this is intentional? > AA or trunk? > > At least in AA, wifi was still being set up by scripts that load both > the network config and the wireless config into one context, which is > probably causing these issues. > In trunk, wireless is being configured by netifd, which passes the full > config to the scripts, so it should be fixed there. > > - Felix > -- Ben West http://gowasabi.net [email protected] 314-246-9434
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
