January 2017 - dev - lists.frrouting.org

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 19 Jan '17

19 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

[frr] Workflow Reminder
by Donald Sharp 12 Jan '17

12 Jan '17

We just had a accidental push of https://github.com/freerangerouting/frr/commit/903c7f556e6631e5f20f2d720e35… to master. I would like to remind people that they are trusted to have commit permission if they are part of the organization or team. Let's follow our guidelines for committing that are outlined here: https://github.com/freerangerouting/frr/blob/master/COMMUNITY.md thanks! donald

1 0

[frr] Slack Channel
by Donald Sharp 12 Jan '17

12 Jan '17

All the slack channel is at: freerangerouting.slack.com I'm hoping to get the invites setup so there is no need to get special permission. In the meantime, feel free to unicast me with your request if you can't get in. donald

1 0

[frr] changing address-family vpn&encap config
by Lou Berger 12 Jan '17

12 Jan '17

Hi all, this is related to cleaning up the confusion of treating the vpn safi as afi+safi, see https://github.com/freerangerouting/frr/issues/61. Does anyone object to the following change to *config* in *stable/2.0* - note this will break backwards compatibility (reading old will be preserved, but output will only be new) OLD address-family ipv4 address-family ipv4 (unicast|multicast) address-family ipv6 address-family ipv6 (unicast|multicast) address-family vpnv4 address-family vpnv4 unicast address-family vpnv6 address-family vpnv6 unicast address-family encap address-family encapv4 address-family encapv6 new address-family <ipv4|ipv6> [<unicast|multicast|vpn|encap>] //default is unicast Lou

2 2

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

11 Jan '17

1) Status 2) Pull Request : https://github.com/freerangerouting/frr/pull/44 -> RD/RT cli discussion -> Functionality how does this properly fit into vnc? 3) Anything else? donald

3 5

[cmaster-next] support for capnproto API on Quagga
by Philippe Guibert 10 Jan '17

10 Jan '17

Hi all, I am working on some support of capnproto interface on Quagga (following David's contribution). In order to avoid duplication of effort, I would like first to get your review from cmaster-next community, The code can be seen here: https://lists.quagga.net/pipermail/quagga-dev/2016-December/016521.html then, based on your reviews, I'll update the patch series and I'll work to rebase it on cmaster-next too. Thanks, Regards, Philippe

1 3