<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-documentation.git/docs/configuration/vpn/dmvpn.md, branch nos-task-id</title>
<subtitle>VyOS readthedocs (mirror of https://github.com/vyos/vyos-documentation.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-documentation.git/atom?h=nos-task-id</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-documentation.git/atom?h=nos-task-id'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/'/>
<updated>2026-07-10T15:33:10+00:00</updated>
<entry>
<title>docs(DMVPN): T4667: Add firewall rule to prevent unencrypted GRE leaks (#2136)</title>
<updated>2026-07-10T15:33:10+00:00</updated>
<author>
<name>zdc</name>
<email>zdc@users.noreply.github.com</email>
</author>
<published>2026-07-10T15:33:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=50acf8f188475b0554b99a739cb8ada12d51e77b'/>
<id>urn:sha1:50acf8f188475b0554b99a739cb8ada12d51e77b</id>
<content type='text'>
* 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 &lt;daniil@baturin.org&gt;

* 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 &lt;daniil@baturin.org&gt;</content>
</entry>
<entry>
<title>feat: flip swap mechanism — MD as primary, RST as override (Phase 1)</title>
<updated>2026-05-06T17:42:32+00:00</updated>
<author>
<name>Yuriy Andamasov</name>
<email>yuriy@vyos.io</email>
</author>
<published>2026-05-06T17:42:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=5d6fa52b8985f8068314aba26878a1d7d5cb84e5'/>
<id>urn:sha1:5d6fa52b8985f8068314aba26878a1d7d5cb84e5</id>
<content type='text'>
This is the first of three phases inverting the per-page swap mechanism
so MD becomes the canonical primary and RST becomes the rare override.

Phase 1 — file renames + conf.py exclude_patterns flip only:
- Rename docs/**/md-&lt;stem&gt;.md to docs/**/&lt;stem&gt;.md (drop md- prefix)
  for all 254 stems previously listed in docs/_swap.txt
- Rename docs/**/&lt;stem&gt;.rst to docs/**/rst-&lt;stem&gt;.rst (add rst- prefix)
  for the same 254 stems
- Repurpose docs/_swap.txt as docs/_rst_overrides.txt; initially empty
  comment-only since no pages need the RST fallback right now
- conf.py exclude_patterns flipped: rst-*.rst is now excluded by default
  instead of md-*.md
- conf.py runtime-artifact references updated to _rst_override_state.json
  and _md_exclude.txt (Phase 2 will rewrite swap_sources.py to produce
  these names; for now no swap script runs because overrides list is empty)

Phase 2 (next commit on this branch) will rewrite scripts/swap_sources.py
with inverted rename direction, delete scripts/import_myst.py + tests, and
update tests/test_swap_sources.py for the new semantics.

Phase 3 will be the cleanup pass and ready-for-review flip.

Generated by robots https://vyos.io
</content>
</entry>
</feed>
