> To prevent unwanted wake-ups, you'll need to ensure no device on the network is sending extraneous packets to the server
Assume the home network is using 10.0.x addresses.
I wonder if it would be useful to put the server on 10.1.x, add a virtual ethernet interface to the RPi that is also on 10.1.x, and configure the RPi to route between 10.0.x and 10.1.x. Configure the RPi to drop any extraneous packets directed to 10.1.x from 10.0.x.
On the Mac "route add -net 10.1.0.0/16 Rpi" and add a name and the server's IP to /etc/hosts.
With that approach you might also make it so the RPi runs a script whenever something tried to make a TCP connection to the server, and that script could deal with telling the server to wake. That way you can choose a wake method for the server without having to worry about whether or not other things on the network might accidentally trigger it.
Assume the home network is using 10.0.x addresses.
I wonder if it would be useful to put the server on 10.1.x, add a virtual ethernet interface to the RPi that is also on 10.1.x, and configure the RPi to route between 10.0.x and 10.1.x. Configure the RPi to drop any extraneous packets directed to 10.1.x from 10.0.x.
On the Mac "route add -net 10.1.0.0/16 Rpi" and add a name and the server's IP to /etc/hosts.
With that approach you might also make it so the RPi runs a script whenever something tried to make a TCP connection to the server, and that script could deal with telling the server to wake. That way you can choose a wake method for the server without having to worry about whether or not other things on the network might accidentally trigger it.