can't ping to an internal IP through tinc's virtual interfaces

[Jason]

On Wed, 30 Jul 2003, Roberto Meyer wrote:

> The only issue I have to solve is that isivpn connects to pamvpn
> through a dynamic IP address, so when e-mail arrives to pamvpn it don't
> know how to deliver it to isivpn.
> 
> I'll test a script to run with openssh so I can update isivpn's IP at
> pamvpn's host-file and reload tincd. This way, pamvpn will be able to 
> 'connnectTo' isivpn anytime it wants.

I'm a little confused about why you need the dynamic ip in the hosts file,
so forgive me if this is off base... but if one of the boxes has a static
ip/dns and the other is dynamic, tell the dynamic one to ConnectTo the
static one and then the vpn will always be up and available.  Then all of
your apps can reach either box using the private VPN IPs which never change. 
Then your mail will be encrypted thru the VPN too.  remember if one of those
boxes talks to the other one using the public internet routable IP for the
destination address, the traffic doesn't go thru the VPN tunnel.

Tinc:         Discussion list about the tinc VPN daemon
Archive:      http://mail.nl.linux.org/lists/
Tinc site:    http://tinc.nl.linux.org/