§Anil Meeting
Anil mentioned with QUIC and DNS SVCB records traffic can be UDP-only.
We described a service manager using capability DNS with ‘naming’ and ‘livecycle’ at the DNS level. Anil likened this to docker compose service manager for a collection of services. It seems like systemd’s service management plus container and network management.
This would allow things like IP-based load balancing, certificate provisioning, Jitsi-spinning up services on request.
I need to extend the
lenscap to support service management APIs as well as
certificate provisioning. OCluster might be a place to look for this. It
could do something really simple like just map to systemd.
Anil likened it to Tailscale’s new service management dashboard. I brought up Tailscale node sharing, which might be ripe for a naming-first solution.
I should also get Anil to deploy this.
Anil also said Jake’s void processes stuff could be useful here. It could also tie in the SNS. And Jess’s identity stuff. But one thing at a time.
We need to:
- register hosts
- load balance tasks
- provision certs
Anil said maybe the Root capability is the wrong name.
I have some DNS tunnelling and SSH over DNS stuff lying around that might be useful for this.
§Hibernia
We can use the UPnP protocol to create a mapping of port 53 with our home router’s public IPv4. Or, just use IPv6. If you’re behind a double NAT – you’re screwed. Though, we can use a VPN e.g. Tailscale w/ magic DNS.
Okay – don’t care about the network topology.
Right, if we’re putting this into an ESP32, why not just push this functionality into the router itself?
Well, many home routers have commodity hardware that users don’t want to edit or maintain…
But also, the ESP32 might not be large enough.
What problem are we trying to solve? Idle server use. At home? At work? We don’t really care about the network topology. The novelty is a WoL on DNS query.
It’s a DNS WoL gateway.
Okay, but what about access control?
Proprietary versions include: Bonjour Sleep Proxy. Though, this is limited to mDNS. Extend this to the full DNS. The sleep proxy is already-on devices on the network.
There’s also wireless extensions.
Okay, provide a Unix program, and deploy it on a host or on the router, or optionally a Unikernel on e.g. an ESP32 (ultra low memory).