how-to block ads
|
Sailor Enlil
join:2006-01-12
Philippines
4 edits | reply to d_l
Re: [Wired] Limited network capacity for some of Linksys Routers
I tried limiting the upload and download streams (in fact I put a cap on the uploads - 40kbps at first like it was with the BEFSR81, then after experiencing the problem tried lowering it to 20kbps for the BEFSR41 but no effect). Anyway back with the BEFSR81 even with Bitcomet handing heavy downloads (currently 2 downloads totalling 500kbps downstream, 40kbps upstream), no problems with other computers surfing the 'net (albiet slower than usual), though services like Youtube are problematic with the BEFSR81, with or without Bitcomet (Youtube has no problems with the BEFSR41 if Bitcomet is not running).
And as I mentioned earlier, this was not a problem with the older BEFSR41 (V3) I bought a few years back (my first router in fact).
EDIT: After further observation it's becoming obvious that the BEFSR41 has network capacity issues with Bitorrent steaming. I even cut the number of jobs in Bitcomet to just 1, and it still hogs the router's internet access (only local network access like shared folders and printers works), and the maximum total download rate is 100kbps and won't go any higher. I even tried the QoS feature (the BEFSR41 V4.2 had QoS capability), but no help at all.
The BEFSR81 on the other hand can handle Bitcomet well and still allow web surfing, and Bitcomet's total download rate can go as high as 500kbps without problems. The main issue I have with the BEFSR81 though is that after trying to sustain heavy downloads for a certain period of time the internet access goes down completely (like the BEFSR41, only local network access remains functional), requiring the BEFSR81 to be power cycled.
I'm beginning to wonder what's going on with these Linksys routers, and starting consider other brands (like D-Link).
EDIT2: I think I found out the real culprit here. I came across a forum containing tips for Bitorrent optimization, mentioning the TCP/IP Half-Open Connection issue (where Bitorrent of course needs more than the 10 allowed that Microsoft put in Windows XP SP2). Well one particular post claimed that today's routers now have their own limit on the number of TCP/IP Half-Open connections that can be opened to the Internet (50!?). So I set the number of connections on the PC running Bitcomet from 100 to 50, and bingo - the internet connection problem disappeared! Guess that explains it. In a matter of speaking, a post in a linked forum said it all:
quote:
If you have a Linksys BESR41 router...don't use BitTorrent. Or Gnutella as an ultrapeer. Apparently, the firmware on this, and other products that have this chip in common, crash and burn when a large (>16) number of connections per IP address behind NAT are established. In other words. A very busy Torrent will bork your router, and the only way to fix this is to reboot it.
And strangely, Bitcomet's total download rate also went up  (it's now doing 250kbps on its one job), running with the BEFSR41.
EDIT3: Ugh! The problem went back after I added a 2nd torrent job, and even worse, the first job's download rate went down. Going back to the BEFSR81 to see if having fewer TCP/IP Half-Open Connections will have any effect on that one.
EDIT4: Well, seems like the BEFSR81 is a bit "happier" now with the current settings. So now I have a BEFSR41 sitting around useless now. 
EDIT5: Finally resolved the problem after further testing of the BEFSR41 (after I had to retire th BEFSR81 when it was clear it was going 6 feet under - the internet disconnect on this one had nothing to do with heavy downloads, it was simply dropping dead on its own a few minutes after power cycling). I utilized the QoS feature of the BEFSR41 and added Bitcomet's Listen Port to the list of apps to enforce QoS, leaving everything else in the QoS settings default. Problem solved. | |
Sailor Enlil
join:2006-01-12
Philippines
1 edit | Well the joy didn't last, and the BEFSR41 V4 borked again with Bitcomet. Being fed up I did what a normally brand-loyal individual would do - go for a competing product. I acquired a D-Link router (DI-604 to be exact) and set it up in place of the Linksys. Results? BAM! The D-Link can handle Bitcomet's activities extremely well! No problems of being unable to surf the 'net despite heavy Torrent activity. Even better - the D-Link seems to have some really big fat pipes in its innards, being able to allow Bitcomet to sustain 500kbps+ downloads without any hiccups (and still permit other computers to surf the net like nothing else is going on).
So I guess it's goodbye Linksys | |
lexein
join:2003-04-25
San Francisco, CA
2 edits | said by Sailor Enlil  :...I acquired a D-Link router (DI-604 to be exact) and set it up in place of the Linksys. Results? BAM! The D-Link can handle Bitcomet's activities extremely well! ... Which version of DI-604 hardware & firmware? Tell us! Thanks...
[Edit] Why do I ask? From 2004-2007 I used a DI-604 for remote admin of 4 computers and a webcam. It was reliable only as long as I didn't use logging, emailing, DNS, or NTP, and stuck with only NAT and port-forwarding. But it took weeks learn these limitations, with frequent requests to the remote staff to power-cycle it. If the DI-604 has improved significantly, I'd be happy to know about it.
(Just noticed it's discontinued: In the US, only the rev. E hardware has any firmware updates, which ended in 2007.) | |
-
|
