| 8 Jul 2025 |
 Zhaofeng Li |
Multicast DNS responder and resolver
huh interesting, so it can publish too
| 20:51:18 |
 Charles | well, it says it can, but i can't get it to work | 20:51:50 |
| Zhaofeng Li | there is resolvectl mdns but it's not very helpful apart from saying "yes" | 20:54:23 |
| Charles | indeed | 20:54:32 |
| Zhaofeng Li | maybe you need the whole SYSTEMD_LOG_LEVEL=debug shebang again | 20:54:55 |
| Zhaofeng Li | for the networking stuff, trying to get systemd to tell you anything useful via the CLIs is usually futile 🫠| 20:56:25 |
| Charles | actually it seems like services.avahi.enable = true; is sufficient | 20:57:13 |
| Charles | (i did not read the docs that hard) | 20:57:21 |
| Charles | oh or maybe it isn't | 21:00:39 |
| Zhaofeng Li | theoretically avahi shouldn't even be needed it seems, but alas for my use case CUPS doesn't seem to work with resolved for publishing | 21:00:40 |
| Zhaofeng Li | The story is always like:
Me: networkctl reconfigure
networkctl: Success 🥰
Me: but it does nothing? networkctl status
networkctl: configured 👌
| 21:02:54 |
 hexa | so, I'm sorry to say | 21:58:02 |
| hexa | dhcp servers are as boring as they come once they work | 21:58:10 |
| hexa | which means I might need help updating the kea suite, which has been stuck on a vulnerable version for a month | 21:58:26 |
| hexa | https://github.com/NixOS/nixpkgs/pull/411875 | 21:58:39 |
| Zhaofeng Li | is it okay to move to 3.0 directly (IIRC there isn't a separate control server anymore)? | 22:21:29 |
| Zhaofeng Li | or it has to be 2.6.x for backport reasons (surprising they changed this behavior in a revision) | 22:22:28 |
| hexa | yeah, we need the 2.6.3 backport | 22:23:10 |
| hexa | and yeah, the behavior change is what breaks the runtime environment | 22:23:26 |
| hexa | for reasons I don't understand | 22:23:30 |
| Zhaofeng Li | ok, let me try | 22:26:18 |
| Zhaofeng Li | built, the KEA_CONTROL_SOCKET_DIR appears to be honored fine
router # [ 8.927187] kea-ctrl-agent[805]: 2025-07-08 22:43:26.795 INFO [kea-ctrl-agent.dctl/805.140519184328576] DCTL_STARTING Control-agent starting, pid: 805, version: 2.6.3 (stable)
router # [ 8.929422] kea-ctrl-agent[805]: 2025-07-08 22:43:26.798 ERROR [kea-ctrl-agent.ctrl-agent/805.140519184328576] CTRL_AGENT_CONFIG_FAIL Control Agent configuration failed: invalid path specified: '/run/kea/VALUE-IN-CONFIG', supported path is '/run/kea/meow'
router # [ 8.931635] kea-ctrl-agent[805]: 2025-07-08 22:43:26.798 FATAL [kea-ctrl-agent.dctl/805.140519184328576] DCTL_CONFIG_FILE_LOAD_FAIL Control-agent reason: invalid path specified: '/run/kea/VALUE-IN-CONFIG', supported path is '/run/kea/meow'
| 22:46:20 |
| Zhaofeng Li | then there's a permission issue, checking
router # [ 8.841737] kea-ctrl-agent[780]: 2025-07-08 22:45:53.570 ERROR [kea-ctrl-agent.ctrl-agent/780.139821817276288] CTRL_AGENT_CONFIG_FAIL Control Agent configuration failed: socket path:/run/kea does not exist or does not have permssions = 750
| 22:47:04 |
| hexa | RuntimeDirectoryMode = "750";
| 22:51:40 |
| hexa | * RuntimeDirectory = "kea";
RuntimeDirectoryMode = "750";
| 22:52:01 |
| hexa | not sure why this part doesn'tw ork | 22:53:09 |
| hexa | * not sure why this part doesn't ork | 22:53:11 |
| hexa | * not sure why this part doesn't work | 22:53:13 |
| Zhaofeng Li | yeah, saw that | 22:53:29 |
| Zhaofeng Li | using socket-name = "/run/private/kea/dhcp4.sock"; works, curious | 22:53:31 |
