Greg, If i understand your intention correctly, I can't imagine that working. Even if it did, it wouldn't be a good idea. The UDP packets would be blocked at any number of points along the way and probably wouldn't get far. Maybe even get black listed?
I would suggest clients need to register so UDP packets can be sent directly to the client. Register the client ip and listening port. This should also ensure any dynamic holes in firewalls are created. Especially important if the clients are on mobile networks. David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On 11 October 2017 at 14:41, Greg Keogh <gfke...@gmail.com> wrote: > I just want to check this is possible... > > A server program running in my Azure VM will use the UdpClient class to > broadcast logging information using a chosen port. It doesn't know anything > about who might want to listen. > > Client programs anywhere in the world know the IP address and port, and > will use the UdpClient class to connect and listen to the logging > broadcasts. > > I've only ever used the UdpClient class like that within a LAN, but I > presume "distance" is no obstacle and what I want is a familiar technique > between remote machines. I've run a few experiments but they all fail to > communicate or crash because I've stuffed-up the parameters. There are so > many combinations of parameters and options that I simply cannot find the > right ones. All samples I find are trivial and don't seem to do what I want. > > Any advice would be welcome. > > *Greg K* >
