strange behaviour

[Chuck Swiger]

On Jan 14, 2011, at 1:48 PM, Коньков Евгений wrote:
> CS> Where are you routing 10.7.7.7 to?
> 
> 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...
> 
> 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
> 
> 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
> 
> 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,
-- 
-Chuck