From owner-freebsd-net@FreeBSD.ORG Thu Apr 12 10:20:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DD01C16A400 for ; Thu, 12 Apr 2007 10:20:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id B5DE613C457 for ; Thu, 12 Apr 2007 10:20:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id A9671215098; Thu, 12 Apr 2007 06:20:33 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 12 Apr 2007 06:20:31 -0400 X-Sasl-enc: pwmU/pWn2U1AvP8vE6IEZLaADfk3Kzvm0G0GKuzhn+Q/ 1176373231 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 5B8E26237; Thu, 12 Apr 2007 06:20:31 -0400 (EDT) Message-ID: <461E07ED.90201@FreeBSD.org> Date: Thu, 12 Apr 2007 11:20:29 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (X11/20070407) MIME-Version: 1.0 To: yoitsmeremember@evil-geni.us References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Net mailing list Subject: Re: altq unfortunately queuing vlan traffic. 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: Thu, 12 Apr 2007 10:20:31 -0000 I can't speak for ALTQ at the moment however I believe dummynet may work on vlan devices. I was careful not to break this when rewriting ether_input() in -CURRENT, as ip_dn_check_rule() is always called any time ether_demux() is entered (regardless if ether_input() has been re-entered due to the presence of M_PROMISC on a given mbuf chain). Regards, BMS