2152 does not have default gateway initialised on some power on

PLCnext Technology & PLCnext Controls
1

I have approx 30 x 2152 in the field (all running FW 2023.0.6). I have observed the 2152 intermittently loses the default gateway setting from it’s running config on some power cycles. So far, on the next power cycle the default gateway setting is initialised on the next power cycle.
After power cycle where comms via a VPN is lost, but LAN comms are still good:

Media.jpeg
Media.jpeg1000×562 211 KB
After subsequent power cycle, without applying and rebooting:
Media 1.jpeg
Media 1.jpeg1000×562 226 KB

I have looked at the change notes for FW 2024.0 LTS and in the known bugs/issues register and note this bug is not listed in either.
Network settings on initial configuration are set using PLCNext Engineer version 2024.0 LTS, and then not altered later on. Prior to identification of the bug, the offending PLC has just been power cycled to restore comms.
May I have some suggestions for a work around or a bug fix?

2

I’m not aware of any reports of this type of behaviour that could be attributed to a bug in the firmware.
You mention a VPN, so the suspicion in this case is that something installed on the device is over-writing the static network configuration in some circumstances.

3

Hi Martin,
The VPN is external to the 2152 (end point is in a RUT 955 with RUT955 and 2152 on the same LAN).
The 2152 has no other software or code installed on the underlying operating system.
Is the default gateway in the running config able to be externally altered in the 2152 other than via the WBM?
If so, that could provide a work around.
cheers,
Matt