In article <3.0.32.19970525143303.00aa5ad0@unix.csosl.co.uk>,
	Nick Loman <nick@csosl.co.uk> writes:
> Are there any thoughts on the legitimacy of firewalling UDP packets in
> such a way that tracerouting a site puts it in a loop?

Are there any thoughs on the legitimacy of spying out other peoples
network topology?

> Does this violate any Internet standards?

No. The fact that a site is connected to Internet doesn't IMHO give you
the right to send packets to it or receive packets from it. If you are
able to do so you are lucky.

> unix# traceroute www.ezcgi.com
> traceroute to ezcgi.com (194.131.104.134), 30 hops max, 40 byte packets
...
>  7  fmservice-doc-gw.pipex.net (158.43.16.74)  25.928 ms  26.893 ms  30.011 ms
>  8  fmservice-doc-gw.pipex.net (158.43.16.74)  36.058 ms *  30.36 ms
>  9  * fmservice-doc-gw.pipex.net (158.43.16.74)  36.317 ms *
> 10  fmservice-doc-gw.pipex.net (158.43.16.74)  30.779 ms *  31.118 ms
> 11  * fmservice-doc-gw.pipex.net (158.43.16.74)  34.592 ms *
> 12  fmservice-doc-gw.pipex.net (158.43.16.74)  30.947 ms *  34.07 ms
> ^C   

Beginners, that's much better:

tron@lyssa:~>ping -c 1 www.web.de
PING web.de (194.45.170.79): 56 data bytes
64 bytes from 194.45.170.79: icmp_seq=0 ttl=243 time=253.490 ms

----web.de PING Statistics----
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 253.490/253.490/253.490 ms
tron@lyssa:~>traceroute www.web.de
traceroute to web.de (194.45.170.79), 30 hops max, 40 byte packets
...
11  cisco.cinetic.de (194.122.253.6)  218.621 ms  186.955 ms  188.903 ms
12  192.168.1.2 (192.168.1.2)  218.623 ms !H  206.853 ms !H  198.744 ms !H

-- 
Matthias Scheler                                http://home.pages.de/~tron/