All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath Routing..
Date: Tue, 16 Aug 2005 08:39:38 +0000	[thread overview]
Message-ID: <20050816083938.GE20254@samad.com.au> (raw)
In-Reply-To: <4301676E.4070100@cyberdoc.dk>


[-- Attachment #1.1: Type: text/plain, Size: 2596 bytes --]

On Tue, Aug 16, 2005 at 06:11:26AM +0200, Daniel Frederiksen wrote:
> Ok folks, here goes..
> 
> I have been boggling with a problem for the past week, and still haven't 
> found a solution..
> 
> I'm trying to route traffic from two providers through a Linux machine.
> But that is not the problem. The ISP's have provided me with a WAN IP 
> class for both of the lines, to be routed into a DMZ where the machines 
> a to respond to their respective designated WAN IP on both lines.
> Every machine on the DMZ has two IP's one on each ISP WAN Class.
> 
> I think I'll better draw a map:
> 
> 
>       WAN1(eth2), WAN2(eth3)
>            ---------                             (eth0)
>            |       |-----\                     ----------
>            |  DMZ  |---\  \                /---|  ISP1  |-----
>            ---------    \  \              /    ----------     \
>                          \  \            /                     \
>                          -----------------
>                          |  Linux GW/FW  |                     WWW
>                          -----------------
>                          /               \       (eth1)        /
>            ---------    /                 \    ----------     /
>            |  LAN  |---/                   \---|  ISP2  |-----
>            ---------                           ----------
>               NAT(eth4)
> 
> 
> The DMZ has two WAN IP classes routed from the ISP.
> 
> The thing I just can not figure out is how to make the respective WAN IP 
> from the DMZ route out the right ISP link, and the right request from 
> the ISP route into the DMZ.
> 
> .. and finally how can I make the LAN able to access it all..

you need to use ip ru

my ip ru looks like 
0:      from all lookup local 
200:    from 141.168.16.16 lookup cable 
201:    from 220.233.15.63 lookup adsl 
32766:  from all lookup main 
32767:  from all lookup default 

I created 200 and 201 which means that all traffic that came in on the
cable 141.168.16.16 will go out the cable

ip ro sh tab cable
192.168.11.0/24 dev br0  scope link 
192.168.10.0/24 dev eth3  scope link 
192.168.9.0/24 dev eth4  scope link 
default via 141.168.16.1 dev eth0  src 141.168.16.16  metric 30 


and the routing tab for the adsl uses the adsl as its default gw.

does that help ?


> 
> Thanks for your time..
> 
> /Daniel Frederiksen
> 
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-08-16  8:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  4:11 [LARTC] Multipath Routing Daniel Frederiksen
2005-08-16  8:39 ` Alexander Samad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-24  2:18 [LARTC] multipath routing Lists @ Aptedtech
2004-03-24  6:05 ` RonSenykoff
2004-03-25  1:22 ` Lists @ Aptedtech
2005-10-26 21:47 ` comp.techs
2005-10-27 14:20 ` Edmundo Carmona
2005-10-27 16:02 ` comp.techs
2005-10-27 18:05 ` comp.techs
2005-11-17 20:47 ` comp.techs
2007-06-05  9:13 ` [LARTC] Multipath routing Michał Margula
2007-06-05 19:46 ` Piotr Chytla
2007-06-06 10:05 ` Michał Margula
2007-06-07  9:07 ` Michał Margula

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=20050816083938.GE20254@samad.com.au \
    --to=alex@samad.com.au \
    --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.