All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Re: Route traffic per protocol - it is possible?
Date: Tue, 14 Jun 2005 14:47:42 -0400	[thread overview]
Message-ID: <20050614184742.GA19709@bender.817west.com> (raw)
In-Reply-To: <20050614182859.47598.qmail@web54307.mail.yahoo.com>

On Tue, Jun 14, 2005 at 11:28:58AM -0700, Scott wrote:
> Hi, I tried with the -p tcp and then with -p tcp -m
> tcp options and to no avail, but with a new error:
> 
> iptables: No chain/target/match by that name
> 
> I have gone through every bit of the command:
> 
> iptables -t mangle -A PREROUTING -p tcp -m tcp --dport
> 22 -j ROUTE --gw 1.2.3.4
> 
> ..to no avail!!  even if I change PREROUTING to INPUT,
> OUTPUT, FORWARD or POSTROUTING it's the same error..
> surely someone must know why, I'm out of answers...

you don't have support for the ROUTE target in your kernel.  if you have
a modular kernel:

  ls /lib/modules/`uname -r`/kernel/net/ipv4/netfilter/ipt_ROUTE*

if you do not have a modular kernel:

  grep ROUTE /proc/net/ip_tables_targets

if neither command produces positive output, patch and recompile your
kernel with support for the ROUTE target.

-j

--
"Peter: We could always go to purgatory like we did last year.
 Lois: This isn't bad. It's not good, but it's not bad.
 Brian: So so.
 Peter: More or less."
        --Family Guy


      reply	other threads:[~2005-06-14 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 20:29 Re: Route traffic per protocol - it is possible? Gustavo Castro Puig
2005-06-08  7:32 ` Scott
2005-06-08  7:42   ` Kenneth Kalmer
2005-06-08 17:06     ` Gustavo Castro Puig
2005-06-08 17:02   ` Gustavo Castro Puig
2005-06-14 18:28     ` Scott
2005-06-14 18:47       ` Jason Opperisano [this message]

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=20050614184742.GA19709@bender.817west.com \
    --to=opie@817west.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 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.