Date: Fri, 14 Jan 2011 14:17:42 -0800 From: Chuck Swiger <cswiger@mac.com> To: =?utf-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= <kes-kes@yandex.ru> Cc: freebsd-questions@freebsd.org Subject: Re: Re[2]: strange behaviour Message-ID: <01A5C1AD-DB6B-4797-962A-D3FB3E34E33F@mac.com> In-Reply-To: <203646179.20110114234846@yandex.ru> References: <1369035653.20110114233621@yandex.ru> <533DC7E8-4BA1-4FA7-A5FA-D4A3C9D08368@mac.com> <203646179.20110114234846@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 14, 2011, at 1:48 PM, =EB=CF=CE=D8=CB=CF=D7 =E5=D7=C7=C5=CE=C9=CA = wrote: > CS> Where are you routing 10.7.7.7 to? >=20 > CS> If you don't have a specific internal route (or NAT) doing > CS> something with it, your upstream Internet routers ought to be > CS> returning ICMP host unreachable errors for RFC-1918 addresses... >=20 > no NAT > #route add 10.7.7.0/24 234.242.32.3 > route: writing to routing socket: Network is unreachable > add net 10.7.7.0: gateway 234.242.32.3: Network is unreachable That doesn't surprise me-- 224 - 239 is multicast or reserved = special-purpose address space. > #route add 10.7.7.0/24 10.11.8.28 > add net 10.7.7.0: gateway 10.11.8.28 > no error messages >=20 > default I.N.E.T UGS 0 2001201 rl0 > 10.0.0.0/8 10.11.19.2 UGS 1 4021798 rl0 > 10.7.7.0/24 10.11.8.28 UGS 0 0 rl0 > 10.11.19.0/29 link#2 UC 0 0 rl0 > 10.11.19.1 00:06:4f:60:1a:b8 UHLW 1 4707299 lo0 > 10.11.19.2 00:e0:4c:4d:10:fe UHLW 2 2 rl0 = 862 > 10.11.19.16/29 link#8 UC 0 0 bridge > 127.0.0.1 127.0.0.1 UH 0 178333 lo0 > 192.168.1.5 192.168.0.1 UH 0 741736 ng2 >=20 > tcpdump shows that no packets leave router. It doesn't look like any of your interfaces think 10.11.8.28 is local to = them; and presumably the upstream gateway used by the default route = doesn't either. Regards, --=20 -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01A5C1AD-DB6B-4797-962A-D3FB3E34E33F>