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

SSL VPN Config - Unable to reach other networks?

I've successfully setup my first SSL VPN for remote access into my network, I can immediately access the listed first subnet, my internal infrastructure.

However, I also want to be able to access two other subnets, they're listed in the SSL VPN profile. But unreachable when connecting.

From my research, I think I'm missing an SNAT? rule or some other form of network management.

The two additional subnets ARE reachable (ping) via the UTM, they're handled by a TP-LINK Omada setup which is connected to the UTM. Nothing fancy there, no firewalls etc. The UTM itself can ping IPs in those subnets without issue.

Wondering if someone can help me point in the right direction here?

Thanks!

Range Desc. Gateway Reachable Via UTM (ping) Reachable Via SSLVPN (ping)
192.168.90.0/24 Personal LAN TP-LINK, 192.168.90.1 yes no
192.168.10.0.24 Persoanl Infra TP-LINK, 192.168.10.1 yes no
10.16.3.0/24 Server Infra UTM. 10.16.3.1 yes yes
10.242.2.0 SSL VPN POOL UTM. 10.16.3.1 yes yes



This thread was automatically locked due to age.
Parents
  • you need the SSL-VPN-IP-Range within the PT-Link-VPN too.

    Or you masquerade/SNAT the SSL-VPN-Traffic with an IP allowed within TP-Link-VPN.


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply
  • you need the SSL-VPN-IP-Range within the PT-Link-VPN too.

    Or you masquerade/SNAT the SSL-VPN-Traffic with an IP allowed within TP-Link-VPN.


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
No Data