Skip to content
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

unable to start opensnitch-daemon (Error unbinding existing q handler from AF_INET proto) #204

Closed
Brutus11111 opened this issue Sep 20, 2018 · 9 comments

Comments

@Brutus11111
Copy link

Hi,

When I start the daemon, I get the following messages:

[2018-09-20 14:53:43]  IMP  Starting opensnitch-daemon v1.0.0b
[2018-09-20 14:53:43]  INF  Loading rules from /etc/opensnitchd/rules ...
[2018-09-20 14:53:43]  !!!  Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument
[2018-09-20 14:54:14]  IMP  Starting opensnitch-daemon v1.0.0b
[2018-09-20 14:54:14]  INF  Loading rules from /etc/opensnitchd/rules ...
[2018-09-20 14:54:14]  !!!  Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument
[2018-09-20 14:54:44]  IMP  Starting opensnitch-daemon v1.0.0b
[2018-09-20 14:54:44]  INF  Loading rules from /etc/opensnitchd/rules ...
[2018-09-20 14:54:44]  !!!  Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument
[2018-09-20 14:55:14]  IMP  Starting opensnitch-daemon v1.0.0b
[2018-09-20 14:55:14]  INF  Loading rules from /etc/opensnitchd/rules ...
[2018-09-20 14:55:14]  !!!  Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument
[2018-09-20 14:55:44]  IMP  Starting opensnitch-daemon v1.0.0b
[2018-09-20 14:55:44]  INF  Loading rules from /etc/opensnitchd/rules ...
[2018-09-20 14:55:44]  !!!  Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument
[2018-09-20 14:56:15]  IMP  Starting opensnitch-daemon v1.0.0b
[2018-09-20 14:56:15]  INF  Loading rules from /etc/opensnitchd/rules ...
[2018-09-20 14:56:15]  !!!  Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument
@lepz0r
Copy link

lepz0r commented Oct 29, 2018

same here

@jfreax
Copy link

jfreax commented Dec 27, 2018

I get the exact same error. Any ideas?

# uname -a
Linux thinx1 4.20.0-gentoo #1 SMP Thu Dec 27 11:23:49 CET 2018 x86_64 Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz GenuineIntel GNU/Linux

@gustavo-iniguez-goya
Copy link
Collaborator

I think this problem is fixed with latest packages.

@gustavo-iniguez-goya
Copy link
Collaborator

Hi @vikgac ,

First provide some logs:

  • Post /var/log/opensnitchd.log
  • lsmod | grep -i queue
  • cat /proc/net/ip_tables_targets
  • cat /proc/net/netfilter/nfnetlink_queue
  • grep NFQUEUE /boot/config-$(uname -r)
  • dpkg -l 'libnetfilter-queue*'

thank you!

@gustavo-iniguez-goya gustavo-iniguez-goya changed the title unable to start opensnitch-daemon unable to start opensnitch-daemon (Error unbinding existing q handler from AF_INET proto) Mar 15, 2021
@morfikov
Copy link

I had the same error (Error while creating queue #0: Error unbinding existing q handler from AF_INET protocol family: invalid argument) and it went away after enabling the following options in the kernel (I'm not sure whether all of them are required, but I selected all of them):

CONFIG_NFT_QUEUE=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y

@gustavo-iniguez-goya
Copy link
Collaborator

Yeah @morfikov , those options usually are configured as modules in the majority of distributions, so when the iptables rules are inserted , the needed modules are loaded.

What distro are you using? Did you compile a custom kernel or you just used the one shipped with your distro?

@morfikov
Copy link

I'm using debian, but with my own kernel.

@gustavo-iniguez-goya
Copy link
Collaborator

aaah, I see. Thank you for providing this information! I suspected that it could be caused for not having support for NFQUEUE in the kernel, but I didn't know for sure. I'll update the wiki with this info.

@awsms
Copy link

awsms commented Oct 14, 2023

aaah, I see. Thank you for providing this information! I suspected that it could be caused for not having support for NFQUEUE in the kernel, but I didn't know for sure. I'll update the wiki with this info.

was this added anywhere to the wiki? i wasted a few time before finding out this info here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants
@jfreax @gustavo-iniguez-goya @morfikov @lepz0r @Brutus11111 @awsms and others