SSH Access
The gateway has two Ethernet ports: the sensor port and the LAN port. We recommend starting setup through the sensor port, which always works with a direct Ethernet cable:
- Initial SSH access — Connect directly to the sensor port (fixed at 192.168.10.2).
- Configure LAN — Via SSH, follow LAN Configuration.
- Ongoing access — SSH over the LAN port via your facility network or Wi-Fi.
Alternatively, if the gateway’s LAN port is connected to a DHCP-served network with internet access, and your service includes remote management (as pilot gateways do), our support team can assist remotely via VPN — including sharing the gateway’s LAN IP address and opening the firewall for local SSH access on your behalf. Contact [email protected] to arrange this.
If you prefer to set up access yourself, you can also SSH in via the LAN port if you know the DHCP-assigned address (e.g., from your router’s client list) — but you will first need to add your LAN subnet to the firewall via the sensor port (see Allow SSH Access).
note
Which physical port is the “sensor port” depends on your gateway hardware. On Compulab gateways, it is the port labeled ETH1 on the case. See Port Assignments for all platforms.
Firewall
The gateway runs UFW (Uncomplicated Firewall) with a default-deny incoming policy. These ports are open after provisioning:
| Port | Protocol | Service | Allowed From |
|---|---|---|---|
| 22 | TCP | SSH | 192.168.10.0/24 (sensor), 100.64.0.0/16 (VPN) |
| 80 | TCP | EQ Sight | All IPv4 addresses |
SSH is only allowed from the sensor subnet and the VPN. To access the gateway via your LAN, you must add a firewall rule for your subnet during LAN Configuration.
Prerequisites
For all access methods:
- Admin username and password from system documentation
- SSH client:
For sensor port access:
- Ethernet cable
- Ability to configure PC network settings
For LAN port access:
- Network connection
- Gateway’s IP address (otherwise some options for finding it are suggested below)
Initial Access via Sensor Port
The sensor port provides a reliable way to access the gateway with its fixed configuration:
-
Connect your computer directly to the gateway’s sensor port using an Ethernet cable
-
Configure your computer’s Ethernet adapter with a static IP address:
- IP Address: 192.168.10.3 (or any address in 192.168.10.0/24 except 192.168.10.2)
- Subnet Mask: 255.255.255.0
-
Connect using your chosen SSH client with these parameters:
- Host:
192.168.10.2 - Username:
admin - Port: 22
- Connection type: SSH
If using a terminal, the command is:
ssh [email protected] - Host:
After establishing this initial connection, you should:
- Configure the LAN port for your network following LAN Configuration
- If supported and desired, connect to your wireless network following Wi-Fi Configuration
- Test SSH access through the LAN port and/or Wi-Fi
- Disconnect your computer and reconnect the sensor to the sensor port
The LAN port will then become your primary means of accessing the gateway, with Wi-Fi and the sensor port remaining available if needed.
Network Access (LAN/Wi-Fi)
-
Find your gateway’s IP address using one of the following methods
Option A: Use the IP address from your network configuration
- For LAN: See LAN Configuration
- For Wi-Fi: See Wi-Fi Configuration
Option B: Ask your network administrator
Option C: Use your router’s admin interface
- Access your router’s web interface (typically at 192.168.1.1 or similar)
- Look for “Connected Devices” or “DHCP Clients”
- Find the device named
EQG-XXXXwhereXXXXis your gateway’s identifier (capitalized hex)
Option D: Scan your network
- Windows: Use Advanced IP Scanner (download)
- Linux/macOS: Use nmap
# Adjust this to match your network: sudo nmap -sn 192.168.1.0/24
-
Connect using your chosen SSH client with these parameters:
- Host:
<gateway-ip-address> - Username:
admin - Port: 22
- Connection type: SSH
If using a terminal, the command is:
ssh admin@<gateway-ip-address> - Host:
-
Enter the admin password when prompted
Need Help?
If you are unable to establish a connection, contact [email protected]. If the gateway has internet access via the LAN port, we can typically resolve access issues remotely via VPN. Otherwise, we can provide a USB debug cable and instructions for direct console access.