- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 4 2023
Sep 3 2023
Disabling all validators for both vyatta-cfg and vyatta-op bring the boot time down to approx 73 seconds.
Modifying node.def (comment out "syntax:expression:") recursively in the paths of:
Moving along in the blamegame I will after a tip try to disable the various validators being runned.
Any updates to this?
That relates would seem reasonable. I'm seeing a similar explosion in commit lag but I have zero static routes. I did change to zone-based firewall and added about 6 vlans. Lines of my config went from ~500 to ~3000. Commit times increased almost linearly.
Can be related: https://vyos.dev/T2431
Continued debugging by also modifying /usr/libexec/vyos/services/vyos-configd by adding:
Attempted some debugging on this issue.
According to https://man7.org/linux/man-pages/man7/capabilities.7.html this capability can load, unload AND delete kernel modules.
@Viacheslav, can you backport this to 1.3
Still occurs for:
PR created: https://github.com/vyos/vyos-build/pull/392
Verified working with VyOS 1.4-rolling-202309030023.
Was missing quotes around the variable within lb_config_tmpl like so:
Some further testing:
Reference to https://jonathancarter.org/2015/04/06/squashfs-performance-testing/ using 1M blocksize will give approx the same readspeed as with default 128k blocksize but result in an even smaller file.
Regarding filesystem.squashfs the changes through changed mksquashfs syntax are:
Was missing quotes around the variable within lb_config_tmpl like so:
Sep 2 2023
The firewall refactoring released 4th aug 2023 only (so far) took care about the documentation in the configuration section:
PR created: https://github.com/vyos/vyos-build/pull/391
PR created: https://github.com/vyos/vyos-build/pull/390
PR389 build failed:
Sep 1 2023
PR created: https://github.com/vyos/vyos-build/pull/389
There was a similar case where it turned out that INPUT/OUTPUT chains for the firewall must be updated to include the stuff VRRP is doing.
Reported in: https://forum.vyos.io/t/error-show-dhcp-lease/12030
See this task instead: https://vyos.dev/T5536
At the moment of applying vrrp configuration eth1 IPv6 address
inet6 2001:db8::3/125 scope global tentative
Then
inet6 2001:db8::3/125 scope global
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2191
Thanks for the follow-up @eyanulis!
Aug 31 2023
Dear Sir
Problem is with virtual address is not reachable on this build. Does not work after VRRP restart.
Close it for now.
There are no requirements to do it.
Ok, thanks for the info.
We have seen occasional corruption of config.boot during system update, as reported, for example:
https://vyos.dev/T5267
That issue has been resolved here:
https://vyos.dev/T5520
Try restart vrrp
There could be this bug https://vyos.dev/T5533
Just use /usr/bin/accel-cmd -p 2001 pppoe interface add "xxx"
Note that the PR for T4797 was never updated for requested changes:
https://github.com/vyos/vyos-1x/pull/1648
Any updates on this?
Still bug
vyos@r1# set service webproxy Possible completions: append-domain Default domain name > authentication Proxy Authentication Settings +> cache-peer Specify other caches in a hierarchy cache-size Disk cache size in MB (default: 100) default-port Default Proxy Port (default: 3128) disable-access-log Disable logging of HTTP accesses + domain-block Domain name to block + domain-noncache Domain name to access without caching +> listen-address IPv4 listen-address for WebProxy [REQUIRED] maximum-object-size Maximum size of object to be stored in cache in kilobytes mem-cache-size Memory cache size in MB minimum-object-size Maximum size of object to be stored in cache in kilobytes outgoing-address Outgoing IP address for webproxy + reply-block-mime MIME type to block reply-body-max-size Maximum reply body size in KB > url-filtering URL filtering settings
Fixed VyOS 1.3-stable-202308240442
set interfaces tunnel tun1 encapsulation 'gre' set interfaces tunnel tun1 remote '203.0.113.254' set interfaces tunnel tun1 source-address '203.0.113.1'