From: "Jason A. Pattie" <pattieja@pcxperience.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Loadbalancing the gateway
Date: Wed, 17 Oct 2001 16:39:56 +0000 [thread overview]
Message-ID: <marc-lartc-100333696222633@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100262859606804@msgid-missing>
Of course, unless the other network knows how to route to the network
your client resides on, and I'm sure it probably can't.
Logu wrote:
>Hi Jason,
>thanks for your response.
>I am not able to ping outside from client machines.
>I have a doubt. If the client and router is on different network, is it
>necessary to implement NATing.
>
>>You actually only have two connections then that Linux can see. One,
>>I'm assuming, is a router that has multiple connections to the ISP which
>>it assigns as the same IP address (multi-line ISDN is similar).
>>
>>You will need to setup your multipath default route like so on the Linux
>>box:
>>
>>If eth0 is assigned 172.16.1.2 on your Linux router, then
>>
>>ip route add default nexthop via 172.16.1.204 dev eth0 nexthop via
>>172.16.1.205 dev eth0
>>
>>If you want to make one route work more than the other, you can assign
>>weights to the routes right after each dev entry in the route statement
>>(i.e., "ip route ... dev eth0 weight 2 ... dev eth0 weight 1", this
>>would send twice as many connections out the first route as the second
>>route). Remember that if you do not use the 'equalize' modifier to the
>>route statement, you get traffic broken up across the links on a per
>>session basis. If using the 'equalize' parameter, it will be broken
>>across the links on a per packet basis.
>>
>>Logu wrote:
>>
>>>Hi,
>>>This is my network
>>>My LAN IP is 172.16.1.0/255.255.255.0
>>>I have two router which has LAN IP 172.16.1.204 and another one
>>>
>172.16.1.205
>
>>>My Linux machine IP is 172.16.1.1.
>>>I have two interface for linux machine one is conected to switch where
>>>
>all
>
>>>my windows machines are connected and another one 172.16.1.2 is connected
>>>
>to
>
>>>hub where my routers are connected
>>>I set windows machines gateway as 172.16.1.1
>>>
>>>Now how should i activate multipath routing
>>>
>>>-Logu
>>>
>>>>You might try multi-path routing. It doesn't exactly load balance the
>>>>lines, as in aggregating the bandwidth together, but it does allow N
>>>>number of simultaneous connections (where N would be the maximum number
>>>>of different routes you have).
>>>>
>>>>In your scenario, let's say you have the 3 routers with IP addresses of
>>>>1.1.1.1/30, 2.2.2.2/30, and 3.3.3.3/30. Now, you have your Linux
>>>>firewall/gateway/router/thingy between the routers and the client. On
>>>>your Linux box, you could have 3 separate network cards each connected
>>>>to one of the routers, or you could have a single network card connected
>>>>to all three routers via a hub or switch (switch would probably be
>>>>better). Let's say you have one network card. In that scenario, you
>>>>would assign an IP address in each of the network ranges for the each of
>>>>the routers. I.e., 1.1.1.2/30, 2.2.2.3/30, 3.3.3.4/30 (note: these IP
>>>>address are probably completely incorrect for assignment in the network
>>>>range I have chosen, just using them as examples; you would get usable
>>>>IP's from your ISP). To assign these IP address, use the 'ip' command.
>>>>
>>>>ip addr add 1.1.1.2/30 brd + dev eth0
>>>>ip addr add 2.2.2.3/30 brd + dev eth0
>>>>ip addr add 3.3.3.4/30 brd + dev eth0
>>>>
>>>>Now, you will need to setup the multi-path route as your default route.
>>>>You can specify the 'equalize' parameter if you like, but I have found
>>>>that it doesn't do exactly what you might expect it to do.
>>>>
>>>>ip route add default nexthop via 1.1.1.1 dev eth0 \
>>>> nexthop via 2.2.2.2 dev eth0 \
>>>> nexthop via 3.3.3.3 dev eth0
>>>>
>>>>And that should take care of that. Now all of this is assuming that you
>>>>have multiple, different IP ranges for your 3 ISDN lines. If they are
>>>>all in the same network range, you can forego having 3 IP's assigned to
>>>>the same network card on your firewall. In that case you would only
>>>>need one. Then substitue appropriately for the router IP addresses.
>>>>
>>>>Logu wrote:
>>>>
>>>>>Hi,
>>>>>I have 3 isdn connections. Is it possible to loadbalace the bandwidth
>>>>>
>>>using
>>>
>>>>>a linux box in between the routers and the client. I will be very much
>>>>>greatful to you if someone helps me in this.
>>>>>
>>>>>-Logu
>>>>>
>
>
>
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
>
--
Jason A. Pattie
pattieja@pcxperience.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-10-17 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 11:56 [LARTC] Loadbalancing the gateway Logu
2001-10-09 14:41 ` Jason A. Pattie
2001-10-11 22:51 ` Julian Anastasov
2001-10-16 14:22 ` Logu
2001-10-16 14:42 ` Jason A. Pattie
2001-10-17 4:36 ` Logu
2001-10-17 16:39 ` Jason A. Pattie [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=marc-lartc-100333696222633@msgid-missing \
--to=pattieja@pcxperience.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.