From: "Ross Simpson" <simpsora@usa.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] adv. routing features not working?
Date: Thu, 20 Dec 2001 23:24:31 +0000 [thread overview]
Message-ID: <marc-lartc-100889067117010@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100888503304877@msgid-missing>
Bert,
I think that I've just spent so much time staring at this that I think
everyone else knows what I know :)
Your suggestions work great (with one minor change).. thank you!
But... I don't understand why.
> ip rule add from 10.4.44.11 table speed
> ip rule add from 10.4.44.12 table lucent
What context is the 'from' in? It seems to me that the linux box would
never see packets from either of those two addresses (.11 and .12). Maybe
to them, but not from them.
> ip route add default via 10.4.44.1 dev eth0 table speed
> ip route add default via 10.4.44.1 dev eth0 table lucent
I changed the gw on the speed entry to 10.4.44.2, which is correct for that
router.
Thanks again for all the help..
Ross
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
Behalf Of bert hubert
Sent: Thursday, December 20, 2001 2:23 PM
To: Ross Simpson
Cc: Lartc@Mailman. Ds9a. Nl
Subject: Re: [LARTC] adv. routing features not working?
On Thu, Dec 20, 2001 at 03:17:47PM -0800, Ross Simpson wrote:
> Bert,
>
> Here's a little diagram:
Ok - that helps a *lot*. I sometimes feel as if the esteemed readers of our
list think that we are clairvoyant!
> > I N T E R N E T
> > / \
> > ------------- -------------
> > | 10.4.44.1 | | 10.4.44.2 |
> > | lucent | | speed |
> > ------------- -------------
> > port-fw 10.4.44.12:80 port-fw 10.4.44.11:80
> > \ /
> > \ /
> > |
> > eth0
> > --------------
> > | 10.4.44.11 |
> > | 10.4.44.12 |
> > | linux |
> > --------------
>
> So basically what I want is that for packets coming in from 'speed' to use
> speed as the outgoing gateway. Looking at incoming packets on the linux
> box, I see that when the router does port forwarding, it doesn't rewrite
any
> addresses -- the packets are still from the remote client and destined for
> the linux box.
Ok.
> The reason I had 'to' in my rule (and two IPs on the linux box) is so I
> could differentiate traffic from each router -- traffic going to
10.4.44.11
> has to be from the 10.4.44.2 router. The 'from' address was always
> different (the remote client).
That's still the case isn't it? I think your linux box needs this:
ip rule add from 10.4.44.11 table speed
ip rule add from 10.4.44.12 table lucent
ip route add default via 10.4.44.1 dev eth0 table speed
ip route add default via 10.4.44.1 dev eth0 table lucent
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-20 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 21:50 [LARTC] adv. routing features not working? Ross Simpson
2001-12-20 21:56 ` bert hubert
2001-12-20 22:18 ` Ross Simpson
2001-12-20 22:22 ` bert hubert
2001-12-20 23:24 ` Ross Simpson [this message]
2001-12-21 10:30 ` bert hubert
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-100889067117010@msgid-missing \
--to=simpsora@usa.net \
--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.