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

IPSEC VPN Routing traffic between multiples sites

Hi,

We need to establish a multiple site to site IPSEC VPN with a XG86w as the HQ.

Both remote sites have a TELTONIKA RUT240 router.

I am able to ping from HQ both remote sites, and from each remote site the HQ, but can’t ping a remote site from another remote site.

 

In the XG86w I have in the local subnet of each tunnel the local HQ network and the local network of the other remote site.

 

On the TELTONIKA RUT240 side, running ipsec status we can see that both are installed.

I'm clearly missing something.

Any help would be appreciated.

 

Alexandre



Added TAGs
[edited by: Raphael Alganes at 3:26 PM (GMT -7) on 7 Oct 2024]
Parents Reply
  • You may try below and let me know if this works for you:

    example:

    On BO1 (TELTONIKA), IPsec tunnel should have

    - local subnet = A (its own local subnet)

    - remote subnet = B (local subnet of XG) and C (local subnet of BO2)

    On BO2

    - local subnet = C

    - remote subnet = A, B

    On HO, tunnel towards BO1

    - local subnet = B,C

    - remote subnet = A

    On HO, tunnel towards BO2

    - local subnet = A,B

    - remote subnet = C

    Then you should be able to ping host of subnet C (BO2) from host of subnet A (BO1)

Children
  • Hi,

    I've tried that also.

    On the TELTONIKA side BO1 or BO2 if I do this the router cannot establish 2 SA, only the BO1 to HO is established and the BO1 to BO2 SA can't be created, and in the HO/XG the connection stays in yellow state.

    So after reading on the TELTONIKA side on BO1 and BO2 I've created 2 tunnels one from BO1 to HO and another from BO1 to BO2.This is the only way to establish 2SA, and on the HO side I can see both connections and all green.

    Same as for BO2.

    So I believe that the current configuration matches the one you have illustrated.

    Thanks,

    Alexandre

  • Had quite a lengthy call with  , it turns out to be the bridge on LAN side of Tektonika router (on both BO1 and BO2) causing some inconsistent behaviour/issue. In all the debugging, BO1's connected client pinging BO2's connected client, the ESPinUDP packets seen egressing on SFOS towards  BO2. BO2 (BO1) has a bridge on its LAN side, seeing icmp echo packet but not forwarded towards the client of BO1. Similarly when BO2's client pinging BO1's client.

    Both BO1 and BO2 uses /29 subnets on its LAN; Later tried changing the subnet on BO1 to /24 and seen client of BO1 could ping BO2's client successfully, but client of BO2 could not ping BO1's client, again something skeptical in the bridged of BO1.

    Tried rebooting both BO1 and BO2, then ping from client of BO1 to client of BO2 is not placed into the tunnel by BO1.

    Suggested below tcpdumps to look at on BO1 and BO2 (Tektonika routers - both are very primitive routers withe basic implementation if IKE1 IPsec) to figure out what the issue could be while pinging from BO1 client to BO2 client or vice-versa; also suggested to use /24 subnet on bridge (LAN side) of BO1 and BO2

    tcpdump -ni wwan0 udp port 4500 or icmp | grep <client ip of BO1 or BO2>

    tcpdump -ni br-lan | grep <client ip of BO1 or BO2>

    Although SFOS has no issue in receiving ESPinUDP packets from BO1, decrypted packets seen on ipsec0 and sends out ESPinUDP packets to BO2.. below commands on SOFS gives out packet details:

    SFOS side tcpdump:

    tcpdump -n port 4500 or host <client ip of BO1 or BO2>

    tcpdump -ni ipsec0  host <client ip of BO1 or BO2> and icmp

  • After this call, I made a few more tests, and found the following.

    HO with a netmask of /24 and both BO1 and BO2 with a netmask of /29 doesn't work. Not sure why, but changed BO1 to a /24 netmask, and it worked.

    Also discovered that the TELTONIKA device was masquerading WAN output packets. Tried the netmask /29 with masquerading on and off and it didn't solve the problem.

    So, now now I'm using a mask of /24 on all networks and it's working as it should. I believe that's a TELTONIKA implementation problem.

    Thanks to Sreenivasulu Naidu for his help (and patience).