Upgradethread 23.1.11_1 to 23.7

Started by seed, July 31, 2023, 03:07:59 PM

Previous topic - Next topic
Quote from: DEC670airp414user on July 31, 2023, 05:11:59 PM
under general DNS>  i have one DNS server applied to WAN.
9.9.9.9

my upgrade worked fine, i decided to tinker when i read this thread:

under unbound i setup DNS over TLS
9.9.9.9
dns.quad.net
port 853

traffic stopped entirely.
deleted the configuration.    and everything went back to working again!

I tried this, but unfortunately it didn't help (I had tried earlier to simply disable the entries) - thanks for the tip tho!

Any idea of what I can look at to resolve this?

I have so little config within Unbound that there's little to clear out, but I'll give it a shot...

waiting for the opnsense-lang update  :'(

seems it doesn't auto-synced.

Quote from: bob9744 on July 31, 2023, 05:26:53 PM
Any idea of what I can look at to resolve this?

I have so little config within Unbound that there's little to clear out, but I'll give it a shot...

Removed access-control-view.conf file (in /usr/local/etc/unbound.opnsense.d) - service started right up. Next: experiment with putting the file back and see if it fails again.

Unfortunately language updates are a lot of work and we couldn't fit this into the holiday season. We aim for 23.7.1 at the moment.


Cheers,
Franco

Quote from: bob9744 on July 31, 2023, 05:37:33 PM
Removed access-control-view.conf file (in /usr/local/etc/unbound.opnsense.d) - service started right up. Next: experiment with putting the file back and see if it fails again.

Is that a custom file? oO


Cheers,
Franco

Yep - I've had it in place for a while now without issue. I use it solely to map my router's name to it's IP for each vlan - convenient to avoid confusion on machines that can access the router through any vlan.

I just upgraded and it all seems to be working great! This is on a Protectli VP2410 running Adguard Home on port 53 and Unbound on 8053, and it all continued to work after the update.

Thanks for the hard work.

i just upgraded. it took some minutes but all services are up and running. looks great.
i want all services to run with wirespeed and therefore run this dedicated hardware configuration:

AMD Ryzen 7 9700x
ASUS Pro B650M-CT-CSM
64GB DDR5 ECC (2x KSM56E46BD8KM-32HA)
Intel XL710-BM1
Intel i350-T4
2x SSD with ZFS mirror
PiKVM for remote maintenance

private user, no business use

Updated and working fine.... thank you OPNSense Team

I also had no problems upgrading from 23.1.11_1 to 23.7 on a Protectli FW4B. I am using Adguard Home on port 53 and Unbound on 53531. Not using TLS.

Completely unspectacular. Thanks folks!
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Yup, seems fine, congrats!
Intel N100, 4 x I226-V, 16 GByte, 256 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

Runs like clockwork - thanks for the good work!

July 31, 2023, 09:19:09 PM #29 Last Edit: July 31, 2023, 09:28:53 PM by RamSense
updated to 23.7 also. Had a little hickup with internet not working, probably due to adguard home, but after a another manual reboot with first disabling adguard home and back to only bind the system was working. Put adguard home back on and all is running like it should.

Only in the terminal I have an error building up in # with this:

Quote[fib_algo] inet.0 (radix4_lockless#2180) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#2180) rebuild_fd_flm: sync rebuild failed
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed
and failures=1,2,3......up to 52 now and still counting up..

others having this also?
Deciso DEC850v2