Requires rewriting function show to python-systemd
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 2 2022
on nightly build nftables v1.0.5 and kernel 5.15.76
As a first step, we need a wrapper script to control the start, stop and restart of socat, because socat sometimes exits automatically
As a first step, we need a wrapper script to control the start, stop and restart of socat, because socat sometimes exits automatically
Nov 1 2022
I created a PR to solve this specific issue (and some more related to this): https://github.com/vyos/vyos-1x/pull/1637
normally, when I want to make an empty-base config, I save config.boot another place. So I load it when I need to restart the configuration. I was thinking that we can make something like it by cli, it should be saved in the first config.boot file and restored.
Maybe a simplified and interactive cli, as when adding new image? So user can decide what to do with other images and containers.
Adds firewall node rule N source/destination fqdn domain.com for single domains per rule and refactors resolver daemon.
In addition to the configuration, you also need to reset all logs/custom scripts and boot from the base image.
What will be if you have several images? Should we delete all other images?
What will be if you have container images? Should we delete them?
And there are many other nuances.
@Arc771
Could you provide an example of how to generate the required keys? We will test it.
But It should be a separate task
So the original task means that we don't have new CLI options in login keys
Missing sk-ssh-ed25519
vyos@r14# set system login user foo authentication public-keys foo type Possible completions: ssh-dss None ssh-rsa None ecdsa-sha2-nistp256 None ecdsa-sha2-nistp384 None ssh-ed25519 None ecdsa-sha2-nistp521
Oct 31 2022
Seems to be not fully functional
Oct 30 2022
Oct 29 2022
@zsdc could we backport it to 1.3?
Backport for VyOS 1.3.3 https://github.com/vyos/vyos-1x/pull/1629
Good point, I'll try and look into this and see if it can be handled everywhere the new PKI nodes are used.
Still on track for 1.4 ?
Oct 28 2022
There's something weird happening with this. If you change simply persistent-keepalive from 25 to 30 or 30 to 25 will reactivate the peer. At least thats my experience. Doing anything else didnt work for me including:
Best suggestion seems to be introducing a script to call podman stop -t N on shutdown/reboot to reduce the timeout before SIGKILL is sent.
Backported in https://github.com/vyos/vyatta-cfg-quagga/pull/97
Is there some progress? VPP is available for AArch64 in meantime.
Here some news about VPP performance: