-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix kernel routes addition with no gateway next-hop IP address #9188
base: master
Are you sure you want to change the base?
Fix kernel routes addition with no gateway next-hop IP address #9188
Conversation
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 for your contribution to FRR!
- One of your commits has an improperly formatted commit message
- One of your commits has a missing or badly formatted
Signed-off-by
line; we can't accept your contribution until all of your commits have one
Click for style suggestions
To apply these suggestions:
curl -s https://gist.githubusercontent.com/polychaeta/887bdfcd0238310bc59c2c245e92cda2/raw/6f97a63da465e3fb8dee8be68cd6520e96db33d1/cr_9188_1627311028.diff | git apply
diff --git a/zebra/kernel_socket.c b/zebra/kernel_socket.c
index eec79588f..81ebee046 100644
--- a/zebra/kernel_socket.c
+++ b/zebra/kernel_socket.c
@@ -973,10 +973,10 @@ static int rtm_read_mesg(struct rt_msghdr *rtm, union sockunion *dest,
opnt = pnt;
pnt += rta_get(pnt, gate, sizeof(*gate));
if (!gate->sa.sa_len) {
- // No gateway address - interface name instead
- pnt = opnt;
- pnt += rta_getsdlname(pnt, ifname, ifnlen);
- }
+ // No gateway address - interface name instead
+ pnt = opnt;
+ pnt += rta_getsdlname(pnt, ifname, ifnlen);
+ }
break;
case RTA_NETMASK:
pnt += rta_getattr(pnt, mask, sizeof(*mask));
If you are a new contributor to FRR, please see our contributing guidelines.
After making changes, you do not need to create a new PR. You should perform an amend or interactive rebase followed by a force push.
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address ignored by zebra It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Missed: - connected and kernel routes may duplicate (need to filter out kernel if already detected as connected) - IPv6 nexthop by ifindex - not sure how to handle properly Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
5d1c068
to
cf76e46
Compare
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 for your contribution to FRR!
Click for style suggestions
To apply these suggestions:
curl -s https://gist.githubusercontent.com/polychaeta/7f544f1334aa187100a7556826a41620/raw/6f97a63da465e3fb8dee8be68cd6520e96db33d1/cr_9188_1627311700.diff | git apply
diff --git a/zebra/kernel_socket.c b/zebra/kernel_socket.c
index eec79588f..81ebee046 100644
--- a/zebra/kernel_socket.c
+++ b/zebra/kernel_socket.c
@@ -973,10 +973,10 @@ static int rtm_read_mesg(struct rt_msghdr *rtm, union sockunion *dest,
opnt = pnt;
pnt += rta_get(pnt, gate, sizeof(*gate));
if (!gate->sa.sa_len) {
- // No gateway address - interface name instead
- pnt = opnt;
- pnt += rta_getsdlname(pnt, ifname, ifnlen);
- }
+ // No gateway address - interface name instead
+ pnt = opnt;
+ pnt += rta_getsdlname(pnt, ifname, ifnlen);
+ }
break;
case RTA_NETMASK:
pnt += rta_getattr(pnt, mask, sizeof(*mask));
If you are a new contributor to FRR, please see our contributing guidelines.
After making changes, you do not need to create a new PR. You should perform an amend or interactive rebase followed by a force push.
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address ignored by zebra It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Missed: - connected and kernel routes may duplicate (need to filter out kernel if already detected as connected) - IPv6 nexthop by ifindex - not sure how to handle properly Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
cf76e46
to
0f312b8
Compare
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 for your contribution to FRR!
Click for style suggestions
To apply these suggestions:
curl -s https://gist.githubusercontent.com/polychaeta/4a48b3ee44dd2ea8f0e141c1e859bdb7/raw/6f97a63da465e3fb8dee8be68cd6520e96db33d1/cr_9188_1627311832.diff | git apply
diff --git a/zebra/kernel_socket.c b/zebra/kernel_socket.c
index eec79588f..81ebee046 100644
--- a/zebra/kernel_socket.c
+++ b/zebra/kernel_socket.c
@@ -973,10 +973,10 @@ static int rtm_read_mesg(struct rt_msghdr *rtm, union sockunion *dest,
opnt = pnt;
pnt += rta_get(pnt, gate, sizeof(*gate));
if (!gate->sa.sa_len) {
- // No gateway address - interface name instead
- pnt = opnt;
- pnt += rta_getsdlname(pnt, ifname, ifnlen);
- }
+ // No gateway address - interface name instead
+ pnt = opnt;
+ pnt += rta_getsdlname(pnt, ifname, ifnlen);
+ }
break;
case RTA_NETMASK:
pnt += rta_getattr(pnt, mask, sizeof(*mask));
If you are a new contributor to FRR, please see our contributing guidelines.
After making changes, you do not need to create a new PR. You should perform an amend or interactive rebase followed by a force push.
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address ignored by zebra It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Missed: - connected and kernel routes may duplicate (need to filter out kernel if already detected as connected) - IPv6 nexthop by ifindex - not sure how to handle properly Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
0f312b8
to
08b1250
Compare
this does not work properly yet:
|
This PR is not properly handling alias routes as kernel -vs- connected. |
|
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
Provided additional check, now duplicates are not installed:
|
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
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-FRRPULLREQ-20539/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings
|
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-FRRPULLREQ-20541/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings
|
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 4: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO4DEB10AMD64-20544/test Topology Tests failed for Topotests debian 10 amd64 part 4:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20544/artifact/TOPO4DEB10AMD64/ErrorLog/log_topotests.txt Successful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests debian 10 amd64 part 4: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO4DEB10AMD64-20544/test Topology Tests failed for Topotests debian 10 amd64 part 4:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20544/artifact/TOPO4DEB10AMD64/ErrorLog/log_topotests.txt
|
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 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO9U18I386-20542/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20542/artifact/TOPO9U18I386/ErrorLog/log_topotests.txt Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO6U18AMD64-20542/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 6:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20542/artifact/TOPO6U18AMD64/ErrorLog/log_topotests.txt Topotests Ubuntu 18.04 i386 part 4: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO4U18I386-20542/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 4:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20542/artifact/TOPO4U18I386/ErrorLog/log_topotests.txt Successful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO9U18I386-20542/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 9:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20542/artifact/TOPO9U18I386/ErrorLog/log_topotests.txt Topotests Ubuntu 18.04 amd64 part 6: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO6U18AMD64-20542/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 6:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20542/artifact/TOPO6U18AMD64/ErrorLog/log_topotests.txt Topotests Ubuntu 18.04 i386 part 4: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TOPO4U18I386-20542/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 4:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-20542/artifact/TOPO4U18I386/ErrorLog/log_topotests.txt
|
Additional consideration about connected routes: somehow strange connected addresses reflects actual interface configuration: Example - interface with tree aliases, same network:
3 addresses assigned on interface, one route installed
A bit miss-matched with what is on interfaces and in system routing table Ok, now let's put aliases with /32 netmask:
What is in FRR:
Looks more consistent, but a bit asymmetrical
And this looks more "symmetrical", but, probably, this is qustion of other issue. |
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-FRRPULLREQ-20550/ 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.
I would recommend adding a new function rib_add_kernel_route that we can abstract this problem a bit better.. Yes we have not properly abstracted this but at some point in time in the future we are getting full dplane breakup from having access to rib internals in zebra. This way we centralize all the different data planes we talk to a bit better.
a8c1090
to
5847482
Compare
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
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-FRRPULLREQ-20576/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings
|
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
741262e
to
5aa2177
Compare
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
5aa2177
to
998c236
Compare
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
998c236
to
1a3a667
Compare
Continuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: FailedRedhat 9 amd64 build: Failed (click for details)Redhat 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/RH9BUILD/config.status/config.statusMake failed for Redhat 9 amd64 build:
Redhat 9 amd64 build: Unknown Log <config.log.gz> Ubuntu 18.04 amd64 build: Failed (click for details)Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U1804AMD64/config.status/config.statusMake failed for Ubuntu 18.04 amd64 build:
Ubuntu 18.04 amd64 build: Unknown Log <config.log.gz> Debian 11 amd64 build: Failed (click for details)Debian 11 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/DEB11AMD64/config.log/config.log.gzMake failed for Debian 11 amd64 build:
Debian 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/DEB11AMD64/config.status/config.status FreeBSD 11 amd64 build: Failed (click for details)FreeBSD 11 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI009BUILD/config.log/config.log.gz FreeBSD 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI009BUILD/config.status/config.statusMake failed for FreeBSD 11 amd64 build:
FreeBSD 12 amd64 build: Failed (click for details)FreeBSD 12 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/FBSD12AMD64/config.log/config.log.gz FreeBSD 12 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/FBSD12AMD64/config.status/config.statusMake failed for FreeBSD 12 amd64 build:
CentOS 7 amd64 build: Failed (click for details)CentOS 7 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI005BUILD/config.log/config.log.gz CentOS 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI005BUILD/config.status/config.statusMake failed for CentOS 7 amd64 build:
Ubuntu 18.04 i386 build: Failed (click for details)Make failed for Ubuntu 18.04 i386 build:
Ubuntu 18.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U18I386BUILD/config.status/config.status Redhat 8 amd64 build: Failed (click for details)Redhat 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/REDHAT8/config.status/config.statusMake failed for Redhat 8 amd64 build:
Redhat 8 amd64 build: Unknown Log <config.log.gz> OpenBSD 7 amd64 build: Failed (click for details)OpenBSD 7 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI011BUILD/config.log/config.log.gz OpenBSD 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI011BUILD/config.status/config.statusMake failed for OpenBSD 7 amd64 build:
Ubuntu 18.04 arm8 build: Failed (click for details)Make failed for Ubuntu 18.04 arm8 build:
Ubuntu 18.04 arm8 build: Unknown Log <config.log.gz> Debian 9 amd64 build: Failed (click for details)Debian 9 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI021BUILD/config.log/config.log.gz Debian 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI021BUILD/config.status/config.statusMake failed for Debian 9 amd64 build:
Ubuntu 20.04 amd64 build: Failed (click for details)Ubuntu 20.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U2004AMD64BUILD/config.log/config.log.gzMake failed for Ubuntu 20.04 amd64 build:
Ubuntu 20.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U2004AMD64BUILD/config.status/config.status Ubuntu 18.04 ppc64le build: Failed (click for details)Ubuntu 18.04 ppc64le build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U1804PPC64LEBUILD/config.log/config.log.gz Ubuntu 18.04 ppc64le build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U1804PPC64LEBUILD/config.status/config.statusMake failed for Ubuntu 18.04 ppc64le build:
Ubuntu 22.04 amd64 build: Failed (click for details)Ubuntu 22.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U22AMD64BUILD/config.log/config.log.gzMake failed for Ubuntu 22.04 amd64 build:
Ubuntu 22.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U22AMD64BUILD/config.status/config.status Debian 10 amd64 build: Failed (click for details)Debian 10 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/DEB10BUILD/config.status/config.statusMake failed for Debian 10 amd64 build:
Debian 10 amd64 build: Unknown Log <config.log.gz> Ubuntu 18.04 arm7 build: Failed (click for details)Ubuntu 18.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U18ARM7BUILD/config.status/config.status Ubuntu 18.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U18ARM7BUILD/config.log/config.log.gzMake failed for Ubuntu 18.04 arm7 build:
Warnings Generated during build:Checkout code: Successful with additional warningsRedhat 9 amd64 build: Failed (click for details)Redhat 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/RH9BUILD/config.status/config.statusMake failed for Redhat 9 amd64 build:
Redhat 9 amd64 build: Unknown Log <config.log.gz> Ubuntu 18.04 amd64 build: Failed (click for details)Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U1804AMD64/config.status/config.statusMake failed for Ubuntu 18.04 amd64 build:
Ubuntu 18.04 amd64 build: Unknown Log <config.log.gz> Debian 11 amd64 build: Failed (click for details)Debian 11 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/DEB11AMD64/config.log/config.log.gzMake failed for Debian 11 amd64 build:
Debian 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/DEB11AMD64/config.status/config.status FreeBSD 11 amd64 build: Failed (click for details)FreeBSD 11 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI009BUILD/config.log/config.log.gz FreeBSD 11 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI009BUILD/config.status/config.statusMake failed for FreeBSD 11 amd64 build:
FreeBSD 12 amd64 build: Failed (click for details)FreeBSD 12 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/FBSD12AMD64/config.log/config.log.gz FreeBSD 12 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/FBSD12AMD64/config.status/config.statusMake failed for FreeBSD 12 amd64 build:
CentOS 7 amd64 build: Failed (click for details)CentOS 7 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI005BUILD/config.log/config.log.gz CentOS 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI005BUILD/config.status/config.statusMake failed for CentOS 7 amd64 build:
Ubuntu 18.04 i386 build: Failed (click for details)Make failed for Ubuntu 18.04 i386 build:
Ubuntu 18.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U18I386BUILD/config.status/config.status Redhat 8 amd64 build: Failed (click for details)Redhat 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/REDHAT8/config.status/config.statusMake failed for Redhat 8 amd64 build:
Redhat 8 amd64 build: Unknown Log <config.log.gz> OpenBSD 7 amd64 build: Failed (click for details)OpenBSD 7 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI011BUILD/config.log/config.log.gz OpenBSD 7 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI011BUILD/config.status/config.statusMake failed for OpenBSD 7 amd64 build:
Ubuntu 18.04 arm8 build: Failed (click for details)Make failed for Ubuntu 18.04 arm8 build:
Ubuntu 18.04 arm8 build: Unknown Log <config.log.gz> Debian 9 amd64 build: Failed (click for details)Debian 9 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI021BUILD/config.log/config.log.gz Debian 9 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/CI021BUILD/config.status/config.statusMake failed for Debian 9 amd64 build:
Ubuntu 20.04 amd64 build: Failed (click for details)Ubuntu 20.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U2004AMD64BUILD/config.log/config.log.gzMake failed for Ubuntu 20.04 amd64 build:
Ubuntu 20.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U2004AMD64BUILD/config.status/config.status Ubuntu 18.04 ppc64le build: Failed (click for details)Ubuntu 18.04 ppc64le build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U1804PPC64LEBUILD/config.log/config.log.gz Ubuntu 18.04 ppc64le build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U1804PPC64LEBUILD/config.status/config.statusMake failed for Ubuntu 18.04 ppc64le build:
Ubuntu 22.04 amd64 build: Failed (click for details)Ubuntu 22.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U22AMD64BUILD/config.log/config.log.gzMake failed for Ubuntu 22.04 amd64 build:
Ubuntu 22.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U22AMD64BUILD/config.status/config.status Debian 10 amd64 build: Failed (click for details)Debian 10 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/DEB10BUILD/config.status/config.statusMake failed for Debian 10 amd64 build:
Debian 10 amd64 build: Unknown Log <config.log.gz> Ubuntu 18.04 arm7 build: Failed (click for details)Ubuntu 18.04 arm7 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U18ARM7BUILD/config.status/config.status Ubuntu 18.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-12812/artifact/U18ARM7BUILD/config.log/config.log.gzMake failed for Ubuntu 18.04 arm7 build:
|
PR was changed according suggestion, also, rebase for more recent version was of master was done |
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 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-12813/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 debian 10 amd64 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-12813/test Topology Tests failed for Topotests debian 10 amd64 part 3
|
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
1a3a667
to
fc9d2ad
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: FailedAddresssanitizer topotests part 9: Failed (click for details)
Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-ASAN9-12814/test Topology Tests failed for Addresssanitizer topotests part 9 Topotests Ubuntu 18.04 i386 part 7: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO7U18I386-12814/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 7 Successful on other platforms/tests
|
Continuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedAddresssanitizer topotests part 4: Failed (click for details)
Addresssanitizer topotests part 4: Unknown Log Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-ASANP4-12815/test Topology Tests failed for Addresssanitizer topotests part 4 Addresssanitizer topotests part 9: Failed (click for details)
Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-ASAN9-12815/test Topology Tests failed for Addresssanitizer topotests part 9 Topotests 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-12815/artifact/TP3U1804AMD64/TopotestDetails/Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TP3U1804AMD64-12815/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 3 Successful on other platforms/tests
|
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
fc9d2ad
to
db51caf
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 Ubuntu 18.04 amd64 part 8: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO8U18ARM64-12828/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 8 Topotests debian 10 amd64 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-12828/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 8: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO8U18ARM64-12828/test Topology Tests failed for Topotests Ubuntu 18.04 amd64 part 8 Topotests debian 10 amd64 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3DEB10AMD64-12828/test Topology Tests failed for Topotests debian 10 amd64 part 3
|
Fixes: FRRouting#9188 Kernel routes added with no nexthop IP address now installed by zebra, excluding these of them who already known as connected It is pretty usual for ptp/tunnel interfaces to add route just to interface, not on gateway IP Usual way to add such route is - route add 172.22.9.0/24 -iface wg0 Signed-off-by: Vladimir Grebenschikov <vova@fbsd.ru>
db51caf
to
2b8548d
Compare
Continuous 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-12849/ This is a comment from an automated CI system. |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Fix for Issue #9185
Advice?