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

NAT or VPN SSL problem??

Hi everyone, I have this problem:

I want to forward traffic from the outside the local network to the private ip of a PC connected via vpn ssl (10.242.2.x)

So I created a DNAT and packet filter rule:

DNAT:
any to public ip1 / port tcp1 FORDWARD TO user_vpn_ssl1 / port tcp1
PACKET FILTER RULE:
allow any TO user_vpn_ssl1 / port tcp1

Using a program that creates a server listening in the the port tcp1, I do not see any connection.

Instead, if I try the connection from a computer in the internal LAN or from another client ssl vpn, it works, I see the connection to port tcp1.

In both attempts, in the firewall log I see that packets are forwarded properly to the ssl vpn client.


This thread was automatically locked due to age.
Parents
  • Perhaps if you use the Internet IPv4 address in stead of any it will be a little "better" but you are actually sending all internet traffic over the VPN either way...

    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

Reply
  • Perhaps if you use the Internet IPv4 address in stead of any it will be a little "better" but you are actually sending all internet traffic over the VPN either way...

    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

Children
No Data