D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Mr. T on December 06, 2008, 08:26:01 AM
-
Hello,
I have 100mbit internet connection
When i run Utorrent, after +- 10 minutes my internet disconnects.
-i've forwarded the ports properly
-configurerd the QoS (set torrent as lowest priority)
-Hardware version: A3, Firmware version: 1.20EU (upgraded from 1.11EU)
Setup:
modem----Cat5e---Router---Cat5e---PC
When internet stops working, i can still connect to the router, LAN still works fine, but no WAN response.
I then need to unplug the router's adaptor to regain WAN connection.
Browsing etcetera works fine, but when im highly loading the Internet connection it jams.
Is there any solution to this issue?
This is what i found in "Logs"
Priority Time Message
[INFO] Sat Dec 06 14:34:35 2008 Blocked incoming TCP connection request from 88.168.249.211:13540 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:35 2008 Blocked incoming TCP connection request from 190.135.59.206:36898 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:33 2008 Blocked incoming TCP connection request from 151.68.180.181:42640 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:33 2008 Blocked incoming TCP connection request from 217.86.157.137:64039 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:30 2008 Above message repeated 2 times
[INFO] Sat Dec 06 14:34:29 2008 Blocked incoming UDP packet from 212.147.99.135:19925 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:29 2008 Blocked incoming TCP connection request from 88.168.249.211:13540 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:29 2008 Blocked incoming TCP connection request from 217.86.157.137:64039 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:29 2008 Blocked incoming TCP connection request from 190.135.59.206:36898 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:28 2008 Blocked incoming TCP connection request from 99.224.57.43:54543 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:28 2008 Blocked incoming TCP connection request from 217.86.157.137:64039 to 88.159.97.255:24286
[INFO] Sat Dec 06 14:34:27 2008 Blocked incoming TCP packet from 76.247.165.107:2846 to 88.159.97.255:6880 as RST:ACK received but there is no active connection
This is what i found in "statistics":
LAN Statistics
Sent : 9302
TX Packets Dropped : 2
Collisions : 0
Received : 131
RX Packets Dropped : 0
Errors : 0
WAN Statistics
Sent : 12221
TX Packets Dropped : 0
Collisions : 0
Received : 24151
RX Packets Dropped : 0
Errors : 0
Wireless Statistics
Sent : 18784
TX Packets Dropped : 0
Received : 14175
RX Packets Dropped : 0
Errors : 432
Specs PC:
-amd athlon xp2500
-latest Utorrent version
-no active firewall/AV
-WinXP pro
-
Limit the number of BT connections coming in. uTorrent configues the maximum depending on your bandwidth automatically. Don't know how you configured the thing.
QoS does not limit this, it only prioritizes. Iin order to throttle BT you need to configure uTorrent (max. bandwidth, number of connecetions out and in etc) .
-
I tried configuring my torrent-settings according to this website: http://forum.utorrent.com/viewtopic.php?id=34259
According to my ISP i have 100mbit up/down (its Fibre). i tried a lot of different settings.
Maybe somebody could indicate what settings generally wouldnt cause any "router hang ups"?
-
Here's my settings that work fine:
(http://img244.imageshack.us/img244/4580/utorrentzf5.th.jpg) (http://img244.imageshack.us/my.php?image=utorrentzf5.jpg)
-
I've tried these settings (even more restrictive with DHT turned off: http://forum.utorrent.com/viewtopic.php?id=34259) and followed the guides on Utorrent ex:
http://www.utorrent.com/documentation/connection-setup
This can work fine for awhile and then it just dies. Only happens to me when I'm using bittorrent.
-
Here's my settings that work fine:
(http://img244.imageshack.us/img244/4580/utorrentzf5.th.jpg) (http://img244.imageshack.us/my.php?image=utorrentzf5.jpg)
Yeah.. Lets all limit our upload to something like that and we definitely have no worry to choke our routers..
:o
-
Yeah.. Lets all limit our upload to something like that and we definitely have no worry to choke our routers..
:o
Got a problem with that? ???
-
I've tried these settings (even more restrictive with DHT turned off: http://forum.utorrent.com/viewtopic.php?id=34259) and followed the guides on Utorrent ex:
http://www.utorrent.com/documentation/connection-setup
This can work fine for awhile and then it just dies. Only happens to me when I'm using bittorrent.
You might want to chech if your internet gateway device (modem) can handle enough connections.
-
You may want to take this to a bittorrent forum.
-
You may want to take this to a bittorrent forum.
That is supposed to be my line...I'm the arrogant SOB on the board.. ;)
-
It will not be your modem hanging up, as the log you posted shows blocked incoming connections. It would show nothing if it was your modem.
It seems all blocked connections have the same port destination. It's possible your machine blocks connections, causing everything to come to a grinding halt.
If you use windows, it's limited to a certain concurrent number of connection attempts per 10 seconds. Once you reach that TCP/IP limit, windows will not allow any more until some time has passed. This is a feature that has been implemented since XP SP2.
-
The blocked addresses are caused by the (deafult/strict) firewall setting of the 655. So IMHO these have nothing to so with the issue described.
-
Got a problem with that? ???
Not really. It was a joke like if i want to dl something fast and have small number of connections + every 1 has ul limit like that, then i definetly have slow dl speed and have to make more connections and choke my router again because of "you"... ;D
You may want to take this to a bittorrent forum.
Isn't this router thing, not torrent problem anyways. How can they know in some torrent forum how many connections etc THIS piece of harware can do or not?
-
Hmm, good point. But they are blocked connection attempts. It's always possible the default behavior is to block attempts if the destination port can not be reached by the firewall.
-
The firewall is set by default to strict (TCP Port And Address Restricted, UDP Address Restricted ). Explains all the blocking.
-
it's no more a router limitation (not problem), or modem limitation than it is your configuration of your torrent client. The router can handle about 200 concurrent connections if I remember correctly.
-
it's no more a router limitation (not problem), or modem limitation than it is your configuration of your torrent client. The router can handle about 200 concurrent connections if I remember correctly.
200 is the max AFAIK