> OK, the ip address is 44.98.2.5, and the problem is he doesn't
> see me. For a bit, the nodes were actually talking to each other
> but he didn't receive anything I sent. Now, he's not even getting
> the node to send again.
>
> the routes are
> 209.4.66.7 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
> 44.98.2.5 205.152.185.200 255.255.255.255 UGH 0 0 2 tunl0
> 44.98.2.22 209.4.65.28 255.255.255.255 UGH 0 0 0 tunl0
> 44.98.2.0 0.0.0.0 255.255.255.0 U 0 0 0 tunl0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 57 lo
> 44.0.0.0 128.54.16.18 255.0.0.0 UG 0 0 0 tunl0
> 0.0.0.0 209.4.66.7 0.0.0.0 UG 0 0 185 ppp0
I see your routes to your tunnel device, so what you have there says:
| Route all datagrams for 44.98.2.5 via the tunnel device, which will
| encapsulate them in an IP datagram from 205.152.185.200.
|
| Datagrams for 0.0.0.0 (and therefore 205.152.185.200) will be routed
| via your ppp0 device.
Presuming 44.98.2.5 is living off the 205.152.185.200 gateway then I see
nothing wrong with your configuration.
This route is wrong:
> 44.98.2.0 0.0.0.0 255.255.255.0 U 0 0 0 tunl0
but shouldn't be causing the problem you are experiencing.
What kernel are you using?
Does he have his IPIP encapsulation set up correctly?
Terry