"Recent posts
#1
26.7 Series / Re: os-upnp plugin not working...
Last post by nero355 - Today at 06:44:07 PMQuote from: Warbreaker on Today at 10:12:52 AMIt seems that way now, I didn't need it on 26.1 but the reason of why it was working is unknown to me, but now you do need it with 26.7IMHO you found a bug, because why would you need both of them when uPnP does more than a Source NAT Rule with Strict-port Enabled does : It completely opens the port like a Port Forward a.k.a. Destination NAT Rule would :)
#2
26.7 Series / Re: Call for testers - new CPU...
Last post by nero355 - Today at 06:37:22 PMQuote from: bamf on July 21, 2026, 08:24:07 PMI was assuming choosing a ZFS mirror in the OPNsense installer creates a fully redundant setup where all drives are bootable.
Quote from: Patrick M. Hausen on July 21, 2026, 08:44:18 PMYeah ... *sigh* ... the whole situation leaves a bit to be desired. But that's a FreeBSD problem, not an OPNsense one. I will work on getting this improved but as participation in open source projects goes - no promises, sorry.Quick FYI :
Linux has the same issue when using MDM Software RAID and you have to manually make sure GRUB is installed on both disks.
I had a lot of customers in the past who wrongly assumed the same thing sadly, so the wrong disk gone = the OS gone too! :(
#3
General Discussion / Re: WAN Static IP Breaks LAN I...
Last post by wiring8228 - Today at 06:35:18 PMThanks for the quick reply.
I see two gateways, one named WAN_GW, which is configured as the upstream gateway to IP address 192.168.2.1.
I had already checked that earlier but unfortunately forgot to mention it. I'll add that to the post above right away.
I see two gateways, one named WAN_GW, which is configured as the upstream gateway to IP address 192.168.2.1.
I had already checked that earlier but unfortunately forgot to mention it. I'll add that to the post above right away.
#4
26.7 Series / Re: System update
Last post by Patrick M. Hausen - Today at 06:34:17 PMWhat's pacman? I mean besides an 80's arcade game ...
#5
General Discussion / Re: WAN Static IP Breaks LAN I...
Last post by Patrick M. Hausen - Today at 06:29:19 PMWhen configuring WAN manually did you create the gateway in System > Gateways and mark it as "upstream" gateway? Only then will the automatic outbound NAT rule creation work and your clients have Internet access.
In the case of DHCP for WAN this happens automatically.
In the case of DHCP for WAN this happens automatically.
#6
26.7 Series / Re: System update
Last post by nero355 - Today at 06:29:18 PMQuote from: Karla on Today at 10:28:41 AMthe system update displayed on GUI similar to pacman updateExamples ?!
#7
26.7 Series / Re: 26.7 upgrade failure - ope...
Last post by nero355 - Today at 06:28:27 PMQuote from: ubu on Today at 09:52:30 AMI don't know what to do. Can someone help please?Run the Health Check if possible and post the output here :)
#8
General Discussion / WAN Static IP Breaks LAN Inter...
Last post by wiring8228 - Today at 06:24:47 PMProblem Description:
Internet connectivity fails for all LAN clients when the OPNsense WAN interface is configured with a static IPv4 address, despite working correctly when set to DHCP.
Expected Behavior:
LAN clients should have full internet access regardless of whether WAN uses DHCP or static IP configuration.
Actual Behavior:
Reproduction Steps:
1. Perform fresh OPNsense 26.7.1 installation
2. Complete the OPNsense Setup Wizard with the following settings:
General Information
DNS [Unbound]
Network [WAN]
Network [LAN]
Deployment type
Post-Wizard Changes
3. Configure Unbound DNS over TLS via Mullvad with the following forwarding servers:
| Server IP | Server Port | Description |
|-----------|-------------|-------------|
| 194.242.2.6 | 853 | Mullvad Family |
| 2a07:e340::6 | 853 | Mullvad Family |
4. From any LAN client, attempt to open a website or ping external addresses → ERR_TIMED_OUT
Relevant System Information:
Network Topology:
├── Upstream Device: tp-link Archer MR200
│ └── IP: 192.168.2.1
├── OPNsense WAN Interface
│ ├── IP: 192.168.2.2/24 (Static)
│ └── Gateway: 192.168.2.1
├── OPNsense LAN Interface
└── IP: 192.168.10.1/24
OPNsense Diagnostic Results:
LAN Client Diagnostics:
Error Messages:
Browser Error: ERR_TIMED_OUT
Ping Test Failure (LAN Clients): ping 1.1.1.1 → Request timed out
Note: OPNsense itself has full internet access and can reach external hosts. The problem exclusively affects traffic originating from LAN clients.
What I've Tried:
| Setting | Action Taken | Result |
|---------|--------------|--------|
| Source NAT | Changed from Automatic to Hybrid mode | No change |
| Routes | Verified default route exists (Flag UGS active) | Route confirmed correct |
| Interfaces | Switched WAN from Static to DHCP | ✅ Problem resolved - internet access restored fo rall LAN clients |
| Gateways | Verified WAN Gateway (192.168.2.1) is set as upstream gateway | Confirmed correct |
Off-topic: Manually converting this text, which was originally written in Markdown, was quite a hassle. Are there any better tools I could use for this?
Internet connectivity fails for all LAN clients when the OPNsense WAN interface is configured with a static IPv4 address, despite working correctly when set to DHCP.
Expected Behavior:
LAN clients should have full internet access regardless of whether WAN uses DHCP or static IP configuration.
Actual Behavior:
- With WAN on DHCP: LAN clients can browse websites without issues
- With WAN on Static IPv4: LAN clients cannot load any websites (browser shows ERR_TIMED_OUT)
Reproduction Steps:
1. Perform fresh OPNsense 26.7.1 installation
2. Complete the OPNsense Setup Wizard with the following settings:
General Information
- Hostname: OPNsense
- Domain: internal
- Override DNS: ❌ disabled
DNS [Unbound]
- Enable Resolver: ✅
- Enable DNSSEC Support: ✅
- Harden DNSSEC data: ✅
Network [WAN]
- Type: Static
- IP Address: 192.168.2.2/24
- Gateway: 192.168.2.1
- Block RFC1918 Private Networks: ❌ disabled
- Block bogon networks: ✅ enabled
Network [LAN]
- IP Address: 192.168.10.1/24
- Configure DHCP server: ✅ enabled
Deployment type
- Automatic DHCP/DNS registration: ✅ enabled
Post-Wizard Changes
3. Configure Unbound DNS over TLS via Mullvad with the following forwarding servers:
| Server IP | Server Port | Description |
|-----------|-------------|-------------|
| 194.242.2.6 | 853 | Mullvad Family |
| 2a07:e340::6 | 853 | Mullvad Family |
4. From any LAN client, attempt to open a website or ping external addresses → ERR_TIMED_OUT
Relevant System Information:
Network Topology:
├── Upstream Device: tp-link Archer MR200
│ └── IP: 192.168.2.1
├── OPNsense WAN Interface
│ ├── IP: 192.168.2.2/24 (Static)
│ └── Gateway: 192.168.2.1
├── OPNsense LAN Interface
└── IP: 192.168.10.1/24
OPNsense Diagnostic Results:
- Ping to 192.168.2.1: SUCCESS
- Ping to 1.1.1.1: SUCCESS
- Ping to google.com: SUCCESS
LAN Client Diagnostics:
- Ping to 192.168.10.1: SUCCESS
- Ping to 1.1.1.1: TIME OUT
- Ping to google.com: TIME OUT
- Website access to google.com: ERR_TIMED_OUT
Error Messages:
Browser Error: ERR_TIMED_OUT
Ping Test Failure (LAN Clients): ping 1.1.1.1 → Request timed out
Note: OPNsense itself has full internet access and can reach external hosts. The problem exclusively affects traffic originating from LAN clients.
What I've Tried:
| Setting | Action Taken | Result |
|---------|--------------|--------|
| Source NAT | Changed from Automatic to Hybrid mode | No change |
| Routes | Verified default route exists (Flag UGS active) | Route confirmed correct |
| Interfaces | Switched WAN from Static to DHCP | ✅ Problem resolved - internet access restored fo rall LAN clients |
| Gateways | Verified WAN Gateway (192.168.2.1) is set as upstream gateway | Confirmed correct |
Off-topic: Manually converting this text, which was originally written in Markdown, was quite a hassle. Are there any better tools I could use for this?
#9
26.7 Series / Re: Upgrade 26.1 -> 26.7 faile...
Last post by nero355 - Today at 06:24:32 PMQuote from: miketubby on Today at 09:40:48 AMI recally cannot remember if I had the microcode plug-in installed, but if it's a problem can't the upgrade process be configured to remove it to save this happening?There are some temporary issues because of the whole FreeBSD 14.x to FreeBSD 15.x switch so you simply need to follow the current upgrading rule which is :
- While still on OPNsense 26.1.x please DISABLE the Intel CPU Microcode functionality or uninstall the plug-in.
- Then upgrade to OPNsense 26.7.x
- Then upgrade your FreeBSD Bootloader.
- Then you might be able to ENABLE the Intel CPU Microcode functionality or install the plug-in again.
For more information and the whole procedure please follow this topic : https://forum.opnsense.org/index.php?topic=52441.0
#10
General Discussion / Re: apc ups commlost
Last post by Patrick M. Hausen - Today at 06:16:31 PMAs I wrote: usbconfig or usbconfig -v does that. And your output does not show the UPS connected.
