mention AF_NETLINK in man 2 socket

2023-01-11 Thread User Ngor
Looks like there are no references to {PF|AF}_NETLINK in the socket manpage. -- Ihor Antonov

netlink socket does not accept SOCK_DGRAM

2023-01-14 Thread User Ngor
man 4 rtnetlink says:     int socket(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE); The following snippet fails int fd = socket(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE); if (fd < 0) { perror("Failed to open netlink socket"); return -1; } printf("all good\n"); close(

Re: netlink socket does not accept SOCK_DGRAM

2023-01-15 Thread User Ngor
It’s a bug. The manage should state SOCK_RAW, but both options should be supported, which is not the case ATM. I’ll fix it in a couple of days. Meanwhile it may be worth looking into snl(3) which abstracts issues like this one. Thanks, I will take a look. Is there an example somewhere of snl

Re: netlink socket does not accept SOCK_DGRAM

2023-01-16 Thread User Ngor
On 1/15/23 12:43, Alexander V. Chernikov wrote: The snl(3) manpage itself includes some examples, including the complete working program in the end     man snl     No manual entry for snl Looks like not connected to the buildworld.. -- Ihor Antonov

local-unbound regression

2023-01-17 Thread User Ngor
I discovered that recent unbound update broke my VPN scripts, after some investigation I think I found the problem - default location of the config file was reset to upstream value. My config file is at /var/unbound/unbound.conf (as created by local-unbound-setup) but when I use local-unbound-c

Re: local-unbound regression

2023-01-17 Thread User Ngor
I discovered that recent unbound update broke my VPN scripts, after some investigation I think I found the problem - default location of the config file was reset to upstream value. My config file is at /var/unbound/unbound.conf (as created by local-unbound-setup) but when I use local-unbound-c

Re: Version of OpenSSL included in upcoming 14.0-RELEASE

2023-01-28 Thread User Ngor
On 1/28/23 07:34, Yasuhiro Kimura wrote: ... Though I'm not familiar with the incompatibility between OpenSSL 1.1.1 and 3.0, I believe it is too optimistic to regard that build of 14-CURRENT succeeds without any error just by updating /usr/src/crypto/openssl from 1.1.1 to 3.0. So it will take fo

Tooling Integration and Developer Experience

2023-01-29 Thread User Ngor
On 1/30/23 02:54, Julian H. Stacey wrote: > Jamie Landeg-Jones wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a trivial fix >> to an admittedly trivial issue, but it's soon going to hit one year old, >> and has not had any feedback. Not even "this is rubbish. close ticket"

Re: Tooling Integration and Developer Experience

2023-01-30 Thread User Ngor
On 1/30/23 10:08, Kurt Jaeger wrote: Hi! ihor@antonovs.family wrote: This can be as easy as moving everything into Phabricator. There's the issue that Phabricator itself is no longer supported upstream: https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/ http

Re: Tooling Integration and Developer Experience

2023-01-30 Thread User Ngor
On 1/30/23 13:53, Warner Losh wrote: On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote: Hi, On 1/30/23 02:54, Julian H. Stacey wrote: The main idea: to prevent information fragmentation andimprove discoverability, cross-referencing abilities, search, etc. With regards to improvi