- User Since
- Oct 11 2021, 11:52 AM (67 w, 4 d)
Fri, Jan 20
Wed, Jan 18
Oct 27 2022
Oct 21 2022
Aug 28 2022
The latest 1.4 works well after merging.
@Viacheslav I've checked it using "VyOS 1.3.1-S1" version a problem the same.
Aug 16 2022
Aug 7 2022
May 16 2022
The command works well.
[email protected]:~$ show version
Apr 29 2022
Apr 22 2022
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.
Apr 17 2022
Of course. This restriction comes from the communication providers. Through (VPN) - everything works well.
Apr 11 2022
VyOS 1.4-rolling-202204090217 works well.
From my ISP access is closed for more than a month.
Apr 10 2022
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.
Apr 4 2022
Mar 24 2022
Mar 10 2022
Could you try to use "ikev2"? Will the same problem be if you use "ikev2"?
Mar 9 2022
Similar situation in VyOS 1.3-stable-202202191602
Feb 27 2022
I ve tested it:
Feb 16 2022
Feb 15 2022
Feb 14 2022
Feb 5 2022
VyOS 1.4-rolling-202201041316 - works well.
Feb 2 2022
I've used for these tests (VyOS 1.4-rolling-202202010836)
The same situation in general when you want to use "!".
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
Feb 1 2022
( VyOS 1.4-rolling-202202010836)- Rule name which starts with a number work well.
Jan 29 2022
The same situation if you set the number or special symbol.
I've checked the same scenario on the cisco router.
Jan 28 2022
Good question. I missed this moment.
So, if you want to reload in some minutes, VYOS offered you two variants:
- To choose between 1 and 99
- 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.
[email protected]:~$ show dhcp client leases interface : eth0 ip address : 18.104.22.168 [Active] subnet mask: 255.255.255.0 domain name: localdomain [overridden by domain-name set using CLI] router : 22.214.171.124 name server: 126.96.36.199 dhcp server: 188.8.131.52 lease time : 1800 last update: Fri Jan 28 01:09:31 UTC 2022 expiry : Fri Jan 28 01:39:30 UTC 2022 reason : RENEW
Jan 21 2022
(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".
Jan 17 2022
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.
Dec 24 2021
If i use this format ('test test test') it works well.
Is it possible using description with space without '' ?
Dec 21 2021
@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.
Dec 17 2021
I ve check this situation on VyOS 1.3(beta-202112120443) and 1.4(rolling-202112160318) (platform SAF51015I) and interfases didont confus.
Dec 16 2021
The bug was fixed. Need to check on SAF51015I platform
Dec 13 2021
@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
Dec 10 2021
I've checked it and what we have:
As I understand it, after the reboot, the following scenarios are running:
Dec 9 2021
"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.
Dec 7 2021
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).
Dec 6 2021
I tested this bug on "vyos-1.3-beta-202112060443".
The problem has been partially resolved. If you restart VYOS, scripts on syn-groups don't work. After using the "vrrp restart" command, everything is ok.
I have the same problem. I created a script, but it doesn't work. VRRP Log write that the skript is unsecure.
Dec 3 2021
I checked it on these versions of VYOS. (VyOS 1.3.0-epa3, VyOS 1.3-beta-202112010443 , VyOS 1.4-rolling-202112021432)