Here is a message I got from one of my customers :
[quote]4) - While I was using your software, I got messages from my firewall that
your software was trying to send UDP packets on port 5355 to 224.0.0.252.
Why is your software trying to contact the internet? Has your program been
infiltrated by malware that is dialing information out to someone?[/quote]
I have nothing in my code doing that. Is there something in the plugins or in Xojo that does so ?
How can I curb this unwanted behavior ?
A search for that IP address returned this:
https://osqa-ask.wireshark.org/questions/2039/why-am-i-seeing-lots-of-traffic-to-2240022
I hope that helps.
That does not seem to be quite that. My customer is positive the traffic comes from the app, and sends to 224.0.0.252.
Link local multicast name resolution protocol uses that on windows. Not sure why your software would use it.
Sounds like something as bonjour and autodiscovery. But then you dont have that in the software you say.
Probably windows 8 your customer has?
Read more:
https://stackoverflow.com/questions/22980161/idtcpclient-sometimes-connect-to-224-0-0-2525355
Sounds to me like it’s exactly that.
How does he know it comes from the app?
[quote=431241:@Michel Bujardet]Here is a message I got from one of my customers :
I have nothing in my code doing that. Is there something in the plugins or in Xojo that does so ?
How can I curb this unwanted behavior ?[/quote]
Just tell your client that 224.0.0.252 is part of the Multicast address of the IPv4 protocol, that in specific is the Link-Local Multicast Name Resolution, any trafic to that IP is made by the OS, not by your app.
Its just a windows thing has nothing to do with your application.
Thank you all for explaining what is going on, especially that my app had nothing to do with that traffic.