lkml.org 
[lkml]   [2006]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: forcedeth - WOL [SOLVED]
On Wed, 27 Sep 2006 22:38:06 +0200
Martin Filip <bugtraq@smoula.net> wrote:

> Hi,
>
> Bj__rn Steinbrink p____e v St 27. 09. 2006 v 20:38 +0200:
>
> > Did you check that WOL was enabled? I need to re-activate it after each
> > boot (I guess that's normal, not sure though).
> > The output of "ethtool eth0" should show:
> >
> > Supports Wake-on: g
> > Wake-on: g
> >
> Yes, of course :)
>
> > Also, I remember a bugzilla entry in which it was said that the MAC was
> > somehow reversed by the driver. I that is still the case (I can't find
> > the bugzilla entry right now), you might just reverse the MAC address in
> > your WOL packet to workaround the bug.
>
> Hey! this is really crazy :) but it works! To bo honest - I really do
> not know what crazy bug could cause problems like this. I thought it's
> NIC thing to manage all the work about WOL. I thought OS only sets NIC
> into "WOL mode".
>
> But seeing this - one packet for windows and one magic packet for linux
> driver - I really do not get it.
>

Are you saying that byte-reversing the MAC address make WOL work correctly?

What tool do you use to send the packet, and how is it being invoked?

Do we know if this reversal *always* happens with this driver, or only
sometimes?

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-09-28 01:59    [W:0.067 / U:0.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site