WoL from device on separate interface

JKnott

@NogBadTheBad said in WoL from device on separate interface:

wakeonlan under Ubuntu uses UDP port 9 and goes cross subnet.

Does pfSense support that? It has to recognize it's WoL and then broadcast the WoL frame to the network.

NogBadTheBad

It does seem to work.

I run homebridge on my IOT VLAN from a Raspberry Pi, there is a plug-in for my Synology NAS that sits on a different VLAN and I can restart my NAS remotely using the Apple home app on my iPhone.

Just done a packet capture on the interface the NAS sits on:-

pi@homebridge:~ $ wakeonlan -i 172.16.2.10 -p 9 00:11:32:4c:81:69
Sending magic packet to 172.16.2.10:9 with 00:11:32:4c:81:69
pi@homebridge:~ $

14:13:56.884304 00:08:a2:0a:9d:cb > 00:11:32:4c:81:69, ethertype IPv4 (0x0800), length 144: (tos 0x0, ttl 63, id 63699, offset 0, flags [DF], proto UDP (17), length 130)
    172.16.4.29.45220 > 172.16.2.10.9: [udp sum ok] UDP, length 102

johnpoz

Only way that could work is if pfsense knows the mac of that IP before.. So you have setup wol in pfsense so it always knows the mac of that IP, or you setup a static arp entry? etc..

I can send a unicast packet all day long to pfsense on whatever port.. But if pfsense doesn't have the mac of the destination IP its not going to send on the packet.

NogBadTheBad

@NogBadTheBad said in WoL from device on separate interface:

wakeonlan -i 172.16.1.23 -p 9 a8:20:66:10:fc:b7

The destination up address is in the wol command.

johnpoz

And again... pfsense is not going to send that on to the IP without knowing the mac.. If the device has been OFF.. it wouldn't know the mac without some sort of static setting.. Or the device would have to answer an arp, which they don't do if off.

its not going to look in that packet and say oh you want to send to that mac, let me do that for you ;)

NogBadTheBad

@johnpoz

My IP address are allocated via a DHCP reservation so they are in the routers ARP table.

johnpoz

There you go - yes if the mac is in the arp table then it will send it on ;) But billy bob user prob doesn't know to do that..

JKnott

@NogBadTheBad said in WoL from device on separate interface:

My IP address are allocated via a DHCP reservation so they are in the routers ARP table.

If you're talking about DHCP static mappings, that's not enough. For example, my ThinkPad hasn't been turned on since yesterday afternoon. While it's IP address is mapped to a MAC in the DHCP static mappings, it does not appear in the arp cache. For a MAC to be in the cache, the device must have recently sent a packet to/through pfSense.

johnpoz

^ agreed it won't be listed in the arp table - but pfsense might look there for mac on IP? Or if you have it in your wol settings, maybe it looks there.

But yeah pfsense needs to know the mac to send on the packet to it.. When pfsense doesn't know the mac it will arp, but if the box is off before pfsense can send on the wol it has to know what mac to send it too.

NogBadTheBad

Even if it shows as permanent in the arp table?

johnpoz

If it shows as perm in the arp table your fine - and how did you do that other than creating a static arp entry.. dhcp reservations do not do that, nor do wol entries that I can tell.

Did you actually create a static arp entry - that for sure would be best way to do it.

NogBadTheBad

Via static on the DHCP page.

johnpoz

Nope that doesn't do it.. I have plenty of dhcp reservations.. You mean this?

That has the problem that devices that are not listed can not talk to pfsense, ie get to the internet or any other vlan..

JKnott

@johnpoz

There is another setting for each individual mapping, which applies only to the IP/MAC pair.

NogBadTheBad

@johnpoz said in WoL from device on separate interface:

Nope that doesn't do it.. I have plenty of dhcp reservations.. You mean this?

That has the problem that devices that are not listed can not talk to pfsense, ie get to the internet or any other vlan..

yes there