From owner-freebsd-net Sun Oct 15 10:18:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id A596B37B670 for ; Sun, 15 Oct 2000 10:18:49 -0700 (PDT) Received: from localhost (c4@localhost) by worldclass.jolt.nu (8.9.3/8.9.3) with ESMTP id TAA32979; Sun, 15 Oct 2000 19:18:05 +0200 (CEST) (envelope-from c4@worldclass.jolt.nu) Date: Sun, 15 Oct 2000 19:18:04 +0200 (CEST) From: Tobias Fredriksson To: Bill Fumerola Cc: freebsd-net@freebsd.org Subject: Re: Limiting network usage on an user-basis? In-Reply-To: <20001014191144.I37870@jade.chc-chimes.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 14 Oct 2000, Bill Fumerola wrote: > On Sun, Oct 15, 2000 at 12:40:56AM +0200, Tobias Fredriksson wrote: > > Is there any way to use ipfw or other freebsd tools to shape so that an > > users processes cant exceed an specified total and is there any good > > documentation that you can point me to about this? > > man ipfw, particularly the parts about 'uid/gid' and dummynet. > > -- > Bill Fumerola - Network Architect, BOFH / Chimes, Inc. > billf@chimesnet.com / billf@FreeBSD.org I think you missunderstood me... I need to set an maximum not on kbit/mbit per second but rather an 500Meg / day limit and i cannot find anything like that in the ipfw documentation... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 15 10:27: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B0FBB37B503 for ; Sun, 15 Oct 2000 10:26:58 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9FHQlp03338; Sun, 15 Oct 2000 10:26:47 -0700 (PDT) Date: Sun, 15 Oct 2000 10:26:47 -0700 From: Alfred Perlstein To: Tobias Fredriksson Cc: Bill Fumerola , freebsd-net@FreeBSD.ORG Subject: Re: Limiting network usage on an user-basis? Message-ID: <20001015102647.G272@fw.wintelcom.net> References: <20001014191144.I37870@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from c4@worldclass.jolt.nu on Sun, Oct 15, 2000 at 07:18:04PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Tobias Fredriksson [001015 10:18] wrote: > > > On Sat, 14 Oct 2000, Bill Fumerola wrote: > > > On Sun, Oct 15, 2000 at 12:40:56AM +0200, Tobias Fredriksson wrote: > > > Is there any way to use ipfw or other freebsd tools to shape so that an > > > users processes cant exceed an specified total and is there any good > > > documentation that you can point me to about this? > > > > man ipfw, particularly the parts about 'uid/gid' and dummynet. > > > > -- > > Bill Fumerola - Network Architect, BOFH / Chimes, Inc. > > billf@chimesnet.com / billf@FreeBSD.org > > I think you missunderstood me... I need to set an maximum not on kbit/mbit > per second but rather an 500Meg / day limit and i cannot find anything > like that in the ipfw documentation... No, you didn't finish reading all the documentation... :) IPFW allows one to assign counters per-uid, by having a script poll the counters and check against your limits you can then perform triggers when someone exceeds thier daily quota. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 15 12:18:31 2000 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 88D9337B66F for ; Sun, 15 Oct 2000 12:18:27 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Oct 2000 20:18:25 +0100 (BST) To: freebsd-net@freebsd.org Subject: M_{LEADING,TRAILING}SPACE definitions. X-Request-Do: Date: Sun, 15 Oct 2000 20:18:24 +0100 From: David Malone Message-ID: <200010152018.aa65610@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm just looking at implimenting writeable external storage management for mbufs. Most parts of the kernel are quite conservative about writing to anything that isn't a plain mbuf, and this work should allow it more freedom. Important in this are the M_LEADINGSPACE and M_TRAILINGSPACE macros. #define M_LEADINGSPACE(m) \ ((m)->m_flags & M_EXT ? \ /* (m)->m_data - (m)->m_ext.ext_buf */ 0 : \ (m)->m_flags & M_PKTHDR ? (m)->m_data - (m)->m_pktdat : \ (m)->m_data - (m)->m_dat) #define M_TRAILINGSPACE(m) \ ((m)->m_flags & M_EXT ? (m)->m_ext.ext_buf + \ (m)->m_ext.ext_size - ((m)->m_data + (m)->m_len) : \ &(m)->m_dat[MLEN] - ((m)->m_data + (m)->m_len)) Note the difference - M_LEADINGSPACE always returns 0 for external storage - M_TRAILINGSPACE will always return the amount of space at the end of the buffer, even if it is unwritable. They have both been this way since version 1.1 of mbuf.h. Does anyone know why they are defined in this inconsistant way? I'd like to make them consistant and either have: 1) Both return 0 if the storage isn't writable. 2) Have both return the amount of space, but make the kernel check M_WRITABLE(m) before writing to it. M_LEADINGSPACE is only used about 16 times in the kernel and it's users tend to assume that the space in question will be writable. M_TRAILINGSPACE is used about 60 times, most consumers seem to ensure the writeability themselves. This suggests I should go for option 2 and then check the places where M_LEADINGSPACE is called. I could have an option (3) where the M_LEADINGSPACE behaves in a different way to M_TRAILINGSPACE, and have the former check M_WRITEABLE before returning. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 15 13:19:31 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 5709D37B66F for ; Sun, 15 Oct 2000 13:19:29 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9FKJPD07531; Sun, 15 Oct 2000 13:19:25 -0700 (PDT) Date: Sun, 15 Oct 2000 13:19:25 -0700 From: Alfred Perlstein To: David Malone Cc: freebsd-net@FreeBSD.ORG Subject: Re: M_{LEADING,TRAILING}SPACE definitions. Message-ID: <20001015131925.I272@fw.wintelcom.net> References: <200010152018.aa65610@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010152018.aa65610@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Sun, Oct 15, 2000 at 08:18:24PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * David Malone [001015 12:18] wrote: > I'm just looking at implimenting writeable external storage management > for mbufs. Most parts of the kernel are quite conservative about > writing to anything that isn't a plain mbuf, and this work should > allow it more freedom. [snip] > 1) Both return 0 if the storage isn't writable. > 2) Have both return the amount of space, but make the kernel check > M_WRITABLE(m) before writing to it. > > M_LEADINGSPACE is only used about 16 times in the kernel and it's > users tend to assume that the space in question will be writable. > M_TRAILINGSPACE is used about 60 times, most consumers seem to > ensure the writeability themselves. This suggests I should go for > option 2 and then check the places where M_LEADINGSPACE is called. How about M_TRAILINGSPACE_WRITABLE/M_LEADINGSPACE_WRITABLE? This is self documenting and would probably prevent such errors in the future. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Oct 15 14:31:19 2000 Delivered-To: freebsd-net@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 3B57737B66E for ; Sun, 15 Oct 2000 14:31:12 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G2H0059NQEGGU@field.videotron.net> for freebsd-net@FreeBSD.ORG; Sun, 15 Oct 2000 17:30:16 -0400 (EDT) Date: Sun, 15 Oct 2000 17:34:25 -0400 (EDT) From: Bosko Milekic Subject: Re: M_{LEADING,TRAILING}SPACE definitions. In-reply-to: <200010152018.aa65610@salmon.maths.tcd.ie> X-Sender: bmilekic@jehovah.technokratis.com To: David Malone Cc: freebsd-net@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 15 Oct 2000, David Malone wrote: [...] > 1) Both return 0 if the storage isn't writable. > 2) Have both return the amount of space, but make the kernel check > M_WRITABLE(m) before writing to it. (2) is better, in my opinion. The arguments are: (i) I'd like to be able to get LEADINGSPACE and TRAILINGSPACE for non-writable buffers as well. (ii) If the kernel is calling M_LEADINGSPACE() and/or M_TRAILINGSPACE() on non-writable buffers, then in the general case, the portion doing this calling is flawed and should be repaired itself. > M_LEADINGSPACE is only used about 16 times in the kernel and it's > users tend to assume that the space in question will be writable. > M_TRAILINGSPACE is used about 60 times, most consumers seem to > ensure the writeability themselves. This suggests I should go for > option 2 and then check the places where M_LEADINGSPACE is called. Yes, that's argument (iii). :-) > I could have an option (3) where the M_LEADINGSPACE behaves in a > different way to M_TRAILINGSPACE, and have the former check > M_WRITEABLE before returning. That would be maintaining the present inconsistency... so I personally wouldn't go for that. Also, despite Alfred's suggestion, I wouldn't bloat mbuf.h with two more macros which would essentially be unused. The idea is that when you're calling the two macros, you should already know whether the mbuf is 'writable' or not, and if you're doing it, you're doing it because you know it's correct, not because you hope that it is. > David. Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 12:19: 1 2000 Delivered-To: freebsd-net@freebsd.org Received: from hub.org (hub.org [216.126.84.1]) by hub.freebsd.org (Postfix) with ESMTP id 53C8737B66E; Mon, 16 Oct 2000 12:18:57 -0700 (PDT) Received: from localhost (scrappy@localhost) by hub.org (8.10.1/8.11.0) with ESMTP id e9GJIuT70779; Mon, 16 Oct 2000 15:18:56 -0400 (EDT) (envelope-from scrappy@hub.org) Date: Mon, 16 Oct 2000 15:18:56 -0400 (EDT) From: "Marc G. Fournier" To: freebsd-net@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Intel(R) PRO/XX Adapters ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Morning all ... Just picked up a Netfinity 7100 to act as a proxy server, running FreeBSD 4.x, and hit a rut in the road I wasn't expecting ... my Intel EtherExpress card isn't supported by the hardware itself :( I have a choice of 4 cards that I can run, and am curious as to whether any of them will be supported, and if anyone has any caveats about any, before I order them ... PILA8470 - Intel(R) PRO/100+ Server Adapter PILA8472 - Intel(R) PRO/100+ Dual Port Server Adapter PWLA8490 - Intel(R) PRO/1000 Gigabit Server Adapter PILA8480 - Intel(R) PRO/100 Intelligent Server Adapter thanks ... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 12:40: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 833A737B502; Mon, 16 Oct 2000 12:40:01 -0700 (PDT) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 13lG75-00009u-00; Mon, 16 Oct 2000 12:39:59 -0700 Date: Mon, 16 Oct 2000 12:39:56 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Marc G. Fournier" Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Intel(R) PRO/XX Adapters ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 16 Oct 2000, Marc G. Fournier wrote: > Morning all ... > > Just picked up a Netfinity 7100 to act as a proxy server, running > FreeBSD 4.x, and hit a rut in the road I wasn't expecting ... my Intel > EtherExpress card isn't supported by the hardware itself :( > > I have a choice of 4 cards that I can run, and am curious as to > whether any of them will be supported, and if anyone has any caveats about > any, before I order them ... > > PILA8470 - Intel(R) PRO/100+ Server Adapter > PILA8472 - Intel(R) PRO/100+ Dual Port Server Adapter > PWLA8490 - Intel(R) PRO/1000 Gigabit Server Adapter > PILA8480 - Intel(R) PRO/100 Intelligent Server Adapter I believe that all but the Intelligent Server Adapter are supported. The PRO/100+ is specifically mentioned on the fxp manpage (what? you didn't check the manpage before posting?). The gigabit server adapter is apparently supported by the wx driver. > thanks ... > > Marc G. Fournier scrappy@hub.org > Systems Administrator @ hub.org > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 13:19:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 5C26E37B670; Mon, 16 Oct 2000 13:19:18 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA17879; Mon, 16 Oct 2000 13:19:32 -0700 (PDT) Message-Id: <200010162019.NAA17879@implode.root.com> To: "Marc G. Fournier" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Intel(R) PRO/XX Adapters ... In-reply-to: Your message of "Mon, 16 Oct 2000 15:18:56 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Oct 2000 13:19:31 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Morning all ... > > Just picked up a Netfinity 7100 to act as a proxy server, running >FreeBSD 4.x, and hit a rut in the road I wasn't expecting ... my Intel >EtherExpress card isn't supported by the hardware itself :( > > I have a choice of 4 cards that I can run, and am curious as to >whether any of them will be supported, and if anyone has any caveats about >any, before I order them ... > >PILA8470 - Intel(R) PRO/100+ Server Adapter >PILA8472 - Intel(R) PRO/100+ Dual Port Server Adapter >PWLA8490 - Intel(R) PRO/1000 Gigabit Server Adapter >PILA8480 - Intel(R) PRO/100 Intelligent Server Adapter Actually, all of the above should work - are you saying that you've tried and they don't work? The Pro/1000 should work with the wx driver and the others should work with the fxp driver. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 15:39:55 2000 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id 51DD637B66C; Mon, 16 Oct 2000 15:39:51 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id e9GMcIB47102; Mon, 16 Oct 2000 19:38:18 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 16 Oct 2000 19:38:18 -0300 (ADT) From: The Hermit Hacker To: Tom Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Intel(R) PRO/XX Adapters ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 16 Oct 2000, Tom wrote: > On Mon, 16 Oct 2000, Marc G. Fournier wrote: > > > Morning all ... > > > > Just picked up a Netfinity 7100 to act as a proxy server, running > > FreeBSD 4.x, and hit a rut in the road I wasn't expecting ... my Intel > > EtherExpress card isn't supported by the hardware itself :( > > > > I have a choice of 4 cards that I can run, and am curious as to > > whether any of them will be supported, and if anyone has any caveats about > > any, before I order them ... > > > > PILA8470 - Intel(R) PRO/100+ Server Adapter > > PILA8472 - Intel(R) PRO/100+ Dual Port Server Adapter > > PWLA8490 - Intel(R) PRO/1000 Gigabit Server Adapter > > PILA8480 - Intel(R) PRO/100 Intelligent Server Adapter > > I believe that all but the Intelligent Server Adapter are supported. > > The PRO/100+ is specifically mentioned on the fxp manpage (what? you > didn't check the manpage before posting?). The gigabit server adapter is > apparently supported by the wx driver. damn, i knew there was somewhere else other then LINT I should have looked ;( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 16:11:37 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9F8EE37B66E; Mon, 16 Oct 2000 16:11:34 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9GNBX625042; Mon, 16 Oct 2000 16:11:33 -0700 (PDT) Date: Mon, 16 Oct 2000 16:11:33 -0700 From: Alfred Perlstein To: bmilekic@freebsd.org Cc: net@freebsd.org Subject: how to detect recent mbuf changes Message-ID: <20001016161133.V272@fw.wintelcom.net> 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 X-Loop: FreeBSD.org Have we bumbed FreeBSD version or do we have some other way to detect the recent change in the way mbuf clusters are counted? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 17:53:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 2363D37B66D; Mon, 16 Oct 2000 17:53:33 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id RAA09825; Mon, 16 Oct 2000 17:53:52 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp05.primenet.com, id smtpdAAA03aigt; Mon Oct 16 17:53:41 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA04059; Mon, 16 Oct 2000 17:53:16 -0700 (MST) From: Terry Lambert Message-Id: <200010170053.RAA04059@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: gcorcoran@lucent.com (Gary T. Corcoran) Date: Tue, 17 Oct 2000 00:53:15 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <39E7AB10.EADBB53B@lucent.com> from "Gary T. Corcoran" at Oct 13, 2000 08:38:40 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Back in July I was asking about the capability to set parameters (variables) > when loading my DSL driver module. There was a small flurry of activity > about some initial ideas on how to do it, but I never heard any more about > it. Did you (Mike, Warner, or anybody) have time to work on it? Did this > capability get put into release 4.1, by any chance? :) A common trick "in the old days" was to load a parameter module that the driver module depended up, and give it a hook that it could call to get data from the parameter module, by reference to a statis structure. You would send the data down to the parameter module before you load the driver module; thus: 1) Load paramter module 2) Open parameter module psuedo device 3) Ioctl parameters up/down via the pseudo device 4) Load the deriver module 5) Driver module attach routine call parameter_fetch() routine out of parameter module 6) Parameter module returns static parameter structure, by reference 7) Driver dereferences parameters out of static struct 8) Driver completes attach Really, it seems to me that if this driver looks like an ethernet interface, you should be able to set the parameters after the atttach, before bringing the interface up. Alternately, if the problem is lack of reference counting on FreeBSD's part, and you therefore can't do the job on the open, since you can't track closes aws they happen, only the last clse, there are a couple of approaches: A) Have one driver, but two devices; one for control, and one for data B) Have only one device, but inactivate it until a special ioctl() starting it up is issued; thus: 1) Open 2) Set parameters 3) ioctl(fd,LUCENT_START,...) 4) ... 5) ioctl(fd,LUCENT_STOP,...) 6) Set new parameters 7) ioctl(fd,LUCENT_START,...) 8) ... One of these aprroaches should be able to work for you; the parameter driver approach with a pseudo device will definitely work, but is much less elegant (parameters on an attach probably mean that you are doing something in an attach that really belongs elsewhere). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 18: 4:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9480837B66E; Mon, 16 Oct 2000 18:04:12 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9H149T28639; Mon, 16 Oct 2000 18:04:09 -0700 (PDT) Date: Mon, 16 Oct 2000 18:04:09 -0700 From: Alfred Perlstein To: Terry Lambert Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) Message-ID: <20001016180409.C272@fw.wintelcom.net> References: <39E7AB10.EADBB53B@lucent.com> <200010170053.RAA04059@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010170053.RAA04059@usr05.primenet.com>; from tlambert@primenet.com on Tue, Oct 17, 2000 at 12:53:15AM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Terry Lambert [001016 17:55] wrote: > > Alternately, if the problem is lack of reference counting on > FreeBSD's part, and you therefore can't do the job on the > open, since you can't track closes aws they happen, only the > last clse, there are a couple of approaches: FreeBSD has had that capability for over a year now. /* * Flags for d_flags. */ #define D_MEMDISK 0x10000 /* memory type disk */ #define D_NAGGED 0x20000 /* nagged about missing make_dev() */ #define D_CANFREE 0x40000 /* can free blocks */ #define D_TRACKCLOSE 0x80000 /* track all closes */ (from sys/conf.h) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 18:14:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by hub.freebsd.org (Postfix) with ESMTP id 6C61D37B679; Mon, 16 Oct 2000 18:14:14 -0700 (PDT) Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id VAA19871; Mon, 16 Oct 2000 21:14:14 -0400 (EDT) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id VAA19859; Mon, 16 Oct 2000 21:14:13 -0400 (EDT) Received: from lucent.com (positron.micro.lucent.com [192.19.56.129]) by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id VAA22823; Mon, 16 Oct 2000 21:14:12 -0400 (EDT) Message-ID: <39EBA79C.26BFFE3@lucent.com> Date: Mon, 16 Oct 2000 21:13:00 -0400 From: "Gary T. Corcoran" Organization: Lucent Microelectronics - Client Access Broadband Systems X-Mailer: Mozilla 4.73 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) References: <200010170053.RAA04059@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry, First, thanks for the reply. > > Back in July I was asking about the capability to set parameters (variables) > > when loading my DSL driver module. There was a small flurry of activity > > about some initial ideas on how to do it, but I never heard any more about > > it. Did you (Mike, Warner, or anybody) have time to work on it? Did this > > capability get put into release 4.1, by any chance? :) > > A common trick "in the old days" was to load a parameter module > that the driver module depended up, and give it a hook that it > could call to get data from the parameter module, by reference > to a statis structure. Hmmm... Quite a hack :), but yes it should work. If all else fails, I guess I could do this... > Really, it seems to me that if this driver looks like an > ethernet interface, you should be able to set the parameters > after the atttach, before bringing the interface up. ... > One of these aprroaches should be able to work for you; the parameter > driver approach with a pseudo device will definitely work, but is > much less elegant (parameters on an attach probably mean that you > are doing something in an attach that really belongs elsewhere). One of the problems with supporting DSL is that there are many "flavors" of protocol that different equipment providers use. But there are two main divisions, which unfortunately make for a Jekyl-and-Hyde personality. The DSL card must either appear as a LAN device (ethernet interface) or a WAN device (sync PPP device). Thus, at the moment of attach(), I need to know whether to do an ether_ifattach() or an sppp_attach(). That's the main reason I need module parameters. The other reason I _want_ module parameters is that Linux provides them, so the Linux flavor of my driver uses them, and it's easier to keep the drivers in sync with changes if they are written in a similar manner (since only the Linux driver is "officially" supported)... Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 18:19:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id DC84237B479; Mon, 16 Oct 2000 18:19:37 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id SAA04562; Mon, 16 Oct 2000 18:16:16 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpdAAAXTaaRi; Mon Oct 16 18:16:01 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA05533; Mon, 16 Oct 2000 18:19:16 -0700 (MST) From: Terry Lambert Message-Id: <200010170119.SAA05533@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 17 Oct 2000 01:19:16 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <20001016180409.C272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 16, 2000 06:04:09 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Alternately, if the problem is lack of reference counting on > > FreeBSD's part, and you therefore can't do the job on the > > open, since you can't track closes aws they happen, only the > > last clse, there are a couple of approaches: > > FreeBSD has had that capability for over a year now. > > /* > * Flags for d_flags. > */ > #define D_TRACKCLOSE 0x80000 /* track all closes */ Under what circumstances is it permissable to _not_ set this bit? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 18:38:58 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3B17437B4B1; Mon, 16 Oct 2000 18:38:53 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9H1ckd29873; Mon, 16 Oct 2000 18:38:46 -0700 (PDT) Date: Mon, 16 Oct 2000 18:38:46 -0700 From: Alfred Perlstein To: Terry Lambert Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) Message-ID: <20001016183846.G272@fw.wintelcom.net> References: <20001016180409.C272@fw.wintelcom.net> <200010170119.SAA05533@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010170119.SAA05533@usr05.primenet.com>; from tlambert@primenet.com on Tue, Oct 17, 2000 at 01:19:16AM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Terry Lambert [001016 18:19] wrote: > > > Alternately, if the problem is lack of reference counting on > > > FreeBSD's part, and you therefore can't do the job on the > > > open, since you can't track closes aws they happen, only the > > > last clse, there are a couple of approaches: > > > > FreeBSD has had that capability for over a year now. > > > > /* > > * Flags for d_flags. > > */ > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > Under what circumstances is it permissable to _not_ set this bit? When you want the old behavior. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 18:57:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 51CEE37B4CF; Mon, 16 Oct 2000 18:57:44 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id SAA00281; Mon, 16 Oct 2000 18:54:45 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAANHa4va; Mon Oct 16 18:54:34 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA06764; Mon, 16 Oct 2000 18:57:25 -0700 (MST) From: Terry Lambert Message-Id: <200010170157.SAA06764@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 17 Oct 2000 01:57:25 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <20001016183846.G272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 16, 2000 06:38:46 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Alternately, if the problem is lack of reference counting on > > > > FreeBSD's part, and you therefore can't do the job on the > > > > open, since you can't track closes aws they happen, only the > > > > last clse, there are a couple of approaches: > > > > > > FreeBSD has had that capability for over a year now. > > > > > > /* > > > * Flags for d_flags. > > > */ > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > Under what circumstances is it permissable to _not_ set this bit? > > When you want the old behavior. Under what circumstances is it permissable to want the old behaviour? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 19:41:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 05A4237B4D7; Mon, 16 Oct 2000 19:41:50 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9H2fmt02044; Mon, 16 Oct 2000 19:41:48 -0700 (PDT) Date: Mon, 16 Oct 2000 19:41:48 -0700 From: Alfred Perlstein To: Terry Lambert Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) Message-ID: <20001016194147.I272@fw.wintelcom.net> References: <20001016183846.G272@fw.wintelcom.net> <200010170157.SAA06764@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010170157.SAA06764@usr05.primenet.com>; from tlambert@primenet.com on Tue, Oct 17, 2000 at 01:57:25AM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Terry Lambert [001016 18:57] wrote: > > > > > Alternately, if the problem is lack of reference counting on > > > > > FreeBSD's part, and you therefore can't do the job on the > > > > > open, since you can't track closes aws they happen, only the > > > > > last clse, there are a couple of approaches: > > > > > > > > FreeBSD has had that capability for over a year now. > > > > > > > > /* > > > > * Flags for d_flags. > > > > */ > > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > > > Under what circumstances is it permissable to _not_ set this bit? > > > > When you want the old behavior. > > Under what circumstances is it permissable to want the old behaviour? Jeez Terry, I don't know, it's how it used to be so I assume it's for compatibility or for drivers that simply don't care. Am I missing something here? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 21:28:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 7B2A537B4D7; Mon, 16 Oct 2000 21:28:48 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id VAA19886; Mon, 16 Oct 2000 21:29:10 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAA1KaWYM; Mon Oct 16 21:29:07 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id VAA06237; Mon, 16 Oct 2000 21:28:41 -0700 (MST) From: Terry Lambert Message-Id: <200010170428.VAA06237@usr01.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 17 Oct 2000 04:28:41 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <20001016194147.I272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 16, 2000 07:41:48 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > Under what circumstances is it permissable to _not_ set this bit? > > > When you want the old behavior. > > Under what circumstances is it permissable to want the old behaviour? > > Jeez Terry, I don't know, it's how it used to be so I assume it's for > compatibility or for drivers that simply don't care. Am I missing > something here? I guess I'm asking "What moron would want to intentionally disable system resource tracking?". It's OK for the driver to not care, I guess, if it doesn't want to allow you to unload it, and other evil things. I can maybe buy the legacy argument, but, frankly, and I said this when Poul and David first asked that the capability to track closes first went in, unless everyone plays by the same rules, no one benefits. I guess it'd be nice if it weren't possible to have new drivers not support device close tracking, even if they did nothing about it, other than disallowing unloads when the open count was positive. In the specific context of this thread, if there was a control daemon, then the first open could always be the control daemon, and "attach" parameters could be passed by doing an open, noting it was the first open, and delaying the attach until the open count went from 1->2. For symmetry, this means that if I want to change the parameters after a reconfiguration, I need to know when the open count has gone from 2->1 (leaving only the control daemon). In order to differentiate the control daemon failing, from a normal non-control close, I would need to track and maintain a list of who the opener is, and remove from that list on close. As a general approach, this removes the need for a seperate control and usage device distinction, for those devices which have it now. It also means that I can distinguish a control open from another open, and that I can wedge an open in through an ioctl() to let me do things like have opens onto the ISO9660 and DVDROM views onto a DVD, without having to have seperate character and block devices, so tat, given a legal codec, I can play DVDs on FreeBSD, just like you can on MacOS X (which uses the caharcter device for one type of access, and the block device for the other: efectively another control device hack). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Oct 16 21:58:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6098737B4C5; Mon, 16 Oct 2000 21:58:07 -0700 (PDT) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA09570; Tue, 17 Oct 2000 14:27:56 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010170428.VAA06237@usr01.primenet.com> Date: Tue, 17 Oct 2000 14:27:56 +0930 (CST) From: "Daniel O'Connor" To: Terry Lambert Subject: Re: Module parameters? (WildWire DSL card driver) Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, (Gary T. Corcoran) , (Alfred Perlstein) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Oct-00 Terry Lambert wrote: > I guess I'm asking "What moron would want to intentionally disable > system resource tracking?". > > It's OK for the driver to not care, I guess, if it doesn't want to > allow you to unload it, and other evil things. > > > I can maybe buy the legacy argument, but, frankly, and I said > this when Poul and David first asked that the capability to > track closes first went in, unless everyone plays by the same > rules, no one benefits. If you don't need 'per-open' instance data then getting notified of the final close would be sufficient. Also, if you only allow one open you don't need to track each close. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 0: 0:46 2000 Delivered-To: freebsd-net@freebsd.org Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26]) by hub.freebsd.org (Postfix) with ESMTP id 413E337B657 for ; Tue, 17 Oct 2000 00:00:33 -0700 (PDT) Received: from esebh11nok.ntc.nokia.com (esebh11nok.ntc.nokia.com [131.228.10.108]) by mgw-x3.nokia.com (8.10.2/8.10.2/Nokia) with ESMTP id e9H6xSB17621; Tue, 17 Oct 2000 09:59:28 +0300 (EET DST) Received: from samail01.nmp.nokia.com ([131.228.240.6]) by esebh11nok.ntc.nokia.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.78) id 47WARQ6R; Tue, 17 Oct 2000 09:59:23 +0300 Received: from tolnx04.europe.nokia.com (root@tolnx04.europe.nokia.com [172.24.106.61]) by samail01.nmp.nokia.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id KAA09824; Tue, 17 Oct 2000 10:19:26 +0200 (EET) Received: (from jepeters@localhost) by tolnx04.europe.nokia.com (8.11.0/8.11.0) id e9H6wwd10940; Tue, 17 Oct 2000 15:58:58 +0900 X-Authentication-Warning: tolnx04.europe.nokia.com: jepeters set sender to jens-ulrik.petersen@nokia.com using -f To: freebsd-net@FreeBSD.ORG Cc: users@ipv6.org Subject: dns lookup with IPv6 transport? From: Jens-Ulrik Petersen Date: 17 Oct 2000 15:58:57 +0900 In-Reply-To: David Greenman's message of "Mon, 16 Oct 2000 13:19:31 -0700" Message-ID: Lines: 11 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have just connected a small network to the 6bone. However currently we have a pure ipv6 connection (ie no ipv4 address allocation!). We want to do dnslookup using IPv6 transport from a FreeBSD-4.1R box. Simple configuration suggests dnslookup over IPv6 is not supported. Is it possible to configuration the kernel/libc/system to allow dnslookups over IPv6? Or does it require using bind? (If bind is required, is it bind-9?) Thanks, Jens To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 0:12:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from netplex.com.au (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id CF4AE37B4D7; Tue, 17 Oct 2000 00:12:08 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e9H7C3G58805; Tue, 17 Oct 2000 00:12:04 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010170712.e9H7C3G58805@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Terry Lambert Cc: bright@wintelcom.net (Alfred Perlstein), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) In-Reply-To: <200010170428.VAA06237@usr01.primenet.com> Date: Tue, 17 Oct 2000 00:12:03 -0700 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry Lambert wrote: > > > > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > > Under what circumstances is it permissable to _not_ set this bit? > > > > When you want the old behavior. > > > Under what circumstances is it permissable to want the old behaviour? > > > > Jeez Terry, I don't know, it's how it used to be so I assume it's for > > compatibility or for drivers that simply don't care. Am I missing > > something here? > > I guess I'm asking "What moron would want to intentionally disable > system resource tracking?". Who said anything about disabling system resource tracking? "track all closes" means to call the devsw d_close function for *each* close, not just for the "last close" as 99% of our drivers expect... If we suddenly caused d_close() to be called on every close() syscall, then existing drivers break because they are used to freeing everything and cleaning up when the close function is called. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 2:24: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (Postfix) with ESMTP id 6BDFD37B4E5 for ; Tue, 17 Oct 2000 02:24:06 -0700 (PDT) Received: from zed.isi.edu (root@zed.isi.edu [128.9.160.57]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id CAA16508; Tue, 17 Oct 2000 02:24:04 -0700 (PDT) From: Bill Manning Received: (from bmanning@localhost) by zed.isi.edu (8.9.3/8.8.6) id CAA03673; Tue, 17 Oct 2000 02:24:04 -0700 Message-Id: <200010170924.CAA03673@zed.isi.edu> Subject: Re: dns lookup with IPv6 transport? To: jens-ulrik.petersen@nokia.com (Jens-Ulrik Petersen) Date: Tue, 17 Oct 2000 02:24:04 -0700 (PDT) Cc: freebsd-net@FreeBSD.ORG, users@ipv6.org In-Reply-To: from "Jens-Ulrik Petersen" at Oct 17, 2000 03:58:57 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org % % We have just connected a small network to the 6bone. However % currently we have a pure ipv6 connection (ie no ipv4 address % allocation!). % % We want to do dnslookup using IPv6 transport from a FreeBSD-4.1R box. % Simple configuration suggests dnslookup over IPv6 is not supported. % Is it possible to configuration the kernel/libc/system to allow % dnslookups over IPv6? Or does it require using bind? (If bind is % required, is it bind-9?) % % Thanks, Jens % Bindv9 is prefered. There is some limited support with bindv8 but it requires significant patching w/ KAME code. -- --bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 4:43:18 2000 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 36D0D37B4D7 for ; Tue, 17 Oct 2000 04:43:15 -0700 (PDT) Received: from localhost ([3ffe:501:100f:13ff::e]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id UAA20708; Tue, 17 Oct 2000 20:27:43 +0900 (JST) Date: Tue, 17 Oct 2000 20:14:48 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Jens-Ulrik Petersen Cc: freebsd-net@FreeBSD.ORG, users@ipv6.org Subject: Re: dns lookup with IPv6 transport? In-Reply-To: In your message of "17 Oct 2000 15:58:57 +0900" References: User-Agent: Wanderlust/2.3.0 (Roam) Emacs/20.7 Mule/4.0 (HANANOEN) 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: 24 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On 17 Oct 2000 15:58:57 +0900, >>>>> Jens-Ulrik Petersen said: > We have just connected a small network to the 6bone. However > currently we have a pure ipv6 connection (ie no ipv4 address > allocation!). > We want to do dnslookup using IPv6 transport from a FreeBSD-4.1R box. > Simple configuration suggests dnslookup over IPv6 is not supported. > Is it possible to configuration the kernel/libc/system to allow > dnslookups over IPv6? Or does it require using bind? (If bind is > required, is it bind-9?) If I remember correctly, FreeBSD 4.1 supports IPv6 of DNS transport. I don't know much about FreeBSD configuration , but how about trying to add the following in your /etc/resolv.conf? nameserver xxxx:yyyy:zzzz:... where xxxx:... is the IPv6 address of your DNS server. 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 Tue Oct 17 5: 5:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id BB69437B4E5 for ; Tue, 17 Oct 2000 05:05:18 -0700 (PDT) Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se [153.88.251.32]) by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id e9HC5HZ21843 for ; Tue, 17 Oct 2000 14:05:17 +0200 (MEST) Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Tue Oct 17 14:05:16 2000 +0200 Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58) id <4Y419CPR>; Tue, 17 Oct 2000 14:03:47 +0200 Message-ID: From: "Wei Zhao (ERA)" To: "'freebsdnet'" Subject: ipv6cp implementation.. Date: Tue, 17 Oct 2000 13:59:04 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am wondering if anyone has any experience implementing ipv6cp for PPP protocol, or anyone knows if there exists any implementation. Thanks Wei Zhao Ericsson Radio Systems AB Tel: +46 8 508 78097 Mobile: +46 73 0387516 Fax:+46 8 50878090 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 5:16:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from jinn.laser.ru (mx.mtu.gpi.ru [212.30.167.230]) by hub.freebsd.org (Postfix) with ESMTP id D249B37B4E5 for ; Tue, 17 Oct 2000 05:16:01 -0700 (PDT) Received: from w9g8j7 (63.6.87.194.dynamic.dol.ru [194.87.6.63]) by jinn.laser.ru (8.8.8/8.8.8) with SMTP id QAA08156 for ; Tue, 17 Oct 2000 16:15:33 +0400 (MSD) (envelope-from kuzmin@laser.ru) Message-ID: <008501c03834$48711800$3f0657c2@w9g8j7> From: "Michael Kuzmin" To: References: <200009211926.e8LJQws65571@hak.lan.Awfulhak.org> Subject: Re: Dying multi-link PPP Date: Tue, 17 Oct 2000 16:16:00 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >> Our configuration is fairly standard, user-ppp with two modems and MP > > >> enabled at both sides of the channel (see ppp.conf below), the only > > >> pecularity is frequent redials due to telco (30 min call limit). It always > > >> works OK after reload and initial connects, but subsequent modem redials > > >> amont to accumulation of problems and performance degradation with > > >> unavoidable death in several hours. > > >> > > >> The usual final (dead) state of the channel is an infinite series of short > > >> connects each with LCP RecvTerminateReq in 15 sec after successful > > >> authorization and lcp -> open. The origin of this dead state could be > > >> tentitavely traced to simultaneous redial of both modem links, at that > > >> moment old ppp master at answering side exits and all new ppp processes > > >> born after that seems to unable to continue... ... > > > > > > You could also try > > > > > > disable pred1 deflate > > > deny pred1 deflate > > > > > > in your mpd profile - I believe there may be a problem with compression > > > at the moment. I just performed special experiments arranged according to your proposals: all redial delays increased to 5 sec, and all compression switched off (both link and bundle levels). Unfortunately that did not help, below is a general picture of dying MP, as seen by "last" command at answering side (atd): ata cuaa1 RELIABLE EC=(LA mo 16 oct 18:49 - 19:19 (00:30) ata cuaa1 RELIABLE EC=(LA mo 16 oct 18:20 - 18:48 (00:28) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:48 - 18:19 (00:30) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:40 - 17:47 (00:06) dialout cuaa2 mo 16 oct 17:36 - 19:01 (01:25) dialout cuaa2 mo 16 oct 17:35 - 17:36 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:33 - 17:40 (00:06) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:29 - 17:29 (00:00) ata cuaa2 4800:15/V34/V42B mo 16 oct 17:29 - 17:29 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:28 - 17:28 (00:00) ata cuaa2 4800:15/V34/V42B mo 16 oct 17:27 - 17:28 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:27 - 17:27 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:26 - 17:26 (00:00) ata cuaa2 4800:16/V34/V42B mo 16 oct 17:25 - 17:25 (00:00) ata cuaa2 4800:16/V34/V42B mo 16 oct 17:18 - 17:19 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:15 - 17:16 (00:00) ata cuaa2 4800:15/V34/V42B mo 16 oct 17:15 - 17:16 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:14 - 17:15 (00:00) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:13 - 17:14 (00:00) ata cuaa2 4800:17/V34/V42B mo 16 oct 17:10 - 17:10 (00:00) ata cuaa2 4800:15/V34/V42B mo 16 oct 17:05 - 17:08 (00:02) ata cuaa1 RELIABLE EC=(LA mo 16 oct 17:03 - 17:11 (00:08) ata cuaa2 4800:15/V34/V42B mo 16 oct 16:32 - 17:02 (00:30) ata cuaa1 RELIABLE EC=(LA mo 16 oct 16:28 - 16:59 (00:31) ata cuaa2 4800:15/V34/V42B mo 16 oct 16:27 - 16:30 (00:02) ata cuaa1 RELIABLE EC=(LA mo 16 oct 16:27 - 16:27 (00:00) mike ttyp1 aqua.laser.ru mo 16 oct 16:15 - 18:49 (02:34) It is quite typical for us: immediately after restart (16:27) there was a period of normal two-link operation (apparently up to 17:08 here), followed by... > the usual final (dead) state of the channel -- an infinite series of short > connects each with LCP RecvTerminateReq in 15 sec after successful > authorization and lcp -> open (a quote from my first message). We terminated it by hand at 17:29 and started two independent single-link ppp sessions over the same modems and the same ppp.config (but different label loaded: ppp cu1 instead of ppp mp) - our working arrangenet for the last month. Switching off MP immediately solved all the problems, as usual. Complete configs and logs (50k compressed) are redy to be sent out to everybody who may agree to review them. With many thanks for your help, Sincerely yours, Michael Kuzmin, LASERnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 9:33:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 90C4E37B4FE for ; Tue, 17 Oct 2000 09:33:42 -0700 (PDT) Received: from localhost (IDENT:ev2vtdH1L51OhK6tRO/VsU527lMchKl465eB5l9aM1ImGiqxiR9AIlv8i4/yWmd8@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.1/8.11.1/peace) with ESMTP/inet6 id e9HGX5K95850; Wed, 18 Oct 2000 01:33:05 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 18 Oct 2000 01:33:02 +0900 (JST) Message-Id: <20001018.013302.92495437.ume@mahoroba.org> To: jinmei@isl.rdc.toshiba.co.jp Cc: jens-ulrik.petersen@nokia.com, freebsd-net@FreeBSD.ORG, users@ipv6.org Subject: Re: dns lookup with IPv6 transport? From: Hajimu UMEMOTO In-Reply-To: References: X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org jinmei> If I remember correctly, FreeBSD 4.1 supports IPv6 of DNS transport. Yes, resolver on FreeBSD 4.1 or later supports IPv6 DNS transport. However, BIND shipped with FreeBSD is not support it, yet. jinmei> I don't know much about FreeBSD configuration , but how about trying jinmei> to add the following in your /etc/resolv.conf? jinmei> nameserver xxxx:yyyy:zzzz:... jinmei> where xxxx:... is the IPv6 address of your DNS server. FYI: My current configuration is: domain mahoroba.org nameserver fe80::220:afff:fef8:7c44%de0 nameserver 2001:200:301:0:220:afff:fef8:7c44 nameserver 202.227.26.33 -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 12: 6:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 40DF937B4CF; Tue, 17 Oct 2000 12:06:14 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id MAA07087; Tue, 17 Oct 2000 12:03:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAAaoaGzn; Tue Oct 17 12:02:55 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA00326; Tue, 17 Oct 2000 12:05:43 -0700 (MST) From: Terry Lambert Message-Id: <200010171905.MAA00326@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: peter@netplex.com.au (Peter Wemm) Date: Tue, 17 Oct 2000 19:05:42 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), bright@wintelcom.net (Alfred Perlstein), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <200010170712.e9H7C3G58805@netplex.com.au> from "Peter Wemm" at Oct 17, 2000 12:12:03 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I guess I'm asking "What moron would want to intentionally disable > > system resource tracking?". > > Who said anything about disabling system resource tracking? "track all > closes" means to call the devsw d_close function for *each* close, not just > for the "last close" as 99% of our drivers expect... If we suddenly caused > d_close() to be called on every close() syscall, then existing drivers break > because they are used to freeing everything and cleaning up when the close > function is called. Who remembers the open that resulted in the close, if not the driver? Perhaps I'm merely complaining that there are not seperate "close" and "last_close" entry points, since exposing a "last_close" entry point, and then a generic "close" handler that calls "last_close" when the reference count goes from 1->0, which is ignored if the driver has a non-generic handler. Not much of a namespace exposure kludge. I guess I'm anout as annoyed as I was when supposed "bit rot" killed the ISODE and X.25 functioning, when certain kernel interfaces were redefined, without the person doing the redefintion taking care to maintain all caller instances, or when a similar thing ate LFS. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 15:23:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 25DC437B4D7 for ; Tue, 17 Oct 2000 15:23:19 -0700 (PDT) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id HAA01426; Wed, 18 Oct 2000 07:23:02 +0900 (JST) Message-Id: <200010172223.HAA01426@coconut.itojun.org> To: Bill Manning Cc: jens-ulrik.petersen@nokia.com (Jens-Ulrik Petersen), freebsd-net@FreeBSD.ORG, users@ipv6.org In-reply-to: bmanning's message of Tue, 17 Oct 2000 02:24:04 MST. <200010170924.CAA03673@zed.isi.edu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: dns lookup with IPv6 transport? From: Jun-ichiro itojun Hagino Date: Wed, 18 Oct 2000 03:19:14 +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Bindv9 is prefered. There is some limited support with bindv8 but it >requires significant patching w/ KAME code. for server side, BIND9 is prefered. for client side, you will be able to lookup DNS over IPv6 fine, with the following platforms: FreeBSD 4.1 and beyond OpenBSD 2.7 and beyond NetBSD 1.5 and beyond most of KAME-patched platforms i'm not sure about other vendor products. The KAME patch to BIND8 is for 8.1.2, and 8.1.2 has security issue. i was supposed to do a patch for 8.2.x, but i have no time yet to finish it... itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Oct 17 23: 0:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from alfa.itea.ntnu.no (alfa.itea.ntnu.no [129.241.18.10]) by hub.freebsd.org (Postfix) with ESMTP id E6B4C37B4F9 for ; Tue, 17 Oct 2000 23:00:47 -0700 (PDT) Received: by alfa.itea.ntnu.no id IAA0000026523; Wed, 18 Oct 2000 08:00:36 +0200 (MET DST) From: Stig Venås Date: Wed, 18 Oct 2000 08:00:35 +0200 To: Jun-ichiro itojun Hagino Cc: Bill Manning , Jens-Ulrik Petersen , freebsd-net@FreeBSD.ORG, users@ipv6.org Subject: Re: dns lookup with IPv6 transport? Message-ID: <20001018080035.A8595@itea.ntnu.no> References: <200010170924.CAA03673@zed.isi.edu> <200010172223.HAA01426@coconut.itojun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010172223.HAA01426@coconut.itojun.org>; from itojun@iijlab.net on Wed, Oct 18, 2000 at 03:19:14AM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 18, 2000 at 03:19:14AM +0900, Jun-ichiro itojun Hagino wrote: > >Bindv9 is prefered. There is some limited support with bindv8 but it > >requires significant patching w/ KAME code. > > for server side, BIND9 is prefered. for client side, you will be able > to lookup DNS over IPv6 fine, with the following platforms: > FreeBSD 4.1 and beyond > OpenBSD 2.7 and beyond > NetBSD 1.5 and beyond > most of KAME-patched platforms > i'm not sure about other vendor products. It's also supported by the GNU C Library since version 2.1.92, so it should work in RedHat 7. Stig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 0: 2:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 3E5EA37B4E5 for ; Wed, 18 Oct 2000 00:02:19 -0700 (PDT) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id QAA07359; Wed, 18 Oct 2000 16:02:11 +0900 (JST) To: "Wei Zhao (ERA)" Cc: "'freebsdnet'" In-reply-to: Wei.Zhao's message of Tue, 17 Oct 2000 13:59:04 +0200. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: ipv6cp implementation.. From: itojun@iijlab.net Date: Wed, 18 Oct 2000 16:02:11 +0900 Message-ID: <7357.971852531@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I am wondering if anyone has any experience implementing ipv6cp for PPP >protocol, or anyone knows if there exists any implementation. NetBSD /usr/sbin/pppd (which is from pppd distribution) NetBSD sys/net/if_spppsubr.c KAME/FreeBSD3 modified iij-ppp (for freebsd, you may want to look at it and try to integrate it into the latest one) there are apparently vendor router implementations including Yamaha, Hitachi and Cisco. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 5:46: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 6378237B4E5 for ; Wed, 18 Oct 2000 05:46:03 -0700 (PDT) Received: (from bonnetf@localhost) by bart.esiee.fr (8.11.1/8.11.1) id e9ICjxS15744 for freebsd-net@freebsd.org; Wed, 18 Oct 2000 14:45:59 +0200 (METDST) From: Frank Bonnet Message-Id: <200010181245.e9ICjxS15744@bart.esiee.fr> Subject: Boot a new machine from lan ( bootp / tftp ) To: freebsd-net@freebsd.org Date: Wed, 18 Oct 2000 14:45:59 METDST X-Mailer: Elm [revision: 212.5] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Is there a way to boot a brand new machine from a bootp/tftp server at 4.1.1 ? which file (kernel) do I have to put in the tftpdir ? The PC has no floppy and no CDROM ( new HP box ) but it seems to know to boot from lan at BIOS. Thanks for any infos -- Frank Bonnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 9:31:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 5F78D37B4C5; Wed, 18 Oct 2000 09:31:24 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9IGV9979806; Wed, 18 Oct 2000 19:31:09 +0300 (EEST) (envelope-from ru) Date: Wed, 18 Oct 2000 19:31:09 +0300 From: Ruslan Ermilov To: Darren Reed Cc: net@FreeBSD.org Subject: IP Filter: small patch for FreeBSD re: ip_id Message-ID: <20001018193109.A78734@sunbay.com> Mail-Followup-To: Darren Reed , net@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Darren and -net! As you probably know, recent versions of FreeBSD do not byte-swap the ip_id IP header field from network to host byte order anymore. When I did that change, I have looked at what NetBSD has already done (I am talking about the IP Filter part re: the ip_id here), and just imported their patches (since I am not running the IPF personally and could not test). Today I was reviewing my modifications, and have found (I think) the place where the byte-swapping of ip_id became now in error. Can you please review the attached (tiny) patch? If you find this change right, please forward it to NetBSD as well. Cheers, -- 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 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: fil.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/fil.c,v retrieving revision 1.19 diff -u -p -r1.19 fil.c --- fil.c 2000/08/13 04:31:05 1.19 +++ fil.c 2000/10/18 16:08:57 @@ -825,12 +825,14 @@ int out; # endif #endif /* _KERNEL */ +#ifndef __FreeBSD__ /* * Be careful here: ip_id is in network byte order when called * from ip_output() */ if ((out) && (v == 4)) ip->ip_id = ntohs(ip->ip_id); +#endif changed = 0; fin->fin_v = v; @@ -1037,8 +1039,10 @@ logit: } #endif /* IPFILTER_LOG */ +#ifndef __FreeBSD__ if ((out) && (v == 4)) ip->ip_id = htons(ip->ip_id); +#endif #ifdef _KERNEL /* --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 11:40:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from klaki.net (klaki.net [130.208.195.10]) by hub.freebsd.org (Postfix) with ESMTP id C73AD37B479 for ; Wed, 18 Oct 2000 11:40:32 -0700 (PDT) Received: (from bre@localhost) by klaki.net (8.9.3/8.9.3) id SAA01238 for freebsd-net@freebsd.org; Wed, 18 Oct 2000 18:40:21 GMT Date: Wed, 18 Oct 2000 18:40:17 +0000 From: Bjarni Runar Einarsson To: freebsd-net@freebsd.org Subject: natd & identd cooperation? Message-ID: <20001018184017.A1218@klaki.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I'm a relatively new FreeBSD user, lured from the world of Linux by the FreeBSD jails... so far so good. I'm currently playing with a 4.1.1 box which gives jailed users access to the 'net via natd. For those users interested in using IRC, the lack of an identd which will correctly either reply on a jail-by-jail basis or relay the ident requests back to a jailed identd is a bit of a problem. No, I'm not interested in randomizing the ident replies. :-) So, my question is, am I overlooking something, or is my only option to go ahead and hack up some identd and natd so they will communicate with each other? My current strategy is to use shared-memory tables to get oidentd and natd to talk to each other, allowing me to set up both static ip<->username mappings and dynamic connection<->user mappings. I have a ready-to-use library (UDB) designed for just this sort of thing, so this shouldn't take too much effort. Am I reinventing the wheel here, or is this a worthwhile project? Please stop me if someone has already solved this problem! Please CC: any replies directly to me, since I am not at the moment subscribed to this mailing list. Thanks! -- Bjarni R. Einarsson PGP: 02764305, B7A3AB89 bre@netverjar.is -><- http://bre.klaki.net/ Netverjar gegn ruslpósti: http://www.netverjar.is/baratta/ruslpostur/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 12: 0:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 0143C37B4CF for ; Wed, 18 Oct 2000 12:00:07 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13lycE-0000Vs-00; Wed, 18 Oct 2000 13:11:06 -0600 Message-ID: <39EDF5CA.157990C4@softweyr.com> Date: Wed, 18 Oct 2000 13:11:06 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Bjarni Runar Einarsson Cc: freebsd-net@freebsd.org Subject: Re: natd & identd cooperation? References: <20001018184017.A1218@klaki.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bjarni Runar Einarsson wrote: > > Hi all, > > I'm a relatively new FreeBSD user, lured from the world of Linux by > the FreeBSD jails... so far so good. > > I'm currently playing with a 4.1.1 box which gives jailed users > access to the 'net via natd. For those users interested in using > IRC, the lack of an identd which will correctly either reply on a > jail-by-jail basis or relay the ident requests back to a jailed > identd is a bit of a problem. > > No, I'm not interested in randomizing the ident replies. :-) > > So, my question is, am I overlooking something, or is my only > option to go ahead and hack up some identd and natd so they will > communicate with each other? > > My current strategy is to use shared-memory tables to get oidentd > and natd to talk to each other, allowing me to set up both static > ip<->username mappings and dynamic connection<->user mappings. I > have a ready-to-use library (UDB) designed for just this sort of > thing, so this shouldn't take too much effort. > > Am I reinventing the wheel here, or is this a worthwhile project? > Please stop me if someone has already solved this problem! Yeah, what you need is my "Liar's identd." You can get the current version from ftp://ftp.bsdconspiracy.net/pub/softweyr/liedentd.tgz I have a couple of improvements from a beta tester to roll in, then I plan to commit it as a port. It responds with the same answer for every request; a future version will allow you to provide a list of responses to make. The default reponse is "Fools trust ident" -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 13:34:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from oberon.dnai.com (oberon.dnai.com [207.181.194.97]) by hub.freebsd.org (Postfix) with ESMTP id 8A25F37B4D7 for ; Wed, 18 Oct 2000 13:34:42 -0700 (PDT) Received: from azoth.dnai.com (azoth.dnai.com [207.181.194.94]) by oberon.dnai.com (8.9.3/8.9.3) with ESMTP id NAA16358 for ; Wed, 18 Oct 2000 13:34:41 -0700 (PDT) Received: from pc2 (cougar.chiplogic.com [216.15.52.34]) by azoth.dnai.com (8.9.3/8.9.3) with SMTP id NAA55832 for ; Wed, 18 Oct 2000 13:34:41 -0700 (PDT) Message-ID: <002201c03943$d7f51890$4b00a8c0@domain> From: "ksreeni" To: Subject: Subscribe freebsd-net Date: Wed, 18 Oct 2000 13:41:41 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C03909.258117C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C03909.258117C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subscribe freebsd-net=20 ------=_NextPart_000_001F_01C03909.258117C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Subscribe freebsd-net
------=_NextPart_000_001F_01C03909.258117C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 16: 3:39 2000 Delivered-To: freebsd-net@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id DFBDA37B4CF for ; Wed, 18 Oct 2000 16:03:32 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G2N0076HEPSGW@field.videotron.net> for net@freebsd.org; Wed, 18 Oct 2000 19:03:28 -0400 (EDT) Date: Wed, 18 Oct 2000 19:07:44 -0400 (EDT) From: Bosko Milekic Subject: Re: how to detect recent mbuf changes In-reply-to: <20001016161133.V272@fw.wintelcom.net> X-Sender: bmilekic@jehovah.technokratis.com To: Alfred Perlstein Cc: net@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 16 Oct 2000, Alfred Perlstein wrote: > Have we bumbed FreeBSD version or do we have some other way to detect > the recent change in the way mbuf clusters are counted? > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." To answer your question: Yes, I notice that it has been bumped in the meantime in -CURRENT after the SMP stuff has gone in. You should be checking __FreeBSD_version for 500013 or greater (the ref-counting and other similar changes -- all but the mutex stuff) has been committed before that version. You'll note that the ref counting code was not MFCd, so you're in luck. Have fun, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 16:55:34 2000 Delivered-To: freebsd-net@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 4F95037B4D7 for ; Wed, 18 Oct 2000 16:55:29 -0700 (PDT) Received: from flip.jhs.private (flip.jhs.private [192.168.91.24]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id e9IMGRo01512; Wed, 18 Oct 2000 22:16:27 GMT (envelope-from jhs@jhs.muc.de) Received: from flip.jhs.private (localhost [127.0.0.1]) by flip.jhs.private (8.9.3/8.9.3) with ESMTP id UAA38568; Wed, 18 Oct 2000 20:54:55 GMT (envelope-from jhs@flip.jhs.private) Message-Id: <200010182054.UAA38568@flip.jhs.private> To: "Chris Angell" Cc: freebsd-net@FreeBSD.ORG Subject: Re: DNS From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Wed, 27 Sep 2000 15:44:08 EDT." <20000927154408.R34501@jade.chc-chimes.com> Date: Wed, 18 Oct 2000 22:54:55 +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 27, 2000 at 12:39:48PM -0700, Chris Angell wrote: > I have tried everything to get my DNS working right. Did you check your config with ports/net/nslint/ ? (Bill Vermillion put me on to nslint :-) PS I wish there was a similar tool for sendmail.cf (I'm hoping someone will say "there is", though I know of none at present... Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 22:51:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from bahn.net (mail.ibahn.net [207.19.254.1]) by hub.freebsd.org (Postfix) with ESMTP id 87EE837B479 for ; Wed, 18 Oct 2000 22:51:36 -0700 (PDT) Received: from jjib-notebook (AP-203.167.11.10.sysads.com [203.167.11.10]) by LAA06015bahn.net (8.9.3/8.9.3) with SMTP id LAA06015 for ; Mon, 16 Oct 2000 11:54:52 +0800 Message-ID: <001b01c03719$ecdd2580$e7e9fea9@jjib-notebook> From: "Raul Ocampo" To: Subject: Date: Mon, 16 Oct 2000 10:36:43 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C0375C.F9CAA4A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C0375C.F9CAA4A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe ------=_NextPart_000_0018_01C0375C.F9CAA4A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unsubscribe
------=_NextPart_000_0018_01C0375C.F9CAA4A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 22:53: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id C47DF37B4E5 for ; Wed, 18 Oct 2000 22:53:04 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA38071; Thu, 19 Oct 2000 01:52:57 -0400 (EDT) Date: Thu, 19 Oct 2000 01:52:56 -0400 (EDT) From: "Matthew N. Dodd" To: Julian Stacey Cc: Chris Angell , freebsd-net@FreeBSD.ORG Subject: Re: DNS In-Reply-To: <200010182054.UAA38568@flip.jhs.private> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Oct 2000, Julian Stacey wrote: > PS I wish there was a similar tool for sendmail.cf (I'm hoping someone > will say "there is", though I know of none at present... `sendmail -bt`? -- | 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 | This Space For Rent | 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 Wed Oct 18 22:55:40 2000 Delivered-To: freebsd-net@freebsd.org Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (Postfix) with ESMTP id D507137B479 for ; Wed, 18 Oct 2000 22:55:34 -0700 (PDT) Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id LAA14888 for ; Thu, 19 Oct 2000 11:19:59 +0500 (GMT) Received: from sarovar.mail.wipro.com ([192.168.2.18]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id LAA10253 for ; Thu, 19 Oct 2000 11:23:10 +0500 (GMT) Received: from U125086-rajendra ([192.168.253.167]) by sarovar.mail.wipro.com (Netscape Messaging Server 3.6) with SMTP id AAA2B7 for ; Thu, 19 Oct 2000 11:23:33 +0530 From: "vipin aravind" To: Subject: unsubscribe Date: Thu, 19 Oct 2000 11:26:29 +0530 Message-ID: <001b01c03991$5348e060$a7fda8c0@U125086-rajendra.wipro.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Oct 18 23: 1:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (Postfix) with ESMTP id D47BB37B4C5 for ; Wed, 18 Oct 2000 23:01:42 -0700 (PDT) Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id LAA15398 for ; Thu, 19 Oct 2000 11:26:14 +0500 (GMT) Received: from sarovar.mail.wipro.com ([192.168.2.18]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id LAA10941 for ; Thu, 19 Oct 2000 11:29:28 +0500 (GMT) Received: from U125086-rajendra ([192.168.253.167]) by sarovar.mail.wipro.com (Netscape Messaging Server 3.6) with SMTP id AAACF3 for ; Thu, 19 Oct 2000 11:29:51 +0530 From: "vipin aravind" To: Subject: unsubscribe Date: Thu, 19 Oct 2000 11:32:48 +0530 Message-ID: <001d01c03992$351bd9c0$a7fda8c0@U125086-rajendra.wipro.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 1: 2:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 18D5E37B4D7 for ; Thu, 19 Oct 2000 01:02:20 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9J81AJ01459; Thu, 19 Oct 2000 11:01:10 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Oct 2000 11:01:10 +0300 From: Ruslan Ermilov To: Bjarni Runar Einarsson Cc: freebsd-net@FreeBSD.ORG Subject: Re: natd & identd cooperation? Message-ID: <20001019110110.C98924@sunbay.com> Mail-Followup-To: Bjarni Runar Einarsson , freebsd-net@FreeBSD.ORG References: <20001018184017.A1218@klaki.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001018184017.A1218@klaki.net>; from bre@netverjar.is on Wed, Oct 18, 2000 at 06:40:17PM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 18, 2000 at 06:40:17PM +0000, Bjarni Runar Einarsson wrote: > Hi all, > > I'm a relatively new FreeBSD user, lured from the world of Linux by > the FreeBSD jails... so far so good. > > I'm currently playing with a 4.1.1 box which gives jailed users > access to the 'net via natd. For those users interested in using > IRC, the lack of an identd which will correctly either reply on a > jail-by-jail basis or relay the ident requests back to a jailed > identd is a bit of a problem. > > No, I'm not interested in randomizing the ident replies. :-) > > So, my question is, am I overlooking something, or is my only > option to go ahead and hack up some identd and natd so they will > communicate with each other? > > My current strategy is to use shared-memory tables to get oidentd > and natd to talk to each other, allowing me to set up both static > ip<->username mappings and dynamic connection<->user mappings. I > have a ready-to-use library (UDB) designed for just this sort of > thing, so this shouldn't take too much effort. > > Am I reinventing the wheel here, or is this a worthwhile project? > Please stop me if someone has already solved this problem! > > Please CC: any replies directly to me, since I am not at the moment > subscribed to this mailing list. > I am working on implementing IDENT support for libalias(3) and (as a consequence) for natd(8). Meanwhile, you can do it with inetd(8) as follows: In /etc/inetd.conf, specify the following string for internal ``auth'': auth stream tcp nowait root internal auth -d foo Then redirect the TCP port 113 to this machine's inetd like this: natd -redirect_port tcp NAT:auth auth If you like, I will let you know when my IDENT patch will be ready. Hope this helps, -- 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 Thu Oct 19 1:28:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from uemsconcpf1.cpf.navy.mil (oban-nat-1.cpf.navy.mil [199.124.14.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D84937B4D7 for ; Thu, 19 Oct 2000 01:28:43 -0700 (PDT) Received: by u352-serv-1-host-269.cpf.navy.mil with Internet Mail Service (5.5.2650.21) id <467A2T6S>; Wed, 18 Oct 2000 22:28:37 -1000 Message-ID: From: "Kuriyama, Kent K Mr (CPF N651KK)" To: freebsd-net@freebsd.org Subject: Question regarding 'pptpclient' Date: Wed, 18 Oct 2000 22:28:34 -1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to establish a PPTP connection between our FreeBSD 4.1.1-STABLE box and an NT4.0 RAS. I have loaded the pptpclient from the packages collection but when I attempt to connect I get the message: "CHAP 0x81 not supported" What does this message mean and is there a work around? Thanks. Kent Kuriyama SPAWAR Sys Ctr San Diego D424, CINCPACFLT N671KK kuriyakk@cpf.navy.mil, 808-471-4125 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 1:40: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 41C4137B4CF for ; Thu, 19 Oct 2000 01:40:05 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.11.0/8.11.0) with ESMTP id e9J8e1I29906; Thu, 19 Oct 2000 09:40:01 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.0) with ESMTP id e9J8eTY02261; Thu, 19 Oct 2000 01:40:29 -0700 (PDT) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200010190840.e9J8eTY02261@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kuriyama, Kent K Mr (CPF N651KK)" Cc: freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: Question regarding 'pptpclient' In-Reply-To: Message from "Kuriyama, Kent K Mr (CPF N651KK)" of "Wed, 18 Oct 2000 22:28:34 -1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Oct 2000 01:40:29 -0700 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org CHAP 0x81 (M$Chap v2) isn't yet supported I'm afraid. > I'm trying to establish a PPTP connection between our FreeBSD 4.1.1-STABLE > box and an NT4.0 RAS. I have loaded the pptpclient from the packages > collection but when I attempt to connect I get the message: > > "CHAP 0x81 not supported" > > What does this message mean and is there a work around? Thanks. > > Kent Kuriyama > SPAWAR Sys Ctr San Diego D424, CINCPACFLT N671KK > kuriyakk@cpf.navy.mil, 808-471-4125 -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 1:52:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from eden.dei.uc.pt (eden.dei.uc.pt [193.137.203.230]) by hub.freebsd.org (Postfix) with ESMTP id D07B737B4E5 for ; Thu, 19 Oct 2000 01:52:28 -0700 (PDT) Received: from snake (snake.dei.uc.pt [10.3.0.3]) by eden.dei.uc.pt (8.11.0/8.11.0) with ESMTP id e9J8qN020372 for ; Thu, 19 Oct 2000 09:52:23 +0100 (WET DST) Message-Id: <4.2.0.58.20001019095328.021bb8c0@eden.dei.uc.pt> X-Sender: elreis@eden.dei.uc.pt X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 19 Oct 2000 09:53:42 -0700 To: freebsd-net@FreeBSD.ORG From: Elisabete Reis Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 2: 1: 6 2000 Delivered-To: freebsd-net@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 2068F37B479 for ; Thu, 19 Oct 2000 02:01:03 -0700 (PDT) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 4968]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113360-234>; Thu, 19 Oct 2000 11:00:58 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id BE56D13631; Thu, 19 Oct 2000 11:00:43 +0200 (CEST) From: Daniel Lang To: freebsd-net@freebsd.org Subject: virtual/alias ips and arp_rtrequest: bad gateway value Message-ID: <20001019110043.A50474@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Date: Thu, 19 Oct 2000 11:00:44 +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Folks, I have some boxes, that use many virtual IPs. ifconfig(8) tells, one has to use a netmask of 0xffffffff for the aliases, if they are on the same network (they are). I run FreeBSD 4.1-STABLE (some 4.1.1-STABLE) Assigning the alias addresses to the interface does work, although I get a warning about a possible netmask problem. The other thing is, that console and syslog is getting overwhelmed with [..] /kernel: arp_rtrequest: bad gateway value [..] I'm not sure, if there's a connection, but I suspect so, since it doesn't occur on other boxes, without alias ips, and I searched through the freebsd mailing lists, where this error has been reported previously, but no solution was posted. However, I run routed on the concerned machines, so maybe this one introduces routes, that may be wrong ? The local network is 131.159.0.0/16. Here is an excerpt from the routing tables: Destination Gateway Flags Refs Use Netif Expire default 131.159.0.254 UGSc 7 567 xl0 127.0.0.1 127.0.0.1 UH 1 36 lo0 131.159 link#1 UC 0 0 xl0 => 131.159.0.16 0:c0:7b:53:ec:2e UHLW 0 0 xl0 1111 131.159.0.76 8:0:20:85:f3:10 UHLW 0 630 xl0 1101 [ many similar routes ] 131.159.72.5/32 link#1 UC 0 0 xl0 => 131.159.72.10/32 link#1 UC 0 0 xl0 => 131.159.72.16 131.159.72.16 UHLW 0 1303 lo0 => 131.159.72.16/32 link#1 UC 0 0 xl0 => 131.159.72.17/32 link#1 UC 0 0 xl0 => 131.159.72.18 131.159.72.18 UHLW 0 514 lo0 => 131.159.72.18/32 link#1 UC 0 0 xl0 => 131.159.72.24/32 link#1 UC 0 0 xl0 => 131.159.72.25 131.159.72.25 UHLW 0 20 lo0 => 131.159.72.25/32 link#1 UC 0 0 xl0 => 131.159.72.29/32 link#1 UC 0 0 xl0 => [ these are alias ips ] 172.16.0.58 131.159.1.92 UGH 0 0 xl0 172.16.4.131 131.159.1.92 UGH 0 0 xl0 The last two must be introduced by routed, since I don't statically route the 172.16 net (which is modem pool using these private ips). Any suggestions ? Best regards, Daniel -- IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you will be approximated. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 2:12:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 4745D37B4D7 for ; Thu, 19 Oct 2000 02:11:40 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9J95BV05285; Thu, 19 Oct 2000 12:05:11 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Oct 2000 12:05:11 +0300 From: Ruslan Ermilov To: Bjarni Runar Einarsson , freebsd-net@FreeBSD.ORG Subject: Re: natd & identd cooperation? Message-ID: <20001019120511.A4555@sunbay.com> Mail-Followup-To: Bjarni Runar Einarsson , freebsd-net@FreeBSD.ORG References: <20001018184017.A1218@klaki.net> <20001019110110.C98924@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001019110110.C98924@sunbay.com>; from ru@FreeBSD.ORG on Thu, Oct 19, 2000 at 11:01:10AM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Oct 19, 2000 at 11:01:10AM +0300, Ruslan Ermilov wrote: > On Wed, Oct 18, 2000 at 06:40:17PM +0000, Bjarni Runar Einarsson wrote: > > Hi all, > > > > I'm a relatively new FreeBSD user, lured from the world of Linux by > > the FreeBSD jails... so far so good. > > > > I'm currently playing with a 4.1.1 box which gives jailed users > > access to the 'net via natd. For those users interested in using > > IRC, the lack of an identd which will correctly either reply on a > > jail-by-jail basis or relay the ident requests back to a jailed > > identd is a bit of a problem. > > > > No, I'm not interested in randomizing the ident replies. :-) > > > > So, my question is, am I overlooking something, or is my only > > option to go ahead and hack up some identd and natd so they will > > communicate with each other? > > > > My current strategy is to use shared-memory tables to get oidentd > > and natd to talk to each other, allowing me to set up both static > > ip<->username mappings and dynamic connection<->user mappings. I > > have a ready-to-use library (UDB) designed for just this sort of > > thing, so this shouldn't take too much effort. > > > > Am I reinventing the wheel here, or is this a worthwhile project? > > Please stop me if someone has already solved this problem! > > > > Please CC: any replies directly to me, since I am not at the moment > > subscribed to this mailing list. > > > I am working on implementing IDENT support for libalias(3) and (as a > consequence) for natd(8). Meanwhile, you can do it with inetd(8) as > follows: > > In /etc/inetd.conf, specify the following string for internal ``auth'': > auth stream tcp nowait root internal auth -d foo > > Then redirect the TCP port 113 to this machine's inetd like this: > natd -redirect_port tcp NAT:auth auth > > If you like, I will let you know when my IDENT patch will be ready. > Following up to myself: the IDENT support for NAT is impossible (or, at least, would be very hard to implement), because IDENT uses TCP as its transport, and we don't know in advance where we should redirect the first (incoming) SYN packet, because ports information is missing from it. Though this is still seems to be possible with T/TCP. -- 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 Thu Oct 19 2:25: 9 2000 Delivered-To: freebsd-net@freebsd.org Received: from center.mshindo.net (center.mshindo.net [210.231.221.221]) by hub.freebsd.org (Postfix) with ESMTP id CF8F437B4C5 for ; Thu, 19 Oct 2000 02:25:04 -0700 (PDT) Received: from cosinecom.com (017.cosine.nttpc.gr.jp [202.229.42.17] (may be forged)) by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id SAA24656; Thu, 19 Oct 2000 18:34:00 +0900 (JST) Date: Thu, 19 Oct 2000 18:25:43 +0900 (JST) Message-Id: <20001019.182543.74756319.mshindo@mshindo.net> To: KuriyaKK@cpf.navy.mil Cc: freebsd-net@freebsd.org Subject: Re: Question regarding 'pptpclient' From: Motonori Shindo In-Reply-To: References: X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands) X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14 63 C0 D7 18 01 CD D9 83 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kuriyama-san, From: "Kuriyama, Kent K Mr (CPF N651KK)" Subject: Question regarding 'pptpclient' Date: Wed, 18 Oct 2000 22:28:34 -1000 > I'm trying to establish a PPTP connection between our FreeBSD 4.1.1-STABLE > box and an NT4.0 RAS. I have loaded the pptpclient from the packages > collection but when I attempt to connect I get the message: > > "CHAP 0x81 not supported" > > What does this message mean and is there a work around? Thanks. CHAP 0x81 is MS-CHAPv2. I'm not using the package version of pptp, instead, I'm using pptp-linux-1.0.2 slightly modified by myself a while back. It's working with NT4.0 RAS. Regards, > Kent Kuriyama > SPAWAR Sys Ctr San Diego D424, CINCPACFLT N671KK > kuriyakk@cpf.navy.mil, 808-471-4125 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > =--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--= +----+----+ |.. .| | Motonori Shindo |_~__| | | .. |~~_~| Sr. Systems Engineer | . | | CoSine Communications Inc. +----+----+ C o S i n e e-mail: mshindo@cosinecom.com Communications =--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 6:50:22 2000 Delivered-To: freebsd-net@freebsd.org Received: from rsys002a.roke.co.uk (rsys002a.roke.co.uk [193.118.192.251]) by hub.freebsd.org (Postfix) with ESMTP id B631237B4CF for ; Thu, 19 Oct 2000 06:50:20 -0700 (PDT) Received: by RSYS002A with Internet Mail Service (5.5.2650.21) id ; Thu, 19 Oct 2000 14:50:10 +0100 Message-ID: <76C92FBBFB58D411AE760090271ED41866E01A@RSYS002A> From: "Gallagher, Mick" To: freebsd-net@freebsd.org Subject: GIF IPv6 tunnelling support Date: Thu, 19 Oct 2000 14:50:09 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, I'm trying to figure out GIF. The GIF man page suggests that the GIF tunnelling behaviour is based on RFC1933, which outlines transition mechanisms for IPv6 (basically v6 in v4 tunnelling). So far as v6-in-v6 and v4-in-v6 tunnelling is concerned, does GIF implement RFC2473 (Generic Packet Tunnelling in IPv6)? Also, does the GIF driver perform packet encapsulation itself, or does it pass inner packets through the stack for encapsulation in the outer packet? (I'm wondering about v6 extension headers in the outer packet). Any help gratefully received. Thanks in advance. Mick Gallagher ---- mick.gallagher@roke.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 7:12:20 2000 Delivered-To: freebsd-net@freebsd.org Received: from lavender.sanpei.org (ppp161.dialup.st.keio.ac.jp [131.113.27.161]) by hub.freebsd.org (Postfix) with ESMTP id CBCC837B4C5 for ; Thu, 19 Oct 2000 07:12:09 -0700 (PDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e9JEBZ817011; Thu, 19 Oct 2000 23:11:35 +0900 (JST) Message-Id: <200010191411.e9JEBZ817011@lavender.sanpei.org> To: freebsd-net@FreeBSD.ORG Subject: [Patch] VLAN MTU1500 patch for FreeBSD 4.1-RELEASE and later X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 Oct 2000 23:11:35 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. This is VLAN MTU1500 patch for FreeBSD 4.1-RELEASE and later(sorry, I did not test under 5-current). This patch was created by HOSOKAWA Tatsumi-san(hosokawa@FreeBSD.org), but he was too busy to announce and commit. So I post this patch by proxy. This patch was tested: - with Intel PRO/100+ Management Adapter(fxp) - with Netgear Gigabit Ethernet (MM SC) GA-620 And we will use other NICs which support VLAN packet. Cheers. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. diff -urN ../src/sys/net/if_ethersubr.c sys/net/if_ethersubr.c --- ../src/sys/net/if_ethersubr.c Tue Jul 18 06:24:34 2000 +++ sys/net/if_ethersubr.c Thu Sep 21 20:50:41 2000 @@ -139,12 +139,26 @@ u_char esrc[6], edst[6]; register struct rtentry *rt; register struct ether_header *eh; +#if NVLAN > 0 + register struct ether_vlan_header *evh = NULL; + register struct ifvlan *ifv = NULL; +#endif /* NVLAN > 0 */ + register struct ifnet *ifp_s; int off, loop_copy = 0; int hlen; /* link layer header lenght */ struct arpcom *ac = IFP2AC(ifp); if ((ifp->if_flags & (IFF_UP|IFF_RUNNING)) != (IFF_UP|IFF_RUNNING)) senderr(ENETDOWN); + ifp_s = ifp; +#if NVLAN > 0 + if (ifp->if_data.ifi_type == IFT_8021_VLAN) { + ifv = ifp->if_softc; + ifp_s = ifv->ifv_p; + if ((ifp_s->if_flags & (IFF_UP|IFF_RUNNING)) != (IFF_UP|IFF_RUNNING)) + senderr(ENETDOWN); + } +#endif /* NVLAN > 0 */ rt = rt0; if (rt) { if ((rt->rt_flags & RTF_UP) == 0) { @@ -171,6 +185,10 @@ senderr(rt == rt0 ? EHOSTDOWN : EHOSTUNREACH); } hlen = ETHER_HDR_LEN; +#if NVLAN > 0 + if (ifv != NULL) + hlen += EVL_ENCAPLEN; +#endif /* NVLAN > 0 */ switch (dst->sa_family) { #ifdef INET case AF_INET: @@ -229,6 +247,10 @@ bcopy(&llc, mtod(m, caddr_t), sizeof(struct llc)); type = htons(m->m_pkthdr.len); hlen = sizeof(struct llc) + ETHER_HDR_LEN; +#if NVLAN > 0 + if (ifv != NULL) + hlen += EVL_ENCAPLEN; +#endif /* NVLAN > 0 */ } else { type = htons(ETHERTYPE_AT); } @@ -304,19 +326,39 @@ * Add local net header. If no space in first mbuf, * allocate another. */ - M_PREPEND(m, sizeof (struct ether_header), M_DONTWAIT); - if (m == 0) - senderr(ENOBUFS); - eh = mtod(m, struct ether_header *); - (void)memcpy(&eh->ether_type, &type, - sizeof(eh->ether_type)); - (void)memcpy(eh->ether_dhost, edst, sizeof (edst)); - if (hdrcmplt) - (void)memcpy(eh->ether_shost, esrc, - sizeof(eh->ether_shost)); - else - (void)memcpy(eh->ether_shost, ac->ac_enaddr, - sizeof(eh->ether_shost)); +#if NVLAN > 0 + if (ifp->if_data.ifi_type == IFT_8021_VLAN) { + M_PREPEND(m, sizeof (struct ether_vlan_header), M_DONTWAIT); + if (m == 0) + senderr(ENOBUFS); + evh = mtod(m, struct ether_vlan_header *); + eh = (struct ether_header *) evh; + /*(void)memcpy(&evh->evl_encap_proto, &htons(vlan_proto), + sizeof(evh->evl_encap_proto));*/ + evh->evl_encap_proto = htons(vlan_proto); + evh->evl_tag = htons(ifv->ifv_tag); + (void)memcpy(&evh->evl_proto, &type, sizeof(evh->evl_proto)); + (void)memcpy(evh->evl_dhost, edst, sizeof(evh->evl_dhost)); + (void)memcpy(evh->evl_shost, ac->ac_enaddr, sizeof(evh->evl_shost)); + } + else { +#endif /* NVLAN > 0 */ + M_PREPEND(m, sizeof (struct ether_header), M_DONTWAIT); + if (m == 0) + senderr(ENOBUFS); + eh = mtod(m, struct ether_header *); + (void)memcpy(&eh->ether_type, &type, + sizeof(eh->ether_type)); + (void)memcpy(eh->ether_dhost, edst, sizeof (edst)); + if (hdrcmplt) + (void)memcpy(eh->ether_shost, esrc, + sizeof(eh->ether_shost)); + else + (void)memcpy(eh->ether_shost, ac->ac_enaddr, + sizeof(eh->ether_shost)); +#if NVLAN > 0 + } +#endif /* NVLAN > 0 */ /* * If a simplex interface, and the packet is being sent to our @@ -366,7 +408,24 @@ struct mbuf *m; { int s, error = 0; + int len = m->m_pkthdr.len; +#if NVLAN > 0 + register struct ifvlan *ifv = NULL; +#endif /* NVLAN > 0 */ + register struct ifnet *ifp_s; + ifp_s = ifp; +#if NVLAN > 0 + if (ifp->if_data.ifi_type == IFT_8021_VLAN) { + ifv = ifp->if_softc; + ifp_s = ifv->ifv_p; + if ((ifp_s->if_flags & (IFF_UP|IFF_RUNNING)) != (IFF_UP|IFF_RUNNING)) { + if (m != NULL) + m_freem(m); + return (ENETDOWN); + } + } +#endif /* NVLAN > 0 */ #ifdef BRIDGE if (do_bridge) { struct ether_header hdr; @@ -387,19 +446,31 @@ * Queue message on interface, and start output if interface * not yet active. */ - if (IF_QFULL(&ifp->if_snd)) { - IF_DROP(&ifp->if_snd); + if (IF_QFULL(&ifp_s->if_snd)) { + IF_DROP(&ifp_s->if_snd); splx(s); m_freem(m); return (ENOBUFS); } - ifp->if_obytes += m->m_pkthdr.len; + ifp_s->if_obytes += m->m_pkthdr.len; if (m->m_flags & M_MCAST) - ifp->if_omcasts++; - IF_ENQUEUE(&ifp->if_snd, m); - if ((ifp->if_flags & IFF_OACTIVE) == 0) - (*ifp->if_start)(ifp); + ifp_s->if_omcasts++; + IF_ENQUEUE(&ifp_s->if_snd, m); + if ((ifp_s->if_flags & IFF_OACTIVE) == 0) + (*ifp_s->if_start)(ifp_s); splx(s); +#if NVLAN > 0 + if (ifv != NULL) { + ifp->if_obytes += len + sizeof (struct ether_vlan_header); + ifp_s->if_obytes += len + sizeof (struct ether_vlan_header); + } else { + ifp_s->if_obytes += len + sizeof (struct ether_header); + } +#else /* NVLAN > 0 */ + ifp_s->if_obytes += len + sizeof (struct ether_header); + if (m->m_flags & M_MCAST) + ifp_s->if_omcasts++; +#endif /* NVLAN > 0 */ return (error); } @@ -633,6 +704,8 @@ #endif /* NETATALK */ } + /* XXXX */ + /*printf("ether_input: encolando el paquete\n");*/ s = splimp(); if (IF_QFULL(inq)) { IF_DROP(inq); diff -urN ../src/sys/net/if_vlan.c sys/net/if_vlan.c --- ../src/sys/net/if_vlan.c Tue Jul 18 06:24:34 2000 +++ sys/net/if_vlan.c Thu Sep 21 16:37:48 2000 @@ -356,10 +356,10 @@ if (ifv->ifv_p) return EBUSY; ifv->ifv_p = p; - if (p->if_data.ifi_hdrlen == sizeof(struct ether_vlan_header)) + /*if (p->if_data.ifi_hdrlen == sizeof(struct ether_vlan_header))*/ ifv->ifv_if.if_mtu = p->if_mtu; - else - ifv->ifv_if.if_mtu = p->if_data.ifi_mtu - EVL_ENCAPLEN; + /*else + ifv->ifv_if.if_mtu = p->if_data.ifi_mtu - EVL_ENCAPLEN;*/ /* * Preserve the state of the LINK0 flag for ourselves. diff -urN ../src/sys/pci/if_fxp.c sys/pci/if_fxp.c --- ../src/sys/pci/if_fxp.c Wed Jul 19 23:36:36 2000 +++ sys/pci/if_fxp.c Thu Sep 21 20:24:54 2000 @@ -34,6 +34,9 @@ * Intel EtherExpress Pro/100B PCI Fast Ethernet driver */ +#if !defined(KLD_MODULE) +#include "vlan.h" +#endif #include #include #include @@ -52,6 +55,12 @@ #include +#if NVLAN > 0 +#include +#include +#include +#endif /* NVLAN > 0 */ + #if defined(__NetBSD__) #include @@ -1177,7 +1186,19 @@ total_len = rfa->actual_size & (MCLBYTES - 1); if (total_len < +#if NVLAN > 0 + sizeof(struct ether_vlan_header)) { +#else sizeof(struct ether_header)) { +#endif /* NVLAN > 0 */ + m_freem(m); + goto rcvloop; + } + /* + * Drop the packet if it has CRC + * errors. + */ + if (rfa->rfa_status & FXP_RFA_STATUS_CRC) { m_freem(m); goto rcvloop; } @@ -1460,7 +1481,11 @@ cbp->late_scb = 0; /* (don't) defer SCB update */ cbp->tno_int = 0; /* (disable) tx not okay interrupt */ cbp->ci_int = 1; /* interrupt on CU idle */ +#if NVLAN > 0 + cbp->save_bf = 1; /* always save bad frames XXX */ +#else /* NVLAN > 0 */ cbp->save_bf = prm; /* save bad frames */ +#endif cbp->disc_short_rx = !prm; /* discard short packets */ cbp->underrun_retry = 1; /* retry mode (1) on DMA underrun */ cbp->mediatype = !sc->phy_10Mbps_only; /* interface mode */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Oct 19 13:53:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 2D91E37B4D7 for ; Thu, 19 Oct 2000 13:53:42 -0700 (PDT) Received: (from csg@localhost) by dustdevil.waterspout.com (8.11.0/8.11.0) id e9JKEdN17700; Thu, 19 Oct 2000 15:14:39 -0500 (EST) (envelope-from csg) Date: Thu, 19 Oct 2000 15:14:39 -0500 From: "C. Stephen Gunn" To: MIHIRA Sanpei Yoshiro Cc: freebsd-net@FreeBSD.ORG Subject: Re: [Patch] VLAN MTU1500 patch for FreeBSD 4.1-RELEASE and later Message-ID: <20001019151439.A17464@waterspout.com> References: <200010191411.e9JEBZ817011@lavender.sanpei.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200010191411.e9JEBZ817011@lavender.sanpei.org>; from sanpei@sanpei.org on Thu, Oct 19, 2000 at 11:11:35PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Oct 19, 2000 at 11:11:35PM +0900, MIHIRA Sanpei Yoshiro wrote: > This is VLAN MTU1500 patch for FreeBSD 4.1-RELEASE and > later(sorry, I did not test under 5-current). This patch was created > by HOSOKAWA Tatsumi-san(hosokawa@FreeBSD.org), but he was too busy > to announce and commit. So I post this patch by proxy. > > This patch was tested: > - with Intel PRO/100+ Management Adapter(fxp) > - with Netgear Gigabit Ethernet (MM SC) GA-620 In my experience with VLAN interfaces, most of this code should not be necessary. The problem lies in the difference in the MTU used by IP, and the maximum frame size a card/driver will receive. There isn't currently a mechanism in FreeBSD to either allow the physical device to report what its maximum receive framesize is, or to allow the vlan driver to request a larger one. While inelegant, I've simply configured my ethernet cards (ti/xl) to allow larger frames to be passed to ether input. With this patch installed, you can simply: ifconfig xl0 up ifconfig vlan0 vlan 123 vlandev xl0 inet 1.2.3.4 netmask 0xffffff00 mtu 1500 You have to set the MTU on the vlan device because the the default is ETHERMTU - EVL_ENCAPLEN (1496). If your hardware _actually_ delivers the oversize frames you're fine. My patch for the xl driver (works on 3c905B-TX cards) is available online. It simply allows for larger frames. http://www.physics.purdue.edu/~csg/FreeBSD/xl_vlan.patch - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 20 4:38:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id C469537B479 for ; Fri, 20 Oct 2000 04:38:52 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9KBcnE42557 for net@FreeBSD.org; Fri, 20 Oct 2000 14:38:49 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Oct 2000 14:38:49 +0300 From: Ruslan Ermilov To: net@FreeBSD.org Subject: IP reassembly, options, checksum, and ICMP error generation Message-ID: <20001020143849.A42456@sunbay.com> Mail-Followup-To: net@FreeBSD.org 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 X-Loop: FreeBSD.org Hi! RFC 791 says we should copy the IP header from the first fragment of the datagram, and re-calcalate the `ip_len' when full reassembly is complete (see section 3.2, Fragmentation and Reassembly). It does mean that although the `ip_len' is changed, the rest of the header, including `ip_sum', is simply copied from the first fragment (FO==0). This affects ICMP error generation. In case where original (fragmented) datagram for this host could not be delivered, the embedded copy of part of the original datagram will have incorrect checksum, like in the case when original (not exactly fragmented) datagram contained IP options. The question is: should we recalculate the header checksum of the original datagram in icmp_error()? -- 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 Fri Oct 20 6:12:39 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail-sp.viplink.com.br (baco.viplink.com.br [200.211.188.87]) by hub.freebsd.org (Postfix) with ESMTP id DA57A37B4CF for ; Fri, 20 Oct 2000 06:12:35 -0700 (PDT) Received: from ROMAMK (200.211.188.76 [200.211.188.76]) by mail-sp.viplink.com.br with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id T6Z55ZM4; Fri, 20 Oct 2000 12:13:10 -0200 Message-ID: <001901c03a97$98ff1320$0a06030a@visionmis.com.br> Reply-To: "Samuka" From: "Samuka" To: Subject: IPX over IP ??? Date: Fri, 20 Oct 2000 11:13:50 -0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org HI, Somebody know, how a can incapsulated IPX over IP? I have two bsd machine with two ethernet interface, frist interface a network ipx and the second interface a network ip (cloud ip). ipx net(a) -------|BSD|------could only ip-------|BSD|------- ipx net(b) The ipx net(a) and ipx net(b) have "see" both ipx net Thankful Samuel Almachar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 20 7: 4: 2 2000 Delivered-To: freebsd-net@freebsd.org Received: from klaki.net (klaki.net [130.208.195.10]) by hub.freebsd.org (Postfix) with ESMTP id BD7A337B4D7 for ; Fri, 20 Oct 2000 07:03:58 -0700 (PDT) Received: (from bre@localhost) by klaki.net (8.9.3/8.9.3) id OAA26137 for freebsd-net@FreeBSD.ORG; Fri, 20 Oct 2000 14:03:48 GMT Date: Fri, 20 Oct 2000 14:03:47 +0000 From: Bjarni Runar Einarsson To: freebsd-net@FreeBSD.ORG Subject: Re: natd & identd cooperation? (and identd + jails) Message-ID: <20001020140347.A25546@klaki.net> References: <20001018184017.A1218@klaki.net> <20001019110110.C98924@sunbay.com> <20001019120511.A4555@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <20001019120511.A4555@sunbay.com>; from Ruslan Ermilov on Thu, Oct 19, 2000 at 12:05:11PM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2000-10-19, 12:05:11 (+0300) Ruslan Ermilov wrote: > > I am working on implementing IDENT support for libalias(3) and (as a > > consequence) for natd(8). Meanwhile, you can do it with inetd(8) as > > follows: I took a stab at the problem, and have implemented primitive support within libalias for cooperation with oidentd. The implementation uses my UDB library (http://bre.klaki.net/programs/udb/), which allows the libalias app. and the ident server to share a table of ip<->user and connection<->user or connection<->connection mappings. The ident protocol doesn't by default allow user-land forwarding of connections (machine A can't request info about connections between B and C), but adding support for forwarded requests to an ident daemon is relatively easy. All in all, it works reasonably well - should I clean it up and share? While hacking I found out that all this effort was not quite necessary for a jailed environment like mine - an unmodified oidentd appears to ident connections correctly already, as long as natd is instructed to use the same ports. Using my libalias/UDB/oidentd hack is only useful because it adds the option of assigning a single user name to a whole jail. -- Bjarni R. Einarsson PGP: 02764305, B7A3AB89 bre@netverjar.is -><- http://bre.klaki.net/ Netverjar gegn ruslpósti: http://www.netverjar.is/baratta/ruslpostur/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 20 7:20:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 89C9C37B4D7 for ; Fri, 20 Oct 2000 07:20:35 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9KEK3l51367; Fri, 20 Oct 2000 17:20:03 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Oct 2000 17:20:03 +0300 From: Ruslan Ermilov To: Bjarni Runar Einarsson Cc: freebsd-net@FreeBSD.ORG Subject: Re: natd & identd cooperation? (and identd + jails) Message-ID: <20001020172003.A50854@sunbay.com> Mail-Followup-To: Bjarni Runar Einarsson , freebsd-net@FreeBSD.ORG References: <20001018184017.A1218@klaki.net> <20001019110110.C98924@sunbay.com> <20001019120511.A4555@sunbay.com> <20001020140347.A25546@klaki.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001020140347.A25546@klaki.net>; from bre@netverjar.is on Fri, Oct 20, 2000 at 02:03:47PM +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 20, 2000 at 02:03:47PM +0000, Bjarni Runar Einarsson wrote: > On 2000-10-19, 12:05:11 (+0300) Ruslan Ermilov wrote: > > > I am working on implementing IDENT support for libalias(3) and (as a > > > consequence) for natd(8). Meanwhile, you can do it with inetd(8) as > > > follows: > > I took a stab at the problem, and have implemented primitive support > within libalias for cooperation with oidentd. > > The implementation uses my UDB library > (http://bre.klaki.net/programs/udb/), which allows the libalias app. > and the ident server to share a table of ip<->user and > connection<->user or connection<->connection mappings. The ident > protocol doesn't by default allow user-land forwarding of connections > (machine A can't request info about connections between B and C), but > adding support for forwarded requests to an ident daemon is > relatively easy. > I am mostly interested in a real IDENT support for libalias(3), that would allow it to redirect incoming IDENT queries to the original host. Is it in any way possible with your patch? -- 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 Fri Oct 20 9:46: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from klaki.net (klaki.net [130.208.195.10]) by hub.freebsd.org (Postfix) with ESMTP id 7161637B479 for ; Fri, 20 Oct 2000 09:46:01 -0700 (PDT) Received: (from bre@localhost) by klaki.net (8.9.3/8.9.3) id QAA27792 for freebsd-net@FreeBSD.ORG; Fri, 20 Oct 2000 16:45:52 GMT Date: Fri, 20 Oct 2000 16:45:48 +0000 From: Bjarni Runar Einarsson To: freebsd-net@FreeBSD.ORG Subject: Re: natd & identd cooperation? (and identd + jails) Message-ID: <20001020164548.A27552@klaki.net> References: <20001018184017.A1218@klaki.net> <20001019110110.C98924@sunbay.com> <20001019120511.A4555@sunbay.com> <20001020140347.A25546@klaki.net> <20001020172003.A50854@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <20001020172003.A50854@sunbay.com>; from Ruslan Ermilov on Fri, Oct 20, 2000 at 05:20:03PM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am mostly interested in a real IDENT support for libalias(3), that > would allow it to redirect incoming IDENT queries to the original host. > Is it in any way possible with your patch? Yes, but it is a user-space solution, which requires the internal ident to accept forwarded ident queries. AFAIK there is no standard way to represent such queries, but for my local setup I just fixed oidentd so it understood syntax like: "ip : port , port" instead of just the ambiguous "port , port". I actually prefer my solution to the one you propose, since it lets me configure on a per-IP or per-connection basis whether I forward the ident query or not. I like not being forced to trust all internal ident daemons. In a PC environment (or a jailed environment where users are given root in their respective jails) forwarding the ident query doesn't really make sense. -- Bjarni R. Einarsson PGP: 02764305, B7A3AB89 bre@netverjar.is -><- http://bre.klaki.net/ Netverjar gegn ruslpósti: http://www.netverjar.is/baratta/ruslpostur/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 20 10:29:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 3F2D837B4E5 for ; Fri, 20 Oct 2000 10:29:24 -0700 (PDT) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.0/8.11.0) with ESMTP id e9KHTNm80873 for ; Fri, 20 Oct 2000 18:29:23 +0100 (BST) X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Fri, 20 Oct 2000 18:29:23 +0100 (BST) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: freebsd-net@FreeBSD.ORG Subject: device sr0 - RISCom/N2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I would like to connect a freeBSD box on a Cisco router. To do it I did rebuilt a kernel with that: pseudo-device sppp device sr0 at pci? port 0x300 irq iomem 0xd0000 Then, when I made dmseg 'sr0', it tells me that: sr0 XXX: driver didn't set ifq_maxlen sr1 XXX: driver didn't set ifq_maxlen And I am blocked here. If someone has any idea, he is more than welcome. Jean-Christophe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 20 14:19:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from pizza.monkeybrains.net (pizza.monkeybrains.net [209.21.40.4]) by hub.freebsd.org (Postfix) with ESMTP id EBAF037B4C5 for ; Fri, 20 Oct 2000 14:19:47 -0700 (PDT) Received: from localhost (rudy@localhost) by pizza.monkeybrains.net (8.11.1/8.11.0) with ESMTP id e9KLIuo73045 for ; Fri, 20 Oct 2000 14:18:56 -0700 (PDT) (envelope-from rudy@monkeybrains.net) Date: Fri, 20 Oct 2000 14:18:56 -0700 (PDT) From: Rudy To: freebsd-net@freebsd.org Subject: arp and bridging Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here is my setup: lala <---> bridge <---> pizza Problem: 'pizza' cannot always access lala. One ip occationally moves from one MAC to another, there are three things which make this 'wierd': 1) If I scan my whole network (namp -sP '209.21.40.*') to prime the current ARP entries, and then do a arp -a, that '00:a0:c9:f2:fc:63' MAC doesn't show up. 2) Another wierd thing: half the MAC address is the same 00:a0:c9:f2:fc:63 (phantom MAC) 00:d0:b7:1f:fc:63 (actual lala address) 3) And finally, in /var/log/messages lala and bridge, no arp complaints show up. Only pizza gets confused. 4) The MAC move only lasts a few minutes and occurs about once a day. Right now, I am doing a make world on the bridge box to bring it up to date. pizza: FreeBSD 4.1.1-STABLE #0: Mon Oct 16 21:19:46 PDT 2000 lala: FreeBSD 3.5-STABLE #0: Wed Jul 5 16:57:58 PDT 2000 bridge: 4.1-STABLE #0: Thu Sep 7 16:19:48 PDT 2000 bridge# sysctl -a | grep bridge net.link.ether.bridge_cfg: fxp0:1,xl0:1,xl1:1, net.link.ether.bridge: 1 net.link.ether.bridge_ipfw: 0 net.link.ether.bridge_ipfw_drop: 0 net.link.ether.bridge_ipfw_collisions: 0 /var/log/messages: Oct 13 02:57:07 pizza /kernel: arp: 209.21.40.3 moved from 00:d0:b7:1f:fc:63 to 00:a0:c9:f2:fc:63 on fxp0 Oct 13 03:11:39 pizza /kernel: arp: 209.21.40.3 moved from 00:a0:c9:f2:fc:63 to 00:d0:b7:1f:fc:63 on fxp0 Oct 13 06:27:06 pizza /kernel: arp: 209.21.40.3 moved from 00:d0:b7:1f:fc:63 to 00:a0:c9:f2:fc:63 on fxp0 Oct 13 06:34:25 pizza /kernel: arp: 209.21.40.3 moved from 00:a0:c9:f2:fc:63 to 00:d0:b7:1f:fc:63 on fxp0 Oct 17 01:11:37 pizza /kernel: arp: 209.21.40.3 moved from 00:d0:b7:1f:fc:63 to 00:a0:c9:f2:fc:63 on fxp0 Oct 17 01:17:18 pizza /kernel: arp: 209.21.40.3 moved from 00:a0:c9:f2:fc:63 to 00:d0:b7:1f:fc:63 on fxp0 Oct 19 04:27:36 pizza /kernel: arp: 209.21.40.3 moved from 00:d0:b7:1f:fc:63 to 00:a0:c9:f2:fc:63 on fxp0 Oct 19 04:45:54 pizza /kernel: arp: 209.21.40.3 moved from 00:a0:c9:f2:fc:63 to 00:d0:b7:1f:fc:63 on fxp0 Oct 20 06:42:28 pizza /kernel: arp: 209.21.40.3 moved from 00:d0:b7:1f:fc:63 to 00:a0:c9:f2:fc:63 on fxp0 Oct 20 06:57:00 pizza /kernel: arp: 209.21.40.3 moved from 00:a0:c9:f2:fc:63 to 00:d0:b7:1f:fc:63 on fxp0 Oct 20 10:42:26 pizza /kernel: arp: 209.21.40.3 moved from 00:d0:b7:1f:fc:63 to 00:a0:c9:f2:fc:63 on fxp0 Oct 20 10:49:27 pizza /kernel: arp: 209.21.40.3 moved from 00:a0:c9:f2:fc:63 to 00:d0:b7:1f:fc:63 on fxp0 This is my first post to the freebsd-net list: hi! Rudy --------------------------------------------------- Join my ISP: http://www.monkeybrains.net/ --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Oct 20 16:10:49 2000 Delivered-To: freebsd-net@freebsd.org Received: from pizza.monkeybrains.net (pizza.monkeybrains.net [209.21.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 0CCDB37B479 for ; Fri, 20 Oct 2000 16:10:47 -0700 (PDT) Received: from localhost (rudy@localhost) by pizza.monkeybrains.net (8.11.1/8.11.0) with ESMTP id e9KN9q175133; Fri, 20 Oct 2000 16:09:52 -0700 (PDT) (envelope-from rudy@monkeybrains.net) Date: Fri, 20 Oct 2000 16:09:52 -0700 (PDT) From: Rudy To: Udo Erdelhoff Cc: freebsd-net@freebsd.org Subject: Re: arp and bridging In-Reply-To: <20001021001110.B2415@nathan.ruhr.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 21 Oct 2000, Udo Erdelhoff wrote: _Hi, _what's the output of "ifconfig -a" on bridge and pizza? Ugly. Now I'm starting to think that the bridge is mixing and matching MAC address. Hmmm.... maybe some code has a little bug. Also, I now remember reading about in the freebsd-net archives, but I can't find it. 00:a0:c9:f2:fc:63 PHANTOOM 00:d0:b7:1f:fc:63 Real pizza> ifconfig -a fxp0: flags=8843 mtu 1500 inet 209.21.40.4 netmask 0xffffff00 broadcast 209.21.40.255 inet 209.21.40.128 netmask 0xffffff00 broadcast 209.21.40.255 ether 00:d0:b7:a6:34:16 media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP bridge# ifconfig -a fxp0: flags=8943 mtu 1500 inet 209.21.40.2 netmask 0xffffff00 broadcast 209.21.40.255 ether 00:a0:c9:f2:72:84 media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP xl0: flags=8943 mtu 1500 ether 00:50:04:d9:b3:a2 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX xl1: flags=8943 mtu 1500 ether 00:01:02:3d:63:9a media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 lala> ifconfig -a fxp0: flags=8843 mtu 1500 inet 209.21.40.3 netmask 0xffffff00 broadcast 209.21.40.255 inet 209.21.40.15 netmask 0xffffff00 broadcast 209.21.40.255 ether 00:d0:b7:1f:fc:63 Rudy --------------------------------------------------- Join my ISP: http://www.monkeybrains.net/ --------------------------------------------------- _the phantom MAC address is intresting. From the Ethernet Codes page at _http://www.cavebear.com/CaveBear/Ethernet/vendor.html _00A0C9 Intel (PRO100B and PRO100+) [used on Cisco PIX firewall among \ _ others] _ _And what are the IP addresses of the boxes? _ _/s/Udo _ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 9:36:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 54B3C37B479; Sat, 21 Oct 2000 09:36:51 -0700 (PDT) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.0+3.3W/3.7W-light) with UUCP id e9LGamO16745; Sun, 22 Oct 2000 01:36:48 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:Qavoy9orEhva/kemSlXhMOy3xwxTkZxpFz6GRl3goCnURK0kQPAQidNClF18BIec@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.1/8.11.1/chaos) with ESMTP/inet6 id e9LGZw904856; Sun, 22 Oct 2000 01:35:58 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 22 Oct 2000 01:35:57 +0900 (JST) Message-Id: <20001022.013557.74746725.ume@mahoroba.org> To: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: new rc.network6 and rc.firewall6 From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I wish to update rc.network6 and introduce rc.firewall6. - ipv6_prefix_* and ipv6_ifconfig_* work for end node - rtsol should be work to only one interface - new variable ipv6_defaultrouter is added - ipv6_firewall_enable, ipv6_firewall_type, ipv6_firewall_script, ipv6_firewall_logging are added to introduce rc.firewall6. I put it on: http://www.imasy.or.jp/~ume/ipv6/FreeBSD/rc.network6.diff http://www.imasy.or.jp/~ume/ipv6/FreeBSD/rc.firewall6 Please review it. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 11: 6: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 9784537B4CF; Sat, 21 Oct 2000 11:06:01 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9LI5bA81970; Sat, 21 Oct 2000 11:05:38 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Hajimu UMEMOTO Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 In-Reply-To: Message from Hajimu UMEMOTO of "Sun, 22 Oct 2000 01:35:57 +0900." <20001022.013557.74746725.ume@mahoroba.org> Date: Sat, 21 Oct 2000 11:05:37 -0700 Message-ID: <81966.972151537@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I wish to update rc.network6 and introduce rc.firewall6. Hmmmm. I must confess that I see /etc as getting rather cluttered these days. Is there no way to perhaps collapse some of the most related functionality into single files and start passing arguments or something? Just a comment.. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 11:10:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 180BA37B4C5 for ; Sat, 21 Oct 2000 11:10:50 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 058245D45 for ; Sat, 21 Oct 2000 20:10:49 +0200 (CEST) Date: Sat, 21 Oct 2000 20:10:49 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: freebsd-net@freebsd.org Subject: Using punch_fw from natd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have two firewalls, protecting our two office networks. The firewalls are simply ipfw rules, without using NAT (and natd). The only remaining "big hole" I have is, that I need to open TCP ports above 1024 for incoming active FTP requests. I'd like to close this remaining hole and noticed the punch_fw option to natd, which does what I want - the problem is, that it is built into natd and works only on packets that are aliased by natd. But I don't want to do network address translation, I just need a daemon that will open incoming TCP ports for active FTP connections. Does anybody have a solution? Maybe a way to convince natd to do the port-punching without aliasing packets? Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 11:32: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from pizza.monkeybrains.net (pizza.monkeybrains.net [209.21.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 4B67337B479 for ; Sat, 21 Oct 2000 11:32:06 -0700 (PDT) Received: from localhost (rudy@localhost) by pizza.monkeybrains.net (8.11.1/8.11.0) with ESMTP id e9LIU4Z94829; Sat, 21 Oct 2000 11:30:04 -0700 (PDT) (envelope-from rudy@monkeybrains.net) Date: Sat, 21 Oct 2000 11:30:04 -0700 (PDT) From: Rudy To: Blaz Zupan Cc: freebsd-net@FreeBSD.ORG Subject: Re: Using punch_fw from natd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You can reduce the numbe of open ports --- ftpd does not use 1024-65535B Here is the rule I use: allow tcp from any to any 49152-65535 keep-state in recv fxp0 setup Users do not have shell accounts on that box, so I am not worried about leaving a bunch of high numbered ports open. (Is this a mistake?) Rudy --------------------------------------------------- Join my ISP: http://www.monkeybrains.net/ --------------------------------------------------- On Sat, 21 Oct 2000, Blaz Zupan wrote: _I have two firewalls, protecting our two office networks. The firewalls are _simply ipfw rules, without using NAT (and natd). The only remaining "big hole" _I have is, that I need to open TCP ports above 1024 for incoming active FTP _requests. I'd like to close this remaining hole and noticed the punch_fw _option to natd, which does what I want - the problem is, that it is built into _natd and works only on packets that are aliased by natd. But I don't want to _do network address translation, I just need a daemon that will open incoming _TCP ports for active FTP connections. Does anybody have a solution? Maybe a _way to convince natd to do the port-punching without aliasing packets? _ _Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia _E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 _ _ _ _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 Sat Oct 21 12: 4:50 2000 Delivered-To: freebsd-net@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 8F1F437B479 for ; Sat, 21 Oct 2000 12:04:48 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 876525D45; Sat, 21 Oct 2000 21:04:44 +0200 (CEST) Date: Sat, 21 Oct 2000 21:04:44 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Rudy Cc: freebsd-net@FreeBSD.ORG Subject: Re: Using punch_fw from natd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You can reduce the numbe of open ports --- ftpd does not use 1024-65535B You can't predict what ports the ftp server uses - my users could be connecting to any ftp server out there which could select any port above 1024. > Users do not have shell accounts on that box, so I am not worried about > leaving a bunch of high numbered ports open. (Is this a mistake?) I'm not protecting just one host, I'm protecting a whole network, with possibly services running out there - for example X uses ports around 6000. I can of course block that, but who guarantees that there isn't some other software listening on some other port on a users Windoze box? Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 12: 5:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 40B1637B4CF; Sat, 21 Oct 2000 12:05:09 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.11.0) id e9LJ2Mf45829; Sat, 21 Oct 2000 21:02:22 +0200 (CEST) (envelope-from asmodai) Date: Sat, 21 Oct 2000 21:02:22 +0200 From: Jeroen Ruigrok van der Werven To: Jordan Hubbard Cc: Hajimu UMEMOTO , freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 Message-ID: <20001021210222.E40989@lucifer.bart.nl> References: <81966.972151537@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <81966.972151537@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Sat, Oct 21, 2000 at 11:05:37AM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20001021 20:10], Jordan Hubbard (jkh@winston.osd.bsdi.com) wrote: >> I wish to update rc.network6 and introduce rc.firewall6. > >Hmmmm. I must confess that I see /etc as getting rather cluttered >these days. Is there no way to perhaps collapse some of the most >related functionality into single files and start passing arguments >or something? Just a comment.. The IPv6 systems are so much different in set-up than the IPv4 systems. Collapsing of the functions is not really doable. However, Umemoto-san and me will discuss this, since we [he mostly] have been working on this for the last few months. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I love to doubt as well as know... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 12:10:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from pizza.monkeybrains.net (pizza.monkeybrains.net [209.21.40.4]) by hub.freebsd.org (Postfix) with ESMTP id D776537B479 for ; Sat, 21 Oct 2000 12:10:23 -0700 (PDT) Received: from localhost (rudy@localhost) by pizza.monkeybrains.net (8.11.1/8.11.0) with ESMTP id e9LJ9Sk95863 for ; Sat, 21 Oct 2000 12:09:28 -0700 (PDT) (envelope-from rudy@monkeybrains.net) Date: Sat, 21 Oct 2000 12:09:28 -0700 (PDT) From: Rudy To: freebsd-net@FreeBSD.org Subject: '/kernel: Too many dynamic rules, sorry' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got '/kernel: Too many dynamic rules, sorry' for the first time. To got rid of keep-state on my port 80 and the problem went away. [1] Are other people using keep-state webservers? What are their sysctl values? I noticed the default hash size is '256'. The /etc/default/make.conf recommends a prime number for the 'top' hash table: # top(1) uses a hash table for the user names. The size of this hash # can be tuned to match the number of local users. The table size should # be a prime number approximately twice as large as the number of lines in # /etc/passwd. Also there are various articles recommending prime numbers for hashes on the web: http://pauillac.inria.fr/caml/man-caml/node15.8.html [2] Does primeness matter with net.inet.ip.fw.dyn_buckets? Wondering what to set the sysctl values to, I searched some more and found luigi's advice: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=285503+0+archive/2000/freebsd-net/20000220.freebsd-net I am running a server and saw this comment: 'Note, this behaviour is probably appropriate for a workstation.' [3] Should I not use keep-state on servers? [4] A nice feature would be the ability to extend timeouts within the ipfw ruleset for specific ports. For instance, I'd like to change the timeout for my ssh connections from 5 minutes to 60 minutes. Something like: allow tcp from any to any 22 keep-state ack-lifetime 3600 in recv fxp0 setup Rudy --------------------------------------------------- Join my ISP: http://www.monkeybrains.net/ --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 14:49:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 7909D37B479; Sat, 21 Oct 2000 14:49:51 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA59877; Sat, 21 Oct 2000 14:49:26 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39F20F65.E6B84146@gorean.org> Date: Sat, 21 Oct 2000 14:49:25 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-101 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok van der Werven Cc: Jordan Hubbard , Hajimu UMEMOTO , freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 References: <81966.972151537@winston.osd.bsdi.com> <20001021210222.E40989@lucifer.bart.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok van der Werven wrote: > > -On [20001021 20:10], Jordan Hubbard (jkh@winston.osd.bsdi.com) wrote: > >> I wish to update rc.network6 and introduce rc.firewall6. > > > >Hmmmm. I must confess that I see /etc as getting rather cluttered > >these days. Is there no way to perhaps collapse some of the most > >related functionality into single files and start passing arguments > >or something? Just a comment.. > > The IPv6 systems are so much different in set-up than the IPv4 systems. > Collapsing of the functions is not really doable. > > However, Umemoto-san and me will discuss this, since we [he mostly] have > been working on this for the last few months. An /etc/ipv6 directory might be a useful alternative as well. In my mind 3 files is the point at which a directory starts being useful, and adding rc.firewall6 would make it 4. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Oct 21 18:39: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 0E19137B479; Sat, 21 Oct 2000 18:39:00 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9M1cYA82994; Sat, 21 Oct 2000 18:38:34 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Jeroen Ruigrok van der Werven Cc: Hajimu UMEMOTO , freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 In-Reply-To: Message from Jeroen Ruigrok van der Werven of "Sat, 21 Oct 2000 21:02:22 +0200." <20001021210222.E40989@lucifer.bart.nl> Date: Sat, 21 Oct 2000 18:38:33 -0700 Message-ID: <82990.972178713@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > However, Umemoto-san and me will discuss this, since we [he mostly] have > been working on this for the last few months. Sounds good to me. My comments were, just to make it clear again, just food for thought and not out-and-out objections. If even 47 more files in /etc is what it takes to get IPv6 fully supported, then so be it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message