vyos-1x.git/src/conf_mode/vpp_interfaces_loopback.py, branch nos-task-idVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=nos-task-id2026-07-29T10:52:38+00:00vpp: T9139: Check interface not referenced by a feature before removal2026-07-29T10:52:38+00:00Nataliia Solomkonatalirs1985@gmail.com2026-07-29T10:17:05+00:00urn:sha1:390e93138b32c54c6a98b98b22351052bc8c206e
Reject deletion of a gre, ipip, vxlan or loopback interface that is still
used by a feature.
vpp: T8367: Fix identical default MAC on bridged loopback interfaces2026-07-20T09:02:54+00:00Nataliia Solomkonatalirs1985@gmail.com2026-07-16T12:16:02+00:00urn:sha1:e72de7eb3e4a6ef67a6836367f43ef363bf77e40
VPP assigns loopback interfaces a default MAC address derived only from
the interface instance number (de:ad:00:00:00:<instance>), with no
host-specific entropy. Two independent VPP nodes configuring the same
loopback instance (e.g. as a bridge BVI over VXLAN) therefore end up with
an identical MAC address.
When that MAC arrives from a peer over the shared L2 segment, VPP's L2
learning logic rejects it as a `mac move violation` - it's statically
pinned to the local BVI and cannot legitimately appear on another port.
This silently drops ARP traffic between the loopbacks while ordinary
bridged client traffic (unique MACs) is unaffected, breaking
loopback-to-loopback connectivity.
Add a mac-address option to the VPP loopback interface, and fall back to
a deterministic, host-unique MAC (derived from host UUID/hostname, same
scheme already used for container interfaces) whenever none is
configured, so the collision can no longer occur by default.
Also fix a related bug found while reproducing the above: a loopback is
fully deleted and recreated in VPP on every apply, receiving a new
`sw_if_index` each time. The loopback conf_mode script never registered
the bridge it's a BVI member of as a dependent, so the bridge kept its
L2 membership bound to the stale, deleted index instead of reattaching
the current one. Register the bridge dependency and reuse the existing
`verify_vpp_remove_bridge_interface()` check to block deleting a
loopback still in use as a BVI.
vpp: T8324: Migrate loopback interface to 'interfaces vpp loopback'2026-03-02T14:15:30+00:00Nataliia Solomkonatalirs1985@gmail.com2026-02-27T10:40:38+00:00urn:sha1:61d607295fa826e707b82432c46668a2fb94ab22vpp: T8254: Move 'nat44' and 'settings nat44' sections to 'nat nat44'2026-02-13T18:20:31+00:00Nataliia Solomkonatalirs1985@gmail.com2026-02-13T10:29:00+00:00urn:sha1:9bfe2749a1fa41a4c77a3364851ac1fbefbf3ef3T7697: Remove year from copyright2025-08-07T15:43:25+00:00Viacheslavv.gletenko@vyos.io2025-08-07T15:43:25+00:00urn:sha1:6801f0ef7365556d1c8eb60aeed01789a7620cb7T7488: Make VPP restartable2025-05-28T11:48:07+00:00Nataliia Solomkonatalirs1985@gmail.com2025-05-27T11:27:50+00:00urn:sha1:31beaf550786502f5b62034c6e4b2e0e52508f8cT7419: VPP ACL implementation (#31)2025-05-13T14:33:35+00:00Nataliia S.81954790+natali-rs1985@users.noreply.github.com2025-05-13T14:33:35+00:00urn:sha1:151afffe15ce89755f3c3f81a9d2c647e487f647
CLI:
```
set vpp acl ip tag-name <tag-name> rule <nn> action <permit|deny|permit-reflect>
set vpp acl ip tag-name <tag-name> rule <nn> source prefix <prefix>
set vpp acl ip tag-name <tag-name> rule <nn> source port <port|range>
set vpp acl ip tag-name <tag-name> rule <nn> destination prefix <prefix>
set vpp acl ip tag-name <tag-name> rule <nn> destination port <port>
set vpp acl ip tag-name <tag-name> rule <nn> protocol <protocol>
set vpp acl ip tag-name <tag-name> rule <nn> tcp-flags <fin|syn|rst|psh|ack|urg|ecn|cwr>
set vpp acl ip tag-name <tag-name> rule <nn> tcp-flags not <fin|syn|rst|psh|ack|urg|ecn|cwr>
set vpp acl ip interface <interface_name> input acl-tag <n> tag-name <tag-name>
set vpp acl ip interface <interface_name> output acl-tag <n> tag-name <tag-name>
set vpp acl macip tag-name <tag-name> rule <nn> prefix <prefix>
set vpp acl macip tag-name <tag-name> rule <nn> mac-address <mac>
set vpp acl macip tag-name <tag-name> rule <nn> mac-mask <mac-mask>
set vpp acl macip tag-name <tag-name> rule <nn> action <permit|deny>
set vpp acl macip interface <interface_name> tag-name <tag-name>
```
OP mode
```
show vpp acl ip tag-name <tag_name>
show vpp acl ip interface
show vpp acl macip tag-name <tag_name>
show vpp acl macip interface
```Revert "warning: introduce a delay between add() and kernel_add()"2025-01-29T13:31:10+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-29T13:31:10+00:00urn:sha1:f5aaef311484f90d87f46d5a5739897e560ceb40
This reverts commit 405d3ee7ac909bbf458f522e6539a1f4eacdf7e6.
Use common class for none ethernet interfaces state2025-01-27T19:23:45+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-27T18:01:57+00:00urn:sha1:dfda2c7f305df94690cc4538a74ab213d25c579cwarning: introduce a delay between add() and kernel_add()2025-01-15T09:50:49+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-01-15T09:50:49+00:00urn:sha1:405d3ee7ac909bbf458f522e6539a1f4eacdf7e6
Introduce a delay to address instability in the VPP API, which may
fail to create the LCP or establish a connection.
This should be reviewed and resolved in future releases.
This fixes confgurations with included kernel-itnerface (LCP)
And all smoketests
Example:
set interfaces ethernet eth1 address '192.0.2.1/30'
set vpp settings interface eth1 driver 'dpdk'
set vpp interfaces vxlan vxlan10 remote '192.0.2.2'
set vpp interfaces vxlan vxlan10 source-address '192.0.2.1'
set vpp interfaces vxlan vxlan10 vni '10'
set vpp interfaces vxlan vxlan10 kernel-interface 'vpptap10'
Without this delay we get:
vyos@r14# commit
[ vpp interfaces vxlan vxlan10 ]
Traceback (most recent call last):
File "/usr/libexec/vyos/services/vyos-configd", line 139, in run_script
script.apply(c)
File "/usr/libexec/vyos//conf_mode/vpp_interfaces_vxlan.py", line 174, in apply
i.kernel_add()
File "/usr/lib/python3/dist-packages/vyos/vpp/interface/vxlan.py", line 85, in kernel_add
self.vpp.lcp_pair_add(self.ifname, self.kernel_interface)
File "/usr/lib/python3/dist-packages/vyos/vpp/control_vpp.py", line 79, in check_retval_wrapper
return_value = decorated_func(cls, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vyos/vpp/control_vpp.py", line 58, in api_safe_wrapper
return decorated_func(cls, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vyos/vpp/control_vpp.py", line 188, in lcp_pair_add
return self.__vpp_api_client.api.lcp_itf_pair_add_del_v2(**api_call_args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vpp_papi/vpp_papi.py", line 129, in __call__
return self._func(**kwargs)
^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vpp_papi/vpp_papi.py", line 564, in f
return self._call_vpp(i, msg, multipart, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/vpp_papi/vpp_papi.py", line 853, in _call_vpp
raise VPPIOError(2, "VPP API client: read failed")
vpp_papi.vpp_papi.VPPIOError: [Errno 2] VPP API client: read failed