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

XG - SNAT / IPSec not working...

Hi all,

 

I have "inherited" an existing network consisting of several branch offices and a HQ/Datacenter.

All locations are connected via a MPLS network. All clients uses .1 as GW on their local network for the MPLS router. The MPLS network has a null-route (hope it is the right term), so all non-MPLS network traffic is routed to .2 on the HQ location where a central firewall handles the traffic (VPN connections, publishing servers etc.). This firewall is due for replacement and I'm currently evaluating the XG. A requirement is IKEv2 support, so UTM is not an option.

I am brand new to the XG - started yesterday - and so far I have migrated networks, internal routing and published servers. That seems to work as expected.

IPSec site-to-site without NAT also seems to work and is so far quite easy to configure.

For a specific IPSec tunnel we only need outbound initiated traffic, and all traffic should be SNAT'ed via a single IP (x.x.x.9). I have no control over the remote VPN settings, so my goal is to duplicate the setup from the existing firewall.

The IPSec tunnel phase 2 is defined with the local network as x.x.x.8/30 ("NAT network") and remote network is of-course the actual network. These settings are directly migrated from the legacy firewall. The tunnel is UP but currently there is no traffic flowing. I did let the XG autocreate the FW rule, which seems like a full open tunnel between the two networks. I intend to restrict this later.

I tried configuring NAT in the VPN rule and also in the FW rule (MASQ) but still no traffic is passed.

Can anyone guide me in the right direction and explain how this should be configured (and debugged if nescessary)?

 

 

 

 



This thread was automatically locked due to age.
Parents Reply Children
  • Hi,

     

    Just to be sure, you need to build up the SA with this /32 Object. This is some kind of limitation in the IPsec Handling of XG.

    XG cannot handle the SNAT otherwise in IPsec. 

    So basically you will do following:

    IPsec SA Localnetwork: /32 - Remote Network: /XX

    NAT to: Dropbox /24.

    This should work fine. 

    Do not forget, the other site have to reconfigure their SA to match your config. 

  • Hi Flosupport,

     

    I did read the article and that makes completely sense if my setup was identical, but it is not.

     

    /JP

  • LuCar Toni said:

    Hi,

     

    Just to be sure, you need to build up the SA with this /32 Object. This is some kind of limitation in the IPsec Handling of XG.

    XG cannot handle the SNAT otherwise in IPsec. 

    So basically you will do following:

    IPsec SA Localnetwork: /32 - Remote Network: /XX

    NAT to: Dropbox /24.

    This should work fine. 

    Do not forget, the other site have to reconfigure their SA to match your config. 

     

     

    Hi Lucar Tony,

     

    Thx. for explaining. That makes sense. Don't ask me why the old setup is made this way, but tomorrow we have to modify the tunnel to IKEv2 anyway, so I will have them change our network in the SA.

     

    I will reply when I can confirm if it is working or not!

     

    Cheers!

     

    /JP

  • LuCar Toni said:

    Just to be sure, you need to build up the SA with this /32 Object. This is some kind of limitation in the IPsec Handling of XG.

     

     

    It worked. I'm so grateful for your help. It was spot on! THX!!!