Guest User!

You are not Sophos Staff.

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

Remote Access - can connect but cannot reach some ip

Hi, I setup up an SSL Remote access and I can connect and browse (by ip or name)  all my windows devices and UTM9 admin portal on my lan  using openvpn app from my android smartphone.

On my lan there is a linux machine (asterisk) but I cannot ping nor browse it from the smartphone.
The firewall on this machine is off.(I can ping it from inside my lan)

All the machines are on the same network 192.168.1.x.

The only difference is that asterisk use a different gateway  than  UTM, but the same primary DNS.
This machine is registered in the DNS

How can I reach it?
What i have to configure on UTM?

My setting are:

UTM is at 192.168.1.100

Domain controller and DNS at 192.168.1.2

All windows machines have 192.168.1.x , gateway 192.168.1.100, DNS 192.168.1.2 , proxy 192.168.1.100:8080

Asterisk at 192.168.1.99  gateway 192.168.1.1 and DNS 192.168.1.2 (this is the machine I cannot reach using VPN)

Thank you in advance for any answer.

Roberto



This thread was automatically locked due to age.
Parents
  • That's a simple routing  problem: the asterisk server does not know how to answer to packets from the SSL VPN Pool, so he sends his answer to his default gateway.

    But this one also doesn't know the way, so the traffic s dropped.

    So the clean way is to set up a route on either your asterisk server or its gateway:

    SSL-VPN Pool (default 10.242.2.0/24) via gateway 192.168.1.100.

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Reply
  • That's a simple routing  problem: the asterisk server does not know how to answer to packets from the SSL VPN Pool, so he sends his answer to his default gateway.

    But this one also doesn't know the way, so the traffic s dropped.

    So the clean way is to set up a route on either your asterisk server or its gateway:

    SSL-VPN Pool (default 10.242.2.0/24) via gateway 192.168.1.100.

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Children
No Data