<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions, branch fix/T8955-http-api-verify-tls</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=fix%2FT8955-http-api-verify-tls</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=fix%2FT8955-http-api-verify-tls'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2026-09-29T21:33:24+00:00</updated>
<entry>
<title>openvpn: T9364: default the MTU to 1420 when DCO is enabled</title>
<updated>2026-09-29T21:33:24+00:00</updated>
<author>
<name>Antonio Quartulli</name>
<email>antonio@mandelbit.com</email>
</author>
<published>2026-09-28T14:02:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=12d3aa212f35b8cdd9a0ccd849b45beea46ed94d'/>
<id>urn:sha1:12d3aa212f35b8cdd9a0ccd849b45beea46ed94d</id>
<content type='text'>
The ovpn Kernel module does no MSS clamping, so with a 1500 bytes MTU
full sized packets get fragmented on the underlay.

Add an "mtu" node, rendered as "tun-mtu". With "offload dco" it
defaults to 1420, unless a raw tun-mtu/link-mtu/udp-mtu option is
present. Reject "mtu" together with such an option, below 100, and
below 1280 when IPv6 runs inside the tunnel.
</content>
</entry>
<entry>
<title>Merge pull request #5496 from vyos/T9338-l3vpn-multi-domain-switching</title>
<updated>2026-09-29T05:11:42+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-09-29T05:11:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=f15b8b2eebd4afa9ece0ed8034f08f279726c854'/>
<id>urn:sha1:f15b8b2eebd4afa9ece0ed8034f08f279726c854</id>
<content type='text'>
T9338: add bgp mpls l3vpn-multi-domain-switching</content>
</entry>
<entry>
<title>ntp: T8882: add per-server poll interval, presend and extension field options</title>
<updated>2026-09-28T18:30:00+00:00</updated>
<author>
<name>Scott Laird</name>
<email>scott@sigkill.org</email>
</author>
<published>2026-05-17T20:39:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=44d21687533bd0e4c27b9d04a61b5694b27f4091'/>
<id>urn:sha1:44d21687533bd0e4c27b9d04a61b5694b27f4091</id>
<content type='text'>
Poll intervals were left entirely to the NTP daemon's built-in defaults, so an
operator could not widen or narrow the polling range for an individual server,
warm up authenticated associations before a poll, or ask a peer for the higher
resolution timestamps it may be able to provide.

Each configured server and pool now accepts a minimum and maximum poll
exponent, defaulting to the values the daemon already used, plus an optional
presend exponent and a switch for the F323 extension field. Existing
configurations render the same associations as before.

