Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Jul 2009 17:11:01 GMT
From:      Mark Rekai <mark@inetu.net>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   conf/136624: sysctl variables for ipnat are not applied on boot
Message-ID:  <200907091711.n69HB1bf086721@www.freebsd.org>
Resent-Message-ID: <200907091720.n69HK0XW027423@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         136624
>Category:       conf
>Synopsis:       sysctl variables for ipnat are not applied on boot
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 09 17:20:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Mark Rekai
>Release:        7.2-RELEASE-p2
>Organization:
>Environment:
FreeBSD xxx.yyy.zzz 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #13: Mon Jul  6 13:29:25 UTC 2009     root@xxx.yyy.zzz:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Changing certain ipf/ipnat kernel variables during boot results in a Device busy.

ipf/ipnat tunables must be made when ipf/ipnat are inactive.  Since /etc/rc.d/ipnat is processed before /etc/rc.d/sysctl, variables set in /etc/sysctl.conf for ipf/ipnat are not applied.

>How-To-Repeat:

>Fix:
Adding sysctl to the REQUIRE list in /etc/rc.d/ipnat appears to be a suitable fix/workaround.

>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907091711.n69HB1bf086721>