Slow WAN after upgrade

[Supermule]

Wait a few days until people return with test results on Iperf to verify.

[jaybowee]

Ok so I gave it a few days and decided to give it a try. Upgrade and clean install. Still the problem is there. I don't know what to do but to either stay on 20.1.9 or give pfsense a try.

[mother-64]

To me this looks like a core/kernel/driver issue, so if you have some time to kill I would definitely try pfsense 2.4.x release (based on FreeBSD 11.3, so it will probably work) *and* the dev 2.5.X dev version based on FBSD 12.1. If you get your usual speed using the 2.5.x, it would probably mean the problem comes from the modification introduced by HBSD in opnsense.

https://docs.netgate.com/pfsense/en/latest/releases/versions.html

[franco]

Or use 20.1 and keep cool while we figure the bugs out in FreeBSD 12 where they actually are.

[jaybowee]

This is most likely due to FreeBSD 12. However since this was introduced in July, it's seems a "bug" reducing WAN throughput from 1gb to 518 mbps would be one of your top priorities. 

[mimugmail]

You are invited to jump in and help This is a community project

[franco]

This is most likely due to FreeBSD 12. However since this was introduced in July, it's seems a "bug" reducing WAN throughput from 1gb to 518 mbps would be one of your top priorities. 

Sooner or later people will realise that we do not write FreeBSD code and if FreeBSD barely makes this a priority this top priority has nobody who will quickly deal with the issue despite all the friendly nudging in a sub forum of a related downstream project.


Cheers,
Franco

[rungekutta]

This is most likely due to FreeBSD 12. However since this was introduced in July, it's seems a "bug" reducing WAN throughput from 1gb to 518 mbps would be one of your top priorities. 

Sooner or later people will realise that we do not write FreeBSD code and if FreeBSD barely makes this a priority this top priority has nobody who will quickly deal with the issue despite all the friendly nudging in a sub forum of a related downstream project.

I can see that it must be very frustrating to field constant questions on issues that are not related to OPNsense as such but rather the upstream OS. And particularly if the interest from FreeBSD to fix them is only lukewarm at best, as you imply above.

However I think one must also realise that for most users, myself included, OPNsense is not so much a "downstream project" to FreeBSD, as it is an appliance with a very specific purpose. It is actually of no consequence to me whether it is based off FreeBSD, Linux, or something else as long as it delivers on the features, configurability, performance and level of security that I need. I spend 98% of the time that I manage OPNsense in the web GUI. I would hazard a guess that vast majority of OPNsense users are the same.

Given what you say about FreeBSD above, and how long this has been going on, I think it actually raises questions on the longevity and viability of FreeBSD as base OS? Hopefully I'm wrong..!

[rungekutta]

PS. I’m still on 20.1...

[mimugmail]

You are wrong, cause you cant even imagine how many months it would take to port it. Just stick to 20.1 for a while ... There are no security risks.

[franco]

For the vast majority of FreeBSD users 12.0 was good enough. One has to think 12.1 is already an improvement and 12.2 is on the way now as well which we will target for 21.7 (explicitly not 21.1 in case it is the same or worse). In particular, "iflib" is causing most of these OPNsense-bound worries and for FreeBSD it was worth integrating in version 12 thus why would we debate how it's not a right fit in the first place? It's not our decision to make and looking forward is the only possible solution from our perspective... so there will be FreeBSD 13 at some point anyway and we will tag along for the ride because we cannot and will not start our own OS.


Cheers,
Franco