<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/etc, branch rolling</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2026-08-11T15:54:25+00:00</updated>
<entry>
<title>Merge pull request #5391 from c-po/comp-file-fix</title>
<updated>2026-08-11T15:54:25+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2026-08-11T15:54:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=521346a16655ee40e9eb5588e2c0a6293dc7984a'/>
<id>urn:sha1:521346a16655ee40e9eb5588e2c0a6293dc7984a</id>
<content type='text'>
op-mode: T7250: restore image/file path completion for show/copy/delete file</content>
</entry>
<entry>
<title>op-mode: T7250: restore image/file path completion for show/copy/delete file</title>
<updated>2026-08-10T20:02:50+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-08-10T19:58:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=438bb7dabdcfa866df18302071bae0daad641332'/>
<id>urn:sha1:438bb7dabdcfa866df18302071bae0daad641332</id>
<content type='text'>
The imagefiles comptype dispatched to _vyatta_image_file_complete, a function
that was never ported when the legacy vyatta-op bash completion script was
imported in commit 72a704d2e2 ("T6527: add legacy Vyatta interpreter files
still in us"), causing "Invalid command: [_vyatta_image_file_complete]" on
tab-completion.

Port the original vyatta-image-complete interpreter so completion of works
again as it did on VyOS 1.4.x.
</content>
</entry>
<entry>
<title>container: T7736: disable IPv6 DAD for netavark bridges to fix aardvark-dns race</title>
<updated>2026-08-07T21:17:28+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-08-07T20:59:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=dabeff277774190d047155be6566da184b2b3e8f'/>
<id>urn:sha1:dabeff277774190d047155be6566da184b2b3e8f</id>
<content type='text'>
netavark assigns the IPv6 gateway address to a container "pod-*" bridge
and immediately invokes aardvark-dns to bind its DNS listener to it. While
the address is "tentative" during Duplicate Address Detection, that bind()
fails with EADDRNOTAVAIL and container startup fails for any IPv6-enabled
network.

The kernel only skips DAD for an address if both "all" and the specific
interface's own accept_dad are disabled at the moment the interface is
created. A per-interface override is always either too late for a network's
first-ever container - as the network can only be created in-time and not
explicitly before starting the first container.
</content>
</entry>
<entry>
<title>fstrim: T9133: skip /etc/fstab to properly identify devices to trim</title>
<updated>2026-07-28T14:35:22+00:00</updated>
<author>
<name>Nacho Barrientos</name>
<email>nacho.barrientos@cern.ch</email>
</author>
<published>2026-07-27T15:13:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=4806b2079e64b997f84217f655ec3b300f30a426'/>
<id>urn:sha1:4806b2079e64b997f84217f655ec3b300f30a426</id>
<content type='text'>
The default (coming from util-linux) fstrim.service in VyOS fails to
perform any trimming because it stops evaluating mount points after
reading /etc/fstab, which contains only overlay filesystems that
fstrim inherently ignores.

More info: https://vyos.dev/T9133
</content>
</entry>
<entry>
<title>utils: T9008: migrate remaining cmd() callers to cmdl() and remove cmd()</title>
<updated>2026-07-17T16:10:08+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-07-09T20:21:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=e0684c0c343835c7674a94424d847592511915b0'/>
<id>urn:sha1:e0684c0c343835c7674a94424d847592511915b0</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>T9071: rename 40-usb_modeswitch.rules to 41-usb_modeswitch_wwan.rules</title>
<updated>2026-07-10T04:15:37+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-07-10T04:15:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=ca8a6189eab702b8430b436b41cc6c38b5a5b9a1'/>
<id>urn:sha1:ca8a6189eab702b8430b436b41cc6c38b5a5b9a1</id>
<content type='text'>
Prefent ISO build issue:
  Skipping overridden file '/usr/lib/udev/rules.d/40-usb_modeswitch.rules'.
  Reading rules file: /etc/udev/rules.d/40-usb_modeswitch.rules
</content>
</entry>
<entry>
<title>udev: T9071: fix invalid ATTR key assignment</title>
<updated>2026-07-09T20:15:37+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-07-09T20:15:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=f41942cea2a57834370024510f11440506d5646b'/>
<id>urn:sha1:f41942cea2a57834370024510f11440506d5646b</id>
<content type='text'>
This fixes a (cosmetic) error which pops up in the logfiles:
  40-usb_modeswitch.rules:4 ATTR key takes '==', '!=', or '=' operator, assuming '='.

It was introduced in commit 93406237d ("wwan: T8924: add UDEV configuration for
USB modeswitch")
</content>
</entry>
<entry>
<title>T8923: normalize "can not" to "cannot"</title>
<updated>2026-06-16T18:24:44+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-06-16T18:24:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=fa853ed8f25b5b9bf396d6e819b2c6259e7f5f42'/>
<id>urn:sha1:fa853ed8f25b5b9bf396d6e819b2c6259e7f5f42</id>
<content type='text'>
Replace two-word "can not" / "Can not" with "cannot" across comments,
ConfigError messages, CLI help text, and op-mode output.

Standard SNMP MIB files under mibs/ are left unchanged.
</content>
</entry>
<entry>
<title>wwan: T8924: add UDEV configuration for USB modeswitch</title>
<updated>2026-05-25T11:41:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-05-25T11:41:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=93406237d7ecd4d28684828e2d127a864f44e862'/>
<id>urn:sha1:93406237d7ecd4d28684828e2d127a864f44e862</id>
<content type='text'>
When using WWAN interfaces, the Linux kernel selects configuration 2 by
default, but that does not work with ModemManager - configuration 3 (MBIM mode)
is a better choice.

Add UDEV rules for Huawei ME906s-158 and HP LT4132 which is a re-brand of
Huawei ME906s-158 to properly set MBIM mode on system startup.
</content>
</entry>
<entry>
<title>Debian: T8147: remove out-of-tree OpenVPN DCO module - incl. in Kernel 6.18</title>
<updated>2026-05-02T18:35:01+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-05-02T18:35:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=0bfde189978dec10de9994837c71bc795743aea7'/>
<id>urn:sha1:0bfde189978dec10de9994837c71bc795743aea7</id>
<content type='text'>
Move from the out-of-tree to an in-tree variant of the OpenVPN DCO module. As
this was not available in the previous used LTS 6.6 Kernel it now is available
while we upgrade to Linux 6.18.
</content>
</entry>
</feed>
