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

SSLVPN not routing to RED network.

I have users connect with Sophos SSL VPN client. They can access any resources at the data center (where the XG resides), but are not able to access any resources at remote locations (connected to the DC via Sophos REDs).

I do not have any static routes defined for the remote networks, as the RED connection appears to take care of that.

Any ideas on what I can try next.

Sophos XG210 17.1.1 MR-1

XG Diagnostics:
Route Lookup 10.10.2.10 - 10.10.2.10 is locations on the reds1, 10.10.2.10 is not behind a router.

Sophos-UnableToSSLVPN_to_REDSite.pdf

This thread was automatically locked due to age.

0 LuCar Toni over 7 years ago

Do you have the RED Network in Permitted Networks in SSLVPN?

Can you perform a Dump on XG to see, what is happening?
Cancel
Vote Up 0 Vote Down

Cancel
0 Derek Lechner over 7 years ago in reply to LuCar Toni

Attached is the tcpdump, I tried to get it to output to a file, but after 20 minutes couldn't get it to work.

In the tcpdump scenario, I tried to bring up the web page of a device at 10.10.2.2.

Yes the RED network 10.10.2.0 /24 is in the Permitted Network Resources of the SSLVPN.tcpdump.pdf
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 7 years ago in reply to Derek Lechner

From XG site, everything looks fine.

So i assume, RED is routing the packet correctly, there could be 2 Reason, the ping is not working.

1. Ping gets to the Client on RED site, but ping is blocked.

2. ping gets to the client but the client has no route back or uses another route onsite back and the packet never arrives.

Can you perform a wireshark dump on the client on RED site?
Cancel
Vote Up 0 Vote Down

Cancel