On 19.07.2009 14:52, Malte S. Stretz wrote:
> 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 t
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
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 handl
On Sunday 19 July 2009 13:27:47 Matthias Buecher / Germany wrote:
>[...]
> I'm done creating the patches for etherwake and busybox's ether-wake to
> use br-lan as a default.
> But can somebody confirm that br-lan is also a working interface for
> other devices or Kamikaze 8.09 in general?
Kamikaze
Matthias "Maddes" Bücher
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
On 18.07.2009 21:33, Matthias Buecher / Germany wrote:
> Hi everybody,
>
> I just found out that etherwake and busybox's ether-wake are not working
> with the default interface "eth0", but with "br-lan".
> This is
Hi everybody,
I just found out that etherwake and busybox's ether-wake are not working
with the default interface "eth0", but with "br-lan".
This is on a WRT350Nv2 with Marvell Orion CPU.
Now my questions:
#1
Is this a WRT350Nv2 / Marvell Orion specific issue?
Or is "br-lan" the right interface f
