Sophos has been making great progress in maturing the Sophos XG platform to the point where it is now a serious contender for deployment instead of the more established Sophos SG (UTM) platform.

There is no rush to migrate your established Sophos SG deployments, as Sophos has stated that it is dedicated to supporting Sophos SG for years to come. But newer features on Sophos XG are making it more compelling to shift.

If you have many Sophos SG devices, there will be some level of cross over as your environment moves from the Sophos SG platform to the Sophos XG platform. One key concern is the compatibility of site-to-site VPNs between both platforms.

I have written a number of articles on how to build a private WAN over the Internet with Sophos SG SSL site-to-site VPN tunnels (See A Simple Guide to Deploying a Site To Site VPN Using Sophos UTMs, and How to Configure Multiple Site-to-Site SSL VPNs with Sophos UTM). It is a great technology if you have an environment with NATs and dynamic IP addresses.

In this article, I am going to cover setting up an SSL VPN tunnel between a Sophos XG and a Sophos SG device. One would have hoped that they would just seamlessly integrate with one another, but they do need to be configured a specific way to work.

One-way relationship

The two platforms can be connected by SSL site-to-site VPN, but only if the XG is the server and the SG is the client. The other way around does not work, despite my efforts. This may change going forward but this was the case as of July 2017 with SFOS 16.06.6 MR6 and SG 9.502-4 .

Configure Sophos XG VPN Settings (Server Side)

Let’s start off by setting up the XG as this is the side that will receive the connection attempts from the SG side. This is the “server side”.

  1. Select Configure | VPN | Show VPN Settings | Override Host
  2. Specify the XG’s public IP address if there is no public DNS in use

Create the VPN Connection Server

SSL VPNs are easy to deploy because all of the server and client configuration is contained in a single configuration file that simply needs to be imported on the client side.

  1. Go to Configure | VPN | SSL VPN (site-to-site) | Server | Add
  2. Provide a Name
  3. Specify the Local (XG side) network
  4. Define and specify the Remote (SG side) network and click Save
  5. Download the Config File for deployment on the SG later

Create the Sophos XG Firewall Rules

The VPN establishes the connection between the two firewalls, but without rules to explicitly allow the traffic to flow between the sites, no traffic would be allowed on either side. To configure two basic rules to allow full bi-directional communication between the two sites:

  1. Go to Protect | Firewall | Add new Firewall Rule | User / Network Rule
  2. Specify the following in the rule:
    • Name
    • Source Zone: Any
    • Source Network: UTM Internal 
    • Destination Zone: Any
    • Destination Network: XG internal
    • Uncheck match Known Users
  3. Click Save
  4. Add new Firewall Rule | User / Network Rule
  5. Specify the following in the rule:
    • Name
    • Source Zone: Any
    • Source Network: XG Internal
    • Destination Zone: Any
    • Destination Network: UTM Internal
    • Uncheck match Known Users
  6. Click Save

Configure Sophos UTM VPN Settings (Client Side)

Next, we will configure the Sophos SG client to connect to the Sophos XG server. We start by importing the configuration file that was generated by Sophos XG.

  1. Go to Site-to-Site VPN | SSL | Connections | + New SSL Connection
  2. Select Client
  3. Upload the configuration file
  4. Uncheck the box for Automatic Firewall Rules (this does not work)
  5. Click Save

Configure the Sophos UTM Firewall Rules

Sophos XG has already been configured to allow the traffic, but the Sophos SG UTM needs a similar ruleset.

  1. Go to Network Protection | + New Rule
  2. Specify the following in the rule:
    • Source: UTM Internal
    • Destination: XG Internal
    • Allow
    • Advanced | Log Traffic
  3. Turn on the Rule
  4. + New Rule
  5. Specify the following in the rule:
    • Source: XG Internal
    • Destination: UTM Internal
    • Allow
    • Advanced | Log Traffic
  6. Turn on the Rule

You can now check the status of the VPN by going to Site-to-site VPN.

You should see that it is connected but that the source and destination subnets do not show up like you would expect them to. If you compare the image to a Sophos SG to SG tunnel, the subsets on either end are shown.

On the Sophos XG side, you can see the status by going to VPN | SSL VPN (site-to-site) | Server.  The connection should look as follows:

Traffic is now able to flow between the two sites. The firewall logs on either side show this as the counters on the Sophos XG are updated.

Reporting on both Sophos SG and Sophos XG

Now that both sites are connected via a site-to-site VPN, you can install a Fastvue Sophos Reporter server on either network, and forward both Sophos UTM and Sophos XG web filtering logs to it for centralized consolidated web usage reporting. And yes, Fasvue Sophos Reporter supports both XG and SG platforms on the same deployment.

Conclusion

Traditionally, one would configure the “head office” as the server and the “branch office” as the client, but it is not a requirement.

Site-to-site VPNs between Sophos XG and SG platforms is definitely possible, just be mindful of the required client-server direction. Alternatively, you could also connect the two platforms together using IPSEC tunnels, but I’ll leave that for another article.