We are currently using an IOT2050 with firmware version V01.03.01 and the sample image v1.3.1.

• P1 (LAN)is configured with a static IP address (192.168.11.254/23), no gateway defined, and the option "never use this connection as a default gateway" is selected. This interface is working correctly.

• P2 (WAN)has been tested both with DHCP and with a static IP (192.168.96.241/24, gateway 192.168.96.45). In both configurations, it does not connect to the network. When using DHCP, it doesn't receive an IP address from the DHCP server, even though other devices on the same network are obtaining IPs via DHCP or work correctly with a static IP.

We are usingNetworkManagerand managing the interfaces usingnmtuias recommended.

In summary:P1 (LAN) is working, but P2 (WAN) is not.

We kindly request support in identifying the cause and resolving this issue.

Hello,

I have noticed that there are other topics reporting similar issues.
Below are the steps I identified when this problem occurs.

Device:Siemens IoT2050
Firmware Version:V1.4.4
Image Used:V01.04.04-iot2050-image-example-iot2050-debian-iot2050.wic.img.zip
Affected Interface:P2 / X2 (eno2)
DHCP Server Used:

• pfSense 2.3.5-RELEASE-p2

• ISC DHCP Server 4.3.6-P1

Behavior Summary

Expected Behavior

When the IoT2050 is powered on with port X2 connected to a network with an active DHCP server, it should receive and configure a valid IP address from the available pool.

Actual Behavior

1. When the IoT2050 is powered on with both X1 and X2 network cables connected:

   • The system sends a DHCP request for a specific IP address within the valid range.

   • However, the IP address is not configured on the X2 interface.

   • The DHCP server (pfSense) receives and responds to the request, but the DHCP client on the IoT2050 fails to apply the received IP address.

Alternative Procedure That Works

1. Power off the IoT2050 and disconnect the network cable from port X2.

2. Power on the device with X2 disconnected.

3. After the system has fully booted, reconnect the cable to port X2.

4. In this case, the IoT2050:

   • Properly initiates the DHCP process.

   • Successfully obtains and configures a valid IP address on X2.

Steps to Reproduce the Issue

1. Power off and then power on the IoT2050 with both network cables connected to X1 and X2.

2. In the pfSense DHCP logs:

   • You’ll see the client requesting an IP within the expected range (e.g.,192.168.3.252).

   • The server replies, but the IP is never configured on the device.

3. As a result, interface X2 has no network connectivity.

Possible Technical Cause

• The DHCP client on the IoT2050 (likelydhclientvia NetworkManager orsystemd-networkd) may have a bug or unexpected behavior that:

  • Ignores the server’s valid response when the interface is active during boot.

  • Remains stuck expecting a different lease confirmation, even when a valid response is received.

• Having the cable connected during boot might influence the timing or order of DHCPDISCOVER/DHCPREQUEST messages, leading to silent failure in IP configuration.

Supporting Material

A video was recorded demonstrating:

• The failure scenario (with both cables connected during boot).

• The working scenario (X2 connected only after the system is fully booted).

• DHCP behavior in both situations.