Wake on lan not working..

[chili666]

Hmmm.... I also think it might be the bridge... It is a Netgear WGE101.

I tried wireshark and it gives me heaps of output ;-)

I filtered it for "ethernet", which leaves just:

9 0.644036 SlimDevi_12:42:6a Broadcast ARP Who has 192.168.178.42? Tell 192.168.178.43
9 0.644036 SlimDevi_12:42:6a Broadcast ARP Who has 192.168.178.42? Tell 192.168.178.43

And several more entries just like those two... I can´t even see if the squeezebox is sending a magic paket or not..

Could anybody tell me what I am supposed to be looking for?

Thanks.

Chili

[vrobin]

You should look for a WOL packet, it's one (or a bunch?) of single UDP packets, usually on port 9 ("echo" in AFAIK but it can be any port even if some devices only work with a given port number) containing in the data zone repeated at least 8 times the MAC Address of the network card of the device to wake up.

If you don't see anything on your wired network you should check some wifi scanner... or more easily, plug your SB in the wired network in ethernet and see if it works (I'm nearly sure it will).

[MajorD]

Is there a way to view the MAC address of the SlimServer through the SB3?

[Club1820]

You should look for a WOL packet, it's one (or a bunch?) of single UDP packets, usually on port 9 ("echo" in AFAIK but it can be any port even if some devices only work with a given port number) containing in the data zone repeated at least 8 times the MAC Address of the network card of the device to wake up.

If you don't see anything on your wired network you should check some wifi scanner... or more easily, plug your SB in the wired network in ethernet and see if it works (I'm nearly sure it will).

Ok. So I installed wireshark and filtered only on the UDP protocol for the IP address that my wireless SB3 is on. NOTHING. no activity.

When all protocols are enabled there is a bunch of activity. All of it being TCP protocol.

Did I do this right? Does this mean that the SB3 is not sending the necessary info to the server/or its not getting there to wake-on-lan?

Thanks!

[vrobin]

Do you spy wired of wireless network?

If your problem is the mac address problem, the wol packet will stop at the router/gateway and never be passed to the lan.

To be sure, try at first to make wol work with ethernet and deal with wifi problems in a second time when wired wol is working.

Here's a tool that can be useful:
http://www.depicus.com/wake-on-lan/w...n-monitor.aspx

The whole site:
http://www.depicus.com/wake-on-lan/

Is a golden mine for wol tools and information.

[Club1820]

Do you spy wired of wireless network?

Not sure what you meant by this. ?

I will try the websites you suggested for more info. and also wire the SB3 and then try WOL.

Thanks.

[vrobin]

Not sure what you meant by this. ?

Do you capture packet from the ethernet network or the wifi network? (don't know how wireshark deals with wireless cards).

[Club1820]

Do you capture packet from the ethernet network or the wifi network? (don't know how wireshark deals with wireless cards).

If I am understanding you correctly - its capturing from ethernet card. The server is on PC that is wired. The SB3 is wireless. Wireshark is installed on the wired, server PC.

Does that sound right? Sorry, this is all new to me.
Thanks.

[chili666]

Thanks for the link to WOL-Monitor.

I just tried it from a machine behind the bridge. Nothing is coming through. All my boxes behind the bridge are shown with only one mac-address in the stats of my router...

I have another bridge (Netgear WG602) lying around. Does anybody know if this makes a difference? Or are there any other chances, other than running cables, left?

Chili

[vrobin]

If I am understanding you correctly - its capturing from ethernet card. The server is on PC that is wired. The SB3 is wireless. Wireshark is installed on the wired, server PC.

Does that sound right? Sorry, this is all new to me.
Thanks.

Yes, capturing on the ethernet card... WOL packet addressed to the router MAC can possibly not be passed to the ethernet network, so I would't be surprised not to see it.