Messages

So, out of pure desperation, I downloaded version 22.1.2_2 (was trying to do this with 22.7), loaded it up in VMware and it worked immediately.  So I guess don't use 22.7 if you want HA.

My test firewalls didn't have 'real" internet access to update to 22.7.x so, in case anyone else tries this, maybe set that up and update to something other than base 22.7, or use an older version.

Seems to be the case. HA was working with ZERO issues until the upgrade. Standard failover/upgrade/carp-maintenance/upgrade/fail-back ... the OS gets updated and everything except HA is working.

I've triple checked firewall rules, pfsync account password, XMLRPC sync is allowed via HTTPS, etc etc.. all the usual step. Doesn't matter. Then the two will fight over which one is primary because they're both sitting around at either 0 or 240, and occasionally the logs will have "pfsync bulk start" followed by "pfsync bulk failed".

There's nothing wrong with the settings, nothing wrong with the physical hardware (two R630 with CARP going over a direct physical link that has been functionally validated), the only thing that changed was upgrading the two boxes to 22.7.5

Not a great situation. Have already burned six hours wasting time checking all of the settings that were exactly the same as before this upgrade. If I have to downgrade the hosts to a different release this is going to be a huge PITA. Bug fix please!

Hi All. I have a few NanoPI R4SE (the enterprise ones w/ eMMC and consistent MAC). As such, the usual instructions for getting OPNsense running on this is not entirely the same as the R4S (without eMMC). Since the R5S does have the eMMC I've ported some of the u-boot commands from there to try on the R4SE.

Does anyone have a command sequence for writing to the TF card that will successfully boot the 22.1.x OPNsense image?

Here's my current command sequence:

Code Select Expand


   1 │ # Boot from SD/TF Card                                                                                                                                                                                                                                                                                                                                                                                                             
   2 │ sudo dd if=u-boot/idbloader.img of=/dev/sda conv=sync seek=64 status=progress
   3 │ sudo dd if=u-boot/u-boot.itb of=/dev/sda conv=sync seek=16384 status=progress
   4 │ sudo dd if=OPNsense-22.1.9-OpenSSL-aarch64-NanoPi-R4S-20220626.img of=/dev/sda conv=sync seek=32768 status=progress


Result, it tries to boot and u-boot does its typical process but then errors with:

Code Select Expand


Failed to initialize SPI flash at 0:0 (error


Rather pleased to have found this thread. I needed support for a "Quectel EM12-G" LTE modem that was installed yesterday at the datacenter, but which is only available in FBSD 13.1. Initiated the 22.7.b update, rebooted, and now the PPP interface section of the UI recognizes the modem and lists the usual expected options.

I'll let this bake in for a few more hours and if there are no issues then I'll upgrade the active node (running a 2-node H/A pair, with the passive one on 22.7.b).

Here's the HW Probe link to the machine specs if it's useful for the dev team: https://bsd-hardware.info/?probe=cd8960f886 ; it's a decent enterprise-spec Dell R630 with 4x 1G and 4x 10G Intel based interfaces, though they're being upgraded soon to run 8x 10G (X710 quad-SFP+ rNDC and X710 quad 10G-BASET).