|Ishan Jain 8bcee50a54
This is a software for routing multicast traffic across L2 networks. It'll allow you to be very specific about the exact traffic that is sent over.
- It needs to listen on the specified port to receive multicast traffic.
This causes problems if there are other softwares that are also listening without using
For now, Disable those softwares when running this. A list of such softwares,
- Multicast DNS RFC https://datatracker.ietf.org/doc/html/rfc6762
How should this be designed??
If a DNS Query comes on the source interface, We don't forward it to the destination. We want the destination to be able to resolve mdns hosts in source. A Query from source should not be forwarded to the destination.
A DNS answer from source should be forwarded to the destination if the domain name is in the allow list for that config.
A DNS query from destination should not be forwarded to source if it is not in the allow list for the config
A DNS answer should not be forwarded from destination to source in any circumstances. This is not enforced right now.