11:31:51 <warden> Hi to all. I noticed that the latest unbound release warns at startup because it does not seems allowed to set the UDP send buffer size:
11:31:54 <warden> warning: setsockopt(..., SO_SNDBUF, ...) was not granted: No buffer space available
11:32:46 <warden> maybe the unbound user needs to be grant for a specific RBAC permission?
18:24:38 <sommerfeld> warden: it may be trying to set it above the max buffer size limit
18:25:52 <sommerfeld> (see ipadm show-prop to see it, and ipadm set-prop to adjust the max_buf value
18:33:59 <warden> sommerfeld: thanks, i'll give it a try! Any suggestion about changing exec_attr for the unbound user, or its SMF configuration? I tried to add net_rawaccess to start/privileges with svccfg, but the warning remains at service startup
19:10:11 <warden> I tried starting unbound as root, and the warning isn't triggered, thus it would be possible to assign the right permission to the unbound user or to its service's fmri?
19:48:45 <sommerfeld> ppriv -e -D can be useful in figuring out which privileges are missing.
19:58:35 <warden> sommerfeld: great, thank you for the suggestion! Unfortunately I just discovered my previous test with root was faked... I left the workaround setting in unbound.conf! :@
20:02:11 <warden> so the problem actually is that the max UDP send_buf property range in illumos does not allow the value that unbound tries to set (4194304 against the limit of 2097152)
20:07:21 <warden> "ipadm set-prop -t -p max_buf=5242880 udp" solved the issue! ;)
20:45:25 <szilard> I have created a build recipe for the Fish shell based on the OpnIndiana patches: https://github.com/omniosorg/omnios-extra/pull/1675