- dev - lists.frrouting.org

[frr] syntax for route map matching ipv6 prefix
by Thomas Hilse 30 Jan '17

30 Jan '17

Hi team, I have tried FRR (version 2.0-rc0-ci.NetDEF.org-20170126.021714-git.1e78204) downloaded from the "netdef" build system: https://ci1.netdef.org/ (FRR build #53 - version for freebsd 10.3) In my test setup - dual homed connection to one ISP - all seems to work as expected. (quagga 1.1.1 has a regression - https://bugzilla.quagga.net/show_bug.cgi?id=870 FRR in my setup is not affected from this regression.) However I am wondering how to define a route map matching an ipv6 prefix in FRR. The syntax which is working with quagga seems to be invalid in FRR (or not supported). I am using route maps to filter the redistribution of routes and to modify the BGP route metricies between the two connections to our ISP. ipv6 prefix-list V6-PREFIX seq 5 permit 2001:db8:1cc:222::/64 ! route-map V6-RM permit 10 match ipv6 address prefix-list V6-PREFIX ! Best regards Thomas

2 4

[frr] The bgpafisafi pull request
by Donald Sharp 26 Jan '17

26 Jan '17

https://github.com/freerangerouting/frr/pull/107 Philippe - You had a review comment two days ago: how do you initialise vrf in the case vrf_name is already null ( commands with no vrf at all)? I would lie the *vrf value to be set inside that function. I responded with: I do not believe this is the right thing to do. Only the calling function knows what the right defaults are for the afi/safi/vrf due to we assume different defaults based upon the command. This approach would break the ability for the calling function to do the right thing. As I stated I will update the Pull Request with better documentation for this funciton. I've also added a commit that updates the function to further explain it. Is there anything else you would like to have done? donald

2 1

[frr] BGP Large Community Support is now in master
by Donald Sharp 26 Jan '17

26 Jan '17

All - We have integrated BGP Large Community Support into master. Please give it a whirl! https://github.com/freerangerouting.com/frr Thanks to all who got this done! thanks! donald

1 0

[frr] Comparison of patches in 1.1.1
by Donald Sharp 25 Jan '17

25 Jan '17

1.1.1 patches Revert "ospf6d: Update router-LSA when nbr's interface-ID changes -> I believe we've fixed this via a different commit lib: limit size of vty buffer to 4096 bytes -> We have lib: ensure vty buf is nul terminated and wrap puts to it with checks -> We implemented this fix differently lib: bump library version -> We need to bump our library version to 2.0.0. Discuss if we need to change the name of libzebra so we avoid library collision? zebra: fix build on OpenBSD >= 5.9 -> We have this fix already via another route vtysh: make warnings about node installs a non-default compile-time option -> We just fixed the root of this issue vtysh: Fix, guard against NULL pointer dereference -> We have this one vty: Add ctrl-v <literal> to allow, e.g., '?' to be input for regex -> We probably should figure out how to grab this. HACKING: set a4paper by default -> Who cares HACKING: Add 'Objectives', 'Governance', and an initial 'Code of Conduct' -> Not needed HACKING: Update useful URLs -> Not needed configure: Bump version to 1.1.1 -> Not needed The only item we should consider is the vty: Add ctrl-v .... fix. Except it is by Paul and there is no Signed-off-by:.... If someone wants to approach Paul or port this over feel free. I'm not going to do that work.

1 0

[frr] Today's Agenda
by Donald Sharp 25 Jan '17

25 Jan '17

1) Stable/2.0 2) Pull Requests State 3) Olivier's working Proposal Anything else?

2 2

Re: [frr] [quagga-dev 16497] Re: Security list changes (Transparency?)
by Olivier Dugeon 20 Jan '17

20 Jan '17

