"Recent posts
#1
General Discussion / Re: Has anyone heard of / trie...
Last post by dev - Today at 04:16:24 PMHi, thanks a lot for chiming in directly and for building this project! It's always great to hear straight from the maintainer, and your transparent explanation definitely puts things into perspective. Especially knowing that the configuration stays entirely on the firewalls themselves.
Since you're here, I'd love to learn a bit more about the background of OPNexus:
Since you're here, I'd love to learn a bit more about the background of OPNexus:
- Motivation: What sparked the idea to build this? Were you scratching your own itch managing multiple boxes, or was something missing in the existing tools?
- Production use: Are you already running OPNexus in a production environment yourself (or managing multiple firewalls with it)?
- Roadmap: What are your future plans for the project? Are there specific features you're focusing on next?
- Licensing: Out of curiosity, what led you to choose the PolyForm Shield license over a traditional open-source license?
#2
26.7, 26.10 Series / Re: Invalid changelog/index.js...
Last post by franco - Today at 03:48:50 PMAh, sorry, I committed a faulty file. Removed here
https://github.com/opnsense/changelog/commit/666361ffd1
and new changelogs.txz updated pushed to mirror.
Cheers,
Franco
https://github.com/opnsense/changelog/commit/666361ffd1
and new changelogs.txz updated pushed to mirror.
Cheers,
Franco
#3
26.7, 26.10 Series / Re: PPPoE over an unassigned V...
Last post by franco - Today at 03:42:16 PMDo you also have igb as WAN?
#4
26.7, 26.10 Series / Re: PPPoE over an unassigned V...
Last post by johndoeuser - Today at 03:16:21 PMI just upgraded from OPNsense 26.7.8_2-amd64 to OPNsense 26.7.9_1-amd64. PPPoE is working again!
#5
26.7, 26.10 Series / Re: [CALL FOR TESTING] DHCP re...
Last post by mschaeffler - Today at 02:36:16 PMjust installed the patch.
#6
26.7, 26.10 Series / Re: [CALL FOR TESTING] Defer P...
Last post by RamSense - Today at 02:27:16 PMHi Franco,
I tested the patch on OPNsense 26.7.9_1 (amd64) and can confirm a successful regression test after reboot.
reboot results:
- Deferred PPP startup confirmed in the system log
- PPPoE connected automatically
- IPv4 default route via PPPoE restored
- IPv4 and IPv6 HTTPS connectivity successful
- No pending PPP startup tasks
- WireGuard interface active and working.
Boot log analysis:
- PPP startup deferred: 1
- PPPoE connection successful: 1
- PPPoE disconnections: 0
- DHCPv6 restarts: 1
- DHCPv6 transmission errors: 0
- Interface startup errors: 0
The PPPoE connection was already working before applying the patch, so this confirms successful startup and no observed regressions in the tested components, rather than that I needed a fix for an existing connection failure.
Thanks for your work on OPNsense!
I tested the patch on OPNsense 26.7.9_1 (amd64) and can confirm a successful regression test after reboot.
reboot results:
- Deferred PPP startup confirmed in the system log
- PPPoE connected automatically
- IPv4 default route via PPPoE restored
- IPv4 and IPv6 HTTPS connectivity successful
- No pending PPP startup tasks
- WireGuard interface active and working.
Boot log analysis:
- PPP startup deferred: 1
- PPPoE connection successful: 1
- PPPoE disconnections: 0
- DHCPv6 restarts: 1
- DHCPv6 transmission errors: 0
- Interface startup errors: 0
The PPPoE connection was already working before applying the patch, so this confirms successful startup and no observed regressions in the tested components, rather than that I needed a fix for an existing connection failure.
Thanks for your work on OPNsense!
#7
26.7, 26.10 Series / Re: Invalid changelog/index.js...
Last post by meyergru - Today at 02:10:58 PMI see the problem as well, Franco:
The part that is buggy is this:
Code Select
root@OPNsense:~ # cat /usr/local/opnsense/changelog/index.json | jq -e > /dev/null && echo good
jq: parse error: Invalid numeric literal at line 120, column 4
The part that is buggy is this:
Quote{"series":"26.7","version":"26.7.9","date":"November 11, 2026"}
,
{"series":"26.7","version":"26.7.7","date":"October 13, 2026"}
,
{"series":"26.7","version":"26.7.1","date":"July 21, 2026"}
,
{"series":"26.7","version":"26.7.6","date":"October 08, 2026"}
,
{"series":"26.7","version":"26.7.8","date":"October 30, 2026"}
,
Use of uninitialized value $date in concatenation (.) or string at /Users/franco/Documents/opnsense/changelog/Scripts/webify.pl line 128.
{"series":"26.7","version":"26.7.","date":""}
,
{"series":"26.7","version":"26.7.r1","date":"July 07, 2026"}
,
{"series":"26.7","version":"26.7.3","date":"August 27, 2026"}
,
{"series":"26.7","version":"26.7.4","date":"September 15, 2026"}
,
{"series":"26.7","version":"26.7.5","date":"September 30, 2026"}
,
{"series":"26.7","version":"26.7.2","date":"August 12, 2026"}
,
#8
26.7, 26.10 Series / Re: Invalid changelog/index.js...
Last post by franco - Today at 12:58:45 PMHi,
You're not talking about the file on the mirror when you refer to a Perl error in the changelog webify script?
It looks like we're missing context.
FWIW, the file downloaded from the mirror:
# cat /usr/local/opnsense/changelog/index.json | jq -e > /dev/null && echo good
good
Cheers,
Franco
You're not talking about the file on the mirror when you refer to a Perl error in the changelog webify script?
It looks like we're missing context.
FWIW, the file downloaded from the mirror:
# cat /usr/local/opnsense/changelog/index.json | jq -e > /dev/null && echo good
good
Cheers,
Franco
#9
26.7, 26.10 Series / Invalid changelog/index.json a...
Last post by kohly - Today at 12:27:19 PMHello OPNsense team,
We noticed that every firmware update check results in an invalid `/usr/local/opnsense/changelog/index.json` on multiple OPNsense systems.
The file contains the following unexpected lines:
Use of uninitialized value $date in concatenation (.) or string at /Users/franco/Documents/opnsense/changelog/Scripts/webify.pl line 128.
{"series":"26.7","version":"26.7.","date":""}
,
Validation fails with:
python3 -m json.tool /usr/local/opnsense/changelog/index.json
Expecting value: line 120 column 1 (char 3781)
After manually removing these three lines, JSON validation succeeds. However, **every subsequent firmware update check reproduces the issue**, even after repairing the file.
We have reproduced this on several independent OPNsense installations.
Could you please check whether the published changelog index is being generated incorrectly?
Thank you and best regards!
We noticed that every firmware update check results in an invalid `/usr/local/opnsense/changelog/index.json` on multiple OPNsense systems.
The file contains the following unexpected lines:
Use of uninitialized value $date in concatenation (.) or string at /Users/franco/Documents/opnsense/changelog/Scripts/webify.pl line 128.
{"series":"26.7","version":"26.7.","date":""}
,
Validation fails with:
python3 -m json.tool /usr/local/opnsense/changelog/index.json
Expecting value: line 120 column 1 (char 3781)
After manually removing these three lines, JSON validation succeeds. However, **every subsequent firmware update check reproduces the issue**, even after repairing the file.
We have reproduced this on several independent OPNsense installations.
Could you please check whether the published changelog index is being generated incorrectly?
Thank you and best regards!
#10
Development and Code Review / Re: netflector available as pl...
Last post by vicking - Today at 11:44:20 AMAfter using netflector for two days I notice that I regularly cant find my Sonos systeem in the Sonos app because it is on a different VLan. With the old udpbroadcastrelay plugin in combination with the mdns repeater I never had these problems. Am I missing something?
