Equipment Support > Hardware By Brand > D-Link > [Info] D-Link DI 604 and Wake On Lan

[Info] D-Link DI 604 and Wake On Lan

I doubt you need to do a broadcast!

If you have a 1,000 computers on a WAN or LAN, and
you want to turn every single one OFF or ON,
in one fell swoop, then yes 0.0.0.255 on a /24
network would be needed for the magic packet
to reach all computers.

However, when you have 1 computer only, you can
sent the packet on port 9, to that computer only,
by doing a virtual server to 192.168.0.100 for port 9,
assuming that is the IP address of that computer
and you only want to use WOL on that single computer.

You can go right ahead and buy it, if that's the case.

reply to RevG
Thanks for your answer.
I have a local network with only two computers, one of them needs to be awakened. But how can I do a virtual server to 192.168.0.100, given that the PC is off and has subsequently no IP ?
I guess in this case the broadcast is the only solution ?

reply to RevG
Would setting a staic ip to the pc you want to wake do the trick?

reply to RevG
The 'Magic Packet' used by WoL uses the MAC address of the network connection. Since the device is off, the IP stack does not exist, and IP addresses have no meaning - only hardware addressing.

So in this case, I believe Basher and FoMoCo are wrong and you are correct - you *do* need to be able to broadcast to the subnet.

Read about WoL on this site here:
»Wake On LAN FAQ
and find a test here:
»/wakeup

I don't personally know whether the DI-604 correctly allows port forwarding to the broadcast address. Read more about similar attempts to get it to work here:
»[Help Me] DI-704 (Brown) and LAN broadcasts
including port forwarding to a specific IP address.

Hope this helps

Thanks for the links.
It looks like the D-Link routers don't allow port forwarding to the broadcast address...
Did someone find a trick ?

I disagree, once more, with rperkin.

Ethernet adaptors, like the dfe-530 tx+,
that support power management need to
understand Layer 3/4 to wake up the host properly.

If they were only aware of Layer 2, the host would be
constantly awakened by Ethernet broadcasts, and would
not be triggered by the Magic Packet!

I suspect we may be talking at cross purposes - and maybe even agreeing

There are a number of events that can wake an ACPI-compatible WinXP system from standby. A WoL Magic Packet is one of these, but not simply random Ethernet packets.

WoL is also capable of waking a suspended system, that is where the CPU is actually off as opposed to running at a low clock speed. And WoL - although initially targeted at PCs - has been implemented on non-PC architectures and is operating system neutral.

If the IP address is still associated with the system (and any arp cache contents not timed out) so that it can be reached by its IP address, then it is possible for a Magic Packet addressed to that specific IP address to cause WoL.

However, the more general case is for the Magic Packet to contain the subnet broadcast address. Clearly only the system whose Ethernet MAC address is specified will respond; others will simply discard it - the Magic Packet is specific to a single MAC address.

I guess the success of WoL depends on two things:
- the state of the system to be woken, and whether it can be reached at its IP address. If this is the case, the Magic Packet can be addressed to the IP address, as you suggest

- if not (and this is the more general case), then it is necessary to address the Magic Packet to the subnet broadcast address. And here there is an issue with some NAT router models which do not allow port forwarding to the broadcast address.

For those interested, here's an early white paper discussing AMD's proposal for WoL:
»www.amd.com.cn/CHCN/assets/conte···0213.pdf

Kind regards