"sudo eps-configure.sh"./usr/bin/eps-configure.sh was added to the product. This script should make configuration much easier. Instead of manually editing /etc/eps.conf, you may want to try and run "sudo eps-configure.sh" after the .deb or .rpm package has been installed. On the central server, install and run EPS like this:
(Or, see the installed script /usr/bin/eps-server.sh for a shell script that auto-restarts the server.)
Once the server is running, note the encryption/decryption configuration cipher settings saved to /etc/eps.conf:
On each of the clients, install and run the client like this:
(Or, see the installed script /usr/bin/eps-client.sh for a shell script that auto-restarts the client.)
Edit the file /etc/eps.conf and paste in the 2 cipher settings from the server. For example:
Note the cipher_key and cipher_iv are the only 2 lines you need to copy from the server to the client. After the eps.conf file has been saved, restart the EPS client.
Once you have 2 or more clients running, the EPS network will be up and running. Either run "/sbin/ifconfig eps0" to see which IP address has been assigned to each client, or look at the contents of the log file /var/log/eps_client_0.log.
A list of client IP addresses is logged to all client log files every time a new client joins the EPS network. You can see all the client IP addresses by running this on any of the connected clients:
The same list is also logged to the server's log file. You can see all the client IP addresses by running this on the server:
Additionally, an entry is created in /etc/hosts for each peer device. You can access the peers using the hostname.