This is not a backport candidate until the full OpenVPN rewrite is backported.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 29 2020
Parent task not yet listed for backport; discussed with @zsdc for possible inclusion in future.
I’ll mark it here for the future. "ldpd 100% CPU utilization"
ref_cpu_utilization
Appear to have done something wrong with the pull request (https://github.com/vyos/vyos-1x/pull/210), herewith the trivial patch:
Jan 28 2020
Using 1.3-rolling-202001270217, its happening too:
Actually, upon reflection, the parser error is just too many terms on the line, hitting HandlingError; the rare exception exists, but is misleading, so 'use cases and/or implementation' ...
As expected,
(1) This is a parser error
(2) It is independent of any specific configuration script; it can be reproduced by calling conf.get_config_dict() with uncommitted changes, from any conf_mode script.
Jan 27 2020
@hagbard, thank you! This feature works properly, last value define how many sessions server can to serve
works as expected on 1.3-rolling-202001270217
I solved this issue by doing the following:
Jan 26 2020
All right, we stay with squid, however I may drop squidguard but ask in the forum first if that feature would be required by many users.
I also can confirm this works in 1.2.4
Sounds like a duplicate of T1632
Sounds like a duplicate of T1632
Welcome, thanks for testing!
Maybe for future CLI designs, the following would be cleaner: set service snmp extension name 'foo bar' script /usr/bin/echo
vyos@vyos# set service snmp script-extensions extension-name 'foo' script /usr/bin/echo vyos@vyos# set service snmp script-extensions extension-name 'foo bar' script /usr/bin/echo
Restarting now no longer shows any error/warning
This is actually an "upstream" bug, see https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1384122 but it can be fixed via our own scripts.
Working fine on 1.3-rolling-202001260217.
Jan 25 2020
Sure, I can probably do that in a day or two, will report back! Didn't even think to try that on my test device, my mind was just stuck at not wanting to upgrade my production devices at the moment.
Ah, your version is a bit old that could have been prior to the migration of the ip enable-arp-ignore script to XML/Python. Could you please retest with a newer rolling release?
Exactly, there is a race condition which I try to reproduce, but can not as ow now with VMware.
I just tried it on a different device with a more clean config, and it's reproducable with this config:
Jan 24 2020
PR https://github.com/vyos/vyos-1x/pull/209
also added missing completion help values.
Confirming that I also report this on 1.3-rolling-202001240217. Just upgraded this morning and I see the same unknown layer 3 protocol error as reported.
This issue is still present in 1.3-rolling-202001240217
Unfortunately I can not reproduce this.