BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//events.eurobsdcon.org//2026//talk//TUT8LU
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2026-TUT8LU@events.eurobsdcon.org
DTSTART;TZID=CET:20260912T140000
DTEND;TZID=CET:20260912T144500
DESCRIPTION:A challenge when setting up VPNs is the proper modification of 
 the routing table.  This is needed\, so that all traffic goes through the 
 VPN interface and is encrypted\, except the encrypted traffic generated by
  the VPN interface.  Even so\, this approach has its pitfalls\, which can 
 cause leaking unencrypted traffic[[1]].\n\nNetwork namespaces offer a way 
 to categorically solve this problem.  Network namespaces partition the net
 work interfaces present in a host.  A process running in a given network n
 amespace only sees the interfaces present within that network namespace.  
 If only the VPN interface is present\, traffic will have to go through thi
 s interface\, making it impossible to send traffic through another interfa
 ce by accident.\n\nOn OpenBSD network namespaces are called routing domain
 s.  Combine routing domains with Wireguard\, which is routing domains awar
 e out of the box\, offer safer VPNs\, while also simplifying configuration
 .  A similar effect can be achieved for other VPNs by using virtual machin
 es.\n\nIn this talk we go over the problems when just modifying the routin
 g table\, how routing domains work and can be used.\n\n[1]: https://www.us
 enix.org/conference/usenixsecurity23/presentation/xue
DTSTAMP:20260715T125837Z
LOCATION:D.0.03
SUMMARY:Reducing the headache of VPNs with routing domains - Martin Vahlens
 ieck
URL:https://events.eurobsdcon.org/2026/talk/TUT8LU/
END:VEVENT
END:VCALENDAR