Richard Clark <rich...@kerkhofftech.ca> wrote: >> Hi Richard, >> >> the link status is not propagated to the netdev because there's an >> external switch chip between the CPU and the RJ45 plug on the outside. >> >> There currently is no mechanism to propagate switch port states to Linux >> netdev link states as such an mechanism has various implications. >>
> Ok, that makes sense. Just my dumb luck that the little portable > GL-Inet I was developing on happens to not have an internal switch, so > everything was fine there. > So currently it looks like good chunk of routers seem to follow the same > block diagram as the original WRT54g and are going to have the same > issue. All the netifd handling to start/stop services on link state > never gets used. So, just to realize that you probably want active DNA[1] anyway, as even on a device that has directly connected ports, plugging in a dumb switch will give you link, yet there is really nothing beyond it. [1]- https://tools.ietf.org/wg/dna/ Detecting Network Attachment _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel