Problems with gif tunnels

[Jeremie Le Hen]

Hi Greg,

> >   Destination        Gateway            Flags    Refs      Use  Netif Expire
> >   default            150.101.14.9       UGS         0        7    rl0
> >   150.101.14.8/30    link#2             UC          0        0    rl0
> >   150.101.14.9       00:90:1a:40:09:98  UHLW        2        2    rl0    903
> >   192.109.197        link#1             UC          0        0    xl0
> >   192.109.197.135    00:10:4b:66:1e:e9  UHLW        0     6757    xl0   1056
> >   192.109.197.137    00:50:da:cf:07:35  UHLW        0    99336    xl0   1188
> >   192.109.197.255    ff:ff:ff:ff:ff:ff  UHLWb       0    34521    xl0
> >   203.16.215.227     150.101.14.9       UGHS        1        4    rl0

I guess you need a route to something like 192.83.231.0/24 through gif0.
Try
%%%
    route add -host 192.83.231.16 -interface gif0
%%%

> > I then get somebody from the other end to ping me:
> >
> >   17:49:10.228597 IP 203.16.215.227 > 150.101.14.10: IP 192.83.231.16 > 192.109.197.145: icmp 64: echo request seq 6908
> >   17:49:11.229188 IP 203.16.215.227 > 150.101.14.10: IP 192.83.231.16 > 192.109.197.145: icmp 64: echo request seq 6909
> >
> > But that's all.  Nothing goes out.  I've tried this on different
> > systems, and I know somebody else who is using what looks like an
> > identical configuration with this ISP, and it works fine.  I've tried
> > different systems, one and two NICs, 4.x and 5.x, all with the same
> > (non)result.  What am I missing?

It would be worth knowing if the ICMP packet goes out from your
``internal'' interface (xl0).  In this case, you should also see
the ICMP echo-reply.

Regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >