From: Esteban Ribicic <eribicic@UolSinectis.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip rule nat Pathces!?
Date: Wed, 05 Mar 2003 12:38:16 +0000 [thread overview]
Message-ID: <marc-lartc-104686793921170@msgid-missing> (raw)
julian,
the patch stuff is making me crazy (i have four servers running
iproute2)..
i tryed to apply pathces on 2.4.20 in the following order so multipath,
nat, fwmark works:
routes-2.4.20-9.diff
rtmasq-2.4.20-2.diff
is the second patch necesary? i though the first (routes-2.4.20-9.diff)
already patched the nat stuff.
besides, if i apply the first patch, the second gives me an error
applyeng the patch.
what patches should apply for 2.4.20? thanks.
On Tue, 2003-03-04 at 20:30, Julian Anastasov wrote:
>
> Hello,
>
> On 4 Mar 2003, Esteban Ribicic wrote:
>
> > when doing somehitng like
> > ip rule add fwmark 3 nat 200.42.75.183 table ppp0 prio 1
> > (the idea is that packets that match the fwmark 3 change their source
> > address to 200.42.75.183)..it first apply the nat and then routes to
> > table ppp0 right?
> > in such case the, nat, why may be nat not being applyed?
> > cause it doesnt work at all..it goes to that interface but does not nat
> > the src address of the package.
> > any idea?
>
> It is not supported but there is a patch:
>
> http://www.ssi.bg/~ja/#rtmasq
>
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
>
>
--
Esteban Ribicic
Network Operation Center
UOL-Sinectis S.A.
Florida 537 Piso 6, Buenos Aires, Argentina
+54-11-4321-9110 Ext 2503
+54-11-4321-9107 Directo
eribicic@uolsinectis.com
www.uolsinectis.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-03-05 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 12:38 Esteban Ribicic [this message]
2003-03-05 22:58 ` [LARTC] ip rule nat Pathces!? Julian Anastasov
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=marc-lartc-104686793921170@msgid-missing \
--to=eribicic@uolsinectis.com \
--cc=lartc@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 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.