Be smarter when using MDNS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
We should:
1. Iterate over all the interfaces we're listening on that support multicast.
2. Figure out what IP addresses we have assigned on those interfaces.
3. Look up the IP in our host's listen addresses.
4. Figure out the correct port to announce.
5. Announce that port over the correct interface.
However, this means we'll need to manage multiple mdns "servers".
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing mDNS server setup and how host listen addresses and network interfaces are discovered. Review the interface, multicast, and port-selection paths before implementing the issue's five-step flow. Done means multicast-capable interfaces announce the correct listen port through separate mDNS servers for each relevant interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100