From: Max Krasnyansky <maxk@qualcomm.com>
To: andrew hendry <andrew.hendry@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation, clarify tuntap IPX example.
Date: Tue, 17 Nov 2009 17:40:17 -0800 [thread overview]
Message-ID: <4B035081.8040900@qualcomm.com> (raw)
In-Reply-To: <d45a3acc0911171730kc3a03d5iacec6d9ef4b1874c@mail.gmail.com>
On 11/17/2009 05:30 PM, andrew hendry wrote:
> Can the TUNSETIFF ioctl change a tap's protocol to IPX as the
> documentation suggests?
> I think tun.c would need IFF_IPX_TAP added for it to work as described?
> Otherwise tap can only be ptp or ethernet, and there is no way to
> route or use AF_IPX.
TAP is an Ethernet device. No special handling is required for IPX or
for that matter any other protocol. Example seems fine too.
Max
> Signed-off-by: Andrew Hendry<andrew.hendry@gmail.com>
>
> --- a/Documentation/networking/tuntap.txt 2009-11-11
> 14:03:22.676167648 +1100
> +++ b/Documentation/networking/tuntap.txt 2009-11-18
> 11:34:18.106647029 +1100
> @@ -127,12 +127,14 @@ Ethernet device, which instead of receiv
> media, receives them from user space program and instead of sending
> packets via physical media sends them to the user space program.
>
> -Let's say that you configured IPX on the tap0, then whenever
> -the kernel sends an IPX packet to tap0, it is passed to the application
> -(VTun for example). The application encrypts, compresses and sends it to
> -the other side over TCP or UDP. The application on the other side decompresses
> -and decrypts the data received and writes the packet to the TAP device,
> -the kernel handles the packet like it came from real physical device.
> +Let's say for the purpose of example, IPX support was added to tuntap.
> +Then whenever the kernel routes an IPX packet to tap0, it is passed to the
> +application reading the file descriptor from /dev/net/tun (VTun for example).
> +The application encrypts, compresses and sends it to the other side over TCP
> +or UDP. The application on the other side decompresses and decrypts the data
> +received and writes the packet to the TAP device, the remote kernel handles
> +the packet like it came from real physical device. The IPX applications are
> +able to communicate as if there was a real IPX network.
>
> 4. What is the difference between TUN driver and TAP driver?
> TUN works with IP frames. TAP works with Ethernet frames.
next prev parent reply other threads:[~2009-11-18 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 1:30 [PATCH] Documentation, clarify tuntap IPX example andrew hendry
2009-11-18 1:40 ` Max Krasnyansky [this message]
2009-11-18 2:14 ` andrew hendry
2009-11-18 5:52 ` Max Krasnyansky
2009-11-18 9:03 ` andrew hendry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B035081.8040900@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=andrew.hendry@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).