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.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 30 2025
Jul 29 2025
Jul 28 2025
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.
Jul 27 2025
Also I realized, that the insert_failed and drop counters of conntrack are increasing:
Jul 26 2025
I forgot to mention, that deleting the vrf_zones table "fixes" the issue.
Hi! I think I am hitting a similar/the same bug with a very minimal configuration.
Jul 25 2025
Jul 24 2025
Jul 23 2025
Jul 22 2025
I understand what you're saying. And I'm not suggesting that 4461 be reverted - it does fix the earlier bug you mentioned where the default route from SLAAC wasn't being cleared.
This "error" is related to https://github.com/vyos/vyos-1x/pull/4461.
Tried to fix here: https://github.com/vyos/vyos-1x/pull/4616
Jul 21 2025
@Viacheslav I just did some local testing with 3 VMs. A VM with today's rolling release to simulate a home router, a blank Debian VM for host testing, and a Sagitta VM simulating an ISP (running dhcpv6-server and router-advert services)
Fixed in FRR master: https://github.com/FRRouting/frr/pull/17544
Could be related to T7379 changes
Jul 20 2025
Jul 19 2025
Jul 15 2025
Jul 14 2025
We need a precise spec for it, what's required to support it. We also need a testing environment. I do think it would be nice to support it, but I wonder if it would bring many new customers.