<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/interfaces_pppoe.xml.in, 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>2025-11-08T06:31:48+00:00</updated>
<entry>
<title>pppoe: T7485: make xml leafNode address a multi-type node</title>
<updated>2025-11-08T06:31:48+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-11-07T21:11:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=b9f0a9243b50211d7c21e996766c2ee9fd3b685c'/>
<id>urn:sha1:b9f0a9243b50211d7c21e996766c2ee9fd3b685c</id>
<content type='text'>
Commit fb9f2f3e950 ("pppoe: T7485: allow explicit request for CPE IPv6 address
via IA_NA") introduced the CLI node definition for address dhcpv6, which at the
time had only a single available option. Because of that, the node wasn't
defined as &lt;multi/&gt; in the XML schema.

However, the generic interface code expects address to be a &lt;multi/&gt; XML node,
which is translated into a list in Python. This mismatch caused an error
referencing the letter d, corresponding to the first character of dhcpv6.
</content>
</entry>
<entry>
<title>pppoe: T7485: allow explicit request for CPE IPv6 address via IA_NA</title>
<updated>2025-10-09T15:16:05+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-10-09T15:16:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=fb9f2f3e95036b75863c184e64aae14d086a32ba'/>
<id>urn:sha1:fb9f2f3e95036b75863c184e64aae14d086a32ba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>interface: T4627: not every interface type supports IPv6 interface-identifiers</title>
<updated>2025-04-23T18:17:06+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-04-23T18:14:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d0a20884614e773b074c39cd496717440faa89c1'/>
<id>urn:sha1:d0a20884614e773b074c39cd496717440faa89c1</id>
<content type='text'>
Turns out commit b124f0b3b ("interface: T4627: support IPv6 Interface
Identifier (token) for SLAAC") uncovered a wrong assumption in VyOS that every
interface type in use always supports SLAAC and IPv6-ND (neighbor discovery).

This is not true for WireGuard, Tunnel and VTI interfaces, thus do not provide
that CLI option. In addition SLAAC support should be removed for those interface
types in a future PR.
</content>
</entry>
<entry>
<title>T6863: Fix default distance for PPPoE (#4229)</title>
<updated>2024-12-12T19:14:17+00:00</updated>
<author>
<name>Roman Khramshin</name>
<email>HollyGurza@users.noreply.github.com</email>
</author>
<published>2024-12-12T19:14:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=678c6cd00412cad5d788da210c6dfeae6e77907c'/>
<id>urn:sha1:678c6cd00412cad5d788da210c6dfeae6e77907c</id>
<content type='text'>
set `default-route-distance` to 1</content>
</entry>
<entry>
<title>T5474: establish common file name pattern for XML conf mode commands</title>
<updated>2023-12-31T22:49:48+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-12-30T22:25:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=4ef110fd2c501b718344c72d495ad7e16d2bd465'/>
<id>urn:sha1:4ef110fd2c501b718344c72d495ad7e16d2bd465</id>
<content type='text'>
We will use _ as CLI level divider. The XML definition filename and also
the Python helper should match the CLI node.

Example:
set interfaces ethernet -&gt; interfaces_ethernet.xml.in
set interfaces bond -&gt; interfaces_bond.xml.in
set service dhcp-server -&gt; service_dhcp-server-xml.in
</content>
</entry>
</feed>
