From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Antonio Alvarez <aramirez@teneinformatica.com>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: iptables and iproute
Date: Mon, 26 Apr 2004 03:55:20 -0400 [thread overview]
Message-ID: <1082966119.19776.1.camel@localhost> (raw)
In-Reply-To: <1082964013.1772.14.camel@Toshiba.Toshiba>
On Mon, 2004-04-26 at 03:20, Antonio Alvarez wrote:
> Hello every body!
>
> I have a machine with 4 ethernet interfaces, 3 directly connected to
> ADSL lines a the another one to a LAN.
>
> I have 3 routing tables with iproute ( each one with his default gw for
> each ADSL line )
>
> I don't have problems with packet traversing my linux machine ( mangle
> the packet in the PREROUTING chain ) to routing.
>
> The problem is how can i control the packet localy generated( ip and
> port )???
> i can't mangle this packet before routing :-/
>
> for example a need to use ssh server in the linux machine using ADSL 1
> but when the machime aswer me use the ADSL 3 ( because this is the
> default gw in the main routing table :-( ...
>
> In sumarize it's possible to use different routing tables with packet
> generated localy??
<snip>
I don't recall the syntax off the top of my head but isn't it possible
to create a iproute2 rule where iif = lo to route locally generated
packets. I believe that's how we do it in the ISCS project. You can
check the ISCS training docs at http://iscs.sourceforge.net - John
--
Open Source Development Corporation
Financially Sustainable open source development
http://www.opensourcedevelopmentcorp.com
next prev parent reply other threads:[~2004-04-26 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 7:20 iptables and iproute Antonio Alvarez
2004-04-26 7:51 ` Cedric Blancher
2004-04-26 8:08 ` Antonio Alvarez
2004-04-26 8:59 ` Cedric Blancher
2004-04-26 9:20 ` Antonio Alvarez
2004-04-26 16:53 ` Antonio Alvarez
2004-04-26 17:27 ` Cedric Blancher
2004-04-26 7:55 ` John A. Sullivan III [this message]
2004-04-26 8:10 ` Antonio Alvarez
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=1082966119.19776.1.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=aramirez@teneinformatica.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.