Skip to main content

You're viewing an archived page. It is no longer being updated.

Open Source Working Group Minutes RIPE 76

Open Source Working Group
Thursday, 17 May 11:00 - 12:30
WG Co-Chairs: Martin Winter, Ondrej Filip
Scribe: Anand Buddhdev
Status: Final

A. Administrative Matters

The chairs opened the session. They requested that people submit presentations earlier because it helps with the planning.

B. Three Is the Magic Number: the RPKI Validator Born Again

Tim Bruijnzeels, RIPE NCC

The presentation is available at:

There were no comments or questions.

C. One year of FRRouting

Martin Winter, NetDEF

The presentation is available at:

Charles Eckel (Cisco) asked whether they have considered using the YANG model.

Martin said there is some more work happening in this area. Discussion is happening, but there is no decision yet.

Job Snijders (NTT) noted that Ubuntu 12.04 is still being supported even though it has reached the end of its life. Martin said that he wanted to drop support for it, but maintaining compatibility with it isn't too difficult.  he said that supporting CentOS 6 was more difficult. Support for these may be dropped with newer versions, because it's hard to build for these older OSes.

Philip (NetAssist) asked about the progress with VRF support. He also asked about support for multiple routing tables, as BIRD does. He said that this feature is very useful for traffic engineering. Finally, he asked about an API for statistics.

Martin asked Philip to talk to him later to understand what kind of statistics he needs. Martin said that he didn't think anyone was using SNMP. He wanted to know if JSON output might be useful, and know what other things might be useful. He then said that the multiple routing table support is in there in the VRF code. He said there's a way to run multiple BGP instances, and many ways to achieve what Philip is looking for.

D. Open-only Networking

Alex Saroyan, XCloud Networks

The presentation is available at:

Baptise Jonglez (University Grenoble Alps) asked whether FRR was running on switches or routers. Alex said he loves FRR, and they use it everywhere. They even contribute to FRR, and use some of its features like BGP unnumbered, because it's easy to configure and use.

Baptiste also asked whether Alex runs layer 3 everywhere, and whether each server was on its own layer 2 network. Alex said that they did, with loopback.

Philip (NetAssist) commented that it was good to use such nice usage of open source tools. He then asked how link state propagation is done. He also wanted to know how the Linux kernel route table is propagated to silicon.

Alex said one doesn't want to wait for BGP timers to expire. Instead, ports are monitored, and if the link goes down, a daemon listening generates a message towards the router, where FRR resets the BGP session.

Alex then explained that on switches, the netOS handles this. On Cumulus, for example, there's a daemon called switchd, that talks to the ASIC over an API, and communicates routing changes to the ASIC. Broadcom's API is not open, but you get access to it with NDAs with Broadcom.

E. Turris Mox OSHW

Ondrej Filip, CZ.NIC

The presentation is online at:

Blake Willis asked whether the boot loader in use was uboot or EFI. Ondrej said it was uboot. Blake then asked if Ondrej had looked looked at the EFI loader? Ondrej said he had not seen it, but would be happy to consider it.

Alexander (NetAssist) asked whether there was PON support in the SFP model?

Ondrej said he didn't know but would look into it.

F. Lightning Talks

The presentations can be found here:

F1. Kea Open Source DHCP Update

Victoria Risk, Internet Systems Consortium

The presentation is online at:

Peter Hessler (OpenBSD project) asked about what "premium hook library" meant.

Victoria explained that they are for-sale add-ons.

F2. Could Blockchain Help in Inter-Domain Security?

Jordi Paillissé Vilanova, Polytechnic University of Catalonia

The presentation is online at:

Ondrej Sury (ISC) asked what problem this solves.

Jordi said it's for checking origin AS (similar to RPKI).