From owner-freebsd-questions@FreeBSD.ORG Sat Jul 9 15:04:49 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEC7C16A41F for ; Sat, 9 Jul 2005 15:04:49 +0000 (GMT) (envelope-from ymr8-cg@lycos.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B07143D46 for ; Sat, 9 Jul 2005 15:04:49 +0000 (GMT) (envelope-from ymr8-cg@lycos.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id BBDC018001BF for ; Sat, 9 Jul 2005 15:04:48 +0000 (GMT) X-OB-Received: from unknown (208.36.123.33) by wfilter.us4.outblaze.com; 9 Jul 2005 15:04:48 -0000 Received: by ws7-4.us4.outblaze.com (Postfix, from userid 1001) id AE276CA07F; Sat, 9 Jul 2005 15:04:48 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain MIME-Version: 1.0 Received: from [68.18.77.159] by ws7-4.us4.outblaze.com with http for ymr8-cg@lycos.com; Sat, 09 Jul 2005 10:04:48 -0500 From: "Ab Normal" To: freebsd-questions@freebsd.org Date: Sat, 09 Jul 2005 10:04:48 -0500 X-Originating-Ip: 68.18.77.159 X-Originating-Server: ws7-4.us4.outblaze.com Message-Id: <20050709150448.AE276CA07F@ws7-4.us4.outblaze.com> Subject: 6.0-SNAP005: pptpclient; mpd/ng; pf; tcpdrop; vidcontrol/saver; gbde/md X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2005 15:04:49 -0000 I've installed FreeBSD 6.0-CURRENT-SNAP005 (i386) on my stand-alone home computer, which connects to the internet via adsl. Being no expert, I don't presume to characterize the following observations as "bugs" (except, perhaps, with regard to tcpdrop), but I wonder if anyone else has experienced any of the same things. 1. In the past, using FreeBSD 4.9 and 4.10, I connected to my dsl modem/router using pptpclient. With pptpclient on 6.0, however, I noticed that download speed from the internet was very slow -- only about 20 percent of the rate I was accustomed to. A check with top revealed that pptp was utilizing 85 percent of the CPU. I recall seeing a lock-order-reversal message on a couple of occasions. (See the log excerpt below.) 2. I installed mpd to replace pptpclient. Downloading is fast again and CPU usage is back to normal, but I notice a couple of minor quirks.=20 The first time after boot that I run my script to bring up the NIC (I don't bring up the NIC on boot) and to launch mpd, no connection occurs. On the second try it works, but I get the following message on standard error: "WARNING: attempt to net_add_domain(netgraph) after domainfinalize()." The warning is not repeated on subsequent connects.=20 I assume it is related to the loading of various ng modules. 3. I'm using pf with 6.0. When I kill (-SIGTERM) mpd to disconnect from the internet, and before I bring down the NIC, the following error message is returned: "pf_test6: kif =3D=3D NULL, if_xname ng0." It appears that pf is bothered by the disappearance of the ng0 interface. 4. After disconnecting from the internet I often have "stuck" tcp4 connections (perhaps due in part to my severe firewall rules). Thinking to remedy this little annoyance with tcpdrop. I created a perl script to parse the output of "netstat -n - f inet" and to call tcpdrop for each inet connection except the NIC-to-modem connection. I've tried running the script before and (mostly) after killing mpd. Sometimes it actually works, but most times tcpdrop triggers a kernel panic and auto reboot. I suspect that the differing results might be related to the state of the connection(s), or to the number of them. Maybe it's safe to dub this phenomenon a "bug" in view of the panic and reboot, even if I'm doing something wrong. 5. I do a lot of work (or at least activity) from the console, and enjoy the new VESA graphics console features. I compiled VESA and SC_PIXEL_MODE into the kernel, and it works fine with my Radeon 7000 card -- except that the screen blanker does not blank the screen. The cursor disappears, but otherwise the display persists. I suppose this may be a necessary consequence of using graphics mode.=20 6. Having used the vnconfig utility and the vncrypt port in FreeBSD 4.x to create file-backed encrypted devices, I applied an analogous procedure using mdconfig and gbde in 6.0. Although it works, processing of the encrypted file system seems quite sluggish with gbde compared to vncrypt. (I do realize that encryption entails overhead, and that gbde seems designed primarily for use with disks rather than files.) By the way, informationally, the recent zlib patch for FreeBSD 5.x would appear to work on 6.0. I actually did the one-line edit to inftrees.c manually rather than running patch, but it was the same line with the same line number employed by the patch. I also ran find-zlib, which indicates that zlib 1.2.2 is statically linked in a few system files -- eg., libstand.a, pxeboot, and loader (shouldn't do much harm there!).=20 It's also statically linked, I think, in Opera 8.01, which could be dangerous. Log excerpt: one of the LORs with pptpclient -- Jul 3 23:32:55 localhost pptp[709]: anon log[ctrlp_disp:pptp_ctrl.c:880]: Outgoing call established (call ID 0, peer's call ID=20 0). Jul 3 23:32:58 localhost kernel: lock order reversal Jul 3 23:32:58 localhost kernel: 1st 0xc1b34270 rtentry (rtentry) @ /usr/src/sys/net/rtsock.c:434 Jul 3 23:32:58 localhost kernel: 2nd 0xc19ba77c radix node head (radix node head) @ /usr/src/sys/net/route.c:148 Jul 3 23:32:58 localhost kernel: KDB: stack backtrace: Jul 3 23:32:58 localhost kernel: kdb_backtrace(0,ffffffff,c09293f0,c0929418,c08b3b64) at kdb_backtrace+0x29 Jul 3 23:32:58 localhost kernel: witness_checkorder(c19ba77c,9,c085a11c,94) at witness_checkorder+0x564 Jul 3 23:32:58 localhost kernel: _mtx_lock_flags(c19ba77c,0,c085a11c,94,7) at _mtx_lock_flags+0x5b Jul 3 23:32:58 localhost kernel: rtalloc1(c1d39c78,0,0,d745ab3c,0) at rtalloc1+0x61 Jul 3 23:32:58 localhost kernel: ifa_ifwithroute(801,c1d39c5c,c1d39c78,c1b34270,c19ba700) at ifa_ifwithroute+0x68 Jul 3 23:32:58 localhost kernel: rt_getifa(d745ab3c,0,c1b34210,c1d39c00,c091f680) at rt_getifa+0xa6 Jul 3 23:32:58 localhost kernel: route_output(c1a39400,c1b316f4,a0,c1a39400,1f60) at route_output+0x5c5 Jul 3 23:32:58 localhost kernel: raw_usend(c1b316f4,0,c1a39400,0,0,c1a47300) at raw_usend+0x60 Jul 3 23:32:58 localhost kernel: rts_send(c1b316f4,0,c1a39400,0,0) at rts_send+0x1b Jul 3 23:32:58 localhost kernel: sosend(c1b316f4,0,d745ac78,c1a39400,0) at sosend+0x5e3 Jul 3 23:32:58 localhost kernel: soo_write(c1a78240,d745ac78,c1b57a00,0,c1a47300) at soo_write+0x46 Jul 3 23:32:58 localhost kernel: dofilewrite(c1a47300,c1a78240,1,bfbfddb0,a0) at dofilewrite+0xa8 Jul 3 23:32:58 localhost kernel: write(c1a47300,d745ad04,3,1f,202) at write+0x39 Jul 3 23:32:58 localhost kernel: syscall(3b,3b,3b,bfbfddb0,a0) at syscall+0x22f Jul 3 23:32:58 localhost kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Jul 3 23:32:58 localhost kernel: --- syscall (4, FreeBSD ELF32, write), eip =3D 0x28253627, esp =3D 0xbfbfdd6c, ebp =3D 0xbfbfdd98 -- - Jul 3 23:32:58 localhost ppp[706]: tun0: Warning: ff02:4::/32: Change route failed: errno: Network is unreachable Jul 3 23:33:24 localhost pptp[710]: anon log[decaps_gre:pptp_gre.c:404]: accepting packet 88 (expecting 87, lost or reordered) -- A Happy User :) . --=20 _______________________________________________ NEW! Lycos Dating Search. The only place to search multiple dating sites at= once. http://datingsearch.lycos.com