All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Salim <salim.si@askey.com.tw>
Cc: lartc@mailman.ds9a.nl,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [LARTC] ip_queue module issue
Date: Wed, 04 Jan 2006 07:13:19 +0000	[thread overview]
Message-ID: <43BB758F.4020409@trash.net> (raw)
In-Reply-To: <002c01c610d4$a04e3930$455f030a@askeyrd3>

Salim wrote:
> it does work when iptables as a whole is built as a module.

Do you use any patches that might register as queue handler,
like IMQ? Otherwise please check your logs for messages from
ip_queue during boot time, it should have logged the reason
if registration failed.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Salim <salim.si@askey.com.tw>
Cc: lartc@mailman.ds9a.nl,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: ip_queue module issue
Date: Wed, 04 Jan 2006 08:13:19 +0100	[thread overview]
Message-ID: <43BB758F.4020409@trash.net> (raw)
In-Reply-To: <002c01c610d4$a04e3930$455f030a@askeyrd3>

Salim wrote:
> it does work when iptables as a whole is built as a module.

Do you use any patches that might register as queue handler,
like IMQ? Otherwise please check your logs for messages from
ip_queue during boot time, it should have logged the reason
if registration failed.

  reply	other threads:[~2006-01-04  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03  2:48 [LARTC] ip_queue module issue Salim
2006-01-03 12:58 ` Patrick McHardy
2006-01-03 12:58   ` Patrick McHardy
2006-01-04  2:14   ` Salim
2006-01-04  2:14     ` Salim
2006-01-04  7:13     ` Patrick McHardy [this message]
2006-01-04  7:13       ` Patrick McHardy

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=43BB758F.4020409@trash.net \
    --to=kaber@trash.net \
    --cc=lartc@mailman.ds9a.nl \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=salim.si@askey.com.tw \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.