All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Jaussaud" <tatooin@kelkoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Multipath Routing Question with Public networks
Date: Sat, 16 Nov 2002 16:12:20 +0000	[thread overview]
Message-ID: <marc-lartc-103746321608005@msgid-missing> (raw)

Hi there;

I'm planning to implement multipath routing across two ISP in the next few weeks, but 
before going further, I have a routing question which is puzzling me :)

Here is the setup:

10.0.0.0/8    172.16.0.0/16
 ISP1        ISP2
  |            |
  |            |
 _|____________|_
 [Linux Firewall]
  |            |
__|_____       |
     |         |
     |       __|_____
     |        | 
_____|________|__________
[Internal Public Network]

All machines are linux based. (Firewall is kernel 2.2, public servers are either 2.2 or 
2.4)

Linux firewall has 4 networks interfaces, all of them using public IP's; 2 routed through 
ISP1, others 2 routed through ISP2. 
From the firewall itself, we can do multipath routing over both ISP's without problems.
In this network topology, we don't use NAT. ALL IPs are publics, and belongs to either 
ISP1 or ISP2 network. So that all servers in the Internal Public Network are reachable 
from the Internet, through both links. 
All servers do have 2 network adapters, using public IPs belonging to ISP1 & ISP2 
networks. 
On All servers, we setup multipath default route, so that they can use both link as well.

Let's say we have Server A in our internal public network, with 2 network adapters, one 
using 10.0.0.1 (routed through ISP1), other using 172.16.0.1 (routed through ISP2)

Assuming that rp_filter is configured correctly on our firewall, what happens when a 
client want to reach Server A using 10.0.0.1 ? What path will be used for the replies, 
with what source IP ?

I assume that if rp_filter is configured correctly, return path do not matter (since we 
don't do NAT), but I'm worried about the SRC IP beeing choosed for the reply. Because, if 
the kernel choose the src IP according to the output default route beeing choosed, then 
half clients<->servers sessions will just break.

So, basically my question is, what rules decide of the SRC IP to be used in a reply 
packet on a system with several default route through different network interfaces ?

Has anyone already experiencing such setup ?

Thanks In advance !
Regards,

Vincent.

---
Vincent Jaussaud
Kelkoo - Security Manager / Networks & Systems Administration
AIM Nick: portsentry
---

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

             reply	other threads:[~2002-11-16 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-16 16:12 Vincent Jaussaud [this message]
2002-11-16 20:58 ` [LARTC] Multipath Routing Question with Public networks Julian Anastasov
2002-11-17 18:34 ` Vincent Jaussaud Mailing Listes
2002-11-17 20:43 ` Julian Anastasov
2002-11-18 11:24 ` Vincent Jaussaud
2002-11-18 11:59 ` Julian Anastasov
2002-11-18 14:21 ` Vincent Jaussaud

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-103746321608005@msgid-missing \
    --to=tatooin@kelkoo.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.