From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Deepak singhal" Date: Sat, 07 Jul 2001 06:33:39 +0000 Subject: Re: [LARTC] Routing MIME-Version: 1 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0020_01C106DB.2EF64320" Message-Id: List-Id: References: In-Reply-To: To: lartc@vger.kernel.org This is a multi-part message in MIME format. ------=_NextPart_000_0020_01C106DB.2EF64320 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I think there is a simple solution to all this. This is what we do in = DVB recieve-only service. What u have to do is to masquerade all ur = outgoing traffic to some ip address of ur 1.5 mb link and route it = through 384kbps link. As the ip address which is sent out is of that of = 1.5 mb link ..it will return back through ur 1.5 mb link automatically . Only restriction is that u shld hv real ips for both links , what i mean = by that is ..ur outgoing traffic shld not get masquerade agn ..as then = the traffic will come back thgh the same link.=20 Deepak Singhal ----- Original Message -----=20 From: Dave Miller=20 To: LARTC@mailman.ds9a.nl=20 Sent: Friday, July 06, 2001 8:48 PM Subject: Re: [LARTC] Routing Actually, both lines must use PPPOE - non static ip's (thanks Verizon = and Bellatlantic), I had the Bellatlantic account before the merger, and = now have the second through Verizon. Doing a double pppoe is no big = deal thanks to Roaring Penguin's software using the GUI that is = available. If my understanding is correct - if I could change the = source address of all the packets going out through the 384 line to read = what the pppoe address is for the 1.5mb line - should that not work? = The rest of the world would see the source address as that of the 1.5 = line instead of the 384 line. I just don't know how to do that. Dave ----- Original Message -----=20 From: "Arthur van Leeuwen" To: "Dave Miller" Cc: Sent: Friday, July 06, 2001 11:01 AM Subject: Re: [LARTC] Routing > On Fri, 6 Jul 2001, Dave Miller wrote: >=20 > > I am running RH 7.0 (kernel 2.2.16) as a router/masq machine with = 5 windows > > machines connected internally. I have 2 dsl lines as internet > > connections, - the first is 384k up and down. The second is = 1.5mbit down > > and only 90kb up. Is there a way to send all my upload / requests = out > > the 384 line, but have it return on the download side of the 1.5mb = line? >=20 > If both lines serve the same network, yes. However, as the dsl lines = are > most probably not to IP addresses in the same network, it is quite = unlikely > that you will succeed. The problem is not whether or not you can = configure > your system to do so; the problem is getting the rest of the world = to > recognize that your return packets should be routed back to provider = 2 > even though your packets came from provider 1. >=20 > > That would give me the best of both worlds currently. > > Since I'm using masq., does that complicate things? > > Would I be better off using Kernel 2.4 with it's advanced = features? >=20 > For routing that is a non-issue. All advanced routing stuff was in = 2.2.17 > already, but the traffic control stuff didn't mature until 2.4. >=20 > Doei, Arthur. >=20 > --=20 > /\ / | arthurvl@sci.kun.nl | Work like you don't need = the money > /__\ / | A friend is someone with whom | Love like you have never = been hurt > / \/__ | you can dare to be yourself | Dance like there's = nobody watching >=20 >=20 > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: = http://ds9a.nl/2.4Routing/ ------=_NextPart_000_0020_01C106DB.2EF64320 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I think there is a simple solution to = all this.=20 This is what we do in DVB recieve-only service. What u have to do is to=20 masquerade all ur outgoing traffic to some ip address of ur 1.5 mb link = and=20 route it through 384kbps link. As the ip address which is sent out is of = that of=20 1.5 mb link ..it will return back through ur 1.5 mb link automatically=20 .
 
Only restriction is that u shld hv = real=20 ips for both links , what i mean by that is ..ur outgoing = traffic shld not get masquerade agn ..as then the traffic=20 will come back thgh the same link. 
 
Deepak Singhal
----- Original Message -----
From:=20 Dave=20 Miller
Sent: Friday, July 06, 2001 = 8:48 PM
Subject: Re: [LARTC] = Routing

Actually, both lines must use PPPOE - non static ip's (thanks = Verizon and=20 Bellatlantic), I had the Bellatlantic account before the merger, and = now have=20 the second through Verizon.  Doing a double pppoe is no big deal = thanks=20 to Roaring Penguin's software using the GUI that is available.  = If my=20 understanding is correct - if I could change the source address of all = the=20 packets going out through the 384 line to read what the pppoe address = is for=20 the 1.5mb line - should that not work?  The rest of the world = would see=20 the source address as that of  the 1.5 line instead of the 384 = line. I=20 just don't know how to do that.
 
Dave
 
----- Original Message -----=20
From: "Arthur van Leeuwen" <arthurvl@sci.kun.nl>
To: "Dave Miller" <lartc@millerscomp.com>
=
Cc: <lartc@mailman.ds9a.nl>
=
Sent: Friday, July 06, 2001 11:01 AM
Subject: Re: [LARTC] Routing

> On Fri, 6 Jul 2001, Dave Miller wrote:
> =
>=20 > I am running RH 7.0 (kernel 2.2.16) as a router/masq machine with = 5=20 windows
> > machines connected internally.  I have 2 dsl = lines=20 as internet
> > connections, - the first is 384k up and = down. =20 The second is 1.5mbit down
> > and only 90kb up.  Is = there a way=20 to send all my upload / requests out
> > the 384 line, but = have it=20 return on the download side of the 1.5mb line?
>
> If = both lines=20 serve the same network, yes. However, as the dsl lines are
> = most=20 probably not to IP addresses in the same network, it is quite = unlikely
>=20 that you will succeed. The problem is not whether or not you can=20 configure
> your system to do so; the problem is getting the = rest of the=20 world to
> recognize that your return packets should be routed = back to=20 provider 2
> even though your packets came from provider = 1.
>=20
> > That would give me the best of both worlds = currently.
>=20 > Since I'm using masq., does that complicate things?
> > = Would I=20 be better off using Kernel 2.4 with it's advanced features?
> =
>=20 For routing that is a non-issue. All advanced routing stuff was in=20 2.2.17
> already, but the traffic control stuff didn't mature = until=20 2.4.
>
> Doei, Arthur.
>
> --
> =  =20 /\    / |      arthurvl@sci.kun.nl  &n= bsp;  =20 | Work like you don't need the money
>  /__\  /  = | A=20 friend is someone with whom | Love like you have never been = hurt
>=20 /    \/__ | you can dare to be yourself   | = Dance=20 like there's nobody watching
>
>
>=20 _______________________________________________
> LARTC mailing = list /=20 LARTC@mailman.ds9a.nl
> = http://mailman.ds9= a.nl/mailman/listinfo/lartc=20 HOWTO: http://ds9a.nl/2.4Routing/=
------=_NextPart_000_0020_01C106DB.2EF64320-- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/