<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/data/configd-include.json, branch feature/T9082-codeql-cpp</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=feature%2FT9082-codeql-cpp</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2024-06-26T19:47:09+00:00</updated>
<entry>
<title>vyos-configd: T6510: autogenerate configd-include.json</title>
<updated>2024-06-26T19:47:09+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-06-26T19:13:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=9473800055e0e1e9833f4a41c6d5d5a8a0d27399'/>
<id>urn:sha1:9473800055e0e1e9833f4a41c6d5d5a8a0d27399</id>
<content type='text'>
Now that there is a build time validation that Config() is not instantiated
twice in a config mode script, and also as there are no more direct calls on
the my_set and my_delete binary, we can auto generate the list of helpers run
by vyos-configd.
</content>
</entry>
<entry>
<title>T5735: Stunnel CLI and configuration</title>
<updated>2024-06-24T14:16:31+00:00</updated>
<author>
<name>khramshinr</name>
<email>khramshinr@gmail.com</email>
</author>
<published>2024-05-29T13:46:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=f6131611e15a644312e3c4baf5b8f6387c2930e7'/>
<id>urn:sha1:f6131611e15a644312e3c4baf5b8f6387c2930e7</id>
<content type='text'>
Add CLI commands
Add config
Add conf_mode
Add systemd config
Add stunnel smoketests
Add log level config
</content>
</entry>
<entry>
<title>snmp: T6489: use new Python wrapper to interact with config filesystem</title>
<updated>2024-06-20T20:32:15+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-06-20T20:30:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=7e0e8101998a6c8de6cb93c42bfbf1278c13f226'/>
<id>urn:sha1:7e0e8101998a6c8de6cb93c42bfbf1278c13f226</id>
<content type='text'>
Do no longer use my_set and my_delete as this prevents scripts beeing run under
supervision of vyos-configd.
</content>
</entry>
<entry>
<title>Merge pull request #3652 from c-po/T6489-unionfs</title>
<updated>2024-06-17T18:00:13+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-06-17T18:00:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=14dd6e5deeb7b3b0b81264bac06d92e86b5b91be'/>
<id>urn:sha1:14dd6e5deeb7b3b0b81264bac06d92e86b5b91be</id>
<content type='text'>
T6489: Add support for CLI config scripts that change the underlaying working configuration</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>login: T6489: add smarter way to interact with the working config instead of my_set/my_delete</title>
<updated>2024-06-15T06:16:23+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-06-15T06:03:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=da29c9b3ab7b0cc23d64c8b033fc5a79c1b09174'/>
<id>urn:sha1:da29c9b3ab7b0cc23d64c8b033fc5a79c1b09174</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T3420: Remove service upnp</title>
<updated>2024-05-14T16:47:29+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2024-05-14T16:47:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=7c438caa2c21101cbefc2eec21935ab55af19c46'/>
<id>urn:sha1:7c438caa2c21101cbefc2eec21935ab55af19c46</id>
<content type='text'>
Remove `service upnp` as it never worked as expected, nft rules do
not integrated and custom patches do not seem like a suitable
solution for now.

Security:
UPnP has been historically associated with security risks due to its automatic
and potentially unauthenticated nature.
UPnP devices might be vulnerable to unauthorized access or exploitation.
</content>
</entry>
<entry>
<title>vrf: T6189: render FRR L3VNI configuration when creating VRF instance</title>
<updated>2024-05-01T18:55:57+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-05-01T18:55:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=e7bb65894f86372dc0f6e8fd39b1628e0a224c68'/>
<id>urn:sha1:e7bb65894f86372dc0f6e8fd39b1628e0a224c68</id>
<content type='text'>
When adding and removing VRF instances on the fly it was noticed that the vni
statement under the VRF instance in FRR vanishes. This was caused by a race
condition which was previously designed to fix another bug.

The wierd design of a Python helper below the VRF tree to only generate the
VNI configuration nodes is now gone and all is rendered in the proper place.
</content>
</entry>
<entry>
<title>vyos-configd: T4942: include config-management script</title>
<updated>2024-01-01T20:30:03+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-01-01T20:30:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=ad4958ff7b1a25564fcc6931d604288d7ff0a1d2'/>
<id>urn:sha1:ad4958ff7b1a25564fcc6931d604288d7ff0a1d2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>vyos-configd: T563: include webproxy script</title>
<updated>2024-01-01T20:28:09+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-01-01T20:28:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=dd2a1955d66926dc4a987bad0acc52dcc6f5d433'/>
<id>urn:sha1:dd2a1955d66926dc4a987bad0acc52dcc6f5d433</id>
<content type='text'>
</content>
</entry>
</feed>
