- dev - lists.frrouting.org

[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

[frr] Request for additional eyes on Pull Requests
by Donald Sharp 06 Jan '17

06 Jan '17

All - We have multiple pull requests that are over 2 weeks old now: https://github.com/freerangerouting/frr/pulls We could use some help looking at the pull requests and getting them integrated. thanks! donald

1 1

[frr] Today's Technical Meeting Agenda
by Donald Sharp 03 Jan '17

03 Jan '17

My apologies to everyone for sending this out late. I am just coming back from vacation :) 1) Status 2) Large Community 3) Access to the Repo and what that means. 4) EVPN discussion cont'd. donald

1 1

[frr] [PATCH v2 0/10] BGP VRF Route Distinguisher configuration
by Philippe Guibert 21 Dec '16

21 Dec '16

This series of patches introduces the ability for a BGP router, to configure a route distinguisher and associate import and export route targets. This permits for a BGP update to be sent with BGP extended communities associated to the exported route targets of the RD. This permits for a BGP update to be received, and to be handled according to the imported route targets of the RD contained in BGP extended communities. This patch is rebased with latest from master branch. It also relies on RD/RT discussions. It implements partial option 6, that is to say introduction of vrf subnode under bgp router node, and subsequent rt/rd vty commands. The testing on this patch shows the ability of route processing bgp updates with associated extended communities ( according to RT export values). Route server configuration with vpnv4 has also been showed to work. The second version of this patch is adding some documentation. It also fixes an issue related to initialisation of bgp vrf context. Cheers, Philippe

1 10

[frr] [PATCH v2 0/10] BGP VRF Route Distinguisher configuration
by Philippe Guibert 21 Dec '16

21 Dec '16

This series of patches introduces the ability for a BGP router, to configure a route distinguisher and associate import and export route targets. This permits for a BGP update to be sent with BGP extended communities associated to the exported route targets of the RD. This permits for a BGP update to be received, and to be handled according to the imported route targets of the RD contained in BGP extended communities. This patch is rebased with latest from master branch. It also relies on RD/RT discussions. It implements partial option 6, that is to say introduction of vrf subnode under bgp router node, and subsequent rt/rd vty commands. The testing on this patch shows the ability of route processing bgp updates with associated extended communities ( according to RT export values). Route server configuration with vpnv4 has also been showed to work. The second version of this patch is adding some documentation. It also fixes an issue related to initialisation of bgp vrf context. Cheers, Philippe

2 11

[frr] List renamed (cmaster-next => frr)
by David Lamparter 20 Dec '16

20 Dec '16

Hi all, I've just renamed the mailing list from cmaster-next to frr. You may need to update your mail filters to match the new name. The old address should still work for sending mails to the mailing list. (Archives & subscriber list should be same as before). We may of course want to run the list somewhere else that is not a personal box of mine; I don't mind running it for now and will of course supply the config & archives. Cheers, -David P.S.: I'm in favour of *not* using an external list service, mostly due to some of these going away and taking their archives with them. Even if we have backups, it's seriously annoying when URLs don't work anymore. It'd be OK if we have backups *and* we can do stable URLs under a domain we own, though at that point we can just run our own mailman. It's not hard..

1 0

[cmaster-next] [PATCH] Rationalize Link Parameters flags
by Olivier Dugeon 20 Dec '16

20 Dec '16

Rationalize Link Parameters flags * lib/if.h: Remove LP_TE as Link Parameters is set if different from 0 See IS_LINK_PARAMS_SET macro and use LP_TE_METRIC to determine if TE metric is set or not * lib/if.c: replace LP_TE by LP_TE_METRIC in default LP status * zebra/interface.c: replace LP_TE by LP_TE_METRIC and check if TE metric is equal to standard metric or not * ospfd/ospf_te.c: replace LP_TE by LP_TE_METRIC * isisd/isis_te.c: replace LP_TE by LP_TE_METRIC Signed-off-by: Olivier Dugeon <olivier.dugeon(a)orange.com> --- isisd/isis_te.c | 2 +- lib/if.c | 4 ++-- lib/if.h | 9 ++++++--- ospfd/ospf_te.c | 2 +- zebra/interface.c | 8 ++++---- 5 files changed, 14 insertions(+), 11 deletions(-)

2 5

[cmaster-next] [PATCH 0/7] BGP VRF Route Distinguisher configuration
by Philippe Guibert 20 Dec '16

20 Dec '16

This series of patches introduces the ability for a BGP router, to configure a route distinguisher and associate import and export route targets. This permits for a BGP update to be sent with BGP extended communities associated to the exported route targets of the RD. This permits for a BGP update to be received, and to be handled according to the imported route targets of the RD contained in BGP extended communities. This patch is rebased with latest from master branch. It also relies on RD/RT discussions. It implements partial option 6, that is to say introduction of vrf subnode under bgp router node, and subsequent rt/rd vty commands. The testing on this patch shows the ability of route processing bgp updates with associated extended communities ( according to RT export values). Route server configuration with vpnv4 has also been showed to work. Cheers, Philippe

1 7