QuoteYou may be wondering how to perform similar firmware updates on other Intel NICs (specifically the Intel i226-V).
The challenge with the i226-V is that Intel does not publicly distribute the .bin NVM firmware images required by the Intel NVM Update Utility. The .bin files are required in order to update i226-V firmware, but they typically must be obtained directly from Intel, such as through Intel RDC or Intel DevZone, or provided under the appropriate terms.
We (Protectli) cannot directly redistribute those .bin files.
Quote from: lmoore on May 20, 2026, 11:37:22 PMWhat happens when you set the Gateway in these two rules to None?
First rule, gateway is None. I said default which is the same behavior as it uses the default gateway.
For second rule, setting gateway to None defeats the purpose but I will try and see what happens.
You will also have rules for your outbound traffic - what do they look like?
I have one outbound rule on the WAN interface which is a killswitch when a tag is set. The tags are not used in these two rules.
With your first rule, you could set the source to WGP1 and enable the Invert Source option. In addition, you could also enable Quick.
I can. But I use interface groups to reduce number of rules. In this case this group is to allow internet traffic over default gateway.
I will have do it as a resort if nothing else solves the issue - have separate rules for WG1 interface and remove it from the interface group. I can give it a try.
Which rules appear in the logs that are blocking these connections?
I haven't checked the logs as this issue occurs when I am connecting to home while I am away. I will simulate it and check the logs.
Quote from: nero355 on May 16, 2026, 03:58:48 PMDid you contact Protectli first and tried to get the update from them directly ?
If so : What did they say ?
QuoteConclusion and Related Notes
You may be wondering how to perform similar firmware updates on other Intel NICs (specifically the Intel i226-V).
The challenge with the i226-V is that Intel does not publicly distribute the .bin NVM firmware images required by the Intel NVM Update Utility. The .bin files are required in order to update i226-V firmware, but they typically must be obtained directly from Intel, such as through Intel RDC or Intel DevZone, or provided under the appropriate terms.
We (Protectli) cannot directly redistribute those .bin files.
Stock firmware on Vault platforms that include the i226-V NIC is typically around NVM 2.17. We have successfully validated updates to NVM 2.27+.
We are currently investigating the proper and compliant way to provide updated firmware images (or tools) to customers.
In the meantime, this OPNsense community forum post contains useful real-world context and discussion that should get you in the right direction, but use at your own risk.
Quote from: endurium on May 20, 2026, 12:41:57 PMIs there a way to "direct" a host to get it's IP address from a specific DNSMasq address pool (DHCP range)?Can't you just use 'Static DHCP Mappings based on the MAC Address' for those hosts with the specific 'DNS Server IP Address' configured in the mapping ?!
Quote from: NausB on May 19, 2026, 11:21:09 PMKernfrage aus meinen ersten Punkten wäre wohl eher:Das habe ich auch noch nicht umgesetzt.
**Wie bekommt man unter OPNsense 26.1.2 einen internen Webserver zuverlässig als Walled-Garden-/Pre-Auth-Ziel vor dem Captive-Portal-Login erreichbar?**
Quote from: NausB on May 19, 2026, 11:21:09 PMSind die **Allowed Addresses** im Captive Portal dafür der richtige Weg, oder braucht es zusätzlich eine andere Konfiguration?Ich denke nicht. Ich hätte die Option so verstanden, dass die genannten Quell-IPs /-Subnetze nicht blockiert würden. Dasselbe wie "Allowed MAC addresses" für MAC-Adressen.
QuoteUnd gibt es bekannte Besonderheiten, wenn das Ziel in einem anderen internen Netz liegt, also z. B.:Ich vermute es.
Quote from: passeri on May 12, 2026, 02:24:12 AMJust pausing to mention existence of other places on the planet at which point simplicity is down the gurgler, decisions need to be made.