On Sat, 16 Oct 2010 20:11:46 +0100 Adam Hardy <> wrote:
[stuff]
Nope you're not the only one:
( 4:~ )%ping -s 1473 208.245.107.9
PING 208.245.107.9 (208.245.107.9) 1473(1501) bytes of data.
^C --- 208.245.107.9 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3022ms
this also appears to violate the PING standard:
( 5:~ )%ping -s 1470 208.245.107.9
PING 208.245.107.9 (208.245.107.9)
1470(1498) bytes of data. From 192.168.0.2 icmp_seq=1 Frag needed and
DF set (mtu = 1492) ^C
--- 208.245.107.9 ping statistics ---
7 packets transmitted, 0 received, +1 errors, 100% packet loss, time
6040ms
Normal PINGs seem to be fine:
( 7:~ )%ping 208.245.107.9
PING 208.245.107.9 (208.245.107.9) 56(84) bytes of data. 64
bytes from 208.245.107.9: icmp_req=1 ttl=118 time=150 ms 64 bytes from
208.245.107.9: icmp_req=2 ttl=118 time=147 ms 64 bytes from
208.245.107.9: icmp_req=3 ttl=118 time=149 ms 64 bytes from
208.245.107.9: icmp_req=4 ttl=118 time=146 ms ^C
--- 208.245.107.9 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 146.120/148.259/150.102/1.622 ms
The device has a DNS of mktgw1.ibllc.com \footnote{Isn't this sounding
like insecure.org now?} and doesn't respond to nmap's pings. I call
fault on their part.
Are you on a PPPoE connection directly or on a NAT'd network?
--
Morgan Gangwere
PGP Key at http://indrora.homelinux.org/gpg_key.asc
BOFH Excuse #43
MTU set too high.
Attachment:
signature.asc
Description: PGP signature