<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/op_mode/lldp.py, 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-06-16T18:24:44+00:00</updated>
<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>T7591: remove copyright years from source files</title>
<updated>2025-06-28T21:16:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-06-28T18:51:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=1478516ae437f19ebeb7d6ff9b83dd74f8e76758'/>
<id>urn:sha1:1478516ae437f19ebeb7d6ff9b83dd74f8e76758</id>
<content type='text'>
The legal team says years are not necessary so we can go ahead with it, since
it will simplify backporting.

Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \
's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors &lt;maintainers@vyos.io&gt;/g'

In addition we will error-out during "make" if someone re-adds a legacy
copyright notice
</content>
</entry>
<entry>
<title>T6045: Recreate show lldp detail views &amp; improve remote port selection</title>
<updated>2024-06-11T11:53:28+00:00</updated>
<author>
<name>Andrew Topp</name>
<email>andrewt@telekinetica.net</email>
</author>
<published>2024-06-08T16:18:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=83a51a045de5db99014f6886f5aca9b792200928'/>
<id>urn:sha1:83a51a045de5db99014f6886f5aca9b792200928</id>
<content type='text'>
If the remote device has explicitly sent the interface name as the portID,
we should use that first as the interface name, before working through
the previous priority order.

I've brought back LLDP detail views directly calling lldpcli. This can be
extended to render a template from op_mode/lldp.py, but lldpcli isn't bad
at rendering readable info. Raw mode (including detailed raw) is still
accessible for programmatic access.
</content>
</entry>
<entry>
<title>T5677: lldp shows empty platform if descr not in lldpctl output</title>
<updated>2023-10-23T04:07:53+00:00</updated>
<author>
<name>Adam Smith</name>
<email>zero1three@gmail.com</email>
</author>
<published>2023-10-23T04:07:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=fca8cce1c114f28cf2db8a0fe2ed7f8b37ea010c'/>
<id>urn:sha1:fca8cce1c114f28cf2db8a0fe2ed7f8b37ea010c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T5195: vyos.util -&gt; vyos.utils package refactoring (#2093)</title>
<updated>2023-07-14T20:18:36+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-07-14T20:18:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d1ca536da448749dff557f13ecae97b124026e96'/>
<id>urn:sha1:d1ca536da448749dff557f13ecae97b124026e96</id>
<content type='text'>
* T5195: move run, cmd, call, rc_cmd helper to vyos.utils.process

* T5195: use read_file and write_file implementation from vyos.utils.file

Changed code automatically using:

find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import read_file$/from vyos.utils.file import read_file/g' {} +
find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import write_file$/from vyos.utils.file import write_file/g' {} +

* T5195: move chmod* helpers to vyos.utils.permission

* T5195: use colon_separated_to_dict from vyos.utils.dict

* T5195: move is_systemd_service_* to vyos.utils.process

* T5195: fix boot issues with missing imports

* T5195: move dict_search_* helpers to vyos.utils.dict

* T5195: move network helpers to vyos.utils.network

* T5195: move commit_* helpers to vyos.utils.commit

* T5195: move user I/O helpers to vyos.utils.io</content>
</entry>
<entry>
<title>T4911: op-mode: bugfix AttributeError: 'str' object has no attribute 'items'</title>
<updated>2023-01-22T07:20:10+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-01-22T07:20:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=33c3a02729ae95a8173f902cddd039c17262fbcb'/>
<id>urn:sha1:33c3a02729ae95a8173f902cddd039c17262fbcb</id>
<content type='text'>
One can not always ensure that "interface" is of type list, add safeguard.
E.G. Juniper Networks, Inc. ex2300-c-12t only has a dict, not a list of dicts

So this is actually an upstream lldpd bug where the output depends on the amount
of data transmitted.
</content>
</entry>
<entry>
<title>T4911: op-mode: bugfix TypeError: 'NoneType' object is not iterable</title>
<updated>2023-01-21T08:22:53+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-01-21T08:22:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=1e2238e3870309f48506a25c730661936b09a9d1'/>
<id>urn:sha1:1e2238e3870309f48506a25c730661936b09a9d1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T4911: op-mode: bugfix TypeError: string indices must be integers</title>
<updated>2023-01-21T08:23:07+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-01-21T08:22:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=a55dcaee83b0966bc9564e0a7996b6e1b4e922a6'/>
<id>urn:sha1:a55dcaee83b0966bc9564e0a7996b6e1b4e922a6</id>
<content type='text'>
One can not always ensure that "capability" is of type list, add a safeguard.
E.G. Unify US-24-250W only has a dict, not a list of dicts.
</content>
</entry>
<entry>
<title>T4911: op-mode: rewrite LLDP in standardised op-mode format</title>
<updated>2023-01-12T18:38:32+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-01-12T17:07:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=bc42dc94cd9d9979e84b4bd6e086893358417c92'/>
<id>urn:sha1:bc42dc94cd9d9979e84b4bd6e086893358417c92</id>
<content type='text'>
</content>
</entry>
</feed>