Co-authored-by: Christian Breunig &lt;christian@vyos.io&gt;
</content>
</entry>
<entry>
<title>Merge pull request #5389 from ruben-herold/T9175-security-poll-suffix</title>
<updated>2026-09-28T09:43:06+00:00</updated>
<author>
<name>Daniil Baturin</name>
<email>daniil@vyos.io</email>
</author>
<published>2026-09-28T09:43:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d80a66463a60265a75f40ee387ae7a0e1ca60af4'/>
<id>urn:sha1:d80a66463a60265a75f40ee387ae7a0e1ca60af4</id>
<content type='text'>
dns: T9175: make PowerDNS security status poll opt-in</content>
</entry>
<entry>
<title>Merge pull request #5453 from m-songer/T9274-add-telegraf-config</title>
<updated>2026-09-25T14:03:20+00:00</updated>
<author>
<name>Nataliia S.</name>
<email>81954790+natali-rs1985@users.noreply.github.com</email>
</author>
<published>2026-09-25T14:03:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=480f28781023d81f4be08524cecff172d1d55c3f'/>
<id>urn:sha1:480f28781023d81f4be08524cecff172d1d55c3f</id>
<content type='text'>
T9274: Add more telegraf configuration</content>
</entry>
<entry>
<title>Merge pull request #5484 from haakonnore/feat/T9319-vxlan-gbp</title>
<updated>2026-09-24T17:06:31+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-09-24T17:06:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=990fa1569d3087842d8ff407d8c2ba4ead1d847e'/>
<id>urn:sha1:990fa1569d3087842d8ff407d8c2ba4ead1d847e</id>
<content type='text'>
vxlan: T9319: add VXLAN-GBP support</content>
</entry>
<entry>
<title>T9274: Add more telegraf configuration- #5453</title>
<updated>2026-09-24T16:00:38+00:00</updated>
<author>
<name>MichaelSonger</name>
<email>michael.songer@infinitivegroup.co.uk</email>
</author>
<published>2026-09-24T16:00:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=75781f0d9dbf0174dfbb55d5f0e8228a38b6f608'/>
<id>urn:sha1:75781f0d9dbf0174dfbb55d5f0e8228a38b6f608</id>
<content type='text'>
Added the ability to make several agent values configurable instead of hardcoded.
</content>
</entry>
<entry>
<title>T9338: add bgp mpls l3vpn-multi-domain-switching</title>
<updated>2026-09-24T06:40:37+00:00</updated>
<author>
<name>Kyrylo Yatsenko</name>
<email>hedrok@gmail.com</email>
</author>
<published>2026-09-24T06:22:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=f4a86a1949f7571d5d3ccde38cfd79d88973f997'/>
<id>urn:sha1:f4a86a1949f7571d5d3ccde38cfd79d88973f997</id>
<content type='text'>
Add command

set protocols bgp interface &lt;interface&gt; mpls l3vpn-multi-domain-switching

that exposes FRR's `mpls bgp l3vpn-multi-domain-switching` under
interface node.
</content>
</entry>
<entry>
<title>vxlan: T9319: add VXLAN-GBP support</title>
<updated>2026-09-22T23:13:09+00:00</updated>
<author>
<name>Haakon Nore</name>
<email>haakon@nore.cloud</email>
</author>
<published>2026-09-15T08:28:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=4fd9ad0ac3a79aba079b10f58ec897847eb271d5'/>
<id>urn:sha1:4fd9ad0ac3a79aba079b10f58ec897847eb271d5</id>
<content type='text'>
Expose the Group Policy extension as a valueless gbp CLI node and pass
it to iproute2 when creating VXLAN links. Recreate links when GBP
changes and reject configurations combining GBP with GPE.

Reject conflicting GBP settings on a shared UDP port, accounting for
address families and underlay VRF socket bindings. Warn that external
mode carries GBP in tunnel metadata instead of the packet mark.

Add smoketest coverage for GBP creation, removal and re-enabling,
retained interface settings, rejection without changing the running
tunnel, shared ports, separate address families, and external mode.
</content>
</entry>
<entry>
<title>ipsec: T8952: Allow per-peer strongSwan `unique` override for site-to-site peers</title>
<updated>2026-09-16T08:22:40+00:00</updated>
<author>
<name>Oleksandr Kuchmystyi</name>
<email>o.kuchmystyi@vyos.io</email>
</author>
<published>2026-09-15T09:10:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d1cc3ed65eb1f00409d0b91fc8149431fb614e89'/>
<id>urn:sha1:d1cc3ed65eb1f00409d0b91fc8149431fb614e89</id>
<content type='text'>
VyOS does not expose the strongSwan `connections.&lt;conn&gt;.unique`
parameter for site-to-site peers. The swanctl default is
`unique = no`, which only replaces existing SAs
if the new one carries `INITIAL_CONTACT`. With `dpd_action = restart`,
charon initiates new IKE_SAs without `INITIAL_CONTACT`,
so duplicates accumulate on every DPD timeout.

Previously the strongSwan `unique` connection policy could only be
driven by the global "disable-uniqreqids" option, which set it to
"never" for every connection. Site-to-site peers had no way to opt
into stricter enforcement on their own.
</content>
</entry>
</feed>
