From owner-freebsd-net Sun Jul 2 14:34: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from odysseus.gedankenpolizei.de (p3E9BAAB9.dip.t-dialin.net [62.155.170.185]) by hub.freebsd.org (Postfix) with ESMTP id 088C637B61F for ; Sun, 2 Jul 2000 14:34:03 -0700 (PDT) (envelope-from karsten@gedankenpolizei.de) Received: (from karsten@localhost) by odysseus.gedankenpolizei.de (8.9.3/8.9.3) id XAA00920 for freebsd-net@freebsd.org; Sun, 2 Jul 2000 23:35:53 +0200 (CEST) (envelope-from karsten) From: Karsten Patzwaldt Date: Sun, 2 Jul 2000 23:35:53 +0200 To: freebsd-net@freebsd.org Subject: NAT and PPPoE Message-ID: <20000702233552.A862@odysseus.gedankenpolizei.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there! OK, I finally got a DSL connection, and I set up a FreeBSD-router as a router, using NAT to give access to the Internet for my whole network. That works so far, I can connect via SSH, POP3 and so on. But FTP and HTTP make problems. Those two protocols can be used from the router without any problems, but the other computers on the LAN time out when trying to connect to any server. They _are_ able to connect to to the webservers of my provider (the german T-Online), but I don't reach any other servers. OK, there might be a proxy enforcement at T-Online, but this would not explain why I can connect to FTP- and HTTP-servers from the router without any problems. I tried to use the -nat option of PPP and natd, both with the same result. I set up a proxy for HTTP and FTP which both work, but this is not what I want. There are 2 other things that struck me. First, HTTP works with other ports than 80. There's a server at port 70 which worked just fine. Second, I can use a proxy server at T-Online and use this to go online. But looking at the router, there must be a possibility to use the computers behind the NAT-router without a proxy server because the router doesn't need a proxy, so why should the others need one? If you've got any ideas or need some more information on my configuration, please contact me directly, as my overall mail volume doesn't allow me to follow -net. Thank you. -- Karsten -- perl -e 'use Math::BigInt;$a=new Math::BigInt 1;print"Zahl: ";$b=<>;$a*= $b--while$b;print"Ergebnis: $a, Stellen: ".(length($a)-1)."\n"' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 2 17:10:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns3.khmere.com (d83b56af.dsl.flashcom.net [216.59.86.175]) by hub.freebsd.org (Postfix) with ESMTP id 17A1A37B7BF; Sun, 2 Jul 2000 17:10:30 -0700 (PDT) (envelope-from nathan@khmere.com) Received: from khmere.com (ns2.khmere.com [216.59.86.176]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id RAA35602; Sun, 2 Jul 2000 17:13:31 -0700 (PDT) Message-ID: <395FD9F1.84B67DE9@khmere.com> Date: Sun, 02 Jul 2000 17:10:26 -0700 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i586) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" , "hackers@FreeBSD.ORG" Subject: Re: loader ??? Awwww... come on someone must know !!! References: <395D7D2B.48B90842@khmere.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org nathan@khmere.com wrote: > I have FreeBSD 4.0-RELEASE (on i386) > > What I am trying to do is nfs root boot from the loader (?) > I do: > > ok> unload kernel > ok> load diskless_kernel > ok> set kernel=diskless_kernel > ok> boot -r -h > > Now what I understand is the -r flag will tell the kernel to overide the > rootdev and use the "staticly linked device" from when you made the > kernel ? > > Now my kernel (the diskless_kernel ) is a diskless kernel ( with BOOTP, > NFS_ROOT .... etc.. ) compiled in. > But when I boot like this is just tries to mount /dev/ad0s1a ... (normal > device ) even though it gets the proper reply from the bootp server that > its rootfs= it even prints : > > rootfs is > Mounting root from ufs:/dev/ad0s1a > > but still mounts the ufs ! > > How do if force it to boot root fs on nfs ? > > I have tried to do a boot -a then when I prompts me for root fs I enter > the proper nfs mount and it is cool ...... but I need it to do it with > out promting... > > I have tried to : > > ok> set rootdev=nfs: > ok> boot -h > ok> can't determine root device > > I have also passed it kernel flags ? (mybe wrong ones ... ? ) > > Now I have looked at the /usr/src/sys/boot/i386/libi386/bootinfo.c and > I see where it checks the roodev to see if it is proper ..... > but I cannot determine what type of device I can name so that this will > not die on me ??? > set rootdev=??? > > how do I have the kernel to load the nfs root instead of use the currdev > ? > > What does etherboot do when it loads the kernel ? does it pass it > special parameters ?? > > If you are wondering why I just don't boot from etherboot ....etc...(I > do ) but... I want to be able to boot my remote systems without a > floppie and chose how to boot from loader (via serail console ...I don't > have serial access for the bios but I can get serial console with > FreeBSD !! ). Either default (use local drive) or load the diskless > kernel , then boot diskless. > This way I almost the same options ..... and maybe automate it... > > Any help would be great !! > > thank you kindly.... > > nathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 2 23:46:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from modemcable127.61-201-24.mtl.mc.videotron.net (modemcable079.102-200-24.mtl.mc.videotron.net [24.200.102.79]) by hub.freebsd.org (Postfix) with SMTP id B8FC337B5B8 for ; Sun, 2 Jul 2000 23:46:20 -0700 (PDT) (envelope-from patrick@mindstep.com) Received: (qmail 84135 invoked from network); 3 Jul 2000 06:46:19 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 3 Jul 2000 06:46:19 -0000 Message-ID: <051c01bfe4ba$466aaf30$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Karsten Patzwaldt" Cc: References: <20000702233552.A862@odysseus.gedankenpolizei.de> Subject: Re: NAT and PPPoE Date: Mon, 3 Jul 2000 02:45:28 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > OK, I finally got a DSL connection, and I set up a FreeBSD-router as a > router, using NAT to give access to the Internet for my whole network. > That works so far, I can connect via SSH, POP3 and so on. But FTP and > HTTP make problems. Those two protocols can be used from the router > without any problems, but the other computers on the LAN time out when > trying to connect to any server. They _are_ able to connect to to the > webservers of my provider (the german T-Online), but I don't reach any > other servers. This sounds very much like the problem many people are having with PPPoE setups and Path MTU Discovery not functioning properly on remote web servers. The only thing you can do is reduce the configure MTU on the CLIENT machines on the LAN to something like 1400 bytes. Also, this problem has been discussed on this list quite extensively a couple of weeks ago. There is a small daemon to run on your FreeBSD gateway that will go around the problem. Look for threads called '"frag-anyways" knob' and '[CFV] where to put the TCP MSS correction code'. The daemon is called "tcpmssd" and works like natd. Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 0:51:53 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 0DD2537B80A for ; Mon, 3 Jul 2000 00:51:45 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id KAA75097; Mon, 3 Jul 2000 10:50:40 +0300 (EEST) Date: Mon, 3 Jul 2000 10:50:40 +0300 From: Ruslan Ermilov To: Karsten Patzwaldt Cc: net@FreeBSD.org Subject: Re: NAT and PPPoE Message-ID: <20000703105040.C73016@sunbay.com> Mail-Followup-To: Karsten Patzwaldt , net@FreeBSD.org References: <20000702233552.A862@odysseus.gedankenpolizei.de> <051c01bfe4ba$466aaf30$040aa8c0@local.mindstep.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <051c01bfe4ba$466aaf30$040aa8c0@local.mindstep.com>; from patrick@mindstep.com on Mon, Jul 03, 2000 at 02:45:28AM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 03, 2000 at 02:45:28AM -0400, Patrick Bihan-Faou wrote: > Hi, > > > OK, I finally got a DSL connection, and I set up a FreeBSD-router as a > > router, using NAT to give access to the Internet for my whole network. > > That works so far, I can connect via SSH, POP3 and so on. But FTP and > > HTTP make problems. Those two protocols can be used from the router > > without any problems, but the other computers on the LAN time out when > > trying to connect to any server. They _are_ able to connect to to the > > webservers of my provider (the german T-Online), but I don't reach any > > other servers. > > This sounds very much like the problem many people are having with PPPoE > setups and Path MTU Discovery not functioning properly on remote web > servers. > > The only thing you can do is reduce the configure MTU on the CLIENT machines > on the LAN to something like 1400 bytes. > > Also, this problem has been discussed on this list quite extensively a > couple of weeks ago. There is a small daemon to run on your FreeBSD gateway > that will go around the problem. > > Look for threads called '"frag-anyways" knob' and '[CFV] where to put the > TCP MSS correction code'. The daemon is called "tcpmssd" and works like > natd. > ... and is available from http://people.FreeBSD.org/~ru/tcpmssd.tgz -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 6:57:57 2000 Delivered-To: freebsd-net@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id B85C037B5B7; Mon, 3 Jul 2000 06:57:52 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id OAA11339; Mon, 3 Jul 2000 14:57:33 +0100 (BST) (envelope-from nik) Date: Mon, 3 Jul 2000 14:57:33 +0100 From: Nik Clayton To: Jeroen Ruigrok/Asmodai Cc: Nik Clayton , net@freebsd.org Subject: Re: No route for 127/8 to lo0 Message-ID: <20000703145733.A3949@catkin.nothing-going-on.org> References: <20000620201733.A665@kilt.nothing-going-on.org> <20000701203929.E26119@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000701203929.E26119@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sat, Jul 01, 2000 at 08:39:29PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 01, 2000 at 08:39:29PM +0200, Jeroen Ruigrok/Asmodai wrote: > -On [20000621 19:58], Nik Clayton (nik@freebsd.org) wrote: > >Why don't we automatically include a network route for 127/8 to lo0? > > > >I first noticed this when I saw Samba repeatedly triggering a PPP > >dialup. > > > >It turns out Samba is sending occasional broadcasts to 127.255.255.255. > >There's no route for that address on a 3.4/4.x system, so the packets > >end up going out of the default route. This is bad for PPP systems (or > >other systems that pay for outgoing traffic in some way). > > Funny. > > I just tried it myself here, but it doesn't cause any dial up sessions > to be established on this CURRENT box. What's your default route set to? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 10:42:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id E318137B9BD; Mon, 3 Jul 2000 10:42:43 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (lucifer.is.an.elder.of.the.ninth-circle.org [195.38.216.226]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id e63HgHc22692; Mon, 3 Jul 2000 19:42:17 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id TAA49379; Mon, 3 Jul 2000 19:42:16 +0200 (CEST) (envelope-from asmodai) Date: Mon, 3 Jul 2000 19:42:16 +0200 From: Jeroen Ruigrok/Asmodai To: Nik Clayton Cc: net@freebsd.org Subject: Re: No route for 127/8 to lo0 Message-ID: <20000703194216.G35215@daemon.ninth-circle.org> References: <20000620201733.A665@kilt.nothing-going-on.org> <20000701203929.E26119@daemon.ninth-circle.org> <20000703145733.A3949@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000703145733.A3949@catkin.nothing-going-on.org>; from nik@freebsd.org on Mon, Jul 03, 2000 at 02:57:33PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20000703 19:34], Nik Clayton (nik@freebsd.org) wrote: > >What's your default route set to? To my ISDN router which does my dialing up. And that one has a default route to my ISDN circuit. No other routes present for so far I can see. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project I could shed anoter million tears, a million breaths, a million names but only one Truth to face... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 19:29:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from alpha.simphost.com (alpha.simphost.com [216.84.199.194]) by hub.freebsd.org (Postfix) with ESMTP id 6772F37C2F4; Mon, 3 Jul 2000 19:29:22 -0700 (PDT) (envelope-from jlschwab@simphost.com) Received: by alpha.simphost.com (Postfix, from userid 1000) id D4ECF3071D; Mon, 3 Jul 2000 20:29:05 -0600 (MDT) Received: from localhost (localhost [127.0.0.1]) by alpha.simphost.com (Postfix) with ESMTP id CD68C2C90E; Mon, 3 Jul 2000 20:29:05 -0600 (MDT) Date: Mon, 3 Jul 2000 20:29:00 -0600 (MDT) From: "Jason L. Schwab" To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Weird Networking.... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello folks; I have a machine running FreeBSD 3.5-STABLE, runs just awesome! It has 18 IP Addresses binded to it. I can ping all 18 IP Addresses from any where and I get replies, so they work just fine. Except! I can only ping the first IP that I setup the machine with locally. I have nothing blocking anything (as in firewall rules) right now. Any ideas? thanks.... - - Jason L. Schwab CEO / Unix System Administrator Simple Hosting Solutions www.simphost.com -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBOWFL8b8A35MJ2lm3EQKWSQCg4PYCbhoxnd/dAAU860mGe5KzTrYAnjXl kOdUbfdmeUmPAH/PaRlHQFbO =Kvgc -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 19:36:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id A346D37C3BC; Mon, 3 Jul 2000 19:36:34 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id VAA16571; Mon, 3 Jul 2000 21:36:11 -0500 (CDT) (envelope-from dan) Date: Mon, 3 Jul 2000 21:36:11 -0500 From: Dan Nelson To: "Jason L. Schwab" Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Weird Networking.... Message-ID: <20000703213611.A16527@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.4i In-Reply-To: ; from "Jason L. Schwab" on Mon Jul 3 20:29:00 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Jul 03), Jason L. Schwab said: > I have a machine running FreeBSD 3.5-STABLE, runs just awesome! > It has 18 IP Addresses binded to it. I can ping all 18 IP Addresses > from any where and I get replies, so they work just fine. Except! I > can only ping the first IP that I setup the machine with locally. How did you set them up? -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 20: 8:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EB0637BF9A; Mon, 3 Jul 2000 20:08:25 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id VAA67501; Mon, 3 Jul 2000 21:08:07 -0600 (MDT) Date: Mon, 3 Jul 2000 21:08:07 -0600 (MDT) From: Nick Rogness To: "Jason L. Schwab" Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird Networking.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 3 Jul 2000, Jason L. Schwab wrote: > > I have a machine running FreeBSD 3.5-STABLE, runs just awesome! It > has 18 IP Addresses binded to it. I can ping all 18 IP Addresses from any > where and I get replies, so they work just fine. Except! I can only ping > the first IP that I setup the machine with locally. > > I have nothing blocking anything (as in firewall rules) right now. > > Any ideas? Yes, it is ARP related. Look at arp(8). You will need to add an arp entry for each IP. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 20:47: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns.pnpa.net (ns.pnpa.net [216.37.241.2]) by hub.freebsd.org (Postfix) with ESMTP id 1E8F137BAF5; Mon, 3 Jul 2000 20:46:57 -0700 (PDT) (envelope-from reillyie@pnpa.net) Received: from localhost (reillyie@localhost) by ns.pnpa.net (8.9.0/8.9.0) with ESMTP id XAA04364; Mon, 3 Jul 2000 23:41:07 -0400 (EDT) Date: Mon, 3 Jul 2000 23:41:07 -0400 (EDT) From: Ian Reilly To: Nick Rogness Cc: "Jason L. Schwab" , freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Weird Networking.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org try something to the effect of.. arp -s `/usr/libexec/linkaddr your.ip.address.here` pub note the use of back quotes On Mon, 3 Jul 2000, Nick Rogness wrote: > On Mon, 3 Jul 2000, Jason L. Schwab wrote: > > > > > I have a machine running FreeBSD 3.5-STABLE, runs just awesome! It > > has 18 IP Addresses binded to it. I can ping all 18 IP Addresses from any > > where and I get replies, so they work just fine. Except! I can only ping > > the first IP that I setup the machine with locally. > > > > I have nothing blocking anything (as in firewall rules) right now. > > > > Any ideas? > > Yes, it is ARP related. Look at arp(8). You will need to add an > arp entry for each IP. > > Nick Rogness > - Speak softly and carry a Gigabit switch. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 3 23:16:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 0F11837B778 for ; Mon, 3 Jul 2000 23:16:23 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Tue Jul 04 02:14:39 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jul 2000 02:14:32 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C93F@SN1EXCHMBX> From: Nick Evans To: "'freebsd-net@freebsd.org'" Subject: Intel Pro/100+ Dual Port Server Adapter and Fault Tolerance Date: Tue, 4 Jul 2000 02:14:24 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE57F.19E68BD0" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE57F.19E68BD0 Content-Type: text/plain; charset="iso-8859-1" Does anyone know if the FXP driver in 4.0-STABLE supports the AFT Fault Tolerance features of this network card? I know the fault tolerance is set in the driver under WindowsNT but I'm not quite sure whether or not it is supported, or will be supported, on FreeBSD. --------------------------------------- nick.evans network.engineering NextVenue, Inc. phone: 212.909.2988 pager: 888.642.5541 email: nevans@nextvenue.com 6425541@skytel.com ------_=_NextPart_001_01BFE57F.19E68BD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Intel Pro/100+ Dual Port Server Adapter and Fault = Tolerance

