diff options
| author | Lee Clements <lclements0@gmail.com> | 2026-07-27 11:12:00 -0400 |
|---|---|---|
| committer | Lee Clements <lclements0@gmail.com> | 2026-07-30 13:21:51 -0400 |
| commit | 184be9b69acfa24280497474423fa42911fb2ca6 (patch) | |
| tree | d654c6e8873989b1ee1631d797dc18baa8b03584 /interface-definitions/include/interface/interface-dial-on-demand.xml.i | |
| parent | 6d8a3ad9a87857d5994ec33982dd3db9a04fb8bd (diff) | |
| download | vyos-1x-184be9b69acfa24280497474423fa42911fb2ca6.tar.gz vyos-1x-184be9b69acfa24280497474423fa42911fb2ca6.zip | |
flow-accounting: T9122: reject a VRF as a netflow source-interface
I had initially treated the VRF as just another interface that could be
used as a source-interface, but after a bit more research none of the
major vendors treat VRFs as interfaces - Cisco and Juniper both source a
flow exporter from a routed interface and never from a VRF - and I don't
think we should either.
Reject a source-interface that names a VRF device with a clear message
instead of the misleading "is not a member of VRF" error, and cover the
rejection in the smoketest. VRF export continues to be selected through
the "system flow-accounting vrf" node.
Diffstat (limited to 'interface-definitions/include/interface/interface-dial-on-demand.xml.i')
0 files changed, 0 insertions, 0 deletions