@netg8ter So you have to configure the switch for 802.1q VLAN before. Look here for details: Switch Overview Configuring the Switch Ports

@Gertjan said in OpenVPN server crashes when client closes connection: OpenVPN server and client version don't need t be identical, but, as they stated on the OpenVPN web site : recent 2.5.x OpenVPN version won't work with really ancient OpenVPN clients and vise versa. That's a valid point to consider this not a bug.

I found a solution! I reconfigured VPN to Server mode: Remote Access ( SSL/TLS + User Auth ) After that everything worked as it should. Perhaps my experience will be useful to someone

@Ghost-0 The "x factor" in this scenario is the other end of the VPN, if you don't control both ends. I believe OpenVPN uses only one CPU core. If a core in your router isn't being maxed out, then it's likely pfSense is not the bottleneck. ZFS is in general better than UFS but it's the file system so is unlikely to help with VPN throughput.

@hudri Yes, whatever port you're using. If you're running multiple services behind pfSense consider the forward all incoming traffic and configure the pfSense firewall accordingly. Some modems call this "exposed host" or "DMZ". Consider that UDP port 1194 is possibly not allowed on public wifi hot spots if you want to use that. You can configure your OpenVPN to listen on a commonly used port like 443. To go around such restriction I'm running two servers on my home pfSense. On on UDP 1194 and the other on TCP 587. The client is configured to automatically attend to connect to the second if the first doesn't response within 10 seconds. Note that OpenVPN over a UDP port is faster than TCP:

@p1ter Does this command work in the 2.6.0 version? Because for me, with command entered in advanced, the credential not validated.

@hr1sha Great that solved the issue, I am now getting the expected upload speed. I guess that means I have been limited by the iPhone hardware (like also @Rico suspected). I chose 256 encryption because I thought it is safer that 128, but after some quick research I guess 128 should be sufficiently safe (I guess).

@viragomann thanks for help. I tried so many things and nothing works. I solved it differently now. I connect direct to the client pfSense. I solved it differently now.

@viragomann said in AWS OpenVpn routing issues after update.: @swansense I'm wondering, what is auto-updating there. This version is out of date for more than two years. You should consider to upgrade it. However, I don't expect that an upgrade resolve your issue to be honest. Which route does OpenVPN intend to add? There should be a hint in the log. If not, maybe set a higher verbosity level. Possibly the route is overlapping your local network. Thank you. You were correct changing the release branch and updating fixed my issue

@SteveITS hey thanks Steve, will have a look at that too. Appreciate it!

@monkeh 0.1 millibit/sec? Yeah, that is a tad slow.

@philbio On the old desktop I installed the 2.7 version on today the CPU is a Intel Core i5-4570TE (2.7GHz) LGA1150, when I was doing a speed test the CPU guage in the gui never went above 10%

@harry63 Same issue here, have made several setting changes with no improvements.

@JKnott One other thing, it works fine with IPv6 over my LAN.

@viragomann What would you like to know about them? No vpn server subnat aint the default 192.168.1.0/24 or 192.168.0.0/24. As often as humany possible.

With DCO mode on Plus you can use traditional routing because of the way it's hooked into the kernel. It works more like a regular interface there instead of only using OpenVPN's internal routing.