Thus your PC will wake despite it going to the other device." The hub then broadcasts the packet to all devices because it doesn't know who it is intended for. The router forwards the packet to that LAN IP address to the hub. The reason you port forward to the always on device is that your router needs a "live" device to keep the ARP entry alive. It will broadcast the packet to it regardless which device you have port forwarded to. Some of you may be scratching your head as to why should we port forward to the always on device and not the PC, well that is the beauty of the hub. Then you will need to port forward to the always on device. You then should create a reserved LAN IP for the always on device so it never changes to a different LAN IP. Also if you have a setting "WoL & Shutdown Link Speed" for your NIC, you should probably set it to whatever the other device supports just to be safe, usually 100Mbps. Plug your PC and the always on device into the hub. Plug the hub in one of the routers LAN ports. Plug the hub behind your router (better) If you are going to plug it behind the router, you are going to have to have a device on the hub that is always on so the router won't kill the line, VoIP or something. Now there are two ways you can get this to work: 1. Hubs and this is the key word here, "broadcast", the data to all devices connected to it. "Why a hub? Hubs are dumb and they do not direct traffic like routers and switches. So judging from what u said the following does not work? I can see the packet and it has the mac address of PC1 but the destination address is the IP address of PC2. What I am doing is trying to replicate the following which I read from another forum. Kurt You mention that "neither case will awake PC1, even if PC1 receives the broadcast packet, as the WOL packet is not intended for PC1." If it shows up in Wireshark, that would strongly suggest that, if PC1 isn't waking up, the problem isn't that it's not receiving the wakeup packet - perhaps its Ethernet adapter doesn't support Wake-on-LAN, or does but doesn't have its wakeup signal wired to the appropriate support chip (i.e., the adapter supports Wake-on-LAN but the PC as a whole doesn't), or the operating system doesn't support that wakeup signal. You could also try running Wireshark on PC1 and, even though it's awake, try sending it a Wake-on-LAN packet, and see whether it shows up in Wireshark. If the hub truly is a hub, rather than a switch that's called a hub, and if the router and the two PCs (all of which I assume are plugged into the hub) are all running at the same speed (all at 10Mb/s or all at 100Mb/s), then, if you have an unused port on the hub, you should be able to run a sniffer on a machine plugged into that port and see all the traffic going through the hub. to every machine plugged into the hub except for the machine sending the broadcast (I don't know of any Ethernet adapters that receive their own transmissions - they might listen to their own transmissions for collision detection, but they don't treat it as an incoming packet, eve in promiscuous mode). If the packet is truly a broadcast, it's made to all machines on the network segment, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |