On Thu, Aug 21, 2003 at 01:53:01PM +1200, Juha Saarinen wrote:
~$ ping alien.xtra.co.nz PING alien.xtra.co.nz (202.27.184.3) from 192.168.1.15 : 56(84) bytes of data.
From v60.XTRAK2-B1.xtra.co.nz (203.96.111.149) icmp_seq=14 Packet filtered From v60.XTRAK2-B1.xtra.co.nz (203.96.111.149) icmp_seq=23 Packet filtered From v60.XTRAK2-B1.xtra.co.nz (203.96.111.149) icmp_seq=27 Packet filtered From v60.XTRAK2-B1.xtra.co.nz (203.96.111.149) icmp_seq=30 Packet filtered From v60.XTRAK2-B1.xtra.co.nz (203.96.111.149) icmp_seq=33 Packet filtered
--- alien.xtra.co.nz ping statistics --- 35 packets transmitted, 0 received, +5 errors, 100% loss, time 34022ms
A Windows worm side-effect?
ec-r-1:~# traceroute alien.xtra.co.nz traceroute to alien.xtra.co.nz (202.27.184.3), 30 hops max, 38 byte packets 1 203.97.57.93 (203.97.57.93) 1.941 ms 0.969 ms 1.553 ms 2 cs1-e4-2-acld.auckland.clix.net.nz (203.97.2.254) 1.207 ms 1.107 ms 0.950 ms 3 g1-0-927.u11.tspn.telstraclear.net (218.101.61.6) 4.328 ms 3.588 ms 2.753 ms 4 xtra.ape.net.nz (192.203.154.60) 2.322 ms 3.084 ms 3.065 ms 5 * * * Infact, hardly anything goes past there for me.. I got /one/ packet thru to the next hop while watching mtr a minute ago. I suspect that this packet that got thru was one that was let thru thier firewall rules however. Of course, if they are filtering egress TTL exceeded packets theres not alot a traceroute can show ;) Nathan Ward