"Recent posts
#1
26.1, 26,4 Series / Aliases wont load ip's for cow...
Last post by Siarap - Today at 06:21:43 AMMany other external blocklist's wont work after update to 26.1.9
It took whole night to load ip's. Now i checked it working. But why whole night?
It took whole night to load ip's. Now i checked it working. But why whole night?
#2
26.1, 26,4 Series / Re: Opnsense randomly (?) cras...
Last post by lmoore - Today at 05:21:54 AMQuote from: Nullman on June 03, 2026, 08:22:11 PMYou are probably dealing with either faulty memory, faulty motherboard, or faulty power supply.
For a hardware related issue this sums it up, though overheating should also be considered, as mentioned earlier regarding fans.
Run sudo sysctl -a | grep 'temperature' to obtain temperature sensor information.
Power supply faults can create strange and bewildering problems.
Memory exercising should be run for many hours with many passes.
Logging the serial console output to a file via your terminal program is a good idea.
Good luck.
#3
26.1, 26,4 Series / 26.1 upgrade chaos, Realtek un...
Last post by computer_freak_8 - Today at 04:46:05 AMFortunately, I have a HomeLab specifically for testing these sorts of things first. It's also entirely possible I misread or skimmed over something in one (or more) of the upgrade pop-ups that could have made this go a lot smoother.
Relevant things to know ahead of time:
The firewall old_hardware appeared to just never come back up from the upgrade. No DHCP, no establishing the WireGuard tunnel, nothing. Plugging in a keyboard/monitor indicated that the interface wasn't coming up properly. When I reboot it, I can see it saying "re0 up" in the boot logs, but it doesn't actually come up (doesn't list WAN VLANs as having received DHCP IPs, they're just blank). In fact, it's so "down", that the switch it's plugged into, never even lights up the lights for that port. The new_hardware firewall plugged into this same port, with the same cable, works fine. I've never had an issue with the physical NIC on old_hardware until now - only driver/software issues, so I don't think that's what's happening this time, either.
I downloaded the amd64 DVD ISO and tried to put it on a flash drive to install on new_hardware, but neither dd- nor cat-created UFDs were able to boot; I had to drop the ISO into a Ventoy drive to be able to boot it at all. (26.1.6). (Yes, I validated the checksum and then unzipped it first.)
At one point I tried a USB Ethernet adapter (ASIX chipset) in the old_hardware machine, but it didn't seem to have the kernel module needed for it.
Getting the config.xml onto the new hardware for a Linux-native seems... much more difficult than it should be. I tried booting a Live Ubuntu instance (on the freshly-OPNsense-installed new_hardware machine) and importing the zroot, but it was just a handful of empty folders. I tried formatting a USB Flash Drive (UFD) with Ubuntu as MBR/vfat and the "b" partition type, but that didn't seem to work (couldn't get it to mount, neither with "mount" nor "mount_msdosfs"). Eventually, I wiped/formatted/filesystem'd the UFD using the OPNsense instance on new_hardware, and then sneakernet'd that over to an Ubuntu box, which was able to read, and place, the config.xml I needed; then sneakernet back, mount, and I had my config imported (after a reboot).
Upon booting this imported config on new_hardware, I still had several issues, such as:
I'm half tempted to just pull the drive from new_hardware and drop it into old_hardware and see what happens. I'm also tempted to install a couple major versions older than current, import the config, migrate all the DHCP stuff over, and retry the upgrade.
I'm not sure the best course of action, but I've already spent 4 hours of troubleshooting and another 45 minutes of documenting of said troubleshooting tonight, so I'm looking for the "easiest" path forward to have a functional old_hardware system again. Note that transplanting the HDD from new_hardware now will NOT give me that, due to being stuck on ISC with no way to export/import to Kea, even though I did fix the DDNS issue.
Also going forward - is there a way to force packages to auto-reinstall after system upgrades, especially critical things like drivers or DDNS?
Relevant things to know ahead of time:
- I'm a native Ubuntu user for nearly 20 years. I'm comfortable in a terminal, but not BSD-native.
- My HomeLab OPNsense install is router-on-a-stick layout; there's one physical NIC but everything is VLANs.
- The NIC hardware is some form of Realtek; I had the os-realtek-re package installed previously (not sure if it disabled on this upgrade or an older one).
- I use DDNS and WireGuard to VPN into this network.
- I have several DHCP reservations for the LAN-side VLAN.
- I have multi-WAN setup.
- There are two physical machines - the one I tried to upgrade, that's still broke, I'll call it "old_hardware", and a machine I pulled out of storage to at least try and get back up and running a bit ("new_hardware").
The firewall old_hardware appeared to just never come back up from the upgrade. No DHCP, no establishing the WireGuard tunnel, nothing. Plugging in a keyboard/monitor indicated that the interface wasn't coming up properly. When I reboot it, I can see it saying "re0 up" in the boot logs, but it doesn't actually come up (doesn't list WAN VLANs as having received DHCP IPs, they're just blank). In fact, it's so "down", that the switch it's plugged into, never even lights up the lights for that port. The new_hardware firewall plugged into this same port, with the same cable, works fine. I've never had an issue with the physical NIC on old_hardware until now - only driver/software issues, so I don't think that's what's happening this time, either.
I downloaded the amd64 DVD ISO and tried to put it on a flash drive to install on new_hardware, but neither dd- nor cat-created UFDs were able to boot; I had to drop the ISO into a Ventoy drive to be able to boot it at all. (26.1.6). (Yes, I validated the checksum and then unzipped it first.)
At one point I tried a USB Ethernet adapter (ASIX chipset) in the old_hardware machine, but it didn't seem to have the kernel module needed for it.
Getting the config.xml onto the new hardware for a Linux-native seems... much more difficult than it should be. I tried booting a Live Ubuntu instance (on the freshly-OPNsense-installed new_hardware machine) and importing the zroot, but it was just a handful of empty folders. I tried formatting a USB Flash Drive (UFD) with Ubuntu as MBR/vfat and the "b" partition type, but that didn't seem to work (couldn't get it to mount, neither with "mount" nor "mount_msdosfs"). Eventually, I wiped/formatted/filesystem'd the UFD using the OPNsense instance on new_hardware, and then sneakernet'd that over to an Ubuntu box, which was able to read, and place, the config.xml I needed; then sneakernet back, mount, and I had my config imported (after a reboot).
Upon booting this imported config on new_hardware, I still had several issues, such as:
- no DHCP working at all. The ISC package was removed, and Kea was not enabled.
- no DDNS. The package was removed.
- os-realtek-re not available at all; I still can't find it in either Packages or Plugins, even after another update/upgrade and re-check (26.1.7 now).
- no export/migration option for ISC-->Kea. Allegedly there's supposed to be a CSV export/import function, but I can't find it.
I'm half tempted to just pull the drive from new_hardware and drop it into old_hardware and see what happens. I'm also tempted to install a couple major versions older than current, import the config, migrate all the DHCP stuff over, and retry the upgrade.
I'm not sure the best course of action, but I've already spent 4 hours of troubleshooting and another 45 minutes of documenting of said troubleshooting tonight, so I'm looking for the "easiest" path forward to have a functional old_hardware system again. Note that transplanting the HDD from new_hardware now will NOT give me that, due to being stuck on ISC with no way to export/import to Kea, even though I did fix the DDNS issue.
Also going forward - is there a way to force packages to auto-reinstall after system upgrades, especially critical things like drivers or DDNS?
#4
26.1, 26,4 Series / Re: "The DHCP Server is active...
Last post by lmoore - Today at 04:44:07 AMAnother option would be to configure the modem with a static IP address before it is connected to the WAN port.
With the right configuration in OPNsense, you can access the modem even when the WAN interface cannot obtain an IP address via DHCP from your ISP.
With the right configuration in OPNsense, you can access the modem even when the WAN interface cannot obtain an IP address via DHCP from your ISP.
#5
Hardware and Performance / Re: cpu-microcode-intel: no ma...
Last post by BrandyWine - Today at 04:30:49 AMWe need more info.
Is the actual new pkg installed? Does the loader conf say to install the bin? What size is the ucode bin file? Is the .80 file there?
Is the actual new pkg installed? Does the loader conf say to install the bin? What size is the ucode bin file? Is the .80 file there?
#6
German - Deutsch / Updates nicht möglich
Last post by Spacer - Today at 12:40:39 AMHallo,
seit ca. einer Woche erhalte ich Fehlermeldungen, wenn ich schauen will ob Updates verfügbar sind.
Hier die Ausgabe der Firewall:
Wer kann mir sagen woran es liegt und wie ich diese Sache beheben kann?
Der Mirror steht auf default. Auch andere Mirrors bringen keine Verbesserung.
seit ca. einer Woche erhalte ich Fehlermeldungen, wenn ich schauen will ob Updates verfügbar sind.
Hier die Ausgabe der Firewall:
QuoteCould not find the repository on the selected mirror.
Wer kann mir sagen woran es liegt und wie ich diese Sache beheben kann?
Der Mirror steht auf default. Auch andere Mirrors bringen keine Verbesserung.
#7
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by Maurice - Today at 12:32:25 AMOPNsense 26.1.9 aarch64 packages and sets released.
#8
26.1, 26,4 Series / Re: OPNsense 26.1.8_5 Freezes ...
Last post by cookiemonster - Today at 12:28:36 AM"Freezes" can be for various reasons, from configuration to hardware or a combination so each user experiencing a freeze will likely have a different problem and therefoer need a different path to diagnostic.
Piling each a request for an "update" or "progress" on "the issue" will not help anyone. It'll become just a "me too fest".
Open a new thread with your setup so you can be helped.
Piling each a request for an "update" or "progress" on "the issue" will not help anyone. It'll become just a "me too fest".
Open a new thread with your setup so you can be helped.
#9
German - Deutsch / Re: "Lahmes" Internet seit Upd...
Last post by cottec - Today at 12:00:32 AMQuote from: trixter on June 03, 2026, 10:55:04 AMbevor ich anfange zu meckern?Sorry, wo hab ich denn gemeckert?
In den Release Notes lese ich das hier:
Code Select
To accommodate the change away from ISC-DCHP defaults the "Track interface" IPv6 mode now has a sibling called "Identity Association" which does the same except it is not automatically starting ISC-DHCPv6 and Radvd router advertisements to allow better interoperability with Kea and Dnsmasq setups.Dann bleibt doch die Frage, was schlecht am automatischen von ISC-DHCPv6 und RA wenn ich noch nicht auf Kea oder Dnsmasg migriert habe?
Nur weil es mit dem Update Legacy wurde sollte man doch meinen, dass es weiterhin funktioniert?
#10
26.1, 26,4 Series / Re: OPNsense 26.1.8_5 Freezes ...
Last post by blen01 - June 03, 2026, 11:44:20 PMHas anyone made progress with this issue? I'm still getting hard freezes in 26.1.9. I suspect its either vlans or possibly wireguard. Its pretty much impossible to figure out what is going on due to the logs not saying anything. The system just freezes.
