Franco Fichtner
Franco Fichtner
Haven't heard back. If we still need to do something let me know.
@mimugmail @pmhausen you guys interested in review? does it make sense? otherwise I'll close.
@mimugmail @pmhausen kindly asking for review again ;) refs https://twitter.com/jurajlutter/status/1725096425279701456
I made a comment here: https://forum.opnsense.org/index.php?topic=47376.msg240322#msg240322 I can't really pin down where this issue suddenly comes from.
> I don't see it as an opnsense plugin issue. I think its a tailscale bug and they need to address it. They should honour the key expiry setting regardless...
As stated a while ago this could also be the way the plugin integrates into tailscale, but so far nobody made the correct assessment that the plugin has a mistake...
@bapt I think the basic gist is https://github.com/opnsense/pkg/commit/3856e4a3962061929753a195a630a585967519c7 although having the `!quiet` diagnostic in the batch case would also be useful IMO, which would make the `batch` argument spurious again...
Feature ticket is https://github.com/opnsense/core/issues/9135 -- it's on the roadmap for 26.1. > Also, it is considered best practice to use link-local addresses as next-hop on links between routers, not Global...
There's no automatic way to handle this since the link local is not really predictable how it is currently integrated. In theory the client first responds to DHCP link local...