VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=circinus-public-unmaintained 2024-08-23T06:18:32+00:00 2024-08-23T06:18:32+00:00 Christian Breunig christian@breunig.cc 2024-06-15T19:40:04+00:00 urn:sha1:549a16f5b1437d437ccc873ded500b8cecd03c28 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" (cherry picked from commit 9e22ab6b2aee48029d3455f65880e45c558cf1da) 2024-06-25T14:01:49+00:00 Daniil Baturin daniil@vyos.io 2024-06-25T14:01:49+00:00 urn:sha1:1916a8cfcf21437219ff624a08bbf8408a4eaa80 snmp: T6489: use new Python wrapper to interact with config filesystem (backport #3694) 2024-06-24T14:08:26+00:00 Christian Breunig christian@breunig.cc 2024-06-15T06:03:37+00:00 urn:sha1:fad0128567931fd32e568896a0ba789396ab9311 (cherry picked from commit da29c9b3ab7b0cc23d64c8b033fc5a79c1b09174) 2024-06-24T14:05:26+00:00 Christian Breunig christian@breunig.cc 2024-06-20T20:30:40+00:00 urn:sha1:4bf4573efe89f80616b6189b2e84ac103113e8d1 Do no longer use my_set and my_delete as this prevents scripts beeing run under supervision of vyos-configd. (cherry picked from commit 7e0e8101998a6c8de6cb93c42bfbf1278c13f226) 2024-05-14T16:47:29+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2024-05-14T16:47:29+00:00 urn:sha1:7c438caa2c21101cbefc2eec21935ab55af19c46 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. 2024-05-01T18:55:57+00:00 Christian Breunig christian@breunig.cc 2024-05-01T18:55:57+00:00 urn:sha1:e7bb65894f86372dc0f6e8fd39b1628e0a224c68 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. 2024-01-01T20:30:03+00:00 Christian Breunig christian@breunig.cc 2024-01-01T20:30:03+00:00 urn:sha1:ad4958ff7b1a25564fcc6931d604288d7ff0a1d2 2024-01-01T20:28:09+00:00 Christian Breunig christian@breunig.cc 2024-01-01T20:28:09+00:00 urn:sha1:dd2a1955d66926dc4a987bad0acc52dcc6f5d433 2024-01-01T20:27:14+00:00 Christian Breunig christian@breunig.cc 2024-01-01T20:27:14+00:00 urn:sha1:c2dfba97446e9411b182f07c6227cc9427f247a8 2024-01-01T20:26:05+00:00 Christian Breunig christian@breunig.cc 2024-01-01T20:26:05+00:00 urn:sha1:3bd1a8eac54d6d4610e239088d91c145f748d12c