Does anyone know if the FXP driver in = 4.0-STABLE supports the AFT Fault Tolerance features of this network = card? I know the fault tolerance is set in the driver under WindowsNT = but I'm not quite sure whether or not it is supported, or will be = supported, on FreeBSD.


---------------------------------------
nick.evans
network.engineering
NextVenue, Inc.
phone: 212.909.2988
pager: 888.642.5541
email: nevans@nextvenue.com
          = 6425541@skytel.com

------_=_NextPart_001_01BFE57F.19E68BD0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 3:16:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail0.u-aizu.ac.jp (mail0.u-aizu.ac.jp [163.143.1.43]) by hub.freebsd.org (Postfix) with ESMTP id A09A637B509 for ; Tue, 4 Jul 2000 03:15:19 -0700 (PDT) (envelope-from sarikaya@u-aizu.ac.jp) Received: from pross114.u-aizu.ac.jp (pross114 [163.143.180.102]) by mail0.u-aizu.ac.jp (8.9.3+3.1W/3.7Winternet-gw) with ESMTP id SAA15450; Tue, 4 Jul 2000 18:59:13 +0900 (JST) Received: from u-aizu.ac.jp (localhost [127.0.0.1]) by pross114.u-aizu.ac.jp (8.9.3+3.1W/3.7Wistcmx+kanji) with ESMTP id SAA19747; Tue, 4 Jul 2000 18:59:13 +0900 (JST) Message-ID: <3961B571.430B0D28@u-aizu.ac.jp> Date: Tue, 04 Jul 2000 18:59:13 +0900 From: Behcet Sarikaya Organization: University of Aizu X-Mailer: Mozilla 4.7 [en_jp] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG, snap-users@kame.net Subject: FreeBSD 4 Question : how to get pccardd on a desktop Content-Type: multipart/alternative; boundary="------------E59A25B56057535D9ABABDEE" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------E59A25B56057535D9ABABDEE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I installed FreeBSD 4.0 on a desktop that has MELCO PCI bus card for PCMCIA cards. I am having some trouble getting pccardd work on this host. MELCO card is recognized as follows (dmesg output): pcic-pci0: irq 0 at device 15.0 on pci0 But when I use rc.pccard to invoke pccardd I get /dev/card0 not defined message and pccardd doesnot start. I used GENERIC.KAME kernel configuration file that is included in kame-20000703-freebsd40-snap.tgz Thanks in advance, -- Behcet Sarikaya Computer Communications Lab. The University of Aizu Tsuruga, Ikki-machi, Aizu-wakamatsu City Fukushima, 965-8580 Japan Tel. +81-242-37-2559 Fax. +81-242-37-2742 Home page: http://www.u-aizu.ac.jp/~sarikaya/ email: sarikaya@u-aizu.ac.jp --------------E59A25B56057535D9ABABDEE Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello,
    I installed FreeBSD 4.0 on a desktop that has MELCO
PCI bus card for PCMCIA cards. I am having some trouble getting pccardd work on this host.
MELCO card is recognized as follows (dmesg output):
pcic-pci0: <Ricoh RL5C475 PCI-CardBus Bridge> irq 0 at device 15.0 on pci0

But when I use rc.pccard to invoke pccardd
I get /dev/card0 not defined
message and pccardd doesnot start.
  I used GENERIC.KAME kernel configuration file that is included in kame-20000703-freebsd40-snap.tgz

Thanks in advance, 

-- 
Behcet Sarikaya
Computer Communications Lab.
The University of Aizu
Tsuruga, Ikki-machi, Aizu-wakamatsu City
Fukushima, 965-8580 Japan
Tel. +81-242-37-2559 Fax. +81-242-37-2742 
Home page:  http://www.u-aizu.ac.jp/~sarikaya/
email: sarikaya@u-aizu.ac.jp
  --------------E59A25B56057535D9ABABDEE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 6: 7:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.pace.co.uk (mh.pace.co.uk [136.170.50.8]) by hub.freebsd.org (Postfix) with ESMTP id 719E437B869 for ; Tue, 4 Jul 2000 06:07:38 -0700 (PDT) (envelope-from kbracey@pace.co.uk) Received: from admin-1.pace.co.uk (admin-1.cam.pace.co.uk [136.170.131.64]) by mail.pace.co.uk (8.9.1b+Sun/8.9.1) with ESMTP id OAA02937 for ; Tue, 4 Jul 2000 14:07:33 +0100 (BST) Received: from art-work.cam.pace.co.uk (art-work.cam.pace.co.uk [136.170.131.5]) by admin-1.pace.co.uk (8.9.1b+Sun/8.9.1) with ESMTP id OAA13694 for ; Tue, 4 Jul 2000 14:07:33 +0100 (BST) Received: from kbracey.cam.pace.co.uk (kbracey.cam.pace.co.uk [136.170.129.213]) by art-work.cam.pace.co.uk (8.9.3+Sun/8.9.1) with SMTP id OAA27810 for ; Tue, 4 Jul 2000 14:07:32 +0100 (BST) Date: Tue, 04 Jul 2000 13:52:47 +0100 From: Kevin Bracey To: freebsd-net@freebsd.org Subject: Race condition in TCP connection drops? Message-ID: <282ed4d849%kbracey@kbracey.cam.pace.co.uk> X-Organization: Pace Micro Technology plc, Cambridge, United Kingdom X-Mailer: Messenger v1.40f for RISC OS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: RISC OS Newsbase 0.61b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just come across a nasty glitch in our FreeBSD derived IP stack, and I'm curious to know whether the problem is inherent in the BSD network code, or is due to our implementation of its environment. I'm describing this from a version of the source from about 2 years ago, so some of the functions (eg xxx_usrreq) referred to will have changed, but as far as I can tell the recent changes haven't affected this particular problem. The problem occurs when a connection is dropped - tcp_drop() calls tcp_close(), which then does: free(tp, M_PCB); inp->inp_ppcb = 0; soisdisconnected(so); in_pcbdetach(inp); tcpstat.tcps_closed++; return ((struct tcpcb *)0); soisdisconnected() calls sowakeup(), which, because SS_ASYNC is set, calls psignal(). Now, on our system, psignal() sends round an immediate message, on receipt of which an application detects the failure and calls close() on the socket. Then, soclose calls tcp_usrreq(PRU_DETACH), which aborts because the inp_ppcb pointer is 0. This is totally reliable on our system, because the psignal mechanism is synchronous. Are there interlocks to prevent this happening on FreeBSD, or is it a race condition? I'm not as familiar as I perhaps should be with the Unix kernel environment. Is there a reason for soisdisconnected() to be called before in_pcbdetach()? -- Kevin Bracey, Principal Software Engineer Pace Micro Technology plc Tel: +44 (0) 1223 518566 645 Newmarket Road Fax: +44 (0) 1223 518526 Cambridge, CB5 8PB, United Kingdom WWW: http://www.acorn.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 11: 0:39 2000 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 94F1837B527 for ; Tue, 4 Jul 2000 11:00:36 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA14200; Tue, 4 Jul 2000 10:49:44 -0700 (PDT) Message-Id: <200007041749.KAA14200@implode.root.com> To: Nick Evans Cc: "'freebsd-net@freebsd.org'" Subject: Re: Intel Pro/100+ Dual Port Server Adapter and Fault Tolerance In-reply-to: Your message of "Tue, 04 Jul 2000 02:14:24 EDT." <712384017032D411AD7B0001023D799B07C93F@SN1EXCHMBX> From: David Greenman Reply-To: dg@root.com Date: Tue, 04 Jul 2000 10:49:44 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Does anyone know if the FXP driver in 4.0-STABLE supports the AFT Fault >Tolerance features of this network card? I know the fault tolerance is set >in the driver under WindowsNT but I'm not quite sure whether or not it is >supported, or will be supported, on FreeBSD. Sorry, no, that feature is not supported. There are currently no plans to add support for it. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 11:29:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 85A2D37B59B for ; Tue, 4 Jul 2000 11:29:34 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA22401; Tue, 4 Jul 2000 14:29:20 -0400 (EDT) (envelope-from wollman) Date: Tue, 4 Jul 2000 14:29:20 -0400 (EDT) From: Garrett Wollman Message-Id: <200007041829.OAA22401@khavrinen.lcs.mit.edu> To: Kevin Bracey Cc: freebsd-net@FreeBSD.ORG Subject: Race condition in TCP connection drops? In-Reply-To: <282ed4d849%kbracey@kbracey.cam.pace.co.uk> References: <282ed4d849%kbracey@kbracey.cam.pace.co.uk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > This is totally reliable on our system, because the psignal mechanism is > synchronous. Are there interlocks to prevent this happening on FreeBSD, or is > it a race condition? On all BSD systems since time immemorial (and probably Bell Labs Unix before that), signal delivery is asynchronous, and the kernel is non-preemptible, so this is not possible. (There are no explicit interlocks /per se/; it's merely the consequence of a design choice made many years ago.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 11:38:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 0C7C237B877 for ; Tue, 4 Jul 2000 11:38:35 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Tue Jul 04 14:36:50 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jul 2000 14:36:43 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C945@SN1EXCHMBX> From: Nick Evans To: "'dg@root.com'" Cc: "'freebsd-net@freebsd.org'" Subject: RE: Intel Pro/100+ Dual Port Server Adapter and Fault Tolerance Date: Tue, 4 Jul 2000 14:36:41 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE5E6.CBA39F40" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE5E6.CBA39F40 Content-Type: text/plain; charset="iso-8859-1" ok, are there any NIC's that support some sort of fault tolerance? -----Original Message----- From: David Greenman [mailto:dg@root.com] Sent: Tuesday, July 04, 2000 1:50 PM To: Nick Evans Cc: 'freebsd-net@freebsd.org' Subject: Re: Intel Pro/100+ Dual Port Server Adapter and Fault Tolerance >Does anyone know if the FXP driver in 4.0-STABLE supports the AFT Fault >Tolerance features of this network card? I know the fault tolerance is set >in the driver under WindowsNT but I'm not quite sure whether or not it is >supported, or will be supported, on FreeBSD. Sorry, no, that feature is not supported. There are currently no plans to add support for it. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. ------_=_NextPart_001_01BFE5E6.CBA39F40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Intel Pro/100+ Dual Port Server Adapter and Fault Tolerance =

