This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] My description of function of TUN TAP interface. Please for

To: vbox-dev@xxxxxxxxxxxxxx
Subject: [Xen-devel] My description of function of TUN TAP interface. Please for correct.
From: "Pavel Muller" <pav.muller@xxxxxxxxx>
Date: Mon, 24 Mar 2008 16:41:16 +0100
Delivery-date: Wed, 23 Apr 2008 06:12:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=C1v2uw9VpOKmRQ+Tqnhx/9Lzfwdr91wZGZ0L5yOIeg4=; b=MGkaL5VViuy3AQCUYzI/ABf7zLMcqLaqFn/AICJhoG9v3l6g15BBKWRkUWTFBKIPZtW9aHsNqwiLroUC3ATvDMjL06v/8re3ryUeAsJ2Rju6/r2qqfQgJpK1+gtg3qHCDh4NtpeARBNW1rJpWobN1xvKQB/mmkGgMPvTEpsfUqI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type; b=EnXiaDtZHU2CDtKjYaagadiakEuBrV5i58NO2PQeTArbLkgcdxaICetFOYamEK3IlkFigVgFq93/SCpep++qhTWyc7eml0W5+J4nBZjJqlHKUtV/ScW7kdYNMMfmtshThpUlQ2OfqdqUE58DUwX0vcwulml8sa4y+P6Otyt2cLo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hier is link with my diagram TUN TAP communication.

Blocks on the diagram:

Aplikace - something application which use virtual network interface
/dev/net/tun - virtual network interface -> it is OK?
universal TUN TAP interface - driver for virtual network interface -> it is OK?
ovladac eth0 - driver eth0 (sorry for czech language:) )
eth0 - NIC (physical hardware)

White narrow - show route (way) outgoing (data from application to the network)
red narrow - show route (way) incoming (data from the network to the application)

OUTGOING communication
1)App send data (with virtual IP) to the TCP/IP stack.
2)TCP/IP stack decide that data are determined for virtual network interface and send

    they to the universal TUN TAP interface.

3)universal TUN TAP interface send data to the /dev/net/tun

4)/dev/net/tun send data to the TCP/IP stack

5)TCP/IP stack send data to eth0 driver

6)eth0 driver send data to NIC

INCOMING communication
1)From the NIC to eth0 driver
2)From eth0 driver to TCP/IP stack
3)From TCP/IP stack to universal TUN TAP interface
4)From universal TUN TAP interface to /dev/net/tun
5)From /dev/net/tun to Application

Thanks for your help.
Regard Pavel
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] My description of function of TUN TAP interface. Please for correct., Pavel Muller <=