Hi all,
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 16 2022
FRRouting Release 8.2.2 was relased, when we will see this implemented?
Mar 15 2022
The same issue with set interfaces bonding bond0 arp-monitor interval 'X' option. Also extra conversion between variable types.
Added the fix to the same PR.
The PR is merged with the wrong Task number. This can be closed.
Mar 14 2022
IKEv2 has a different working behavior compared to the IKEv1. IKEv2 provides proper inline rekeying of IKE SAs by use of CREATE_CHILD_SA exchanges. This means that new keys may be established without any interruption of the existing IKE and IPsec SAs.
Mar 13 2022
Update download URL -> PR: https://github.com/vyos/vyos-vm-images/pull/26
Mar 12 2022
PR for 1.4: https://github.com/vyos/vyos-1x/pull/1247
Mar 11 2022
You are correct, my config is not correct.
emmm, I know it.
In T4288#119770, @chesskuo wrote:I found the swanctl.conf.
The config does not match the vyso config.I set the close_action as restart, but config does not show this line.
Your configuration should be like:
Mar 10 2022
A simplified validator that rejects non-ipv6 address range (still lacks of 1st ipv6 minor than 2nd address validator):
Re-open to investigate failure in vyos-configtest.
Re-open to investigate failure in vyos-configtest.
Re-open to investigate failure in vyos-configtest.
For 1.4, problem is in ipv6-range validator, which accepts lots of values that should be considered as invalid:
I'm going to be experimenting with Jinja 2 to see if we can incorporate it into our template processor.
Actually, let's leave it in 1.3 but backport the warning and generate public-key-command.
@zsdc Do you have any idea for CLI configuration mode?
Hello sir, thank you !!!
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
Mar 8 2022
system seems to be able to process flow data now and im seeing the flow data (netflow and sflow) reach my destination pathed via flow location, appears to work now!
I'm removing loadkey from 1.4. It will be removed from 1.3.1, as well. Eventually, the warning will be dropped from 1.4 but it will remain in 1.3.
Next, we need to create an OTP key generator in the VyOS CLI
PR with basic functionality:
https://github.com/vyos/vyos-1x/pull/1242
https://github.com/vyos/vyatta-cfg-system/pull/178
Mar 7 2022
Resolved in https://phabricator.vyos.net/T3774, but it will not be backported to 1.2.
Should be fixed in https://github.com/vyos/vyos-1x/pull/1241
I found the swanctl.conf.
The config does not match the vyso config.