ARPergefactor supports two different modes of operation, to allow for a great range of setups. Choose your preferred mode, based on the infrastructure at hand.

<?xml version="1.0" encoding="UTF-8"?>
<ExpergefactorConfig version="2" scope="network|host">

  <!-- everything else -->

</ExpergefactorConfig>

💻 host

If you only have two devices in your setup (a client and a server), you probably need to use the host scope. In this mode of operation only packets that originate from the device on which ARPergefactor is installed on are taken into consideration for waking another host. We also won't try to manipulate the address resolution cache of other hosts on the network, which can be a good choice, if you are part of a greater network.

📡 network

But if you have a spare device on your network, which happens to be always-on anyway (maybe a Raspberry PI or something like that), you should try to run ARPergefactor on that device with the network scope. While in this mode packets from all hosts on the network can trigger the wake of your server system, without the need to run ARPergefactor on each and every client. Be aware, that we will manipulate the address resolution cache of other hosts temporarily, if you start using ServiceFilterRules, in order to find out which service is being accessed. Usually that shouldn't break anything, but it can alarm the administrators of the network, if this wasn't you in the first place.