- dev - lists.frrouting.org

Re: [dev] FRR Router 6.0.2 eigrp neighbor
by Donald Sharp 05 Feb '19

05 Feb '19

Can we get a `show ip eigrp int` and a `show ip eigrp neigh`? On Mon, Feb 4, 2019 at 6:12 AM akÿfffffdn ak via dev <dev(a)lists.frrouting.org> wrote: > > > > > ---------- Forwarded message ---------- > From: "akÿfffffdn ak" <akinengineer(a)yahoo.com> > To: "dev(a)lists.frrouting.org" <dev(a)lists.frrouting.org> > Cc: > Bcc: > Date: Mon, 4 Feb 2019 11:11:25 +0000 (UTC) > Subject: FRR Router 6.0.2 eigrp neighbor > Hi > Router1# > frr version 6.0.2 > ! > interface ens37 > ip address 192.168.10.1/24 > ! > router-id 1.1.1.1 > ! > router eigrp 10 > network 192.168.10.0/24 > network 192.168.127.0/24 > > Router2# > frr version 6.0.2 > ! > interface ens37 > ip address 192.168.10.2/24 > ! > router-id 1.1.1.2 > ! > router eigrp 10 > network 192.168.10.0/24 > network 192.168.127.0/24 > > > but there is not any eigrp neighbor between two router. > What else should I do for installing eigrp neighborhood between two router? > > > > > ---------- Forwarded message ---------- > From: "akÿfffffdn ak via dev" <dev(a)lists.frrouting.org> > To: "dev(a)lists.frrouting.org" <dev(a)lists.frrouting.org> > Cc: > Bcc: > Date: Mon, 04 Feb 2019 03:12:11 -0800 (PST) > Subject: [dev] FRR Router 6.0.2 eigrp neighbor > _______________________________________________ > dev mailing list > dev(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/dev

1 0

Conditions to have code accepted into the project
by Albert López 05 Feb '19

05 Feb '19

Dear all, We have an implementation of the LISP protocol and we are evaluating how easy would be to adapt it to be integrated in the FRRouting project. Our initial code has its own memory management, timers (task scheduling), ... In order to know how much of the code can be reused, I would like to know if it is really mandatory to use the memory management library provided by the FRRouting project or the task scheduling (for instance to send periodic control messages) to have the code accepted and merged in the FRRRouting project. Another question we have is that our code is licensed under Apache 2. Is FRRouting license compatible with apache 2 ? I believe yes but I am not sure. Best regards Albert López

4 7

FRR Router 6.0.2 eigrp neighbor
by akÿfffffdn ak 04 Feb '19

04 Feb '19

HiRouter1#frr version 6.0.2! interface ens37 ip address 192.168.10.1/24!router-id 1.1.1.1!router eigrp 10 network 192.168.10.0/24 network 192.168.127.0/24 Router2# frr version 6.0.2! interface ens37 ip address 192.168.10.2/24!router-id 1.1.1.2!router eigrp 10 network 192.168.10.0/24 network 192.168.127.0/24 but there is not any eigrp neighbor between two router.What else should I do for installing eigrp neighborhood between two router?

1 0

Slack invite
by Tim Osburn 28 Jan '19

28 Jan '19

Could I get a invite to the FRRouting slack channel please? Tim Osburn W7RSZ / JG1MBR https://www.osburn.com

1 0

Invite to Slack
by Morgan Humes 27 Jan '19

27 Jan '19

Hi, I'm looking to get an invite to the Slack server. Thanks! Morgan morgan(a)lanaddict.com

1 0

Fwd: [NetDev-People] 0x13: Registration is now open
by Donald Sharp 25 Jan '19

25 Jan '19

All - The netdev conference has opened up registration. I look forward to seeing you there! donald ---------- Forwarded message --------- From: Jamal Hadi Salim via people <people(a)lists.netdevconf.org> Date: Fri, Jan 25, 2019 at 6:27 AM Subject: [NetDev-People] 0x13: Registration is now open To: people <people(a)netdevconf.org> Cc: <program-committee(a)netdevconf.org> We are pleased to announce the opening of registration for Netdev 0x13. Netdev 0x13 conference will be held on March 20th-22nd at the Hotel Grandium in Prague, Czech Republic. https://www.hotel-grandium.cz/en/ As always: Our main motivation is to bring the community together to the idea exchange fountain we call Netdev conf. We have a large amount of good submissions this time and we are going to be on a tight schedule. For that reason, in addition to several breaks, we have decided to provide lunch as well. We do not aim to make profit from the event; however, to recoup some of the cost we have raised our registration fee by CDN $10/day. Cost is: CDN $350 + 21% VAT (CDN $423.50) for early bird registration which expires on February 20th 11:59PM Eastern time. Starting Feb 21st onwards, the price goes up to $430CAD + Taxes (VAT) = $520.30 CAD Students are 50% off (ID required) EU laws require we charge Value Added Tax (VAT) on the registration fee. VAT must be paid on the registration fees in the country where the conference is held. We will be posting more info on the website, for now to register go to: https://www.onlineregistrations.ca/Netdev0x13/ Where to stay: The conference is at the Hotel Grandium in Prague. https://www.hotel-grandium.cz/en/ We will provide you with a discount code for that hotel in the next day or so. Announcement will be sent via email and posted on the website cheers, jamal _______________________________________________ people mailing list people(a)netdevconf.org https://lists.netdevconf.org/cgi-bin/mailman/listinfo/people

