vyos-documentation.git/docs/configexamples, branch test/ai-validation-e2e-v1.1.0

T3871: bind interface names to hardware slots instead of hw-id (#2246)

2026-10-31T10:53:23+00:00

* docs: T3871: describe how interface names are assigned Names are no longer derived from the hw-id node. They are bound to the slot the hardware occupies and recorded in a mapping file, so document what decides a name, what happens when a card is replaced or added, and how to rename an interface. The troubleshooting page said to pin a MAC with hw-id when interfaces were renamed after a VM migration or a clone. That node no longer exists and the situation it describes no longer arises, so replace it with a pointer to the new section and a note on where to look when an interface really is missing. * docs: T3871: drop hw-id from the example output The node is gone from the CLI, so example configuration dumps which still show it no longer match what a reader sees on their own system. Remove it from the shown output only; no prose changes. The comparison shown on the testing page is rewritten rather than trimmed, as deleting the lines would have left an edit level behind with nothing under it.

Merge pull request #2349 from omnom62/ansible-blueprints-upgrade

2026-10-22T12:22:59+00:00

docs: Ansible example - upgrades with vyos.blueprints

docs: suppress Tunnelbroker address lint false positives (#2267)

2026-10-20T11:59:28+00:00

docs: Ansible example - upgrades with the vyos.blueprints collection

2026-10-18T01:44:23+00:00

docs: Ansible example - wrap to 80 columns, shorten an existing heading

2026-10-16T00:48:39+00:00

docs: Ansible example - backups with the vyos.blueprints collection

2026-10-16T00:29:09+00:00

Merge pull request #2139 from jeleel-muibi/docs-gcp-ha-vpn-bgp-example

2026-09-04T08:58:21+00:00

docs: add Google Cloud HA VPN BGP example

docs(DMVPN): T4667: Add firewall rule to prevent unencrypted GRE leaks (#2136)

2026-07-10T15:33:10+00:00

* docs(DMVPN): T4667: Add firewall rule to prevent unencrypted GRE leaks In DMVPN the mGRE tunnel and the IPSec protecting it are handled independently, so GRE can be forwarded while no IPSec SA is active for a peer (e.g. while an SA is still being negotiated or after one expires), allowing unencrypted GRE to leave the router. This is inherent to combining GRE with IPSec and is common to DMVPN implementations in general. Add a "Protecting against unencrypted traffic leaks" section to the DMVPN reference page explaining the behaviour and recommending an output filter rule that drops GRE not matched by an outbound IPSec policy (ipsec match-none-out). Note that this disables unencrypted GRE on the node entirely, so coexisting plain GRE tunnels would stop working. Apply the same rule in the Dual HUB Dual Cloud example on the VyOS nodes. Co-authored-by: Daniil Baturin * docs(DMVPN): reflow DMVPN documentation for line length compliance Reformat the DMVPN guide and dual-hub dual-cloud example to wrap long lines and improve readability without changing the documented behavior or configuration guidance. --------- Co-authored-by: Daniil Baturin

docs: clarify Google Cloud peer gateway wording

2026-07-09T19:27:52+00:00

docs: disable IPsec route autoinstall in GCP example

2026-07-09T19:25:14+00:00