Go to file
Ishan Jain 8bcee50a54
use builtin dns parser, added more tests, save a copy of txt record data
2023-11-22 03:17:48 +05:30
src use builtin dns parser, added more tests, save a copy of txt record data 2023-11-22 03:17:48 +05:30
.gitignore WIP: Working on config parser and a basic version which can receive multicast traffic 2023-06-05 01:51:39 +05:30
Cargo.lock WIP: Writing a mdns parser 2023-11-21 03:23:00 +05:30
Cargo.toml WIP: Writing a mdns parser 2023-11-21 03:23:00 +05:30
README.md wip: unified ipv6 socket for ipv4 and ipv6 traffic 2023-11-17 23:49:19 +05:30
config.toml restructured project 2023-07-30 20:18:17 +05:30

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

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.