misc/148137: call order of natd and ipfw startup scripts

Vitezslav Novy vnovy at vnovy.net
Fri Jun 25 10:30:03 UTC 2010


>Number:         148137
>Category:       misc
>Synopsis:       call order of natd and ipfw startup scripts
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 25 10:30:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Vitezslav Novy
>Release:        8.1-PRERELEASE
>Organization:
>Environment:
FreeBSD vn.chello.upc.cz 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #2: Thu Jun 24 10:46:33 CEST 2010     rumik at vn.chello.upc.cz:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
>From 8.0-RELEASE ipfw startup script doesn't call natd startup script. Also there is no information about call order of ipfw a natd startup script. On my system ipfw is called before natd. If ipdivert module is not loaded using loader.conf, natd loads it, but ipfw running before fail to install divert rules. 
>How-To-Repeat:
Configure "open" type ipfw with userland natd and do not configure loading of ipdivert in loader.conf. Use GENERIC kernel (without ipfw compiled in).  After reboot divert rules are not installed.
>Fix:
Define right order (natd, ipfw) of startup scripts
or
load ipdivert module in ipfw startup script if natd_enable="YES"


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


More information about the freebsd-bugs mailing list