From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764831AbXGTT6j (ORCPT ); Fri, 20 Jul 2007 15:58:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757325AbXGTT6a (ORCPT ); Fri, 20 Jul 2007 15:58:30 -0400 Received: from khc.piap.pl ([195.187.100.11]:55067 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751689AbXGTT63 (ORCPT ); Fri, 20 Jul 2007 15:58:29 -0400 To: andrei radulescu-banu Cc: Stephen Hemminger , Patrick McHardy , linux-kernel@vger.kernel.org, Linux Netdev List Subject: Re: Linux, tcpdump and vlan References: <997818.30021.qm@web56615.mail.re3.yahoo.com> From: Krzysztof Halasa Date: Fri, 20 Jul 2007 21:58:27 +0200 In-Reply-To: <997818.30021.qm@web56615.mail.re3.yahoo.com> (andrei radulescu-banu's message of "Thu, 19 Jul 2007 09:02:38 -0700 (PDT)") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Another idea - perhaps we could make the software VLANs behave the same as hw ones? I.e., stripping the tag on RX while setting some magic skb field? The packets could go via main interface first (normal path, with eth_type_trans stripping the tag and setting protocol = some 802.1Q), netif_rx | netif_receive_skb, then through the VLAN device with finally eth_type_trans setting the IPv4 etc. protocol to pass to L3 layers. I can see potential problems on TX, the packets would have to be presented without the tag (but with VLAN ID set somewhere in the skb) and that probably means all drivers would have to be modified. Seems a bit of work, I know my message is missing the patch... -- Krzysztof Halasa