From owner-freebsd-net Sun Mar 28 1:58: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by hub.freebsd.org (Postfix) with ESMTP id 0E81D14C0A for ; Sun, 28 Mar 1999 01:58:03 -0800 (PST) (envelope-from heinig@hdz-ima.rwth-aachen.de) Received: from HDZ-IMA.RWTH-Aachen.de (majestix.hdz-ima.RWTH-Aachen.DE) by mail.rwth-aachen.de (PMDF V5.1-12 #30440) with ESMTP id <01J9D0G6X6VO0003BU@mail.rwth-aachen.de> for net@FreeBSD.ORG; Sun, 28 Mar 1999 10:54:33 +0100 Received: from MAJESTIX/MAIL by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20); Sun, 28 Mar 1999 10:56:00 +0000 Received: from MAIL by MAJESTIX (Mercury 1.20); Sun, 28 Mar 1999 10:55:35 +0000 Received: from hdz-ima.rwth-aachen.de by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20) with ESMTP; Sun, 28 Mar 1999 10:55:32 +0000 Date: Sun, 28 Mar 1999 11:53:44 +0200 From: Gerald Heinig Subject: Re: OSI layering Query.. Please Help ME To: justin@apple.com Cc: net@FreeBSD.ORG Message-id: <36FDFC28.A4A971E9@hdz-ima.rwth-aachen.de> Organization: Informatik im Maschinenbau / Hochschuldidaktisches Zentrum, RWTH Aachen MIME-version: 1.0 X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <199903280454.UAA00698@walker3.apple.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin C. Walker" wrote: > find detailed discussions of the model, and its applicabiliity to IP, > in many places. See, e.g., Stallings, "Handbook of Computer > Communications Standards, V. 1, The Open Systems Interconnect model > ..." (MacMillan/Stallings); Stevens' "TCP/IP Illustrated, V1" > (Addison Wesley), discusses layering as it applies specifically to > TCP and IP (i.e., up through what OSI calls the transport layer). > > > And what exactly are PDU? > Protocol Data Units - this is OSI-speak for "packets", > although it allows you to talk about packets at the various protocol > layers (e.g., an IP packet as distinct from a TCP packet or an > ethernet packet). > > > What exactly is SAP?? > Service Access Point - it's a protocol addressing term. > E.g., in IP terms, an SAP at the network layer would be a port (and > is known as an NSAP). You'd need to delve more deeply into the OSI > model to appreciate the subtlety of the concept :-}. Hmmm. Yet another interpretation :-(. Did you get this out of the books you mentioned above? The books I took my definitions out of are "Data communications, computer networks and OSI" by Fred Halsall and "Internetworking with TCP/IP volume 1" by Douglas Comer. The Halsall book is very abstract and hardly mentions TCP/IP, but the Comer book does. It says, for example: "Level 3: A reference to transport level communication derived from the ISO 7-layer reference model. For TCP/IP internets, level 3 refers to IP and the IP datagram format. Thus, a level 3 address is an IP address." Since level 3 is defined as the network layer, the point at which you access this layer is the logical network interface and you use a network service access point address to do this. Or so the logic goes. The Halsall book is very hazy on this and seems to contradict itself at several points. Worse, nobody seems to be able to agree on this... :-( Gerald -- "Would you like to buy an encyclopaedia to help your child get to college?" "He doesn't need it. He takes the bus!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 2:34:23 1999 Delivered-To: freebsd-net@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 0200C14DF3 for ; Sun, 28 Mar 1999 02:34:19 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id MAA18173; Sun, 28 Mar 1999 12:33:54 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id MAA01882; Sun, 28 Mar 1999 12:15:01 +0200 (CEST) (envelope-from andreas) Date: Sun, 28 Mar 1999 12:15:01 +0200 From: Andreas Klemm To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: mbuf clusters and socket send buffers (was Re: 3.1-STABLE dies on 40+ connects) Message-ID: <19990328121501.A1353@titan.klemm.gtn.com> References: <199903260054.QAA22060@biggusdiskus.flyingfox.com> <199903261504.KAA23189@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903261504.KAA23189@khavrinen.lcs.mit.edu>; from Garrett Wollman on Fri, Mar 26, 1999 at 10:04:22AM -0500 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 26, 1999 at 10:04:22AM -0500, Garrett Wollman wrote: > < said: > > > A thought related to this discussion: does it make sense to allow the > > send buffers to be larger than the peer's advertised window size? > > In other words, why "preposition" those bytes in the kernel before > > the peer has indicated a willingness to accept them? > > No, it doesn't. Just ask Van Jacobson. > > Unfortunately, that doesn't get OUR TCP stack rewritten any faster. What do you think about the work of the PSC ? http://www.psc.edu/networking/auto.html This has been brought up in this thread... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 4:12:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (Postfix) with ESMTP id 57A0115272 for ; Sun, 28 Mar 1999 04:12:31 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id OAA21512; Sun, 28 Mar 1999 14:19:32 +0200 (CEST) Message-Id: <199903281219.OAA21512@rt2.synx.com> Date: Sun, 28 Mar 1999 14:11:10 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: FreeBSD as a router To: cmetz@inner.net Cc: mike@sentex.net, freebsd-net@FreeBSD.ORG In-Reply-To: <199903272156.VAA08726@inner.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27 Mar, Craig Metz wrote: >..... > If the original poster was thinking about using FreeBSD-based commodity PCs > for small-to-midrange routers in an environment where cost/flexibility is > important and it doesn't have to deliver every last bit of line capacity, then > it might be a great choice. Research networks (e.g., vBNS and CAIRN) are ie: http://www.iprg.nokia.com/products/ip400/ The 'IP440' is a PC-based, FreeBSD operated router. Although, they don't advertise it but in their press releases. (Thanks to Malartre for this link : http://www.lmi.fr/c12565ef002d29ae/996ef68a9fd10db3c125669e00311b6a/129d72353914ed45c125669c0028b1c6?OpenDocument (Sorry, once again in French). Anyway, the IP440 casing is horrible. This leads to another question : I'm looking for a box designer, owning Gerbers, able to build a 1U, 19inch rackable PC-based system. Hints ? >.... > time), but that might not be really necessary, and the difference in cost might > really be worth it. Hum... not for Nokia... prices start at 15 K$ for the IP440 !! RN. IaM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 4:29:54 1999 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 1F5E614D6D; Sun, 28 Mar 1999 04:29:53 -0800 (PST) From: "Jonathan M. Bresler" To: remy@synx.com Cc: cmetz@inner.net, mike@sentex.net, freebsd-net@FreeBSD.ORG In-reply-to: <199903281219.OAA21512@rt2.synx.com> (message from Remy Nonnenmacher on Sun, 28 Mar 1999 14:11:10 +0200 (CEST)) Subject: Re: FreeBSD as a router References: <199903281219.OAA21512@rt2.synx.com> Message-Id: <19990328122953.1F5E614D6D@hub.freebsd.org> Date: Sun, 28 Mar 1999 04:29:53 -0800 (PST) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Sun, 28 Mar 1999 14:11:10 +0200 (CEST) > From: Remy Nonnenmacher > > ie: http://www.iprg.nokia.com/products/ip400/ > > The 'IP440' is a PC-based, FreeBSD operated router. Although, they > don't advertise it but in their press releases. (Thanks to Malartre for > this link : > http://www.lmi.fr/c12565ef002d29ae/996ef68a9fd10db3c125669e00311b6a/129d72353914ed45c125669c0028b1c6?OpenDocument > (Sorry, once again in French). > > Anyway, the IP440 casing is horrible. This leads to another question : > I'm looking for a box designer, owning Gerbers, able to build a 1U, > 19inch rackable PC-based system. Hints ? not just the IP440 but also teh IP210, IP330 and IP650. base line code is freebsd-2.2.6 with their own routing and TCP/IP code. the 210 uses the same case as the 440. the 330 is a 1U box. the 650 is a 3U case with compact pci, hot swap cards. > >.... > > time), but that might not be really necessary, and the difference in cost might > > really be worth it. > > Hum... not for Nokia... prices start at 15 K$ for the IP440 !! talk to you Nokia rep.....hte 330 is much cheaper. we use Nokias everywher, and lots of them. very highly recommended. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 7:18:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by hub.freebsd.org (Postfix) with ESMTP id E24FE152F7 for ; Sun, 28 Mar 1999 07:18:44 -0800 (PST) (envelope-from heinig@hdz-ima.rwth-aachen.de) Received: from HDZ-IMA.RWTH-Aachen.de (majestix.hdz-ima.RWTH-Aachen.DE) by mail.rwth-aachen.de (PMDF V5.1-12 #30440) with ESMTP id <01J9DBRXHFPI00046N@mail.rwth-aachen.de> for net@FreeBSD.ORG; Sun, 28 Mar 1999 16:19:21 +0100 Received: from MAJESTIX/MAIL by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20); Sun, 28 Mar 1999 16:20:49 +0000 Received: from MAIL by MAJESTIX (Mercury 1.20); Sun, 28 Mar 1999 16:20:31 +0000 Received: from hdz-ima.rwth-aachen.de by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20) with ESMTP; Sun, 28 Mar 1999 16:20:26 +0000 Date: Sun, 28 Mar 1999 17:18:37 +0200 From: Gerald Heinig Subject: Re: OSI layering Query.. Correction :-( To: danny@alpha.net.au, net@FreeBSD.ORG Message-id: <36FE484D.5F569F9A@hdz-ima.rwth-aachen.de> Organization: Informatik im Maschinenbau / Hochschuldidaktisches Zentrum, RWTH Aachen MIME-version: 1.0 X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <199903262358.JAA27392@sydney.alpha.net.au> <36FD9D67.4BFE39D@hdz-ima.rwth-aachen.de> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerald Heinig wrote: > > > > > And what exactly are PDU? > > Protocol Data Units. The information packages/packets that get sent > up/down the protocol stacks during protocol operation/data > transmission/reception. For example, a TPDU (transport protocol data > unit) contains the TSAP address (transport service access point address > - corresponds loosely to the "port number" in IP) and the "payload" ie. > data you're trying to transmit. This gets sent down (if you're > transmitting) to the NSAP (network service access point - equivalent to > a network interface in IP) which adds its NSAP address (which > corresponds to the IP address in IP). This then gets sent down to the > link layer (layer 2) to the LSAP (link layer service access point, ie. > the network card) which adds its LSAP address (ie. MAC/hardware/ethernet > address) plus header/trailer/FCS (frame check sequence) and sends the > caboodle off onto the wire. Hi Danny, Sorry, the above is wrong, I just checked. T/N/LSAPs are just addresses, NOT interfaces, logical or physical. An NSAP would correspond to an IP address, an LSAP to a hardware address. A PDU is usually used to describe the data that two machines exchange at the same layer. For example, saying machine A sends an IP packet to machine B is the same as saying machine A sends a network PDU to machine B. Note this is a rather abstract view of things. You can also think of PDUs as the data that passes up and down the protocol stacks during transmission/reception. As the PDU passes further down the stack, each layer adds its SAP to it. So, a TPDU (transport PDU) has in its packet the payload (data you're trying to send) and the TSAP. The next layer down (network layer) adds its NSAP, the next layer its LSAP until the physical layer adds the FCS and sends the message off onto the wire. > > > > > What exactly is SAP?? > > Service Access Point. The place where you can access a service. A Correct. > telephone socket is the SAP for a connection-oriented voice data Wrong. Forget that. > transfer service. IP mail exchange has an (IP) transport service access > point address of 25 ie.it uses IP port 25 for mail exchange. Your > machine's network interface would be the NSAP, the interface's IP > address would correspond to its NSAP address. Note: *CORRESPOND*!!! Again, wrong. The machine's IP address would correspond to its NSAP. > There is such a thing as an NSAP address and it is *NOT* the same as an > IP address!!! we're talking analogies here! > > > > I am really confused help me. Looks like I was as well. :-) :-) It seems to be somewhat awkward to map OSI terminology directly to IP. Some books say OSI layers 3 *and* 4 are IP layer 3, some disagree. Sorry about any confusion I caused: I should have given the book another good read *before* posting, not after. :-( Gerald -- "Would you like to buy an encyclopaedia to help your child get to college?" "He doesn't need it. He takes the bus!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 8: 4:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (Postfix) with ESMTP id 18BE01521A; Sun, 28 Mar 1999 08:04:36 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id KAA02464; Sun, 28 Mar 1999 10:03:28 -0600 (CST) (envelope-from joelh) To: Greg Lehey Cc: Andrzej Bialecki , Jesse , "Daniel C. Sobral" , freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Followups-to: freebsd-hackers@freebsd.org Subject: Re: Debug kernel by default? (was: Taking panic dumps (was: 3.1-STABLE dies on 40+ connects (resolved))) References: <19990327174738.B425@lemis.com> <19990328114410.U53452@lemis.com> From: Joel Ray Holveck Date: 28 Mar 1999 10:03:28 -0600 In-Reply-To: Greg Lehey's message of "Sun, 28 Mar 1999 11:44:10 +0930" Message-ID: <86677l38kv.fsf@detlev.UUCP> Lines: 23 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Followups set to -hackers, this isn't -net material. > In that connection, any comments about changing the default way of > building a kernel to create a debug kernel and a stripped copy, and > install the stripped copy? It would require about 10 MB more storage > and a little more time to build the kernel, but since kgdb is useless > without the debug symbols, and disk space is cheap, it seems to me > that it would be worthwhile. I would personally lean a little closer to either making it configurable. This could be a flag in make.conf, or the new behaviour of config -g, or (least desirable) even an option in the kernel config file. Still, somehow or another, make it disablable; that's easy enough to do. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 12:38:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 534FA15730 for ; Sun, 28 Mar 1999 12:38:47 -0800 (PST) (envelope-from justin@walker3.apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.8.5/8.8.5) with ESMTP id MAA32904 for ; Sun, 28 Mar 1999 12:36:11 -0800 Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id for ; Sun, 28 Mar 1999 12:36:09 -0800 Received: from walker3.apple.com (walker3.apple.com [17.219.24.201]) by scv1.apple.com (8.9.3/8.9.3) with ESMTP id MAA06216 for ; Sun, 28 Mar 1999 12:36:07 -0800 Received: by walker3.apple.com (8.9.1/8.9.1) id MAA00636 for net@FreeBSD.ORG; Sun, 28 Mar 1999 12:36:11 -0800 (PST) Message-Id: <199903282036.MAA00636@walker3.apple.com> To: net@freebsd.org Subject: Re: OSI layering Query.. Please Help ME Date: Sun, 28 Mar 1999 12:36:09 -0800 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Gerald Heinig > Date: 1999-03-28 01:57:47 -0800 > To: justin@apple.com > Subject: Re: OSI layering Query.. Please Help ME > > "Justin C. Walker" wrote: > > > find detailed discussions of the model, and its applicabiliity to IP, > > in many places. See, e.g., Stallings, "Handbook of Computer > > Communications Standards, V. 1, The Open Systems Interconnect model > > ..." (MacMillan/Stallings); Stevens' "TCP/IP Illustrated, V1" > > (Addison Wesley), discusses layering as it applies specifically to > > TCP and IP (i.e., up through what OSI calls the transport layer). > > > > > And what exactly are PDU? > > Protocol Data Units - this is OSI-speak for "packets", > > although it allows you to talk about packets at the various protocol > > layers (e.g., an IP packet as distinct from a TCP packet or an > > ethernet packet). > > > > > What exactly is SAP?? > > Service Access Point - it's a protocol addressing term. > > E.g., in IP terms, an SAP at the network layer would be a port (and > > is known as an NSAP). You'd need to delve more deeply into the OSI > > model to appreciate the subtlety of the concept :-}. > > Hmmm. Yet another interpretation. Did you get this out of the books > you mentioned above? The books I took my definitions out of are "Data > communications, computer networks and OSI" by Fred Halsall and > "Internetworking with TCP/IP volume 1" by Douglas Comer. The Halsall > book is very abstract and hardly mentions TCP/IP, but the Comer book > does. It says, for example: > > "Level 3: A reference to transport level communication derived from the > ISO 7-layer reference model. For TCP/IP internets, level 3 refers to IP > and the IP datagram format. Thus, a level 3 address is an IP address." > > Since level 3 is defined as the network layer, the point at which you > access this layer is the logical network interface and you use a network > service access point address to do this. Or so the logic goes. Well, yes; what the I meant to say is that the IP address is an NSAP (Network SAP); the port is a TSAP. A bit of "fingers outrunning brain"... > The Halsall book is very hazy on this and seems to contradict itself at > several points. Worse, nobody seems to be able to agree on this... All of which indicates (to me, at least) that applying OSI terminology where it doesn't belong merely serves to confuse and cloud. The layering ideas from OSI (or SNA, ...) are a convenient framework, but the OSI terminology need not survive its protocols :-}. Regards, Justin Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 12:48:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 5278614CF7 for ; Sun, 28 Mar 1999 12:48:47 -0800 (PST) (envelope-from nagao@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id FAA13925 for ; Mon, 29 Mar 1999 05:48:27 +0900 (JST) Received: from localhost (yuzu.iij.ad.jp [192.168.4.215]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id FAA16779 for ; Mon, 29 Mar 1999 05:48:26 +0900 (JST) To: freebsd-net@freebsd.org Subject: dummynet -- limit num of packets per sec. X-Mailer: Mew version 1.94b15 on Emacs 20.3 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990329054823Z.nagao@iij.ad.jp> Date: Mon, 29 Mar 1999 05:48:23 +0900 (JST) From: NAGAO Tadaaki X-Dispatcher: imput version 990323(IM111) Lines: 19 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I added some lines of codes to my local copy of dummynet codes so that the number of packets per second could be limited as well as a bandwidth could now, which I needed to measure the performance of some network software. Though I'm not sure whether it is useful for limiting the real network traffic, it might be useful for testing some network devices and softwares, and yes, it was really useful for me. :-) Is there some demand on such a thing? If so, I'll make the diff and/or send-pr on it. Anyone? -- NAGAO Tadaaki Applied Technology Division, Internet Initiative Japan Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 12:59:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id D9AAB14E89 for ; Sun, 28 Mar 1999 12:59:12 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA04424; Sun, 28 Mar 1999 20:37:21 +0200 From: Luigi Rizzo Message-Id: <199903281837.UAA04424@labinfo.iet.unipi.it> Subject: Re: dummynet -- limit num of packets per sec. To: nagao@iij.ad.jp (NAGAO Tadaaki) Date: Sun, 28 Mar 1999 20:37:21 +0200 (MET DST) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <19990329054823Z.nagao@iij.ad.jp> from "NAGAO Tadaaki" at Mar 29, 99 05:48:04 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 570 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello, > > I added some lines of codes to my local copy of dummynet codes > so that the number of packets per second could be limited as well as > a bandwidth could now, which I needed to measure the performance of > some network software. > > Though I'm not sure whether it is useful for limiting the real > network traffic, it might be useful for testing some network > devices and softwares, and yes, it was really useful for me. :-) > > Is there some demand on such a thing? > If so, I'll make the diff and/or send-pr on it. why not -- send me a diff. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 13:34:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 6867C14E8E; Sun, 28 Mar 1999 13:34:45 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id NAA72802; Sun, 28 Mar 1999 13:33:44 -0800 (PST) From: Archie Cobbs Message-Id: <199903282133.NAA72802@bubba.whistle.com> Subject: Re: Debug kernel by default? (was: Taking panic dumps (was: 3.1-STABLE dies on 40+ connects (resolved))) In-Reply-To: <19990328114410.U53452@lemis.com> from Greg Lehey at "Mar 28, 99 11:44:10 am" To: grog@lemis.com (Greg Lehey) Date: Sun, 28 Mar 1999 13:33:44 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey writes: > In that connection, any comments about changing the default way of > building a kernel to create a debug kernel and a stripped copy, and > install the stripped copy? It would require about 10 MB more storage > and a little more time to build the kernel, but since kgdb is useless > without the debug symbols, and disk space is cheap, it seems to me > that it would be worthwhile. Building debug kernels takes up a lot more space, which some people may not have. How about simply fixing 'config -g' to generate a Makefile that does the extra step of copying and stripping the kernel and installing the stripped version kernel.strip instead of kernel? Then we can modify the handbook et.al. to say "You should build a debug kernel with 'config -g' if at all possible..". All other steps remain the same. Eventually, when/if it's determined that 'config -g' should be the default, we can make it so easily. But that should be a separate step.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 14:57: 1 1999 Delivered-To: freebsd-net@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 2D8B814EA3; Sun, 28 Mar 1999 14:56:28 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Sun, 28 Mar 1999 23:54:28 +0100 Message-ID: From: paul@originative.co.uk To: archie@whistle.com, grog@lemis.com Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: Debug kernel by default? (was: Taking panic dumps (was: 3.1-S TABLE dies on 40+ connects (resolved))) Date: Sun, 28 Mar 1999 23:54:27 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Archie Cobbs [mailto:archie@whistle.com] > Sent: 28 March 1999 22:34 > To: grog@lemis.com > Cc: freebsd-net@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG > Subject: Re: Debug kernel by default? (was: Taking panic dumps (was: > 3.1-STABLE dies on 40+ connects (resolved))) > > > Greg Lehey writes: > > In that connection, any comments about changing the default way of > > building a kernel to create a debug kernel and a stripped copy, and > > install the stripped copy? It would require about 10 MB > more storage > > and a little more time to build the kernel, but since kgdb > is useless > > without the debug symbols, and disk space is cheap, it seems to me > > that it would be worthwhile. > > Building debug kernels takes up a lot more space, which some people > may not have. > > How about simply fixing 'config -g' to generate a Makefile that > does the extra step of copying and stripping the kernel and installing > the stripped version kernel.strip instead of kernel? > Unless I misunderstood Greg I think the intention is to always build a debug kernel without the user really realising that is happening so that when they have a panic they've got the infrastructure there to let the "support team" track down the problem. I think that's a good idea, switch the options around so that by default a debug kernel is built and provide an option to build a "production" kernel. I don't think a kernel built with -g is going to be significantly slower or bigger than a standard kernel once stripped and those after maximum performance should know how to go about getting it. The extra disk space for the build would be only problem but given the size of the code base these days most people who have source will have enough spare disk to build a debug kernel. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 15:39:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id D22FC15676 for ; Sun, 28 Mar 1999 15:37:58 -0800 (PST) (envelope-from nagao@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id IAA14415; Mon, 29 Mar 1999 08:37:38 +0900 (JST) Received: from localhost (yuzu.iij.ad.jp [192.168.4.215]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id IAA19203; Mon, 29 Mar 1999 08:37:37 +0900 (JST) To: luigi@labinfo.iet.unipi.it Cc: freebsd-net@FreeBSD.ORG Subject: Re: dummynet -- limit num of packets per sec. In-Reply-To: <199903281837.UAA04424@labinfo.iet.unipi.it> References: <19990329054823Z.nagao@iij.ad.jp> <199903281837.UAA04424@labinfo.iet.unipi.it> X-Mailer: Mew version 1.94b15 on Emacs 20.3 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_Mar_29_08:37:31_1999_595)--" Content-Transfer-Encoding: 7bit Message-Id: <19990329083734O.nagao@iij.ad.jp> Date: Mon, 29 Mar 1999 08:37:34 +0900 (JST) From: NAGAO Tadaaki X-Dispatcher: imput version 990323(IM111) Lines: 176 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----Next_Part(Mon_Mar_29_08:37:31_1999_595)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, In message <199903281837.UAA04424@labinfo.iet.unipi.it>, Luigi Rizzo wrote: > > I added some lines of codes to my local copy of dummynet codes > > so that the number of packets per second could be limited as well as > > a bandwidth could now, which I needed to measure the performance of > > some network software. > > > > Though I'm not sure whether it is useful for limiting the real > > network traffic, it might be useful for testing some network > > devices and softwares, and yes, it was really useful for me. :-) > > > > Is there some demand on such a thing? > > If so, I'll make the diff and/or send-pr on it. > > why not -- send me a diff. Thanks for replying. Here attached two diffs; one is for /usr/src/sys/netinet/ip_dummynet.[ch] and the other for /usr/src/sbin/ipfw/ipfw.c. Sorry, I didn't write a description for the dummynet manpage, but the usage is: ipfw pipe NNN config pps S where S is the allowed number of packets per second, and, of course, other parameters (bw, delay, queue and plr) can be given simultanously. -- NAGAO Tadaaki Applied Technology Division, Internet Initiative Japan Inc. ----Next_Part(Mon_Mar_29_08:37:31_1999_595)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="sys.diff" Index: sys/netinet/ip_dummynet.c =================================================================== RCS file: /usr/ncvs/src/sys/netinet/ip_dummynet.c,v retrieving revision 1.7.2.3 diff -u -r1.7.2.3 ip_dummynet.c --- ip_dummynet.c 1999/03/26 16:48:55 1.7.2.3 +++ ip_dummynet.c 1999/03/28 16:34:51 @@ -160,6 +160,15 @@ pipe->r_len_bytes -= len ; /* + * limit the number of packets per second (pps). + */ + if (pipe->pps) { + if (pipe->pps_counter < hz) + break; + pipe->pps_counter -= hz; + } + + /* * to add delay jitter, must act here. A lower value * (bounded to 0) means lower delay. */ @@ -258,6 +267,8 @@ s = splimp(); if (p->r.head != NULL || p->numbytes < p->bandwidth ) p->numbytes += p->bandwidth ; + if (p->pps && (p->r.head != NULL || p->pps_counter < hz )) + p->pps_counter += p->pps ; dn_move(p, 0); /* is it really 0 (also below) ? */ splx(s); } @@ -512,10 +523,10 @@ if (p->queue_size_bytes > 1024*1024) p->queue_size_bytes = 1024*1024 ; #if 0 - printf("ip_dn: config pipe %d %d bit/s %d ms %d bufs\n", + printf("ip_dn: config pipe %d %d bit/s %d ms %d bufs %d pps\n", p->pipe_nr, p->bandwidth * 8 * hz , - p->delay * 1000 / hz , p->queue_size); + p->delay * 1000 / hz , p->queue_size, p->pps); #endif for (a = NULL , b = all_pipes ; b && b->pipe_nr < p->pipe_nr ; a = b , b = b->next) ; @@ -527,6 +538,7 @@ b->queue_size = p->queue_size ; b->queue_size_bytes = p->queue_size_bytes ; b->plr = p->plr ; + b->pps = p->pps ; } else { int s ; x = malloc(sizeof(struct dn_pipe), M_IPFW, M_DONTWAIT) ; @@ -543,6 +555,7 @@ x->queue_size = p->queue_size ; x->queue_size_bytes = p->queue_size_bytes ; x->plr = p->plr ; + x->pps = p->pps ; s = splnet() ; x->next = b ; Index: sys/netinet/ip_dummynet.h =================================================================== RCS file: /usr/ncvs/src/sys/netinet/ip_dummynet.h,v retrieving revision 1.2.2.1 diff -u -r1.2.2.1 ip_dummynet.h --- ip_dummynet.h 1999/01/25 19:19:28 1.2.2.1 +++ ip_dummynet.h 1999/03/28 16:34:54 @@ -74,6 +74,7 @@ int queue_size_bytes ; int delay ; /* really, ticks */ int plr ; /* pkt loss rate (2^31-1 means 100%) */ + int pps; /* packets per sec */ struct dn_queue r; int r_len; /* elements in r_queue */ @@ -82,6 +83,7 @@ struct dn_queue p ; int ticks_from_last_insert; long numbytes; /* which can send or receive */ + long pps_counter; }; /* ----Next_Part(Mon_Mar_29_08:37:31_1999_595)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ipfw.diff" Index: sbin/ipfw/ipfw.c =================================================================== RCS file: /usr/ncvs/src/sbin/ipfw/ipfw.c,v retrieving revision 1.64.2.1 diff -u -r1.64.2.1 ipfw.c --- ipfw.c 1999/01/25 19:17:07 1.64.2.1 +++ ipfw.c 1999/03/28 16:35:05 @@ -461,6 +461,7 @@ char buf[30] ; char qs[30] ; char plr[30] ; + char pps[30] ; int l ; if (rulenum != 0 && rulenum != p->pipe_nr) @@ -485,9 +486,13 @@ sprintf(plr,"plr %f", 1.0*p->plr/(double)(0x7fffffff)); else plr[0]='\0'; + if (p->pps) + sprintf(pps, "%d pkt/s", p->pps); + else + pps[0] = '\0'; - printf("%05d: %s %4d ms %s %s -- %d pkts (%d B) %d drops\n", - p->pipe_nr, buf, p->delay, qs, plr, + printf("%05d: %s %s %4d ms %s %s -- %d pkts (%d B) %d drops\n", + p->pipe_nr, buf, pps, p->delay, qs, plr, p->r_len, p->r_len_bytes, p->r_drops); } free(data); @@ -977,6 +982,9 @@ pipe.queue_size_bytes = pipe.queue_size ; pipe.queue_size = 0 ; } + av+=2; ac-=2; + } else if (!strncmp(*av,"pps",strlen(*av)) ) { + pipe.pps = strtoul(av[1], NULL, 0); av+=2; ac-=2; } else show_usage("unrecognised option ``%s''", *av); ----Next_Part(Mon_Mar_29_08:37:31_1999_595)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 18: 6:10 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 77A071548B for ; Sun, 28 Mar 1999 18:06:05 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id TAA04774; Sun, 28 Mar 1999 19:05:44 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36FEDFF7.59509D60@softweyr.com> Date: Sun, 28 Mar 1999 19:05:43 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Thompson Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router References: <4.1.19990326233717.009c8210@mail.dnai.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Thompson wrote: > > This is probably a stupid question (not that it ever stopped > me before), but is a FreeBSD system capable of running as a > high-capacity Internet router? Define "high-capacity." If you mean routing 10 Fast Ethernet channels into an ATM OC-12, the answer is "not without a lot of custom hardware and software." If, on the other hand, you're talking about routing an internal network or two into a garden-variety single-point connection to the internet, say anything up to about T3/E3, sure. Too many internal network interfaces may tend to swamp the system with interrupts, but other than that, a FreeBSD router should work fine. > I would like to run a number > of FreeBSD servers running a web application behind a FreeBSD > system acting as a router/firewall. Any examples of web sites > doing this would be great. You could buy a nice network switch and use the FreeBSD machines for what they're REALLY good at - providing services. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Mar 28 22:15:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id 999871579A; Sun, 28 Mar 1999 22:15:14 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA46868; Mon, 29 Mar 1999 02:15:01 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 29 Mar 1999 02:15:00 -0400 (AST) From: The Hermit Hacker To: freebsd-multimedia@freebsd.org Cc: freebsd-net@freebsd.org Subject: Two questions relating to Video Conferencing ... 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... I have two questions that, to date, I haven't been able to find an answer to without having to deal with another operating system, which I don't find acceptable :( Or, rather, one question requires changing operating system, the other I'm not even sure if its possible... Scenario: I'm just about to install a VidConf network for a client, to be used from home and the office to do tele-commuting. All the 'clients' machines are going to be running WinNT, but their file server at the office is a FreeBSD box w/ Samba. Q1. is there anything I can run on the FreeBSD box to provide them an equivalent to an ILS server, as is available for NT machines? They are all going to be using NetMeeting as their clients, but I want them to be able to connect to the central server to find out who else is online... Q2. is there any way of setting up a "proxy server"? I'm running FreeBSD at home as my gateway and main development machine. I have an NT machine up and running so that I'm not totally lost when I go do the install, and would like to do VidConf'ng to a friend in a remote location. The problem is that I need to go through my gateway, which is running NATd...is there any way of doing this? Someone way of saying "if a connection comes in on port XXX, redirect it to port XXX on internal IP YYY? Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 2:39:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id E0AD115791 for ; Mon, 29 Mar 1999 02:39:12 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from cvzoom.net (lcl75.cvzoom.net [208.226.155.75]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id FAA10479 for ; Mon, 29 Mar 1999 05:25:07 -0500 (EST) Message-ID: <36FF11E2.4B661EED@cvzoom.net> Date: Mon, 29 Mar 1999 05:38:42 +0000 From: Donn Miller X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: net@freebsd.org Subject: FreeBSD equiv. of this Linux socket call... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm looking for the FreeBSD equivalent of this Linux socket call: dhcpSocket = socket(AF_PACKET,SOCK_PACKET,htons(ETH_P_ALL)); So far, I think "SOCK_PACKET" can be replaced by a call to /dev/bpf0. How should /dev/bpf be opened? Should it be by the regular libc open() command, which returns a file descriptor, that is later used to bind this file descriptor to a device interface? What is AF_PACKET; I don't think FreeBSD supports that either. Thanks, this is a tough one. Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 6:24:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 6EB2F14E92 for ; Mon, 29 Mar 1999 06:24:54 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id JAA12135; Mon, 29 Mar 1999 09:24:24 -0500 (EST) (envelope-from wollman) Date: Mon, 29 Mar 1999 09:24:24 -0500 (EST) From: Garrett Wollman Message-Id: <199903291424.JAA12135@khavrinen.lcs.mit.edu> To: Donn Miller Cc: net@FreeBSD.ORG Subject: FreeBSD equiv. of this Linux socket call... In-Reply-To: <36FF11E2.4B661EED@cvzoom.net> References: <36FF11E2.4B661EED@cvzoom.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > What is AF_PACKET; I don't > think FreeBSD supports that either. It is a vile kluge. Use libpcap(3) -- that works on both platforms. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 11:28:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 10E6C14BD5 for ; Mon, 29 Mar 1999 11:28:55 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA255083679; Mon, 29 Mar 1999 13:54:39 -0500 Date: Mon, 29 Mar 1999 13:54:39 -0500 (EST) From: Bill Fumerola To: The Hermit Hacker Cc: freebsd-net@FreeBSD.ORG Subject: Re: Two questions relating to Video Conferencing ... 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, 29 Mar 1999, The Hermit Hacker wrote: > Q2. is there any way of setting up a "proxy server"? I'm running > FreeBSD at home as my gateway and main development machine. I have an NT > machine up and running so that I'm not totally lost when I go do the > install, and would like to do VidConf'ng to a friend in a remote location. > The problem is that I need to go through my gateway, which is running > NATd...is there any way of doing this? Someone way of saying "if a > connection comes in on port XXX, redirect it to port XXX on internal IP > YYY? ports/*/{socket,netcat} + {x,}inetd are your friends. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 11:56:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from dnai.com (dnai.com [207.181.194.98]) by hub.freebsd.org (Postfix) with ESMTP id D631C14D84 for ; Mon, 29 Mar 1999 11:56:15 -0800 (PST) (envelope-from miket@dnai.com) Received: from einstein (dnai-207-181-255-56.dialup.dnai.com [207.181.255.56]) by dnai.com (8.8.8/8.8.8) with SMTP id LAA22515; Mon, 29 Mar 1999 11:54:38 -0800 (PST) Message-Id: <4.1.19990329115145.00a62ab0@mail.dnai.com> X-Sender: miket@mail.dnai.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 29 Mar 1999 11:53:50 -0800 To: Craig Metz , mike@sentex.net (Mike Tancsa) From: Mike Thompson Subject: Re: FreeBSD as a router Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <199903272156.VAA08726@inner.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 04:59 PM 3/27/99 -0500, Craig Metz wrote: > What really matters here is the application. > >If the original poster was thinking about using FreeBSD-based >commidity PCs for the core routers of a large ISP... Sorry, I should have defined high-capacity better. I would like to isolate a half-dozen FreeBSD servers running a custom distributed web application behind a router/firewall. This is to increase security for intra-machine communication. At our co-location facility we have a 100Mb ethernet tap to a Cisco switch/router combination isolating our systems on a VPN. My question is about whether FreeBSD can keep up as a router (with a few firewall rules) between two 100Mb ethernet networks on decent hardware such as 2 PCI NICs and a 450 MHz PII. From the responses it sounds like it can. I am interested in using FreeBSD as the router/firewall because it is easy to configure and I don't have to learn something new on top everything else I am doing. Thanks to everyone for their responses. Mike Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 12:15:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id C023E15005 for ; Mon, 29 Mar 1999 12:15:30 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA10735 for net@FreeBSD.ORG; Mon, 29 Mar 1999 22:15:09 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B116E87B6; Mon, 29 Mar 1999 21:47:14 +0200 (CEST) Date: Mon, 29 Mar 1999 21:47:14 +0200 From: Ollivier Robert To: net@FreeBSD.ORG Subject: Re: FreeBSD equiv. of this Linux socket call... Message-ID: <19990329214714.A42277@keltia.freenix.fr> Mail-Followup-To: net@FreeBSD.ORG References: <36FF11E2.4B661EED@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <36FF11E2.4B661EED@cvzoom.net>; from Donn Miller on Mon, Mar 29, 1999 at 05:38:42AM +0000 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Donn Miller: > this file descriptor to a device interface? What is AF_PACKET; I don't > think FreeBSD supports that either. And we won't. This is an Linux specific evil hack. They don't support bpf so they created a new way (again!) of grabbing packets. Speaking of bpf... NFR has a performance patch for bpf included in the distribution. Has anyone tried to merge our version and their own ? -rw-r----- 1 roberto staff 30444 Dec 9 23:12 bpf.c -rw-r----- 1 roberto staff 7476 Dec 9 23:12 bpf.h -rw-r----- 1 roberto staff 4367 Dec 9 23:12 bpfdesc.h -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 12:57:28 1999 Delivered-To: freebsd-net@freebsd.org Received: from inner.net (avarice.inner.net [199.33.248.2]) by hub.freebsd.org (Postfix) with ESMTP id B3C4F14D56 for ; Mon, 29 Mar 1999 12:57:19 -0800 (PST) (envelope-from cmetz@inner.net) Received: from inner.net (cmetz.cstone.net [205.197.102.217]) by inner.net (8.9.1/8.9.1) with ESMTP id UAA10838; Mon, 29 Mar 1999 20:51:34 GMT Message-Id: <199903292051.UAA10838@inner.net> To: Mike Thompson Cc: mike@sentex.net (Mike Tancsa), freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router In-reply-to: Your message of "Mon, 29 Mar 1999 11:53:50 PST." <4.1.19990329115145.00a62ab0@mail.dnai.com> X-Copyright: Copyright 1999, Craig Metz, All Rights Reserved. X-Reposting: With explicit permission only Date: Mon, 29 Mar 1999 15:55:46 -0500 From: Craig Metz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <4.1.19990329115145.00a62ab0@mail.dnai.com>, you write: >Sorry, I should have defined high-capacity better. I would like to >isolate a half-dozen FreeBSD servers running a custom distributed >web application behind a router/firewall. This is to increase >security for intra-machine communication. At our co-location >facility we have a 100Mb ethernet tap to a Cisco switch/router >combination isolating our systems on a VPN. My question is about >whether FreeBSD can keep up as a router (with a few firewall rules) >between two 100Mb ethernet networks on decent hardware such as 2 PCI >NICs and a 450 MHz PII. From the responses it sounds like it can. If you're using FreeBSD as a firewall between servers and the Internet, what really matters here is not the 100Mb/s local links but the speed of your WAN link, because that's how much traffic is really going to move through that box. Can FreeBSD keep up with a T1/E1 line? I'd be surprised if it couldn't. Can FreeBSD keep up with a DS3? Given good enough hardware, probably. Faster than that as total traffic going through the box and you need to worry. -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 13:36: 3 1999 Delivered-To: freebsd-net@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.9]) by hub.freebsd.org (Postfix) with ESMTP id 666CB14C0E for ; Mon, 29 Mar 1999 13:35:53 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id PAA01360; Mon, 29 Mar 1999 15:34:58 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 29 Mar 1999 15:34:58 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: cmetz@inner.net Cc: miket@dnai.com, mike@sentex.net, freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router References: <4.1.19990329115145.00a62ab0@mail.dnai.com> <199903292051.UAA10838@inner.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14079.61724.162248.667212@avalon.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoth Craig Metz on Mon, 29 March: : : If you're using FreeBSD as a firewall between servers and the Internet, what : really matters here is not the 100Mb/s local links but the speed of your WAN : link, because that's how much traffic is really going to move through that box. : Can FreeBSD keep up with a T1/E1 line? I'd be surprised if it couldn't. Can : FreeBSD keep up with a DS3? Given good enough hardware, probably. Faster than : that as total traffic going through the box and you need to worry. Since the discussion is occurring at this level, it is probably helpful to note that the *size* of the packets also plays a large role in determining maximum routing throughput: The box has to do a lot more routing for 512B packets than it does for 1024B packets at the same bandwidth. I'm guessing that a thorough search would show up some clock vs. packet-size vs. bandwidth limit graphs for FreeBSD, Linux, various commerical routers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 13:41:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from snowcrest.net (mtshasta.snowcrest.net [209.232.210.195]) by hub.freebsd.org (Postfix) with ESMTP id 4665914DB0 for ; Mon, 29 Mar 1999 13:41:28 -0800 (PST) (envelope-from djewett@snowcrest.net) Received: from ws2600 (ppp00313.snowcrest.net [209.78.170.141]) by snowcrest.net (8.8.5/8.8.5) with SMTP id NAA20467; Mon, 29 Mar 1999 13:40:48 -0800 (PST) Message-ID: <001001be7a2c$8c2a6190$8daa4ed1@ws2600> From: "Derek Jewett" To: "Mike Thompson" , "Craig Metz" Cc: "Mike Tancsa" , Subject: Re: FreeBSD as a router Date: Mon, 29 Mar 1999 13:38:53 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If it's consilation we are building a pretty unique solution with a FreeBSD 3.x box using multi port cards.. We are using ETC's ET/5025pq-4-25 card (4-port v.35 cards), along with 4-port Ethernet NIC (adaptec Quartet64) to create a multi port router/firewall/switch/thingamajig.. We stole the idea from Nokia's IP440 switch concept. Just we don't use Firewall-1, we use FBSD native utilities... For info on the Cards; ETC - www.etinc.com/et5025pq.htm Quartet64 - www.adaptec.com and search for Quartet64 the 4-port NIC is about $540 and the 4-port v.35 T1 card is about $1600 with cables -----Original Message----- From: Craig Metz To: Mike Thompson Cc: Mike Tancsa ; freebsd-net@FreeBSD.ORG Date: Monday, March 29, 1999 12:57 PM Subject: Re: FreeBSD as a router >In message <4.1.19990329115145.00a62ab0@mail.dnai.com>, you write: >>Sorry, I should have defined high-capacity better. I would like to >>isolate a half-dozen FreeBSD servers running a custom distributed >>web application behind a router/firewall. This is to increase >>security for intra-machine communication. At our co-location >>facility we have a 100Mb ethernet tap to a Cisco switch/router >>combination isolating our systems on a VPN. My question is about >>whether FreeBSD can keep up as a router (with a few firewall rules) >>between two 100Mb ethernet networks on decent hardware such as 2 PCI >>NICs and a 450 MHz PII. From the responses it sounds like it can. > > If you're using FreeBSD as a firewall between servers and the Internet, what >really matters here is not the 100Mb/s local links but the speed of your WAN >link, because that's how much traffic is really going to move through that box. >Can FreeBSD keep up with a T1/E1 line? I'd be surprised if it couldn't. Can >FreeBSD keep up with a DS3? Given good enough hardware, probably. Faster than >that as total traffic going through the box and you need to worry. > > -Craig > > > >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 Mon Mar 29 13:51:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1F18114CC7 for ; Mon, 29 Mar 1999 13:51:15 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA76355; Mon, 29 Mar 1999 13:47:08 -0800 (PST) Date: Mon, 29 Mar 1999 13:47:07 -0800 (PST) From: Julian Elischer To: Derek Jewett Cc: Mike Thompson , Craig Metz , Mike Tancsa , freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router In-Reply-To: <001001be7a2c$8c2a6190$8daa4ed1@ws2600> 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, 29 Mar 1999, Derek Jewett wrote: > If it's consilation we are building a pretty unique solution with a FreeBSD > 3.x box using multi port cards.. We are using ETC's ET/5025pq-4-25 card > (4-port v.35 cards), along with 4-port Ethernet NIC (adaptec Quartet64) to > create a multi port router/firewall/switch/thingamajig.. We stole the idea > from Nokia's IP440 switch concept. Just we don't use Firewall-1, we use FBSD > native utilities... so, what do you think Nokia use? :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 14: 0:53 1999 Delivered-To: freebsd-net@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 6C12715540 for ; Mon, 29 Mar 1999 14:00:40 -0800 (PST) (envelope-from bmilekic@oracle.dsuper.net) Received: from localhost (bmilekic@localhost) by oracle.dsuper.net (Delphi 1.3/8.6.9) with ESMTP id RAA25754; Mon, 29 Mar 1999 17:00:17 -0500 (EST) Date: Mon, 29 Mar 1999 17:00:04 -0500 (EST) From: Bosko Milekic To: Donn Miller Cc: net@FreeBSD.ORG Subject: Re: FreeBSD equiv. of this Linux socket call... In-Reply-To: <36FF11E2.4B661EED@cvzoom.net> 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 After open()ing your bpf device file, there are several ioctl()s that need to be called to set the different characteristics of the device. These ioctl()s will basically allow you to load the actual filter, enable promiscuous mode, etc. Only after these ioctl()s, you can perform (and later interpret) I/O with, obviously, read() and write(). I strongly recommend reading the bpf man page, if you haven't done so already, for more information about the ioctl()s. Regards, Bosko. -- Bosko Milekic http://www.supernet.ca/~bmilekic/ Delphi SuperNet voice: (+1) 514 281-7500 fax: (+1) 514 281-6599 PGP Key available upon request. On Mon, 29 Mar 1999, Donn Miller wrote: > Date: Mon, 29 Mar 1999 05:38:42 +0000 > From: Donn Miller > To: net@FreeBSD.ORG > Subject: FreeBSD equiv. of this Linux socket call... > > I'm looking for the FreeBSD equivalent of this Linux socket call: > > dhcpSocket = socket(AF_PACKET,SOCK_PACKET,htons(ETH_P_ALL)); > > So far, I think "SOCK_PACKET" can be replaced by a call to /dev/bpf0. > How should /dev/bpf be opened? Should it be by the regular libc open() > command, which returns a file descriptor, that is later used to bind > this file descriptor to a device interface? What is AF_PACKET; I don't > think FreeBSD supports that either. > > Thanks, this is a tough one. > > Donn > > > > > 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 Mon Mar 29 14:15: 3 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B5B291550E for ; Mon, 29 Mar 1999 14:15:01 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA14019; Mon, 29 Mar 1999 17:14:28 -0500 (EST) (envelope-from wollman) Date: Mon, 29 Mar 1999 17:14:28 -0500 (EST) From: Garrett Wollman Message-Id: <199903292214.RAA14019@khavrinen.lcs.mit.edu> To: alk@pobox.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router In-Reply-To: <14079.61724.162248.667212@avalon.east> References: <4.1.19990329115145.00a62ab0@mail.dnai.com> <199903292051.UAA10838@inner.net> <14079.61724.162248.667212@avalon.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > in determining maximum routing throughput: The box has to do a lot > more routing for 512B packets than it does for 1024B packets at the > same bandwidth. Very true. Just some quick statistics for one real-world network: Port Link Packet Sizes Num Status 0-64 65-127 128-255 256-511 512-1023 1024-1518 =============================================================================== 26 ACTIVE 1235904191 407413622 49843785 46400345 68324479 340953031 ...in percentage terms, that's: 57.5% 19.0% 2.3% 2.2% 3.2% 15.9% These numbers include all of the external network traffic of a medium-sized (500 people/1200 machines) nationally-reknowned research laboratory over the course of 13 days. As you can see, more than half of all packets are relatively tiny, and consist of things such as ICMPs, small TCP segments from interactive sessions, and DNS queries. (One of these days I'll set up port mirroring so that I can see just what all that traffic is.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 15:28:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from inner.net (avarice.inner.net [199.33.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 129E714C18 for ; Mon, 29 Mar 1999 15:28:30 -0800 (PST) (envelope-from cmetz@inner.net) Received: from inner.net (cmetz.cstone.net [205.197.102.217]) by inner.net (8.9.1/8.9.1) with ESMTP id XAA11026; Mon, 29 Mar 1999 23:22:52 GMT Message-Id: <199903292322.XAA11026@inner.net> To: alk@pobox.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router In-reply-to: Your message of "Mon, 29 Mar 1999 15:34:58 CST." <14079.61724.162248.667212@avalon.east> X-Copyright: Copyright 1999, Craig Metz, All Rights Reserved. X-Reposting: With explicit permission only Date: Mon, 29 Mar 1999 18:27:03 -0500 From: Craig Metz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <14079.61724.162248.667212@avalon.east>, you write: >Since the discussion is occurring at this level, it is probably >helpful to note that the *size* of the packets also plays a large role >in determining maximum routing throughput: The box has to do a lot >more routing for 512B packets than it does for 1024B packets at the >same bandwidth. The box doesn't have to do "more routing" for a 512B packet than a 1024B packet, but, if you're filling the same number of bits/second, there are twice as many packets to move for 512B packets than for 1024B packets. (I believe this is what you meant, I just wanted to make sure people didn't get the wrong interpretation) Most router benchmarks like to talk about PPS as opposed to bits/second, and this is why -- most of the routing overhead is per-packet, not per-byte. >I'm guessing that a thorough search would show up some clock >vs. packet-size vs. bandwidth limit graphs for FreeBSD, Linux, >various commerical routers. I'd love to see well-done test data to substantiate or refute this sort of discussion; people know what the good and bad properties of the hardware and the software are and can take reasonably good guesses, but they're still just guesses and not measured performance numbers. I know that there is data out there, but I don't know how good it is. -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 16:51:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 0A5A014FBF for ; Mon, 29 Mar 1999 16:51:54 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id TAA14572; Mon, 29 Mar 1999 19:51:13 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990329195605.045c8520@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 29 Mar 1999 20:00:35 -0500 To: Craig Metz , Mike Thompson From: Mike Tancsa Subject: Re: FreeBSD as a router Cc: freebsd-net@FreeBSD.ORG, dennis@etinc.com In-Reply-To: <199903292051.UAA10838@inner.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If you're using FreeBSD as a firewall between servers and the Internet, what >really matters here is not the 100Mb/s local links but the speed of your WAN >link, because that's how much traffic is really going to move through that box. >Can FreeBSD keep up with a T1/E1 line? I'd be surprised if it couldn't. Can >FreeBSD keep up with a DS3? Given good enough hardware, probably. Faster than >that as total traffic going through the box and you need to worry. The Etinc.com people make a HSSI card with FreeBSD drivers.. To quote " The ET/HSSI adapter adds 1 or 2 HSSI ports to PC-based routers. Both ports can run up to 52Mb/s, accommodating 2 full-rate DS3 circuits. The ET/HSSI 32-bit PCI architecture utilizes single-cycle bus-mastering technology to maximize throughput and efficiency." I have never used their high end cards, only a couple of their T1 cards. Perhaps dennis@etinc.com could comment on this, as he certainly would be a qualified contributor on this matter. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 16:59:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 29A1B1518E for ; Mon, 29 Mar 1999 16:59:10 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA17901; Mon, 29 Mar 1999 16:57:23 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA12740; Mon, 29 Mar 1999 16:57:23 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id RAA24793; Mon, 29 Mar 1999 17:57:14 -0700 Message-ID: <3700216B.D9C090D8@softweyr.com> Date: Mon, 29 Mar 1999 17:57:15 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Thompson Cc: Craig Metz , Mike Tancsa , freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router References: <4.1.19990329115145.00a62ab0@mail.dnai.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Thompson wrote: > > At 04:59 PM 3/27/99 -0500, Craig Metz wrote: > > What really matters here is the application. > > > >If the original poster was thinking about using FreeBSD-based > >commidity PCs for the core routers of a large ISP... > > Sorry, I should have defined high-capacity better. I would like to > isolate a half-dozen FreeBSD servers running a custom distributed > web application behind a router/firewall. This is to increase > security for intra-machine communication. At our co-location > facility we have a 100Mb ethernet tap to a Cisco switch/router > combination isolating our systems on a VPN. And what throughput do you have coming into the other side of the Cisco? In other words, what kind of total throughput from the outside world to your servers do you expect to see? Does this router have a 100 Mb/s connection to the external network, whatever that is? > My question is about > whether FreeBSD can keep up as a router (with a few firewall rules) > between two 100Mb ethernet networks on decent hardware such as 2 PCI > NICs and a 450 MHz PII. From the responses it sounds like it can. Probably can. If your real throughput is less than 100 Mb/s, then it almost certainly can. Firewall performance probably won't keep up with 100 Mb/s unless you have VERY few rules, but it might be adequate depending on what your REAL throughput requirements are. > I am interested in using FreeBSD as the router/firewall because it > is easy to configure and I don't have to learn something new on > top everything else I am doing. > > Thanks to everyone for their responses. Best of luck. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 17: 3:42 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 0C6DA14FA0 for ; Mon, 29 Mar 1999 17:03:35 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id RAA17941; Mon, 29 Mar 1999 17:01:30 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA12848; Mon, 29 Mar 1999 17:01:29 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id SAA25052; Mon, 29 Mar 1999 18:01:24 -0700 Message-ID: <37002265.42C5A00B@softweyr.com> Date: Mon, 29 Mar 1999 18:01:25 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Derek Jewett , Mike Thompson , Craig Metz , Mike Tancsa , freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > On Mon, 29 Mar 1999, Derek Jewett wrote: > > > If it's consilation we are building a pretty unique solution with a FreeBSD > > 3.x box using multi port cards.. We are using ETC's ET/5025pq-4-25 card > > (4-port v.35 cards), along with 4-port Ethernet NIC (adaptec Quartet64) to > > create a multi port router/firewall/switch/thingamajig.. We stole the idea > > from Nokia's IP440 switch concept. Just we don't use Firewall-1, we use FBSD > > native utilities... > > so, what do you think Nokia use? Checkpoint Firewall-1, just as he said. Their VPN product uses Checkpoint VPN-1 also. Checkpoint has both available to OEMs on FreeBSD, but won't release it as a product. Go figure. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 17:23:32 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id D234014E8A for ; Mon, 29 Mar 1999 17:23:27 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA14792; Mon, 29 Mar 1999 20:22:54 -0500 (EST) (envelope-from wollman) Date: Mon, 29 Mar 1999 20:22:54 -0500 (EST) From: Garrett Wollman Message-Id: <199903300122.UAA14792@khavrinen.lcs.mit.edu> To: Craig Metz Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router In-Reply-To: <199903292322.XAA11026@inner.net> References: <14079.61724.162248.667212@avalon.east> <199903292322.XAA11026@inner.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I'd love to see well-done test data to substantiate or refute this sort of > discussion; people know what the good and bad properties of the hardware and > the software are and can take reasonably good guesses, but they're still just > guesses and not measured performance numbers. I know that there is data out > there, but I don't know how good it is. I actually did something like this a few years back. The tests we were running were flat-out packet generation (because we needed to know how fast we could send packets before we attempted to receive or forward them). At that time, the fastest machine we had in the hardware lab was a 200-MHz Pentium Pro with the Natoma chipset; with the best hardware/driver combination (Intel 82557), we were able to transmit at line rate at packet sizes down to about 80 bytes (excuse me, octets) before the machine ran out of gas. With better chipsets and faster memory subsystems, there should be plenty of headroom to forward packets at line rate, particularly if you're doing VJ-style fast forwarding. (Whether that leaves enough CPU to run a routing protocol as well I can't say.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 19:10:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from tch.org (tacostand.tch.org [199.74.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 8220114F64 for ; Mon, 29 Mar 1999 19:10:20 -0800 (PST) (envelope-from ser@tch.org) Received: (from ser@localhost) by tch.org (8.9.1/8.9.1) id TAA00972; Mon, 29 Mar 1999 19:09:57 -0800 (PST) (envelope-from ser) Date: Mon, 29 Mar 1999 19:09:56 -0800 From: Steve Rubin To: Bill Fumerola Cc: freebsd-net@freebsd.org Subject: Re: switch vs bridge (fwd) Message-ID: <19990329190956.A961@tch.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Bill Fumerola on Wed, Mar 24, 1999 at 02:23:01PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 24, 1999 at 02:23:01PM -0500, Bill Fumerola wrote: > On Wed, 24 Mar 1999, Peter Brezny wrote: > > > is a switch the same thing as a multi port bridge? > > Not hardly. > > A switch replicates packets based on their Ethernet destination. Which is exactly how a bridge behaves. -- Steve Rubin ser@tch.org TCH Network Services http://www.tch.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Mar 29 22:32:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id EEA8014F42 for ; Mon, 29 Mar 1999 22:32:10 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA00488; Mon, 29 Mar 1999 23:31:45 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <37006FD1.45A2865A@softweyr.com> Date: Mon, 29 Mar 1999 23:31:45 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD as a router References: <14079.61724.162248.667212@avalon.east> <199903292322.XAA11026@inner.net> <199903300122.UAA14792@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman wrote: > > < said: > > > I'd love to see well-done test data to substantiate or refute this sort of > > discussion; people know what the good and bad properties of the hardware and > > the software are and can take reasonably good guesses, but they're still just > > guesses and not measured performance numbers. I know that there is data out > > there, but I don't know how good it is. > > I actually did something like this a few years back. The tests we > were running were flat-out packet generation (because we needed to > know how fast we could send packets before we attempted to receive or > forward them). At that time, the fastest machine we had in the > hardware lab was a 200-MHz Pentium Pro with the Natoma chipset; with > the best hardware/driver combination (Intel 82557), we were able to > transmit at line rate at packet sizes down to about 80 bytes (excuse > me, octets) before the machine ran out of gas. With better chipsets > and faster memory subsystems, there should be plenty of headroom to > forward packets at line rate, particularly if you're doing VJ-style > fast forwarding. (Whether that leaves enough CPU to run a routing > protocol as well I can't say.) If somebody wants to write up some sketchy details as to what I should configure, I can do a couple of quick tests later this week. I have a PII-233 machine with 64MB RAM, one onboard EEPro100, and two 3C905B on PCI cards. I also have access to a SmartBits traffic generator that can do 2 or 3 full-duplex 100Base-TX streams without breaking a sweat, and gives really reliable numbers. If other network interfaces would be better, let me know and I'll see if I can scare up a couple of them. Another EEPro100 shouldn't be a problem to borrow, for instance. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 2:46:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 820A014D1A for ; Tue, 30 Mar 1999 02:46:41 -0800 (PST) (envelope-from fanf@demon.net) Received: by noc.demon.net; id LAA18846; Tue, 30 Mar 1999 11:46:21 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma018797; Tue, 30 Mar 99 11:46:06 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10Rw21-0006sG-00; Tue, 30 Mar 1999 11:46:05 +0100 To: net@freebsd.org From: Tony Finch Cc: Tony Finch Subject: Re: FreeBSD as a router Newsgroups: chiark.mail.freebsd.net In-Reply-To: <199903272156.VAA08726@inner.net> Organization: Deliberate Obfuscation To Amuse Tony References: <36fd12fb.3761327633@mail.sentex.net> Message-Id: Date: Tue, 30 Mar 1999 11:46:05 +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Craig Metz wrote: > >If the original poster was thinking about using FreeBSD-based >commidity PCs for the core routers of a large ISP, well, he can >keep thinking that (just don't do it!). It may not be wise but people do do it :-) It was how PR# kern/10570 was discovered. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 2:54:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (wya-lfd107.hotmail.com [207.82.252.171]) by hub.freebsd.org (Postfix) with SMTP id 16E34159F3 for ; Tue, 30 Mar 1999 02:54:18 -0800 (PST) (envelope-from vas99@hotmail.com) Received: (qmail 46050 invoked by uid 0); 30 Mar 1999 10:54:00 -0000 Message-ID: <19990330105400.46048.qmail@hotmail.com> Received: from 195.66.200.160 by www.hotmail.com with HTTP; Tue, 30 Mar 1999 02:53:59 PST X-Originating-IP: [195.66.200.160] From: "Vasily Kondrashov" To: freebsd-net@freebsd.org Subject: Network Address Translation. Date: Tue, 30 Mar 1999 02:53:59 PST Mime-Version: 1.0 Content-type: text/plain Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org natd setting up howto is available at http://members.tripod.com/vas99/natd.html Any comments are welcome via e-mail (vas99@hotmail.com) Vasily. Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 4:20: 4 1999 Delivered-To: freebsd-net@freebsd.org Received: from shome.eu.org (sirius.stack.net [192.124.172.17]) by hub.freebsd.org (Postfix) with ESMTP id 0306B14E9F for ; Tue, 30 Mar 1999 04:19:58 -0800 (PST) (envelope-from as@shome.eu.org) Received: from lamb (lamb.shome.eu.org [195.19.5.8]) by shome.eu.org (8.8.7/8.8.7) with SMTP id QAA15219 for ; Tue, 30 Mar 1999 16:15:24 +0400 From: "Alex Sel'kov" To: Subject: 2 cards in one collision domain Date: Tue, 30 Mar 1999 16:21:51 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What's wrong? Why I recieve this strange messages? Another question: I have two 21143-based NIC's, but only one of them correctly select 100Mbit transfer rate. Regards, as > --- /var/log/messages > Mar 30 02:18:02 <0.3> turtle /kernel: arp: 00:00:1c:b0:d9:37 is > using my IP > address 192.168.10.1! > Mar 30 02:18:02 <0.3> turtle /kernel: arp: 00:c0:ca:11:78:ed is > using my IP > address 192.168.10.1! > > --- ifconfig -a > > de0: flags=8843 mtu 1500 > inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255 > ether 00:00:1c:b0:d9:37 > media: autoselect (100baseTX) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UT > P 10baseT/UTP > de1: flags=8843 mtu 1500 > inet 192.168.20.1 netmask 0xffffff00 broadcast 192.168.20.255 > ether 00:c0:ca:11:78:ed > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UT > P 10baseT/UTP > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 5:28:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 76D4F15AC0 for ; Tue, 30 Mar 1999 05:28:08 -0800 (PST) (envelope-from stefan@promo.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id PAA25775; Tue, 30 Mar 1999 15:26:38 +0200 (CEST) Date: Tue, 30 Mar 1999 15:26:37 +0200 From: Stefan Bethke To: "Alex Sel'kov" Cc: freebsd-net@FreeBSD.ORG Subject: Re: 2 cards in one collision domain Message-ID: <690244.3131796397@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex Sel'kov wrote: > What's wrong? Why I recieve this strange messages? > > Another question: I have two 21143-based NIC's, but only one of them > correctly select 100Mbit transfer rate. >> --- /var/log/messages >> Mar 30 02:18:02 <0.3> turtle /kernel: arp: 00:00:1c:b0:d9:37 is >> using my IP >> address 192.168.10.1! >> Mar 30 02:18:02 <0.3> turtle /kernel: arp: 00:c0:ca:11:78:ed is >> using my IP >> address 192.168.10.1! >> >> --- ifconfig -a >> >> de0: flags=8843 mtu 1500 >> inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255 >> ether 00:00:1c:b0:d9:37 >> media: autoselect (100baseTX) status: active >> supported media: autoselect 100baseTX 100baseTX >> 10baseT/UT >> P 10baseT/UTP >> de1: flags=8843 mtu 1500 >> inet 192.168.20.1 netmask 0xffffff00 broadcast 192.168.20.255 >> ether 00:c0:ca:11:78:ed >> media: autoselect (10baseT/UTP) status: active >> supported media: autoselect 100baseTX 100baseTX >> 10baseT/UT >> P 10baseT/UTP >> lo0: flags=8049 mtu 16384 >> inet 127.0.0.1 netmask 0xff000000 You didn't by chance enable net.link.ether.inet.proxyall? The kernel normally shouldn't, but your's stumbles over it's own ARP replies: an ARP request for 192.168.10.1 is presumably answered correctly on de0, but also on de1. In turn de0 snoops the reply, and moans. The non-working autoselect might be due to different PHY chips used (jugding from the vastly different MAC addresses, I guess the cards are from two diffent vendors). Check what dmesg says about the PHY chips. Your hub/switch does support auto-negotiation, does it? Some PHYs are not very good at auto-sensing, AFAIK. In this case, set the media manually. Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 6:25:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from shome.eu.org (sirius.stack.net [192.124.172.17]) by hub.freebsd.org (Postfix) with ESMTP id 784CF14D40 for ; Tue, 30 Mar 1999 06:25:47 -0800 (PST) (envelope-from as@shome.eu.org) Received: from lamb (lamb.shome.eu.org [195.19.5.8]) by shome.eu.org (8.8.7/8.8.7) with SMTP id SAA15477 for ; Tue, 30 Mar 1999 18:21:14 +0400 From: "Alex Sel'kov" To: Subject: RE: 2 cards in one collision domain Date: Tue, 30 Mar 1999 18:27:40 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You didn't by chance enable net.link.ether.inet.proxyall? The kernel > normally shouldn't, but your's stumbles over it's own ARP replies: an ARP > request for 192.168.10.1 is presumably answered correctly on de0, but also > on de1. In turn de0 snoops the reply, and moans. > Hmm. I'm newbie, so I can't play with such things like sysctl yet :) sysctl -a| grep net.link.ether.inet.proxyall net.link.ether.inet.proxyall: 0 As far as I can understand 0 stands for "disabled"? But you are definitely right - looks like enabled internal bridge. Where I can look for parameters which control such behaivor? > The non-working autoselect might be due to different PHY chips used > (jugding from the vastly different MAC addresses, I guess the cards are > from two diffent vendors). Check what dmesg says about the PHY chips. > Yes, cards from differnt vendors. Mar 29 03:19:40 <0.2> turtle /kernel: de0: rev 0x41 int a irq 16 on pci0.19.0 Mar 29 03:19:40 <0.2> turtle /kernel: de0: 21143 [10-100Mb/s] pass 4.1 (invalid EESPROM checksum) Mar 29 03:19:40 <0.2> turtle /kernel: de0: address 00:00:1c:b0:d9:37 Mar 29 03:19:40 <0.2> turtle /kernel: de1: rev 0x30 int a irq 16 on pci2.4.0 Mar 29 03:19:40 <0.2> turtle /kernel: de1: 21143 [10-100Mb/s] pass 3.0 Mar 29 03:19:40 <0.2> turtle /kernel: de1: address 00:c0:ca:11:78:ed First one (de0) works fine. Second negotiate only 10Mb transfer rate. Under linux/w98 everything works fine. > Your hub/switch does support auto-negotiation, does it? Some PHYs are not > very good at auto-sensing, AFAIK. In this case, set the media manually. > If I try to set media to 100baseTX manually than de1 completely stops responding. Ok, this is stupid problem - I can sipmly exchange card with another machine. Just curious. Regards, as To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 9:27:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id F345C15B67; Tue, 30 Mar 1999 09:27:02 -0800 (PST) (envelope-from stefan@promo.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id TAA26966; Tue, 30 Mar 1999 19:25:11 +0200 (CEST) Date: Tue, 30 Mar 1999 19:25:09 +0200 From: Stefan Bethke To: "Alex Sel'kov" Cc: freebsd-net@FreeBSD.ORG Subject: RE: 2 cards in one collision domain Message-ID: <1551469.3131810709@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex Sel'kov wrote: >> You didn't by chance enable net.link.ether.inet.proxyall? The kernel >> normally shouldn't, but your's stumbles over it's own ARP replies: an ARP >> request for 192.168.10.1 is presumably answered correctly on de0, but >> also on de1. In turn de0 snoops the reply, and moans. >> > > Hmm. I'm newbie, so I can't play with such things like sysctl yet :) > > sysctl -a| grep net.link.ether.inet.proxyall > net.link.ether.inet.proxyall: 0 > > As far as I can understand 0 stands for "disabled"? Yes. > But you are definitely right - looks like enabled internal bridge. Where > I can look for parameters which control such behaivor? Did you add "options BRIDGE" to your kernel config file? I'm now somewhat confused. I *think* that you'd normally shouldn't see this message, unless you enabled bridging. However, why would you want to enable bridging between two interfaces connected to the same net? Why have you connected both interfaces to the same net? If you want your host to be on two subnets on the same wire, simply configure both IPs (see /etc/rc.conf for details). >> The non-working autoselect might be due to different PHY chips used >> (jugding from the vastly different MAC addresses, I guess the cards are >> from two diffent vendors). Check what dmesg says about the PHY chips. >> > > Yes, cards from differnt vendors. > > Mar 29 03:19:40 <0.2> turtle /kernel: de0: > rev 0x41 int a irq 16 on pci0.19.0 > Mar 29 03:19:40 <0.2> turtle /kernel: de0: 21143 [10-100Mb/s] pass 4.1 > (invalid EESPROM checksum) > Mar 29 03:19:40 <0.2> turtle /kernel: de0: address 00:00:1c:b0:d9:37 > > Mar 29 03:19:40 <0.2> turtle /kernel: de1: > rev 0x30 int a irq 16 on pci2.4.0 > Mar 29 03:19:40 <0.2> turtle /kernel: de1: 21143 [10-100Mb/s] pass 3.0 > Mar 29 03:19:40 <0.2> turtle /kernel: de1: address 00:c0:ca:11:78:ed Hhm. Can you compile /sys/pci/if_de.c with TULIP_DEBUG enabled? And give us some more information on the make and model of the cards your using? Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 14:23:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.amicapital.com (smtp.amicapital.com [207.31.97.178]) by hub.freebsd.org (Postfix) with ESMTP id 3D95B15B5F for ; Tue, 30 Mar 1999 14:23:36 -0800 (PST) (envelope-from tarrowsmith@amicapital.com) Received: from tarrowsm ([192.168.4.56]) by mail.amicapital.com (8.8.7/8.8.7) with SMTP id RAA18354 for ; Tue, 30 Mar 1999 17:16:52 -0500 (EST) (envelope-from tarrowsmith@amicapital.com) From: "T.J. Arrowsmith" To: Subject: Connecting to the Internet Date: Tue, 30 Mar 1999 17:22:41 -0500 Message-ID: <000901be7afb$d345cea0$3804a8c0@tarrowsm.amicapital.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.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, My company is currently running a FreeBSD box as a firewall/mail server. Currently we are connected to the internet via a frame relay circuit. I'd like to add a backup connection through a separate ISP, using a DSL line. Is it possible to configure the FreeBSD box to route traffic primarily through the main frame relay circuit, and have it switch to the DSL circuit when/if the Frame Relay circuit fails? I'm not sure at all if i'm asking the right questions here, so if there's something I haven't considered, feel free to let me know. Thanks in advance, T.J. Arrowsmith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Mar 30 17:33:34 1999 Delivered-To: freebsd-net@freebsd.org Received: from shome.eu.org (sirius.stack.net [192.124.172.17]) by hub.freebsd.org (Postfix) with ESMTP id 2026914BF9 for ; Tue, 30 Mar 1999 17:33:30 -0800 (PST) (envelope-from as@shome.eu.org) Received: from lamb (lamb.shome.eu.org [195.19.5.8]) by shome.eu.org (8.8.7/8.8.7) with SMTP id FAA17341; Wed, 31 Mar 1999 05:28:30 +0400 From: "Alex Sel'kov" To: Cc: Subject: RE: 2 cards in one collision domain Date: Wed, 31 Mar 1999 05:34:43 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) In-reply-to: <1551469.3131810709@d225.promo.de> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Did you add "options BRIDGE" to your kernel config file? > > I'm now somewhat confused. I *think* that you'd normally > shouldn't see this > message, unless you enabled bridging. > Yes, I did. But net.link.ether.bridge: 0 is not enough to disable bridging at all? > However, why would you want to enable bridging between two interfaces > connected to the same net? > No, I don't. But this is only one of possible configurations. I must to play with various scenario, with and without bridging. In this current case I don't want any bridging functionality. Anyway, I can simply use a different kernel versions in different scenario. > Why have you connected both interfaces to the same net? If you want your > host to be on two subnets on the same wire, simply configure both IPs (see > /etc/rc.conf for details). Yes, I want have two connections to large shared media (large bridged/switched net on logical link layer). I can use aliases, but this is not exact what I need. because I can have different rules of game at MAC layer and MAC address can make difference. > Hhm. Can you compile /sys/pci/if_de.c with TULIP_DEBUG enabled? And give > us some more information on the make and model of the cards your using? > de0: Vendor: Nexo (http://www.nexo.com.tw). Name - NEC-100D. Chip - INTEL 21143-PD. Transceiver - DM9101F. de1: Vendor: unknown. Name: unknown. Chip - Digital 21143-PC. Transceiver - Kendin KS8761. dmesg: de0: rev 0x41 int a irq 16 on pci0.19.0 de0: 21143 [10-100Mb/s] pass 4.1 (invalid EESPROM checksum) de0: address 00:00:1c:b0:d9:37 de0: timeout: probing 100baseTX de1: rev 0x30 int a irq 16 on pci2.4.0 de1: 21143 [10-100Mb/s] pass 3.0 de1: address 00:c0:ca:11:78:ed de1: timeout: probing 100baseTX de0: enabling 100baseTX port de1: timeout: probing 10baseT de1: enabling 10baseT port de0: timeout: probing 100baseTX de1: timeout: probing 100baseTX de1: timeout: probing 10baseT de1: enabling 10baseT port arp: 192.168.10.254 is on de0 but got reply from 00:80:48:d9:76:77 on de1 I got last message because now kernel recompiled without bridging support. But it looks strange - it is not an error from my point of view... :) Regards, as To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 1:31: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id C0AF515159 for ; Wed, 31 Mar 1999 01:31:01 -0800 (PST) (envelope-from stefan@promo.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id LAA01214; Wed, 31 Mar 1999 11:29:25 +0200 (CEST) Date: Wed, 31 Mar 1999 11:29:23 +0200 From: Stefan Bethke To: "Alex Sel'kov" Cc: freebsd-net@FreeBSD.ORG Subject: RE: 2 cards in one collision domain Message-ID: <327978.3131868563@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex Sel'kov wrote: >> Did you add "options BRIDGE" to your kernel config file? >> >> I'm now somewhat confused. I *think* that you'd normally >> shouldn't see this >> message, unless you enabled bridging. >> > > Yes, I did. But net.link.ether.bridge: 0 is not enough to disable bridging > at all? No. In some parts of the kernel, some code is ommited or included specifically with options BRIDGE, for example, some ARP code in src/sys/netinet/if_ether.c. >> However, why would you want to enable bridging between two interfaces >> connected to the same net? > No, I don't. But this is only one of possible configurations. I must to > play with various scenario, with and without bridging. In this current > case I don't want any bridging functionality. > > Anyway, I can simply use a different kernel versions in different > scenario. That would seem resonable. >> Why have you connected both interfaces to the same net? If you want your >> host to be on two subnets on the same wire, simply configure both IPs >> (see /etc/rc.conf for details). > > Yes, I want have two connections to large shared media (large > bridged/switched net on logical link layer). I can use aliases, but this > is not exact what I need. because I can have different rules of game at > MAC layer and MAC address can make difference. > >> Hhm. Can you compile /sys/pci/if_de.c with TULIP_DEBUG enabled? And >> give us some more information on the make and model of the cards your >> using? >> > > de0: > > Vendor: Nexo (http://www.nexo.com.tw). Name - NEC-100D. Chip - INTEL > 21143-PD. > Transceiver - DM9101F. > > de1: > > Vendor: unknown. Name: unknown. Chip - Digital 21143-PC. Transceiver - > Kendin KS8761. > > dmesg: [ reordered for clarity ] > de0: rev 0x41 int a irq 16 on pci0.19.0 > de0: 21143 [10-100Mb/s] pass 4.1 (invalid EESPROM checksum) > de0: address 00:00:1c:b0:d9:37 > de0: timeout: probing 100baseTX > de0: enabling 100baseTX port > de0: timeout: probing 100baseTX > de1: rev 0x30 int a irq 16 on pci2.4.0 > de1: 21143 [10-100Mb/s] pass 3.0 > de1: address 00:c0:ca:11:78:ed > de1: timeout: probing 100baseTX > de1: timeout: probing 10baseT > de1: enabling 10baseT port > de1: timeout: probing 100baseTX > de1: timeout: probing 10baseT > de1: enabling 10baseT port It seems to me that the auto-sensing of your hub (a dual-speed hub?) and the cards don't get together well. The safest way in this case is to set the interface to the correct speed manually. As for de1, can you compile if_de.c with TULIP_DEBUG defined? This should give some more indications why the PHY isn't set up correctly for 100baseTX. I've just looked up the data sheets for both tranceivers, and the Kendin KS8761 (http://www.kendin.com/) doesn't support the MII control interface (the DM9101 does, http://www.davicom8.com/lan/dm9101.htm). In this case, the 2114x must specify the link rate to use via some other signal (the tranceiver needs two signals SEL10 and SEL100). I'll try to look into this. > arp: 192.168.10.254 is on de0 but got reply from 00:80:48:d9:76:77 on de1 > > I got last message because now kernel recompiled without bridging support. > But it looks > strange - it is not an error from my point of view... :) It's just a warning you can safely ignore. One could argue that it is pointless for the kernel to report stations moving from one interface to another, but usually, people don't connect two interfaces to the same net, either. Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 1:47:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from web707.mail.yahoo.com (web707.mail.yahoo.com [128.11.23.27]) by hub.freebsd.org (Postfix) with SMTP id 8EDC514EC8 for ; Wed, 31 Mar 1999 01:47:41 -0800 (PST) (envelope-from boardyan@yahoo.com) Message-ID: <19990331094625.5906.rocketmail@web707.mail.yahoo.com> Received: from [131.228.20.20] by web707.mail.yahoo.com; Wed, 31 Mar 1999 01:46:25 PST Date: Wed, 31 Mar 1999 01:46:25 -0800 (PST) From: boards yan Subject: congestion window To: freebsd-net@FreeBSD.ORG Cc: mks@networks.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Could anyone tell me how can I see congestion window through trpt output? Thanks a lot. rcv_nxt 2056ebeb rcv_wnd fffa snd_una 3130ef39 snd_nxt 313105b9 snd_max 313105b9 snd_wl1 2056ebeb snd_wl2 310d1339 snd_wnd 1988 REXMT=3 (t_rxtshft=0), KEEP=14400 023 ESTABLISHED:user SEND -> ESTABLISHED rcv_nxt 2056ebeb rcv_wnd fffa snd_una 3130ef39 snd_nxt 313105b9 snd_max 313105b9 snd_wl1 2056ebeb snd_wl2 310d1339 snd_wnd 1988 REXMT=3 (t_rxtshft=0), KEEP=14400 023 ESTABLISHED:user SEND -> ESTABLISHED _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 3:44:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from sims-ha.videotron.net (faure.videotron.net [205.151.222.100]) by hub.freebsd.org (Postfix) with ESMTP id 7C01F15C21 for ; Wed, 31 Mar 1999 03:44:07 -0800 (PST) (envelope-from pcbroch@videotron.ca) Received: from shark ([207.96.177.9]) by sims-ha.videotron.net (Sun Internet Mail Server sims.3.5.1998.03.08.20.27) with SMTP id <0F9G007Q0J8XRD@sims-ha.videotron.net> for freebsd-net@freebsd.org; Wed, 31 Mar 1999 06:43:45 -0500 (EST) Date: Wed, 31 Mar 1999 06:47:49 -0500 From: Patrick Brochu Subject: Network Address Translation. To: freebsd-net@freebsd.org Message-id: <001301be7b6c$4d3117e0$0201a8c0@shark> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 5.00.2014.211 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 References: <19990330105400.46048.qmail@hotmail.com> X-Priority: 3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all. Anybody could send me their rc.firewall file for a good firewall setup using natd (i'm using FreeBSD machine as a gateway to the internet for 3 other pcs). I dont want just the divert rule, but would also like filtering of services like web, ftp, etc. All the files i've seen so far don't work with my setup. Thanks. ----- Original Message ----- From: Vasily Kondrashov To: Sent: Tuesday, March 30, 1999 5:53 AM Subject: Network Address Translation. > natd setting up howto is available at > http://members.tripod.com/vas99/natd.html > > Any comments are welcome via e-mail (vas99@hotmail.com) > > Vasily. > Get Your Private, Free Email at http://www.hotmail.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 6:10:42 1999 Delivered-To: freebsd-net@freebsd.org Received: from host.nstl.nnov.ru (host.nstl.nnov.ru [195.98.49.67]) by hub.freebsd.org (Postfix) with ESMTP id C72E715C5F; Wed, 31 Mar 1999 06:10:31 -0800 (PST) (envelope-from alex-m@nstl.nnov.ru) Received: from nstl.nstl.nnov.ru (nstl.nstl.nnov.ru [195.98.58.2]) by host.nstl.nnov.ru (8.9.2/8.9.2) with ESMTP id SAA51537; Wed, 31 Mar 1999 18:10:11 +0400 (MSD) (envelope-from alex-m@nstl.nnov.ru) Received: from nstl.nstl.nnov.ru (adm.nstl.nnov.ru [195.98.58.5]) by nstl.nstl.nnov.ru (8.8.5/8.8.5) with SMTP id SAA19956; Wed, 31 Mar 1999 18:09:40 +0400 (MSK/MSD) Date: Wed, 31 Mar 1999 18:09:34 +0400 From: Alexander Dubinin X-Mailer: The Bat! (v1.18 Christmas Edition) UNREG Reply-To: Alexander Dubinin Organization: NSTL X-Priority: 3 (Normal) Message-ID: <7756.990331@nstl.nnov.ru> To: freebsd-hardware@freebsd.org Cc: freebsd-net@freebsd.org Subject: Which ISDN card is better? 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 Hello All! I need to find ISDN card, what can work with BRI ISDN line (At full 128K transfer rate, and may be more - with compression) and is supported by FreeBSD. That cards you can recommend? Next, I need to make connection via ISDN network between two local networks, and plan to use FreeBSD for it. Is any inmpementation of VPN software available? I want to use PTPP with dial-on-demand, and, maybe, encryption. Have anyone good advice for this? Thanx! Sorry for bad English :) Bye! Alexander Dubinin, Nizhny Novgorod Software Technology Lab Support Engineer E-mail: AlexanderX_Dubinin@nstl.ims.intel.com, alex@nstl.nnov.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 13:12:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from shome.eu.org (sirius.stack.net [192.124.172.17]) by hub.freebsd.org (Postfix) with ESMTP id C459E15192 for ; Wed, 31 Mar 1999 13:12:04 -0800 (PST) (envelope-from as@shome.eu.org) Received: from lamb (lamb.shome.eu.org [195.19.5.8]) by shome.eu.org (8.8.7/8.8.7) with SMTP id BAA19623; Thu, 1 Apr 1999 01:07:17 +0400 From: "Alex Sel'kov" To: Cc: Subject: RE: 2 cards in one collision domain Date: Thu, 1 Apr 1999 01:14:04 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) In-reply-to: <327978.3131868563@d225.promo.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > No. In some parts of the kernel, some code is ommited or included > specifically with options BRIDGE, for example, some ARP code in > src/sys/netinet/if_ether.c. > Aha. I got it. This is the place, where I can turn off unnecessary diagnostic code :) >It seems to me that the auto-sensing of your hub (a dual-speed hub?) and >the cards don't get together well. The safest way in this case is to set >the interface to the correct speed manually. Strange. I don't have such problem under linux (I mean autosensing). And when I try to force 100baseTX using ifconfig hub simply disconnect this adapter. > As for de1, can you compile if_de.c with TULIP_DEBUG defined? This should > give some more indications why the PHY isn't set up correctly for > 100baseTX. > But I'm already do this! :) OK, once again: [root@turtle TURTLE]$ dmesg | grep de1 de1: rev 0x30 int a irq 16 on pci2.4.0 de1: 21143 [10-100Mb/s] pass 3.0 de1: address 00:c0:ca:11:78:ed de1: timeout: probing 100baseTX de1: timeout: probing 10baseT de1: enabling 10baseT port de1: timeout: probing 100baseTX de1: timeout: probing 10baseT de1: enabling 10baseT port That's all messages with TULIP_DEBUG. > It's just a warning you can safely ignore. One could argue that it is > pointless for the kernel to report stations moving from one interface to > another, but usually, people don't connect two interfaces to the same net, > either. > Cut a piece of code not so difficult as write one ever for me :) BTW, thank you and other developers for a great job you doing for all of us! Regards, as To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 13:28: 7 1999 Delivered-To: freebsd-net@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D83631500C for ; Wed, 31 Mar 1999 13:27:57 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA15316; Wed, 31 Mar 1999 16:27:26 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA67169; Wed, 31 Mar 1999 16:27:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 31 Mar 1999 16:27:13 -0500 (EST) To: "Alex Sel'kov" Cc: , Subject: RE: 2 cards in one collision domain In-Reply-To: References: <327978.3131868563@d225.promo.de> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14082.37178.590322.537301@grasshopper.cs.duke.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex Sel'kov writes: > > As for de1, can you compile if_de.c with TULIP_DEBUG defined? This should > > give some more indications why the PHY isn't set up correctly for > > 100baseTX. > > > > But I'm already do this! :) > > OK, once again: > > [root@turtle TURTLE]$ dmesg | grep de1 > de1: rev 0x30 int a irq 16 on pci2.4.0 > de1: 21143 [10-100Mb/s] pass 3.0 > de1: address 00:c0:ca:11:78:ed > de1: timeout: probing 100baseTX > de1: timeout: probing 10baseT > de1: enabling 10baseT port > de1: timeout: probing 100baseTX > de1: timeout: probing 10baseT > de1: enabling 10baseT port > > That's all messages with TULIP_DEBUG. > It would be GREAT if somebody could actually fix the tulip driver so that it works with 21143's like this -- they're the onboard adaptor in Digital (alpha) Personal Workstations. I've had no end of problems with these adaptors. I spent a few hours looking at the driver & the 21143 specs, and became quite confused.. At one time, I offered to buy Matt Thomas (the driver's author) a 21143 based card. He told me he had some, but no switch.. Maybe we should take up a collection & buy him one ;-) Anyway, the only way I've had any success is by setting the card to 100Mb full-duplex and setting the switch to 100Mb, half-duplex. Somehow, the tulip ends up in half-duplex mode & all is well. If I set both the adaptor and switch to full-duplex (100mb), the card remains in half-duplex and performance is poor. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 15:38:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from abused.com (abused.com [204.216.142.63]) by hub.freebsd.org (Postfix) with ESMTP id 335F415406 for ; Wed, 31 Mar 1999 15:38:24 -0800 (PST) (envelope-from gvbmail@tns.net) Received: from gvb (gvb.tns.net [204.216.245.137]) by abused.com (8.9.3/I feel abused.) with SMTP id PAA84651 for ; Wed, 31 Mar 1999 15:38:04 -0800 (PST) Message-Id: <4.1.19990331153542.00bd3a10@abused.com> X-Sender: gvbmail@mail.tns.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 31 Mar 1999 15:38:02 -0800 To: freebsd-net@freebsd.org From: GVB Subject: Apache web server tuning.. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FreeBSD is the OS.... I am running Apache-SSL with FP extensions... the server suited us fine for the load, but now with increased business the server is starting to choke on me... It is now time to research FreeBSD kernel tuning and Apache tuning... Anyone have any basic recommendations as far as kernel options and things? I know thing like maxusers, somaxusers, fd_setsize, nmbclusters.. any other places I can find some info, or some other things I can fine tune to get more performance out of this machine? Each httpsd process is using about 2 megs of memory... thats alot in my book, and I'll like to decrease that... any help is appriciated.. Thanks in advance.. GVB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 17:25:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.kolej.mff.cuni.cz (smtp.kolej.mff.cuni.cz [195.113.25.225]) by hub.freebsd.org (Postfix) with ESMTP id 5EF6314C10 for ; Wed, 31 Mar 1999 17:25:19 -0800 (PST) (envelope-from mdvorak@ninell.cz) Received: from uvulium (uvulium.kolej.mff.cuni.cz [195.113.25.92]) by smtp.kolej.mff.cuni.cz (8.9.1a/8.9.0) with SMTP id DAA21714 for ; Thu, 1 Apr 1999 03:24:59 +0200 (CEST) From: "Martin Dvorak" To: Subject: dynamic intelligent traffic shaping Date: Thu, 1 Apr 1999 03:26:46 +0200 Message-ID: <000901be7bde$b5285cb0$5c1971c3@uvulium> 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.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've carefully read all messages about shaping the traffic on FreeBSD system on this mailing list and have two questions: 1. What is the best solution (dummynet or altq or something else) in the following situation: FreeBSD system on Internet server (on T1), each customer has its own IP address(es), each customer's monthly traffic has to be kept at some level (probably by using some clever algorithm (in a script probably), which dynamically (I suppose every hour) changes the traffic limit on customer's IP address(es) to reach as close as possible to monthly limit set by administrator)? That means I need to change shaping speed for each IP address quite often but also need the system to be stable as much as possible. 2. What is the best solution (dummynet or altq or something else) in the following situation: large Internet intranet (I do not know how it is called officialy but I mean an intranet with only one link to Internet (512kb or more) but each computer on this intranet has its own worldwide (non-intranet) IP address and normal (non-limited) access to Internet) with thousands computers on this intranet, a bridge/router on the link between the intranet and Internet. This bridge/router works like this: every intranet packet routes in the intranet with no traffic shaping (of course), but as for packets comming to/from Internet it should shape the traffic of each IP to give every computer on the intranet the same speed to/from Internet. That is the algorithm for shaping the speed of each IP address has to be much more clever than in the first case, it has to be able to change to shaping speed much more frequently (I guess every 5 minutes or even fewer) while changing the speed of much more IP addresses. If not talking about the algorithm (I will describe my idea shortly on the end of this message), I don't even know if it is possible to do it on some acceptable hardware configuration because I guess that only the changing of speed on each IP address so frequently would put very high load on the system, or not? Thank you very much for any though, suggestion or advice. I will appreciate it very much because I really do not have very much experience with these shaping/routing and related matters. Regards, Martin PS: Maybe it will be easier for you to understand what I need in the second case, if I describe why I need it. So, I need it because I want to give each regular user on the intranet the same conditions. I am afraid of people, who would put a proxy on their connection to our intranet and then used this connection for all other computers in their company or even for somebody else. That would mean that these people would steal some part of the link to Internet from the regular users and they would have worse connection to Internet even though they have not broken any rule. That is why I think of this algorithm which would shape the speed of every user (IP address) by their usual traffic. That means: if the line is free, any packet can pass, if it is not, packets from the users which generate smaller traffic will have higher priority. I hope, it could work this way, because I do not want to limit each user's monthly traffic or something like that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 17:35:11 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.scl.ameslab.gov (mailhub.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (Postfix) with ESMTP id 74F0B14CF2 for ; Wed, 31 Mar 1999 17:35:10 -0800 (PST) (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.ether.scl.ameslab.gov ([147.155.137.54]) by mailhub.scl.ameslab.gov with esmtp (Exim 1.90 #1) for net@freebsd.org id 10SWOJ-0000Nl-00; Wed, 31 Mar 1999 19:35:32 -0600 Date: Wed, 31 Mar 1999 19:34:50 -0600 From: Guy Helmer To: net@freebsd.org Subject: Interest in bringing 3C515 driver into the tree? 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 created a 3c515 driver based on the if_vx driver. I've been using it for a couple of months without problems now, although the PnP code could use some testing... Should I bring it into the source tree, or should I just make it available as an add-on? Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 17:40:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 45FB114CF2 for ; Wed, 31 Mar 1999 17:40:33 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id RAA59676; Wed, 31 Mar 1999 17:38:27 -0800 (PST) Date: Wed, 31 Mar 1999 17:38:26 -0800 (PST) From: Julian Elischer To: Martin Dvorak Cc: freebsd-net@FreeBSD.ORG Subject: Re: dynamic intelligent traffic shaping In-Reply-To: <000901be7bde$b5285cb0$5c1971c3@uvulium> 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 sounds like you want to do something like: [internet]---E1--[FreeBSD-A]---ethernet---[FreeBSD-B]---intranet using CBQ with ALTQ would allow you to allocate each user a minimum throughput and any excess would be allowed to be used on a first-come-first-served basis. this would be on hte incoming direction, queueing packets leaving FreeBSD-A. Outgoing queueing would be done on FreeBSD-B. I haven't played with Dummynet. On Thu, 1 Apr 1999, Martin Dvorak wrote: > Hi, > > I've carefully read all messages about shaping the traffic on FreeBSD system > on this mailing list and have two questions: > > 1. What is the best solution (dummynet or altq or something else) in the > following situation: FreeBSD system on Internet server (on T1), each > customer has its own IP address(es), each customer's monthly traffic has to > be kept at some level (probably by using some clever algorithm (in a script > probably), which dynamically (I suppose every hour) changes the traffic > limit on customer's IP address(es) to reach as close as possible to monthly > limit set by administrator)? That means I need to change shaping speed for > each IP address quite often but also need the system to be stable as much as > possible. > > 2. What is the best solution (dummynet or altq or something else) in the > following situation: large Internet intranet (I do not know how it is called > officialy but I mean an intranet with only one link to Internet (512kb or > more) but each computer on this intranet has its own worldwide > (non-intranet) IP address and normal (non-limited) access to Internet) with > thousands computers on this intranet, a bridge/router on the link between > the intranet and Internet. This bridge/router works like this: every > intranet packet routes in the intranet with no traffic shaping (of course), > but as for packets comming to/from Internet it should shape the traffic of > each IP to give every computer on the intranet the same speed to/from > Internet. That is the algorithm for shaping the speed of each IP address has > to be much more clever than in the first case, it has to be able to change > to shaping speed much more frequently (I guess every 5 minutes or even > fewer) while changing the speed of much more IP addresses. If not talking > about the algorithm (I will describe my idea shortly on the end of this > message), I don't even know if it is possible to do it on some acceptable > hardware configuration because I guess that only the changing of speed on > each IP address so frequently would put very high load on the system, or > not? > > Thank you very much for any though, suggestion or advice. I will appreciate > it very much because I really do not have very much experience with these > shaping/routing and related matters. > > Regards, > Martin > > > PS: > Maybe it will be easier for you to understand what I need in the second > case, if I describe why I need it. So, I need it because I want to give each > regular user on the intranet the same conditions. I am afraid of people, who > would put a proxy on their connection to our intranet and then used this > connection for all other computers in their company or even for somebody > else. That would mean that these people would steal some part of the link to > Internet from the regular users and they would have worse connection to > Internet even though they have not broken any rule. That is why I think of > this algorithm which would shape the speed of every user (IP address) by > their usual traffic. That means: if the line is free, any packet can pass, > if it is not, packets from the users which generate smaller traffic will > have higher priority. I hope, it could work this way, because I do not want > to limit each user's monthly traffic or something like that. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Mar 31 22:28:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 733A31564D; Wed, 31 Mar 1999 22:28:22 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA05117; Wed, 31 Mar 1999 23:27:43 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <370311DE.32EA2E90@softweyr.com> Date: Wed, 31 Mar 1999 23:27:42 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Dubinin Cc: freebsd-hardware@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Which ISDN card is better? References: <7756.990331@nstl.nnov.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alexander Dubinin wrote: > > Hello All! > > I need to find ISDN card, what can work with BRI ISDN line (At full > 128K transfer rate, and may be more - with compression) and is > supported by FreeBSD. That cards you can recommend? > > Next, I need to make connection via ISDN network between two local > networks, and plan to use FreeBSD for it. Is any inmpementation of > VPN software available? I want to use PTPP with dial-on-demand, and, > maybe, encryption. Have anyone good advice for this? I think we have somebody from Eicon on the freebsd-net list, perhaps he can help you. I've had good experiences with Eicon ISDN PCMCIA cards, and understand their external T/As are just as good. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 31 22:44:28 1999 Delivered-To: freebsd-net@freebsd.org Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (Postfix) with ESMTP id C75D9151AF for ; Wed, 31 Mar 1999 22:44:27 -0800 (PST) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.3/8.9.3) with ESMTP id BAA05870; Thu, 1 Apr 1999 01:43:58 -0500 (EST) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Thu, 1 Apr 1999 01:43:45 -0500 (EST) From: Jim Cassata To: GVB Cc: freebsd-net@FreeBSD.ORG Subject: Re: Apache web server tuning.. In-Reply-To: <4.1.19990331153542.00bd3a10@abused.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 Apache site has some good tips. We run standard apache and apachessl on the same machine. the ssl-enabled daemons are considerably larger, and there is no need to run so many of them. Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Wed, 31 Mar 1999, GVB wrote: > FreeBSD is the OS.... I am running Apache-SSL with FP extensions... the > server suited us fine for the load, but now with increased business the > server is starting to choke on me... It is now time to research FreeBSD > kernel tuning and Apache tuning... Anyone have any basic recommendations as > far as kernel options and things? I know thing like maxusers, somaxusers, > fd_setsize, nmbclusters.. any other places I can find some info, or some > other things I can fine tune to get more performance out of this machine? > Each httpsd process is using about 2 megs of memory... thats alot in my > book, and I'll like to decrease that... any help is appriciated.. > > Thanks in advance.. > > GVB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 1 0:18:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 313ED15E82; Thu, 1 Apr 1999 00:16:05 -0800 (PST) (envelope-from stefan@promo.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id KAA07902; Thu, 1 Apr 1999 10:15:22 +0200 (CEST) Date: Thu, 01 Apr 1999 10:15:20 +0200 From: Stefan Bethke To: Alexander Dubinin Cc: freebsd-net@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Subject: Re: Which ISDN card is better? Message-ID: <42147.3131950520@d225.promo.de> In-Reply-To: <7756.990331@nstl.nnov.ru> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alexander Dubinin wrote: > I need to find ISDN card, what can work with BRI ISDN line (At full > 128K transfer rate, and may be more - with compression) and is > supported by FreeBSD. That cards you can recommend? isdn4bsd, which is part of 3.1-RELEASE and later, supports a large number of cheap ISA and PCI cards. It's PPP implementation doesn't (yet) support compression, but otherwise you can run two 64 kbps channels at full rate on even an 486/33. > Next, I need to make connection via ISDN network between two local > networks, and plan to use FreeBSD for it. Is any inmpementation of > VPN software available? I want to use PTPP with dial-on-demand, and, > maybe, encryption. Have anyone good advice for this? Why would you need a VPN to just connect two nets via ISDN? Just put the two maschines into the two nets, and hook them up, so they route over the ISDN link. HTH, Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 1 2: 0:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (Postfix) with ESMTP id AB80014D7F for ; Thu, 1 Apr 1999 02:00:13 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id SAA25753; Thu, 1 Apr 1999 18:59:53 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98122515) with ESMTP id SAA25421; Thu, 1 Apr 1999 18:59:52 +0900 (JST) Message-Id: <199904010959.SAA25421@hotaka.csl.sony.co.jp> To: "Martin Dvorak" Cc: freebsd-net@FreeBSD.org Subject: Re: dynamic intelligent traffic shaping In-reply-to: Your message of "Thu, 01 Apr 1999 03:26:46 +0200." <000901be7bde$b5285cb0$5c1971c3@uvulium> Date: Thu, 01 Apr 1999 18:59:52 +0900 From: Kenjiro Cho Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Dvorak said: >> I've carefully read all messages about shaping the traffic on FreeBSD system >> on this mailing list and have two questions: >> 1. What is the best solution (dummynet or altq or something else) in the >> following situation: FreeBSD system on Internet server (on T1), each >> customer has its own IP address(es), each customer's monthly traffic has to >> be kept at some level (probably by using some clever algorithm (in a script >> probably), which dynamically (I suppose every hour) changes the traffic >> limit on customer's IP address(es) to reach as close as possible to monthly >> limit set by administrator)? That means I need to change shaping speed for >> each IP address quite often but also need the system to be stable as much as >> possible. Monthly quota doesn't make sense to me. Are you saying that, if a customer uses up his quota on the first day, he is not allowed to use the network for the rest of the month even when there is no load on the net? You should think about the contract between a customer and the service provider. (it is called "service level specification" in the IETF diffserv workinggroup.) >> 2. What is the best solution (dummynet or altq or something else) in the >> following situation: large Internet intranet (I do not know how it is called >> officialy but I mean an intranet with only one link to Internet (512kb or >> more) but each computer on this intranet has its own worldwide >> (non-intranet) IP address and normal (non-limited) access to Internet) with >> thousands computers on this intranet, a bridge/router on the link between >> the intranet and Internet. This bridge/router works like this: every >> intranet packet routes in the intranet with no traffic shaping (of course), >> but as for packets comming to/from Internet it should shape the traffic of >> each IP to give every computer on the intranet the same speed to/from >> Internet. That is the algorithm for shaping the speed of each IP address has >> to be much more clever than in the first case, it has to be able to change >> to shaping speed much more frequently (I guess every 5 minutes or even >> fewer) while changing the speed of much more IP addresses. If not talking >> about the algorithm (I will describe my idea shortly on the end of this >> message), I don't even know if it is possible to do it on some acceptable >> hardware configuration because I guess that only the changing of speed on >> each IP address so frequently would put very high load on the system, or >> not? Sounds like WFQ rather than shaping. Note that, to control the incoming traffic, you have to have WFQ at the other end of the Internet link. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 1 7:49:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id ED72F14FEF for ; Thu, 1 Apr 1999 07:49:36 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA15763; Thu, 1 Apr 1999 15:28:57 +0200 From: Luigi Rizzo Message-Id: <199904011328.PAA15763@labinfo.iet.unipi.it> Subject: more problems with 'de' driver and multicast... To: net@freebsd.org Date: Thu, 1 Apr 1999 15:28:57 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2384 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i don't know if anyone cares at all, but i am having a whole lot of problems with the 'de' driver and multicast. Details below -- conclusion is either help me fix these problem, or be careful when using the 'de' driver with multicast at least. cheers luigi DETAILS: I am running a rather interesting experiment on a cluster of 28 diskless machines running FreeBSD3.1R off another 3.1R server. All machines are connected to a 100mbit hub, and use a DE-based card (some have a 21140A rev.2.2, others a 21143 rev.4.1 as detected by the "de" driver). The experiment consists in running on each machine an instance of an application using layered multicast congestion control -- the relevant part for this msg is that rlc issues very frequent ADD_MEMBERSHIP/DROP_MEMBERSHIP calls. First problem is that the machines with the 21143 cards after a while stop receiving data (apparently, both multicast and unicast traffic) and do not restart unless there is some spontaneous transmission originated the machine itself. I.e. i cannot ping them from the controlling machine but have to move to the console... Second problem is that all machines -- irrespective of the type of card -- i seem to fail quite often in generating the IGMP LEAVE message when they should (i.e. according to IGMPv2 when they are the last ones who replied to a query). I suspect in both case the problem lies in some problem in the driver, specifically in handling the modifications to the address filters. This part of the code has changed significantly from 2.2 to 3.x and i don't think the new code has been tested very well. I already had and fixed a related problem (which fortunately shows up only on machines running mrouted), and the weird behaviour of the 'de' counters in netstat (try a netstat -ni and see how often does the Opkt counter changes) further reduces my confidence in the driver. So, if someone has suggestions on how to fix the code... i have at least a reasonably good testbed to try patches. -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 1 14:15:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from netshell.com.br (gabriel.netshell.com.br [200.236.148.170]) by hub.freebsd.org (Postfix) with SMTP id F01E314F31 for ; Thu, 1 Apr 1999 14:15:43 -0800 (PST) (envelope-from grios@netshell.com.br) Received: (qmail 2197 invoked from network); 1 Apr 1999 22:17:27 -0000 Received: from modem07.tdnet.com.br (HELO netshell.com.br) (200.236.148.200) by gabriel.netshell.com.br with SMTP; 1 Apr 1999 22:17:26 -0000 Message-ID: <3703F046.71756D2A@netshell.com.br> Date: Thu, 01 Apr 1999 19:16:38 -0300 From: User Grios X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: diskless Content-Type: multipart/mixed; boundary="------------C26F792B39E57AC9C94EC02B" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------C26F792B39E57AC9C94EC02B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, i am trying to get my diskless system working with FBSD, but the following error occurs: Loading freebsd.192.168.0.2... rootfs 192.168.0.1:/usr/export/slave swapfs 192.168.0.1:/usr/export/swapfs swapsize 32000 hostname slave *** RPC Error: (0,0,0): Unable to mount SWAP file system: Permission denied I read The Handbook, but there is nothing there about this error message! Any tip? Thank you for your time and cooperation! --------------C26F792B39E57AC9C94EC02B Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <3702EB49.8CFAF9CD@netshell.com.br> Date: Thu, 01 Apr 1999 00:43:05 -0300 From: User Grios X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: questions@freebsd.org Subject: Diskless Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, i am trying to get my diskless system working with FBSD, but the following error occurs: Loading freebsd.192.168.0.2... rootfs 192.168.0.1:/usr/export/slave swapfs 192.168.0.1:/usr/export/swapfs swapsize 32000 hostname slave *** RPC Error: (0,0,0): Unable to mount SWAP file system: Permission denied I read The Handbook, but there is nothing there about this error message! Any tip? Thank you for your time and cooperation! --------------C26F792B39E57AC9C94EC02B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 1 17:10:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from netshell.com.br (gabriel.netshell.com.br [200.236.148.170]) by hub.freebsd.org (Postfix) with SMTP id 74796151B9 for ; Thu, 1 Apr 1999 17:09:54 -0800 (PST) (envelope-from grios@netshell.com.br) Received: (qmail 7090 invoked from network); 2 Apr 1999 01:11:39 -0000 Received: from modem14.tdnet.com.br (HELO netshell.com.br) (200.236.148.207) by gabriel.netshell.com.br with SMTP; 2 Apr 1999 01:11:39 -0000 Message-ID: <37041918.B7E52891@netshell.com.br> Date: Thu, 01 Apr 1999 22:10:48 -0300 From: User Grios X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc To: freebsd-net@freebsd.org Subject: Diskless, please please! 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 am trying to get my diskless system working with FBSD, but the following error occurs: Loading freebsd.192.168.0.2... rootfs 192.168.0.1:/usr/export/slave swapfs 192.168.0.1:/usr/export/swapfs swapsize 32000 hostname slave *** RPC Error: (0,0,0): Unable to mount SWAP file system: Permission denied I read The Handbook, but there is nothing there about this error message! Any tip? Thank you for your time and cooperation! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 1 17:18:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E6DC14F98 for ; Thu, 1 Apr 1999 17:17:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id UAA17201 for ; Thu, 1 Apr 1999 20:17:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA70511; Thu, 1 Apr 1999 20:17:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Apr 1999 20:17:07 -0500 (EST) To: freebsd-net@freebsd.org Subject: Re: Diskless, please please! In-Reply-To: <37041918.B7E52891@netshell.com.br> References: <37041918.B7E52891@netshell.com.br> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14084.6443.591013.898926@grasshopper.cs.duke.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org User Grios writes: > Hi, i am trying to get my diskless system working with FBSD, but the > following error occurs: > > > Loading freebsd.192.168.0.2... > rootfs 192.168.0.1:/usr/export/slave > swapfs 192.168.0.1:/usr/export/swapfs > swapsize 32000 > hostname slave > *** RPC Error: (0,0,0): > Unable to mount SWAP file system: Permission denied In mountd(8), it states that you must use the -r arg to mountd and export your entire filesystem with -alldirs. Have you done both? -r Allow mount RPCs requests for regular files to be served. Al- though this seems to violate the mount protocol specification, some diskless workstations do mount requests for their swapfiles and expect them to be regular files. Since a regular file cannot be specified in /etc/exports, the entire file system in which the swapfiles resides will have to be exported with the -alldirs flag. BTW - mail to ... Host unknown (Name server: gabriel.netshell.com.br.: host not found) Cheers, ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 2 2:30:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 8265514DA1 for ; Fri, 2 Apr 1999 02:30:10 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id MAA07123; Fri, 2 Apr 1999 12:29:47 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id MAA15272; Fri, 2 Apr 1999 12:12:27 +0200 (CEST) (envelope-from andreas) Date: Fri, 2 Apr 1999 12:12:26 +0200 From: Andreas Klemm To: GVB Cc: freebsd-net@FreeBSD.ORG Subject: Re: Apache web server tuning.. Message-ID: <19990402121226.A15211@titan.klemm.gtn.com> References: <4.1.19990331153542.00bd3a10@abused.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <4.1.19990331153542.00bd3a10@abused.com>; from GVB on Wed, Mar 31, 1999 at 03:38:02PM -0800 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 31, 1999 at 03:38:02PM -0800, GVB wrote: > [...] It is now time to research FreeBSD kernel tuning > and Apache tuning... [...] For apache and FreeBSD tuning: http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml Watch your mbufs and mbuf clusters with: netstat -m 39/224 mbufs in use: 30 mbufs allocated to data 9 mbufs allocated to packet headers 26/78/4196 mbuf clusters in use (current/peak/max) 184 Kbytes allocated to network (30% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines To increase mbuf clusters use this kernel option: options NMBCLUSTERS=8192 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 2 8:39:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from bladerunner.skynetweb.com (bladerunner.skynetweb.com [208.239.240.41]) by hub.freebsd.org (Postfix) with ESMTP id 7B0D314C13 for ; Fri, 2 Apr 1999 08:39:01 -0800 (PST) (envelope-from pryker@skynetweb.com) Received: from skynetweb.com (host80.skynetweb.com [208.231.1.80] (may be forged)) by bladerunner.skynetweb.com (8.8.8/8.8.8) with ESMTP id LAA15096 for ; Fri, 2 Apr 1999 11:38:39 -0500 (EST) (envelope-from pryker@skynetweb.com) Message-ID: <3704AA7F.230EF37F@skynetweb.com> Date: Fri, 02 Apr 1999 12:31:11 +0100 From: Phillip Ryker Organization: SkyNetWEB Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Dummynet kernel config Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org List, I am trying to increase NBMCLUSTERS in the kernel config. I have put the following line in my kernel config: options "NBMCLUSTERS=4096" but it is telling me that "NBMCLUSTERS" is unrecognized?? Any help would be appreciated. thank you -- Phillip Ryker ------------------------------ | SkyNetWEB Ltd. | | 1301 S. Baylis Street | | Baltimore Maryland 21224 | | Phone: 410.563.6384 | | Fax: 410.563.5457 | ------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 2 9: 4:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.shellnet.co.uk (smtp.shellnet.co.uk [194.129.209.14]) by hub.freebsd.org (Postfix) with ESMTP id 6622614C89 for ; Fri, 2 Apr 1999 09:04:43 -0800 (PST) (envelope-from steven@shellnet.com) Received: from dial-23-01.bolton.cspace.co.uk (dial-23-01.bolton.cspace.co.uk [194.128.147.39]) by smtp.shellnet.co.uk (8.9.1/8.9.1-shellnet.stevenf) with SMTP id SAA00829; Fri, 2 Apr 1999 18:04:11 +0100 (BST) Posted-Date: Fri, 2 Apr 1999 18:04:11 +0100 (BST) From: steven@shellnet.com (Steven Fletcher) To: Phillip Ryker Cc: freebsd-net@freebsd.org Subject: Re: Dummynet kernel config Date: Fri, 02 Apr 1999 17:04:09 GMT Message-ID: <3705f81a.82341076@smtp.shellnet.co.uk> References: <3704AA7F.230EF37F@skynetweb.com> In-Reply-To: <3704AA7F.230EF37F@skynetweb.com> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 02 Apr 1999 12:31:11 +0100, you wrote: >but it is telling me that "NBMCLUSTERS" is unrecognized?? You spelt it wrong. Try NMBCLUSTERS instead. Steven Fletcher steven@shellnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 2 11:24:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (Postfix) with ESMTP id 7D19E14CA9 for ; Fri, 2 Apr 1999 11:24:16 -0800 (PST) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.3/8.9.3) with ESMTP id OAA09349; Fri, 2 Apr 1999 14:23:47 -0500 (EST) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Fri, 2 Apr 1999 14:23:47 -0500 (EST) From: Jim Cassata To: Phillip Ryker Cc: freebsd-net@FreeBSD.ORG Subject: Re: Dummynet kernel config In-Reply-To: <3704AA7F.230EF37F@skynetweb.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 try options NMBCLUSTERS :) Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Fri, 2 Apr 1999, Phillip Ryker wrote: > List, > > I am trying to increase NBMCLUSTERS in the kernel config. I have put > the following line in my kernel config: > > options "NBMCLUSTERS=4096" > > but it is telling me that "NBMCLUSTERS" is unrecognized?? > > Any help would be appreciated. > > thank you > -- > Phillip Ryker > ------------------------------ > | SkyNetWEB Ltd. | > | 1301 S. Baylis Street | > | Baltimore Maryland 21224 | > | Phone: 410.563.6384 | > | Fax: 410.563.5457 | > ------------------------------ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 2 11:54:26 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail1.WorldMediaCo.com (unknown [207.252.121.17]) by hub.freebsd.org (Postfix) with ESMTP id 9FD8B14CAA for ; Fri, 2 Apr 1999 11:54:02 -0800 (PST) (envelope-from opsys@omaha.com) Received: from fbsdrouter ([207.252.121.18]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with SMTP id com; Fri, 2 Apr 1999 13:43:50 -0600 Date: Fri, 2 Apr 1999 13:53:42 -0600 (CST) From: opsys@omaha.com (opsys) X-Sender: opsys@fbsdrouter To: Phillip Ryker Cc: freebsd-net@FreeBSD.ORG Subject: Re: Dummynet kernel config In-Reply-To: <3704AA7F.230EF37F@skynetweb.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 Thats because its NMBCLUSTERS not NBMCLUSTERS. :-) Chris World Media Co. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 3 7:12:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from sims-ha.videotron.net (faure.videotron.net [205.151.222.100]) by hub.freebsd.org (Postfix) with ESMTP id 93BA514D01 for ; Sat, 3 Apr 1999 07:12:48 -0800 (PST) (envelope-from pcbroch@videotron.ca) Received: from shark ([207.96.177.9]) by sims-ha.videotron.net (Sun Internet Mail Server sims.3.5.1998.03.08.20.27) with SMTP id <0F9M007LCCT76N@sims-ha.videotron.net> for freebsd-net@FreeBSD.ORG; Sat, 3 Apr 1999 10:10:20 -0500 (EST) Date: Sat, 03 Apr 1999 10:14:41 -0500 From: Patrick Brochu Subject: Problem pinging To: freebsd-net@FreeBSD.ORG Message-id: <000501be7de4$b290c480$0201a8c0@shark> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 5.00.2014.211 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 References: <4.1.19990331153542.00bd3a10@abused.com> <19990402121226.A15211@titan.klemm.gtn.com> X-Priority: 3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all: I have my FreeBSD box connected to the internet via ed1 using DHCP to get it's configuration. All works well, the interface gets configured properly and i can use it. ifconfig -a ed1: flags=8843 mtu 1500 inet 207.96.177.9 netmask 0xffffff00 broadcast 207.96.177.255 ether 00:00:b4:9c:c0:97 ed0: flags=8843 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:00:e8:cf:e3:d7 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 My problem is when i try to ping it. I get the following: /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt /kernel: arplookup 127.0.0.1 failed, could not allocate llinfo Any idea what this might be? ping any_other_name works just fine. ----- Original Message ----- From: Andreas Klemm To: GVB Cc: Sent: Friday, April 02, 1999 5:12 AM Subject: Re: Apache web server tuning.. > On Wed, Mar 31, 1999 at 03:38:02PM -0800, GVB wrote: > > [...] It is now time to research FreeBSD kernel tuning > > and Apache tuning... [...] > > For apache and FreeBSD tuning: > > http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml > > Watch your mbufs and mbuf clusters with: > > netstat -m > > 39/224 mbufs in use: > 30 mbufs allocated to data > 9 mbufs allocated to packet headers > 26/78/4196 mbuf clusters in use (current/peak/max) > 184 Kbytes allocated to network (30% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > To increase mbuf clusters use this kernel option: > > options NMBCLUSTERS=8192 > > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > http://www.freebsd.org/~fsmp/SMP/SMP.html > powered by Symmetric MultiProcessor FreeBSD > > > 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 Mon Apr 5 13:17:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from gateway.schneider.com (mailgate1.schneider.com [207.67.105.2]) by hub.freebsd.org (Postfix) with SMTP id 41CA41547C for ; Mon, 5 Apr 1999 13:17:49 -0700 (PDT) (envelope-from WAYNEK@SCHNEIDER.COM) Received: from SMTPGW1.schneider.com by gateway.schneider.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 5 Apr 1999 19:38:46 UT Date: Mon, 05 Apr 1999 15:03 -0600 From: "Wayne, Ken" To: freebsd-net@freebsd.org Subject: PPP Dialup Message-ID: <1D4CF651E2DBD211A34F00805F31EA72@SCHNEIDER.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excuse me if I am not doing this correctly, it's my first time sending to this list. I am trying to setup my FreeBSD box to answer incoming calls and establish a PPP connection. I've followed the manual to the best of my knowledge but at this point can't even get the modem to pick up the phone line. I've done this many times with '95 and NT and (although by default I don't have it setup to do this)I can dial out from my BSD box with the same modem if I want , so I don't think it has anything to do with my phone lines or hardware. Any suggestions, or pointers to any "how to's" would be greatly appreciated. Thanks, -Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 5 22:45:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 703AF14C12; Mon, 5 Apr 1999 22:45:35 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com ([204.68.178.37]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA19255; Mon, 5 Apr 1999 23:43:26 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <37099037.B4643579@softweyr.com> Date: Mon, 05 Apr 1999 22:40:23 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Wayne, Ken" Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: PPP Dialup References: <1D4CF651E2DBD211A34F00805F31EA72@SCHNEIDER.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Wayne, Ken" wrote: > > Excuse me if I am not doing this correctly, it's my first time sending to > this list. You're fine. Questions about how to setup and use FreeBSD will probably get more response from the freebsd-questions mailing list, even if they are about networking. That's the general "how do I?" mailing list. > I am trying to setup my FreeBSD box to answer incoming calls and establish a > PPP connection. I've followed the manual to the best of my knowledge but at > this point can't even get the modem to pick up the phone line. I've done > this many times with '95 and NT and (although by default I don't have it > setup to do this)I can dial out from my BSD box with the same modem if I want > , so I don't think it has anything to do with my phone lines or hardware. > > Any suggestions, or pointers to any "how to's" would be greatly appreciated. Have you read http://www.daemonnews.org/199901/freeras.html yet? It's not exactly a tutorial, but might give you some good ideas as to where to look for more help. I might be somewhat biased about how helpful it is, though. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 6 17:48: 3 1999 Delivered-To: freebsd-net@freebsd.org Received: from grafica.co.nz (prometheus.grafica.co.nz [203.96.151.13]) by hub.freebsd.org (Postfix) with ESMTP id C0DCA151C6 for ; Tue, 6 Apr 1999 17:47:58 -0700 (PDT) (envelope-from keith@grafica.co.nz) Received: from grafica.co.nz (localhost.grafica.co.nz [127.0.0.1]) by grafica.co.nz (8.9.3/8.9.3) with ESMTP id MAA02798 for ; Wed, 7 Apr 1999 12:47:18 +1200 (NZST) Message-ID: <370AAB14.D93409F2@grafica.co.nz> Date: Wed, 07 Apr 1999 12:47:16 +1200 From: Keith Newton Organization: Graphic Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: IP accounting and NATD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, sorry to pose a question that I am sure has been asked before, but I have sifted through hundreds of mailing list posting and usenet postings and nobody has asked this question quite along the lines that I am needing. So here goes.... The deal is I have a FreeBSD machine with two ethernet cards in it, fxp0 and de0. The fxp0 is attached to and internal LAN using 192.168.2.XXX the de0 interface is connected to the internet. At the moment all traffic passes through NATD to get from the LAN to the INET and vica versa. the rules in the firewall are /sbin/ipfw add divert natd all from any to any via de0 /sbin/ipfw add pass all from any to any Now this is fine and works. I on the other hand want to do IP accounting of the traffic passing from specific computers on the LAN to the outside world using NATD. So I tried the following rules /sbin/ipfw -f flush /sbin/ipfw add 1001 divert natd all from 192.168.2.1 to any via de0 /sbin/ipfw add 1002 divert natd all from any to 192.168.2.1 via de0 /sbin/ipfw add 1011 divert natd all from 192.168.2.2 to any via de0 /sbin/ipfw add 1012 divert natd all from any to 192.168.2.2 via de0 /sbin/ipfw add 1021 divert natd all from 192.168.2.3 to any via de0 /sbin/ipfw add 1022 divert natd all from any to 192.168.2.3 via de0 /sbin/ipfw add 1031 divert natd all from 192.168.2.101 to any via de0 /sbin/ipfw add 1032 divert natd all from any to 192.168.2.101 via de0 /sbin/ipfw add 1041 divert natd all from 192.168.2.102 to any via de0 /sbin/ipfw add 1042 divert natd all from any to 192.168.2.102 via de0 ...... ..... ...... ...... /sbin/ipfw add 1201 allow all from any to any for all the machines on the LAN that need outside access, the next step should this have worked was to filter for the protocols (port numbers) and then to write a script to read the info from a set of files. Now the above didn't work Does anyone have any pointers, I feel like I am stabbing around in the dark missing one obvious thing. Thanks in advance, Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 6 19:17: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A587B15252 for ; Tue, 6 Apr 1999 19:17:02 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id TAA23719 for ; Tue, 6 Apr 1999 19:12:26 -0700 (PDT) Date: Tue, 6 Apr 1999 19:12:24 -0700 (PDT) From: Julian Elischer To: net@freebsd.org Subject: Coping with 1000s of W95 clients. 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 The windows world has given us teh wonderful legacy of coping with clients that have their TCP stack as a program library, so that if the program crashes or doesn't make the right calls, the TCP session can be left in a bad state. The 'canonical example' is Win95 machines that don't "shutdown()" the TCP session before exiting. In the following situation you are left wit an entry on your server sitting in FIN_WAIT_2 state. client: Some action that causes the server do a 'shutdown()' on its socket. (e.g. bad input, or "Quit") server: shutdown(). (results in FIN sent to client) client: Receive and ACK the FIN (the stack does this, and returns EOF to Bthe app. client: Exit() (after all its got EOF) (or worse, user powers it down). server: recieves the ACK and waits forever in FIN_WAIT_2 hoping to get a FIN from the now defunct process. The BSD4.3 hack is to have a (11 minute, 15 second) timeout on FIN_WAIT_2 state **IF THE LOCAL END HAS DONE A FULL CLOSE**. A notable example of this sees to be the APACHE server that actually does a 'shutdown()' first, rather than a close(), thus making it's session immune to the timeout. Even if it does a close() the FIN_WAIT_2 state is held for 11.25 minutes. It is possible for a badly behaved set of clients to bring a server to its knees in that time by creating tons of such sessions. The actual test for deciding whether to time-out FIN_WAIT_2 is: if (so->so_state & SS_CANTRCVMORE) {} which is NOT set by a shutdown() (half-close), only a close(). Anyway the point is that eventually you end up with a LOT of sessions stuck in FIN_WAIT_2 state. The only way to stop this is to break the standard, as this would be correct behaviour by the server. After a discussion with Paul Vixie a long time ago, We have written some code to try and reduce this problem. Machines that truely 'die' still wait around for a while, but badly behaved apps will eact (in general) to this by sending a RST (or rather their OS will), giving us permission to purge the session. Basically, any session that is still in FIN_WAIT_2 after 30 seconds reverts to FIN_WAIT_1, and resends the FIN. I believe that this is similar to a fix Paul Vixie mentionned implementing in NetBSD once. If the machine has gone south, FIN_WAIT_1 will time out. If it's still there, but the App is gone, we'll get a RST. If the App is still alive, we'll get an ACK again. Here's the patch for discussion: Ignore the 2 cosmetic changes :-) I wouldn't mind including this as an option, to allow FreeBSD to better handle 1000s of Usoft clients and stupid users. julian Index: tcp_fsm.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_fsm.h,v retrieving revision 1.10 diff -c -r1.10 tcp_fsm.h *** tcp_fsm.h 1997/08/16 19:15:38 1.10 --- tcp_fsm.h 1999/04/07 01:29:22 *************** *** 71,80 **** * if all data queued for output is included in the segment. */ static u_char tcp_outflags[TCP_NSTATES] = { ! TH_RST|TH_ACK, 0, TH_SYN, TH_SYN|TH_ACK, ! TH_ACK, TH_ACK, ! TH_FIN|TH_ACK, TH_ACK, TH_FIN|TH_ACK, TH_ACK, TH_ACK, ! }; #endif #ifdef KPROF --- 71,88 ---- * if all data queued for output is included in the segment. */ static u_char tcp_outflags[TCP_NSTATES] = { ! TH_RST|TH_ACK, /* 0, CLOSED */ ! 0, /* 1, LISTEN */ ! TH_SYN, /* 2, SYN_SENT */ ! TH_SYN|TH_ACK, /* 3, SYN_RECEIVED */ ! TH_ACK, /* 4, ESTABLISHED */ ! TH_ACK, /* 5, CLOSE_WAIT */ ! TH_FIN|TH_ACK, /* 6, FIN_WAIT_1 */ ! TH_ACK, /* 7, CLOSING */ ! TH_FIN|TH_ACK, /* 8, LAST_ACK */ ! TH_ACK, /* 9, FIN_WAIT_2 */ ! TH_ACK, /* 10, TIME_WAIT */ ! }; #endif #ifdef KPROF Index: tcp_input.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_input.c,v retrieving revision 1.84 diff -c -r1.84 tcp_input.c *** tcp_input.c 1999/02/06 00:47:45 1.84 --- tcp_input.c 1999/04/07 01:29:22 *************** *** 1495,1504 **** --- 1495,1526 ---- * specification, but if we don't get a FIN * we'll hang forever. */ + #ifdef TCP_USOFT_BUG + /* + * Wait longer and longer for the other + * end to respond with something. + * Eventually they should either + * RST or FIN. If they are still alive + * and actually want us to remain in this + * state, they will keep ACKing and + * we'll stay here indefinitly. + * If they don't respond at all, we will + * revert to FIN_WAIT_1 and eventually + * time out as it would. How to cope with + * the case of broken clients who are still + * alive but never FIN is arguable. Certainly + * if we've closed our end entirely, we + * might as well just close the connection. + */ + tp->t_timer[TCPT_2MSL] = + ((tp->t_idle > TCPTV_MSL) ? + tp->t_idle : TCPTV_MSL); + #else /* TCP_USOFT_BUG */ if (so->so_state & SS_CANTRCVMORE) { soisdisconnected(so); tp->t_timer[TCPT_2MSL] = tcp_maxidle; } + #endif /* TCP_USOFT_BUG */ tp->t_state = TCPS_FIN_WAIT_2; } break; Index: tcp_output.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_output.c,v retrieving revision 1.32 diff -c -r1.32 tcp_output.c *** tcp_output.c 1999/01/20 17:31:59 1.32 --- tcp_output.c 1999/04/07 01:29:23 *************** *** 128,134 **** * clear the FIN bit. Usually this would * happen below when it realizes that we * aren't sending all the data. However, ! * if we have exactly 1 byte of unset data, * then it won't clear the FIN bit below, * and if we are in persist state, we wind * up sending the packet without recording --- 128,134 ---- * clear the FIN bit. Usually this would * happen below when it realizes that we * aren't sending all the data. However, ! * if we have exactly 1 byte of unsent data, * then it won't clear the FIN bit below, * and if we are in persist state, we wind * up sending the packet without recording Index: tcp_timer.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_timer.c,v retrieving revision 1.28 diff -c -r1.28 tcp_timer.c *** tcp_timer.c 1998/04/24 09:25:35 1.28 --- tcp_timer.c 1999/04/07 01:29:23 *************** *** 213,222 **** * control block. Otherwise, check again in a bit. */ case TCPT_2MSL: ! if (tp->t_state != TCPS_TIME_WAIT && ! tp->t_idle <= tcp_maxidle) ! tp->t_timer[TCPT_2MSL] = tcp_keepintvl; ! else tp = tcp_close(tp); break; --- 213,245 ---- * control block. Otherwise, check again in a bit. */ case TCPT_2MSL: ! if (tp->t_state != TCPS_TIME_WAIT ! && tp->t_idle <= tcp_maxidle) { ! #ifdef TCP_USOFT_BUG ! if (tp->t_state == TCPS_FIN_WAIT_2) { ! /* ! * We've timed out waiting for the other end ! * to finish up. Quite possibly it's a Win9x ! * machine. ! * If so we could be waiting here forever. ! * Pretend we were never ack'd and reset ! * ourselves to a retry of FIN_WAIT_1. If ! * it's still alive, this should at least ! * elicit a RST from it which ! * will let us know we can shut down. ! * If it has only done a half close, ! * it'll ACK our retries so we'll ! * keep waiting in FIN_WAIT_2. ! * If it's dead, we'll time out. ! */ ! tp->t_state = TCPS_FIN_WAIT_1; ! tp->t_flags &= ~TF_SENTFIN; ! tp->snd_una = (tp->snd_nxt -= 1); ! tcp_output(tp); ! } else ! #endif ! tp->t_timer[TCPT_2MSL] = tcp_keepintvl; ! } else tp = tcp_close(tp); break; xxxxxxxxxxend of patchxxxxxx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 6 20: 6:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from gw.caamora.com.au (jonath5.lnk.telstra.net [139.130.41.237]) by hub.freebsd.org (Postfix) with ESMTP id 77C14151BF for ; Tue, 6 Apr 1999 20:06:24 -0700 (PDT) (envelope-from jon@gw.caamora.com.au) Received: (from jon@localhost) by gw.caamora.com.au (8.8.8/8.8.8) id NAA10236; Wed, 7 Apr 1999 13:04:21 +1000 (EST) (envelope-from jon) Message-ID: <19990407130420.I9649@caamora.com.au> Date: Wed, 7 Apr 1999 13:04:20 +1000 From: jonathan michaels To: "Wayne, Ken" , freebsd-net@FreeBSD.ORG Subject: Re: PPP Dialup Mail-Followup-To: "Wayne, Ken" , freebsd-net@FreeBSD.ORG References: <1D4CF651E2DBD211A34F00805F31EA72@SCHNEIDER.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <1D4CF651E2DBD211A34F00805F31EA72@SCHNEIDER.COM>; from Wayne, Ken on Mon, Apr 05, 1999 at 03:03:00PM -0600 X-Operating-System: FreeBSD gw.caamora.com.au 2.2.7-RELEASE i386 X-Mood: i'm alive, if it counts Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 05, 1999 at 03:03:00PM -0600, Wayne, Ken wrote: > Any suggestions, or pointers to any "how to's" would be greatly appreciated. try reading teh ppp pedantic primer, or teh man page by brian@awfulhak .. (sorry, brian) like that. thier are two ways to get ppp to act as a server and brain dealts in detail with both. teh frist one uses getty teh other uses mgetty+sendfax. the firs one is just a few tables modified abd a couple of gotachs in teh modem taken care off (e1 and v1, but read teh man page). using mgetty+sendfax package is far mor complicated but give you a host ove very flrxible options .. if you want to setup a ras type device, tehn mgetty+sendfax would be a good place to start (for a pstn style permanent and dialup modem ras setup, i'm not sure it it will handle teh isdn specific issues). in clossing, i've use teh simple getty mode woth goodeffect, and even tried the mgetty+sendfax package but got bowled over by my dsylexia and several other issues that cause teh weird spelling that you will no doubt second guess at. i would apreciate not being remindered i need a spellinv checker, most of these thngs are wriotten by people who don;t understand how dsylexia works. by the way, one more item teh mailing list freebsd-isp has teh kind of people that use this kind of stuff and so shoudl be able to help you if you need further help in this matter. regards jonathan, not so pretending to be a broccolli today. -- =============================================================================== Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 7 1:18:34 1999 Delivered-To: freebsd-net@freebsd.org Received: from osku.suutari.iki.fi (unknown [195.165.67.179]) by hub.freebsd.org (Postfix) with ESMTP id 025CC155FF for ; Wed, 7 Apr 1999 01:18:21 -0700 (PDT) (envelope-from ari@suutari.iki.fi) Received: from suutari.iki.fi (mocha.intranet.syncrontech.com [192.168.2.3]) by osku.suutari.iki.fi (8.9.1/8.9.1) with ESMTP id LAA23867; Wed, 7 Apr 1999 11:15:42 +0300 (EEST) (envelope-from ari@suutari.iki.fi) Message-ID: <370B152D.ACEF8847@suutari.iki.fi> Date: Wed, 07 Apr 1999 11:19:57 +0300 From: ari X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Keith Newton Cc: freebsd-net@FreeBSD.ORG Subject: Re: IP accounting and NATD References: <370AAB14.D93409F2@grafica.co.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Keith Newton wrote: > > > /sbin/ipfw add 1001 divert natd all from 192.168.2.1 to any via de0 > /sbin/ipfw add 1002 divert natd all from any to 192.168.2.1 via de0 I guess that incoming packets will not match this line, since they are not coming to 192.168.2.1 but to the address of de0. So you'll need something like 'divert natd all from any to any via de0 in' and something else to do accounting for incoming packets. Ari S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 7 1:44:53 1999 Delivered-To: freebsd-net@freebsd.org Received: from mx01.iafrica.com.na (mx01.iafrica.com.na [196.31.227.173]) by hub.freebsd.org (Postfix) with ESMTP id B7B0815655 for ; Wed, 7 Apr 1999 01:44:30 -0700 (PDT) (envelope-from tim@iafrica.com.na) Received: from dup80-whk.iafrica.com.na ([196.20.4.149] helo=aptiva) by mx01.iafrica.com.na with smtp (Exim 2.11 #1) id 10Unuo-0009U2-00 for freebsd-net@FreeBSD.ORG; Wed, 7 Apr 1999 10:42:30 +0200 Message-ID: <370B1A5F.3FAC@iafrica.com.na> Date: Wed, 07 Apr 1999 10:42:07 +0200 From: Tim Priebe Reply-To: tim@iafrica.com.na X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: vlans 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 have been trying to setup a Firewall for our Polytechnic, but am having trouble finding much documentation on VLANs. I found the VLAN code, and then a few messages in the arcives to this list. If there is a difinitive document on on VLANs under FreeBSD, or someone working on one, where can I find it. Otherwise, I would like to get this firewall working with VLANs, and then prepare a document on setting up VLANs under FreeBSD. If anyone has anyone has any information, suggestions, or software that they would be willing to share in regards to this, could they please send them to me. Thanks, Tim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 7 4:47: 9 1999 Delivered-To: freebsd-net@freebsd.org Received: from grafica.co.nz (prometheus.grafica.co.nz [203.96.151.13]) by hub.freebsd.org (Postfix) with ESMTP id 9866014C8C for ; Wed, 7 Apr 1999 04:47:05 -0700 (PDT) (envelope-from keith@grafica.co.nz) Received: from grafica.co.nz (prometheus.grafica.co.nz [192.168.2.42]) by grafica.co.nz (8.9.3/8.9.3) with SMTP id XAA06259; Wed, 7 Apr 1999 23:45:51 +1200 (NZST) From: "Keith Newton" Reply-To: keith@grafica.co.nz To: ari Cc: freebsd-net@FreeBSD.ORG Date: Wed, 7 Apr 1999 23:45:58 -1200 Subject: Re: IP accounting and NATD X-Mailer: DMailWeb Web to Mail Gateway 2.0p, http://netwinsite.com/top_mail.htm Message-id: <370b4576.1870.0@grafica.co.nz> X-User-Info: 202.36.204.137 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi, > >Keith Newton wrote: >> >> >> /sbin/ipfw add 1001 divert natd all from 192.168.2.1 to any via de0 >> /sbin/ipfw add 1002 divert natd all from any to 192.168.2.1 via de0 > >=09I guess that incoming packets will not match this line, since >=09they are not coming to 192.168.2.1 but to the address of de0. >=09So you'll need something like 'divert natd all from any to any via de0 >in' >=09and something else to do accounting for incoming packets. > > >=09=09Ari S. > Thanks, I have experimented further and may have something, do you know of a person whom I could contact so that my endeavors could be reshaped into something everyone could use. Thanks, Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 8 2:33:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from fep02-svc.tin.it (mta02-acc.tin.it [212.216.176.33]) by hub.freebsd.org (Postfix) with ESMTP id 0E54F15935 for ; Thu, 8 Apr 1999 02:33:19 -0700 (PDT) (envelope-from molter@tin.it) Received: from nympha.ecomotor.it ([212.216.21.74]) by fep02-svc.tin.it (InterMail v4.0 201-221-105) with SMTP id <19990408093114.BNMN21723.fep02-svc@nympha.ecomotor.it> for ; Thu, 8 Apr 1999 11:31:14 +0200 Received: (qmail 6260 invoked by uid 1000); 8 Apr 1999 09:30:28 -0000 From: "Marco Molteni" Date: Thu, 8 Apr 1999 11:30:28 +0200 (CEST) X-Sender: molter@localhost To: freebsd-net@freebsd.org Subject: typo in the man page for listen(2) 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, while reading the man page for the listen system call on a FreeBSD 3.1-RELEASE box, I noticed (what I think is) a typo: it refers to a non existent sysctl variable ``kern.somaxconn'' while it should be ``kern.ipc.somaxconn''. Here is the patch against the man page; could someone commit it? Marco --- /usr/src/lib/libc/sys/listen.2 Fri Apr 11 20:47:06 1997 +++ listen.2 Thu Apr 8 11:17:47 1999 @@ -74,15 +74,15 @@ The .Xr sysctl 3 MIB variable -.Dq Li kern.somaxconn +.Dq Li kern.ipc.somaxconn specifies a hard limit on .Fa backlog ; if a value greater than -.Li kern.somaxconn +.Li kern.ipc.somaxconn or less than zero is specified, .Fa backlog is silently forced to -.Li kern.somaxconn . +.Li kern.ipc.somaxconn . .Sh IMPLEMENTATION NOTES .Pp In the non-threaded library To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 8 8:27:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from redbox.venux.net (redbox.venux.net [216.47.238.10]) by hub.freebsd.org (Postfix) with ESMTP id 5A20414ECD for ; Thu, 8 Apr 1999 08:27:44 -0700 (PDT) (envelope-from matthew@venux.net) Received: from thunder (net177138.hcv.com [209.153.177.138]) by redbox.venux.net (Postfix) with SMTP for id 079B82E20B; Thu, 8 Apr 1999 11:25:37 -0400 (EDT) Message-Id: <4.1.19990408111724.00a55620@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 08 Apr 1999 11:25:50 -0400 To: freebsd-net@freebsd.org From: Matthew Hagerty Subject: Proxy and NATd, possible to run both? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I was wondering if it is possible to run both a proxy and NATd on the same box? I am trying to use programs like NetMeeting and ICQ on my internal machines, but they don't work so hot behind a NATd server. However, both programs (NetMeeting and ICQ) can be used through a proxy server, but I am still a little fuzzy on the difference between the two (proxy and NATd). To use a proxy server do my internal computers require real IP addresses or can I use the 10.x.x.x with a proxy server? I was going to start looking into (what's it called, SOCKS?) but I would like to know if something like this will work before I pull my hair out trying to get the system to do something that is not possible. Thanks, Matthew Hagerty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 8 18:28:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from kaa.kfunigraz.ac.at (KAA-ATM.kfunigraz.ac.at [143.50.202.22]) by hub.freebsd.org (Postfix) with ESMTP id C802915A2E for ; Thu, 8 Apr 1999 18:25:17 -0700 (PDT) (envelope-from dada@balu.kfunigraz.ac.at) Received: from balu.kfunigraz.ac.at (balu [143.50.16.16]) by kaa.kfunigraz.ac.at (8.9.2/8.9.2) with ESMTP id DAA28327; Fri, 9 Apr 1999 03:23:04 +0200 (MDT) Received: from localhost.kfunigraz.ac.at (IDENT:K6yQVU3oi7a80kZKgw8vcB5njAxIJYDv@BONLINEA21.kfunigraz.ac.at [143.50.36.21]) by balu.kfunigraz.ac.at (8.9.2/8.9.2) with ESMTP id DAA29029; Fri, 9 Apr 1999 03:23:00 +0200 (MDT) Received: from localhost (PYU6vulXczw+uIp/3lVytxrEL7TTHQYV@localhost.kfunigraz.ac.at [127.0.0.1]) by localhost.kfunigraz.ac.at (8.8.8/8.8.8) with SMTP id DAA00758; Fri, 9 Apr 1999 03:18:25 +0200 (CEST) (envelope-from dada@localhost.kfunigraz.ac.at) Date: Fri, 9 Apr 1999 03:18:23 +0200 (CEST) From: Martin Kammerhofer Reply-To: Martin Kammerhofer To: Julian Elischer Cc: freebsd-net@FreeBSD.ORG Subject: Re: Coping with 1000s of W95 clients. 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 Tue, 6 Apr 1999, Julian Elischer wrote: > > The 'canonical example' is Win95 machines that > don't "shutdown()" the TCP session before exiting. > In the following situation you are left wit an entry on your server > sitting in FIN_WAIT_2 state. > Even FreeBSD boxes are causing this :(. I see this every day on my home box where a local apache and a netscape browser are running. HTTP 1.1 introduced keepalive connections where the server keeps the connection open for some 15 sec after servicing the request(s). The idea was to cut down on connection setup overhead. If a client has to open for each of dozens of inlined GIFs contained in a page a new TCP connection (as it was the case with HTTP 1.0) performance will suffer. Now when the server closes the connection after no further request came in for 15sec a FIN will be sent and acknowledged from the browser's OS. After that the server's TCP is in FIN_WAIT_2 state and the browser's in CLOSE_WAIT. If the browser would periodically check his sockets, read zero length from them, notice that the server closed and close the socket too, all would be fine. Unfortunately browsers like Netscape (at least up to 4.08) just sit idle until the user accesses her next webpage - maybe idling for days! The problem is well known, those having installed apache from the FreeBSD ports collection can read about it in file:/usr/local/share/doc/apache/manual/misc/fin_wait_2.html . > > The BSD4.3 hack is to have a (11 minute, 15 second) timeout on FIN_WAIT_2 > state **IF THE LOCAL END HAS DONE A FULL CLOSE**. A notable example of If an application really does shut down _only_ the socket's output side with shutdown(socket,how=1) then it wants to keep the socket open for further reads! Timing out a half duplex connection is plain wrong. The timeout is actually tcp_maxidle = tcp_keepcnt * tcp_keepintvl; Keepcnt is 8 (hard coded) and keepintvl is settable by sysctl (net.inet.tcp.keepintvl). Eight times the default keepintvl of 150 is 1200 or 10 minutes. (Those TCP timers run with 2 Hz.) Because - the idle time counter is incremented _after_ the timer is run, - and the condition for waiting another 75sec (=keepintvl) is ``tp->t_idle<= tcp_maxidle'' instead of ``tp->t_idle < tcp_maxidle'' another keepintvl is added so it's 9 * 75 = 675sec total. > > The only way to stop this is to break the standard, as this would be FreeBSD's 675sec timeout on FIN_WAIT_2 is already breaking RFC 793. > Basically, any session that is still in FIN_WAIT_2 after 30 seconds > reverts to FIN_WAIT_1, and resends the FIN. I believe that > this is similar to a fix Paul Vixie mentionned implementing in NetBSD > once. > I don't think is a good solution. Retransmitting the FIN certainly doesn't break the spec, but it won't help much. If there were dead browsers ``on the other side'' of all those annoying FIN_WAIT_2 sockets, then retransmitting and getting ACKs or RSTs would certainly help. But in most cases there is a browser just waiting for user actions! Resending the FIN would accomplish nothing in this case. The browsers TCP stack would reacknowledge the FIN and continue hanging around in CLOSE_WAIT. I guess the percentage of cases where you get a RST or ICMP is quite low and not worth the increase in net traffic. The easy solution to shorten FIN_WAIT_2 is simple: sysctl -w net.inet.tcp.keepintvl=27 This would give you a FIN_WAIT_2 timeout of 9 * 27 / 2 = 121.5 sec This should cut down the number of FW2 sockets by a factor of 675/121 = 5.6 . The only drawback to this solution is, that keepalives won't work reliably any more. (I'm referring to the transport layer keepalives here, _not_ the HTTP 1.1 application layer keepalives). After 2 hours idle time there would be only a 2 min time window to respond before a keepalive connection is dropped. This leads me two solution 2: Just introduce a configurable timeout for idle finwait2 sockets. This is a quite small change and less intrusive than your suggestion. Those who have so many hits that finwait2 sockets pile up could just lower the finwait2 timeout. Martin Index: netinet/tcp_input.c =================================================================== RCS file: /home/dada/cvsroot/src/netinet/tcp_input.c,v retrieving revision 1.3 diff -u -u -r1.3 tcp_input.c --- tcp_input.c 1999/04/06 19:28:25 1.3 +++ tcp_input.c 1999/04/08 22:17:58 @@ -1496,7 +1496,7 @@ */ if (so->so_state & SS_CANTRCVMORE) { soisdisconnected(so); - tp->t_timer[TCPT_2MSL] = tcp_maxidle; + tp->t_timer[TCPT_2MSL] = tcp_finwait2idle; } tp->t_state = TCPS_FIN_WAIT_2; } Index: netinet/tcp_timer.c =================================================================== RCS file: /home/dada/cvsroot/src/netinet/tcp_timer.c,v retrieving revision 1.4 diff -u -u -r1.4 tcp_timer.c --- tcp_timer.c 1999/04/08 12:15:01 1.4 +++ tcp_timer.c 1999/04/08 23:34:49 @@ -85,6 +85,10 @@ SYSCTL_INT(_net_inet_tcp, TCPCTL_KEEPINTVL, keepintvl, CTLFLAG_RW, &tcp_keepintvl , 0, ""); +int tcp_finwait2idle = TCPTV_FINWAIT2IDLE; +SYSCTL_INT(_net_inet_tcp, TCPCTL_FINWAIT2IDLE, finwait2idle, + CTLFLAG_RW, &tcp_finwait2idle , 0, ""); + static int always_keepalive = 0; SYSCTL_INT(_net_inet_tcp, OID_AUTO, always_keepalive, CTLFLAG_RW, &always_keepalive , 0, ""); @@ -162,6 +166,10 @@ tp = intotcpcb(ip); if (tp == 0 || tp->t_state == TCPS_LISTEN) continue; + tp->t_idle++; + tp->t_duration++; + if (tp->t_rtt) + tp->t_rtt++; for (i = 0; i < TCPT_NTIMERS; i++) { if (tp->t_timer[i] && --tp->t_timer[i] == 0) { #ifdef TCPDEBUG @@ -180,10 +188,6 @@ #endif } } - tp->t_idle++; - tp->t_duration++; - if (tp->t_rtt) - tp->t_rtt++; tpgone: ; } @@ -235,10 +239,13 @@ */ case TCPT_2MSL: if (tp->t_state != TCPS_TIME_WAIT && - tp->t_idle <= tcp_maxidle) + tp->t_idle < tcp_finwait2idle) tp->t_timer[TCPT_2MSL] = tcp_keepintvl; - else + else { + if (tp->t_state == TCPS_FIN_WAIT_2) + tcpstat.tcps_finwait2drops++; tp = tcp_close(tp); + } break; /* Index: netinet/tcp_timer.h =================================================================== RCS file: /home/dada/cvsroot/src/netinet/tcp_timer.h,v retrieving revision 1.1 diff -u -u -r1.1 tcp_timer.h --- tcp_timer.h 1999/04/02 01:15:25 1.1 +++ tcp_timer.h 1999/04/08 22:13:15 @@ -101,6 +101,8 @@ #define TCPTV_KEEPINTVL ( 75*PR_SLOWHZ) /* default probe interval */ #define TCPTV_KEEPCNT 8 /* max probes before drop */ +#define TCPTV_FINWAIT2IDLE ( 120*PR_SLOWHZ) /* max idle time in FINWAIT2 */ + #define TCPTV_MIN ( 1*PR_SLOWHZ) /* minimum allowable value */ #define TCPTV_REXMTMAX ( 64*PR_SLOWHZ) /* max allowable REXMT value */ @@ -129,6 +131,8 @@ #ifdef KERNEL extern int tcp_keepinit; /* time to establish connection */ extern int tcp_keepidle; /* time before keepalive probes begin */ +extern int tcp_finwait2idle; /* idle time until drop in FIN_WAIT_2 */ + extern int tcp_keepintvl; /* time between keepalive probes */ extern int tcp_maxidle; /* time to drop after starting probes */ extern int tcp_ttl; /* time to live for TCP segs */ Index: netinet/tcp_usrreq.c =================================================================== RCS file: /home/dada/cvsroot/src/netinet/tcp_usrreq.c,v retrieving revision 1.2 diff -u -u -r1.2 tcp_usrreq.c --- tcp_usrreq.c 1999/04/04 22:17:54 1.2 +++ tcp_usrreq.c 1999/04/08 22:16:52 @@ -833,7 +833,7 @@ soisdisconnected(tp->t_inpcb->inp_socket); /* To prevent the connection hanging in FIN_WAIT_2 forever. */ if (tp->t_state == TCPS_FIN_WAIT_2) - tp->t_timer[TCPT_2MSL] = tcp_maxidle; + tp->t_timer[TCPT_2MSL] = tcp_finwait2idle; } return (tp); } Index: netinet/tcp_var.h =================================================================== RCS file: /home/dada/cvsroot/src/netinet/tcp_var.h,v retrieving revision 1.2 diff -u -u -r1.2 tcp_var.h --- tcp_var.h 1999/04/04 22:17:54 1.2 +++ tcp_var.h 1999/04/08 23:32:18 @@ -248,6 +248,7 @@ u_long tcps_keeptimeo; /* keepalive timeouts */ u_long tcps_keepprobe; /* keepalive probes sent */ u_long tcps_keepdrops; /* connections dropped in keepalive */ + u_long tcps_finwait2drops; /* connections dropped in finwait2 */ u_long tcps_sndtotal; /* total packets sent */ u_long tcps_sndpack; /* data packets sent */ @@ -310,7 +311,8 @@ #define TCPCTL_SENDSPACE 8 /* send buffer space */ #define TCPCTL_RECVSPACE 9 /* receive buffer space */ #define TCPCTL_KEEPINIT 10 /* receive buffer space */ -#define TCPCTL_MAXID 11 +#define TCPCTL_FINWAIT2IDLE 11 /* max idle time in FIN_WAIT_2 state */ +#define TCPCTL_MAXID 12 #define TCPCTL_NAMES { \ { 0, 0 }, \ @@ -324,6 +326,7 @@ { "sendspace", CTLTYPE_INT }, \ { "recvspace", CTLTYPE_INT }, \ { "keepinit", CTLTYPE_INT }, \ + { "finwait2idle", CTLTYPE_INT }, \ } #ifdef KERNEL Index: netstat/inet.c =================================================================== RCS file: /home/dada/cvsroot/src/netstat/inet.c,v retrieving revision 1.1 diff -u -u -r1.1 inet.c --- inet.c 1999/04/08 23:38:57 1.1 +++ inet.c 1999/04/08 23:42:27 @@ -253,6 +253,7 @@ p(tcps_keeptimeo, "\t%lu keepalive timeout%s\n"); p(tcps_keepprobe, "\t\t%lu keepalive probe%s sent\n"); p(tcps_keepdrops, "\t\t%lu connection%s dropped by keepalive\n"); + p(tcps_finwait2drops, "\t%lu connection%s dropped in finwait2\n"); p(tcps_predack, "\t%lu correct ACK header prediction%s\n"); p(tcps_preddat, "\t%lu correct data packet header prediction%s\n"); #undef p To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 8 19:55:35 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 0550C15A1E for ; Thu, 8 Apr 1999 19:55:30 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id TAA02140; Thu, 8 Apr 1999 19:35:01 -0700 (PDT) Date: Thu, 8 Apr 1999 19:34:59 -0700 (PDT) From: Julian Elischer To: Martin Kammerhofer Cc: freebsd-net@FreeBSD.ORG Subject: Re: Coping with 1000s of W95 clients. 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 Thanks for taking the time to respond. On Fri, 9 Apr 1999, Martin Kammerhofer wrote: > On Tue, 6 Apr 1999, Julian Elischer wrote: > > > > > The 'canonical example' is Win95 machines that > > don't "shutdown()" the TCP session before exiting. > > In the following situation you are left wit an entry on your server > > sitting in FIN_WAIT_2 state. > > > Even FreeBSD boxes are causing this :(. I see this every day on my home > box where a local apache and a netscape browser are running. HTTP 1.1 > introduced keepalive connections where the server keeps the connection > open for some 15 sec after servicing the request(s). The idea was to cut > down on connection setup overhead. If a client has to open for each of > dozens of inlined GIFs contained in a page a new TCP connection (as it was > the case with HTTP 1.0) performance will suffer. Yes I understand this, but the server will not initiate a shutdown so the socket is not in FIN_WAIT_2 at tehat time. > Now when the server closes the > connection after no further request came in for 15sec a FIN will be sent > and acknowledged from the browser's OS. After that the server's TCP is in > FIN_WAIT_2 state and the browser's in CLOSE_WAIT. This is unfortunatly ok, and indistinguishable from the case where rsh (for example) has closed the input to a remote 'sort' (to allow it to start sorting) and teh remode 'sort' is busy doing stuff, but will (eventually) respond with all the sorted data. (assuming for some reason you wanted to sort on another machine with 300 times as much ram or something). The fact that the browser is misbehaving is not a problem for the server OS in this case. Apache actually waits a few seconds and then does a full close() on the socket, so that in that case a timeout is valid, but in the case where the client may want to send more data.. > If the browser would > periodically check his sockets, read zero length from them, notice that > the server closed and close the socket too, all would be fine. > Unfortunately browsers like Netscape (at least up to 4.08) just sit idle > until the user accesses her next webpage - maybe idling for days! I agree that this is a bad client, but it's indistinguishable from a good client. The server however knows that it can do a close() and force a timeout. So if it doesn't, it's the server's fault as well :-) > The problem is well known, those having installed apache from the FreeBSD > ports collection can read about it in > file:/usr/local/share/doc/apache/manual/misc/fin_wait_2.html . > I don't have this unfortunatly.. > > > > The BSD4.3 hack is to have a (11 minute, 15 second) timeout on FIN_WAIT_2 > > state **IF THE LOCAL END HAS DONE A FULL CLOSE**. A notable example of > > If an application really does shut down _only_ the socket's output > side with shutdown(socket,how=1) then it wants to keep the socket > open for further reads! Timing out a half duplex connection is plain > wrong. unless the far end has actually crashed or closed quietly. A keepalive that elicits a RST or an ACK would isolate those cases. (i.e. resend the FIN and see what comes back) > > The timeout is actually tcp_maxidle = tcp_keepcnt * tcp_keepintvl; > Keepcnt is 8 (hard coded) and keepintvl is settable by sysctl > (net.inet.tcp.keepintvl). Eight times the default keepintvl of 150 > is 1200 or 10 minutes. (Those TCP timers run with 2 Hz.) yes I read the code too :-) > Because > - the idle time counter is incremented _after_ the timer is run, > - and the condition for waiting another 75sec (=keepintvl) is > ``tp->t_idle<= tcp_maxidle'' instead of ``tp->t_idle < tcp_maxidle'' > another keepintvl is added so it's 9 * 75 = 675sec total. (11 min 15 secs :-) > > > > > The only way to stop this is to break the standard, as this would be > > FreeBSD's 675sec timeout on FIN_WAIT_2 is already breaking RFC 793. > > > Basically, any session that is still in FIN_WAIT_2 after 30 seconds > > reverts to FIN_WAIT_1, and resends the FIN. I believe that > > this is similar to a fix Paul Vixie mentionned implementing in NetBSD > > once. > > > I don't think is a good solution. Retransmitting the FIN certainly doesn't > break the spec, but it won't help much. If there were dead browsers ``on > the other side'' of all those annoying FIN_WAIT_2 sockets, then > retransmitting and getting ACKs or RSTs would certainly help. But in most > cases there is a browser just waiting for user actions! Resending the > FIN would accomplish nothing in this case. The browsers TCP stack would > reacknowledge the FIN and continue hanging around in CLOSE_WAIT. At least you know NOT to time out. On the other hand if you get no answer at for 10 minutes straight (it's crashed) or a RST (it's rebooted), you know you can throw away the whole session. > I guess the percentage of cases where you get a RST or ICMP is quite low > and not worth the increase in net traffic. In some cases it's quite high. > > The easy solution to shorten FIN_WAIT_2 is simple: > > sysctl -w net.inet.tcp.keepintvl=27 yes, I've added though sysctl -w net.inet.tcp.finretry (so I can play with it :-) > > This would give you a FIN_WAIT_2 timeout of 9 * 27 / 2 = 121.5 sec > This should cut down the number of FW2 sockets by a factor of > 675/121 = 5.6 . The only drawback to this solution is, that keepalives > won't work reliably any more. (I'm referring to the transport layer > keepalives here, _not_ the HTTP 1.1 application layer keepalives). > After 2 hours idle time there would be only a 2 min time window to > respond before a keepalive connection is dropped. yes I thought of this. > > This leads me two solution 2: > > Just introduce a configurable timeout for idle finwait2 sockets. > This is a quite small change and less intrusive than your suggestion. > Those who have so many hits that finwait2 sockets pile up could > just lower the finwait2 timeout. and what about silly servers that do a shutdown() but never notice that the other end has vanished.. If the kernel could ping the other end, it's KNOW about it. I gotta run, to a FreeBSD meeting... julian > > Martin > > Index: netinet/tcp_input.c > =================================================================== > RCS file: /home/dada/cvsroot/src/netinet/tcp_input.c,v > retrieving revision 1.3 > diff -u -u -r1.3 tcp_input.c > --- tcp_input.c 1999/04/06 19:28:25 1.3 > +++ tcp_input.c 1999/04/08 22:17:58 > @@ -1496,7 +1496,7 @@ > */ > if (so->so_state & SS_CANTRCVMORE) { > soisdisconnected(so); > - tp->t_timer[TCPT_2MSL] = tcp_maxidle; > + tp->t_timer[TCPT_2MSL] = tcp_finwait2idle; > } > tp->t_state = TCPS_FIN_WAIT_2; > } > Index: netinet/tcp_timer.c > =================================================================== > RCS file: /home/dada/cvsroot/src/netinet/tcp_timer.c,v > retrieving revision 1.4 > diff -u -u -r1.4 tcp_timer.c > --- tcp_timer.c 1999/04/08 12:15:01 1.4 > +++ tcp_timer.c 1999/04/08 23:34:49 > @@ -85,6 +85,10 @@ > SYSCTL_INT(_net_inet_tcp, TCPCTL_KEEPINTVL, keepintvl, > CTLFLAG_RW, &tcp_keepintvl , 0, ""); > > +int tcp_finwait2idle = TCPTV_FINWAIT2IDLE; > +SYSCTL_INT(_net_inet_tcp, TCPCTL_FINWAIT2IDLE, finwait2idle, > + CTLFLAG_RW, &tcp_finwait2idle , 0, ""); > + > static int always_keepalive = 0; > SYSCTL_INT(_net_inet_tcp, OID_AUTO, always_keepalive, > CTLFLAG_RW, &always_keepalive , 0, ""); > @@ -162,6 +166,10 @@ > tp = intotcpcb(ip); > if (tp == 0 || tp->t_state == TCPS_LISTEN) > continue; > + tp->t_idle++; > + tp->t_duration++; > + if (tp->t_rtt) > + tp->t_rtt++; > for (i = 0; i < TCPT_NTIMERS; i++) { > if (tp->t_timer[i] && --tp->t_timer[i] == 0) { > #ifdef TCPDEBUG > @@ -180,10 +188,6 @@ > #endif > } > } > - tp->t_idle++; > - tp->t_duration++; > - if (tp->t_rtt) > - tp->t_rtt++; > tpgone: > ; > } > @@ -235,10 +239,13 @@ > */ > case TCPT_2MSL: > if (tp->t_state != TCPS_TIME_WAIT && > - tp->t_idle <= tcp_maxidle) > + tp->t_idle < tcp_finwait2idle) > tp->t_timer[TCPT_2MSL] = tcp_keepintvl; > - else > + else { > + if (tp->t_state == TCPS_FIN_WAIT_2) > + tcpstat.tcps_finwait2drops++; > tp = tcp_close(tp); > + } > break; > > /* > Index: netinet/tcp_timer.h > =================================================================== > RCS file: /home/dada/cvsroot/src/netinet/tcp_timer.h,v > retrieving revision 1.1 > diff -u -u -r1.1 tcp_timer.h > --- tcp_timer.h 1999/04/02 01:15:25 1.1 > +++ tcp_timer.h 1999/04/08 22:13:15 > @@ -101,6 +101,8 @@ > #define TCPTV_KEEPINTVL ( 75*PR_SLOWHZ) /* default probe interval */ > #define TCPTV_KEEPCNT 8 /* max probes before drop */ > > +#define TCPTV_FINWAIT2IDLE ( 120*PR_SLOWHZ) /* max idle time in FINWAIT2 */ > + > #define TCPTV_MIN ( 1*PR_SLOWHZ) /* minimum allowable value */ > #define TCPTV_REXMTMAX ( 64*PR_SLOWHZ) /* max allowable REXMT value */ > > @@ -129,6 +131,8 @@ > #ifdef KERNEL > extern int tcp_keepinit; /* time to establish connection */ > extern int tcp_keepidle; /* time before keepalive probes begin */ > +extern int tcp_finwait2idle; /* idle time until drop in FIN_WAIT_2 */ > + > extern int tcp_keepintvl; /* time between keepalive probes */ > extern int tcp_maxidle; /* time to drop after starting probes */ > extern int tcp_ttl; /* time to live for TCP segs */ > Index: netinet/tcp_usrreq.c > =================================================================== > RCS file: /home/dada/cvsroot/src/netinet/tcp_usrreq.c,v > retrieving revision 1.2 > diff -u -u -r1.2 tcp_usrreq.c > --- tcp_usrreq.c 1999/04/04 22:17:54 1.2 > +++ tcp_usrreq.c 1999/04/08 22:16:52 > @@ -833,7 +833,7 @@ > soisdisconnected(tp->t_inpcb->inp_socket); > /* To prevent the connection hanging in FIN_WAIT_2 forever. */ > if (tp->t_state == TCPS_FIN_WAIT_2) > - tp->t_timer[TCPT_2MSL] = tcp_maxidle; > + tp->t_timer[TCPT_2MSL] = tcp_finwait2idle; > } > return (tp); > } > Index: netinet/tcp_var.h > =================================================================== > RCS file: /home/dada/cvsroot/src/netinet/tcp_var.h,v > retrieving revision 1.2 > diff -u -u -r1.2 tcp_var.h > --- tcp_var.h 1999/04/04 22:17:54 1.2 > +++ tcp_var.h 1999/04/08 23:32:18 > @@ -248,6 +248,7 @@ > u_long tcps_keeptimeo; /* keepalive timeouts */ > u_long tcps_keepprobe; /* keepalive probes sent */ > u_long tcps_keepdrops; /* connections dropped in keepalive */ > + u_long tcps_finwait2drops; /* connections dropped in finwait2 */ > > u_long tcps_sndtotal; /* total packets sent */ > u_long tcps_sndpack; /* data packets sent */ > @@ -310,7 +311,8 @@ > #define TCPCTL_SENDSPACE 8 /* send buffer space */ > #define TCPCTL_RECVSPACE 9 /* receive buffer space */ > #define TCPCTL_KEEPINIT 10 /* receive buffer space */ > -#define TCPCTL_MAXID 11 > +#define TCPCTL_FINWAIT2IDLE 11 /* max idle time in FIN_WAIT_2 state */ > +#define TCPCTL_MAXID 12 > > #define TCPCTL_NAMES { \ > { 0, 0 }, \ > @@ -324,6 +326,7 @@ > { "sendspace", CTLTYPE_INT }, \ > { "recvspace", CTLTYPE_INT }, \ > { "keepinit", CTLTYPE_INT }, \ > + { "finwait2idle", CTLTYPE_INT }, \ > } > > #ifdef KERNEL > Index: netstat/inet.c > =================================================================== > RCS file: /home/dada/cvsroot/src/netstat/inet.c,v > retrieving revision 1.1 > diff -u -u -r1.1 inet.c > --- inet.c 1999/04/08 23:38:57 1.1 > +++ inet.c 1999/04/08 23:42:27 > @@ -253,6 +253,7 @@ > p(tcps_keeptimeo, "\t%lu keepalive timeout%s\n"); > p(tcps_keepprobe, "\t\t%lu keepalive probe%s sent\n"); > p(tcps_keepdrops, "\t\t%lu connection%s dropped by keepalive\n"); > + p(tcps_finwait2drops, "\t%lu connection%s dropped in finwait2\n"); > p(tcps_predack, "\t%lu correct ACK header prediction%s\n"); > p(tcps_preddat, "\t%lu correct data packet header prediction%s\n"); > #undef p > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 9 15: 9: 4 1999 Delivered-To: freebsd-net@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (Postfix) with ESMTP id 1887A15FA5 for ; Fri, 9 Apr 1999 14:49:59 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA18608 for ; Fri, 9 Apr 1999 12:20:15 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id MAA23764; Fri, 9 Apr 1999 12:19:45 -0500 Message-ID: <19990409121944.42560@right.PCS> Date: Fri, 9 Apr 1999 12:19:44 -0500 From: Jonathan Lemon To: freebsd-net@freebsd.org Subject: patch for slowtimeout handling Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Attached is a patch that alters the handling of the TCP timers, especially the slowtimo() function. Its main design is to handle cases where there are a large number of sockets in the TIME_WAIT state (large being defined to be about 40K or so). The general concept of the patch is that timers can either be expressed by the current integer countdown and linear list scan, or on callout basis. Switching from one mode to another depends on where the connection is in the TCP state machine. Currently, I only switch to a callout basis upon entering the TIME_WAIT state. (The rationale for this was I didn't want to add more overhead of adding/removing entries from the timing wheel every time I reset the keepalive timers). There currently is a separate timing wheel for each TCP timer, again because I wanted to make sure that TIME_WAIT entries did not impact the normal processing. Each entry ticks down at the normal slowtimo() rate (1/2 second). The 4 timing wheels could be merged, or just scrapped and put on the current existing wheel in kern_timeout.c. (This wasn't done since these patches are against the RELENG_3 branch, which doesn't have Garret's external callout interface yet). I'd like to solicit feedback on these patches; and the possibility of integrating the changes (probably in some modified form) into the tree. -- Jonathan Index: tcp_fsm.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_fsm.h,v retrieving revision 1.10 diff -u -r1.10 tcp_fsm.h --- tcp_fsm.h 1997/08/16 19:15:38 1.10 +++ tcp_fsm.h 1999/04/09 16:48:21 @@ -63,6 +63,20 @@ #define TCPS_HAVEESTABLISHED(s) ((s) >= TCPS_ESTABLISHED) #define TCPS_HAVERCVDFIN(s) ((s) >= TCPS_TIME_WAIT) +#if 0 +#define TCP_NEWSTATE(tp, state) ((tp)->t_state = state) +#else +#define TCP_NEWSTATE(tp, state) tcp_newstate(tp, state) +#define TCP_NEWSTATE_OPT(tp, state) \ +do { \ + if (state == TCPS_TIME_WAIT || \ + (tp)->t_state == TCPS_TIME_WAIT) \ + tcp_newstate(tp, state); \ + else \ + (tp)->t_state = state; \ +} while(0) +#endif + #ifdef TCPOUTFLAGS /* * Flags used when sending segments in tcp_output. Index: tcp_input.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_input.c,v retrieving revision 1.82 diff -u -r1.82 tcp_input.c --- tcp_input.c 1998/12/03 20:23:20 1.82 +++ tcp_input.c 1999/02/27 06:45:04 @@ -88,7 +88,7 @@ SYSCTL_INT(_net_inet_tcp, OID_AUTO, delayed_ack, CTLFLAG_RW, &tcp_delack_enabled, 0, ""); -u_long tcp_now; +u_long tcp_now = 1; /* we treat 0 specially */ struct inpcbhead tcb; struct inpcbinfo tcbinfo; @@ -115,7 +115,7 @@ (tp)->t_segq == NULL && \ (tp)->t_state == TCPS_ESTABLISHED) { \ if (tcp_delack_enabled) \ - tp->t_flags |= TF_DELACK; \ + TCPDELACK_SETF(tp, TF_DELACK); \ else \ tp->t_flags |= TF_ACKNOW; \ (tp)->rcv_nxt += (ti)->ti_len; \ @@ -477,7 +477,7 @@ } inp->inp_options = ip_srcroute(); tp = intotcpcb(inp); - tp->t_state = TCPS_LISTEN; + TCP_NEWSTATE(tp, TCPS_LISTEN); tp->t_flags |= tp0->t_flags & (TF_NOPUSH|TF_NOOPT); /* Compute proper scaling value from buffer space */ @@ -491,9 +491,9 @@ * Segment received on connection. * Reset idle time and keep-alive timer. */ - tp->t_idle = 0; + TCP_SETIDLE(tp, 0); if (TCPS_HAVEESTABLISHED(tp->t_state)) - tp->t_timer[TCPT_KEEP] = tcp_keepidle; + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepidle); /* * Process options if not in LISTEN state, @@ -559,9 +559,9 @@ if ((to.to_flag & TOF_TS) != 0) tcp_xmit_timer(tp, tcp_now - to.to_tsecr + 1); - else if (tp->t_rtt && + else if (TCP_RTTVAL(tp) && SEQ_GT(ti->ti_ack, tp->t_rtseq)) - tcp_xmit_timer(tp, tp->t_rtt); + tcp_xmit_timer(tp, TCP_RTTVAL(tp)); acked = ti->ti_ack - tp->snd_una; tcpstat.tcps_rcvackpack++; tcpstat.tcps_rcvackbyte += acked; @@ -579,9 +579,9 @@ * decide between more output or persist. */ if (tp->snd_una == tp->snd_max) - tp->t_timer[TCPT_REXMT] = 0; - else if (tp->t_timer[TCPT_PERSIST] == 0) - tp->t_timer[TCPT_REXMT] = tp->t_rxtcur; + TCP_SETTMR(tp, TCPT_REXMT, 0); + else if (TCP_TMRVAL(tp, TCPT_PERSIST) == 0) + TCP_SETTMR(tp, TCPT_REXMT, tp->t_rxtcur); sowwakeup(so); if (so->so_snd.sb_cc) @@ -606,7 +606,7 @@ sbappend(&so->so_rcv, m); sorwakeup(so); if (tcp_delack_enabled) { - tp->t_flags |= TF_DELACK; + TCPDELACK_SETF(tp, TF_DELACK); } else { tp->t_flags |= TF_ACKNOW; tcp_output(tp); @@ -728,7 +728,7 @@ taop->tao_cc != 0 && CC_GT(to.to_cc, taop->tao_cc)) { taop->tao_cc = to.to_cc; - tp->t_state = TCPS_ESTABLISHED; + TCP_NEWSTATE(tp, TCPS_ESTABLISHED); /* * If there is a FIN, or if there is data and the @@ -739,7 +739,7 @@ */ if (tcp_delack_enabled && ((tiflags & TH_FIN) || (ti->ti_len != 0 && in_localaddr(inp->inp_faddr)))) - tp->t_flags |= (TF_DELACK | TF_NEEDSYN); + TCPDELACK_SETF(tp, TF_DELACK | TF_NEEDSYN); else tp->t_flags |= (TF_ACKNOW | TF_NEEDSYN); @@ -751,7 +751,7 @@ tp->rcv_adv += min(tp->rcv_wnd, TCP_MAXWIN); tcpstat.tcps_connects++; soisconnected(so); - tp->t_timer[TCPT_KEEP] = tcp_keepinit; + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepinit); dropsocket = 0; /* committed to socket */ tcpstat.tcps_accepts++; goto trimthenstep6; @@ -769,8 +769,8 @@ * do a standard 3-way handshake. */ tp->t_flags |= TF_ACKNOW; - tp->t_state = TCPS_SYN_RECEIVED; - tp->t_timer[TCPT_KEEP] = tcp_keepinit; + TCP_NEWSTATE(tp, TCPS_SYN_RECEIVED); + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepinit); dropsocket = 0; /* committed to socket */ tcpstat.tcps_accepts++; goto trimthenstep6; @@ -869,7 +869,7 @@ * ACKNOW will be turned on later. */ if (tcp_delack_enabled && ti->ti_len != 0) - tp->t_flags |= TF_DELACK; + TCPDELACK_SETF(tp, TF_DELACK); else tp->t_flags |= TF_ACKNOW; /* @@ -879,12 +879,12 @@ * SYN_SENT* --> FIN_WAIT_1 */ if (tp->t_flags & TF_NEEDFIN) { - tp->t_state = TCPS_FIN_WAIT_1; + TCP_NEWSTATE(tp, TCPS_FIN_WAIT_1); tp->t_flags &= ~TF_NEEDFIN; tiflags &= ~TH_SYN; } else { - tp->t_state = TCPS_ESTABLISHED; - tp->t_timer[TCPT_KEEP] = tcp_keepidle; + TCP_NEWSTATE(tp, TCPS_ESTABLISHED); + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepidle); } } else { /* @@ -897,7 +897,7 @@ * If there was no CC option, clear cached CC value. */ tp->t_flags |= TF_ACKNOW; - tp->t_timer[TCPT_REXMT] = 0; + TCP_SETTMR(tp, TCPT_REXMT, 0); if (to.to_flag & TOF_CC) { if (taop->tao_cc != 0 && CC_GT(to.to_cc, taop->tao_cc)) { @@ -908,19 +908,19 @@ */ taop->tao_cc = to.to_cc; if (tp->t_flags & TF_NEEDFIN) { - tp->t_state = TCPS_FIN_WAIT_1; + TCP_NEWSTATE(tp, TCPS_FIN_WAIT_1); tp->t_flags &= ~TF_NEEDFIN; } else { - tp->t_state = TCPS_ESTABLISHED; - tp->t_timer[TCPT_KEEP] = tcp_keepidle; + TCP_NEWSTATE(tp, TCPS_ESTABLISHED); + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepidle); } tp->t_flags |= TF_NEEDSYN; } else - tp->t_state = TCPS_SYN_RECEIVED; + TCP_NEWSTATE(tp, TCPS_SYN_RECEIVED); } else { /* CC.NEW or no option => invalidate cache */ taop->tao_cc = 0; - tp->t_state = TCPS_SYN_RECEIVED; + TCP_NEWSTATE(tp, TCPS_SYN_RECEIVED); } } @@ -971,7 +971,7 @@ if ((tiflags & TH_SYN) && (to.to_flag & TOF_CC) && tp->cc_recv != 0) { if (tp->t_state == TCPS_TIME_WAIT && - tp->t_duration > TCPTV_MSL) + TCP_DURATIONVAL(tp) > TCPTV_MSL) goto dropwithreset; if (CC_GT(to.to_cc, tp->cc_recv)) { tp = tcp_close(tp); @@ -1055,7 +1055,7 @@ case TCPS_CLOSE_WAIT: so->so_error = ECONNRESET; close: - tp->t_state = TCPS_CLOSED; + TCP_NEWSTATE(tp, TCPS_CLOSED); tcpstat.tcps_drops++; tp = tcp_close(tp); break; @@ -1288,11 +1288,11 @@ * SYN-RECEIVED* -> FIN-WAIT-1 */ if (tp->t_flags & TF_NEEDFIN) { - tp->t_state = TCPS_FIN_WAIT_1; + TCP_NEWSTATE(tp, TCPS_FIN_WAIT_1); tp->t_flags &= ~TF_NEEDFIN; } else { - tp->t_state = TCPS_ESTABLISHED; - tp->t_timer[TCPT_KEEP] = tcp_keepidle; + TCP_NEWSTATE(tp, TCPS_ESTABLISHED); + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepidle); } /* * If segment contains data or ACK, will call tcp_reass() @@ -1347,7 +1347,7 @@ * to keep a constant cwnd packets in the * network. */ - if (tp->t_timer[TCPT_REXMT] == 0 || + if (TCP_TMRVAL(tp, TCPT_REXMT) == 0 || ti->ti_ack != tp->snd_una) tp->t_dupacks = 0; else if (++tp->t_dupacks == tcprexmtthresh) { @@ -1359,7 +1359,7 @@ if (win < 2) win = 2; tp->snd_ssthresh = win * tp->t_maxseg; - tp->t_timer[TCPT_REXMT] = 0; + TCP_SETTMR(tp, TCPT_REXMT, 0); tp->t_rtt = 0; tp->snd_nxt = ti->ti_ack; tp->snd_cwnd = tp->t_maxseg; @@ -1428,8 +1428,8 @@ */ if (to.to_flag & TOF_TS) tcp_xmit_timer(tp, tcp_now - to.to_tsecr + 1); - else if (tp->t_rtt && SEQ_GT(ti->ti_ack, tp->t_rtseq)) - tcp_xmit_timer(tp,tp->t_rtt); + else if (TCP_RTTVAL(tp) && SEQ_GT(ti->ti_ack, tp->t_rtseq)) + tcp_xmit_timer(tp, TCP_RTTVAL(tp)); /* * If all outstanding data is acked, stop retransmit @@ -1438,10 +1438,10 @@ * timer, using current (possibly backed-off) value. */ if (ti->ti_ack == tp->snd_max) { - tp->t_timer[TCPT_REXMT] = 0; + TCP_SETTMR(tp, TCPT_REXMT, 0); needoutput = 1; - } else if (tp->t_timer[TCPT_PERSIST] == 0) - tp->t_timer[TCPT_REXMT] = tp->t_rxtcur; + } else if (TCP_TMRVAL(tp, TCPT_PERSIST) == 0) + TCP_SETTMR(tp, TCPT_REXMT, tp->t_rxtcur); /* * If no data (only SYN) was ACK'd, @@ -1497,9 +1497,9 @@ */ if (so->so_state & SS_CANTRCVMORE) { soisdisconnected(so); - tp->t_timer[TCPT_2MSL] = tcp_maxidle; + TCP_SETTMR(tp, TCPT_2MSL, tcp_maxidle); } - tp->t_state = TCPS_FIN_WAIT_2; + TCP_NEWSTATE(tp, TCPS_FIN_WAIT_2); } break; @@ -1511,15 +1511,15 @@ */ case TCPS_CLOSING: if (ourfinisacked) { - tp->t_state = TCPS_TIME_WAIT; tcp_canceltimers(tp); /* Shorten TIME_WAIT [RFC-1644, p.28] */ if (tp->cc_recv != 0 && - tp->t_duration < TCPTV_MSL) - tp->t_timer[TCPT_2MSL] = - tp->t_rxtcur * TCPTV_TWTRUNC; + TCP_DURATIONVAL(tp) < TCPTV_MSL) + TCP_SETTMR(tp, TCPT_2MSL, + tp->t_rxtcur * TCPTV_TWTRUNC); else - tp->t_timer[TCPT_2MSL] = 2 * TCPTV_MSL; + TCP_SETTMR(tp, TCPT_2MSL, 2 * TCPTV_MSL); + TCP_NEWSTATE(tp, TCPS_TIME_WAIT); soisdisconnected(so); } break; @@ -1543,7 +1543,7 @@ * it and restart the finack timer. */ case TCPS_TIME_WAIT: - tp->t_timer[TCPT_2MSL] = 2 * TCPTV_MSL; + TCP_SETTMR(tp, TCPT_2MSL, 2 * TCPTV_MSL); goto dropafterack; } } @@ -1667,7 +1667,7 @@ * more input can be expected, send ACK now. */ if (tcp_delack_enabled && (tp->t_flags & TF_NEEDSYN)) - tp->t_flags |= TF_DELACK; + TCPDELACK_SETF(tp, TF_DELACK); else tp->t_flags |= TF_ACKNOW; tp->rcv_nxt++; @@ -1680,7 +1680,7 @@ */ case TCPS_SYN_RECEIVED: case TCPS_ESTABLISHED: - tp->t_state = TCPS_CLOSE_WAIT; + TCP_NEWSTATE(tp, TCPS_CLOSE_WAIT); break; /* @@ -1688,7 +1688,7 @@ * enter the CLOSING state. */ case TCPS_FIN_WAIT_1: - tp->t_state = TCPS_CLOSING; + TCP_NEWSTATE(tp, TCPS_CLOSING); break; /* @@ -1697,18 +1697,18 @@ * standard timers. */ case TCPS_FIN_WAIT_2: - tp->t_state = TCPS_TIME_WAIT; tcp_canceltimers(tp); /* Shorten TIME_WAIT [RFC-1644, p.28] */ if (tp->cc_recv != 0 && - tp->t_duration < TCPTV_MSL) { - tp->t_timer[TCPT_2MSL] = - tp->t_rxtcur * TCPTV_TWTRUNC; + TCP_DURATIONVAL(tp) < TCPTV_MSL) { + TCP_SETTMR(tp, TCPT_2MSL, + tp->t_rxtcur * TCPTV_TWTRUNC); /* For transaction client, force ACK now. */ tp->t_flags |= TF_ACKNOW; } else - tp->t_timer[TCPT_2MSL] = 2 * TCPTV_MSL; + TCP_SETTMR(tp, TCPT_2MSL, 2 * TCPTV_MSL); + TCP_NEWSTATE(tp, TCPS_TIME_WAIT); soisdisconnected(so); break; @@ -1716,7 +1716,7 @@ * In TIME_WAIT state restart the 2 MSL time_wait timer. */ case TCPS_TIME_WAIT: - tp->t_timer[TCPT_2MSL] = 2 * TCPTV_MSL; + TCP_SETTMR(tp, TCPT_2MSL, 2 * TCPTV_MSL); break; } } @@ -1997,7 +1997,7 @@ tp->t_srtt = rtt << TCP_RTT_SHIFT; tp->t_rttvar = rtt << (TCP_RTTVAR_SHIFT - 1); } - tp->t_rtt = 0; + tp->t_rtt = 0; tp->t_rxtshift = 0; /* Index: tcp_output.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_output.c,v retrieving revision 1.32 diff -u -r1.32 tcp_output.c --- tcp_output.c 1999/01/20 17:31:59 1.32 +++ tcp_output.c 1999/02/27 06:46:16 @@ -93,7 +93,7 @@ * to send, then transmit; otherwise, investigate further. */ idle = (tp->snd_max == tp->snd_una); - if (idle && tp->t_idle >= tp->t_rxtcur) + if (idle && TCP_IDLEVAL(tp) >= tp->t_rxtcur) /* * We have been idle for "a while" and no acks are * expected to clock out any data we send -- @@ -143,7 +143,7 @@ flags &= ~TH_FIN; win = 1; } else { - tp->t_timer[TCPT_PERSIST] = 0; + TCP_SETTMR(tp, TCPT_PERSIST, 0); tp->t_rxtshift = 0; } } @@ -194,10 +194,10 @@ */ len = 0; if (win == 0) { - tp->t_timer[TCPT_REXMT] = 0; + TCP_SETTMR(tp, TCPT_REXMT, 0); tp->t_rxtshift = 0; tp->snd_nxt = tp->snd_una; - if (tp->t_timer[TCPT_PERSIST] == 0) + if (TCP_TMRVAL(tp, TCPT_PERSIST) == 0) tcp_setpersist(tp); } } @@ -299,8 +299,8 @@ * if window is nonzero, transmit what we can, * otherwise force out a byte. */ - if (so->so_snd.sb_cc && tp->t_timer[TCPT_REXMT] == 0 && - tp->t_timer[TCPT_PERSIST] == 0) { + if (so->so_snd.sb_cc && TCP_TMRVAL(tp, TCPT_REXMT) == 0 && + TCP_TMRVAL(tp, TCPT_PERSIST) == 0) { tp->t_rxtshift = 0; tcp_setpersist(tp); } @@ -563,7 +563,7 @@ * case, since we know we aren't doing a retransmission. * (retransmit and persist are mutually exclusive...) */ - if (len || (flags & (TH_SYN|TH_FIN)) || tp->t_timer[TCPT_PERSIST]) + if (len || (flags & (TH_SYN|TH_FIN)) || TCP_TMRVAL(tp, TCPT_PERSIST)) ti->ti_seq = htonl(tp->snd_nxt); else ti->ti_seq = htonl(tp->snd_max); @@ -609,7 +609,7 @@ * In transmit state, time the transmission and arrange for * the retransmit. In persist state, just set snd_max. */ - if (tp->t_force == 0 || tp->t_timer[TCPT_PERSIST] == 0) { + if (tp->t_force == 0 || TCP_TMRVAL(tp, TCPT_PERSIST) == 0) { tcp_seq startseq = tp->snd_nxt; /* @@ -631,7 +631,7 @@ * not currently timing anything. */ if (tp->t_rtt == 0) { - tp->t_rtt = 1; + TCP_SETRTT(tp, 1); tp->t_rtseq = startseq; tcpstat.tcps_segstimed++; } @@ -645,11 +645,11 @@ * Initialize shift counter which is used for backoff * of retransmit time. */ - if (tp->t_timer[TCPT_REXMT] == 0 && + if (TCP_TMRVAL(tp, TCPT_REXMT) == 0 && tp->snd_nxt != tp->snd_una) { - tp->t_timer[TCPT_REXMT] = tp->t_rxtcur; - if (tp->t_timer[TCPT_PERSIST]) { - tp->t_timer[TCPT_PERSIST] = 0; + TCP_SETTMR(tp, TCPT_REXMT, tp->t_rxtcur); + if (TCP_TMRVAL(tp, TCPT_PERSIST)) { + TCP_SETTMR(tp, TCPT_PERSIST, 0); tp->t_rxtshift = 0; } } @@ -732,7 +732,7 @@ if (win > 0 && SEQ_GT(tp->rcv_nxt+win, tp->rcv_adv)) tp->rcv_adv = tp->rcv_nxt + win; tp->last_ack_sent = tp->rcv_nxt; - tp->t_flags &= ~(TF_ACKNOW|TF_DELACK); + TCPDELACK_CLRF(tp, TF_ACKNOW|TF_DELACK); if (sendalot) goto again; return (0); @@ -743,15 +743,17 @@ register struct tcpcb *tp; { register int t = ((tp->t_srtt >> 2) + tp->t_rttvar) >> 1; + int persist; - if (tp->t_timer[TCPT_REXMT]) + if (TCP_TMRVAL(tp, TCPT_REXMT)) panic("tcp_output REXMT"); /* * Start/restart persistance timer. */ - TCPT_RANGESET(tp->t_timer[TCPT_PERSIST], + TCPT_RANGESET(persist, t * tcp_backoff[tp->t_rxtshift], TCPTV_PERSMIN, TCPTV_PERSMAX); + TCP_SETTMR(tp, TCPT_PERSIST, persist); if (tp->t_rxtshift < TCP_MAXRXTSHIFT) tp->t_rxtshift++; } Index: tcp_subr.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_subr.c,v retrieving revision 1.49.2.1 diff -u -r1.49.2.1 tcp_subr.c --- tcp_subr.c 1999/02/04 06:40:28 1.49.2.1 +++ tcp_subr.c 1999/02/26 21:38:08 @@ -85,6 +85,10 @@ SYSCTL_INT(_net_inet_tcp, TCPCTL_DO_RFC1644, rfc1644, CTLFLAG_RW, &tcp_do_rfc1644 , 0, ""); +static int tcp_tcbhashsize = 0; +SYSCTL_INT(_net_inet_tcp, TCPCTL_TCBHASHSIZE, tcbhashsize, + CTLFLAG_RD, &tcp_tcbhashsize, 0, ""); + SYSCTL_INT(_net_inet_tcp, OID_AUTO, pcbcount, CTLFLAG_RD, &tcbinfo.ipi_count, 0, "Number of active PCBs"); @@ -140,6 +144,7 @@ printf("WARNING: TCB hash size not a power of 2\n"); hashsize = 512; /* safe default */ } + tcp_tcbhashsize = hashsize; tcbinfo.hashbase = hashinit(hashsize, M_PCB, &tcbinfo.hashmask); tcbinfo.porthashbase = hashinit(hashsize, M_PCB, &tcbinfo.porthashmask); @@ -149,6 +154,7 @@ max_protohdr = sizeof(struct tcpiphdr); if (max_linkhdr + sizeof(struct tcpiphdr) > MHLEN) panic("tcp_init"); + tcp_timer_init(); } /* @@ -315,8 +321,11 @@ tp->t_rxtcur = TCPTV_RTOBASE; tp->snd_cwnd = TCP_MAXWIN << TCP_MAX_WINSHIFT; tp->snd_ssthresh = TCP_MAXWIN << TCP_MAX_WINSHIFT; + TCP_SETIDLE(tp, 0); + TCP_SETDURATION(tp, 0); inp->inp_ip_ttl = ip_defttl; inp->inp_ppcb = (caddr_t)tp; + tcpt_attach(tp); return (tp); /* XXX */ } @@ -333,7 +342,7 @@ struct socket *so = tp->t_inpcb->inp_socket; if (TCPS_HAVERCVDSYN(tp->t_state)) { - tp->t_state = TCPS_CLOSED; + TCP_NEWSTATE(tp, TCPS_CLOSED); (void) tcp_output(tp); tcpstat.tcps_drops++; } else @@ -449,6 +458,8 @@ } if (tp->t_template) (void) m_free(dtom(tp->t_template)); +tcp_canceltimers(tp); + tcpt_detach(tp); inp->inp_ppcb = NULL; soisdisconnected(so); in_pcbdetach(inp); Index: tcp_timer.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_timer.c,v retrieving revision 1.28 diff -u -r1.28 tcp_timer.c --- tcp_timer.c 1998/04/24 09:25:35 1.28 +++ tcp_timer.c 1999/04/09 16:51:55 @@ -1,4 +1,4 @@ -/* +/*- * Copyright (c) 1982, 1986, 1988, 1990, 1993, 1995 * The Regents of the University of California. All rights reserved. * @@ -40,11 +40,14 @@ #include #include #include +#include #include #include #include #include +#include + #include /* before tcp_seq.h, for tcp_random18() */ #include @@ -85,21 +88,147 @@ /* max idle time in persist */ int tcp_maxidle; +LIST_HEAD(tcptw_list, tcpt_callout); +LIST_HEAD(, tcpt_callout) active_head; +TAILQ_HEAD(, tcpt_callout) delack_head; + +struct tcpt_timingwheel { + int tw_size; + int tw_mask; + struct tcptw_list *tw_wheel; +}; +struct tcpt_timingwheel tcpt_timingwheel[TCPT_NTIMERS]; + +struct vm_zone *tcptzone; +MALLOC_DEFINE(M_TCPTW, "tcptw", "TCP Timing wheel"); + +/* must be a power of 2 */ +static int tcpt_wheelsize[] = { 32768, 32768, 32768, 32768 }; + +void +tcp_timer_init() +{ + int i, s; + struct tcpt_timingwheel *tw; + + for (i = 0; i < TCPT_NTIMERS; i++) { + tw = &tcpt_timingwheel[i]; + tw->tw_size = tcpt_wheelsize[i]; + tw = &tcpt_timingwheel[i]; + MALLOC(tw->tw_wheel, struct tcptw_list *, + tw->tw_size * sizeof(struct tcptw_list), + M_TCPTW, M_NOWAIT); + tw->tw_mask = tw->tw_size - 1; + for (s = 0; s < tw->tw_size; s++) + LIST_INIT(&tw->tw_wheel[s]); + } + tcptzone = zinit("tcptw", sizeof(struct tcpt_callout), maxsockets, + ZONE_INTERRUPT, 0); + TAILQ_INIT(&delack_head); + LIST_INIT(&active_head); +} + +void +tcpt_attach(tp) + struct tcpcb *tp; +{ + struct tcpt_callout *tc; + + tc = zalloci(tcptzone); + if (tc == NULL) + panic("tcpt_attach: no buffers"); + tc->tc_use_callout = 0; + tc->tc_tp = tp; + LIST_INSERT_HEAD(&active_head, tc, tc_le_active); + tp->timer_callout = (caddr_t)tc; +} + +void +tcpt_detach(tp) + struct tcpcb *tp; +{ + struct tcpt_callout *tc = (struct tcpt_callout *)tp->timer_callout; + int i; + + if (tc->tc_use_callout) { + for (i = 0; i < TCPT_NTIMERS; i++) { + if (tp->t_timer[i] == 0) + continue; + LIST_REMOVE(tc, tc_le[i]); + } + } else { + LIST_REMOVE(tc, tc_le_active); + } + + zfreei(tcptzone, tp->timer_callout); + tp->timer_callout = (caddr_t)0; +} + +/* + * Note: a hazard exists here where it could be possible that the + * callout is on _no_ lists. E.g.: we enter TCP_WAIT state with + * no timeouts set; this will remove us from the active list, but + * not add us to any other lists. + */ +void +tcp_newstate(tp, state) + struct tcpcb *tp; + int state; +{ + struct tcpt_callout *tc = (struct tcpt_callout *)tp->timer_callout; + int i, use_callout; + + use_callout = 0; /* default */ + + switch (state) { + case TCPS_TIME_WAIT: + use_callout = 1; + } + tp->t_state = state; + if (use_callout == tc->tc_use_callout) + return; + + if (tc->tc_use_callout == 0) { + LIST_REMOVE(tc, tc_le_active); + tc->tc_use_callout = 1; + + for (i = 0; i < TCPT_NTIMERS; i++) { + struct tcpt_timingwheel *tw; + struct tcptw_list *bucket; + + if (tp->t_timer[i] == 0) + continue; + tw = &tcpt_timingwheel[i]; + bucket = &tw->tw_wheel[tp->t_timer[i] & tw->tw_mask]; + LIST_INSERT_HEAD(bucket, tc, tc_le[i]); + } + } else { + for (i = 0; i < TCPT_NTIMERS; i++) { + if (tp->t_timer[i] == 0) + continue; + LIST_REMOVE(tc, tc_le[i]); + } + tc->tc_use_callout = 0; + LIST_INSERT_HEAD(&active_head, tc, tc_le_active); + } +} + /* * Fast timeout routine for processing delayed acks */ void tcp_fasttimo() { - register struct inpcb *inp; - register struct tcpcb *tp; + struct tcpt_callout *tc, *ntc; + struct tcpcb *tp; int s; if (tcp_delack_enabled) { s = splnet(); - for (inp = tcb.lh_first; inp != NULL; inp = inp->inp_list.le_next) { - if ((tp = (struct tcpcb *)inp->inp_ppcb) && - (tp->t_flags & TF_DELACK)) { + for (tc = LIST_FIRST(&active_head); tc; tc = ntc) { + ntc = LIST_NEXT(tc, tc_le_active); + tp = tc->tc_tp; + if (tp->t_flags & TF_DELACK) { tp->t_flags &= ~TF_DELACK; tp->t_flags |= TF_ACKNOW; tcpstat.tcps_delack++; @@ -118,10 +247,11 @@ void tcp_slowtimo() { - register struct inpcb *ip, *ipnxt; - register struct tcpcb *tp; - register int i; - int s; + struct tcpt_timingwheel *tw; + struct tcpt_callout *tc, *ntc; + struct tcptw_list *bucket; + struct tcpcb *tp; + int s, i, curtick; #ifdef TCPDEBUG int ostate; #endif @@ -129,22 +259,18 @@ s = splnet(); tcp_maxidle = tcp_keepcnt * tcp_keepintvl; + curtick = tcp_now + 1; - ip = tcb.lh_first; - if (ip == NULL) { - splx(s); - return; - } - /* - * Search through tcb's and update active timers. - */ - for (; ip != NULL; ip = ipnxt) { - ipnxt = ip->inp_list.le_next; - tp = intotcpcb(ip); - if (tp == 0 || tp->t_state == TCPS_LISTEN) + for (tc = LIST_FIRST(&active_head); tc; tc = ntc) { + ntc = LIST_NEXT(tc, tc_le_active); + tp = tc->tc_tp; + if (tp->t_state == TCPS_LISTEN) continue; for (i = 0; i < TCPT_NTIMERS; i++) { - if (tp->t_timer[i] && --tp->t_timer[i] == 0) { + if (tp->t_timer[i] && tp->t_timer[i] < curtick) + printf("Error1: timer < tick\n"); + if (tp->t_timer[i] && tp->t_timer[i] == curtick) { + tp->t_timer[i] = 0; #ifdef TCPDEBUG ostate = tp->t_state; #endif @@ -160,13 +286,43 @@ #endif } } - tp->t_idle++; - tp->t_duration++; - if (tp->t_rtt) - tp->t_rtt++; tpgone: ; } + + for (i = 0; i < TCPT_NTIMERS; i++) { + tw = &tcpt_timingwheel[i]; + bucket = &tw->tw_wheel[curtick & tw->tw_mask]; + for (tc = LIST_FIRST(bucket); tc; tc = ntc) { + ntc = LIST_NEXT(tc, tc_le[i]); +#ifdef TCPDEBUG + if (tc->tc_tp->t_timer[i] && tc->tc_tp->t_timer[i] < curtick) + printf("Error2: timer < tick\n"); + if (tc->tc_tp->t_flags & TF_DELACK) + printf("Error3: delack on timingwheel\n"); +#endif + if (tc->tc_tp->t_timer[i] == curtick) { + LIST_REMOVE(tc, tc_le[i]); + tc->tc_tp->t_timer[i] = 0; +#ifdef TCPDEBUG + ostate = tp->t_state; +#endif + tp = tcp_timers(tc->tc_tp, i); + if (tp == NULL) + goto tpgone2; +#ifdef TCPDEBUG + if (tp->t_inpcb->inp_socket->so_options + & SO_DEBUG) + tcp_trace(TA_USER, ostate, tp, + (struct tcpiphdr *)0, + PRU_SLOWTIMO); +#endif + } +tpgone2: + ; + } + } + tcp_iss += TCP_ISSINCR/PR_SLOWHZ; /* increment iss */ #ifdef TCP_COMPAT_42 if ((int)tcp_iss < 0) @@ -177,16 +333,68 @@ } /* + * for now, allocate the timer structure at the same time as the tcp block + */ +void +tcp_settimer(tp, timer, timeout) + struct tcpcb *tp; + int timer; + int timeout; +{ + struct tcpt_callout *tc = (struct tcpt_callout *)tp->timer_callout; + struct tcpt_timingwheel *tw; + struct tcptw_list *bucket; + +#if 0 + /* + * normal processing. This has been hoisted up into the macro. + */ + if (tc->tc_use_callout == 0) { + tp->t_timer[timer] = (timeout == 0 ? 0 : tcp_now + timeout); + return; + } +#endif + + tw = &tcpt_timingwheel[timer]; + + if (tp->t_timer[timer]) { + /* + * XXX + * one could check that the new timeout doesn't + * put the structure back in the same bucket. + */ + LIST_REMOVE(tc, tc_le[timer]); + tp->t_timer[timer] = 0; + } + if (timeout == 0) + return; + + tp->t_timer[timer] = tcp_now + timeout; + bucket = &tw->tw_wheel[tc->tc_tp->t_timer[timer] & tw->tw_mask]; + LIST_INSERT_HEAD(bucket, tc, tc_le[timer]); +} + +/* * Cancel all timers for TCP tp. */ void tcp_canceltimers(tp) struct tcpcb *tp; { + struct tcpt_callout *tc = (struct tcpt_callout *)tp->timer_callout; register int i; - for (i = 0; i < TCPT_NTIMERS; i++) - tp->t_timer[i] = 0; + if (tc->tc_use_callout) { + for (i = 0; i < TCPT_NTIMERS; i++) { + if (tp->t_timer[i] == 0) + continue; + LIST_REMOVE(tc, tc_le[i]); + tp->t_timer[i] = 0; + } + } else { + for (i = 0; i < TCPT_NTIMERS; i++) + tp->t_timer[i] = 0; + } } int tcp_backoff[TCP_MAXRXTSHIFT + 1] = @@ -214,8 +422,8 @@ */ case TCPT_2MSL: if (tp->t_state != TCPS_TIME_WAIT && - tp->t_idle <= tcp_maxidle) - tp->t_timer[TCPT_2MSL] = tcp_keepintvl; + TCP_IDLEVAL(tp) <= tcp_maxidle) + TCP_SETTMR(tp, TCPT_2MSL, tcp_keepintvl); else tp = tcp_close(tp); break; @@ -237,7 +445,7 @@ rexmt = TCP_REXMTVAL(tp) * tcp_backoff[tp->t_rxtshift]; TCPT_RANGESET(tp->t_rxtcur, rexmt, tp->t_rttmin, TCPTV_REXMTMAX); - tp->t_timer[TCPT_REXMT] = tp->t_rxtcur; + TCP_SETTMR(tp, TCPT_REXMT, tp->t_rxtcur); /* * If losing, let the lower level know and try for * a better route. Also, if we backed off this far, @@ -309,8 +517,8 @@ * backoff that we would use if retransmitting. */ if (tp->t_rxtshift == TCP_MAXRXTSHIFT && - (tp->t_idle >= tcp_maxpersistidle || - tp->t_idle >= TCP_REXMTVAL(tp) * tcp_totbackoff)) { + (TCP_IDLEVAL(tp) >= tcp_maxpersistidle || + TCP_IDLEVAL(tp) >= TCP_REXMTVAL(tp) * tcp_totbackoff)) { tcpstat.tcps_persistdrop++; tp = tcp_drop(tp, ETIMEDOUT); break; @@ -332,7 +540,7 @@ if ((always_keepalive || tp->t_inpcb->inp_socket->so_options & SO_KEEPALIVE) && tp->t_state <= TCPS_CLOSING) { - if (tp->t_idle >= tcp_keepidle + tcp_maxidle) + if (TCP_IDLEVAL(tp) >= tcp_keepidle + tcp_maxidle) goto dropit; /* * Send a packet designed to force a response @@ -358,9 +566,9 @@ tcp_respond(tp, tp->t_template, (struct mbuf *)NULL, tp->rcv_nxt, tp->snd_una - 1, 0); #endif - tp->t_timer[TCPT_KEEP] = tcp_keepintvl; + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepintvl); } else - tp->t_timer[TCPT_KEEP] = tcp_keepidle; + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepidle); break; dropit: tcpstat.tcps_keepdrops++; Index: tcp_timer.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_timer.h,v retrieving revision 1.13 diff -u -r1.13 tcp_timer.h --- tcp_timer.h 1997/09/07 05:26:48 1.13 +++ tcp_timer.h 1999/04/09 16:45:01 @@ -37,6 +37,7 @@ #ifndef _NETINET_TCP_TIMER_H_ #define _NETINET_TCP_TIMER_H_ +#include /* * Definitions of the TCP timers. These timers are counted * down PR_SLOWHZ times a second. @@ -125,6 +126,74 @@ else if ((u_long)(tv) > (u_long)(tvmax)) \ (tv) = (tvmax); \ } + +/* + * Set a tcp timer + */ +#if 0 +#define TCP_SETTMR(tp, timer, timeout) \ + (tp)->t_timer[timer] = timeout +#define TCP_TMRVAL(tp, timer) \ + (tp)->t_timer[timer] +#define TCPDELACK_SETF(tp, flags) \ + (tp)->t_flags |= (flags) +#define TCPDELACK_CLRF(tp, flags) \ + (tp)->t_flags &= ~(flags) +#define TCP_SETIDLE(tp, val) ((tp)->t_idle = val) +#define TCP_IDLEVAL(tp) (tp)->t_idle +#define TCP_SETDURATION(tp, val) ((tp)->t_duration = val) +#define TCP_DURATIONVAL(tp) (tp)->t_duration +#define TCP_SETRTT(tp, val) (tp)->t_rtt = val +#define TCP_RTTVAL(tp) (tp)->t_rtt +#else +struct tcpt_callout { + struct tcpcb *tc_tp; /* backpointer to tcpcb */ + int tc_use_callout; + TAILQ_ENTRY(tcpt_callout) tc_tqe_delack; + LIST_ENTRY(tcpt_callout) tc_le[TCPT_NTIMERS]; + LIST_ENTRY(tcpt_callout) tc_le_active; +}; +struct tcpcb; +void tcp_timer_init __P((void)); +void tcp_settimer __P((struct tcpcb *, int, int)); +int tcp_readtimer __P((struct tcpcb *, int)); +void tcp_newstate __P((struct tcpcb *, int)); +void tcpt_attach __P((struct tcpcb *)); +void tcpt_detach __P((struct tcpcb *)); +#define TCP_SETTMR(tp, timer, timeout) \ +do { \ + if (((struct tcpt_callout *)tp->timer_callout)->tc_use_callout) \ + tcp_settimer(tp, timer, timeout); \ + else \ + tp->t_timer[timer] = \ + (timeout == 0 ? 0 : tcp_now + timeout); \ +} while(0) +#define TCP_TMRVAL(tp, timer) (tp)->t_timer[timer] +#define TCPDELACK_SETF(tp, flags) (tp)->t_flags |= (flags) +#define TCPDELACK_CLRF(tp, flags) (tp)->t_flags &= ~(flags) + +#define TCPDELACK_SETF_X(tp, flags) \ +do { \ + (tp)->t_flags |= (flags); \ + tcp_setdelack(tp, 1); \ +} while(0) +#define TCPDELACK_CLRF_X(tp, flags) \ +do { \ + (tp)->t_flags &= ~(flags); \ + tcp_setdelack(tp, 0); \ +} while(0) +/* + * these are slightly wrong, since they age all connections regardless + * of the state; the original tcp_slowtimo did not age LISTEN sockets. + */ +#define TCP_SETIDLE(tp, val) ((tp)->t_idle = tcp_now + val) +#define TCP_IDLEVAL(tp) (tcp_now - (tp)->t_idle) +#define TCP_SETDURATION(tp, val) ((tp)->t_duration = tcp_now + val) +#define TCP_DURATIONVAL(tp) (tcp_now - (tp)->t_duration) +#define TCP_SETRTT(tp, val) (tp)->t_rtt = tcp_now + val +#define TCP_RTTVAL(tp) \ + ((tp)->t_rtt ? tcp_now - (tp)->t_rtt : 0) +#endif #ifdef KERNEL extern int tcp_keepinit; /* time to establish connection */ Index: tcp_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_usrreq.c,v retrieving revision 1.40 diff -u -r1.40 tcp_usrreq.c --- tcp_usrreq.c 1999/01/20 17:31:59 1.40 +++ tcp_usrreq.c 1999/02/26 21:19:39 @@ -207,7 +207,7 @@ if (inp->inp_lport == 0) error = in_pcbbind(inp, (struct sockaddr *)0, p); if (error == 0) - tp->t_state = TCPS_LISTEN; + TCP_NEWSTATE(tp, TCPS_LISTEN); COMMON_END(PRU_LISTEN); } @@ -514,7 +514,7 @@ if (oinp) { if (oinp != inp && (otp = intotcpcb(oinp)) != NULL && otp->t_state == TCPS_TIME_WAIT && - otp->t_duration < TCPTV_MSL && + TCP_DURATIONVAL(otp) < TCPTV_MSL && (otp->t_flags & TF_RCVD_CC)) otp = tcp_close(otp); else @@ -539,8 +539,8 @@ soisconnecting(so); tcpstat.tcps_connattempt++; - tp->t_state = TCPS_SYN_SENT; - tp->t_timer[TCPT_KEEP] = tcp_keepinit; + TCP_NEWSTATE(tp, TCPS_SYN_SENT); + TCP_SETTMR(tp, TCPT_KEEP, tcp_keepinit); tp->iss = tcp_iss; tcp_iss += TCP_ISSINCR/2; tcp_sendseqinit(tp); @@ -715,7 +715,7 @@ so->so_state |= nofd; return (ENOBUFS); } - tp->t_state = TCPS_CLOSED; + TCP_NEWSTATE(tp, TCPS_CLOSED); return (0); } @@ -766,7 +766,7 @@ case TCPS_CLOSED: case TCPS_LISTEN: - tp->t_state = TCPS_CLOSED; + TCP_NEWSTATE(tp, TCPS_CLOSED); tp = tcp_close(tp); break; @@ -776,18 +776,18 @@ break; case TCPS_ESTABLISHED: - tp->t_state = TCPS_FIN_WAIT_1; + TCP_NEWSTATE(tp, TCPS_FIN_WAIT_1); break; case TCPS_CLOSE_WAIT: - tp->t_state = TCPS_LAST_ACK; + TCP_NEWSTATE(tp, TCPS_LAST_ACK); break; } if (tp && tp->t_state >= TCPS_FIN_WAIT_2) { soisdisconnected(tp->t_inpcb->inp_socket); /* To prevent the connection hanging in FIN_WAIT_2 forever. */ if (tp->t_state == TCPS_FIN_WAIT_2) - tp->t_timer[TCPT_2MSL] = tcp_maxidle; + TCP_SETTMR(tp, TCPT_2MSL, tcp_maxidle); } return (tp); } Index: tcp_var.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_var.h,v retrieving revision 1.49 diff -u -r1.49 tcp_var.h --- tcp_var.h 1999/01/20 17:32:00 1.49 +++ tcp_var.h 1999/02/26 20:02:42 @@ -131,6 +131,7 @@ /* RFC 1644 variables */ tcp_cc cc_send; /* send connection count */ tcp_cc cc_recv; /* receive connection count */ + caddr_t timer_callout; /* timer callout */ }; /* @@ -305,7 +306,8 @@ #define TCPCTL_RECVSPACE 9 /* receive buffer space */ #define TCPCTL_KEEPINIT 10 /* receive buffer space */ #define TCPCTL_PCBLIST 11 /* list of all outstanding PCBs */ -#define TCPCTL_MAXID 12 +#define TCPCTL_TCBHASHSIZE 12 /* size of TCBHASH (read-only) */ +#define TCPCTL_MAXID 13 #define TCPCTL_NAMES { \ { 0, 0 }, \ @@ -320,6 +322,7 @@ { "recvspace", CTLTYPE_INT }, \ { "keepinit", CTLTYPE_INT }, \ { "pcblist", CTLTYPE_STRUCT }, \ + { "pcbhashsize", CTLTYPE_INT }, \ } #ifdef KERNEL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 9 16:28:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 2844414D18 for ; Fri, 9 Apr 1999 16:28:20 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA01251; Fri, 9 Apr 1999 20:52:19 +0200 From: Luigi Rizzo Message-Id: <199904091852.UAA01251@labinfo.iet.unipi.it> Subject: possible dummynet enhancement (random pkt reordering) To: net@freebsd.org Date: Fri, 9 Apr 1999 20:52:19 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1638 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some time ago, a few people asked me on how to simulate pkt reordering with dummynet. I did have a few ideas but not so clear. However, the following seems a reasonably good method if someone feels like implementing it. (this is an excerpt from a reply i sent to Rick Jones at HP): ... reordering is slightly harder to do in a realistic way. I had an email exchange with somebody who wanted to implement it, and turned out that the simplest way would be to randomly decide to swap a pair of packets while they are in the first queue (the bw limiter). This way you preserve the throughput. Depending on which pkts you swap and how frequently you might have different effects which i have not studied in detail. But one reasonable way could be: whenever you can move a pkt from the R-queue to the P-queue, swap the first two pkts (i.e. the one that you would move, and the next one) with a random probability. Then, move the pkt to the P-queue. i think translating the above sentence from english to C should not take much more than a few lines of code... if you can do that, i would be much more interested to know how it works than in the actual code :) cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 9 16:38:23 1999 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 03E3C14ECA for ; Fri, 9 Apr 1999 16:38:20 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA25112; Fri, 9 Apr 1999 16:35:27 -0700 (PDT) Message-Id: <199904092335.QAA25112@implode.root.com> To: Jonathan Lemon Cc: freebsd-net@FreeBSD.ORG Subject: Re: patch for slowtimeout handling In-reply-to: Your message of "Fri, 09 Apr 1999 12:19:44 CDT." <19990409121944.42560@right.PCS> From: David Greenman Reply-To: dg@root.com Date: Fri, 09 Apr 1999 16:35:27 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'd like to solicit feedback on these patches; and the possibility >of integrating the changes (probably in some modified form) into >the tree. I think Garrett's tcp timers rewrite makes this obsolete...have you seen his proposed changes? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 9 18: 2:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 4FA4F14EC3 for ; Fri, 9 Apr 1999 18:02:17 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id RAA17452; Fri, 9 Apr 1999 17:59:13 -0700 (PDT) Date: Fri, 9 Apr 1999 17:59:12 -0700 (PDT) From: Julian Elischer To: Jonathan Lemon Cc: freebsd-net@FreeBSD.ORG Subject: Re: patch for slowtimeout handling In-Reply-To: <19990409121944.42560@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 9 Apr 1999, Jonathan Lemon wrote: > Attached is a patch that alters the handling of the TCP timers, > especially the slowtimo() function. Its main design is to handle > cases where there are a large number of sockets in the TIME_WAIT > state (large being defined to be about 40K or so). Look at Garret's changes.. he's a set that has replaced all the timers with the wheel model timers. Now that you've done this you would be the ideal person to look at his changes (they are I believe more extensive than yours) because you've already got the correct context loaded into your bbrain :-) > > The general concept of the patch is that timers can either be > expressed by the current integer countdown and linear list scan, > or on callout basis. Switching from one mode to another depends > on where the connection is in the TCP state machine. Currently, > I only switch to a callout basis upon entering the TIME_WAIT state. > > (The rationale for this was I didn't want to add more overhead of > adding/removing entries from the timing wheel every time I reset > the keepalive timers). I believe Garret (from the quick look I gave the changes) uses has changed all the timers. you and he might be able to discuss the tradeoffs you and he have made.. > > > There currently is a separate timing wheel for each TCP timer, > again because I wanted to make sure that TIME_WAIT entries did > not impact the normal processing. Each entry ticks down at the > normal slowtimo() rate (1/2 second). The 4 timing wheels could be > merged, or just scrapped and put on the current existing wheel > in kern_timeout.c. (This wasn't done since these patches are > against the RELENG_3 branch, which doesn't have Garret's external > callout interface yet). Well I guess you've seen his code then.. :-) > > I'd like to solicit feedback on these patches; and the possibility > of integrating the changes (probably in some modified form) into > the tree. It's a good idea. I've been playing in that area myself. The tradeoffs are simply whether, in very fast systems, (LOTS OF PACKETS) the overhead of doing timer-wheel operations per packet is greater than the 'per tick' load of hunting through all the PCB's. Possibly your idea of a hybrid is the best approach. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 10 6:43:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from hw (unknown [159.226.21.134]) by hub.freebsd.org (Postfix) with SMTP id 02FCC14D28 for ; Sat, 10 Apr 1999 06:43:34 -0700 (PDT) (envelope-from qhy@hw.ia.ac.cn) Received: from [159.226.21.172] by hw (4.1/SMI-4.1) id AA20676; Sat, 10 Apr 99 21:23:22 CST Date: Sat, 10 Apr 1999 21:44:27 +0800 (CST) From: Que Hongyu X-Sender: qhy@freebsd.hanwang.com.cn To: net@freebsd.org Subject: NAT help 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, I am using 3.1-RELEASE and want to use NAT. here is my situation: I have only one net card with primiary IP: 159.226.21.172/255.255.255.192 I add alias to it, 10.1.1.1/24. then I want to NAT 10.1.1.0/24 to outside internet. After reading some document, I have tried add options IPFIREWALL options IPDIRVERT options IPFIREWALL_DEFAULT_TO_ACCEPT plus, ipfw add divert all from any to any via ed1 But It does not work , can anyone give me some hints? Thanks Que Hongyu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 10 7:13:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (Postfix) with ESMTP id A723714EB7 for ; Sat, 10 Apr 1999 07:13:05 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id QAA20704; Sat, 10 Apr 1999 16:09:17 +0200 (CEST) Message-Id: <199904101409.QAA20704@rt2.synx.com> Date: Sat, 10 Apr 1999 16:09:14 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: possible dummynet enhancement (random pkt reordering) To: luigi@labinfo.iet.unipi.it Cc: net@FreeBSD.ORG In-Reply-To: <199904091852.UAA01251@labinfo.iet.unipi.it> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 9 Apr, Luigi Rizzo wrote: > Some time ago, a few people asked me on how to simulate pkt reordering > with dummynet. I did have a few ideas but not so clear. However, > the following seems a reasonably good method if someone feels like > implementing it. (this is an excerpt from a reply i sent to Rick Jones > at HP): > > ... reordering is slightly harder to do in a realistic way. I had an > email exchange with somebody who wanted to implement it, and turned > out that the simplest way would be to randomly decide to swap a > pair of packets while they are in the first queue (the bw limiter). > This way you preserve the throughput. Depending on which pkts you > swap and how frequently you might have different effects which i > have not studied in detail. But one reasonable way could be: > > whenever you can move a pkt from the R-queue to the P-queue, > swap the first two pkts (i.e. the one that you would move, and the > next one) with a random probability. Then, move the pkt to the > P-queue. > This would be a fair easy thing to do. However, it has some main drawbacks especially at low bandwidth or when there is a great amount of concurrent sessions : (hereafter, a 'session' is an established TCP stream defined by the Quple ((IP/Port)src, (IP/Port)dest) ). - At low bandwidth, streaming sessions (ie: FTP) would cause starvation of interactive (ie: Telnet) ones due to the ratio of packets from one type over the other in the R-queue. This is especially true is dummynet is used at the receiving side in an hope to limit incoming bandwidth. - At great amount of streaming sessions, random packet reordering would force the receiver to reassembly and, aside memory usage, will forbid 'smooth' data delivery at application level. (and unfortunetly, user seems to prefer a low, continous, bandwidth over nothing-then-all). I see two way (over many others) to limit that problem without entering the complexity of real Fair Queuing : - Rotating queues - Tagged placement The rotating queue is proposed on the GPS (Generalized Processor Sharing) algo and on the interesting idea of the Stateless-Core FQ. The idea behind is to build a limited set of queues that will receive packets based on their classification (either an internally generated number for each session Quple, or an hash value extracted from the Quple). Each session goes into only one queue of the set, thus preserving packets ordering. The extracting process rotates under the queue heads and extracts from each queue one packet at a time. This limits (but not prevents) interactive starvation. Full FQ is the case where the session identifier uniquely identify a single queue over a number of queue equal to the so-called WFI (Worst-case Fair Index), that is roughly the max number of concurrent session). The tagged placement approximates this by inserting packets of a session contiguously inside a single queue and then, simulate multiple queues extraction in the same way of rotating queues. In this case, multiple queues are only pointers inside the real queues where a group of packets of a session starts/ends. Roughly, this achieves the same goal with less memory (?) but with higher, near-perfect, WFI (?), and rough ly same complexity (???) (? = personnal doubts). The idea behind tagged placement is that the queue size will force a limit to the WFI since the queue will drop packets when becoming full, thus limiting the WFI to the max number of packets in the queue. These two ways solves the smooth delivery problem but doesn't guaranty anti-starvation (alegedly, TP would). The rotating queue is fairly easy to implement in dummynet. Basically this means : - replace the R-queue by a set of smaller R-queues. (eg: 16) - Build a function generating the input R-queue number to be used when presented a Quple (can be just a modulo sum of all low bytes of the elements of the Quples (wteg: &0x0f) - slightly modify the R-queue extractions to use R-queues. (wteg: queue[i++&0xf]). Please note that this will _not_ address the problem of remote limiting wich is more complex and need to delay acks packets based on their session identifier. Comments, please. ------ Note: I also found a fairly easy way to share bandwidth between queues but this mail is too short. (Nope, not playing Ferma ;), it's only not the subject but i would like to discuss it with interested peoples). RN. ItM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 10 7:37: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.dynamixweb.com (host01.dynamixweb.com [209.47.109.194]) by hub.freebsd.org (Postfix) with ESMTP id 17F141508F for ; Sat, 10 Apr 1999 07:37:01 -0700 (PDT) (envelope-from svetzal@icom.ca) Received: from blazer (cr609409-a.pr1.on.wave.home.com [24.112.98.34]) by mail.dynamixweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 2G6LC0GH; Sat, 10 Apr 1999 10:38:00 -0400 From: "Steven Vetzal" To: "'Que Hongyu'" Cc: Subject: RE: NAT help Date: Sat, 10 Apr 1999 10:37:20 -0400 Message-ID: <000001be835f$a46a1520$7ffea8c0@blazer.pr1.on.wave.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I've never used natd with an alias - does this work? I always make sure I've got some bpf's in the kernel: pseudo-device bpfilter 4 make sure you've got natd in your /etc/services natd 8668/divert make sure you've started natd (8^) And you've got additional firewall rules like $fwcmd add 100 pass all from any to any via lo0 $fwcmd add 200 deny all from any to 127.0.0.0/8 $fwcmd add 65000 pass all from any to any Of course, this is basic nat stuff, and you probably know all this already... I'd be interested to see if you can make this work with an alias. Steve -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Que Hongyu Sent: April 10, 1999 9:44 AM To: net@FreeBSD.ORG Subject: NAT help Hi, I am using 3.1-RELEASE and want to use NAT. here is my situation: I have only one net card with primiary IP: 159.226.21.172/255.255.255.192 I add alias to it, 10.1.1.1/24. then I want to NAT 10.1.1.0/24 to outside internet. After reading some document, I have tried add options IPFIREWALL options IPDIRVERT options IPFIREWALL_DEFAULT_TO_ACCEPT plus, ipfw add divert all from any to any via ed1 But It does not work , can anyone give me some hints? Thanks Que Hongyu 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 Apr 10 8:46:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (Postfix) with ESMTP id 536E714E9C for ; Sat, 10 Apr 1999 08:46:08 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id RAA20807; Sat, 10 Apr 1999 17:43:43 +0200 (CEST) Message-Id: <199904101543.RAA20807@rt2.synx.com> Date: Sat, 10 Apr 1999 17:43:40 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: DN Bandwidth sharing. (was Re: possible dummynet enhancement (rando m pkt reordering)) To: luigi@labinfo.iet.unipi.it Cc: net@FreeBSD.ORG In-Reply-To: <199904101214.OAA02250@labinfo.iet.unipi.it> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10 Apr, Luigi Rizzo wrote: > Excuse me but i think there is a misunderstanding. Having dummynet > reorder packets is just to simulate a network "feature" that should > not exist on most networks (but it might if you have clustered > links or multiple paths) and see how the protocol stack behaves. > > It is not a way to implement some form of fairness... > Oups, sorry. Was too focused on getting things better than worst for test-beds tools purposes. I missed the 'enhancement' meaning. > so, i think the first part of your email does not apply (i know > applications will have a harder time!) while the second part could be > interesting and worth reposting under a separate Subject (or, if as you > say it is long, put it somewhere on the web and give me an URL). > Here is : pipes are gathered by logical groups depending on their number. A group is just a range (0-99, 100-199, 200-299, etc....). Within a group, bandwidth that have not been used by a pipe is spred over the active pipes within that group. Actually, the process is : - Design the set of ipfw rules that will designate a pipe (ie: HTTP, telnet, smtp, other) and the flow (in/out). - build the set of pipes that will handle the flow *in the worst case* (every pipe active). The sum of the bandwith must be the real, physical, maximum allowed bandwidth for that group. Exemple : Lets say that, using a 64Kb/s link, you allow, in the worst case : - HTTP : 30Kb/s - Telnet : 10Kb/s - SMTP : 5Kb/s - Other : (64 - 30 - 10 - 5) = 19Kb/s So the set of pipes are : ipfw pipe 1 config bw 30K .. ipfw pipe 2 config bw 10K .. ipfw pipe 3 config bw 5K .. ipfw pipe 4 config bw 19K .. and routing ipfw rules like : ipfw add 1 pipe 1 from any to any http via tun0 out ipfw add 2 pipe 2 from any to any telnet via tun0 out ipfw add 3 pipe 3 from any to any smtp via tun0 out ipfw add 4 pipe 4 from any to any via tun0 out (ps: needs net.inet.ip.fw.one_pass=1) then, same process for the input stream : ipfw pipe 100 config bw .. ipfw pipe 101 . 102 . 103 and routing rules using 'in' final clause. This done, each group corresponds to a physical value (the output bandwidth for pipes 0-99, the input one for pipes 100-199). Original dummynet fixed and preserved bandwidth function is kept by using one pipe per group, ie: using pipes number by multiples of 100. If the old config was : ipfw pipe 1 config .... ipfw pipe 2 config .... ipfw pipe 3 config .... the new config would be : ipfw pipe 1 config .... ipfw pipe 100 config ... ipfw pipe 200 config ... The implementation was fairly easy because, fortunetly, pipes are linked in their increasing numbering order so it's just a matter of detecting a cross-100 multiple and relooping in the group to distribute gathered bandwidth during the first pass. There are many possibilities to build priority queing this way (sub-grouping) but it bothers me to have too much hidden semantic in the pipe numbering. a big ipfw rules table is already a good way to get lost. A much cleaner way would be to add a class number in each pipe but it's more computational intensive, aside needing an ipfw modification. RN. IeM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 10 11:28:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id F197114D74 for ; Sat, 10 Apr 1999 11:28:07 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA02250; Sat, 10 Apr 1999 14:14:15 +0200 From: Luigi Rizzo Message-Id: <199904101214.OAA02250@labinfo.iet.unipi.it> Subject: Re: possible dummynet enhancement (random pkt reordering) To: remy@synx.com Date: Sat, 10 Apr 1999 14:14:14 +0200 (MET DST) Cc: net@FreeBSD.ORG In-Reply-To: <199904101409.QAA20704@rt2.synx.com> from "Remy Nonnenmacher" at Apr 10, 99 04:08:55 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 606 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excuse me but i think there is a misunderstanding. Having dummynet reorder packets is just to simulate a network "feature" that should not exist on most networks (but it might if you have clustered links or multiple paths) and see how the protocol stack behaves. It is not a way to implement some form of fairness... so, i think the first part of your email does not apply (i know applications will have a harder time!) while the second part could be interesting and worth reposting under a separate Subject (or, if as you say it is long, put it somewhere on the web and give me an URL). cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 10 20:34:53 1999 Delivered-To: freebsd-net@freebsd.org Received: from camel.ethereal.net (fraenatus.ethereal.net [204.107.140.58]) by hub.freebsd.org (Postfix) with ESMTP id 7911515102 for ; Sat, 10 Apr 1999 20:34:51 -0700 (PDT) (envelope-from mistwolf@camel.ethereal.net) Received: (from mistwolf@localhost) by camel.ethereal.net (8.9.1a/8.9.1) id UAA23518 for freebsd-net@FreeBSD.ORG; Sat, 10 Apr 1999 20:32:27 -0700 (PDT) Message-ID: <19990410203227.A23292@ethereal.net> Date: Sat, 10 Apr 1999 20:32:27 -0700 From: Jamie Norwood To: freebsd-net@FreeBSD.ORG Subject: NatD question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an odd(?) NatD setup I am tryin to implement but haven't been able get it working or find adequate resources to help me figure it out. I have a cable modem, and with it I am assigned 4 IPs. Now, as they are not IPs I can subnet, and because I want some basic firewall functions (Blocking NetBios, for instance.), I want to connect the cable modem to my FreeBSD server, then connect a second NIC to a hub on which rests 2 other machines. This part i have wokring ok. What I want, though, is for those two machines to be accessible from the outside world as public IPs through transparent translation on the FreeBSD box. So what I have is: The Internet | | /-------------\ | Cable Modem | \-------------/ | | \--------------------------------------\ | | /---------------\ | 208.166.54.56 | | 208.166.54.57 | | 208.166.54.58 | | | | 10.166.54.56 | \---------------/ | /-----\ /-------------------------| Hub | | \-----/ /--------------\ | | 10.166.54.57 | | \--------------/ | /--------------\ | 10.166.54.58 | \--------------/ Where do I begin in writing the NatD rules that will allow packets destined for 208.166.54.57 hit 10.166.54.57, and for machines on the internet to see 10.166.54.57 as 208.166.54.57 when sending packets back? Thanks! Jamie -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+++** ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 11 15:35:34 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.dynamixweb.com (host01.dynamixweb.com [209.47.109.194]) by hub.freebsd.org (Postfix) with ESMTP id C26A71553E for ; Sun, 11 Apr 1999 15:34:57 -0700 (PDT) (envelope-from svetzal@icom.ca) Received: from blazer (cr609409-a.pr1.on.wave.home.com [24.112.98.34]) by mail.dynamixweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 2G6LC0HA; Sun, 11 Apr 1999 08:46:49 -0400 From: "Steven Vetzal" To: "'Jamie Norwood'" , Subject: RE: NatD question Date: Sun, 11 Apr 1999 08:46:10 -0400 Message-ID: <000001be8419$476fa320$7ffea8c0@blazer.pr1.on.wave.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <19990410203227.A23292@ethereal.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Jamie, You don't use rules to do that - just edit /etc/rc.conf to launch natd with the additional flags -redirect_address 10.166.54.57 208.166.54.57 -redirect_address 10.166.54.58 208.166.54.58 Steve -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jamie Norwood Sent: April 10, 1999 11:32 PM To: freebsd-net@FreeBSD.ORG Subject: NatD question I have an odd(?) NatD setup I am tryin to implement but haven't been able get it working or find adequate resources to help me figure it out. I have a cable modem, and with it I am assigned 4 IPs. Now, as they are not IPs I can subnet, and because I want some basic firewall functions (Blocking NetBios, for instance.), I want to connect the cable modem to my FreeBSD server, then connect a second NIC to a hub on which rests 2 other machines. This part i have wokring ok. What I want, though, is for those two machines to be accessible from the outside world as public IPs through transparent translation on the FreeBSD box. So what I have is: The Internet | | /-------------\ | Cable Modem | \-------------/ | | \--------------------------------------\ | | /---------------\ | 208.166.54.56 | | 208.166.54.57 | | 208.166.54.58 | | | | 10.166.54.56 | \---------------/ | /-----\ /-------------------------| Hub | | \-----/ /--------------\ | | 10.166.54.57 | | \--------------/ | /--------------\ | 10.166.54.58 | \--------------/ Where do I begin in writing the NatD rules that will allow packets destined for 208.166.54.57 hit 10.166.54.57, and for machines on the internet to see 10.166.54.57 as 208.166.54.57 when sending packets back? Thanks! Jamie -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+++** ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 11 17:48:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from fasterix.frmug.org (d139.paris-81.cybercable.fr [212.198.81.139]) by hub.freebsd.org (Postfix) with ESMTP id 2B6F314E2E for ; Sun, 11 Apr 1999 17:48:50 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.9.3/pb-19990315) id CAA33510; Mon, 12 Apr 1999 02:46:28 +0200 (CEST) Message-ID: <19990412024623.A33477@fasterix.frmug.fr.net> Date: Mon, 12 Apr 1999 02:46:23 +0200 From: Pierre Beyssac To: Ollivier Robert , net@FreeBSD.ORG Subject: Re: FreeBSD equiv. of this Linux socket call... References: <36FF11E2.4B661EED@cvzoom.net> <19990329214714.A42277@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <19990329214714.A42277@keltia.freenix.fr>; from Ollivier Robert on Mon, Mar 29, 1999 at 09:47:14PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 29, 1999 at 09:47:14PM +0200, Ollivier Robert wrote: > Speaking of bpf... NFR has a performance patch for bpf included in the > distribution. Has anyone tried to merge our version and their own ? > > -rw-r----- 1 roberto staff 30444 Dec 9 23:12 bpf.c > -rw-r----- 1 roberto staff 7476 Dec 9 23:12 bpf.h > -rw-r----- 1 roberto staff 4367 Dec 9 23:12 bpfdesc.h It's not exactly a performance patch, but mostly fixes to get bpf to correctly work with select(), if I remember correctly. The "performance patch" is an increase in maximum allowed buffer size, from 0x8000 to 0x80000 bytes. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 11 21:44:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from kaa.kfunigraz.ac.at (KAA-ATM.kfunigraz.ac.at [143.50.202.22]) by hub.freebsd.org (Postfix) with ESMTP id C6D7D1504D for ; Sun, 11 Apr 1999 21:43:57 -0700 (PDT) (envelope-from dada@balu.kfunigraz.ac.at) Received: from balu.kfunigraz.ac.at (balu [143.50.16.16]) by kaa.kfunigraz.ac.at (8.9.2/8.9.2) with ESMTP id GAA26769 for ; Mon, 12 Apr 1999 06:41:38 +0200 (MDT) Received: from localhost.kfunigraz.ac.at (IDENT:WbSZTPwNLyAZQd1FNU0QbSw9rOsk9/Io@BONLINEA17.kfunigraz.ac.at [143.50.36.17]) by balu.kfunigraz.ac.at (8.9.2/8.9.2) with ESMTP id GAA19745 for ; Mon, 12 Apr 1999 06:41:37 +0200 (MDT) Received: from localhost (uLO0/RrwhtezVs8tmS2jjiehnrLPYZxF@localhost.kfunigraz.ac.at [127.0.0.1]) by localhost.kfunigraz.ac.at (8.8.8/8.8.8) with SMTP id BAA08377 for ; Sun, 11 Apr 1999 01:25:32 +0200 (CEST) (envelope-from dada@localhost.kfunigraz.ac.at) Date: Sun, 11 Apr 1999 01:25:30 +0200 (CEST) From: Martin Kammerhofer Reply-To: Martin Kammerhofer To: freebsd-net@freebsd.org Subject: RFC 2414 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 Shouldn't there be an net.inet.tcp.rfc2414 option? Implementing 2414 is no big deal... Just a thought, Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 11 22:39:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from camel.ethereal.net (fraenatus.ethereal.net [204.107.140.58]) by hub.freebsd.org (Postfix) with ESMTP id A549D150D8 for ; Sun, 11 Apr 1999 22:39:26 -0700 (PDT) (envelope-from mistwolf@camel.ethereal.net) Received: (from mistwolf@localhost) by camel.ethereal.net (8.9.1a/8.9.1) id WAA07436; Sun, 11 Apr 1999 22:36:50 -0700 (PDT) Message-ID: <19990411223649.A7310@ethereal.net> Date: Sun, 11 Apr 1999 22:36:49 -0700 From: Jamie Norwood To: "Steven Vetzal" , Subject: Re: NatD question References: <19990410203227.A23292@ethereal.net> <000001be8419$476fa320$7ffea8c0@blazer.pr1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <000001be8419$476fa320$7ffea8c0@blazer.pr1.on.wave.home.com>; from Steven Vetzal on Sun, Apr 11, 1999 at 08:46:10AM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This works. I feel stupid now for not trying it before; I had tried loading a config file with multiple redirct_address lines, but that wasn't working. Odd. Jamie On Sun, Apr 11, 1999 at 08:46:10AM -0400, Steven Vetzal wrote: > Hi Jamie, > > You don't use rules to do that - just edit /etc/rc.conf to launch natd with > the additional flags > > -redirect_address 10.166.54.57 208.166.54.57 -redirect_address 10.166.54.58 > 208.166.54.58 > > Steve > > > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Jamie Norwood > Sent: April 10, 1999 11:32 PM > To: freebsd-net@FreeBSD.ORG > Subject: NatD question > > > I have an odd(?) NatD setup I am tryin to implement but haven't been able > get it working or find adequate resources to help me figure it out. > > I have a cable modem, and with it I am assigned 4 IPs. Now, as they > are not IPs I can subnet, and because I want some basic firewall functions > (Blocking NetBios, for instance.), I want to connect the cable modem > to my FreeBSD server, then connect a second NIC to a hub on which rests > 2 other machines. > > This part i have wokring ok. What I want, though, is for those two machines > to be accessible from the outside world as public IPs through transparent > translation on the FreeBSD box. > > So what I have is: > > The Internet > | > | > /-------------\ > | Cable Modem | > \-------------/ > | > | > \--------------------------------------\ > | > | > /---------------\ > | 208.166.54.56 | > | 208.166.54.57 | > | 208.166.54.58 | > | | > | 10.166.54.56 | > \---------------/ > | > /-----\ > /-------------------------| Hub | > | \-----/ > /--------------\ | > | 10.166.54.57 | | > \--------------/ | > /--------------\ > | 10.166.54.58 | > \--------------/ > > Where do I begin in writing the NatD rules that will allow packets destined > for 208.166.54.57 hit 10.166.54.57, and for machines on the internet to see > 10.166.54.57 as 208.166.54.57 when sending packets back? > > Thanks! > > Jamie > > > -- > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > 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+++** > ------END GEEK CODE BLOCK------ > > > > 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 -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 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+++** ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 12 2:41:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from kame200.kame.net (kame200.kame.net [203.178.141.200]) by hub.freebsd.org (Postfix) with ESMTP id 69F8814F0C for ; Mon, 12 Apr 1999 02:41:35 -0700 (PDT) (envelope-from kazu@kame.net) Received: from localhost (localhost [127.0.0.1]) by kame200.kame.net (8.9.2/8.9.2) with ESMTP id SAA03748 for ; Mon, 12 Apr 1999 18:41:07 +0900 (JST) (envelope-from kazu@kame.net) To: net@FreeBSD.ORG Subject: KAME stable release 19990412 From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) X-Mailer: Mew version 1.94b21 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990412184106O.kazu@kame.net> Date: Mon, 12 Apr 1999 18:41:06 +0900 X-Dispatcher: imput version 990405(IM114) Lines: 67 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As usual, KAME Project has released "stable" packages of IPv6/IPsec network code for FreeBSD 2.2.8/3.1(New!), NetBSD 1.3.3, and BSD/OS 3.1. These packages are free of charge but absolutely no warranty. They are avaiable from the following web site: http://www.kame.net/ NOTE: IF YOU GAIN ACCESS TO THIS WEB PAGE OVER IPv6, THE TURTLE WILL DANCE. --Kazu, KAME Project --from here The following is the RELNOTE file. RELNOTES of KAME kit KAME Project $Date: 1999/04/12 02:39:05 $ Here is a summary of differences between KAME stable 19990131 and 19990412. <> - Fixed mbuf leaks and other mbuf-related twists. <> - Fixed mbuf leaks and other mbuf-related twists. - Rate limit for icmp6 redirect. - Reject overlapping fragment on reception. - More spec-conformant source address selection for NA output. - MINCLSIZE is decreased to force drivers to give cluster mbuf. - (FreeBSD 3.1) cisco HDLC support for sppp device. - (BSDI) merged `goto ours' hack using the routing table from KAME for FreeBSD. - ND6 reachable time is now recomputed in at least two hours even if no router advertisement is received. - Changed to use ND based MTU instead of the link's physical MTU when detecting whether the packet should be fragmented. <> - setsockopt(IPV6_{UNI,MULTI}CAST_HOPS) now behaves as described in spec. - Fixed libinet6 in order to support a lot of interfaces(e.g. over 100 gifs can be configured). <> - Avoid corrupted packet on tcp retransmission. - Fixed a bug in IPsec header size computation for MTU consideration. - esp_output() now takes care of both IPv4 and IPv6 (used to be separate). - Fix memory leakage in IPsec tunnel decapsulation. - (NetBSD) tcp4/6 takes care about IPsec header size in MSS computation. <> - traceroute6 supports source route (-g). - -c specifies alternate configuration file path for rtadvd. - Bug fixes and enhancements of bgpd. - Additions of several manpages. <> - ports/pkgsrc: upgraded base version for many items in the collection. - ports/pkgsrc additions: wbd, squid, ethereal - ports/pkgsrc removals: im --to here To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 13 13:42:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id CEA3C14C06 for ; Tue, 13 Apr 1999 13:40:17 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA24569 for net@FreeBSD.ORG; Tue, 13 Apr 1999 22:37:31 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 740D38841; Tue, 13 Apr 1999 22:18:26 +0200 (CEST) Date: Tue, 13 Apr 1999 22:18:26 +0200 From: Ollivier Robert To: net@FreeBSD.ORG Subject: Re: KAME stable release 19990412 Message-ID: <19990413221826.A14913@keltia.freenix.fr> Mail-Followup-To: net@FreeBSD.ORG References: <19990412184106O.kazu@kame.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990412184106O.kazu@kame.net>; from Kazu Yamamoto on Mon, Apr 12, 1999 at 06:41:06PM +0900 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Kazu Yamamoto: > As usual, KAME Project has released "stable" packages of IPv6/IPsec > network code for FreeBSD 2.2.8/3.1(New!), NetBSD 1.3.3, and BSD/OS > 3.1. And I must say I'm impressed by the easiness of the installation. In less than half an hour I got a 2 interfaces IPv6 router w/o needing to build the world (as in the INRIA stack). Congrats to the KAME team ! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 13 13:42:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 16E9B14ECB for ; Tue, 13 Apr 1999 13:42:23 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA24604 for net@freebsd.org; Tue, 13 Apr 1999 22:40:01 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 081FD8841; Tue, 13 Apr 1999 22:20:22 +0200 (CEST) Date: Tue, 13 Apr 1999 22:20:22 +0200 From: Ollivier Robert To: net@freebsd.org Subject: if_ex.c driver and multicast Message-ID: <19990413222022.B14913@keltia.freenix.fr> Mail-Followup-To: net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is it hard to add multicast capabilities to a network driver ? I tumbled on the lack of multicast support of the if_ex.c driver (Intel EtherExpress 10/ISA) when installing IPv6. I had to swap them for 3c905s. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 13 22: 6:32 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 26BF515336 for ; Tue, 13 Apr 1999 22:06:27 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com ([204.68.178.225]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA10351; Tue, 13 Apr 1999 23:04:06 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <371421C3.B1553B2@softweyr.com> Date: Tue, 13 Apr 1999 23:04:03 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: net@FreeBSD.ORG Subject: Re: if_ex.c driver and multicast References: <19990413222022.B14913@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ollivier Robert wrote: > > Is it hard to add multicast capabilities to a network driver ? > > I tumbled on the lack of multicast support of the if_ex.c driver (Intel > EtherExpress 10/ISA) when installing IPv6. I had to swap them for 3c905s. It depends on the level of support the chipset has for multicast. Intel chips in general kind of suck at this. Apparently they haven't even fixed it in the EEPro/100 chipset yet. I haven't looked at the 3c9xx series, but hope they're a bit better than Intel. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Apr 14 5:13:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 9AFC81513D for ; Wed, 14 Apr 1999 05:12:30 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id OAA06110 for ; Wed, 14 Apr 1999 14:10:08 +0200 (CEST) Received: from tu (t1o68p59.telia.com [62.20.138.59]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id OAA13108 for ; Wed, 14 Apr 1999 14:09:58 +0200 (CEST) Received: by localhost with Microsoft MAPI; Wed, 14 Apr 1999 14:06:23 +0200 Message-ID: <01BE867F.FA58BA40.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'net@freebsd.org'" Subject: steps in networking Date: Wed, 14 Apr 1999 14:06:13 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 Is there anyone out there that could write up a little "manual" of the different steps on what to do/edit to accomplish the below description using FreeBSD + ipfw + NAT or FreeBSD + IPF + IPNAT.. INTERNAL (192.168.1.xx) ------ (192.168.1.1)FreeBSD box(192.168.2.2) -------- (192.168.2.1)Congo Router(Dynamic IP)-------Internet The FreeBSD box have 2 networkinterfaces ep0 and ep1. And I need some sort of firewall solution ( not superstrong ), but what I do need is for packets to the outside world (internet) from the internal network to be able to get through the solution. The network looks like this today: INTERNAL (192.168.1.xx) ------ (192.168.1.1)Congo Router(Dynamic IP) ------- Internet So is there anybody out there that wants to be kind enough to help me, you would make my day. I don't want to put in yet another bulky Windows NT Server box into the network, they already add too much to my workload as it is, and you never know exactly what they are doing. Mail me if you need additional information. Thank ye in advance / Thomas Uhrfelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 5:21:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id 88DF914EB1 for ; Wed, 14 Apr 1999 05:21:24 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailf.telia.com (8.8.8/8.8.8) with ESMTP id OAA25056 for ; Wed, 14 Apr 1999 14:19:02 +0200 (CEST) Received: from tu (t1o68p59.telia.com [62.20.138.59]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id OAA17142 for ; Wed, 14 Apr 1999 14:19:00 +0200 (CEST) Received: by localhost with Microsoft MAPI; Wed, 14 Apr 1999 14:15:29 +0200 Message-ID: <01BE8681.3FC5E6B0.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'freebsd-net@freebsd.org'" Subject: steps in networking Date: Wed, 14 Apr 1999 14:15:03 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 Is there anyone out there that could write up a little "manual" of the different steps on what to do/edit to accomplish the below description using FreeBSD + ipfw + NAT or FreeBSD + IPF + IPNAT.. INTERNAL (192.168.1.xx) ------ (192.168.1.1)FreeBSD box(192.168.2.2) -------- (192.168.2.1)Congo Router(Dynamic IP)-------Internet The FreeBSD box have 2 networkinterfaces ep0 and ep1. And I need some sort of firewall solution ( not superstrong ), but what I do need is for packets to the outside world (internet) from the internal network to be able to get through the solution. The network looks like this today: INTERNAL (192.168.1.xx) ------ (192.168.1.1)Congo Router(Dynamic IP) ------- Internet So is there anybody out there that wants to be kind enough to help me, you would make my day. I don't want to put in yet another bulky Windows NT Server box into the network, they already add too much to my workload as it is, and you never know exactly what they are doing. Mail me if you need additional information. Thank ye in advance Thomas Uhrfelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 6:36:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailg.telia.com (mailg.telia.com [194.22.194.26]) by hub.freebsd.org (Postfix) with ESMTP id 88497150A3 for ; Wed, 14 Apr 1999 06:35:51 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailg.telia.com (8.8.5/8.8.8) with ESMTP id PAA16378; Wed, 14 Apr 1999 15:33:29 +0200 (CEST) Received: from tu (t1o68p59.telia.com [62.20.138.59]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id PAA17318; Wed, 14 Apr 1999 15:33:18 +0200 (CEST) Received: by localhost with Microsoft MAPI; Wed, 14 Apr 1999 15:29:42 +0200 Message-ID: <01BE868B.9E2A48E0.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'Thomas Seidmann'" Cc: "'freebsd-net@freebsd.org'" Subject: SV: steps in networking Date: Wed, 14 Apr 1999 15:29:24 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 > Thomas Uhrfelt wrote: > > > > Is there anyone out there that could write up a little "manual" of the > > different steps on what to do/edit to accomplish the below description > > using FreeBSD + ipfw + NAT or FreeBSD + IPF + IPNAT.. > > > > INTERNAL (192.168.1.xx) ------ (192.168.1.1)FreeBSD box(192.168.2.2) > > -------- (192.168.2.1)Congo Router(Dynamic IP)-------Internet > [stuff deleted] > > I'm afraid you cannot handle this case with neither NAT variant > mentioned above, since you need a public IP address on the machine doing > the actual NAT. So you have basically two possibilities: > 1. Perform NAT on the router itself, provided it can (I guess it > doesn't) > 2. Connect the FreeBSD box directly to the Internet, i.e. replace the > router with it - that's what I'm doing at our site (medium business). > Depending on the interface your router has to connect to your ISP you > may need to obtain a sychronous communication adapter - we are using > SDLComm's N2, i.e. the FreeBSD 'sr' device. I am totally new to the basics of Unix networking, but as we today have a network that is like: 192.168.1.xxx ----- 192.168.1.1 [ router ] ----> dynamic IP towards Internet How should I best configure a FreeBSD box to handle the packetfiltering and where should I put it into the chain. I can't replace the router as our supplier have special software installed to handle the ISDN connection. But as it works today with this configuration shouldnt the router already handle some form of NAT? I need all the help I can get Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 7:20: 2 1999 Delivered-To: freebsd-net@freebsd.org Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82]) by hub.freebsd.org (Postfix) with ESMTP id 5121714ECF for ; Wed, 14 Apr 1999 07:19:42 -0700 (PDT) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.2/8.9.2) with ESMTP id PAA55177; Wed, 14 Apr 1999 15:26:15 +0200 (CEST) (envelope-from tseidmann@simultan.ch) Message-ID: <37149772.AE041694@simultan.ch> Date: Wed, 14 Apr 1999 15:26:10 +0200 From: Thomas Seidmann X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "thomas.uhrfelt@plymovent.se" Cc: "'freebsd-net@freebsd.org'" Subject: Re: steps in networking References: <01BE8681.3FC5E6B0.thomas.uhrfelt@plymovent.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Uhrfelt wrote: > > Is there anyone out there that could write up a little "manual" of the > different steps on what to do/edit to accomplish the below description > using FreeBSD + ipfw + NAT or FreeBSD + IPF + IPNAT.. > > INTERNAL (192.168.1.xx) ------ (192.168.1.1)FreeBSD box(192.168.2.2) > -------- (192.168.2.1)Congo Router(Dynamic IP)-------Internet [stuff deleted] I'm afraid you cannot handle this case with neither NAT variant mentioned above, since you need a public IP address on the machine doing the actual NAT. So you have basically two possibilities: 1. Perform NAT on the router itself, provided it can (I guess it doesn't) 2. Connect the FreeBSD box directly to the Internet, i.e. replace the router with it - that's what I'm doing at our site (medium business). Depending on the interface your router has to connect to your ISP you may need to obtain a sychronous communication adapter - we are using SDLComm's N2, i.e. the FreeBSD 'sr' device. Let me know if I can help you in case you choose the 2nd variant, though it's nicely documented in the FreeBSD Handbook and natd(8). > Thomas Uhrfelt Cheers, Thomas -- ========================================================== Thomas Seidmann Simultan AG, CH-6246 Altishofen, Switzerland mailto:tseidmann@simultan.ch tel +41.62.7489000 http://www.simultan.ch/~thomas fax +41.62.7489010 ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 8: 4:34 1999 Delivered-To: freebsd-net@freebsd.org Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id 8404115098 for ; Wed, 14 Apr 1999 08:04:21 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.200] by guepardo.vicosa.com.br with ESMTP (SMTPD32-5.00) id AFB025A0148; Wed, 14 Apr 1999 12:09:36 -0300 Message-ID: <3714AE1B.2DF1BBFC@tdnet.com.br> Date: Wed, 14 Apr 1999 12:02:51 -0300 From: User Grios X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: NIS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear gentleman, i seted NIS on my system as a server and client, but when i change my NIS password, using yppasswd, it is not changed to the server! Then i try to loggin with my NIS password, i am denied, i can only use my local password! Why my server does not use my NIS password, only the local one? I believe that my server is not using NIS to validate user, but the local database, how can i change that? Here goes some info: etosha$ uname -a FreeBSD etosha 2.2.8-STABLE FreeBSD 2.2.8-STABLE #0: Tue Apr 6 23:34:08 EST 1999 toor@etosha:/usr/src/sys/compile/ETOSHA i386 etosha$ rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100004 1 udp 1019 ypserv 100004 2 udp 1019 ypserv 100004 1 tcp 1023 ypserv 100004 2 tcp 1023 ypserv 100009 1 udp 1010 yppasswdd 100009 1 tcp 1022 yppasswdd 100007 2 udp 1006 ypbind 100007 2 tcp 1021 ypbind 100005 3 udp 1002 mountd 100005 3 tcp 1020 mountd 100005 1 udp 1002 mountd 100005 1 tcp 1020 mountd 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100024 1 udp 990 status 100024 1 tcp 1019 status 100008 1 udp 1026 walld etosha$ What is the problem? Thank you for your time and cooperation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 8:57:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id E6AA81537E; Wed, 14 Apr 1999 08:57:13 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA12023; Wed, 14 Apr 1999 11:55:03 -0400 (EDT) Message-Id: <199904141555.LAA12023@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 14 Apr 1999 10:48:29 -0400 To: questions@freebsd.org From: Dennis Subject: 2 or 4 port Ethernet cards Cc: net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Whats the current state of affairs with 2 and 4 port 10/100 adapters for Freebsd? Of the ones available, do any have a 4 port controller (rather than 4 separate processors)? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 8:59:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id CDC31157E4 for ; Wed, 14 Apr 1999 08:59:25 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.195] by guepardo.vicosa.com.br with ESMTP (SMTPD32-5.00) id AC9827A00B6; Wed, 14 Apr 1999 13:04:40 -0300 Message-ID: <3714BB04.502A33FB@tdnet.com.br> Date: Wed, 14 Apr 1999 12:57:56 -0300 From: User Grios X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: David Wolfskill , freebsd-net@freebsd.org Subject: Re: NIS References: <199904141507.IAA06851@pau-amma.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Wolfskill wrote: > > Did you put the "NIS magic cookie" in the passwd file? (That is, > place the line "+:::::::::" at the end of the file using "vipw"?) > > Cheers, > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 Yeah, now i can change passwd, etc! But users are not allowed to log in the system! If they try telnet, ftp, pop3, etc etc.... The error message is: login incorrect! I tried from console, and the same error occured! None NIS user can loggin the system The strangest stuff is that when i finger i get no problem, when i try to change a NIS USER passwd, no problem too, no user can log! Does anybody know what could it be ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 9:30: 3 1999 Delivered-To: freebsd-net@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id EF169157ED; Wed, 14 Apr 1999 09:29:56 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by HOUSTON with Internet Mail Service (5.5.2232.9) id <26XZLNCY>; Wed, 14 Apr 1999 10:27:36 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC03022B67E8@HOUSTON> From: Charles Randall To: questions@freebsd.org Cc: net@freebsd.org, Dennis Subject: RE: 2 or 4 port Ethernet cards Date: Wed, 14 Apr 1999 10:27:35 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For a historical perspective, search Deja News for "freebsd quad ethernet". http://www.dejanews.com/[ST_rn=qs]/dnquery.xp?QRY=freebsd+quad+ethernet&svcc lass=dnold In particular, the thread named "Dual or QUAD Ethernetcard for FreeBSD". Charles -----Original Message----- From: Dennis [mailto:dennis@etinc.com] Sent: Wednesday, April 14, 1999 8:48 AM To: questions@freebsd.org Cc: net@freebsd.org Subject: 2 or 4 port Ethernet cards Whats the current state of affairs with 2 and 4 port 10/100 adapters for Freebsd? Of the ones available, do any have a 4 port controller (rather than 4 separate processors)? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 9:41:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 6E6D6155FF; Wed, 14 Apr 1999 09:41:08 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by HOUSTON with Internet Mail Service (5.5.2232.9) id <26XZLNFW>; Wed, 14 Apr 1999 10:38:45 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC03022B67F5@HOUSTON> From: Charles Randall To: questions@freebsd.org Cc: net@freebsd.org, Dennis Subject: RE: 2 or 4 port Ethernet cards Date: Wed, 14 Apr 1999 10:38:43 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oops. Wrong thread. I meant meant "Dual or QUAD Ethernetcard for FreeBSD?". -----Original Message----- From: Charles Randall [mailto:crandall@matchlogic.com] Sent: Wednesday, April 14, 1999 10:28 AM To: questions@freebsd.org Cc: net@freebsd.org; Dennis Subject: RE: 2 or 4 port Ethernet cards For a historical perspective, search Deja News for "freebsd quad ethernet". http://www.dejanews.com/[ST_rn=qs]/dnquery.xp?QRY=freebsd+quad+ethernet&svcc lass=dnold In particular, the thread named "Dual or QUAD Ethernetcard for FreeBSD". Charles -----Original Message----- From: Dennis [mailto:dennis@etinc.com] Sent: Wednesday, April 14, 1999 8:48 AM To: questions@freebsd.org Cc: net@freebsd.org Subject: 2 or 4 port Ethernet cards Whats the current state of affairs with 2 and 4 port 10/100 adapters for Freebsd? Of the ones available, do any have a 4 port controller (rather than 4 separate processors)? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 10: 6:52 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5886614DC5 for ; Wed, 14 Apr 1999 10:06:46 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA15698 for net@FreeBSD.ORG; Wed, 14 Apr 1999 19:04:23 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id DC0BD8841; Wed, 14 Apr 1999 08:00:34 +0200 (CEST) Date: Wed, 14 Apr 1999 08:00:34 +0200 From: Ollivier Robert To: net@FreeBSD.ORG Subject: Re: if_ex.c driver and multicast Message-ID: <19990414080034.A19286@keltia.freenix.fr> Mail-Followup-To: net@FreeBSD.ORG References: <19990413222022.B14913@keltia.freenix.fr> <371421C3.B1553B2@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <371421C3.B1553B2@softweyr.com>; from Wes Peters on Tue, Apr 13, 1999 at 11:04:03PM -0600 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Wes Peters: > It depends on the level of support the chipset has for multicast. Well, it works under NT with IPv6 so there must be some kind of support. It is only that the driver doesn't support it. > I haven't looked at the 3c9xx series, but hope they're a bit better > than Intel. They seem to work w/o problem with the nice xl driver. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 10:23:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B4A281559F; Wed, 14 Apr 1999 10:23:08 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id NAA12588; Wed, 14 Apr 1999 13:20:53 -0400 (EDT) Message-Id: <199904141720.NAA12588@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 14 Apr 1999 12:14:17 -0400 To: Charles Randall , questions@freebsd.org From: Dennis Subject: RE: 2 or 4 port Ethernet cards Cc: net@freebsd.org In-Reply-To: <64003B21ECCAD11185C500805F31EC03022B67E8@HOUSTON> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:27 AM 4/14/99 -0600, Charles Randall wrote: >For a historical perspective, search Deja News for "freebsd quad ethernet". > >http://www.dejanews.com/[ST_rn=qs]/dnquery.xp?QRY=freebsd+quad+ethernetsvcc >lass=dnold > >In particular, the thread named "Dual or QUAD Ethernetcard for FreeBSD". > >Charles Well the Zynx and adaptec cards are both about the same design (pretty sucky)... and Im hoping to find something a little better. I dont believe that 4 bus mastering controllers sharing 1 PCI interface can do 4 X 100Mb/s. Its certainly not a high performance solution. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 10:29:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 816D3157FF for ; Wed, 14 Apr 1999 10:29:41 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA09373; Wed, 14 Apr 1999 13:27:10 -0400 (EDT) (envelope-from wollman) Date: Wed, 14 Apr 1999 13:27:10 -0400 (EDT) From: Garrett Wollman Message-Id: <199904141727.NAA09373@khavrinen.lcs.mit.edu> To: Wes Peters Cc: Ollivier Robert , net@FreeBSD.ORG Subject: Re: if_ex.c driver and multicast In-Reply-To: <371421C3.B1553B2@softweyr.com> References: <19990413222022.B14913@keltia.freenix.fr> <371421C3.B1553B2@softweyr.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > It depends on the level of support the chipset has for multicast. > Intel chips in general kind of suck at this. Apparently they haven't > even fixed it in the EEPro/100 chipset yet. > I haven't looked at the 3c9xx series, but hope they're a bit better > than Intel. 3Com NICs have historically been crap. Several of them had a one-bit multicast filter. Intel's have always had good support for multicast (but unlike DEC NICs they don't do perfect filtering). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 10:38:34 1999 Delivered-To: freebsd-net@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id DC9E715832; Wed, 14 Apr 1999 10:38:29 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id MAA24429; Wed, 14 Apr 1999 12:35:28 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 12:35:27 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: wollman@khavrinen.lcs.mit.edu Cc: hardware@freebsd.org Subject: Re: if_ex.c driver and multicast References: <19990413222022.B14913@keltia.freenix.fr> <371421C3.B1553B2@softweyr.com> <199904141727.NAA09373@khavrinen.lcs.mit.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14100.53656.953140.550591@avalon.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [redirecting the thread to "hardware":] Is there anyplace where one can still get tulip-based cards? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 10:39: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.cpd.ufv.br (mail.cpd.ufv.br [200.19.130.117]) by hub.freebsd.org (Postfix) with ESMTP id 7588D1571A for ; Wed, 14 Apr 1999 10:38:39 -0700 (PDT) (envelope-from grios@dpi.ufv.br) Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by mail.cpd.ufv.br (8.9.0/8.9.0) with SMTP id OAA13713; Wed, 14 Apr 1999 14:39:59 -0300 Received: from pontenova.dpi.ufv.br by vicosa.dpi.ufv.br (4.1/SMI-4.1) id AA03137; Wed, 14 Apr 99 14:41:16 EST Date: Wed, 14 Apr 1999 17:36:00 +0000 (UTC) From: "Gustavo V. G. Coelho Rios (35150-96)" To: David Wolfskill Cc: freebsd-net@freebsd.org Subject: Re: NIS In-Reply-To: <199904141622.JAA07125@pau-amma.whistle.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am using MD5! How can i be consistent about client/server! I believe that NIS support MD5, isn't it? Does anybody know about NIS support to MD5 ? Thank you very much! On Wed, 14 Apr 1999, David Wolfskill wrote: > OK; did you use DES for encrypting passwords, or MD5? I believe NIS > requires DES. At the very least, you certainly need to be consistent > between the NIS clients & NIS server(s) (with respect to encryption > technique used). > > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 10:52: 3 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A5ED915400 for ; Wed, 14 Apr 1999 10:51:57 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id KAA07300; Wed, 14 Apr 1999 10:49:30 -0700 (PDT) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id KAA29030; Wed, 14 Apr 1999 10:49:30 -0700 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id LAA17803; Wed, 14 Apr 1999 11:44:47 -0600 Message-ID: <3714D40F.B70B4C23@softweyr.com> Date: Wed, 14 Apr 1999 11:44:47 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: net@FreeBSD.ORG Subject: Re: if_ex.c driver and multicast References: <19990413222022.B14913@keltia.freenix.fr> <371421C3.B1553B2@softweyr.com> <19990414080034.A19286@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ollivier Robert wrote: > > According to Wes Peters: > > It depends on the level of support the chipset has for multicast. > > Well, it works under NT with IPv6 so there must be some kind of support. It > is only that the driver doesn't support it. Oh yes, you can do it, but it's not easy. I've worked on support for multicast on intel 586 and 596 chips on the VxWorks realtime system, but it's ugly. IIRC, the chip treats multicast packets like broadcast and hands all the packets to the driver to figure out, because it doesn't have enough ethernet multicast registration slots on the chip to do auto-filtering. This is being filtered through 3 or 4-year old memories, so take it with a grain of salt. ;^) > > I haven't looked at the 3c9xx series, but hope they're a bit better > > than Intel. > > They seem to work w/o problem with the nice xl driver. Much better, isn't it? Now if I could just get my blasted 3c905*B* to work as well as the 905s. Sigh. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Apr 14 11:53:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from ccsales.com (ccsales.com [216.0.22.30]) by hub.freebsd.org (Postfix) with ESMTP id D975A15798; Wed, 14 Apr 1999 11:53:13 -0700 (PDT) (envelope-from randyk@ccsales.com) Received: (from randyk@localhost) by ccsales.com (8.9.1/8.9.0) id LAA05978; Wed, 14 Apr 1999 11:51:46 -0700 (PDT) Message-ID: <19990414115146.24299@ccsales.com> Date: Wed, 14 Apr 1999 11:51:46 -0700 From: randyk To: Dennis , questions@FreeBSD.ORG Cc: net@FreeBSD.ORG Subject: Re: 2 or 4 port Ethernet cards Reply-To: randyk@ccsales.com References: <64003B21ECCAD11185C500805F31EC03022B67E8@HOUSTON> <199904141720.NAA12588@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199904141720.NAA12588@etinc.com>; from Dennis on Wed, Apr 14, 1999 at 12:14:17PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What about Compaq, they have a dual adapter? Randy Katz > and Im hoping to find something a little better. I dont believe that 4 bus > mastering > controllers sharing 1 PCI interface can do 4 X 100Mb/s. Its certainly not a > high > performance solution. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 13:49:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 5A7391570C for ; Wed, 14 Apr 1999 13:49:05 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA030122713; Wed, 14 Apr 1999 16:45:13 -0400 Date: Wed, 14 Apr 1999 16:45:13 -0400 (EDT) From: Bill Fumerola To: Dennis Cc: net@FreeBSD.ORG Subject: Re: 2 or 4 port Ethernet cards In-Reply-To: <199904141555.LAA12023@etinc.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 Wed, 14 Apr 1999, Dennis wrote: > Whats the current state of affairs with 2 and 4 port 10/100 adapters > for Freebsd? Of the ones available, do any have a 4 port controller > (rather than 4 separate processors)? A Intel PRO/100+ Dual Port Server Adapter will probe correctly, however I couldn't put any traffic over it. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Apr 14 13:57: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.cpd.ufv.br (mail.cpd.ufv.br [200.19.130.117]) by hub.freebsd.org (Postfix) with ESMTP id 63E801570C for ; Wed, 14 Apr 1999 13:56:52 -0700 (PDT) (envelope-from grios@dpi.ufv.br) Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by mail.cpd.ufv.br (8.9.0/8.9.0) with SMTP id RAA20673 for ; Wed, 14 Apr 1999 17:58:39 -0300 Received: from pontenova.dpi.ufv.br by vicosa.dpi.ufv.br (4.1/SMI-4.1) id AA04596; Wed, 14 Apr 99 17:59:54 EST Date: Wed, 14 Apr 1999 20:54:38 +0000 (UTC) From: "Gustavo V. G. Coelho Rios (35150-96)" To: freebsd-net@freebsd.org Subject: NIS and MD5 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, i am trying to get NIS working but no user can loggin! I can finger , this work properly, i can change a nis user password, but on NIS user can log into the system! Can anybody tell anything about that? I suppose that`s because i am using MD5 method for password! CAn NIS work under MD5 ? CAn anybody give any tip? Thank you for your time and cooperation. Best regards, Gustavo Rios To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 14:48:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 9577A15824 for ; Wed, 14 Apr 1999 14:48:33 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 23902 invoked from network); 14 Apr 1999 21:46:12 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 14 Apr 1999 21:46:12 -0000 Date: Wed, 14 Apr 1999 14:45:03 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Dennis Cc: questions@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: 2 or 4 port Ethernet cards In-Reply-To: <199904141555.LAA12023@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm using the znyx 2 and 4 port controllers. They're individual processors though. Work fine as near as I can tell. On Wed, 14 Apr 1999, Dennis wrote: > > Whats the current state of affairs with 2 and 4 port 10/100 adapters > for Freebsd? Of the ones available, do any have a 4 port controller > (rather than 4 separate processors)? > > Dennis > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 15:35:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 546DF153C1 for ; Wed, 14 Apr 1999 15:35:01 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA01041 for net@FreeBSD.ORG; Thu, 15 Apr 1999 00:32:39 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id CC3978841; Wed, 14 Apr 1999 23:43:53 +0200 (CEST) Date: Wed, 14 Apr 1999 23:43:53 +0200 From: Ollivier Robert To: net@FreeBSD.ORG Subject: Re: if_ex.c driver and multicast Message-ID: <19990414234353.A23610@keltia.freenix.fr> Mail-Followup-To: net@FreeBSD.ORG References: <19990413222022.B14913@keltia.freenix.fr> <371421C3.B1553B2@softweyr.com> <19990414080034.A19286@keltia.freenix.fr> <3714D40F.B70B4C23@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <3714D40F.B70B4C23@softweyr.com>; from Wes Peters on Wed, Apr 14, 1999 at 11:44:47AM -0600 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Wes Peters: > Much better, isn't it? Now if I could just get my blasted 3c905*B* to > work as well as the 905s. Sigh. My cards are pure 905, not B I think. I tried a 905B in another machine (under NT) and it was not possible to make the system see it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 18:46:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.dynamixweb.com (host01.dynamixweb.com [209.47.109.194]) by hub.freebsd.org (Postfix) with ESMTP id 66F9314FDF for ; Wed, 14 Apr 1999 18:46:24 -0700 (PDT) (envelope-from svetzal@icom.ca) Received: from blazer (cr609409-a.pr1.on.wave.home.com [24.112.98.34]) by mail.dynamixweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 2G6LC0VV; Wed, 14 Apr 1999 21:47:15 -0400 From: "Steven Vetzal" To: Subject: Bridging Date: Wed, 14 Apr 1999 21:46:38 -0400 Message-ID: <001901be86e1$d0c9c400$7ffea8c0@blazer.pr1.on.wave.home.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 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I've built a config with two interfaces (xl0 and mx0) and would like to use bridging... Despite the man page not mentioning either interface as supported, I built the kernel config anyways and went to try it out (Stop! Don't throw that tomato! 8^). In fact it almost works (I can ping the IP address of the mx0 interface on systems connected through xl0 which is unnumbered). Both interfaces _say_ they have the PROMISC flag set (I'm assuming this might be core to some interfaces supporting briding or not?) but I can't ping all the way through the bridge from hosts on xl0 to hosts on mx0. Have I got a hope-in-hell of making this work or should I just give up now 8^) Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 18:58:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.dynamixweb.com (host01.dynamixweb.com [209.47.109.194]) by hub.freebsd.org (Postfix) with ESMTP id 6659E14F69 for ; Wed, 14 Apr 1999 18:58:53 -0700 (PDT) (envelope-from svetzal@icom.ca) Received: from blazer (cr609409-a.pr1.on.wave.home.com [24.112.98.34]) by mail.dynamixweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 2G6LC0V5; Wed, 14 Apr 1999 21:59:43 -0400 From: "Steven Vetzal" To: Subject: RE: Bridging Date: Wed, 14 Apr 1999 21:59:08 -0400 Message-ID: <001f01be86e3$8d459b80$7ffea8c0@blazer.pr1.on.wave.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <001901be86e1$d0c9c400$7ffea8c0@blazer.pr1.on.wave.home.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well that was silly of me - I guess it would help to mention what OS I'm running on that box 8^) My environment is FreeBSD 3.1-RELEASE... -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Steven Vetzal Sent: April 14, 1999 9:47 PM To: freebsd-net@FreeBSD.ORG Subject: Bridging Greetings, I've built a config with two interfaces (xl0 and mx0) and would like to use bridging... Despite the man page not mentioning either interface as supported, I built the kernel config anyways and went to try it out (Stop! Don't throw that tomato! 8^). In fact it almost works (I can ping the IP address of the mx0 interface on systems connected through xl0 which is unnumbered). Both interfaces _say_ they have the PROMISC flag set (I'm assuming this might be core to some interfaces supporting briding or not?) but I can't ping all the way through the bridge from hosts on xl0 to hosts on mx0. Have I got a hope-in-hell of making this work or should I just give up now 8^) Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 19:33:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.scl.ameslab.gov (mailhub.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (Postfix) with ESMTP id 0ABBC1513A for ; Wed, 14 Apr 1999 19:33:52 -0700 (PDT) (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.ether.scl.ameslab.gov ([147.155.137.54]) by mailhub.scl.ameslab.gov with esmtp (Exim 1.90 #1) id 10Xbws-000745-00; Wed, 14 Apr 1999 21:32:14 -0500 Date: Wed, 14 Apr 1999 21:31:30 -0500 From: Guy Helmer To: Steven Vetzal Cc: freebsd-net@FreeBSD.ORG Subject: RE: Bridging In-Reply-To: <001f01be86e3$8d459b80$7ffea8c0@blazer.pr1.on.wave.home.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 Wed, 14 Apr 1999, Steven Vetzal wrote: > Well that was silly of me - I guess it would help to mention what OS I'm > running on that box 8^) > > My environment is FreeBSD 3.1-RELEASE... > > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Steven Vetzal > Sent: April 14, 1999 9:47 PM > To: freebsd-net@FreeBSD.ORG > Subject: Bridging > > I've built a config with two interfaces (xl0 and mx0) and would like to use > bridging... Well, neither if_xl.c nor if_mx.c have support for bridging in 3.1. A quick perusal of the sources indicates that it shouldn't be too hard to whip up patches to support it, though. Give me a couple of days and I'll see what I can come up with... Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 14 22:46:10 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 71C6C150DB for ; Wed, 14 Apr 1999 22:46:07 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA11810; Thu, 15 Apr 1999 05:27:30 +0200 From: Luigi Rizzo Message-Id: <199904150327.FAA11810@labinfo.iet.unipi.it> Subject: Re: Bridging To: ghelmer@scl.ameslab.gov (Guy Helmer) Date: Thu, 15 Apr 1999 05:27:30 +0200 (MET DST) Cc: svetzal@cujo2.icom.ca, freebsd-net@FreeBSD.ORG In-Reply-To: from "Guy Helmer" at Apr 14, 99 09:31:11 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 926 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Well that was silly of me - I guess it would help to mention what OS I'm > > running on that box 8^) > > > > My environment is FreeBSD 3.1-RELEASE... ... > > I've built a config with two interfaces (xl0 and mx0) and would like to use > > bridging... > > Well, neither if_xl.c nor if_mx.c have support for bridging in 3.1. A > quick perusal of the sources indicates that it shouldn't be too hard to > whip up patches to support it, though. Give me a couple of days and I'll > see what I can come up with... yup -- thanks, Guy luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 15 8:22:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from etosha (modem08.tdnet.com.br [200.236.148.201]) by hub.freebsd.org (Postfix) with SMTP id 3415614D24 for ; Thu, 15 Apr 1999 08:22:33 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: (qmail 8663 invoked from network); 15 Apr 1999 15:21:01 -0000 Received: from softdnserror (HELO tdnet.com.br) (192.168.0.1) by softdnserror with SMTP; 15 Apr 1999 15:21:01 -0000 Message-ID: <3716039F.C9451246@tdnet.com.br> Date: Thu, 15 Apr 1999 12:19:59 -0300 From: User Grios X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: NIS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear gentleman, I am trying to get NIS working under FreeBSD 2.2.8-Stable. I seted it up, now i can return any information about any NIS user, but no NIS user can log in! Does anybody here have any idea about what is wrong? Thank you for your time and cooperation, Gustavo Rios. PS: My crypt method is MD5, not DES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 15 8:36:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 9D7941530C for ; Thu, 15 Apr 1999 08:36:37 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10Xo9c-000H3X-00 for freebsd-net@freebsd.org; Thu, 15 Apr 1999 22:34:12 +0700 Date: Thu, 15 Apr 1999 22:34:12 +0700 (ALMST) From: Boris Popov To: freebsd-net@freebsd.org Subject: NetWare client 1.3beta7 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 Hello, Again, just next release. It includes next fixes and features: - Connection deadlock problem solved. - New ncpurge utility added. - mount_nwfs command line syntax extended to use it in fstab file, please reread man page. - ncpurge utility added. - New ncpsvc command added. You can now remotely load/unload nlms, execute ncf files, mount/dismount volumes, enable/disable logins and syncronise time on NetWare server with Unix box. - Adapted for -current as of 12.04.1999. URL: ftp://ftp.butya.kz/pub/nwlib/ncplib.tar.gz P.S. Although is beta, the development version runs for a three weeks without any crashes. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 15 9:52:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id 2833915931 for ; Thu, 15 Apr 1999 09:52:14 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailf.telia.com (8.8.8/8.8.8) with ESMTP id SAA10887 for ; Thu, 15 Apr 1999 18:49:43 +0200 (CEST) Received: from tu (t4o68p71.telia.com [62.20.139.191]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id SAA04984 for ; Thu, 15 Apr 1999 18:49:42 +0200 (CEST) Received: by localhost with Microsoft MAPI; Thu, 15 Apr 1999 18:45:59 +0200 Message-ID: <01BE8770.345C6570.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'freebsd-net@freebsd.org'" Subject: ipfw rules Date: Thu, 15 Apr 1999 18:45:51 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 am writing my firewallrules, but I am a little unsure on what to allow/disallow so I am thinking about building my rc.firewall based on the script on this location http://www.metronet.com/~pgilley/freebsd/ipfw/chris.html Do any of you have any comments on this one ( especially concerning the ICMP thing, is that solvable today? ) / Thomas Uhrfelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 15 10: 1:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 6FA53152F1 for ; Thu, 15 Apr 1999 10:01:36 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA26324; Thu, 15 Apr 1999 12:58:35 -0400 (EDT) Date: Thu, 15 Apr 1999 12:58:34 -0400 (EDT) From: "Matthew N. Dodd" To: Boris Popov Cc: freebsd-net@FreeBSD.ORG Subject: Re: NetWare client 1.3beta7 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 Good job Boris. I'm really pleased with the support you've added. Is there any provision in the various Netware protocols for remote console access? If so do you have plans to support it? Thanks. On Thu, 15 Apr 1999, Boris Popov wrote: > Again, just next release. It includes next fixes and features: > > - Connection deadlock problem solved. > - New ncpurge utility added. > - mount_nwfs command line syntax extended to use it in fstab file, > please reread man page. > - ncpurge utility added. > - New ncpsvc command added. You can now remotely load/unload nlms, > execute ncf files, mount/dismount volumes, enable/disable logins > and syncronise time on NetWare server with Unix box. > - Adapted for -current as of 12.04.1999. > > URL: ftp://ftp.butya.kz/pub/nwlib/ncplib.tar.gz > > P.S. Although is beta, the development version runs for a three weeks > without any crashes. > -- > Boris Popov > http://www.butya.kz/~bp/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 15 18:13:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id E268514D07 for ; Thu, 15 Apr 1999 18:12:36 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10Xx8l-000HJB-00; Fri, 16 Apr 1999 08:09:55 +0700 Date: Fri, 16 Apr 1999 08:09:55 +0700 (ALMST) From: Boris Popov To: "Matthew N. Dodd" Cc: freebsd-net@FreeBSD.ORG Subject: Re: NetWare client 1.3beta7 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 15 Apr 1999, Matthew N. Dodd wrote: > Is there any provision in the various Netware protocols for remote console > access? If so do you have plans to support it? Well, if we speaking about NetWare 3.x, the only protocol for remote access is RSPX. It isn't well (officially) documented. For NetWare 4.x I'm preffer telnet session. In any case, I'm slowly make patches for 'doscmd' to emulate VLM's interrupt set. This should allow to run many DOS utilites. The only problem is a huge number of calls to implement. > > On Thu, 15 Apr 1999, Boris Popov wrote: > > Again, just next release. It includes next fixes and features: > > > > URL: ftp://ftp.butya.kz/pub/nwlib/ncplib.tar.gz > > -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 16 4:25:24 1999 Delivered-To: freebsd-net@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id CC86614D45; Fri, 16 Apr 1999 04:25:15 -0700 (PDT) (envelope-from Dimitri.Tombroff@sun.com) Received: from France.Sun.COM ([129.157.188.1]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id EAA10391; Fri, 16 Apr 1999 04:22:52 -0700 (PDT) Received: from sunchorus.france.sun.com by France.Sun.COM (SMI-8.6/SMI-SVR4-sd.fkk205) id NAA05875; Fri, 16 Apr 1999 13:22:48 +0200 Received: from tumba.France.Sun.COM by sunchorus.france.sun.com (SMI-8.6/SMI-SVR4) id NAA17676; Fri, 16 Apr 1999 13:22:48 +0200 Received: from sun.com by tumba.France.Sun.COM (SMI-8.6/SMI-SVR4) id NAA01856; Fri, 16 Apr 1999 13:18:18 +0200 Message-ID: <37171C7A.1D6F5A02@sun.com> Date: Fri, 16 Apr 1999 13:18:18 +0200 From: Dimitri Tombroff Organization: Sun Microsystems X-Mailer: Mozilla 4.51 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Default route for multicast IP addresses Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, It seems that all multicast IP addresses are associated to the default route. > route get 225.332.324.213 route to: 225.77.68.213 destination: default mask: default .... I can't see what part of the routing kernel code does that, or what initialisation utility/script configure the routing table to obtain that behavior, thanks for any help, Dimiti To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 16 7:30:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id D1831153FD; Fri, 16 Apr 1999 07:30:51 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA25127; Fri, 16 Apr 1999 10:28:23 -0400 (EDT) (envelope-from wollman) Date: Fri, 16 Apr 1999 10:28:23 -0400 (EDT) From: Garrett Wollman Message-Id: <199904161428.KAA25127@khavrinen.lcs.mit.edu> To: Dimitri Tombroff Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Default route for multicast IP addresses In-Reply-To: <37171C7A.1D6F5A02@sun.com> References: <37171C7A.1D6F5A02@sun.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > It seems that all multicast IP addresses are associated to the default > route. > I can't see what part of the routing kernel code does that, or what > initialisation utility/script > configure the routing table to obtain that behavior, The part that sets up a default route. A zero-bit-long mask matches all addresses -- that's what makes it a default route. If you want multicasts to go out some other interface, create a route specifically for them. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 16 10:11:23 1999 Delivered-To: freebsd-net@freebsd.org Received: from dpiran.net (unknown [195.96.144.10]) by hub.freebsd.org (Postfix) with ESMTP id 7C41D1540F for ; Fri, 16 Apr 1999 10:10:06 -0700 (PDT) (envelope-from nader@dpiran.net) Received: from donya.dpi.net.ir (donya.dpi.net.ir [195.96.144.140]) by dpiran.net (8.9.1/8.9.1) with ESMTP id VAA04161 for ; Fri, 16 Apr 1999 21:37:57 +0430 (IDT) Received: from donya.dpi.net.ir (donya.dpi.net.ir [195.96.144.140]) by donya.dpi.net.ir (8.9.1/8.9.1) with SMTP id VAA19766; Fri, 16 Apr 1999 21:37:38 +0330 (IST) Message-Id: <199904161807.VAA19766@donya.dpi.net.ir> Date: Fri, 16 Apr 1999 21:37:38 +0330 (IST) From: Nader Atoofi Reply-To: Nader Atoofi Subject: RIPV2 To: freebsd-net@freebsd.org Cc: nader@dpiran.net MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: bTQHrN/5sWpVExXQYxytDw== X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 i86pc i386 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi you all, As my firewall has been resided on between our Cisco router, I'm going to setup RIP for exchanging routing information between our routers and firewalls.(As we have two firewall, it is very important for availability. I setup our routers(Cisco 2500) and Firewalls(FreeBSD 2.2.6-RELEASE) to handle RIPV1 and it worked good in our network except that our supernet didn't distribute completely in RIP. For resolving it, I had to switch to RIPV2, and I setup our routers and firewall so, but the RIP information don't completely distribute between router and firewall. 1. How can I distribute static route via RIP. For example, I do it in cisco with router rip redistribute static but I don't know how to do it on our FREEBSD box. 2. As I explained, our firewalls don't work properly in RIPV2. As I worked a lot on it, I understand that it's working good in one of it interfaces, but not in the other interface. I added if=ed0 if=ed1 in my /etc/gateways but it didn't work. Can anyone help me in this regard? --Nader Nader Atoofi === Unix and Network Administrator === === DP IRAN Co. Tehran Iran === === E_Mail : nader@dpi.net.ir === === E_Mail : nader@dpiran.net === Web : http://atoofi.com DP IRAN Web : http://dpiran.net/~nader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 16 10:25:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from repulse.cnchost.com (repulse.concentric.net [207.155.248.4]) by hub.freebsd.org (Postfix) with ESMTP id 4AA741597F for ; Fri, 16 Apr 1999 10:25:39 -0700 (PDT) (envelope-from skoh@vixell.com) Received: from vixell.com ([207.82.123.131]) by repulse.cnchost.com (8.9.3/) id NAA04172; Fri, 16 Apr 1999 13:23:15 -0400 (EDT) [ConcentricHost SMTP Relay 1.5] Message-ID: <371772C7.8A9FB1F9@vixell.com> Date: Fri, 16 Apr 1999 10:26:31 -0700 From: "Steve W. Koh" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en,ko MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: subscribe freebsd-net Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe freebsd-net -- Steve W. Koh swkoh@usa.net 510-523-6606 x.424 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 16 14:59:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from efex.light1.net (unknown [207.76.225.3]) by hub.freebsd.org (Postfix) with ESMTP id 2F3CC158DD; Fri, 16 Apr 1999 14:59:21 -0700 (PDT) (envelope-from root@efex.light1.net) Received: from localhost (root@localhost) by efex.light1.net (8.9.2/8.9.1) with ESMTP id RAA15043; Fri, 16 Apr 1999 17:57:12 -0400 (EDT) Date: Fri, 16 Apr 1999 17:57:03 -0400 (EDT) From: System Administrator To: net@freebsd.org, security@freebsd.org Subject: unexpected rebooting 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... my box has been rebooting unexpectedly.. word around has been a new dos.. i have been told im out of mbuf clusters.. but im not really sure what to do around when the box reboots i get arplookup and llook errors root@efex:/var/log# zgrep arplookup messages* messages.1:Apr 16 14:30:03 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:05 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:06 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:11 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:12 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:22 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:23 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:24 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo messages.1:Apr 16 14:30:30 efex /kernel: arplookup 207.76.225.58 failed: could not allocate llinfo then the box reboots.. not really any more information to give.. but if there is something i can give please tell me any help will be appreciated. thanks Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 17 1:44:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from amanda.qmpgmc.ac.uk (amanda.qmpgmc.ac.uk [194.81.5.1]) by hub.freebsd.org (Postfix) with ESMTP id B5AF8151A4; Sat, 17 Apr 1999 01:44:29 -0700 (PDT) (envelope-from greg@qmpgmc.ac.uk) Received: from greg (gquinlan [194.81.0.56]) by amanda.qmpgmc.ac.uk (8.9.3/8.9.3) with SMTP id JAA17018; Sat, 17 Apr 1999 09:41:58 +0100 (BST) Reply-To: "Greg Quinlan" From: "Greg Quinlan" To: "System Administrator" , , Subject: Re: unexpected rebooting Date: Wed, 21 Apr 1999 09:42:02 +0100 Message-ID: <01be8bd2$d3fcb6a0$380051c2@greg.qmpgmc.ac.uk> 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 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike, I have had a similar thing, my server unexpectedly reboots, I run 3.1-Release but intend on going to 3.1-Stable. I was told that it may have something the do with an error in VM. I do not get any ARP errors! (Our problems may be unrelated) Greg -----Original Message----- From: System Administrator To: net@FreeBSD.ORG ; security@FreeBSD.ORG Date: 16 April 1999 22:58 Subject: unexpected rebooting >hi... >my box has been rebooting unexpectedly.. word around has been a new dos.. >i have been told im out of mbuf clusters.. but im not really sure what to >do >around when the box reboots i get arplookup and llook errors >root@efex:/var/log# zgrep arplookup messages* >messages.1:Apr 16 14:30:03 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:05 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:06 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:11 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:12 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:22 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:23 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:24 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo >messages.1:Apr 16 14:30:30 efex /kernel: arplookup 207.76.225.58 failed: >could not allocate llinfo > >then the box reboots.. >not really any more information to give.. but if there is something i can >give please tell me >any help will be appreciated. > >thanks >Mike > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-security" 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 Apr 17 8:21: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id A27FE14C22 for ; Sat, 17 Apr 1999 08:20:59 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailf.telia.com (8.8.8/8.8.8) with ESMTP id RAA02331 for ; Sat, 17 Apr 1999 17:18:32 +0200 (CEST) Received: from tu (t1o68p13.telia.com [62.20.138.13]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id RAA23859 for ; Sat, 17 Apr 1999 17:18:15 +0200 (CEST) Received: by localhost with Microsoft MAPI; Sat, 17 Apr 1999 17:14:35 +0200 Message-ID: <01BE88F5.C4660D20.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'freebsd-net@freebsd.org'" Subject: DHCP - IPFW - Controlling IPs Date: Sat, 17 Apr 1999 17:14:25 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 have now sucessfully installed ISC:s DHCP server on my FreeBSD box to pass out IP:s etc. to the users on our local network, but I Have a little thing grinding on my mind, as I am going to use DUMMYNET and IPFW to regulate what users can and cannot do on other networks. Is there any way that I can check ( periodically or all the time ) that the IP the packet is coming from really is the one that is assigned by the DHCP daemon? What I mean is, for my ipfw rules/pipes to work, I need to be sure that the user has just that IP I have assigned to him. In other words, so he can't go in and change his Win95/NT/Mac and turn off DHCP and assign an IP on his own.. Is this possible to control at all? / Thomas Uhrfelt Datortekniker PlymoVent AB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 17 8:32:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id DAEEC153A0 for ; Sat, 17 Apr 1999 08:32:37 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA16705; Sat, 17 Apr 1999 15:14:45 +0200 From: Luigi Rizzo Message-Id: <199904171314.PAA16705@labinfo.iet.unipi.it> Subject: Re: DHCP - IPFW - Controlling IPs To: thomas.uhrfelt@plymovent.se Date: Sat, 17 Apr 1999 15:14:45 +0200 (MET DST) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <01BE88F5.C4660D20.thomas.uhrfelt@plymovent.se> from "Thomas Uhrfelt" at Apr 17, 99 05:14:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 659 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have now sucessfully installed ISC:s DHCP server on my FreeBSD box to pass out IP:s etc. to the users on our local network, but I ... > networks. Is there any way that I can check ( periodically or all the time ) that the IP the packet is coming from really is the one that the thing you can do is to hardwire (i think there is an option in the 'arp' command, but you might want to make it work together with DHCP) your ARP table so you might be passing out traffic, but the pkts generated by your router will never get to the correct destination. But other than that, no, IPFW does not currently even know the MAC address and so cannot check. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 17 9:50:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from nygate.undp.org (nygate.undp.org [192.124.42.3]) by hub.freebsd.org (Postfix) with ESMTP id A46EA14EC2 for ; Sat, 17 Apr 1999 09:50:33 -0700 (PDT) (envelope-from chaos@xonix.com) Received: from umka.undp.org (umka.undp.org [192.124.42.40]) by nygate.undp.org (8.9.1/8.9.1/1.13) with ESMTP id MAA28152 for ; Sat, 17 Apr 1999 12:48:09 -0400 (EDT) Received: from inet01.hq.undp.org ([192.168.69.4]) by umka.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAA6908 for ; Sat, 17 Apr 1999 12:46:57 -0400 Received: from xonix.com ([207.172.89.50]) by inet01.hq.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAA6EA0; Sat, 17 Apr 1999 12:44:45 -0400 Message-ID: <3718BA5F.41DF3675@xonix.com> Date: Sat, 17 Apr 1999 12:44:15 -0400 From: Ugen X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: "thomas.uhrfelt@plymovent.se" Cc: "'freebsd-net@freebsd.org'" Subject: Re: DHCP - IPFW - Controlling IPs References: <01BE88F5.C4660D20.thomas.uhrfelt@plymovent.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't think something like this exists (although theoretically if they are on a local network with some modification it would be possible to also filter by an Ethernet address) - however this is one reason IP address based security can only be used for Unix hosts and other "trusted" systems where only trusted people are able to set the addresses (presumably). Well, if you are in a switched environment you can probably make your switch/router somehow maintain IP to MAC address consistency. Other then that whenever dealing with individual windows etc. workstations it is crucial to have some other kind of security available... --Ugen Thomas Uhrfelt wrote: > I have now sucessfully installed ISC:s DHCP server on my FreeBSD box to pass out IP:s etc. to the users on our local network, but I > Have a little thing grinding on my mind, as I am going to use DUMMYNET and IPFW to regulate what users can and cannot do on other > networks. Is there any way that I can check ( periodically or all the time ) that the IP the packet is coming from really is the one that > is assigned by the DHCP daemon? What I mean is, for my ipfw rules/pipes to work, I need to be sure that the user has just > that IP I have assigned to him. In other words, so he can't go in and change his Win95/NT/Mac and turn off DHCP and assign an > IP on his own.. Is this possible to control at all? > > / > > Thomas Uhrfelt > Datortekniker > > PlymoVent AB > > 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 Apr 17 11: 6:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.dynamixweb.com (host01.dynamixweb.com [209.47.109.194]) by hub.freebsd.org (Postfix) with ESMTP id 361B814D63 for ; Sat, 17 Apr 1999 11:06:26 -0700 (PDT) (envelope-from svetzal@icom.ca) Received: from blazer (cr609409-a.pr1.on.wave.home.com [24.112.98.34]) by mail.dynamixweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id 2G6LC08Z; Sat, 17 Apr 1999 14:07:12 -0400 From: "Steven Vetzal" To: Subject: Dummynet & Bridging Date: Sat, 17 Apr 1999 14:06:45 -0400 Message-ID: <000601be88fd$0ed07b00$7ffea8c0@blazer.pr1.on.wave.home.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 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I've been having some fun trying to get dummynet working on a bridging configuration, and was wondering if what I'm trying to do is implemented. I'm doing this on 3.1-RELEASE I have a system set up as a bridge between a 100-Base-T and a 10-Base-T network, the bridging works great, and ipfw rules also seem to work fine through it. The trouble comes in when I try to use dummynet pipes. I've been doing my testing with ping, and the two rules allow bi-directional icmp traffic through the bridge between two particular hosts (and I can tell the rules are used because the counters are incrementing each icmp packet sent) 00600 1211 72660 allow ip from 192.168.254.1 to 192.168.254.132 out xmit mx0 00620 1220 73200 allow ip from 192.168.254.132 to 192.168.254.1 out xmit xl0 Now that I know traffic is working great through the rules, I try adding a "pipe" rule higher up the chain to redirect the packets: ipfw add 500 pipe 1 ip from 192.168.254.1 to 192.168.254.132 out via mx0 The .132 host continues to ping, and tcpdump shows the packet hitting his side of the bridge, hitting the other side of the bridge, the .1 host response hitting the other side of the bridge, but the response doesn't get carried through the bridge back to the source host. Now dummynet(4) says that the ipfw filter is invoked only once on a bridge, on the input path. But my attempt at: ipfw add 500 pipe 1 ip from 192.168.254.1 to 192.168.254.132 in via xl0 and all variations I can think of show no traffic flowing through the rule. Now I'm sure I've got this all confused, but can't find documentation anywhere on how this stuff works... And I'm not even sure it's supposed to. The reason I'm not sure it's supposed to work is because if I set up the following rules: 00500 60 3600 pipe 1 ip from 192.168.254.8 to 192.168.254.132 out 00510 16 960 pipe 2 ip from 192.168.254.132 to 192.168.254.8 in I can ping the _bridge host_ and receive a response and the two rule counters increment as I figure they would. However, bridging has to be working to some degree because the interface I ping is not the one connected to this host! (the interfaced attached to my test host is unnumbered) Anyways, I'm thoroughly confused. Anyone out there have any resources or suggestions for me? Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 17 11:36:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id EAC2714D87 for ; Sat, 17 Apr 1999 11:36:14 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA16929; Sat, 17 Apr 1999 18:18:27 +0200 From: Luigi Rizzo Message-Id: <199904171618.SAA16929@labinfo.iet.unipi.it> Subject: Re: Dummynet & Bridging To: svetzal@cujo2.icom.ca (Steven Vetzal) Date: Sat, 17 Apr 1999 18:18:27 +0200 (MET DST) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <000601be88fd$0ed07b00$7ffea8c0@blazer.pr1.on.wave.home.com> from "Steven Vetzal" at Apr 17, 99 02:06:26 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2503 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Greetings, > > I've been having some fun trying to get dummynet working on a bridging > configuration, and was wondering if what I'm trying to do is implemented. > I'm doing this on 3.1-RELEASE i am assuming that you did it on 3.1 stable because 3.1-R was missing some pieces in the device driver(s) etc. > 00600 1211 72660 allow ip from 192.168.254.1 to 192.168.254.132 out xmit > mx0 > 00620 1220 73200 allow ip from 192.168.254.132 to 192.168.254.1 out xmit > xl0 > > Now that I know traffic is working great through the rules, I try adding a > "pipe" rule higher up the chain to redirect the packets: > > ipfw add 500 pipe 1 ip from 192.168.254.1 to 192.168.254.132 out via mx0 > > The .132 host continues to ping, and tcpdump shows the packet hitting his > side of the bridge, hitting the other side of the bridge, the .1 host > response hitting the other side of the bridge, but the response doesn't get > carried through the bridge back to the source host. try sysctl -w net.inet.ip.firewall.one_pass=1 so that the pkt is not reinjected in the firewall after the pipe (should not happen with bridging, but still...) This said, there might be some bug somewhere, i could not test this code (interaction of bridging and dummynet) on the 3.x branch, only on 2.2.x. If you can, i suggest to put some diagnostic msg near the beginning of bdg_forward, in the place where a dummynet pkt is recognised, to understand what happens to the pkt. > Now dummynet(4) says that the ipfw filter is invoked only once on a bridge, > on the input path. But my attempt at: > > ipfw add 500 pipe 1 ip from 192.168.254.1 to 192.168.254.132 in via xl0 > > and all variations I can think of show no traffic flowing through the rule. > > Now I'm sure I've got this all confused, but can't find documentation > anywhere on how this stuff works... And I'm not even sure it's supposed to. > The reason I'm not sure it's supposed to work is because if I set up the > following rules: > > 00500 60 3600 pipe 1 ip from 192.168.254.8 to 192.168.254.132 out > 00510 16 960 pipe 2 ip from 192.168.254.132 to 192.168.254.8 in > > I can ping the _bridge host_ and receive a response and the two rule > counters increment as I figure they would. However, bridging has to be > working to some degree because the interface I ping is not the one connected > to this host! (the interfaced attached to my test host is unnumbered) well, that's only a thing done in the reception side. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 17 15: 5:22 1999 Delivered-To: freebsd-net@freebsd.org Received: from netserver.pth.com (pth.com [206.165.121.73]) by hub.freebsd.org (Postfix) with ESMTP id 781BB152B5 for ; Sat, 17 Apr 1999 15:05:19 -0700 (PDT) (envelope-from paul@pth.com) Received: from yosemite.pth.com ([192.42.172.9] helo=yosemite) by netserver.pth.com with smtp (Exim 2.12 #1) id 10YdAr-0000DA-00 for freebsd-net@freebsd.org; Sat, 17 Apr 1999 18:02:53 -0400 To: freebsd-net@freebsd.org Subject: NATD and ESP packets Date: Sat, 17 Apr 1999 18:01:20 -0400 From: Paul Haddad Reply-To: paul@pth.com X-Mailer: by Apple MailViewer (2.106) Message-Id: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I'm trying to setup a VPN from one of my machines through my freebsd router to my employers network. The package that I'm using sends out and receives esp (ip-proto-50) type packets, is there any way to get natd to handle these packets? I have natd set up now and it handles tcp and udp packets with no problems, but it seems to just ignore the esp packets (i.e. they get sent out, but src IP address is the address of my internal machine not the freebsd router). If natd can't handle esp packets is there any other way to do nat with esp packets? Thanks, --- Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 17 17:31:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from at.dotat.com (zed.dotat.com [203.2.134.254]) by hub.freebsd.org (Postfix) with ESMTP id DDB8B14EA4 for ; Sat, 17 Apr 1999 17:31:33 -0700 (PDT) (envelope-from hart@at.dotat.com) Received: from at.dotat.com (localhost.dotat.com [127.0.0.1]) by at.dotat.com (8.8.8/8.8.8) with ESMTP id KAA01569; Sun, 18 Apr 1999 10:00:05 +0930 (CST) Message-Id: <199904180030.KAA01569@at.dotat.com> To: "thomas.uhrfelt@plymovent.se" Cc: "'freebsd-net@freebsd.org'" Subject: Re: DHCP - IPFW - Controlling IPs In-reply-to: Your message of "Sat, 17 Apr 1999 17:14:25 +0200." <01BE88F5.C4660D20.thomas.uhrfelt@plymovent.se> Date: Sun, 18 Apr 1999 10:00:05 +0930 From: Leigh Hart Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Thomas, Thomas Uhrfelt wrote: > > I have now sucessfully installed ISC:s DHCP server on my FreeBSD > box to pass out IP:s etc. to the users on our local network, but I > Have a little thing grinding on my mind, as I am going to use DUMMYNET > and IPFW to regulate what users can and cannot do on other networks. > > Is there any way that I can check ( periodically or all the time ) > that the IP the packet is coming from really is the one that is > assigned by the DHCP daemon? What I mean is, for my ipfw rules/pipes > to work, I need to be sure that the user has just that IP I have > assigned to him. In other words, so he can't go in and change his > Win95/NT/Mac and turn off DHCP and assign an IP on his own.. > Is this possible to control at all? I don't believe there are any existing structures / programs in place to do this specifically, however, what you *can* do is monitor what's going on with arp (as long as the FreeBSD box is hearing all of the arp packets, that is). Periodically traverse the arp table (either by writing some C/Perl or using "arp -an" in a shell script) and compare the results against your authoritive list (ie: the DHCP config). Then you can respond to illegal MAC/IP pairs in a number of ways, in order of difficulty to implement: * log the information and review in retrospect, useful if your HW has physically unchangable Mac addresses, then reprimand the person; * flood ping/nuke/whatever the IP address until the offending machine crashes and dies; * hard code a proxy arp for the IP address, preventing traffic flow; or * sniff the wire and respond to all the IP's sourced packets with an ICMP "administratively-prohibited" message. Cheers Leigh -- | "By the time they had diminished | Leigh Hart, | | from 50 to 8, the other dwarves | CCNA - http://www.cisco.com/ | | began to suspect 'Hungry' ..." | GPO Box 487 Adelaide SA 5001 | | -- Gary Larson, "The Far Side" | http://www.dotat.com/hart/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 18 13: 1:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from sucuri.amazon.com.br (sucuri.amazon.com.br [200.241.240.1]) by hub.freebsd.org (Postfix) with ESMTP id 3DAB614E09 for ; Sun, 18 Apr 1999 13:01:20 -0700 (PDT) (envelope-from aldrin@americasnet.com) Received: from athome.logicStudios.org (root@pm4-s36.amazon.com.br [200.242.245.165]) by sucuri.amazon.com.br (8.9.3/8.9.3) with ESMTP id QAA32406; Sun, 18 Apr 1999 16:58:50 -0300 Received: from localhost.logicStudios.org (aldrin@localhost.logicStudios.org [127.0.0.1]) by athome.logicStudios.org (8.8.8/8.8.8) with ESMTP id RAA02049; Sun, 18 Apr 1999 17:07:55 -0300 (EST) (envelope-from aldrin@americasnet.com) Date: Sun, 18 Apr 1999 17:07:54 -0300 (EST) From: Aldrin L X-Sender: aldrin@athome.logicStudios.org To: Boris Popov Cc: freebsd-net@FreeBSD.ORG Subject: Re: NetWare client 1.3beta7 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 15 Apr 1999, Boris Popov wrote: > P.S. Although is beta, the development version runs for a three weeks > without any crashes. I'm about to start a project that i'm willing to use FreeBSD instead of linux. The FreeBSD server has to upload a file to a netware 4.1 server. Can i do it with your netware client? :] Any suggestion will be appreciated. :] done. Aldrin Leal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 18 21:30:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 1BCDE14D66 for ; Sun, 18 Apr 1999 21:30:11 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10Z4RI-0009XK-00; Mon, 19 Apr 1999 10:09:40 +0700 Date: Mon, 19 Apr 1999 10:09:40 +0700 (ALMST) From: Boris Popov To: Aldrin L Cc: freebsd-net@FreeBSD.ORG Subject: Re: NetWare client 1.3beta7 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 Sun, 18 Apr 1999, Aldrin L wrote: > > P.S. Although is beta, the development version runs for a three weeks > > without any crashes. > > I'm about to start a project that i'm willing to use FreeBSD > instead of linux. The FreeBSD server has to upload a file to a netware 4.1 > server. Can i do it with your netware client? :] Reliable file transfers was a primary goal. In addition you get a power of Unix in NetWare server maintance tasks :). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 19 5:58:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from pelican.sms.fi (pelican.sms.fi [192.58.51.9]) by hub.freebsd.org (Postfix) with ESMTP id F0A5514C4E for ; Mon, 19 Apr 1999 05:58:09 -0700 (PDT) (envelope-from pete@sms.fi) Received: from sms.fi (thrush.sms.fi [192.58.51.24]) by pelican.sms.fi (8.9.2/8.9.2) with ESMTP id PAA33140; Mon, 19 Apr 1999 15:55:16 +0300 (EEST) (envelope-from pete@sms.fi) Message-ID: <371B271B.DEEB1033@sms.fi> Date: Mon, 19 Apr 1999 15:52:43 +0300 From: Petri Helenius X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: User Grios Cc: freebsd-net@freebsd.org Subject: Re: diskless References: <3703F046.71756D2A@netshell.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any pointers for a suitable diskless bootkit for FreeBSD? (rom image + kernel file --> bootfile converter?) Pete User Grios wrote: > > Hi, i am trying to get my diskless system working with FBSD, but the > following error occurs: > > Loading freebsd.192.168.0.2... > rootfs 192.168.0.1:/usr/export/slave > swapfs 192.168.0.1:/usr/export/swapfs > swapsize 32000 > hostname slave > *** RPC Error: (0,0,0): > Unable to mount SWAP file system: Permission denied > > I read The Handbook, but there is nothing there about this error > message! > > Any tip? > Thank you for your time and cooperation! > > ------------------------------------------------------------------------ > > Subject: Diskless > Date: Thu, 01 Apr 1999 00:43:05 -0300 > From: User Grios > To: questions@freebsd.org > > Hi, i am trying to get my diskless system working with FBSD, but the > following error occurs: > > Loading freebsd.192.168.0.2... > rootfs 192.168.0.1:/usr/export/slave > swapfs 192.168.0.1:/usr/export/swapfs > swapsize 32000 > hostname slave > *** RPC Error: (0,0,0): > Unable to mount SWAP file system: Permission denied > > I read The Handbook, but there is nothing there about this error > message! > > Any tip? > Thank you for your time and cooperation! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 19 7:54:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110]) by hub.freebsd.org (Postfix) with ESMTP id DE269155AB for ; Mon, 19 Apr 1999 07:54:42 -0700 (PDT) (envelope-from mjenkins@carp.gbr.epa.gov) Received: (from mjenkins@localhost) by carp.gbr.epa.gov (8.8.8/8.8.8) id JAA20481; Mon, 19 Apr 1999 09:51:56 -0500 (CDT) (envelope-from mjenkins) Date: Mon, 19 Apr 1999 09:51:56 -0500 (CDT) From: Mike Jenkins Message-Id: <199904191451.JAA20481@carp.gbr.epa.gov> To: freebsd-net@freebsd.org Subject: Re: DHCP - IPFW - Controlling IPs Cc: thomas.uhrfelt@plymovent.se In-Reply-To: <01BE88F5.C4660D20.thomas.uhrfelt@plymovent.se> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Apr 1999 Thomas Uhrfelt wrote: > I have now sucessfully installed ISC:s DHCP server on my FreeBSD box to pass out IP:s etc. to the users on our local network, but I > Have a little thing grinding on my mind, as I am going to use DUMMYNET and IPFW to regulate what users can and cannot do on other > networks. Is there any way that I can check ( periodically or all the time ) that the IP the packet is coming from really is the one that > is assigned by the DHCP daemon? What I mean is, for my ipfw rules/pipes to work, I need to be sure that the user has just > that IP I have assigned to him. In other words, so he can't go in and change his Win95/NT/Mac and turn off DHCP and assign an > IP on his own.. Is this possible to control at all? Couldn't he divert incoming packets on the internal interface (packets leaving the internal LAN) to a program that does the following: IF "src IP is leased out via dhcp" THEN allow ELSE deny END IF Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 19 8:39: 9 1999 Delivered-To: freebsd-net@freebsd.org Received: from tns01.tns-inc.com (mail.tns-inc.com [38.164.22.4]) by hub.freebsd.org (Postfix) with ESMTP id 348DF14CFB for ; Mon, 19 Apr 1999 08:39:04 -0700 (PDT) (envelope-from RWebster@tns-inc.com) Received: from rwebster (152.207.78.109) by tns01.tns-inc.com (Worldmail 1.3.167) for freebsd-net@freebsd.org; 19 Apr 1999 11:28:37 -0400 Reply-To: From: "Rich Webster" To: Subject: ip routing?? Date: Mon, 19 Apr 1999 11:28:31 -0400 Message-ID: <002001be8a79$484af360$30b6fea9@rwebster> 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 Disposition-Notification-To: "Rich Webster" X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've installed a BSD box twice now on an Ethernet segment that contains a few other machines all using ten-net addresses and a mask of 255.255.255.0 The BSD box has full IP access to the network, I can ping, ftp and telnet anywhere from it. But I can not access it from another machine. I was beginning to think that it was a trust relationship thing because I can not reach the BSD box at any IP layer from another box. I tried pinging, telnet, and ftp and the box just does not respond unless I run something like netstat (or route flush) and then it does respond but only while netstat is running on the BSD box. As soon as netstat stops the pings begin to time out again. When I flush the routes I can reach it for a short time but then the machine must rediscover its incorrect routing info and I begin to time out again. Initially I thought that maybe BSD has a problem with classless routing. It seems like a routing problem but I don't know whay or why. I am running routed. Does this make any sense at all? Can someone suggest some trouble shooting steps? -----Original Message----- From: Dan Langille [mailto:junkmale@xtra.co.nz] Sent: Friday, April 16, 1999 5:47 PM To: Rich Webster Cc: questions@FreeBSD.ORG Subject: Re: newbie IP question On 16 Apr 99, at 14:54, Rich Webster wrote: > I have installed a BSD box twice now and it seems to work fine. I can > ping and use IP to do whatever I like from the machine. However I can not > ping it or access it from another machine. I am using a ten net address > with the default class c mask. I notice that if I run netstat -r that > while netstat is running the BSD box is pingable from another machine. I > can ftp to the machine. When netstat -r stops I lose my connection. What > is happening here? This is a fresh install. Do I need to tell the BSD > box who it can trust to respond to? Please e-mail you answer to me at > rwebster@tns-inc.com. Thank you very much in advance. I've been playing > with this for a while and am now pretty frustrated. There a few things you need to do here. 1 - make the FreeBSD box a gateway. 2 - enable ip alaising on the FreeBSD box 3 - make the FreeBSD box your default gateway on your other boxes. To do this you need: see http://www.freebsddiary.com/freebsd/alias.htm I am assuming you are using PPP. If not, then please complain. -- Dan Langille The FreeBSD Diary http://www.FreeBSDDiary.com/freebsd Richard Webster Internetwork Solutions Engineer Total Network Solutions, Inc. 630 Freedom Business Center Suite 314 King of Prussia, PA 19406 Phone: (610) 768-7789 Fax: (610) 768-7776 email: rwebster@tns-inc.com Website: www.tns-inc.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 19 21:30: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id 27ACD156AA for ; Mon, 19 Apr 1999 21:30:01 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA64195 for ; Tue, 20 Apr 1999 01:27:40 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 20 Apr 1999 01:27:28 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Subject: -STABLE isn't stable - SCSI *and* Ethernet ... 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 Wow...what a mistake this past couple of days have been...the other day, figuring that after ~3months, it might be time to re-sync with -STABLE, figuring that, by its very name, this should be a safe thing to do... ...what a rude awakening I've had :( First off, the xl driver has recently been broken...Bill Paul has so far produced two patches in an attempt to fix them, but...its -STABLE...why should it have broken in the first place? The breakage, which has been reported by one other who tried a similar upgrade, is that after a random period of time, the ethernet's go completely dead and require a reboot to fix :( Bill's latest fix has been reported as "hanging the machine on boot"... 5 minutes ago, I had a new joy: Apr 19 23:34:50 hub /kernel: vm_fault: pager read error, pid 73235 (sendmail) Apr 19 23:34:50 hub /kernel: swap_pager: I/O error - pagein failed; blkno 520, size 4096, error 6 And my /home directory just totally disappeared...I just rebooted back up into my old kernel, and all drives fsck'd fine, and so far, no problems... These are the kinds of things I expect on my home machine, running 4.0-CURRENT...not my production machine running 3.1-STABLE :( Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 0:11:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 681791525F for ; Tue, 20 Apr 1999 00:11:32 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id JAA23508 for ; Tue, 20 Apr 1999 09:09:05 +0200 (CEST) Received: from tu (t2o68p100.telia.com [62.20.138.220]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id JAA16720 for ; Tue, 20 Apr 1999 09:09:04 +0200 (CEST) Received: by localhost with Microsoft MAPI; Tue, 20 Apr 1999 09:05:14 +0200 Message-ID: <01BE8B0C.E7182420.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'freebsd-net@freebsd.org'" Subject: mail redirection Date: Tue, 20 Apr 1999 08:20:30 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 Some might have noticed my posts about setting up a firewall/filter using FreeBSD the last week or so, now I have successfully this baby up and flying and are looking into more innovative ways to use this installation. On our network we have about 40-50 users on their own workstations ( a mix of Macs,Win95:s and NTs ). And as it is today, they themselves fetch/send the mail from our mailprovider ( pop3 & smtp ) at their own will. What I am trying to accomplish now is for the FreeBSD box to fetch all their mail ( maybe 1-2 times an hour ) and act as a POP/SMTP server to the users, carrying their mail for them and sending in out to the mailprovider. Each person got their own password / uid on the mailserver so the FreeBSD box of course needs to know that information. My biggest concern is that I don't want to create "users" on the FreeBSD box. Example: USER ---> passwd:1212 uid:1313 ---> FreeBSD Box ---> passwd: JIh3egd uid: a012.... ----> The users normal mailaccount Is this possible to do? And if it is, what programs do you recommend to fully implement this task? And while I am at it, at bootup of the FreeBSD box I get a message ( right after the memory messages ) like this - Bad BIOS32 Service Directory! What is this? Also is there any plans for porting VPND to FreeBSD, saw it and thought it might be a good project to support or? http://www2.crosswinds.net/nuremberg/~anstein/unix/vpnd.html Regards, / Thomas Uhrfelt ... Now hooked on FreeBSD ... Datortekniker PlymoVent AB / Thomas Uhrfelt ... Now hooked on FreeBSD ... Datortekniker PlymoVent AB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 8: 8:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 83C7714E6D for ; Tue, 20 Apr 1999 08:08:45 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA27745; Tue, 20 Apr 1999 09:06:15 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <371C97E5.FED95478@softweyr.com> Date: Tue, 20 Apr 1999 09:06:13 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "thomas.uhrfelt@plymovent.se" Cc: "'freebsd-net@freebsd.org'" Subject: Re: mail redirection References: <01BE8B0C.E7182420.thomas.uhrfelt@plymovent.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Uhrfelt wrote: > > On our network we have about 40-50 users on their own workstations ( a mix of > Macs,Win95:s and NTs ). And as it is today, they themselves fetch/send the > mail from our mailprovider ( pop3 & smtp ) at their own will. What I am > trying to accomplish now is for the FreeBSD box to fetch all their mail ( > maybe 1-2 times an hour ) and act as a POP/SMTP server to the users, carrying > their mail for them and sending in out to the mailprovider. > > Each person got their own password / uid on the mailserver so the FreeBSD box > of course needs to know that information. My biggest concern is that I don't > want to create "users" on the FreeBSD box. I think the cyrus mail server uses it's own mailbox and account information system. I can't check right now because I don't have a CD-ROM handy and www.freebsd.org is off-line. You might be able to do this with a combination of fetchmail to drag the mail off the mail provider's server and cyrus to serve the mail to local accounts. Why not just create local user accounts and disable them from logging in? I recommend installing the nologin port/package, but I wrote it. Just change the user's shell to nologin and they won't be logging in, nor will they be able to ftp to the machine. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 8:43:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (Postfix) with ESMTP id 1FBD41577D for ; Tue, 20 Apr 1999 08:43:46 -0700 (PDT) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.3/8.9.3) with ESMTP id LAA68332; Tue, 20 Apr 1999 11:41:10 -0400 (EDT) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Tue, 20 Apr 1999 11:41:10 -0400 (EDT) From: Jim Cassata To: Thomas Uhrfelt Cc: "'freebsd-net@freebsd.org'" Subject: Re: mail redirection In-Reply-To: <01BE8B0C.E7182420.thomas.uhrfelt@plymovent.se> 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 Is the FreeBSD box connecting via a modem? Why not put user accounts on the FreeBSD server only? You have to manage user accounts somewhere, why not on your box and not ISP? You can have user accounts and mailboxes with no home directories or telnet or ftp access (what I do for POP3) enough of my questions... on to yours. If I understand your question, you may want to set the freebsd box up as primary mailhost for your domain through DNS, with the other mail server acting as secondary, spooling incoming mail until your box connects and is sent the mail. If your primary is offline (eg the modem isn't dialled up) mail will collect on the secondary. Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Tue, 20 Apr 1999, Thomas Uhrfelt wrote: > Some might have noticed my posts about setting up a firewall/filter using > FreeBSD the last week or so, now I have successfully this baby up and flying > and are looking into more innovative ways to use this installation. > > On our network we have about 40-50 users on their own workstations ( a mix of > Macs,Win95:s and NTs ). And as it is today, they themselves fetch/send the > mail from our mailprovider ( pop3 & smtp ) at their own will. What I am > trying to accomplish now is for the FreeBSD box to fetch all their mail ( > maybe 1-2 times an hour ) and act as a POP/SMTP server to the users, carrying > their mail for them and sending in out to the mailprovider. > > Each person got their own password / uid on the mailserver so the FreeBSD box > of course needs to know that information. My biggest concern is that I don't > want to create "users" on the FreeBSD box. > > Example: > > USER ---> passwd:1212 uid:1313 ---> FreeBSD Box ---> passwd: JIh3egd uid: > a012.... ----> The users normal mailaccount > > Is this possible to do? And if it is, what programs do you recommend to fully > implement this task? > > And while I am at it, at bootup of the FreeBSD box I get a message ( right > after the memory messages ) like this > > - Bad BIOS32 Service Directory! > > What is this? > > Also is there any plans for porting VPND to FreeBSD, saw it and thought it > might be a good project to support or? > http://www2.crosswinds.net/nuremberg/~anstein/unix/vpnd.html > > > Regards, > > / > Thomas Uhrfelt ... Now hooked on FreeBSD ... > Datortekniker > PlymoVent AB > / > Thomas Uhrfelt ... Now hooked on FreeBSD ... > Datortekniker > PlymoVent AB > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 9: 2:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from kamna.i.cz (kamna.i.cz [193.85.255.30]) by hub.freebsd.org (Postfix) with SMTP id 47D9014F09 for ; Tue, 20 Apr 1999 09:02:08 -0700 (PDT) (envelope-from mm@i.cz) Received: (qmail 7975 invoked from network); 20 Apr 1999 15:59:49 -0000 Received: from woody.i.cz (@193.85.255.60) by kamna.i.cz with SMTP; 20 Apr 1999 15:59:49 -0000 Content-Length: 869 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <371C97E5.FED95478@softweyr.com> Date: Tue, 20 Apr 1999 17:59:40 +0200 (MET DST) Reply-To: mm@i.cz From: Martin Machacek To: freebsd-net@freebsd.org Subject: Re: mail redirection Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20-Apr-99 Wes Peters wrote: > Thomas Uhrfelt wrote: >> >> On our network we have about 40-50 users on their own workstations ( a mix >> of >> Macs,Win95:s and NTs ). And as it is today, they themselves fetch/send the >> mail from our mailprovider ( pop3 & smtp ) at their own will. What I am >> trying to accomplish now is for the FreeBSD box to fetch all their mail ( >> maybe 1-2 times an hour ) and act as a POP/SMTP server to the users, >> carrying >> their mail for them and sending in out to the mailprovider. >> >> Each person got their own password / uid on the mailserver so the FreeBSD >> box >> of course needs to know that information. My biggest concern is that I don't >> want to create "users" on the FreeBSD box. Use qmail and qpop. It allows to have separate user database independant on /etc/passwd. Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 9:47:52 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailg.telia.com (mailg.telia.com [194.22.194.26]) by hub.freebsd.org (Postfix) with ESMTP id C3F0E1525D for ; Tue, 20 Apr 1999 09:47:46 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailg.telia.com (8.8.5/8.8.8) with ESMTP id SAA00833; Tue, 20 Apr 1999 18:45:12 +0200 (CEST) Received: from tu (t1o68p22.telia.com [62.20.138.22]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id SAA02189; Tue, 20 Apr 1999 18:45:11 +0200 (CEST) Received: by localhost with Microsoft MAPI; Tue, 20 Apr 1999 18:41:14 +0200 Message-ID: <01BE8B5D.5E534F10.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'mm@i.cz'" Cc: "'freebsd-net@freebsd.org'" Subject: SV: mail redirection Date: Tue, 20 Apr 1999 18:41:03 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 > >> of course needs to know that information. My biggest concern is that I > >> don't > >> want to create "users" on the FreeBSD box. > > Use qmail and qpop. It allows to have separate user database independant on > /etc/passwd. > > > Martin Is there a "guide" on how to accomplish this configuration anywhere? I have fairly new to to *nix world, but I want this baby-BSD box of mine to outperform the NT boxes we have right now. / Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 9:52:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id 51BAC14C07 for ; Tue, 20 Apr 1999 09:52:22 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by maile.telia.com (8.8.5/8.8.8) with ESMTP id SAA01141; Tue, 20 Apr 1999 18:49:49 +0200 (CEST) Received: from tu (t2o68p31.telia.com [62.20.138.151]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id SAA03618; Tue, 20 Apr 1999 18:49:48 +0200 (CEST) Received: by localhost with Microsoft MAPI; Tue, 20 Apr 1999 18:45:50 +0200 Message-ID: <01BE8B5E.0330A960.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'Jim Cassata'" Cc: "'freebsd-net@freebsd.org'" Subject: SV: mail redirection Date: Tue, 20 Apr 1999 18:45:37 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 > Is the FreeBSD box connecting via a modem? Why not put user accounts on > the FreeBSD server only? You have to manage user accounts somewhere, why > not on your box and not ISP? You can have user accounts and mailboxes > with no home directories or telnet or ftp access (what I do for POP3) Not exactly, today we have users ( validated onto a windows NT domain ) and each of them goes thru our ISDN on the net emptying their mailboxes at our ISP ( different uid:s / passwords than on logon at the NT domain ). what I want to do is for my freebsd box to connect to the ISP, then emptying all those accounts ( about 40 or so ) and then bring em home to the BSD box and have the users polling the BSD box instead. that way I can control a) the costs of ISDN b) the redirection of mail, as in having multimple recipients on the same email adress. > If I understand your question, you may want to set the freebsd box up as > primary mailhost for your domain through DNS, with the other mail server > acting as secondary, spooling incoming mail until your box connects and is > sent the mail. If your primary is offline (eg the modem isn't dialled up) > mail will collect on the secondary. I want it to be the only mailhost for my domain, the users shouldnt even know that their mailboxes are in fact on the ISPs computers.. all the mail the will see is coming from the BSD box. / Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 10:18: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from home.ieng.com (home.ieng.com [207.24.215.20]) by hub.freebsd.org (Postfix) with ESMTP id 29CA715774 for ; Tue, 20 Apr 1999 10:18:00 -0700 (PDT) (envelope-from pauls@ieng.com) Received: from localhost (pauls@localhost) by home.ieng.com (8.9.1a/8.9.1) with SMTP id NAA15123 for ; Tue, 20 Apr 1999 13:15:25 -0400 (EDT) Date: Tue, 20 Apr 1999 13:15:25 -0400 (EDT) From: Paul Southworth To: freebsd-net@freebsd.org Subject: Interfaces don't go down when network is physically down 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 FreeBSD 3.0-RELEASE, when you physically break an ethernet (eg, unplug the cable) the host still thinks the interface is up and can still ping it. Is there any way to avoid that scenario - ie, when you break an interface, have it be really broken, down, unpingable? The reason I ask is that a physically down ethernet network interface does not appear to be visible FreeBSD (or to gated) which means that OSPF really doesn't work properly. For example, two machines, three networks: +------+ +------+ ----net1----| box1 |----net2----| box2 |----net3---- +------+ +------+ If box1 is announcing net1 to box2 via OSPF, and I physically take down the net1 interface on box1, box1's gated never knows it, keeps announcing the route to box2. box2 can still reach the net1 interface on box1, even though net1 should really be unreachable via box1. Any work-around for this? [FYI, this is not really a FreeBSD-specific problem - Linux and Solaris also appear to fail this test.] --Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 11:18:30 1999 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 211EA14E78 for ; Tue, 20 Apr 1999 11:18:19 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA10552; Tue, 20 Apr 1999 11:14:50 -0700 (PDT) Message-Id: <199904201814.LAA10552@implode.root.com> To: Paul Southworth Cc: freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-reply-to: Your message of "Tue, 20 Apr 1999 13:15:25 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 20 Apr 1999 11:14:50 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On FreeBSD 3.0-RELEASE, when you physically break an ethernet (eg, unplug >the cable) the host still thinks the interface is up and can still >ping it. Is there any way to avoid that scenario - ie, when you break >an interface, have it be really broken, down, unpingable? For many of the ethernet interfaces, there isn't any indication that the link is down. On the other hand, for the 100Mbps interfaces, it is possible in some cases to get an interrupt from the PHY of the link status change. We don't currently do anything with that, however. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 11:44:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id A10DE15061 for ; Tue, 20 Apr 1999 11:44:53 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA00647; Tue, 20 Apr 1999 14:42:08 -0400 (EDT) Date: Tue, 20 Apr 1999 14:42:08 -0400 (EDT) From: "Matthew N. Dodd" To: David Greenman Cc: Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-Reply-To: <199904201814.LAA10552@implode.root.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 Tue, 20 Apr 1999, David Greenman wrote: > For many of the ethernet interfaces, there isn't any indication that the > link is down. On the other hand, for the 100Mbps interfaces, it is possible > in some cases to get an interrupt from the PHY of the link status change. > We don't currently do anything with that, however. Should we? Is it acceptable for the driver to frob the IFF_UP flag when it gets an event that should be reflected by a state change of IFF_UP? -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 12: 6: 2 1999 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 829E81583F for ; Tue, 20 Apr 1999 12:06:00 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA10789; Tue, 20 Apr 1999 12:01:59 -0700 (PDT) Message-Id: <199904201901.MAA10789@implode.root.com> To: "Matthew N. Dodd" Cc: Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-reply-to: Your message of "Tue, 20 Apr 1999 14:42:08 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 20 Apr 1999 12:01:59 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Tue, 20 Apr 1999, David Greenman wrote: >> For many of the ethernet interfaces, there isn't any indication that the >> link is down. On the other hand, for the 100Mbps interfaces, it is possible >> in some cases to get an interrupt from the PHY of the link status change. >> We don't currently do anything with that, however. > >Should we? > >Is it acceptable for the driver to frob the IFF_UP flag when it gets an >event that should be reflected by a state change of IFF_UP? I can't think of any problems off hand. I think you'd want to use if_up() and if_down(), however, since these will do routing socket notifications about the state change, although I don't know if these are safe in all interrupt contexts. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 12:11:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 3153914D8F for ; Tue, 20 Apr 1999 12:11:38 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id PAA01241; Tue, 20 Apr 1999 15:09:03 -0400 (EDT) Date: Tue, 20 Apr 1999 15:09:03 -0400 (EDT) From: "Matthew N. Dodd" To: David Greenman Cc: Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-Reply-To: <199904201901.MAA10789@implode.root.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 Tue, 20 Apr 1999, David Greenman wrote: > I can't think of any problems off hand. I think you'd want to use > if_up() and if_down(), however, since these will do routing socket > notifications about the state change, although I don't know if these > are safe in all interrupt contexts. (from comments leading if_up() in sys/net/if.c) * NOTE: must be called at splnet or eqivalent. Comments for if_down() indicate the same spl. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 12:15:18 1999 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 23A191582E for ; Tue, 20 Apr 1999 12:15:09 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA10860; Tue, 20 Apr 1999 12:11:14 -0700 (PDT) Message-Id: <199904201911.MAA10860@implode.root.com> To: "Matthew N. Dodd" Cc: Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-reply-to: Your message of "Tue, 20 Apr 1999 15:09:03 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 20 Apr 1999 12:11:14 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Tue, 20 Apr 1999, David Greenman wrote: >> I can't think of any problems off hand. I think you'd want to use >> if_up() and if_down(), however, since these will do routing socket >> notifications about the state change, although I don't know if these >> are safe in all interrupt contexts. > >(from comments leading if_up() in sys/net/if.c) > * NOTE: must be called at splnet or eqivalent. > >Comments for if_down() indicate the same spl. ...yes, but that doesn't really mean anything, other than that it messes with things that need soft interrupt protection. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 12:20:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id C5CFE153CA for ; Tue, 20 Apr 1999 12:20:52 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 199141F68; Wed, 21 Apr 1999 03:18:25 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" Cc: David Greenman , Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-reply-to: Your message of "Tue, 20 Apr 1999 14:42:08 -0400." Date: Wed, 21 Apr 1999 03:18:24 +0800 From: Peter Wemm Message-Id: <19990420191825.199141F68@spinner.netplex.com.au> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Matthew N. Dodd" wrote: > On Tue, 20 Apr 1999, David Greenman wrote: > > For many of the ethernet interfaces, there isn't any indication that the > > link is down. On the other hand, for the 100Mbps interfaces, it is possible > > in some cases to get an interrupt from the PHY of the link status change. > > We don't currently do anything with that, however. > > Should we? > > Is it acceptable for the driver to frob the IFF_UP flag when it gets an > event that should be reflected by a state change of IFF_UP? I've always thought IFF_RUNNING was for this... IFF_UP was meant to be reserved for the administrator, while IFF_RUNNING indicates the driver and hardware state. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 12:27:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 45C9314BCD for ; Tue, 20 Apr 1999 12:27:05 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id PAA01563; Tue, 20 Apr 1999 15:24:18 -0400 (EDT) Date: Tue, 20 Apr 1999 15:24:18 -0400 (EDT) From: "Matthew N. Dodd" To: Peter Wemm Cc: David Greenman , Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-Reply-To: <19990420191825.199141F68@spinner.netplex.com.au> 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, 21 Apr 1999, Peter Wemm wrote: > I've always thought IFF_RUNNING was for this... IFF_UP was meant to be > reserved for the administrator, while IFF_RUNNING indicates the driver and > hardware state. Bill seems to be thinking the same thing. (At least I think he is; he's off on a rant now.) The original poster wanted to know why wasn't able to detect link status events (cable unpluged etc). While OSPF will eventually detect that the link is dead, stuff like RIP may not. If IFF_RUNNING is for the driver to use how can we give routing daemons hints about link status changes? I am under the impression that they are looking for IFF_UP, not IFF_RUNNING. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 13:23:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id D712B15818 for ; Tue, 20 Apr 1999 13:23:23 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id QAA29630; Tue, 20 Apr 1999 16:20:49 -0400 (EDT) (envelope-from wollman) Date: Tue, 20 Apr 1999 16:20:49 -0400 (EDT) From: Garrett Wollman Message-Id: <199904202020.QAA29630@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: David Greenman , Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-Reply-To: References: <199904201814.LAA10552@implode.root.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Should we? > Is it acceptable for the driver to frob the IFF_UP flag when it gets an > event that should be reflected by a state change of IFF_UP? The trouble is that, once an interface goes down, there might not be any traffic traversing it which will cause it to come back up again. (Some NICs don't notice the state of the wire unless they are transmitting.) That's why Cisco implemented `keepalive'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 17:19: 1 1999 Delivered-To: freebsd-net@freebsd.org Received: from odin.siol.net (odin.siol.net [193.189.160.10]) by hub.freebsd.org (Postfix) with ESMTP id 5064215802 for ; Tue, 20 Apr 1999 17:18:57 -0700 (PDT) (envelope-from tomaz.borstnar@over.net) Received: from hang ([193.189.190.108]) by odin.siol.net (Post.Office MTA v3.5.3 release 223 ID# 620-58654U60000L60000S0V35) with SMTP id net; Wed, 21 Apr 1999 02:16:28 +0200 Message-Id: <4.1.19990421015443.03e07b90@193.189.189.100> X-Misc: N/A X-Legalese: #include Date: Wed, 21 Apr 1999 01:56:23 +0200 To: mm@i.cz From: Tomaz Borstnar Subject: Re: mail redirection Cc: freebsd-net@freebsd.org In-Reply-To: References: <371C97E5.FED95478@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 05:59 PM 4/20/99 , Martin Machacek wrote the following message: >>> Each person got their own password / uid on the mailserver so the FreeBSD >>> box >>> of course needs to know that information. My biggest concern is that I don't >>> want to create "users" on the FreeBSD box. >Use qmail and qpop. It allows to have separate user database independant on >/etc/passwd. This can be done with any mail software if one replaces routines (getpw*) for getting user info from username, etc. Getpw which does this is part of xtacacs distribution. Tomaz ---- Tomaz Borstnar "Love is the answer to the final question you ask" - Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 20:15:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id A8EA6151DE; Tue, 20 Apr 1999 20:15:04 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id AAA78958; Wed, 21 Apr 1999 00:12:39 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 21 Apr 1999 00:12:39 -0300 (ADT) From: The Hermit Hacker To: freebsd-net@freebsd.org Cc: freebsd-stable@freebsd.org Subject: xl1: transmission error w/ -stable ... 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 Got this tonight, that required a cold boot :( xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 xl1: transmission error: 90 This is source from April 17th... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 20 21:41:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id CB2D715083 for ; Tue, 20 Apr 1999 21:41:08 -0700 (PDT) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA10745 for ; Wed, 21 Apr 1999 00:38:41 -0400 (EDT) Date: Wed, 21 Apr 1999 00:38:41 -0400 (EDT) From: To: freebsd-net@freebsd.org Subject: Q: NATD -redirect_address problem 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 the following problem: a dual home box. nic card A (fxp0) connects to the internet with a public ip of 63.64.500.1 nic card b (de0) connects to the private 192.168.x.x network with an ip of 192.168.1.125 I have nat working fine. What im *trying* to do is use the -redirect_address flag to get nat to use a *2nd* public ip of 63.64.500.2 to direct traffic to our internal exchange server of 192.168.1.2 So that all traffic from the inside private net is aliased to the 63.64.500.1 IP *except* the exchange box. The exchange box is on 192.168.1.2 and I want the traffic in and out of the nat box thats directed to the exchange box to use the public IP 63.64.500.2. But nat will only seem to use the first public IP of 63.64.500.1 no matter how hard I try to get -redirect_address 192.168.1.2 63.64.500.2. It just doesnt fly. How do I get nat to alias using two different public IP's or is that possible? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 5: 2:18 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id CBECA14DC8 for ; Wed, 21 Apr 1999 05:02:09 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id NAA03146; Wed, 21 Apr 1999 13:59:32 +0200 (CEST) Date: Wed, 21 Apr 1999 13:59:24 +0200 From: Stefan Bethke To: scanner@jurai.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: Q: NATD -redirect_address problem Message-ID: <612413.3133691964@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org scanner@jurai.net wrote: > a dual home box. > nic card A (fxp0) connects to the internet with a public ip of = 63.64.500.1 > nic card b (de0) connects to the private 192.168.x.x network with an ip = of > 192.168.1.125 > > I have nat working fine. What im *trying* to do is use the > -redirect_address flag to get nat to use a *2nd* public ip of = 63.64.500.2 > to direct traffic to our internal exchange server of 192.168.1.2 > So that all traffic from the inside private net is aliased to the > 63.64.500.1 IP *except* the exchange box. The exchange box is on > 192.168.1.2 and I want the traffic in and out of the nat box thats > directed to the exchange box to use the public IP 63.64.500.2. But nat > will only seem to use the first public IP of 63.64.500.1 no matter how > hard I try to get -redirect_address 192.168.1.2 63.64.500.2. > It just doesnt fly. How do I get nat to alias using two different public > IP's or is that possible? Run two natd's with appropriate ipfw rules. Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@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 Apr 21 12:18: 9 1999 Delivered-To: freebsd-net@freebsd.org Received: from listserv.mda.state.mi.us (listserv.mda.state.mi.us [167.240.254.54]) by hub.freebsd.org (Postfix) with ESMTP id 9790A15914 for ; Wed, 21 Apr 1999 12:16:51 -0700 (PDT) (envelope-from evansj@listserv.mda.state.mi.us) Received: (from evansj@localhost) by listserv.mda.state.mi.us (8.9.1/8.9.1) id PAA00405; Wed, 21 Apr 1999 15:09:58 -0400 (EDT) (envelope-from evansj) Message-ID: <19990421150958.62240@listserv.mda.state.mi.us> Date: Wed, 21 Apr 1999 15:09:58 -0400 From: Jeff Evans To: freebsd-net@freebsd.org Subject: help with alias routing (source address) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been able to setup an alias IP-address for my FreeBSD box, but I've been unable to force it to use the alias when communicating with a specific ip-address. I'm trying to setup a freebsd to run squid in httpd-accelerator mode. Long story short, I'd like to force communication to a specific address to originate from the alias ip-address. Here's my current setup: browser x.x.x.x <---> x.x.x.54 FreeBSD/Squid x.x.x.54 <-> x.x.x.35 Real web browser x.x.x.x <---> x.x.x.54 FreeBSD/Squid x.x.x.55 <-> x.x.x.35 Real web Currently both the FreeBSD and Web server are on the same subnet, but this might change. I've played around with some route commands, but haven't found the magic one yet. I'm also guessing putting in a seperate NIC for the other ip-address might be the magic ticket also (along with static routes). I really appreciate any help offered. This is going to a good cause, getting rid of yet another Micro$oft server. -Jeff - Jeff Evans evansj@state.mi.us * Michigan Dept. of Agriculture - http://www.mda.state.mi.us/ ******************************************************************* Lots and Lots of info on current setup (sorry if this is too much). ******************************************************************* #[ROOT] ifconfig ie0 alias 167.240.254.55 netmask 0xffffffff #[ROOT] netstat -ran Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 167.240.254.2 UGSc 11 0 ie0 127.0.0.1 127.0.0.1 UH 0 315 lo0 167.240.254/24 link#2 UC 0 0 ie0 167.240.254.2 0:0:c:7:ac:1 UHLW 12 0 ie0 1171 167.240.254.35 0:80:5f:ea:91:9b UHLW 0 2 ie0 897 167.240.254.55/32 link#2 UC 0 0 ie0 #[ROOT] ifconfig -a lp0: flags=8810 mtu 1500 ie0: flags=8843 mtu 1500 inet 167.240.254.54 netmask 0xffffff00 broadcast 167.240.254.255 inet 167.240.254.55 netmask 0xffffffff broadcast 167.240.254.55 ether 00:aa:00:18:14:7a tun0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 #[ROOT] uname -a FreeBSD listserv.mda.state.mi.us 3.0-RELEASE FreeBSD 3.0-RELEASE #2: Mon Jan 4 11:21:08 EST 1999 root@fubar.cl.msu.edu:/usr/src/sys/compile/fubar i386 #[ROOT] sysctl -a | grep net net.local.stream.sendspace: 8192 net.local.stream.recvspace: 8192 net.local.dgram.maxdgram: 2048 net.local.dgram.recvspace: 4096 net.local.inflight: 0 net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 net.inet.ip.forwarding: 0 net.inet.ip.redirect: 1 net.inet.ip.ttl: 64 net.inet.ip.rtexpire: 3600 net.inet.ip.rtminexpire: 10 net.inet.ip.rtmaxcache: 128 net.inet.ip.sourceroute: 0 net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 0 net.inet.ip.accept_sourceroute: 0 net.inet.ip.fastforwarding: 0 net.inet.ip.subnets_are_local: 0 net.inet.icmp.maskrepl: 0 net.inet.icmp.bmcastecho: 0 net.inet.tcp.rfc1323: 0 net.inet.tcp.rfc1644: 0 net.inet.tcp.mssdflt: 512 net.inet.tcp.rttdflt: 3 net.inet.tcp.keepidle: 14400 net.inet.tcp.keepintvl: 150 net.inet.tcp.sendspace: 16384 net.inet.tcp.recvspace: 16384 net.inet.tcp.keepinit: 150 net.inet.tcp.log_in_vain: 0 net.inet.tcp.delayed_ack: 1 net.inet.tcp.pcbcount: 12 net.inet.tcp.always_keepalive: 0 net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 9216 net.inet.udp.recvspace: 41600 net.inet.udp.log_in_vain: 0 net.inet.raw.maxdgram: 8192 net.inet.raw.recvspace: 8192 net.link.generic.system.ifcount: 6 net.link.ether.inet.prune_intvl: 300 net.link.ether.inet.max_age: 1200 net.link.ether.inet.host_down_time: 20 net.link.ether.inet.maxtries: 5 net.link.ether.inet.useloopback: 1 net.link.ether.inet.proxyall: 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 13: 7:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from ns1.elpn.com (ns1.elpn.com [209.194.74.2]) by hub.freebsd.org (Postfix) with ESMTP id 4809E15308 for ; Wed, 21 Apr 1999 13:07:01 -0700 (PDT) (envelope-from rosteen@elpn.com) Received: from elpn.com (cox.com [206.98.143.200]) by ns1.elpn.com (8.8.8/8.8.8) with ESMTP id OAA15415 for ; Wed, 21 Apr 1999 14:00:35 -0600 (MDT) (envelope-from rosteen@elpn.com) Message-ID: <371E2F21.A18B3DA9@elpn.com> Date: Wed, 21 Apr 1999 16:03:46 -0400 From: rosteen Reply-To: rosteen@elpn.com X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: more space please Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, How would one with Freebsd OS change over to a bigger drive on a particular server? It's more like what is the preferred/easiest method so that all configs can be transferred with little to no effort. Thanks, Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 17:20:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id C7F0B158F5 for ; Wed, 21 Apr 1999 17:20:05 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id SAA01439; Wed, 21 Apr 1999 18:17:35 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <371E6A9D.50CF2A89@softweyr.com> Date: Wed, 21 Apr 1999 18:17:33 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: rosteen@elpn.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: more space please References: <371E2F21.A18B3DA9@elpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org rosteen wrote: > > Hello, > How would one with Freebsd OS change over to a bigger drive on a > particular server? > It's more like what is the preferred/easiest method so that all configs > can be transferred with little to no effort. If you're running 3.1 or above, you could stick the new drive in your system, slice it up as needed, and add the new space to the existing filesystems with Vinum volume manager. Otherwise, my suggestion would be to put the new drive in the system, run sysinstall on it, they copy the files from the existing disk to the new one before removing the original disk. I usually just wait until the next upgrade to switch drives and do a fresh install on the new drive, but I'm a masochist. I wonder what it would take to get PowerQuest to add BSD ufs to Partition Magic? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Apr 21 20: 8: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from Meta-Bug.ppp.ucar.edu (ras36.ucar.edu [128.117.68.36]) by hub.freebsd.org (Postfix) with SMTP id 78260153F0 for ; Wed, 21 Apr 1999 20:07:50 -0700 (PDT) (envelope-from rousskov@ircache.net) Received: from localhost (rousskov@localhost) by Meta-Bug.ppp.ucar.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id VAA06249 for ; Wed, 21 Apr 1999 21:05:15 -0600 Date: Wed, 21 Apr 1999 21:05:15 -0600 From: Alex Rousskov X-Sender: rousskov@Meta-Bug To: freebsd-net@FreeBSD.ORG Subject: _Some_ acks delayed for 200 msec? 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 there, I am stuck with what looks like a TCP or kernel timing thing. Setup: A single open (persistent) TCP connection between two PCs running FreeBSD 2.2.8-RELEASE. Switched 100Mbit FDX network. HTTP-like test: a small client request, a larger response from a server, client request, server response, etc. All on the same connection. All message sizes are almost constant for this test. Non-blocking sockets write/read data as soon as possible. No external activity. No packet loss. With various kernel and test configurations, I get exactly about 5 requests per second (about ~6.2Mbps) on a persistent connection. With non-persistent connections, I get at least 65Mbps throughput. Finally, here is a portion of a tcpdump@client that illustrates the problem. Only the client side is shown. Watch for time "jumps" in the first column. 20:34:32.433366 . ack 464131 20:34:32.433614 . ack 467011 20:34:32.630026 . ack 468451 <--- jump 20:34:32.630379 . ack 469613 20:34:32.630527 P 8100:8280(180) ack <--- client request N 20:34:32.631236 . ack 471661 20:34:32.631508 . ack 474541 20:34:32.631923 . ack 478861 20:34:32.632278 . ack 480023 20:34:32.632442 P 8280:8460(180) ack <--- client request N+1 20:34:32.633333 . ack 482071 20:34:32.633922 . ack 487831 20:34:32.830024 . ack 489271 <--- jump 20:34:32.830375 . ack 490433 20:34:32.830531 P 8460:8640(180) ack <--- client request N+2 20:34:32.831235 . ack 492481 20:34:32.831398 . ack 493921 20:34:32.831636 . ack 496801 20:34:32.831881 . ack 499681 20:34:32.832233 . ack 500843 20:34:32.832381 P 8640:8820(180) ack <--- client request N+3 20:34:32.833083 . ack 502891 20:34:32.833247 . ack 504331 20:34:32.833484 . ack 507211 20:34:32.833730 . ack 510091 20:34:32.834082 . ack 511253 20:34:32.834232 P 8820:9000(180) ack <--- ... 20:34:32.834938 . ack 513301 20:34:32.835330 . ack 517621 20:34:32.835580 . ack 520501 20:34:32.835934 . ack 521663 20:34:32.836085 P 9000:9180(180) ack 20:34:32.836787 . ack 523711 20:34:32.836950 . ack 525151 20:34:32.837189 . ack 528031 20:34:32.837433 . ack 530911 20:34:32.837787 . ack 532073 20:34:32.837936 P 9180:9360(180) ack 20:34:32.838659 . ack 534121 20:34:32.838930 . ack 537001 20:34:32.839176 . ack 539881 20:34:33.030027 . ack 541321 <---- jump 20:34:33.030382 . ack 542483 .... Note that jumps occur every 200 msec. The number of packets (and replies/requests in between) is irrelevant. Every 200 msec an "unlucky" ack will be delayed until the end of that 200 msec "slice". The dataflow from a server is stable as illustrated by the dump below. In other words, there is always something to ack (8080=server)... 20:34:32.633665 .8080 > .1084: . 484951:486391(1440) ack 8460 win 17280 20:34:32.633787 .8080 > .1084: . 486391:487831(1440) ack 8460 win 17280 20:34:32.633909 .8080 > .1084: . 487831:489271(1440) ack 8460 win 17280 20:34:32.633922 .1084 > .8080: . ack 487831 win 17280 20:34:32.830024 .1084 > .8080: . ack 489271 win 17280 20:34:32.830338 .8080 > .1084: P 489271:490433(1162) ack 8460 win 17280 Now, if that is the infamous delayed ack problem, then - why only *some* acks are delayed? - why Nagle-like optimization is used on a switched (no routing) network? - why disabling Nagle (TCP_NODELAY) does not help? - why disabling delayed acks in the kernel (options TCP_ACK_HACK) does not help? If it is not a delayed ack or Nagle, then what is it _and_ how can I avoid it? Thanks, Alex. P.S. Web Polygraph (http://polygraph.ircache.net/) is the application doing the tests, but ( hopefully :) that is irrelevant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 22: 7:20 1999 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 2136C14F95 for ; Wed, 21 Apr 1999 22:07:17 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA16761; Wed, 21 Apr 1999 22:03:40 -0700 (PDT) Message-Id: <199904220503.WAA16761@implode.root.com> To: Alex Rousskov Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-reply-to: Your message of "Wed, 21 Apr 1999 21:05:15 MDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 21 Apr 1999 22:03:40 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Now, if that is the infamous delayed ack problem, then > - why only *some* acks are delayed? Probably because of timing of the response packets. It's impossible to say with your limited, one-sided tcpdump. > - why Nagle-like optimization is used on a switched (no routing) > network? The Nagle algorithm doesn't know or care about "local" networks. > - why disabling Nagle (TCP_NODELAY) does not help? It will likely have to be disabled on both sides for your application since there appears to be a syncronous request/response involved. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 22:19:53 1999 Delivered-To: freebsd-net@freebsd.org Received: from Meta-Bug.ppp.ucar.edu (ras36.ucar.edu [128.117.68.36]) by hub.freebsd.org (Postfix) with SMTP id 5C88315273 for ; Wed, 21 Apr 1999 22:19:16 -0700 (PDT) (envelope-from rousskov@ircache.net) Received: from localhost (rousskov@localhost) by Meta-Bug.ppp.ucar.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id XAA06441; Wed, 21 Apr 1999 23:16:07 -0600 Date: Wed, 21 Apr 1999 23:16:07 -0600 From: Alex Rousskov X-Sender: rousskov@Meta-Bug To: David Greenman Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-Reply-To: <199904220503.WAA16761@implode.root.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 Wed, 21 Apr 1999, David Greenman wrote: > >Now, if that is the infamous delayed ack problem, then > > - why only *some* acks are delayed? > > Probably because of timing of the response packets. It's impossible to > say with your limited, one-sided tcpdump. Response packets are coming as soon as an ack is sent or prior to that, as far as I can tell. There was a small bi-directional tcpdump in the original post. By "one-sided", do you mean a dump collected on a single [client] host, or that server responses were filtered out in the long dump that I sent? I can certainly provide more info. Just tell me what would be useful. I was afraid of posting long tcpdumps... > The Nagle algorithm doesn't know or care about "local" networks. Right. I confused Nagle with TCP_ACK_HACK (which is sort of a Nagle-like algorithm). TCP_ACK_HACK (a sysctl option in 3.1) does depend on network "locality" from our experience. > > - why disabling Nagle (TCP_NODELAY) does not help? > > It will likely have to be disabled on both sides for your application since > there appears to be a syncronous request/response involved. It was disabled on both sides. Thanks a lot, Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 22:27:40 1999 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 B32D214F65 for ; Wed, 21 Apr 1999 22:27:38 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA16883; Wed, 21 Apr 1999 22:24:00 -0700 (PDT) Message-Id: <199904220524.WAA16883@implode.root.com> To: Alex Rousskov Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-reply-to: Your message of "Wed, 21 Apr 1999 23:16:07 MDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 21 Apr 1999 22:24:00 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Wed, 21 Apr 1999, David Greenman wrote: > >> >Now, if that is the infamous delayed ack problem, then >> > - why only *some* acks are delayed? >> >> Probably because of timing of the response packets. It's impossible to >> say with your limited, one-sided tcpdump. > >Response packets are coming as soon as an ack is sent or prior to that, as >far as I can tell. There was a small bi-directional tcpdump in the original >post. By "one-sided", do you mean a dump collected on a single [client] >host, or that server responses were filtered out in the long dump that I >sent? I can certainly provide more info. Just tell me what would be useful. >I was afraid of posting long tcpdumps... I mean both. >> The Nagle algorithm doesn't know or care about "local" networks. > >Right. I confused Nagle with TCP_ACK_HACK (which is sort of a Nagle-like >algorithm). TCP_ACK_HACK (a sysctl option in 3.1) does depend on network >"locality" from our experience. > >> > - why disabling Nagle (TCP_NODELAY) does not help? >> >> It will likely have to be disabled on both sides for your application since >> there appears to be a syncronous request/response involved. > >It was disabled on both sides. I'm not familiar with what your application is doing over the wire, so I can only speculate. It sounds to me as though TCP_NODELAY wasn't actually set properly on the socket. Keep in mind that this option is not inherited in the accept()'ed file descriptor and thus the option must be set on that descriptor and not on the listen() socket. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 22:49:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from Meta-Bug.ppp.ucar.edu (ras36.ucar.edu [128.117.68.36]) by hub.freebsd.org (Postfix) with SMTP id B9F4615109 for ; Wed, 21 Apr 1999 22:49:09 -0700 (PDT) (envelope-from rousskov@ircache.net) Received: from localhost (rousskov@localhost) by Meta-Bug.ppp.ucar.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id XAA06477; Wed, 21 Apr 1999 23:46:01 -0600 Date: Wed, 21 Apr 1999 23:46:00 -0600 From: Alex Rousskov X-Sender: rousskov@Meta-Bug To: David Greenman Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-Reply-To: <199904220524.WAA16883@implode.root.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 Wed, 21 Apr 1999, David Greenman wrote: > I'm not familiar with what your application is doing over the wire, so I > can only speculate. It sounds to me as though TCP_NODELAY wasn't actually > set properly on the socket. Keep in mind that this option is not inherited > in the accept()'ed file descriptor and thus the option must be set on that > descriptor and not on the listen() socket. Oof! I've trusted the accept(2) man page that says: The accept() argument extracts the first connection request on the queue of pending connections, creates a new socket with the same properties of s and allocates a new file descriptor for the socket. Apparently, "same properties" does not include TCP_NODELAY! I will test with [correctly] disabled Nagle on the server side and let you know the result. Thanks, Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 23: 1:47 1999 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 3CB4815179 for ; Wed, 21 Apr 1999 23:01:25 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA17004; Wed, 21 Apr 1999 22:57:48 -0700 (PDT) Message-Id: <199904220557.WAA17004@implode.root.com> To: Alex Rousskov Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-reply-to: Your message of "Wed, 21 Apr 1999 23:46:00 MDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 21 Apr 1999 22:57:48 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Wed, 21 Apr 1999, David Greenman wrote: > >> I'm not familiar with what your application is doing over the wire, so I >> can only speculate. It sounds to me as though TCP_NODELAY wasn't actually >> set properly on the socket. Keep in mind that this option is not inherited >> in the accept()'ed file descriptor and thus the option must be set on that >> descriptor and not on the listen() socket. > >Oof! I've trusted the accept(2) man page that says: > > The accept() argument extracts the first connection request > on the queue of pending connections, creates a new socket with the > same properties of s and allocates a new file descriptor for the > socket. > >Apparently, "same properties" does not include TCP_NODELAY! This is the classic behavior of BSD, but I nonetheless think it's a bug not to duplicate certain options (especially TCP_NODELAY). It should probably be fixed. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 23:37:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from relay.eunet.es (goya.eunet.es [193.127.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 891B81514E for ; Wed, 21 Apr 1999 23:37:31 -0700 (PDT) (envelope-from JMegias@correoex.caja-granada.es) Received: (from uucp@localhost) by relay.eunet.es (8.8.8/8.8.8) id IAA01256 for freebsd-net@FreeBSD.ORG; Thu, 22 Apr 1999 08:31:46 +0200 (MET DST) Received: from CORREOEX (sccpd00 [130.130.7.3]) by mulhacen.caja-granada.es (8.6.12/4.4) with ESMTP id IAA10835 for ; Thu, 22 Apr 1999 08:24:15 +0200 Received: by correoex.caja-granada.es with Internet Mail Service (5.5.1960.3) id ; Thu, 22 Apr 1999 08:24:21 +0200 Message-ID: <078C61D95216D2119EF500104B943B3143E030@correoex.caja-granada.es> From: "Megias Sanchez, Jose Manuel" To: "'freebsd-net@FreeBSD.ORG'" Subject: RE: more space please Date: Thu, 22 Apr 1999 08:24:20 +0200 X-Mailer: Internet Mail Service (5.5.1960.3) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have one computer running FreeBSD 2.2.7 and I'll update to FreeBSD 3.3.1 soon. It's very interesting the utility Vinum volume manager, but what is it? is it a port? where can I get more information about it? Any information would be very interesting, thanks in advance. -----Mensaje original----- De: Wes Peters [mailto:wes@softweyr.com] Enviado el: jueves 22 de abril de 1999 2:18 Para: rosteen@elpn.com Cc: freebsd-net@FreeBSD.ORG Asunto: Re: more space please rosteen wrote: > > Hello, > How would one with Freebsd OS change over to a bigger drive on a > particular server? > It's more like what is the preferred/easiest method so that all configs > can be transferred with little to no effort. If you're running 3.1 or above, you could stick the new drive in your system, slice it up as needed, and add the new space to the existing filesystems with Vinum volume manager. Otherwise, my suggestion would be to put the new drive in the system, run sysinstall on it, they copy the files from the existing disk to the new one before removing the original disk. I usually just wait until the next upgrade to switch drives and do a fresh install on the new drive, but I'm a masochist. I wonder what it would take to get PowerQuest to add BSD ufs to Partition Magic? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 21 23:40:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from Meta-Bug.ppp.ucar.edu (ras36.ucar.edu [128.117.68.36]) by hub.freebsd.org (Postfix) with SMTP id A36EA14FCE for ; Wed, 21 Apr 1999 23:40:46 -0700 (PDT) (envelope-from rousskov@ircache.net) Received: from localhost (rousskov@localhost) by Meta-Bug.ppp.ucar.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id AAA06554; Thu, 22 Apr 1999 00:37:38 -0600 Date: Thu, 22 Apr 1999 00:37:37 -0600 From: Alex Rousskov X-Sender: rousskov@Meta-Bug To: David Greenman Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-Reply-To: <199904220557.WAA17004@implode.root.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 Wed, 21 Apr 1999, David Greenman wrote: > This is the classic behavior of BSD, but I nonetheless think it's a bug not > to duplicate certain options (especially TCP_NODELAY). It should probably be > fixed. I would say at least the man page should be fixed :) Correctly setting TCP_NODELAY on the server side fixed the problem. Thanks a lot! Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 22 8: 1:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 4A0BA15107 for ; Thu, 22 Apr 1999 08:01:33 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id IAA02901; Thu, 22 Apr 1999 08:58:45 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <371F3922.FC5099F7@softweyr.com> Date: Thu, 22 Apr 1999 08:58:42 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Megias Sanchez, Jose Manuel" Cc: "'freebsd-net@FreeBSD.ORG'" Subject: Re: more space please References: <078C61D95216D2119EF500104B943B3143E030@correoex.caja-granada.es> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Megias Sanchez, Jose Manuel" wrote: > > Hi, I have one computer running FreeBSD 2.2.7 and I'll update to > FreeBSD 3.3.1 soon. It's very interesting the utility Vinum volume manager, > but what is it? is it a port? where can I get more information about it? > > Any information would be very interesting, thanks in advance. I'm hoping you meant 3.1, or maybe even 3.2 there. ;^) Since you don't have a 3.x system, you can't just read the manpages. Try http://www.lemis.com/vinum.html, that will give you an overview of what Vinum is and a look at the man pages. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 23 15:26:18 1999 Delivered-To: freebsd-net@freebsd.org Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 0E16F14CC6 for ; Fri, 23 Apr 1999 15:25:57 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id RAA06146 for ; Fri, 23 Apr 1999 17:21:14 -0400 (EDT) Date: Fri, 23 Apr 1999 17:21:04 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: freebsd-net@freebsd.org Subject: ARP weirdness(?) 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, I have a firewall box running 2.2.7 and ipfilter. On one ethernet interface I have real addresses and on the other I use 192.168.0.x. Everything was going great until yesterday. Someone plugged a machine into the dirty side of the network with the same 192.168.0 network address that my machine on the clean side of the firewall uses. For some reason the "intruder" box kept being recognized as "the" 192.168.0.2. Why is that? I would think that if you have two machines claiming the same address the one that is attached to the right network would win. Is there any way to lock this down? 'arp -s' doesn't seem to make it stick... Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 23 19: 4:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from thelab.hub.org (nat193.65.mpoweredpc.net [142.177.193.65]) by hub.freebsd.org (Postfix) with ESMTP id 712F514D4B; Fri, 23 Apr 1999 19:04:19 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA21880; Fri, 23 Apr 1999 23:01:46 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 23 Apr 1999 23:01:46 -0300 (ADT) From: The Hermit Hacker To: freebsd-stable@freebsd.org Cc: freebsd-net@freebsd.org Subject: xl* instability still in -STABLE ... what can be done? 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... I'm still having the problem with my -STABLE machine where after X hrs of run time, the ethernet just disappears. I can get in through serial console, but 'ifconfig xl1 down; ifconfig xl1 up' doesn't do anything, a full reboot appears to be required. Anything that I can do at this end ot help debug this problem? Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Apr 24 7:10:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 1E6EB14C16 for ; Sat, 24 Apr 1999 07:10:54 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA02465; Sat, 24 Apr 1999 13:57:35 +0200 From: Luigi Rizzo Message-Id: <199904241157.NAA02465@labinfo.iet.unipi.it> Subject: testers needed for bridging code in -current To: net@freebsd.org Date: Sat, 24 Apr 1999 13:57:35 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 829 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i have a bunch of patches for bridging/dummynet/ipfw (bug fixes, code cleanup, and minor performance enhancements). I need a volunteer for testing these on -current -- preferably someone who is already using PicoBSD floppies so testing will only take him a few minutes. Please email me if you can help. (I don't think anyone is using bridging alone on -current, as i think the code does not even compile without IPFW...) thanks luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 25 4:56:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 6F75A15153 for ; Sun, 25 Apr 1999 04:56:24 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA04109 for net@freebsd.org; Sun, 25 Apr 1999 11:43:26 +0200 From: Luigi Rizzo Message-Id: <199904250943.LAA04109@labinfo.iet.unipi.it> Subject: any alternative to gated for OSPF ? To: net@freebsd.org Date: Sun, 25 Apr 1999 11:43:26 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 516 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, is there anything alternative to gated for supporting OSPF ? I need it for a picobsd floppy but gated is kind of big... luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 25 7:46:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 30B531527B for ; Sun, 25 Apr 1999 07:46:39 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id QAA12063 for net@freebsd.org; Sun, 25 Apr 1999 16:46:39 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 63AB68840; Sun, 25 Apr 1999 16:10:51 +0200 (CEST) Date: Sun, 25 Apr 1999 16:10:51 +0200 From: Ollivier Robert To: net@freebsd.org Subject: Re: any alternative to gated for OSPF ? Message-ID: <19990425161051.A35119@keltia.freenix.fr> Mail-Followup-To: net@freebsd.org References: <199904250943.LAA04109@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199904250943.LAA04109@labinfo.iet.unipi.it>; from Luigi Rizzo on Sun, Apr 25, 1999 at 11:43:26AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Luigi Rizzo: > is there anything alternative to gated for supporting OSPF ? I need it > for a picobsd floppy but gated is kind of big... Have you looked at Zebra ? DISTNAME= zebra-980604 CATEGORIES= net MASTER_SITES= ftp://ftp.zebra.org/pub/zebra/ -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Apr 25 8:35:45 1999 Delivered-To: freebsd-net@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id DCA7714DB1 for ; Sun, 25 Apr 1999 08:35:40 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id BAA05406 for ; Mon, 26 Apr 1999 01:05:39 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA29304; Mon, 26 Apr 1999 01:06:09 +0930 Date: Mon, 26 Apr 1999 01:06:09 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: net@freebsd.org Subject: NetGraph and PPP Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been taking a look at the Whistle netgraph code, and it looks very interesting. What is the status of work on the mpd code wrt netgraph integration? I'm interested in doing some work on this - can anyone suggest a simple project I can cut my teeth on? Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 26 9:51:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.chromatix.com (unknown [207.97.115.130]) by hub.freebsd.org (Postfix) with ESMTP id E98F614C80 for ; Mon, 26 Apr 1999 09:51:11 -0700 (PDT) (envelope-from nick@chromatix.com) Received: from dogwood (dogwood.chromatix.com [207.97.115.140]) by mail.chromatix.com (8.8.8/8.8.8) with SMTP id MAA00526 for ; Mon, 26 Apr 1999 12:51:22 -0400 (EDT) (envelope-from nick@chromatix.com) Message-ID: <002501be9005$70fe1ad0$8c7361cf@dogwood.chromatix.com> From: "Nick LoPresti" To: Subject: Got a socks question for ya Date: Mon, 26 Apr 1999 12:54:25 -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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was wondering how to get my 3.0 FreeBSD machine to work behind a socks proxy server. I tried looking at the SOCKS v5 Application Layer but couldn't get anything out of it. Does anyone else do this? Anyone know how? ================================================ Nick nick@chromatix.com Web Page: http://www.lopresti.dhs.org/users/nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Apr 26 16:49:10 1999 Delivered-To: freebsd-net@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id E513D1539B for ; Mon, 26 Apr 1999 16:49:05 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA15252; Tue, 27 Apr 1999 09:19:04 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA17335; Tue, 27 Apr 1999 09:19:09 +0930 Date: Tue, 27 Apr 1999 09:19:09 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Nick LoPresti Cc: freebsd-net@FreeBSD.ORG Subject: Re: Got a socks question for ya In-Reply-To: <002501be9005$70fe1ad0$8c7361cf@dogwood.chromatix.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 Mon, 26 Apr 1999, Nick LoPresti wrote: > I was wondering how to get my 3.0 FreeBSD machine to work behind a socks > proxy server. I tried looking at the SOCKS v5 Application Layer but > couldn't get anything out of it. Does anyone else do this? Anyone know > how? Install the /usr/ports/net/socks5 port and set up the /usr/local/etc/socks.conf and /usr/local/etc/libsocks5.conf files according to the manpage (I think that's the right one). Then you can use 'runsocks ' to 'socksify' most (dynamically-linked) executables, and there are also a bunch of provided commands like rftp, rping, etc, which 'natively' talk through the firewall. Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 7:46:53 1999 Delivered-To: freebsd-net@freebsd.org Received: from bladerunner.skynetweb.com (bladerunner.skynetweb.com [208.239.240.41]) by hub.freebsd.org (Postfix) with ESMTP id 7284414C26 for ; Tue, 27 Apr 1999 07:46:46 -0700 (PDT) (envelope-from pryker@skynetweb.com) Received: from skynetweb.com (host80.skynetweb.com [208.231.1.80] (may be forged)) by bladerunner.skynetweb.com (8.8.8/8.8.8) with ESMTP id KAA08342 for ; Tue, 27 Apr 1999 10:46:45 -0400 (EDT) (envelope-from pryker@skynetweb.com) Message-ID: <37258582.1E8EFF6D@skynetweb.com> Date: Tue, 27 Apr 1999 10:38:10 +0100 From: Phillip Ryker Organization: SkyNetWEB Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Dummynet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org List, Is it possible to limit bandwidth to a specific range of IP's with out using subnets, for example, I have a server behind a FreeBSD box that is running Dummynet. The server has the foloowing IP's assigned to it: 208.233.6.42 - 50 MASK 255.255.255.0 Since the addresses are on the same subnet that the routers address is on I can not use the subnet mask to specify the range of IP's to limit. How would I limit all traffic to that group of IP's? Thank you -- Phillip Ryker ------------------------------ | SkyNetWEB Ltd. | | 1301 S. Baylis Street | | Baltimore Maryland 21224 | | Phone: 410.563.6384 | | Fax: 410.563.5457 | ------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 8:54: 7 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 98AAB155F9 for ; Tue, 27 Apr 1999 08:53:58 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA08527; Tue, 27 Apr 1999 15:41:22 +0200 From: Luigi Rizzo Message-Id: <199904271341.PAA08527@labinfo.iet.unipi.it> Subject: Re: Dummynet To: pryker@skynetweb.com (Phillip Ryker) Date: Tue, 27 Apr 1999 15:41:22 +0200 (MET DST) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <37258582.1E8EFF6D@skynetweb.com> from "Phillip Ryker" at Apr 27, 99 10:37:51 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 575 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > List, > > Is it possible to limit bandwidth to a specific range of IP's with out > using subnets, for example, I have a server behind a FreeBSD box that is > running Dummynet. The server has the foloowing IP's assigned to it: > > 208.233.6.42 - 50 MASK 255.255.255.0 > > Since the addresses are on the same subnet that the routers address is > on I can not use the subnet mask to specify the range of IP's to limit. > How would I limit all traffic to that group of IP's? at the bvery least you could just set different ipfw rules pointing to the same pipe. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 10:35:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from gateway.schneider.com (mailgate1.schneider.com [207.67.105.2]) by hub.freebsd.org (Postfix) with SMTP id 8BECF1547D for ; Tue, 27 Apr 1999 10:35:45 -0700 (PDT) (envelope-from WAYNEK@SCHNEIDER.COM) Received: from SMTPGW1.schneider.com by gateway.schneider.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 27 Apr 1999 16:52:28 UT Date: Tue, 27 Apr 1999 12:32 -0600 From: "Wayne, Ken" To: freebsd-net@freebsd.org Subject: Replacing Exchange Server Message-ID: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am in the information gathering stage of what to use instead of MS Exchange as my mail server and would appreciate any suggestions on which FreeBSD email server you would recommend. My requirements are simply to replace what I am currently doing with Exchange. I registered a domain that my ISP hosts and have a static IP address from my ISP and an MX record in there DNS. They queue my email for me and Exchange sends an ETRN command to retrieve mail from the queue periodically. I have about 15 email addresses, and the clients are outlook on Win '95. It would appear that SendMail could do what I want, but is this the best mail service (ease of use, support, features, etc...), does it support ETRN, and can I use Outlook to read my mail? Thank You, -Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 14:17:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0161914E76 for ; Tue, 27 Apr 1999 14:17:26 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA02955; Tue, 27 Apr 1999 23:17:18 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 81A788837; Tue, 27 Apr 1999 21:56:17 +0200 (CEST) Date: Tue, 27 Apr 1999 21:56:17 +0200 From: Ollivier Robert To: freebsd-net@freebsd.org Cc: "Wayne, Ken" Subject: Re: Replacing Exchange Server Message-ID: <19990427215617.A67634@keltia.freenix.fr> Mail-Followup-To: freebsd-net@freebsd.org, "Wayne, Ken" References: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM>; from Wayne, Ken on Tue, Apr 27, 1999 at 12:32:00PM -0600 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Wayne, Ken: > It would appear that SendMail could do what I want, but is this the best mail > service (ease of use, support, features, etc...), does it support ETRN, and > can I use Outlook to read my mail? I'm somewhat biaised towards Postfix, having been an alpha tester for months and running it on every machine I can lay my hands on :-) FreeBSD.org's experience with it in place of sendmail is pretty good, Postfix is way faster and more secure than sendmail. You'll need an IMAP/POP server; Cyrus (see ports/mail/cyrus) works well with Postfix). It is very easy to setup and has probably more features that you need :-) (virtual domains, very efficient antispam features, regex support, and much more). Support is handled, like many other Open Source products, through a mailing-list, postfix-users (mailto:Majordomo@postfix.org). You can use an LDAP server for aliases, virtual domains and such. See for details. BTW Outlook is not really a good Windows mail reader. Better use something like Pegasus, Agent or Eurora. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 15:18:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from cortex.NSMA.Arizona.EDU (cortex.NSMA.Arizona.EDU [128.196.180.125]) by hub.freebsd.org (Postfix) with ESMTP id D486A14D35 for ; Tue, 27 Apr 1999 15:18:17 -0700 (PDT) (envelope-from ddw@raphe.NSMA.Arizona.EDU) Received: from raphe (raphe [128.196.180.144]) by cortex.NSMA.Arizona.EDU (8.7.5/8.7.5) with ESMTP id PAA16094 for ; Tue, 27 Apr 1999 15:26:39 -0700 (MST) Message-Id: <199904272226.PAA16094@cortex.NSMA.Arizona.EDU> To: freebsd-net@freebsd.org Subject: Re: Replacing Exchange Server In-reply-to: Your message of "Tue, 27 Apr 1999 21:56:17 +0200." <19990427215617.A67634@keltia.freenix.fr> Date: Tue, 27 Apr 1999 15:16:06 -0700 From: Doug Wellington Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Previously: >> It would appear that SendMail could do what I want [...] > >I'm somewhat biaised towards Postfix [...] How does postfix really compare to the other major MTA's? (Sendmail, exim, zmailer, and, my favorite, qmail.) If I remember correctly, postfix/vmailer is an update of smail, isn't it? The guy working on it right now (Weitse) is one of the Gods of the Internet, having created the tcp wrappers among other things. (But then again, the people working on the other packages aren't slouches either!) As a side note: sendmail isn't all that bad. On the Internet, it is used for more email than all the other MTA's put together. (In corporate America, it's quite a different story...) With the more recent versions configurable with m4, it is actually quite easy to set up, and there is a new commercial version available if you need that kind of accountability and support. If you want something good on a resume (for the non-corporate world), knowing sendmail is going to take you further than the others... >FreeBSD.org's experience with it in place of sendmail is pretty good, Postfix >is way faster and more secure than sendmail. Heehee, well, traditionally, almost anything has been faster and more secure than sendmail. That has changed and the new versions are quite good though... >BTW Outlook is not really a good Windows mail reader. What makes you say that? -Doug Doug Wellington ddw@nsma.arizona.edu Network and System Administrator ARL, Division of Neural Systems, Memory and Aging The University of Arizona, Tucson, AZ I DON'T buy anything from spammers, and I KEEP TRACK OF WHO SPAMS ME. I put up with ads on the TV because they pay for programming. When spammers pay for the Internet, then I'll start putting up with spam. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 15:25:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id E531714D35 for ; Tue, 27 Apr 1999 15:25:34 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id PAA19684; Tue, 27 Apr 1999 15:25:32 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA24473; Tue, 27 Apr 1999 15:25:32 -0700 Received: from softweyr.com (dyn5.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA23408; Tue, 27 Apr 99 15:25:30 PDT Message-Id: <3726395A.2E61980A@softweyr.com> Date: Tue, 27 Apr 1999 16:25:30 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "Wayne, Ken" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Replacing Exchange Server References: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Wayne, Ken" wrote: > > I am in the information gathering stage of what to use instead of MS Exchange > as my mail server and would appreciate any suggestions on which FreeBSD email > server you would recommend. > > My requirements are simply to replace what I am currently doing with > Exchange. I registered a domain that my ISP hosts and have a static IP > address from my ISP and an MX record in there DNS. They queue my email for > me and Exchange sends an ETRN command to retrieve mail from the queue > periodically. I have about 15 email addresses, and the clients are outlook > on Win '95. > > It would appear that SendMail could do what I want, but is this the best mail > service (ease of use, support, features, etc...), does it support ETRN, and > can I use Outlook to read my mail? As is usual in the PC world, Exchange is providing several services here, none of them very good. You can accomplish the same with several tools that are shipped with FreeBSD. For mail transport, use Sendmail. It *is* the standard for Internet email. It is also flexible and well known, and the most secure transport because it is so widely used and open-source. If you do not want to learn the somewhat arcane configuration file syntax, you can buy Sendmail Plus and use the Plus part to generate your configuration files; most FreeBSD admins simply customize one of the example config files shipped with FreeBSD. To retrieve your mail from your ISP via ETRN mode, you need fetchmail. You can setup a cron job to run fetchmail regularly, as I do. I provide client access to the mail server, you need a POP3 or IMAP4 server, or perhaps both. imap-uw provides both types of access and is simple to configure. It works well with sendmail. I'm using the above configuration for my small domain, with 7 or so active email accounts, and it works quite well. Other servers exists in each of these areas, and have their unique plusses and minuses. Best of luck. Replacing Exchange with just about anything would be an improvement, and you've started off with a good base in FreeBSD. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 15:49:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 48B15151A3 for ; Tue, 27 Apr 1999 15:49:29 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 3E2D54CE02; Tue, 27 Apr 1999 18:49:29 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id SAA09849; Tue, 27 Apr 1999 18:49:27 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.7/8.8.5) id SAA04128; Tue, 27 Apr 1999 18:49:27 -0400 (EDT) Message-Id: <199904272249.SAA04128@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: spork@super-g.com Subject: Re: ARP weirdness(?) Cc: freebsd-net@freebsd.org Date: Tue, 27 Apr 1999 15:49:26 -0700 Versions: dmail (solaris) 2.2c/makemail 2.8t Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 3.x does this. It would take a small amount of porting to make it work on 2.2.x; see http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/if_ether.c.diff?r1=1.47&r2=1.48 Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Apr 27 22:47:32 1999 Delivered-To: freebsd-net@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1B8FE14C3B for ; Tue, 27 Apr 1999 22:47:24 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id HAA22634 for freebsd-net@freebsd.org; Wed, 28 Apr 1999 07:47:23 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 05A658840; Wed, 28 Apr 1999 07:37:45 +0200 (CEST) (envelope-from roberto) Date: Wed, 28 Apr 1999 07:37:45 +0200 From: Ollivier Robert To: freebsd-net@freebsd.org Subject: Re: Replacing Exchange Server Message-ID: <19990428073745.A72846@keltia.freenix.fr> Mail-Followup-To: freebsd-net@freebsd.org References: <19990427215617.A67634@keltia.freenix.fr> <199904272226.PAA16094@cortex.NSMA.Arizona.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit User-Agent: Mutt/0.95.5i In-Reply-To: <199904272226.PAA16094@cortex.NSMA.Arizona.EDU>; from Doug Wellington on Tue, Apr 27, 1999 at 03:16:06PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Doug Wellington: > How does postfix really compare to the other major MTA's? (Sendmail, exim, > zmailer, and, my favorite, qmail.) If I remember correctly, postfix/vmailer Very nicely. I've been using sendmail for years (I'm also a beta tester of sendmail and am a former beta-teser of qmail) but Postfix just blow it away. Really. There are two real alternative to sendmail these days. Postfix and Qmail. Why not the other ones ? Just one reason: all the others use the same design as sendmail with a big monolithic setuid root binary. That makes them less secure and slower. > is an update of smail, isn't it? Absolutely not. It is a complete redesign in a modular way, à la qmail but better. It uses a inetd-like process (master) to manage all the other processes, giving a very secure and fast architecture. More details on the web site. No setuid binary at all. No process trusts the other. You have parallel delivery (but better than qmail's), header rewriting, header filtering, regex support for the same, has virtual domains, supports UUCP, has a very easy configuration file and too many other features to list :-) Smail on the other hand is still using a monolithic setuid root binary. > The guy working on it right now (Weitse) is > one of the Gods of the Internet, having created the tcp wrappers among other That's the one. > Heehee, well, traditionally, almost anything has been faster and more secure > than sendmail. That has changed and the new versions are quite good though.. Ask our postmaster (jmb) for the difference in speed between the two... > >BTW Outlook is not really a good Windows mail reader. > > What makes you say that? Lost of things. It doesn't deal with In-Reply-To: properly, doesn't generate References: at all IIRC, it is too easy to send HTML & UTF-8 crap, its quoting code is completely broken. Among others. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 0: 9:48 1999 Delivered-To: freebsd-net@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id CA74914E0F for ; Wed, 28 Apr 1999 00:09:43 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 90505 invoked by uid 1000); 28 Apr 1999 07:21:17 -0000 Date: Wed, 28 Apr 1999 09:21:17 +0200 From: Andreas Braukmann To: freebsd-net@FreeBSD.ORG Cc: "Wayne, Ken" Subject: Re: Replacing Exchange Server Message-ID: <19990428092117.J82441@paert.tse-online.de> References: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM>; from Wayne, Ken on Tue, Apr 27, 1999 at 12:32:00PM -0600 Organization: TSE TeleService GmbH Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Tue, Apr 27, 1999 at 12:32:00PM -0600, Wayne, Ken wrote: > They queue my email for me and Exchange sends an ETRN command to > retrieve mail from the queue periodically. I have about 15 email > addresses, and the clients are outlook on Win '95. hmm. I've setup mail servers based upon sendmail, exim (www.exim.org) and qmail (www.qmail.org) in the past. For simple setups like yours I found 'qmail' suitable, and easy to maintain. 'fetchmail' (see ports-collection) supports the 'ETRN' way of getting the mail. You may easily setup a cron job doing it. > It would appear that SendMail could do what I want, but is this sure. > the best mail service (ease of use, support, features, etc...), But security and maintainability concerns lead one to simply avoid sendmail. For more complex situations or a really 'volume-oriented' setup I personally would jump into 'postfix'. (www.postfix.org) Regards, Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 6:27:22 1999 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 5502D15701; Wed, 28 Apr 1999 06:27:14 -0700 (PDT) From: "Jonathan M. Bresler" To: ddw@raphe.NSMA.Arizona.EDU Cc: freebsd-net@freebsd.org In-reply-to: <199904272226.PAA16094@cortex.NSMA.Arizona.EDU> (message from Doug Wellington on Tue, 27 Apr 1999 15:16:06 -0700) Subject: Re: Replacing Exchange Server Message-Id: <19990428132714.5502D15701@hub.freebsd.org> Date: Wed, 28 Apr 1999 06:27:14 -0700 (PDT) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > As a side note: sendmail isn't all that bad. On the Internet, it is used for > more email than all the other MTA's put together. (In corporate America, it's > quite a different story...) With the more recent versions configurable with > m4, it is actually quite easy to set up, and there is a new commercial version > available if you need that kind of accountability and support. If you want > something good on a resume (for the non-corporate world), knowing sendmail is > going to take you further than the others... sendmail is unrivalled in configurability. No other MTA supports the range of mail transfer protocols and customizable (sp) that sendmail supports. The cost of this flexibility is a somewhat more complicated configuration mechanism.....this is not surprisinbg ;) sendmail has the largest carde of trained administrators. the sendmail oreilly book is excellent. i am sure that sendmail will continue to improve. you cant go wrong using sendmail. it may not be the absolute best tool for every job. Sendmail is a very good MTA for nearly every job. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve JMB193 http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 6:40:53 1999 Delivered-To: freebsd-net@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id A6DE314C08 for ; Wed, 28 Apr 1999 06:40:44 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id OAA08135; Wed, 28 Apr 1999 14:40:44 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma008113; Wed, 28 Apr 99 14:40:33 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10cUZj-0007cC-00; Wed, 28 Apr 1999 14:40:31 +0100 To: net@freebsd.org From: Tony Finch Subject: Re: Replacing Exchange Server In-Reply-To: <199904272226.PAA16094@cortex.NSMA.Arizona.EDU> References: <19990427215617.A67634@keltia.freenix.fr> Message-Id: Date: Wed, 28 Apr 1999 14:40:31 +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Wellington wrote: > >If I remember correctly, postfix/vmailer is an update of smail, isn't it? That's exim, although exim was written from scratch. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Arthur: "Oh, that sounds better, have you worked out the controls?" Ford: "No, we just stopped playing with them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 8:41:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 35DCE15725; Wed, 28 Apr 1999 08:41:14 -0700 (PDT) (envelope-from lyndon@MessagingDirect.COM) Received: from MessagingDirect.COM (zappa.esys.ca [198.161.92.28]) by rembrandt.esys.ca (2.1/8.9.1/Execmail 2.1) with ESMTP id JAA20024; Wed, 28 Apr 1999 09:41:05 -0600 Message-Id: <199904281541.JAA20024@rembrandt.esys.ca> Date: Wed, 28 Apr 1999 09:41:02 -0600 From: Lyndon.Nerenberg@MessagingDirect.COM Subject: Re: Replacing Exchange Server To: jmb@hub.freebsd.org Cc: ddw@raphe.NSMA.Arizona.EDU, freebsd-net@FreeBSD.ORG In-Reply-To: <19990428132714.5502D15701@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > sendmail is unrivalled in configurability. No other MTA > supports the range of mail transfer protocols and customizable (sp) > that sendmail supports. ISODE PP? I don't recall sendmail handling X.400. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 14: 7:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from ss1000.ms.mff.cuni.cz (ss1000.ms.mff.cuni.cz [195.113.19.221]) by hub.freebsd.org (Postfix) with ESMTP id 4C42614F7B for ; Wed, 28 Apr 1999 14:07:47 -0700 (PDT) (envelope-from mkop5230@ss1000.ms.mff.cuni.cz) Received: from beta.ms.mff.cuni.cz (mkop5230@beta.ms.mff.cuni.cz [195.113.16.70]) by ss1000.ms.mff.cuni.cz (8.8.8/8.8.8) with ESMTP id XAA08138 for ; Wed, 28 Apr 1999 23:07:47 +0200 Received: from localhost (mkop5230@localhost) by beta.ms.mff.cuni.cz (980427.SGI.8.8.8/8.8.8) with ESMTP id XAA11597 for ; Wed, 28 Apr 1999 23:07:46 +0200 (MDT) Date: Wed, 28 Apr 1999 23:07:46 +0200 From: Milan Kopacka Reply-To: Milan Kopacka To: freebsd-net@freebsd.org Subject: Out of mbuf clusters 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 Hallo, I'm getting "Out of mbuf clusters" kernel panic, if there are processes in the system dying and leaving many opened tcp sockets. Special attack -> forking "open tcp socket and die" processes needs time under 30 sec to bring the machine down (thousands of opened sockets). FreeBSD 3.0 or 3.1; no special tuning of GENERIC kernel, just disabling some hw drivers & so on. (K6/300, 64MB of memory, de0 eth driver) In mailing lists archives I have found an advice to tune the kernel by increasing NMBCLUSTERS. How much does it help to raise the flag higher? I'm not talking about normal load, but about such mbuf attack from non-root user. Could someone explain to me, why being out of mbuf clusters is a reason to kernel panic? thanks Milan Kopacka -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 14:24:37 1999 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 8C4BD1550E; Wed, 28 Apr 1999 14:24:36 -0700 (PDT) From: "Jonathan M. Bresler" To: Lyndon.Nerenberg@MessagingDirect.COM Cc: ddw@raphe.NSMA.Arizona.EDU, freebsd-net@FreeBSD.ORG In-reply-to: <199904281541.JAA20024@rembrandt.esys.ca> (Lyndon.Nerenberg@MessagingDirect.COM) Subject: Re: Replacing Exchange Server Message-Id: <19990428212436.8C4BD1550E@hub.freebsd.org> Date: Wed, 28 Apr 1999 14:24:36 -0700 (PDT) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > sendmail is unrivalled in configurability. No other MTA > > supports the range of mail transfer protocols and customizable (sp) > > that sendmail supports. > > ISODE PP? I don't recall sendmail handling X.400. correct. thank god! jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 21:39:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id DA7C21509E for ; Wed, 28 Apr 1999 21:39:37 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id VAA89472; Wed, 28 Apr 1999 21:39:02 -0700 (PDT) From: Archie Cobbs Message-Id: <199904290439.VAA89472@bubba.whistle.com> Subject: Re: NetGraph and PPP In-Reply-To: from Kris Kennaway at "Apr 26, 99 01:06:09 am" To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Wed, 28 Apr 1999 21:39:01 -0700 (PDT) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kennaway writes: > I've been taking a look at the Whistle netgraph code, and it looks very > interesting. What is the status of work on the mpd code wrt netgraph > integration? > > I'm interested in doing some work on this - can anyone suggest a simple > project I can cut my teeth on? Mpd works great with netgraph, as witnessed by thousands of InterJets out in the field :-) For our ISDN driver we took some proprietary 3rd party code (that we can't donate to FreeBSD obviously) and wrapped it up in a netgraph node. It's very convenient. For example, we could do frame relay over ISDN very easily if we wanted to (though nobody does that). Actually we wrote two nodes, the ISDN device node (which has three hooks: B1, B2, and D as you might expect) and another node that represents the ISDN stack. For the ISDN stack node, control messages are used to do things like set the switch type and SPIDs, dial, answer, etc. It hooks up to the device node obviously. A great project in this area would be to take the i4b code and make it look like a netgraph node that presents the same "API", ie. an ISDN stack node. Then we already have an mpd device type that knows how to use this node for PPP (which we can donate). I can send you the node's header file if you're interested in tackling this. Then mpd will work with i4b. Also, as well as netgraphifying the "top end" of i4b, we could netgraphify the "bottom end" device drivers to make all the different hardware types supported by i4b look like netgraph nodes. Ours (for the Siemens IPAC chip in S and U interface configurations) could then plug directly into i4b. We could probably donate this too. Other ideas for netgraph nodes we've had.. 1. Convert ipfw into a netgraph node 2. Write a node type that implements DPF: http://www.pdos.lcs.mit.edu/~engler/dpf.html 3. Revamped PPP node with separate node types for compression, encryption, etc. This is probably my next project, to push all PPP data packet processing into the kernel and obliviate the need for the existing kernel PPP drivers. 4. Make the entire networking stack netgraph based, supporting dynamic loading of networking stacks such as IP, IPX, etc. Similarly, IP protocols themselves (TCP, UDP, GRE, etc) could be netgraph nodes. I think #4 is a bit of a pipe dream.. for one, it would never pass the DG filter :-) Our request to put the netgraph source into the FreeBSD tree has been rejected (so far)... so the current patch set may need tweaking to compile right now. More people using and playing with it might bring it's demand over the threshold... this is a kind of chicken-and-egg problem in itself. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Apr 28 23:19:54 1999 Delivered-To: freebsd-net@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AE33B14D45 for ; Wed, 28 Apr 1999 23:19:52 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA46507; Wed, 28 Apr 1999 23:19:59 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Archie Cobbs Cc: kkennawa@physics.adelaide.edu.au (Kris Kennaway), net@FreeBSD.ORG Subject: Re: NetGraph and PPP In-reply-to: Your message of "Wed, 28 Apr 1999 21:39:01 PDT." <199904290439.VAA89472@bubba.whistle.com> Date: Wed, 28 Apr 1999 23:19:59 -0700 Message-ID: <46505.925366799@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Our request to put the netgraph source into the FreeBSD tree has > been rejected (so far)... so the current patch set may need tweaking I'm glad you qualified that - I don't think there's been anything close to wholesale rejection, and I also don't think anyone would mind (too much) if it came in on its own branch at some point. That's supposed to be what CVS is for, after all. > to compile right now. More people using and playing with it might > bring it's demand over the threshold... this is a kind of chicken-and-egg > problem in itself. It is, but I think you're on the right track. Establish a demand and you've established a reason to have it somewhere in the repository. Establish an even greater demand and that will be a rather good argument for bringing it, in some form, into -current at some stage. I think it's all probably a little premature at this stage to talk about things like that, however, and will only raise various red flags if we invert the order of priorities (first users, then -current) here. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 3:52:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from email.alpcom.it (email.alpcom.it [193.42.134.240]) by hub.freebsd.org (Postfix) with ESMTP id E805C14F0E for ; Thu, 29 Apr 1999 03:52:44 -0700 (PDT) (envelope-from Lorenzo.Cavassa@ALPcom.IT) Received: from monviso.alpcom.it by ALPCOM.IT (PMDF V5.1-9 #23639) with SMTP id <01JALRT82OW000JDOT@ALPCOM.IT> for freebsd-net@FreeBSD.org; Thu, 29 Apr 1999 11:53:23 MET Received: by monviso.alpcom.it (950911.SGI.8.6.12.PATCH825/940406.SGI) for freebsd-net@FreeBSD.org id KAA29094; Thu, 29 Apr 1999 10:52:41 +0000 (GMT) Date: Thu, 29 Apr 1999 10:52:40 +0000 From: Lorenzo Cavassa Subject: Gigabit ethernet support? To: freebsd-net@FreeBSD.org Message-id: <19990429105240.A29065@monviso.alpcom.it> MIME-version: 1.0 X-Mailer: Mutt 0.93.2i Content-type: text/plain; charset=us-ascii X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-editor: VIM 5 - http://www.vim.org X-PGP-key-fingerprint: 203C 79AE 2A7A 6147 D4A8 8BEE D26A 06EB X-PGP-keyID: 0x833FB7FD -- key available on keyservers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i need some advices about an ( eventually ) gigabit ethernet support in FreeBSD 3.x-RELEASE or 3.x-CURRENT: NICs, drivers and so on ( also case-studies and/or performance tests ). Thank! Lorenzo -- ------------------------------------------------------------------------ Lorenzo Cavassa | voice: +39 011.316.8975 CSP | fax: +39 011.316.8212 Corso Unione Sovietica, 216 | email: cavassa@csp.it IT-10134, Torino, Italy | web: http://www.csp.it ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 4:22:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 13D3A14E62 for ; Thu, 29 Apr 1999 04:22:45 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id HAA17394; Thu, 29 Apr 1999 07:22:29 -0400 (EDT) Date: Thu, 29 Apr 1999 07:22:29 -0400 (EDT) From: "Matthew N. Dodd" To: Lorenzo Cavassa Cc: freebsd-net@FreeBSD.ORG Subject: Re: Gigabit ethernet support? In-Reply-To: <19990429105240.A29065@monviso.alpcom.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Apr 1999, Lorenzo Cavassa wrote: > i need some advices about an ( eventually ) gigabit ethernet support in > FreeBSD 3.x-RELEASE or 3.x-CURRENT: NICs, drivers and so on ( also > case-studies and/or performance tests ). You've got some choice at this point though 1 option is probably a little unattractive. Packet Engines GNIC/GNICII devices. - Single source (PacketEngines; http://www.packetengines.com/) - no driver in any FreeBSD source tree. - 2.2 drivers at ftp://ftp.scl.ameslab.gov/pub/drivers/ - Webpage at http://www.scl.ameslab.gov/Projects/Gigabit/ Alteon TIGON 1/TIGON 2 devices. - Multiple sources. + Alteon AceNIC (Tigon 1 and Tigon 2) + 3Com 3c985-SX (Tigon 1 and Tigon 2) + Netgear GA620 (Tigon 2) + (others) - driver in -CURRENT - 2.2 and 3.0 versions available at http://www.freebsd.org/~wpaul/Alteon Choose wisely. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 13:50: 0 1999 Delivered-To: freebsd-net@freebsd.org Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by hub.freebsd.org (Postfix) with ESMTP id 52A15152E6 for ; Thu, 29 Apr 1999 13:49:56 -0700 (PDT) (envelope-from nicole@xwin.nmhtech.com) Received: by xwin.nmhtech.com (Postfix, from userid 1001) id 878B92EE1A; Thu, 29 Apr 1999 13:49:55 -0700 (PDT) Content-Length: 2556 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 In-Reply-To: Date: Thu, 29 Apr 1999 13:49:55 -0700 (PDT) From: Nicole Harrington To: "Matthew N. Dodd" Subject: Re: Gigabit ethernet support? Cc: freebsd-net@FreeBSD.ORG, Lorenzo Cavassa Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Apr-99 My Secret Spies Reported That Matthew N. Dodd wrote: > On Thu, 29 Apr 1999, Lorenzo Cavassa wrote: >> i need some advices about an ( eventually ) gigabit ethernet support in >> FreeBSD 3.x-RELEASE or 3.x-CURRENT: NICs, drivers and so on ( also >> case-studies and/or performance tests ). >=20 > You've got some choice at this point though 1 option is probably a little > unattractive. >=20 > Packet Engines GNIC/GNICII devices. > - Single source (PacketEngines; http://www.packetengines.com/) =20 > - no driver in any FreeBSD source tree. > - 2.2 drivers at ftp://ftp.scl.ameslab.gov/pub/drivers/ > - Webpage at http://www.scl.ameslab.gov/Projects/Gigabit/ >=20 I have been working on a project with the Packet engines devices and I hav= e been disapointed. They have been promising me a more robust driver for thei= r nic card for months now and won't relase any information without an NDA for others (like Bill Paul) to write drivers for them. Their current drivers ha= ve known issues. Unless they make some moves, we will likely be moving to Alteon. Nicole > Alteon TIGON 1/TIGON 2 devices. > - Multiple sources. > + Alteon AceNIC (Tigon 1 and Tigon 2) =20 > + 3Com 3c985-SX (Tigon 1 and Tigon 2) =20 > + Netgear GA620 (Tigon 2) > + (others) =20 > - driver in -CURRENT > - 2.2 and 3.0 versions available at > http://www.freebsd.org/~wpaul/Alteon > > Choose wisely. >=20 > --=20 >| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/= VMS >| | >| winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,v= ax=20 >| | >| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage= ? =20 >| | >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message |\ __ /| (`\ =20 | o_o |__ ) ) =20 // \\ =20 nicole@nmhtech.com | http://www.webweaver.net/ webmistress@dangermouse.org | http://www.dangermouse.org -------------------------(((---(((----------------------- =20 - Powered by Coka Cola and FreeBSD - - Strong enough for a man - But made for a Woman - =20 - I'm not ADD - I'm just Multithreaded - - Microsoft: What bug would you like today? - ---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 14:20:42 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 9B2A31557A for ; Thu, 29 Apr 1999 14:20:37 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id RAA26296; Thu, 29 Apr 1999 17:20:32 -0400 (EDT) Date: Thu, 29 Apr 1999 17:20:32 -0400 (EDT) From: "Matthew N. Dodd" To: Nicole Harrington Cc: freebsd-net@FreeBSD.ORG, Lorenzo Cavassa Subject: Re: Gigabit ethernet support? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Apr 1999, Nicole Harrington wrote: > On 29-Apr-99 My Secret Spies Reported That Matthew N. Dodd wrote: > > On Thu, 29 Apr 1999, Lorenzo Cavassa wrote: > >> i need some advices about an ( eventually ) gigabit ethernet support in > >> FreeBSD 3.x-RELEASE or 3.x-CURRENT: NICs, drivers and so on ( also > >> case-studies and/or performance tests ). > > > > You've got some choice at this point though 1 option is probably a little > > unattractive. > > > > Packet Engines GNIC/GNICII devices. > > - Single source (PacketEngines; http://www.packetengines.com/) > > - no driver in any FreeBSD source tree. > > - 2.2 drivers at ftp://ftp.scl.ameslab.gov/pub/drivers/ > > - Webpage at http://www.scl.ameslab.gov/Projects/Gigabit/ > > > > I have been working on a project with the Packet engines devices and I have > been disapointed. They have been promising me a more robust driver for their > nic card for months now and won't relase any information without an NDA for > others (like Bill Paul) to write drivers for them. Their current drivers have > known issues. > > Unless they make some moves, we will likely be moving to Alteon. You might tell them that SysKonnect is negotiating the release of programming information for their gigabit ethernet cards. Packet Engines stands to lose the NIC market even though they had the first shipping product. If you'd like to send me your contact information I'd be glad to go around a few times with them. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 15: 6:28 1999 Delivered-To: freebsd-net@freebsd.org Received: from qatar.net.qa (qatar.net.qa [194.133.33.11]) by hub.freebsd.org (Postfix) with ESMTP id 287B414F82; Thu, 29 Apr 1999 15:06:19 -0700 (PDT) (envelope-from sodah@qatar.net.qa) Received: from qatar.net.qa (dicp.qatar.net.qa [194.133.37.76]) by qatar.net.qa (8.8.8/Internet-Qatar) with ESMTP id BAA22939; Fri, 30 Apr 1999 01:04:44 +0300 (GMT) Message-ID: <3728D77E.6276D1AE@qatar.net.qa> Date: Fri, 30 Apr 1999 01:04:46 +0300 From: Fadi Sodah X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-admin@FreeBSD.org Subject: hub 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 am running ircd hub on my machine. when i run the commmand dmesg, it reported --->>>> 'arp_rtrequest: bad gateway value' what could be wrong? the machine has the following config. /etc/rc.conf .... named_enable="NO" # Run named, the DNS server (or NO). ### Network routing options: ### defaultrouter="xxx.yy.z.www"* # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave gateway_enable="NO" # Set to YES if this host wil... router_enable="NO" # Set to YES to enable a routing daemon. router="routed" # Name of routing daemon to use if router_flags="-q" # Flags for routing daemon. mrouted_enable="NO" # mrouted_flags="" # Flags for multicast routing daemon. ipxgateway_enable="NO" # Set to YES to enable IPX routing. ipxrouted_enable="NO" # Set ... ipxrouted_flags="" # Flags for IPX routing daemon. arpproxy_all="" # replaces obso ....RP_PROXYALL. forward_sourceroute="NO" # do source routing (if ..."YES") accept_sourceroute="NO" # accept source routed packets to us natd_enable="NO" # Enable natd if firewall_enable. natd_interface="fxp0" # interf to u....natd_enable. natd_flags="" # Additional flags for natd. *)p.s i replaced the real ip with xxx.yy.z.www thx -Pons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 16:48:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id CB7A615155 for ; Thu, 29 Apr 1999 16:48:25 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA24955; Thu, 29 Apr 1999 16:45:38 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA04570; Thu, 29 Apr 1999 16:45:08 -0700 Received: from softweyr.com (dyn5.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA08232; Thu, 29 Apr 99 16:44:06 PDT Message-Id: <37289996.97CB07C9@softweyr.com> Date: Thu, 29 Apr 1999 11:40:38 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "Matthew N. Dodd" Cc: Lorenzo Cavassa , freebsd-net@FreeBSD.ORG Subject: Re: Gigabit ethernet support? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Matthew N. Dodd" wrote: > > On Thu, 29 Apr 1999, Lorenzo Cavassa wrote: > > i need some advices about an ( eventually ) gigabit ethernet support in > > FreeBSD 3.x-RELEASE or 3.x-CURRENT: NICs, drivers and so on ( also > > case-studies and/or performance tests ). > > You've got some choice at this point though 1 option is probably a little > unattractive. > > Packet Engines GNIC/GNICII devices. > - Single source (PacketEngines; http://www.packetengines.com/) > - no driver in any FreeBSD source tree. > - 2.2 drivers at ftp://ftp.scl.ameslab.gov/pub/drivers/ > - Webpage at http://www.scl.ameslab.gov/Projects/Gigabit/ I'll be providing a supported 3.x driver for the PE cards as soon as I can get my hands on some, and get my head wrapped around GE driver code. It turns out Packet Engines is now a part of my company. Plus, I need some for GigE testing here at work. Now that we're all one big happy family I should be able to transfer a few over here in the next month or so. They won't make it in time for 3.2, but I hope to have something working for 3.3. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 18:19:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by hub.freebsd.org (Postfix) with ESMTP id CFC331528C for ; Thu, 29 Apr 1999 18:18:11 -0700 (PDT) (envelope-from nicole@xwin.nmhtech.com) Received: by xwin.nmhtech.com (Postfix, from userid 1001) id 594D92EE1A; Thu, 29 Apr 1999 18:18:11 -0700 (PDT) Content-Length: 2484 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 In-Reply-To: <37289996.97CB07C9@softweyr.com> Date: Thu, 29 Apr 1999 18:18:11 -0700 (PDT) From: Nicole Harrington To: Wes Peters Subject: Re: Gigabit ethernet support? Cc: freebsd-net@FreeBSD.ORG, Lorenzo Cavassa , Matthew N.Dodd Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Apr-99 My Secret Spies Reported That Wes Peters wrote: > "Matthew N. Dodd" wrote: >>=20 >> On Thu, 29 Apr 1999, Lorenzo Cavassa wrote: >> > i need some advices about an ( eventually ) gigabit ethernet support i= n >> > FreeBSD 3.x-RELEASE or 3.x-CURRENT: NICs, drivers and so on ( also >> > case-studies and/or performance tests ). >>=20 >> You've got some choice at this point though 1 option is probably a littl= e >> unattractive. >>=20 >> Packet Engines GNIC/GNICII devices. >> - Single source (PacketEngines; http://www.packetengines.com/) >> - no driver in any FreeBSD source tree. >> - 2.2 drivers at ftp://ftp.scl.ameslab.gov/pub/drivers/ >> - Webpage at http://www.scl.ameslab.gov/Projects/Gigabit/ >=20 > I'll be providing a supported 3.x driver for the PE cards as soon as I > can get my hands on some, and get my head wrapped around GE driver > code. It turns out Packet Engines is now a part of my company. Plus, I= =20 > need some for GigE testing here at work. Now that we're all one big > happy family I should be able to transfer a few over here in the next > month or so. They won't make it in time for 3.2, but I hope to have > something working for 3.3. >=20 > --=20 Cool.=20 I decided to let Packet Engines in on the talk and they "seemed" quite receptive. We shall see. Would you like to speak with her? Perhaps you could speed things along. Sh= e almost seemed to be willing to do a NON NDA deal with Bill Paul than lose t= he action. Nicole > "Where am I, and what am I doing in this handbasket?" >=20 > Wes Peters Softweyr LLC > http://www.softweyr.com/~softweyr wes@softweyr.com >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message |\ __ /| (`\ =20 | o_o |__ ) ) =20 // \\ =20 nicole@nmhtech.com | http://www.webweaver.net/ webmistress@dangermouse.org | http://www.dangermouse.org -------------------------(((---(((----------------------- =20 - Powered by Coka Cola and FreeBSD - - Strong enough for a man - But made for a Woman - =20 - I'm not ADD - I'm just Multithreaded - - Microsoft: What bug would you like today? - ---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 21:12:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 0A49E14E58 for ; Thu, 29 Apr 1999 21:12:13 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA02242; Fri, 30 Apr 1999 00:12:05 -0400 (EDT) Date: Fri, 30 Apr 1999 00:12:05 -0400 (EDT) From: "Matthew N. Dodd" To: Nicole Harrington Cc: Wes Peters , freebsd-net@FreeBSD.ORG, Lorenzo Cavassa Subject: Re: Gigabit ethernet support? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Apr 1999, Nicole Harrington wrote: > I decided to let Packet Engines in on the talk and they "seemed" quite > receptive. We shall see. Thats a good thing. > Would you like to speak with her? Perhaps you could speed things > along. She almost seemed to be willing to do a NON NDA deal with Bill > Paul than lose the action. We should probably bring Bill into the loop at some point. I'm hesitant to sign him up for more work than he's got now. If Packet Engines can see clear to make the programming materials available on their webpage it seems certain that someone will pick it up. If your efforts require adherence to schedules and deadlines then this measure of patience may not be possible. If I can be of help in talking with Packet Engines I offer my assistance. I am currently talking with SysKonnect so I'm in a fairly good position to try and get the two bidding against each other as it were. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Apr 29 21:17:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 6A3A214F28 for ; Thu, 29 Apr 1999 21:17:26 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA02329; Fri, 30 Apr 1999 00:17:20 -0400 (EDT) Date: Fri, 30 Apr 1999 00:17:20 -0400 (EDT) From: "Matthew N. Dodd" To: Wes Peters Cc: Lorenzo Cavassa , freebsd-net@FreeBSD.ORG Subject: Re: Gigabit ethernet support? In-Reply-To: <37289996.97CB07C9@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Apr 1999, Wes Peters wrote: > I'll be providing a supported 3.x driver for the PE cards as soon as I > can get my hands on some, and get my head wrapped around GE driver > code. It turns out Packet Engines is now a part of my company. Plus, > I need some for GigE testing here at work. Now that we're all one big > happy family I should be able to transfer a few over here in the next > month or so. They won't make it in time for 3.2, but I hope to have > something working for 3.3. Well, you've signed yourself up. Looks like we need not persue this any further. If you've a mind to communicate your intentions through the front channels that were mentioned in other email I'm sure it would eliminate a bit of unneeded tail-chasing. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 30 7:21: 1 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id AD57214F45 for ; Fri, 30 Apr 1999 07:20:42 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA14634; Fri, 30 Apr 1999 11:25:52 +0200 From: Luigi Rizzo Message-Id: <199904300925.LAA14634@labinfo.iet.unipi.it> Subject: Re: possible bug in udp_usrreq ? To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Fri, 30 Apr 1999 11:25:52 +0200 (MET DST) Cc: net@freebsd.org In-Reply-To: <199904300918.LAA14603@labinfo.iet.unipi.it> from "Luigi Rizzo" at Apr 30, 99 11:18:35 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2385 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Whoops... i correct myself: the bug appears to be also in the code in the Stevens book, the reference figure for the multicast case is 23.26 (I am Bcc-ing Richard just in case he knows already...) and maybe the fix is slightly different than the one i propose, something like m->m_len -= iphdrlen + sizeof (struct udphdr) ; m->m_pkthdr.len -= iphdrlen + sizeof (struct udphdr) ; m->m_data += iphdrlen + sizeof (struct udphdr) ; because we can't (probably) touch iphdrlen since it is already incremented in the unicast section (unless they are mutually exclusive). cheers luigi > Hi, > > i just noticed a possible bug in udp_usrreq.c:udp_input() > > When demuxing datagrams to udp socket, near line 199 of the file, > there is the following section of code to skip the ip and udp > headers: > > /* > * Construct sockaddr format source address. > */ > udp_in.sin_port = uh->uh_sport; > udp_in.sin_addr = ip->ip_src; > --> m->m_len -= sizeof (struct udpiphdr); > --> m->m_data += sizeof (struct udpiphdr); > > note, there is no update to m->m_pkthdr.len such as > > m->m_pkthdr.len -= sizeof (struct udpiphdr); > > which in my opinion should be there, as it is instead done in the > Stevens TCPIP/Ill.vol.2 pg 775 (fig.23.25) and also in the section > of code related to unicast datagrams near line 313: > > iphlen += sizeof(struct udphdr); > m->m_len -= iphlen; > m->m_pkthdr.len -= iphlen; > m->m_data += iphlen; > > Actually, looking at the differences, the multicast section of the > code looks really broken and unable to handle ip options. It should > be exactly the same as in the unicast case. > > Just for curiosity, i cheched in the CVS tree and all revisions of > udp_input() seems to have the same problem. Even my old 1.1.5 > machine also shows the same bug, so i wonder when the problem > came out, maybe someone with access to older Berkeley sources can > see when that happened ? > > cheers > luigi > -----------------------------------+------------------------------------- > Luigi RIZZO . > EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione > HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa > TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) > -----------------------------------+------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 30 7:21:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 698A7152A7; Fri, 30 Apr 1999 07:20:42 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA14603; Fri, 30 Apr 1999 11:18:55 +0200 From: Luigi Rizzo Message-Id: <199904300918.LAA14603@labinfo.iet.unipi.it> Subject: possible bug in udp_usrreq ? To: net@freebsd.org Date: Fri, 30 Apr 1999 11:18:54 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1691 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i just noticed a possible bug in udp_usrreq.c:udp_input() When demuxing datagrams to udp socket, near line 199 of the file, there is the following section of code to skip the ip and udp headers: /* * Construct sockaddr format source address. */ udp_in.sin_port = uh->uh_sport; udp_in.sin_addr = ip->ip_src; --> m->m_len -= sizeof (struct udpiphdr); --> m->m_data += sizeof (struct udpiphdr); note, there is no update to m->m_pkthdr.len such as m->m_pkthdr.len -= sizeof (struct udpiphdr); which in my opinion should be there, as it is instead done in the Stevens TCPIP/Ill.vol.2 pg 775 (fig.23.25) and also in the section of code related to unicast datagrams near line 313: iphlen += sizeof(struct udphdr); m->m_len -= iphlen; m->m_pkthdr.len -= iphlen; m->m_data += iphlen; Actually, looking at the differences, the multicast section of the code looks really broken and unable to handle ip options. It should be exactly the same as in the unicast case. Just for curiosity, i cheched in the CVS tree and all revisions of udp_input() seems to have the same problem. Even my old 1.1.5 machine also shows the same bug, so i wonder when the problem came out, maybe someone with access to older Berkeley sources can see when that happened ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Apr 30 16:27:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from qatar.net.qa (qatar.net.qa [194.133.33.11]) by hub.freebsd.org (Postfix) with ESMTP id E3ED314C2E; Fri, 30 Apr 1999 16:27:10 -0700 (PDT) (envelope-from sodah@qatar.net.qa) Received: from qatar.net.qa (dieh.qatar.net.qa [194.133.37.108]) by qatar.net.qa (8.8.8/Internet-Qatar) with ESMTP id CAA09695; Sat, 1 May 1999 02:25:34 +0300 (GMT) Message-ID: <372A3BF0.B46F1607@qatar.net.qa> Date: Sat, 01 May 1999 02:25:36 +0300 From: Fadi Sodah X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isp@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Best firewall configuration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings What is the best firewall configuration to make smurf and ICMPs attack useless ? I'm runing an IRC server and would like to protect it as much as I can from all possible attacks. My ISP is offering a service, which will allow me to create any type of Packet Filtering policy I require for my aloccated server. The Firewall "Officers" sit between my server and the ISP backbone network. These Officers have full packet filtering capability and can filter on any protocol or IP address. My ISP asked me to tell them what exactly do I need and they gave me this example:- "List the IP Addresses to be configured for Packet Filtering Services and indicate the Policy Line for each. You may have multiple policy lines per IP Address. Attach a separate piece of paper if necessary." FROM: TO: Allow or Deny IP Address or Block IP Address or Block Port or Application Example Allow Any 206.171.12.100 ICMP Example Deny Any 206.171.12.32/27 ICMP Thanks in advance -Pons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat May 1 9:46:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from odin.siol.net (odin.siol.net [193.189.160.10]) by hub.freebsd.org (Postfix) with ESMTP id 122D4151D2 for ; Sat, 1 May 1999 09:46:38 -0700 (PDT) (envelope-from tomaz.borstnar@over.net) Received: from hang ([193.189.191.242]) by odin.siol.net (Post.Office MTA v3.5.3 release 223 ID# 620-58654U60000L60000S0V35) with ESMTP id net for ; Sat, 1 May 1999 18:46:36 +0200 Message-Id: <4.2.0.37.19990501172504.0180b050@193.189.189.100> X-Sender: tmail@193.189.189.100 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.37 (Beta) Date: Sat, 01 May 1999 17:30:02 +0200 To: freebsd-net@FreeBSD.ORG From: Tomaz Borstnar Subject: Re: Replacing Exchange Server In-Reply-To: <3726395A.2E61980A@softweyr.com> References: <6365787828FBD211A35100805F31EA72@SCHNEIDER.COM> 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 At 12:25 AM 4/28/99 , Wes Peters wrote the following message: >For mail transport, use Sendmail. It *is* the standard for Internet email. >It is also flexible and well known, and the most secure transport because Well, de facto standard, but it didn't (doesn't?) always obey standards and maintenance can be problematic. Several people including me have good experience with Zmailer - it is fast, easy to maintain, open-source, etc - and best of all - you don't need to rush to upgrade as was the reason with sendmail usually - mostly because of security concerns, but anyway. Many still run old versions of Zmailer, because they go by the principle "don't fix it if it ain't broken'. Anyway, http://www.zmailer.org is site with more info. Tomaz ---- Tomaz Borstnar "Love is the answer to the final question you ask" - Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun May 2 2:37:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from enaila.nidlink.com (enaila.nidlink.com [216.18.128.8]) by hub.freebsd.org (Postfix) with ESMTP id E14751522C for ; Sun, 2 May 1999 02:37:38 -0700 (PDT) (envelope-from sworkman@nidlink.com) Received: from hal (tnt132-99.nidlink.com [216.18.132.99]) by enaila.nidlink.com (8.9.0/8.9.0) with SMTP id CAA19842 for ; Sun, 2 May 1999 02:37:37 -0700 (PDT) Message-ID: <001501be947f$eab94380$0100a8c0@hal> From: "Shawn Workman" To: Subject: BOOTP Date: Sun, 2 May 1999 02:41:11 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01BE9445.3D96F470" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0012_01BE9445.3D96F470 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have an AMD K6 233 running FreeBSD 3.1 Stable and a DEC Alpha Multia = (don't Laugh). I am looking into booting the Alpha using BOOTP off of = my i386 box. Is this possible? Would I need to have the Alpha version of FreeBSD on my i386 machine? Any help here would be greatly appreciated... ------=_NextPart_000_0012_01BE9445.3D96F470 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have an AMD K6 233 running FreeBSD = 3.1 Stable=20 and a  DEC Alpha Multia (don't Laugh).  I am looking into = booting the=20 Alpha using BOOTP off of my i386 box.
 
Is this possible?
 
Would I need to have the Alpha = version of=20 FreeBSD on my i386 machine?
 
Any help here would be greatly=20 appreciated...
 
------=_NextPart_000_0012_01BE9445.3D96F470-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 0: 4:32 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 70A101500C for ; Mon, 3 May 1999 00:04:26 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id JAA00791 for ; Mon, 3 May 1999 09:04:21 +0200 (CEST) Received: from tu (t4o68p87.telia.com [62.20.139.207]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id JAA28888 for ; Mon, 3 May 1999 09:04:20 +0200 (CEST) Received: by localhost with Microsoft MAPI; Mon, 3 May 1999 09:03:26 +0200 Message-ID: <01BE9543.CE488840.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'freebsd-net@freebsd.org'" Subject: routing over Inet with FreeBSD 3.1R/S Date: Mon, 3 May 1999 09:03:16 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 have a question about routing "homenets" via Internet, here comes a description of my 'thought' out configuration. [C1:1-o] <---> [i-C1-o] <--Internet--> [o-C2-i] <---> [o-C2:1] C1 and C2 are routers/firewalls on completely different geographic sites, C1:1 and C2:1 simulates workstations within the buildings behind the firewall. -o Outside interface -i Inside interface IPs --- C1:1-o 192.168.1.100 C1-i 192.168.1.1 C1-o 36.100.100.1 (public IP) C2-o 37.100.100.1 (public IP) C2-i 192.168.10.1 C2:1-o 192.168.10.100 With these routing tables will a packet from C1:1 be able to use for example telnet 192.168.10.100 to address the computer C2:1 directly, as in will the packet be routed through the net correctly? C1:1 ---- default gateway 192.168.1.1 C1 -- 192.168.10.0/24 ---> 37.100.100.1 (C2-o) default gateway [ISP supplied] C2 -- 192.168.1.0/24 ---> 36.100.100.1 (C1-o) default gateway [ISP supplied] C2:1 ---- default gateway 192.168.10.1 Will this work? I can't test it right now, but I need to know if it will work prior to setting up the network. Or will a package like SKIP allow me to do such a thing? All the help you can give me on this one is much appriciated. Regards, / Thomas Uhrfelt ... Now hooked on FreeBSD ... Datortekniker PlymoVent AB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 8:49:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 7FECA151B2 for ; Mon, 3 May 1999 08:49:42 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA01241; Mon, 3 May 1999 09:49:32 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <372DC58B.2D8604B5@softweyr.com> Date: Mon, 03 May 1999 09:49:31 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "thomas.uhrfelt@plymovent.se" Cc: "'freebsd-net@freebsd.org'" Subject: Re: routing over Inet with FreeBSD 3.1R/S References: <01BE9543.CE488840.thomas.uhrfelt@plymovent.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Uhrfelt wrote: > > I have a question about routing "homenets" via Internet, here comes > a description of my 'thought' out configuration. > > [C1:1-o] <---> [i-C1-o] <--Internet--> [o-C2-i] <---> [o-C2:1] > > C1 and C2 are routers/firewalls on completely different geographic > sites, C1:1 and C2:1 simulates workstations within the buildings > behind the firewall. > > -o Outside interface > -i Inside interface > > IPs > --- > C1:1-o 192.168.1.100 > C1-i 192.168.1.1 > C1-o 36.100.100.1 (public IP) > C2-o 37.100.100.1 (public IP) > C2-i 192.168.10.1 > C2:1-o 192.168.10.100 > > With these routing tables will a packet from C1:1 be able to use for > example > telnet 192.168.10.100 to address the computer C2:1 directly, as in > will the packet be routed through the net correctly? No, you're not allowed to place 192.168.x.x addresses on the public internet, that's why they're called PRIVATE addresses. If you make your routers do Network Address Translation you can accomplish this, depending on the size of the two private networks. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 17: 6:52 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.snowcrest.net (mail.snowcrest.net [216.102.43.227]) by hub.freebsd.org (Postfix) with ESMTP id 2F82D14F7B for ; Mon, 3 May 1999 17:06:50 -0700 (PDT) (envelope-from djewett@snowcrest.net) Received: from ws2600 (stkfrA048.snowcrest.net [209.78.172.48]) by mail.snowcrest.net (8.9.0/8.9.0) with SMTP id RAA21731 for ; Mon, 3 May 1999 17:06:48 -0700 (PDT) Message-ID: <000a01be95c1$9d20c5b0$30ac4ed1@ws2600> From: "Derek Jewett" To: Subject: Large Scale Nat Date: Mon, 3 May 1999 17:03:59 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone out there doing static NAT under FreeBSD 3.1 in large scale? We have a firewall running NATd doing some static NAT to a number of users. I would like to crank that number up to some 350 users needed NAT translations static assigned at the firewall. If anyone is doing this what type of load does it pose, what size machine is needed..? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 17:10:10 1999 Delivered-To: freebsd-net@freebsd.org Received: from bladerunner.skynetweb.com (bladerunner.skynetweb.com [208.239.240.41]) by hub.freebsd.org (Postfix) with ESMTP id 1ECFE154A3 for ; Mon, 3 May 1999 17:10:08 -0700 (PDT) (envelope-from pryker@skynetweb.com) Received: from skynetweb.com (host80.skynetweb.com [208.231.1.80] (may be forged)) by bladerunner.skynetweb.com (8.8.8/8.8.8) with ESMTP id UAA28060 for ; Mon, 3 May 1999 20:10:07 -0400 (EDT) (envelope-from pryker@skynetweb.com) Message-ID: <372DF279.89628127@skynetweb.com> Date: Mon, 03 May 1999 20:01:13 +0100 From: Phillip Ryker Organization: SkyNetWEB Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: IPsec... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org List, does FreeBSD have IPsec built into the kernel code?? If not, are there any plans to implement this?? Thank you -- Phillip Ryker ------------------------------ | SkyNetWEB Ltd. | | 1301 S. Baylis Street | | Baltimore Maryland 21224 | | Phone: 410.563.6384 | | Fax: 410.563.5457 | ------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 18:42:51 1999 Delivered-To: freebsd-net@freebsd.org Received: from mag.ipc.ru (c2-ppp16.ipc.ru [195.133.114.43]) by hub.freebsd.org (Postfix) with ESMTP id EFFDA15758 for ; Mon, 3 May 1999 18:42:44 -0700 (PDT) (envelope-from mag@ipc.ru) Received: from ipc.ru (localhost [127.0.0.1]) by mag.ipc.ru (8.9.2/8.9.2) with ESMTP id FAA01000 for ; Tue, 4 May 1999 05:44:13 +0400 (MSD) (envelope-from mag@ipc.ru) Message-ID: <372E50EC.546790AA@ipc.ru> Date: Tue, 04 May 1999 05:44:13 +0400 From: "Alexey G. Misurenko" Reply-To: mag@ipc.ru X-Mailer: Mozilla 4.5 [ru] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: GRE Tunnel (rfc1701 & rfc1702) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellow! Can anody body try tu use or may be use GRE Tunnel? Plesase don't proposed use nos-tun utilities - they don't work. If bee corectly - they work but not with GRE tunnel type I test they (nos-tun) with cisco & baynetwork. And ok result I recieve only with cisco with tunnel parameters nos. But with bay networks & cisco with gre tunnel type I can't resiave posetive result... May bee somebody porting gre device from NetBSD to FreeBSD? Lats me know about with! WBR, Alexey G Misurenko p.s. Sorry for my badly english -- ************************************************* * MAG-RIPE mag@ipc.ru http://www.ipc.ru/ * * SysAdmin of IP Comminication +7 095 737 6683 * ************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 18:52:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from mag.ipc.ru (c2-ppp16.ipc.ru [195.133.114.43]) by hub.freebsd.org (Postfix) with ESMTP id 2F0F4154F5; Mon, 3 May 1999 18:52:16 -0700 (PDT) (envelope-from mag@ipc.ru) Received: from ipc.ru (localhost [127.0.0.1]) by mag.ipc.ru (8.9.2/8.9.2) with ESMTP id FAA01012; Tue, 4 May 1999 05:53:45 +0400 (MSD) (envelope-from mag@ipc.ru) Message-ID: <372E5326.74CEDF33@ipc.ru> Date: Tue, 04 May 1999 05:53:42 +0400 From: "Alexey G. Misurenko" Reply-To: mag@ipc.ru X-Mailer: Mozilla 4.5 [ru] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-isp@freebsd.org Subject: problem with natd Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok problem is I have network inetface lnc3 with 2 ip address (A.A.A.A & B.B.B.B) I want next think: If destenation address is in X.X.X.X/N then divert them to natd else pass throuht lnc3 witout modification I try to use next command construction % natd -a B.B.B.B % ipfw flush % ipfw add 10 divert natd all from any to X.X.X.X/N % ipfw add 11 pass all from any to any And %( This is don't work - I can't see any host in X.X.X.X/N WARN: All needing options on /etc/services & kernel is up because natd work when ipfw rules number 10 is add 10 divert natd all from any to any. WBR, Alexey G Misurenko -- ************************************************* * MAG-RIPE mag@ipc.ru http://www.ipc.ru/ * * SysAdmin of IP Comminication +7 095 737 6683 * ************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 19: 2:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from satty.npi.msu.su (satty.npi.msu.su [158.250.20.4]) by hub.freebsd.org (Postfix) with ESMTP id A53BA156D5 for ; Mon, 3 May 1999 19:02:53 -0700 (PDT) (envelope-from dima@zippy.machaon.ru) Received: from zippy.machaon.ru (ws-134.machaon.ru [195.230.75.134] (may be forged)) by satty.npi.msu.su (8.9.1a/8.9.1) with ESMTP id GAA24285; Tue, 4 May 1999 06:02:49 +0400 (MSD) Date: Tue, 4 May 1999 06:02:48 +0400 (MSD) From: Dmitry Khrustalev To: "Alexey G. Misurenko" Cc: freebsd-net@FreeBSD.ORG Subject: Re: GRE Tunnel (rfc1701 & rfc1702) In-Reply-To: <372E50EC.546790AA@ipc.ru> 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 try http://www.machaon.ru/~dima/gre.tar.gz. Have fun. -Dima On Tue, 4 May 1999, Alexey G. Misurenko wrote: > Hellow! > > Can anody body try tu use or may be use GRE Tunnel? > > Plesase don't proposed use nos-tun utilities - they > don't work. If bee corectly - they work but not > with GRE tunnel type > > I test they (nos-tun) with cisco & baynetwork. > And ok result I recieve only with cisco with > tunnel parameters nos. But with bay networks & cisco > with gre tunnel type I can't resiave posetive result... > > > May bee somebody porting gre device from NetBSD to FreeBSD? > Lats me know about with! > > WBR, Alexey G Misurenko > p.s. Sorry for my badly english > > > -- > ************************************************* > * MAG-RIPE mag@ipc.ru http://www.ipc.ru/ * > * SysAdmin of IP Comminication +7 095 737 6683 * > ************************************************* > > > > > > 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 Mon May 3 19:22:42 1999 Delivered-To: freebsd-net@freebsd.org Received: from pcslink.com (pcslink.com [206.43.160.1]) by hub.freebsd.org (Postfix) with ESMTP id C8BA714D94; Mon, 3 May 1999 19:22:26 -0700 (PDT) (envelope-from ryan@pcslink.com) Received: (from ryan@localhost) by pcslink.com (8.8.7/8.6.12) id TAA22536; Mon, 3 May 1999 19:22:08 -0700 (MST) From: Ryan Mooney Message-Id: <199905040222.TAA22536@pcslink.com> Subject: Re: problem with natd In-Reply-To: <372E5326.74CEDF33@ipc.ru> from "Alexey G. Misurenko" at "May 4, 99 05:53:42 am" To: mag@ipc.ru Date: Mon, 3 May 1999 19:22:08 -0700 (MST) Cc: freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Ok problem is > I have network inetface lnc3 with 2 ip address (A.A.A.A & B.B.B.B) > I want next think: > If destenation address is in X.X.X.X/N > then divert them to natd > else pass throuht lnc3 witout modification > > I try to use next command construction > > % natd -a B.B.B.B > % ipfw flush > % ipfw add 10 divert natd all from any to X.X.X.X/N via lnc3 % ipfw add 10 divert natd all from X.X.X.X/N to any via lnc3 The via is optional, but clarifies things (at least for me) that traffic only gets nat'd on traversing that interface. > % ipfw add 11 pass all from any to any > > And %( This is don't work - I can't see any host in X.X.X.X/N Dumb question, but you CAN see X.X.X.X/N from the BSD box w/o nat right? >-=-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-=-< Ryan Mooney Phone (602)265-9188 PCSLink ryan@pcslink.com Internet Services NT is an excellent choice for managers who need to show that they used up their fiscal year budget for hardware/software expenditures. <-=-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-=-> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon May 3 23:18:38 1999 Delivered-To: freebsd-net@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id 79AC1150C7 for ; Mon, 3 May 1999 23:18:35 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by maile.telia.com (8.8.5/8.8.8) with ESMTP id IAA04568 for ; Tue, 4 May 1999 08:18:34 +0200 (CEST) Received: from tu (t4o68p15.telia.com [62.20.139.135]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id IAA09352 for ; Tue, 4 May 1999 08:18:33 +0200 (CEST) Received: by localhost with Microsoft MAPI; Tue, 4 May 1999 08:17:35 +0200 Message-ID: <01BE9606.90D23CE0.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'freebsd-net@freebsd.org'" Subject: SV: routing over Inet with FreeBSD 3.1R/S Date: Tue, 4 May 1999 08:17:25 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 > Thomas Uhrfelt wrote: > > > > I have a question about routing "homenets" via Internet, here comes > > a description of my 'thought' out configuration. > > > > [C1:1-o] <---> [i-C1-o] <--Internet--> [o-C2-i] <---> [o-C2:1] > > > > C1 and C2 are routers/firewalls on completely different geographic > > sites, C1:1 and C2:1 simulates workstations within the buildings > > behind the firewall. > > > > -o Outside interface > > -i Inside interface > > > > IPs > > --- > > C1:1-o 192.168.1.100 > > C1-i 192.168.1.1 > > C1-o 36.100.100.1 (public IP) > > C2-o 37.100.100.1 (public IP) > > C2-i 192.168.10.1 > > C2:1-o 192.168.10.100 > > > > With these routing tables will a packet from C1:1 be able to use > > for > > example > > telnet 192.168.10.100 to address the computer C2:1 directly, as in > > will the packet be routed through the net correctly? > > No, you're not allowed to place 192.168.x.x addresses on the public > internet, that's why they're called PRIVATE addresses. If you make > your routers do Network Address Translation you can accomplish > this, depending on the size of the two private networks. I am performing NAT, but my problem is that I need to be able to address some of the "inside" computers on the C2 net directly without having a public IP, how can I accomplish that? I do know that 192 addresses are private, but since I route them directly to my other private network that shouldnt pose a problem or? / Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue May 4 1:31:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 2BAF514DC3 for ; Tue, 4 May 1999 01:31:42 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id SAA01488; Tue, 4 May 1999 18:01:41 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA27257; Tue, 4 May 1999 18:02:12 +0930 Date: Tue, 4 May 1999 18:02:12 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Phillip Ryker Cc: freebsd-net@freebsd.org Subject: Re: IPsec... In-Reply-To: <372DF279.89628127@skynetweb.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 Mon, 3 May 1999, Phillip Ryker wrote: > List, > > does FreeBSD have IPsec built into the kernel code?? If not, are there > any plans to implement this?? No and yes. There are several groups working on IPSEC/IPv6 code, who recently decided to get together and produce a single stack. Once this is done FreeBSD intends to adopt it. In the meantime, you can check out www.kame.net who have releases for 2.something, 3.0-REL and 3.1-REL, last I checked. With a bit of hand patching you could probably pretty easily bring that up to 3.1-STABLE (there haven't been that many network-related changes since 3.1, AFAIK). Kris ----- "That suit's sharper than a page of Oscar Wilde witticisms that's been rolled up into a point, sprinkled with lemon juice and jabbed into someone's eye" "Wow, that's sharp!" - Ace Rimmer and the Cat, _Red Dwarf_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue May 4 1:49: 5 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 4D459154F7; Tue, 4 May 1999 01:48:54 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id JAA18524; Tue, 4 May 1999 09:48:48 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00653; Tue, 4 May 1999 08:38:05 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905040738.IAA00653@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: mag@ipc.ru Cc: freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: problem with natd In-reply-to: Your message of "Tue, 04 May 1999 05:53:42 +0400." <372E5326.74CEDF33@ipc.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 May 1999 08:38:05 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > % natd -a B.B.B.B > % ipfw flush > % ipfw add 10 divert natd all from any to X.X.X.X/N > % ipfw add 11 pass all from any to any You must NAT both ways... you're missing % ipfw add 9 divert natd all from X.X.X.X/N to any -- 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 Tue May 4 3:14:38 1999 Delivered-To: freebsd-net@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.132]) by hub.freebsd.org (Postfix) with ESMTP id 25D2014D54 for ; Tue, 4 May 1999 03:14:35 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id FAA11426; Tue, 4 May 1999 05:14:19 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Tue, 4 May 1999 05:14:19 -0500 (CDT) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: Thomas Uhrfelt Cc: "'freebsd-net@freebsd.org'" Subject: Re: SV: routing over Inet with FreeBSD 3.1R/S In-Reply-To: <01BE9606.90D23CE0.thomas.uhrfelt@plymovent.se> 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 Tue, 4 May 1999, Thomas Uhrfelt wrote: > > Thomas Uhrfelt wrote: > > > > > > I have a question about routing "homenets" via Internet, here comes > > > a description of my 'thought' out configuration. > > > > > > [C1:1-o] <---> [i-C1-o] <--Internet--> [o-C2-i] <---> [o-C2:1] > > > > > > C1 and C2 are routers/firewalls on completely different geographic > > > sites, C1:1 and C2:1 simulates workstations within the buildings > > > behind the firewall. > > > > > > -o Outside interface > > > -i Inside interface > > > > > > IPs > > > --- > > > C1:1-o 192.168.1.100 > > > C1-i 192.168.1.1 > > > C1-o 36.100.100.1 (public IP) > > > C2-o 37.100.100.1 (public IP) > > > C2-i 192.168.10.1 > > > C2:1-o 192.168.10.100 > > > > > > With these routing tables will a packet from C1:1 be able to use > > > for > > > example > > > telnet 192.168.10.100 to address the computer C2:1 directly, as in > > > will the packet be routed through the net correctly? > > > > No, you're not allowed to place 192.168.x.x addresses on the public > > internet, that's why they're called PRIVATE addresses. If you make > > your routers do Network Address Translation you can accomplish > > this, depending on the size of the two private networks. > > I am performing NAT, but my problem is that I need to be able to > address some of the "inside" computers on the C2 net directly without > having a public IP, how can I accomplish that? I do know that 192 > addresses are private, but since I route them directly to my other > private network that shouldnt pose a problem or? Encapsulate the private network packets with a tunnel between the firewalls (or to designated machines behind the firewall). That will make it appear that the global internet is bypassed and the firewalls are only one hop apart. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue May 4 5:16:26 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id AC29D1511C for ; Tue, 4 May 1999 05:16:10 -0700 (PDT) (envelope-from thomas.uhrfelt@plymovent.se) Received: from d1o68.telia.com (root@d1o68.telia.com [62.20.138.241]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id OAA01706; Tue, 4 May 1999 14:16:08 +0200 (CEST) Received: from tu (t1o68p103.telia.com [62.20.138.103]) by d1o68.telia.com (8.8.8/8.8.5) with SMTP id OAA28069; Tue, 4 May 1999 14:16:07 +0200 (CEST) Received: by localhost with Microsoft MAPI; Tue, 4 May 1999 14:15:09 +0200 Message-ID: <01BE9638.844DD1A0.thomas.uhrfelt@plymovent.se> From: Thomas Uhrfelt Reply-To: "thomas.uhrfelt@plymovent.se" To: "'rkw@dataplex.net'" Cc: "'freebsd-net@freebsd.org'" Subject: SV: SV: routing over Inet with FreeBSD 3.1R/S Date: Tue, 4 May 1999 14:11:51 +0200 Organization: Plymovent AB X-Mailer: Microsoft Internet-e-post/MAPI - 8.0.0.4211 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 am performing NAT, but my problem is that I need to be able to > > address some of the "inside" computers on the C2 net directly > > without > > having a public IP, how can I accomplish that? I do know that 192 > > addresses are private, but since I route them directly to my other > > private network that shouldnt pose a problem or? > > Encapsulate the private network packets with a tunnel between the > firewalls (or to designated machines behind the firewall). > > That will make it appear that the global internet is bypassed and the > firewalls are only one hop apart. I am currently investigating just that, what programs will do the trick for me? SKIP? / Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue May 4 12:20:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from mta1.mail.telepac.pt (mail1.telepac.pt [194.65.3.53]) by hub.freebsd.org (Postfix) with ESMTP id 185C31505D for ; Tue, 4 May 1999 12:20:40 -0700 (PDT) (envelope-from jpedras@mail.telepac.pt) Received: from manecao.tafkap.priv ([194.65.203.5]) by mta1.mail.telepac.pt (InterMail v03.02.07 118-124-101) with ESMTP id <19990504192041.DSEC1242@manecao.tafkap.priv> for ; Tue, 4 May 1999 20:20:41 +0100 Content-Length: 975 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 04 May 1999 20:20:36 +0100 (BST) From: Joao Pedras To: freebsd-net@freebsd.org Subject: etherboot & fbsd Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all! I have been trying to boot a 166 P5 from my 3.1-stable box. I am trying to acomplish this using etherboot (FreeBSD patched of course). I tried with a 3c905B and a Digital 21140 card with no success in either case. I tried with bootpd and now with dhcpd from isc. I am trying this with an image of the rom on diskette, like is told in etherboot documentation. From watching the hub, seems to me that the server doesn't "listen" the request. No answer seems to "come out". If someone is using etherboot with FreeBSD plz say something about your configuration. Plz don't mind to ask anything. Joao --------------------------------------------------- Sent using XFMail on 04-May-99 at 20:13:42 This message was sent by XFMail proudly powered by FreeBSD -> http://www.freebsd.org <- "The Power to Serve" --------------------------------------------------- The gods gave man fire and he invented fire engines. They gave him love and he invented marriage. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue May 4 14:16:15 1999 Delivered-To: freebsd-net@freebsd.org Received: from mattg-freebsd.aiinet.com (ai51225.aiinet.com [206.103.251.225]) by hub.freebsd.org (Postfix) with ESMTP id 037A415068; Tue, 4 May 1999 14:16:11 -0700 (PDT) (envelope-from mgessner.freebsd@flashmail.com) Received: from flashmail.com (localhost.aiinet.com [127.0.0.1]) by mattg-freebsd.aiinet.com (8.9.2/8.9.2) with ESMTP id RAA00732; Tue, 4 May 1999 17:16:34 GMT (envelope-from mgessner.freebsd@flashmail.com) Message-ID: <372F2B72.6B44D5F7@flashmail.com> Date: Tue, 04 May 1999 17:16:34 +0000 From: Matthew Gessner X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Question about LOTS of outgoing TCP connections with data Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I apologize immediately for the cross post, but I don't know who frequents which lists. At least I avoided hackers :-) I have a program that creates X tcp connections to a given host (it's a proprietary network interface card... X.25, TCP/IP, etc). Now, I want to be able to test this sucker from FreeBSD. When I start all 400 connections, 3.1-RELEASE REBOOTS. Hmm... kind of nasty behaviour. I'm running on a Pentium 166MHz with 32MB of RAM and a 96MB swap space. PLEASE PLEASE PLEASE can someone tell me if I have a kernel configuration problem with this? Or is there something more sinister going on? I KNOW FreeBSD can EASILY handle such things, a la www.cdrom.com which hosts a lot more data throughput than this. Thanks a bunch in advance. HELLO to Eivind Eklund if he reads this! ;-) Matt Gessner, mgessner.freebsd@flashmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 2:44:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 21D2014FFA; Wed, 5 May 1999 02:44:03 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id LAA29760; Wed, 5 May 1999 11:43:52 +0200 (CEST) Date: Wed, 05 May 1999 11:43:08 +0200 From: Stefan Bethke To: Matthew Gessner Cc: freebsd-net@FreeBSD.ORG Subject: Re: Question about LOTS of outgoing TCP connections with data Message-ID: <312971.3134893388@d225.promo.de> In-Reply-To: <372F2B72.6B44D5F7@flashmail.com> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ moved to -net ] Matthew Gessner wrote: > I have a program that creates X tcp connections to a given host (it's a > proprietary network interface card... X.25, TCP/IP, etc). > > Now, I want to be able to test this sucker from FreeBSD. When I start > all 400 connections, 3.1-RELEASE REBOOTS. > > Hmm... kind of nasty behaviour. > > I'm running on a Pentium 166MHz with 32MB of RAM and a 96MB swap space. Does is simply reboot, or does it panic? In any case, try increasing NMBCLUSTERS (or MAXUSERS). Try 200 connections, and look at the used allocations with netstat -m, this should give you an idea whether this is your problem, and how much you should increase NBMCLUSTERS. Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@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 May 5 7: 3:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from lance.castle.net (lance.castle.net [199.173.5.4]) by hub.freebsd.org (Postfix) with SMTP id 720A61593B for ; Wed, 5 May 1999 07:03:33 -0700 (PDT) (envelope-from gkaplan@castle.net) Received: (qmail 2097 invoked from network); 5 May 1999 14:00:35 -0000 Received: from parsip-usr-20.intac.com (HELO castle.net) (199.173.8.89) by lance.castle.net with SMTP; 5 May 1999 14:00:35 -0000 Message-ID: <37304F9C.C71D8A87@castle.net> Date: Wed, 05 May 1999 10:03:08 -0400 From: gkaplan X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Net Subject: modem initialization usr sportster 56k Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a pnp 56k (X2) internal modem that I am able to use to complete a serial ppp connection to my isp without problems. When trying to complete the isp connection under freebsd 2.2.8 the connection fails at some almost arbitrary point in the dialog. I have gotten as far as the isp presenting the user menu under telnet; but results are not predictable. After view appropriate news groups and other sources I find the suggestion that there is a deficiency in the modem hardware or software logic that can be overcome by using an appropriate modem initialization string . WHAT would that string be . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 10:38:21 1999 Delivered-To: freebsd-net@freebsd.org Received: from poboxer.pobox.com (mail.kdsamerica.com [208.149.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 30B2114D18 for ; Wed, 5 May 1999 10:38:18 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id MAA45442; Wed, 5 May 1999 12:38:17 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 5 May 1999 12:38:16 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: net@freebsd.org Subject: ipfw and tulip X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14128.33126.285857.312148@avalon.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I observe that using ipfw 'pipe' delays with a tulip card terminates the kernel. Are there specific 100bTX cards with which this is known to work reliably? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 10:49:59 1999 Delivered-To: freebsd-net@freebsd.org Received: from poboxer.pobox.com (mail.kdsamerica.com [208.149.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 01A5B14D18 for ; Wed, 5 May 1999 10:49:54 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id MAA45495; Wed, 5 May 1999 12:49:36 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 5 May 1999 12:49:36 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: luigi@labinfo.iet.unipi.it Cc: net@FreeBSD.ORG Subject: Re: ipfw and tulip References: <14128.33126.285857.312148@avalon.east> <199905051534.RAA29264@labinfo.iet.unipi.it> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14128.33844.572885.297129@avalon.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoth Luigi Rizzo on Wed, 5 May: : > I observe that using ipfw 'pipe' delays with a tulip card terminates : > the kernel. Are there specific 100bTX cards with which this is known : > to work reliably? : : we need more info on the os release you are using. Oops -- 4.0-current, up-to-date as of Monday. : There were some glitches in dummynet, which may or may not affect you : depending on whether you use BRIDGE, -current, and multiple routes out : of your net. RELENG_3 and RELENG_2_2 were in better shape. : : I think i fixed all known (to me) problems with yesterday's round : of commits. That's great. I'll report if it reproduces after a new cvsup/buildworld. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 10:50:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 6581D14D18 for ; Wed, 5 May 1999 10:50:40 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA29289; Wed, 5 May 1999 17:40:46 +0200 From: Luigi Rizzo Message-Id: <199905051540.RAA29289@labinfo.iet.unipi.it> Subject: Re: ipfw and tulip To: alk@pobox.com Date: Wed, 5 May 1999 17:40:46 +0200 (MET DST) Cc: net@FreeBSD.ORG In-Reply-To: <14128.33844.572885.297129@avalon.east> from "Anthony Kimball" at May 5, 99 12:49:17 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 529 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > : we need more info on the os release you are using. > > Oops -- 4.0-current, up-to-date as of Monday. yup -- known offender :) luigi > : There were some glitches in dummynet, which may or may not affect you > : depending on whether you use BRIDGE, -current, and multiple routes out > : of your net. RELENG_3 and RELENG_2_2 were in better shape. > : > : I think i fixed all known (to me) problems with yesterday's round > : of commits. > > That's great. I'll report if it reproduces after a new > cvsup/buildworld. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 11:19:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 9BE591538F for ; Wed, 5 May 1999 11:19:15 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA29264; Wed, 5 May 1999 17:34:48 +0200 From: Luigi Rizzo Message-Id: <199905051534.RAA29264@labinfo.iet.unipi.it> Subject: Re: ipfw and tulip To: alk@pobox.com Date: Wed, 5 May 1999 17:34:48 +0200 (MET DST) Cc: net@FreeBSD.ORG In-Reply-To: <14128.33126.285857.312148@avalon.east> from "Anthony Kimball" at May 5, 99 12:37:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 975 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I observe that using ipfw 'pipe' delays with a tulip card terminates > the kernel. Are there specific 100bTX cards with which this is known > to work reliably? we need more info on the os release you are using. There were some glitches in dummynet, which may or may not affect you depending on whether you use BRIDGE, -current, and multiple routes out of your net. RELENG_3 and RELENG_2_2 were in better shape. I think i fixed all known (to me) problems with yesterday's round of commits. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 15:25:32 1999 Delivered-To: freebsd-net@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 7FBB5158B7 for ; Wed, 5 May 1999 15:25:24 -0700 (PDT) (envelope-from ian@apdata.com.au) Received: from apdata.com.au (localhost [127.0.0.1]) by rose.niw.com.au (Postfix) with ESMTP id 9A975A3203; Thu, 6 May 1999 07:55:18 +0930 (CST) Message-ID: <3730C54E.AD22B3CC@apdata.com.au> Date: Thu, 06 May 1999 07:55:18 +0930 From: Ian West Organization: Applied Data Control X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: gkaplan Cc: Net Subject: Re: modem initialization usr sportster 56k References: <37304F9C.C71D8A87@castle.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org gkaplan wrote: > > I have a pnp 56k (X2) internal modem that I am able to use to complete a > serial ppp connection to my isp without problems. > > When trying to complete the isp connection under freebsd 2.2.8 the > connection fails at some almost arbitrary point in the dialog. I have > gotten as far as the isp presenting the user menu under telnet; but > results are not predictable. After view appropriate news groups and > other sources I find the suggestion that there is a deficiency in the > modem hardware or software logic that can be overcome by using an > appropriate modem initialization string . WHAT would that string be . > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message I had a similar problem a while back and the problem turned out to be the default flow control setting. Try looking at at&f1 which I believe forces hardware flow control. Following is an extract from a backup of the script. # The following line, AT&F1 is important for the USR/3COM modem. # If it isn't there, the modem gets all uptight and breaks stuff. # ISPDIAL : "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT&F1 OK-AT-OK $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed May 5 15:38:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from fasterix.frmug.org (d155.paris-77.cybercable.fr [212.198.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 04B0715561 for ; Wed, 5 May 1999 15:38:16 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.9.3/pb-19990315) id AAA33484; Thu, 6 May 1999 00:37:49 +0200 (CEST) Message-ID: <19990506003741.A33423@fasterix.frmug.fr.net> Date: Thu, 6 May 1999 00:37:41 +0200 From: Pierre Beyssac To: Phillip Ryker , freebsd-net@FreeBSD.ORG Subject: Re: IPsec... References: <372DF279.89628127@skynetweb.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=ReaqsoxgOBHFXBhH X-Mailer: Mutt 0.92.8i In-Reply-To: <372DF279.89628127@skynetweb.com>; from Phillip Ryker on Mon, May 03, 1999 at 08:01:13PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii On Mon, May 03, 1999 at 08:01:13PM +0100, Phillip Ryker wrote: > does FreeBSD have IPsec built into the kernel code?? If not, are there > any plans to implement this?? If that's not a rethoric questions (i.e., if you want IPSEC now) and you only need tunnel-mode IPSEC (for a VPN for example), you might be interested by the following (attached) I posted a few days ago to freebsd-security. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=vpn Date: Fri, 30 Apr 1999 23:30:59 +0200 From: Pierre Beyssac To: freebsd-security@FreeBSD.ORG Subject: Re: VPN On Fri, Apr 30, 1999 at 08:36:59AM -0700, Jonathan M. Bresler wrote: > > Don't use Microsoft PPTP, see http://www.counterpane.com/. > the problem is not with PPTP itself, but rather microsoft's > inimitable style of implementing protocols. BTW, as there seems to be a lot of interest in VPNs currently, and I had a need for something that could run between my FreeBSD box and a Linux box, I've written a small usermode IPSEC-compliant tunnel when I became tired of the impressive number of non-compatible hacks based on PPP, ssh, TCP, PPTP, you name it, while IPSEC clearly will sweep all of this. It's more of a proof-of-concept code for the moment (only fixed keys: it lacks key negociation stuff), and it can't beat a kernel implementation for performance, but it's easier to install, easier to port to other systems (you only need some kind of a "tun" device), easier to debug, easier to add weird crypto algorithms, easier to export (the crypto is from the OpenSSL library), and last but not least easier to distribute as a package external to the core OS. I'm happily running it between several FreeBSD and Linux boxes to setup tunnels to friends through my cable modem. If anyone is interested, it can be found here. WARNING: it's really experimental and the documentation is lacking, don't even bother if you don't know how to setup a point to point link or how to add the tun device to your kernel. http://www.enst.fr/~beyssac/tunip.tar.gz -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org --ReaqsoxgOBHFXBhH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu May 6 11:38:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from valis.worldgate.com (valis.worldgate.com [198.161.84.2]) by hub.freebsd.org (Postfix) with ESMTP id D812814C8A for ; Thu, 6 May 1999 11:38:27 -0700 (PDT) (envelope-from skafte@gras-varg.worldgate.com) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by valis.worldgate.com (8.9.1a/8.9.1) with ESMTP id MAA24826; Thu, 6 May 1999 12:38:26 -0600 (MDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id MAA06031; Thu, 6 May 1999 12:38:24 -0600 (MDT) Date: Thu, 6 May 1999 12:38:24 -0600 From: Greg Skafte To: Joao Pedras Cc: freebsd-net@FreeBSD.ORG Subject: Re: etherboot & fbsd Message-ID: <19990506123823.B5203@gras-varg.worldgate.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Joao Pedras on Tue, May 04, 1999 at 08:20:36PM +0100 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just started working on this using intel etherexpress 100 cards. I've got to the point of booting the elf kernel but it is haning on mounting the nfsroot partion. so far I'm using only bootp and tftp, I haven't experimented with DCHP. http://ftp.freebsd.org/~fsmp/HomeAuto/diskless has good info, also http://www.iet.unipi.it/~luigi also has some stuff. Quoting Joao Pedras (jpedras@mail.telepac.pt) On Subject: etherboot & fbsd Date: Tue, May 04, 1999 at 08:20:36PM +0100 > Hello all! > > I have been trying to boot a 166 P5 from my 3.1-stable box. I am trying to > acomplish this using etherboot (FreeBSD patched of course). > > I tried with a 3c905B and a Digital 21140 card with no success in either case. > > I tried with bootpd and now with dhcpd from isc. > > I am trying this with an image of the rom on diskette, like is told in > etherboot documentation. > > >From watching the hub, seems to me that the server doesn't "listen" the > request. No answer seems to "come out". > > If someone is using etherboot with FreeBSD plz say something about your > configuration. > > Plz don't mind to ask anything. > > Joao > > --------------------------------------------------- > Sent using XFMail on 04-May-99 at 20:13:42 > This message was sent by XFMail > proudly powered by FreeBSD > -> http://www.freebsd.org <- "The Power to Serve" > --------------------------------------------------- > > The gods gave man fire and he invented fire engines. They gave him > love and he invented marriage. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- Email: skafte@worldgate.com Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu May 6 17: 7:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from twinlark.arctic.org (twinlark.arctic.org [204.107.140.52]) by hub.freebsd.org (Postfix) with SMTP id E388814BF4 for ; Thu, 6 May 1999 17:07:36 -0700 (PDT) (envelope-from dgaudet-list-freebsd-net@arctic.org) Received: (qmail 25576 invoked by uid 500); 7 May 1999 00:07:14 -0000 Date: Thu, 6 May 1999 17:07:14 -0700 (PDT) From: Dean Gaudet To: freebsd-net@FreeBSD.ORG Subject: cidr aliases Message-ID: X-Comment: Visit http://www.arctic.org/~dgaudet/legal for information regarding copyright and disclaimer. 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 an application which requires a godawfully large number of aliases on one box. The linear list used to handle this stuff in 2.2.x (and 3.1.x from what I can tell) just isn't cutting it. (16ms localnet ping times for some of the higher numbered aliases... bandwidth drops off from 8Mbyte/s down to 160kbyte/s due to the high cost of receiving packets...) We essentially allocate entire CIDR blocks to a single box. So naturally it'd be cool if we could just alias the entire CIDR block in one fell swoop... this would reduce the kernel structures down to the minimum. I hacked together the patch included below against 2.2.8, which seems to be a reasonable start. It's not clean... but I was wondering if someone else with more knowledge of the stack has a few moments to say "you're on crack, do it this way" or "you're heading the right way, here's a few tweaks". A better solution would actually set some bit on a per-alias basis to indicate if it is a CIDR-alias or a regular host-alias. But for now I'm happy if all aliases are CIDR-aliases... and I totally cheat by using the netmask to indicate what the CIDR block is. This patch works fine when accessed from other boxes -- I can set up TCP connections to any of the addresses in the CIDR block. But the localhost can't ping itself on any of the addresses. Dean --- ./net/if.c.orig Wed May 5 10:46:01 1999 +++ ./net/if.c Wed May 5 10:46:06 1999 @@ -186,6 +186,9 @@ equal(ifa->ifa_broadaddr, addr)) return (ifa); } + /* pretend that aliases consume their entire subnet */ + if ((ifa = ifa_ifwithnet(addr)) && (ifa->ifa_flags & IFA_ALIAS)) + return (ifa); return ((struct ifaddr *)0); } /* --- ./net/if.h.orig Mon Jul 6 22:24:08 1998 +++ ./net/if.h Wed May 5 10:54:16 1999 @@ -321,6 +321,7 @@ }; #define IFA_ROUTE RTF_UP /* route installed */ +#define IFA_ALIAS 0x80 /* this is unused by RTF flags... */ /* * Message format for use in obtaining information about interfaces --- ./netinet/ip_input.c.orig Wed May 5 10:46:01 1999 +++ ./netinet/ip_input.c Wed May 5 10:46:06 1999 @@ -435,6 +435,16 @@ if (ip->ip_dst.s_addr == ia->ia_netbroadcast.s_addr) goto ours; } + /* if it's not the first address on the interface it + * is an alias -- in that case consider all addresses + * under the aliased netmask to be ours... that is, + * pretend an entire CIDR block is aliased to us. + */ + if (ia->ia_ifa.ifa_flags & IFA_ALIAS) { + if ((ntohl(ip->ip_dst.s_addr) & ia->ia_subnetmask) + == ia->ia_subnet) + goto ours; + } } if (IN_MULTICAST(ntohl(ip->ip_dst.s_addr))) { struct in_multi *inm; --- ./netinet/ip_icmp.c.orig Wed May 5 10:46:01 1999 +++ ./netinet/ip_icmp.c Wed May 5 10:55:22 1999 @@ -529,6 +529,10 @@ if (ia->ia_ifp && (ia->ia_ifp->if_flags & IFF_BROADCAST) && t.s_addr == satosin(&ia->ia_broadaddr)->sin_addr.s_addr) break; + if (ia->ia_ifa.ifa_flags & IFA_ALIAS) + if ((ntohl(ip->ip_dst.s_addr) & ia->ia_subnetmask) + == ia->ia_subnet) + break; } icmpdst.sin_addr = t; if ((ia == (struct in_ifaddr *)0) && m->m_pkthdr.rcvif) --- ./netinet/in.c.orig Wed May 5 10:47:02 1999 +++ ./netinet/in.c Wed May 5 10:52:57 1999 @@ -327,6 +327,7 @@ break; case SIOCAIFADDR: + ia->ia_ifa.ifa_flags |= IFA_ALIAS; maskIsNew = 0; hostIsNew = 1; error = 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri May 7 17:10:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id B64ED14E0B for ; Fri, 7 May 1999 17:10:25 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.3/8.9.2) id RAA69847 for freebsd-net@freebsd.org; Fri, 7 May 1999 17:10:24 -0700 (PDT) (envelope-from insane) Date: Fri, 7 May 1999 17:10:24 -0700 From: "Ron 'The InSaNe One' Rosson" To: freebsd-net@freebsd.org Subject: FreeBSD Box hooked up to @Home Message-ID: <19990507171024.A69647@lunatic.oneinsane.net> Reply-To: insane@oneinsane.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD lunatic.oneinsane.net 3.1-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 5:06PM up 6 days, 21:28, 4 users, load averages: 0.00, 0.01, 0.00 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to configure an OLD 486 computer running 3.1-R to act as a gateway for a family members @Home Internet connection. Right now I have 2 ethernet cards installed, NAT enabled and isc-dhcp installed. My issues are the dhcp side.. If anyone has done this before I would like to see how you did it. I do not want to go and try and re invent the wheel to get this accomplished. Any pointers highly accepted TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- "Outside of a dog, a book is a man's best friend. Inside of a dog it's too dark to read." - Groucho Marx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri May 7 18:44:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from hustle.rahul.net (hustle.rahul.net [192.160.13.2]) by hub.freebsd.org (Postfix) with SMTP id 181A915AB2 for ; Fri, 7 May 1999 18:43:52 -0700 (PDT) (envelope-from iverson@raw.lionheart.com) Received: from raw.lionheart.com by hustle.rahul.net with BSMTP id AA03826 (5.67b8/IDA-1.5 for ); Fri, 7 May 1999 18:43:50 -0700 From: iverson@raw.lionheart.com Received: from raw.lionheart.com by raw.lionheart.com with uucp (Smail3.1.28.1 #17) id m10fw7e-000M63C; Fri, 7 May 99 18:41 PDT Message-Id: Subject: Domain based routing? To: freebsd-net@freebsd.org Date: Fri, 7 May 1999 18:37:36 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 962 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Freebsd-net folks, I am curious if y'all can stear me to something in FreeBSD or one of the ports for setting up routing based on domains -- something like this: if0: LAN (has router0 with WAN to internet on it) if1: PPP to internet route to if1 and bring up PPP if traffic is for domain foo.com route to router0 for anything else I could manually setup static routes for foo.com, but that seems excessively tedious and prone to error should routing information change (foo.com is huge, too). I'm hoping someone else has already done something similar to this and can just say, "Yeah, use the XXX feature of gated (or better, routed)". FYI, foo.com is not the PPP-ISP, and in fact, I want stuff for the ISP to take the if0 path. Also, my host won't be advertising any routes or forwarding stuff bewteen if1 and router0. I just need to direct some traffic to a different interface based on domain. Thanks, - Tim Iverson iverson@lionheart.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri May 7 22:25: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 9EAA01532F for ; Fri, 7 May 1999 22:25:04 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA14366; Fri, 7 May 1999 23:24:51 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <3733CAA2.3F5EE600@softweyr.com> Date: Fri, 07 May 1999 23:24:50 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: insane@oneinsane.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD Box hooked up to @Home References: <19990507171024.A69647@lunatic.oneinsane.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ron 'The InSaNe One' Rosson wrote: > > I am trying to configure an OLD 486 computer running 3.1-R to act as > a gateway for a family members @Home Internet connection. Right > now I have 2 ethernet cards installed, NAT enabled and isc-dhcp installed. > > My issues are the dhcp side.. If anyone has done this before I would like > to see how you did it. I do not want to go and try and re invent the > wheel to get this accomplished. Using ISC dhclient 2.0 (currently still in beta; I have 2.0b1pl18 and it's working just fine for me) you can specify which interfaces to run dhclient on. You should be able to statically configure the internal interface and dhclient on the @Home interface. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat May 8 10:10:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from orac.early.com (orac.early.com [204.170.83.2]) by hub.freebsd.org (Postfix) with ESMTP id C416A15438 for ; Sat, 8 May 1999 10:10:10 -0700 (PDT) (envelope-from flash@orac.early.com) Received: (from flash@localhost) by orac.early.com (8.8.7/8.8.7) id NAA26415 for freebsd-net@freebsd.org; Sat, 8 May 1999 13:10:09 -0400 (EDT) From: Stephen Corbesero Message-Id: <199905081710.NAA26415@orac.early.com> Subject: Multi-Port Ethernet for FreeBSD To: freebsd-net@freebsd.org Date: Sat, 8 May 1999 13:10:09 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] 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 Is there a list of currently available multi-port (dual or quad) ethernet NIC's (manufacturer and model number) that are supported by FreeBSD 3.1 and/or 2.2.8? Thanks in advance. -- Stephen Corbesero This message has been brought to you by protons. flash@early.com Protons -- The other charged particle. http://www.early.com/~flash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat May 8 11:39:26 1999 Delivered-To: freebsd-net@freebsd.org Received: from kit.isi.edu (kit.isi.edu [128.9.160.207]) by hub.freebsd.org (Postfix) with ESMTP id F1511150B3 for ; Sat, 8 May 1999 11:39:14 -0700 (PDT) (envelope-from eddy@kit.isi.edu) Received: (from eddy@localhost) by kit.isi.edu (8.9.2/8.8.7) id LAA85324; Sat, 8 May 1999 11:39:06 -0700 (PDT) (envelope-from eddy) From: Rusty Eddy Message-Id: <199905081839.LAA85324@kit.isi.edu> Subject: Re: Multi-Port Ethernet for FreeBSD In-Reply-To: <199905081710.NAA26415@orac.early.com> from Stephen Corbesero at "May 8, 1999 1:10: 9 pm" To: flash@Early.COM (Stephen Corbesero) Date: Sat, 8 May 1999 11:39:06 -0700 (PDT) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Is there a list of currently available multi-port (dual or quad) > ethernet NIC's (manufacturer and model number) that are supported by > FreeBSD 3.1 and/or 2.2.8? > > Thanks in advance. i don't know of a document but i can tell you about a couple adaptec cards: quartet ANA-6944 (32bit PCI) is supported (DEC chipset) quartet ANA-62044ANA (64bit PCI) is _not_ supported (AIC chipset) they have a *hefty* price at $695 www.zynx.com is worth a look, (look for the dec chipset) these guys even have linux and bsdi drivers for some products (but of course not freebsd :-/) - rusty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message