Re: kern/162739: [ipfw] ipfw_nat redirect_addr option no longer works (as expected?)

Old Synopsis: ipfw+nat redirect_addr option no longer works (as expected?) New Synopsis: [ipfw] ipfw_nat redirect_addr option no longer works (as expected?) Responsible-Changed-From-To: freebsd-bugs->freebsd-ipfw Responsible-Changed-By: ae Responsible-Changed-When: Tue Nov 22 05:10:40 UTC 2011 Re

Re: conf/30399: [bsd.cpu.mk] [patch] Have Fortran use the CPUTYPE variable

Synopsis: [bsd.cpu.mk] [patch] Have Fortran use the CPUTYPE variable State-Changed-From-To: open->feedback State-Changed-By: arundel State-Changed-When: Mon Nov 21 23:24:45 UTC 2011 State-Changed-Why: I suggest we close this problem report. Fortran now is simply *some* programming language in por

Re: bin/114082: [make.conf] [patch] default CFLAGS have a blank at the end

Synopsis: [make.conf] [patch] default CFLAGS have a blank at the end Responsible-Changed-From-To: freebsd-bugs->arundel Responsible-Changed-By: arundel Responsible-Changed-When: Mon Nov 21 23:20:52 UTC 2011 Responsible-Changed-Why: Assign to me. Although i don't have commit rights to src, i'm wor

Re: bin/78529: df(1) shows wrong info about hard drive after carrying hard drive from one PC to other.

Synopsis: df(1) shows wrong info about hard drive after carrying hard drive from one PC to other. State-Changed-From-To: open->closed State-Changed-By: arundel State-Changed-When: Mon Nov 21 22:29:24 UTC 2011 State-Changed-Why: It appears this issue was caused by changes between 5.3-STABLE and 5

kern/162741: [PATCH] vm_kmem_size miscalculated due to int type overflow sometimes

>Number: 162741 >Category: kern >Synopsis: [PATCH] vm_kmem_size miscalculated due to int type overflow >sometimes >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Dat

misc/162739: ipfw+nat redirect_addr option no longer works (as expected?)

>Number: 162739 >Category: misc >Synopsis: ipfw+nat redirect_addr option no longer works (as expected?) >Confidential: no >Severity: serious >Priority: high >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Cl

kern/162736: r214955 (nanobsd) broke build with whitespace in KERNCONFDIR

>Number: 162736 >Category: kern >Synopsis: r214955 (nanobsd) broke build with whitespace in KERNCONFDIR >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required:

misc/162724: make whereobj doesn't work after make buildenv

>Number: 162724 >Category: misc >Synopsis: make whereobj doesn't work after make buildenv >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

Openbgpd incorrectly sets TCP_MD5 on the listen socket, regardless of configuration

Sorry for the brief report and the scarce details. The fing form insists on rejecting the captcha after one hour writing a report. So, in short: If TCP_MD5 is available on the system, options IPSEC options TCP_SIGNATURE #include support for RFC 2385 device