"Recent posts
#1
General Discussion / Re: WAN out connection Issues
Last post by Tetra - Today at 01:28:21 AMFollow-up: For testing purposes I did some allow any firewall changes and I believe the firewall was blocking the pings from the other devices connected to my ISP router. The OPNsense WAN interface can now ping the ISP Router private not public, while other devices connected to the ISP can ping the public IP. Other devices can also ping the OPNsense WAN interface but the issue still persists where the endpoint can't ping the ISP Router(public or private).
#2
26.7 Series / webgui stops respoding config ...
Last post by clash - Today at 01:02:57 AMHi,
After upgrading to OPNsense 26.7.3_11-amd64 Iam expiriencing very slow and then unresponsiv webgui.
Then I tried
configctl webgui restart
but it tells me:
--
unable to connect to configd socket (@/var/run/configd.socket)
--
After restarting config, the Webgui work well again.
Is this a known issue? Can I increase configd logging?
After upgrading to OPNsense 26.7.3_11-amd64 Iam expiriencing very slow and then unresponsiv webgui.
Then I tried
configctl webgui restart
but it tells me:
--
unable to connect to configd socket (@/var/run/configd.socket)
--
After restarting config, the Webgui work well again.
Is this a known issue? Can I increase configd logging?
#3
26.7 Series / Re: OpenVPN CLient Export fail...
Last post by rubydragon - Today at 12:28:27 AMI had the same issue as stated and even ended up recreating everything from scratch with the same result. Starting from 26.7, the "server" only certificate is apparently not working anymore. You have to pick "combined client/server". If that can help anyone else...
#4
General Discussion / Re: WAN out connection Issues
Last post by Tetra - September 03, 2026, 11:42:21 PMSo on the ISP I still have some of my other personal devices connected and they can ping each other and the ISP Router, but can't ping still the OPNsense WAN interface. I've confirmed that its properly pulling a IP from the router by restarting the interface. All my other devices work just fine connected the ISP router but this OPNsense WAN interface.
#5
26.7 Series / Re: Wireguard vs. DNS resoluti...
Last post by meyergru - September 03, 2026, 10:35:41 PMFor S2S connections, the cron job helps. For C2S, there should be nothing keeping your Wireguard server from starting, because the peer does not have to have an endpoint, so there is no DNS to be resolved that could keep the instance from coming up?
#6
26.7 Series / Re: os-vnstat: Interface?
Last post by Patrick M. Hausen - September 03, 2026, 10:22:31 PMLook at Interfaces > Assignments. Probably WAN is assigned to pppoe0. So they are one and the same. It's a bit unfortunate different subsystems and/or plugins use different identifiers. Since OPNsense introduced that WAN, LAN, ... abstraction layer above the device names IMHO all fuctions should explicitly use these only.
#7
26.7 Series / Re: Confused by 26.7 upgrade
Last post by bamf - September 03, 2026, 10:15:59 PMThis is neither a consumer product nor a commercial solution. This is the community edition of an enterprise firewall. If you choose to use it, you need to educate yourself and read the release notes of every update before pressing the button. Community support relies on users doing their homework. Expecting enterprise-grade stability and active hand-holding without carefully reading the changelog misses the point of a community edition.
#8
26.7 Series / [Guide] Sophos SG210 Rev.3 LCD...
Last post by Nusoaheisl - September 03, 2026, 09:46:49 PMHi all,
I found this older archived thread while working on basically the same problem:
Sophos lcdproc: "sdeclcd: cannot release IO-permission for 0x378!"
Since the old thread is archived and can't be replied to anymore, I thought I'd leave the solution here for anyone ending up there through search :)
I recently went pretty deep down the rabbit hole with a Sophos SG 210 Rev.3 and finally got the original front LCD including all four buttons working properly on current OPNsense.
Tested setup:
The interesting part is that, at least on my SG 210 Rev.3, sdeclcd wasn't actually the correct solution.
The bigger problem was UART2.
The NCT6779D Super-I/O had UART2 configured at:
while the Intel PCH serial routing exposed the second UART at:
Because of that mismatch, FreeBSD never created a usable second serial device for the LCD.
After safely remapping UART2 from 0x2f8 → 0x3e8, bridging it through a PTY and using LCDproc with the HD44780/EZIO driver, the display started working properly — including the keypad.
Full documentation / source:
GitHub – Sophos SG210 Rev.3 LCD for OPNsense
Discussion and additional hardware information:
Reddit – r/opnsense discussion
The current version has also survived:
So far it's been completely stable on my unit.
I deliberately only claim compatibility with the SG 210 Rev.3, because that's the hardware I can physically verify.
Other SG/XG models and revisions use different LCD hardware/layouts, although I'm currently collecting more information about those as well.
I also have a second identical SG 210 now, so I'm planning to use that as a dedicated test box for the next step: turning this into a proper BSD/OPNsense package instead of having people manually install files and maintain a custom syshook.
Hopefully this helps anyone still trying to get the original Sophos front panel working :)
I found this older archived thread while working on basically the same problem:
Sophos lcdproc: "sdeclcd: cannot release IO-permission for 0x378!"
Since the old thread is archived and can't be replied to anymore, I thought I'd leave the solution here for anyone ending up there through search :)
I recently went pretty deep down the rabbit hole with a Sophos SG 210 Rev.3 and finally got the original front LCD including all four buttons working properly on current OPNsense.
Tested setup:
- Sophos SG 210 Rev.3
- OPNsense 26.7.3_8
- FreeBSD 15.1-RELEASE-p3
- Original Sophos LCD/front panel
- LCDproc using hd44780
- ConnectionType=ezio
- 2400 baud
- All 4 front buttons working
The interesting part is that, at least on my SG 210 Rev.3, sdeclcd wasn't actually the correct solution.
The bigger problem was UART2.
The NCT6779D Super-I/O had UART2 configured at:
Code Select
0x2f8
while the Intel PCH serial routing exposed the second UART at:
Code Select
0x3e8
Because of that mismatch, FreeBSD never created a usable second serial device for the LCD.
After safely remapping UART2 from 0x2f8 → 0x3e8, bridging it through a PTY and using LCDproc with the HD44780/EZIO driver, the display started working properly — including the keypad.
Full documentation / source:
GitHub – Sophos SG210 Rev.3 LCD for OPNsense
Discussion and additional hardware information:
Reddit – r/opnsense discussion
The current version has also survived:
- normal reboots
- a full OPNsense update
- another reboot after the update
So far it's been completely stable on my unit.
I deliberately only claim compatibility with the SG 210 Rev.3, because that's the hardware I can physically verify.
Other SG/XG models and revisions use different LCD hardware/layouts, although I'm currently collecting more information about those as well.
I also have a second identical SG 210 now, so I'm planning to use that as a dedicated test box for the next step: turning this into a proper BSD/OPNsense package instead of having people manually install files and maintain a custom syshook.
Hopefully this helps anyone still trying to get the original Sophos front panel working :)
#9
26.7 Series / Re: Running OPNsense 26.7 on a...
Last post by franco - September 03, 2026, 09:26:42 PMSure, you can install one or flash the Nano image which is much easier. Some sticks don't work. Some can be slow, but also depends on USB speed of the box.
Cheers,
Franco
Cheers,
Franco
#10
26.7 Series / Re: Fatal error: Uncaught Erro...
Last post by franco - September 03, 2026, 09:20:34 PMHi BigFreddy,
In theory this is software as it wants a file on the disk that isn't available (yet -- like in your other thread). Practically, the file could get lost via the OS/file system/hard disk which makes this harder to work around since the package has all the files and tries to extract them. Depending on how important the file is this could work out in the next boot or not.
Cheers,
Franco
In theory this is software as it wants a file on the disk that isn't available (yet -- like in your other thread). Practically, the file could get lost via the OS/file system/hard disk which makes this harder to work around since the package has all the files and tries to extract them. Depending on how important the file is this could work out in the next boot or not.
Cheers,
Franco
