Re: Best practice for forwarding Dnstap (unix socket) traffic to another address

2022-01-12 Thread Tony Finch
Fred Morris wrote: > > What I'm looking at is trying to build a BIND kernel, like a nanokernel. Socat > won't work in this case, because because there's no "IPC" layer, because there > is only one process in the kernel. Sounds fun. I think your solution must be to modify BIND's dnstap sender so t

Re: Best practice for forwarding Dnstap (unix socket) traffic to another address

2022-01-09 Thread Fred Morris
I should have included this in the first message, and I apologize. What I'm looking at is trying to build a BIND kernel, like a nanokernel. Socat won't work in this case, because because there's no "IPC" layer, because there is only one process in the kernel. One process. No users. I need to

Best practice for forwarding Dnstap (unix socket) traffic to another address

2022-01-09 Thread Fred Morris
Hello. For a variety reasons: * Dnstap doesn't comport with the usual MTU restrictions, that is an "event" is not reliably going to fit in a UDP frame. * Dnstap casts your application as the "server" and BIND as the "client". * For whatever reasons the implementer(s) saw fit to include a