VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos-contrib/veeos-1x.git) https://git.amelek.net/vyos-contrib/veeos-1x.git/atom?h=current 2025-04-22T15:21:51+00:00 2025-04-22T15:21:51+00:00 Daniil Baturin daniil@vyos.io 2025-04-22T15:21:51+00:00 urn:sha1:801bdc92ca8e55a001f5b7883c4770372643a1f3 geoip: T5636: Add geoip for policy route/route6 2025-04-22T14:40:06+00:00 Alex Bukharov alex.bukharov@innablr.com.au 2025-04-22T14:40:06+00:00 urn:sha1:427ebbb1e103ff45774bdf79bd5b1cddeff2f686 2025-04-17T14:23:24+00:00 Christian Breunig christian@breunig.cc 2025-04-17T14:23:24+00:00 urn:sha1:54df1043f123f0c6f2140d8cf402657a7f0c9565 grub: T7327: honor "system option kernel" settings during image upgrade 2025-04-15T18:55:03+00:00 Christian Breunig christian@breunig.cc 2025-04-15T18:47:09+00:00 urn:sha1:3fe5f8fb95a444ecb5b8489736a2e33419746f93 When performing an image upgrade and Linux Kernel command-line option that should be passed via GRUB to the Linux Kernel are missing on the first boot. This is because when generating the GRUB command-line via the op-mode scripts the CLI nodes defining the options are not honored. This commit re-implements the code-path in op-mode which generates the strings passed via GRUB to the Linux Kernel command-line. NOTE: If (for a yet unknown reason) a Kernel command-line option string changes during a major - or minor - upgrade of the Linux Kernel, we will need to adapt that logic and possibly call a helper from within the NEW updated image rootfs. Thus we can ship future information back into the past like the "Grays Sports Almanac" from Back to the Future Part II. 2025-04-15T14:54:02+00:00 Daniil Baturin daniil@vyos.io 2025-04-15T14:54:02+00:00 urn:sha1:9e47c2153be7cc0e5ed21ca8a976336d4bf872d8 kea: T7281: Add ping-check, use built-in option for classless static routes 2025-04-15T14:51:25+00:00 Daniil Baturin daniil@vyos.io 2025-04-15T14:51:25+00:00 urn:sha1:2f54cbc0504a20424274e45b9210467d33acf919 ids: T7241: remove Fastnetmon from the base system 2025-04-15T14:41:30+00:00 Daniil Baturin daniil@vyos.io 2025-04-15T14:41:30+00:00 urn:sha1:a86a3980b4ffae9970de1abd123e02965ab3356a T7353: T7360: netplug: behavior change 1.3.8 -> 1.4 when interface with DHCP address looses carrier 2025-04-14T19:26:47+00:00 Christian Breunig christian@breunig.cc 2025-04-14T19:26:47+00:00 urn:sha1:588f2e02028bc3e0d1203c750c3cba56fb8291f2 When an interface goes down - e.g. cable unplugged - the DHCPv6 assigned IPv6 address is not removed from said interface. We should provide the same behavior as with IPv4. IPv6 address should be removed and dhcpv6 client restarted once the interface goes operational up again. 2025-04-14T18:24:56+00:00 Christian Breunig christian@breunig.cc 2025-04-13T05:25:32+00:00 urn:sha1:97e74caa682298323165baa5055483405b740dac The initial rewrite of vyos-netplug-dhcp-client by me tried to outsmart the DHCP client implementation by re-using vyos.ifconfig.Interface(). This added a regression where an interface loosing it's carrier no longer deconfigured it's IP address. This was a change in behavior form VyOS 1.3. In addition a bug is fixed as when a VLANs interface parent looses it's carrier we now also stop the DHCP client process. This script is now back to simply starting/stopping the DHCP client process. 2025-04-14T17:20:23+00:00 Simon 965089+sarthurdev@users.noreply.github.com 2025-04-14T17:20:23+00:00 urn:sha1:290de0c6d1435c9008ee155349123b637198c98e firewall: T7333: Use separate cache keys per inet family