![]() the assigned IP 10.212.134.200 or 172.20.0.1 despite trying several combinations of firewall policies. I can succesfully ping 192.168.12.0/24 from Site2 with no issues and access any resources - as expected as a VPN Client of Site1.īUT I can't ping anything from Site1 to Site2 e.g. No static routes for VPN or Firewall Policies SSL VPN Client connected to Site 2 - assigned SSL VPN IP 10.212.134.200 It also supports FortiToken, 2-factor authentication. ![]() Your connection will be fully encrypted and all traffic will be sent over the secure tunnel. SSLVPN allows you to create a secure SSL VPN connection between your device and FortiGate. ![]() SSL VPN Server, SSL IP VPN Pool: 10.212.134.200 - 10.212.134.210įirewall Policy (ssl.root) to (lan) allowed FortiClient App supports SSLVPN connection to FortiGate Gateway. ![]() I have setup a FortiGate 40F as a SSL VPN Client behind a StarLink CGNAT connection to a FortiGate 40F on a normal public IP connection, because StarLink is problematic with IPSEC VPN and I wasn't able to get dialup NAT-T to work. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |