F5F Stay Refreshed Power Users Networks Issues with OpenVPN loading on a network share.

Issues with OpenVPN loading on a network share.

Issues with OpenVPN loading on a network share.

G
Gatoscrim
Junior Member
Find
39
02-14-2016, 04:22 AM
#1
OpenVPN is active on your PFENSE system and works well from an external location. Speed tests show solid performance—250/250mbit on the laptop and 900/900mbit on the server. However, file transfers over the VPN drop to about 11/15mbit when using OpenVPN, which suggests a bottleneck. It’s possible that enabling "force all traffic" through the VPN is affecting throughput, even though you’ve turned it off previously. Testing didn’t resolve the issue. Regarding the "force all traffic" setting, activating it likely forces the OS to prioritize VPN traffic, but you may need to adjust firewall rules or network settings on the client side to ensure proper routing and reconnection behavior.
Reply
Reply
G
Gatoscrim
02-14-2016, 04:22 AM #1

OpenVPN is active on your PFENSE system and works well from an external location. Speed tests show solid performance—250/250mbit on the laptop and 900/900mbit on the server. However, file transfers over the VPN drop to about 11/15mbit when using OpenVPN, which suggests a bottleneck. It’s possible that enabling "force all traffic" through the VPN is affecting throughput, even though you’ve turned it off previously. Testing didn’t resolve the issue. Regarding the "force all traffic" setting, activating it likely forces the OS to prioritize VPN traffic, but you may need to adjust firewall rules or network settings on the client side to ensure proper routing and reconnection behavior.

Reply
Reply
D
destruc7
Member
Find
72
02-14-2016, 06:45 PM
#2
On my 4-core board I see openVPN running but only using one CPU core. It might be the same problem. Pushing all traffic through the VPN could be draining that single core, causing delays.
Reply
Reply
D
destruc7
02-14-2016, 06:45 PM #2

On my 4-core board I see openVPN running but only using one CPU core. It might be the same problem. Pushing all traffic through the VPN could be draining that single core, causing delays.

Reply
Reply
L
Lennyboy1603
Junior Member
Find
13
02-14-2016, 07:53 PM
#3
If the situation matched, the CPU would be locked at 100% on at least one core, indicating a performance of around 1.9ghz. However, this isn't happening. At 1.6/2mb/s, the usage stays at 9%. Keep in mind this processor uses AES-NI. Also, I don't have an option to force all traffic, which means I only tested it and it didn't affect anything. By the way, using "force all traffic" results in identical CPU usage whether it's on or off—likely because the workload is minimal.
Reply
Reply
L
Lennyboy1603
02-14-2016, 07:53 PM #3

If the situation matched, the CPU would be locked at 100% on at least one core, indicating a performance of around 1.9ghz. However, this isn't happening. At 1.6/2mb/s, the usage stays at 9%. Keep in mind this processor uses AES-NI. Also, I don't have an option to force all traffic, which means I only tested it and it didn't affect anything. By the way, using "force all traffic" results in identical CPU usage whether it's on or off—likely because the workload is minimal.

Reply
Reply