I had this issue of seeing in comfort server manager ( CSM), my comfort ip address blinking constantly. Using wireshark, I discovered that there is no loop in my network and this blinking stops when I disconnect another device on my network.
When this device is connected, I can see that all of my ethernet devices reply to the pc/30303 port and again and adain. Hence CSM receiving every few milliseconds the right answer from comfort and making the PC /CSM window look likes blinking.
When my other device is out of the network, the answering sequence to CSM /port 30303 from all my ethernet devices only happens once.
But looking at the two wireshark captures, I cannot determine where is the problem. Any idea on how to solve that?My other device is on the same sub segment, it is a device collecting energy comsumption details ( ecodevice made by GCE electronics).Thank you
Does the other device also work on port 30303? and it coould be repeating the replies from ETH03?
CS Manager sends a request to port 30303 on UDP and it should receive a reply from the ETH03s on the network, even on other subnets (which appears in red)
Even with the blinking you are able to see the correct IP address and port? Are you abel to change the IP and port?
So with more investigation.. it is CSM app that does renew every milliseconds ish the discover frame on 30303 when the other GCE (brand) device is on the network. So this update frequency does not allow me to change the Comfort IP address.
I used another discovery application from GCE also on 30303 and this one sends only one discovery paquet and all devices replies once only. So the issue seems for me between the CSM app and the reply that specific device sends back to CSM.I cannot see in the sniffing what would be the issue. The discovery frames sent by the two app ( CSM and GCE) are slightly differents.
Note that on this subnet I have 15 other devices including 3 other units from the GCE vendor ( I am assuming that their different module are using the same tcpIP modules.
I also disconnected the switches and router on my network and the problem was still there.
Not a big issue if during regular operations, this call to port 30303 is not used.
I will later make a capture on 30303 to check that there is no discovery frame storm.
I also have seen this when there is another similar device on the same network. I wonder whether a change to CSM could be made to discover the devices but not constantly have them flicker so you can't actually select one?