<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/interfaces_wireless.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-04-23T18:17:06+00:00</updated>
<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>T6693: wireless: Enable WiFi-6 (802.11ax) for 2.4GHz AccessPoints</title>
<updated>2024-09-07T16:07:57+00:00</updated>
<author>
<name>Alain Lamar</name>
<email>alain_lamar@yahoo.de</email>
</author>
<published>2024-09-04T20:28:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=194a14e958ad336d590ba8f076e163f6908dcddc'/>
<id>urn:sha1:194a14e958ad336d590ba8f076e163f6908dcddc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wireless: T6496: use mac-address validator on BSSID and move it up one CLI level</title>
<updated>2024-07-05T06:53:48+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-07-05T06:47:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=0c9499c5b3f7cc053c1f29ecf28d679c1a3156e2'/>
<id>urn:sha1:0c9499c5b3f7cc053c1f29ecf28d679c1a3156e2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wireless: T6496: use ascii regex for WPA passphrase constraint</title>
<updated>2024-07-05T06:48:31+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-07-05T06:44:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=5a6ac65fe0684fc5298de3daa8582294ac387b46'/>
<id>urn:sha1:5a6ac65fe0684fc5298de3daa8582294ac387b46</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wireless: T6496: support for EAP-MSCHAPv2 client over wifi</title>
<updated>2024-07-05T06:48:31+00:00</updated>
<author>
<name>Christopher</name>
<email>root@teritum.dev</email>
</author>
<published>2024-06-10T18:52:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=fc4263021acb72d2d8afb165922d9cb7e11b2bf1'/>
<id>urn:sha1:fc4263021acb72d2d8afb165922d9cb7e11b2bf1</id>
<content type='text'>
fix: attempt to fix indentation on `wpa_supplicant.conf.j2`

fix: attempt to fix indentation on `wpa_supplicant.conf.j2`

fix: incorrect bssid mapping

fix: use the correct jinja templating (I think)

fix: “remote blank space

fix: attempt to fix the formatting in j2

fix: attempt to fix the formatting in j2

feat: rename enterprise username and password + add checks in conf mode.

fix: move around `bssid` config option on `wpa_supplicant.conf.j2` and fix the security config part

fix: fix indentation on `wpa_supplicant.conf.j2`
</content>
</entry>
<entry>
<title>wireless: T6320: add 802.11ax at 6GHz</title>
<updated>2024-06-27T18:48:05+00:00</updated>
<author>
<name>Alain Lamar</name>
<email>alain_lamar@yahoo.de</email>
</author>
<published>2024-06-27T18:38:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d5e988ba2d0fa0189feff22374c9b46eb49e2e79'/>
<id>urn:sha1:d5e988ba2d0fa0189feff22374c9b46eb49e2e79</id>
<content type='text'>
Authored-By: Alain Lamar &lt;alain_lamar@yahoo.de&gt;
</content>
</entry>
<entry>
<title>wireless: T6318: move country-code to a system wide configuration</title>
<updated>2024-06-16T07:22:28+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-06-15T19:40:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=9e22ab6b2aee48029d3455f65880e45c558cf1da'/>
<id>urn:sha1:9e22ab6b2aee48029d3455f65880e45c558cf1da</id>
<content type='text'>
Wireless devices are subject to regulations issued by authorities. For any
given AP or router, there will most likely be no case where one wireless NIC is
located in one country and another wireless NIC in the same device is located
in another country, resulting in different regulatory domains to apply to the
same box.

Currently, wireless regulatory domains in VyOS need to be configured per-NIC:
  set interfaces wireless wlan0 country-code us

This leads to several side-effects:
* When operating multiple WiFi NICs, they all can have different regulatory
  domains configured which might offend legislation.
* Some NICs need additional entries to /etc/modprobe.d/cfg80211.conf to apply
  regulatory domain settings, such as: "options cfg80211 ieee80211_regdom=US"
  This is true for the Compex WLE600VX. This setting cannot be done
  per-interface.

Migrate the first found wireless module country-code from the wireless
interface CLI to: "system wireless country-code"
</content>
</entry>
<entry>
<title>wifi: T6095: incorrect country-code "uk" it's actually "gb"</title>
<updated>2024-03-05T19:19:03+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-03-05T19:15:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=45cd735f89a4b6c7419a26d2800d832c9da9f735'/>
<id>urn:sha1:45cd735f89a4b6c7419a26d2800d832c9da9f735</id>
<content type='text'>
All valid country codes can be retrieved from [1] and extracted which resulted
in the completion helper list of this commit.

1: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/tree/db.txt
</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>
