[83067] in North American Network Operators' Group
Re: Traffic to our customer's address(126.0.0.0/8) seems blocked by packet filter
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Wed Aug 3 23:29:46 2005
Date: Thu, 4 Aug 2005 03:29:10 +0000
From: bmanning@vacation.karoshi.com
To: Randy Bush <randy@psg.com>
Cc: mkawano@bb.softbank.co.jp, joelja@darkwing.uoregon.edu,
nanog@merit.edu
In-Reply-To: <17137.4743.465363.888685@roam.psg.com>
Errors-To: owner-nanog@merit.edu
On Wed, Aug 03, 2005 at 08:52:55AM -1000, Randy Bush wrote:
>
> > You can ping to 126.66.0.30/8.
>
> and how does one ping a /8?
>
> randy
%ping 126.255.255.255 works for some mutant stacks.
plays old-hob w/ your arp cache tho.
but i suspect that the /8 on the reference was either
a typo from the original query or a vestigal remainder
from the emacs buffer.
pinging the indicated /32 gives me this:
$ ping 126.66.0.30
PING 126.66.0.30 (126.66.0.30): 56 data bytes
64 bytes from 126.66.0.30: icmp_seq=0 ttl=235 time=311.999 ms
64 bytes from 126.66.0.30: icmp_seq=1 ttl=235 time=443.25 ms
^C
--- 126.66.0.30 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max = 311.999/377.624/443.25 ms
from the IVTF conference hotel lobby.
--bill
