From: "Dave Miller" <lartc@millerscomp.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing
Date: Fri, 06 Jul 2001 15:18:05 +0000 [thread overview]
Message-ID: <marc-lartc-99443982309048@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416816@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]
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 -----
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:
>
> > 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?
>
> 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.
>
> > 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?
>
> 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.
>
> Doei, Arthur.
>
> --
> /\ / | 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
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
[-- Attachment #2: Type: text/html, Size: 3712 bytes --]
next prev parent reply other threads:[~2001-07-06 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 11:13 [LARTC] routing Spyros
2001-01-03 12:37 ` David
2001-01-05 12:25 ` Junus
2001-01-05 12:33 ` Junus
2001-07-06 14:03 ` [LARTC] Routing Dave Miller
2001-07-06 15:01 ` Arthur van Leeuwen
2001-07-06 15:18 ` Dave Miller [this message]
2001-07-07 6:33 ` Deepak singhal
2001-07-07 18:24 ` Arthur van Leeuwen
2001-07-07 18:33 ` Dave Miller
2001-07-07 18:37 ` Arthur van Leeuwen
2001-12-25 4:58 ` [LARTC] routing Daniel Wittenberg
2001-12-25 12:16 ` bert hubert
2002-10-30 12:57 ` [LARTC] Routing Jose Sebastiao Martins
2002-10-30 15:57 ` Martin A. Brown
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-99443982309048@msgid-missing \
--to=lartc@millerscomp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox