From: Mark on
On Mon, Jun 21, 2010 at 9:03 PM, Stan Hoeppner <stan(a)hardwarefreak.com>wrote:

>
> Thus, with the same router, I could take a few different *nix OS flavors
> and
> perl versions, blowing up the router with some, and not denting it with
> others.
>
> It's all about the packet load you push through the router. It's
> absolutely
> normal for setups that "seem" the same to nuke the router, because once you
> peek under the hood, they aren't really behaving the same at all.
>
> Take a peek under the hood. :)
>

Interesting, so is the router to blame or the OS? Because you're fixing the
problem by the OS, not changing the router. Short of people buying beefy
commercial grade routers for home usage torrent downloading, what's the
solution?
From: Mark Allums on
On 6/21/2010 11:03 PM, Stan Hoeppner wrote:
> Thus, with the same router, I could take a few different *nix OS flavors and
> perl versions, blowing up the router with some, and not denting it with others.
>
> It's all about the packet load you push through the router. It's absolutely
> normal for setups that "seem" the same to nuke the router, because once you
> peek under the hood, they aren't really behaving the same at all.
>
> Take a peek under the hood. :)

+1

This "exercise" has proven (as if there were any doubt) that not all
equipment is created equal, nor operating systems, for that matter.

To further illustrate, my internet connection is a "tethered" Blackberry
phone. It loses it's mind frequently (about once a day), and has to be
reset by pulling the battery.

It wasn't intended to be used heavily for this purpose.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C205A4C.7070305(a)allums.com