VeZoZ
02-11-2002, 07:08 PM
I tried to get a problem fixed with connecting to any sites in their datacenter when using sympatico.ca as my isp. Considering sympatico.ca is a rather large canadian isp I thought they might fix this but they havn't in over a week now and I've talked to 3 techs in total now through icq which is my only means to contact them other then phone now.
I sent a tech an icq with the trace route information I had
Target Name: rackshack.net
IP: 207.218.223.136
Date/Time: 2/11/2002 5:57:52 PM
1 150 ms 251 ms Guelph-ppp3515084.sympatico.ca [206.172.238.241]
2 160 ms 221 ms Guelph-ppp201775.sympatico.ca [64.228.7.250]
3 180 ms 201 ms core2-toronto63-atm8-2-39.in.bellnexxia.net [206.108.104.197]
4 190 ms 191 ms core3-toronto63-pos6-0.in.bellnexxia.net [64.230.242.101]
5 240 ms 261 ms core2-seattle-pos6-0.in.bellnexxia.net [206.108.102.206]
6 250 ms 251 ms bx1-seattle-pos3-0-0.in.bellnexxia.net [206.108.102.174]
7 240 ms 261 ms [64.132.69.5]
8 260 ms 270 ms core-01-ge-1-1-0.sttl.twtelecom.net [168.215.54.113]
9 250 ms 280 ms core-01-so-0-0-0.ptld.twtelecom.net [168.215.53.198]
10 261 ms 310 ms core-01-so-0-0-0.bois.twtelecom.net [168.215.53.202]
11 271 ms 300 ms core-02-ge-2-3-0.bois.twtelecom.net [168.215.55.54]
12 301 ms 310 ms core-01-so-0-0-0.slcy.twtelecom.net [168.215.55.50]
13 311 ms 320 ms core-01-so-1-0-0.dnvr.twtelecom.net [168.215.55.213]
14 331 ms 340 ms core-02-so-2-3-0.dlfw.twtelecom.net [168.215.53.69]
15 321 ms 330 ms dist-01-so-0-0-0.hsto.twtelecom.net [168.215.53.62]
16 331 ms 360 ms [66.162.210.250]
17 * * [-]
They did a return trace route and they had the same problem
Tracing route to Guelph-ppp3515084.sympatico.ca [206.172.238.241]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms ev1hou-2600-1.ev1.net [207.218.193.1]
2 23 ms 11 ms 26 ms tayhou-223-13.ev1.net [207.218.223.13]
3 72 ms 18 ms 18 ms tayhou-223-1.ev1.net [207.218.223.1]
4 7 ms 6 ms 8 ms p1-1-0-0.a03.hstntx01.us.ra.verio.net [128.241.9
.245]
5 * * * Request timed out
Now I they told me that
unfortunately Verio is outside of our network and therefore our control
and replied with
well so it's going to be down forever?
This was their solution
if you know how to poison the route through verio's network you could give that a try
Ever since the attack I've had this problem and rackshack I guess seems to think it's fine for some isp's not to be able to view anything in their datacenter.
I thought maybe taking it here which actually works may get rackshack to do something about this.
I sent a tech an icq with the trace route information I had
Target Name: rackshack.net
IP: 207.218.223.136
Date/Time: 2/11/2002 5:57:52 PM
1 150 ms 251 ms Guelph-ppp3515084.sympatico.ca [206.172.238.241]
2 160 ms 221 ms Guelph-ppp201775.sympatico.ca [64.228.7.250]
3 180 ms 201 ms core2-toronto63-atm8-2-39.in.bellnexxia.net [206.108.104.197]
4 190 ms 191 ms core3-toronto63-pos6-0.in.bellnexxia.net [64.230.242.101]
5 240 ms 261 ms core2-seattle-pos6-0.in.bellnexxia.net [206.108.102.206]
6 250 ms 251 ms bx1-seattle-pos3-0-0.in.bellnexxia.net [206.108.102.174]
7 240 ms 261 ms [64.132.69.5]
8 260 ms 270 ms core-01-ge-1-1-0.sttl.twtelecom.net [168.215.54.113]
9 250 ms 280 ms core-01-so-0-0-0.ptld.twtelecom.net [168.215.53.198]
10 261 ms 310 ms core-01-so-0-0-0.bois.twtelecom.net [168.215.53.202]
11 271 ms 300 ms core-02-ge-2-3-0.bois.twtelecom.net [168.215.55.54]
12 301 ms 310 ms core-01-so-0-0-0.slcy.twtelecom.net [168.215.55.50]
13 311 ms 320 ms core-01-so-1-0-0.dnvr.twtelecom.net [168.215.55.213]
14 331 ms 340 ms core-02-so-2-3-0.dlfw.twtelecom.net [168.215.53.69]
15 321 ms 330 ms dist-01-so-0-0-0.hsto.twtelecom.net [168.215.53.62]
16 331 ms 360 ms [66.162.210.250]
17 * * [-]
They did a return trace route and they had the same problem
Tracing route to Guelph-ppp3515084.sympatico.ca [206.172.238.241]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms ev1hou-2600-1.ev1.net [207.218.193.1]
2 23 ms 11 ms 26 ms tayhou-223-13.ev1.net [207.218.223.13]
3 72 ms 18 ms 18 ms tayhou-223-1.ev1.net [207.218.223.1]
4 7 ms 6 ms 8 ms p1-1-0-0.a03.hstntx01.us.ra.verio.net [128.241.9
.245]
5 * * * Request timed out
Now I they told me that
unfortunately Verio is outside of our network and therefore our control
and replied with
well so it's going to be down forever?
This was their solution
if you know how to poison the route through verio's network you could give that a try
Ever since the attack I've had this problem and rackshack I guess seems to think it's fine for some isp's not to be able to view anything in their datacenter.
I thought maybe taking it here which actually works may get rackshack to do something about this.
