The similar bug with load if we change something in service https api
curl -k --location 192.168.122.11 --request POST 'https://192.168.122.11/config-file' --form data='{"op": "load", "file": "config.boot"}' --form key='foo'
{"success": false, "error": "", "data": null}Based on the requirements, it is natural to add this to the commit_revision post-commit hook of the config_mgmt module: this is low overhead as we use the existing configtree representation of the current config to save with ConfigTree().to_json().
@rherold Could you re-check it?
for me , it's ok . I didn't see another issue related it . we can close
@indrajitr Thanks!
Can we close it?
Applied to current and sagitta
Can we close it?
@indrajitr, Could you re-check and close if it was solved?
PR created: https://github.com/vyos/vyos-build/pull/434
Regarding STRIP_EXCLUDE variable... one idea is to assign it dynamically like so:
Proposed CLI:
set system syslog global service wireguard
Expected command for debug
echo "module wireguard +p" | sudo tee /sys/kernel/debug/dynamic_debug/control
To disable
echo "module wireguard -p" | sudo tee /sys/kernel/debug/dynamic_debug/control
PR https://github.com/vyos/vyos-user-utils/pull/7
vyos@r4# echo '{"system": "VyOS", "rate": 100}' | jq '.system'
"VyOS"
[edit]
vyos@r4#Try this
delete system conntrack ignore set system conntrack ignore ipv4 rule 10 source address 0.0.0.0/0
@xrobau noted that PR426 have an anomaly regarding one of the libraries during the strip-run:
Just to confirm, changing the if line does solve the issue, and I am able to log in.
@yun thanks for pointing that out: the detailed information was lost in the rewrite of config-mgmt, and I will restore, in some or other form. As I recall, the PR looked good, so let me check any changes and review.
Out of curiosity, shouldn't this just be moved to the end of the startup scripts?
Not sure if this should be re-opened, or, a new ticket should be created. It appears that this function is the only thing that creates etc passwd (etc), and it's only ever called once.
Forum thread about my issues: https://forum.vyos.io/t/10g-sfp-trouble-with-linking-intel-x553/12253 for reference.
Also adding these lines as to "completely ignore conntrack for all traffic" doesnt seem to help:
Just confirming this is still an issue, as mentioned in slack, and is really adding a lot of cpu load to pure routers
PR for VyOS 1.5 https://github.com/vyos/vyos-1x/pull/2335
The hostname part should be fixed by now in recent builds
PR for VyOS 1.4 https://github.com/vyos/vyos-1x/pull/2334
PR for 1.3.5 https://github.com/vyos/vyos-1x/pull/2333
Merged, will show up in nightly 2023-10-04.
Merged, will show up in nightly 2023-10-04.