Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

VPN to VPN rules

Hi all,

Given the state of the world, I'm trying to make some firewall changes to our setup, and I'm hoping someone can give me a bit of a steer.


We have a pair of IPSec VPN's running to Azure (which works fine)

We have a Remote SSL VPN for staff to dial into the office (which works fine)

What I'm trying to get working is an interlink between the two VPN configs so that staff can dial in from home, and then get to our Azure.

 

I've added the remote subnet to the IPsec ranges, and I'd thought it might be as simple as making a VPN<>VPN rule like so:

No dice though. If anyone could provide some insight as to how to diagnose where my config is failing me?



This thread was automatically locked due to age.
Parents Reply
  • I ran a packet capture, and got this little gem:

     

     

    Violation, Firewall. Just not sure why. It says rule 0, but there isn't a rule 0. I'm obviously missing something here. Rule 0 as I understand it is the default rule to drop if traffic doesn't match the rules in place right?

    So based on the premise that our Remote SSL works, and the IPSec's work, it would suggest that the fault is somewhere in the VPN <> VPN rule?

Children