All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rafal Krzewski <Rafal.Krzewski@caltha.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing with multiple uplinks problem
Date: Mon, 24 May 2004 10:38:59 +0000	[thread overview]
Message-ID: <40B1D0C3.7050807@caltha.pl> (raw)
In-Reply-To: <40B1A7EB.7010300@caltha.pl>

Jose Luis Domingo Lopez wrote:

>>+-------------+                      +-------------+
>>|    actaea   |                 eth0 |    ilex     |
>>| 192.168.1.4 |------ localnet ------| 192.168.1.1 |
>>+-------------+    192.168.1.0/24    +-------------+
>>                                 eth1 /          | ppp0
>>                               80.72.34.162  83.31.149.159 
>>
>>                                     /           |
>>                                  wlnet        tpsa
>>                            80.72.34.160/24      |
>>                                  /              |
>>                         +--------------+   +------------+
>>                         | 80.72.34.161 |   | 213.25.2.3 |
>>                         +--------------+   +------------+
>>                                 \               /
>>                                  \-----------, /
>>       +--------------+          ""            \
>>       |    salix     |        /   Internet    "
>>       | 212.87.7.182 |--------'-,          ,-"
>>       +--------------+           "--------"

>>ilex:~# ip rule show
>>0:      from all lookup local
>>32764:  from 213.25.2.3 lookup tpsa
>>32765:  from 80.72.34.161 lookup wlnet
>>32766:  from all lookup main
>>32767:  from all lookup default
>>
> 
> "ip rules" 32764 and 32765 will only apply to traffic with source IP
> addresses as shown, but not to traffic coming through any of the
> associated routers (except this routers also do SNAT to traffic coming
> from the Internet). So packets from salix (212.87.7.182) will be routed
> looking first at table local (the one that should apply to traffic
> ending at ilex itself), and then loooking at "table main".

And... this was the problem!

I misread the following lines from the HOWTO:
	    ip rule add from $IP1 table T1
	    ip rule add from $IP2 table T2
as:
	    ip rule add from $P1 table T1
	    ip rule add from $P2 table T2
resulting in invalid rule entries

Now, with the following rule table everything works correctly:

ilex:~# ip rule show
0:      from all lookup local
32764:  from 83.31.149.159 lookup tpsa
32765:  from 80.72.34.162 lookup wlnet
32766:  from all lookup main
32767:  from all lookup default

Many thanks for pointing me the right direction!

Rafal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-05-24 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24  7:44 [LARTC] routing with multiple uplinks problem Rafal Krzewski
2004-05-24  8:36 ` Jose Luis Domingo Lopez
2004-05-24 10:38 ` Rafal Krzewski [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=40B1D0C3.7050807@caltha.pl \
    --to=rafal.krzewski@caltha.pl \
    --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.