Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] multiple gateway problem
Date: Tue, 04 Dec 2001 17:54:11 +0000	[thread overview]
Message-ID: <marc-lartc-100748852521060@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100740321228322@msgid-missing>

Ross,

I'm new to this stuff myself, but do you have any default routes set up for
packets that are neither from 10.4.44.1 or 10.4.44.2? Are you testing from
inside or outside? In my own trials what you list below will allow outside
connections through either line, but inside-to-outside stuff isn't caught by
either rule and depends on general defaults.

I'm unclear though on just when a packet generated on the router takes on
which IP as its identity (for instance, when it presents with the
'localhost' IP). It does seem that when a request comes in on a certain
external IP that IP is preserved in the packets of a responding daemon, if
the daemon's on the router, so rules like yours apply to it. 

Obviously I should spend an afternoon with a packet sniffer testing this
stuff out - I haven't run across a full explanation of it yet.

Whit

On Mon, Dec 03, 2001 at 11:15:42AM -0800, Ross Simpson wrote:

> echo 199 lucent >> /etc/iproute2/rt_tables (router #1)
> echo 200 speed >> /etc/iproute2/rt_tables (router #2)
> ip rule add from 10.4.44.1 table lucent
> ip rule add from 10.4.44.2 table speed
> 
> ip rule ls:
> 0:      from all lookup local
> 32764:  from 10.4.44.2 lookup speed
> 32765:  from 10.4.44.1 lookup lucent
> 32766:  from all lookup main
> 32767:  from all lookup 253
> 
> ip route add default via 10.4.44.1 dev eth0 table speed
> ip route add default via 10.4.44.2 dev eth0 table lucent
> ip route flush cache
> 
> I can access forwarded ports on the external ip of the 'lucent' router, but
> forwarded ports on the 'speed' router are not answering.
> I've verified that port forwarding on the speed router works.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-12-04 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 18:13 [LARTC] multiple gateway problem Ross Simpson
2001-12-04 14:48 ` Jorge Castellet
2001-12-04 17:54 ` Whit Blauvelt [this message]
2001-12-04 21:09 ` Ross Simpson
2001-12-04 21:31 ` Whit Blauvelt
2001-12-05  7:14 ` Kristian Hoffmann
2001-12-06 17:13 ` Ross Simpson
2001-12-06 17:44 ` Whit Blauvelt

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-100748852521060@msgid-missing \
    --to=whit@transpect.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox