SonicWall Cloud Edge does not limit the number of tunnels that can be connected to a single gateway, so in case you only have one gateway in a particular network, but your company's infrastructure consists of a hybrid environment (a mix of different on-prem and cloud-based resources) , then you can interconnect them.
If the two sites are both tunneled to your SonicWall network, you can enable the two to communicate, regardless of their location or dependency so that both sites will have a full and secure line between them.
Please follow the steps below:
IPsec based connections
Ensure both tunnels are route-based tunnels; that is, they do not depend on a specific internal subnet to create a handshake between the sites, but a route is configured on each device’s separate Route Table indicating which subnets to forward into the tunnel.
On the Management Platform, set both tunnel’s “Gateway Proposal Subnets” and “Remote gateway Proposal Subnets” to ANY (0.0.0.0/0). This may make the tunnel go down! Please make sure the device you are using supports route-based VPN. This means the tunnel is set up to 0.0.0.0/0 and a route is added separately.
Make sure the Routes Table on the SonicWall side has all of the routes of all of the sites configured (Network/ Route Tables) so in case you had them defined within the tunnel module, instead you need to add them here.
Click Add Route and add the routing to the internal LAN subnets that are behind each tunnel.
After you are done, click Apply Configuration.
Navigate to the first site's (labeled Site1) routing table, and in addition to the route that indicates all subnets (usually 10.255.0.0/16) to go through the Site to site tunnel, add a route dictating all traffic that goes to the second site's LAN subnet as well.
Navigate to the second site's (labeled Site2) routing table, and set up a static route indicating both the LAN subnet and Site1’s LAN subnet to go through the IPSEC Site-2-Site tunnel.
WireGuard based connections
In order to establish a connection from one resource to another, you'll need to reinstall the connector, as the default installation (Accessor mode) does not allow it.
# Locate the WireGuard packages (the output of this command is the full package name) dpkg -l | grep wireguard # Delete all packages found that are associated with WireGuard (replace pkg with the output from the previous command) apt-get remove --purge pkg
CentOS # Locate the WireGuard packages (the output of this command is the full package name) \ yum list installed | grep wireguard # Delete all packages found that are associated with WireGuard (replace pkg with the output from the previous command) yum remove pkg
Once you successfully removed the files mentioned in the commands above, reboot the machine and execute the connector installation script (the curl command that you copied from the Management Platform).
When you reach the 4th step, choose NO (n), which will prevent accessor mode installation.
Proceed with the installation. Make sure to select YES (y) for both IP Forwarding and Routing all traffic.
Open the route table of the network in which the WireGuard connector is installed (usually your router or firewall).
Configure a static route dictating all traffic from your SonicWall LAN subnet (10.XXX.0.0/16) to go through the IP of the machine that hosts the connector.
Open the terminal of the machine that hosts the connector and execute the following command:
# Temporarily shut the connector down wg-quick down wg0
# Open the connector's route table. vi /etc/wireguard/wg0.conf
# Enter the subnets of the resources you'd like to communicate with each other set AllowedIPs = , ,< Site 2 Subnet>
# Turn the connector up wg-quick up wg0
# Make sure that the desired change has taken place
CAUTION:Before you configure a second tunnel, make sure that the remote network's subnet does not overlap with the existing network's subnet. Once the two tunnels are up and running, you'll be able to set up a communication line between the two sites.