No access to URLs on WAN side after upgrading to 24.1 [SOLVED]

Started by pgh, January 30, 2024, 08:56:52 PM

Previous topic - Next topic
[SOLVED]
After upgrading to 24.1 I could no more access any host at the WAN side.
Calling "nslookup google.com" at terminal works great (on linux and windows) but the domain-names are not resolved!
I also tried the DNS Diagnose-Tool of my OPNsense, using 8.8.8.8, and it could receive the IP of amazon.com, but again no Domain-Name resolving when working with browser, calling apt-get etc.
Before upgrading to 24.1 I saved the configuration. I tried to solve the issue by restore the config saved before: the issue remains.
I also tried several restarts... did also not helped.
Now I am confused, sad, angry and cannot surf in the www :-(
Please help me!

Many of my VLANs lost internet, they can ping the firewall but unbound does not respond, cant ping 8.8.8.8. Automatic outbound nat rules are missing, i had to recreate them but still no internet.

S2S IPSec tunnels do not work anymore, up but no traffic.

Disabled Surricata and rebootet, no change.

Quote from: pgh on January 30, 2024, 08:56:52 PM
After upgrading to 24.1 I could no more access any host at the WAN side.
Calling "nslookup google.com" at terminal works great (on linux and windows) but the domain-names are not resolved!
I also tried the DNS Diagnose-Tool of my OPNsense, using 8.8.8.8, and it could receive the IP of amazon.com, but again no Domain-Name resolving when working with browser, calling apt-get etc.
Before upgrading to 24.1 I saved the configuration. I tried to solve the issue by restore the config saved before: the issue remains.
I also tried several restarts... did also not helped.
Now I am confused, sad, angry and cannot surf in the www :-(
Please help me!

Check if you still have an IPv4 gateway, two of my machines completly lost the IPv4 gateway entries. I had to recreate them by hand, luckly these remote firewall still had ipv6 running so i was able to fix it.