From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 03:12:34 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B0A316A4CF for ; Sun, 14 Dec 2003 03:12:34 -0800 (PST) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28D0D43D62 for ; Sun, 14 Dec 2003 03:11:45 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.3) with ESMTP id hBEBAm2e001030; Sun, 14 Dec 2003 03:10:48 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id hBEBAg5d001029; Sun, 14 Dec 2003 03:10:42 -0800 (PST) (envelope-from rizzo) Date: Sun, 14 Dec 2003 03:10:42 -0800 From: Luigi Rizzo To: Eugene Grosbein Message-ID: <20031214031042.A99005@xorpc.icir.org> References: <20031213101706.A79791@xorpc.icir.org> <20031214042812.GC2249@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20031214042812.GC2249@svzserv.kemerovo.su>; from eugen@www.svzserv.kemerovo.su on Sun, Dec 14, 2003 at 11:29:07AM +0700 cc: DrumFire cc: net@freebsd.org Subject: Re: how to saturate 100Mbit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 11:12:34 -0000 On Sun, Dec 14, 2003 at 11:29:07AM +0700, Eugene Grosbein wrote: > On Sat, Dec 13, 2003 at 10:17:06AM -0800, Luigi Rizzo wrote: > > > the fxp has a problem which does not allow it to go above 103/110/120kpps > > depending on which descriptor model you use, no matter how fast > > the CPU is. > > Can you explain the problem, please? Sorry if i sound a bit vague but did these tests a couple of years ago, and i do not have access to the fxp specs or contacts with people who designed the chip so i cannot say what is exactly the problem. The problem is in the hardware, not in the driver. Apparently the chip wastes a lot of time (couple of microseconds if i remember well) between reading the descriptor and then transmitting the data. This extra delay is in parallel with some other chip activity, so for larger frames (say 256 bytes) it is completely masked and packets are transmitted at the nominal rate, but smaller packet are sent as if the interframe gap were larger than the standard. At the time i did a lot of experiments to make sure that the NIC was not stalled by the cpu not supplying frames in time, etc., and all tests confirmed the above diagnosis. BTW it is not something that has to do with flow control frames, because enabling/disabling them does not change the throughput (and you can see the frames when they are not disabled). Changing the way descriptor are used (there are two different formats, one has something like the data right after the descriptor) helped increase the performance to 120kpps, whereas the standard freebsd driver is stuck at something between 103 and 110kpps. Not that it matters terribly, just useful to know when you have to push small frames at line rate and you find you can't with those cards. There are others (e.g. intel/dec 2114x, 3com's xl, possibly others, plus probably all of the gbit units when used at 100Mbit) which work fine at line rate with 64-byte frames. > > Even not using any special kernel modules, a simple loop over > > a sendto() on a udp socket can achieve around 500kpps on a 2.4GHz > > box (em or bge). With some tricks and a sufficiently fast PCI > > bus you can reach some 750kpps but then it really depends > > on how fast is your PCI bus. A > > 100*1024*1024/8/1500=8738.1(3) > > It seems one does not need hundred of thousand pps to achive 100Mbps. certainly not, but because most of the time the overhead is mostly per packet, if you want to run performance tests you care about packets, not data rate. cheers luigi From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 03:23:02 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94CE216A4CE for ; Sun, 14 Dec 2003 03:23:02 -0800 (PST) Received: from smtp003.mail.ukl.yahoo.com (smtp003.mail.ukl.yahoo.com [217.12.11.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 1992643D1D for ; Sun, 14 Dec 2003 03:23:01 -0800 (PST) (envelope-from NateBSD@yahoo.it) Received: from unknown (HELO LapBSD.MetalZone) (natebsd@80.182.192.142 with plain) by smtp003.mail.ukl.yahoo.com with SMTP; 14 Dec 2003 11:22:59 -0000 From: Nate Grey To: Maxim Konovalov Date: Sun, 14 Dec 2003 12:23:01 +0000 User-Agent: KMail/1.5.4 References: <200312131149.44582.NateBSD@yahoo.it> <20031213214424.E42015@news1.macomnet.ru> In-Reply-To: <20031213214424.E42015@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312141223.01385.NateBSD@yahoo.it> cc: net@FreeBSD.org Subject: Re: Fwd: 5.2-RC + ipfw X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 11:23:02 -0000 On Saturday 13 December 2003 18:47, Maxim Konovalov wrote: > Please try an enclosed patch or put a whitespace right after the '(' > before '\'. > > Index: ipfw2.c > =================================================================== > RCS file: /home/ncvs/src/sbin/ipfw/ipfw2.c,v > retrieving revision 1.42 > diff -u -r1.42 ipfw2.c > --- ipfw2.c 31 Oct 2003 18:31:55 -0000 1.42 > +++ ipfw2.c 13 Dec 2003 18:42:18 -0000 > @@ -2901,15 +2901,14 @@ > goto done; > > #define OR_START(target) \ > - if (ac && (*av[0] == '(' || *av[0] == '{')) { \ > + if (ac && ( \ > + !strncmp(*av, "(", strlen(*av)) || \ > + !strncmp(*av, "{", strlen(*av)) )) { \ > if (open_par) \ > errx(EX_USAGE, "nested \"(\" not allowed\n"); \ > prev = NULL; \ > open_par = 1; \ > - if ( (av[0])[1] == '\0') { \ > - ac--; av++; \ > - } else \ > - (*av)++; \ > + ac--; av++; \ > } \ > target: \ > > %%% Problem solved just adding a whitespace. Should I apply the patch anyway? From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 03:35:17 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5799B16A4CF for ; Sun, 14 Dec 2003 03:35:17 -0800 (PST) Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 877A543D35 for ; Sun, 14 Dec 2003 03:35:15 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (lumfglg7@news1.macomnet.ru [195.128.64.14]) by relay.macomnet.ru (8.12.10/8.12.10) with ESMTP id hBEBZDkQ27343624; Sun, 14 Dec 2003 14:35:13 +0300 (MSK) Date: Sun, 14 Dec 2003 14:35:13 +0300 (MSK) From: Maxim Konovalov To: Nate Grey In-Reply-To: <200312141223.01385.NateBSD@yahoo.it> Message-ID: <20031214143434.J94122@news1.macomnet.ru> References: <200312131149.44582.NateBSD@yahoo.it> <20031213214424.E42015@news1.macomnet.ru> <200312141223.01385.NateBSD@yahoo.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: net@FreeBSD.org Subject: Re: Fwd: 5.2-RC + ipfw X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 11:35:17 -0000 On Sun, 14 Dec 2003, 12:23-0000, Nate Grey wrote: > On Saturday 13 December 2003 18:47, Maxim Konovalov wrote: > > Please try an enclosed patch or put a whitespace right after the '(' > > before '\'. > > > > Index: ipfw2.c > > =================================================================== > > RCS file: /home/ncvs/src/sbin/ipfw/ipfw2.c,v > > retrieving revision 1.42 > > diff -u -r1.42 ipfw2.c > > --- ipfw2.c 31 Oct 2003 18:31:55 -0000 1.42 > > +++ ipfw2.c 13 Dec 2003 18:42:18 -0000 > > @@ -2901,15 +2901,14 @@ > > goto done; > > > > #define OR_START(target) \ > > - if (ac && (*av[0] == '(' || *av[0] == '{')) { \ > > + if (ac && ( \ > > + !strncmp(*av, "(", strlen(*av)) || \ > > + !strncmp(*av, "{", strlen(*av)) )) { \ > > if (open_par) \ > > errx(EX_USAGE, "nested \"(\" not allowed\n"); \ > > prev = NULL; \ > > open_par = 1; \ > > - if ( (av[0])[1] == '\0') { \ > > - ac--; av++; \ > > - } else \ > > - (*av)++; \ > > + ac--; av++; \ > > } \ > > target: \ > > > > %%% > > Problem solved just adding a whitespace. Should I apply the patch anyway? Please do if you can. Thanks. -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 11:40:49 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1FD316A4CE for ; Sun, 14 Dec 2003 11:40:49 -0800 (PST) Received: from smtpout.mac.com (A17-250-248-86.apple.com [17.250.248.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF3D643D32 for ; Sun, 14 Dec 2003 11:40:47 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id hBEJekcq006571; Sun, 14 Dec 2003 11:40:46 -0800 (PST) Received: from [192.168.1.6] (pool-68-161-96-170.ny325.east.verizon.net [68.161.96.170]) (authenticated bits=0)hBEJejA6014647; Sun, 14 Dec 2003 11:40:46 -0800 (PST) In-Reply-To: <20031213001913.GA40544@pit.databus.com> References: <200312120312.UAA10720@lariat.org> <20031212074519.GA23452@pit.databus.com> <6.0.0.22.2.20031212011133.047ae798@localhost> <20031212083522.GA24267@pit.databus.com> <6.0.0.22.2.20031212103142.04611738@localhost> <20031212181944.GA33245@pit.databus.com> <6.0.0.22.2.20031212161250.045e9408@localhost> <20031213001913.GA40544@pit.databus.com> Mime-Version: 1.0 (Apple Message framework v594) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <72143632-2E6D-11D8-824E-003065A20588@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Sun, 14 Dec 2003 14:41:00 -0500 To: Barney Wolff X-Mailer: Apple Mail (2.594) cc: net@freebsd.org Subject: Re: Controlling ports used by natd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 19:40:49 -0000 On Dec 12, 2003, at 7:19 PM, Barney Wolff wrote: > I have a real philosophical problem with ceding ports to worms, viruses > and trojans. Where will it stop? Portno is a finite resource. This is a respectable position, but the notion of categorizing ranges of ports into an association with a security policy already exists: bindresvport(). Perhaps one could argue that this limitation isn't that meaningful now that it's unfortunately common for malware to be running with root privileges-- or the Windows equivalent, more likely. Still, if you and your users don't run untrusted programs as root, system permissions will prevent malware from acting as a rogue DHCP/DNS/arp/routed/NMBD/whatever server, sniffing the local network, etc...all of which contributes to slowing down the opportunities for and rate at which a worm spreads. -- -Chuck From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 12:31:07 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11C9116A4CE for ; Sun, 14 Dec 2003 12:31:07 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD9E643D35 for ; Sun, 14 Dec 2003 12:31:01 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.10/8.12.10) with ESMTP id hBEKV1iC005757; Sun, 14 Dec 2003 15:31:01 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.10/8.12.10/Submit) id hBEKV1w1005756; Sun, 14 Dec 2003 15:31:01 -0500 (EST) (envelope-from barney) Date: Sun, 14 Dec 2003 15:31:01 -0500 From: Barney Wolff To: Charles Swiger Message-ID: <20031214203101.GA5552@pit.databus.com> References: <200312120312.UAA10720@lariat.org> <20031212074519.GA23452@pit.databus.com> <6.0.0.22.2.20031212011133.047ae798@localhost> <20031212083522.GA24267@pit.databus.com> <6.0.0.22.2.20031212103142.04611738@localhost> <20031212181944.GA33245@pit.databus.com> <6.0.0.22.2.20031212161250.045e9408@localhost> <20031213001913.GA40544@pit.databus.com> <72143632-2E6D-11D8-824E-003065A20588@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <72143632-2E6D-11D8-824E-003065A20588@mac.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.38 cc: net@freebsd.org Subject: Re: Controlling ports used by natd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 20:31:07 -0000 On Sun, Dec 14, 2003 at 02:41:00PM -0500, Charles Swiger wrote: > On Dec 12, 2003, at 7:19 PM, Barney Wolff wrote: > >I have a real philosophical problem with ceding ports to worms, viruses > >and trojans. Where will it stop? Portno is a finite resource. > > This is a respectable position, but the notion of categorizing ranges > of ports into an association with a security policy already exists: > bindresvport(). > > Perhaps one could argue that this limitation isn't that meaningful now > that it's unfortunately common for malware to be running with root > privileges-- or the Windows equivalent, more likely. Still, if you and > your users don't run untrusted programs as root, system permissions > will prevent malware from acting as a rogue > DHCP/DNS/arp/routed/NMBD/whatever server, sniffing the local network, > etc...all of which contributes to slowing down the opportunities for > and rate at which a worm spreads. The difference is who gets to decide that a port or port range is reserved. I'm happy to cede authority to the IANA, or other standards body. I'm not willing to cede it to malware writers. Regardless of philosophy, correctly configured stateful firewalls do not need to prevent ordinary programs from binding particular source port numbers to prevent access to and spread of worms. It's enough to block particular dest ports on requests.* Statefulness is required to tell a UDP request from a response. * Actually, a sensible firewall config allows only needed ports and blocks all others. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 15:45:22 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6661D16A4CE for ; Sun, 14 Dec 2003 15:45:22 -0800 (PST) Received: from overlord.e-gerbil.net (e-gerbil.net [69.31.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B1C243D36 for ; Sun, 14 Dec 2003 15:45:21 -0800 (PST) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (ras@localhost.e-gerbil.net [127.0.0.1]) by overlord.e-gerbil.net (8.12.9/8.12.9) with ESMTP id hBENjIjg020162; Sun, 14 Dec 2003 18:45:19 -0500 (EST) (envelope-from ras@overlord.e-gerbil.net) Received: (from ras@localhost) by overlord.e-gerbil.net (8.12.9/8.12.9/Submit) id hBENjITh020161; Sun, 14 Dec 2003 18:45:18 -0500 (EST) (envelope-from ras) Date: Sun, 14 Dec 2003 18:45:17 -0500 From: Richard A Steenbergen To: Eugene Grosbein Message-ID: <20031214234517.GY82121@overlord.e-gerbil.net> References: <20031213101706.A79791@xorpc.icir.org> <20031214042812.GC2249@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031214042812.GC2249@svzserv.kemerovo.su> User-Agent: Mutt/1.5.1i cc: Luigi Rizzo cc: DrumFire cc: net@freebsd.org Subject: Re: how to saturate 100Mbit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 23:45:22 -0000 On Sun, Dec 14, 2003 at 11:29:07AM +0700, Eugene Grosbein wrote: > > 100*1024*1024/8/1500=8738.1(3) SI in bits across a network is base 10, not 2 (1000 vs 1024). -- Richard A Steenbergen http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 21:50:57 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3140F16A4CE for ; Sun, 14 Dec 2003 21:50:57 -0800 (PST) Received: from swin.edu.au (c3p0.cc.swin.edu.au [136.186.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 558C743D3F for ; Sun, 14 Dec 2003 21:50:54 -0800 (PST) (envelope-from pvandenbergen@swin.edu.au) Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26]) by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id QAA704534; Mon, 15 Dec 2003 16:50:18 +1100 (EST) From: paul van den bergen To: "Willie Viljoen" , "Marco Molteni" , "Helge Oldach" Date: Mon, 15 Dec 2003 16:50:18 +1100 User-Agent: KMail/1.5 References: <200312120926.KAA06641@galaxy.hbg.de.ao-srv.com> <002e01c3c096$f5e57970$0a00a8c0@arista> In-Reply-To: <002e01c3c096$f5e57970$0a00a8c0@arista> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312151650.18243.pvandenbergen@swin.edu.au> cc: freebsd-net@freebsd.org Subject: Re: ssh tunnels and Xvnc - (yes, I know... What? not again!?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 05:50:57 -0000 On Fri, 12 Dec 2003 09:01 pm, Willie Viljoen wrote: > > >from home you double tunnel: > > >LOCALPORT=6333 > > >REMOTEPORT=5901 > > >ssh -t -L $LOCALPORT:localhost:12945 work1 \ > > > ssh -L 12945:localhost:$REMOTEPORT work2 > > > > As home is a W2k box, ssh won't probably work exactly like this... > > > > Putty supports a "don't allocate a pseudo-terminal" option to achieve > > the effect of ssh's "-t" option. (Required, otherwise work1 will bark.) > > PuTTY is problematic though. There is a way to get it to work exactly like > this. A Windows NT/2000/XP/2003 port of OpenSSH with an installer is at > http://lexa.mckenna.edu/ > > The port installs a small subset of Cygwin and uses it to provide full > OpenSSH functionality, so you can get SSH as it is on UNIX from the Windows > command prompt. > > Will Neat! thanks, now I have to try it out (which requires a few moments at home uninterupted... good luck to me!) And thanks to everyone who helped with this... I was getting majorly confused... -- Dr Paul van den Bergen Centre for Advanced Internet Architectures caia.swin.edu.au pvandenbergen@swin.edu.au IM:bulwynkl2002 "And some run up hill and down dale, knapping the chucky stones to pieces wi' hammers, like so many road makers run daft. They say it is to see how the world was made." Sir Walter Scott, St. Ronan's Well 1824 From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 21:56:47 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 951B916A4CE for ; Sun, 14 Dec 2003 21:56:47 -0800 (PST) Received: from swin.edu.au (c3p0.cc.swin.edu.au [136.186.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEBE243D32 for ; Sun, 14 Dec 2003 21:56:45 -0800 (PST) (envelope-from pvandenbergen@swin.edu.au) Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26]) by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id QAA705175 for ; Mon, 15 Dec 2003 16:56:44 +1100 (EST) From: paul van den bergen To: freebsd-net@freebsd.org Date: Mon, 15 Dec 2003 16:56:44 +1100 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312151656.44591.pvandenbergen@swin.edu.au> Subject: wireless monitoring of APs??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 05:56:47 -0000 All this talk of tcpdump, etc. has made me remember a question I thought of a while back and never got a decent answer on... What tools are there in BSD-land that are usefull for monitoring activity on an AP? i.e. like dstumbler but from the LAN side? well, alright, not like dstumbler as it has 1) and installed piece of hardware to use and 2) direct access to the device, where as an AP attatched to a boxen does not... but surely you see my point? it would be desirable to be able to display on a BSD box the same sort of information as dstumbler or other network managent tools for APs as it is for on-board wifi cards... I suspect the problem is that there is no information coming from the AP on the ethernet activity it sees on the wireless side being relayed to the wired side... and hence a agent would have to be running on the AP itself to allow such functionality... -- Dr Paul van den Bergen Centre for Advanced Internet Architectures caia.swin.edu.au pvandenbergen@swin.edu.au IM:bulwynkl2002 "And some run up hill and down dale, knapping the chucky stones to pieces wi' hammers, like so many road makers run daft. They say it is to see how the world was made." Sir Walter Scott, St. Ronan's Well 1824 From owner-freebsd-net@FreeBSD.ORG Sun Dec 14 22:03:29 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2942216A4CE for ; Sun, 14 Dec 2003 22:03:29 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1941643D33 for ; Sun, 14 Dec 2003 22:03:28 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1AVlpE-000JUM-B8; Sun, 14 Dec 2003 22:03:24 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 14 Dec 2003 22:03:23 -0800 To: paul van den bergen References: <200312151656.44591.pvandenbergen@swin.edu.au> Message-Id: cc: freebsd-net@freebsd.org Subject: Re: wireless monitoring of APs??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 06:03:29 -0000 most APs have snmp From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 03:15:34 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 358AF16A4CE for ; Mon, 15 Dec 2003 03:15:34 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63BD943D3F for ; Mon, 15 Dec 2003 03:15:32 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 773F6651FA; Mon, 15 Dec 2003 11:15:31 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26698-02-4; Mon, 15 Dec 2003 11:15:31 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 6E0AF651F4; Mon, 15 Dec 2003 11:15:30 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 6B3F6BD; Mon, 15 Dec 2003 11:15:29 +0000 (GMT) Date: Mon, 15 Dec 2003 11:15:29 +0000 From: Bruce M Simpson To: paul van den bergen Message-ID: <20031215111529.GB65986@saboteur.dek.spc.org> Mail-Followup-To: paul van den bergen , freebsd-net@freebsd.org References: <200312151656.44591.pvandenbergen@swin.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312151656.44591.pvandenbergen@swin.edu.au> cc: freebsd-net@freebsd.org Subject: Re: wireless monitoring of APs??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 11:15:34 -0000 On Mon, Dec 15, 2003 at 04:56:44PM +1100, paul van den bergen wrote: > What tools are there in BSD-land that are usefull for monitoring activity on > an AP? i.e. like dstumbler but from the LAN side? well, alright, not like > dstumbler as it has 1) and installed piece of hardware to use and 2) direct > access to the device, where as an AP attatched to a boxen does not... Depends on what you want to monitor. I'm sidetracked at the moment with some TCP work, so I haven't finished trafd+radiotap, but I am sure you'll find many useful SNMP MIBs out there for talking to an AP. BMS From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 05:28:29 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9A0516A4CE for ; Mon, 15 Dec 2003 05:28:29 -0800 (PST) Received: from midgard.ttsg.com (midgard.ttsg.com [216.231.105.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68DDE43D39 for ; Mon, 15 Dec 2003 05:28:28 -0800 (PST) (envelope-from hali@ttsg.com) Received: from midgard.ttsg.com (localhost [127.0.0.1]) by midgard.ttsg.com (8.12.10/8.12.9) with ESMTP id hBFDSRXR090536 for ; Mon, 15 Dec 2003 08:28:27 -0500 (EST) Received: from localhost (hali@localhost)hBFDSRUI090533 for ; Mon, 15 Dec 2003 08:28:27 -0500 (EST) Date: Mon, 15 Dec 2003 08:28:27 -0500 (EST) From: Hussain Ali To: freebsd-net@freebsd.org In-Reply-To: <200312121407.PAA10760@galaxy.hbg.de.ao-srv.com> Message-ID: <20031215081016.C23184-100000@midgard.ttsg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: grouping 2 or more interfaces as 1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 13:28:29 -0000 > In theory, yes. In practice, throughput is pretty often limited by PC > architectural issues. Consider, for example, PCI bus speed... Also > consider the overhead of actually distributing traffic between the > physical interfaces... > So i can get 200Mb/s out of 2 interfaces. (Theortically), this would be on the same Vlan with only one of the interfaces having an ip. Back to bridging for a moment. Can a bridge be setup in the same way? (googling mostly says no, bridging is commonly used with firewalls and not to the same switch) -Hussain From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 11:02:38 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B18FC16A4CE for ; Mon, 15 Dec 2003 11:02:38 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FD9A43D41 for ; Mon, 15 Dec 2003 11:02:25 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id hBFJ2PFR040460 for ; Mon, 15 Dec 2003 11:02:25 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBFJ2OxV040454 for freebsd-net@freebsd.org; Mon, 15 Dec 2003 11:02:24 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 15 Dec 2003 11:02:24 -0800 (PST) Message-Id: <200312151902.hBFJ2OxV040454@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 19:02:38 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2002/03/09] conf/35726 net Won't let me use ifconfig on the interfac 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/11/14] bin/22846 net Routed does not reflect preference of Int 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2002/05/04] kern/37761 net process exits but socket is still ESTABLI o [2003/07/11] kern/54383 net NFS root configurations without dynamic p 2 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 13:19:13 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE2B16A4CE for ; Mon, 15 Dec 2003 13:19:13 -0800 (PST) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (c-180-197-180.ka.dial.de.ignite.net [62.180.197.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id B703043D2D for ; Mon, 15 Dec 2003 13:18:31 -0800 (PST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk (NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk [2002:3eb4:c5b4:0:200:c0ff:fefc:19aa]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id hBFLI7c10917 verified NO) for ; Mon, 15 Dec 2003 22:18:09 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost)hBFLHrT06410; Mon, 15 Dec 2003 22:17:53 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Mon, 15 Dec 2003 22:17:53 +0100 (CET) Message-Id: <200312152117.hBFLHrT06410@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> X-Authentication-Warning: NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk: beer set sender to bounce@NOSPAM.dyndns.dk using -f From: Barry Bouwsma To: "%s" Subject: ENOBUFS and DNS... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 21:19:14 -0000 [Drop hostname part of IPv6-only address above to obtain IPv4-capable e-mail, or just drop me from the recipients and I'll catch up from the archives] Hello, "%s"! I've read in this list from a couple years ago, several discussions about ENOBUFS being returned to UDP-using applications. This is what I'm experiencing with BIND when I get hit with lots of queries over a slow link. I'm serving DNS info for my subdomain, with an off-site secondary. I'm on a dial-in now (no comments please); I don't ever remember seeing this with a cable modem connection (about 2-4x upstream speed than now, with downstream speed higher still). When I send a mail to the FreeBSD lists, shortly after, I get hit with lots of DNS queries to verify my address(es). My modem is saturated both down- and upstream for some minutes. For a minute or two, `named' spits out syslog messages about insufficient resources, as the replies it tries to make return ENOBUFS. If I were to tweak the sysctl net.inet.ip.intr_queue_maxlen from its default of 50 up, would that possibly help named? Or might that cause problems elsewhere? Or should I ignore this, or would the best possible solution be for me simply not to send any more mail to the lists? I can think of a few possibilties for this being made worse over my thin pipe. Comments about my thoughts below are welcome, to help me improve my understanding of things. I'm usually filling the downstream pipe even without the queries coming in (pay-per-minute so I'm trying to maximize use of pipe). This alone may worsen things, as incoming queries see a high latency, causing them to be repeated before a response is received, possibly causing other nameservers to initiate queries to me, resulting in many more queries coming in than if I returned answers promptly. The size of the outgoing responses is larger than the queries, so it takes more time to push out responses than it does for them to come in. These factors combined with the timeouts/retries that resolvers and nameservers have, mean that no matter what I do, things won't get a lot better for me. (As a note, when I sent mails over the cable modem, a different mailing list software was used by FreeBSD. Still, I'd see heaps of queries shortly after, just as now. This in the event the current software makes the deliveries faster at the same time, causing more simultaneous queries to me. Also, perhaps more sites are doing not only sender validation but also validation of the from address due to spam growth the last year.) I suspect that not all sites are able to successfuly query me, as after the initial couple minutes of ENOBUFS problems and as the incoming queries taper off, some time later I'll see a repeat of the ENOBUFS problem, as I'm assuming another round of attempts is made to dispose of the queue built up at freebsd.org. If I'm still online when that happens, to be queried, of course. I haven't looked to see whether BIND does anything special when an ENOBUFS pops up in order not to drop the response. Perhaps if it were to do so, queueing responses, things would only get worse as the backlog continues to increase, so by the time responses get sent, the requester has already given up (after sending a few more queries to increase the backlog further). Thus in such a case the better thing is to drop random responses in order to get fewer of them out in a more timely fashion. Or perhaps I shouldn't worry, trusting that the sites which fail to receive a response from me directly after a few tries might poke the offsite secondary nameserver, and that the error-recovery is handled by DNS, so I shouldn't do anything to UDP to try to help. Anyway, just for fun, I'm going to double the above sysctl value for this message and see how things change. Later I'll think about suspending my downloads to speed up incoming queries. Also, I just remembered that userland ppp allows me to prioritize certain traffic so I should try that too, though normally the downloads I do only snarf a few hundred bytes/sec from the outgoing pipe, so that might help little.... As noted, comments about my ideas are welcome. Thanks, Barry Bouwsma From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 13:43:12 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 864B316A4CE for ; Mon, 15 Dec 2003 13:43:12 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B4043D36 for ; Mon, 15 Dec 2003 13:43:10 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost.nic.fr [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id hBFLgxDa089517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Mon, 15 Dec 2003 16:42:59 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id hBFLgxR4089514; Mon, 15 Dec 2003 16:42:59 -0500 (EST) (envelope-from wollman) Date: Mon, 15 Dec 2003 16:42:59 -0500 (EST) From: Garrett Wollman Message-Id: <200312152142.hBFLgxR4089514@khavrinen.lcs.mit.edu> To: Barry Bouwsma In-Reply-To: <200312152117.hBFLHrT06410@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> References: <200312152117.hBFLHrT06410@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> X-Spam-Score: -19.5 () IN_REP_TO,MAILTO_TO_REMOVE,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 cc: %s Subject: ENOBUFS and DNS... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 21:43:12 -0000 < said: > If I were to tweak the sysctl net.inet.ip.intr_queue_maxlen from its > default of 50 up, would that possibly help named? No, it will not have any effect on your problem. The IP input queue is only on receive, and your problem is on transmit. The only thing that could possibly help your problem is increasing your output queue length, and it is already quite substantial; doing this will probably hurt as much as it helps, since the output queue is serviced in strict FIFO order and there is no way to ``call back'' a packet once it makes it there. Something like ALTQ might help if you are able to use a WFQ discipline and assign a high weight to DNS traffic. -GAWollman From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 17:01:59 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 730D716A4CE for ; Mon, 15 Dec 2003 17:01:59 -0800 (PST) Received: from mx.force10networks.com (corp.force10networks.com [206.54.51.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 620EA43D36 for ; Mon, 15 Dec 2003 17:01:56 -0800 (PST) (envelope-from satyam@force10networks.com) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 15 Dec 2003 15:01:59 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IP checksum question Thread-Index: AcPDX3GSJZa2CtZ9Qqmc82DCFxpmqg== From: "Satyam Kurapati" To: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: IP checksum question X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2003 01:01:59 -0000 Hi, What is the reason for zeroing out the IP checksum in IP input packet processing, after validating ? If I leave it as it is, will there be any problems in the upper layers or in the IP forward paths ? Thanks in advance! /Satyam Satyam Kurapati Force10 Networks Inc. From owner-freebsd-net@FreeBSD.ORG Mon Dec 15 21:00:15 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D91D016A4CE for ; Mon, 15 Dec 2003 21:00:15 -0800 (PST) Received: from web42004.mail.yahoo.com (web42004.mail.yahoo.com [66.218.93.172]) by mx1.FreeBSD.org (Postfix) with SMTP id A0E8243D39 for ; Mon, 15 Dec 2003 21:00:13 -0800 (PST) (envelope-from darrylb_au44@yahoo.com.au) Message-ID: <20031216050013.92333.qmail@web42004.mail.yahoo.com> Received: from [203.26.24.218] by web42004.mail.yahoo.com via HTTP; Tue, 16 Dec 2003 16:00:13 EST Date: Tue, 16 Dec 2003 16:00:13 +1100 (EST) From: =?iso-8859-1?q?Darryl=20Barlow?= To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Wireless Problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2003 05:00:16 -0000 I have installed FreeBSD on a Desktop Machine with a TI 1410 PCI Cardbus Bridge and an Avaya Silver Wireless Network Card. The card connects perfectly to a D-Link Access Point in Debian and even in Windows XP. However, in FreeBSD there is "no carrier" no matter what I seem to try. Troubleshooting help would be much appreciated. Device seems to come up with: ifconfig wi0 inet 192.168.4.8 netmask 255.255.255.0 ssid HOME wepmode ON wepkey 1234567890 dmesg is as follows: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc06d4000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06d421c. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1199664705 Hz CPU: AMD Athlon(tm) Processor (1199.66-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000 real memory = 134135808 (127 MB) avail memory = 122912768 (117 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe6000000-0xe7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 9 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 9.0 (no driver attached) cbb0: at device 10.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: slot 10 INTA is routed to irq 5 rl0: port 0xa400-0xa4ff mem 0xd5000000-0xd50000ff at device 11.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode pcib0: slot 11 INTA is routed to irq 10 rl0: Ethernet address: 00:50:bf:27:7b:64 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 12.0 (no driver attached) sym0: <810a> port 0x9800-0x98ff mem 0xd4800000-0xd48000ff irq 9 at device 13.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using LOAD/STORE-based firmware. atapci1: port 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 mem 0xd4000000-0xd401ffff irq 10 at device 17.0 on pci0 ata2: at 0x9400 on atapci1 ata3: at 0x8800 on atapci1 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 orm0: