can't bind socket: Permission denied for IPv6
nusenu
nusenu-lists at riseup.net
Sat Jun 30 16:07:00 UTC 2018
>> I've got the following intermittent socket bind errors in my log files:
>>
>> error: can't bind socket: Permission denied for <IPv6 address>
>
> Does the patch fix the problem for you?
I'm running 1.7.3 with this patch applied and still got an
can't bind socket: Permission denied for ...
error in the logs, but it feels like it is happening less frequently?
> If so, the flowinfo or scopeid
> information is changed and needs to be reset for the next assignment.
> And somehow the information gets permission denied, maybe because of
> privacy IPv6 address changes, those values refer to a no longer
> accessible address?
The IPv6 addresses are statically assigned and should be available
all the time (also verified via ping6).
How bad is that error actually (since everything appears to work fine)?
Should I disable IPv6 outgoing-interface lines to workaround this errors?
thanks,
nusenu
--
https://twitter.com/nusenu_
https://mastodon.social/@nusenu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20180630/1544b132/attachment.bin>
More information about the Unbound-users
mailing list