Messages

well at least... we learn something rigth?
never put a new releases in production without testing...
if you do... better have a backup plan...
there are reasons why there are users still on older 21.x or 20.x release

everyone knows that for all releases there will always be bug... thing is opnsense/franco is at it solving/fixing the bug.

there is a patch out for testing...

# opnsense-patch e8d42b6

patch created by @franco
needs to be executed in the console, have already applied it and seems to have fixed the issue in may test.
please test the patch out if possible.

thread with similar issue
https://forum.opnsense.org/index.php?topic=29824.0
github bug report
https://github.com/opnsense/core/issues/5956

no it is a bug in 22.x, something must have changed in the code, there is already a patch, but has not yet been included in 22.7.2.

# opnsense-patch e8d42b6

patch created by @franco
needs to be executed in the console, have already applied it and seems to have fixed the issue in may test.
franco said it will be included in 22.7.3, pending test reports also


https://github.com/opnsense/core/issues/5956

I think it is, what I'm doing now is clicking edit in gateways and changing nothing, for the monitor IP to go online.
will try that static route approach, as it is bother some to keeps doing it.

hope the patcht/fix we dont have to wait long.
thanks

might be related

https://forum.opnsense.org/index.php?topic=29824.0

having the wan monitoring being down even after the connection is restored

hmmm may be same issue
https://forum.opnsense.org/index.php?topic=29757.0

once the wan link is down or for a long time it seems to be tagged as down indefinitely

how to you distinguish
"my lan subnets" and "the rest"

typically you would set a wan group with wan1 tier1 and wan 2 teir 2 as WANmulti_rest
create or edit the default allow all, to use WANmulti_rest as gateway
create a rule above that for the "my lan subnets" for gateway wan2

are you on multiple lan? or just 1?

did it install correctly? my remote server still says no new updates
cant still detect 22.7_4

which update prompt? 22.7.1?

Yeah, 22.7.1. My post with my latest update woes is on the bottom of the previous page.

Do the update/changelog details and the install files come from different sources?

I'm just wondering as I've changed nothing, nor rebooted and now I'm getting the update prompt. The only thing that seems to make sense in this situation is that it's picked up the update (directly from Deciso?), but the University of Kent mirror that I use didn't yet have a copy of the new files to install.

which update prompt? 22.7.1?

I have clean install(using the 22.7 image) the server near me, yesterday and has updated with the latest 22.7.1 this morning.
clean installed worked for me though.

the remote unit I have has not detected the 22.7.1 update, I would be clean installing that one also in the future. and see what happens

1.1.1.1 and google DNS IPs.

yes there would be access... though since this is a 5G modem, sometimes I have to actually restart the modem but once it is online, the monitoring IP status would not change.
have to click edit save without actually changing anything will make it online
as if monitoring IP is sort of "blocked", denied or indefinitely set to "down" until a complete restart of the monitoring service.

may 5G gateway disconnects alot, which may require it to reboot.
may issue is that if the modem is rebooted somehow the monitor IP, gets marked as down. what I do is replace it with another IP. or just hit edit and apply without changing the IP. it will then be marked as active.

supposed to be it should detect the modem to be active after some time right?

Hi

I have Dnsmasq DNS and Unbound.

Dnsmasq for the guest and one other vlan to my pihole.
(you can choose the interface where you want to listen)

unbound forward it to my technitiumdns server.

Works perfect so you can split the dns and try all things of setups :)

bg

if dnsmaq or any other DNS server, I have to do port forward correct? since no 2 services will have the same port? even if i have different listen ip/interface for both?
like dnsmaq port 53 interface "GuestLan"
ubound port 53 interface "LAN"

does DNSmasq allow inputting of forwarding DNS

EDIT:
ok got it to work via port forward, I incorrectly set it first as TCP only, now at UDP TCP and works correctly.
I am also now using, Ubound for my main LAN and Bind for my Guest Lan.

nice!

will try all your suggestion

is it possible to run 2 instance of ubound?
or set ubound to serve to different network?

1 for forwarding to porn and malware block DNS
and 1 for no blocking?

or should this be simply done with 2 servers/opnsense entirely


or if dnsmasq at port 54, how do I set it so that my free wifi network will use that as DNS?
"local:54" in the DNS server list in DHCP?