vyos-1x.git/src/etc, branch fix/T8955-http-api-verify-tls

cli: T9077: quote expansions and send DSR to /dev/tty

2026-09-24T15:21:55+00:00

Harden the quote-aware '?' handler: quote readline buffer expansions and write the DSR query to /dev/tty so help still works when stdout is redirected.

cli: T9077: insert literal '?' inside quoted values instead of triggering help

2026-09-24T15:21:55+00:00

The '?' key is a raw readline binding (possible-completions), so a literal question mark can never be typed into a value: readline intercepts the keystroke before bash parsing begins and quoting cannot protect it. Values like remote-group URLs with query strings get silently corrupted ('.../blacklist?key=x' is stored as '.../blacklistkey=x') with no error at any stage. Rebind '?' to a bind -x handler that scans the line left of the cursor for an open single/double quote or a pending backslash escape. Inside a quote or escape the key self-inserts; otherwise it triggers the standard help via a DSR round-trip (printf '\e[5n' with the terminal's reply ESC [ 0 n bound to possible-completions), keeping the help path and output identical to the previous behavior. 'set terminal key query-help enable' now restores the quote-aware handler instead of the raw binding; 'disable' keeps its existing self-insert override, which takes precedence at login as before. Co-Authored-By: Claude Fable 5

journald: T9183: stop forwarding journal entries to syslog

2026-09-17T20:59:55+00:00

rsyslog reads the journal directly through imjournal (rsyslog.conf.j2 loads it alongside imuxsock), so journald forwarding the same entries to /dev/log delivers every non-kernel message twice. Both copies land in /var/log files and go to every remote syslog target, differing only in PID formatting. Ship the setting as a journald drop-in here rather than as a full journald.conf in vyos-build, so the image carries only the settings VyOS actually overrides. MaxLevelSyslog=debug comes across from that file; the rest of it was commented-out systemd defaults. Tested on a live 2026.09.11 router: with the drop-in in place a single logger event produces one entry, remote targets receive one copy, and kernel messages (imklog) and HAProxy's own socket are unaffected.

vbash: T7575: Trim trailing whitespace

2026-09-09T22:36:33+00:00

vbash: T7575: Prevent re-declare readonly variable

2026-09-09T22:36:33+00:00

Merge pull request #5446 from c-po/dhcp-static-route-flakiness

2026-09-08T16:00:08+00:00

static: T9278: reconcile FRR config after every DHCP lease event

sysctl: T9283: stop low-level Kernel messages on the console

2026-09-06T15:33:18+00:00

kernel.printk was set to "4 4 1 7" by the vyos-build image build hook 08-sysconf.chroot, which rewrote the Debian conffile /etc/sysctl.conf during ISO assembly. Move the setting to where the remaining kernel.* defaults live so the image build no longer has to touch a Debian conffile and the hook can be dropped.

dhcp: T9278: do not append the VRF option twice to ip route commands

2026-09-06T14:16:37+00:00

01-vyos-cleanup builds its route deletion with an explicit "vrf ". The ip() wrapper caught that command and delroute() appended $VRF_OPTION again, so both "ip route show" and "ip route del" ran with "vrf red vrf red". The FRR-down kernel fallback had the same flaw. Add vrf_option(), yielding $VRF_OPTION only when the arguments carry no "vrf" token, and use it in both places. The append cannot simply be dropped, as delroute() is also reached without a VRF. iptovtysh() parses single fields and was never affected.

dhcp: T9278: move DHCP client hook tracing to a gated debug level

2026-09-06T14:16:37+00:00

Each lease event emitted some fifteen daemon.info lines tracing internal steps rather than recording a change. Add a "debug" level to logmsg(), silenced unless /tmp/vyos.dhclient.debug exists, following the flag file convention used for FRR and ifconfig. Demoting alone would not help, as journald shows all priorities by default. Fifteen tracing messages move to debug; the sixteen recording an actual change stay at info. Also fix logmsg(): "warn" had no case arm although it is used, and the global LOG_PRIO leaked the preceding call's priority. It is now local.

static: T9278: reconcile FRR config after every DHCP lease event

2026-09-04T20:14:45+00:00

The default route derived from "interfaces address dhcp" is rendered from the DHCP lease file, so it is only known at lease time. Until now the sole runtime path into staticd was the one-shot vtysh injection in dhclient-enter-hooks.d/03-vyos-ipwrapper. That injection races the FRR reload of the very commit which started the DHCP client: dhclient runs with "-nw", thus the commit does not wait for a lease, and when BOUND arrives mid-reload frr_alive() can report FRR as down. The route is then installed into the kernel only and FRR never learns about it. Nothing recovers afterwards, as FRRender.generate() short-circuits on an unchanged configuration dict. The self-healing re-render used by "protocols static route dhcp-interface" was gated on /tmp/static_dhcp_interfaces, which never lists plain "address dhcp" interfaces - protocols_static.py does not even run on an interface-only commit, as no config-mode dependency points to it. Derive the DHCP dependent interface list from the configuration dict itself, both for the default VRF and for every named VRF, and use it for FRR change detection. Drop the interface list gate in the dhclient exit hook so any lease event requests a re-render. Also poll for the lease and for the rendered route in the affected smoketests instead of relying on a fixed sleep.