- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 6 2024
Ok, that makes sense. Still need to place the tag.
Not all targets have username/password
For example for the future "location"
set system config-management commit-archive aws authentication access-key set system config-management commit-archive aws authentication secret-key set system config-management commit-archive aws bucket <my-bucket-name> set system config-management commit-archive aws path '/'
This way, predefined targets are more preferred.
May 4 2024
The format I started playing with looks like this:
set system config-management commit-archive 1 username 'xxx' set system config-management commit-archive 1 password 'xxx' set system config-management commit-archive 1 scheme 'scp' set system config-management commit-archive 1 location '192.0.2.1/backup'
Adding additional PR to add bonding.py to op-mode-standardized.json: https://github.com/vyos/vyos-1x/pull/3408
What about this format?
We still have named/predefined targets (scp|ftp|sftp|http|https) and <name> as tag
set system config-management commit-archive target scp <name> authentication username 'xxx' set system config-management commit-archive target scp <name> authentication password 'xxx' set system config-management commit-archive target scp <name> server '192.0.2.1' set system config-management commit-archive target scp <name> path '/'
need configuration index too or maybe name
so we can have several destinations for same protocol
I already looked a bit into it. What complicates it is the old location is a multi and one can add a list of locations.
Should be fixed after rewriting commit-archive T6304
NETNS was removed from the 1.4 series the other day so hopefully that feature can be worked on for 1.5 since its needed:
May 3 2024
What you're trying to achieve seems to be a derivate of https://www.wireguard.com/netns/
How was this configuration achieved? Or is it manually crafted?
Will be available in the next rolling release.
I think the problem is similar to https://vyos.dev/T5611
Upstream bug https://github.com/FRRouting/frr/issues/15912 fixed in https://github.com/FRRouting/frr/pull/15913
Checked. Runs without errors
The same bug as in T6283