Is there a specific reason not to put it in vyos-1x instead?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 1 2021
Apr 25 2021
Apr 22 2021
Apr 16 2021
Apr 15 2021
Apr 1 2021
Mar 23 2021
Mar 15 2021
Mar 14 2021
Sadly, this isn't a trivial update due to dependencies. However, Microsoft's own documentation says the version that is unsupported for real is 2.2.10, and 2.20 is still supported, even if they recommend the very latest one.
This is a config syntax design mistake on our side indeed. The "preference" option should have always been under "cache".
Feb 28 2021
I agree we should just check if it starts with a letter and doesn't include characters that an FQDN cannot have.
Feb 24 2021
Feb 22 2021
Feb 18 2021
Well, they do work together.
Feb 17 2021
Feb 11 2021
Feb 6 2021
The preliminary idea is to use load-balancing inbound syntax for balancing load between multiple hosts inside the network (i.e. LVS) and load-balancing outbound for balancing connections between multiple WAN interfaces.
Feb 4 2021
Yes, but since it won't solve the notification problem, these are separate concerns. Let's make a new task for migrating that script from atd to systems for scheduling reboots.
Feb 3 2021
Jan 31 2021
Jan 27 2021
I think we can make it a systemd service that is started on commit-confirm and stopped on confirm.
No one complained in a long time. ;)
If it re-appears, feel free to reopen. We also need to find a platform that knowingly does IKEv1 lifetime negotiation for testing this.
Last I checked it was able to log in the post-rewrite code. If the problem re-appears, feel free to reopen of course.
Jan 26 2021
Jan 24 2021
In light of the mode-force in 1.2.x, we definitely can't make this the new default within an LTS branch.