multicaster/README.md

# Multicaster

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.


# Working Notes

* 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 `SO_REUSE_ADDR`.

For now, Disable those softwares when running this. A list of such softwares,

a. avahi-daemon


* Multicast DNS RFC https://datatracker.ietf.org/doc/html/rfc6762


### How should this be designed??


#### MDNS

1. 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.

2. A DNS answer from source should be forwarded to the destination _if_ the domain name is in the allow list for that config.

3. A DNS query from destination should not be forwarded to source if it is not in the allow list for the config

4. A DNS answer should not be forwarded from destination to source in any circumstances. This is not enforced right now.
WIP: Working on config parser and a basic version which can receive multicast traffic 2023-06-04 20:21:39 +00:00			`# Multicaster`

			`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.`


			`# Working Notes`

wip: unified ipv6 socket for ipv4 and ipv6 traffic 2023-11-17 18:19:19 +00:00			`* It needs to listen on the specified port to receive multicast traffic.`
Completed a basic version of the program that works with mdns 2023-07-27 23:29:18 +00:00			This causes problems if there are other softwares that are also listening without using `SO_REUSE_ADDR`.
WIP: Working on config parser and a basic version which can receive multicast traffic 2023-06-04 20:21:39 +00:00
			`For now, Disable those softwares when running this. A list of such softwares,`

			`a. avahi-daemon`
Added a basic version of processor. It can listen on multiple ports and aggregate all of it in 1 place 2023-06-04 23:08:36 +00:00

wip: unified ipv6 socket for ipv4 and ipv6 traffic 2023-11-17 18:19:19 +00:00			`* Multicast DNS RFC https://datatracker.ietf.org/doc/html/rfc6762`


Added a basic version of processor. It can listen on multiple ports and aggregate all of it in 1 place 2023-06-04 23:08:36 +00:00			`### How should this be designed??`







Updated communicator & processor Trying to figure out the way to know the right ingress interface 2023-07-27 18:13:22 +00:00			`#### MDNS`
Added a basic version of processor. It can listen on multiple ports and aggregate all of it in 1 place 2023-06-04 23:08:36 +00:00
Updated communicator & processor Trying to figure out the way to know the right ingress interface 2023-07-27 18:13:22 +00:00			`1. 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.`

			`2. A DNS answer from source should be forwarded to the destination _if_ the domain name is in the allow list for that config.`

			`3. A DNS query from destination should not be forwarded to source if it is not in the allow list for the config`

Completed a basic version of the program that works with mdns 2023-07-27 23:29:18 +00:00			`4. A DNS answer should not be forwarded from destination to source in any circumstances. This is not enforced right now.`
Added a basic version of processor. It can listen on multiple ports and aggregate all of it in 1 place 2023-06-04 23:08:36 +00:00