For the ConnectPort X2
, XBee Gateway
(formerly X2e ZB), and ConnectPort X2e for Smart Energy
(SE), the default network settings of the Ethernet
models are set to DHCP Client,
with no default IP address or network settings. The Gateway expects to receive an IP address from your DHCP server (along with the Subnet mask, Default gateway address, and Primary/Secondary DNS server address(es)).
The default network settings of the XBee Gateway
and ConnectPort X2e SE Cellular
models are configured in a similar fashion. Although these models allow connection to the Internet via built-in Cellular modem, their role as a network "Client" remains unchanged, and these are not
. For the same reason, an XBee Gateway or ConnectPort X2e SE which contains both Ethernet and Wi-Fi interfaces isn't able to route between the two local network interfaces either.ConnectPort X4
and ConnectPort X8 Ethernet
gateways running EOS firmware version 2.8.4.x
are configured in a similar way to the CP-X2, X2e SE, and XBee Gateway models above, acting as a DHCP client on the local network. CP-X4 and X8 gateways still running firmware older than 2.8.4.x will be configured similar to the cellular models mentioned below, and may potentially conflict with a local Network Router when at their default IP of 192.168.1.1. The old firmware in these models can be updated to resolve that potential issue.
For the ConnectPort X4
, and X8 Cellular
models, the default IP address is static, and is set to 192.168.1.1. The subnet mask is set for 255.255.255.0, and the Gateway expects to get Primary/Secondary DNS server addresses when it establishes the cellular Link.ConnectPort X4, X5, and X8 cellular are Cellular Routers
, and act as DHCP server to those network devices connected via the LAN side of the Gateway. A DHCP-enabled PC or Laptop connecting via crossover ethernet cable to the ethernet connector of the CP-X4/X8 will obtain an IP address of 192.168.1.100 (default range is .100 to .131). A standard web browser can then be opened to http://192.168.1.1, to access the WebUI configuration page of the Gateway.
How to discover the local IP address of the Gateway on your network:
In order to connect to one of the Gateways above via the Gateway's Ethernet interface, you'll want to use the Digi Device Discovery Tool
to "discover" your Gateway. If you have trouble discovering the Gateway with the Device Discovery Tool (i.e. you see "No Devices Found" in the Device Discovery Window when you run it), see this article
for troubleshooting tips on why your Digi product might not be showing up. Alternately, plug your Gateway into a network that has a DHCP server running on it, so the Gateway can obtain an IP address and other network details from the DHCP server on your local network.