All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: I need a clever solution for two Bittorrent machines behind a firewall
Date: Thu, 18 Nov 2004 12:43:09 -0500	[thread overview]
Message-ID: <20041118174309.GA16065@bender.817west.com> (raw)
In-Reply-To: <00c801c4cd90$8980f090$0400a8c0@bradmorgan>

On Thu, Nov 18, 2004 at 10:03:33AM -0700, Brad Morgan wrote:
> I'm using a Linux firewall with IPTables as my home firewall.  Both my son
> and I are gamers and my son actually has a couple of machines so he and his
> friends can game together.
> 
> Blizzard's new World of Warcraft uses a custom Bittorrent for their patches
> and it looks like both my son and I will be playing this one.  At the
> moment, I manually switch the target computer before going online (we only
> had one login during the open beta) but since you don't know until you login
> if there's a patch and we may buy two copies for simultaneous use, I'd like
> to figure out how a clever way to switch the target machine "on the fly" so
> we both take advantage of the increased download speed of a cooperating
> Bittorrent client.  I've experienced the speed difference because our first
> install didn't have any ports open and it was SLOW (over an hour).  The
> second install took maybe 10 minutes to download patches with the proper
> ports open and forwarded.
> 
> Anyone have any suggestions?  Pointers to solutions or other places to ask
> the question will be gladly accepted.

i suppose it depends on the flexibility of the bittorrent client.  the
one i use has the option to specify my "incoming TCP listen port."
so each machine behind the firewall just needs to specify a different
port, and you can forward accordingly.

i'm not familiar with the game your talking about or how it implements
its BT client.

-j

--
"The only monster here is the gambling monster that has enslaved your
 mother! I call him Gamblor, and it's time to snatch your mother from
 his neon claws!"
        --The Simpsons


  reply	other threads:[~2004-11-18 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 17:03 I need a clever solution for two Bittorrent machines behind a firewall Brad Morgan
2004-11-18 17:43 ` Jason Opperisano [this message]
2004-11-18 19:31 ` Kenneth Porter
2004-11-19  2:01   ` Jochen Radmacher

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=20041118174309.GA16065@bender.817west.com \
    --to=opie@817west.com \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.