strange behavior after update to Version 24.1.2 (and until 24.7.2)

[Matzke]

... still present on 24.1.8

[franco]

... GitHub ticket?


Cheers,
Franco

[schnipp]

I can confirm, the issue still persists in Opnsense version 24.1.8

@Matzke: Can you please share the github ticket id

[franco]

Might be related to https://github.com/opnsense/core/issues/7452 -- the patch is https://github.com/opnsense/core/commit/9a3caab85 but will only land in 24.1.9.


Cheers,
Franco

[schnipp]

Thank you.

I am not sure whether this issue is covered by the mentioned ticket. Since the error is not critical (restarting the service after booting temporarily fixes the problem), I will test after OPnsense 24.1.9 is released  :)

[schnipp]

Looks good, IPv6 is back again.  :)

Many thanks

[Matzke]

Dear all,

I just updated to OPNsense 24.1.9_4-amd64 and after a reboot - problem is still present and not solved.

I didn't opened a ticket because have very little time (at the moment health-related and lot's of visits for myself at hospitals). I hope it will be solved.

The problem is a bit of critical because it can only easily be solved when I'm on the site where opnsense is installed (I can't solve it remotely because all outside WAN ports (NAT as well as OpenVPN) are unreachable).

[Yszty]

Same problem here with: OPNsense 24.7_9-amd64

I setup mirror configuration, same devices, same ISP, mask /28. Only one difference is opnsense version. With    OPNsense 24.1.6-amd64 everything working.


On OPNsense 24.7_9-amd64 after switch from backup to master.

* DNS broke - no name resolution
* GW pings failed - declaring GW down

after some time

* GW went up BUT

I was able ping 8.8.8.8,
but unable to ping google.com

after permanently switch off backup node and restart master, everything started working normaly.

[Matzke]

Dear Yszty,

I think this is not the same problem because I don't have a mirror configuration - I have a single OpnSense on every site.

But unfortunatelly I can report, that the problem still exists in 24.7.2-amd64

I think a restart of service "Gateway Monitor"  can solve the problem after restart of OPNSense - but therefore I always have to be on the site and can't do anything from remote because in 90% OPNSense isn't reachable from outside after restart/update.

Please help.