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

listen with different address and interfaces #42

Closed
genofire opened this issue May 3, 2019 · 3 comments · Fixed by #43
Closed

listen with different address and interfaces #42

genofire opened this issue May 3, 2019 · 3 comments · Fixed by #43

Comments

@genofire
Copy link
Contributor

genofire commented May 3, 2019

It need to listen with ff05::2:1001 (global on client net) and ff02::2:1001 (statuspage, inside tunnel) in different interface.

freifunk-gluon/gluon@59a4427
@genofire genofire mentioned this issue May 4, 2019
Open
@TobleMiner TobleMiner mentioned this issue May 6, 2019
Merged
@TobleMiner TobleMiner reopened this May 22, 2019
@TobleMiner
Copy link
Member

#43 Allows for specification of an arbitrary number of multicast interfaces and groups

@jplitza
Copy link
Member

jplitza commented Jun 1, 2019

@TobleMiner Yeah, so why the re-open?

@TobleMiner
Copy link
Member

@jplitza I'd have appreciated some input regarding changes to the default respondd.service file. I can make the required adjustments myself though.

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.

Allow for per interface multicast group specification TobleMiner/mesh-announce
3 participants
@TobleMiner @jplitza @genofire