From owner-freebsd-net@FreeBSD.ORG Wed Oct 19 14:36:38 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F998106564A for ; Wed, 19 Oct 2011 14:36:38 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 084BA8FC22 for ; Wed, 19 Oct 2011 14:36:37 +0000 (UTC) Received: by wyi40 with SMTP id 40so2302581wyi.13 for ; Wed, 19 Oct 2011 07:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=88SSNcJbtxXSZeoa/skFJsGOWCAxkEReeUhKvbnVFz0=; b=xvYPRcY5g3TskPw0p5+vqX+R9szGsS3k9Wlz3apjX7xRp6lkxDPNvibVtKP25e8bXy FIZ9cPIStTh/SuKXVliSJhCp8ljpL5AFz2YjcASkMAyos62LHJaA0VHimx0BnSbImp7C Apx9nR1rAl6INGGHfkkXwjBsyxJ+ECuitcxus= MIME-Version: 1.0 Received: by 10.227.127.205 with SMTP id h13mr2679274wbs.92.1319034997032; Wed, 19 Oct 2011 07:36:37 -0700 (PDT) Received: by 10.180.96.104 with HTTP; Wed, 19 Oct 2011 07:36:36 -0700 (PDT) In-Reply-To: <4e9e6ba6.c972cd0a.3d45.ffffd504@mx.google.com> References: <4e9e0de3.4364cc0a.38b5.ffffc94f@mx.google.com> <4e9e6ba6.c972cd0a.3d45.ffffd504@mx.google.com> Date: Wed, 19 Oct 2011 10:36:36 -0400 Message-ID: From: Ryan Stone To: Rozhuk.IM@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net Subject: Re: ether_demux does not handle frames with embedded vlan tags X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2011 14:36:38 -0000 2011/10/19 : > This may be a wrong configuration or QinQ: packet may have M_VLAN tag is > set and still vlan-tagged (ether_type = VLAN) It is not QinQ in my case. The interface that the upper hook exports is that you send it a valid ethernet frame and it passes that frame up the stack. A vlan-tagged frame is a valid frame so I don't see why it should not be handled correctly.