24 Lis
2016
24 Lis
'16
17:47
Thank you,
this (--enable-recvmmsg=no) fixes it for me. Hopefully the patch and new
version will get into ports soon.
Thank you very much for your help.
Pavol, now with working DNS on FreeBSD :)
On 24.11.2016 13:05, Leo Vandewoestijne wrote:
On Thu, 24 Nov 2016, Vladim??r ??un??t wrote:
--
Email encryption for everyone via @fsf
https://u.fsf.org/zb
Hi,
I hope English will be understandable enough (to you).
On 11/23/2016 11:00 PM, Pavol wrote:
I was already on that, and requested that two weeks ago:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214303
Somehow my confirm did not came trough, I just did that again.
--
With kind regards,
Leo Vandewoestijne
<***(a)dns.company>
<www.dns.company>
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
I am trying to get knot 2.3.1 (from ports)
working in a jail, but I am
unable to connect to the udp port even when trying directly from jail.
Using netcat from within jail and also from other machines gets
through into the jail. I don't think it is pf's fault.
How can I debug this a bit more?
Was knot compiled with recvmmsg support? The FreeBSD implementation of
this was buggy and I don't know which version got fixed:
https://github.com/freebsd/freebsd/pull/91
It's possible to disable the functions by passing --enable-recvmmsg=no
to ./configure.