-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pbrd: add vty support for vlan filtering and send to zebra #13514
Conversation
Continuous Integration Result: SUCCESSFULContinuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-11499/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor changes + some contribution guidelines missing (formatting, signed-off tag).
doc/user/pbr.rst
Outdated
|
||
When a incoming packet matches the specified ip protocol, take the | ||
packet and forward according to the nexthops specified. | ||
packet and forward according to the nexthops specified. Protocols are | ||
queried from the protocols database (`/etc/protocols`; see `man 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: if you want to highlight /etc/protocols
you have to use double-ticks (``)
lib/pbr.h
Outdated
#define PBR_FILTER_SRC_PORT (1 << 2) | ||
#define PBR_FILTER_DST_PORT (1 << 3) | ||
#define PBR_FILTER_FWMARK (1 << 4) | ||
#define PBR_FILTER_PROTO (1 << 5) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you leave the old (untouched) code as it is (no formating in this commit)?
pbrd/pbr_map.c
Outdated
{ | ||
if (pbrms) { | ||
pbrms->match_pcp = pcp; | ||
zlog_info("setting pbrms->match_pcp = %u ", pbrms->match_pcp); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds to be like a debug and should be guarded 🤷
pbrd/pbr_vty.c
Outdated
@@ -25,6 +28,80 @@ | |||
#include "pbrd/pbr_debug.h" | |||
#include "pbrd/pbr_vty_clippy.c" | |||
|
|||
DEFPY(pbr_map_match_pcp, pbr_map_match_pcp_cmd, "[no] match pcp <(0-7)$pcp>", | |||
NO_STR | |||
"match the rest of the command\n" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use a capital first letter (Match) to comply with other commands.
pbrd/pbr_vty.c
Outdated
NO_STR | ||
"match the rest of the command\n" | ||
"match based on 802.1p Priority Code Point (PCP) value\n" | ||
"a valid value in range 0..7 \n") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, zero-point writing values as it's displayed by default from the command itself. Also, please drop whitespace before \n
.
pbrd/pbr_vty.c
Outdated
return CMD_WARNING; | ||
|
||
if (!no) { | ||
if (strcmp(tag_type, "tagged") == 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: strmatch()
pbrd/pbr_vty.c
Outdated
<A.B.C.D|X:X::X:X>$addr [INTERFACE$intf]\ | ||
|INTERFACE$intf\ | ||
>\ | ||
<A.B.C.D|X:X::X:X>$addr [INTERFACE$intf]\ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't apply the formatting here if you don't touch the code. It's hard to read sometimes (even if it's not the logical/real change).
pbrd/pbr_vty.c
Outdated
@@ -879,6 +955,12 @@ static void vty_show_pbrms(struct vty *vty, | |||
pbrms->installed ? "yes" : "no", | |||
pbrms->reason ? rbuf : "Valid"); | |||
|
|||
/* match clauses first */ | |||
|
|||
if (pbrms->dsfield & PBR_DSFIELD_DSCP) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why moving this here from the below?
pbrd/pbr_zebra.c
Outdated
@@ -3,6 +3,9 @@ | |||
* Zebra connect code. | |||
* Copyright (C) 2018 Cumulus Networks, Inc. | |||
* Donald Sharp | |||
* Portions: | |||
* Copyright (c) 2021 The MITRE Corporation. All Rights Reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we drop "All Rights Reserved" and leave just the Copyright + the company name? And the below Approved...
zebra/zapi_msg.c
Outdated
@@ -5,6 +5,8 @@ | |||
* Copyright (C) 1997-1999 Kunihiro Ishiguro | |||
* Copyright (C) 2015-2018 Cumulus Networks, Inc. | |||
* et al. | |||
* Copyright (c) 2021 The MITRE Corporation. All Rights Reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto.
.gitignore
Outdated
/changelog-auto | ||
/m4/ac | ||
/pathd/ | ||
/pceplib/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can't really ignore these entire components, can we?
.gitignore
Outdated
pceplib/test/*.log | ||
pceplib/test/*.trs | ||
*.xref |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that already, don't need to dup ?
#define PBR_FILTER_DST_PORT (1 << 3) | ||
#define PBR_FILTER_FWMARK (1 << 4) | ||
#define PBR_FILTER_PROTO (1 << 5) | ||
uint32_t filter_bm; /* not encoded by zapi */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we may need to encode these bits - how can we tell the difference between "not present" and "value is zero" otherwise?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, can you explain a little more in depth what you mean? The comment was only changed in the original MR to be on one line instead of 2. I have reverted it per a ci:cd warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see anything related to the issues that Paul and I asked about earlier - the encoding issues?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mind .gitignore file changes but really really needs to be in it's own commit.
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 amd64 part 3: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 3: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-11742/artifact/TP3U1804AMD64/TopotestDetails/Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TP3U1804AMD64-11742/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 3 Topotests debian 10 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9DEB10AMD64-11742/test Topology Tests failed for Topotests debian 10 amd64 part 9 Topotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18I386-11742/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9 Topotests debian 10 amd64 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-11742/test Topology Tests failed for Topotests debian 10 amd64 part 3 Successful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests Ubuntu 18.04 amd64 part 3: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 3: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-11742/artifact/TP3U1804AMD64/TopotestDetails/Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TP3U1804AMD64-11742/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 3 Topotests debian 10 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9DEB10AMD64-11742/test Topology Tests failed for Topotests debian 10 amd64 part 9 Topotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18I386-11742/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9 Topotests debian 10 amd64 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-11742/test Topology Tests failed for Topotests debian 10 amd64 part 3
|
Please just rebase your branch - no merge commits please? |
400aa6c
to
1ee6580
Compare
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 amd64 part 7: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18AMD64-11965/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 7 Successful on other platforms/tests
|
81651ca
to
07c66d5
Compare
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests debian 10 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9DEB10AMD64-12016/test Topology Tests failed for Topotests debian 10 amd64 part 9 Successful on other platforms/tests
|
07c66d5
to
399db32
Compare
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18AMD64-12151/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 9 Topotests Ubuntu 18.04 arm8 part 7: Failed (click for details)Topotests Ubuntu 18.04 arm8 part 7: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12151/artifact/TOPO7U18ARM8/TopotestDetails/ Topotests Ubuntu 18.04 arm8 part 7: No useful log foundTopotests Ubuntu 18.04 amd64 part 7: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18AMD64-12151/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 7 Topotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18I386-12151/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9 Topotests debian 10 amd64 part 7: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7DEB10AMD64-12151/test Topology Tests failed for Topotests debian 10 amd64 part 7 Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-12151/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7 Successful on other platforms/tests
|
{ | ||
if (pbrms) { | ||
pbrms->match_pcp = pcp; | ||
pbr_map_check(pbrms, true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this work for matching PCP==0 ? Unless I missed something in the code, there is no use of a separate flag to indicate that PCP should be matched vs. ignored.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe you're right and that currently match pcp zero is simply ignored since there is a check in pbr_vty.c to see if it is non-zero. My initial thought is to set the default value to 8, rather than 0, in the pbrms_get and then handle 8 as a special ignore case and allow 0 as a match case. However, this will be difficult to test since, again per Eli, the default Linux kernel provider does not support matching PCPs, so actually testing this case differential may be difficult. Might be good to have a quick meeting to discuss if you have any availability?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think your proposal could work. It would mean that the check for "are we matching" is something like (pcp != 8) and then the value to match against is (pcp & 7).
Another way might be to set the "8" bit for every match and unset for no match. Then the "are we matching check" (e.g., in zapi_msg.c) remains (pcp != 0) and the value to match is (pcp & 7).
I don't have a strong opinion either way - please pick whichever seems clearer to you.
if (pbrms) { | ||
pbrms->match_vlan_id = vlan_id; | ||
pbrms->match_vlan_flags = vlan_flags; | ||
pbr_map_check(pbrms, true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same concern as above for PCP: How does the code distinguish between "match VLAN_ID==0" and "ignore VLAN_ID" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, VLAN_ID should only be a value between 1-4094 (see https://datatracker.ietf.org/doc/html/rfc5517). ID 0 is reserved, and handled by the untagged_0 match, so a value of zero is always ignored unless you do match match untagged-or-zero
, rather than match 0
. Eli documented this in the .rst and it is has special casing already in pbr_vty.c where it specifically excludes the value of 0 and matches instead on the constants defined in the pbr header (PBR_MAP_VLAN_UNTAGGED_0, PBR_MAP_VLAN_UNTAGGED, etc.). So, from my understanding these cases are distinct already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks - it's a good explanation and I agree.
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
399db32
to
2e4e7b9
Compare
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 i386 part 3: Failed (click for details)Topotests Ubuntu 18.04 i386 part 3: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12352/artifact/TOPO3U18I386/TopotestDetails/Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3U18I386-12352/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 3 Topotests debian 10 amd64 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-12352/test Topology Tests failed for Topotests debian 10 amd64 part 3 Successful on other platforms/tests
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still seem to have some open questions?
and I think the commits need to be reorganized - we'd rather not have "fix it" or "undo it" commits when those could be squashed.
@@ -114,6 +114,5 @@ refix | |||
.kitchen | |||
.emacs.desktop* | |||
|
|||
/test-suite.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a duplicated line
#define PBR_FILTER_DST_PORT (1 << 3) | ||
#define PBR_FILTER_FWMARK (1 << 4) | ||
#define PBR_FILTER_PROTO (1 << 5) | ||
uint32_t filter_bm; /* not encoded by zapi */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see anything related to the issues that Paul and I asked about earlier - the encoding issues?
Yes, the latest push is just to rebase on master. I am currently working on the other changes and planned to mark the thread resolved when I have. I was under the impression we would squash the commits at merge time, but you want me to squash them now with an interactive rebase? |
2e4e7b9
to
ef32761
Compare
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests Ubuntu 18.04 arm8 part 9: Failed (click for details)Topotests Ubuntu 18.04 arm8 part 9: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12428/artifact/TOPO9U18ARM8/TopotestDetails/ Topotests Ubuntu 18.04 arm8 part 9: No useful log foundTopotests Ubuntu 18.04 i386 part 3: Failed (click for details)Topotests Ubuntu 18.04 i386 part 3: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12428/artifact/TOPO3U18I386/TopotestDetails/Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3U18I386-12428/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 3 Topotests Ubuntu 18.04 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18AMD64-12428/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 9 Topotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18I386-12428/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9 Topotests debian 10 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9DEB10AMD64-12428/test Topology Tests failed for Topotests debian 10 amd64 part 9 Successful on other platforms/tests
|
@@ -3244,6 +3248,15 @@ static inline void zread_rule(ZAPI_HANDLER_ARGS) | |||
if (zpr.rule.filter.fwmark) | |||
zpr.rule.filter.filter_bm |= PBR_FILTER_FWMARK; | |||
|
|||
if (zpr.rule.filter.pcp) | |||
zpr.rule.filter.filter_bm |= PBR_FILTER_PCP; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check or mask correctly here?
ef32761
to
bad3c7e
Compare
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests debian 10 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9DEB10AMD64-12649/test Topology Tests failed for Topotests debian 10 amd64 part 9 Topotests Ubuntu 18.04 arm8 part 9: Failed (click for details)Topotests Ubuntu 18.04 arm8 part 9: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12649/artifact/TOPO9U18ARM8/TopotestDetails/ Topotests Ubuntu 18.04 arm8 part 9: No useful log foundTopotests Ubuntu 18.04 i386 part 3: Failed (click for details)Topotests Ubuntu 18.04 i386 part 3: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12649/artifact/TOPO3U18I386/TopotestDetails/Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3U18I386-12649/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 3 Topotests Ubuntu 18.04 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18AMD64-12649/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 9 Topotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18I386-12649/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9 Successful on other platforms/tests
|
Resolves conflict encountered during rebasing on master; new commits add else condition to pbr_encode_pbr_map_sequence--maintained in this PR Signed-off-by: Josh Werner <joshuawerner@mitre.org>
Address formatting warnings from ci:cd; remove unintentional reformatting from initial commit per comments; remove redundant value displays and an unguarded debug statement; standardize output format in vty per comment; realign vty ordering per comment Signed-off-by: Josh Werner <joshuawerner@mitre.org>
Removes files added to the .gitignore per a PR comment. Also deletes erroneous duplicate. Signed-off-by: Josh Werner <joshuawerner@mitre.org>
Simple commit applying style suggestions from frrbot. Signed-off-by: Josh Werner <joshuawerner@mitre.org>
Sets the pbrms match_pcp to default to 8 instead of 0 to distinguish between the case where pcp is ignored and pcp 0 is instead matched Signed-off-by: Josh Werner <joshuawerner@mitre.org>
bad3c7e
to
b21c325
Compare
Continuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopotests debian 10 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9DEB10AMD64-12659/test Topology Tests failed for Topotests debian 10 amd64 part 9 Topotests Ubuntu 18.04 arm8 part 9: Failed (click for details)Topotests Ubuntu 18.04 arm8 part 9: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12659/artifact/TOPO9U18ARM8/TopotestDetails/ Topotests Ubuntu 18.04 arm8 part 9: No useful log foundTopotests Ubuntu 18.04 amd64 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18AMD64-12659/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 9 Topotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO9U18I386-12659/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9 Successful on other platforms/tests
|
Please close: superseded by #14026 |
Closing this: new, revised version referenced above... |
This adds VTY and initial Zebra support for VLAN filters. Since the kernel PBR facilities do not provide any way of matching on VLAN fields, another provider may be required (i.e. netfilter). This rebases the previous pull request by Eli Baum PR 9705, now closed, on master since the previous fork can no longer be updated in situ.
Signed-off-by: Josh Werner joshuawerner@mitre.org