Quote from: keeka on January 23, 2026, 05:17:58 PMOne rule performs the NAT and the second permits the resulting traffic. With the previous system, it was a NAT port forward rule and a (potentially auto-managed) firewall rule.
I have not tried 26.1RC yet moto x3m. But I have a feeling, with the way I've set up NAT and FW under 25.7, a straight forward migration will not be possible. For example, the change in the priority of floating rules on single interfaces and the lack of auto/associated firewall rules for port forwards.
Quote from: Patrick M. Hausen on March 26, 2026, 08:42:52 AMWhy don't you set it to 0, then? You can add arbitrary tunables from the UI.
Quote from: BrandyWine on March 28, 2026, 12:38:00 AMRequires onsite visit? Do you mean to be able to do "reboot" from the console, or recycle the power?
If that's the type of remote location it is, then maybe some form of out-of-band console access should be there?
Or, set that option to 0, and still evaluate OOB access.
# nslookup server01
Server: opnsense01
Address: 10.10.10.254
DNS request timed out.
timeout was 2 seconds.
Name: server01.example.com
Address: 10.10.10.235
# DO NOT EDIT THIS FILE -- OPNsense auto-generated file
#
rebind-localhost-ok
stop-dns-rebind
port=53
dhcp-fqdn
domain=example.com
dhcp-authoritative
# Never forward addresses in the non-routed address spaces.
bogus-priv
server=/example.com/10.20.20.254
rebind-domain-ok=/example.com/
# host entries flushed via dnsmasq_watcher.py [isc] and a dump of the static reservations
addn-hosts=/var/etc/dnsmasq-hosts
addn-hosts=/var/etc/dnsmasq-leases
dns-forward-max=5000
cache-size=10000
local-ttl=1
conf-dir=/usr/local/etc/dnsmasq.conf.d,*.conf
dhcp-range=tag:igc0,10.10.10.120,10.10.10.189,255.255.255.0,86400
domain=example.com,10.10.10.120,10.10.10.189
dhcp-host=aa:bb:cc:dd:ee:ff,10.10.10.190,device-xx
...
# default IPv4 DNS mapped to this server (0.0.0.0)
dhcp-option=6,0.0.0.0
# default IPv6 DNS mapped to this server (::)
dhcp-option=option6:23,[::]
no-ident
Quote from: Patrick M. Hausen on May 03, 2026, 11:19:00 PMBoot the older version, uninstall the os-microcode plugin, redo the update.
Quote from: Patrick M. Hausen on May 03, 2026, 10:52:18 PM- power cycle with keyboard and monitor attached
- abort the boot process and escape to the boot loader prompt
- disable the loading of the microcode update
This should get you going with a search engine, possibly AI, or search function of this forum - I don't have the time to research the details of each step just right now, sorry.
HTH,
Patrick