From owner-freebsd-ipfw@FreeBSD.ORG Sun Nov 29 19:14:50 2009 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C15C1065676 for ; Sun, 29 Nov 2009 19:14:50 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mgwigglesworth.net (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id C24358FC16 for ; Sun, 29 Nov 2009 19:14:49 +0000 (UTC) To: Kevin Smith Date: Sun, 29 Nov 2009 14:02:27 -0500 Envelope-To: kerbzo@gmail.com, admin@benaianet.com, freebsd-ipfw@freebsd.org, freebsd-current@freebsd.org, ben@wanderview.com References: <4B129960.9030107@gmail.com> <4B12B6B9.3030106@bsd.com.br> <4B12C32F.3060709@gmail.com> Message-ID: <4B12C543.2070204@mgwigglesworth.net> From: "Mailing LIst Member" Received: from [192.168.5.12] (192.168.5.12 [192.168.5.12]) by mgwigglesworth.net; Sun, 29 Nov 2009 14:02:42 -0500 User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ipfw@freebsd.org, freebsd-current@freebsd.org, Alex Almeida , ben@wanderview.com Subject: Re: dummynet issues X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2009 19:14:50 -0000 Kevin Smith wrote: > Alex Almeida wrote: > >> Hi, >> >> The same happened with me, just by setting: >> net.inet.ip.fw.one_pass: 0 >> >> And stopped the message, however I was using version 6.4. >> >> I hope that helps you, >> >> Hugs >> >> Alex Almeida >> >> >> >> >> Kevin Smith escreveu: >> >>> Hi, >>> >>> I'm experiencing some dummynet issues after upgrading from 7-STABLE to >>> 8.0-RELEASE. >>> My /var/log/messages is full of these logs: >>> >>> Nov 29 15:34:18 stone kernel: dummynet: OUCH! pipe should have been idle! >>> Nov 29 15:34:49 stone last message repeated 409 times >>> Nov 29 15:36:49 stone last message repeated 1595 times >>> Nov 29 15:46:50 stone last message repeated 8162 times >>> Nov 29 15:56:51 stone last message repeated 7099 times >>> Nov 29 16:06:52 stone last message repeated 4771 times >>> Nov 29 16:16:53 stone last message repeated 3859 times >>> Nov 29 16:26:54 stone last message repeated 3493 times >>> Nov 29 16:36:55 stone last message repeated 5874 times >>> >>> Also I noticed that traffic shaping is not working any longer , i.e.: >>> actually outgoing pipes do not limit bandwidth at all. >>> Until 8 Release upgrading the same configuration was working perfectly. >>> >>> This is my uname -a >>> >>> FreeBSD stone.it 8.0-RELEASE FreeBSD 8.0-RELEASE #5: Sat Nov 28 20:22:30 >>> CET 2009 kevin@stone.it:/usr/obj/usr/src/sys/STONE i386 >>> >>> Attached my dmesg.boot and my kernel configuration. >>> >>> Is anybody experiencing same issues? >>> Thank you, >>> regards, >>> >>> -- >>> Kevin >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> freebsd-ipfw@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw >>> To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" >>> > Hi, > > I've already net.inet.ip.fw.one_pass set to 0, and also setting it to 1, > even if this is not what I need, does not fix. > Thank you anyway, > regards, > > -- > Kevin > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" > I know this may be a rediculous question, given the audience, however, I will inquire anyhow. "Have you verified that your kernel has installed cleanly?" I am still on 7.2-Stable, on my production servers, however, when I have attempted hasty upgrades, and reinstalled the kernel after compiling it on the new system, it required a second iteration of cleaning, and recompiling/installing for the kernel to recognize the net options that are being referenced. Hence, when I initially compiled and installed the kernel, I had to repeat the process a second time, to see all firewalling activated correctly.(pipes, and other rules) Of course, as previously indicated, this may be just a new bug for the newer system, however, I would try that first. Also, make sure you port the new version of your rules/config file to the 8-Release branch. I have had trouble going between 6 and 7 with some of these rules not being recognized but the option compiled. I can't remember what that was, for a good example, however, just a few things to investigate. I apologize if these options have already been investigated. Respectfully, Martes