vyos-1x.git/interface-definitions/protocols_failover.xml.in, branch fix/T8955-http-api-verify-tlsVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=fix%2FT8955-http-api-verify-tls2025-10-08T12:07:59+00:00T7803: Make failover route vrf-aware2025-10-08T12:07:59+00:00Kyrylo Yatsenkohedrok@gmail.com2025-09-22T19:10:22+00:00urn:sha1:931e5b5712b4fa8b13027291eb21881c40b8a051
* Added 'protocol failover' to 'set vrf name':
set vrf name red protocols failover route 10.11.0.110/32 next-hop 10.0.0.2
* Added vrf and interface to target:
set ... next-hop 10.0.0.2 check target '10.120.0.21' vrf blue
set ... next-hop 10.0.0.2 check target '10.120.0.21' interface eth1
Last two are needed when check VRF is not same as route VRF.
In this case icmp can use any/both options, tcp requires `vrf` and
arp requires `interface`
xml: T5738: re-use XML building blocks for interfaces as much as possible2024-12-23T12:31:32+00:00Christian Breunigchristian@breunig.cc2024-12-23T12:31:32+00:00urn:sha1:020f217c2e4bfcff3cecb0b33c93af517775f4ae
Change XML definitions to re-use already existing building blocks, or merge
two building block sinto one (e.g. static route interfaces).
T5722: Failover route add option onlink2024-04-15T15:17:14+00:00Viacheslav Hletenkov.gletenko@vyos.io2024-04-15T15:17:14+00:00urn:sha1:bb832acb97881d747a57da2728eab3ad138b8129
onlink pretend that the nexthop is directly attached to this link,
even if it does not match any interface prefix.
Useful when gateway not in the same interface network
set interfaces ethernet eth0 vif 10 address '10.20.30.1/32'
set protocols static route 10.20.30.0/32 interface eth0.10
set protocols failover route 192.0.2.11/32 next-hop 10.20.30.0 onlink
```
vyos@r4# sudo ip route add 192.0.2.111/32 via 10.20.30.0 dev eth0.10 metric 1 proto failover
Error: Nexthop has invalid gateway.
[edit]
vyos@r4#
[edit]
vyos@r4# sudo ip route add 192.0.2.111/32 via 10.20.30.0 dev eth0.10 onlink metric 1 proto failover
[edit]
vyos@r4#
```
T5474: establish common file name pattern for XML conf mode commands2023-12-31T22:49:48+00:00Christian Breunigchristian@breunig.cc2023-12-30T22:25:20+00:00urn:sha1:4ef110fd2c501b718344c72d495ad7e16d2bd465
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 -> interfaces_ethernet.xml.in
set interfaces bond -> interfaces_bond.xml.in
set service dhcp-server -> service_dhcp-server-xml.in