From: Greg Stark <gsstark@mit.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Shaping incoming traffic on the other interface
Date: Fri, 11 Jun 2004 05:13:27 +0000 [thread overview]
Message-ID: <87d646u16w.fsf@stark.xeocode.com> (raw)
In-Reply-To: <87u0xjtma8.fsf@stark.xeocode.com>
Andreas Klauer <Andreas.Klauer@metamorpher.de> writes:
> I think there was a patch on the BT mailing list a few weeks ago
> that solves this random port problem (on your side). Other clients
> of course can choose whatever ports they like.
Why does bittorrent need to use more than one port in the first place?
Does SO_REUSEADDR not work properly on Windows?
--
greg
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-11 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 16:23 [LARTC] Re: Shaping incoming traffic on the other interface Greg Stark
2004-06-10 16:54 ` Matteo Brusa
2004-06-10 20:07 ` Greg Stark
2004-06-10 20:30 ` Jason Boxman
2004-06-10 20:33 ` Andreas Klauer
2004-06-11 5:13 ` Greg Stark [this message]
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=87d646u16w.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--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