This article discusses how one can configure an IPSec WAN that allows branch offices connected to a central office to route traffic to each other.
For example: “Office A” (10.1.0.0/16) and “Office B” (10.2.0.0/16) are both connected to “Headquarters” (10.0.0/16) vian an IPSec tunnel. By default, Office A and Office B can pass traffic to Headquarters, but not to each other.
To Accomplish this you could create a third tunnel between Office A and Office B directly. However, support for multi-subnet IPSec configurations, added in Core 95, makes this possible without creating separate tunnels between each of the offices. While this is not a significant advantage with only one or two offices, it allows you to reduce the number of tunnels in remote offices, which does reduce management overhead and hardware requirements.
Begin with the intial configuration described below and as outlined in the main IPSec documentation. Once you have confirmed that you are able to send traffic from Office A and Office B to Headquarters and back, then proceed to the next step.
You will make the following changes to the IPSec configurations for each office:
This will make it so that each of the remote offices now knows to send traffic destined to the other remote office via the IPSec tunnel. However, we need to tell the central office IPFire box how to handle this traffic.
You now need to add two rules to the firewall on the “Headquarters” machine. - Source: 10.1.0.0/16 - Enable the “Use Network Address Translation (NAT)” check box and choose the “Source NAT” radio button. - In the “New source IP address” drop-down menu, choose the green address of the Headquarters machine. - Destination: 10.2.0.0/16 - Protocol: All Ensure that the rule is activated, and save your settings.
Create another rule that is identical, except reverse the source and destination.
Apply the firewall rules.
If all is properly configured, you should now be able to reach devices devices on the LAN in Office B from Office A, and vice versa.