"Recent posts
#1
26.7 Series / Re: Critical PHP vuln: php2she...
Last post by moware - Today at 11:07:34 AMQuote from: tangofan on Today at 04:28:50 AMQuote from: nero355 on October 21, 2026, 10:16:23 PMJust updated succesfully! Thanks to all the people involved getting this fixed soo fast! :)
Indeed, it was great to get a fix so quickly. One small nitpick: The release version didn't change, e.g. to 26.7.7_1. Perhaps just an oversight in the heat of battle. Certainly something that can be presumably easily corrected, if necessary.
It's also a bit confusing that the UI in "System: Firmware" shows "Updated on: Wed Oct 14 04:15:27 CEST 2026" in the "Status" tab, which made me wonder whether the patch had been installed by the nightly cron-job at all.
Fortunately, there's also a "Packages" tab, which shows php85 at version "8.5.12", so everything seems to be fine.
Thanks a lot for the quick patch, OPNsense team!
#2
26.7 Series / Re: Internet Connectivity Issu...
Last post by ajaydharwa - Today at 11:04:20 AMthanks.
#3
26.7 Series / Re: Upgrade to 26.7 fails, no ...
Last post by SchengFui - Today at 10:43:56 AMMinor updates may be available, answer 'y' to run them instead.
Proceed with this action? [26.7/y/N]: y
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Flushing temporary package files... done
Starting web GUI...done.
Fetching base-26.1.11-amd64.txz: ..[] failed, no signature found
*** OPNsenseWIN7.localdomain: OPNsense 26.1.11_10 (amd64) ***
Proceed with this action? [26.7/y/N]: y
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Flushing temporary package files... done
Starting web GUI...done.
Fetching base-26.1.11-amd64.txz: ..[] failed, no signature found
*** OPNsenseWIN7.localdomain: OPNsense 26.1.11_10 (amd64) ***
#4
26.7 Series / Re: Critical PHP vuln: php2she...
Last post by newsense - Today at 10:25:57 AMQuote from: tangofan on Today at 04:28:50 AMCertainly something that can be presumably easily corrected, if necessary.
There's really no need for further action until 26.7.8
#5
26.7 Series / Re: Upgrade to 26.7 fails, no ...
Last post by newsense - Today at 10:23:27 AMWhat's the full output when you press y instead of 26.7 ?
#6
26.7 Series / Re: Failover switching with au...
Last post by Seimus - Today at 10:08:18 AMBy default the system picks a GW depending on the priority and "upstream flag"
Better Priority or "Upstream" flag always wins.
So set your primary GW with better prior and the other with worse one (lower priority = better candidate, but the Upstream overrides it If I remember correctly.)
This settings is to choose from GWs that are flagged as UP.
In regards of GW monitoring there are 2 parameters with 2 thresholds each.
Latency & Packet loss, each of them has low and high threshold.
The LOW threshold once reached flags the GW as either Packets loss Occurrence or Latency Occurrence
The HIGH threshold once reached flags the GW as DOWN.
You need to fine to this to your needs if the defaults values do not fit for you.
The defaults are. But usually they are enough.
Have a look at
https://docs.opnsense.org/manual/how-tos/multiwan.html
Regards,
S.
Better Priority or "Upstream" flag always wins.
So set your primary GW with better prior and the other with worse one (lower priority = better candidate, but the Upstream overrides it If I remember correctly.)
This settings is to choose from GWs that are flagged as UP.
In regards of GW monitoring there are 2 parameters with 2 thresholds each.
Latency & Packet loss, each of them has low and high threshold.
The LOW threshold once reached flags the GW as either Packets loss Occurrence or Latency Occurrence
The HIGH threshold once reached flags the GW as DOWN.
You need to fine to this to your needs if the defaults values do not fit for you.
The defaults are. But usually they are enough.
Have a look at
https://docs.opnsense.org/manual/how-tos/multiwan.html
Regards,
S.
#7
German - Deutsch / Gelöst: Nach Update von 26.1.1...
Last post by iRobot - Today at 09:19:16 AMHallo,
gefunden, es passiert bei jedem Update, auch bei dem aktuellen Update 26.7.1
In den iPv6-Einstellungen im LAN-Interface steht IPv6 Configuration Type auf "Identity association" und bei "Assign prefix ID" eine 10. Nach einem Update steht dort aber eine "0".
10 eintragen, speichern, schon läuft die FritzBox wieder als Telefonanlage.
gefunden, es passiert bei jedem Update, auch bei dem aktuellen Update 26.7.1
In den iPv6-Einstellungen im LAN-Interface steht IPv6 Configuration Type auf "Identity association" und bei "Assign prefix ID" eine 10. Nach einem Update steht dort aber eine "0".
10 eintragen, speichern, schon läuft die FritzBox wieder als Telefonanlage.
#8
26.7 Series / Failover switching with automa...
Last post by JoeFromNowhere - Today at 09:08:17 AMHello everyone,
I just switched from pfsense with squidguard to Opnsense with adguard and mostly everything works well !
I just have something about gateways failover that worked with pfsense and not with opnsense.
My wan network looks like this :
WAN1 : 7Gb/s fiber connection with a 4G backup behind that switch automatically to 4G if fiber is down.
WAN2 : 1Gb/s fiber connection
WAN1 has priority 1 and WAN2 has priority 2.
Automatic switching to 4G backup when WAN1 fiber is down goes like this :
First packets losses for a small time. Then connection goes ok with higher latency (Fiber : 15ms, 4G : 30ms)
So the only thing Opnsense really knows when WAN1 switch to 4G backup is higher latency.
What I would like from Opnsense :
- When WAN1 fiber connection is down, switch to WAN2.
- When WAN1 and WAN2 fiber connection are down, switch back to WAN1 with backup 4G connection (higher latency).
I successed making it work with pfsense, but with Opsense :
- it doesn't switch to WAN2 fiber link if I set WAN1 high latency threshold high (WAN1 in warning state).
- it doesn't switch back from WAN2 to WAN1 backup 4G when WAN1 and WAN2 fiber links are down if I set WAN1 high latency threshold low (WAN1 in down state).
I tried with and without gateway groups, always allowing gateway switching in general settings.
Someone has a solution ?
Thanks !
I just switched from pfsense with squidguard to Opnsense with adguard and mostly everything works well !
I just have something about gateways failover that worked with pfsense and not with opnsense.
My wan network looks like this :
WAN1 : 7Gb/s fiber connection with a 4G backup behind that switch automatically to 4G if fiber is down.
WAN2 : 1Gb/s fiber connection
WAN1 has priority 1 and WAN2 has priority 2.
Automatic switching to 4G backup when WAN1 fiber is down goes like this :
First packets losses for a small time. Then connection goes ok with higher latency (Fiber : 15ms, 4G : 30ms)
So the only thing Opnsense really knows when WAN1 switch to 4G backup is higher latency.
What I would like from Opnsense :
- When WAN1 fiber connection is down, switch to WAN2.
- When WAN1 and WAN2 fiber connection are down, switch back to WAN1 with backup 4G connection (higher latency).
I successed making it work with pfsense, but with Opsense :
- it doesn't switch to WAN2 fiber link if I set WAN1 high latency threshold high (WAN1 in warning state).
- it doesn't switch back from WAN2 to WAN1 backup 4G when WAN1 and WAN2 fiber links are down if I set WAN1 high latency threshold low (WAN1 in down state).
I tried with and without gateway groups, always allowing gateway switching in general settings.
Someone has a solution ?
Thanks !
#9
26.7 Series / Re: Critical PHP vuln: php2she...
Last post by bimbar - Today at 09:04:28 AMQuote from: notspam on Today at 12:01:38 AMThanks @Franco:
for the fast patch !
#10
26.7 Series / Re: Critical PHP vuln: php2she...
Last post by FelixLo - Today at 09:03:54 AMThanks a lot guys. Was my first update (and upgrade) experience with opnsense and worked just flawlessly!
