LAN Configuration

The gateway’s LAN port can be configured to match your network requirements. By default, it is set to obtain an IP address automatically via DHCP.

Port Assignments

The gateway has two Ethernet roles:

Sensor port — Connects to the EQ Wave sensor via the media converter. Fixed at 192.168.10.2/24. Not user-configurable.
LAN port — Connects to your facility network. Configurable (DHCP by default).

Which physical port or network interface fills each role depends on the gateway hardware:

Gateway	Sensor Port	LAN Port	Notes
Compulab IOT-GATE-iMX8PLUS	`eth1` (case label: ETH1)	`eth0` (case label: ETH2)	Case label ETH2 does not match OS name `eth0`. PoE input on this port.
Compulab IOT-DIN-iMX8PLUS	`eth1` (case label: ETH1, top)	`eth0` (case label: ETH0, bottom)	Case labels match OS interface names.
Raspberry Pi 5	`eth0` (built-in)	USB Ethernet adapter or Wi-Fi	Built-in NIC is used for the sensor because it has lower latency than USB.
Flex (customer hardware)	Lowest-latency NIC	Secondary NIC or Wi-Fi	Assign the NIC closest to the CPU (e.g., PCIe-attached, not USB) as the sensor port.

The gateway software creates two NetworkManager connection profiles that abstract away these differences: eq-sensor (sensor port) and eq-lan (LAN port). The nmcli commands in this guide use these profile names and work on all platforms.

Prerequisites

SSH access to the gateway
Choice and details of the network configuration:
1. DHCP configuration:
  - Network CIDR from your administrator (e.g., 192.168.1.0/24)
2. Static IP configuration:
  - Network details from your administrator:
    - IP address and subnet mask (e.g., 192.168.1.100/24)
    - Gateway address
    - DNS server addresses (optional)
3. Direct PC connection:
  - Choose a static IP/subnet (<static-ip>/<subnet>) for the gateway. Any valid IP/subnet will work, but we recommend 192.168.1.2/24 because:
    - It’s a commonly used private network range
    - It allows direct connection while keeping the sensor connected

warning

If you plan to connect the gateway to a LAN, configure the IP settings according to your network requirements instead of using the direct PC connection settings.

Steps

1. View Current Configuration

# List all network connections
nmcli connection show

# Show details for LAN connection
nmcli connection show "eq-lan"

# Show active connections (green indicates active)
nmcli -p connection show

2. Implement the Chosen IP Configuration

Choose one of the following configuration methods:

Option A: DHCP Configuration (Default)

To use automatic IP address configuration:

sudo nmcli connection modify "eq-lan" ipv4.method auto

Option B: Static IP Configuration

You might want to configure a static IP address in these scenarios:

Network policy requires static IP addresses
Direct connection to a PC/laptop (when not connecting to a LAN)

For LAN integration with static IP requirements:

sudo nmcli connection modify "eq-lan" \
    ipv4.method manual \
    ipv4.addresses "<ip-address>/<subnet-mask>" \
    ipv4.gateway "<gateway-address>" \
    ipv4.dns "<dns-servers>"

Example using typical values (coordinate with your network administrator):

sudo nmcli connection modify "eq-lan" \
    ipv4.method manual \
    ipv4.addresses "192.168.1.100/24" \
    ipv4.gateway "192.168.1.1" \
    ipv4.dns "8.8.8.8,8.8.4.4"

For direct PC connection:

sudo nmcli connection modify "eq-lan" \
    ipv4.method manual \
    ipv4.addresses "<static-ip>/<subnet>"  # Use your chosen static IP and subnet from prerequisites

3. Activate the New Configuration

sudo nmcli connection down "eq-lan"
sudo nmcli connection up "eq-lan"

4. Verify Configuration

After applying the configuration:

For LAN connection:
- Connect the gateway’s LAN port to your network
- Check the gateway’s IP address:
```
nmcli connection show "eq-lan" | grep IP4.ADDRESS
```
For direct PC connection:
- Set your PC’s network adapter to a static IP in the same subnet as your chosen static IP (but different from the gateway’s IP)
- For example, with gateway IP 192.168.1.2/24:
  - Configure your PC as 192.168.1.3/24
- Connect an Ethernet cable between your PC and the gateway’s LAN port
- Your gateway’s IP address will be your chosen static IP

important

Make note of the gateway’s IP address for future access.

5. Allow SSH Access

The gateway’s firewall only allows SSH from the sensor subnet (192.168.10.0/24) and the VPN (100.64.0.0/16) by default. To access the gateway via your LAN, add a firewall rule for your subnet:

# Replace <network-cidr> with your subnet
# For example: 192.168.2.0/24 or 10.0.1.0/24
sudo ufw allow from <network-cidr> to any port ssh

6. Verify SSH Access

Test the new configuration by connecting to the gateway following SSH Access

Troubleshooting

If you lose network connectivity or cannot connect:

Check network cable connections
Verify IP address configuration with nmcli connection show "eq-lan"
Review firewall rules with sudo ufw status
Test network connectivity

You can always access the gateway through the sensor port if needed.

Energy Quotient™ Platform Documentation