Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 09 Jul 2008 11:45:35 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        zaphod@fsklaw.com, freebsd-net@freebsd.org
Subject:   Re: Tunneling issues
Message-ID:  <200807091545.m69FjcP4031350@lava.sentex.ca>
In-Reply-To: <7904ac587e71a42fb86c2bbe77bde0ae.squirrel@cor>
References:  <8f7879db41dbaecc479a017110e8f32f.squirrel@cor> <200807040155.m641tl8s000607@lava.sentex.ca> <7904ac587e71a42fb86c2bbe77bde0ae.squirrel@cor>

next in thread | previous in thread | raw e-mail | index | archive | help
At 11:21 AM 7/9/2008, zaphod@fsklaw.com wrote:

>I agree it should work.  But it's not.  With respect to the next two
>questions, yes and yes.

Can you post some of the configs you are using for 3 of the sites so 
we can perhaps spot the problem(s) you are having ? I have a similar 
setup with 5 sites, all talking to each other via IPSEC tunnels. Its 
a lot of policies, but they work just fine.




>I'm not a huge fan of OpenVPN, but the bigger issue is that the gif
>tunnels come up at boot up. As well as routes.  Given the client server
>nature of OpenVPN it is suitable, because if a server reboots, I'm not
>certain a client would auto re-connect.

We have ~ 400 sites running OpenVPN across Canada that all reconnect 
just fine after reboots / power cycles etc.  We dont let the clients 
talk to each other, but that would just be a config change to allow 
that to work.

         ---Mike 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807091545.m69FjcP4031350>