cdr1000
join:2004-02-18
10100
 ·RCN CABLE
| [Connectivity] Routing
8/21/08 4 PM
Newshosting trace
Bottleneck at port 119, 23, 80, 3128, 8000
tge2-1.core1.nyw.ny.rcn.net (207.172.15.82)
====================================================
Out BGP (port 119, 23, 80, 3128, etc)
2 69.16.186.81 (69.16.186.81) 9.302 ms 9.254 ms 9.965 ms
3 unknown.hwng.net (69.16.190.121) 9.951 ms 9.548 ms 9.971 ms
4 border1.eqnx.va.rcn.net (206.223.115.25) 9.963 ms 9.947 ms 9.971 ms
5 tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 9.958 ms 9.731 ms 9.971 ms
6 ge9-3-0.core2.lnh.md.rcn.net (207.172.19.189) 9.964 ms 9.123 ms 9.973 ms
7 pos6-0.core1.phdl.pa.rcn.net (207.172.19.8) 9.961 ms 10.006 ms 9.973 ms
8 pos6-0.core2.nyw.ny.rcn.net (207.172.19.7) 9.869 ms 9.250 ms 9.966 ms
9 tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 193.258 ms 192.591 ms 203.966 ms
10 tge1-1.aggr1.nyw.ny.rcn.net (207.172.19.101) 9.565 ms 9.199 ms 9.973 ms
11 ge3-0-0.wsd-ubr1.qens-wsd.ny.cable.rcn.net (208.59.246.116) 9.962 ms 9.719 ms 9.970 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Out SC (port 7000)
2 69.16.186.81 (69.16.186.81) 9.633 ms 9.777 ms 9.967 ms
3 tge7-4.ar2.iad1.us.scnet.net (216.246.102.185) 9.954 ms 9.672 ms 9.972 ms
4 58.xe-2-1-0.cr1.iad1.us.scnet.net (64.202.119.17) 9.960 ms 9.473 ms 9.971 ms
5 as4436.112.xe-1-2-0.cr1.iad1.us.scnet.net (216.246.36.201) 9.962 ms 9.985 ms 9.968 ms
6 po2.ar1.iad1.us.nlayer.net (69.31.31.146) 9.978 ms 9.631 ms 9.959 ms
7 border1.eqnx.va.rcn.net (206.223.115.25) 9.954 ms 9.330 ms 9.971 ms
8 tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 9.962 ms 9.470 ms 9.971 ms
9 ge9-3-0.core2.lnh.md.rcn.net (207.172.19.189) 9.962 ms 9.483 ms 9.977 ms
10 pos6-0.core1.phdl.pa.rcn.net (207.172.19.8) 9.957 ms 9.125 ms 9.971 ms
11 pos6-0.core2.nyw.ny.rcn.net (207.172.19.7) 9.964 ms 9.264 ms 9.971 ms
12 tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 9.964 ms 9.402 ms 9.972 ms
13 tge1-1.aggr1.nyw.ny.rcn.net (207.172.19.101) 9.969 ms 9.043 ms 9.971 ms
14 ge3-0-0.wsd-ubr1.qens-wsd.ny.cable.rcn.net (208.59.246.116) 9.963 ms 9.555 ms 9.971 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Out Cogent (port 8000)
2 69.16.186.81 (69.16.186.81) 9.643 ms 9.838 ms 9.951 ms
3 * gi7-3.mpd01.iad01.atlas.cogentco.com (38.112.21.237) 0.376 ms 9.753 ms
4 ge7-4.border1.eqnx.va.rcn.net (207.172.9.25) 9.946 ms 9.177 ms 9.974 ms
5 tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 9.959 ms 9.321 ms 9.971 ms
6 ge9-3-0.core2.lnh.md.rcn.net (207.172.19.189) 9.964 ms 9.333 ms 9.973 ms
7 pos6-0.core1.phdl.pa.rcn.net (207.172.19.8) 9.961 ms 9.476 ms 9.970 ms
8 pos6-0.core2.nyw.ny.rcn.net (207.172.19.7) 9.964 ms 9.362 ms 9.973 ms
9 tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 107.862 ms 198.464 ms 199.740 ms
10 tge1-1.aggr1.nyw.ny.rcn.net (207.172.19.101) 9.560 ms 9.230 ms 9.969 ms
11 ge3-0-0.wsd-ubr1.qens-wsd.ny.cable.rcn.net (208.59.246.116) 9.959 ms 9.986 ms 9.958 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Out BtN (port 9000)
2 69.16.186.81 (69.16.186.81) 9.728 ms 9.941 ms 9.972 ms
3 unknown.hwng.net (69.16.190.29) 9.946 ms 9.974 ms 9.970 ms
4 2-3.r1.dc.hwng.net (69.16.190.25) 9.966 ms 9.923 ms 9.971 ms
5 border1.eqnx.va.rcn.net (206.223.115.25) 9.960 ms 9.822 ms 9.967 ms
6 tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 9.965 ms 9.329 ms 9.970 ms
7 ge9-3-0.core2.lnh.md.rcn.net (207.172.19.189) 15.331 ms 199.468 ms 200.093 ms
8 pos6-0.core1.phdl.pa.rcn.net (207.172.19.8) 9.407 ms 9.177 ms 9.891 ms
9 pos6-0.core2.nyw.ny.rcn.net (207.172.19.7) 9.914 ms 9.549 ms 9.971 ms
10 tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 9.963 ms 9.316 ms 9.970 ms
11 tge1-1.aggr1.nyw.ny.rcn.net (207.172.19.101) 9.961 ms 9.213 ms 9.968 ms
12 ge3-0-0.wsd-ubr1.qens-wsd.ny.cable.rcn.net (208.59.246.116) 9.971 ms 9.106 ms 9.951 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
»md.speedtest.rcn.net/
= 18.02 Mbps [Megabit-per-second]
»pa.speedtest.rcn.net/
= 18.63 Mbps [Megabit-per-second]
»ny.speedtest.rcn.net/
= 19.08 Mbps [Megabit-per-second]
»ma.speedtest.rcn.net/
= 18.42 Mbps [Megabit-per-second]
»il.speedtest.rcn.net/
= 10.46 Mbps [Megabit-per-second]
Foward Signal to Noise 33.4 dB
Forward Power Level 6.2 dBmV
Modem TX Power 42.2 dBmV |
|
jmirabella
Joe Mirabella
Premium,VIP
join:2003-10-20
Lanham, MD
clubs: | looks like your router isnt responding to pings.. |
|
cdr1000
join:2004-02-18
10100
·RCN CABLE
1 edit | I did not touch my router settings for a long time.
Here is the info: Broadband Router Gigafast EE400-R
Access Control
Response to Ping from WAN Deny
Web Management from WAN Deny
My speed is the same speed without the router.
RCN is still the best I can get.™
Thank you in advance for you help |
|
kentonet
Premium
join:2002-05-29
Northampton, PA | reply to jmirabella
Could it also be a filter on the cable modem? I believe RCN sends out DOCSIS configs with ICMP filters after certain conditions are met, presumably for P2P protection or something. |
|
cdr1000
join:2004-02-18
10100
·RCN CABLE
| RCN does not filter P2P.
Number of threads may be limited, but not the speed.
More like a temporary routing problem at
tge2-1.core1.nyw.ny.rcn.net (207.172.15.82)
=========================================================
"Following is a traceroute between NewsHosting.com and your current location. Note the times between the hops. You should see a small, consistent increase, but not anything higher than 300 milliseconds."
Out BGP (port 119, 23, 80, 3128, etc)
2 69.16.186.81 (69.16.186.81) 9.770 ms 9.090 ms 9.968 ms
3 unknown.hwng.net (69.16.190.121) 9.952 ms 9.666 ms 9.973 ms
4 border1.eqnx.va.rcn.net (206.223.115.25) 9.962 ms 9.700 ms 9.972 ms
5 tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 9.963 ms 9.961 ms 9.973 ms
6 ge9-3-0.core2.lnh.md.rcn.net (207.172.19.189) 9.963 ms 9.978 ms 9.970 ms
7 pos6-0.core1.phdl.pa.rcn.net (207.172.19.8) 9.963 ms 9.243 ms 9.972 ms
8 pos6-0.core2.nyw.ny.rcn.net (207.172.19.7) 9.950 ms 9.765 ms 9.970 ms
9 tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 148.307 ms 303.148 ms 219.955 ms
10 tge1-1.aggr1.nyw.ny.rcn.net (207.172.19.101) 9.843 ms 9.353 ms 9.971 ms
11 ge3-0-0.wsd-ubr1.qens-wsd.ny.cable.rcn.net (208.59.246.116) 9.962 ms 9.499 ms 9.972 ms
===========================================================
Changing ports from 119, 23, 80, 3128 to 7000, 8000, 9000 did not help. |
|
kentonet
Premium
join:2002-05-29
Northampton, PA
| Of course they don't outright filter P2P. I didn't claim that.
What they will (or at least used to) do, though, is have your modem filter ICMP (both directions) after a certain threshold is broken. This can happen, for instance, after completing (and shutting down) a BitTorrent seeding session on a DMZ, or with punched ports or UPnP clients, where remote users are still attempting to connect to your BitTorrent client. Your computer would then send an ICMP control packet back, which drops a token in the bucket on some RCN monitoring server. If the torrent is busy enough (such as a Linux distribution install-CD torrent), those tokens would fill the bucket up fairly quickly and RCN (automatically) would presumably fling a new DOCSIS config to the modem with the ICMP filter active.
I've actually watched this happen on my SurfBoard modem while I was running a primitive UPnP server on my Linux router, when clients didn't clean up their UPnP port assignments properly. |
|
cdr1000
join:2004-02-18
10100
·RCN CABLE
| I think that they do not change DOCSIS config often.
They match your modem MAC with config, which caps the modem.
Most likely they go by your IP address if they want to filter.
To fix torrent crashes, you can try:
Motorola Surfboard SB5100 FLASHED WITH SIGMA-X2 BUILD 142.
Still no answer why on ports 119, 23, 80, 3128
pings to newshosting are not good as it use to be:
tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 142.786 ms 9.983 ms 203.789 ms
tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 76.854 ms 198.335 ms 199.824 ms
port 8000
tge1-3.core4.lnh.md.rcn.net (207.172.19.204) 105.052 ms 9.105 ms 209.558 ms
tge2-1.core1.nyw.ny.rcn.net (207.172.15.82) 136.294 ms 208.824 ms 208.315 ms
port 9000
tge1-1.aggr1.nyw.ny.rcn.net (207.172.19.101) 32.823 ms 208.337 ms 216.434 ms
I wonder how can we communicate with RCN technical support? |
|
jmirabella
Joe Mirabella
Premium,VIP
join:2003-10-20
Lanham, MD
clubs: | there really is no problem here, high pings to one device is most probably just ratelimited ICMP responses from the core network.. the ping times to the destination is fine. |
|
cdr1000
join:2004-02-18
10100 | My download speed off newshosting is below 18 mbps for about three weeks.
As usual, first I tried all ports, disconnected my router, my switch, used different machines, NIC, etc.
RCN speed test shows close 20 mbps. |
|
cdr1000
join:2004-02-18
10100 | reply to cdr1000
Still no changes.
16-17 mbps with some spikes up to 18 mbps.
Is it related to "analag crash"?
Taking some bandwidth for HD? |
|
