FortiClient VPN SSL VPN
-
@jf-2600hz
Routes can be added in System > Routing. You may have to add a gateway before you can use it for routing.But still not clear, why you should add routes to pfSense. When you establish a VPN from a device behind pfSense, all needed routes for the VPN gateway should be set on the devices itself. This traffic should never pass pfSense. Only the outer VPN packets pass the router.
-
Im really not sure at this point. because my vpn works, its just certain links (URLs) that do not work now. I will keep on digging
-
Mmm, the only way this makes much sense would be if you're using pfSense itself as the VPN client? But the way this reads you're connecting to the remote Fortinet server from a client behind pfSense? In which case only some local subnet conflict could really be doing anything.
Steve
-
@stephenw10 Hi Steve, that is correct. My PC is behind the pfSense, and to connect to my work applications I need to connect to my FortiClient. Would I need to set up an OpenVPN in psfense to replace the forticlient by using its credentials ?
Should I be modifying my local subnets ? My network engineer was saying that I need to vpn dynamic routes to propagate in the pfsense which I do not see them
-
No, you should be able to connect the FortiClient on the PC through pfSense to the external server. pfSense will just pass that encrypted traffic and cannot affect it.
I would expect it to 'just work'. Routes sent to the client from the server only affect the client. If it's refusing those routes for some reason it's probably some local conflict. Again though pfSense has no affect there.
Fortinet SSL VPN does not appear to be OpenVPN so you cannot connect to it from pfSense directly.Steve
-
@stephenw10 Ok I understand. Any hints on what type of local conflict could be causing the issue.
-
What is your local subnet on LAN?
What subnets are you unable to connect to?
Look for a conflict. So, for example, if your LAN is set to use a /16 subnet mask you would be unable to connect to anything remotely that fell within that.
Your LAN should not use /16 but it's a relatively common setup error.Steve
-
@stephenw10 I had set up a 192.168.99.1/24 and then tried 192.168.1.1/24 same affect.
When I connect to my Forticlient I get IP Address
10.212.134.182 -
Ok, well no conflict there directly. What other routes are passed to the client when it connects though?
What addresses are you trying to reach that fail?Steve
-
@jf-2600hz
The clients routing table can give more details.
In Windows shell runroute printand provide the output.
-
Not sure what I did, but I accidently locked myself out, so I redid a new build and everything is working fine now. Thanks for your help !!
