night199uk - Should Signalk advertise it's NMEA...
Should Signalk advertise it's NMEA0183 service over mDNS/DNS-SD/Avahi using _nmea-0183._tcp? Mine doesn't seem to be; despite advertising other services. Trying to figure out if it's a bug on my side.
Advertising via _nmea-0183._tcp would allow Linux clients e.g. geoclue and others to retrieve the GPS position from the network they're attached to.
5 Replies
It is supposed to per https://github.com/SignalK/signalk-server/blob/master/src/interfaces/nmea-tcp.js#L78
GitHub
signalk-server/src/interfaces/nmea-tcp.js at master · SignalK/sign...
An implementation of a Signal K central server for boats. - SignalK/signalk-server
Mine does
Arright, must be something about my docker setup. Thanks 🙂
Are you running in host or bridge mode?
host. I took a root in the code, and I'm guessing in host mode something on the host has already bound port 5353 (prob systemd-resolve) and the mdns node library can't bind 5353. i didn't dig into it too deeply but it looks like that's probably what's going on. i don't want/need to run in bridge mode for other reasons.