wiki:KarlsruheHackathon2017

Version 32 (modified by Gert Döring, 5 years ago) (diff)

route/tun discussion

OpenVPN Hackathon 2017

who

This year's hackathon is organized by Heiko Hund (d12fk).

We will stick to the format of the previous years, which means attendance is in principle limited to "active developers that are also regularly contributing to #openvpn-devel or the mailing list". We should have enough space in the meeting room for 16 devs.

who is coming?

Name Topics Arrival Departure Hotel
Heiko Hund - Fri. 10am Sun. 20pm @home
Antonio Quartulli traffic manipulation API Thu noon Sun afternoon Der Blaue Reiter
Samuli Seppänen OpenVPN 3 development Thu late evening Sun mid-afternoon Der Blaue Reiter
Steffan Karger Post-quantum key exchange, performance Fri 13:16 (Bhf Durlach) Sun mid-afternoon Blaue Reiter
Gert Döring  branch maintenance - what goes where, and why? Fri noon-ish Sun late afternoon Blauer Reiter
Arne Schwabe  - Fri 12 am at HBF Sun late afternoon Blauer Reiter
David Sommerseth clean-ups, plug-ins, OpenVPN 3 client Thursday evening Sun afternoon Blaue Reiter
Lev Stipakov ovpn3 Thu late evening Sun mid-afternoon Der Blaue Reiter
Jan Just Keijser performance, EduVPN Friday early afternoon Sun late-afternoon Der Blaue Reiter
Gert van Dijk Post-quantum key exchange, documentation Fri 13:16 (Bhf Durlach) Sun mid-afternoon Blaue Reiter
Johan Draaisma Moral support Thu noon-ish Sun at noon Der Blaue Reiter
James Yonan Thursday   
Simon Rozman eduVPN, MSI packaging Thu late evening Sun mid-afternoon Der Blaue Reiter
François Kooman eduVPN, OAuth Thu afternoon Mon Der Blaue Reiter

where?

The meeting is held at the Sophos office in Karlsruhe (Germany): https://osm.org/go/0DlEda7Ld?m=&node=2127345937.

Karlsruhe is an one hour ICE train ride away from Frankfurt Airport.

If you have any questions or got lost - please contact Heiko at +49 172 74 911 92.

when?

The hackathon will take place from Friday November 10th 2017 to Sunday November 12th.

what?

So what is the goal of the Hackathon?

  • should we get rid of LZ4 as bundled library and always rely on what the system has installed?
  • plan clean up route.c and tun.c - which approach should we use? improve OS/distro modularization? settle on an improved API?
  • add more topics here!

We're all open for additions here - I think the meetings in Brussels (2011+2012), Munich (2013+2014), Delft (2015) and Helsinki (2016) have shown that "just being able to sit together and hack" is a useful exercise.

input

There will be drinks and snacks to get us through the day. We have a kitchen, so you can also make sandwiches or a bowl of cereals. Chance of BBQ if there's demand in November.

internet

Free Wifi and wired network is available

accommodation

The closest Hotel is the "Der Blaue Reiter" just across the street.
Cheapest accomodation is IBIS budget a good 10 minute walk away.

results =

(informal notes on some of the discussions that benefit from writing down)

  • MSI (samuli, simon, ...)
    • discussed - next steps?
  • route.c / tun.c rehaul (ordex, dazo, cron2, jjk)
    • Linux support for ifconfig/route is dropped
    • we keep iproute2 support (because jjk brought up special cases where you really want to call out to external programs that can be wrapped to "do local thins", and --up scripts are just much more effort)
    • we add direct netlink support
    • netlink support needs to come along with strong unit tests that verifies all setter/getter operations using explicit "ip ..." calls to verify that our abstraction layer is really doing what it's meant to (cron2 worried about binary representations being error-prone)
    • the netlink library needs to clearly print what it does to the log ("what it thinks it does", and the unit test needs to ensure that this is actually true)
    • we split route.c to route.c and route-platform.c, but we do not want route-{linux,freebsd,netbsd,solaris,..}.c as that would be mostly copy-paste code duplication of mostly identical code with "one line different" (the route call)
    • we look into splitting tun.c into tun-unix.c and tun-win32.c, but not tun-{linux,freebsd,netbsd,solaris,...].c, for the same reasons
    • tun.c needs to see all those nearly-identical tun_read()/tun_write() functions merged into one place, and then we see what else is copy-paste code reuse
  • vagrant (dazo, mattock, cron2)
    • ...?