This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Site-to-Site - XG "Home Base" with Ubiquity Security Gateway "Remote Sites": Cannot reach remote office subnets

Hello.

Myself (and a client of mine) currently utilize Sophos XG firewall at the 'main' location of an office/company.  We have several remote sites, each with a Site-to-Site VPN tunnel between the two locations.

Traffic can freely and without issue flow from the remote sites into the main site, and get responses back.  This behavior works.

However, we need to get the inverse working - from our main office to the remote offices.  This is currently not functioning.

From other resources and searches I've done, I've found that we need rules for the home base side of the network to reach out to the remote networks to permit that traffic.  However, we already have such a rule and the Policy Checker indicates that rule matches.  Traffic still, however, doesn't seem to get handed over the IPSec tunnel to the remote side at the moment.  If it were, the remote site would likely be responding.

The rule we've got that SHOULD be permitting our IT Management systems to go over is this:

... where MGMT is the "zone" for the IT Team's management systems and "Source Networks" of "IT" is the 10.1.4.0/24 subnet where they exist.

 

To my knowledge, the XG should be able to handle routing this traffic over the tunnel, however it doesn't seem to want to do that.

 

Where should I look next to try and debug this?  Do I need special routing rules or such entered to make the traffic actually go over the IPSec tunnel to the remote site?



This thread was automatically locked due to age.
Parents
  • Right-o, so five hours on the line with Sophos Support and we seem to have solved this issue...

    There were actually multiple things at play.  Firstly, the Remote sites had not established a tunnel for the 10.1.4 traffic yet; this could be due to nothing out on that end regularly reaching the 10.1.4 network.

    The second issue was APPARENTLY XG does NOT like PSKs with any types of symbols in them - exclamation marks were causing problems in the PSK that the client was using on the tunnel, so even when we were trying remote to reach to 10.1.4 at Home Base, we ended up having PSK mismatch issues; the issues were resolved when we redid the PSKs with no symbols in the password (but we increased the length SUBSTANTIALLY to account for the loss in entropy and bitstrength due to not having symbols).

     

    Once the PSK for the tunnels was fixed and the Remote tried to ping into the 10.1.4 traffic and subnet (and the 10.1.121 subnet) the individual tunnels all came online and data properly traversed the tunnel, and we were able to reach there.  However, DPD is going to cause some headaches even though Sophos Support suggested that we leave it online, because it's not regularly done that remotes ping to 10.1.4 to establish the tunnel.

     

    I may look into the Sophos documentation of an 'intermediate' subnet for NATting to NAT and then UnNAT so there's a single tunnel made for any remote and vice versa; that'll be its own headache and we have a few major projects at the client's locations before I can go and redo that with them.

Reply
  • Right-o, so five hours on the line with Sophos Support and we seem to have solved this issue...

    There were actually multiple things at play.  Firstly, the Remote sites had not established a tunnel for the 10.1.4 traffic yet; this could be due to nothing out on that end regularly reaching the 10.1.4 network.

    The second issue was APPARENTLY XG does NOT like PSKs with any types of symbols in them - exclamation marks were causing problems in the PSK that the client was using on the tunnel, so even when we were trying remote to reach to 10.1.4 at Home Base, we ended up having PSK mismatch issues; the issues were resolved when we redid the PSKs with no symbols in the password (but we increased the length SUBSTANTIALLY to account for the loss in entropy and bitstrength due to not having symbols).

     

    Once the PSK for the tunnels was fixed and the Remote tried to ping into the 10.1.4 traffic and subnet (and the 10.1.121 subnet) the individual tunnels all came online and data properly traversed the tunnel, and we were able to reach there.  However, DPD is going to cause some headaches even though Sophos Support suggested that we leave it online, because it's not regularly done that remotes ping to 10.1.4 to establish the tunnel.

     

    I may look into the Sophos documentation of an 'intermediate' subnet for NATting to NAT and then UnNAT so there's a single tunnel made for any remote and vice versa; that'll be its own headache and we have a few major projects at the client's locations before I can go and redo that with them.

Children
No Data