Quote from: nautilus7 on May 12, 2025, 12:09:24 AMIs anyone going to fix the version typo on the title of this thread?
Sorry ;)
Done
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: nautilus7 on May 12, 2025, 12:09:24 AMIs anyone going to fix the version typo on the title of this thread?
QuoteReading the questions:
I just realized that I completely forgot about the DynDNS. I mean the time it needs to update.
I was super quick with testing. What a shame, if this would be the reason..... :-[
So I just rolled back to 24.1.1, updated again to 24.1.2 (without the patch).
I will now test again and having a look at the DynDNS topic....
Quote(1) Do you use DNS entries as endpoint addresses?Yes, I have a dynamic IP, so I have a dyndns domain pointing to my OPNsense router.
Quote(2) Do you use tunnel addresses on your instances?Yes, this is the entry for the respective instance: 10.21.4.1/24,fd21:04::01/64
Quote(3) Do you have allowed IPs on your peers?Yes, different for split and full tunnel:
Quote(4) Do you have the instances assigned as interfaces?Yes
Quote(5) If yes for (4) do you have an IPv4/IPv6 mode set in the interface?IPv4 and IPv6 Configuration Type set to "none"
Quote(6) If yes for (4) do you have VIPs assigned to these interfaces?No
Quote from: franco on February 21, 2024, 02:15:36 PM
You could try reverting this one:
https://github.com/opnsense/core/commit/3340a32473
But it's basically a can of worms because it fixes a non-operational issue on the surface, which points to lack of proper setup if it causes breakage... perhaps meddling with VIPs or a left-over interface IPv4 configuration (this has been discontinued but some old configs may still have it) which is not optimal at the moment.
# opnsense-patch 3340a32473
Cheers,
Franco
Quotei've had vpn stuck at boot only if dns race condition was a problem (e.g. adguard as a main dns; unbound can't resolve if not routed to wan).