Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Eric B." <ebenze@hotmail.com>
To: netfilter@vger.kernel.org
Subject: Re: iptables -j ROUTE --gw xxxx not working?
Date: Tue, 8 Apr 2008 15:20:52 -0400	[thread overview]
Message-ID: <ftggj3$kkk$1@ger.gmane.org> (raw)
In-Reply-To: alpine.LNX.1.10.0804082104350.2229@fbirervta.pbzchgretzou.qr

"Jan Engelhardt" <jengelh@computergmbh.de> wrote in message 
news:alpine.LNX.1.10.0804082104350.2229@fbirervta.pbzchgretzou.qr...
>
> On Tuesday 2008-04-08 20:38, Eric B. wrote:
>>Hi,
>>
>>I'm running RHEL4.2 with iptables iptables v1.2.11 from pkg
>>iptables-1.2.11-3.1.RHEL4.
>>
>>I've tried the following command but been told that --gw argument is
>>unknown:
>>
>># iptables -t mangle -I POSTROUTING -j ROUTE --gw 192.168.104.251
>>iptables v1.2.11: Unknown arg `--gw'
>
> Then you don't have(*) ROUTE. I would not even bother with this
> ancient method of policy routing. Nowadays, MARK is used together
> with iproute2 to select output routes.

I would be more than happy to avoid this ancient method of policy routing. 
Indeed, I was trying to get MARK to work together with iproute2 to select my 
output routes and wasn't working, hence I figured I would try something 
different (see my msg titled Need help understanding how to debug packet 
traversal) and see if my logic was at least right.  I seem to be having a 
lot of difficulty "seeing" what my packet is doing via iptables/iproute2.

Sure enough, I did a quick search for a *.ROUTE.so module and couldn't find 
anything on my system.

Okay - back to the drawing board then....

Thanks for the clarification,

Eric




      reply	other threads:[~2008-04-08 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 18:38 iptables -j ROUTE --gw xxxx not working? Eric B.
2008-04-08 19:06 ` Jan Engelhardt
2008-04-08 19:20   ` Eric B. [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='ftggj3$kkk$1@ger.gmane.org' \
    --to=ebenze@hotmail.com \
    --cc=netfilter@vger.kernel.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