Forum Home
Press F1
Thread ID: 84559	2007-11-10 03:38:00	Odd traceroute, can someone please shed some light on it?	rixth (9629)	Press F1

Post ID	Timestamp	Content	User
610006	2007-11-10 03:38:00	I can get to ascent.co.nz but the traceroute is certainly weird! Do you get the same/similar? C:\Users\Tom>ping ascent.co.nz Pinging ascent.co.nz [203.128.225.5] with 32 bytes of data: Reply from 10.255.1.2: TTL expired in transit. Reply from 10.255.1.2: TTL expired in transit. Reply from 10.255.1.2: TTL expired in transit. Reply from 10.255.1.2: TTL expired in transit. C:\Users\Tom>tracert ascent.co.nz Tracing route to ascent.co.nz [203.128.225.5] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms wrt54gl [192.168.0.59] 2 * * * Request timed out. 3 68 ms 80 ms 78 ms lo1.akl-grafton-bras1.ihug.net [203.109.128.90] 4 68 ms 65 ms 67 ms 38.129.109.203.ip.ihug.net [203.109.129.38] 5 * * * Request timed out. 6 1383 ms 64 ms 74 ms g1-0-1642.u12.telstraclear.net [203.98.18.161] 7 71 ms 67 ms 67 ms g1-0-1642.u12.telstraclear.net [203.98.18.161] 8 68 ms 70 ms 70 ms g1-926.u11.pnr.telstraclear.net [218.101.61.33] 9 66 ms 68 ms 69 ms jcore2-ge-0-2-0-927-acld.auckland.clix.net.nz [218.101.61.14] 10 66 ms 70 ms 68 ms ge-1-0-0-927.ie1.telstraclear.net [218.101.61.8] 11 81 ms 83 ms 84 ms ge-4-0-819.u22.telstraclear.net [203.98.23.2] 12 140 ms 169 ms 173 ms clix-landcorp-nz.cpe.clix.net.nz [203.97.1.182] 13 145 ms 133 ms 140 ms 10.255.1.2 14 170 ms 80 ms 78 ms 10.255.1.1 15 159 ms 160 ms 161 ms 10.255.1.2 16 * * * Request timed out. 17 * 1002 ms 77 ms 10.255.1.2 18 80 ms 78 ms 76 ms 10.255.1.1 19 * * * Request timed out. 20 * 79 ms 77 ms 10.255.1.1 21 * 80 ms 78 ms 10.255.1.2 22 81 ms 88 ms 88 ms 10.255.1.1 23 * * 995 ms 10.255.1.2 24 80 ms 78 ms 78 ms 10.255.1.1 25 81 ms 79 ms 77 ms 10.255.1.2 26 * * * Request timed out. 27 * 1000 ms 81 ms 10.255.1.2 28 81 ms 81 ms 82 ms 10.255.1.1 29 287 ms 85 ms 86 ms 10.255.1.2 30 100 ms 84 ms 82 ms 10.255.1.1	rixth (9629)
610007	2007-11-10 04:00:00	Can't ping ascent - it times out:(	wainuitech (129)
610008	2007-11-10 07:51:00	Hmm, can't ping it but I can go to the website alright and tracert times out as well.	beeswax34 (63)
610009	2007-11-10 09:51:00	Ran tracert, got the same as rixth but with no timeouts. :)	Trev (427)
610010	2007-11-11 03:03:00	When I did it (from TelstraClear cable) tracert got stuck alternating between 10.255.1.1 & 10.255.1.2 after getting to clix-landcorp-nz.cpe.clix.net.nz. Odd thing is, is that the entire 10.x.x.x range of addresses is designated as for "Private IP" (ie LAN only) use, so shouldn't appear in a public internet trace & aren't supposed to be forwarded onto the public net by any router. No idea what they're doing there, unless it's deliberate mechanism to stop tracing through a router somehow???	MushHead (10626)
610011	2007-11-11 03:23:00	Might be something to do with being a secure website, to stop someone hacking in to get credit card info. :)	Trev (427)
610012	2007-11-11 03:34:00	It will be a security feature not to respond to pings. Microsoft doesn't respond to pings either yet we still know they are there. :p	Jen (38)
610013	2007-11-11 03:43:00	Firewall at ascent end does not reply to pings and traceroute time-exceed responses. <vinref@ngrunt:~:112>ping ascent.co.nz PING ascent.co.nz (203.128.225.5): 56 data bytes ^C ----ascent.co.nz PING Statistics---- 8 packets transmitted, 0 packets received, 100.0% packet loss <vinref@ngrunt:~:113>traceroute ascent.co.nz traceroute to ascent.co.nz (203.128.225.5), 64 hops max, 40 byte packets 1 home.gateway (192.168.1.254) 0.361 ms 0.325 ms 0.321 ms 2 loop0.lns1.bne1.internode.on.net (150.101.180.16) 10.029 ms 10.129 ms 9.621 ms 3 gi0-3.cor2.bne1.internode.on.net (150.101.180.115) 11.808 ms 10.948 ms 10.300 ms 4 pos4-2.bdr1.syd6.internode.on.net (203.16.212.13) 27.826 ms 28.325 ms 26.311 ms 5 59.154.10.29 (59.154.10.29) 28.588 ms 29.502 ms 29.487 ms 6 gigabitethernet4-3.ken12.sydney.telstra.net (139.130.2.65) 30.284 ms 28.513 ms 29.260 ms 7 * * * 8 TenGigE0-1-0-2.chw-core2.Sydney.telstra.net (203.50.19.129) 27.949 ms 26.173 ms * 9 Port-Channel1.pad-gw1.Sydney.telstra.net (203.50.6.25) 29.842 ms 30.883 ms 29.313 ms 10 unknown.net.reach.com (134.159.126.33) 26.368 ms 25.166 ms 28.312 ms 11 202.84.219.98 (202.84.219.98) 52.496 ms 52.602 ms 54.195 ms 12 203.167.233.14 (203.167.233.14) 52.243 ms 52.383 ms 55.672 ms 13 ie1-g-0-0-0.telstraclear.net (203.98.50.1) 52.530 ms 52.486 ms 54.670 ms 14 ge-4-0-819.u22.telstraclear.net (203.98.23.2) 64.354 ms 63.196 ms 62.858 ms 15 clix-landcorp-nz.cpe.clix.net.nz (203.97.1.182) 61.348 ms 62.157 ms 62.382 ms 16 * * * 17 * *^C	vinref (6194)
610014	2007-11-11 20:44:00	When I did it (from TelstraClear cable) tracert got stuck alternating between 10.255.1.1 & 10.255.1.2 after getting to clix-landcorp-nz.cpe.clix.net.nz. Odd thing is, is that the entire 10.x.x.x range of addresses is designated as for "Private IP" (ie LAN only) use, so shouldn't appear in a public internet trace & aren't supposed to be forwarded onto the public net by any router. No idea what they're doing there, unless it's deliberate mechanism to stop tracing through a router somehow??? you can have "private IP's" in a trace. and number of ISP and big telco's have some private IP inside a routing room, so you come in on a public IP bound around the telco on private IP and then come out again on public IP. EG: the telco has a public IP in auckland, uses private IP on fibre to get to AUZ and then links out on public IP again. as for the trace of ip's bouncing back and forth, it looks to me as a blocking effect to stop you doing a ping.	robsonde (120)
1