1 0

Re: [dev] Open Network Equipment and FRRouting
by Andrew Lunn 23 Jan '19

23 Jan '19

On Mon, Jan 21, 2019 at 01:54:48PM +0000, Łukasz Wójcik via dev wrote: > Date: Mon, 21 Jan 2019 14:17:45 +0100 > From: Łukasz Wójcik <lukasz.wojcik(a)zoho.com> > To: dev(a)lists.frrouting.org > Subject: Open Network Equipment and FRRouting > > Hello there, > > > In the era of Open Networking equipment, e.g. switching ASICs support > forwarding based on L3 information. I was wondering, > if FRRouting supports or plans to support any mechanisms that would > allow for passing L3 data to the hardware, and therefore > offloading some work to the HW ? I would imagine some kind of API or > event-driven mechanisms that would require HW manufacturer's Hi Łukasz There are multiple ways to do this. The simplest is to just use the kernel APIs as they are for adding/removing routes. The kernel already has all the internal plumbing to pass the information down into the switch driver, and offload it to the hardware. FFR just works. The problem is, few of the Open Networking equipment are actually open. They have a big binary blob SDK running in user space, not an open source driver in the kernel. Andrew

4 5

hello can you add me to slack ?
by Jean-Daniel Pauget 22 Jan '19

22 Jan '19

hello, just asking for a slack access ?! regards, -- Jean-Daniel Pauget http://rezopole.net/ Rezopole/LyonIX +33 (0)4 27 46 00 50

2 1

Re: [dev] Open Network Equipment and FRRouting
by JR Rivers 22 Jan '19

22 Jan '19

There are also commercial offerings available that couple the kernel networking stack to switching hardware. cheers, JR On Mon, Jan 21, 2019 at 2:31 PM Łukasz Wójcik via dev < dev(a)lists.frrouting.org> wrote: > > > > ---------- Forwarded message ---------- > From: "Łukasz Wójcik" <lukasz.wojcik(a)zoho.com> > To: Hagen Woesner <hagen.woesner(a)bisdn.de>, dev(a)lists.frrouting.org > Cc: > Bcc: > Date: Mon, 21 Jan 2019 20:10:12 +0100 > Subject: Re: [dev] Open Network Equipment and FRRouting > I'll definitely check that out. Open Source, and is documented ;-) > > > Best regards, > > -ŁW > > On 21-Jan-19 18:11, Hagen Woesner wrote: > > Dear Łukasz, > > We (BISDN) have developed baseboxd, which is a netlink-to-OFDPA > > translator, and therefore works with FRR on whitebox switches, however > > there are of course still limitations in the number of platforms and > > supported features. > > For a number of Delta, Edge-core, Quanta, Celestica switches you can > > find ONIE images for download > > (http://repo.bisdn.de/pub/onie-testing/) and could try it out yourself. > > I hope this is not perceived as too much advertisement, after all it's > > free and Open Source, so I think it should be acceptable here. > > > > Documentation and code: > > https://www.basebox.org/ > > https://www.github.com/bisdn/basebox > > https://docs.bisdn.de > > > > Best regards, > > Hagen > > > > > > Am 21.01.19 um 17:04 schrieb Łukasz Wójcik via dev: > >> _______________________________________________ > >> dev mailing list > >> dev(a)lists.frrouting.org > >> https://lists.frrouting.org/listinfo/dev > > > > > > > > > > > ---------- Forwarded message ---------- > From: "Łukasz Wójcik via dev" <dev(a)lists.frrouting.org> > To: Hagen Woesner <hagen.woesner(a)bisdn.de>, dev(a)lists.frrouting.org > Cc: > Bcc: > Date: Mon, 21 Jan 2019 14:31:58 -0800 (PST) > Subject: Re: [dev] Open Network Equipment and FRRouting > _______________________________________________ > dev mailing list > dev(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/dev >

1 0

Re: [dev] Open Network Equipment and FRRouting
by Hagen Woesner 21 Jan '19

21 Jan '19

Dear Łukasz, We (BISDN) have developed baseboxd, which is a netlink-to-OFDPA translator, and therefore works with FRR on whitebox switches, however there are of course still limitations in the number of platforms and supported features. For a number of Delta, Edge-core, Quanta, Celestica switches you can find ONIE images for download (http://repo.bisdn.de/pub/onie-testing/) and could try it out yourself. I hope this is not perceived as too much advertisement, after all it's free and Open Source, so I think it should be acceptable here. Documentation and code: https://www.basebox.org/ https://www.github.com/bisdn/basebox https://docs.bisdn.de Best regards, Hagen Am 21.01.19 um 17:04 schrieb Łukasz Wójcik via dev: > _______________________________________________ > dev mailing list > dev(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/dev -- BISDN GmbH Dr.-Ing. Hagen Woesner Körnerstraße 7-10, 10785 Berlin, Germany mailto hagen.woesner(a)bisdn.de tel: +49 30 610816101 mobile: +49 160 7862096 www.bisdn.de Berlin Institute for Software Defined Networks - BISDN GmbH Managing Directors: Dr.-Ing. Hagen Woesner, Andreas Köpsel Commercial register: Amtsgericht Berlin-Charlottenburg HRB 141569 B VAT ID No: DE283257294 Corporate seat: Berlin

2 1