Date: Thu, 27 Jun 2002 14:04:15 -0700 (PDT) From: Chris Wasser <cwasser@shaw.ca> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/39937: ipstealth issue Message-ID: <200206272104.g5RL4Fkk040004@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 39937 >Category: kern >Synopsis: ipstealth issue >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 27 14:10:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Chris Wasser >Release: 4.6-RELEASE >Organization: n/a >Environment: FreeBSD hanger18 4.6-RELEASE FreeBSD 4.6-RELEASE #2: Mon Jun 24 15:07:45 MDT 2002 root@hanger18:/usr/obj/usr/src/sys/UKCV1_PRODUCTION i386 >Description: If IPSTEALTH is enabled in the kernel (options IPSTEALTH) and the sysctl is set to 1, any attempts to use a bpf driven application such as dhclient will result in the machine locking up. I've tried tracing the lockup but it just spins around and around and I can't get a decent trace to give as it keeps cycling in the same functions over and over. >How-To-Repeat: In your kernel, enable ipstealth: options IPSTEALTH Tweak the sysctl option: sysctl net.inet.ip.stealth=1 Run dhclient on any interface: dhclient dc0 >Fix: Unsure. It may just be my own stupidity, but this definitely did not happen in 4.5-* >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206272104.g5RL4Fkk040004>