Orange - 192.168.1.14
Ping OK on 192.168.1.158 (Mango), 192.168.1.1, www.google.co.uk
Ping unsuccessful on 192.168.1.72 (Tomato)
Code:
rhys@Orange:~$ ping 192.168.1.72
PING 192.168.1.72 (192.168.1.72) 56(84) bytes of data.
^C
--- 192.168.1.72 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3024ms
rhys@Orange:~$ ping 192.168.1.158
PING 192.168.1.158 (192.168.1.158) 56(84) bytes of data.
64 bytes from 192.168.1.158: icmp_req=1 ttl=64 time=3.85 ms
64 bytes from 192.168.1.158: icmp_req=2 ttl=64 time=1.88 ms
64 bytes from 192.168.1.158: icmp_req=3 ttl=64 time=2.10 ms
^C
--- 192.168.1.158 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.884/2.611/3.850/0.882 ms
rhys@Orange:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=2.37 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=1.78 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=1.88 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=10.8 ms
^C
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 1.787/4.227/10.869/3.841 ms
rhys@Orange:~$ ping www.google.co.uk
PING www.google.co.uk (173.194.67.94) 56(84) bytes of data.
64 bytes from wi-in-f94.1e100.net (173.194.67.94): icmp_req=1 ttl=45 time=18.7 ms
64 bytes from wi-in-f94.1e100.net (173.194.67.94): icmp_req=2 ttl=45 time=18.4 ms
64 bytes from wi-in-f94.1e100.net (173.194.67.94): icmp_req=3 ttl=45 time=18.2 ms
^C
--- www.google.co.uk ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 18.218/18.477/18.769/0.251 ms
Mango - 192.168.1.158
Ping OK on 192.168.1.14 (Orange), 192.168.1.1, www.google.co.uk
Ping unsuccessful on 192.168.1.72 (Tomato)
Code:
rhys@Mango:~$ ping 192.168.1.14
PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data.
64 bytes from 192.168.1.14: icmp_req=1 ttl=64 time=1.62 ms
64 bytes from 192.168.1.14: icmp_req=2 ttl=64 time=2.13 ms
64 bytes from 192.168.1.14: icmp_req=3 ttl=64 time=1.82 ms
^C
--- 192.168.1.14 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 1.623/1.862/2.139/0.215 ms
rhys@Mango:~$ ping 192.168.1.72
PING 192.168.1.72 (192.168.1.72) 56(84) bytes of data.
^C
--- 192.168.1.72 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2015ms
rhys@Mango:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.499 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.433 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.418 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.431 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.423 ms
^C
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.418/0.440/0.499/0.039 ms
rhys@Mango:~$ ping www.google.co.uk
PING www.google.co.uk (173.194.41.95) 56(84) bytes of data.
64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=1 ttl=53 time=11.3 ms
64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=2 ttl=53 time=11.3 ms
64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=3 ttl=53 time=11.2 ms
64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=4 ttl=53 time=11.3 ms
^C
--- www.google.co.uk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 11.280/11.332/11.376/0.040 ms
Tomato - 192.168.1.72
Ping OK on 192.168.1.14 (Orange) 192.168.1.158 (Mango), 192.168.1.1, 173.194.41.95 (www.google.co.uk)
Ping unsuccessful on 192.168.1.72 (Tomato), www.google.co.uk
Code:
rhys@Tomato:~$ ping 192.168.1.14
PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data.
64 bytes from 192.168.1.14: icmp_req=1 ttl=64 time=1.31 ms
64 bytes from 192.168.1.14: icmp_req=2 ttl=64 time=1.47 ms
64 bytes from 192.168.1.14: icmp_req=3 ttl=64 time=1.93 ms
^C
--- 192.168.1.14 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.313/1.571/1.932/0.266 ms
rhys@Tomato:~$ ping 192.168.1.158
PING 192.168.1.158 (192.168.1.158) 56(84) bytes of data.
64 bytes from 192.168.1.158: icmp_req=1 ttl=64 time=0.181 ms
64 bytes from 192.168.1.158: icmp_req=2 ttl=64 time=0.191 ms
64 bytes from 192.168.1.158: icmp_req=3 ttl=64 time=0.187 ms
^C
--- 192.168.1.158 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.181/0.186/0.191/0.011 ms
rhys@Tomato:~$ ping 192.168.1.72
PING 192.168.1.72 (192.168.1.72) 56(84) bytes of data.
^C
--- 192.168.1.72 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1006ms
rhys@Tomato:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.496 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.443 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.439 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.450 ms
^C
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.439/0.457/0.496/0.022 ms
rhys@Tomato:~$ ping www.google.co.uk
ping: unknown host www.google.co.uk
rhys@Tomato:~$ ping 173.194.41.95
PING 173.194.41.95 (173.194.41.95) 56(84) bytes of data.
64 bytes from 173.194.41.95: icmp_req=1 ttl=53 time=11.3 ms
64 bytes from 173.194.41.95: icmp_req=2 ttl=53 time=11.1 ms
64 bytes from 173.194.41.95: icmp_req=3 ttl=53 time=11.1 ms
64 bytes from 173.194.41.95: icmp_req=4 ttl=53 time=11.4 ms
^C
--- 173.194.41.95 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 11.161/11.273/11.435/0.174 ms
I'm curious to know why there's a DNS issue on Tomato for external domains, would this be a good place to start?
EDIT:
Just as a side note, I have restarted my router and disconnected all cables and blown out any dust (just incase) and reconnected everything.
Bookmarks