Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug: NewResponder should not have to listen on all interfaces #46

Open
upsampled opened this issue May 13, 2024 · 0 comments · May be fixed by #47
Open

Bug: NewResponder should not have to listen on all interfaces #46

upsampled opened this issue May 13, 2024 · 0 comments · May be fixed by #47

Comments

@upsampled
Copy link

I am running this library as a server and noticed that even though I only included one interface in the dnssd.Config, I was seeing IGMP messages on both interfaces. This was confirmed running -Verbose flag in the cmd/register:

# register -Name "TSTService" -Type "_tst._tcp" -Port 9876 -Interface eth1 -Verbose
18:09:36.417    ...STARTING...
DEBUG 2024/05/13 18:09:36.432281 mdns.go:183: Joined IPv4 eth1
DEBUG 2024/05/13 18:09:36.434637 mdns.go:183: Joined IPv4 wwan0
DEBUG 2024/05/13 18:09:36.446972 mdns.go:204: Joined IPv6 eth1
DEBUG 2024/05/13 18:09:36.449525 mdns.go:204: Joined IPv6 wwan0

Not sure if the interfaces listed in dnssd.Config should be the only interfaces listened on, but there should at least be a way to limited the interfaces being used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#46 : Allow for the option to not listen on all interfaces upsampled/dnssd
1 participant
@upsampled