ok, are there any NIC's that support some sort of = fault tolerance?

-----Original Message-----
From: David Greenman [mailto:dg@root.com]
Sent: Tuesday, July 04, 2000 1:50 PM
To: Nick Evans
Cc: 'freebsd-net@freebsd.org'
Subject: Re: Intel Pro/100+ Dual Port Server Adapter = and Fault Tolerance



>Does anyone know if the FXP driver in 4.0-STABLE = supports the AFT Fault
>Tolerance features of this network card? I know = the fault tolerance is set
>in the driver under WindowsNT but I'm not quite = sure whether or not it is
>supported, or will be supported, on = FreeBSD.

   Sorry, no, that feature is not = supported. There are currently no plans to
add support for it.

-DG

David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - = http://www.terasolutions.com
Pave the road of life with opportunities.

------_=_NextPart_001_01BFE5E6.CBA39F40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 14:52:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail6.uunet.ca (mail6.uunet.ca [142.77.1.27]) by hub.freebsd.org (Postfix) with ESMTP id 38AF837B938 for ; Tue, 4 Jul 2000 14:52:22 -0700 (PDT) (envelope-from cwy@xiphos.ca) Received: from xiphos.ca ([216.95.199.148]) by mail6.uunet.ca with ESMTP id <231678-20538>; Tue, 4 Jul 2000 17:52:04 -0400 Message-ID: <39625CD1.57B64231@xiphos.ca> Date: Tue, 4 Jul 2000 17:53:21 -0400 From: Charlie Younghusband X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "'freebsd-net@freebsd.org'" Subject: supported features in BSD TCP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi folks, My company is considering working on some extensions to TCP for space communications. So I'm shopping around for a good modifiable TCP stack, with many questions I haven't found concisely in any docs Does the FreeBSD TCP implementation support: -Full RFC 1122 (general good behaviour for internet hosts), 768 (UDP) and 793 (standard TCP circa '81) b -RFC 1323 "TCP Extensions for High Performance" aka big fat pipes, including round trip time measurement and PAWS -T/TCP -- TCP Extensions for Transactions (RFC 1644) -TCP Vegas -Selective Negative Acknowledgements (SNACKs) -TCP Header compression (RFC 1144) And the BSD newbie questions: -What's the deal with FreeBSD/NetBSD/OpenBSD? Which one should I be using? (not intended to be flamebait, sorry...) -What are my options if I make modifications to the TCP stack (and new code) regarding licensing? I'm told that I can repackage it and sell it? (My boss wants to keep our options open, free open source is harder to pay my salary ;) And any other suggestions as to what direction I should take with this...the work will involve some custom space-standard services (aka breaking the normal TCP stack) as well as trying to fill out the TCP stack with high performance options described above...I looked briefly at some of the FreeBSD TCP source which seemed readable but a little too simple to include some of the features I hoped to start with... TIA Charlie -- Charlie Younghusband Network Systems Engineering Xiphos Technologies http://www.xiphos.ca/ 514-848-9640 (f) 514-848-9644 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 4 15:41:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 8659537B8C9 for ; Tue, 4 Jul 2000 15:40:49 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id PAA54662; Tue, 4 Jul 2000 15:40:45 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200007042240.PAA54662@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Charlie Younghusband Reply-To: freebsd-net@FreeBSD.ORG Cc: "'freebsd-net@freebsd.org'" Subject: Re: supported features in BSD TCP In-Reply-To: Message from Charlie Younghusband of "Tue, 04 Jul 2000 17:53:21 EDT." <39625CD1.57B64231@xiphos.ca> Date: Tue, 04 Jul 2000 15:40:45 -0700 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Charlie Younghusband wrote: > Hi folks, > > My company is considering working on some extensions to TCP for space > communications. So I'm shopping around for a good modifiable TCP stack, > with many questions I haven't found concisely in any docs > > Does the FreeBSD TCP implementation support: > -Full RFC 1122 (general good behaviour for internet hosts), 768 (UDP) > and 793 (standard TCP circa '81) Yes. > -RFC 1323 "TCP Extensions for High Performance" aka big fat pipes, > including round trip time measurement and PAWS Yes, controllable by a sysctl on/off switch. > -T/TCP -- TCP Extensions for Transactions (RFC 1644) Yes, controllable by a sysctl on/off switch. > -TCP Vegas No. (General opinion of this is that it would be bad for the internet) > -Selective Negative Acknowledgements (SNACKs) If you mean SACK, yes (patches available, not yet integrated). SNACK I had not heard of. We have a TCP newreno implementation as well. > -TCP Header compression (RFC 1144) Yes. Some others: - Precision TCP timers. We use our enhanced callout mechanism to provide precise scalable performance with large connection counts. Traditional BSD network stacks have a 1/2 second "service" list where all the connections are serviced from. Under load (hundreds of thousands of connections) our stack stands up better than most BSD stacks. (Which is why it is used at Yahoo). - kqueue (this is more a FreeBSD feature than a TCP stack feature though) - IPV6 - TCP checksum offloading - Experimental patches for zero-copy TCP/IP are around. - Can be made to saturate a gigabit ethernet link. > And the BSD newbie questions: > -What's the deal with FreeBSD/NetBSD/OpenBSD? Which one should I be > using? (not intended to be flamebait, sorry...) I believe neither NetBSD/OpenBSD have T/TCP. I am not certain about rfc1323. I believe NetBSD are about to implement TCP timers. > -What are my options if I make modifications to the TCP stack (and new > code) regarding licensing? I'm told that I can repackage it and sell > it? (My boss wants to keep our options open, free open source is harder > to pay my salary ;) You can pretty much do whatever you like, but remember that copyright on large chunks is still held by UC Berkeley. > And any other suggestions as to what direction I should take with > this...the work will involve some custom space-standard services (aka > breaking the normal TCP stack) as well as trying to fill out the TCP > stack with high performance options described above...I looked briefly > at some of the FreeBSD TCP source which seemed readable but a little too > simple to include some of the features I hoped to start with... Code does not have to be complicated to have features. Just be sure you are looking at a recent version - the older stuff was pretty light. (ie: 4.x at a minimum, 5.0 preferably) > TIA > Charlie Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 2:11:31 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.pace.co.uk (mh.pace.co.uk [136.170.50.8]) by hub.freebsd.org (Postfix) with ESMTP id 49CB737B782 for ; Wed, 5 Jul 2000 02:11:23 -0700 (PDT) (envelope-from kbracey@pace.co.uk) Received: from admin-1.pace.co.uk (admin-1.cam.pace.co.uk [136.170.131.64]) by mail.pace.co.uk (8.9.1b+Sun/8.9.1) with ESMTP id KAA11762 for ; Wed, 5 Jul 2000 10:11:17 +0100 (BST) Received: from art-work.cam.pace.co.uk (art-work.cam.pace.co.uk [136.170.131.5]) by admin-1.pace.co.uk (8.9.1b+Sun/8.9.1) with ESMTP id KAA19926 for ; Wed, 5 Jul 2000 10:11:17 +0100 (BST) Received: from kbracey.cam.pace.co.uk (kbracey.cam.pace.co.uk [136.170.129.213]) by art-work.cam.pace.co.uk (8.9.3+Sun/8.9.1) with SMTP id KAA09230 for ; Wed, 5 Jul 2000 10:11:16 +0100 (BST) Date: Wed, 05 Jul 2000 10:02:02 +0100 From: Kevin Bracey To: freebsd-net@freebsd.org Subject: Re: Race condition in TCP connection drops? Message-ID: <2de442d949%kbracey@kbracey.cam.pace.co.uk> In-Reply-To: <200007041829.OAA22401@khavrinen.lcs.mit.edu> X-Organization: Pace Micro Technology plc, Cambridge, United Kingdom X-Mailer: Messenger v1.40f for RISC OS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: RISC OS Newsbase 0.61b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200007041829.OAA22401@khavrinen.lcs.mit.edu> Garrett Wollman wrote: > < said: > > > This is totally reliable on our system, because the psignal mechanism is > > synchronous. Are there interlocks to prevent this happening on FreeBSD, or is > > it a race condition? > > On all BSD systems since time immemorial (and probably Bell Labs Unix > before that), signal delivery is asynchronous, and the kernel is > non-preemptible, so this is not possible. Thanks, I suspected it was something like that. A while back I tried changing psignal call to mark per-socket signal requirements in a bitfield, and then send them on exit from the network stack, as I was somewhat suspicious of this sort of problem occurring. Unfortunately that caused problems when the system was under high load (MPEG 2 video streaming in this case) - data would come in in spurts as fast as the stack could deal with it, so the network stack would remain looping through the interrupt queue in the packet input routine without sending any signals, so the socket buffer would overflow because the MPEG software wasn't getting a chance to read it. I'll have a go at doing something like that again, but with a few more points where signals can be triggered (eg each time round the input loop). Also, as far as I can see there's no need for soisdisconnected() to be called before in_pcbdetach() - if that's right, swapping those statements would be a very easy fix for my particular problem. -- Kevin Bracey, Principal Software Engineer Pace Micro Technology plc Tel: +44 (0) 1223 518566 645 Newmarket Road Fax: +44 (0) 1223 518526 Cambridge, CB5 8PB, United Kingdom WWW: http://www.acorn.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 4: 1:49 2000 Delivered-To: freebsd-net@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 1822437B847 for ; Wed, 5 Jul 2000 04:01:44 -0700 (PDT) (envelope-from bonnetf@bart.esiee.fr) Received: (from bonnetf@localhost) by bart.esiee.fr (8.10.1/8.10.1) id e65B1d004446 for freebsd-net@freebsd.org; Wed, 5 Jul 2000 13:01:39 +0200 (MEST) From: Frank Bonnet Message-Id: <200007051101.e65B1d004446@bart.esiee.fr> Subject: icmp-response bandwidth limit 201/200 pps To: freebsd-net@freebsd.org Date: Wed, 05 Jul 2000 13:01:39 MEST X-Mailer: Elm [revision: 212.5] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi On a machine running FreeBSD 4.0-20000622-STABLE and the caching software "squid" I get sometimes the following message : Jul 5 12:29:57 cache /kernel: icmp-response bandwidth limit 201/200 pps Any fbsd-net-guru to explain to me ? TIA -- Frank Bonnet Groupe ESIEE Paris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 5:20:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from odysseus.gedankenpolizei.de (p3E9BAAA7.dip.t-dialin.net [62.155.170.167]) by hub.freebsd.org (Postfix) with ESMTP id 530B937BDE8 for ; Wed, 5 Jul 2000 05:20:28 -0700 (PDT) (envelope-from karsten@gedankenpolizei.de) Received: (from karsten@localhost) by odysseus.gedankenpolizei.de (8.9.3/8.9.3) id OAA00491; Wed, 5 Jul 2000 14:22:09 +0200 (CEST) (envelope-from karsten) From: Karsten Patzwaldt Date: Wed, 5 Jul 2000 14:22:08 +0200 To: Ruslan Ermilov Cc: Karsten Patzwaldt , net@FreeBSD.ORG Subject: Re: NAT and PPPoE Message-ID: <20000705142208.A453@odysseus.gedankenpolizei.de> References: <20000702233552.A862@odysseus.gedankenpolizei.de> <051c01bfe4ba$466aaf30$040aa8c0@local.mindstep.com> <20000703105040.C73016@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000703105040.C73016@sunbay.com>; from ru@sunbay.com on Mon, Jul 03, 2000 at 10:50:40AM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 03, 2000 at 10:50:40AM +0300, Ruslan Ermilov wrote: > > Look for threads called '"frag-anyways" knob' and '[CFV] where to put the > > TCP MSS correction code'. The daemon is called "tcpmssd" and works like > > natd. > > > ... and is available from http://people.FreeBSD.org/~ru/tcpmssd.tgz Whoa, thanks, great, that fixed it! -- Karsten -- perl -e 'use Math::BigInt;$a=new Math::BigInt 1;print"Zahl: ";$b=<>;$a*= $b--while$b;print"Ergebnis: $a, Stellen: ".(length($a)-1)."\n"' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 7: 0:42 2000 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 238BC37B50F; Wed, 5 Jul 2000 07:00:33 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA28014; Wed, 5 Jul 2000 10:00:29 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 5 Jul 2000 10:00:29 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Archie Cobbs Cc: "Andrey A. Chernov" , freebsd-net@FreeBSD.ORG Subject: Re: cvs commit: src/sys/net if.c if_ethersubr.c if_var.h In-Reply-To: <200007011627.JAA05559@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (I've redirected this to freebsd-net, but Bcc'd committers and cvs-all since that is where it started) On Sat, 1 Jul 2000, Archie Cobbs wrote: > I'm going to fix that later. Right now you'll get a panic if you > eject a PCCARD ethernet that was doing netgraph, unfortunately. > > The problem is that the interfaces are not very object oriented > (with respect to type), combined with the dynamically loadable code. > As an example of the former, all ethernet drivers call if_attach() > and ether_attach() when connecting, but only if_detach() when > disconnecting. Perhaps they should all only call ether_attach() > and ether_detach(). > > The simplest 'correct' solution I can think of is to have a linker set > into which each interface type could link if it wanted to have a > special if_detach() callout.. and then put ethernet in there, so > it can call (*ng_ether_detach_p)() when an ethernet interface is > detached. > > Got any better ideas? > > Anyway, I'm on vacationthis next week so probably won't get around > to fixing this until after then.. unless someone else wants to > take a stab. This is similar to the bpf_detach() issue a few months ago -- nested, typed attaches and detaches might be beter handled in a more OOP way -- perhaps if_detach() should take the DLT type, allowing it to determine the appropriate set of attaches based on that type, which would include bpf_attach/detach, ether_attach/detach, ng attaching, and so on. BTW, one of the current causes of panics associated with removable ethernet devices is the (struct ifnet *) pointer in mbuf's. We use the pointer for a number of things, including ipfw rules with interface entries, bpf "seen" detection for packets, et al. However, when the struct ifnet is freed, needless to say, the results are unfortunate. A number of people have chatted about this at various times, and potential solutions include garbage collecting (the solution for BPF attachments in bpf_detach, but scales poorly to mbufs), an extra level of indirection (which would leak a (struct ifnet *) but allow NULLing of the pointer without tracking down all entries), and just leaking the struct ifnet. In a world of virtual interfaces and netgraph (a world a promote), I think we need to solve the removable interface issue properly. Refcounting is probably too heavy weight for mbuf creation/deletion, as it would require a lock for the struct ifnet during mbuf handling, which would be nasty. It could be worked around by storing queues of extra mbufs off the ifnet, or storing a symbolic name for the ifnet (since it is infrequently used) and doing a lookup when necessary. Anyhow, your thoughts (and even solutions here) are welcome :-). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 8:26:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DD39537B806; Wed, 5 Jul 2000 08:26:36 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA28965; Wed, 5 Jul 2000 11:26:13 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 5 Jul 2000 11:26:13 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Jason L. Schwab" Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird Networking.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 3 Jul 2000, Jason L. Schwab wrote: > I have a machine running FreeBSD 3.5-STABLE, runs just awesome! It > has 18 IP Addresses binded to it. I can ping all 18 IP Addresses from any > where and I get replies, so they work just fine. Except! I can only ping > the first IP that I setup the machine with locally. > > I have nothing blocking anything (as in firewall rules) right now. What command are you using to add IP addresses? Specifically, are you setting a netmask on the ifconfig line, and if so, what is that netmask? Do you get any warnings on adding the IP address to the interface? The command I use to add aliases under 4.x is: ifconfig de0 inet add 204.156.12.59 netmask 255.255.255.255 Under 3.x, I believe you have to use "alias" instead of "add" as I'm not sure that change was backported: ifconfig de0 inet alias 204.156.12.59 netmask 255.255.255.255 Specifying a netmask of 255.255.255.255 allows a routing entry to be created; by default, the netmask will normally be 255.255.255.0, which will conflict with the routing entry for the base IP address on the device (if they are in the same network). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 13:26:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from mrout2.yahoo.com (mrout2.yahoo.com [208.48.125.152]) by hub.freebsd.org (Postfix) with ESMTP id D0FE637B5E5 for ; Wed, 5 Jul 2000 13:26:38 -0700 (PDT) (envelope-from jayanth@yahoo-inc.com) Received: from milk.yahoo.com (milk.yahoo.com [206.251.16.37]) by mrout2.yahoo.com (8.10.0/8.10.0/y.out) with ESMTP id e65KQb432067 for ; Wed, 5 Jul 2000 13:26:37 -0700 (PDT) Received: (from jayanth@localhost) by milk.yahoo.com (8.8.8/8.6.12) id NAA00459 for freebsd-net@FreeBSD.ORG; Wed, 5 Jul 2000 13:26:37 -0700 (PDT) Date: Wed, 5 Jul 2000 13:26:37 -0700 From: jayanth To: freebsd-net@FreeBSD.ORG Subject: slowstart_flightsize Message-ID: <20000705132637.A26858@yahoo-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Not sure if this issue has been discussed before. Am I right in assuming that the sysctl value net.inet.tcp.slowstart_flightsize should never be set to zero ? If this value is zero the congestion window is reduced to 1 byte not one segment during slow start. Just wondering if a check should be added that sets the congestion window to one segment even if slowstart_flightsize = 0. jayanth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 5 23:20:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 67B9737B6F7 for ; Wed, 5 Jul 2000 23:20:18 -0700 (PDT) (envelope-from core@kame.net) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id PAA06768 for ; Thu, 6 Jul 2000 15:20:15 +0900 (JST) From: core@kame.net Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id PAA01314 for ; Thu, 6 Jul 2000 15:20:13 +0900 (JST) Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id PAA23099 for ; Thu, 6 Jul 2000 15:20:12 +0900 (JST) Date: Thu, 06 Jul 2000 15:18:46 +0900 (JST) Message-Id: <20000706.151846.26966264.kazu@Mew.org> To: net@FreeBSD.ORG Subject: KAME stable 20000704 X-Mailer: Mew version 1.95b43 on Emacs 21.0 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As usual, KAME Project has released "stable" packages of IPv6/IPsec network code for the following BSD variants. --- bsdi3 BSDI BSD/OS http://www.bsdi.com/ kernel: BSD/OS 3.1 patchlevel 0 userland: BSD/OS 3.0 patchlevel 0 include: BSD/OS 3.0 patchlevel 0 + ISC BIND 4.9.7 bsdi4 BSDI BSD/OS 4.1 patchlevel 0 http://www.bsdi.com/ freebsd2 FreeBSD 2.2.8-RELEASE http://www.freebsd.org/ freebsd3 FreeBSD 3.4-RELEASE http://www.freebsd.org/ netbsd NetBSD 1.4.2 http://www.netbsd.org/ openbsd OpenBSD 2.7 http://www.openbsd.org/ --- Note: {Free,Net,Open}BSD-current have already merged the KAME source code, from *past* versions of KAME codebase. For differences between KAME kits and *BSD tree, please visit: http://www.kame.net/project-overview.html#release http://www.kame.net/dev/cvsweb.cgi/kame/COVERAGE They are free of charge but absolutely no warranty. They are avaiable from the following web site: http://www.kame.net/ To know the changes from the previous stable package, please refer to the CHANGELOG/RELNOTES file. --KAME Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 1: 8: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E782E37B898; Thu, 6 Jul 2000 01:08:04 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA85784; Thu, 6 Jul 2000 01:08:04 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 6 Jul 2000 01:08:04 -0700 (PDT) From: Kris Kennaway To: current@Freebsd.org Cc: net@freebsd.org Subject: Call for help: KAME (inter)operational testing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If anyone is able to help in verifying the new FreeBSD-current KAME ipv6/ipsec code, especially if you have available other platform ipv6/ipsec implementations to test against, please let me know or drop by the #kame channel on efnet on IRC (server irc.lsl.com, for example) so we can work together. We need to test the new KAME code as much as possible prior to merging into 4.0-STABLE, so anything you can do to help would be appreciated. I particularly want to make sure that racoon (IKE daemon) works as expected (/usr/ports/security/racoon) since that is the primary reason for wanting to push this stuff into -stable. Thanks! Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 8:41:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 374C637C478 for ; Thu, 6 Jul 2000 08:41:18 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id KAA19759; Thu, 6 Jul 2000 10:46:21 -0500 (CDT) (envelope-from jlemon) Date: Thu, 6 Jul 2000 10:46:21 -0500 (CDT) From: Jonathan Lemon Message-Id: <200007061546.KAA19759@prism.flugsvamp.com> To: jayanth@yahoo-inc.com, net@freebsd.org Subject: Re: slowstart_flightsize X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >Not sure if this issue has been discussed before. > >Am I right in assuming that the sysctl value >net.inet.tcp.slowstart_flightsize should never be >set to zero ? If this value is zero the congestion window >is reduced to 1 byte not one segment during slow start. >Just wondering if a check should be added that sets the >congestion window to one segment even if slowstart_flightsize = 0. Yes, there probably should be a safety belt of some sort, the range of this should probably be something like 1 .. 5 (or some other small number). I didn't put in any checks, since I figured that the people tweaking this knob would already know what its purpose was. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 9:15: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 5688437BC44 for ; Thu, 6 Jul 2000 09:14:59 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Thu Jul 06 12:13:14 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Thu, 6 Jul 2000 12:13:07 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> From: Nick Evans To: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: bridging Date: Thu, 6 Jul 2000 12:13:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE765.1217DC50" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE765.1217DC50 Content-Type: text/plain; charset="iso-8859-1" Correct me if I am wrong, but isn't bridging of two interfaces supposed to make a duplicate of the traffic from one onto another? Why is it then that on the second interface I bridge to I only see broadcast and multicast packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. any ideas? ------------------------------------------ nick.evans network.engineering NextVenue, Inc. phone: (212) 909.2988 pager: (888) 642.5541 ------_=_NextPart_001_01BFE765.1217DC50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable bridging

