Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Yann Lejeune <lejeuney@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Problem with ROUTE target
Date: Mon, 30 Jul 2007 14:24:11 +0200	[thread overview]
Message-ID: <20070730122411.GA6610@mano.netyl.org> (raw)
In-Reply-To: <2cb453e80707300029m341a5afap295e775ea0572e7c@mail.gmail.com>

On 2007/07/30-09:29(+0200), Ludovic wrote :
> i'm using kernel 2.6.21.5 and iptables 1.3.7. I have patched it with
> patch-o-matic in order to have the ROUTE target but it doesn't work:
> 
> root@linux:~ $ iptables -t mangle -A POSTROUTING -d 10.8.0.6 -j ROUTE --oif tun0
> iptables: No chain/target/match by that name
> 
> root@linux:~ $ ll /lib/iptables/ | grep ROUTE
> 12 -rwxr-xr-x 1 root root  8216 Jul 26 17:55 libipt_ROUTE.so
> 
 < skip >
> 
> root@linux:~ $ lsmod
> Module                  Size  Used by
> ipt_ROUTE               3760  0
> 
> What can i do to find where my problem is ?
> 

Hi Ludovic,
 Two things:

  - help message on errors is given by iptables in user-land. It seems that
    it's compiled with "ROUTE target" support. So it (iptables) "knows" the
    command line synthax. In this case, it is a "user-land error".

  - The error you get when you send a valid command line, comes from that
    the ROUTE target may not be correctly loaded in the netfilter framework
    but lsmod shows us that you performed a modprobe...

 Can you please send the content of the file proc/net/ip_tables_target


Regards

Yann.



  reply	other threads:[~2007-07-30 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30  7:29 Problem with ROUTE target Ludovic
2007-07-30 12:24 ` Yann Lejeune [this message]
2007-07-30 12:29   ` Ludovic
  -- strict thread matches above, loose matches on Subject: below --
2006-03-24 10:34 Francis.Sauch

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=20070730122411.GA6610@mano.netyl.org \
    --to=lejeuney@gmail.com \
    --cc=netfilter@lists.netfilter.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