From: James Morris <jmorris@intercode.com.au>
To: Jean-Michel Hemstedt <jean-michel.hemstedt@alcatel.be>
Cc: netfilter-devel@lists.samba.org, netfilter@lists.samba.org
Subject: Re: FYI: QUEUE & ipqmpd bugs
Date: Sat, 6 Jul 2002 02:12:01 +1000 (EST) [thread overview]
Message-ID: <ag4gim$3mn$2@main.gmane.org> (raw)
In-Reply-To: <003301c2242d$7fca2e40$0689cb8a@etbx180>
On Fri, 5 Jul 2002, Jean-Michel Hemstedt wrote:
> FYI,
>
> I upgraded to iptables-1.2.6a (user & kernel-2.4.18 patches)
> and got the following (maybe known) problems:
>
> - QUEUE target is NOK with kernel compiled with CONFIG_IP_NF_QUEUE=m
> => the packets are queued, but ipq_create_handle() returns
> "can't create netlink socket"
> "ERROR: Unable to create netlink socket: Connection refused"
> (problem with exported symbols?)
> =>quick fix: compile kernel with CONFIG_IP_NF_QUEUE=y
>
You need to explicitly load the ip_queue module.
- James
--
James Morris
<jmorris@intercode.com.au>
next parent reply other threads:[~2002-07-05 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003301c2242d$7fca2e40$0689cb8a@etbx180>
2002-07-05 16:12 ` James Morris [this message]
2002-07-05 19:15 ` FYI: QUEUE & ipqmpd bugs Harald Welte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ag4gim$3mn$2@main.gmane.org' \
--to=jmorris@intercode.com.au \
--cc=jean-michel.hemstedt@alcatel.be \
--cc=netfilter-devel@lists.samba.org \
--cc=netfilter@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox