Messages

I've been struggling with IPv6 since the 24.7.1 update. High latency spikes, drops but never had to restart the DHCPv6 daemon tho. Just rolled back to 24.7_9 in a hope that fixes my issues.

@OPNsense team : something is terribly wrong in the IPv6 implementation in 24.7.1, just can't put my finger on it. Next to RRD stopping graphing on interface issues.

Point taken - this flow didn't work like that in my head :)

Maybe a small change in the UI suggested > the Subdomains tab > at the top it still says 'add domain' etc. That's not really logical at that page.

The current template for dynamic_dns takes the full fqdn as entrypoint. This should be split into subdomain / domain.tld. If you use the full subdomain.domain.tld, the Dynamic DNS/DNS plugin cannot find the right domain and errors.

Instead of

Code Select Expand


dynamic_dns {
provider bunny awsdasdasdasd
domains {
subdomain.example.com @
}
}


It should be

Code Select Expand


dynamic_dns {
provider bunny awsdasdasdasd
domains {
example.com subdomain
}
}


Expanding on this, if you have multiple subdomains in that same zone, they should be added like this

Code Select Expand


dynamic_dns {
provider bunny awsdasdasdasd
domains {
example.com subdomain subdomain2 subdomain3
}
}


I'm using Bunny.net as external DNS provider. It works perfectly fine for DNS/TLS certificates.

As soon as I enable "dyndns" on a record, it stops the process and I can't start it anymore until I remove the checkbox.
Can't seem to find a reason for it in the logs.

Downgraded the kernel to 24.7 seems to have fixed [most of] the issue.
Tried it with a few of the ones mentioned in the traceroute topic but that made everything unstable.
Running on a DEC740

IPv6 sometimes spikes to 100+ seconds but the packets don't get lost.

Since upgrading to 24.7.1 I see intermittent IPv6 drops for a few to 15 seconds. I get alerted each time by Uptime Kuma that a specific server isn't available anymore.

Would this be the same issue as the kernel problems with traceroute / icmp-echo?

It's not just ICMP that fails at those times but also existing SSH connections are dropped.

Updated & removed an additional 2 Caddy's from my Proxmox environment. Thanks!

Looking forward to that "Today is patchday!" announcement!

Awesome. I can wait. That UDM/Unifi controller thing stays one of the worst things out there.

@monviech - wouldn't it be possible to add the tls_skip_verify as an advanced option with an explicit warning or so?

I'm having a few internal services that are impossible to provide with a decent certificate, eg. Unifi controller, Scrypted, my Synology.

I don't use it either at this moment. I would be using cloudflare .. can give it a try but my domains mostly resolve by CNAME to my router A record. So no need to update them all when it changes.

I do have an internal RP running on Caddy that's not externally accessible and runs on an internal DNS zone. maybe I can remove that one too. Let me see over the weekend.

It doesn't always need to be a problem that's posted here, I think.

Thank you so much, development team, for the Caddy plugin. I've been able to remove a lot of complexity on my network due to this.

The setup was child's play and it works beautifully well.

I'm using the most basic setup.
No hints, track the interface and prefix from 0 > F depending on the VLAN I'm assigning it to.
No manual setups with DHCP or anything.

I might look into the setup by asani.

They've changed it so you now always get the same /57 on your router, it seems.

If you end up with a non-working IPv6 deployment on Telenet after years of trusty performance, it's not you.

Telenet started a roll-out of new firmware to their modems. You notice this by IPv6 not (reliably) working in the morning. Updates are done at night.

The only thing you need to do is change the Prefix delegation size from 60 to 57.

Did you ever get further than this? I found a ZTE cellular modem while cleaning up the garage and am trying the exact same thing. It works in Windows and I also get the same /dev/cuau2