Hello,
I noticed that the communication module responds to ARP requests for 192.168.0.1 during boot, even if that is not the IP address that is going to be assigned.
It is, notably, the IP address of the router.
This causes alarms because it is effectively an address conflict.
root@monitor:~# arping 192.168.0.1
ARPING 192.168.0.1
[...]
56 bytes from 8c:3e:32:88:12:ef (192.168.0.1): index=378 time=829.873 usec
56 bytes from 8c:3e:32:88:12:ef (192.168.0.1): index=379 time=686.780 usec
56 bytes from 8c:3e:32:88:12:ef (192.168.0.1): index=380 time=666.628 usec
56 bytes from b8:74:24:3d:1a:7a (192.168.0.1): index=381 time=3.939 msec
56 bytes from 8c:3e:32:88:12:ef (192.168.0.1): index=382 time=519.581 usec
56 bytes from 8c:3e:32:88:12:ef (192.168.0.1): index=383 time=672.201 usec
56 bytes from 8c:3e:32:88:12:ef (192.168.0.1): index=384 time=551.164 usec
hostname: rutterone.acao.it
ip address: 192.168.0.1
interface: enp6s18
ethernet address: b8:74:24:xx:xx:xx
ethernet vendor: Viessmann Elektronik GmbH
old ethernet address: 8c:3e:32:xx:xx:xx
old ethernet vendor: <unknown>
timestamp: Monday, February 24, 2025 12:54:49 +0100
previous timestamp: Monday, February 24, 2025 12:54:49 +0100
delta: 0 seconds
