Re: openbsd routing logic confused by ip prefixes - correction

["B. Culibrk" <bc@ectrl.com>]

On Wed, 2004-02-04 at 16:45, José M. Fandiño wrote:

> 
> yes, I did that test before sending a mail to misc@ but
> the current scenario is more complex. 
> 
> I will need to do proxy-arp for legacy boxes in the 
> first block, I think that a little ascii diagram can 
> explain it better:
> 
>                  195.55.55.1                   old network 195.55.55.0/26
> |INTERNET|---|GW|----------------------|OBSD |-------------
>                            195.55.55.66 (with proxyarp for the old network)
> 
> As you can see I need a more specific route for 195.55.55.1/32 
> in the external interface and a network route to 195.55.55.0/26 
> in the internal. This is very easy to setup in GNU/Linux, all the
> problem is add a 195.55.55.1/32 route to OpenBSD.
> 
> ** Even adding a route like this works:
> route add -net 195.55.55.0/30 -interface 195.55.55.66
> 
> but a host route (read 195.55.55.1/32) fails, and it
> fails only with OpenBSD. :-?
> 
> If I run "tcpdump -i xl0 -n host 195.55.55.1 or host 195.55.55.66"
> to see the wire, the OpenBSD tcp/ip stack _don't_send_packets_.
> 
> I think it's a problem which the routing logic of OBSD,
> why a can setup a /30 route and not a /32 route to 
> 195.55.55.1?
> 
> 	/-----/
> 
> fuego2# ping 195.55.55.1
> PING 195.55.55.1 (195.55.55.1): 56 data bytes
> Feb 3 22:28:38 fuego2 /bsd: arpresolve: can't allocate llinfo
> ^C--- 195.55.55.1 ping statistics ---
> 5 packets transmitted, 0 packets received, 100.0% packet loss

Are you sure that your proxy_arp is working fine?