@nirmalts said in pfSense becomes sluggish at times: for a window of 2-3 hrs everyday. Your check list is quiet complete. Even the most smallest pfSense capable devices like these can crank out several tens of megabits per second, nearly always limited by what happens upstream. The solution is easy : don't use VPN suppliers during that observed windows. Remember : they all work with the "best effort" methods. And it seems that legal video streaming services ran out of 'not seen' content so the less legal providers are even more used. Which explains the massive "VPN" usage and it's consequences.

Of course mark also don't add/remove routes or don't pull routes. Otherwise you will kill the lan connection (don't understand why but it does).

That custom option was something that was leftover from trying on my own, I suspected the Local Networks box was the proper place where it supposed to be anywhere. I didn't set the 10.0.8.0/24 as a remote network in the branch office but upon taking your suggestion it now works. Thank you so much!

bump

@Rico said in No internet Access with OpenVPN after upgrading to pfsense 2.4.5 release: erver/Clien thanks!! all good now

We finally found the problem! It was a previously misconfigured remote network subnet mask (/4 instead of /24 - probably a typo because this was done rapidly during a night) on the pfsense client that remained in the routing table. Somebody corrected the client's configuration afterward but probably forgot to restart the tunnel to update the routes. And it explains very well why some destinations were treated differently than others.

I work remotely but it is important for me that my ID is in another country. For myself, I found a great way out veepn [link removed] is an excellent VPN that works without interruptions. I have been using it for 3 months and no problems were found.

@hawkbh. hi guys i have resolved it. thak you!

So, change the server did the trick. @BuiltOnSelfSuccess said in Slooooooooooow connectivity: MY VPN provider does not impose any bandwidth restrictions. Are your still certain ? "impose" = willingly applying bandwidth restrictions is one thing. If a server is very popular, bandwidth will go down. It could even be de POP just before there server, something they do not control ...

@Rico said in OpenVPN Local Networks vs Remote Networks: Sure for 2 or 3 Sites no big deal, but say you have 50 Sites and want to add one more....happy for any parameter you need to touch only once and push. ;-) -Rico Ok, that makes sense. So in the example in the link above, if you put all networks in the Local Networks field, will one of the sites add a route for its own LAN network?

There may very well be something that needs to be addressed in the AWS VPC settings, however, I am unfamiliar with the platform. Short of a misconfig that I'm missing, an AWS VPC setting or something happening on the client-side, it's just troubleshooting at this point. I PM'd you.

@Gil said in Removing a CA key: That does appear to be a bit of a bug. I'll manually edit the xml. Thanks. Fix: https://redmine.pfsense.org/issues/10509

Point taken. As I said, I can always include that within the CN for each P2P router.

Ahhh I see....meant if you really care about security I suggest you not to install any custom/unofficial pfSense packages via the commandline. Only use the official repository. -Rico

I want to solve my own issue. After hours and hours of testing things out, the problem was rather simple. I just had to go to the OpenVPN Server settings -> Tunnel Settings -> IPv4 Local network(s) and just add my WAN network to the list. I guess that's why it never showed up in the logs. Because it wasn't ever blocked by the firewall. The VPN-users just never had any access to it I still can't login via my LAN-net IP. Not sure why that doesn't work, still. but it works via HAproxy. So maybe it's an http/https issue

OK, so there is no way. Thanks again!