New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SO_BINDTODEVICE failing with virtual interface #99
Comments
Hi @and0x000! |
Looking through the code, there may be an issue when combined with |
hi @k0ekk0ek thanks for the quick reply.
I tried specifying the Regarding where to specify it, the documentation seems a bit contradictory to me. |
Follow-up: it does not work either with
|
I think #100 will fix the problem for you. You're probably using a package, but can you try to compile with that fix? |
@k0ekk0ek I got a version with the fix compiled by @asciiprod (kudos). The fix works for my case. |
I tried to run NSD 4.3.1 on a machine (Debian 10.4), which uses bonding for LACP. Starting NSD fails with this error message:
Running it on a pretty much identical setup with plain interfaces works.
Best guess so far is, that
SO_BINDTODEVICE
introduced with NSD 4.3.0 seems to not play well with virtual devices.Is it possible to detect such virtual interfaces automatically and subsequently not apply this socket option to avoid startup failures?
Furthermore, the option to disable this functionality for config files (
bindtodevice: <yes or no>
) seems broken. It is considered invalid by nsd-checkconf. Setting it prevents NSD from being started as well.The text was updated successfully, but these errors were encountered: