From owner-freebsd-bugs@FreeBSD.ORG Tue Jun 24 14:45:19 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 82C822E5 for ; Tue, 24 Jun 2014 14:45:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5033221BA for ; Tue, 24 Jun 2014 14:45:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5OEjJHb048506 for ; Tue, 24 Jun 2014 15:45:19 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 191343] New: ipnat error at boot disables active sessions Date: Tue, 24 Jun 2014 14:45:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: David.Boyd49@twc.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 14:45:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191343 Bug ID: 191343 Summary: ipnat error at boot disables active sessions Product: Base System Version: 10.0-STABLE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: David.Boyd49@twc.com Customer upgraded 2 test systems to release/10.0.0 and then to releng/10.0 (10.0-RELEASE-p5). With same ipnat configuration as used in 9.2-RELEASE, ipnat didn't create active sessions. Customer then rebooted system and ipnat functionality returned. A subsequent reboot disabled ipnat again. Customer reported this problem to me. Skeptically, I agreed to visit site. The console log for the failing ipnat reports an error at boot: IP Filter: v5.1.2 initialized, default = pass all, logging = enabled Enabling ipfilter Installing NAT rules. 0 entries flushed from NAT table 0 entries flushed from NAT list in=0x801406600:SIOCSTPUT:no such process Now the weird part: On reboot (shutdown -r now) the SIOCSTPUT error is not reported and ipnat works. On reboot (shutdown -r now) the SIOCSTPUT error returns and ipnat fails. After a hard reset or power off/power on the SIOCSTPUT error "always" returns and ipnat fails (20+ attempts) and then the every other reboot cycle begins again (50+ attempts). Hardware is Supermicro PDSME+ motherboard with quad-core Intel Xeon (2.66 Ghz) and 4 GB memory I have verified the kernel configuration is simply include GENERIC ident SUPERMICRO I rebuilt customer's system with stable/10 as of 06/20/2014 ... no change. I have /etc/ipf.rules, /etc/ipnat.rules, /etc/rc.conf, kernel config files in my possession. I also have acquired one of the test machines so patching, rebuilding and testing are possible. -- You are receiving this mail because: You are the assignee for the bug.