Sleepwalk
❔ .NET Service discovery
The service ran a UDP client that listened on a particular port. Whenever it received any message on that port, it would send a UDP message back to the sender that just had the ASCII encoded name of the application. In the client, when the user wanted to connect to a device, it would UDP broadcast on all network interfaces to the target port, and also listen for any UDP messages sent to the IP address of the interface. Any messages it got that contained the application name would be verified (I had a GRPC function to return some basic information about the particular device), and added to a list that the user could choose from. That worked well enough for my needs.
11 replies
❔ .NET Service discovery
Hey @Denis, I implemented something very similar to this a couple years ago. The service ran on a raspberry pi inside a piece of industrial equipment, a client running on a laptop would need to connect to it, they both needed to be on the same LAN, and that LAN might have multiple copies of that equipment that you could connect to.
I didn't find anything lying around that really fit what I needed, so I implemented my own discovery service using UDP broadcast packets.
11 replies