Our great sponsors
-
mdns-discovery-proxy
A Discovery Proxy for Multicast DNS-Based Service Discovery written in Python (by mkuron)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Good point, just had a look at the code. The NF queue will receive packets from all IPs in the /80 and they are all processed and validated by the ghost program that reads from the queue. So it could do the rate limiting there with full visibility.
https://github.com/aidansteele/ipv6-ghost-ship/blob/main/mai...
> Using ULA … the network side of our private internet space is only 6 characters
How do you fit the fixed 8-bit ULA prefix (fd00::/8) plus the 40 random bits you're supposed to use for the Global ID (per RFC 4193) into six hex characters? It should be at least 12, e.g. fdXX:XXXX:XXXX::/48.
As for remembering addresses, yes, just use (m)DNS. You can even set up an mDNS Discovery Proxy[0][1] so that devices which don't support mDNS themselves can resolve the names via regular unicast DNS.
[0] https://www.rfc-editor.org/rfc/rfc8766.html
[1] https://github.com/mkuron/mdns-discovery-proxy