add support for SRv6 IPv4 L3VPN #9649
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
proelbtn
changed the title
proelbtn
changed the title
proelbtn
force-pushed
the
add-support-for-end-dt4
branch
from
dd02af9 to
0ed86ba
Compare
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
|
This PR is a new feature and must go in after the 2 week window |
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDTest incomplete. See below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: IncompleteAddresssanitizer topotests part 4: Incomplete(check logs for details)Successful on other platforms/tests
|
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)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3U18I386-284/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 3: see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-284/artifact/TOPO3U18I386/ErrorLog/log_topotests.txt Successful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests Ubuntu 18.04 i386 part 3: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-PULLREQ2-TOPO3U18I386-284/test Topology Tests failed for Topotests Ubuntu 18.04 i386 part 3: see full log at https://ci1.netdef.org/browse/FRR-PULLREQ2-284/artifact/TOPO3U18I386/ErrorLog/log_topotests.txt CLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
|
ci:rerun |
slankdev
reviewed
Sep 21, 2021
tests/topotests/bgp_srv6l3vpn_to_bgp_vrf2/test_bgp_srv6l3vpn_to_bgp_vrf2.py
Show resolved
Hide resolved
slankdev
reviewed
Sep 21, 2021
tests/topotests/bgp_srv6l3vpn_to_bgp_vrf2/test_bgp_srv6l3vpn_to_bgp_vrf2.py
Outdated
Show resolved
Hide resolved
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)Topotests Ubuntu 18.04 i386 part 9: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topotests Ubuntu 18.04 i386 part 9: No useful log foundCLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
proelbtn
force-pushed
the
add-support-for-end-dt4
branch
from
0ed86ba to
34ebf6b
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-PULLREQ2-343/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warningsCLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
|
ci:rerun |
proelbtn
force-pushed
the
add-support-for-end-dt4
branch
from
34ebf6b to
ab9c5ae
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-PULLREQ2-497/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warningsCLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
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)Topotests debian 10 amd64 part 9: No useful log foundTopotests Ubuntu 18.04 amd64 part 9: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 9: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests debian 10 amd64 part 9: Failed (click for details)Topotests debian 10 amd64 part 9: No useful log foundTopotests Ubuntu 18.04 amd64 part 9: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 9: No useful log foundCLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
|
ci:rerun |
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 1: Failed (click for details)Topotests debian 10 amd64 part 1: No useful log foundTopotests Ubuntu 18.04 amd64 part 1: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 1: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests debian 10 amd64 part 1: Failed (click for details)Topotests debian 10 amd64 part 1: No useful log foundTopotests Ubuntu 18.04 amd64 part 1: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 1: No useful log foundCLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
|
ci:rerun |
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-509/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warningsCLANG Static Analyzer Summary
1 Static Analyzer issues remaining.See details at |
@donaldsharp 4 weeks has passed when you first comment, I'm looking forward to any review :). |
proelbtn
commented
Oct 19, 2021
proelbtn
force-pushed
the
add-support-for-end-dt4
branch
2 times, most recently
from
8e2e2ea to
53fa878
Compare
idryzhov
reviewed
Nov 22, 2021
Continuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: FailedUbuntu 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-1719/artifact/U18I386BUILD/config.status/config.status CentOS 8 amd64 build: Failed (click for details)CentOS 8 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CENTOS8BUILD/config.log/config.log.gzMake failed for CentOS 8 amd64 build: CentOS 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CENTOS8BUILD/config.status/config.status 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-1719/artifact/U18ARM7BUILD/config.status/config.status Ubuntu 18.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U18ARM7BUILD/config.log/config.log.gzMake failed for Ubuntu 18.04 arm7 build: Fedora 29 amd64 build: Failed (click for details)Fedora 29 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/F29BUILD/config.log/config.log.gz Fedora 29 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/F29BUILD/config.status/config.statusMake failed for Fedora 29 amd64 build: Debian 11 amd64 build: Failed (click for details)Debian 11 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/DEB11AMD64/config.status/config.status Ubuntu 16.04 i386 build: Failed (click for details)Ubuntu 16.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1604I386/config.log/config.log.gz Ubuntu 16.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1604I386/config.status/config.statusMake failed for Ubuntu 16.04 i386 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 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-1719/artifact/DEB10BUILD/config.status/config.statusMake failed for Debian 10 amd64 build: Debian 10 amd64 build: Unknown Log <config.log.gz> Ubuntu 16.04 arm7 build: Failed (click for details)Make failed for Ubuntu 16.04 arm7 build: Ubuntu 16.04 arm7 build: Unknown Log <config.log.gz> CentOS 7 amd64 build: Failed (click for details)CentOS 7 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/CI005BUILD/config.status/config.statusMake failed for CentOS 7 amd64 build: Debian 9 amd64 build: Failed (click for details)Debian 9 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/CI021BUILD/config.status/config.statusMake failed for Debian 9 amd64 build: Ubuntu 16.04 arm8 build: Failed (click for details)Ubuntu 16.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U16ARM8BUILD/config.status/config.status Ubuntu 16.04 arm8 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U16ARM8BUILD/config.log/config.log.gzMake failed for Ubuntu 16.04 arm8 build: Ubuntu 16.04 amd64 build: Failed (click for details)Ubuntu 16.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CI014BUILD/config.log/config.log.gz Ubuntu 16.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CI014BUILD/config.status/config.statusMake failed for Ubuntu 16.04 amd64 build: Ubuntu 18.04 amd64 build: Failed (click for details)Ubuntu 18.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1804AMD64/config.log/config.log.gz Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1804AMD64/config.status/config.statusMake failed for Ubuntu 18.04 amd64 build: Ubuntu 18.04 ppc64le build: Failed (click for details)Ubuntu 18.04 ppc64le build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/U1804PPC64LEBUILD/config.status/config.statusMake failed for Ubuntu 18.04 ppc64le 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-1719/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-1719/artifact/U2004AMD64BUILD/config.status/config.status Successful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsUbuntu 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-1719/artifact/U18I386BUILD/config.status/config.status CentOS 8 amd64 build: Failed (click for details)CentOS 8 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CENTOS8BUILD/config.log/config.log.gzMake failed for CentOS 8 amd64 build: CentOS 8 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CENTOS8BUILD/config.status/config.status 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-1719/artifact/U18ARM7BUILD/config.status/config.status Ubuntu 18.04 arm7 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U18ARM7BUILD/config.log/config.log.gzMake failed for Ubuntu 18.04 arm7 build: Fedora 29 amd64 build: Failed (click for details)Fedora 29 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/F29BUILD/config.log/config.log.gz Fedora 29 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/F29BUILD/config.status/config.statusMake failed for Fedora 29 amd64 build: Debian 11 amd64 build: Failed (click for details)Debian 11 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/DEB11AMD64/config.status/config.status Ubuntu 16.04 i386 build: Failed (click for details)Ubuntu 16.04 i386 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1604I386/config.log/config.log.gz Ubuntu 16.04 i386 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1604I386/config.status/config.statusMake failed for Ubuntu 16.04 i386 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 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-1719/artifact/DEB10BUILD/config.status/config.statusMake failed for Debian 10 amd64 build: Debian 10 amd64 build: Unknown Log <config.log.gz> Ubuntu 16.04 arm7 build: Failed (click for details)Make failed for Ubuntu 16.04 arm7 build: Ubuntu 16.04 arm7 build: Unknown Log <config.log.gz> CentOS 7 amd64 build: Failed (click for details)CentOS 7 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/CI005BUILD/config.status/config.statusMake failed for CentOS 7 amd64 build: Debian 9 amd64 build: Failed (click for details)Debian 9 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/CI021BUILD/config.status/config.statusMake failed for Debian 9 amd64 build: Ubuntu 16.04 arm8 build: Failed (click for details)Ubuntu 16.04 arm8 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U16ARM8BUILD/config.status/config.status Ubuntu 16.04 arm8 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U16ARM8BUILD/config.log/config.log.gzMake failed for Ubuntu 16.04 arm8 build: Ubuntu 16.04 amd64 build: Failed (click for details)Ubuntu 16.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CI014BUILD/config.log/config.log.gz Ubuntu 16.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/CI014BUILD/config.status/config.statusMake failed for Ubuntu 16.04 amd64 build: Ubuntu 18.04 amd64 build: Failed (click for details)Ubuntu 18.04 amd64 build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1804AMD64/config.log/config.log.gz Ubuntu 18.04 amd64 build: config.status output from configure script can be found at https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/artifact/U1804AMD64/config.status/config.statusMake failed for Ubuntu 18.04 amd64 build: Ubuntu 18.04 ppc64le build: Failed (click for details)Ubuntu 18.04 ppc64le build: Unknown Log URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-1719/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-1719/artifact/U1804PPC64LEBUILD/config.status/config.statusMake failed for Ubuntu 18.04 ppc64le 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-1719/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-1719/artifact/U2004AMD64BUILD/config.status/config.status |
🛑 Basic BGPD CI results: FAILUREResults table
For details, please contact louberger |
This patch enables zebra to insert End.DT4 nexthop into linux kernel. Signed-off-by: Ryoga Saito <ryoga.saito@linecorp.com>
This patch enables sharpd to insert End.DT4 routes into zebra. Signed-off-by: Ryoga Saito <ryoga.saito@linecorp.com>
There is an test for SRv6 VPNv6, This is a clone for SRv6 VPNv4. Signed-off-by: Ryoga Saito <ryoga.saito@linecorp.com>
Co-authored-by: Hiroki SHIROKURA <slank.dev@gmail.com> Signed-off-by: Ryoga Saito <contact@proelbtn.com>
proelbtn
force-pushed
the
add-support-for-end-dt4
branch
from
721adf6 to
1c5fede
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 i386 part 9: Failed (click for details)Topotests Ubuntu 18.04 i386 part 9: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests Ubuntu 18.04 i386 part 9: Failed (click for details)Topotests Ubuntu 18.04 i386 part 9: No useful log found |
|
ci:rerun |
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 6: Failed (click for details)Topotests debian 10 amd64 part 6: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests debian 10 amd64 part 6: Failed (click for details)Topotests debian 10 amd64 part 6: No useful log found |
|
ci:rerun |
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 4: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 4: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Checkout code: Successful with additional warningsTopotests Ubuntu 18.04 amd64 part 4: Failed (click for details)Topotests Ubuntu 18.04 amd64 part 4: No useful log found |
|
ci:rerun |
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-1739/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings |
|
@donaldsharp @idryzhov take a look again please? |
|
Dear Developer(s), I was testing this patch for creating srv6 IPv4 VPN in a virtual environment. The setup can be described as following: a virtual machine (Debian 11 with kernel 5.16 or 5.11) is used as a playground. A docker container compiled with the lastest version of FRR with this patch is used to emulate routers and hosts, which are connected as a linear (h1<->R1<->R2<->h2) topology. The two routers are configured as the following files. Things looks good, except that adding seg6local action End.DT4 seems not working. Executing vtysh commands: "show bgp segment-routing srv6" and "show ip route vrf vrf10" gives:
Execute the command to list the routes in the default routing table, "ip -6 r show" gives: Basically, the routing rule to instruct the decapsulation of srv6 packets is missing, and the seg6local action for local SID is not correctly configured. The routes to send to the remote IPv4 addresses is sitting in VRf10, which is correct. would anyone happen to know some hints for this issue? R1 configuration file: R2 configuration file: |
|
Thanks for testing my patch. First, please check the value of net.vrf.strict_mode. It should be set to 1 (it's the requirement to insert End.DT4 routes into kernel). If End.DT4 routes aren't shown up after you set net.vrf.strict_mode to 1, please send me debug log (please enable these items: zebra rib, zebra kernel msgdump, bgp updates). |
@proelbtn thanks for your reply. The original post was updated a bit to provide more accurate description. Further tests are done, when net.vrf.strict_mode is set to 1. The nexthop pointing to vrftable seems not working, others look good to me. I also tested to manually add the local decap function using iproute2, "ip route add 2002:ac:1:0: 100::/128 encap seg6local action End.DT4 vrftable 1010 dev eth0", which eventually can add a route into the default routing table, as following: The debug information, which I believe that leads to the End.DT4 failure is attached here: |
|
@byteocean Thanks. I believe the insertion error is occured with this reason: You also should set net.ipv6.conf.all.disable_ipv6 or net.ipv6.conf.vrf10.disable_ipv6 to 0 because the next-hop device of the inserted End.DT4 routes is the VRF device (below is the output of ip addr and ip -6 route in my environment). |
|
@proelbtn Thanks a lot for the hint. I think, indeed it was the problem you pointed out that leads to the issue of inserting the End.DT4 action. btw, since the iproute2 command, "ip route add 2002:ac:1:0: 100::/128 encap seg6local action End.DT4 vrftable 1010 dev eth0", is able to execute with the kernel < 5.14. Would it be possible to adapt the patch to the approach of adding route instead of adding nexthop? |
|
@byteocean Yes, we can add SRv6 End.DT4 routes into kernel with For more information please look at: http://vger.kernel.org/netconf2017_files/nexthop-objects.pdf |
|
@donaldsharp @idryzhov Happy new year! Take a review again, please? |
|
Hi @proelbtn, I am not familiar with SRv6 and can't properly review the code. |
|
When I contribute vpnv4 with SRv6, @mjstapp , @riw777 , @odd22 reviewed my PR. ref: #5865 @mjstapp @riw777 @odd22 |
|
Would be really cool to get this PR merged for the next frr release! 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current version of FRR couldn't insert routes whose nexthop is End.DT4. This patch adds support for them.
First and Second patch enables bgpd and sharpd to handle routes whose End.DT4 routes.
Third path are topotest for SRv6 IPv4 L3VPN. Linux prior to 5.14 couldn't handle End.DT4 nexthop correctly (for detail, see below), so this topotest requires Linux 5.15.
https://patchwork.kernel.org/project/netdevbpf/patch/20210902052014.605249-1-contact@proelbtn.com/