Hi All, Here's an 'interesting' one for you. Traceroutes to any destination that have non-responding hops in their path don't complete....the command just hangs waiting for a response from the 'dead' hop. Code: root@Router:/tmp/home/root# traceroute 220.127.116.11 traceroute to 18.104.22.168 (22.214.171.124), 30 hops max, 38 byte packets 1 5e0574be.bb.sky.com (126.96.36.199) 23.315 ms 23.048 ms 24.040 ms 2 10.245.139.241 (10.245.139.241) 22.127 ms 22.110 ms 22.569 ms 3 te0-1-0-7.er11.thlon.ov.easynet.net (188.8.131.52) 29.166 ms 30.370 ms 31.482 ms 4 ntl-ge2-9.prt0.rbsov.bbc.co.uk (184.108.40.206) 27.345 ms 26.346 ms 26.258 ms 5 Now, a traceroute -v showed that it was receiving ping replies from 'itself to itself' which is a bit odd. Then I remembered that I've an external device which pings my WAN address from outside every second....I turned this off and now traceroute completes - the non responding hops (5,6 & 7) now get '*' marks and time out. Re-enabling the external ping box stops tomato's traceroute from working. Behaviour found on Shibby Tomato 105 AIO, don't know if it's always been there. Any ideas?