Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756684AbZKRBkR (ORCPT ); Tue, 17 Nov 2009 20:40:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755997AbZKRBkQ (ORCPT ); Tue, 17 Nov 2009 20:40:16 -0500 Received: from wolverine01.qualcomm.com ([199.106.114.254]:17929 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755950AbZKRBkP (ORCPT ); Tue, 17 Nov 2009 20:40:15 -0500 X-IronPort-AV: E=McAfee;i="5300,2777,5805"; a="27846689" Message-ID: <4B035081.8040900@qualcomm.com> Date: Tue, 17 Nov 2009 17:40:17 -0800 From: Max Krasnyansky User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20090922 Fedora/3.0-3.9.b4.fc12 Thunderbird/3.0b4 MIME-Version: 1.0 To: andrew hendry CC: "netdev@vger.kernel.org" , linux-kernel Subject: Re: [PATCH] Documentation, clarify tuntap IPX example. References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2310 Lines: 45 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 > > --- 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/