| Age | Commit message (Collapse) | Author |
|---|
|
|
|
T6868: Monitoring Loki Basic Authentication Password Length Limit Inc…
|
|
vpp: T8261: Refactor resource settings into 'resource-allocation' section
|
|
|
|
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
Grafana Cloud token consist of several components that are put into a json structure, base64 encoded and have also a prefix.
Contents of the Token:
Name of the Token (max 255)
Organization (currently 7 digits)
Secret (fixed 24)
Region (longest currently 20)
That beeing said, the length can easily exceed 255 chars. They dont expect the Password to be longer than 500 chars. I propose to simply set 512.
|
|
srv6: T6977: add srv6 encapsulation source-address
|
|
vpp: T8274: Remove dpdk-options section for num-* parameters
|
|
Remove `dpdk-options` under `set vpp settings interface <ethN>`
and move its child options to the interface level:
- `num-rx-desc`
- `num-rx-queues`
- `num-tx-desc`
- `num-tx-queues`
Also remove `set vpp settings interface <ethN> dpdk-options promisc`.
|
|
vpp: T8266: Add global `interface-rx-mode` setting and remove per-interface commands
|
|
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
|
|
|
commands
Add `set vpp settings interfaces-rx-mode <polling|interrupt|adaptive>`
to configure RX mode for all interfaces. Raise error if any interface
does not support the selected mode.
Also remove per-interface rx-mode commands:
- `set vpp settings interface <name> rx-mode`
- `set vpp kernel-interfaces <name> rx-mode`
|
|
syslog: T8272: remove dead code from previous "file" logging support
|
|
T8257: image install search previous needs to consider legacy bind mount
|
|
Commit 395e3cb72 ("syslog: T6989: remove 'file' logging destination") removed
CLI support for custom file based logging targets. The code about logrotate
was not removed and just stayed "dead".
Dead code is removed by this commit.
|
|
vpp: T8268: Unify CPU settings into a single 'cpu-cores' node under 'resource-allocation'
|
|
'resource-allocation'
Replace legacy VPP CPU settings (main-core, skip-cores, workers, corelist-workers) with a single resource-allocation cpu-cores option.
CPU assignment is now handled automatically: two cores are reserved for the system, the VPP main thread is placed on the first available core, and the remaining allocated cores are used as workers.
This simplifies configuration and ensures consistent CPU allocation.
|
|
xml: T8271: cleanup duplicate includes and split duplicate code into new building blocks
|
|
bgp: T7984: add CLI support for "neighbor <N> remote-as auto"
|
|
T8270: fix yescrypt hash validation regex
|
|
lcd: T8213: add support for MTC S16209x
|
|
|
|
vpp: T8258: Move `poll-sleep-usec` out of `unix` section
|
|
Instead of `vpp settings unix poll-sleep-usec`
use `vpp settings poll-sleep-usec`.
|
|
vpp: T8262: Refactor IPsec settings to use only 'ipsec-acceleration' flag
|
|
|
|
$ make interface_definitions
$ git add -f templates-cfg
$ ... refactor
$ make interface_definitions
$ git diff templates-cfg
No change in any node.def file detected.
|
|
$ make interface_definitions
$ git add -f templates-cfg
$ ... refactor
$ make interface_definitions
$ git diff templates-cfg
No change in any node.def file detected.
|
|
Verified that the resulting node.def files are still the same by:
$ make interface_definitions
$ git add -f templates-cfg
$ ... refactor
$ make interface_definitions
$ git diff templates-cfg
No change in any node.def file detected.
|
|
During development and XML node refactoring the resulting node.def files are
rebuild over and over again. Unfortunately they are not cleaned up during
subsequent calls to "make interface_definitions" or "make op_mode_definitions".
This could cause previous build node.def files to still exist after a rebuild
which adds potential false-positives during refactoring.
|
|
|
|
|
|
|
|
Implementation has been tested using a virtual serial pipe as I (Christian
Breunig) did not find my hardware LCD display. You can easily do this via:
$ sudo socat -d -d PTY,link=/dev/ttyS99,raw,echo=0 PTY,link=/tmp/serial,raw,echo=0
$ sudo cat /tmp/serial
You will get a lot of control characters, but real information like the OS
Kernel version will scroll through.
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
FRR implemented a new know to learn the peers remote ASN from the BGP OPEN
message from https://github.com/FRRouting/frr/pull/16345.
|
|
|
|
vpp: T8254: Move 'nat44' and 'settings nat44' sections to 'nat nat44'
|
|
|
|
vpp: T8255: Changed logging level variable name
|
|
T8232: Simplify and extend config_dict construction
|
|
This commit changes logging settings naming:
- before: `set vpp settings logging default-log-level <alert>`
- after: `set vpp settings logging default-level <alert>`
|
|
For those images created with the legacy bind mount, the resident
config.boot at {mounted_image}/opt/vyatta/etc/config is the baseline,
not the saved config (which is then restored at boot). Image install
needs to search the legacy path at {mounted_image}/config as well as the
normalized path.
|
|
|
|
|
|
|
|
As a needed argument to the internal config_dict function, reify for
caching under vyos-configd or other running process.
|
|
|
|
|
|
|
