Messages

Quick update: It's working again after adding a new firewall rule to WLAN to use WANdsl as gateway for any (and also adding a DNS allow rule before that). Strange thing is: I did not have this rule before on 23.1, but it still worked somehow. Is it possible to have an active firewall rule that is not being shown in the web UI (on 23.1 that is, 23.7 did not show a rule in the UI and it did not work without that rule).

Something strange happened after upgrading my OPNsense from 23.1 to 23.7.
I have 2 WANs (WANcable, WANdsl), configured as single gateways (_DHCP).
I have 1 LAN (192.168.100.x)
I have 1 WLAN (192.168.200.x)
When using OPNsense 23.1 I (somehow) managed to configure that the WLAN should only use WANdsl for internet access while LAN only uses WANcable for internet access. It worked fine.
After the upgrade to 23.7 both LAN and WLAN only use WANcable for internet access and I don't know why.
Any ideas where to look? I can't find any hints in the official documentation.
Do I have to create special firewall rules that were not needed on 23.1? Any switch that changed somewhere in a deep submenu between 23.1 and 23.7? Or a bug? :-)

Hi,

I use OPNsense with two WAN interfaces (DSL and cable) and two internal nets (LAN+WLAN). I run Unbound to resolve DNS queries for my two local networks. I got the problem that when the cable WAN was down, DNS did not work anymore for my two internal networks. I expected Unbound to resolve DNS via the still working DSL WAN.
How does Unbound resolve DNS queries?
If "Enable Forwarding Mode" is enabled, it uses the DNS servers configured under "System->Settings->General". If there are two DNS servers configured, 1 for DSL, 1 for cable, Unbound would automatically use the other one if one of them was down?
If "Enable Forwarding Mode" is disabled, which WAN connection would Unbound use?

Confirmed for Firefox!

Hi,

just wanted to add: I had the same problem using 21.1.1!
I made some changes to the dhcpd via webGUI (changed the dhcp range, added another dhcp-range for another interface, more small stuff), opnsense saved everything without complaining, and then: same messages in log as meschmesch posted. Also: my new dhcp-range was not offered to the network, still old IPs were given out.
dhcpd status on dashboard was "red" (stopped), I could not start it by clicking on the "play" (start) button.
After the reboot everything worked (correct dhcp range offered, dhcpd webGUI dashboard button "green" again).
Took me a lot of time, until I found the forum post of meschmesch. Never would have thought I have to reboot a BSD to get something to work. ;)
This seems lika a bug in opnsense to me.