On Jun 8, 2016 1:31 PM, "Vick Khera" wrote:
>
> On Wed, Jun 8, 2016 at 2:41 PM, Jeremy Bennett <
jbenn...@hikitechnology.com>
> wrote:
>
> > If you won't have mobile users, IPSec could be a viable option.
> >
>
> iPhone mobile VPN works great with IPSec, no additional software
I've had OpenVPN set up with around 20 remote sites for years. Fairly low
bandwidth but I prefer the configuration myself. My remote sites don't
route all traffic back to HQ ; It all depends on the routes you push to the
remote sites.
___
pfSense mailing
Is there any news on the authenticated ntp side ?
Regards
Forwarded Message
> From: Valerio Bellizzomi
> Reply-to: pfSense Support and Discussion Mailing List
>
> To: pfSense Support and Discussion Mailing List
>
Thanks for your advice. I've only worked with OpenVPN, but I'll do some
more research on IPSec.
Good thing the hardware that I most like to use for pfSense deployments has
an Intel Atom processor that does support AES (
Jeremy & Vick,
I'm open to considering an IPSec if that's the best option for this use
case. We're talking about 8 locations starting out, with a 9th office
opening shortly thereafter, and the possibility of going up to a total of
15-20 sites within 1-2 years after that.
When I read
Hi
Basically running a similar setup .
Pfsense with four ports .
bce0 Wan
bce1 Lan
bce2 BGP to the rest of the offices .
bce3 Open VPN for out of office connectivity .
You will need to seat with your IP engineers and properly design your network
address scheme.
Regards
Watz
On Wed, Jun 8, 2016 at 6:31 AM, David White wrote:
> I didn't think I would have to setup a new server / port for each remote
> office. I thought that, with the SSL/TLS setup, I could have a single
> server and configure it so that clients can see & interact with each