On Sunday 19 July 2009 14:22:38 Matthias Buecher / Germany wrote: > On 19.07.2009 13:52, Malte S. Stretz wrote: > > On Sunday 19 July 2009 13:27:47 Matthias Buecher / Germany wrote: > >> [...] > > > > And even if eth0 is bridged, etherwake should work on the base device > > eth0 as well if I'm not mistaken. > > > > Anyway, if it doesn't work for you, I guess the best way to handle this > > is by doing something like this in the scripts which use etherwake: > > > > . /etc/functions.sh > > include /lib/network > > DEFAULT_IFACE=lan > > scan_interfaces > > config_get iface $DEFAULT_IFACE ifname > > etherwake -i $iface "$@" > > > > The $DEFAULT_IFACE could be made configurable. > > For my private script I currently use the following code, which works > great. As I'm the only user of the script, a simple env var is good enough. > [...]
Try the attached script :) Cheers, Malte --
uciwol
Description: application/shellscript
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
