From: "hareram" <hareram@sol.net.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] need help on multiple isp routing
Date: Fri, 30 Sep 2005 07:55:17 +0000 [thread overview]
Message-ID: <064101c5c592$9f746670$09603fca@southern> (raw)
In-Reply-To: <000901c5c4c8$d4a518a0$1000a8c0@naksitrallid.dyn.ee>
Hi
the best way to do is
Source route Routing and Masq
hare
----- Original Message -----
From: "Anonymous" <netmon@hot.ee>
To: "LARTC" <lartc@mailman.ds9a.nl>
Sent: Friday, September 30, 2005 1:05 PM
Subject: Re: [LARTC] need help on multiple isp routing
> thank you very much for your reply! i've red your article even it mention
> a 50x50 multipath load ballance (am i right?) solution which is not
> exactly what i need. now i begin to realize how wrong i was. but i need
> more like a "split" kind of access with 2 different ISPs - 1 ISP for just
> 1 PC (192.168.0.16), and then another ISP for all the other clients
> (192.168.0.0/26). anyway your article is kinda helpfull. i don't give up
> on split access idea, even i already spent 3 days of my 6 day vacation
> trying to configure it. i still have 3 days more! :)
>
> ----- Original Message -----
> From: "hareram" <hareram@sol.net.in>
> To: "Anonymous" <netmon@hot.ee>; <lartc@mailman.ds9a.nl>
> Sent: Friday, September 30, 2005 9:20 AM
> Subject: Re: [LARTC] need help on multiple isp routing
>
>
>> Hi
>>
>> This Link may help you
>>
>> http://linux.com.lb/wiki/index.pl?node=Load%20Balancing%20Across%20Multiple%20Links
>>
>> hare
>> ----- Original Message -----
>> From: "Anonymous" <netmon@hot.ee>
>> To: <lartc@mailman.ds9a.nl>
>> Sent: Thursday, September 29, 2005 2:53 PM
>> Subject: [LARTC] need help on multiple isp routing
>>
>>
>>> here's my network layout
>>>
>>>
>>> ppp0 (ADSL 2048/256)
>>> |
>>> | ppp1 (SDSL 1024/1024)
>>> | |
>>> -------- LINUX -------
>>> |
>>> eth0 (192.168.0.1 DHCP+DNS, Squid, Samba)
>>> |
>>> |
>>> -----8 port 100mbit dumb switch
>>> | | | | |
>>> 192.168.0.16/26 | | |
>>> | | - DHCP
>>> assigned clients
>>> | ---
>>> (192.168.0.0/26)
>>> -----
>>>
>>> i need 192.168.0.16 to take ppp0 route for all it's needs (masquaraded
>>> on ppp0) and use transparent squid cache set up on 192.168.0.1 for www.
>>> while all other DHCP assigned clients would use masquerading on ppp1 for
>>> all their needs and use forced load-ballanced cache of second ISP.
>>> _______________________________________________
>>> LARTC mailing list
>>> LARTC@mailman.ds9a.nl
>>> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>>>
>>>
>>
>>
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-09-30 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 7:37 [LARTC] need help on multiple isp routing Anonymous
2005-09-29 9:23 ` Anonymous
2005-09-30 6:32 ` hareram
2005-09-30 7:35 ` Anonymous
2005-09-30 7:55 ` hareram [this message]
2005-10-01 19:13 ` Anonymous
2005-10-03 14:37 ` Anonymous
2005-10-03 15:38 ` /dev/rob0
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='064101c5c592$9f746670$09603fca@southern' \
--to=hareram@sol.net.in \
--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.