From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to balance OUTBOUND traffic by packet if..
Date: Tue, 11 Jan 2005 02:31:57 +0000 [thread overview]
Message-ID: <41E33A9D.99998441@iswest.com> (raw)
In-Reply-To: <1383.192.168.1.2.1105108845@maild.mine.nu>
junk@maild.mine.nu wrote:
>
> I am still looking for a solution to this problem.......
> > junk@maild.mine.nu wrote:
I realize this is the opposite of what you try to accomplish, but
perhaps it will help?
Google
"LARTC load balance a file download across two connections - success"
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-01-11 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 14:40 [LARTC] How to balance OUTBOUND traffic by packet if junk
2005-01-08 12:02 ` Andy Furniss
2005-01-11 0:28 ` junk
2005-01-11 2:31 ` gypsy [this message]
2005-01-11 10:02 ` junk
2005-01-12 11:10 ` Andy Furniss
2005-01-12 11:36 ` Andy Furniss
2005-01-13 3:21 ` Andy Furniss
2005-01-13 12:27 ` Andy Furniss
2005-01-14 2:08 ` Patrick McHardy
2005-01-14 15:10 ` Andy Furniss
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=41E33A9D.99998441@iswest.com \
--to=gypsy@iswest.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