Quote from: Zapad on February 03, 2026, 11:11:47 AMja, habe ich.
Ich habe Fritzbox mit exposed host und Bridged, gesamt 4 IP 2x ip4 und 2 ip6.
habe 2 Gateway Gruppen mit Ausfall Option, aber kein Richtlinien basiertes Routing für wireguard.
ddns läuft über Exposed Host, und darüber greife ich auf Wireguard.
Habe jetzt weiter expirementiert es läuft in 2 Versionen:
1x Status Typ > kein, Zustandrichtlinie > Standard
1x Status Typ > Status behalten, Zustandrichtlinie > Interface
mit anderen Optionen läuft es nicht.
Quote from: k0ns0l3 on February 11, 2026, 01:23:01 PMHallo Community,
Ist die Upgrade auf 26.1 mittlerweile reibungslos oder gibt es immer noch Probleme.
Danke für Info
Lg
Quote from: JamesFrisch on February 13, 2026, 09:06:36 PMShameless plug for a little script I wrote.I looked at your script quickly and my observation is that it is completely decoupled from OPNsense logic to update the IPs when the WAN connection gets established. Why would I schedule a script with cron?
I first wanted to edit ddclient to make it more suitable for working with deSEC and OPNsense, but soon came to the conclusion that ddclient is too big and bloated.
So I wrote a little script:
https://github.com/jameskimmel/deSEC_DynDNS
Hope you guys like it, give it a try.
<174>1 2026-02-15T16:48:16+01:00 opnsense.network.local httpd 67053 - [meta sequenceId="39454"] [ssl:info] [pid 38425:tid 56393967149056] AH01914: Configuring server sub.domain.tld:443 for SSL protocol
<174>1 2026-02-15T16:48:16+01:00 opnsense.network.local httpd 67053 - [meta sequenceId="39455"] [md:debug] [pid 38425:tid 56393967149056] mod_md.c(1136): AH10113: get_certificates called for vhost sub.domain.tld.
<174>1 2026-02-15T16:48:16+01:00 opnsense.network.local httpd 67053 - [meta sequenceId="39456"] [md:debug] [pid 38425:tid 56393967149056] mod_md.c(1230): AH10077: sub.domain.tld[state=0]: providing certificates for server sub.domain.tld
<174>1 2026-02-15T16:48:16+01:00 opnsense.network.local httpd 67053 - [meta sequenceId="39459"] [ssl:debug] [pid 38425:tid 56393967149056] ssl_util_ssl.c(451): AH02412: [sub.domain.tld:443] Cert matches for name 'sub.domain.tld' [subject: CN=sub.domain.tld / issuer: CN=R12,O=Let's Encrypt,C=US / serial: xxx / notbefore: Nov 17 14:02:36 2025 GMT / notafter: Feb 15 14:02:35 2026 GMT]
<174>1 2026-02-15T16:48:16+01:00 opnsense.network.local httpd 67053 - [meta sequenceId="39460"] [ssl:info] [pid 38425:tid 56393967149056] AH02568: Certificate and private key sub.domain.tld:443:0 configured from /usr/local/md/domains/sub.domain.tld/pubcert.pem and /usr/local/md/domains/sub.domain.tld/privkey.pemQuote from: albb0920 on Today at 03:33:44 PMI hope I understood your question correctly.
Temperature sensor measurements are exposed through sysctl,
I haven't figured out how these can be wired to OPNsense dashboard though.Quoteroot@usb:~ # sysctl -a | grep aq | grep phy_temperature
dev.aq.1.phy_temperature: 46
dev.aq.0.phy_temperature: 42