From owner-freebsd-net Sun Sep 23 2:36:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 51CE037B416 for ; Sun, 23 Sep 2001 02:36:18 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id FAA73528 for ; Sun, 23 Sep 2001 05:36:17 -0400 (EDT) Date: Sun, 23 Sep 2001 05:36:17 -0400 (EDT) From: "Matthew N. Dodd" To: freebsd-net@freebsd.org Subject: review request. Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1070860394-1001237777=:3806" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1070860394-1001237777=:3806 Content-Type: TEXT/PLAIN; charset=US-ASCII sys/net/if.c and bpf.c have problems with if_detach() and bpfdetach() when they are called with a struct ifnet that has not had if_attach() and bpfattach() called on it. Null pointer reference -> *boom* etc. This patch fixes the test already present in bpfdetach() and adds a test to if_detach(). Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | --0-1070860394-1001237777=:3806 Content-Type: TEXT/plain; name="diff.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="diff.txt" SW5kZXg6IGlmLmMNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxl OiAvY3ZzL3NyYy9zeXMvbmV0L2lmLmMsdg0KcmV0cmlldmluZyByZXZpc2lv biAxLjExNg0KZGlmZiAtdSAtcjEuMTE2IGlmLmMNCi0tLSBpZi5jCTE4IFNl cCAyMDAxIDE3OjQxOjQyIC0wMDAwCTEuMTE2DQorKysgaWYuYwkyMyBTZXAg MjAwMSAwOToxNzoxMSAtMDAwMA0KQEAgLTI0OCw2ICsyNDgsMTQgQEANCiAJ ICogUmVtb3ZlIHJvdXRlcyBhbmQgZmx1c2ggcXVldWVzLg0KIAkgKi8NCiAJ cyA9IHNwbG5ldCgpOw0KKw0KKwlpZiAoaWZwLT5pZl9pbmRleCA9PSAwKSB7 DQorCQlzcGx4KHMpOw0KKwkJcHJpbnRmKCJpZl9kZXRhY2g6ICVzJWQgd2Fz IG5vdCBhdHRhY2hlZFxuIiwgaWZwLT5pZl9uYW1lLA0KKwkJICAgIGlmcC0+ aWZfdW5pdCk7DQorCQlyZXR1cm47DQorCX0NCisNCiAJaWZfZG93bihpZnAp Ow0KIA0KIAkvKg0KSW5kZXg6IGJwZi5jDQo9PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09DQpSQ1MgZmlsZTogL2N2cy9zcmMvc3lzL25ldC9icGYuYyx2DQpyZXRy aWV2aW5nIHJldmlzaW9uIDEuODINCmRpZmYgLXUgLXIxLjgyIGJwZi5jDQot LS0gYnBmLmMJMjEgU2VwIDIwMDEgMjI6NDY6NTQgLTAwMDAJMS44Mg0KKysr IGJwZi5jCTIzIFNlcCAyMDAxIDAzOjU4OjA0IC0wMDAwDQpAQCAtMTI2NCw3 ICsxMjY0LDcgQEANCiAJfQ0KIA0KIAkvKiBJbnRlcmZhY2Ugd2Fzbid0IGF0 dGFjaGVkICovDQotCWlmIChicC0+YmlmX2lmcCA9PSBOVUxMKSB7DQorCWlm IChicCA9PSBOVUxMKSB7DQogCQltdHhfdW5sb2NrKCZicGZfbXR4KTsNCiAJ CXByaW50ZigiYnBmZGV0YWNoOiAlcyVkIHdhcyBub3QgYXR0YWNoZWRcbiIs IGlmcC0+aWZfbmFtZSwNCiAJCSAgICBpZnAtPmlmX3VuaXQpOw0K --0-1070860394-1001237777=:3806-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 2:54: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from amsfep14-int.chello.nl (amsfep14-int.chello.nl [213.46.243.21]) by hub.freebsd.org (Postfix) with ESMTP id 051E337B41D for ; Sun, 23 Sep 2001 02:53:58 -0700 (PDT) Received: from daemon.chronias.ninth-circle.org ([62.163.96.180]) by amsfep14-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20010923094958.RCO25701.amsfep14-int.chello.nl@daemon.chronias.ninth-circle.org>; Sun, 23 Sep 2001 11:49:58 +0200 Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.3/8.11.3) id f8N9l8R25554; Sun, 23 Sep 2001 11:47:08 +0200 (CEST) (envelope-from asmodai) Date: Sun, 23 Sep 2001 11:47:08 +0200 From: Jeroen Ruigrok/Asmodai To: "Matthew N. Dodd" Cc: freebsd-net@freebsd.org Subject: Re: review request. Message-ID: <20010923114707.H4995@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.19i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -On [20010923 11:38], Matthew N. Dodd (winter@jurai.net) wrote: >sys/net/if.c and bpf.c have problems with if_detach() and >bpfdetach() when they are called with a struct ifnet that has not had >if_attach() and bpfattach() called on it. Null pointer reference -> >*boom* etc. > >This patch fixes the test already present in bpfdetach() and adds a test >to if_detach(). Patch looks sane to me. Basically it is a combination of asserting and defensive programming, which never hurts. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|freebsd.org|xmach.org] Documentation nutter/C-rated Coder, finger asmodai@ninth-circle.dnsalias.net http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ At the End of the Rainbow, with Gold in our hands... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 10:43:22 2001 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 295E337B419 for ; Sun, 23 Sep 2001 10:43:20 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8NHE5080834; Sun, 23 Sep 2001 12:14:05 -0500 (CDT) (envelope-from jlemon) Date: Sun, 23 Sep 2001 12:14:05 -0500 (CDT) From: Jonathan Lemon Message-Id: <200109231714.f8NHE5080834@prism.flugsvamp.com> To: winter@jurai.net, net@freebsd.org Subject: Re: review request. X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article you write: >-=-=-=-=-=- > >sys/net/if.c and bpf.c have problems with if_detach() and >bpfdetach() when they are called with a struct ifnet that has not had >if_attach() and bpfattach() called on it. Null pointer reference -> >*boom* etc. I would say that this is to be expected. Why is the system calling the detach functions on a device that isn't attached in the first place? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 13:32:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from cs.earlham.edu (cs.earlham.edu [159.28.230.3]) by hub.freebsd.org (Postfix) with ESMTP id DB6C637B408 for ; Sun, 23 Sep 2001 13:32:42 -0700 (PDT) Received: from quark.cs.earlham.edu (quark.cs.earlham.edu [159.28.230.3]) by cs.earlham.edu (8.11.3/8.11.1) with ESMTP id f8NKWgc02418 for ; Sun, 23 Sep 2001 15:32:42 -0500 (EST) (envelope-from hassan@cs.earlham.edu) Date: Sun, 23 Sep 2001 15:32:42 -0500 (EST) From: Hassan Halta To: Subject: ypserv Problems Message-ID: <20010923152458.U2098-100000@quark.cs.earlham.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, We have been getting these bizarre errors with ypserv. "res_mkquery failed" and the message keeps repeating itself in the messages file over and over again. We were thinking about Renewing our version of NIS or Bind. We just installed FreeBSD 4.3 and it seems that its version of NIS or Bind is misbehaving! I don't really know what's the problem. I would really appreciate it if someone helps us out with this issue. Thanjs a lot. -Hassan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 15:46:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [209.98.56.21]) by hub.freebsd.org (Postfix) with ESMTP id 8308E37B41E for ; Sun, 23 Sep 2001 15:46:10 -0700 (PDT) Received: from twinstar (twinstar.grasslake.net [192.168.30.2]) by accord.grasslake.net (8.11.6/8.11.6) with SMTP id f8NMdmX00476 for ; Sun, 23 Sep 2001 17:39:49 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <001201c14482$4b2d45e0$021ea8c0@twinstar> From: "Shawn Barnhart" To: Subject: IPSec problem, racoon can't transmit? Date: Sun, 23 Sep 2001 17:51:33 -0500 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm trying to setup an IPSec connection between two machines, A 10.10.10.1 and B 192.168.1.1 (real IPs are being used, there are just examples): I used the following commands: On Machine A (10.10.10.1): setkey -c spdadd 10.10.10.1/32 192.168.1.1/32 any -P out ipsec esp/transport/10.10.10.1-192.168.1.1/require; spdadd 192.168.1.1/32 10.10.10.1/32 any -P in ipsec esp/transport/192.168.1.1-10.10.10.1/require; ^D On Machine B (192.168.1.1): setkey -c spdadd 192.168.1.1/32 10.10.10.1/32 any -P out ipsec esp/transport/192.168.1.1-10.10.10.1/require; spdadd 10.10.10.1/32 192.168.1.1/32 any -P in ipsec esp/transport/10.10.10.1-192.168.1.1/require; ^D I have a vanilla racoon.conf and psk.txt (mode 600) on both machines. When I start racoon on both machines, all appears fine. To make a long story short, Machine A never seems to generate ANY isakmp packets. Machine B's racoon run-time info never indicates it's gotten a phase I initiation from A if the session was originated from A. I've run tcpdump on both machines, and A never sends any isakmp packets, although it does get them from B if B originates traffic first and appears to generate a response according to racoon debug info, but B never gets the responses (and if tcpdump is to believed A never sends them). Both machines are running racoon-20010831a and 4.4-STABLE built yesterday. What would cause this? I have good communication with these hosts without IPSec, I can originate ssh sessions and other traffic without problems. Can I use racoon with a security policy that requires encrypted traffic between these hosts? It almost seems like a catch-22: can't do key exchange traffic without encryption, and can't get encryption without key exchange, and ... What am I missing? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 16:32:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 49BA237B439 for ; Sun, 23 Sep 2001 16:32:23 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA84390; Sun, 23 Sep 2001 19:32:18 -0400 (EDT) Date: Sun, 23 Sep 2001 19:32:18 -0400 (EDT) From: "Matthew N. Dodd" To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: review request. In-Reply-To: <200109231714.f8NHE5080834@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 23 Sep 2001, Jonathan Lemon wrote: > >sys/net/if.c and bpf.c have problems with if_detach() and > >bpfdetach() when they are called with a struct ifnet that has not had > >if_attach() and bpfattach() called on it. Null pointer reference -> > >*boom* etc. > > I would say that this is to be expected. Why is the system calling > the detach functions on a device that isn't attached in the first > place? Driver mistake, but I see no reason why these functions shouldn't handle this gracefully. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 16:41: 8 2001 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 6572E37B41F for ; Sun, 23 Sep 2001 16:41:06 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8NNd9Y01766; Sun, 23 Sep 2001 18:39:09 -0500 (CDT) (envelope-from jlemon) Date: Sun, 23 Sep 2001 18:39:09 -0500 From: Jonathan Lemon To: "Matthew N. Dodd" Cc: Jonathan Lemon , net@freebsd.org Subject: Re: review request. Message-ID: <20010923183909.A79251@prism.flugsvamp.com> References: <200109231714.f8NHE5080834@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Sep 23, 2001 at 07:32:18PM -0400, Matthew N. Dodd wrote: > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > >sys/net/if.c and bpf.c have problems with if_detach() and > > >bpfdetach() when they are called with a struct ifnet that has not had > > >if_attach() and bpfattach() called on it. Null pointer reference -> > > >*boom* etc. > > > > I would say that this is to be expected. Why is the system calling > > the detach functions on a device that isn't attached in the first > > place? > > Driver mistake, but I see no reason why these functions shouldn't handle > this gracefully. Because all it does is conceal the original error. Better to catch the mistake and fix the driver than paper it over. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 16:53:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 219DF37B401 for ; Sun, 23 Sep 2001 16:53:23 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA85217; Sun, 23 Sep 2001 19:53:20 -0400 (EDT) Date: Sun, 23 Sep 2001 19:53:20 -0400 (EDT) From: "Matthew N. Dodd" To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: review request. In-Reply-To: <20010923183909.A79251@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 23 Sep 2001, Jonathan Lemon wrote: > On Sun, Sep 23, 2001 at 07:32:18PM -0400, Matthew N. Dodd wrote: > > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > > >sys/net/if.c and bpf.c have problems with if_detach() and > > > >bpfdetach() when they are called with a struct ifnet that has not had > > > >if_attach() and bpfattach() called on it. Null pointer reference -> > > > >*boom* etc. > > > > > > I would say that this is to be expected. Why is the system calling > > > the detach functions on a device that isn't attached in the first > > > place? > > > > Driver mistake, but I see no reason why these functions shouldn't handle > > this gracefully. > > Because all it does is conceal the original error. Better to catch > the mistake and fix the driver than paper it over. Right; rather than failing the detach routines will fuss about it so you know exactly how you screwed up. I don't see this papering anything over. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 23 17: 5:49 2001 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 C8A6F37B42C for ; Sun, 23 Sep 2001 17:05:44 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8O03kL02988; Sun, 23 Sep 2001 19:03:46 -0500 (CDT) (envelope-from jlemon) Date: Sun, 23 Sep 2001 19:03:46 -0500 From: Jonathan Lemon To: "Matthew N. Dodd" Cc: Jonathan Lemon , net@freebsd.org Subject: Re: review request. Message-ID: <20010923190346.B79251@prism.flugsvamp.com> References: <20010923183909.A79251@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Sep 23, 2001 at 07:53:20PM -0400, Matthew N. Dodd wrote: > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > On Sun, Sep 23, 2001 at 07:32:18PM -0400, Matthew N. Dodd wrote: > > > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > > > >sys/net/if.c and bpf.c have problems with if_detach() and > > > > >bpfdetach() when they are called with a struct ifnet that has not had > > > > >if_attach() and bpfattach() called on it. Null pointer reference -> > > > > >*boom* etc. > > > > > > > > I would say that this is to be expected. Why is the system calling > > > > the detach functions on a device that isn't attached in the first > > > > place? > > > > > > Driver mistake, but I see no reason why these functions shouldn't handle > > > this gracefully. > > > > Because all it does is conceal the original error. Better to catch > > the mistake and fix the driver than paper it over. > > Right; rather than failing the detach routines will fuss about it so you > know exactly how you screwed up. I don't see this papering anything over. Because this is not a normal operational error. If anything, the statement should be a KASSERT(), but I don't really see the need for it. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 1:19:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 748FF37B412 for ; Mon, 24 Sep 2001 01:19:45 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id EAA96969; Mon, 24 Sep 2001 04:19:42 -0400 (EDT) Date: Mon, 24 Sep 2001 04:19:42 -0400 (EDT) From: "Matthew N. Dodd" To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: review request. In-Reply-To: <20010923190346.B79251@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > Right; rather than failing the detach routines will fuss about it so you > > know exactly how you screwed up. I don't see this papering anything over. > > Because this is not a normal operational error. If anything, the > statement should be a KASSERT(), but I don't really see the need for it. bpfdetach() already has a test for this case; adding one to if_detach() doesn't seem like a bad thing so long as abusing if_index isn't a problem. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 4:42:49 2001 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 A8D3037B40D for ; Mon, 24 Sep 2001 04:42:38 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f8OBer060394; Mon, 24 Sep 2001 14:40:53 +0300 (EEST) (envelope-from ru) Date: Mon, 24 Sep 2001 14:40:53 +0300 From: Ruslan Ermilov To: Jonathan Lemon Cc: "Matthew N. Dodd" , net@FreeBSD.ORG Subject: Re: review request. Message-ID: <20010924144053.G50028@sunbay.com> References: <20010923183909.A79251@prism.flugsvamp.com> <20010923190346.B79251@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010923190346.B79251@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Sun, Sep 23, 2001 at 07:03:46PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Seconded. This should be a KASSERT() if at all. If that counts. :-) On Sun, Sep 23, 2001 at 07:03:46PM -0500, Jonathan Lemon wrote: > On Sun, Sep 23, 2001 at 07:53:20PM -0400, Matthew N. Dodd wrote: > > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > > On Sun, Sep 23, 2001 at 07:32:18PM -0400, Matthew N. Dodd wrote: > > > > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > > > > >sys/net/if.c and bpf.c have problems with if_detach() and > > > > > >bpfdetach() when they are called with a struct ifnet that has not had > > > > > >if_attach() and bpfattach() called on it. Null pointer reference -> > > > > > >*boom* etc. > > > > > > > > > > I would say that this is to be expected. Why is the system calling > > > > > the detach functions on a device that isn't attached in the first > > > > > place? > > > > > > > > Driver mistake, but I see no reason why these functions shouldn't handle > > > > this gracefully. > > > > > > Because all it does is conceal the original error. Better to catch > > > the mistake and fix the driver than paper it over. > > > > Right; rather than failing the detach routines will fuss about it so you > > know exactly how you screwed up. I don't see this papering anything over. > > Because this is not a normal operational error. If anything, the > statement should be a KASSERT(), but I don't really see the need for it. > -- > Jonathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- 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 Sep 24 8:24:58 2001 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 1804237B41A for ; Mon, 24 Sep 2001 08:24:53 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8OFOcB67483; Mon, 24 Sep 2001 11:24:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 24 Sep 2001 11:24:38 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Matthew N. Dodd" Cc: freebsd-net@freebsd.org Subject: Re: review request. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'd be happy to see a KASSERT() dropped in there--the type of bug this is probably intended to address is a reversed set of procedures during interface cleanup, or multiple invocation. In SMPng, the failure modes for this kind of error situation will be a lot less forgiving (especially with regards to potential races), and as such we want to find those failures early, rather than let them slip through. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sun, 23 Sep 2001, Matthew N. Dodd wrote: > sys/net/if.c and bpf.c have problems with if_detach() and > bpfdetach() when they are called with a struct ifnet that has not had > if_attach() and bpfattach() called on it. Null pointer reference -> > *boom* etc. > > This patch fixes the test already present in bpfdetach() and adds a test > to if_detach(). > > Thanks. > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 8:37:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1D56B37B403 for ; Mon, 24 Sep 2001 08:37:34 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Sep 2001 16:37:33 +0100 (BST) To: freebsd-net@freebsd.org Subject: bootpd and "Maximum DHCP Message Size" option. Date: Mon, 24 Sep 2001 16:37:33 +0100 From: Ian Dowse Message-ID: <200109241637.aa38673@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I came across a problem recently when using Etherboot with FreeBSD's bootpd. Etherboot was specifying a "Maximum DHCP Message Size" of 1500, which caused bootpd to generate a reply larger than the MTU, and Etherboot can't handle fragments. As pointed out by Ken Yap on the Etherboot mailing list, the description in RFC2132 of the Maximum DHCP Message Size option is slightly ambiguous: 9.10. Maximum DHCP Message Size This option specifies the maximum length DHCP message that it is willing to accept. The length is specified as an unsigned 16-bit integer. A client may use the maximum DHCP message size option in DHCPDISCOVER or DHCPREQUEST messages, but should not use the option in DHCPDECLINE messages. The code for this option is 57, and its length is 2. The minimum legal value is 576 octets. The problem is that it doesn't seem to specify whether this size refers to the length of the DHCP message in the UDP payload, or the full length of the packet. Etherboot assumes the latter, but FreeBSD's bootpd assumes the former. The isc-dhcpd code takes the safest option, and ensures that the full Ethernet packet is no longer than the client-specified maximum message length. Below is a patch that makes bootpd do the same. Any objections if I commit this? Ian Index: bootp.h =================================================================== RCS file: /dump/FreeBSD-CVS/src/libexec/bootpd/bootp.h,v retrieving revision 1.5 diff -u -r1.5 bootp.h --- bootp.h 12 Nov 1999 10:11:48 -0000 1.5 +++ bootp.h 24 Sep 2001 15:05:37 -0000 @@ -38,6 +38,8 @@ #define BP_FILE_LEN 128 #define BP_VEND_LEN 64 #define BP_MINPKTSZ 300 /* to check sizeof(struct bootp) */ +/* Overhead to fit a bootp message into an Ethernet packet. */ +#define BP_MSG_OVERHEAD (14 + 20 + 8) /* Ethernet + IP + UDP headers */ struct bootp { unsigned char bp_op; /* packet opcode type */ Index: bootpd.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/libexec/bootpd/bootpd.c,v retrieving revision 1.14 diff -u -r1.14 bootpd.c --- bootpd.c 9 Dec 2000 09:35:33 -0000 1.14 +++ bootpd.c 24 Sep 2001 15:04:51 -0000 @@ -1292,10 +1292,10 @@ p += len; } - if (msgsz > sizeof(*bp)) { + if (msgsz > sizeof(*bp) + BP_MSG_OVERHEAD) { if (debug > 1) report(LOG_INFO, "request has DHCP msglen=%d", msgsz); - pktlen = msgsz; + pktlen = msgsz - BP_MSG_OVERHEAD; } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 9:17:54 2001 Delivered-To: freebsd-net@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id CE96337B412; Mon, 24 Sep 2001 09:17:48 -0700 (PDT) Received: from hbo (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with SMTP id f8OGHZC25209; Mon, 24 Sep 2001 09:17:35 -0700 (PDT) From: "Lars Eggert" To: "Brian Somers" Cc: , Subject: Solution (RE: VPN client with mpd) Date: Mon, 24 Sep 2001 09:17:35 -0800 MIME-Version: 1.0 Message-ID: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_004D_01C144D9.BF7459F0" In-Reply-To: <200109222035.f8MKZkR34433@hak.lan.Awfulhak.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_004D_01C144D9.BF7459F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Thanks to Archie and Brian, I now have a working PPTP tunnel up. Here's what I changed from the example vpn configuration included in the mpd package in /usr/local/etc/mpd/mpd.conf, I thought I'd document this in case someone else runs accross the same problem: 1. Remove the "set iface addrs" line, addresses are assigned during negotiation. 2. Change the "set iface route" to whatever you'd like to route through the tunnel. I only route everything destined to my work subnet there. 3. Change the "set bundle authname" and "set bundle password" lines. Obviously. 4. Change "set link yes chap" to "set link allow chap". Both Archie and Brian suggested this; with the change, mpd will allow negotiation with remote peers that do not want to CHAP-authenticate themselves (like my remote VPN servers, it seems). 5. Change the local end range in the "set ipcp ranges" line to 0.0.0.0/0, to accept any tunnel endpoint address the server assigns us. Change the server address range to something meaningful (my server picks its virtual address out of a single class C, for example). 6. Uncomment all the lines below the commment about MPPE encryption. 7. Change the "mpd.links" file to point to the correct remote VPN server. Bingo! Connection established. The only remaining problem is that a few RAS servers (e.g., some Cisco box we're evaluating) seem to propose their own physical address as a virtual tunnel address. This causes an encapsulation loop resulting in a kernel panic. The Windows PPTP client avoids this problem; I wonder if a simple check in mpd that would reject physical addresses proposed as tunnel ends during negotiation may do the trick? Other servers, however, work fine with the above configuration. Thanks again to Brian and Archie, Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California ------=_NextPart_000_004D_01C144D9.BF7459F0 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIF5jCCArUw ggIeoAMCAQICAwWBRzANBgkqhkiG9w0BAQIFADCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsT FENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAw MC44LjMwMB4XDTAxMDgyNDE2NDAwMFoXDTAyMDgyNDE2NDAwMFowVDEPMA0GA1UEBBMGRWdnZXJ0 MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2VydDEcMBoGCSqGSIb3DQEJARYNbGFy c2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0AvLBsD78nxcUHeHkaMgl3b4 qYPnfgbf8Lh+HQP8RgGMRG/Yb+vTpkGezlwt9pkJxiD11uZDy4CNNJUu3gKxKSb+zRV70O+lkwwf tuHoLHoH4xwo3LcQ2LGDpd+I95tUN4dfJ3TmeEcUSF50dC/SuUI4w8AlhXQ8IxrhgdayTpECAwEA AaNWMFQwKgYFK2UBBAEEITAfAgEAMBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREE ETAPgQ1sYXJzZUBpc2kuZWR1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAheZhn0pQ A8zI7U2K1ZIAl11j0a1DKxnp3GtTvOUrGRB3WvYxidvdZ1kizhEsWeXU81TkNDH0DaRqtOEeu6Q2 OhB+jeKEqY7IDAJE4/fI0e+d6PnG1hd+vEvYmsKHkmzBhPc94XUOKNWO+qVNP2NGyNI3QIDy5wX4 fdcOo1S34r4wggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEV MBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0 ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQw IgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNv bmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcNMDIwODI5MjM1OTU5WjCB kjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQD Ex9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNEKYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y 8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtU ihOH/7ObnUlmAC0JieyUa+mhaQIDAQABo04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJp dmF0ZUxhYmVsMS0yOTcwEgYDVR0TAQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcN AQEEBQADgYEAcxtvJmWL/xU0S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONnt UPQ6bDSSrOaSnG7BIwHCCafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2 lhglTWr0ncXDkS+plrgFPFL83eliA0gxggKqMIICpgIBATCBmjCBkjELMAkGA1UEBhMCWkExFTAT BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUx HTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFp bCBSU0EgMjAwMC44LjMwAgMFgUcwCQYFKw4DAhoFAKCCAWUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3 DQEHATAcBgkqhkiG9w0BCQUxDxcNMDEwOTI0MTcxNzM1WjAjBgkqhkiG9w0BCQQxFgQUyNf6yo++ okC6/ar5IoQgdmR5FocwWAYJKoZIhvcNAQkPMUswSTAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgIC AIAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwBwYFKw4DAhowCgYIKoZIhvcNAgUwgasGCSsGAQQB gjcQBDGBnTCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UE BxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZp Y2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMFgUcwDQYJKoZI hvcNAQEBBQAEgYC6lxkzcIcEG4L5W23g/fAdkWeODVehmxN2LwD717/Fd1WuLCo1RyTemnsyEN+q pOAP+RFNlZ9kFfvy4y9QNagaHFAN+QWb1rgRQKrB+b1QRTIk4/LU/8EvDv0xday6eUQkRtGlBGrz TMK2lfsIDWEfqOuCRDOHMeg88QPoUcEb3AAAAAAAAA== ------=_NextPart_000_004D_01C144D9.BF7459F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 11:39:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail4.uunet.ca (mail4.uunet.ca [209.167.141.34]) by hub.freebsd.org (Postfix) with ESMTP id D7EBE37B420 for ; Mon, 24 Sep 2001 11:39:13 -0700 (PDT) Received: from alexdev ([207.176.248.4]) by mail4.uunet.ca with SMTP id <207585-26612>; Mon, 24 Sep 2001 14:39:11 -0400 From: "Alex Feldman" To: Subject: Ipv6 Date: Mon, 24 Sep 2001 14:36:30 -0400 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I update the driver to accept IPv6 address. When I configure interface for both IPv4 and IPv6, everything is good (I can ping), but when I'm using only IPv6, the remote machine not replying to my request. Is it some configuration problem? Or something else? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 11:48:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail4.uunet.ca (mail4.uunet.ca [209.167.141.34]) by hub.freebsd.org (Postfix) with ESMTP id 40A6637B40B; Mon, 24 Sep 2001 11:48:36 -0700 (PDT) Received: from alexdev ([207.176.248.4]) by mail4.uunet.ca with SMTP id <206777-28482>; Mon, 24 Sep 2001 14:48:28 -0400 From: "Alex Feldman" To: "Brian Whalen" Cc: , Subject: RE: IPv6 Date: Mon, 24 Sep 2001 14:45:46 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010924114424.P37147-100000@cx175057-a.ocnsd1.sdca.home.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org No, two machine configured back to back. Do you have any idea? Thank ypu Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 15:31:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from bg.sics.se (cpe-66-1-164-86.az.sprintbbd.net [66.1.164.86]) by hub.freebsd.org (Postfix) with ESMTP id 4F36937B41F; Mon, 24 Sep 2001 15:31:34 -0700 (PDT) Received: (from bg@localhost) by bg.sics.se (8.11.3/8.11.3) id f8OMVTi00679; Mon, 24 Sep 2001 15:31:29 -0700 (MST) (envelope-from bg) To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Cc: bg@sics.se Subject: Problems with IPsec and IPCOMP From: Bjoern Groenvall Date: 24 Sep 2001 15:31:28 -0700 Message-ID: Lines: 83 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am trying to enable IPCOMP between a FreeBSD 4.3(172.16.11.153=A) and a 4.2(172.16.11.8=B) machine. It seems like A produces compressed packets but B is unable to decompress them (see tcpdump log). Can somebody see what I'm doing wrong? Does anybody have an example configuration (that uses IPCOMP) that actually works? I would love to have such a configuration as a starting point. Cheers, Björn ------ The configuration # On both 172.16.11.153 and 172.16.11.8 setkey -c < 172.16.11.8: AH(spi=0x000003e9,seq=0x1): icmp: echo request 15:24:37.115322 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x1): icmp: echo reply 15:24:38.122541 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x2): icmp: echo request 15:24:38.122958 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x2): icmp: echo reply 15:24:39.132541 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x3): icmp: echo request 15:24:39.132959 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x3): icmp: echo reply 15:24:40.142557 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x4): icmp: echo request 15:24:40.142974 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x4): icmp: echo reply 15:24:48.796453 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x5): 1045 > 23: S 2680451051:2680451051(0) win 16384 (DF) [tos 0x10] 15:24:48.796936 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x5): 23 > 1045: S 2119201956:2119201956(0) ack 2680451052 win 17520 (DF) 15:24:48.797173 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x6): 1045 > 23: . ack 1 win 17520 (DF) [tos 0x10] 15:24:48.798584 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x7): 1045 > 23: P 1:37(36) ack 1 win 17520 (DF) [tos 0x10] 15:24:48.821877 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x6): 23 > 1045: P 1:4(3) ack 37 win 17484 (DF) [tos 0x10] 15:24:48.822139 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x8): 1045 > 23: . ack 4 win 17517 (DF) [tos 0x10] 15:24:48.822633 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x7): 23 > 1045: P 4:53(49) ack 37 win 17520 (DF) [tos 0x10] 15:24:48.822823 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x9): 1045 > 23: . ack 53 win 17471 (DF) [tos 0x10] 15:24:48.824418 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0xa): IPComp(cpi=0x0002) (DF) [tos 0x10] 15:24:49.823821 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0xb): IPComp(cpi=0x0002) (DF) [tos 0x10] 15:24:51.823787 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0xc): IPComp(cpi=0x0002) (DF) [tos 0x10] 15:24:55.823845 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0xd): IPComp(cpi=0x0002) (DF) [tos 0x10] 15:24:59.760189 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0xe): 1045 > 23: FP 127:128(1) ack 53 win 17520 (DF) [tos 0x10] 15:24:59.760622 172.16.11.8 > 172.16.11.153: AH(spi=0x000003e8,seq=0x8): 23 > 1045: . ack 37 win 17520 (DF) [tos 0x10] 15:25:03.824115 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0xf): IPComp(cpi=0x0002) (DF) [tos 0x10] 15:25:19.824283 172.16.11.153 > 172.16.11.8: AH(spi=0x000003e9,seq=0x10): IPComp(cpi=0x0002) (DF) [tos 0x10] ^C 27 packets received by filter 0 packets dropped by kernel # -- _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 19:15:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id AC66237B41F for ; Mon, 24 Sep 2001 19:15:29 -0700 (PDT) Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0108-Fujitsu Gateway) id LAA02630; Tue, 25 Sep 2001 11:15:24 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) From: tsuchiya@flab.fujitsu.co.jp Received: from const.kawasaki.flab.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0108-Fujitsu Domain Master) id LAA00892; Tue, 25 Sep 2001 11:15:24 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) Received: (from tsuchiya@localhost) by const.kawasaki.flab.fujitsu.co.jp (8.9.3+3.2W/3.5Wpl7) id LAA00788; Tue, 25 Sep 2001 11:15:26 +0900 Date: Tue, 25 Sep 2001 11:15:26 +0900 Message-Id: <200109250215.LAA00788@const.kawasaki.flab.fujitsu.co.jp> To: silby@silby.com, tsuchiya@flab.fujitsu.co.jp Subject: Re: TCP performance question Cc: net@FreeBSD.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > On Fri, 21 Sep 2001, Tsuchiya Yoshihiro wrote: > > > Mike Silbersack wrote: > > > > >Try disabling delayed ACKs and see how that affects your results. The > > >default delay for delayed acks is 100ms. > > > > > >sysctl -w net.inet.tcp.delayed_ack=0 > > > > > > > I found a machine with FreeBSD4.3 and tried it, but it didn't work. > > > > Yoshi > > What didn't work? Were you unable to disable delayed acks, or did > disabling them have no effect? > Sorry, it seems it works between two FreeBSD machines. I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my problem. That's what I did previously. I found discussion on "delayed ack problem"(January 24 and 25) in this mailing list. Though still do not understand why delayed_ack=0 does not work for FreeBSD and Solaris. Anyway I appreciate your helping me. Thank you, Yoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 19:30:27 2001 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 ESMTP id 152DE37B41C for ; Mon, 24 Sep 2001 19:30:24 -0700 (PDT) Received: (qmail 71012 invoked by uid 1000); 25 Sep 2001 02:30:20 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Sep 2001 02:30:20 -0000 Date: Mon, 24 Sep 2001 21:30:20 -0500 (CDT) From: Mike Silbersack To: Cc: Subject: Re: TCP performance question In-Reply-To: <200109250215.LAA00788@const.kawasaki.flab.fujitsu.co.jp> Message-ID: <20010924212903.H70783-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 25 Sep 2001 tsuchiya@flab.fujitsu.co.jp wrote: > Sorry, it seems it works between two FreeBSD machines. > > I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my > problem. That's what I did previously. > > I found discussion on "delayed ack problem"(January 24 and 25) in this > mailing list. Though still do not understand why delayed_ack=0 does not > work for FreeBSD and Solaris. > > Anyway I appreciate your helping me. > Thank you, > Yoshi If you can reproduce the problem, please take some traces with tcpdump and post them somewhere for public consumption. Perhaps then the problem can be found and fixed. 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 Mon Sep 24 21:48:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id B39D537B413 for ; Mon, 24 Sep 2001 21:48:39 -0700 (PDT) Received: from localhost ([3ffe:501:4819:2000:200:39ff:fe97:3f1e]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id NAA00823; Tue, 25 Sep 2001 13:49:41 +0900 (JST) Date: Tue, 25 Sep 2001 13:48:21 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Joe Abley Cc: freebsd-net@FreeBSD.ORG Subject: Re: ipv6/gif/cisco syslog noise In-Reply-To: <20010921111029.H4205@buffoon.automagic.org> References: <20010919153739.K85635@buffoon.automagic.org> <20010920.050441.28824742.ume@mahoroba.org> <20010919164416.Q85635@buffoon.automagic.org> <20010921111029.H4205@buffoon.automagic.org> User-Agent: Wanderlust/2.6.0 (Twist And Shout-pre) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 43 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Thanks for the quick response. >>>>> On Fri, 21 Sep 2001 11:10:30 -0400, >>>>> Joe Abley said: > In this case, on the cisco router which terminates the tunnel, defining > the tunnel interface with a 126-bit netmask causes a /126 prefix to be > distributed in the IGP, and this provides reachability information for > both ends of the tunnel to other routers in the network. > If the cisco interface had been numbered with a 128-bit netmask, a > /128 prefix would have been distributed which would have provided > reachability information for the cisco tunnel interface, but not the > FreeBSD gif interface. Hence traffic sourced from the FreeBSD box using > that gif interface address as a source address would not get replies > routed correctly. Hmm, then, you might want to try the following configuration: ifconfig gif0 inet6 2001:438:1fff:ffff:8::32 prefixlen 126 that is, using a prefix length smaller than 128 *without* specifying the destination address. I'm not sure if this works well for FreeBSD 4.3, but it surely does at least for FreeBSD 4.4. Actually, The KAME/BSD kernel does not treat p2p interfaces differently from (NB)MA interfaces in terms of IPv6 addressing. In other words, it should be compatible with commercial routers such as Cisco and Juniper. > The reason for allocating four addresses (a 126-bit prefix) to the > point-to-point link stems from similar practice in IPv4, I think (it > wasn't my decision; it's current policy in AS6461). I'd use /64 instead of /126, since there is no reason to save address space in IPv6, but it is of course up to the site's decision. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 24 22:20:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 1934437B442 for ; Mon, 24 Sep 2001 22:20:15 -0700 (PDT) Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0108-Fujitsu Gateway) id OAA23119; Tue, 25 Sep 2001 14:20:08 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) From: tsuchiya@flab.fujitsu.co.jp Received: from const.kawasaki.flab.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0108-Fujitsu Domain Master) id OAA28388; Tue, 25 Sep 2001 14:20:08 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) Received: (from tsuchiya@localhost) by const.kawasaki.flab.fujitsu.co.jp (8.9.3+3.2W/3.5Wpl7) id OAA00963; Tue, 25 Sep 2001 14:20:10 +0900 Date: Tue, 25 Sep 2001 14:20:10 +0900 Message-Id: <200109250520.OAA00963@const.kawasaki.flab.fujitsu.co.jp> To: silby@silby.com, tsuchiya@flab.fujitsu.co.jp Subject: Re: TCP performance question Cc: net@FreeBSD.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > > > I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my > > problem. That's what I did previously. > > > > I found discussion on "delayed ack problem"(January 24 and 25) in this > > mailing list. Though still do not understand why delayed_ack=0 does not > > work for FreeBSD and Solaris. > > > > Anyway I appreciate your helping me. > > Thank you, > > Yoshi > > If you can reproduce the problem, please take some traces with tcpdump and > post them somewhere for public consumption. Perhaps then the problem can > be found and fixed. > > Mike "Silby" Silbersack Ok, "yokan" is FreeBSD4.1.1 and I set delayed_ack=0, and "purcell" is a Solaris 2.7 box. The sending size at first is 1460+588byte and 1460+589byte later. When the size gets more than 1460+589bytes, the performance goes down. At that time, purcell begins to send acks, possibly because yokan behaves very slow. ========================== 04:54:40.136343 yokan.1238 > purcell.12354: . ack 609417 win 16060 (DF) 04:54:40.136362 purcell.12354 > yokan.1238: P 609417:610005(588) ack 610005 win 8760 (DF) 04:54:40.136386 yokan.1238 > purcell.12354: . ack 610005 win 15472 (DF) 04:54:40.136418 yokan.1238 > purcell.12354: . 610005:611465(1460) ack 610005 win 17520 (DF) 04:54:40.136430 yokan.1238 > purcell.12354: P 611465:612053(588) ack 610005 win 17520 (DF) 04:54:40.137228 purcell.12354 > yokan.1238: . 610005:611465(1460) ack 612053 win 8760 (DF) 04:54:40.137276 yokan.1238 > purcell.12354: . ack 611465 win 16060 (DF) 04:54:40.137287 purcell.12354 > yokan.1238: P 611465:612053(588) ack 612053 win 8760 (DF) 04:54:40.137311 yokan.1238 > purcell.12354: . ack 612053 win 15472 (DF) 04:54:40.137359 yokan.1238 > purcell.12354: . 612053:613513(1460) ack 612053 win 17520 (DF) 04:54:40.137370 yokan.1238 > purcell.12354: P 613513:614101(588) ack 612053 win 17520 (DF) 04:54:40.138168 purcell.12354 > yokan.1238: . 612053:613513(1460) ack 614101 win 8760 (DF) 04:54:40.138203 yokan.1238 > purcell.12354: . ack 613513 win 16060 (DF) 04:54:40.138223 purcell.12354 > yokan.1238: P 613513:614101(588) ack 614101 win 8760 (DF) 04:54:40.138245 yokan.1238 > purcell.12354: . ack 614101 win 15472 (DF) 04:54:40.138278 yokan.1238 > purcell.12354: . 614101:615561(1460) ack 614101 win 17520 (DF) 04:54:40.208029 purcell.12354 > yokan.1238: . ack 615561 win 8760 (DF) 04:54:40.208055 yokan.1238 > purcell.12354: P 615561:616150(589) ack 614101 win 17520 (DF) 04:54:40.208675 purcell.12354 > yokan.1238: . 614101:615561(1460) ack 616150 win 8760 (DF) 04:54:40.208708 yokan.1238 > purcell.12354: . ack 615561 win 16060 (DF) 04:54:40.208729 purcell.12354 > yokan.1238: P 615561:616150(589) ack 616150 win 8760 (DF) 04:54:40.208754 yokan.1238 > purcell.12354: . ack 616150 win 15471 (DF) 04:54:40.208786 yokan.1238 > purcell.12354: . 616150:617610(1460) ack 616150 win 17520 (DF) 04:54:40.278035 purcell.12354 > yokan.1238: . ack 617610 win 8760 (DF) 04:54:40.278060 yokan.1238 > purcell.12354: P 617610:618199(589) ack 616150 win 17520 (DF) 04:54:40.278678 purcell.12354 > yokan.1238: . 616150:617610(1460) ack 618199 win 8760 (DF) 04:54:40.278709 yokan.1238 > purcell.12354: . ack 617610 win 16060 (DF) 04:54:40.278731 purcell.12354 > yokan.1238: P 617610:618199(589) ack 618199 win 8760 (DF) 04:54:40.278755 yokan.1238 > purcell.12354: . ack 618199 win 16931 (DF) 04:54:40.278796 yokan.1238 > purcell.12354: . 618199:619659(1460) ack 618199 win 17520 (DF) 04:54:40.348028 purcell.12354 > yokan.1238: . ack 619659 win 8760 (DF) 04:54:40.348059 yokan.1238 > purcell.12354: P 619659:620248(589) ack 618199 win 17520 (DF) 04:54:40.348680 purcell.12354 > yokan.1238: . 618199:619659(1460) ack 620248 win 8760 (DF) 04:54:40.348711 yokan.1238 > purcell.12354: . ack 619659 win 16060 (DF) 04:54:40.348736 purcell.12354 > yokan.1238: P 619659:620248(589) ack 620248 win 8760 (DF) 04:54:40.348758 yokan.1238 > purcell.12354: . ack 620248 win 16931 (DF) 04:54:40.348795 yokan.1238 > purcell.12354: . 620248:621708(1460) ack 620248 win 17520 (DF) 04:54:40.418025 purcell.12354 > yokan.1238: . ack 621708 win 8760 (DF) ========================== And here, it's between "yokan" and another FreeBSD machine. "regulus" is a FreeBSD4.3 box, and delayed_ack=0 has been done on both of the machines. It seems they send acks normally and there is no performance slow down. ========================== 04:55:38.774912 yokan.1239 > regulus.12354: P 613513:614101(588) ack 612053 win 17520 (DF) 04:55:38.775723 regulus.12354 > yokan.1239: . ack 613513 win 16060 (DF) 04:55:38.775765 regulus.12354 > yokan.1239: . ack 614101 win 16932 (DF) 04:55:38.776424 regulus.12354 > yokan.1239: . 612053:613513(1460) ack 614101 win 17520 (DF) 04:55:38.776459 yokan.1239 > regulus.12354: . ack 613513 win 16060 (DF) 04:55:38.776479 regulus.12354 > yokan.1239: P 613513:614101(588) ack 614101 win 17520 (DF) 04:55:38.776504 yokan.1239 > regulus.12354: . ack 614101 win 15472 (DF) 04:55:38.776541 yokan.1239 > regulus.12354: . 614101:615561(1460) ack 614101 win 17520 (DF) 04:55:38.777358 regulus.12354 > yokan.1239: . ack 615561 win 16060 (DF) 04:55:38.777384 yokan.1239 > regulus.12354: P 615561:616150(589) ack 614101 win 17520 (DF) 04:55:38.777828 regulus.12354 > yokan.1239: . ack 616150 win 16931 (DF) 04:55:38.778482 regulus.12354 > yokan.1239: . 614101:615561(1460) ack 616150 win 17520 (DF) 04:55:38.778510 yokan.1239 > regulus.12354: . ack 615561 win 16060 (DF) 04:55:38.778958 regulus.12354 > yokan.1239: P 615561:616150(589) ack 616150 win 17520 (DF) 04:55:38.778984 yokan.1239 > regulus.12354: . ack 616150 win 16931 (DF) 04:55:38.779020 yokan.1239 > regulus.12354: . 616150:617610(1460) ack 616150 win 17520 (DF) 04:55:38.779835 regulus.12354 > yokan.1239: . ack 617610 win 16060 (DF) 04:55:38.779861 yokan.1239 > regulus.12354: P 617610:618199(589) ack 616150 win 17520 (DF) 04:55:38.780305 regulus.12354 > yokan.1239: . ack 618199 win 16931 (DF) 04:55:38.780959 regulus.12354 > yokan.1239: . 616150:617610(1460) ack 618199 win 17520 (DF) 04:55:38.780986 yokan.1239 > regulus.12354: . ack 617610 win 16060 (DF) 04:55:38.781435 regulus.12354 > yokan.1239: P 617610:618199(589) ack 618199 win 17520 (DF) 04:55:38.781459 yokan.1239 > regulus.12354: . ack 618199 win 16931 (DF) ========================== Thanks, Yoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 2:41:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id D414F37B43C for ; Tue, 25 Sep 2001 02:41:39 -0700 (PDT) Received: from m6.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0108-Fujitsu Gateway) id SAA04584; Tue, 25 Sep 2001 18:41:34 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) From: tsuchiya@flab.fujitsu.co.jp Received: from const.kawasaki.flab.fujitsu.co.jp by m6.gw.fujitsu.co.jp (8.9.3/3.7W-0108-Fujitsu Domain Master) id SAA04562; Tue, 25 Sep 2001 18:41:33 +0900 (envelope-from tsuchiya@flab.fujitsu.co.jp) Received: (from tsuchiya@localhost) by const.kawasaki.flab.fujitsu.co.jp (8.9.3+3.2W/3.5Wpl7) id SAA01211; Tue, 25 Sep 2001 18:41:35 +0900 Date: Tue, 25 Sep 2001 18:41:35 +0900 Message-Id: <200109250941.SAA01211@const.kawasaki.flab.fujitsu.co.jp> To: silby@silby.com, tsuchiya@flab.fujitsu.co.jp Subject: Re: TCP performance question Cc: net@FreeBSD.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > > > > > I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my > > > problem. That's what I did previously. > > > > > > I found discussion on "delayed ack problem"(January 24 and 25) in this > > > mailing list. Though still do not understand why delayed_ack=0 does not > > > work for FreeBSD and Solaris. > > > > > > Anyway I appreciate your helping me. > > > Thank you, > > > Yoshi > > > > If you can reproduce the problem, please take some traces with tcpdump and > > post them somewhere for public consumption. Perhaps then the problem can > > be found and fixed. > > > > Mike "Silby" Silbersack > > > Ok, "yokan" is FreeBSD4.1.1 and I set delayed_ack=0, and "purcell" is > a Solaris 2.7 box. The sending size at first is 1460+588byte and 1460+589byte > later. When the size gets more than 1460+589bytes, the performance goes down. > At that time, purcell begins to send acks, possibly because yokan behaves > very slow. > I installed FreeBSD4.4 on this machine(yokan), and tested TCP with Solaris. Sadly, the result is as bad as it was; same thing happened. Yoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 11: 9:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 8DE0937B410 for ; Tue, 25 Sep 2001 11:09:30 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f8PI9S806663; Tue, 25 Sep 2001 11:09:28 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id f8PI9Rl19337; Tue, 25 Sep 2001 11:09:27 -0700 (PDT) (envelope-from jdp) Date: Tue, 25 Sep 2001 11:09:27 -0700 (PDT) Message-Id: <200109251809.f8PI9Rl19337@vashon.polstra.com> To: net@freebsd.org From: John Polstra Cc: larse@ISI.EDU Subject: Re: Solution (RE: VPN client with mpd) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article , Lars Eggert wrote: > > Thanks to Archie and Brian, I now have a working PPTP tunnel up. Here's > what I changed from the example vpn configuration included in the mpd > package in /usr/local/etc/mpd/mpd.conf, I thought I'd document this in > case someone else runs accross the same problem: [...] > 4. Change "set link yes chap" to "set link allow chap". Both Archie and > Brian suggested this; with the change, mpd will allow negotiation with > remote peers that do not want to CHAP-authenticate themselves (like my > remote VPN servers, it seems). The trouble with this is that your password will be sent unencrypted across the Internet, very possibly hitting a sniffer or two along the way. It's better to insist on chap and fix the broken peers. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 11:19:13 2001 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 27B5E37B403 for ; Tue, 25 Sep 2001 11:16:25 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f8PIEVJ77448; Tue, 25 Sep 2001 14:14:31 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Sep 2001 14:14:31 -0400 (EDT) From: Garrett Wollman Message-Id: <200109251814.f8PIEVJ77448@khavrinen.lcs.mit.edu> To: John Polstra Cc: net@FreeBSD.ORG Subject: Re: Solution (RE: VPN client with mpd) In-Reply-To: <200109251809.f8PI9Rl19337@vashon.polstra.com> References: <200109251809.f8PI9Rl19337@vashon.polstra.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > The trouble with this is that your password will be sent unencrypted > across the Internet, very possibly hitting a sniffer or two along the > way. It's better to insist on chap and fix the broken peers. Actually, no: the other side, which considers itself a server, doesn't want to authenticate *itself* in any way to clients (since Windows clients have no way to accept server authentication). It's perfectly happy to have clients authenticate themselves. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 11:24:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 22F2837B415 for ; Tue, 25 Sep 2001 11:21:40 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f8PILb806758; Tue, 25 Sep 2001 11:21:37 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id f8PILa519449; Tue, 25 Sep 2001 11:21:36 -0700 (PDT) (envelope-from jdp) Date: Tue, 25 Sep 2001 11:21:36 -0700 (PDT) Message-Id: <200109251821.f8PILa519449@vashon.polstra.com> To: net@freebsd.org From: John Polstra Cc: wollman@khavrinen.lcs.mit.edu Subject: Re: Solution (RE: VPN client with mpd) In-Reply-To: <200109251814.f8PIEVJ77448@khavrinen.lcs.mit.edu> References: <200109251809.f8PI9Rl19337@vashon.polstra.com> <200109251814.f8PIEVJ77448@khavrinen.lcs.mit.edu> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article <200109251814.f8PIEVJ77448@khavrinen.lcs.mit.edu>, Garrett Wollman wrote: > < said: > > > The trouble with this is that your password will be sent unencrypted > > across the Internet, very possibly hitting a sniffer or two along the > > way. It's better to insist on chap and fix the broken peers. > > Actually, no: the other side, which considers itself a server, doesn't > want to authenticate *itself* in any way to clients (since Windows > clients have no way to accept server authentication). It's perfectly > happy to have clients authenticate themselves. Oh. I haven't actually sniffed it, so I'll assume you're right. I apologize for the misinformation. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 11:28:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.fidnet.com (three.fidnet.com [205.216.200.53]) by hub.freebsd.org (Postfix) with SMTP id 693FF37B409 for ; Tue, 25 Sep 2001 11:23:46 -0700 (PDT) Received: (qmail 30455 invoked from network); 25 Sep 2001 18:17:02 -0000 Received: from unknown (HELO Beast) (216.229.82.132) by three.fidnet.com with SMTP; 25 Sep 2001 18:17:02 -0000 From: "Matthew Rezny" To: "net@freebsd.org" Date: Tue, 25 Sep 2001 13:17:08 -0500 Reply-To: "Matthew Rezny" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195;2) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Alteon gigE NIC (if_ti) problems Message-Id: <20010925182346.693FF37B409@hub.freebsd.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I recent gave up truing to make a Intel gigE NIC work in my Alpha so I got an Alteon board. It works without the severe problem of the Intel card. However, its acting a little weird. I see messages saying the link went down and up quite often. I've tried both 4.3 and 4.4 and have the same thing. I increased NMBCLUSTERS significantly and still see the same thing. I made the switch from 4.3 to 4.4 at the same time I incrased NMBCLUSTERS from 8192 to 32767 so I can't say which, but one (or both) of those changes increased the rate at which I see the link status change message. Before I saw it every once in a while reguardless of whether there was heavy traffic or not. Now it shows up every few seconds when there is any traffic at all. Anyone have any ideas what's going on? BTW, I would include my dmesg but its full of "ti0: link down" and "ti0: gigabit link up" so here's there pertinent info. Alpha 21164PC 533 on PC164SX Alteon gigE card in 64bit PCI slot with IRQ 11 which is not shared If any other info would help, just ask and I'll get it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 11:28:33 2001 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 CF15C37B40A for ; Tue, 25 Sep 2001 11:25:43 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f8PIPfG77678; Tue, 25 Sep 2001 14:25:41 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Sep 2001 14:25:41 -0400 (EDT) From: Garrett Wollman Message-Id: <200109251825.f8PIPfG77678@khavrinen.lcs.mit.edu> To: John Polstra Cc: net@freebsd.org, wollman@khavrinen.lcs.mit.edu Subject: Re: Solution (RE: VPN client with mpd) In-Reply-To: <200109251821.f8PILa519449@vashon.polstra.com> References: <200109251809.f8PI9Rl19337@vashon.polstra.com> <200109251814.f8PIEVJ77448@khavrinen.lcs.mit.edu> <200109251821.f8PILa519449@vashon.polstra.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Oh. I haven't actually sniffed it, so I'll assume you're right. I > apologize for the misinformation. Well, that's the situation as it was described upthread, and I experienced something similar when I was first setting up PPP dialups here. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 11:41:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id A1B1B37B420 for ; Tue, 25 Sep 2001 11:38:14 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f8PIcB806907; Tue, 25 Sep 2001 11:38:11 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id f8PIcBO19523; Tue, 25 Sep 2001 11:38:11 -0700 (PDT) (envelope-from jdp) Date: Tue, 25 Sep 2001 11:38:11 -0700 (PDT) Message-Id: <200109251838.f8PIcBO19523@vashon.polstra.com> To: net@freebsd.org From: John Polstra Cc: wollman@khavrinen.lcs.mit.edu Subject: Re: Solution (RE: VPN client with mpd) In-Reply-To: <200109251825.f8PIPfG77678@khavrinen.lcs.mit.edu> References: <200109251814.f8PIEVJ77448@khavrinen.lcs.mit.edu> <200109251821.f8PILa519449@vashon.polstra.com> <200109251825.f8PIPfG77678@khavrinen.lcs.mit.edu> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article <200109251825.f8PIPfG77678@khavrinen.lcs.mit.edu>, Garrett Wollman wrote: > < said: > > > Oh. I haven't actually sniffed it, so I'll assume you're right. I > > apologize for the misinformation. > > Well, that's the situation as it was described upthread, and I > experienced something similar when I was first setting up PPP dialups > here. Having looked back at my ppp.conf files, I'm sure you're right. The way to keep your unencrypted passwords off the net is with "deny pap". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 14:18:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from host3.expertcity.rangefire.net (host1.expertcity.rangefire.net [216.64.159.146]) by hub.freebsd.org (Postfix) with ESMTP id 63F8437B40C for ; Tue, 25 Sep 2001 14:18:49 -0700 (PDT) Received: from [10.4.1.134] (helo=expertcity.com) by host3.expertcity.rangefire.net with esmtp (Exim 3.22 #4) id 15lzbH-0000ZY-00 for net@freebsd.org; Tue, 25 Sep 2001 14:18:46 -0700 Message-ID: <3BB0F49B.8070704@expertcity.com> Date: Tue, 25 Sep 2001 14:18:19 -0700 From: Jeff Behl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: net@freebsd.org Subject: ENOBUFS and network performance tuning Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have 4.3, and soon to be 4.4, boxes dedicated to a single app which basically 'bounces' traffic between two incoming TCP connections. After around 240 sessions (each session consisting of two incoming connections with traffic being passed between them), I started getting ENOBUFS errors. netstat -m showed mbuf's never peaked, so we increased kern.ipc.somaxconn from 128 -> 256. Should this help the problem? Any other guidelines to help tune a FreeBSD box for this sort of use would be greatly appreciated. Currently, the only change we make is increasing MAXUSERS to 128, though I'm not sure this is the preferred approach. Also, is there a definitive guide to what all the kernel variables (sysctl -a) are? thanks Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 14:24:18 2001 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 ESMTP id D183437B414 for ; Tue, 25 Sep 2001 14:24:14 -0700 (PDT) Received: (qmail 73422 invoked by uid 1000); 25 Sep 2001 21:24:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Sep 2001 21:24:12 -0000 Date: Tue, 25 Sep 2001 16:24:12 -0500 (CDT) From: Mike Silbersack To: Jeff Behl Cc: Subject: Re: ENOBUFS and network performance tuning In-Reply-To: <3BB0F49B.8070704@expertcity.com> Message-ID: <20010925162212.Q73194-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 25 Sep 2001, Jeff Behl wrote: > Any other guidelines to help tune a FreeBSD box for this sort of use > would be greatly appreciated. Currently, the only change we make is > increasing MAXUSERS to 128, though I'm not sure this is the preferred > approach. That's the simplest approach, as it bumps up numerous kernel setting. With 4.4 you can tune it in loader.conf, so changing the setting isn't a big deal. You should probably check how many sockets are sticking around in the TIME_WAIT state and compare it to kern.ipc.maxsockets - that may be the limit you're hitting first. 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 Tue Sep 25 15:38:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.iPolicyNet.COM (mail.policyone.com [63.199.81.149]) by hub.freebsd.org (Postfix) with ESMTP id 5A04437B412 for ; Tue, 25 Sep 2001 15:38:13 -0700 (PDT) Received: from ca-mail01.CA.iPolicyNet.COM (CA-Mail01.CA.iPolicyNet.COM [199.172.181.4]) by mail.iPolicyNet.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA06702; Tue, 25 Sep 2001 15:27:56 -0700 (PDT) Received: by CA-Mail01.CA.iPolicyNet.COM with Internet Mail Service (5.5.2653.19) id ; Tue, 25 Sep 2001 15:26:48 -0700 Message-ID: From: "Vohra, Meenakshi" To: "'freebsd-questions@freebsd.org'" Cc: "'freebsd-net@freebsd.org'" Subject: error in key_acquire2 : Date: Tue, 25 Sep 2001 15:26:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org After installing 2 FreeBSD machines, i have set up policies between them as : any type of traffic between them should undergo a esp transport mode by refering foll. document. http://www.daemonnews.org/200101/ipsec-howto.html Then as specified i updated the psk.txt to enter shared secret. followed by running racoon on both machines as: /usr/local/sbin/racoon -f /usr/local/etc/racoon/racoon.conf when i try to ping one machine from another. I am getting following error: key_acquire2 : invalid sequence number is passed pls. suggest me what could be the possible reason thanx meenakshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 15:48: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.fidnet.com (four.fidnet.com [205.216.200.54]) by hub.freebsd.org (Postfix) with SMTP id 6DAB237B401 for ; Tue, 25 Sep 2001 15:48:00 -0700 (PDT) Received: (qmail 26889 invoked from network); 25 Sep 2001 22:47:54 -0000 Received: from unknown (HELO Beast) (216.229.82.132) by 0 with SMTP; 25 Sep 2001 22:47:54 -0000 From: "Matthew Rezny" To: "Jim McGrath" Cc: "net@freebsd.org" Date: Tue, 25 Sep 2001 17:48:02 -0500 Reply-To: "Matthew Rezny" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195;2) In-Reply-To: <31269226357BD211979E00A0C9866DAB01BE7963@rios.sitaranetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: RE: Alteon gigE NIC (if_ti) problems Message-Id: <20010925224800.6DAB237B401@hub.freebsd.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The Intel NIC flooded the remote end (computer or switch) with trash such that the device was unable to process anything as long as the link was up. This occured as long as the computer was on, before the driver loaded or the OS booted, so it wasn't a driver problem. I tried both the wx and gx driver and neither seemed to initialize it in any way that allowed it to work properly. Traffic could pass through the link but the remote end couldn't do much since it was flooded with junk that appeared to be flow-control stuff. With this Alteon card, the remote end is just fine and all traffic passes through. The disconnect appears on the computer. The link light on the switch never goes off when the computer says its link is continously going down and up. I suspect that when it thinks the link drops, all trafffic gets delayed until some timeout period after the link is back, which is why I'm seeing slowdowns. On Tue, 25 Sep 2001 18:36:15 -0400, Jim McGrath wrote: >What kind of problems were you having with the Intel GigE NIC? I've got it >running in an Intel box, the only recent problems have been of my own >making. I found a bug in the code for the copper version of the NIC. Were >you running a fiber or copper NIC? > >I'm not as familiar with the ti driver, but it sounds like a watchdog timer >problem. That will cause a reset of the NIC. > >Jim > >-----Original Message----- >From: Matthew Rezny [mailto:mrezny@umr.edu] >Sent: Tuesday, September 25, 2001 2:17 PM >To: net@freebsd.org >Subject: Alteon gigE NIC (if_ti) problems > > >I recent gave up truing to make a Intel gigE NIC work in my Alpha so I >got an Alteon board. It works without the severe problem of the Intel >card. However, its acting a little weird. I see messages saying the >link went down and up quite often. I've tried both 4.3 and 4.4 and have >the same thing. I increased NMBCLUSTERS significantly and still see the >same thing. I made the switch from 4.3 to 4.4 at the same time I >incrased NMBCLUSTERS from 8192 to 32767 so I can't say which, but one >(or both) of those changes increased the rate at which I see the link >status change message. Before I saw it every once in a while >reguardless of whether there was heavy traffic or not. Now it shows up >every few seconds when there is any traffic at all. Anyone have any >ideas what's going on? > >BTW, I would include my dmesg but its full of "ti0: link down" and >"ti0: gigabit link up" so here's there pertinent info. >Alpha 21164PC 533 on PC164SX >Alteon gigE card in 64bit PCI slot with IRQ 11 which is not shared >If any other info would help, just ask and I'll get it. > > > >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 Tue Sep 25 20: 1: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from mine.kame.net (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id ED63F37B409 for ; Tue, 25 Sep 2001 20:01:01 -0700 (PDT) Received: from localhost ([3ffe:501:4819:1000:260:1dff:fef7:1d80]) by mine.kame.net (8.11.1/3.7W) with ESMTP id f8Q318H58262; Wed, 26 Sep 2001 12:01:09 +0900 (JST) To: mvohra@iPolicyNet.COM Cc: freebsd-net@freebsd.org, freebsd-net@freebsd.org Subject: Re: error in key_acquire2 : In-Reply-To: Your message of "Tue, 25 Sep 2001 15:26:47 -0700" References: X-Mailer: Cue version 0.6 (010810-1737/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20010926115902P.sakane@kame.net> Date: Wed, 26 Sep 2001 11:59:02 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org please please tell us the version which you are using at least, freebsd, racoon, when you ask question. before you ask questions to this list, check and examine your configuration, ifconfig, netstat, tcpdump, racoon.conf, racoon.log, setkey in this case, > After installing 2 FreeBSD machines, i have set up policies between them as > : any type of traffic between them should undergo a esp transport mode by > refering foll. document. > http://www.daemonnews.org/200101/ipsec-howto.html > Then as specified i updated the psk.txt to enter shared secret. followed by > running racoon on both machines as: > /usr/local/sbin/racoon -f /usr/local/etc/racoon/racoon.conf > > when i try to ping one machine from another. > I am getting following error: > key_acquire2 : invalid sequence number is passed it is just warning. the recent version of the kame repository doesn't output this message. the problem exists other place. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 20:29: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from mine.kame.net (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id 2B15137B413 for ; Tue, 25 Sep 2001 20:28:57 -0700 (PDT) Received: from localhost ([3ffe:501:4819:1000:260:1dff:fef7:1d80]) by mine.kame.net (8.11.1/3.7W) with ESMTP id f8Q3UZH58365; Wed, 26 Sep 2001 12:30:35 +0900 (JST) To: swb@grasslake.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPSec problem, racoon can't transmit? In-Reply-To: Your message of "Sun, 23 Sep 2001 17:51:33 -0500" <001201c14482$4b2d45e0$021ea8c0@twinstar> References: <001201c14482$4b2d45e0$021ea8c0@twinstar> X-Mailer: Cue version 0.6 (010810-1737/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20010926122828R.sakane@kame.net> Date: Wed, 26 Sep 2001 12:28:28 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20000228(IM140) Lines: 17 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > When I start racoon on both machines, all appears fine. To make a long > story short, Machine A never seems to generate ANY isakmp packets. Machine > B's racoon run-time info never indicates it's gotten a phase I initiation > from A if the session was originated from A. I've run tcpdump on both > machines, and A never sends any isakmp packets, although it does get them > from B if B originates traffic first and appears to generate a response > according to racoon debug info, but B never gets the responses (and if > tcpdump is to believed A never sends them). > Both machines are running racoon-20010831a and 4.4-STABLE built yesterday. do you mean Machine A didn't send only isakmp packets ? or machine A couldn't send all of packets to machine B ? the re-keying might failed. could you check the log file of racoon on both side ? if you picked ERROR tag from the file, you could find the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 20:39:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from mine.kame.net (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id 76D2C37B40D for ; Tue, 25 Sep 2001 20:39:09 -0700 (PDT) Received: from localhost ([3ffe:501:4819:1000:260:1dff:fef7:1d80]) by mine.kame.net (8.11.1/3.7W) with ESMTP id f8Q3f2H58409; Wed, 26 Sep 2001 12:41:02 +0900 (JST) To: dms@wplus.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: Win32 to FreeBSD VPN In-Reply-To: Your message of "Wed, 19 Sep 2001 23:35:26 +0400" <3BA8F37E.4B2EB92F@wplus.net> References: <3BA8F37E.4B2EB92F@wplus.net> X-Mailer: Cue version 0.6 (010810-1737/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20010926123855B.sakane@kame.net> Date: Wed, 26 Sep 2001 12:38:55 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20000228(IM140) Lines: 10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Does anybody have working VPN between > Win32 client and FreeBSD server (PPTP or IPSec) > if yes - which software you use. > Could someone point me to really working free or commercial software > to solve this problem? i am not sure of windows32. you can get informations by search engine with keywords, "IPsec FreeBSD Windows". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 25 21:46:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 52C1037B406 for ; Tue, 25 Sep 2001 21:46:35 -0700 (PDT) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA58348; Tue, 25 Sep 2001 22:24:55 -0700 (PDT) Message-ID: <3BB15A08.8048F19D@elischer.org> Date: Tue, 25 Sep 2001 21:31:04 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Shoichi Sakane Cc: dms@wplus.net, freebsd-net@FreeBSD.ORG Subject: Re: Win32 to FreeBSD VPN References: <3BA8F37E.4B2EB92F@wplus.net> <20010926123855B.sakane@kame.net> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Shoichi Sakane wrote: > > > Does anybody have working VPN between > > Win32 client and FreeBSD server (PPTP or IPSec) > > if yes - which software you use. > > > Could someone point me to really working free or commercial software > > to solve this problem? for pptp look at the 'mpd' port for freeBSD (and look up various mails about it in the archives) > > i am not sure of windows32. you can get informations by search engine > with keywords, "IPsec FreeBSD Windows". > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 4:56:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 30C6F37B429 for ; Wed, 26 Sep 2001 04:56:49 -0700 (PDT) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.11.6/8.11.6) with SMTP id f8QBuml55091 for ; Wed, 26 Sep 2001 07:56:48 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: freebsd-net@freebsd.org Subject: Re: Win32 to FreeBSD VPN Date: Wed, 26 Sep 2001 07:56:48 -0400 Message-ID: References: <3BA8F37E.4B2EB92F@wplus.net> In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org =46or the server size, use mpd on FreeBSD. It works very well. For = client side, best to stick with PPTP if you are using anything less than win2k. = I am not aware of any free IPSec clients for Windows that work well on all platforms. Even the built in VPN client on MS will require quite a few knowledge base articles read to get all working. You can hit some nasty bugs that will eat up your time :-( www.dejanews.com is also a great resource for helping you through the "error 629" nonsense that some = clients get messed up by. ---Mike On 25 Sep 2001 23:39:18 -0400, in sentex.lists.freebsd.net you wrote: >> Does anybody have working VPN between=20 >> Win32 client and FreeBSD server (PPTP or IPSec)=20 >> if yes - which software you use. > >> Could someone point me to really working free or commercial software=20 >> to solve this problem? > >i am not sure of windows32. you can get informations by search engine >with keywords, "IPsec FreeBSD Windows". > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 7:29:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from star.rila.bg (star.rila.bg [194.141.1.32]) by hub.freebsd.org (Postfix) with ESMTP id CDE1537B434 for ; Wed, 26 Sep 2001 07:29:17 -0700 (PDT) Received: from star.rila.bg (vlady@localhost [127.0.0.1]) by star.rila.bg (8.11.4/8.11.4) with ESMTP id f8QEVVc67605 for ; Wed, 26 Sep 2001 17:31:32 +0300 (EEST) (envelope-from vlady@star.rila.bg) Message-Id: <200109261431.f8QEVVc67605@star.rila.bg> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.3 To: freebsd-net@freebsd.org From: "Vladimir Terziev" Subject: IEEE 802.11 devices question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Sep 2001 17:31:31 +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does FreeBSD have a generic driver for IEEE 802.11 and IEEE 802.11b devices? regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 7:48:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 1CEE737B41D for ; Wed, 26 Sep 2001 07:48:36 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f8QEmWv19473; Wed, 26 Sep 2001 07:48:32 -0700 Date: Wed, 26 Sep 2001 07:48:32 -0700 From: Brooks Davis To: Vladimir Terziev Cc: freebsd-net@FreeBSD.ORG Subject: Re: IEEE 802.11 devices question Message-ID: <20010926074832.A19209@Odin.AC.HMC.Edu> References: <200109261431.f8QEVVc67605@star.rila.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109261431.f8QEVVc67605@star.rila.bg>; from vladimirt@rila.bg on Wed, Sep 26, 2001 at 05:31:31PM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 26, 2001 at 05:31:31PM +0300, Vladimir Terziev wrote: >=20 > Does FreeBSD have a generic driver for IEEE 802.11 and IEEE 802.11b de= vices? No. It does however, support just about every 802.11b device on the market via the an(4) and wi(4) drivers. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7seq/XY6L6fI4GtQRAqpQAKCDYoU0BGEEVLDGQLHMag2RejvMlACdF7wX QrLnL1C/Zad8Uni+gepYUNw= =lajk -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 9:50:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by hub.freebsd.org (Postfix) with ESMTP id 6282037B41C for ; Wed, 26 Sep 2001 09:50:52 -0700 (PDT) Received: from milk.yahoo.com (milk.yahoo.com [216.145.52.137]) by mrout1.yahoo.com (8.11.6/8.11.6/y.out) with ESMTP id f8QGoff93971; Wed, 26 Sep 2001 09:50:41 -0700 (PDT) Received: (from root@localhost) by milk.yahoo.com (8.11.0/8.11.0) id f8QGoeR18003; Wed, 26 Sep 2001 09:50:40 -0700 (PDT) (envelope-from jayanth) Date: Wed, 26 Sep 2001 09:50:40 -0700 From: jayanth To: tsuchiya@flab.fujitsu.co.jp Cc: silby@silby.com, net@FreeBSD.ORG Subject: Re: TCP performance question Message-ID: <20010926095040.A17953@yahoo-inc.com> References: <200109250520.OAA00963@const.kawasaki.flab.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200109250520.OAA00963@const.kawasaki.flab.fujitsu.co.jp>; from tsuchiya@flab.fujitsu.co.jp on Tue, Sep 25, 2001 at 02:20:10PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I think this is a performance issue and it would be nice to send the 589 bytes of data immediately rather than wait for the delayed ack from the other end. This issue is a combination of mbuf cluster size and the TF_MORETOCOME flag. 2049 is one byte more than the cluster size, so the first 1460 bytes are sent and the remaining 588 is delayed because of the TF_MORETOCOME flag. The remaining 1 byte is now copied to the socket buffer, but in tcp_output.c there are 4 conditionals which I am not sure should be true together. This prevents the next transmission of data,i.e the next 589 bytes. In tcp_output.c /* * Sender silly window avoidance. If connection is idle * and can send all data, a maximum segment, * at least a maximum default-size segment do it, * or are forced, do it; otherwise don't bother. * If peer's buffer is tiny, then send * when window is at least half open. * If retransmitting (possibly after persist timer forced us * to send into a small window), then must resend. */ if (len) { if (len == tp->t_maxseg) goto send; if (!(tp->t_flags & TF_MORETOCOME) && (idle || tp->t_flags & TF_NODELAY) && (tp->t_flags & TF_NOPUSH) == 0 && len + off >= so->so_snd.sb_cc) goto send; ^^^^^^^^^^^^^^^^^^^^^^^^^^ In this particular case idle and TF_NODELAY are off and hence the conditional is false. If len + off >= so->so_snd.sb_cc then why not send all the data ? Probably needs a little more thought. ^^^^^^^^^^^^^^^^^^^^^^^^^^ if (tp->t_force) goto send; if (len >= tp->max_sndwnd / 2 && tp->max_sndwnd > 0) goto send; if (SEQ_LT(tp->snd_nxt, tp->snd_max)) goto send; } The issue being that if I can send 588 why not anything between 589 and 1460. This assumption is based on the fact that the congestion window is large enough for us to send data. I dont think TF_NODELAY needs to be set by the application here. jayanth tsuchiya@flab.fujitsu.co.jp (tsuchiya@flab.fujitsu.co.jp) wrote: > > > > > > I tried to say that it had no effect between FreeBSD4.3 and Solaris, on my > > > problem. That's what I did previously. > > > > > > I found discussion on "delayed ack problem"(January 24 and 25) in this > > > mailing list. Though still do not understand why delayed_ack=0 does not > > > work for FreeBSD and Solaris. > > > > > > Anyway I appreciate your helping me. > > > Thank you, > > > Yoshi > > > > If you can reproduce the problem, please take some traces with tcpdump and > > post them somewhere for public consumption. Perhaps then the problem can > > be found and fixed. > > > > Mike "Silby" Silbersack > > > Ok, "yokan" is FreeBSD4.1.1 and I set delayed_ack=0, and "purcell" is > a Solaris 2.7 box. The sending size at first is 1460+588byte and 1460+589byte > later. When the size gets more than 1460+589bytes, the performance goes down. > At that time, purcell begins to send acks, possibly because yokan behaves > very slow. > > ========================== > 04:54:40.136343 yokan.1238 > purcell.12354: . ack 609417 win 16060 (DF) > 04:54:40.136362 purcell.12354 > yokan.1238: P 609417:610005(588) ack 610005 win 8760 (DF) > 04:54:40.136386 yokan.1238 > purcell.12354: . ack 610005 win 15472 (DF) > 04:54:40.136418 yokan.1238 > purcell.12354: . 610005:611465(1460) ack 610005 win 17520 (DF) > 04:54:40.136430 yokan.1238 > purcell.12354: P 611465:612053(588) ack 610005 win 17520 (DF) > 04:54:40.137228 purcell.12354 > yokan.1238: . 610005:611465(1460) ack 612053 win 8760 (DF) > 04:54:40.137276 yokan.1238 > purcell.12354: . ack 611465 win 16060 (DF) > 04:54:40.137287 purcell.12354 > yokan.1238: P 611465:612053(588) ack 612053 win 8760 (DF) > 04:54:40.137311 yokan.1238 > purcell.12354: . ack 612053 win 15472 (DF) > 04:54:40.137359 yokan.1238 > purcell.12354: . 612053:613513(1460) ack 612053 win 17520 (DF) > 04:54:40.137370 yokan.1238 > purcell.12354: P 613513:614101(588) ack 612053 win 17520 (DF) > 04:54:40.138168 purcell.12354 > yokan.1238: . 612053:613513(1460) ack 614101 win 8760 (DF) > 04:54:40.138203 yokan.1238 > purcell.12354: . ack 613513 win 16060 (DF) > 04:54:40.138223 purcell.12354 > yokan.1238: P 613513:614101(588) ack 614101 win 8760 (DF) > 04:54:40.138245 yokan.1238 > purcell.12354: . ack 614101 win 15472 (DF) > 04:54:40.138278 yokan.1238 > purcell.12354: . 614101:615561(1460) ack 614101 win 17520 (DF) > 04:54:40.208029 purcell.12354 > yokan.1238: . ack 615561 win 8760 (DF) > 04:54:40.208055 yokan.1238 > purcell.12354: P 615561:616150(589) ack 614101 win 17520 (DF) > 04:54:40.208675 purcell.12354 > yokan.1238: . 614101:615561(1460) ack 616150 win 8760 (DF) > 04:54:40.208708 yokan.1238 > purcell.12354: . ack 615561 win 16060 (DF) > 04:54:40.208729 purcell.12354 > yokan.1238: P 615561:616150(589) ack 616150 win 8760 (DF) > 04:54:40.208754 yokan.1238 > purcell.12354: . ack 616150 win 15471 (DF) > 04:54:40.208786 yokan.1238 > purcell.12354: . 616150:617610(1460) ack 616150 win 17520 (DF) > 04:54:40.278035 purcell.12354 > yokan.1238: . ack 617610 win 8760 (DF) > 04:54:40.278060 yokan.1238 > purcell.12354: P 617610:618199(589) ack 616150 win 17520 (DF) > 04:54:40.278678 purcell.12354 > yokan.1238: . 616150:617610(1460) ack 618199 win 8760 (DF) > 04:54:40.278709 yokan.1238 > purcell.12354: . ack 617610 win 16060 (DF) > 04:54:40.278731 purcell.12354 > yokan.1238: P 617610:618199(589) ack 618199 win 8760 (DF) > 04:54:40.278755 yokan.1238 > purcell.12354: . ack 618199 win 16931 (DF) > 04:54:40.278796 yokan.1238 > purcell.12354: . 618199:619659(1460) ack 618199 win 17520 (DF) > 04:54:40.348028 purcell.12354 > yokan.1238: . ack 619659 win 8760 (DF) > 04:54:40.348059 yokan.1238 > purcell.12354: P 619659:620248(589) ack 618199 win 17520 (DF) > 04:54:40.348680 purcell.12354 > yokan.1238: . 618199:619659(1460) ack 620248 win 8760 (DF) > 04:54:40.348711 yokan.1238 > purcell.12354: . ack 619659 win 16060 (DF) > 04:54:40.348736 purcell.12354 > yokan.1238: P 619659:620248(589) ack 620248 win 8760 (DF) > 04:54:40.348758 yokan.1238 > purcell.12354: . ack 620248 win 16931 (DF) > 04:54:40.348795 yokan.1238 > purcell.12354: . 620248:621708(1460) ack 620248 win 17520 (DF) > 04:54:40.418025 purcell.12354 > yokan.1238: . ack 621708 win 8760 (DF) > ========================== > > And here, it's between "yokan" and another FreeBSD machine. "regulus" is > a FreeBSD4.3 box, and delayed_ack=0 has been done on both of the machines. > It seems they send acks normally and there is no performance slow down. > > ========================== > 04:55:38.774912 yokan.1239 > regulus.12354: P 613513:614101(588) ack 612053 win 17520 (DF) > 04:55:38.775723 regulus.12354 > yokan.1239: . ack 613513 win 16060 (DF) > 04:55:38.775765 regulus.12354 > yokan.1239: . ack 614101 win 16932 (DF) > 04:55:38.776424 regulus.12354 > yokan.1239: . 612053:613513(1460) ack 614101 win 17520 (DF) > 04:55:38.776459 yokan.1239 > regulus.12354: . ack 613513 win 16060 (DF) > 04:55:38.776479 regulus.12354 > yokan.1239: P 613513:614101(588) ack 614101 win 17520 (DF) > 04:55:38.776504 yokan.1239 > regulus.12354: . ack 614101 win 15472 (DF) > 04:55:38.776541 yokan.1239 > regulus.12354: . 614101:615561(1460) ack 614101 win 17520 (DF) > 04:55:38.777358 regulus.12354 > yokan.1239: . ack 615561 win 16060 (DF) > 04:55:38.777384 yokan.1239 > regulus.12354: P 615561:616150(589) ack 614101 win 17520 (DF) > 04:55:38.777828 regulus.12354 > yokan.1239: . ack 616150 win 16931 (DF) > 04:55:38.778482 regulus.12354 > yokan.1239: . 614101:615561(1460) ack 616150 win 17520 (DF) > 04:55:38.778510 yokan.1239 > regulus.12354: . ack 615561 win 16060 (DF) > 04:55:38.778958 regulus.12354 > yokan.1239: P 615561:616150(589) ack 616150 win 17520 (DF) > 04:55:38.778984 yokan.1239 > regulus.12354: . ack 616150 win 16931 (DF) > 04:55:38.779020 yokan.1239 > regulus.12354: . 616150:617610(1460) ack 616150 win 17520 (DF) > 04:55:38.779835 regulus.12354 > yokan.1239: . ack 617610 win 16060 (DF) > 04:55:38.779861 yokan.1239 > regulus.12354: P 617610:618199(589) ack 616150 win 17520 (DF) > 04:55:38.780305 regulus.12354 > yokan.1239: . ack 618199 win 16931 (DF) > 04:55:38.780959 regulus.12354 > yokan.1239: . 616150:617610(1460) ack 618199 win 17520 (DF) > 04:55:38.780986 yokan.1239 > regulus.12354: . ack 617610 win 16060 (DF) > 04:55:38.781435 regulus.12354 > yokan.1239: P 617610:618199(589) ack 618199 win 17520 (DF) > 04:55:38.781459 yokan.1239 > regulus.12354: . ack 618199 win 16931 (DF) > ========================== > Thanks, > Yoshi > > 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 Wed Sep 26 11:33: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from hirogen.kabelfoon.nl (hirogen.kabelfoon.nl [62.45.45.69]) by hub.freebsd.org (Postfix) with ESMTP id 87CA637B40C for ; Wed, 26 Sep 2001 11:33:05 -0700 (PDT) Received: from ntpc (kf-pij-tg01-426.dial.kabelfoon.nl [62.45.89.172]) by hirogen.kabelfoon.nl (Postfix) with SMTP id D6E327CC8; Wed, 26 Sep 2001 20:33:02 +0200 (CEST) From: "Peter Blok" To: "'Shoichi Sakane'" , Cc: Subject: RE: Win32 to FreeBSD VPN Date: Wed, 26 Sep 2001 20:28:11 +0200 Message-ID: <000601c146b8$ffc609a0$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010926123855B.sakane@kame.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have W2K working with ipsec on 4.4-STABLE. Wasn't that hard. -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Shoichi Sakane Sent: Wednesday, September 26, 2001 05:39 To: dms@wplus.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: Win32 to FreeBSD VPN > Does anybody have working VPN between > Win32 client and FreeBSD server (PPTP or IPSec) > if yes - which software you use. > Could someone point me to really working free or commercial software > to solve this problem? i am not sure of windows32. you can get informations by search engine with keywords, "IPsec FreeBSD Windows". 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 Wed Sep 26 13:36:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11]) by hub.freebsd.org (Postfix) with ESMTP id C63B037B41F for ; Wed, 26 Sep 2001 13:36:16 -0700 (PDT) Received: from stannous-ultra.cisco.com (stannous-ultra.cisco.com [64.102.40.156]) by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f8QKaHv13457 for ; Wed, 26 Sep 2001 13:36:17 -0700 (PDT) Received: (stannous@localhost) by stannous-ultra.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA08126 for freebsd-net@freebsd.org; Wed, 26 Sep 2001 16:36:06 -0400 (EDT) Date: Wed, 26 Sep 2001 16:36:06 -0400 From: Sam Tannous To: freebsd-net@freebsd.org Subject: 3COM 3c985-SX or 3c985B-SX Message-ID: <20010926163606.B8081@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org From what I've seen in this list, this seems to be the best performing gigabit ethernet card on FreeBSD. Most stores now stock the newer 3c985B-SX rather then the 3c985-SX. Does the existing driver handle the newer "b" card as well as the old card? I just want to make sure before I go ordering 4 cards. -- Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 13:55:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.fidnet.com (three.fidnet.com [205.216.200.53]) by hub.freebsd.org (Postfix) with SMTP id 10F5A37B417 for ; Wed, 26 Sep 2001 13:55:41 -0700 (PDT) Received: (qmail 19895 invoked from network); 26 Sep 2001 20:55:32 -0000 Received: from unknown (HELO Beast) (216.229.82.132) by three.fidnet.com with SMTP; 26 Sep 2001 20:55:32 -0000 From: "Matthew Rezny" To: "net@freebsd.org" Date: Wed, 26 Sep 2001 15:55:30 -0500 Reply-To: "Matthew Rezny" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195;2) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Alteon gigE NIC (if_ti driver) problems Message-Id: <20010926205541.10F5A37B417@hub.freebsd.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have some more information since my initial posting yesterday. I set the NMBCLUSTERS back to default, which made no difference. Therefore, moving from 4.3 to 4.4 is what drastically increased the frequency at which the link goes down and back up. I also captured dmesg now I case there is any useful information in it. The fluctuation of the link occurs multiple times a second with the new kernel when attempting to use the network with this machine. Any suggestions would be greatly appreciated. Thanks. Unrecognized boot flag '0'. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-RELEASE #1: Tue Sep 25 22:54:14 CDT 2001 root@wintermute.hexaneinc.com:/usr/src/sys/compile/CUSTOM EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x101 OSF PAL rev: 0x1000600020117 real memory = 400474112 (391088K bytes) avail memory = 383492096 (374504K bytes) Preloaded elf kernel "kernel" at 0xfffffc00006d4000. ccd0-3: Concatenated disk drivers md0: Malloc disk cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 atapci0: port 0x1000-0x10ff,0x1320-0x1323,0x1310-0x1317 irq 9 at device 5.0 on pci0 ata2: at 0x1310 on atapci0 atapci0: interrupting at CIA irq 9 atapci1: port 0x1100-0x11ff,0x1324-0x1327,0x1318-0x131f irq 9 at device 5.1 on pci0 ata3: at 0x1318 on atapci1 atapci1: interrupting at CIA irq 9 ti0: mem 0x82850000-0x82853fff irq 11 at device 6.0 on pci0 ti0: interrupting at CIA irq 11 ti0: Ethernet address: 00:60:cf:20:1e:99 sym0: <875> port 0x1200-0x12ff mem 0x82858000-0x82858fff,0x8285a000-0x8285a0ff irq 10 at device 7.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking sym0: interrupting at CIA irq 10 isab0: at device 8.0 on pci0 isa0: on isab0 atapci2: port 0x1300-0x130f,0x3f4-0x3f7,0x1f0-0x1f7 at device 8.1 on pci0 atapci3: port 0x374-0x377,0x170-0x177 at device 8.2 on pci0 atapci3: Busmastering DMA not configured pci0: at 8.3 pci0: at 9.0 irq 8 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Polled port ppc0: interrupting at ISA irq 7 sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 sbc0: interrupting at ISA irq 5 pcm0: on sbc0 Timecounter "alpha" frequency 533166528 Hz IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging disabled ad0: 34837MB [70780/16/63] at ata2-master UDMA66 ad1: 34837MB [70780/16/63] at ata3-master UDMA66 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4339MB (8887200 512 byte sectors: 255H 63S/T 553C) cd0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 14:23:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from opensrs.saignon.net (216-120-17-31.dsl.cust.tfb.com [216.120.17.31]) by hub.freebsd.org (Postfix) with ESMTP id 0AD3137B42C for ; Wed, 26 Sep 2001 14:23:47 -0700 (PDT) Received: from tsaignmobl (u2938@prx2.ipivot.com [216.188.41.2]) by opensrs.saignon.net (8.11.4/8.11.3) with SMTP id f8QLPWw19627 for ; Wed, 26 Sep 2001 14:25:33 -0700 (PDT) (envelope-from tony@saign.com) From: Tony Saign Reply-To: Cc: Subject: RE: IEEE 802.11 devices question Date: Wed, 26 Sep 2001 14:23:42 -0700 Message-ID: <000101c146d1$8471e350$da0b010a@tsaignmobl> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20010926074832.A19209@Odin.AC.HMC.Edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Has anyone successfully configured an Intel PRO 2011 wireless device?? That and a modem issue on my laptop are the only things that have stopped me from switching from MS (ick!) to FreeBSD. -Tony * -----Original Message----- * From: owner-freebsd-net@FreeBSD.ORG * [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Brooks Davis * Sent: Wednesday, September 26, 2001 7:49 AM * To: Vladimir Terziev * Cc: freebsd-net@FreeBSD.ORG * Subject: Re: IEEE 802.11 devices question * * * On Wed, Sep 26, 2001 at 05:31:31PM +0300, Vladimir Terziev wrote: * > * > Does FreeBSD have a generic driver for IEEE 802.11 and * IEEE 802.11b devices? * * No. It does however, support just about every 802.11b device on the * market via the an(4) and wi(4) drivers. * * -- Brooks * * -- * Any statement of the form "X is the one, true Y" is FALSE. * PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 19: 3:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f224.law14.hotmail.com [64.4.21.224]) by hub.freebsd.org (Postfix) with ESMTP id 41E5E37B43A for ; Wed, 26 Sep 2001 19:03:09 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 26 Sep 2001 19:03:09 -0700 Received: from 138.89.20.42 by lw14fd.law14.hotmail.msn.com with HTTP; Thu, 27 Sep 2001 02:03:08 GMT X-Originating-IP: [138.89.20.42] From: "ipver four" To: freebsd-net@FreeBSD.ORG Subject: FreeBSD and Cisco router IPSEC tunnel Date: Wed, 26 Sep 2001 22:03:08 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Sep 2001 02:03:09.0102 (UTC) FILETIME=[8DFBFCE0:01C146F8] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Has anyone successfully setup an IPSEC tunnel between a FreeBSD box and a Cisco router? If positive, can you tell me how to do it? Thanks, John _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 22:23:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from medusa.oit.pdx.edu (medusa.oit.pdx.edu [131.252.120.41]) by hub.freebsd.org (Postfix) with ESMTP id 4137D37B420; Wed, 26 Sep 2001 22:23:47 -0700 (PDT) Received: from gere.odin.pdx.edu (gere.odin.pdx.edu [131.252.120.42]) by medusa.oit.pdx.edu (8.11.6/8.11.6) with ESMTP id f8R5Njc18189; Wed, 26 Sep 2001 22:23:46 -0700 (PDT) Received: from localhost (singh@localhost) by gere.odin.pdx.edu (8.11.6/8.11.6) with ESMTP id f8R5Nj524630; Wed, 26 Sep 2001 22:23:45 -0700 (PDT) X-Authentication-Warning: gere.odin.pdx.edu: singh owned process doing -bs Date: Wed, 26 Sep 2001 22:23:45 -0700 (PDT) From: Harkirat Singh X-X-Sender: To: Cc: Subject: Dummynet - Burst Loss Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello! I want to know is it possible to create a burst of packet loss using dummynet. I have used Dummynet to create a random packet loss and quiet familiar with it. However, I did not get any information as how a burst of packet loss can be created. I shall be greatfull if someone can guide me about this.. Regards, harkirat Singh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 22:31:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from mx3.uninterruptible.net (cyclonis.catonic.net [63.160.99.136]) by hub.freebsd.org (Postfix) with ESMTP id 529CA37B444 for ; Wed, 26 Sep 2001 22:31:16 -0700 (PDT) Received: from mail.uninterruptible.net (ns1.uninterruptible.net [216.7.46.11]) by mx3.uninterruptible.net (Postfix) with ESMTP id 1BAE45501 for ; Thu, 27 Sep 2001 00:28:55 -0500 (CDT) Received: from Spaz.Catonic.NET (tnt8-216-180-71-236.dialup.HiWAAY.net [216.180.71.236]) by mail.uninterruptible.net (Postfix) with ESMTP id 78F775001F for ; Thu, 27 Sep 2001 05:31:09 +0000 (GMT) Received: by Spaz.Catonic.NET (Postfix, from userid 1002) id 15189330F; Thu, 27 Sep 2001 05:32:55 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by Spaz.Catonic.NET (Postfix) with ESMTP id 110104C10 for ; Thu, 27 Sep 2001 05:32:55 +0000 (GMT) Date: Thu, 27 Sep 2001 05:32:54 +0000 (GMT) From: Kris Kirby To: Subject: Network optimization? Message-ID: X-Tech-Support-Email: bofh@catonic.net X-Frames: I hate frames. Organization: Non Illegitemus Carborundum MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Please, if I have addressed this wrong, do not hesitate to point me toward another list. I'm looking for tips on network / kernel optimization. I know that when 100Mb/s ethernet first came to FreeBSD, there were P90s moving at 9MB/s, but I've never been able to break 7MB/s, except for my K7-850 with Barricuda hard drives (9.0). I'm using xl's on most machine (K7 as well) with a fxp in my P166 with SCSI drives (sees only ~6 MB/s on a good day). Any ideas? I've got 2560 total mbuf clusters on the P166; I can't really think of much else to change to speed things up... ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 26 23:52:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id EAB4E37B413 for ; Wed, 26 Sep 2001 23:52:29 -0700 (PDT) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0109-Fujitsu Gateway) id PAA24367; Thu, 27 Sep 2001 15:52:09 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) From: tsuchiya@flab.fujitsu.co.jp Received: from const.kawasaki.flab.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0108-Fujitsu Domain Master) id PAA01018; Thu, 27 Sep 2001 15:52:08 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) Received: (from tsuchiya@localhost) by const.kawasaki.flab.fujitsu.co.jp (8.9.3+3.2W/3.5Wpl7) id PAA03232; Thu, 27 Sep 2001 15:52:15 +0900 Date: Thu, 27 Sep 2001 15:52:15 +0900 Message-Id: <200109270652.PAA03232@const.kawasaki.flab.fujitsu.co.jp> To: jayanth@yahoo-inc.com, tsuchiya@flab.fujitsu.co.jp Subject: Re: TCP performance question Cc: net@FreeBSD.ORG, silby@silby.com Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > This issue is a combination of mbuf cluster size and the > TF_MORETOCOME flag. > if (len) { > if (len == tp->t_maxseg) > goto send; > if (!(tp->t_flags & TF_MORETOCOME) && > (idle || tp->t_flags & TF_NODELAY) && > (tp->t_flags & TF_NOPUSH) == 0 && > len + off >= so->so_snd.sb_cc) > goto send; When I changed the condition, the problem we had did not occur. I am wondering what is the right fix. Yoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 4:27:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from mmu.edu.my (ext-dns.mmu.edu.my [203.106.62.11]) by hub.freebsd.org (Postfix) with ESMTP id DF6B937B420 for ; Thu, 27 Sep 2001 04:27:22 -0700 (PDT) Received: from venus.cyber.mmu.edu.my (venus.cyber.mmu.edu.my [203.106.62.12]) by mmu.edu.my (8.9.1b+Sun/8.9.1) with ESMTP id TAA11236; Thu, 27 Sep 2001 19:23:12 +0800 (MYT) Received: from there ([10.100.99.41]) by venus.cyber.mmu.edu.my (8.8.8+Sun/8.8.8) with SMTP id TAA22756; Thu, 27 Sep 2001 19:22:58 +0800 (SGT) Message-Id: <200109271122.TAA22756@venus.cyber.mmu.edu.my> Content-Type: text/plain; charset="iso-8859-1" From: nuzrin yaapar Reply-To: nuzrin@goose.net.my Organization: multimedia university To: Josef Karthauser , Stephen Hurd Subject: Re: Patch to allow disabling logging of arp movements through sysctl Date: Thu, 27 Sep 2001 19:36:23 +0800 X-Mailer: KMail [version 1.3] Cc: net@FreeBSD.org References: <20010903224210.C28738@tao.org.uk> In-Reply-To: <20010903224210.C28738@tao.org.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org is there any chance this patch will be commited soon to the -STABLE tree? i'm having a similar problems and it's driving me crazy. my log is full with all the arp movement messages. On Tuesday 04 September 2001 5:42 am, Josef Karthauser wrote: > You should really send this to net@FreeBSD.org (Cc'd). Filing a -PR is a > good thing too, as you can always refer to the -PR number in any mail to > the list. > > Joe > > On Mon, Sep 03, 2001 at 03:43:41PM -0600, Stephen Hurd wrote: > > I've had a problem with my DSL connection for some time now, the bridging > > they use appears to forward arp responses AND respond to arp requests. > > This ends up filling my log with: > > > > Sep 3 15:17:57 tw2 /kernel: arp: 216.13.207.2 moved from > > 00:06:29:d5:04:c7 to 00:10:b5:4f:d1:1a on rl0 > > Sep 3 15:17:57 tw2 /kernel: arp: 216.13.207.2 moved from > > 00:10:b5:4f:d1:1a to 00:06:29:d5:04:c7 on rl0 > > > > I've dug around on the list archives, and it looks like I'm not the first > > person to get annoyed at this, but I haven't found a solution. So, I've > > finally gotten so annoyed at my huge logs that I broke down and added the > > following patch to add the sysctl variable > > net.link.ether.inet.log_arp_movements > > > > Is this the "right place" to send the patch or should I file a PR? > > > > --- /usr/src/sys/netinet/if_ether.c.old Mon Sep 3 14:26:38 2001 > > +++ /usr/src/sys/netinet/if_ether.c Mon Sep 3 15:13:08 2001 > > @@ -497,10 +497,15 @@ > > * but formerly didn't normally send requests. > > */ > > static int log_arp_wrong_iface = 1; > > +static int log_arp_movements = 1; > > > > SYSCTL_INT(_net_link_ether_inet, OID_AUTO, log_arp_wrong_iface, > > CTLFLAG_RW, &log_arp_wrong_iface, 0, > > "log arp packets arriving on the wrong interface"); > > +SYSCTL_INT(_net_link_ether_inet, OID_AUTO, log_arp_movements, > > CTLFLAG_RW, + &log_arp_movements, 0, > > + "log arp replies from MACs different the the one in the cache"); > > + > > > > static void > > in_arpinput(m) > > @@ -586,12 +591,13 @@ > > } > > if (sdl->sdl_alen && > > bcmp((caddr_t)ea->arp_sha, LLADDR(sdl), sdl->sdl_alen)) { > > - if (rt->rt_expire) > > - log(LOG_INFO, "arp: %s moved from %6D to %6D on %s%d\n", > > - inet_ntoa(isaddr), (u_char *)LLADDR(sdl), ":", > > - ea->arp_sha, ":", > > - ac->ac_if.if_name, ac->ac_if.if_unit); > > - else { > > + if (rt->rt_expire) { > > + if (log_arp_movements) > > + log(LOG_INFO, "arp: %s moved from %6D to %6D on %s%d\n", > > + inet_ntoa(isaddr), (u_char *)LLADDR(sdl), ":", > > + ea->arp_sha, ":", > > + ac->ac_if.if_name, ac->ac_if.if_unit); > > + } else { > > log(LOG_ERR, > > "arp: %6D attempts to modify permanent entry for %s on %s%d\n", > > ea->arp_sha, ":", inet_ntoa(isaddr), > > > > > > > > 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 Thu Sep 27 4:40:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from server1.lordlegacy.org (lordlegacy.org [209.61.182.147]) by hub.freebsd.org (Postfix) with ESMTP id A26B637B40A for ; Thu, 27 Sep 2001 04:40:35 -0700 (PDT) Received: from sharon ([216.13.207.127]) by server1.lordlegacy.org (8.9.3/8.9.3) with SMTP id BAA21260; Thu, 27 Sep 2001 01:53:00 -0500 From: "Stephen Hurd" To: , "Josef Karthauser" , "Stephen Hurd" Cc: Subject: RE: Patch to allow disabling logging of arp movements through sysctl Date: Thu, 27 Sep 2001 05:51:26 -0600 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <200109271122.TAA22756@venus.cyber.mmu.edu.my> X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > is there any chance this patch will be commited soon to the -STABLE > tree? i'm > having a similar problems and it's driving me crazy. my log is full > with all > the arp movement messages. As I understand it, there's a very good change... possibly so good that it's already done. ;-) Alfred Perlstein asked me to remind him about it after 4.4-RELEASE and I did, so it's probobly already done. Or if it isn't, it will be shortly I would think... then I can brag to all my geek friends that I wrote a kernel patch for FreeBSD and it was accepted! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 8:26:34 2001 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 CF63F37B422 for ; Thu, 27 Sep 2001 08:26:21 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f8RFPqg29115; Thu, 27 Sep 2001 09:25:52 -0600 (MDT) (envelope-from ken) Date: Thu, 27 Sep 2001 09:25:52 -0600 From: "Kenneth D. Merry" To: Matthew Rezny Cc: "net@freebsd.org" Subject: Re: Alteon gigE NIC (if_ti driver) problems Message-ID: <20010927092551.A29083@panzer.kdm.org> References: <20010926205541.10F5A37B417@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010926205541.10F5A37B417@hub.freebsd.org>; from mrezny@umr.edu on Wed, Sep 26, 2001 at 03:55:30PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Sep 26, 2001 at 15:55:30 -0500, Matthew Rezny wrote: > I have some more information since my initial posting yesterday. I set > the NMBCLUSTERS back to default, which made no difference. Therefore, > moving from 4.3 to 4.4 is what drastically increased the frequency at > which the link goes down and back up. I also captured dmesg now I case > there is any useful information in it. The fluctuation of the link > occurs multiple times a second with the new kernel when attempting to > use the network with this machine. Any suggestions would be greatly > appreciated. Thanks. [ ... ] > ti0: mem > 0x82850000-0x82853fff irq 11 at device 6.0 on pci0 > ti0: interrupting at CIA irq 11 > ti0: Ethernet address: 00:60:cf:20:1e:99 [ ... ] > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up > ti0: link down > ti0: gigabit link up [ ... ] The most likely explanation for this is that you've got a bad/dirty piece of fiber. The number of mbuf clusters probably isn't going to affect this at all, unless you're dumping a lot of traffic over the NIC and increasing the number of mbufs allows you to dump more packets. So I'd say replace your fiber. 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 Thu Sep 27 8:28:28 2001 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 0057537B503 for ; Thu, 27 Sep 2001 08:28:15 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f8RFS4T29148; Thu, 27 Sep 2001 09:28:04 -0600 (MDT) (envelope-from ken) Date: Thu, 27 Sep 2001 09:28:04 -0600 From: "Kenneth D. Merry" To: Sam Tannous Cc: freebsd-net@FreeBSD.ORG Subject: Re: 3COM 3c985-SX or 3c985B-SX Message-ID: <20010927092804.B29083@panzer.kdm.org> References: <20010926163606.B8081@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010926163606.B8081@cisco.com>; from stannous@cisco.com on Wed, Sep 26, 2001 at 04:36:06PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Sep 26, 2001 at 16:36:06 -0400, Sam Tannous wrote: > >From what I've seen in this list, this seems > to be the best performing gigabit ethernet card > on FreeBSD. Most stores now stock the newer > 3c985B-SX rather then the 3c985-SX. Does the existing > driver handle the newer "b" card as well as the > old card? I just want to make sure before I go > ordering 4 cards. The 3c985B is a Tigon 2 board with 1MB SRAM, and should work just fine. 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 Thu Sep 27 8:56:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailtest.btconnex.net (mailtest.btconnex.net [209.47.192.8]) by hub.freebsd.org (Postfix) with SMTP id E093737B42B for ; Thu, 27 Sep 2001 08:56:23 -0700 (PDT) Received: (qmail 10594 invoked from network); 27 Sep 2001 15:56:09 -0000 Received: from unknown (HELO ?192.168.66.37?) (192.168.66.37) by mailtest.btconnex.net with SMTP; 27 Sep 2001 15:56:09 -0000 Date: Thu, 27 Sep 2001 11:56:06 -0400 (EDT) From: Elliott Perrin X-X-Sender: To: , Subject: VPN over VLANS and dynamic clients Message-ID: <20010927114500.W77821-100000@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello there, I am not currently subscribed to net or security so if I could be CC'ed on all replies that would be excellent. I am trying to setup VPN connectivity for a client that needs to be able to log in to their office from dynamic IP's. I have setup VLANS over an fxp card that corespond to their VLAN in our Cisco's. BTW, it is not an option to setup the VPN through the Cisco as I cannot specify more than one policy and we already have a client's VPN running through the Cisco. The FBSD box has public IP and a private IP, both on vlan interfaces (vlan0 and vlan1) with the private IP sitting on the subnet of the client. I want to be able to have a client authenticate and be handed an IP from the LAN that they are connecting to. so it would look like this. client - dynamic IP ----> pub ip on FBSD--192.168. on FBSD (part of LAN) |--------------------------------------| need encryption between here Have I been hitting the pipe too much this morning or is there a way to accomplish this??? Any hints, advice are more than welcome. Thanks eperrin@beanfield.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 9:48:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.fidnet.com (one.fidnet.com [205.216.200.51]) by hub.freebsd.org (Postfix) with SMTP id D337D37B41B for ; Thu, 27 Sep 2001 09:48:52 -0700 (PDT) Received: (qmail 793 invoked from network); 27 Sep 2001 16:48:46 -0000 Received: from unknown (HELO Beast) (216.229.82.132) by 0 with SMTP; 27 Sep 2001 16:48:46 -0000 From: "Matthew Rezny" To: "Kenneth D. Merry" Cc: "net@freebsd.org" Date: Thu, 27 Sep 2001 11:48:56 -0500 Reply-To: "Matthew Rezny" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195;2) In-Reply-To: <20010927092551.A29083@panzer.kdm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Alteon gigE NIC (if_ti driver) problems Message-Id: <20010927164852.D337D37B41B@hub.freebsd.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for the suggestion, it set me in the right direction. I checked my fibre before but went ahead and checked it again. In doing so, I rearranged the cables at the switch to check if that made a difference. Sure enough, one port on the switch makes the connection drop often. I hope its just dust in the port and not something more serious. The important thing is it looks like everything is working now. On Thu, 27 Sep 2001 09:25:52 -0600, Kenneth D. Merry wrote: >On Wed, Sep 26, 2001 at 15:55:30 -0500, Matthew Rezny wrote: >> I have some more information since my initial posting yesterday. I set >> the NMBCLUSTERS back to default, which made no difference. Therefore, >> moving from 4.3 to 4.4 is what drastically increased the frequency at >> which the link goes down and back up. I also captured dmesg now I case >> there is any useful information in it. The fluctuation of the link >> occurs multiple times a second with the new kernel when attempting to >> use the network with this machine. Any suggestions would be greatly >> appreciated. Thanks. > >[ ... ] > >> ti0: mem >> 0x82850000-0x82853fff irq 11 at device 6.0 on pci0 >> ti0: interrupting at CIA irq 11 >> ti0: Ethernet address: 00:60:cf:20:1e:99 > >[ ... ] > >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >[ ... ] > >The most likely explanation for this is that you've got a bad/dirty >piece of fiber. The number of mbuf clusters probably isn't going to >affect this at all, unless you're dumping a lot of traffic over the >NIC and increasing the number of mbufs allows you to dump more >packets. > >So I'd say replace your fiber. > >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 Thu Sep 27 10:15:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by hub.freebsd.org (Postfix) with ESMTP id 130BD37B428 for ; Thu, 27 Sep 2001 10:15:32 -0700 (PDT) Received: from milk.yahoo.com (milk.yahoo.com [216.145.52.137]) by mrout2.yahoo.com (8.11.6/8.11.6/y.out) with ESMTP id f8RHEx911343; Thu, 27 Sep 2001 10:14:59 -0700 (PDT) Received: (from root@localhost) by milk.yahoo.com (8.11.0/8.11.0) id f8RHExg26899; Thu, 27 Sep 2001 10:14:59 -0700 (PDT) (envelope-from jayanth) Date: Thu, 27 Sep 2001 10:14:59 -0700 From: jayanth To: tsuchiya@flab.fujitsu.co.jp Cc: jayanth@yahoo-inc.com, net@FreeBSD.ORG, silby@silby.com Subject: Re: TCP performance question Message-ID: <20010927101459.A26671@yahoo-inc.com> References: <200109270652.PAA03232@const.kawasaki.flab.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200109270652.PAA03232@const.kawasaki.flab.fujitsu.co.jp>; from tsuchiya@flab.fujitsu.co.jp on Thu, Sep 27, 2001 at 03:52:15PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Probably add a new flag TF_IDLE that is true, if there is more data to send when the connection was idle. This way the next time around the idle variable will be true if the TF_IDLE flag is true and if we can empty the socket buffer all the data will be sent. Will send you a patch soon. jayanth tsuchiya@flab.fujitsu.co.jp (tsuchiya@flab.fujitsu.co.jp) wrote: > > > This issue is a combination of mbuf cluster size and the > > TF_MORETOCOME flag. > > > if (len) { > > if (len == tp->t_maxseg) > > goto send; > > if (!(tp->t_flags & TF_MORETOCOME) && > > (idle || tp->t_flags & TF_NODELAY) && > > (tp->t_flags & TF_NOPUSH) == 0 && > > len + off >= so->so_snd.sb_cc) > > goto send; > > When I changed the condition, the problem we had did not occur. I am wondering > what is the right fix. > Yoshi > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 10:16: 1 2001 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 1676E37B637 for ; Thu, 27 Sep 2001 10:15:48 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f8RHFZI29890; Thu, 27 Sep 2001 11:15:35 -0600 (MDT) (envelope-from ken) Date: Thu, 27 Sep 2001 11:15:34 -0600 From: "Kenneth D. Merry" To: Matthew Rezny Cc: "net@freebsd.org" Subject: Re: Alteon gigE NIC (if_ti driver) problems Message-ID: <20010927111534.A29860@panzer.kdm.org> References: <20010927092551.A29083@panzer.kdm.org> <200109271648.f8RGmm829714@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: <200109271648.f8RGmm829714@panzer.kdm.org>; from mrezny@umr.edu on Thu, Sep 27, 2001 at 11:48:56AM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Sep 27, 2001 at 11:48:56 -0500, Matthew Rezny wrote: > Thanks for the suggestion, it set me in the right direction. I checked > my fibre before but went ahead and checked it again. In doing so, I > rearranged the cables at the switch to check if that made a difference. > Sure enough, one port on the switch makes the connection drop often. I > hope its just dust in the port and not something more serious. The > important thing is it looks like everything is working now. Yeah, it's probably dust. If you got any rubber plugs with the switch, you may want to make sure you keep those in the ports when they're not otherwise in use, to keep dust out. 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 Thu Sep 27 10:52:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from hirogen.kabelfoon.nl (hirogen.kabelfoon.nl [62.45.45.69]) by hub.freebsd.org (Postfix) with ESMTP id BB7ED37B507 for ; Thu, 27 Sep 2001 10:52:39 -0700 (PDT) Received: from ntpc (kf-pij-tg01-426.dial.kabelfoon.nl [62.45.89.172]) by hirogen.kabelfoon.nl (Postfix) with SMTP id 3361F7C8B; Thu, 27 Sep 2001 19:52:33 +0200 (CEST) From: "Peter Blok" To: "'ipver four'" , Subject: RE: FreeBSD and Cisco router IPSEC tunnel Date: Thu, 27 Sep 2001 19:47:44 +0200 Message-ID: <000101c1477c$83c706a0$8a02a8c0@ntpc> 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 CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org What router are you talking about? The ex-Altiga routers, or Cisco's own -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of ipver four Sent: Thursday, September 27, 2001 04:03 To: freebsd-net@FreeBSD.ORG Subject: FreeBSD and Cisco router IPSEC tunnel Has anyone successfully setup an IPSEC tunnel between a FreeBSD box and a Cisco router? If positive, can you tell me how to do it? Thanks, John _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp 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 Thu Sep 27 11:15:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from zogbe.tasam.com (uta-ip196.ntc.off-campus.vt.edu [63.165.178.196]) by hub.freebsd.org (Postfix) with ESMTP id C3B2437B41A for ; Thu, 27 Sep 2001 11:15:12 -0700 (PDT) Received: from localhost (clash@localhost) by zogbe.tasam.com (8.11.6/8.11.6) with ESMTP id f8RIEgh51563; Thu, 27 Sep 2001 14:14:47 -0400 (EDT) Date: Thu, 27 Sep 2001 14:14:41 -0400 (EDT) From: Joseph Gleason To: Kris Kirby Cc: Subject: Re: Network optimization? In-Reply-To: Message-ID: <20010927140608.T42171-100000@zogbe.tasam.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To isolate drives from network, I usually use dd, faucet and hose to test the network. cd /usr/ports/net/netpipes make install clean on System A: faucet 45363 --in dd if=/dev/stdin of=/dev/null bs=1k on System B: hose HostA 45363 --out dd if=/dev/zero of=/dev/stdout bs=1k count=1m Of course, adjust the bs and count if you want. When it completed, the dd will tell you the transfer rate. This will give you network performance independant of drives. Then you can use benchmarking tools from the ports tree to test your drives. Armed with the this info, you should be able to isolate the problem subsystem. I hope my dirty little method is useful to you. Good luck. On Thu, 27 Sep 2001, Kris Kirby wrote: > > Please, if I have addressed this wrong, do not hesitate to point me toward > another list. > > I'm looking for tips on network / kernel optimization. I know that when > 100Mb/s ethernet first came to FreeBSD, there were P90s moving at 9MB/s, > but I've never been able to break 7MB/s, except for my K7-850 with > Barricuda hard drives (9.0). I'm using xl's on most machine (K7 as well) > with a fxp in my P166 with SCSI drives (sees only ~6 MB/s on a good day). > > Any ideas? I've got 2560 total mbuf clusters on the P166; I can't really > think of much else to change to speed things up... > > ----- > Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. > | > ------------------------------------------------------- > "Fate, it seems, is not without a sense of irony." > > > 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 Thu Sep 27 12: 8:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by hub.freebsd.org (Postfix) with ESMTP id BB26837B408 for ; Thu, 27 Sep 2001 12:08:15 -0700 (PDT) Received: from milk.yahoo.com (milk.yahoo.com [216.145.52.137]) by mrout1.yahoo.com (8.11.6/8.11.6/y.out) with ESMTP id f8RJ7of10839 for ; Thu, 27 Sep 2001 12:07:50 -0700 (PDT) Received: (from root@localhost) by milk.yahoo.com (8.11.0/8.11.0) id f8RJ7or27801 for net@Freebsd.org; Thu, 27 Sep 2001 12:07:50 -0700 (PDT) (envelope-from jayanth) Date: Thu, 27 Sep 2001 12:07:50 -0700 From: jayanth To: net@Freebsd.org Subject: simple udp question Message-ID: <20010927120750.C26671@yahoo-inc.com> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org one of the developers here noticed that if a process does the following three steps: binds a udp socket to a specific IP address connects the udp socket calls connect with a NULL parameter, to disconnect the socket. The socket now loses its originally bound IP address because udp_disconnect forces the local address of the socket to be INADDR_ANY. Can we change this behaviour to retain the originally bound IP address ? thanks, jayanth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 14:15: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id CDDCD37B410 for ; Thu, 27 Sep 2001 14:15:04 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id OAA20260; Thu, 27 Sep 2001 14:01:41 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f8RL1ep95144; Thu, 27 Sep 2001 14:01:40 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200109272101.f8RL1ep95144@arch20m.dellroad.org> Subject: Re: simple udp question In-Reply-To: <20010927120750.C26671@yahoo-inc.com> "from jayanth at Sep 27, 2001 12:07:50 pm" To: jayanth Date: Thu, 27 Sep 2001 14:01:40 -0700 (PDT) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org jayanth writes: > one of the developers here noticed that if a process does > the following three steps: > > binds a udp socket to a specific IP address > connects the udp socket > calls connect with a NULL parameter, to disconnect the socket. > > The socket now loses its originally bound IP address because > udp_disconnect forces the local address of the socket to be INADDR_ANY. > > Can we change this behaviour to retain the originally bound IP address ? Sounds logical to me.. It might be worth doing some research to figure out if there was some reason for forcing the address to INADDR_ANY in the first place, i.e., if this was done to fix some other bug somewhere (which we'd be resurrecting). -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 17:26:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f112.law14.hotmail.com [64.4.21.112]) by hub.freebsd.org (Postfix) with ESMTP id 2169337B40B for ; Thu, 27 Sep 2001 17:26:54 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 27 Sep 2001 17:26:53 -0700 Received: from 138.89.20.42 by lw14fd.law14.hotmail.msn.com with HTTP; Fri, 28 Sep 2001 00:26:53 GMT X-Originating-IP: [138.89.20.42] From: "ipver four" To: pblok@inter.NL.net, freebsd-net@FreeBSD.ORG Subject: RE: FreeBSD and Cisco router IPSEC tunnel Date: Thu, 27 Sep 2001 20:26:53 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 28 Sep 2001 00:26:53.0961 (UTC) FILETIME=[46252790:01C147B4] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >What router are you talking about? The ex-Altiga routers, or Cisco's own I am thinking about Cisco 7200 or 3600 series. Thanks, John _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 27 18:28:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from neogw.osaka.iij.ad.jp (neogw.osaka.iij.ad.jp [202.232.14.130]) by hub.freebsd.org (Postfix) with ESMTP id 3F7AA37B40B for ; Thu, 27 Sep 2001 18:28:13 -0700 (PDT) Received: by neogw.osaka.iij.ad.jp; id KAA17760; Fri, 28 Sep 2001 10:28:12 +0900 (JST) Received: from keiichi01.osaka.iij.ad.jp(192.168.65.66) by neogw.osaka.iij.ad.jp via smap (V4.2) id xma017753; Fri, 28 Sep 01 10:27:44 +0900 Received: from keiichi01.osaka.iij.ad.jp (localhost.osaka.iij.ad.jp [127.0.0.1]) by keiichi01.osaka.iij.ad.jp (8.11.3/8.11.3) with ESMTP id f8R9ZEJ27065; Thu, 27 Sep 2001 18:35:26 +0900 (JST) (envelope-from keiichi@iij.ad.jp) Date: Thu, 27 Sep 2001 18:35:14 +0900 Message-ID: <86zo7h2cz1.wl@keiichi01.osaka.iij.ad.jp> From: Keiichi SHIMA / =?ISO-2022-JP?B?GyRCRWc3RDBsGyhC?= To: Cc: "Alex Feldman" Subject: Re: Ipv6 In-Reply-To: References: User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.2 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Internet Initiative Japan Inc. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Alex Feldman wrote: > > I update the driver to accept IPv6 address. > When I configure interface for both IPv4 and IPv6, everything is good (I > can > ping), but when I'm using only IPv6, the remote machine not replying to my > request. > > Is it some configuration problem? Or something else? Currently the DNS system requires IPv4 transport. If you disable IPv4 completely, you cannot resolve any hostnames. In this case, you must set up DNS proxy (ex. totd) from IPv6 to IPv4. Is this your case, isn't it? --- Keiichi SHIMA IIJ Research Laboratory KAME Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 2:53:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from shikima.mine.nu (pc1-card3-0-cust115.cdf.cable.ntl.com [62.252.49.115]) by hub.freebsd.org (Postfix) with ESMTP id 6400537B406 for ; Fri, 28 Sep 2001 02:53:11 -0700 (PDT) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 15muKg-00008P-00 for freebsd-net@freebsd.org; Fri, 28 Sep 2001 10:53:22 +0100 Date: Fri, 28 Sep 2001 10:53:22 +0100 From: Rasputin To: freebsd-net@freebsd.org Subject: IPSec basics Message-ID: <20010928105322.A494@shikima.mine.nu> Reply-To: Rasputin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi there, I'm about to try to set IPSec over a wireless link (as WEP can't be trusted), and just wanted to check I have the concepts straight in my head. One end is an iBook which connects to the Net via a FreeBSD gateway, posing as an Airport. The FreeBSD box runs ipf and ipnat. The iBook will be using PGPDesktopSecurity, since that's the only IPSec client for OS9 I know of. All I want to do is encrypt traffic over the wireless, and use it for authentication as well. This is a pure IPv4 setup ,and all I *think* I need is transport mode. I hear IPSec doesn't grok NAT, but I'm hoping this is referring to tunnel mode (i.e. VPNs). Just wanted to check that would work. Also, will the ruleset on the firewall need changing, or is IPsec handled before the packets hit the firewall? If changes are needed, a tutorial would be very useful. Thnaks a lot. -- "Hey! Who took the cork off my lunch??!" -- W. C. Fields Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 6: 5:54 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail11.uunet.ca (mail11.uunet.ca [142.77.1.48]) by hub.freebsd.org (Postfix) with ESMTP id 4456A37B405 for ; Fri, 28 Sep 2001 06:05:51 -0700 (PDT) Received: from alexdev ([207.176.248.4]) by mail11.uunet.ca with SMTP id <71453-4060>; Fri, 28 Sep 2001 09:02:50 -0400 From: "Alex Feldman" To: "=?us-ascii?B?S2VpaWNoaSBTSElNQSAvICI/T2NeZQ==?=" , Subject: RE: Ipv6 Date: Fri, 28 Sep 2001 08:59:32 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <86zo7h2cz1.wl@keiichi01.osaka.iij.ad.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Currently the DNS system requires IPv4 transport. If you disable IPv4 >completely, you cannot resolve any hostnames. In this case, you must >set up DNS proxy (ex. totd) from IPv6 to IPv4. Is this your case, >isn't it? Not, because I connected two machine back to back. Btw, when I set ipv6_forwarding to 1, I was able to ping6. But more interesting, when I next time boot this machine (ipv6_forwarding set to 0 by default), I was still able to ping6. So, what is happened? Thank you. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 8:46:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from ardbeg.meer.net (ardbeg.meer.net [209.157.152.23]) by hub.freebsd.org (Postfix) with ESMTP id 9D7C337B40E for ; Fri, 28 Sep 2001 08:46:10 -0700 (PDT) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by ardbeg.meer.net (8.11.3/8.11.3) with ESMTP id f8SFk5j16865 for ; Fri, 28 Sep 2001 08:46:05 -0700 (PDT) Received: from neville-neil.com (pm3b-87.mv.meer.net [209.157.137.87]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id IAA2483610 for ; Fri, 28 Sep 2001 08:45:13 -0700 (PDT) Message-Id: <200109281545.IAA2483610@meer.meer.net> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-net@freebsd.org Subject: Who are the core people on net? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Sep 2001 08:45:29 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi Folks, I was going to send a more targetted email for information on the future plans on the TCP/IP stack for FreeBSD but the web site does not have a section (that I can find quickly) on just who the core team for networking is. Would those folks please send me an email? Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 9: 3:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 1114A37B410 for ; Fri, 28 Sep 2001 09:03:50 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA71157; Fri, 28 Sep 2001 09:57:00 -0700 (PDT) Date: Fri, 28 Sep 2001 09:57:00 -0700 (PDT) From: Julian Elischer To: Rasputin Cc: freebsd-net@freebsd.org Subject: Re: IPSec basics In-Reply-To: <20010928105322.A494@shikima.mine.nu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org how does a freebsd machine pose as an airport? That requires you run special AP firmware on the card. On Fri, 28 Sep 2001, Rasputin wrote: > > Hi there, > > I'm about to try to set IPSec over a wireless link (as WEP can't be trusted), > and just wanted to check I have the concepts straight in my head. > > One end is an iBook which connects to the Net via a FreeBSD > gateway, posing as an Airport. > > The FreeBSD box runs ipf and ipnat. > The iBook will be using PGPDesktopSecurity, since that's the > only IPSec client for OS9 I know of. > > All I want to do is encrypt traffic over the wireless, > and use it for authentication as well. > > This is a pure IPv4 setup ,and all I *think* I need is > transport mode. > > I hear IPSec doesn't grok NAT, but I'm hoping this is referring > to tunnel mode (i.e. VPNs). > > Just wanted to check that would work. > > Also, will the ruleset on the firewall need changing, or > is IPsec handled before the packets hit the firewall? > > If changes are needed, a tutorial would be very useful. > > Thnaks a lot. > -- > "Hey! Who took the cork off my lunch??!" > -- W. C. Fields > Rasputin :: Jack of All Trades - Master of Nuns :: > > 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 Sep 28 10:24:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 250A537B40B for ; Fri, 28 Sep 2001 10:24:39 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id D575781D0B; Fri, 28 Sep 2001 12:24:33 -0500 (CDT) Date: Fri, 28 Sep 2001 12:24:33 -0500 From: Alfred Perlstein To: "George V. Neville-Neil" Cc: freebsd-net@freebsd.org Subject: Re: Who are the core people on net? Message-ID: <20010928122433.G59854@elvis.mu.org> References: <200109281545.IAA2483610@meer.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109281545.IAA2483610@meer.meer.net>; from gnn@neville-neil.com on Fri, Sep 28, 2001 at 08:45:29AM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * George V. Neville-Neil [010928 10:46] wrote: > Hi Folks, > > I was going to send a more targetted email for information > on the future plans on the TCP/IP stack for FreeBSD but the web site does > not have a section (that I can find quickly) on just who the core team for > networking is. Would those folks please send me an email? Sending it to -net would work, you might want to cc jlemon and silby @freebsd, possibly me as well. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 12:12: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id BE98A37B403; Fri, 28 Sep 2001 12:12:05 -0700 (PDT) Subject: Driver kit for BCM570x gigE NICs To: freebsd-hackers@freebsd.org Date: Fri, 28 Sep 2001 12:12:05 -0700 (PDT) Cc: 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 Message-Id: <20010928191205.BE98A37B403@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have made a driver retrofit kit available for Broadcom BCM570x-based gigabit ethernet cards at the following URL: http://www.freebsd.org/~wpaul/Broadcom/4.x/bcm570x_drv.tar.gz This kit contains source and pre-compiled driver modules for FreeBSD 4.3-RELEASE and later. This should make it easier for people to test the bge driver on existing 4.x systems without having to recompile the kernel. Again, I would appreciate hearing from people who have cards that use this chipset and can test the driver. If you can run speed tests with things like netperf, ttcp or just plain file/data transfers, I'd be interested to see the results. Share and enjoy! -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "You stole fizzy lifting drinks. You broke the rules. You LOSE." -W. Wonka ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 12:43:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by hub.freebsd.org (Postfix) with ESMTP id 0E7AA37B40F for ; Fri, 28 Sep 2001 12:43:36 -0700 (PDT) Received: from milk.yahoo.com (milk.yahoo.com [216.145.52.137]) by mrout1.yahoo.com (8.11.6/8.11.6/y.out) with ESMTP id f8SJhQf31029; Fri, 28 Sep 2001 12:43:26 -0700 (PDT) Received: (from root@localhost) by milk.yahoo.com (8.11.0/8.11.0) id f8SJhP637382; Fri, 28 Sep 2001 12:43:25 -0700 (PDT) (envelope-from jayanth) Date: Fri, 28 Sep 2001 12:43:25 -0700 From: jayanth To: tsuchiya@flab.fujitsu.co.jp Cc: jayanth@yahoo-inc.com, net@FreeBSD.ORG, silby@silby.com, jlemon@flugsvamp.com Subject: Re: TCP performance question Message-ID: <20010928124325.B36879@yahoo-inc.com> References: <200109270652.PAA03232@const.kawasaki.flab.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="NMuMz9nt05w80d4+" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200109270652.PAA03232@const.kawasaki.flab.fujitsu.co.jp>; from tsuchiya@flab.fujitsu.co.jp on Thu, Sep 27, 2001 at 03:52:15PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Yoshi, I have attached a patch. Let me know if this fixes the problem. jayanth tsuchiya@flab.fujitsu.co.jp (tsuchiya@flab.fujitsu.co.jp) wrote: > > > This issue is a combination of mbuf cluster size and the > > TF_MORETOCOME flag. > > > if (len) { > > if (len == tp->t_maxseg) > > goto send; > > if (!(tp->t_flags & TF_MORETOCOME) && > > (idle || tp->t_flags & TF_NODELAY) && > > (tp->t_flags & TF_NOPUSH) == 0 && > > len + off >= so->so_snd.sb_cc) > > goto send; > > When I changed the condition, the problem we had did not occur. I am wondering > what is the right fix. > Yoshi > > --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="idle.patch" --- tcp_output.c Fri Sep 28 11:15:32 2001 +++ tcp_output.c.new Fri Sep 28 12:05:03 2001 @@ -133,7 +133,7 @@ * If there is some data or critical controls (SYN, RST) * to send, then transmit; otherwise, investigate further. */ - idle = (tp->snd_max == tp->snd_una); + idle = (tp->t_flags & TF_LASTIDLE) ? 1 : (tp->snd_max == tp->snd_una); if (idle && (ticks - tp->t_rcvtime) >= tp->t_rxtcur) { /* * We have been idle for "a while" and no acks are @@ -156,6 +156,13 @@ tp->snd_cwnd = tp->t_maxseg * ss_fltsz_local; else tp->snd_cwnd = tp->t_maxseg * ss_fltsz; + } + tp->t_flags &= ~TF_LASTIDLE; + if (idle) { + if (tp->t_flags & TF_MORETOCOME) { + tp->t_flags |= TF_LASTIDLE; + idle = 0; + } } again: sendalot = 0; --- tcp_var.h Fri Sep 28 11:11:48 2001 +++ tcp_var.h.new Fri Sep 28 12:04:09 2001 @@ -95,6 +95,7 @@ #define TF_SENDCCNEW 0x08000 /* send CCnew instead of CC in SYN */ #define TF_MORETOCOME 0x10000 /* More data to be appended to sock */ #define TF_LQ_OVERFLOW 0x20000 /* listen queue overflow */ +#define TF_LASTIDLE 0x40000 /* idle, when previously called */ int t_force; /* 1 if forcing out a byte */ tcp_seq snd_una; /* send unacknowledged */ --NMuMz9nt05w80d4+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 12:53:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from shikima.mine.nu (pc1-card3-0-cust115.cdf.cable.ntl.com [62.252.49.115]) by hub.freebsd.org (Postfix) with ESMTP id 9A3DC37B407 for ; Fri, 28 Sep 2001 12:53:43 -0700 (PDT) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 15n3hL-0007a1-00; Fri, 28 Sep 2001 20:53:23 +0100 Date: Fri, 28 Sep 2001 20:53:23 +0100 From: Rasputin To: Julian Elischer Cc: freebsd-net@freebsd.org Subject: Re: IPSec basics Message-ID: <20010928205323.A29122@shikima.mine.nu> Reply-To: Rasputin References: <20010928105322.A494@shikima.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Fri, Sep 28, 2001 at 09:57:00AM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Julian Elischer [010928 17:05]: > > how does a freebsd machine pose as an airport? > That requires you run special AP firmware on the card. Not really, you set up an iBSS and the iBook treats it as though it were an airport. You don't get all the power-saving features of a true airport, but stick a DHCP server on wi0 and the clients don't seem to be any the wiser.... -- If you can't learn to do it well, learn to enjoy doing it badly. Nuns :: Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 13:14:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 5166337B40D for ; Fri, 28 Sep 2001 13:14:18 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id E631181D0B; Fri, 28 Sep 2001 15:14:12 -0500 (CDT) Date: Fri, 28 Sep 2001 15:14:12 -0500 From: Alfred Perlstein To: jayanth Cc: tsuchiya@flab.fujitsu.co.jp, net@FreeBSD.ORG, silby@silby.com, jlemon@flugsvamp.com Subject: Re: TCP performance question Message-ID: <20010928151412.J59854@elvis.mu.org> References: <200109270652.PAA03232@const.kawasaki.flab.fujitsu.co.jp> <20010928124325.B36879@yahoo-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010928124325.B36879@yahoo-inc.com>; from jayanth@yahoo-inc.com on Fri, Sep 28, 2001 at 12:43:25PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * jayanth [010928 14:43] wrote: > Yoshi, > I have attached a patch. Let me know if this fixes the problem. > > jayanth cool, but.. > --- tcp_output.c Fri Sep 28 11:15:32 2001 > +++ tcp_output.c.new Fri Sep 28 12:05:03 2001 > @@ -133,7 +133,7 @@ > * If there is some data or critical controls (SYN, RST) > * to send, then transmit; otherwise, investigate further. > */ > - idle = (tp->snd_max == tp->snd_una); > + idle = (tp->t_flags & TF_LASTIDLE) ? 1 : (tp->snd_max == tp->snd_una); how about: idle = (tp->t_flags & TF_LASTIDLE) || (tp->snd_max == tp->snd_una); -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 13:23:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C5A0937B40D for ; Fri, 28 Sep 2001 13:23:31 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA72174; Fri, 28 Sep 2001 14:19:00 -0700 (PDT) Date: Fri, 28 Sep 2001 14:19:00 -0700 (PDT) From: Julian Elischer To: Rasputin Cc: freebsd-net@freebsd.org Subject: Re: IPSec basics In-Reply-To: <20010928205323.A29122@shikima.mine.nu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org that is NOT running as an AP. but of course it will do what you want. just don't expect it to work as an AP.. On Fri, 28 Sep 2001, Rasputin wrote: > * Julian Elischer [010928 17:05]: > > > > how does a freebsd machine pose as an airport? > > That requires you run special AP firmware on the card. > > Not really, you set up an iBSS and the iBook treats it as though it > were an airport. > > You don't get all the power-saving features of a true airport, but stick > a DHCP server on wi0 and the clients don't seem to be any the wiser.... > > -- > If you can't learn to do it well, learn to enjoy doing it badly. > Nuns :: > Rasputin :: Jack of All Trades - Master of Nuns :: > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 13:46:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from shikima.mine.nu (pc1-card3-0-cust115.cdf.cable.ntl.com [62.252.49.115]) by hub.freebsd.org (Postfix) with ESMTP id C25BB37B407 for ; Fri, 28 Sep 2001 13:46:30 -0700 (PDT) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 15n4WQ-0007ut-00; Fri, 28 Sep 2001 21:46:10 +0100 Date: Fri, 28 Sep 2001 21:46:10 +0100 From: Rasputin To: Julian Elischer Cc: freebsd-net@freebsd.org Subject: Re: IPSec basics Message-ID: <20010928214610.A30418@shikima.mine.nu> Reply-To: Rasputin References: <20010928205323.A29122@shikima.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Fri, Sep 28, 2001 at 02:19:00PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Julian Elischer [010928 21:25]: > that is NOT running as an AP. > but of course it will do what you want. > just don't expect it to work as an AP.. Well, it looks like a duck and quacks like a duck... :) But you're technically correct, fair enough. So, anyone know whether IPSec will cause problems? -- How wonderful opera would be if there were no singers. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 13:48:54 2001 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 1243337B407 for ; Fri, 28 Sep 2001 13:48:52 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8SKmaB40141; Fri, 28 Sep 2001 16:48:36 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 28 Sep 2001 16:48:36 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "George V. Neville-Neil" Cc: freebsd-net@freebsd.org Subject: Re: Who are the core people on net? In-Reply-To: <200109281545.IAA2483610@meer.meer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org freebsd-net@FreeBSD.org is always a good place to send network stack related e-mail. Another place you might want to consider sending e-mail to is freebsd-arch@FreeBSD.org, which is used for general architectural discussions. -net tends to catch a networking-oriented audience, whereas -arch will get more general architectural review. Serious architectural changes would probably have to go through both lists. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Fri, 28 Sep 2001, George V. Neville-Neil wrote: > Hi Folks, > > I was going to send a more targetted email for information > on the future plans on the TCP/IP stack for FreeBSD but the web site does > not have a section (that I can find quickly) on just who the core team for > networking is. Would those folks please send me an email? > > Thanks, > George > > > > > > 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 Sep 28 13:55: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [209.98.56.21]) by hub.freebsd.org (Postfix) with ESMTP id B4A9B37B401 for ; Fri, 28 Sep 2001 13:55:04 -0700 (PDT) Received: from localhost (swb@localhost) by accord.grasslake.net (8.11.6/8.11.6) with ESMTP id f8SKmNr09065; Fri, 28 Sep 2001 15:48:25 -0500 (CDT) (envelope-from swb@accord.grasslake.net) Date: Fri, 28 Sep 2001 15:48:23 -0500 (CDT) From: Shawn Barnhart To: Shoichi Sakane Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPSec problem, racoon can't transmit? In-Reply-To: <20010926122828R.sakane@kame.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 26 Sep 2001, Shoichi Sakane wrote: > > When I start racoon on both machines, all appears fine. To make a long > > story short, Machine A never seems to generate ANY isakmp packets. Machine > > B's racoon run-time info never indicates it's gotten a phase I initiation > > from A if the session was originated from A. I've run tcpdump on both > > machines, and A never sends any isakmp packets, although it does get them > > from B if B originates traffic first and appears to generate a response > > according to racoon debug info, but B never gets the responses (and if > > tcpdump is to believed A never sends them). > > > Both machines are running racoon-20010831a and 4.4-STABLE built yesterday. > > do you mean Machine A didn't send only isakmp packets ? > or machine A couldn't send all of packets to machine B ? Machine A didn't ever send isakmp packets to machine B, whether it originates the traffic that brings up the IPSec link or whether it should be responding to Phase I negotiation initiation with B. > the re-keying might failed. could you check the log file of racoon > on both side ? if you picked ERROR tag from the file, you could find > the problem. The ERROR tag does say that Phase I failed, and my guess is that the reason is that A isn't sending isakmp packets (tcpdump on B never sees isakmp traffic from A). Machine A is running DIVERT sockets for natd, and I think that is what's killing the connection. I haven't had time to see if that's really the case though, and if it is, it's a showstopper. -- swb@grasslake.net Hard work often pays off after time, but laziness always pays off now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 15: 1: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 4C99B37B40C for ; Fri, 28 Sep 2001 15:00:57 -0700 (PDT) Received: from ntt27f48otgmw8 (dhcp246.nttmcl.com [216.69.69.246]) by alicia.nttmcl.com (8.10.1/8.10.1) with SMTP id f8SM0uv22183 for ; Fri, 28 Sep 2001 15:00:56 -0700 (PDT) Reply-To: From: "Anuranjan" To: Subject: PCMCIA-PCI adapter issue in 4.3 freeBSD Date: Fri, 28 Sep 2001 15:01:49 -0700 Message-ID: <005e01c14869$2d00aef0$f64545d8@ntt27f48otgmw8> 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 CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'm a newbie to wireless on freeBSD. I found on some sites people mentioning that the PCMCIA-PCI adapter doesn't work on freeBSD as of now(some problem in the PCI slot being used for this purpose). Has anyone tried using it this way? Is there a patch available for this stuff? I'm trying to install an Orinoco WLAN PC card on the PCI slot and the machine doesn't boot. I saw in some discussion group a mention that the kernel crashes in case of PCI slot being used for the WLAN card adapter. Or is going for a PCMCIA-ISA adapter a better solution? -A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 15: 4:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 371FE37B409 for ; Fri, 28 Sep 2001 15:04:28 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f8SM4Cm26776; Fri, 28 Sep 2001 15:04:12 -0700 Date: Fri, 28 Sep 2001 15:04:12 -0700 From: Brooks Davis To: Anuranjan Cc: freebsd-net@FreeBSD.ORG Subject: Re: PCMCIA-PCI adapter issue in 4.3 freeBSD Message-ID: <20010928150412.A26468@Odin.AC.HMC.Edu> References: <005e01c14869$2d00aef0$f64545d8@ntt27f48otgmw8> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <005e01c14869$2d00aef0$f64545d8@ntt27f48otgmw8>; from anu@nttmcl.com on Fri, Sep 28, 2001 at 03:01:49PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 28, 2001 at 03:01:49PM -0700, Anuranjan wrote: > I'm a newbie to wireless on freeBSD. I found on some sites people mention= ing > that the PCMCIA-PCI adapter doesn't work on freeBSD as of now(some problem > in the PCI slot being used for this purpose). Has anyone tried using it t= his > way? Is there a patch available for this stuff? The Orinoco PCI-PCCard bridges are supported in 4.4. They don't work (with some vary rare exceptions) in 4.3. You ned to upgrade. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7tPPbXY6L6fI4GtQRAskFAKDN+9AxPEVZ5ISr5t1BfansHO05pQCfX/dV E75sD2WYu52tksHGFVxPzgE= =Zv0N -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 18:30:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from wren.cs.unc.edu (wren.cs.unc.edu [152.2.128.86]) by hub.freebsd.org (Postfix) with ESMTP id D13C537B409 for ; Fri, 28 Sep 2001 18:30:36 -0700 (PDT) Received: from le-cs.cs.unc.edu (IDENT:le@le-cs.cs.unc.edu [152.2.131.150]) by wren.cs.unc.edu (8.9.3/8.9.3) with ESMTP id VAA17551 for ; Fri, 28 Sep 2001 21:30:33 -0400 (EDT) Date: Fri, 28 Sep 2001 21:30:33 -0400 (EDT) From: Nguyen-Tuong Long Le To: Subject: FD_SETSIZE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am wondering what is the side effects of increasing FD_SETSIZE beyond 1024? Our group have a propiertary web server software that handles a large number of sockets. While increasing the kern.maxfiles and kern.maxfilesperproc gives our web server more connections, select() seems to fail if the descriptor is beyond 1024. Can I just increase FD_SETSIZE and recompile the kernel? I saw some magic numbers in kern/sys_generic.c and am not sure whether there are some side effects. Thanks, Long P.S. Please kindly email me because I am not in the list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 19:34:53 2001 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 ESMTP id E583B37B407 for ; Fri, 28 Sep 2001 19:34:50 -0700 (PDT) Received: (qmail 86911 invoked by uid 1000); 29 Sep 2001 02:34:48 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Sep 2001 02:34:48 -0000 Date: Fri, 28 Sep 2001 21:34:48 -0500 (CDT) From: Mike Silbersack To: Alfred Perlstein Cc: "George V. Neville-Neil" , Subject: Re: Who are the core people on net? In-Reply-To: <20010928122433.G59854@elvis.mu.org> Message-ID: <20010928213333.T86905-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 28 Sep 2001, Alfred Perlstein wrote: > Sending it to -net would work, you might want to cc jlemon and > silby @freebsd, possibly me as well. > > -- > -Alfred Perlstein [alfred@freebsd.org] And jayanth, and jesper, and ruslan, and... Unless you've found some vulnerability which needs to be discussed quietly until it is fixed, it's probably best just to send mail to -net. 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 Sep 28 20:12:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from bushwire.net (f1.bushwire.net [64.81.73.11]) by hub.freebsd.org (Postfix) with SMTP id 2835E37B40B for ; Fri, 28 Sep 2001 20:12:11 -0700 (PDT) Received: (qmail 18096 invoked by uid 1001); 29 Sep 2001 03:12:09 -0000 Date: 29 Sep 2001 03:12:09 +0000 Message-ID: <20010929031209.18095.qmail@prefix.bushwire.net> From: "Mark" To: "Nguyen-Tuong Long Le" Cc: freebsd-net@freebsd.org Subject: Re: FD_SETSIZE References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from le@cs.unc.edu on Fri, Sep 28, 2001 at 09:30:33PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Sep 28, 2001 at 09:30:33PM -0400, Nguyen-Tuong Long Le allegedly wrote: > Hi, > > I am wondering what is the side effects of increasing FD_SETSIZE > beyond 1024? Our group have a propiertary web server software that > handles a large number of sockets. While increasing the kern.maxfiles > and kern.maxfilesperproc gives our web server more connections, > select() seems to fail if the descriptor is beyond 1024. > > Can I just increase FD_SETSIZE and recompile the kernel? I saw > some magic numbers in kern/sys_generic.c and am not sure whether > there are some side effects. I know this doesn't answer your question directly, but do you have to use select()? If not, you might want to consider poll() or better yet, kqueue(). Neither suffer from a predefined limit such as FD_SETSIZE and both should scale and perform as well as, or better than, select(). Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 20:30:17 2001 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 A7DB337B410 for ; Fri, 28 Sep 2001 20:26:12 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8T3NYN09661; Fri, 28 Sep 2001 22:23:34 -0500 (CDT) (envelope-from jlemon) Date: Fri, 28 Sep 2001 22:23:34 -0500 (CDT) From: Jonathan Lemon Message-Id: <200109290323.f8T3NYN09661@prism.flugsvamp.com> To: le@cs.unc.edu, net@freebsd.org Subject: Re: FD_SETSIZE X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article you write: >Hi, > >I am wondering what is the side effects of increasing FD_SETSIZE >beyond 1024? Our group have a propiertary web server software that >handles a large number of sockets. While increasing the kern.maxfiles >and kern.maxfilesperproc gives our web server more connections, >select() seems to fail if the descriptor is beyond 1024. > >Can I just increase FD_SETSIZE and recompile the kernel? I saw >some magic numbers in kern/sys_generic.c and am not sure whether >there are some side effects. No need to recompile the kernel. Add a #define FD_SETSIZE to your program, *before* , and recompile your application. And you probably really want to check out kqueue(2). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 21:25: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from ardbeg.meer.net (ardbeg.meer.net [209.157.152.23]) by hub.freebsd.org (Postfix) with ESMTP id 4F67A37B403 for ; Fri, 28 Sep 2001 21:25:07 -0700 (PDT) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by ardbeg.meer.net (8.11.3/8.11.3) with ESMTP id f8T4P7j74553 for ; Fri, 28 Sep 2001 21:25:07 -0700 (PDT) Received: from neville-neil.com (pm3b-87.mv.meer.net [209.157.137.87]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id VAA2685096 for ; Fri, 28 Sep 2001 21:24:45 -0700 (PDT) Message-Id: <200109290424.VAA2685096@meer.meer.net> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-net@freebsd.org Subject: Questions... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Sep 2001 21:25:02 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org OK, several people said I should just send this to -net so here you are. I have a few questions about the direction and code base for the FreeBSD TCP/IP stack. 1) Is there a published list of "TODOs" that y'all are working on to add/modify the system? 2) How different is -CURRENT from -STABLE? 3) Will the code be multi-threaded for SMP? 4) Will y'all continue to periodically integrate the Kame code as you v6 solution? 5) Will the v6 code by multi-threaded? Well, that's a start. Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 22:25: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 5F34437B405 for ; Fri, 28 Sep 2001 22:25:01 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 1BC1481D0B; Sat, 29 Sep 2001 00:24:56 -0500 (CDT) Date: Sat, 29 Sep 2001 00:24:56 -0500 From: Alfred Perlstein To: "George V. Neville-Neil" Cc: freebsd-net@freebsd.org Subject: Re: Questions... Message-ID: <20010929002456.M59854@elvis.mu.org> References: <200109290424.VAA2685096@meer.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109290424.VAA2685096@meer.meer.net>; from gnn@neville-neil.com on Fri, Sep 28, 2001 at 09:25:02PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * George V. Neville-Neil [010928 23:25] wrote: > OK, several people said I should just send this to -net so here you are. > > I have a few questions about the direction and code base for the FreeBSD > TCP/IP stack. > > 1) Is there a published list of "TODOs" that y'all are working on to > add/modify the system? Not that I know of. > 2) How different is -CURRENT from -STABLE? This can be answered by reading archives of the mailing lists and newflashes. The most signifigant changes that I can think of are: SMP primatives KSE FFS Snapshots Cardbus > 3) Will the code be multi-threaded for SMP? Hopefully. > 4) Will y'all continue to periodically integrate the Kame code as you v6 > solution? I can't say yes or no, but it looks like this is the pattern we are following, in fact it seems like it's actuallty the KAME guys doing a lot of work to integrate into _us_. > 5) Will the v6 code by multi-threaded? Hopefully, there's nothing inherently bad with it that will make it too difficult. > Well, that's a start. Why the sudden interest? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 28 23:35:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.nsu.ru (b.ns.ssc.nsu.ru [193.124.215.221]) by hub.freebsd.org (Postfix) with ESMTP id 4FA3837B403 for ; Fri, 28 Sep 2001 23:35:11 -0700 (PDT) Received: from iclub.nsu.ru ([193.124.222.66] ident=root) by mail.nsu.ru with esmtp (Exim 3.20 #1) id 15nDi7-0005A4-00; Sat, 29 Sep 2001 13:34:51 +0700 Received: (from fjoe@localhost) by iclub.nsu.ru (8.11.4/8.11.4) id f8T6YoQ44069; Sat, 29 Sep 2001 13:34:50 +0700 (NSS) (envelope-from fjoe) Date: Sat, 29 Sep 2001 13:34:49 +0700 From: Max Khon To: Nguyen-Tuong Long Le Cc: freebsd-net@FreeBSD.ORG Subject: Re: FD_SETSIZE Message-ID: <20010929133448.A43884@iclub.nsu.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from le@cs.unc.edu on Fri, Sep 28, 2001 at 09:30:33PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi, there! On Fri, Sep 28, 2001 at 09:30:33PM -0400, Nguyen-Tuong Long Le wrote: > I am wondering what is the side effects of increasing FD_SETSIZE > beyond 1024? Our group have a propiertary web server software that > handles a large number of sockets. While increasing the kern.maxfiles > and kern.maxfilesperproc gives our web server more connections, > select() seems to fail if the descriptor is beyond 1024. > > Can I just increase FD_SETSIZE and recompile the kernel? I saw > some magic numbers in kern/sys_generic.c and am not sure whether > there are some side effects. you don't need to recompile kernel. just recompile your web server software with -DFD_SETSIZE=xxx /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 29 1:35:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 86C5037B408 for ; Sat, 29 Sep 2001 01:35:48 -0700 (PDT) Received: from localhost ([3ffe:501:100f:10c1:200:39ff:fe97:3f1e]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id RAA19566 for ; Sat, 29 Sep 2001 17:37:02 +0900 (JST) Date: Sat, 29 Sep 2001 17:35:35 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: freebsd-net@FreeBSD.ORG Subject: Re: Ipv6 In-Reply-To: References: <86zo7h2cz1.wl@keiichi01.osaka.iij.ad.jp> User-Agent: Wanderlust/2.6.0 (Twist And Shout-pre) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 44 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Fri, 28 Sep 2001 08:59:32 -0400, >>>>> "Alex Feldman" said: >> Currently the DNS system requires IPv4 transport. If you disable IPv4 >> completely, you cannot resolve any hostnames. In this case, you must >> set up DNS proxy (ex. totd) from IPv6 to IPv4. Is this your case, >> isn't it? A "DNS proxy" like totd is not related to the issue of DNS transport. Also, "the DNS system requires IPv4 transport" is not necessarily true. We should say that - If you rely on a DNS (cache) server that does not support IPv6 transport, you cannot resolve the IP(v6) address from a host name. In this case, you'll need to turn IPv4 on in your system, or to make the DNS server support IPv6 transport. - Even if there is no problem on name resolution, you cannot communicate with IPv4-only nodes. If you want to do this, you'll need some translation service from IPv6 to IPv4. Such translation service may comprise a "DNS proxy" and an actual translation box. Anyway, > Not, because I connected two machine back to back. > Btw, when I set ipv6_forwarding to 1, I was able to ping6. > But more interesting, when I next time boot this machine (ipv6_forwarding > set to 0 by default), I was still able to ping6. > So, what is happened? Just saying "(not) able to ping6" is not very informative. Be more specific, please. At least you should tell us - the OS name (probably FreeBSD) and its version of each node - (if the node is FreeBSD) the result of + ifconfig -a + netstat -rn + the exact output of the "ping6 execution" (do not describe the situation, just copy and paste the output) JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 29 1:44:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id EDA8337B408 for ; Sat, 29 Sep 2001 01:44:08 -0700 (PDT) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA74605; Sat, 29 Sep 2001 02:36:39 -0700 (PDT) Message-ID: <3BB588A8.C9ED7512@elischer.org> Date: Sat, 29 Sep 2001 01:39:04 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Nguyen-Tuong Long Le Cc: freebsd-net@freebsd.org Subject: Re: FD_SETSIZE References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Nguyen-Tuong Long Le wrote: > > Hi, > > I am wondering what is the side effects of increasing FD_SETSIZE > beyond 1024? Our group have a propiertary web server software that > handles a large number of sockets. While increasing the kern.maxfiles > and kern.maxfilesperproc gives our web server more connections, > select() seems to fail if the descriptor is beyond 1024. > > Can I just increase FD_SETSIZE and recompile the kernel? I saw > some magic numbers in kern/sys_generic.c and am not sure whether > there are some side effects. > > Thanks, > Long > > P.S. Please kindly email me because I am not in the list. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message it can be extended safely, but you'll get better performance if you write a version for FreeBSD to use kqueue instead.. -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 29 8: 5:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from ardbeg.meer.net (ardbeg.meer.net [209.157.152.23]) by hub.freebsd.org (Postfix) with ESMTP id B168337B405 for ; Sat, 29 Sep 2001 08:05:13 -0700 (PDT) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by ardbeg.meer.net (8.11.3/8.11.3) with ESMTP id f8TF5Cj99049; Sat, 29 Sep 2001 08:05:12 -0700 (PDT) Received: from neville-neil.com (pm3b-85.mv.meer.net [209.157.137.85]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id IAA2735004; Sat, 29 Sep 2001 08:04:34 -0700 (PDT) Message-Id: <200109291504.IAA2735004@meer.meer.net> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alfred Perlstein Cc: freebsd-net@freebsd.org Subject: Re: Questions... In-Reply-To: Message from Alfred Perlstein of "Sat, 29 Sep 2001 00:24:56 CDT." <20010929002456.M59854@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Sep 2001 08:04:53 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > The most signifigant changes that I can think of are: > SMP primatives > KSE > FFS Snapshots > Cardbus > Other than KSE (which I've only seen lately and so I don't know what it is) SMP should be the only thing that deeply affects the stack, at least to my currently limited knowledge. > Hopefully, there's nothing inherently bad with it that will make it > too difficult. Well, no more difficult than the current network stack. The number of global variables (at least when I was looking at the old 4.4 BSD Lite code) is not insignificant. Also, have y'all removed the spl() code locks (ala BSD/OS) yet? > Why the sudden interest? I'm working up a proposal for Addison/Wesley to rework/rewrite the Stevens books (Volume I and II) and of course for Volume II this stuff is all quite important since I intend to use the FreeBSD code base as the basis for it. I want to find out what the trajectory of the code is so I can decide which version to put in the book. I'm hoping that it will be 5.0 (or 5.something) so that by the time that code base is shipped (November 2002) the book won't be too far behind it. Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 29 13:30:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 8E8A937B405 for ; Sat, 29 Sep 2001 13:30:14 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 6F9CB81D0B; Sat, 29 Sep 2001 15:30:14 -0500 (CDT) Date: Sat, 29 Sep 2001 15:30:14 -0500 From: Alfred Perlstein To: "George V. Neville-Neil" Cc: freebsd-net@freebsd.org Subject: Re: Questions... Message-ID: <20010929153014.T59854@elvis.mu.org> References: <200109291504.IAA2735004@meer.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109291504.IAA2735004@meer.meer.net>; from gnn@neville-neil.com on Sat, Sep 29, 2001 at 08:04:53AM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * George V. Neville-Neil [010929 10:05] wrote: > > Hopefully, there's nothing inherently bad with it that will make it > > too difficult. > > Well, no more difficult than the current network stack. The number > of global variables (at least when I was looking at the old 4.4 BSD Lite > code) is not insignificant. Also, have y'all removed the spl() code > locks (ala BSD/OS) yet? The spls have no effect any longer, we're leaving them in however to mark places where protection is needed, when a subsystem becomes MP safe the spls are removed. As far as glabals there are actually very few there. > > Why the sudden interest? > > I'm working up a proposal for Addison/Wesley to rework/rewrite the > Stevens books (Volume I and II) and of course for Volume II this stuff > is all quite important since I intend to use the FreeBSD code base > as the basis for it. I want to find out what the trajectory of the code is > so I can decide which version to put in the book. I'm hoping that it > will be 5.0 (or 5.something) so that by the time that code base is shipped > (November 2002) the book won't be too far behind it. Interesting! I would target 5.0 as that's where a bunch of activity is going to be, I imagine a lot of changes may occur, but there's just about zero possibility of a rewrite, that would just be absurd. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 29 21: 3:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from ardbeg.meer.net (ardbeg.meer.net [209.157.152.23]) by hub.freebsd.org (Postfix) with ESMTP id 9DBEB37B403 for ; Sat, 29 Sep 2001 21:03:08 -0700 (PDT) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by ardbeg.meer.net (8.11.3/8.11.3) with ESMTP id f8U438j51977; Sat, 29 Sep 2001 21:03:08 -0700 (PDT) Received: from neville-neil.com (pm3b-80.mv.meer.net [209.157.137.80]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id VAA20726; Sat, 29 Sep 2001 21:02:39 -0700 (PDT) Message-Id: <200109300402.VAA20726@meer.meer.net> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alfred Perlstein Cc: freebsd-net@freebsd.org Subject: Re: Questions... In-Reply-To: Message from Alfred Perlstein of "Sat, 29 Sep 2001 15:30:14 CDT." <20010929153014.T59854@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Sep 2001 21:03:00 -0700 From: "George V. Neville-Neil" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > The spls have no effect any longer, we're leaving them in however > to mark places where protection is needed, when a subsystem becomes > MP safe the spls are removed. As far as glabals there are actually > very few there. OK, I'll start supping -CURRENT again. > Interesting! Or perhaps a fools errand :-) I've had a few friends try to warn me off of such a project. I guess we'll see. > I would target 5.0 as that's where a bunch of activity > is going to be, I imagine a lot of changes may occur, but there's > just about zero possibility of a rewrite, that would just be absurd. That was what I was figuring. I'll be keeping in touch. Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 29 23:40:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from wren.cs.unc.edu (wren.cs.unc.edu [152.2.128.86]) by hub.freebsd.org (Postfix) with ESMTP id AC23637B409 for ; Sat, 29 Sep 2001 23:40:17 -0700 (PDT) Received: from le-cs.cs.unc.edu (IDENT:le@le-cs.cs.unc.edu [152.2.131.150]) by wren.cs.unc.edu (8.9.3/8.9.3) with ESMTP id CAA09582 for ; Sun, 30 Sep 2001 02:40:14 -0400 (EDT) Date: Sun, 30 Sep 2001 02:40:13 -0400 (EDT) From: Nguyen-Tuong Long Le To: Subject: Re: FD_SETSIZE In-Reply-To: <200109290253.f8T2rrG19859@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, Thanks so much for your response and help! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message