Bug 78305 - RFE: systemd-networkd: support persistent tun/tap devices
Summary: RFE: systemd-networkd: support persistent tun/tap devices
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-05 15:46 UTC by Till Maas
Modified: 2014-08-15 14:35 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Till Maas 2014-05-05 15:46:23 UTC 
Please support persistent tun/tap devices that are owned by an user or group with systemd-network. Example code can be found here:
http://www.virtualbox.org/svn/vbox/trunk/src/apps/tunctl/tunctl.c

Notice: The devices can have arbitrary names and do not need to be named like tun0 or tap0 (not sure if tunctcl.c allows this).
Comment 1 Tom Gundersen 2014-06-24 00:30:19 UTC 
I'd be happy to merge support for this. Could I ask you what usecase you have in mind?
Comment 2 Till Maas 2014-06-24 08:56:37 UTC 
(In reply to comment #1)
> I'd be happy to merge support for this. Could I ask you what usecase you
> have in mind?

I use it with openvpn to setup a tap device so that openvpn does not need to setup the device and can run with less privileges (this allows for example to use the script-security 0 directive in openvpn). Also I used it to be able to run SSH or socat VPN as a normal user after preparing the device as root to have less code running as root.
Comment 3 Tom Gundersen 2014-08-15 14:35:58 UTC 
This has now been implemented.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.