https://github.com/vyos/vyos-1x/pull/2492
for equuleus

https://github.com/vyos/vyos-1x/pull/1956

https://github.com/vyos/vyos-1x/pull/1930

https://github.com/vyos/vyos-1x/pull/1771

https://github.com/vyos/vyos-1x/pull/1646

The latest 1.4 works well after merging.

@Viacheslav I've checked it using "VyOS 1.3.1-S1" version a problem the same.

https://github.com/vyos/vyos-1x/pull/1471

The command works well.

https://github.com/vyos/vyatta-op/pull/55

We can solve this problem in three ways.
Now the script (https://github.com/vyos/vyatta-op/blob/29703664633a20385a077083b4393738bdcb7409/scripts/tech-support-archive) creates up to 5 versions of support archives, after which it starts deleting the previous one. The problem is that each new version of the archives contains from 1 to 4 old archives. As a result, the archive can take up a lot of space.

Of course. This restriction comes from the communication providers. Through (VPN) - everything works well.

VyOS 1.4-rolling-202204090217 works well.

I've tested the scenario using VyOS 1.4-rolling-202204090217 and (esp lifetime '30'). Attached is the config.
After turning on the right and left routers, IPsec creates two tunnels that are updated every 10 seconds. (Tunnels are updated using strange intervals, the first 1-10 seconds, the second 10-20 seconds).

I tested it with VyOS 1.4-rolling-202204090217 and it works well for a while.

@n.fort
I ve added this code in to the scrip and the issue resolved.
if [ "$(id -g -n)" != 'vyattacfg' ] ; then
exec sg vyattacfg -c "/bin/vbash $(readlink -f $0) $@"
fi

Could you try to use "ikev2"? Will the same problem be if you use "ikev2"?

Similar situation in VyOS 1.3-stable-202202191602

I ve tested it:

VyOS 1.4-rolling-202201041316 - works well.

I've used for these tests (VyOS 1.4-rolling-202202010836)
The same situation in general when you want to use "!".
Bad exampels.

set nat source rule 10 destination port !1-5
set nat source rule 10 destination port !22
set nat source rule 10 destination port !http
set nat source rule 10 destination port telnet,!http,!123,1001-1005
set nat source rule 10 destination port telnet,http,!123,1001-1005

( VyOS 1.4-rolling-202202010836)- Rule name which starts with a number work well.

The same situation if you set the number or special symbol.

I've checked the same scenario on the cisco router.

Good question. I missed this moment.
So, if you want to reload in some minutes, VYOS offered you two variants:

1. To choose between 1 and 99
2. To set time when you want to reload VYOS if 99 minutes too short for you (for example 10:00, 12:45, 23:59, and so on)

But descriptions of thees command doesn't have enough information about it.

We didn't receive the customer's request.
The timers work without problems.
I'll open a design request to see the range 1-99.

I have emulated the same scenario in to vyos VyOS 1.4-rolling-202201041316
And it works well.
{

vyos@vyos:~$ show dhcp client leases
interface  : eth0
ip address : 172.168.32.146     [Active]
subnet mask: 255.255.255.0
domain name: localdomain        [overridden by domain-name set using CLI]
router     : 172.168.32.2
name server: 172.168.32.2
dhcp server: 172.168.32.254
lease time : 1800
last update: Fri Jan 28 01:09:31 UTC 2022
expiry     : Fri Jan 28 01:39:30 UTC 2022
reason     : RENEW

(VyOS 1.4-rolling-202201200814) - The same.

I ve testet it on (Version:VyOS 1.4-rolling-202201200814). It seems well.

I ve tested this scenario on VyOS 1.4-rolling-202201200814, as said Srividya you can choose minutes betwen 1-99.
If this is critical, you can expand the range by opening a "feature request".

I think we will have a problem with such a large number of rules. Now, if there are 1500 vyos rules, it takes 30 minutes to load. If there are 999999 rules, it will take a very long time to load.

@Viacheslav
If i use this format ('test test test') it works well.
Is it possible using description with space without '' ?

@adestis thank you. This issue isn't critical. It's more for to improve the design and for convenience of our customers.
You can use /32 to add a host, but we have to have the opportunity to add hosts without masks.
For example, if you need to create a group consisting of 1000 (or more random hosts), it's more convenient to use configuration without masks.

I ve check this situation on VyOS 1.3(beta-202112120443) and 1.4(rolling-202112160318) (platform SAF51015I) and interfases didont confus.

The bug was fixed. Need to check on SAF51015I platform

@c-po Everything works well, thanks. I've checked on this version (VyOS 1.3-beta-202112120443).
I m going to check it on 1.4

I've checked it and what we have:

As I understand it, after the reboot, the following scenarios are running:

"VyOS 1.4-rolling-202112081536" : sync-group scripts work well after rebooting.

I've checked this bug on "VyOS 1.3-beta-202112080938", everything is well.
After rebooting scripts(sync-groups) work as needed.

Thank you for sharing your information.

I confirm the bug. After rebooting script doesn't work on sync-groups. It's necessary to reload vrrp to start running the script (After rebooting).
More detail:
https://phabricator.vyos.net/T4041

I tested this bug on "vyos-1.3-beta-202112060443".

I have the same problem. I created a script, but it doesn't work. VRRP Log write that the skript is unsecure.

I checked it on these versions of VYOS. (VyOS 1.3.0-epa3, VyOS 1.3-beta-202112010443 , VyOS 1.4-rolling-202112021432)

If you add configuration to "vtysh" will you see config like this or another: