Gemalto is now part of the Thales Group, find out more.

You are here

Cinterion ELS61-E2 network problems | Thales IoT Developer Community

September 25, 2020 - 10:26am, 740 views


I have a weird network problem with a handful of new ELS61-E2 modules, which I recently bought to replace some older Coniugo modems.

My setup is as follows:
I have an SMS server running Windows Server 2012 R2, and a piece of software called "Diafaan SMS server"
This server connects to modems over LAN

Server and modems are on same network, same VLAN (10.129.x.x / VLAN1)
Server is working fine, SMS are beeing sent out, on both old Coniugo and new ELS61 modems.

I am in the process of replacing old SMS server with a new one, based on Windows Server 2019 and a newer version of Diafaan.

New setup is SMS server in VLAN51 (10.128.64.x), and modens still on VLAN1 / 10.129.x.x
There are full network connectivity. Modems can be ping'ed from server and vice versa.

Problems start when I try to connect the ELS61 modules to the new server.
I can add the module as a new gateway in Diafaan (connection tests OK), but in this process Diafaan server reboots the module, and then IP connection is lost.

Weird is, that connetion is only lost from the new server in VLAN51. I can still ping module from a server in VLAN1.

Even more weird is, that if I go into ELS61 configuration, and under Network / Static Routes try to add a route, then immediately deletes it and press Save & Apply, then network connectivity from VLAN51 is restored.

There are no static routes defined in the first place.
Modules are powered using PoE. Not sure if this has any signficance.

Firmware version is: OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152) 
Kernel version is:  4.9.120