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=vyos%2F1.3dev0 2019-12-10T09:08:43+00:00 2019-12-10T09:08:43+00:00 Christian Poessinger christian@poessinger.com 2019-12-10T09:08:41+00:00 urn:sha1:27dabfab5419cbf00f3b80683f31453db8bed1f9 Newer GCC version (8.3 in Debian Buster) no longer support the -ansi option as in GCC 4 used in Debian Jessie. Thus the URL which is used as regex for the proxy must be escaped properly - else the // in the URL is treated as C++ comment. 2019-12-06T19:58:56+00:00 Christian Poessinger christian@poessinger.com 2019-12-03T21:38:31+00:00 urn:sha1:6f42d44586fbed3f5addfe81fa5d6b4ab40f2dbf An XML include file can now inlude another XML include file. This is very handy on e.g. VIF or VIF-S interfaces that also have an address node. Thus more code is reused and simplified. 2019-12-06T19:58:56+00:00 Christian Poessinger christian@poessinger.com 2019-12-03T21:36:32+00:00 urn:sha1:2d96dbe667de57bc90eb4dc826cce3ed19e94823 As 219779bc6151 ("T1843: run interface-definitions though GCC preprocessor") implemented the foundation of using the GCC preprocessor to make our XML definitions more lightweight this commit transforms the configuration of VIF and VIF-S interfaces to this new style. It implementes it for the following types: * bond * ethernet * wireless 2019-12-06T19:58:56+00:00 Christian Poessinger christian@poessinger.com 2019-12-03T21:01:19+00:00 urn:sha1:0d4d4dd840e06c18250d73f27de61261ff141944 A lot of XML code is duplicated (VLAN, interface address) for instance. Such XML definitions should be moved to feature.xml.i files and then just pulled in via GCC preprocessor #include definition in e.g. bond or ethernet definitions. This will give us the ability to single-source repeating node definitions as: * Interface Address * Interface Description * Interface Disable * VLAN (both vif-s and vif-c) The .in suffix of the interface-definitions is a marker that those files are input files to the GCC preprocessor. They will be rendered into proper XML files in the build directory. Some node definitions have been reworder to remove escaped double quote occurances which would have been warned about by the GCC preprocessor. 2019-11-23T19:44:02+00:00 Christian Poessinger christian@poessinger.com 2019-11-11T20:54:51+00:00 urn:sha1:65d7bf3875b7c463c8d0632b879098128c30daa9 2019-11-08T16:05:48+00:00 DmitriyEshenko snooppy@mail.ua 2019-11-08T16:05:48+00:00 urn:sha1:bdd95c4fa54015a37bbe5c206469bd1b0552d0dc 2019-09-20T19:28:53+00:00 Christian Poessinger christian@poessinger.com 2019-09-07T10:29:12+00:00 urn:sha1:a610e328750e3cfc23c29a2cafb40d7ef7082b13 2019-09-12T15:40:00+00:00 DmitriyEshenko snooppy@mail.ua 2019-09-12T15:40:00+00:00 urn:sha1:785a2d26998db580a1996edba584aac612b11b3a 2019-09-10T17:28:29+00:00 hagbard vyosdev@derith.de 2019-09-09T18:55:54+00:00 urn:sha1:1017c8103f12ebd6db4f250d8a154571fff32db1 - param key location added in op-mode script - param delkey and listkey implemented in op-mode script - param delkey implemented in op-mode script - generate and store named keys - interface implementation tu use cli option 'private-key' 2019-09-06T10:56:56+00:00 Christian Poessinger christian@poessinger.com 2019-09-05T17:35:43+00:00 urn:sha1:98aafc8f704ef54b6ece514c038b6aea414df734 Tested using: Site 1 (VyOS 1.2.2) ------------------- set interfaces vxlan vxlan100 address '10.10.10.2/24' set interfaces vxlan vxlan100 remote '172.18.201.10' set interfaces vxlan vxlan100 vni '100' Site 2 (rewrite) ---------------- set interfaces vxlan vxlan100 address '10.10.10.1/24' set interfaces vxlan vxlan100 description 'VyOS VXLAN' set interfaces vxlan vxlan100 remote '172.18.202.10' set interfaces vxlan vxlan100 vni '100'