VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git) https://git.amelek.net/marekm72/vyos-1x.git/atom?h=1.4.0-epa1 2023-12-29T17:03:08+00:00 2023-12-29T17:03:08+00:00 Christian Breunig christian@breunig.cc 2023-12-29T12:30:43+00:00 urn:sha1:b0754013579f6e5db9027cc5123c99ba18a700a2 We have had duplicated test cases in test_jinja_filters.py and test_template.py, They have been consolidated into test_template.py. (cherry picked from commit 80e2e80b5504d1da643a0d5c9772a1f9dee0aa99) 2023-12-29T17:03:07+00:00 Christian Breunig christian@breunig.cc 2023-12-29T12:29:02+00:00 urn:sha1:07294ffd83191093fc1086ff9d1949666be57971 The subnet router anycast address is predefined. Its format is as follows: | n bits | 128-n bits | +------------------------------------------------+----------------+ | subnet prefix | 00000000000000 | +------------------------------------------------+----------------+ The "subnet prefix" in an anycast address is the prefix that identifies a specific link. This anycast address is syntactically the same as a unicast address for an interface on the link with the interface identifier set to zero. Packets sent to the Subnet-Router anycast address will be delivered to one router on the subnet. All routers are required to support the Subnet-Router anycast addresses for the subnets to which they have interfaces. The Subnet-Router anycast address is intended to be used for applications where a node needs to communicate with any one of the set of routers. Our code as of now returns the subnet router anycast address as the first_host_address(). (cherry picked from commit cc4ce81ece57faca8ce111b8f3748389ecb40202) 2021-07-03T11:45:31+00:00 Christian Poessinger christian@poessinger.com 2021-07-03T11:40:19+00:00 urn:sha1:2d79a5000c8a02fd7570f629c3182fd55fdb8c86 2021-04-05T13:37:04+00:00 Christian Poessinger christian@poessinger.com 2021-04-05T13:36:44+00:00 urn:sha1:23598fc082fcf0c02e113586bfc615583a05d2f3 2021-01-19T20:04:28+00:00 Christian Poessinger christian@poessinger.com 2021-01-19T20:01:20+00:00 urn:sha1:9207897983a3bfafa0ec3e436c1ad67790f09f06 Support a 1:1 or 1:n prefix translation. The following configuration will NAT source addresses from the 10.2.0.0/16 range to an address from 192.0.2.0/29. For this feature to work a Linux Kernel 5.8 or higher is required! vyos@vyos# show nat source { rule 100 { outbound-interface eth1 source { address 10.2.0.0/16 } translation { address 192.0.2.0/29 } } } This results in the nftables configuration: chain POSTROUTING { type nat hook postrouting priority srcnat; policy accept; oifname "eth1" counter packets 0 bytes 0 snat ip prefix to ip saddr map { 10.2.0.0/16 : 192.0.2.0/29 } comment "SRC-NAT-100" } 2020-12-06T12:44:01+00:00 Christian Poessinger christian@poessinger.com 2020-12-06T12:35:17+00:00 urn:sha1:b83c988a1390efc6f7d881fa9cc06eddb825f827 2020-11-13T13:50:11+00:00 Christian Poessinger christian@poessinger.com 2020-11-13T13:50:09+00:00 urn:sha1:6962bc53fa246f3e5c081ffec5f996fcb821273b We had two places were the is_ip, is_ipv4 and is_ipv6 helpers had been defined. All places now have been converged into vyos.template as they are used both in the Jinja2 templates and also in our scripts. 2020-11-01T12:51:44+00:00 Christian Poessinger christian@poessinger.com 2020-11-01T09:46:46+00:00 urn:sha1:bb76575715682594d4d6d73d8b9e87692bdc6841 Remove workaround which split (local|remote)_address and also subnet keys into individual keys for the assigned IP address family (4/6). During template rendering check IP version by introducing new ipv4 and ipv6 Jinja2 filters {% if foo | ipv4 %} or {% if bar | ipv6 %} options. 2020-10-25T18:39:58+00:00 Christian Poessinger christian@poessinger.com 2020-10-25T18:39:58+00:00 urn:sha1:d69991eaa93d06335bdbd83b943d4655cc61acac