"Recent posts
#1
Hardware and Performance / Re: TOPTON Mini PC Running OPN...
Last post by BrandyWine - Today at 01:20:56 AMQuote from: Nullman on May 12, 2026, 09:58:36 PMYes. I dont want to open my device just so i can remove dust carpets. I dont want to lubricate or replace failing/dead fans. I dont want to get my hands dirty with thermal paste.Is there any fanless hardware that has no holes to let in air & to let out hot air? All my fanless asic devices have holes in them.
#2
Hardware and Performance / Re: quad interface fierwall PC...
Last post by passeri - Today at 12:41:52 AMQuote from: nero355 on May 12, 2026, 06:49:24 PMFor xDSL connections the products made by DrayTek are my absolute favorite! :)Yes, I had two (serially) for ADSL connections. They were very solid and by reputation very secure. Fibre and a wish to do some things entailing a Draytek business licence overrode.
I handed off the first to family and sold the second only last year for a better price than one usually expects for older networking gear.
#3
Hardware and Performance / Re: TOPTON Mini PC Running OPN...
Last post by nero355 - May 12, 2026, 11:54:59 PMQuote from: Nullman on May 12, 2026, 09:58:36 PMI dont want to get my hands dirty with thermal paste.'Special for you my friend' : https://duckduckgo.com/?q=zalman+stg1+paste&ia=images&iax=images
No need to get messy with that good old paste! :P
#4
Tutorials and FAQs / Re: HOWTO - Redirect all DNS R...
Last post by nero355 - May 12, 2026, 11:51:32 PMQuote from: rumshot on May 12, 2026, 09:30:58 PMEven more confusing:After applying the correct DNAT/SNAT Rules and related Firewall Rules that should work indeed, but instead of the queries going to those Public DNS Servers the queries should show up in the Query Log of your Private DNS Server ;)
* `dig @1.1.1.1 google.com
* `dig @2.2.2.2 aljazeera.com
still succeed from the client (macbook terminal) (just in case has something special with mac).
QuoteI also noticed:That's not good...
* some DNS requests *are* going to `192.168.50.1`
* but other requests still leave directly to public DNS servers
Try these settings : https://forum.opnsense.org/index.php?msg=259581
And if you have questions let me know :)
#5
Q-Feeds (Threat intelligence) / Re: Invalid license after upda...
Last post by Q-Feeds - May 12, 2026, 11:42:48 PMThank you for reporting! This was an issue on our end and we solved it. You might need to re-apply the settings in the plugin. (no need to rotate the api-key)
For those interested. Community licenses don't have an expiry date but the plugin checks against a license check which returned 'null'. as an expiry date This caused the issue. the expiry date now shows the date 9999-12-31
For those interested. Community licenses don't have an expiry date but the plugin checks against a license check which returned 'null'. as an expiry date This caused the issue. the expiry date now shows the date 9999-12-31
#6
26.1, 26,4 Series / Re: 26.1.8 breaks NUT
Last post by zyghom - May 12, 2026, 10:45:30 PMsame issue with the upgrade but work around worked - thank you
#7
Q-Feeds (Threat intelligence) / Re: Invalid license after upda...
Last post by appasquatic - May 12, 2026, 10:37:22 PMMe too, unfortunately.
I didn't try to register a new API Key license yet, but it sounds like it would not solve the issue.
I don't know how to test if it is an plugin issue, or something else. Any ideas?
I didn't try to register a new API Key license yet, but it sounds like it would not solve the issue.
I don't know how to test if it is an plugin issue, or something else. Any ideas?
#8
Q-Feeds (Threat intelligence) / Re: Invalid license after upda...
Last post by MagikMark - May 12, 2026, 10:27:55 PMSame problem here. I even regenerated new API. No Luck
#9
26.1, 26,4 Series / OPNsense Interface No Longer A...
Last post by nepopnuser - May 12, 2026, 10:27:20 PMHello. After upgrading from 26.1.6_2 to 26.1.8 I can no longer access the web interface. Not sure if this is related to the other "access" issues posted.
The console works fine and when try to use "Assign interface" it says the following.
We are running OPNsense on an older Dell just as a VPN appliance. It was configured and working with one NIC and the firewall completely disabled. We are relying on our existing firewall to protect this connection.
Please let me know if you need any other details. Thanks.
The console works fine and when try to use "Assign interface" it says the following.
Code Select
Fatal error: Uncaught Error: Call to undefined function confgig_read_array() in /usr/local/etc/inc/console.inc:150
Stack trace:
#0 /usr/local/etc/inc/console.inc(81): _set_networking_interfaces_ports(false)
#1 /usr/local/opnsense/scripts/shell/setports.php(37): set_networking_interfaces_ports()
#2 {main}
thrown in /usr/local/etc/inc/console.inc on line 150
We are running OPNsense on an older Dell just as a VPN appliance. It was configured and working with one NIC and the firewall completely disabled. We are relying on our existing firewall to protect this connection.
Please let me know if you need any other details. Thanks.
#10
26.1, 26,4 Series / Re: 26.1.8 breaks Firewall Rul...
Last post by muchacha_grande - May 12, 2026, 10:06:50 PMIn my case, when I select the "All rules" filter, the number of rules are right in both indicators, the little circle on the filter selector and the number below the grid.
The problem is in the rest of the numbers of the interface filters. All little circles shows different numbers than the real value. The counter below de grid always shows the right value.
One extra problem I've found is that when I select the "Floating" filter, it shows nothing in the grid but I have eight floating rules as correctly indicated in the number below the grid. Fortunately I can see these eight rules using the "All rules" filter.
EDIT:
I see that I misunderstood the way filtering works. The numbers are correct because what I see in the grid includes the floating rule where the selected interface is selected. So the only problem I still find is that the Floating filter is showing an empty grid.
The problem is in the rest of the numbers of the interface filters. All little circles shows different numbers than the real value. The counter below de grid always shows the right value.
One extra problem I've found is that when I select the "Floating" filter, it shows nothing in the grid but I have eight floating rules as correctly indicated in the number below the grid. Fortunately I can see these eight rules using the "All rules" filter.
EDIT:
I see that I misunderstood the way filtering works. The numbers are correct because what I see in the grid includes the floating rule where the selected interface is selected. So the only problem I still find is that the Floating filter is showing an empty grid.
