Hi,

I have a raspberry pi, connected via crossover cable to a HP N54L Microserver - both are using wireless USB adapter to connect to the router for internet and I have just connected a crossover cable between the two so I can try and WoL over it.

This may sound mad but I have my reasons .

When my microserver is connected to the router via ethernet WoL works perfectly.

With my new crossover cable connection I ran sudo ifconfig eth0 10.0.0.1 on the pi and ifconfig eth0 10.0.0.2 on the microserver and I can ssh between the two quite happily using just the crossover cable connection.

When I run:
wakeonlan AA:BB:CCD:EE:FF from the pi I get nothing
I also tried wakeonlan AA:BB:CCD:EE:FF -i 10.0.0.2 in case that might help but this didn't work either.

Is there a way I can do this?

Thanks,
Matt

Then I'd wonder if power is being applied to the nic. WOL has to have power applied to the nic and it should be known on the lan by arp. Also bios issue to enable wol. Not sure about OS, might be some issue there.

Maybe a default interface issue? The WOL packets could be going out of your wireless USB adapter to the router rather than through the crossover cable. Maybe that's what the "-i" flag in wakeonlan does, not sure, I can't seem to find a man page anywhere.

I guess it is possible that the auto mdx feature isn't working correctly for some reason. If on same subnet and lan segment then it should have arp packets.

"--ipaddr=HOST
Broadcast packet to this IP address or hostname. This is important if your wol client is a multihomed host and you want to send only to one subnet (default IP address is 255.255.255.255). "

http://linux.die.net/man/1/wol