| reply to funchords
Re: Comcast is using Sandvine to manage P2P Connections Psst. I was being just as humorous as Sturm was. But enough has been said. |
|
ajax25
join:2003-12-10
Colonia, NJ | reply to ajax25
said by ajax25:As of last night 9 downloaders at 90.7%. Nothing moving. I was able to connect to one of the seeders after stopping and restarting the torrent. Only 16K of data got through, but I was able to confirm that that seeder was on comcast. This baby is still hanging at around 95%. Still two
seeders, one I know is comcast.
There is also a second torrent hung in the upper 90%
range, have not been able to see the seeder for that one.
If the seeder does connect they get kicked very fast.
I'm in NJ if that makes any difference. |
|
abcstoreSee Store For DetailsPremium
join:2001-12-21
Richmond, VA
1 edit | reply to NormanS
said by NormanS:said by italiansmoke:I have my torrent upload speed set at 15kb/s. That should work for alleviating surfing issues. Having upload set to 28_k_bit on a 8/2Mbit pipe kills the whole thing almost completely. No ping, no DNS, no surfing.
ABC |
|
|
|
 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5
1 edit | said by abcstore:Having upload set to 28_k_bit on a 8/2Mbit pipe kills the whole thing almost completely. No ping, no DNS, no surfing. Are you working through a router? If so, try disabling DHT in your P2P client and close it. Reset your router (power off and on), wait for a few moments, then restart your bittorrent client.
If that helps, your router cannot handle the high number of connections that DHT creates. Turning DHT off shouldn't affect you badly, as DHT's main purpose is to function as a backup tracker.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
More features, more fun, Join BroadbandReports.com, it's free...
|
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
1 edit | reply to abcstore
said by abcstore:Having upload set to 28_k_bit on a 8/2Mbit pipe kills the whole thing almost completely. No ping, no DNS, no surfing. I've only got 3/0.5 Mb/s, but letting the upload run at 39 kB/s (yes, that's Bytes!) does not hurt DNS, or surfing. Ping only suffers slightly. The worst effect is on streaming video (gets very choppy).
It helps that the router (D-Link DIR-655) does QoS, and the DSL modem (SpeedStream 4100) performs ACK packet prioritization.
P.S. I normally run the upload throttled back to 29 kB/s.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
abcstoreSee Store For DetailsPremium
join:2001-12-21
Richmond, VA | reply to funchords
My router is a FreeBSD handling multiple T1s and MPLS lines. 6/2Mbit cable line is a tiny fraction of what's going on.
At times you can seed and browse but 99% of the time seeding kills everything (through cable).
ABC
--
This signature is NOT for sale! |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5
1 edit | Do your packets go through Warrenton? (can you check via traceroute?)
If so, it is very, very important that you report this to Comcast tech support and let them know that you are in their Network Management test market. Please let me know.
See »www.comcast.net/terms/network/ for (sketchy) details.
Test market or no, your results are pretty surprising. So is it any amount of seeding that kills everything? Can you turn it down to 5 KB/s (40 kbps) or 1 KB/s (8 kbps) and still be prevented?
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
More features, more fun, Join BroadbandReports.com, it's free...
|
|
abcstoreSee Store For DetailsPremium
join:2001-12-21
Richmond, VA | reply to funchords
said by funchords:Do your packets go through Warrenton? (can you check via traceroute?) If so, it is very, very important that you report this to Comcast tech support and let them know that you are in their Network Management test market. Please let me know. See » www.comcast.net/terms/network/ for (sketchy) details. Test market or no, your results are pretty surprising. So is it any amount of seeding that kills everything? Can you turn it down to 5 KB/s (40 kbps) or 1 KB/s (8 kbps) and still be prevented?
3 6 ms 6 ms 6 ms ge-3-1-ur01.chesterfield.va.richmond.comcast.net [68.86.17 4.185]
4 4 ms 6 ms 6 ms te-1-2-ar01.chesterfield.va.richmond.comcast.net [68.86.17 2.70]
5 13 ms 12 ms 13 ms te-4-3-cr01.charlotte.nc.cbone.comcast.net [68.86.72.133]
6 19 ms 15 ms 17 ms te-1-1-cr01.richmond.va.cbone.comcast.net [68.86.68.110]
7 15 ms 17 ms 16 ms te-1-1-cr01.mclean.va.cbone.comcast.net [68.86.68.114]
8 18 ms 20 ms 20 ms te-4-2-ar01.newcastle.de.bo.comcast.net [68.86.72.162]
9 21 ms 23 ms 21 ms te-1-1-ar02.ndceast.pa.bo.comcast.net [68.86.228.102]
10 22 ms 21 ms 20 ms te-4-1-ur02.ndceast.pa.bo.comcast.net [68.86.134.49]
11 21 ms 21 ms 21 ms 68.87.98.12
12 20 ms 21 ms 19 ms 68.87.60.144
Seeding at 5Kb/s I can't even reply to this thread... Neither could I open the link you provided.
ABC
P.S. Boy, am I glad FIOS finally got to my house! 15Mbit and no throttling
--
This signature is NOT for sale! |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5
1 edit | You are about 100 miles from Warrenton ... hmmm, no explanation.
I'm wondering if something in the FreeBSD setup might be squelching you -- maybe a MPLS rule or a NAT table limitation working against you? Can you plug directly into the cable modem and test?
What Comcast is doing in most areas (the non-trial areas) should have no effect on DNS or web surfing. It would kill seeding, however, by throwing TCP RST packets at your connections. |
|
