Messages

[Netsh int tcp set global autotuning=normal]

I have to post here after some digging and blaming the OPS version.

The issue for me, was a configuration in windows on PC (Client).
At first I tried to connect using my phone with the same way and I managed to obtained the full speed.
So tried to test everything in windows environment.

Somehow the issue was relegated to the TCP global option that was disabled.
When run it to default: "Netsh int tcp set global autotuning=normal" The performance back to full speed.

Cheers!

I think this is something with the recent version.
2 weeks ago I noticed a slow connection from my end.

The connections is:  NAS > OpnSense > wireguard > Remote Client.
and the System is with i3-1215U that handle everything.

At First I though it's the NAS, but apparently this is something with OPS.
Iperf between the NAS > OPS I getting 2.74 GBytes.
Between OpnSense > wireguard > Remote Client I'm getting average of 53.0 MBytes |  44.5 Mbits/sec.

Before the update to 27.5.x I managed to received 200+ MB with Iperf and transfer files around 22mb/s with the same system and same configuration, nothing changed.
I also try to disable firewall, CrwordSec, IDS, IPS, change MTU, paly with offload settings and add some configuration to the Tunables.
Unfortunately nothing help to solve it.

I believe It's a deeper issue.

Wowwwww man!!!
this is insane, thank you for this sharing info. this is the issue I'm facing right now.

Any suggestion please?

[Manage everything from Opnsense]

Hello folks!
I'm new to OPNs and recently I finish install the OS.
Everything works lovely and I'm really satisfied.

My main goal to move to Opnsense was to protect my TrueNas server with revers proxy for Emby outside the network without opening ports while the traffic go through Mullved VPN AND make sure I can still access it from LAN/WG_VPN home.

I think of two options, and I really need help to decide which one is better or maybe hear another one better.

1.Manage everything from Opnsense - My OPNs using Bridge on all the LAN ports, So I thought to setup Mullved VPN only for the TrueNas port (port 3), then Install the HA proxy and configure it to work with the Emby port. But I'm not sure if it will impact the app connectivity for other apps like qbittorent with ports open.

2.Split the work - TrueNas allows to use wiregard and theoretically connect to Mullved and install the HA proxy on the OPS. Or maybe otherwise, Install the VPN from the OPS side and then configure with one of the apps from Truenas docker the revers proxy.

The things that is really important to achieve:
- Best secure way to get it done!

- Still able to access the NAS and his apps locally.

- To choose the best way to implement this in terms of troubleshooting in case I needed.

- To get the best performers. I personally think that running this OPNs will reduce no need stress from the TrueNAS.

What do you think?
I really like to hear your opinion.

Thank in advance!