Testing MQTT connection with the Cerbo-gx (Venus large v3.42) I encountered multicast packets send on the segment 192.168.1.x. (Using WireShark with a network sniffer ETAP-2003).
Unexpected multicast packets with source address 169.254.6.178 are send.
As I want, for security reasons, the network to be clean, it is essential to understand every packet being there.
This address is used for a purpose. IANA (Internet Assigned Numbers Authority) owns this range 169.254.x.x for, as they quote:
Computers use addresses starting with “169.254.” when they do not have a manually configured address or when they are not told which address to use by a service on the network. They are commonly called the “link local” addresses
I assume the source is a Victron component. The UDP payload is a valid json string:
{
“Source”: “victron”,
“IP”: “169.254.6.178”,
“Text”: [
{
“Language”: “en”,
“Name”: “Victron”,
“Description”: “Victron Metrics”
}
],
“Icon”: “http://169.254.6.178:80/navico/icon.png”,
“URL”: “http://169.254.6.178:80/app”,
“OnlyShowOnClientIP”: “false”,
“BrowserPanel”: {
“Enable”: true,
“ProgressBarEnable”: false,
“MenuText”: [
{
“Language”: “en”,
“Name”: “Home”
}
]
}
}
All components are configured with fixed IP-addresses by a local DHCP server.
Now I have following questions:
- Since all network settings of the Victron components are configured, they work as expected, what would be the first suspect to examine thay emits these multicast packets?
- Why would a Victron component multicast this kind of information?
Some tips would be highly appreciated.