Hello sir, thank you !!!
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
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
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.
In multiple options, the prefix help values are not defined correctly.
The Teleport can be run in a container:
https://goteleport.com/docs/setup/guides/docker/
Mar 6 2022
Should be fixed by https://github.com/vyos/vyatta-cfg-firewall/pull/32
Mar 5 2022
Mar 4 2022
If the solution is so simple, whats the issue? from what I understand it's just a matter of working on:
vyos-vrrp-conntracksync.sh
Mar 3 2022
1.3.0:
Still generating the same config
Syntax for the executed commands are incorrect, please try with the following commands: