[TelstraClear] Routing problem at t/clear makes GZ and other NZ sites dead.

Forums › Vodafone New Zealand (including Vodafone, WxC, Farmside) › [TelstraClear] Routing problem at t/clear makes GZ and other NZ sites dead.

sleemanj

1330 posts

Uber Geek

#25637 27-Aug-2008 18:33

Is anybody else seeing a routing problem making various NZ sites inacessible (including Geekzone, I'm on 3G at the moment to type this)? Hoon Hay in Christchurch. Tried ringing te help desk but estimated wait time was nearly an hour! Been like this since at least 1pm, probably earlier. The traces look like they try to leave NZ and get no further.

traceroute to www.stuff.co.nz (202.135.111.130), 30 hops max, 40 byte packets
1 192.168.10.1 (192.168.10.1) 1.044 ms 1.181 ms 1.330 ms
2 202-78-155-1.cable.telstraclear.net (202.78.155.1) 23.765 ms 25.392 ms 27.570 ms
3 ge-1-3-0-872-ie1-international.telstraclear.net (218.101.61.169) 25.961 ms 26.050 ms 26.161 ms
4 ae0-843.ie4.telstraclear.net (218.101.61.106) 36.083 ms 36.193 ms 36.284 ms

boffin@mortimer:~$ traceroute www.geekzone.co.nz
traceroute to www.geekzone.co.nz (210.48.73.74), 30 hops max, 40 byte packets
1 192.168.10.1 (192.168.10.1) 1.041 ms 1.183 ms 1.312 ms
2 202-78-155-1.cable.telstraclear.net (202.78.155.1) 11.356 ms 25.394 ms 25.505 ms
3 ge-1-3-0-872-ie1-international.telstraclear.net (218.101.61.169) 22.791 ms 25.789 ms 25.879 ms

---
James Sleeman
I sell lots of stuff for electronic enthusiasts...

sleemanj

1330 posts

Uber Geek

#160285 27-Aug-2008 21:44

I called the "help" desk, I shouldn't have bothered: http://www.geekzone.co.nz/sleemanj

---
James Sleeman
I sell lots of stuff for electronic enthusiasts...

freitasm

BDFL - Memuneh
67107 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

#160288 27-Aug-2008 21:48

This is probably the same problem reported here.

Tuikapo

170 posts

Master Geek

#160307 27-Aug-2008 23:26

freitasm: This is probably the same problem reported here.

Unlikely... The problem reported in the other post is an HTTP Redirect, which isn't likely to be a redirect, it seems like HTTP Proxy cache is dishing up the wrong page to I.P DNS Request, this problem seems to be a geniune route problem, but it would be hard to tell, as some routers do not allow forward of traceroutes. BGP routes go wrong all the time anyway, its when they don't find another one problems start to begin.

andgor

38 posts

Geek

#160408 28-Aug-2008 11:05

Yep. Me to :-).
Complained with their custhelp thingy yesterday morning and got a reply today saying that it had been "forwarded to our technical support team".

I had a bit of a play during the day after that and discovered that packets were getting to their destinations from my cable connection but not the other way around. Packets heading for my cable connection stopped at 218.101.61.189. (I updated the custhelp thingy with this information last night). So I had my VPN between home and work (which for some reason stayed up, even though traffic was only working in one direction) sending traffic from home direct to work, but the other way I routed via a server I have in Florida :-).

Anyway, seems to be working now. Will have to be nice to them and tell them that (now going to 218.101.61.173 instead of 218.101.61.189).

sleemanj

1330 posts

Uber Geek

#160418 28-Aug-2008 11:47

Yep. Me to :-).

Yea I guess it was just our subnet. Interestingly ICMP still not getting back to me, but obviously the trans proxy is ok..

traceroute to www.telstraclear.net.nz (202.78.133.58), 30 hops max, 40 byte packets
1 * * *
2 202-78-155-1.cable.telstraclear.net (202.78.155.1) 16.550 ms 20.493 ms 21.187 ms
3 ge-1-3-0-872-ie1-international.telstraclear.net (218.101.61.169) 31.226 ms 31.957 ms 34.801 ms
4 * * *
5 g9-927.u12.brh.telstraclear.net (218.101.61.4) 57.015 ms 43.230 ms 58.583 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *

---
James Sleeman
I sell lots of stuff for electronic enthusiasts...

Tuikapo

170 posts

Master Geek

#160507 28-Aug-2008 16:29

Mate there are likely to be firewalls there.... Thats the only reason you can't traceroute past that host.