Need bidirectional communication channel between netavark and aardvark about aardvark-dns HOT 8 OPEN

Are you thinking something like a unix socket, where we could pass requests from NV to AV and receive a response when the change was fully implemented?

from aardvark-dns.

Yes, I just want something were can make sure netavark won't return until aardvark-dns is ready and if there was an error we should get it back.

from aardvark-dns.

I would prefer not to drag a full REST API in, so I wonder if we can't do something a little lighter (protobuf, maybe? Does that have good rust bindings?)

The idea in general seems sound, and could serve to enable additional features in the future (we've talked about having Aardvark listen for DBus events and launch Netavark when the firewall reloads, and bidirectional comms could be useful for that)

from aardvark-dns.

I don't care about the protocol, protbuf would work we use it already for the dhcp proxy so it is not a new dependency for netavark.
But honestly I think it right now a simple string based API would be enough assuming we keep the current way of writing entries to file.

from aardvark-dns.

xref: containers/podman#18325

from aardvark-dns.

xref: containers/podman#16272

from aardvark-dns.

I didn't even bother linking issues, I could properly link 20+ issues from the podman repo that may not be fixed by this but at least can be diagnosed by the users.

Common error is having something listening on port 53.

$ sudo nc -u -l 53
$ sudo podman run --network podman1 --rm alpine nslookup google.com
nslookup: write to '10.89.0.1': Connection refused
;; connection timed out; no servers could be reached

That is what the user sees, dns not working but they don't know why.

The only real clue is in the journal but most people will never check that:

aardvark-dns[34502]: Unable to start server unable to start CoreDns server: Address already in use (os error 98)

The goal here would be to have the podman run command error out with the aardvark error.

from aardvark-dns.

@Luap99 do you want to self-assign this or prefer to wait until your workload lessens?

from aardvark-dns.