- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jul 30 2025
Jul 29 2025
With the above fix, the configuration above will be preserved after a crash, for example, the grub boot settings such as hugepages.
I think we should go for option #2, since it's pretty flexible now. The old disable-uniqreqids option can be migrated to never on every connection.
FYI - this was completed/merged some time ago in: https://github.com/vyos/vyos-1x/pull/4263
Finally figured it out. PR: https://github.com/vyos/vyos-1x/pull/4628
I'm getting this same (or very similar) issue on 1.4.2LTS (running on VEP-4600).
PR for patches https://github.com/vyos/vyos-build/pull/998
We'll move to the FRR 10.4 https://vyos.dev/T7448
@frebib update failed all smoketests for the 10.3 https://vyos.dev/T7448, the same probably will be for 10.4
the task for FRR 10.4 upgrade https://vyos.dev/T7664
Jul 28 2025
Is there a policy on bumping FRR's version, or can we do this?
https://github.com/vyos/vyos-build/blob/bd78d813e31c23b1d75de3cc058484ce9ae3b0c9/scripts/package-build/frr/package.toml#L9
Looks like this made in into FRR 10.4 https://frrouting.org/release/10.4.0/
In VyOS 1.3, this command was used to integrate with StrongSwan's uniqueids=no setting in ipsec.conf, facilitating environments requiring non-unique IKE_SAs. However, with StrongSwan's transition to swanctl.conf, such unique ID management should ideally be performed via the connections.<conn>.unique parameter. More details about the migration you can find here.
Implemented as T7648
Jul 27 2025
Also I realized, that the insert_failed and drop counters of conntrack are increasing: