All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brent Clark <bclark@eccotours.dyndns.org>
To: iptables <netfilter@lists.netfilter.org>
Subject: ROUTE  woes ?
Date: Tue, 23 Aug 2005 20:09:19 +0200	[thread overview]
Message-ID: <430B664F.3030006@eccotours.dyndns.org> (raw)
In-Reply-To: <20050818154431.GA7489@oasis.frogfoot.net>


Hi list

I tried at suggestion of:

gate:/usr/src# iptables -t mangle -A FORWARD -p tcp --dport 80 -j ROUTE --oif eth2

But all i get is:
iptables: No chain/target/match by that name

During this time I have been googling and trying to find out why this is failing.

The reason I cant undertand is that I am running debian sarge so therefore the iptables version is v1.3.1

I looked for the module ROUTE and it defiantly if there.

ROUTE target v1.11 options:
     --oif       ifname          Route packet through `ifname' network interface
     --iif       ifname          Change packet's incoming interface to `ifname'
     --gw        ip              Route packet via this gateway `ip'
     --continue                  Route packet and continue traversing the
                                 rules. Not valid with --iif or --tee.
     --tee                       Duplicate packet, route the duplicate,
                                 continue traversing with original packet.
                                 Not valid with --iif or --continue.

So on looking at the kernel src

I worked out that I had not added or  complied in multipath, I have now

gate:/usr/src/linux# cat .config | grep ROUTE
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y

and too this day I still am getting

gate:/usr/src/linux# iptables -t mangle -A FORWARD -p tcp --dport 80 -j ROUTE --oif eth2
iptables: No chain/target/match by that name
gate:/usr/src/linux#

If anyone can help in anyway, I would be most greatful.

Kind Regards, and again thanks in advance.

Brent Clark



       reply	other threads:[~2005-08-23 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4304A259.3070906@eccotours.co.za>
     [not found] ` <20050818154431.GA7489@oasis.frogfoot.net>
2005-08-23 18:09   ` Brent Clark [this message]
2005-08-23 19:23     ` ROUTE woes ? Ruben Cardenal
     [not found] <E1E7eMx-00076v-2D@mail.eccotours.co.za>
2005-08-23 20:14 ` Brent Clark
2005-08-23 20:20   ` Ruben Cardenal
     [not found] <20050823201959.3AC9E49EE@sorry.no-ip-here.net>
2005-08-23 20:29 ` /dev/rob0
2005-08-23 20:34   ` Ruben Cardenal
     [not found] <20050823203317.5EA2749EE@sorry.no-ip-here.net>
2005-08-23 20:52 ` /dev/rob0
     [not found] <200508231925.j7NJPMB6017123@linux01.gwdg.de>
2005-08-24  5:55 ` Jan Engelhardt
2005-08-24  6:18   ` Ruben Cardenal
     [not found] <E1E7obP-0004Pv-UB@mail.eccotours.co.za>
2005-08-24  8:00 ` Brent Clark

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=430B664F.3030006@eccotours.dyndns.org \
    --to=bclark@eccotours.dyndns.org \
    --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.