From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per-connection routing for multiple uplinks/providers
Date: Tue, 16 Apr 2002 06:56:43 +0000 [thread overview]
Message-ID: <marc-lartc-101894033010404@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101890143014670@msgid-missing>
On Tue, 16 Apr 2002, Bob Gustafson wrote:
> >On Mon, 15 Apr 2002, Bob Gustafson wrote:
> >
> >> What I would like to do is cleanly move packets out to the Internet over
> >> two (maybe 3) separate interfaces, utilizing all of the bandwidth, and
> >> avoiding snags.
> >
> >[snip, lots of nice interesting wishes]
> >
> >> Does such a beast exist? Is it possible to build with current
> >> ip/tc/netfilter technology? I am running a near stock RH 7.2 at the
> >> moment. Each ISP line is going through a separate (proprietary/black-box)
> >> firewall/router and then into the RH7.2 box.
> >
> >QoS and routing are basically independent of each other. Orthogonal,
> >mathematicians would say. Furthermore, there *is* in fact a patch floating
> >around somewhere on the internet that flushes the route cache after every
> >packet... that might help. I've never used it, as I don't trust it to keep
> >TCP connections intact, but still, it might prove useful.
> >
> >You'll have to do some digging on your own though...
>
> I was afraid of that. But this list was the first place to dig, yes?
Yes, nowadays it is. :) At least you know there's something out there.
Oh, as I recall the patch is by some weird guy in Utrecht, The Netherlands.
Can't seem to find it using Google at the moment though.
The stuff on http://www-2.cs.cmu.edu/~jcl/programs/ipeql/ipeql.html
does seem like something you might want to look at (even though it is
*old*).
> >
> >Doei, Arthur. (Oh, and it is Arthur van Leeuwen. The surname is
> > 'van Leeuwen'. Kinda like in 'Ludwig van Beethoven')
>
> Ahh, learn something every day. The van *isn't* just like a middle
> name then.
Nope. It would've been capitalized if it were. :)
> (I was pretty careful about the spelling of Leeuwen though :-)
Don't computers make life *easy*? :P
> Thanks much for the feedback
My pleasure.
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://lartc.org/
next prev parent reply other threads:[~2002-04-16 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 20:08 [LARTC] Per-connection routing for multiple uplinks/providers ?? Bob Gustafson
2002-04-15 21:55 ` [LARTC] Per-connection routing for multiple uplinks/providers Arthur van Leeuwen
2002-04-16 6:01 ` Bob Gustafson
2002-04-16 6:56 ` Arthur van Leeuwen [this message]
2002-04-16 11:48 ` Patrick McHardy
2002-04-16 13:38 ` Mihai RUSU
2002-04-16 13:57 ` Patrick McHardy
2002-04-16 14:14 ` Mihai RUSU
2002-04-16 20:01 ` Bob Gustafson
2002-04-16 20:26 ` Don Cohen
2002-04-16 21:38 ` Bob Gustafson
2002-04-28 15:27 ` [LARTC] Per-connection routing for multiple uplinks/providers ?? mikee
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-101894033010404@msgid-missing \
--to=arthurvl@sci.kun.nl \
--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