Date: Sat, 15 Jan 2011 02:04:27 -0800 From: perryh@pluto.rain.com To: cswiger@mac.com Cc: kes-kes@yandex.ru, freebsd-questions@freebsd.org Subject: Re: strange behaviour Message-ID: <4d31712b.50rR8DPepKqFzqZo%perryh@pluto.rain.com> In-Reply-To: <533DC7E8-4BA1-4FA7-A5FA-D4A3C9D08368@mac.com> References: <1369035653.20110114233621@yandex.ru> <533DC7E8-4BA1-4FA7-A5FA-D4A3C9D08368@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Swiger <cswiger@mac.com> wrote: > > # ping 10.7.7.7 > > PING 10.7.7.7 (10.7.7.7): 56 data bytes > > ping: sendto: Invalid argument > > ping: sendto: Invalid argument > > ping: sendto: Invalid argument > > > > what is problem and how to fix?? > > Where are you routing 10.7.7.7 to? > > If you don't have a specific internal route (or NAT) doing > something with it, your upstream Internet routers ought to be > returning ICMP host unreachable errors for RFC-1918 addresses... In that case, shouldn't ping be reporting the ICMP error -- after sending the packet -- rather than complaining about an "Invalid argument" and refusing to send it at all? Even if 10.5.0.1 and 10.7.7.7 are routed differently on the local host I would not expect one to give "Invalid argument" and the other not.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d31712b.50rR8DPepKqFzqZo%perryh>