[ previous ] [ next ] [ threads ]
 From:  Michael David Joy <mdjoy at phy dot olemiss dot edu>
 To:  Morgan Foote <mfoote at currentindustries dot com>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] Bug in beta 1.2b1
 Date:  Mon, 27 Sep 2004 11:07:23 -0500
This sounds like a number of connections issue as Bittorrent has the
tendency to create LOTS AND LOTS of simultaneous connections. I've
noticed that Torrents in general can take down most low powered routers
with ease (the ~50-100 Mhz linksys,dlink,netgear variety).

You might try increasing the amount of ram on the box so it doesn't come
to a screeching halt as the # of torrent connections increase. Memory is
cheap, and would be a quick fix until a more optimal solution is found.

You also might try using Azureus and limiting the # of simultaneous
connections and see what happens. Just for an example, a large torrent
of Mandrake once had 1200 simultaneous connections for one client. The
total throughput was well over 2300 kB/s (yes bytes), and it actually
crashed an old FORE Systems ATM Switch in the building.

On Mon, 2004-09-27 at 10:44, Morgan Foote wrote:
> Hello All,
> I hope this message gets sent to the right list. On long file transfers
> especially with BT my monowall (hd/cf image on a dell optiplex 100
> Celeron 500 with 64mb of ram, onboard video, onboard 3com xl series, and
> a Intel fxp card) the machine will be come unreachable (via ping and the
> webgui) and will stop passing traffic after about 15 minutes.  I get no
> response on the console as well, requiring a hard boot.  When not doing
> big transfers it works all day.  
> M. Morgan Foote
> Network Administrator
> Current Industries
> mfoote at currentindustries dot com
> 360-734-5353