Football fans at Citylink

Football fans at Citylink

Saw this on geekzone, somebody doing a traceroute from their TCL home connection to citylink

Telstra >> ihug >> citylink.  All sub 30ms responses.

192.168.0.1
192.168.1.1
218.101.61.122
218.101.61.161
No response from host
g1-0-927.u11.tspn.telstraclear.net
g1-926.u12.brh.telstraclear.net
lnk1-ihug-ge-1-0-1642.u12.telstraclear.net
fa0-24.akl-sky-car1.ihug.net
203-109-145-17.static.ihug.co.nz
rufer.citylink.co.nz
zidane.citylink.co.nz


Maybe some feverites working at Citylink?!?!

Geekzone... you can stop giving that turncoat Freitas your (well Google's) money...

NERD ALERT!  NERD ALERT

That's cool...

[code]five:~ yomcat$ traceroute citylink.co.nz
traceroute to citylink.co.nz (202.8.44.4), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.110 ms 0.797 ms 0.993 ms
2 203-97-250-1.cable.telstraclear.net (203.97.250.1) 9.866 ms 11.302 ms 10.517 ms
3 ae1-947.ie4.telstraclear.net (218.101.61.54) 9.822 ms 10.545 ms 9.464 ms
4 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 23.043 ms 21.285 ms 23.082 ms
5 * * *
6 g1-0-927.u11.tspn.telstraclear.net (218.101.61.6) 114.575 ms 55.320 ms 34.602 ms
7 g1-926.u12.brh.telstraclear.net (218.101.61.35) 215.597 ms 28.891 ms 27.837 ms
8 lnk1-ihug-ge-1-0-1642.u12.telstraclear.net (203.98.18.162) 20.234 ms 19.782 ms 21.110 ms
9 fa0-24.akl-sky-car1.ihug.net (203.109.143.34) 20.661 ms 20.758 ms 20.888 ms
10 203-109-145-17.static.ihug.co.nz (203.109.145.17) 25.776 ms 20.698 ms 21.151 ms
11 rufer.citylink.co.nz (202.8.44.97) 38.046 ms 32.178 ms 32.755 ms
12 zidane.citylink.co.nz (202.8.44.4) 34.347 ms 38.707 ms 31.139 ms
five:~ yomcat$ [/code]

You've got some good pings there, looks like TCL may have finally solved their ARP flooding issue.

What they are thinking having all their network on one VLAN though, I don't know.