From owner-freebsd-net@FreeBSD.ORG Wed Feb 2 11:05:32 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8C7716A4CE; Wed, 2 Feb 2005 11:05:32 +0000 (GMT) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C0D143D31; Wed, 2 Feb 2005 11:05:32 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-2.free.fr (Postfix) with ESMTP id EB334C0BA; Wed, 2 Feb 2005 12:05:30 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 425BD407C; Wed, 2 Feb 2005 12:05:11 +0100 (CET) Date: Wed, 2 Feb 2005 12:05:11 +0100 From: Jeremie Le Hen To: Nickolay Kritsky Message-ID: <20050202110511.GN60177@obiwan.tataz.chchile.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: freebsd-net@FreeBSD.org cc: andre@FreeBSD.org cc: Jeremie Le Hen Subject: Re: dummynet and vr(4)/egress broken in 4.11 ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 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, 02 Feb 2005 11:05:32 -0000 > Take a look at PRs 61685 and 76539. Hope that helps. Well, I was aware of the first one (I'm doing shaping on my internal interface as a workaround), but not the second one. The second one is very new and this could indeed be the same problem I encountered. It seems that the import of IPFilter 3.4.35 in the middle of 2004 is the source of the problem because when I switch back to 3.4.31 on 4.11, everything works. I Cc'ed andre@ since he had not took over 76539, maybe he's not aware of it. Andre, what can you tell us about the drawbacks of the proposed patches ? I think there must be some as they would have been merged if this was not the case. Are there any change to have this fixed in RELENG_4 ? I know that no more releases are scheduled in this branch, but there is no obvious reason to let a bug live there IMHO. -- Jeremie Le Hen jeremie@le-hen.org