Installation and start of the ApplicGate on Linux with .NET 8.0 or higher
- Copy ApplicGate.dll and ApplicGate.runtimeconfig.json to a new directory (e.g. /home/GateAdmin/ApplicGate)
- Change to this directory and issue one of the following commands:
-- For standard example (with the configuration files routing.csv and groups.csv): dotnet ApplicGate.dll /install
-- For sample EAS configuration (with the configuration files routing.csv and groups.csv): dotnet ApplicGate.dll /install:EAS
-- For sample RSP remote configuration (with the configuration files routing.csv and groups.csv): dotnet ApplicGate.dll /install:RSPremote!DestinationIP!DestinationPort!certificate
--- DestinationIP, DestinationPort and certificate are parameters for the autologon routing entry:
---- Default DestinationIP is vpn.testcomp.com
---- Default DestinationPort is 441
---- Default certificate for the keyword SSLTARGET is snnn.rsp@testcomp.com.pfx/snnnrsp, the certificate must be created separately.
-- For sample RSP VPN Server configuration (with the configuration files routing.csv and groups.csv): dotnet ApplicGate.dll /install:RSPvpnServer!GatewayIP!Port1!Port2!certificate
--- GatewayIP, Port1 and Port2 are parameters for the reverselogon routing entries:
---- Default GatewayIP is *
---- Default Port1 (logon of remote servers) is 441
---- Default Port2 (logon of clients) is 442
--- certificate is a parameter for the SSL keywords:
---- Default certificate is vpn.testcomp.com.pfx/vpntest, the certificate must be created separately.
- The service applicgate.service will be enabled and started.
- Start your browser as displayed to access ApplicGate:
-- The first manage entry of routing.csv will be shown (usually http://127.0.0.1:98).
- During installation the license will be checked: The license must be stored in group License!
- All necessary files will be written to the directory where ApplicGate.dll is stored.
- Hint: You can store your customized routing.csv and groups.csv files before you start the installation because existing files will not be overwritten.
Detailed description:
Start of ApplicGate:
Argument 1: File name of Routing Table (if full is path omitted, path of dll file will be used) or /help
Argument 2 (optional): File name of Group Table (full path or path of argument 1 is used)
Argument 3 (optional): File name for Backup configuration
e.g. dotnet ApplicGate.dll routing.csv groups.csv
Usually the Application Gateway is started using systemd:
Build a bash file, eg. applicgate.start (example see below):
#!/bin/bash
# Start ApplicGate
#
echo Starting ApplicGate ...
%export%
dotnet ApplicGate.dll routing.csv groups.csv
while [ $? -eq 1 ]
do
echo Restarting ApplicGate ...
dotnet ApplicGate.dll routing.csv groups.csv
done
echo ApplicGate stopped: exit code $?
Do not forget to set the protection e.g. chmod o+x,g+x,u+x applicgate.start
Then define a configuration file for systemd, e.g. applicgate.service
[Unit]
Description=ApplicGate
After=network-online.target
Wants=network-online.target
[Service]
ExecStart=/home/GateAdmin/ApplicGate/applicgate.start
WorkingDirectory=/home/GateAdmin/ApplicGate
[Install]
WantedBy=multi-user.target
Then enable and start the service:
sudo systemctl enable /home/GateAdmin/ApplicGate/applicgate.service
sudo systemctl start applicgate.service
List of Error Levels of ApplicGate.exe:
0 ... Stopped via web interface
1 ... Restart request via web interface
2 ... Cannot load Routing table (see log file)
3 ... Cannot load Group table (see log file)
4 ... Arguments are missing, usage will be displayed
6 ... Cannot open log file in default directory
Hint to install a new version of the program:
- Rename old program files
- Copy new version of program files
- Issue restart via web interface
