VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=fix%2FT8955-http-api-verify-tls 2026-08-14T18:38:45+00:00 2026-08-14T18:38:45+00:00 Ritika Chopra r.chopra@vyos.io 2026-07-20T19:47:51+00:00 urn:sha1:1b98452d7e035c68849ebcb3242ecae25d5a9795 ROOT-CAUSE: Some Azure VF interfaces miss to get renamed leading to errors in the downstream rules and mess up with the interface names. Two main problematic scenarios were found which prohibited the renaming of a VF interface to vf_ethN: 1. Missing udev add event, when change event is received directly 2. A VF interface registering during rootfs stage FIX: Rule 63: -Azure VF naming is now handled by a dedicated helper - vyos_vf_name to provide collision-free names for VF interfaces. The helper vyos_vf_name would be packaged into initramfs so the same behavior works in early boot and normal boot (a separate PR). -Rule 63 is now guarded to prevent recursive renaming of VF interfaces. Rule 65: -A fallback VF rename path has been added for any leftover VF interfaces that were missed to be renamed due to some unexpected situation. Those VF interfaces are renamed prior to running persistent renaming of synthetic interfaces. This prevents VF interfaces from being considered as synthetic interfaces which may lead to errors in the flow of execution. -Rule 65 is now guarded so generic persistent naming does not override VF names. 2026-08-08T16:33:38+00:00 Christian Breunig christian@breunig.cc 2026-08-06T19:59:21+00:00 urn:sha1:22cfee116c9935f4a33da4923eff189f2f646371 Multi-vendor PCIe NIC systems could lose or rename Ethernet/wireless interfaces on boot, because naming was decided from a single per-device udev event before all hardware had a chance to enumerate. Replace that with one authoritative pass, run once configuration is available during router startup: wait for configured hardware, apply every hw-id binding, and name whatever has none yet by PCIe distance from the root complex and MAC address - the same result every boot. A node with its hw-id deleted (NIC replacement) or its whole configuration removed is treated as an ordinary open slot, filled the same way - recovering its original hardware whenever the interfaces that vacated slots this boot also show up as candidates. Boot now reports any interface still unresolved, and the pass is covered by a new test suite in vyos-build named: make testifname Assisted-by: Claude:claude-sonnet-5 2026-07-17T16:10:08+00:00 Christian Breunig christian@breunig.cc 2026-07-09T20:21:52+00:00 urn:sha1:e0684c0c343835c7674a94424d847592511915b0 Complete the safer-subprocess migration started by the cmdl()/ifconfig refactoring and convert every remaining vyos.utils.process.cmd() call site to the list-based cmdl(). Drop the vyos.utils.process.cmd() implementation as it is no longer in use. 2026-03-27T15:00:17+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2026-03-27T14:43:47+00:00 urn:sha1:139b0841f8242a5c6ebdafb37380c1fb78342aae Fix typos and mistakes No functional changes 2025-09-13T19:02:12+00:00 Christian Breunig christian@breunig.cc 2025-09-13T11:25:34+00:00 urn:sha1:0d95db6e4a872b1004cfbb7373931f62003287d3 Fix this build warning by placing the vyos_net_name script in it's own udev folder to not accidently be copied to a wrong location.