From owner-freebsd-net Mon Aug 24 05:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16015 for freebsd-net-outgoing; Mon, 24 Aug 1998 05:07:44 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from chappe.cnes.fr (chappe.cnes.fr [132.149.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15955; Mon, 24 Aug 1998 05:07:32 -0700 (PDT) (envelope-from kevin.choi@cnes.fr) Received: from pasteur.cst.cnes.fr (pasteur.cnes.fr [132.149.22.8]) by chappe.cnes.fr (8.8.8/8.8.8) with ESMTP id OAA18576; Mon, 24 Aug 1998 14:06:31 +0200 (MET DST) Received: from imhotep.cst.cnes.fr (unverified) by pasteur.cst.cnes.fr (Content Technologies SMTPRS 2.0.15) with SMTP id ; Mon, 24 Aug 1998 14:07:11 +0200 Received: from pc-kichoi (pc-kichoi.cst.cnes.fr [132.149.9.82]) by imhotep.cst.cnes.fr (8.6.12/MH-19960223.01) with SMTP id OAA21993; Mon, 24 Aug 1998 14:07:07 +0200 From: "Kevin Kyeong-il CHOI" To: "FreeBSD Question" , "FreeBSD Net" Subject: Anyone knows if a driver on FreeBSD 2.2.6 for ... ? Date: Mon, 24 Aug 1998 14:06:57 +0200 Message-Id: <002101bdcf57$b1311450$52099584@pc-kichoi.cst.cnes.fr> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0022_01BDCF68.74B9E450" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0022_01BDCF68.74B9E450 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, Does anyone know if a driver on FreeBSD exist for "Fore Runner ATM adapter LE 25Mbps" ? Thank you for your answer in advance. Regards ------------------------------------- Kevin Kyeong-il CHOI ~'/ (o\) ^ \___/o Doctoral Research Engineer Service DEE/IR/TL/ES Centre National d'Etudes Spatiales 18 Avenue Edouard-Belin 31401 Toulouse cedex 4 France (T) +33-561 28 15 31 (F) +33-561 28 29 13 (Email) kevin.choi@cnes.fr ------------------------------------- ------=_NextPart_000_0022_01BDCF68.74B9E450 Content-Type: application/octet-stream; name="Kevin Kyeong-il CHOI.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Kevin Kyeong-il CHOI.vcf" BEGIN:VCARD VERSION:2.1 N:CHOI;Kevin;Kyeong-il;; FN:Kevin Kyeong-il CHOI ORG:CNES; TITLE:Dr TEL;WORK;VOICE:(05) 61 28 15 31 TEL;HOME;VOICE:(05) 62 17 01 99 EMAIL;PREF;INTERNET:kevin.choi@cnes.fr REV:19980710T091856Z END:VCARD ------=_NextPart_000_0022_01BDCF68.74B9E450-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 24 10:12:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29391 for freebsd-net-outgoing; Mon, 24 Aug 1998 10:12:11 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29346; Mon, 24 Aug 1998 10:12:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA25422; Mon, 24 Aug 1998 10:04:28 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpds25415; Mon Aug 24 17:04:24 1998 Date: Mon, 24 Aug 1998 10:04:21 -0700 (PDT) From: Julian Elischer To: Kevin Kyeong-il CHOI cc: FreeBSD Question , FreeBSD Net Subject: Re: Anyone knows if a driver on FreeBSD 2.2.6 for ... ? In-Reply-To: <002101bdcf57$b1311450$52099584@pc-kichoi.cst.cnes.fr> 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 there are some drivers for FORE cards but I don't know the models. julian On Mon, 24 Aug 1998, Kevin Kyeong-il CHOI wrote: > Hi, > > Does anyone know if a driver on FreeBSD exist > for > "Fore Runner ATM adapter LE 25Mbps" > ? > > Thank you for your answer in advance. > > Regards > > ------------------------------------- > Kevin Kyeong-il CHOI > > ~'/ (o\) > ^ > \___/o > > Doctoral Research Engineer > > Service DEE/IR/TL/ES > Centre National d'Etudes Spatiales > 18 Avenue Edouard-Belin > 31401 Toulouse cedex 4 > France > (T) +33-561 28 15 31 > (F) +33-561 28 29 13 > (Email) kevin.choi@cnes.fr > ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 25 14:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08666 for freebsd-net-outgoing; Tue, 25 Aug 1998 14:24:16 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08490; Tue, 25 Aug 1998 14:24:01 -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 RAA03172; Tue, 25 Aug 1998 17:22:59 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 17:22:59 -0400 (EDT) From: Garrett Wollman Message-Id: <199808252122.RAA03172@khavrinen.lcs.mit.edu> To: Stefan Bethke Cc: freebsd-current@FreeBSD.ORG, net@FreeBSD.ORG Reply-To: net@FreeBSD.ORG Subject: Semantics of MGET(m, M_WAIT, *)? [was: Huge Bug not fixed?] In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Please watch followups!] < said: > What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest > that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes > available, as it is already the case if the vm map must be extended. It should sleep, but actually doing so while avoiding deadlocks is problematic. Since the mbuf allocator as currently formulated is going away, callers to mget should expect that the allocation might fail, but that M_WAIT makes it ``try harder'' as it were. -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 Aug 25 14:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12663 for freebsd-net-outgoing; Tue, 25 Aug 1998 14:42:10 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12608; Tue, 25 Aug 1998 14:41:54 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA27816; Tue, 25 Aug 1998 22:48:45 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA00354; Tue, 25 Aug 1998 23:42:20 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id XAA01723; Tue, 25 Aug 1998 23:41:08 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 25 Aug 1998 23:41:07 +0200 (CEST) From: Stefan Bethke To: net@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Semantics of MGET(m, M_WAIT, *)? [was: Huge Bug not fixed?] In-Reply-To: <199808252122.RAA03172@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 25 Aug 1998, Garrett Wollman wrote: > [Please watch followups!] > > < > said: > > > What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest > > that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes > > available, as it is already the case if the vm map must be extended. > > It should sleep, but actually doing so while avoiding deadlocks is > problematic. Since the mbuf allocator as currently formulated is > going away, callers to mget should expect that the allocation might > fail, but that M_WAIT makes it ``try harder'' as it were. Which leaves the problem in so_send(). Anyone working on this already? I'd be relieved if I'd rather had not to grasp so_send() and all it's implications... however, if this is too low on others list, I'd might give it a try. Anything I should know about the "mbuf allocator going away" while trying to delve into that? I did a quick search in the archives, but did't really find anything. Thanks, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 06:54:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02889 for freebsd-net-outgoing; Wed, 26 Aug 1998 06:54:35 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from versa.eng.comsat.com (versa.eng.comsat.com [134.133.169.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02865 for ; Wed, 26 Aug 1998 06:54:10 -0700 (PDT) (envelope-from marc@versa.eng.comsat.com) Received: (from marc@localhost) by versa.eng.comsat.com (8.8.8/8.7.3) id KAA09706 for freebsd-net@@freebsd.org; Wed, 26 Aug 1998 10:47:31 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 26 Aug 1998 10:47:14 -0400 (EDT) Organization: Comsat Mobile Communications From: Marc Giannoni To: freebsd-net@@FreeBSD.ORG Subject: NETCCITT sources Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----FW: NETCCITT sources----- Date: Wed, 26 Aug 1998 10:16:00 -0400 (EDT) From: Marc Giannoni To: freebsd-questions@freebsd.org, freebsd-core@freebsd.org, freebsd-net@freebsd.org, freebsd-advocacy@freebsd.org Subject: NETCCITT sources Hey Folks: I have a set of kernel sources for NETCCITT (remember that old stuff?) from the 2.2 branch which I've modified to compile under 'stable'. Essentially all that was needed was function prototyping (ANSI C) and some changes to utilize the kernel MBUF macros. A 'core' team member expressed the opinion that there was just not enough interest to justify reviving these. Are you all sure about that? X.25 networks are still used around the world and it would make FreeBSD that much more 'useful' if we were to include this stuff. Here at Comsat, we are planning on deploying a test FreeBSD system with the X.25 layer in order to evaluate transitioning one of our systems to this platform. But without 'core' support, it's not going to fly with our management. ---------------------------------- E-Mail: Marc Giannoni Date: 26-Aug-98 Time: 10:16:00 This message was sent by XF-Mail ---------------------------------- --------------End of forwarded message------------------------- ---------------------------------- E-Mail: Marc Giannoni Date: 26-Aug-98 Time: 10:47:15 This message was sent by XF-Mail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 07:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06836 for freebsd-net-outgoing; Wed, 26 Aug 1998 07:21:14 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA06826 for ; Wed, 26 Aug 1998 07:21:09 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2262 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 26 Aug 1998 16:20:01 +0200 (METDST) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0zBgT5-0000fAC; Wed, 26 Aug 98 16:22 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: TCP checksum errors resulting from IP addr change To: freebsd-net@FreeBSD.ORG (FreeBSD Networking) Date: Wed, 26 Aug 1998 16:22:35 +0200 (METDST) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (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 I'm trying to debug a strange effect occuring on a sync PPP ISDN interface which is used to connect to a Cisco 1003. To get an address dynamically from the remote side, the local PPP inter- face (on 2.2.5-RELEASE) is set up with: ifconfig isppp0 link1 0.0.0.0 192.76.124.10 netmask 0xffffffff debug Now i telnet to 192.76.124.10 and the link gets established but the telnet session doesn't. I looked at the traces and noticed the very first IP packet going out with source address 0.0.0.0 to the Cisco - i removed that in the driver but still the telnet session is not established. (btw. only the first session is not established, if i terminate the first telnet and restart it on the open link, it works immediately; but i want the first to work ...). I enabled TCP debugging on the Cisco, and for all the packets from this first telnet session it says "TCP checksum error". So i think, IP address 0.0.0.0 is used for checksum calculation of the TCP packets for this forst session, but the "real" IP address of the interface changes to 192.something after the first packet and the TCP checksum is somehow not recalculated causing checksum errors on the remote side. Has anyone a hint or an idea how to solve this ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 07:32:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08446 for freebsd-net-outgoing; Wed, 26 Aug 1998 07:32:34 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA08439 for ; Wed, 26 Aug 1998 07:32:29 -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 OAA02693; Wed, 26 Aug 1998 14:34:44 +0200 From: Luigi Rizzo Message-Id: <199808261234.OAA02693@labinfo.iet.unipi.it> Subject: and now bridging :) To: net@FreeBSD.ORG Date: Wed, 26 Aug 1998 14:34:44 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i have a pre-pre-release of some bridging code for FreeBSD. I have the basic ops working and tested on 2.2.X with the "ed" driver. It _should_ work for the "de" driver as well, and modifications for other drivers should be trivial and will be done "on demand". I think this code, together with the PicoBSD floppy, will make a very very nice bridge between 10 and 100 Mbit/s networks, and possibly also wireless network interfaces. The code should be pretty well performant even on slow isa-based cards because i can (and do this in the "ed" driver) fetch only the ethernet header of all packets, and download the rest of the packet only for those pkts that need to be forwarded. The code, including comments on how to use it, is available at http://www.iet.unipi.it/~luigi/bsd-bdg980826.diffs THIS IS A PRERELEASE NOT READY FOR PRODUCTION. The diffs have been hand-edited so expect some verbosity in applying the patches or trivial compile errors. The code needs some further test and optimization, and support for more boards. The reason i am posting this now is that i need people to test this code, and send feedback on bugs and/or possible enhancements. In particular: * i need to add some per-interface status (for flags and statistics) in the leasts intrusive way. Because the ifnet struct is used also used as a field in arpcom etc, i am a bit reluctant in changing that struct. The only option would then be an external array indexed by if_index. Do you see any other option ? * how does the above patch apply to -current ? * does anyone have a pointer to source code for the spanning tree algorithm that i can put into a user-space daemon ? * extensions: what would be nice to do ? Like add some tunneling option to the bridge ? (in which case i would need to add a "virtual" interface that can be used to tunnel packets). if you download the code, please try it out, otherwise just wait a few more days until it stabilizes. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 07:39:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09462 for freebsd-net-outgoing; Wed, 26 Aug 1998 07:39:26 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09457 for ; Wed, 26 Aug 1998 07:39:22 -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 KAA05325; Wed, 26 Aug 1998 10:38:15 -0400 (EDT) (envelope-from wollman) Date: Wed, 26 Aug 1998 10:38:15 -0400 (EDT) From: Garrett Wollman Message-Id: <199808261438.KAA05325@khavrinen.lcs.mit.edu> To: Marc Giannoni Cc: freebsd-net@FreeBSD.ORG Subject: NETCCITT sources In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: Sending the same message to four disparate lists is not a way to Win Friends and Influence People. > A 'core' team member expressed the opinion that there was just not > enough interest to justify reviving these. No, that's not really our reason for killing the X.25 support. We simply don't have any major kernel developers who are able to support this particular dusty deck. As we further evolve the networking code, dealing with an ancient, obsolete protocol stack would be a significant hindrance. We're perfectly willing, however, to ``bless'' any third party who wanted to try to make this stuff work. -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 Aug 26 15:23:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02491 for freebsd-net-outgoing; Wed, 26 Aug 1998 15:23:19 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from absinthe.shenton.org (Absinthe.Shenton.Org [209.31.147.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02448 for ; Wed, 26 Aug 1998 15:23:10 -0700 (PDT) (envelope-from chris@absinthe.shenton.org) Received: (from chris@localhost) by absinthe.shenton.org (8.7.2/8.7.2) id SAA05248; Wed, 26 Aug 1998 18:20:42 -0400 (EDT) To: Luigi Rizzo cc: net@FreeBSD.ORG Subject: Re: and now bridging :) References: <199808261234.OAA02693@labinfo.iet.unipi.it> X-Emacs: Emacs 20.2, MULE 3.0 (MOMIJINOGA) MIME-Version: 1.0 (generated by SEMI 1.2.1 - "Nomachi") Content-Type: text/plain; charset=US-ASCII From: Chris Shenton Date: 26 Aug 1998 18:20:41 -0400 In-Reply-To: Luigi Rizzo's message of Wed, 26 Aug 1998 14:34:44 +0200 (MET DST) Message-ID: <877lzv8jwm.fsf@absinthe.shenton.org> Lines: 16 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo writes: > i have a pre-pre-release of some bridging code for FreeBSD. I have the > basic ops working and tested on 2.2.X with the "ed" driver. It > _should_ work for the "de" driver as well, and modifications for other > drivers should be trivial and will be done "on demand". > > I think this code, together with the PicoBSD floppy, will make a very > very nice bridge between 10 and 100 Mbit/s networks Way cool! I was thinking of looking into TAMU's drawbridge to make a 10-100Mbps bridge but figured the security overhead would kill performance. Got plans to support the Intel EtherExpress Pro 100Mbps card? [Demand :-] Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 15:35:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05605 for freebsd-net-outgoing; Wed, 26 Aug 1998 15:35:33 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from strato-fe0.ultra.net (strato-fe0.ultra.net [146.115.8.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05591 for <"freebsd-net@"@FreeBSD.ORG>; Wed, 26 Aug 1998 15:35:29 -0700 (PDT) (envelope-from moncrg@ma.ultranet.com) Received: from ma.ultranet.com (d186.dial-5.cmb.ma.ultra.net [209.6.68.186]) by strato-fe0.ultra.net (8.8.8/ult.n14767) with ESMTP id SAA16649; Wed, 26 Aug 1998 18:34:31 -0400 (EDT) Message-ID: <35E49BB9.BF3CB38B@ma.ultranet.com> Date: Wed, 26 Aug 1998 18:35:21 -0500 From: "Gregory D. Moncreaff" Reply-To: moncrg@ma.ultranet.com X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: Marc Giannoni CC: "freebsd-net@"@FreeBSD.ORG Subject: Re: NETCCITT sources References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd vote for it! I also tried to sound out about NETISO but it seems that only 3 or so people ask about it a year and that is not enough of a "horde" for him? you'd think that it wouldn't be a big issue since Net/Open BSDs still have it Of course by dropping it FreeBSD is losing some of its heritage... I'd really prefer to stick with FreeBSD but might be forced to consider Net/Open... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 18:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03712 for freebsd-net-outgoing; Wed, 26 Aug 1998 18:17:39 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03645 for <"freebsd-net@"@FreeBSD.ORG>; Wed, 26 Aug 1998 18:17:08 -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 VAA07223; Wed, 26 Aug 1998 21:16:11 -0400 (EDT) (envelope-from wollman) Date: Wed, 26 Aug 1998 21:16:11 -0400 (EDT) From: Garrett Wollman Message-Id: <199808270116.VAA07223@khavrinen.lcs.mit.edu> To: moncrg@ma.ultranet.com Cc: Marc Giannoni , "freebsd-net@"@FreeBSD.ORG Subject: Re: NETCCITT sources In-Reply-To: <35E49BB9.BF3CB38B@ma.ultranet.com> References: <35E49BB9.BF3CB38B@ma.ultranet.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > you'd think that it wouldn't be a big issue > since Net/Open BSDs still have it They also have VAX support, which is another thing we don't consider to be worth the effort. > Of course by dropping it FreeBSD is losing > some of its heritage... Not really. OSI was something that was kluged in by Berkeley fairly late in the game, when people still thought it might actually be used by somebody. XNS is far closer to being BSD heritage (since it was the original proof-of-concept that the socket framework was capable of supporting multiple protocols), and only one cranky ISV complained about its loss. > I'd really prefer to stick with FreeBSD > but might be forced to consider Net/Open... Don't think we consider this threatening. There are some things they are able to support that we don't want to -- such is life. We have no desire to see anyone unhappy; if you have an application for which their codebase is a better match than ours, by all means, use it! -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 18:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05885 for freebsd-net-outgoing; Wed, 26 Aug 1998 18:31:26 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from haleakala.aloha.net (haleakala.aloha.net [204.94.112.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05847 for ; Wed, 26 Aug 1998 18:31:15 -0700 (PDT) (envelope-from volack@computer.org) Received: from volack.volack (oahu-645.u.aloha.net [207.12.2.133]) by haleakala.aloha.net (8.8.5/8.6.9) with SMTP id PAA23334; Wed, 26 Aug 1998 15:30:16 -1000 (HST) Date: Wed, 26 Aug 1998 15:30:16 -1000 (HST) From: "Joseph J. Volack, Jr., PE" X-Sender: volack@volack.volack To: Marc Giannoni cc: freebsd-net@FreeBSD.ORG Subject: Re: NETCCITT sources 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 Wed, 26 Aug 1998, Marc Giannoni wrote: > > -----FW: NETCCITT sources----- > > Date: Wed, 26 Aug 1998 10:16:00 -0400 (EDT) > From: Marc Giannoni > To: freebsd-questions@freebsd.org, freebsd-core@freebsd.org, > freebsd-net@freebsd.org, freebsd-advocacy@freebsd.org > Subject: NETCCITT sources > > Hey Folks: > > I have a set of kernel sources for NETCCITT (remember that old stuff?) > from the 2.2 branch which I've modified to compile under 'stable'. > Essentially all that was needed was function prototyping (ANSI C) and > some changes to utilize the kernel MBUF macros. > > A 'core' team member expressed the opinion that there was just not > enough interest to justify reviving these. > > Are you all sure about that? X.25 networks are still used around the world > and it would make FreeBSD that much more 'useful' if we were to include this > stuff. > > Here at Comsat, we are planning on deploying a test FreeBSD system with the > X.25 layer in order to evaluate transitioning one of our systems to this > platform. But without 'core' support, it's not going to fly with our > management. > Yes, we are interested here. Any chance that you might make your modified stack available? Joe Volack ******************************************* * Joseph J. Volack, Jr., PE * * Unix, VMS, and NT Systems * * Multiprotocol Multiventor Data Networks * * Custom Designed Network Appliances * ******************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 18:56:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09953 for freebsd-net-outgoing; Wed, 26 Aug 1998 18:56:19 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09932 for ; Wed, 26 Aug 1998 18:56:10 -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 VAA07365; Wed, 26 Aug 1998 21:55:19 -0400 (EDT) (envelope-from wollman) Date: Wed, 26 Aug 1998 21:55:19 -0400 (EDT) From: Garrett Wollman Message-Id: <199808270155.VAA07365@khavrinen.lcs.mit.edu> To: net@FreeBSD.ORG Subject: Next big network patch: specialized sosend for TCP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's the next patch that's going into the TCP stack. I am running this right now, so I'm certain it's not completely bogus, but have not stress-tested it as yet. It does appear to be somewhat faster (having eliminated about a dozen branches), but -current is a very hostile environment for microbenchmarks of the sort I would usually use. Once again, any comments would be appreciated. -GAWollman Index: netinet/tcp_usrreq.c =================================================================== RCS file: /home/cvs/src/sys/netinet/tcp_usrreq.c,v retrieving revision 1.38 diff -u -r1.38 tcp_usrreq.c --- tcp_usrreq.c 1998/08/23 03:07:15 1.38 +++ tcp_usrreq.c 1998/08/27 01:44:26 @@ -73,6 +73,9 @@ struct proc *)); static struct tcpcb * tcp_disconnect __P((struct tcpcb *)); +static int tcp_sosend __P((struct socket *, struct sockaddr *, + struct uio *, struct mbuf *, struct mbuf *, + int, struct proc *)); static struct tcpcb * tcp_usrclosed __P((struct tcpcb *)); @@ -325,6 +328,10 @@ /* * Do a send by putting data in output queue and updating urgent * marker if URG set. Possibly send more data. + * + * XXX - this routine is really only here for the benefit of NFS. + * Somebody who knows the NFS code should figure out why NFS + * is going through here and where it should go. */ static int tcp_usr_send(struct socket *so, int flags, struct mbuf *m, @@ -336,14 +343,12 @@ struct tcpcb *tp; COMMON_START(); - if (control && control->m_len) { - m_freem(control); /* XXX shouldn't caller do this??? */ - if (m) - m_freem(m); - error = EINVAL; - goto out; - } - + /* + * We used to check for control information here, but + * tcp_sosend() doesn't call here, and any direct callers (i.e., NFS) + * should know enough to refrain from sending any since TCP + * has never supported control information. + */ if(!(flags & PRUS_OOB)) { sbappend(&so->so_snd, m); if (nam && tp->t_state < TCPS_SYN_SENT) { @@ -459,7 +464,7 @@ tcp_usr_connect, pru_connect2_notsupp, in_control, tcp_usr_detach, tcp_usr_disconnect, tcp_usr_listen, in_setpeeraddr, tcp_usr_rcvd, tcp_usr_rcvoob, tcp_usr_send, pru_sense_null, tcp_usr_shutdown, - in_setsockaddr, sosend, soreceive, sopoll + in_setsockaddr, tcp_sosend, soreceive, sopoll }; /* @@ -786,5 +791,230 @@ tp->t_timer[TCPT_2MSL] = tcp_maxidle; } return (tp); +} + +#include +#include +#include +#include +#include + +#define SBLOCKWAIT(f) (((f) & MSG_DONTWAIT) ? M_NOWAIT : M_WAITOK) +/* + * Specialized from kern/uipc_socket.c:sosend(). This isn't + * even close to fully optimized, but it has been run through + * a round of invisible constant propagation and dead code + * elimination. The (uio != 0) and (top != 0) should probably + * be separated by a single major branch, since the code + * is well interspersed at present (which is probably bad + * for branch prediction). + * + * Returns nonzero on error, timeout or signal; callers + * must check for short counts if EINTR/ERESTART are returned. + * Data and control buffers are freed on return. + */ +static int +tcp_sosend(so, addr, uio, top, control, flags, p) + register struct socket *so; + struct sockaddr *addr; + struct uio *uio; + struct mbuf *top; + struct mbuf *control; + int flags; + struct proc *p; +{ + struct mbuf **mp; + register struct mbuf *m; + register long space, len, resid; + struct inpcb *inp; + struct tcpcb *tp; + int error, s, mlen; + TCPDEBUG0; + + /* + * I believe that a socket can never become ``bare'' + * during the execution of this routine. (I don't think + * that a socket can ever become ``bare'' except for brief + * moments during initialization and rundown, but haven't + * proven that.) (Of course, I haven't proven this, either. + * We'll see.) + */ + if ((inp = sotoinpcb(so)) == 0) { + error = EINVAL; + goto release; + } + tp = intotcpcb(inp); + + if (uio) + resid = uio->uio_resid; + else + resid = top->m_pkthdr.len; + /* + * In theory resid should be unsigned. + * However, space must be signed, as it might be less than 0 + * if we over-committed, and we must use a signed comparison + * of space and resid. On the other hand, a negative resid + * causes us to loop sending 0-length segments to the protocol. + * Also bail early if we get control information -- TCP doesn't + * support that. + */ + if (resid < 0 || (control && control->m_len) || inp == 0) { + error = EINVAL; + goto out; + } + + if (p) + p->p_stats->p_ru.ru_msgsnd++; + +restart: + error = sblock(&so->so_snd, SBLOCKWAIT(flags)); + if (error) + goto out; + do { + s = splnet(); +#define snderr(errno) do { error = errno; splx(s); goto release; } while (0) + if (so->so_state & SS_CANTSENDMORE) + snderr(EPIPE); + if (so->so_error) { + error = so->so_error; + so->so_error = 0; + splx(s); + goto release; + } + if ((so->so_state & SS_ISCONNECTED) == 0 + && addr == 0) + snderr(ENOTCONN); + + space = sbspace(&so->so_snd); + if (flags & MSG_OOB) + space += 1024; /* XXX totally arbitrary */ + if (uio == 0 && resid > so->so_snd.sb_hiwat) + snderr(EMSGSIZE); + if (space < resid && uio && space < so->so_snd.sb_lowat) { + if (so->so_state & SS_NBIO) + snderr(EWOULDBLOCK); + sbunlock(&so->so_snd); + error = sbwait(&so->so_snd); + splx(s); + if (error) + goto out; + goto restart; + } + splx(s); + mp = ⊤ + do { + if (uio == NULL) { + /* + * Data is prepackaged in "top". + */ + resid = 0; + } else do { + if (top == 0) { + MGETHDR(m, M_WAIT, MT_DATA); + mlen = MHLEN; + m->m_pkthdr.len = 0; + m->m_pkthdr.rcvif = (struct ifnet *)0; + } else { + MGET(m, M_WAIT, MT_DATA); + mlen = MLEN; + } + if (resid >= MINCLSIZE) { + MCLGET(m, M_WAIT); + if ((m->m_flags & M_EXT) == 0) + goto nopages; + mlen = MCLBYTES; + len = min(min(mlen, resid), space); + } else { +nopages: + len = min(min(mlen, resid), space); + } + space -= len; + error = uiomove(mtod(m, caddr_t), (int)len, uio); + resid = uio->uio_resid; + m->m_len = len; + *mp = m; + top->m_pkthdr.len += len; + if (error) + goto release; + mp = &m->m_next; + if (resid <= 0) { + break; + } + } while (space > 0); + s = splnet(); /* XXX */ + TCPDEBUG1(); + /* + * XXX -- should be possible to perform this check + * out of the loop. + */ + if ((flags & MSG_OOB) && sbspace(&so->so_snd) < -512) { + splx(s); + snderr(ENOBUFS); + } + sbappend(&so->so_snd, top); + + /* + * Do implied connect if not yet connected, + * initialize window to default value, and + * initialize maxseg/maxopd using peer's cached + * MSS. + */ + if (addr && tp->t_state < TCPS_SYN_SENT) { + error = tcp_connect(tp, addr, p); + if (error) + goto out; + tp->snd_wnd = TTCP_CLIENT_SND_WND; + tcp_mss(tp, -1); + } + + if (flags & MSG_OOB) { + /* + * According to RFC961 (Assigned Protocols), + * the urgent pointer points to the last octet + * of urgent data. We continue, however, + * to consider it to indicate the first octet + * of data past the urgent section. + * Otherwise, snd_up should be one lower. + */ + tp->snd_up = tp->snd_una + so->so_snd.sb_cc; + tp->t_force = 1; + error = tcp_output(tp); + tp->t_force = 0; + TCPDEBUG2(PRU_SEND_OOB); + } else if ((flags & MSG_EOF) && resid <= 0) { + socantsendmore(so); + tp = tcp_usrclosed(tp); +#ifdef DIAGNOSTIC + /* + * The only way tcp_usrclosed() can cause the + * tcpcb to go away entirely is if it was either + * CLOSED or LISTENing. In either state, we + * should never have gotten this far. + */ + if (tp == 0) + panic("tcp_sosend: socket already closed"); +#endif + error = tcp_output(tp); + TCPDEBUG2(PRU_SEND_EOF); + } else { + error = tcp_output(tp); + TCPDEBUG2(PRU_SEND); + } + splx(s); + top = 0; + mp = ⊤ + if (error) + goto release; + } while (resid && space > 0); + } while (resid); + +release: + sbunlock(&so->so_snd); +out: + if (top) + m_freem(top); + if (control) + m_freem(control); + return (error); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 20:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19697 for freebsd-net-outgoing; Wed, 26 Aug 1998 20:02:32 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA19692 for ; Wed, 26 Aug 1998 20:02:31 -0700 (PDT) (envelope-from barney@databus.databus.com) From: Barney Wolff To: freebsd-net@FreeBSD.ORG Date: Wed, 26 Aug 1998 22:59 EDT Subject: Re: NETCCITT sources Content-Type: text/plain Message-ID: <35e4cc130.1026@databus.databus.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to chime in with interest in X.25 support, but admit to knowing nothing about how it worked. Did/does it come with board support or is that up to the vendor or a volunteer? Barney Wolff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 26 21:46:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03180 for freebsd-net-outgoing; Wed, 26 Aug 1998 21:46:36 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03148 for ; Wed, 26 Aug 1998 21:46:20 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from obie.softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with SMTP id WAA06588; Wed, 26 Aug 1998 22:51:15 -0600 (MDT) (envelope-from wes@softweyr.com) Date: Wed, 26 Aug 1998 22:51:15 -0600 (MDT) Message-Id: <199808270451.WAA06588@obie.softweyr.com> Subject: Re: NETCCITT sources From: Wes Peters To: moncrg@ma.ultranet.com, wollman@khavrinen.lcs.mit.edu, freebsd-net@FreeBSD.ORG Cc: marc@versa.eng.comsat.com Reply-To: Wes Peters In-Reply-To: <199808270116.VAA07223@khavrinen.lcs.mit.edu> References: <199808270116.VAA07223@khavrinen.lcs.mit.edu> X-Priority: 3 (Normal) X-Mailer: BeatWare Mail-It 1.6 X-BeOS-Platform: Intel or clone Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id VAA03165 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My hidden microphone recorded Garrett Wollman (wollman@khavrinen.lcs.mit.edu) saying: % < said (with respect to NETCCITT): % % > Of course by dropping it FreeBSD is losing % > some of its heritage... % % Not really. OSI was something that was kluged in by Berkeley fairly % late in the game, when people still thought it might actually be used % by somebody. And, in the world in general, OSI has finally! died the horrible, protracted death it always deserved. Back in 93-94, when it looked (to some) like OSI was going to be the wave of the future, but the TCP/IP internet was starting to grow rapidly, we had a saying: "OSI - the network of the future. Always has been, always will be." Fortunately, even this isn't true anymore. OSI is an idea whose time came and went long before the eggheads and bureaucrats that designed ever produced ANYTHING. The TCP/IP internet survived and thrived because its entire design revolved around getting things DONE. OSI died because it was designed to death with little or no attention paid to "silly details" like implementing or using it. % > I'd really prefer to stick with FreeBSD % > but might be forced to consider Net/Open... % % Don't think we consider this threatening. Yeah -- the attitude you'll get from most of us here is "whatever spins YOUR beanie." NetBSD, OpenBSD, Linux -- sorry we couldn't help. FreeBSD has enough projects lying about to keep those who are working on it now busy for decades, so unless you want to become the champion of netccitt, don't expect much. I suspect this is an area that has not gotten much attention in NetBSD or OpenBSD lately, either, but good luck in your search. -- "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 Aug 26 22:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08928 for freebsd-net-outgoing; Wed, 26 Aug 1998 22:23:15 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08921 for ; Wed, 26 Aug 1998 22:23:13 -0700 (PDT) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.8.8/8.8.8) with SMTP id BAA01327 for ; Thu, 27 Aug 1998 01:20:31 -0500 (EST) (envelope-from jim@web-ex.com) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Thu, 27 Aug 1998 01:20:31 -0500 (EST) From: Jim Cassata To: FreeBSD Net Subject: dedicated 56k 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 This may sound lame for you guys, but what do I have to do to run ppp over a 56k adtran dsu connected to my serial port? I have a router on the other end, but this is the first time I am attempting this. I have used SDL Riscomm N2D's in the past, and configure the serial link with ifconfig for T1s. I am not having any luck here, and all info I can find deals with modems attached to my serial port. FreeBSD 3.0 SNAP and an Adtran dsu III AR. Any help would be greatly appreciated. Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 27 00:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25767 for freebsd-net-outgoing; Thu, 27 Aug 1998 00:30:05 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25700 for ; Thu, 27 Aug 1998 00:29:59 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA05421; Thu, 27 Aug 1998 00:27:23 -0700 (PDT) Message-Id: <199808270727.AAA05421@implode.root.com> To: Garrett Wollman cc: net@FreeBSD.ORG Subject: Re: Next big network patch: specialized sosend for TCP In-reply-to: Your message of "Wed, 26 Aug 1998 21:55:19 EDT." <199808270155.VAA07365@khavrinen.lcs.mit.edu> From: David Greenman Reply-To: dg@root.com Date: Thu, 27 Aug 1998 00:27:23 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Here's the next patch that's going into the TCP stack. I am running >this right now, so I'm certain it's not completely bogus, but have not >stress-tested it as yet. It does appear to be somewhat faster (having >eliminated about a dozen branches), but -current is a very hostile >environment for microbenchmarks of the sort I would usually use. > >Once again, any comments would be appreciated. ... > > /* >@@ -786,5 +791,230 @@ > tp->t_timer[TCPT_2MSL] = tcp_maxidle; > } > return (tp); >+} >+ >+#include >+#include >+#include >+#include >+#include >+ >+#define SBLOCKWAIT(f) (((f) & MSG_DONTWAIT) ? M_NOWAIT : M_WAITOK) #include's don't belong in the middle of a file. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 27 09:22:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02769 for freebsd-net-outgoing; Thu, 27 Aug 1998 09:22:43 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from antiochus-fe0.ultra.net (antiochus-fe0.ultra.net [146.115.8.188]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02746 for ; Thu, 27 Aug 1998 09:22:39 -0700 (PDT) (envelope-from moncrg@ma.ultranet.com) Received: from ma.ultranet.com (d142.dial-2.cmb.ma.ultra.net [209.6.65.142]) by antiochus-fe0.ultra.net (8.8.8/ult.n14767) with ESMTP id MAA28054; Thu, 27 Aug 1998 12:21:25 -0400 (EDT) Message-ID: <35E59588.80FD2077@ma.ultranet.com> Date: Thu, 27 Aug 1998 12:21:12 -0500 From: "Gregory D. Moncreaff" X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: Wes Peters CC: freebsd-net@FreeBSD.ORG Subject: Re: NETCCITT sources References: <199808270116.VAA07223@khavrinen.lcs.mit.edu> <199808270451.WAA06588@obie.softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wes Peters wrote: > > And, in the world in general, OSI has finally! died the horrible, > protracted death it always deserved. Guess you haven't heard of ICAO's ATN [areonautical telecommunications network], it is based on OSI's CLNP, TP etc with X.25 as the air/ground subnetwork granted, all the ground infrastructure will undoubtably run TCP/IP as well, however there is no avoiding the bits-in-the-air [as it were] of CLNP on X.25 > > FreeBSD > has enough projects lying about to keep those who are working on it now > busy for decades, so unless you want to become the champion of netccitt, > don't expect much. I'm not so much asking for help as asking that it [OSI/X.25 protocol support] not be made any more difficult [aka the removal of the OSI conditional code in sbin/ifconfig/ifconfig.c that occured recently, or the rejection of a patch to such that fixed the prototype warnings] I've been using for 2 and a half years now if at all possible [2.1.0 -> 2.2.5 -> 2.2.7 -> ???] Hey, I offerred to [help] maintain netiso's OSI, I guess no one was interested... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 27 10:13:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12146 for freebsd-net-outgoing; Thu, 27 Aug 1998 10:13:47 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12140 for ; Thu, 27 Aug 1998 10:13:43 -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 NAA09704; Thu, 27 Aug 1998 13:12:50 -0400 (EDT) (envelope-from wollman) Date: Thu, 27 Aug 1998 13:12:50 -0400 (EDT) From: Garrett Wollman Message-Id: <199808271712.NAA09704@khavrinen.lcs.mit.edu> To: "Gregory D. Moncreaff" Cc: freebsd-net@FreeBSD.ORG Subject: Re: NETCCITT sources In-Reply-To: <35E59588.80FD2077@ma.ultranet.com> References: <199808270116.VAA07223@khavrinen.lcs.mit.edu> <199808270451.WAA06588@obie.softweyr.com> <35E59588.80FD2077@ma.ultranet.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Hey, I offerred to [help] maintain netiso's OSI, > I guess no one was interested... It's more than that -- even with a maintainer on board (and such people have an unfortunate tendency to drift away over time), there is still a significant maintenance headache for anyone making major changes to the structure of the kernel. Either they have to go through rounds of tedious interchange with all the outside maintainers of various bits, or they have to do all the work themselves. Speaking as someone who has gone through this a number of times, it's not fun and either way often leaves bits of the kernel broken for undesirably long periods. >From our perspective, if something isn't widely-enough used that people will notice its breaking, we are better off having it maintained outside our tree -- that way, we're not stuck with the burden of maintaining something none of us use or can verify functionally. -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 Thu Aug 27 11:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22738 for freebsd-net-outgoing; Thu, 27 Aug 1998 11:08:16 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22693 for ; Thu, 27 Aug 1998 11:08:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA00847; Thu, 27 Aug 1998 10:58:03 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdIAT842; Thu Aug 27 17:58:00 1998 Date: Thu, 27 Aug 1998 10:57:57 -0700 (PDT) From: Julian Elischer Reply-To: Julian Elischer To: Garrett Wollman cc: net@FreeBSD.ORG Subject: Re: Next big network patch: specialized sosend for TCP In-Reply-To: <199808270155.VAA07365@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 26 Aug 1998, Garrett Wollman wrote: > + if (resid >= MINCLSIZE) { > + MCLGET(m, M_WAIT); > + if ((m->m_flags & M_EXT) == 0) > + goto nopages; > + mlen = MCLBYTES; > + len = min(min(mlen, resid), space); > + } else { > +nopages: > + len = min(min(mlen, resid), space); > + } can be rewritten to: > + if (resid >= MINCLSIZE) { > + MCLGET(m, M_WAIT); > + if (m->m_flags & M_EXT) > + mlen = MCLBYTES; > + } > + len = min(min(mlen, resid), space); (unless I'm smoking crack) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 27 11:28:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25843 for freebsd-net-outgoing; Thu, 27 Aug 1998 11:28:39 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25822 for ; Thu, 27 Aug 1998 11:28:28 -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 OAA10118; Thu, 27 Aug 1998 14:27:34 -0400 (EDT) (envelope-from wollman) Date: Thu, 27 Aug 1998 14:27:34 -0400 (EDT) From: Garrett Wollman Message-Id: <199808271827.OAA10118@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: net@FreeBSD.ORG Subject: Re: Next big network patch: specialized sosend for TCP In-Reply-To: References: <199808270155.VAA07365@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > On Wed, 26 Aug 1998, Garrett Wollman wrote: > can be rewritten to: >> + if (resid >= MINCLSIZE) { >> + MCLGET(m, M_WAIT); >> + if (m->m_flags & M_EXT) >> + mlen = MCLBYTES; >> + } >> + len = min(min(mlen, resid), space); There's a lot more work to be done in here. For example, one of the things I'd like to see is whether sucking the data in MSS-sized chunks helps or hurts us. I think we may also see a win by aligning short packets against the end of the mbuf, so that when TCP m_prepend()s its headers, it doesn't need to allocate another buffer. (This is still really klugey; hopefully I'll get a chance to finish my UDP work which is much more fully-formed.) -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 Thu Aug 27 12:13:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05154 for freebsd-net-outgoing; Thu, 27 Aug 1998 12:13:34 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05134 for ; Thu, 27 Aug 1998 12:13:25 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA03430; Thu, 27 Aug 1998 12:03:14 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdgW3426; Thu Aug 27 19:03:12 1998 Date: Thu, 27 Aug 1998 12:03:09 -0700 (PDT) From: Julian Elischer To: "Gregory D. Moncreaff" cc: Wes Peters , freebsd-net@FreeBSD.ORG Subject: Re: NETCCITT sources In-Reply-To: <35E59588.80FD2077@ma.ultranet.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 If you are interested in maintaining it (I try maintain netatalk) then we can surely put the code back. The first thing that we would need is a mega-patch that puts it back. If you supply that and can tell us that it's been tested, thatn there are many committers who will do the commit work for you. If you do a lot you could probably get commit privs. yourself, but you need to be willing to test it and support it on a regular basis. julian On Thu, 27 Aug 1998, Gregory D. Moncreaff wrote: > Wes Peters wrote: > > > > And, in the world in general, OSI has finally! died the horrible, > > protracted death it always deserved. > > Guess you haven't heard of ICAO's ATN > [areonautical telecommunications network], > it is based on OSI's CLNP, TP etc > with X.25 as the air/ground subnetwork > > granted, all the ground infrastructure will > undoubtably run TCP/IP as well, however there > is no avoiding the bits-in-the-air [as it were] > of CLNP on X.25 > > > > > FreeBSD > > has enough projects lying about to keep those who are working on it now > > busy for decades, so unless you want to become the champion of netccitt, > > don't expect much. > > I'm not so much asking for help as asking > that it [OSI/X.25 protocol support] not be made > any more difficult [aka the removal of the OSI > conditional code in sbin/ifconfig/ifconfig.c > that occured recently, or the rejection of a > patch to such that fixed the prototype warnings] > > I've been using for 2 and a half years now if at all > possible [2.1.0 -> 2.2.5 -> 2.2.7 -> ???] > > Hey, I offerred to [help] maintain netiso's OSI, > I guess no one was interested... > > 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 Aug 27 15:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18572 for freebsd-net-outgoing; Thu, 27 Aug 1998 15:43:45 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from strato-fe0.ultra.net (strato-fe0.ultra.net [146.115.8.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18523 for ; Thu, 27 Aug 1998 15:43:20 -0700 (PDT) (envelope-from moncrg@ma.ultranet.com) Received: from ma.ultranet.com (d39.dial-5.cmb.ma.ultra.net [209.6.68.39]) by strato-fe0.ultra.net (8.8.8/ult.n14767) with ESMTP id SAA22007; Thu, 27 Aug 1998 18:42:21 -0400 (EDT) Message-ID: <35E5EF10.8251570@ma.ultranet.com> Date: Thu, 27 Aug 1998 18:43:12 -0500 From: "Gregory D. Moncreaff" Reply-To: moncrg@ma.ultranet.com X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: Garrett Wollman CC: freebsd-net@FreeBSD.ORG Subject: NETISO sources [was Re: NETCCITT] References: <199808270116.VAA07223@khavrinen.lcs.mit.edu> <199808270451.WAA06588@obie.softweyr.com> <35E59588.80FD2077@ma.ultranet.com> <199808271712.NAA09704@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 well I've been working on and off with this since 2.1.0 and am likely to still be here in 2000 last time I looked at this, it was only a couple of macro changes and prototype cleanups for 2.2-stable to get ISO packets: CLNP/ESIS running over ethernet I can't speak much about EON or TPIP variants at this point the probable first step would be to pull in Net/OpenBSD changes as it looks like they did a fine job with all the prototype warnings and go from there it would probably be a good idea to put netiso back into libc and libc_r [iso_addr] netstat and ifconfig and maybe route would have to be updated [-DISO] and you should be able to route CLNP between ethernet segments and add a few sysctl variables in net.iso.* and add ifconfig_${ifn}_iso to rc.network to match ipx did I miss anything? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 27 18:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20458 for freebsd-net-outgoing; Thu, 27 Aug 1998 18:43:05 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20442 for ; Thu, 27 Aug 1998 18:42:55 -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 VAA11467; Thu, 27 Aug 1998 21:42:01 -0400 (EDT) (envelope-from wollman) Date: Thu, 27 Aug 1998 21:42:01 -0400 (EDT) From: Garrett Wollman Message-Id: <199808280142.VAA11467@khavrinen.lcs.mit.edu> To: net@FreeBSD.ORG Cc: kirk@McKusick.com Subject: Puzzled over sosend's handling of pre-prepared mbufs... Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In looking over mbuf handling for TCP some more, I noticed a puzzling omission. When sosend() is handed an mbuf chain rather than a uio, it makes no effort to check whether the chain would actually fit within the socket buffer limits. It simply calls pru_send() with the mbuf chain, which -- in TCP's case -- just passes it to sbappend() also without making any sort of check. The only client of this interface, NFS, also makes no attempt to check the socket buffer capacity. Is this reasonable? I would rather see NFS obey the same buffering model as everything else; that will make life much easier when the underlying buffer mechanism changes. In this case, that would mean that the process making the NFS request would get blocked rather than ``overrun'' the buffer. (I put ``overrun'' in quotation marks since there is no physical limit on socket buffer lengths, just a logical/administrative one.) -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 Aug 28 01:53:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19785 for freebsd-net-outgoing; Fri, 28 Aug 1998 01:53:35 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA19772 for ; Fri, 28 Aug 1998 01:53:28 -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 IAA04891 for net@freebsd.org; Fri, 28 Aug 1998 08:56:15 +0200 From: Luigi Rizzo Message-Id: <199808280656.IAA04891@labinfo.iet.unipi.it> Subject: Proposal for (minimal) change to network drivers in promisc. mode To: net@FreeBSD.ORG Date: Fri, 28 Aug 1998 08:56:15 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In most (all ?) network card drivers, there are comments like the following (generally copied from one driver to the other...): /* * Note that the interface cannot be in promiscuous mode if * there are no BPF listeners. And if we are in promiscuous now, isn't that a strong assumption ? There could be more reasons to enable promiscuous mode on a machine (e.g. the bridging code i am writing now, and possibly others), and the savings in the code deriving from that assumption are really negligible: typically the code would go from if (sc->arpcom.ac_if.if_bpf) { bpf_mtap(&sc->arpcom.ac_if, m); if ((sc->arpcom.ac_if.if_flags & IFF_PROMISC) && pkt is not for us) drop pkt ; } to if (sc->arpcom.ac_if.if_bpf) bpf_mtap(&sc->arpcom.ac_if, m); if ((sc->arpcom.ac_if.if_flags & IFF_PROMISC) && pkt is not for us) drop pkt ; where the second 'if' is very cheap when not in promiscuous mode. Some drivers already decouple bpf and PROMISC handling in the way shown above, and i think this is all in the interest of clarity. For others the modifications would be trivial. At a first scan of the code i see the following: "de", "fe", "ie", "lnc" already fixed. "ed", "fxp", "ep", "wl", "zp": one-line fix as shown above Note: the ep" driver one seems to have a redundant expensive check for broadcast address "le", "ze" almost as simple as above "eg", "el", "ex", "tx" seem not to support multicast/promisc mode so this is less of a problem. What do you think, can i submit patches for at least a few of these drivers with the hope that they get committed ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 28 07:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25965 for freebsd-net-outgoing; Fri, 28 Aug 1998 07:52:25 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25959 for ; Fri, 28 Aug 1998 07:52:20 -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 KAA13419; Fri, 28 Aug 1998 10:50:58 -0400 (EDT) (envelope-from wollman) Date: Fri, 28 Aug 1998 10:50:58 -0400 (EDT) From: Garrett Wollman Message-Id: <199808281450.KAA13419@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: Proposal for (minimal) change to network drivers in promisc. mode In-Reply-To: <199808280656.IAA04891@labinfo.iet.unipi.it> References: <199808280656.IAA04891@labinfo.iet.unipi.it> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > now, isn't that a strong assumption ? There could be more reasons > to enable promiscuous mode on a machine (e.g. the bridging code i > am writing now, and possibly others) I don't have a strong opinion.... -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 Aug 28 09:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15921 for freebsd-net-outgoing; Fri, 28 Aug 1998 09:57:47 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA15883 for ; Fri, 28 Aug 1998 09:57: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 RAA05239; Fri, 28 Aug 1998 17:00:02 +0200 From: Luigi Rizzo Message-Id: <199808281500.RAA05239@labinfo.iet.unipi.it> Subject: new bridging code snap... To: net@FreeBSD.ORG Date: Fri, 28 Aug 1998 17:00:01 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have made some progress with the bridging code (the previous one was quite broken!) and the diffs wrt/ 2.2.6 or 2.2.7 are at http://www.iet.unipi.it/~luigi/bsd-bdg980828.diffs This version seems to work (tested) with the "ed", "de" and "lnc" drivers, plus i have patched (but untested for lack of hardware) the "ep" and "fxp" drivers as well. Just put "option BRIDGE" in your config file, and enable bridging with sysctl -w net.link.ether.bridge=1 (set to 0 to disable). Configure an IP address only on one of the ethernet interfaces. This code includes the bpf change i suggested earlier today, plus a fix to the "lnc" driver which panics dereferencing a null pointer if the if_start() routine is called without properly calling if_init() -- i am not sure why is this happens, and if it is the bridge code or the kernel bootp code. Known problems: * the bridge will only answer to ARP requests coming from the "main" interface (the one configured with an IP address). This will be fixed in the future. * the "de" driver at least with my card seems to become deaf when a cable problem occurs, and it needs a packet transmission to start listening again. I am not sure if it is a problem in the driver or in my card (media is 100baseTX) but this can cause temporary problems when you plug cables on and off. Have fun, provide feedback... cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Aug 29 19:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28381 for freebsd-net-outgoing; Sat, 29 Aug 1998 19:16:48 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from i.caniserv.com (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA28376 for ; Sat, 29 Aug 1998 19:16:45 -0700 (PDT) (envelope-from Darcy@ok-connect.com) Received: (qmail 3977 invoked from network); 30 Aug 1998 02:29:07 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 30 Aug 1998 02:29:07 -0000 Message-Id: <3.0.32.19980829191437.00ac31c0@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 29 Aug 1998 19:14:38 -0700 To: freebsd-net@FreeBSD.ORG From: Darcy Buskermolen Subject: 3COM 905B TX 10/100Mbit Ethernet card 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 looked at the supported NIC's list and I do not see this card, or am I just missing something. I have several here in the officer and I have excellent performance with them, I'm really in the market to see them sing in BSD. Anyway any information regarding this NIC would be great. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Aug 29 20:09:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03366 for freebsd-net-outgoing; Sat, 29 Aug 1998 20:09:44 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from soundgarden.cchem.berkeley.edu (soundgarden.CChem.Berkeley.EDU [128.32.50.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03361 for ; Sat, 29 Aug 1998 20:09:42 -0700 (PDT) (envelope-from msinatra@uclink4.berkeley.edu) Received: from k2.cchem.berkeley.edu (K2.CChem.Berkeley.EDU [128.32.50.68]) by soundgarden.cchem.berkeley.edu (8.9.1/8.9.1) with ESMTP id UAA15317; Sat, 29 Aug 1998 20:08:37 -0700 (PDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: msinatra@localhost Message-Id: In-Reply-To: <3.0.32.19980829191437.00ac31c0@mail.ok-connect.com> X-mailer: Eudora Pro 4.0.1 Macintosh Distribution: ucb Date: Sat, 29 Aug 1998 20:08:36 -0700 To: Darcy Buskermolen , freebsd-net@FreeBSD.ORG From: Michael Sinatra Subject: Re: 3COM 905B TX 10/100Mbit Ethernet card Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 7:14 PM -0700 8/29/98, Darcy Buskermolen wrote: >I've looked at the supported NIC's list and I do not see this card, or am I >just missing something. I have several here in the officer and I have >excellent performance with them, I'm really in the market to see them sing >in BSD. The xl driver has just been added to the STABLE and CURRENT sources. (In fact, right now there is a discussion about this over on the stable and current mailing lists.) I have been using this for about a week with my 905B and it works great. Remember that you will need to put 'device xl0' in the kernel config file, then rebuild the kernel. Reboot and you're set! +++ Michael Sinatra msinatra@uclin4.berkeley.edu unix systems administrator college of chemistry university of california berkeley, ca 94720-1460 (510) 643-1032 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message