On Jan 14, 2008 5:00 PM, Max Hayden Chiz <[EMAIL PROTECTED]> wrote: > cause the latency issue. By contrast if I limit the number of > connections, BitTorrent can consume almost all of the bandwidth and > the issue will not appear. > > Perhaps this problem is specific to my configuration (or specific to > DOCSIS cable modems). But if it makes Brian (or someone else's > problem) go away, then it is likely that this problem is not unique.
i doubt it's your machine not being happy with number of connections - i routinely have hundreds of states. depends on your modem, maybe? or who made the board inside your modems? or what crack-addled rhesus monkey pretended to write the firmware. If several different manufacturers licensed the IP stack or NAT engine from the same vendor, then it's perfectly possible that you both have ill-designed hardware. if you have a shell host somewhere, you could use netcat to determine where your router falls over. use netcat to send /dev/zero over the wire, with just a single stream, that should be pretty fast. then start opening up more tcp connections (but don't send anything through them) until it starts to bog down. That should give you enough information to create several different rule classes to limit number of connections by port. Web,ssh, dns and chat get to open connections first, and can always open one more connection, all other ports get to share ... 80% of max connections? -- GDB has a 'break' feature; why doesn't it have 'fix' too?
