On Wed, Mar 3, 2010 at 9:28 AM, Rafael Cristian Machado de Avila <rcristia...@gmail.com> wrote: > Also not sure what kind of access will be made between the networks. Example > Active Directory, File Server, administrative applications
This is one of the main uses we make of pfSense. I have two offices, a data center, and two home offices all linked together via IPsec VPN and pfSense at each point. The offices and data center use fixed endpoints (fixed IP) and the home offices use "client" mode. In "client" mode you can only make the connections outbound so if the IPsec circuit is not up, you cannot force it up from the main office, for example. Only a client at the home office can cause it to start up. This is easily worked around using appropriate keepalive settings. You can control what traffic flows to where via the firewall rules under the firewall's IPsec tab. We just leave it open. Over the vpn hops, we run mostly internal HTTP servers, SIP, ssh, and IMAP for mail access to the main office. If you have enough bandwidth to support what your purpose is, pfSense will not be the bottleneck. It is rock solid reliable and has been for years. You will be happy with it. --------------------------------------------------------------------- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
