Ad Schellevis

Currently there's don't seem to be another/better solution to fix this, the backend doesn't know the language (and assumes EN) and the `xx_noop` isn't supported which would flag for translation...

Well just wait for your pull request with suggestions then….

I'm not sure what the downsides are for using `rack` (if any), as this also doesn't influence everyone and the freebsd defaults are the same, we could also opt for...

I'll put it up for discussion here, it certainly doesn't sound like a bad idea, just not fully sure about an automatic default yet.

reverse proxying / web application is likely the most common use-case on our end at the moment, changing the default would be relatively easy, adding another toggle somewhere else then...

Which is mostly webservers (reverse proxies in our case).... openvpn is hardly used in tcp mode, IPsec doesn't use it either. A tunable is likely the best place in my...

> 25.7.9 is for example not specifically made for surety reason, seems a general update including some bugfixing In community releases you can almost always be certain these are not...

Sure, this is also one of the reasons why our business edition exist, to ease the operation. Eventually everything costs time (and money), when time is less problematic than money,...

This is a duplicate of https://github.com/opnsense/core/issues/6486 and cause by missing target addresses, I made an effort some years ago to implement it (https://github.com/opnsense/core/commit/362b08622a9f7da00cd8e701f421b8c063a44010), but since the protocol is a requirement...

@MiceMiceRabies I had some additional inspiration, can you try https://github.com/opnsense/core/commit/75e67641305488c33f798ee6aba192cda334d809 ? You can patch your current system using: ``` opnsense-patch 75e6764 ``` We likely keep this change on the master...