Difference between revisions of "Tun-Tap"
Jump to navigation
Jump to search
(Created page with "Category: Network Category: Empty articles") |
|||
| Line 1: | Line 1: | ||
| + | Tun-Tap devices are used by e.g. OpenVPN software. CRIU has support for them. | ||
| + | |||
| + | == Devices == | ||
| + | |||
| + | The netdevice entry sits in <code>netdev-ID.img</code> image file and has optional <code>tun</code> field. | ||
| + | |||
| + | == Files == | ||
| + | |||
| + | Other than this there's always a reg-file entry in the [[images]] for tun deivce. In addition to this there's an entry in the <code>tunfile</code> image. The device-to-file mapping is performed by device name. | ||
| + | |||
[[Category: Network]] | [[Category: Network]] | ||
| − | [[Category: | + | [[Category: Under the hood]] |
Latest revision as of 14:13, 27 September 2016
Tun-Tap devices are used by e.g. OpenVPN software. CRIU has support for them.
Devices[edit]
The netdevice entry sits in netdev-ID.img image file and has optional tun field.
Files[edit]
Other than this there's always a reg-file entry in the images for tun deivce. In addition to this there's an entry in the tunfile image. The device-to-file mapping is performed by device name.