Hello Martin, I'm pretty sure that Paul is now aware of our FRR initiative and decided to remove all FRR contributors to Quagga list. Just look at Quagga on savannah. Now, there is only 2 admins: Paul and Greg. If I remember right there is more admin, at least Donald. Regards Olivier Le 11/01/2017 à 14:47, Martin Winter a écrit : > On 11 Jan 2017, at 16:24, Paul Jakma wrote: > >> Hi Martin, >> >> I removed you. >> >> I'd be glad to talk further on transparency with you. > > I think it would be beneficial for everyone to have a open discussion on who should be on the list > or not. > > I don’t like to have this discussion in privacy - this isn’t about me. Maybe I did something stupid > or you (or community?) decided on new rules for who should be on it. I think it would be beneficial > to everyone to have make it public on who is on the list and probably why they are on the list (so > it makes somehow the selection more transparent. > > BTW: It seems it was some larger “cleanup” as more people got removed as well. Not just me. > > So please, can you share your thoughts publicly? > > Regards, > > - Martin > >> On Wed, 11 Jan 2017, Martin Winter wrote: >> >>> For the ones here who are unaware: >>> >>> There is a security list (security(a)quagga.net) which deals with security issues reported to Quagga: Assessing them, fixing them, provide the much needed disclosures etc. This is a closed list which had mostly “maintainers” and a few other selected individuals on it. >>> >>> As part of our testing, I used to be on this list as well - until yesterday when I was taken off without explanation. >>> >>> Not blaming anyone, but I was surprised on it - and wanted to get a public discussion on who is on the list and that I might no longer be able to test security fixes in private as part of this. >>> >>> So who is still on the list? Or did the list get deleted? Or what happened? >>> >>> Regards, >>> >>> - Martin Winter >>> >>> _______________________________________________ >>> Quagga-dev mailing list >>> Quagga-dev(a)lists.quagga.net >>> https://lists.quagga.net/mailman/listinfo/quagga-dev >>> >> >> -- >> Paul Jakma | paul(a)jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A >> Fortune: >> A university faculty is 500 egotists with a common parking problem. > > _______________________________________________ > Quagga-dev mailing list > Quagga-dev(a)lists.quagga.net > https://lists.quagga.net/mailman/listinfo/quagga-dev

3 4

Re: [frr] [freerangerouting/frr] feature/zebra-srcdest (#98)
by Christian Franke 20 Jan '17

20 Jan '17

Hello Donald, On 01/20/2017 02:58 PM, Donald Sharp wrote: > I don't understand what we are trying to achieve here as that I don't > understand the srcdest feature in linux. Can we get an email to the > frr alias with a quick overview and design document? The motivation and design of Dst-src routing is described in the IETF working group document draft-ietf-rtgwg-dst-src-routing. [1] Among other things, this feature is useful for multihomed networks without their own address space in the face of ISPs employing BCP38, which is likely to become more common with the progressing adoption of IPv6. The pull request extends Zebra so that it can support dst-src routes in its RIB, providing the basis for implementing dynamic routing with dst-src routes. Please let me know if there are any more questions. -Christian [1] https://tools.ietf.org/html/draft-ietf-rtgwg-dst-src-routing-03

1 0

[frr] Current Pull Requests and their state
by Donald Sharp 20 Jan '17

20 Jan '17

Sending this out because I wanted to make sure we were all on the same page of what I think needs to be done. Sorting from Oldest -> Newest: 1) https://github.com/freerangerouting/frr/pull/42 PIM-SM + MSDP -> pull to master request This code passes the CI system now, and has 1 review comment in regards to using a large buffer size that still needs to be addressed. Additionally this code will not function properly for register messages( at the very least ) on *bsd. 2) https://github.com/freerangerouting/frr/pull/44 BGP VRF Route Distinguisher configuration + VRF import Processing + VRF Multipath -> pull to master request This code passes the CI system and had/has 2 questions being asked: 1) Functional -> How does this fit in with the vnc code already there? 2) CLI: How do we properly envision configuration? Question #2 I believe we have consensus via the RD/RT vrf-policy discussion from Tuesday. Question #1 I believe we need to have a better understanding of RFAPI how it works and how we plan to fit the two systems together. Lou -> I believe David is working on setting up a meeting to discuss this. 3) https://github.com/freerangerouting/frr/pull/75 Fix a number of VPN SAFI related issues, add vrf flavor of vnc commands -> pull request to stable/2.0 Currently this code needs to be merged with latest stable/2.0. Additionally I believe there is discussion about whether or not we are putting to many new commands into stable/2.0 from David. I cannot remember the result of that discussion? 4) https://github.com/freerangerouting/frr/pull/88 Mergedown vpn old format -> pull request to master Code passes both CI and is ready to be merged. I plan to look at this further today. 5) https://github.com/freerangerouting/frr/pull/90 Master version of #83 Fix a number of VPN/Encap SAFI related issues (no VRF CLI changes) -> pull request to master Code passes both CI and is ready to be merged. I plan to look at this further today. 6) https://github.com/freerangerouting/frr/pull/92 Support for BGP Large Communities -> pull request to master Code passes CI and is ready to be merged. An issue has been identified in regards to broken show ip bgp command that I need to address. 7) https://github.com/freerangerouting/frr/pull/93 Various Build Warnings Fixage -> Pull request to master Code passes CI and is ready to be merged. An issue has been identified that can either be fixed now or in a future commit. 8) https://github.com/freerangerouting/frr/pull/96 lib: guard strict cli completeions -> pull request to master Code passes CI and is ready to be merged. I do not believe anyone has looked at it yet. 9) https://github.com/freerangerouting/frr/pull/97 2.0 version of vrf-policy and add/clear vrf prefix vty support Code passes CI and is ready to be merged. I do not believe anyone has looked at it yet. 10) https://github.com/freerangerouting/frr/pull/98 feature/zebra-srcdest Code passes CI and is ready to be merged. Request for feature discussion has been made. thanks! donald

1 0

[frr] 2.0-rc1 tagged, ready for test blasting
by David Lamparter 20 Jan '17

20 Jan '17

Hi everyone, as the 2.0-rc1 github issue list is finally empty, we have 2.0-rc1 tagged in git: https://github.com/freerangerouting/frr/releases/tag/frr-2.0-rc1 so, please throw all testing at it that you may have available and report any and all issues (even tiny bits!) on: https://github.com/freerangerouting/frr/milestone/2 (please make sure to put the "2.0-rc2" tag on it!) Cheers, -David

1 0

[frr] Todays Technical Agenda
by Donald Sharp 18 Jan '17

18 Jan '17

11 am EST ( 4pm UTC ) - If you would like an invite please unicast me. Agenda: 1) Last Week status 2) RD/RT - cli finish 3) Olivier's Proposal for Pull Requests 4) Functional changes needed for VRF 5) Formating changes 6) If you have something you want to add to the agenda, let me know! Thanks!

2 2