WOL within the same vlan and across different vlans

[roncro]

Hello,

I used to have a machine on a port with the "default settings" and also a work station, on a different (both 2960s) switch but also connected to a default port.

I was able to remotely wake up a computer (using RHEL/Centos ether-wake).

I assume that just works, because the machines are both on vlan 1, the native untagged default vlan.

I moved the client the machine I want to wake up, to vlan 2, it being a native vlan on that port:

interface GigabitEthernet1/0/2
switchport trunk native vlan 2
switchport trunk allowed vlan 2,4-7
switchport mode trunk

Another machine on a port with the same settings as above, should be able to wake the machine up, since it is in the same vlan(s) correct?  (Of course it doesn't else I'd wouldn't be writing this ost).

So what else is needed to be able to send a a WOL packet to a machine where the sender and receiver of the WOL packet are on a port configure like above.

The next ste is that, of course, I would like to send a wake up packet from a different vlan to the same machine I want to wake up.

Are there some udp/broadcast settings that by default come with vlan1, but not necessarilly with other vlans?

thanks,

Ron

[Richard Burts · Accepted solution]

Ron 

Thanks for the update. Glad to know that you got it sorted out and working. Raw ethertype was certainly a surprise. Glad there was an option to use udp. 

[paul driver · Accepted solution]

Hello

excellent news  -Udp forwarding did work then be it on the vlan2 broadcast address instead of the specific host address 

Thanks for the update glad you to hear you got it to work!

[roncro]

yes,  perfect!!

(I almost pulled some hair out here..  but ether-wake simply doesn't use udp anymore, wol that I am using now does.)

I am using the broadcast helper address,   "ip helper-address 192.168.2.255"  on the 0/1.1 interface.

I am using the "broadcast helper address" because of 2 more machines that I want to remotely wake up. As I understand it,  since it is a broadcast like 255.255.255.255:9 in the vlan1 broadcast domain,  the 0/1.1 interface will see it, so it needs to be the one that forwards it to the 0/1.2 interface.  correct?

Ron

[paul driver]

---

@roncro wrote:

yes,  perfect!!

(I almost pulled some hair out here..  but ether-wake simply doesn't use udp anymore, wol that I am using now does.)

I am using the broadcast helper address,   "ip helper-address 192.168.2.255"  on the 0/1.1 interface.

I am using the "broadcast helper address" because of 2 more machines that I want to remotely wake up. As I understand it,  since it is a broadcast like 255.255.255.255:9 in the vlan1 broadcast domain,  the 0/1.1 interface will see it, so it needs to be the one that forwards it to the 0/1.2 interface.  correct?

Ron

---

Correct!