XLX_Installation_Doc_21.10.2021
XLX_Installation_Doc_21.10.2021
21.10.2021
1. Copyright:
The XLX Multiprotocol Gateway Reflector Server is part of the software system for the D-Star
Network.
The sources are published under GPL Licenses.
2. Usage:
The packages which are described in this document are designed to install server software
which is used for the D-Star network infrastructure.
It requires a 24/7 internet connection which can support 20 voice streams or more to
connect repeaters and hotspot dongles!!
If you want to run this software please make sure that you can provide this service free of
charge, like the developer team provides the software and the network infrastructure free
of charge!
3. Requirements:
The software packages for Linux are tested on Debian7 (Wheezy) 32 and 64bit or newer.
Raspbian will work but is not recommended.
Please use the stable version listed above, we cannot support others.
4. Supported Protocols:
Firewall settings:
XLX Server requires the following ports to be open and forwarded properly for in- and outgoing
network traffic:
The hash file to access the xlxapi server and the way of working:
After activating the calling home feature, the dashboard creates a file called
“callinghome.php” in the /tmp folder of your Linux.
This file contains the timestamp and the hash file that you need to access the xlxapi server
database.
The first time, we need to use this folder because it’s the only folder on a Linux system
where everybody has full write access.
The problem with the /tmp folder is that Linux cleans up this folder on every server reboot
and you are losing the callinghome.php with your hash file!
If the dashboard doesn’t find the callinghome.php, a new one will be created automatically,
but of course the hash which is random will be a new one.
So this one does not match the hash you had initially and your XLX has no access to the
database any more.
You have two possibilities.
1.You backup your working hash, located in /tmp and put it back to /tmp after rebooting.
2.You are creating a folder called for example callhome, give full write access to this folder
and change the callinghome.php path in the config.inc.php to the new location.
Definitely the best way, and of course you can set this up before activating the calling home
feature.
# cd /
# mkdir callhome
# chmod 777 callhome
# pico /var/www/html/pgs/config.inc.php
//change the calling home location from /tmp/callinghome.php
to /callhome/callinghome.php
When done, the dashboard will create a new callinghome.php with a new hash file into this
folder.
The reflector status will stay red, until I update the new hash file manually in the database.
Known issue:
From time to time, it happens that the hash file became blank?!
I’m not 100% sure about the cause, but one fact makes me believe that it has something to
do with the growing /var/log/messages.
The behavior only happens after a long running period without rebooting the server.
After purging the messages logfile (# echo”” > /var/log/messages ), the callinghome.php
stays proper again !??