Correct me if I am wrong, but isn't bridging of two = interfaces supposed to make a duplicate of the traffic from one onto = another? Why is it then that on the second interface I bridge to I only = see broadcast and multicast packets? I have fxp0 and fxp1 acting as a = bridge, fxp0 sees all kinds of http traffic, napster, IM, etc. but fxp1 = sees only multi/broadcast packets.

any ideas?


------------------------------------------
nick.evans
network.engineering
NextVenue, Inc.
phone: (212) 909.2988
pager: (888) 642.5541

------_=_NextPart_001_01BFE765.1217DC50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 9:28:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 2647037BBFA; Thu, 6 Jul 2000 09:28:25 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id DC40A3E4A; Thu, 6 Jul 2000 18:28:20 +0200 (CEST) Date: Thu, 6 Jul 2000 18:28:20 +0200 From: Jesper Skriver To: Nick Evans Cc: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging Message-ID: <20000706182820.B54678@skriver.dk> References: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX>; from nevans@nextvenue.com on Thu, Jul 06, 2000 at 12:13:07PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 06, 2000 at 12:13:07PM -0400, Nick Evans wrote: > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that > on the second interface I bridge to I only see broadcast and multicast > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. Bridging will only bridge unicast packet's who's destination MAC adress is on the other side of the bridge. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 9:28:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id D8FB137C463 for ; Thu, 6 Jul 2000 09:28:51 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA85744; Thu, 6 Jul 2000 18:29:39 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200007061629.SAA85744@info.iet.unipi.it> Subject: Re: bridging In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> from Nick Evans at "Jul 6, 2000 12:13:07 pm" To: Nick Evans Date: Thu, 6 Jul 2000 18:29:39 +0200 (CEST) Cc: net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Cc list trimmed to -net only!] > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that > on the second interface I bridge to I only see broadcast and multicast > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. because for unicast traffic, the bridge only forwards those packets for which there are receivers on that interface. Ideally it should do the same for multicast but that is a bit trickier to implement so i decided to leave this out. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 9:44: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 5149237C483; Thu, 6 Jul 2000 09:43:59 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA16116; Thu, 6 Jul 2000 12:44:54 -0400 (EDT) Message-Id: <200007061644.MAA16116@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 06 Jul 2000 12:53:56 -0400 To: Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" From: Dennis Subject: Re: bridging In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:13 PM 7/6/00 -0400, Nick Evans wrote: > > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that on > the second interface I bridge to I only see broadcast and multicast packets? > I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of http traffic, > napster, IM, etc. but fxp1 sees only multi/broadcast packets. Bridges only forward traffic that it thinks it need to...broadcasts, TO known devices and TO unknown devices.It doesnt forward traffic that it knows is destined for the local network. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 10:14:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from wiz.plymouth.edu (ness.plymouth.edu [158.136.1.140]) by hub.freebsd.org (Postfix) with ESMTP id 3F07337BBEF; Thu, 6 Jul 2000 10:14:25 -0700 (PDT) (envelope-from ted@wiz.plymouth.edu) Received: (from ted@localhost) by wiz.plymouth.edu (8.10.2/8.10.0) id e66HE6B85065; Thu, 6 Jul 2000 13:14:06 -0400 (EDT) From: Ted Wisniewski Message-Id: <200007061714.e66HE6B85065@wiz.plymouth.edu> Subject: Re: bridging In-Reply-To: <20000706182820.B54678@skriver.dk> from Jesper Skriver at "Jul 6, 2000 06:28:20 pm" To: jesper@skriver.dk (Jesper Skriver) Date: Thu, 6 Jul 2000 13:14:06 -0400 (EDT) Cc: nevans@nextvenue.com (Nick Evans), freebsd-hackers@FreeBSD.ORG ('freebsd-hackers@freebsd.org'), freebsd-net@FreeBSD.ORG ('freebsd-net@freebsd.org') X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (* On Thu, Jul 06, 2000 at 12:13:07PM -0400, Nick Evans wrote: (* > Correct me if I am wrong, but isn't bridging of two interfaces supposed to (* > make a duplicate of the traffic from one onto another? Why is it then that (* > on the second interface I bridge to I only see broadcast and multicast (* > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of (* > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. (* (* Bridging will only bridge unicast packet's who's destination MAC adress is (* on the other side of the bridge. How about RIP? I recently tried to upgrade my FreeBSD 4.0 bridging-firewall to CURRENT and I could no longer get RIP packets through (reliably) (even with no rules and "DEFAULT_TOACCEPT") and had all kinds of routing problems... Routers could not learn the route out because RIP was not going through. Of course I backed back off to 4.0-RELEASE and life was good again... I sent in a PR but have not heard anything yet. Advice? Thanks -- | Ted Wisniewski INET: ted@oz.plymouth.edu | | Computer Services ted@wiz.plymouth.edu | | Plymouth State College tedw@tigger.plymouth.edu | | Plymouth NH, 03264 HTTP: http://oz.plymouth.edu/~ted/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 16:25:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 3D40F37B9C0 for ; Thu, 6 Jul 2000 16:25:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA26570 for ; Thu, 6 Jul 2000 16:24:57 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from FreeBSD.org (jhb@localhost [127.0.0.1]) by foo.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA09526 for ; Thu, 6 Jul 2000 16:24:32 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: <39651530.2E0E0F8@FreeBSD.org> Date: Thu, 06 Jul 2000 16:24:32 -0700 From: John Baldwin Organization: BSD, Inc. X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: net@FreeBSD.org Subject: Patches to ifconfig(8) to allow 'ether' to set ethernet addresses Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, I've patched the ifconfig(8) utility to add in enough of the backend to the fake ether address "family" to allow setting addresses via the "ether" keyword. IOW, you can now do: ifconfig fxp0 ether Nothing else has been changed as far as the user interface. I did change the address family of the 'ether' address to AF_LINK, and just special cased the opening of the socket to fallback to AF_INET if the family it was trying to open was AF_INET. This also allowed several extra checks in addition to address family checking in the status output to be gotten rid of since the fake address "families" don't conflict with inet anymore. The patch can be found at http://people.FreeBSD.org/~jhb/patches/ether.patch. Also, as a side note, ifconfig -l
is broken. It only seems to work for the 'ether' family for some reason. Every other address family lists all the interfaces. The problem seems to be that the sysctl() call isn't actually limiting the list it returns by the address family. For example, I have no IPX interfaces configured on my current box, yet: > ifconfig -a | grep -i ipx > ifconfig -l ipx fxp0 lo0 gif0 gif1 gif2 gif3 stf0 faith0 -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 19:24:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [208.48.125.95]) by hub.freebsd.org (Postfix) with ESMTP id 6F10037BD7D for ; Thu, 6 Jul 2000 19:24:16 -0700 (PDT) (envelope-from jayanth@yahoo-inc.com) Received: from milk.yahoo.com (milk.yahoo.com [206.251.16.37]) by mrout1.yahoo.com (8.10.0/8.10.0/y.out) with ESMTP id e672O2488469 for ; Thu, 6 Jul 2000 19:24:03 -0700 (PDT) Received: (from jayanth@localhost) by milk.yahoo.com (8.8.8/8.6.12) id TAA26629 for net@FreeBSD.ORG; Thu, 6 Jul 2000 19:24:02 -0700 (PDT) Date: Thu, 6 Jul 2000 19:24:02 -0700 From: jayanth To: net@FreeBSD.ORG Subject: deleting cloned routes Message-ID: <20000706192402.A25086@yahoo-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One of the issues during a syn flood is that the routing table fills up easily because of the cloned routes being generated. In Freebsd current, an incomplete connection is randomly dropped when the listen queue overflows. This logic could be easily extended by deleting the cloned route that is associated with the connection being dropped , if there is no information cached for that route. Is this a reasonable fix ? jayanth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 20: 1: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F55937B612; Thu, 6 Jul 2000 20:00:55 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id 82A0B3D32; Thu, 6 Jul 2000 23:01:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 7DB9F5BC4; Thu, 6 Jul 2000 23:01:58 -0400 (EDT) Date: Thu, 6 Jul 2000 23:01:58 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Nick Evans Cc: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bridges create a broadcast zone. broadcast packets will cross the bridge unobstructed. On Thu, 6 Jul 2000, Nick Evans wrote: > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that > on the second interface I bridge to I only see broadcast and multicast > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. > > any ideas? > > > ------------------------------------------ > nick.evans > network.engineering > NextVenue, Inc. > phone: (212) 909.2988 > pager: (888) 642.5541 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 20:45:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 7801837BBD6 for ; Thu, 6 Jul 2000 20:45:21 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 44661 invoked by uid 1000); 7 Jul 2000 03:45:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 03:45:19 -0000 Date: Thu, 6 Jul 2000 22:45:19 -0500 (CDT) From: Mike Silbersack To: jayanth Cc: net@FreeBSD.ORG Subject: Re: deleting cloned routes In-Reply-To: <20000706192402.A25086@yahoo-inc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 Jul 2000, jayanth wrote: > One of the issues during a syn flood is that the routing table > fills up easily because of the cloned routes being generated. > > In Freebsd current, an incomplete connection is randomly dropped > when the listen queue overflows. This logic could be easily extended > by deleting the cloned route that is associated with the connection > being dropped , if there is no information cached for that route. > > Is this a reasonable fix ? > > jayanth Seems to make sense on the surface to me. But, I haven't ever looked at the route code, so I have one more question: Even with the routes deleted won't you still end up with a bloated, fragmented route table? (Granted, it'll cap the growth by a large amount, so it should still be a big win.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 6 21: 6:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id A66A437BC8B; Thu, 6 Jul 2000 21:06:11 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id WAA67421; Thu, 6 Jul 2000 22:05:29 -0600 (MDT) Date: Thu, 6 Jul 2000 22:05:29 -0600 (MDT) From: Nick Rogness To: Sean Lutner Cc: Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 Jul 2000, Sean Lutner wrote: > > Bridges create a broadcast zone. broadcast packets will cross the bridge > unobstructed. OK. So do bridged interfaces fall within the same collision domain?... or are they just members of the same broadcast domain? Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 0:44:15 2000 Delivered-To: freebsd-net@freebsd.org Received: from d12lmsgate.de.ibm.com (d12lmsgate.de.ibm.com [195.212.91.199]) by hub.freebsd.org (Postfix) with ESMTP id 4E26037B5B2 for ; Fri, 7 Jul 2000 00:44:10 -0700 (PDT) (envelope-from DRHAGER@de.ibm.com) Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22]) by d12lmsgate.de.ibm.com (1.0.0) with ESMTP id JAA317384 for ; Fri, 7 Jul 2000 09:43:27 +0200 From: DRHAGER@de.ibm.com Received: from d12mta01.de.ibm.com (d12mta01_cs0 [9.165.222.237]) by d12relay01.de.ibm.com (8.8.8m3/NCO v2.07) with SMTP id JAA129350 for ; Fri, 7 Jul 2000 09:43:59 +0200 Received: by d12mta01.de.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id C1256915.002A77B3 ; Fri, 7 Jul 2000 09:43:51 +0200 X-Lotus-FromDomain: IBMDE To: net@FreeBSD.ORG Message-ID: Date: Fri, 7 Jul 2000 09:43:36 +0200 Subject: Adapter problem Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I got recently some old ISA/PCI motherboards (UM8810P) and 486-DX CPUs. I took some cheap NE2000 clone for PCI (RealTek 8029). Those worked ok for me sofar... I installed fbsd 3.1 Stable. Now, on booting the card comes up alright: ... ed1: rev 0x00 int a irq 12 on pci0.13.0 ed1: adress 00:40:05:6c:9d:84, type NE2000 16bit ... With ifconfig I see the card also. Everyting is connected fine. Now, if I try a ping, I get in the syslog: ed1: Device Timeout Can I do something? Or do I have to buy better cards? (A 3Com works well...) Any help appreciated! -Orm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 5:59:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts1-srv.bellnexxia.net (tomts1.bellnexxia.net [209.226.175.139]) by hub.freebsd.org (Postfix) with ESMTP id 56B3B37BC0E for ; Fri, 7 Jul 2000 05:59:40 -0700 (PDT) (envelope-from mwozniak@netcom.ca) Received: from mwozniak.uniservers.com ([64.228.64.43]) by tomts1-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20000707125939.XZHH8304.tomts1-srv.bellnexxia.net@mwozniak.uniservers.com>; Fri, 7 Jul 2000 08:59:39 -0400 Reply-To: From: "Michael Wozniak" To: , Subject: RE: Adapter problem Date: Fri, 7 Jul 2000 08:59:21 -0400 Message-ID: <001201bfe813$2e271880$0c80a8c0@mwozniak.uniservers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Typically a PS/2 mouse sits on IRQ 12. I would guess either disabling the mouse to free IRQ 12 for the 8029, or changing the IRQ of the slot you have the 8029 plugged in, or moving the 8029 to another slot will do it for you. Mike. > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of DRHAGER@de.ibm.com > Sent: Friday, July 07, 2000 3:44 AM > To: net@FreeBSD.ORG > Subject: Adapter problem > > ed1: rev 0x00 int a irq 12 on > pci0.13.0 > ed1: adress 00:40:05:6c:9d:84, type NE2000 16bit > ... > > With ifconfig I see the card also. Everyting is connected fine. > Now, if I try a ping, I get in the syslog: > ed1: Device Timeout To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 7:20:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5876037BE00 for ; Fri, 7 Jul 2000 07:20:17 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA37794; Fri, 7 Jul 2000 10:20:04 -0400 (EDT) (envelope-from wollman) Date: Fri, 7 Jul 2000 10:20:04 -0400 (EDT) From: Garrett Wollman Message-Id: <200007071420.KAA37794@khavrinen.lcs.mit.edu> To: jayanth Cc: net@FreeBSD.ORG Subject: deleting cloned routes In-Reply-To: <20000706192402.A25086@yahoo-inc.com> References: <20000706192402.A25086@yahoo-inc.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > In Freebsd current, an incomplete connection is randomly dropped > when the listen queue overflows. This logic could be easily extended > by deleting the cloned route that is associated with the connection > being dropped , if there is no information cached for that route. > Is this a reasonable fix ? It's a workable hack. I wouldn't call it a fix -- the real fix would be to separate out the three functions currently bundled together in the routing table into separate, more appropriate data structures. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 7:47:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7313C37BBD9; Fri, 7 Jul 2000 07:47:39 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA66448; Fri, 7 Jul 2000 10:47:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 7 Jul 2000 10:47:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Nick Rogness Cc: Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 Jul 2000, Nick Rogness wrote: > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > unobstructed. > > OK. So do bridged interfaces fall within the same collision > domain?... or are they just members of the same broadcast domain? FreeBSD bridging support places nodes in the same broadcast domain, but different collision domains. As such, you may see reordering of packets between segments, and packets may be lost transitting between segments. FreeBSD's bridging support is not 802.1d-compliant for a variety of reasons, and does not support spanning tree. That said, it is adequate for many uses, including our packet filtering support, which is very useful indeed :-). That said, we might do well to look at the OpenBSD bridging code and see if we can merge the behaviors -- they have some spiffy features (which I heard about at USENIX), including MAC-address based filtering, and some sort of VPN bridged technique (which sounds very useful). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 7:47:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by hub.freebsd.org (Postfix) with ESMTP id EAFBA37B505 for ; Fri, 7 Jul 2000 07:47:36 -0700 (PDT) (envelope-from lconrad@Go2France.com) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.03) id AD821FE80056; Fri, 07 Jul 2000 16:47:30 +0200 Message-Id: <4.3.2.7.2.20000707162836.03d4ead0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 07 Jul 2000 16:45:50 +0200 To: freebsd-net@FreeBSD.ORG From: Len Conrad Subject: Re: KAME stable 20000704 In-Reply-To: <20000706.151846.26966264.kazu@Mew.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Are there any hardware-encryption boards for KAME or OpenSSL? We've been talking to some large accounts that have evaluated variouis VPN solutions and had concluded that software-only VPN's just can't keep up with large number of simultaneous tunnels. They told us some Cisco box with hardware-encryption had the best comfort level. Len ===================== >As usual, KAME Project has released "stable" packages of IPv6/IPsec >network code for the following BSD variants. > >--- >bsdi3 BSDI BSD/OS http://www.bsdi.com/ > kernel: BSD/OS 3.1 patchlevel 0 > userland: BSD/OS 3.0 patchlevel 0 > include: BSD/OS 3.0 patchlevel 0 + ISC BIND 4.9.7 >bsdi4 BSDI BSD/OS 4.1 patchlevel 0 http://www.bsdi.com/ >freebsd2 FreeBSD 2.2.8-RELEASE http://www.freebsd.org/ >freebsd3 FreeBSD 3.4-RELEASE http://www.freebsd.org/ >netbsd NetBSD 1.4.2 http://www.netbsd.org/ >openbsd OpenBSD 2.7 http://www.openbsd.org/ >--- > >Note: {Free,Net,Open}BSD-current have already merged the KAME source >code, from *past* versions of KAME codebase. For differences between >KAME kits and *BSD tree, please visit: > http://www.kame.net/project-overview.html#release > http://www.kame.net/dev/cvsweb.cgi/kame/COVERAGE > >They are free of charge but absolutely no warranty. They are avaiable >from the following web site: > > http://www.kame.net/ > >To know the changes from the previous stable package, please refer to >the CHANGELOG/RELNOTES file. > >--KAME Project > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message Len http://BIND8NT.MEIway.com: ISC BIND 8 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 8: 4:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id E3C5437C740 for ; Fri, 7 Jul 2000 08:04:47 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id AAA12856; Sat, 8 Jul 2000 00:04:32 +0900 (JST) To: Len Conrad Cc: freebsd-net@FreeBSD.ORG In-reply-to: lconrad's message of Fri, 07 Jul 2000 16:45:50 +0200. <4.3.2.7.2.20000707162836.03d4ead0@mail.Go2France.com> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: KAME stable 20000704 From: itojun@iijlab.net Date: Sat, 08 Jul 2000 00:04:32 +0900 Message-ID: <12854.962982272@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Are there any hardware-encryption boards for KAME or OpenSSL? >We've been talking to some large accounts that have evaluated variouis VPN >solutions and had concluded that software-only VPN's just can't keep up >with large number of simultaneous tunnels. They told us some Cisco box >with hardware-encryption had the best comfort level. no (not at this moment). openbsd has *tremendous* support for hardware-encryption enabled ipsec. not sure if the supported card is sold outside of the US. KAME intends to do it, though, it is a major problem to tackle. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 8:54:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 582CB37BC89 for ; Fri, 7 Jul 2000 08:54:01 -0700 (PDT) (envelope-from ras@e-gerbil.net) Received: from localhost (ras@localhost) by overlord.e-gerbil.net (8.9.3/8.9.3) with ESMTP id LAA06682 for ; Fri, 7 Jul 2000 11:53:56 -0400 (EDT) (envelope-from ras@e-gerbil.net) X-Authentication-Warning: overlord.e-gerbil.net: ras owned process doing -bs Date: Fri, 7 Jul 2000 11:53:56 -0400 (EDT) From: "Richard A. Steenbergen" To: freebsd-net@freebsd.org Subject: stuck in LAST_ACK Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 207.91.110.247.20 24.64.167.230.1223 LAST_ACK tcp4 0 0 207.91.110.247.20 24.64.167.230.1156 LAST_ACK tcp4 0 0 207.91.110.247.20 24.64.167.230.1148 LAST_ACK tcp4 0 0 207.91.110.247.20 24.64.167.230.4799 LAST_ACK tcp4 0 0 207.91.110.247.20 24.64.167.230.4145 LAST_ACK tcp4 0 0 207.91.110.247.20 24.64.167.230.4023 LAST_ACK I somehow managed to get some sockets stuck in LAST_ACK, which is preventing the ftpd from binding port 20 even w/SO_REUSEADDR or SO_REUSEPORT. This is on a -STABLE system, any ideas how it would get stuck in LAST_ACK? -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 9: 4: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from sofia.csl.sri.com (sofia.csl.sri.com [130.107.19.127]) by hub.freebsd.org (Postfix) with ESMTP id 4D6AA37C194 for ; Fri, 7 Jul 2000 09:03:44 -0700 (PDT) (envelope-from molter@sofia.csl.sri.com) Received: (from molter@localhost) by sofia.csl.sri.com (8.9.3/8.9.3) id JAA09878; Fri, 7 Jul 2000 09:05:03 -0700 (PDT) (envelope-from molter) From: Marco Molteni Date: Fri, 7 Jul 2000 09:05:03 -0700 To: net@FreeBSD.ORG Cc: Garrett Wollman Subject: Re: deleting cloned routes Message-ID: <20000707090503.A9860@sofia.csl.sri.com> Reply-To: net@FreeBSD.ORG References: <20000706192402.A25086@yahoo-inc.com> <200007071420.KAA37794@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200007071420.KAA37794@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Fri, Jul 07, 2000 at 10:20:04AM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 07 Jul 2000, Garrett Wollman wrote: > < said: > > > In Freebsd current, an incomplete connection is randomly dropped > > when the listen queue overflows. This logic could be easily extended > > by deleting the cloned route that is associated with the connection > > being dropped , if there is no information cached for that route. > > > Is this a reasonable fix ? > > It's a workable hack. I wouldn't call it a fix -- the real fix would > be to separate out the three functions currently bundled together in > the routing table into separate, more appropriate data structures. Garrett, as you may remember, I am interested in the routing code. Do you care to elaborate a little more about "separate out the three functions currently bundled together in the routing table" ? Thanks Marco -- Marco Molteni "rough consensus and running code" SRI International, System Design Laboratory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 9:10:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id B1A9037BE30 for ; Fri, 7 Jul 2000 09:10:36 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id MAA92715; Fri, 7 Jul 2000 12:10:32 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200007071610.MAA92715@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Len Conrad Cc: freebsd-net@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: KAME stable 20000704 References: <4.3.2.7.2.20000707162836.03d4ead0@mail.Go2France.com> In-reply-to: Your message of "Fri, 07 Jul 2000 16:45:50 +0200." <4.3.2.7.2.20000707162836.03d4ead0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jul 2000 12:10:32 -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There's no current support in KAME or OpenSSL for hardware encryption acceleration. The OpenBSD guys have support for a Hi/fn 7751-based board (see http://www.powercrypt.com which is reasonably priced.) It's supported for use in their IPSEC stack only at this point. I've got a couple of these boards that I'm playing with in my spare time. Currently, I'm learning the wonders of newbus to figure out how to port the OpenBSD driver. The powercrypt board is available with FreeBSD drivers (including for 4.0 and 5.0-current) which exports a user-mode interface for fairly "raw" access to the hardware. You might be able to use that interface to speed-up SSL operations. The Hi/fn board can support probably a couple hundred crypto contexts simultanously, if I recall correctly. That number drops quite a bit if you want to perform compression because the compression contexts are quite a bit larger. louie > Hi > > Are there any hardware-encryption boards for KAME or OpenSSL? > > We've been talking to some large accounts that have evaluated variouis VPN > solutions and had concluded that software-only VPN's just can't keep up > with large number of simultaneous tunnels. They told us some Cisco box > with hardware-encryption had the best comfort level. > > Len > > ===================== > > >As usual, KAME Project has released "stable" packages of IPv6/IPsec > >network code for the following BSD variants. > > > >--- > >bsdi3 BSDI BSD/OS http://www.bsdi.com/ > > kernel: BSD/OS 3.1 patchlevel 0 > > userland: BSD/OS 3.0 patchlevel 0 > > include: BSD/OS 3.0 patchlevel 0 + ISC BIND 4.9.7 > >bsdi4 BSDI BSD/OS 4.1 patchlevel 0 http://www.bsdi.com/ > >freebsd2 FreeBSD 2.2.8-RELEASE http://www.freebsd.org/ > >freebsd3 FreeBSD 3.4-RELEASE http://www.freebsd.org/ > >netbsd NetBSD 1.4.2 http://www.netbsd.org/ > >openbsd OpenBSD 2.7 http://www.openbsd.org/ > >--- > > > >Note: {Free,Net,Open}BSD-current have already merged the KAME source > >code, from *past* versions of KAME codebase. For differences between > >KAME kits and *BSD tree, please visit: > > http://www.kame.net/project-overview.html#release > > http://www.kame.net/dev/cvsweb.cgi/kame/COVERAGE > > > >They are free of charge but absolutely no warranty. They are avaiable > >from the following web site: > > > > http://www.kame.net/ > > > >To know the changes from the previous stable package, please refer to > >the CHANGELOG/RELNOTES file. > > > >--KAME Project > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-net" in the body of the message > > Len > http://BIND8NT.MEIway.com: ISC BIND 8 installable binary for NT4 > http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 9:56:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 72F3237B546 for ; Fri, 7 Jul 2000 09:56:37 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FXC002BV6GDCV@falla.videotron.net> for freebsd-net@FreeBSD.ORG; Fri, 7 Jul 2000 12:43:25 -0400 (EDT) Date: Fri, 07 Jul 2000 12:45:34 -0400 (EDT) From: Bosko Milekic Subject: Re: stuck in LAST_ACK In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: "Richard A. Steenbergen" Cc: freebsd-net@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Do they time out after a while ? (e.g. 5-10 minutes) On Fri, 7 Jul 2000, Richard A. Steenbergen wrote: > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp4 0 0 207.91.110.247.20 24.64.167.230.1223 LAST_ACK > tcp4 0 0 207.91.110.247.20 24.64.167.230.1156 LAST_ACK > tcp4 0 0 207.91.110.247.20 24.64.167.230.1148 LAST_ACK > tcp4 0 0 207.91.110.247.20 24.64.167.230.4799 LAST_ACK > tcp4 0 0 207.91.110.247.20 24.64.167.230.4145 LAST_ACK > tcp4 0 0 207.91.110.247.20 24.64.167.230.4023 LAST_ACK > > I somehow managed to get some sockets stuck in LAST_ACK, which is > preventing the ftpd from binding port 20 even w/SO_REUSEADDR or > SO_REUSEPORT. This is on a -STABLE system, any ideas how it would get > stuck in LAST_ACK? > > -- > Richard A Steenbergen http://www.e-gerbil.net/humble > PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > > -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 9:57:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 7783C37B7E2 for ; Fri, 7 Jul 2000 09:57:43 -0700 (PDT) (envelope-from ras@e-gerbil.net) Received: from localhost (ras@localhost) by overlord.e-gerbil.net (8.9.3/8.9.3) with ESMTP id MAA47570; Fri, 7 Jul 2000 12:57:37 -0400 (EDT) (envelope-from ras@e-gerbil.net) X-Authentication-Warning: overlord.e-gerbil.net: ras owned process doing -bs Date: Fri, 7 Jul 2000 12:57:36 -0400 (EDT) From: "Richard A. Steenbergen" To: Bosko Milekic Cc: freebsd-net@FreeBSD.ORG Subject: Re: stuck in LAST_ACK In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Bosko Milekic wrote: > > Do they time out after a while ? (e.g. 5-10 minutes) Nope, they've been here for at least the past 2 days. I'm not willing to reboot, moved the FTP data port elsewhere for the momment. :P -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 10: 5:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from webshield2.nai.com (webshield2.nai.com [161.69.3.73]) by hub.freebsd.org (Postfix) with SMTP id 7BA4937BE14 for ; Fri, 7 Jul 2000 10:05:48 -0700 (PDT) (envelope-from Roger_Knobbe@NAI.com) Received: FROM ca-ex-bridge1.nai.com BY webshield2.nai.com ; Fri Jul 07 10:09:06 2000 -0700 Received: by na-ex-bridge1.nai.com with Internet Mail Service (5.5.2650.21) id <3LR3V29F>; Fri, 7 Jul 2000 10:08:08 -0700 Message-ID: <1D4F16D4D695D21186A300A0C9DCF983611F15@dns-83-207.dhcp.nai.com> From: "Knobbe, Roger" To: "'freebsd-net@freebsd.org'" Subject: majordomo not listening? Date: Fri, 7 Jul 2000 10:04:22 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been sending mail for a couple of weeks on and off to majordomo@freebsd.org trying to remove rogerk@tis.com (an old, forwarded address) from the freebsd-net mailing list. It ain't working. Could the moderator please remove me? Thanks. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1 Comment: Crypto Provided by Network Associates iQA/AwUBOWYNy368oPxhkRjlEQLYMwCg6tnXmvLebpjh4K+fU7VbaZjoW04AnRSf ECwpfOsDwy5QS+ihOnxWA/bP =5uuS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 10:36:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 9DF2537BF36 for ; Fri, 7 Jul 2000 10:36:13 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA38634; Fri, 7 Jul 2000 13:36:11 -0400 (EDT) (envelope-from wollman) Date: Fri, 7 Jul 2000 13:36:11 -0400 (EDT) From: Garrett Wollman Message-Id: <200007071736.NAA38634@khavrinen.lcs.mit.edu> To: net@FreeBSD.ORG Subject: Re: deleting cloned routes In-Reply-To: <20000707090503.A9860@sofia.csl.sri.com> References: <20000706192402.A25086@yahoo-inc.com> <200007071420.KAA37794@khavrinen.lcs.mit.edu> <20000707090503.A9860@sofia.csl.sri.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > as you may remember, I am interested in the routing code. Do you care > to elaborate a little more about "separate out the three functions > currently bundled together in the routing table" ? There are currently three (or perhaps four) functions handled by the routing code in FreeBSD. These are: 1) Forwarding table -- the traditional function of the routing code: given a packet addressed to w.x.y.z, to whom should I send that packet to start it on its journey? 2) Next-hop table -- which bits do I glom on the front of packets addressed to a.b.c.d in order to get them there, and out which interface(s) should I send them? 3) Per-host cache -- just a random collection of information that we think is useful to remember about a host that we have talked to, but we don't care if it gets thrown away from time to time. 4) Routing table -- expression of the generalized mapping -> *() Currently, in FreeBSD, we have a data structure which is designed to do (4) quite well, and was hacked by me into doing (3) and by people at Berkeley into doing (2). The function of (1) is entirely subsumed into (4). (It's actually even worse than that: if the system is running an actual routing process, it has at least two independent copies of (4): one in the routing process and one in the kernel.) The trouble with doing this is that the (4) data structure is not particularly efficient (in either space or time) for the functions of (1)-(3). For example, on an ILP32 architecture, `struct rtentry' contains ~80 bytes of overhead which are not required for per-host cache entries. (What can I say? When all you have is a radix tree, everything looks like a route.) A different data structure, taking advantage of the fixed address length and disposability of this information would be much more efficient. As another example, there are algorithms for creating a forwarding table which while computationally expensive result in data structures small enough to fit into a L2 cache, even for a full 70,000-route border router. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 11:20:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id A0C4537C568 for ; Fri, 7 Jul 2000 11:20:13 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FXC0034DAF0HD@field.videotron.net> for freebsd-net@FreeBSD.ORG; Fri, 7 Jul 2000 14:09:00 -0400 (EDT) Date: Fri, 07 Jul 2000 14:11:09 -0400 (EDT) From: Bosko Milekic Subject: Re: stuck in LAST_ACK In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: "Richard A. Steenbergen" Cc: freebsd-net@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Show us `netstat -m' please, also `netstat -a | grep LAST_ACK' (at least a portion). Also, `uname -a' would be nice. jlemon fixed a similar problem not too long ago in -CURRENT that may be related to this. On Fri, 7 Jul 2000, Richard A. Steenbergen wrote: > On Fri, 7 Jul 2000, Bosko Milekic wrote: > > > > > Do they time out after a while ? (e.g. 5-10 minutes) > > Nope, they've been here for at least the past 2 days. I'm not willing to > reboot, moved the FTP data port elsewhere for the momment. :P > > -- > Richard A Steenbergen http://www.e-gerbil.net/humble > PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) > > -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 11:22:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 6EBE237C4CC for ; Fri, 7 Jul 2000 11:22:38 -0700 (PDT) (envelope-from ras@e-gerbil.net) Received: from localhost (ras@localhost) by overlord.e-gerbil.net (8.9.3/8.9.3) with ESMTP id OAA79509; Fri, 7 Jul 2000 14:22:31 -0400 (EDT) (envelope-from ras@e-gerbil.net) X-Authentication-Warning: overlord.e-gerbil.net: ras owned process doing -bs Date: Fri, 7 Jul 2000 14:22:26 -0400 (EDT) From: "Richard A. Steenbergen" To: Bosko Milekic Cc: freebsd-net@FreeBSD.ORG Subject: Re: stuck in LAST_ACK In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Bosko Milekic wrote: > > Show us `netstat -m' please, also `netstat -a | grep LAST_ACK' (at least > a portion). Also, `uname -a' would be nice. jlemon fixed a similar > problem not too long ago in -CURRENT that may be related to this. 480/2224/260000 mbufs in use (current/peak/max): 451 mbufs allocated to data 29 mbufs allocated to packet headers 320/1792/65000 mbuf clusters in use (current/peak/max) 4140 Kbytes allocated to network (18% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines The full LAST_ACK list was in a previous email, 4.0-STABLE, didn't think the newreno stuff was an issue there. -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 12:29:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id CBD6D37BE0F for ; Fri, 7 Jul 2000 12:29:29 -0700 (PDT) (envelope-from inferno@nightfire.de) Received: from nightfire.de (hmbdi7-212-144-176-101.arcor-ip.net [212.144.176.101]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id VAA11958; Fri, 7 Jul 2000 21:29:23 +0200 (MET DST) Message-ID: <39662F09.A6A8182A@nightfire.de> Date: Fri, 07 Jul 2000 21:27:05 +0200 From: Olaf Hoyer Reply-To: ohoyer@fbwi.fh-wilhelmshaven.de X-Mailer: Mozilla 4.7 [de]C-CCK-MCD QXW0322q (Win95; I) X-Accept-Language: de,en MIME-Version: 1.0 To: DRHAGER@de.ibm.com Cc: net@FreeBSD.ORG Subject: Re: Adapter problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org DRHAGER@de.ibm.com schrieb: > > Hi, > I got recently some old ISA/PCI motherboards (UM8810P) and 486-DX CPUs. > > I took some cheap NE2000 clone for PCI (RealTek 8029). Those worked ok > for me sofar... > I installed fbsd 3.1 Stable. > > Now, on booting the card comes up alright: > > ... > ed1: rev 0x00 int a irq 12 on > pci0.13.0 > ed1: adress 00:40:05:6c:9d:84, type NE2000 16bit > ... > > With ifconfig I see the card also. Everyting is connected fine. > Now, if I try a ping, I get in the syslog: > ed1: Device Timeout > > Can I do something? Or do I have to buy better cards? > (A 3Com works well...) > Hi! Does the 3Com also hooks up to IRQ 12? Lots of old 486 mobo do not free the IRQ 12 even if no PS/2 mouse is present and switched off in BIOS. Also lots of the "el cheapo" clone cards are low mechanical quality... Regards Olaf Hoyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 12:49: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id B7BF637C886; Fri, 7 Jul 2000 12:49:01 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id VAA25929; Fri, 7 Jul 2000 21:48:51 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Fri, 7 Jul 2000 21:48:50 +0200 (EET) From: Narvi To: Nick Rogness Cc: Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 Jul 2000, Nick Rogness wrote: > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > unobstructed. > > OK. So do bridged interfaces fall within the same collision > domain?... or are they just members of the same broadcast domain? > They can't be in the same collison domain - you'll realise it if you think about it for a second. > > Nick Rogness > - Speak softly and carry a Gigabit switch. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 13:22:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id B665D37C322 for ; Fri, 7 Jul 2000 13:22:06 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 77460 invoked by uid 1000); 7 Jul 2000 20:15:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 20:15:21 -0000 Date: Fri, 7 Jul 2000 15:15:21 -0500 (CDT) From: Mike Silbersack To: "Richard A. Steenbergen" Cc: Bosko Milekic , freebsd-net@FreeBSD.ORG Subject: Re: stuck in LAST_ACK In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Richard A. Steenbergen wrote: > The full LAST_ACK list was in a previous email, 4.0-STABLE, didn't think > the newreno stuff was an issue there. It's not newreno related, it's a fix that is related to sockets getting stuck in LAST_ACK when the system is low/out of mbufs. (And the patch has been mfc'd to 3 and 4.) How old is your -STABLE? The patch was added on June 8th or so. Although with your huge number of mbufs, I doubt you ran out an caused the situation. OTOH, the high number of mbufs/mbuf clusters you have is almost worrysome; a netkill on that box could eat up a LOT of memory, which won't get freed. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 13:31:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 3522137C558; Fri, 7 Jul 2000 13:29:28 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id OAA12959; Fri, 7 Jul 2000 14:29:00 -0600 (MDT) Date: Fri, 7 Jul 2000 14:28:59 -0600 (MDT) From: Nick Rogness To: Narvi Cc: Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Narvi wrote: > > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > > unobstructed. > > > > OK. So do bridged interfaces fall within the same collision > > domain?... or are they just members of the same broadcast domain? > > > > They can't be in the same collison domain - you'll realise it if you > think about it for a second. It is possible to span 2 collison domains across 1 VLAN...so yes they could be, if it were possible with FreeBSD (?IS it?) to put two ethernet cards in this setup: FreeBSD int1 int2 / \ / \ / \ switch1 switch2 If int1 and int2 were part of the same collision domain, then switch1 and switch2 would also be part of the same collosion domain and visa versa. This would be pretty cool to see happen, essentially making a VLAN switch (with Layer 3 capabilities). Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 14:16:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 983EE37C1D9; Fri, 7 Jul 2000 14:16:42 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA95711; Fri, 7 Jul 2000 17:16:14 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200007072116.RAA95711@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Rogness Cc: Narvi , Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: bridging References: In-reply-to: Your message of "Fri, 07 Jul 2000 14:28:59 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jul 2000 17:16:14 -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org They can't be in the same collision domain -- the only way to do that is to have an Ethernet repeater which repeats bit by bit fron one segment to another, and propagating a collision on one segment as a jam on another. On a FreeBSD box, where you interfaces to ethernet segments are NIC cards, you can't get your hands on the ethernet frame until the NIC has received it completely. Thus, you don't have to opportunity to act as a repeater (not that you'd want to anyway) to have a single collision domain. louie > On Fri, 7 Jul 2000, Narvi wrote: > > > > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > > > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > > > unobstructed. > > > > > > OK. So do bridged interfaces fall within the same collision > > > domain?... or are they just members of the same broadcast domain? > > > > > > > They can't be in the same collison domain - you'll realise it if you > > think about it for a second. > > It is possible to span 2 collison domains across 1 VLAN...so > yes they could be, if it were possible with FreeBSD (?IS it?) to > put two ethernet cards in this setup: > > FreeBSD > int1 int2 > / \ > / \ > / \ > switch1 switch2 > > If int1 and int2 were part of the same collision domain, then > switch1 and switch2 would also be part of the same collosion > domain and visa versa. This would be pretty cool to see happen, > essentially making a VLAN switch (with Layer 3 capabilities). > > > Nick Rogness > - Speak softly and carry a Gigabit switch. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 15: 6:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 0608737B6A7; Fri, 7 Jul 2000 15:06:39 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id QAA67245; Fri, 7 Jul 2000 16:06:23 -0600 (MDT) Date: Fri, 7 Jul 2000 16:06:23 -0600 (MDT) From: Nick Rogness To: "Louis A. Mamakos" Cc: Narvi , Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: <200007072116.RAA95711@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Louis A. Mamakos wrote: > They can't be in the same collision domain -- the only way to do that > is to have an Ethernet repeater which repeats bit by bit fron one > segment to another, and propagating a collision on one segment as a > jam on another. > > On a FreeBSD box, where you interfaces to ethernet segments are NIC > cards, you can't get your hands on the ethernet frame until the > NIC has received it completely. Thus, you don't have to opportunity > to act as a repeater (not that you'd want to anyway) to have a > single collision domain. You know, you are right...never thought it through completely before I sent my reply. Sorry everyone for the wasted bandwidth. Have 1 more question (has to do with this bridging deal): Anyone working on load-sharing/load-balancing or clustering network solution with FreeBSD? Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 15:28:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 0C34337BDD0 for ; Fri, 7 Jul 2000 15:28:23 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FXC009Z6MBFYJ@falla.videotron.net> for freebsd-net@FreeBSD.ORG; Fri, 7 Jul 2000 18:26:03 -0400 (EDT) Date: Fri, 07 Jul 2000 18:28:12 -0400 (EDT) From: Bosko Milekic Subject: Re: stuck in LAST_ACK In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Mike Silbersack Cc: "Richard A. Steenbergen" , freebsd-net@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Mike Silbersack wrote: > > On Fri, 7 Jul 2000, Richard A. Steenbergen wrote: > > > The full LAST_ACK list was in a previous email, 4.0-STABLE, didn't think > > the newreno stuff was an issue there. > > It's not newreno related, it's a fix that is related to sockets getting > stuck in LAST_ACK when the system is low/out of mbufs. (And the patch has > been mfc'd to 3 and 4.) > > How old is your -STABLE? The patch was added on June 8th or so. Although > with your huge number of mbufs, I doubt you ran out an caused the > situation. Hmm, maybe if the system tries to allocate an mbuf, has none on mmbfree, calls m_mballoc(), which calls kmem_malloc(), which cannot eventually allocate a physical page, where (how) == M_DONTWAIT == M_NOWAIT, which returns NULL, and the code cannot sleep as (how) == M_DONWAIT, so you get NULL back and get into the problematic case if this is a prior-June 8th-fix -STABLE. > > OTOH, the high number of mbufs/mbuf clusters you have is almost > worrysome; a netkill on that box could eat up a LOT of memory, which won't > get freed. Yes, another reason to look into the mbuf subsystem free pages patch. > > Mike "Silby" Silbersack > > > > > -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 7 23:21: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2823337B8A1; Fri, 7 Jul 2000 23:21:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA12582; Fri, 7 Jul 2000 23:21:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 7 Jul 2000 23:21:06 -0700 (PDT) From: Kris Kennaway To: Len Conrad Cc: freebsd-net@FreeBSD.ORG Subject: Hardware crypto (Re: KAME stable 20000704) In-Reply-To: <4.3.2.7.2.20000707162836.03d4ead0@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Len Conrad wrote: > Are there any hardware-encryption boards for KAME or OpenSSL? Bill Paul is looking at this for FreeBSD. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jul 8 0:39:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from ns3.khmere.com (d83b56af.dsl.flashcom.net [216.59.86.175]) by hub.freebsd.org (Postfix) with ESMTP id 2293237B66D; Sat, 8 Jul 2000 00:39:06 -0700 (PDT) (envelope-from nathan@khmere.com) Received: from khmere.com (ns2.khmere.com [216.59.86.176]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id AAA05751; Sat, 8 Jul 2000 00:42:21 -0700 (PDT) Message-ID: <39673C7E.ED9D9D21@khmere.com> Date: Sat, 08 Jul 2000 07:36:46 -0700 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i586) X-Accept-Language: en MIME-Version: 1.0 To: "hackers@FreeBSD.ORG" , "freebsd-net@FreeBSD.ORG" Subject: loader help !! (bug ??) 4.0-STABLE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for the re-post but not reponse !! I have FreeBSD 4.0-STABLE on i386, was -RELEASE ) What I am trying to do is nfs root boot from the loader (?) I do: ok> unload kernel ok> load diskless_kernel ok> set kernel=diskless_kernel ok> boot -r -h Now what I understand is the -r flag will tell the kernel to overide the rootdev and use the "staticly linked device" from when you made the kernel (this would be the BOOTP_NFSROOT option ?) Now my kernel (the diskless_kernel ) is a diskless kernel ( with BOOTP, NFS_ROOT .... etc.. ) compiled in. But when I boot like this is just tries to mount /dev/ad0s1a ... (normal device ) even though it gets the proper reply from the bootp server that its rootfs= it even prints : rootfs is Mounting root from ufs:/dev/ad0s1a but still mounts the ufs ! How do if force it to boot root fs on nfs ? I have tried to do a boot -a then when I prompts me for root fs I enter the proper nfs mount and for RELEASE it would boot diskless but for STABLE is fails !! I have tried to : ok> set rootdev=nfs: ok> boot -h ok> can't determine root device I have also passed it various kernel flags and env options... (mybe wrong ones ... ? ) how do I have the kernel to load the rootfs = nfs root instead of use the currdev ? What does etherboot do when it loads the kernel ? does it pass it special parameters ?? If you are wondering why I just don't boot from etherboot ....etc...(I do ) but... I want to be able to boot my remote systems without a floppie and chose how to boot from loader (via serail console ...I don't have serial access for the bios but I can get serial console with FreeBSD !! ). Either default (use local drive) or load the diskless kernel , then boot diskless. This way I almost the same options ..... and maybe automate it... Any help would be great !! thank you kindly.... nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jul 8 19: 1:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 3AB2B37BE3E; Sat, 8 Jul 2000 19:01:26 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id LAA29286; Sun, 9 Jul 2000 11:01:24 +0900 (JST) To: net@freebsd.org Cc: jlemon@freebsd.org Subject: repair IPv6 allmulti X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net Date: Sun, 09 Jul 2000 11:01:24 +0900 Message-ID: <29284.963108084@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org IPV6_JOIN_GROUP to :: (all-zero IPv6 address, meaning "all multi") has been broken for the following platforms: FreeBSD 4.0-RELEASE (and STABLE) FreeBSD-current KAME/FreeBSD 4.0 Basically what we need is a behavior similar to original BSD in_addmulti(), in in6_addmulti(). if we join all-zero address, we need a join to all multicast. FreeBSD multicast code removed this semantics (all-zero means all multi) somewhere between 2.x and 3.x. we have been using the following in KAME/FreeBSD 3.x. i'd like to bring it into FreeBSD-current. (adding all-zero case into ether_resolvemulti) without this, we need a code duplicate of if_addmulti() into in6_addmulti(), which is a maintenance headache (also as i don't know about freebsd multicast code too well, i can't handle it). itojun Index: if_ethersubr.c =================================================================== RCS file: /cvsroot/kame/kame/freebsd4/sys/net/if_ethersubr.c,v retrieving revision 1.4 diff -c -r1.4 if_ethersubr.c *** if_ethersubr.c 2000/04/28 14:00:03 1.4 --- if_ethersubr.c 2000/07/09 01:58:15 *************** *** 808,813 **** --- 808,823 ---- #ifdef INET6 case AF_INET6: sin6 = (struct sockaddr_in6 *)sa; + if (IN6_IS_ADDR_UNSPECIFIED(&sin6->sin6_addr)) { + /* + * An IP6 address of 0 means listen to all + * of the Ethernet multicast address used for IP6. + * (This is used for multicast routers.) + */ + ifp->if_flags |= IFF_ALLMULTI; + *llsa = 0; + return 0; + } if (!IN6_IS_ADDR_MULTICAST(&sin6->sin6_addr)) return EADDRNOTAVAIL; MALLOC(sdl, struct sockaddr_dl *, sizeof *sdl, M_IFMADDR, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jul 8 22:22:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1879137B6EB; Sat, 8 Jul 2000 22:22:27 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA12359; Sat, 8 Jul 2000 23:22:26 -0600 (MDT) (envelope-from ken) Date: Sat, 8 Jul 2000 23:22:26 -0600 From: "Kenneth D. Merry" To: net@FreeBSD.ORG Subject: new zero copy sockets and NFS patches Message-ID: <20000708232226.A12332@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ -arch and -current BCC'ed for wider coverage, please direct followups to -net and/or me ] I have put a new copy of the zero copy sockets and NFS patches, against -current as of early July 8th, 2000, here: http://people.FreeBSD.ORG/~ken/zero_copy/ Feedback would be very welcome, we haven't gotten much response on this yet. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - There was a potential panic caused by a bug in the driver side of the header splitting code. The bug only popped up with non-split packets that were long enough to fill up a mbuf. This generally meant IP fragments with a non-zero fragment offset, usually generated by NFS reads. Essentially the length of the initial receive buffer in the mbuf chain was overstated by two bytes, which caused the next mbuf pointer in the next contiguous mbuf to get partially overwritten. That could cause a panic in some situations. Thanks to Drew Gallatin for tracking this one down. - We now do header splitting on IP fragments with a fragment offset greater than 0. Thanks to Justin Gibbs for the idea. - The Tigon driver now loads and unloads cleanly. Thanks to Drew Gallatin for getting this working. - Outgoing IP fragments are now generated in page-multiple chunks if the outgoing interface's MTU is greater than a page in size. This helps receive-side bandwidth NFS significantly, since page flipping techniques can be used. Thanks to Drew Gallatin for this performance enhancement. Also, there are some new benchmark results in the benchmarks section of the web page -- Drew Gallatin has achieved 986Mbps TCP throughput with netperf, and 100MB/sec throughput over NFS. See the web page for a more detailed explanation of the hardware, conditions, etc. For those of you who missed the first message about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Two sets of zero copy send code, written by Drew Gallatin and Robert Picco . - Zero copy receive code, written by Drew Gallatin. - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jul 8 22:41: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 732D137BFD8 for ; Sat, 8 Jul 2000 22:41:04 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 88650 invoked by uid 1000); 9 Jul 2000 05:41:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Jul 2000 05:41:01 -0000 Date: Sun, 9 Jul 2000 00:41:01 -0500 (CDT) From: Mike Silbersack To: "Kenneth D. Merry" Cc: net@FreeBSD.ORG Subject: Re: new zero copy sockets and NFS patches In-Reply-To: <20000708232226.A12332@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 8 Jul 2000, Kenneth D. Merry wrote: > http://people.FreeBSD.ORG/~ken/zero_copy/ > > Feedback would be very welcome, we haven't gotten much response on this > yet. Please put up graphs showing the performance increase; it's difficult to understand the results you've posted so far, which may explain the general lack of excitement. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jul 8 22:50:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0F1BF37C0BA for ; Sat, 8 Jul 2000 22:50:22 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA12627; Sat, 8 Jul 2000 23:50:14 -0600 (MDT) (envelope-from ken) Date: Sat, 8 Jul 2000 23:50:14 -0600 From: "Kenneth D. Merry" To: Mike Silbersack Cc: net@FreeBSD.ORG Subject: Re: new zero copy sockets and NFS patches Message-ID: <20000708235014.A12542@panzer.kdm.org> References: <20000708232226.A12332@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from silby@silby.com on Sun, Jul 09, 2000 at 12:41:01AM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 09, 2000 at 00:41:01 -0500, Mike Silbersack wrote: > On Sat, 8 Jul 2000, Kenneth D. Merry wrote: > > > http://people.FreeBSD.ORG/~ken/zero_copy/ > > > > Feedback would be very welcome, we haven't gotten much response on this > > yet. > > Please put up graphs showing the performance increase; it's difficult to > understand the results you've posted so far, which may explain the general > lack of excitement. True enough, graphs help. Check out this paper: http://www.cs.duke.edu/ari/publications/end-system.pdf It is linked off the Trapeze publications page: http://www.cs.duke.edu/ari/publications/publications.html The above paper covers the performance benefits of zero copy, checksum offloading, larger MTUs, etc., and includes several graphs demonstrating the effect of those optimizations. The zero copy code used there is pretty much the same as the patches above. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message