D-Link Forums
The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Beta Code! => Topic started by: smapdi on March 29, 2009, 07:44:27 AM
-
When I start a torrent on one of my wired PCs, it suddenly becomes unable to send or receive any TCP data. Other computers connected to the router via wire or wireless are not affected.
I can ping out to the network and the internet but doing anything over TCP (web browsing, telnet, ssh, SMB network browsing) times out.
This only started happening after the 1.22B05 update so I am pretty certain it was caused by it. I checked the router logs but they do not show anything obviously wrong pertaining to the internal address of my pc.
When I release and renew the IP address from the PC, the issue goes away. Maybe something is funky with the DHCP daemon on the router? Any thoughts?
-
What are:
your bandwidth
BT client used
conf settings BT (max. useable bandwidth, no of up and down slots)
general rule: choke your upload and your download will choke too.
-
What are:
your bandwidth
BT client used
conf settings BT (max. useable bandwidth, no of up and down slots)
general rule: choke your upload and your download will choke too.
I have the Verizon FIOS 20/20 package which is currently showing in the QOS as:
Measured Uplink Speed : 20745 kbps
uTorrent is set to use max of 200Bps for upload.
I don't see how the client can be an issue as the only thing changed in the setup (which worked perfectly before) is the new firmware version.
-
I don't see how the client can be an issue as the only thing changed in the setup (which worked perfectly before) is the new firmware version.
Neither do I, but solving an issue is mainly a process of ruling out most of the possible causes. And info is required for that. And remember: it's a beta.
In fact, I don't have any issue with BT. So did you:
* Flash to 1.22b05 and reconfigured from scratch or did you load the saved config? If the latter, set all to factory defaults and reconfigure. Loading saved settings may cause erratic behaviour.
* How are your QoS settings?
-
Aside from the fact that you say nothing else changed but the firmware, your description of the problem REALLY sounds client based to me. What torrent client are you using?
-
The 1.22 beta causes one computer on my network (a Mac Mini) to have the same exact problem when trying to download a movie trailer in Front Row.
I have all the symptoms you describe on my one computer (all other computers on the network are fine).
Flashing back to 1.21 fixed the problem.
-
Still client based. Otherwise it should occur on all your other computers. Simple logic.
-
Still client based. Otherwise it should occur on all your other computers. Simple logic.
Um... No.
Firmware based. Otherwise, downgrading from 1.22 to 1.21 wouldn't fix the problem. Upgrading from 1.21 to 1.22 wouldn't cause the problem.
The client is the static part of the equation.
Why would the other computers have network issues if one computer, performing a certain task, has an issue?
Sorry, but I disagree with your assessment.
-
No, it is not.
Explain this: "all other computers on the network are fine" assuming it is the firmware ;D
-
Explain this: "all other computers on the network are fine" assuming it is the firmware ;D
None of the other computers on my network are trying to download a movie trailer from Apple using Front Row.
In the OP's example, the other computers aren't trying to download a file from bittorrent.
Given the evidence, the 1.22 firmware has an issue when a wireless-attached computer starts downloading a large file. Perhaps it's the hardware version (mine is A2) and it's relationship to 1.22. It could also be the fact that the computer is using 802.11n to download the large file. Maybe it's the network protocol involved when the download is performed.
The simple fact is that a problem arises after upgrading to 1.22. Downgrading to 1.21 makes the problem go away (and it's repeatable).
Although, I admit, without a specific known bug in the firmware, anything on the network could be causing the problem.
-
None of the other computers on my network are trying to download a movie trailer from Apple using Front Row.
In the OP's example, the other computers aren't trying to download a file from bittorrent.
Given the evidence, the 1.22 firmware has an issue when a wireless-attached computer starts downloading a large file. Perhaps it's the hardware version (mine is A2) and it's relationship to 1.22. It could also be the fact that the computer is using 802.11n to download the large file. Maybe it's the network protocol involved when the download is performed.
I have A2 too with 1.22, and no issues whatsoever with larges files. And I download a lot of 20 Gb files (BD). So Why don't I suffer from it?
The simple fact is that a problem arises after upgrading to 1.22. Downgrading to 1.21 makes the problem go away (and it's repeatable).
Although, I admit, without a specific known bug in the firmware, anything on the network could be causing the problem.
Your last remark does make sense. So it's quite premature to point at the firmware. If you find the source within your network that could give some clues to some setting in the firmware. Have you tried not reloading the saved config file and manually configure from scratch?
-
I tried again last night. With 1.21, I could download a movie trailer. I upgraded to 1.22 (I always do my settings from scratch) and movie trailers would kill the networking on that computer. I downgraded to 1.21 and could download movie trailers.
In a system with three components like this (computer -- router -- internet), debugging a problem should always start with "what changed". Did the computer get an update? Did the ISP have an outage? Did a DNS die?
In my situation, the router firmware was the only change. All router settings except WPA & the admin password are the same.
Why don't you have a problem downloading large files? Maybe you're using ftp & Front Row is using sftp. Maybe your computer is closer to the router. Maybe your network card isn't a broadcom based Airport Extreme.
There's definitely a connection between 1.22 and the problem. It's repeatable. It could be that 1.22 triggers a bug in that broadcom card. It could be that 1.22 doesn't like an 802.11n computer to be too far away when initiating a large download. I don't know the exact cause.
But, it would be interesting to know what changed between 1.21 and 1.22 to see if it could affect this. If they made no such changes, then I'd start attacking the Mini to see if it has a problem.
Since 1.21 works fine, though, I have no reason to go to 1.22... (but can't wait for 1.30!!!)
-
sorry I would have to agree with eddieZ.
1.22b05 H/W A2
No problems here downloading large files over wireless, from the internet or internally.
-
I reset the router to defaults and re-did all the settings but I still have the same issue.
Eddie, you asked about my QoS settings:
WAN Traffic Shaping
Enable Traffic Shaping: (checked)
Automatic Uplink Speed : (checked)
Measured Uplink Speed : 21420 kbps
Connection Type : Auto-detect
Detected xDSL or Other Frame Relay Network : Yes
QoS Engine Setup
Enable QoS Engine : (checked)
Automatic Classification : (checked)
Dynamic Fragmentation : (checked)
-
Could you also give me some insight on your client NIC and PC configs?
-
Could you also give me some insight on your client NIC and PC configs?
The wired client is a Windows Vista 64bit Ultimate SP1 machine with all the latest windows patches.
Standard Windows firewall is on. Only other software that could affect the card is NOD32 Antivirus v.3.0.672.0 .
I am using the onboard NIC, a Marvell Yukon 88E8056 PCI-E Gigabit Ethernet.
Any other info you need?
-
Driver version and driver settings. And all other network items installed on your PC...I have the same Marvell NIC and it works flawlessly with 1.22 b05
-
Driver version and driver settings. And all other network items installed on your PC...I have the same Marvell NIC and it works flawlessly with 1.22 b05
Driver version 10.51.1.9
Driver Settings:
Energy Star: Enabled
Flow Control: Tx&Rx Enabled
Interrupt Moderation: Enabled
IPv4 Checksum Offload: Rx Enabled
Jumbo Packet: 1514 Bytes
Large Send Offload (IPv4): Enabled
Max IRQ per Sec: 5000
Network Address: Not Present
Priority & VLAN: Priority & VLAN Enabled
Receive Buffers: 256
Speed & Duplex: Auto-Negotiation
TCP Checksum Offload (IPv4): Tx&Rx Enabled
Transmit Buffers: 256
UDP Checksum Offload (IPv4): Tx&Rx Enabled
-
have you used perfmon before? to monitor the network traffic on your interface and generate a report from it to see whats going on for example how much network bandwidth is being utilized and if packets are being dropped and what not?
-
Driver version 10.51.1.9
Driver Settings:
Energy Star: Enabled
Flow Control: Tx&Rx Enabled
Interrupt Moderation: Enabled
IPv4 Checksum Offload: Rx Enabled
Jumbo Packet: 1514 Bytes
Large Send Offload (IPv4): Enabled
Max IRQ per Sec: 5000
Network Address: Not Present
Priority & VLAN: Priority & VLAN Enabled
Receive Buffers: 256
Speed & Duplex: Auto-Negotiation
TCP Checksum Offload (IPv4): Tx&Rx Enabled
Transmit Buffers: 256
UDP Checksum Offload (IPv4): Tx&Rx Enabled
Try disabling Energy star and flowcontrol.
Does the PC have a energy saving mode which turns off all devices?
-
Try disabling Energy star and flowcontrol.
Does the PC have a energy saving mode which turns off all devices?
I made the changes and the issue is still there.
This is a desktop which has the power management stuff on always on.
-
Latest driver is out, by the way. Try that one. http://www.marvell.com
-
Latest driver is out, by the way. Try that one. http://www.marvell.com
I will give it a shot when I get home.
-
Hmm, upon trying 2 torrents it appears changing the driver changed something enough to make it work. Weird.
Let's hope this makes it permanent.
-
:O Maybe it's the MPAA installing a driver hook preventing you from torrenting!