Messages

great!

useful

useful

where is code?

apcupsd and NUT work together without any issues. I use apcupsd alongside NUT because it provides features such as automatic shutdown of the OPNsense host and configurable battery thresholds.

Since the NUT configuration in OPNsense doesn't work properly, I'm using apcupsd alongside it.

nut.conf, upsd.conf, ups.conf ...etc configure not working

NUT includes the driver APCUPSD-Driver and it may tempt some users to use it.

From the thread I got the impression they were trying to install and run the standalone apcupsd alongside NUT which probably won't work.
There is an os-apcupsd plugin. Don't run that if you intend to run NUT and vice versa.

# opnsense-update -zkr 26.7-igc

Will the official patch be included in the next update?

Code Select Expand

$ curl -sv --connect-timeout 10 "https://s3.eu-west-1.amazonaws.com"
* Host s3.eu-west-1.amazonaws.com:443 was resolved.
* IPv6: (none)
* IPv4: 3.5.75.39, 3.5.67.235, 3.5.66.27, 3.5.71.89, 52.92.32.24, 3.5.67.45, 3.5.71.84, 3.5.74.68
*   Trying 3.5.75.39:443...
*   Trying 3.5.67.235:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* SSL Trust Anchors:
*   CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*   subject: CN=*.s3-eu-west-1.amazonaws.com
*   start date: Nov 14 00:00:00 2025 GMT
*   expire date: Nov  6 23:59:59 2026 GMT
*   issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M04
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   subjectAltName: "s3.eu-west-1.amazonaws.com" matches cert's "s3.eu-west-1.amazonaws.com"
* OpenSSL verify result: 0
* SSL certificate verified via OpenSSL.
* Established connection to s3.eu-west-1.amazonaws.com (3.5.75.39 port 443) from x.x.x.x port 33241
* using HTTP/1.x
> GET / HTTP/1.1
> Host: s3.eu-west-1.amazonaws.com
> User-Agent: curl/8.21.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 307 Temporary Redirect
< x-amz-id-2: xxxxxxxxxxxxxxxxx
< x-amz-request-id: xxxxxxxxxxxxxxxxxx
< Date: Tue, 14 Jul 2026 13:37:25 GMT
< Location: https://aws.amazon.com/s3/
< Content-Length: 0
< Server: AmazonS3
<
* Connection #0 to host s3.eu-west-1.amazonaws.com:443 left intact
 No issues here either, on both my OPNsense host and another computer.
v26.1.11

https://github.com/freebsd/freebsd-src/pull/2318

Is this patch included in OPNsense v26.7?

https://amnezia.org/blog/amnezia-vpn-no-connection-what-to-do

https://amnezia.org/blog/amneziawg-2-0-available-for-self-hosted

I've checked everything again, and I believe all of the settings are configured correctly.
There were definitely no issues up to version v26.1.8.
The issue started occurring after updating to v26.1.9.

- no wireguard group
- set(check) Disable routes

Before v26.1.9, everything was working normally. The only difference is that I had configured one OPNsense native WireGuard instance and one selective routing setup.

In v26.1.10, the OPNsense WireGuard tunnel still works properly even after a reboot, but the selective routing configuration does not work.

This is not an issue with the VPN server or the configuration file.

The issue also occurred in version v26.1.9

You cannot view this attachment.


You cannot view this attachment.


An error occurs on the WireGuard peer configured for selective routing, and it does not start after boot. If the service is restarted manually, it works correctly.

Currently, mullvad selective routing is configured to connect to only one server, and it is working correctly.

I would like to add several more countries to the configuration.

However, because the tunnel address is identical, it seems that only a single instance is being utilized.

After adding peer settings for another country, it appears that routing is performed only through the newly configured country's server, rather than the server that was originally in use.

Mullvad allows a maximum of five devices.

Is it possible to use multiple country endpoints simultaneously while using the same WireGuard private key?