Skip to main content
Version: v25.07.31

Ethernet Troubleshooting

This document shows simple ways to troubleshoot Ethernet settings on CE devices. It doesn't matter whether the connection uses DHCP, static IP, or PPPoE. This guide explains the main steps and commands to diagnose and fix common problems.

It includes:

  • How to log in to the CE terminal and view the last settings.
  • Check the current IP address and interface status.
  • View the system log for Ethernet interfaces.
  • View the run-time service for Ethernet interfaces.
  • Verify the system's network settings using UCI.

By following the steps in this guide, users can diagnose and fix most Ethernet problems themselves.

Troubleshooting Steps​

Cloud configuration verification​

This section details how to check the configurations made in the cloud. The commands below can be used to verify the cloud configuration.

Access the CE Terminal​

Follow these steps to gain access to the CE device via the Command Line Interface (CLI).

sudo su -

The sudo su - command starts a shell session with superuser privileges, enabling execution of tasks that require elevated permissions, such as networking and system configuration.

Verify the Last Applied Configuration​

This command is used to view information about the last successfully applied Ethernet configuration. Here this command is used to check the configuration details of the eth0 Ethernet interface from the stored configuration response JSON file.

cat /tmp/last_config_response.json | jq '.interfacesConfig.ethernet.eth0'

This example output shows the last configuration done on Ethernet.

Example Response:​

{
  "disable": false,
  "trafficPolicy": null,
  "zoneType": "wan",
  "multiWanConfigType": "dhcp",
  "isPrimaryMultiWan": false,
  "isSecondaryMultiWan": false,
  "multiWanFailOverTime": null,
  "multiWanRestoreTime": null,
  "multiWanPingTarget": null,
  "multiWanNotificationEmail": null,
  "interfaceName": "eth0",
  "configType": "dhcp",
  "bridgeGroup": null,
  "addresses": [
    {
      "address": "10.255.254.50",
      "netmask": "255.255.255.0",
      "gatewayIp": null,
      "announce": false
    }
  ],
  "description": "WAN Interface eth0",
  "isAutoConfigured": 0,
  "status": null,
  "duplex": null,
  "mtu": 0,
  "speed": null,
  "isHubInterface": null,
  "pppoeUser": null,
  "pppoePassword": null,
  "multiWanConfig": {
    "interfaceName": "eth0",
    "targetIps": [
      "8.8.8.8",
      "4.2.2.2"
    ],
    "failureInterval": 5,
    "recoveryInterval": 5,
    "pingInterval": 5,
    "pingTimeout": 2,
    "multiWANMetric": 1,
    "multiWANWeight": 2,
    "enable": false
  }
}
Q:1 What is the purpose of cloud configuration verification?

Cloud configuration verification ensures that the CE device has correctly received and applied the latest Ethernet settings pushed from the cloud platform. By checking the stored configuration, you can confirm: Whether the correct interface type (DHCP, Static, PPPoE) was applied, Whether IP, netmask, gateway, and Multi‑WAN settings were delivered properly, Whether any mismatch exists between cloud settings and the CE’s actual runtime behavior. This step helps identify configuration sync issues before moving on to deeper troubleshooting.

Q:2 Which file stores the last configuration received from the cloud?

The last configuration received from the cloud is stored in: /tmp/last_config_response.json. This JSON file contains the most recent Ethernet configuration applied to the CE, including interface type, IP settings, Multi‑WAN parameters, and other interface attributes. It is the primary reference for verifying what the cloud has pushed to the device.