Roughly speaking it handles RTM_GETLINK events from network devices and fires off a shell script in response. I use it to admin up a network interface when created and then to fire off DHCP to configure when it is runnable (IFF_RUNNING). I just started looking at moving both route and mdev to use netlink/rtnetlink. I'll take a look at extending mdev to support RTM_GETLINK messages. For now consider this patch abandoned and I'll come back after I read up a bit more.
- Eric On Mon, May 11, 2020 at 8:32 PM Rob Landley <r...@landley.net> wrote: > On 5/10/20 1:34 PM, Eric Molitor wrote: > > A simple implementation of ifplugd that I'm using on a few personal > projects. > > I've cleaned it up and attempted to mostly adhere to the toybox coding > style. > > Quick glance, it says to look at an example ifplugd.action script which > isn't > included? > > I note that I'm averse to commands that _need_ an external script to > function. > When I finish cleaning up dhcp you should be able to "dhcp -i eth0" and > have it > just _do_ it, for example. (An optional script it calls out to if > detected, or > if told to do so on the command line, is one thing. "will not work at all > without it" is another.) > > But then... I dunno what ifplugd is supposed to _do_ exactly? (Haven't used > it...) I had a todo item to teach mdev to respond to more hotplug events, > and > ethernet transceiver toggle (and the wireless equivalent) was in there, > but it's > a big todo heap of "haven't made a wpasupplicant yet, but I did go to the > talk > from the guy who was writing a new replacement thingy for all that > infrastructure"... > > Rob >
_______________________________________________ Toybox mailing list Toybox@lists.landley.net http://lists.landley.net/listinfo.cgi/toybox-landley.net