If you mean a packet destined for the source address of the
POINTOPOINT link, then yes, this is intentional. If you want to be
able to ping the local end you'll need a route on lo.
> Hi
>
> I don't know if this is intentional or a bug, but if ifconfig is used to
> configure a point to point device, such as 'tun' or the newer 'gif' devices,
> then the kernel insists on installing a route where the destination is the
> end point of the tunnel, the gateway is the source of the tunnel and the
> interface is the device itself. I have checked this in version 3.2+KAME,
> what I a using, and also on version 4.1. The effect of the above is that the
> packet that uses the tunnel will never appear on the wire.
>
> Here is an output
>
> the_swamp# ifconfig gif0 132.146.115.164 132.145.113.1
> the_swamp# netstat -rnf inet
> Routing tables
>
> Internet:
> Destination Gateway Flags Netif Expire
> default 132.146.115.1 UGSc 1 0 fxp1
> 127.0.0.1 127.0.0.1 UH 0 4 lo0
> 132.145.113.1 132.146.115.164 UH 0 0 gif0
> 132.146.115/24 link#2 UC 0 0 fxp1 =>
> 132.146.115.1 0:30:19:9a:e4:71 UHLW 2 0 fxp1 460
>
> I am also interested in using gated with point to point tunnels, but gated
> also insists on doing the above for point to point links.
>
> I thank you in advance for any advice you may have.
>
> Parminder Mudhar
> __________________________
> [EMAIL PROTECTED]
--
Brian <[EMAIL PROTECTED]> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
