Results 1 to 1 of 1
  1. #1
    Master Untangler
    Join Date
    Dec 2018

    Default IPsec VPN using IKEV2 with multiple subnets bug?

    As I have been posting previously I have been trying to get Untangle to play well with a USG exposing multiple subnets over a single tunnel.

    Here's the other thread -

    While I finally got all of the tunnels to pass traffic without having to restart the Untangle IPsec service it doesn't work the way I'm pretty sure it should.

    While on the USG I can create a single "Network" and expose the and networks to it in a single IKEv2 tunnel I can't do the same with Untangle for the and subnets on the USG.

    This works on the USG:

    This doesn't work with Untangle:

    Instead in order to get all subnets to be able to communicate I have to make IKEv2 tunnels for EACH subnet combination that I want to communicate.

    Like this (First line description should be Untangle 5 --> USG 15 but I typo-ed):

    I tried multiple combinations of setups before finding out that this works including using multiple IKEv1 tunnels on the Untangle side as well as on the USG side and it didn't work.

    I don't understand why the IKEv2 tunnels with all subnets included won't work that I was trying in my other thread but hopefully this helps someone else in the future as I have spent probably 12 hours playing with this over the long weekend now since I'd like to run Untangle at work as I really like it over the USG but we have one office that has to stay on the USG for now.

    If someone wants to look into the issues I can get them into both systems but as of right now it seems to be a bug of some kind.
    Last edited by jlficken; 05-27-2019 at 06:43 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

SEO by vBSEO 3.6.0 PL2