Solved Wake on LAN over different VLANS

[Wayne Workman]

@szecca1 Better yet, see if you can get in touch with a Nortel person and see what they say about it. Or search their website for information.

[szecca1]

@Wayne-Workman I put an email to my company because I didn’t want to try it and cause my entire network to go down. As soon as I hear from them I will give it a try

[Wayne Workman]

@szecca1 Try it and see.

[szecca1]

@cml I double checked and we already enabled that portion of the switch and still nothing. But I did find a configuration on the switch from broadcast addresses and nothing is listed. Do you think if I entered the broadcast address there,the passport would then allow the packets to pass through the VLANs?

[cml]

Not familiar with Nortel’s configuration, but there is this post:

http://blog.michaelfmcnamara.com/2009/02/wake-on-lan-and-directed-broadcast/

[szecca1]

@cml My layer 3 device is Nortel 8010

[Wayne Workman]

I thought this article was pretty good.
http://theithollow.com/2012/04/how-to-broadcast-across-subnets/

[cml]

Your switch is not forwarding the packets across subnets. Do you know what manufacture/model your L3 device is?

[szecca1]

@cml You are correct, the top one is on the same vlan as the fog server.

I just ran wireshark on the bottom machine and ran wol from the fog server and wireshark didnt pick anything up

[cml]

The top one is on the same subnet as your fog server correct?

Try running wireshark on the bottom machine (i assume it is on the same subnet as your target), but send the wol from your fog server.

[szecca1]

@cml

Ok i did exactly what you said. the top one is from a computer in the 10.1.x.x address and the bottom one which is the one that worked is from the 10.2.x.x address.

[cml]

@szecca1

In wireshark first select your connection and then click start

Once started type wol into the filter box and click on apply.

This is what it looks like when I send a wol:

[szecca1]

@cml
I attempted to do that and by the image you see I tried exactly the same thing and the computer doesnt turn on.
I have wireshark but have never used the program to know how to filter to wol

[cml]

One thing you can try is sending the packet from the command line with wakeonlan

wakeonlan 28:D2:44:0C:D9:9B
Sending magic packet to 255.255.255.255:9 with 28:D2:44:0C:D9:9B

Do you have wireshark? If so set the filter to wol and see if you get a packet, if not your switches may be blocking it.

Here were the relevent Cisco commands I had to set on our 4500:

***fogserver vlan***
interface Vlan2					
 ip helper-address 10.2.255.255
!
***high network vlan***
interface Vlan1					
 ip helper-address 10.1.0.119
 ip directed-broadcast 101
!
ip forward-protocol udp echo
ip forward-protocol udp discard

access-list 101 permit udp host 10.1.0.119 any eq echo
access-list 101 permit udp host 10.1.0.119 any eq discard

[szecca1]

@Wayne-Workman I just downloaded this program and tested it exactly how you had asked and the computer wakes up perfectly fine. I then turned it off and attempted to wake on lan again from FOG and again to no avail. So you’re saying it’s a switch/router config thats to blame but I am not sure where that could be.

[Wayne Workman]

@szecca1

OK… troubleshooting time I suppose.

You need to find a utility that will send a wake-on-lan packet to your desired IP address… (the broadcast address).

Then,
Go on site and see if you can broadcast a WOL packet and see if computers start up. If it works, then your switches / router configurations are to blame.

If it doesn’t work… maybe make sure WOL is enabled on those computers… maybe try to WOL an individual client and see if that works.

Report back and we will go from there.

I’d recommend trying this one:
http://sourceforge.net/projects/aquilawol/

[szecca1]

@Wayne-Workman “The three default subnet masks are 255.0.0.0 for Class A, 255.255.0.0 for class B, and 255.255.255.0 for Class C.”

From this my impression is we have a class B subnet mask but I could be wrong, but I dont think this matters as whichever class it is, wake on lan isnt working lol

[Wayne Workman]

Your public IP might be a Class B address…

But internally, you have Class A addressing via NAT.

[szecca1]

@Tom-Elliott ok that makes sense, and I ran another test and still wake on lan is not working. At this point I am not sure what to do. The imaging works perfectly but the clients have to be on in order for the imaging to go through, obviously.

[Tom Elliott]

That’s often the case class a class B classy are usually directed by the first octet one through 126.whatever is considered class a, 128.whatever through 191.whatever is considered class b,192 up is class c