connection established, can't ping

[Guus Sliepen]

On Tue, Sep 28, 2004 at 07:31:03PM +0400, David Chkhikvadze wrote:

> OK, I did it but nothing chainged. I get same exact output from tinc -n vpn 
> -d5 -D. 
>  
> maybe something else? 
>  
> this is output of route -F: 
>  
> Kernel IP routing table 
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface 
> 62.168.172.144  *               255.255.255.248 U     0      0        0 eth1 
> localnet        *               255.255.255.0   U     0      0        0 eth0 
> localnet        *               255.255.255.0   U     0      0        0 vpn 
> default         62.168.172.145  0.0.0.0         UG    0      0        0 eth1 

Aha. Everything for localnet now goes to eth0, never to vpn. You have to
make sure your routing table sends those packets to the vpn interface
that should go to the other side.

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20040928/5feaa6ff/attachment.pgp