From owner-freebsd-net Sun Jun 13 17: 7:26 1999 Delivered-To: freebsd-net@freebsd.org Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166]) by hub.freebsd.org (Postfix) with ESMTP id E405514EA2 for ; Sun, 13 Jun 1999 17:07:24 -0700 (PDT) (envelope-from stanb@awod.com) Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA097588841; Sun, 13 Jun 1999 20:07:21 -0400 Subject: Where can I get ncplib ? To: freebsd-net@FreeBSD.ORG Date: Sun, 13 Jun 1999 20:07:19 -0400 (EDT) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 659 Message-Id: <19990614000724.E405514EA2@hub.freebsd.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I saw the anouncement of a new version a week or so ago, and I thought I had saved the messae, but instead I saved a reply to it without the download address :-) So where do I get it please? -- Stan Brown stanb@netcom.com 843-745-3154 Westvaco Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jun 13 17:35:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by hub.freebsd.org (Postfix) with ESMTP id 609E314C35 for ; Sun, 13 Jun 1999 17:35:44 -0700 (PDT) (envelope-from alantrulock@erols.com) Received: from ALAN (209-122-199-241.s495.tnt4.lnh.md.dialup.rcn.com [209.122.199.241]) by smtp2.erols.com (8.8.8/8.8.5) with SMTP id UAA28648; Sun, 13 Jun 1999 20:38:53 -0400 (EDT) From: alantrulock@erols.com (Alan Trulock) To: "Stan Brown" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? Date: Mon, 14 Jun 1999 00:34:25 GMT Message-ID: <37664dfd.77645842@smtp.erols.com> References: <19990614000724.E405514EA2@hub.freebsd.org> In-Reply-To: <19990614000724.E405514EA2@hub.freebsd.org> 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 http://www.butya.kz/~bp/ On Sun, 13 Jun 1999 20:07:19 -0400 (EDT), you wrote: > I saw the anouncement of a new version a week or so ago, and I thought > I had saved the messae, but instead I saved a reply to it without the > download address :-) > > So where do I get it please? > >--=20 >Stan Brown stanb@netcom.com = 843-745-3154 >Westvaco >Charleston SC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jun 13 19:21:24 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 A5E9314E92 for ; Sun, 13 Jun 1999 19:21:23 -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 911722E20B; Sun, 13 Jun 1999 22:18:42 -0400 (EDT) Message-Id: <4.1.19990613222038.00b5edf0@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 13 Jun 1999 22:21:59 -0400 To: freebsd-net@FreeBSD.ORG From: Matthew Hagerty Subject: Problem with 3c562/563 PCMCIA LAN+33.6 PC Card 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 purchased a 3Com EtherLink III LAN+33.6 Modem PCMCIA card only to find that FreeBSD does not yet support the 3c562 controller. There was a post in hackers a day or two ago that mentioned the 3c562, it's subject line was: sysnewconfig990609-kld990609test8.7.patch.gz Does this patch give a 3.2-RELEASE support for the 3c562 controller? If so, is there any way I can get a boot floppy with this support so I can do a network install (I don't have a CD-ROM for my laptop). If there is no support for the 3c562, what would be a good driver for me to start with to write a driver? Also, where can one get a programmers guide to 3Com's NIC chipsets? Thanks you, Matthew Hagerty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jun 13 19:33:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by hub.freebsd.org (Postfix) with ESMTP id CC7E514BE2 for ; Sun, 13 Jun 1999 19:33:48 -0700 (PDT) (envelope-from alantrulock@erols.com) Received: from ALAN (209-122-199-241.s495.tnt4.lnh.md.dialup.rcn.com [209.122.199.241]) by smtp2.erols.com (8.8.8/8.8.5) with SMTP id WAA14279; Sun, 13 Jun 1999 22:37:02 -0400 (EDT) From: alantrulock@erols.com (Alan Trulock) To: "Jason L. Schwab" Cc: freebsd-net@FreeBSD.ORG Subject: Re: gateway. Date: Mon, 14 Jun 1999 02:32:13 GMT Message-ID: <3767694d.84639303@smtp.erols.com> References: In-Reply-To: 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 Without knowing more about your system, I would suggest taking a look here. http://www.freebsd.org/tutorials/ppp/ppp.html --Al On Sat, 12 Jun 1999 23:41:31 -0600 (MDT), you wrote: > > How can I have my windows 95/98 boxes use freebsd as there gateway, >I know how to tell them what server to gothro, but what do I need to do = on >the fbsd box.. i'm running the 3.2-stable branch....thanks > > > >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 Jun 13 20: 6:59 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 6745314C02 for ; Sun, 13 Jun 1999 20:06:58 -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 43A792E20B; Sun, 13 Jun 1999 23:04:17 -0400 (EDT) Message-Id: <4.1.19990613225624.009bdd70@mail.venux.net> X-Sender: mhagerty@mail.venux.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 13 Jun 1999 23:07:34 -0400 To: freebsd-net@freebsd.org From: Matthew Hagerty Subject: NATD, failed to write packet back, please help. 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 have had the error before but I was always able to find the problem (or blame the service provider). I have a cable modem, FreeBSD-3.1-RELEASE, and I am running NATD for my home network just fine. I set up a 3.2-RELEASE box for a friend with a cable modem (same provider) and when I bring the FreeBSD box online I get the dreaded "natd: failed to write packed back" error. I know the NIC is good because I used it to communicate on my network before connecting to my friends cable modem. I know the cable between the NIC and the cable modem is good because it is the same one my friend was using to connect his Win95 box to the cable modem. I know the cable modem is good because when we connect the Win95 box back to the modem the service works just fine. I configured this machine exactally the same way as I have mine. IPFIREWALL and IPDIVERT are in the custom kernel, gateway_enable="YES", NATD interface set correctly, the whole 9 yards. My friend and I are actually on the same leg for our service and only 7 IP addresses away from each other. We use the same defaultrouter and netmask. I don't understand what could be causing the FreeBSD box to not work. Any insight would be greatly appreciated. Thank you, Matthew Hagerty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 14 6:30:40 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 97E1B14DE2 for ; Mon, 14 Jun 1999 06:30:38 -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 AA081821805; Mon, 14 Jun 1999 05:16:45 -0400 Date: Mon, 14 Jun 1999 05:16:45 -0400 (EDT) From: Bill Fumerola To: Stan Brown Cc: freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? In-Reply-To: <19990614000724.E405514EA2@hub.freebsd.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 13 Jun 1999, Stan Brown wrote: > I saw the anouncement of a new version a week or so ago, and I thought > I had saved the messae, but instead I saved a reply to it without the > download address :-) > > So where do I get it please? The port has been updated. - 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 Jun 14 9:12:39 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 D607D14A12 for ; Mon, 14 Jun 1999 09:12:32 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10tZKr-000KvY-00; Mon, 14 Jun 1999 23:11:45 +0700 Date: Mon, 14 Jun 1999 23:11:45 +0700 (ALMST) From: Boris Popov To: Bill Fumerola Cc: Stan Brown , freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 14 Jun 1999, Bill Fumerola wrote: > > I saw the anouncement of a new version a week or so ago, and I thought > > I had saved the messae, but instead I saved a reply to it without the > > download address :-) > > > > So where do I get it please? > > The port has been updated. Whoops, I'm probably miss something :). There is no port for ncplib - Netware client, it is native FreeBSD package. But there is a port for Mars_nwe - Netware server emulator and it has been updated to version 0.99pl17. > > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - -- 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 Jun 14 9:14:46 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 C3CE314A12 for ; Mon, 14 Jun 1999 09:14:42 -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 AA137921654; Mon, 14 Jun 1999 08:00:54 -0400 Date: Mon, 14 Jun 1999 08:00:54 -0400 (EDT) From: Bill Fumerola To: Boris Popov Cc: Stan Brown , freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 14 Jun 1999, Boris Popov wrote: > Whoops, I'm probably miss something :). There is no port for > ncplib - Netware client, it is native FreeBSD package. But there is a port > for Mars_nwe - Netware server emulator and it has been updated to version > 0.99pl17. That's what I saw. Boris, why don't you look at http://www.FreeBSD.org/handbook/porting.html and make a port for ncplib so we can provide it as a FreeBSD package. Please? :> - 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 Jun 14 9:35:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 275C8153D7 for ; Mon, 14 Jun 1999 09:35:39 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id MAA17049; Mon, 14 Jun 1999 12:35:06 -0400 (EDT) Date: Mon, 14 Jun 1999 12:35:06 -0400 (EDT) From: "Matthew N. Dodd" To: Bill Fumerola Cc: Boris Popov , Stan Brown , freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 14 Jun 1999, Bill Fumerola wrote: > Boris, why don't you look at > http://www.FreeBSD.org/handbook/porting.html and make a port for > ncplib so we can provide it as a FreeBSD package. Please? :> At some point it would be better to bring ncplib into the tree so that FreeBSD can use it to install from a netware share. In addition, it might be enough of a carrot should we mention the lack of kernel SMB client support to Boris at some point in the future. Good job again Boris! -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 14 11: 8:58 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 0A5281564A; Mon, 14 Jun 1999 11:08:33 -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 RAA10029; Mon, 14 Jun 1999 17:39:55 +0200 From: Luigi Rizzo Message-Id: <199906141539.RAA10029@labinfo.iet.unipi.it> Subject: CfP: First Intl. Workshop on Networked Group Communication To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Mon, 14 Jun 1999 17:39:54 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1001 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear FreeBSD'ers, perhaps this might interest some of you so forgive me for the intrusion... cheers luigi ---- Just a brief reminder -- the deadline (July 1st) for submissions to the First International Workshop on Networked Group Communication (NGC99) http://www.iet.unipi.it/~luigi/ngc99/ is approaching. Please note that in addition to regular contributions we will also select a few "student contributions", authored by students only. See the online call for papers at the above URL for detailed info. 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 Mon Jun 14 20:17: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 95F1014E03 for ; Mon, 14 Jun 1999 20:16:42 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10tjhr-000LJO-00; Tue, 15 Jun 1999 10:16:11 +0700 Date: Tue, 15 Jun 1999 10:16:10 +0700 (ALMST) From: Boris Popov To: Bill Fumerola Cc: freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 14 Jun 1999, Bill Fumerola wrote: > On Mon, 14 Jun 1999, Boris Popov wrote: > > Boris, why don't you look at http://www.FreeBSD.org/handbook/porting.html Thanks, I'm already look at this nice document, otherwise how do I wrote and maintain a Mars_nwe port :) > and make a port for ncplib so we can provide it as a FreeBSD package. The only problem for writing a port for ncplib is that it requires /usr/src/sys directory for build. This can be avoided by including pregenerated versions of vnode_if.* files. They are depended from FreeBSD version and can be changed in future. So there is no easy way to build these files. If the templates /sys/kern/vnode_if.* will be copied to /usr/share/somewhere it will be very simple to write a port. Another problem is lack of ability to build a package, because kernel module should be builded in native environment. However if the port will check /usr/src/sys directory and complain if it's not found it will be possible to create package-less port. -- 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 Jun 14 20:29:20 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 4125B1512F for ; Mon, 14 Jun 1999 20:29:10 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10tjsv-000LKk-00; Tue, 15 Jun 1999 10:27:37 +0700 Date: Tue, 15 Jun 1999 10:27:37 +0700 (ALMST) From: Boris Popov To: "Matthew N. Dodd" Cc: Bill Fumerola , Stan Brown , freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 14 Jun 1999, Matthew N. Dodd wrote: > On Mon, 14 Jun 1999, Bill Fumerola wrote: > > Boris, why don't you look at > > http://www.FreeBSD.org/handbook/porting.html and make a port for > > ncplib so we can provide it as a FreeBSD package. Please? :> > > At some point it would be better to bring ncplib into the tree so that > FreeBSD can use it to install from a netware share. In addition, it might May be someone from core can determine if that expedient to include ncplib in source tree ? > be enough of a carrot should we mention the lack of kernel SMB client > support to Boris at some point in the future. Did you read my mind :)) About a month ago I'm start a work on readonly (yet) smbfs. -- 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 Jun 14 20:42:23 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 6546015428 for ; Mon, 14 Jun 1999 20:42:18 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id XAA26778; Mon, 14 Jun 1999 23:41:55 -0400 (EDT) Date: Mon, 14 Jun 1999 23:41:55 -0400 (EDT) From: "Matthew N. Dodd" To: Boris Popov Cc: Bill Fumerola , Stan Brown , freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 15 Jun 1999, Boris Popov wrote: > May be someone from core can determine if that expedient to include > ncplib in source tree ? NTFS seems to provide ample precedent no? What is needed is a willing committer. Asking -core to point out the slow committers wouldn't be a bad thing either. (slow as in the rest of them having the ability to evade you.) > > be enough of a carrot should we mention the lack of kernel SMB client > > support to Boris at some point in the future. > > Did you read my mind :)) About a month ago I'm start a work on > readonly (yet) smbfs. And to think the fools doubted my mind control lasers. 'Ware, 'ware, ye non-believers! (Actually, I have faith in Boris' ability to out-do himself when it comes to coding up random filesharing clients. I'm fully expecting that in a few years he'll present us with DECnet or Vines or something equally frightening. Not that I'm exagerating about the lasers.) So, where can we start testing this read only SMB client? :) Will this one be 'smblib'? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 14 22: 7:21 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 1227C15034 for ; Mon, 14 Jun 1999 22:07:10 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10tlQh-000LQc-00; Tue, 15 Jun 1999 12:06:35 +0700 Date: Tue, 15 Jun 1999 12:06:35 +0700 (ALMST) From: Boris Popov To: "Matthew N. Dodd" Cc: Bill Fumerola , Stan Brown , freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 14 Jun 1999, Matthew N. Dodd wrote: > > > be enough of a carrot should we mention the lack of kernel SMB client > > > support to Boris at some point in the future. > > > > Did you read my mind :)) About a month ago I'm start a work on > > readonly (yet) smbfs. > > And to think the fools doubted my mind control lasers. > > (Actually, I have faith in Boris' ability to out-do himself when it comes > to coding up random filesharing clients. I'm fully expecting that in a Not random, it depends on my needs. > few years he'll present us with DECnet or Vines or something equally Probably no. For write it I should have a reason and time to do so. > frightening. Not that I'm exagerating about the lasers.) > > So, where can we start testing this read only SMB client? :) Don't know, currently I'm have some problems with protocol implementation, but if there is interest I'll post msg to this list when fs become stable (it will support writes but not for paged IO). -- 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 Tue Jun 15 4:31:33 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 93D0714D2D for ; Tue, 15 Jun 1999 04:31:22 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10trR0-0000BK-00 for freebsd-net@freebsd.org; Tue, 15 Jun 1999 18:31:18 +0700 Date: Tue, 15 Jun 1999 18:31:18 +0700 (ALMST) From: Boris Popov To: freebsd-net@freebsd.org Subject: Multiple ethernet frames for IPX 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, Yes, it is really works now ;). This is first public release of if_ef driver which extends current functionality of existing ethernet drivers. Below I'm put a part of README file included in the distribution. If someone can review/test this work and give me any suggestions, critics or anything else I'm will be very grateful. URL of driver archive ftp://ftp.butya.kz/pub/ipx/ifef-1.0b0.tar.gz Ok, here is README: ----------------------------------------------------------------------- Multiple ethernet frame types support for FreeBSD. This document explains how it works and how to install this support. 1. Introduction =============== Traditional *BSD network architecture uses one 'raw' ethernet device to support all frame types. This makes known problems when one protocol should be bound to a number of different frame types. The most significant problem is a routing, because routes based on interface number and even if we receive all frames and pass them to protocol input routine it will be problematical to pass packets back to appropriate frame type. This can be solved in a number of ways: 1. Rewrite all of the protocols in order to distinguish frame type, 2. Rewrite an ethernet driver (in which way ?), 3. Add support for frame type into struct ifaddr definition, 4. Write a pseudo ethernet driver to split up a single ethernet into multiple devices and each of them should represent single frame type, 5. add others by taste. After playing with differents variants I have found that writing pseudo ethernet driver is a most (from my point of view) convenient. 2. Design ========= At first, we should select an appropriate device naming convention. This also can be done in a number of ways and determined by reasonable balance between easy to understand device names and a number of code to be rewriting. So, I select next scheme: ed0 - traditinal ethernet device, ed0f0 - Ethernet_II frame device, ed0f1 - Ethernet_802.3 frame, ed0f2 - Ethernet_802.2 frame and ed0f3 - Ethernet_SNAP frame. As follows from the above, in the new scheme device unit number represents one of the frame type. This is easy to implement and reqires very little changes to existing kernel code (in particular adding few lines to ifunit() routine). Behaviour of each of ed0f* device should be close to underlying ethernet device. This is also can be easy achieved with number of caveats. After that, it should be easy to configure multiple frame types for a single protocol on single 'raw' device: ifconfig ed0f0 ipx 0x102 - configure IPX network 102 on ethernet_II, ifconfig ed0f1 ipx 0x101 - configure IPX network 101 on ethernet_802.3 etc... Since interfaces are different all routing mechanism should work as expected and require no intervention into the protocol stack implementation. 3. Implementation ================= Well, this was a mostly theoretical issues. In my first implementation of this technology all code was builtin in kernel, but it is possible to move most of the code to KLD module. While loading this module scans all ethernet devices and clones them with different names: deviceUNIT becomes deviceUNITfUNIT After loading all new devices can be configured as usual and old 'raw' device still continues to work without any problems. Currently support is limited only to IPX protocol, but it could be very easy to extend each frame to support other protocol types (you should know how particular protocol incaspulated into given frame type). Here is a sample ifconfig output from our production server machine: ed2: flags=8843 mtu 1500 ether 00:40:95:00:22:fa ed2f0: flags=8843 mtu 1500 ipx 101H.40950022fa ether 00:40:95:00:22:fa ed2f1: flags=8843 mtu 1500 ipx 9da8aa54.40950022fa ether 00:40:95:00:22:fa ed2f2: flags=8842 mtu 1500 ether 00:40:95:00:22:fa ed2f3: flags=8842 mtu 1500 ether 00:40:95:00:22:fa -- 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 Tue Jun 15 6:10:35 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 2BEF4150C4 for ; Tue, 15 Jun 1999 06:10:32 -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 AA263907010; Tue, 15 Jun 1999 04:56:50 -0400 Date: Tue, 15 Jun 1999 04:56:50 -0400 (EDT) From: Bill Fumerola To: Boris Popov Cc: freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 15 Jun 1999, Boris Popov wrote: > > Boris, why don't you look at http://www.FreeBSD.org/handbook/porting.html > > Thanks, I'm already look at this nice document, otherwise how do I > wrote and maintain a Mars_nwe port :) Sorry, didn't know. I was trying to head off questions before they were asked. :> > > and make a port for ncplib so we can provide it as a FreeBSD package. > > The only problem for writing a port for ncplib is that it requires > /usr/src/sys directory for build. This can be avoided by including > pregenerated versions of vnode_if.* files. They are depended from FreeBSD > version and can be changed in future. So there is no easy way to build > these files. If the templates /sys/kern/vnode_if.* will be copied to > /usr/share/somewhere it will be very simple to write a port. Another > problem is lack of ability to build a package, because kernel module > should be builded in native environment. > > However if the port will check /usr/src/sys directory and complain > if it's not found it will be possible to create package-less port. Well, there are ports that do depend on /usr/src existing already in the tree. Anything that could help people get access to the program quickly (even if it's a port but can't be generated as a package) would be nice. - 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 Tue Jun 15 7:10:20 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 AC85814EFC for ; Tue, 15 Jun 1999 07:10:08 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10ttuR-0000Md-00; Tue, 15 Jun 1999 21:09:51 +0700 Date: Tue, 15 Jun 1999 21:09:51 +0700 (ALMST) From: Boris Popov To: Bill Fumerola Cc: freebsd-net@FreeBSD.ORG Subject: Re: Where can I get ncplib ? 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, 15 Jun 1999, Bill Fumerola wrote: > > However if the port will check /usr/src/sys directory and complain > > if it's not found it will be possible to create package-less port. > > Well, there are ports that do depend on /usr/src existing already in the > tree. > > Anything that could help people get access to the program quickly (even if > it's a port but can't be generated as a package) would be nice. Ok, I'll look into this. -- 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 Tue Jun 15 13:30:52 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 037EA14F56 for ; Tue, 15 Jun 1999 13:30:39 -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 NAA56337; Tue, 15 Jun 1999 13:30:20 -0700 (PDT) Date: Tue, 15 Jun 1999 13:30:19 -0700 (PDT) From: Julian Elischer To: Boris Popov Cc: freebsd-net@FreeBSD.ORG Subject: Re: Multiple ethernet frames for IPX 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, 15 Jun 1999, Boris Popov wrote: > Hello, > > Yes, it is really works now ;). This is first public release of > if_ef driver which extends current functionality of existing ethernet > drivers. [...] most cool work. I don't know if this is how we will finally solve this problem, (we might well do so), but even if we don't this is a very good step in this direction. I wonder if this can be generalised within the framework of interfaces, to be less specific to ethernet.. There are other types of interfaces that have sub-interfaces.. e.g. ATM, Frame relay, VLAN (I think) etc. It looks to me as if we might consider what can be generalised and extracted from these examples. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 15 18:21: 7 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 2D2B015203 for ; Tue, 15 Jun 1999 18:20:59 -0700 (PDT) (envelope-from justin@walker3.apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out2.apple.com (8.8.5/8.8.5) with ESMTP id SAA49294 for ; Tue, 15 Jun 1999 18:20:59 -0700 Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (mailgate2.apple.com- SMTPRS 2.0.15) with ESMTP id for ; Tue, 15 Jun 1999 18:20:51 -0700 Received: from walker3.apple.com (walker3.apple.com [17.219.24.201]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id SAA26288 for ; Tue, 15 Jun 1999 18:20:50 -0700 Received: by walker3.apple.com (8.9.1/8.9.1) id SAA00645 for freebsd-net@FreeBSD.ORG; Tue, 15 Jun 1999 18:20:57 -0700 (PDT) Message-Id: <199906160120.SAA00645@walker3.apple.com> To: freebsd-net@freebsd.org Subject: Re: Multiple ethernet frames for IPX Date: Tue, 15 Jun 1999 18:20:51 -0700 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: Boris Popov > Date: 1999-06-15 04:31:38 -0700 > To: freebsd-net@FreeBSD.ORG > Subject: Multiple ethernet frames for IPX > Delivered-to: freebsd-net@freebsd.org > X-Loop: FreeBSD.org > > Hello, > > Yes, it is really works now. This is first public release of > if_ef driver which extends current functionality of existing ethernet > drivers. > > Below I'm put a part of README file included in the distribution. > If someone can review/test this work and give me any suggestions, critics > or anything else I'm will be very grateful. > > URL of driver archive > ftp://ftp.butya.kz/pub/ipx/ifef-1.0b0.tar.gz > > Ok, here is README: I have a couple of questions: How does this handle the problem of getting a forwarded packet back into the wrapper it needs (e.g., 802.3/SNAP)? Why is this better than, e.g., having stacks register for packet-type reception? I'd think this would perform better than the "virtual device" scheme. A (minor?) drawback is updating both stack and "driver family support" (e.g., ether_input()) to handle this. Thanks, 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 Tue Jun 15 19:16:31 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 564BA152A7 for ; Tue, 15 Jun 1999 19:16:23 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10u5FG-0003N4-00; Wed, 16 Jun 1999 09:16:06 +0700 Date: Wed, 16 Jun 1999 09:16:05 +0700 (ALMST) From: Boris Popov To: Julian Elischer Cc: freebsd-net@FreeBSD.ORG Subject: Re: Multiple ethernet frames for IPX 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, 15 Jun 1999, Julian Elischer wrote: > > Yes, it is really works now ;). This is first public release of > > if_ef driver which extends current functionality of existing ethernet > > drivers. > > I don't know if this is how we will finally solve this problem, (we might > well do so), but even if we don't this is a very good step in this > direction. I wonder if this can be generalised within the framework of > interfaces, to be less specific to ethernet.. > > There are other types of interfaces that have sub-interfaces.. e.g. ATM, > Frame relay, VLAN (I think) etc. > It looks to me as if we might consider what can be generalised and > extracted from these examples. I tried to keep kernel changes minimal. At my home machine next functionality is implemented: ifconfig ed0 frame 8023 ifconfig ed0f1 ipx 0x101 ... long time passed ... ifconfig ed0f1 ipx 0x101 delete ifconfig ed0 frame 8023 delete First statement creates clone from the ed0 interface and second uses it. Last command works, but interface detaching isn't supported under FreeBDS. This ideology suits for all types of the interfaces, but requires significant changes to ifconfig and *_ioctl() routines. > > julian -- 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 Tue Jun 15 19:28:20 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 155C8151A2 for ; Tue, 15 Jun 1999 19:28:09 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10u5Qi-0003NQ-00; Wed, 16 Jun 1999 09:27:56 +0700 Date: Wed, 16 Jun 1999 09:27:56 +0700 (ALMST) From: Boris Popov To: "Justin C. Walker" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906160120.SAA00645@walker3.apple.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, 15 Jun 1999, Justin C. Walker wrote: > > Yes, it is really works now. This is first public release of > > if_ef driver which extends current functionality of existing ethernet > > drivers. > > I have a couple of questions: > > How does this handle the problem of getting a forwarded packet back > into the wrapper it needs (e.g., 802.3/SNAP)? Packet sended/forwarded to interface. Since frame type determined from the interface it is not a problem for ether_output() rotine to select appropriate frame to wrap in. > > Why is this better than, e.g., having stacks register for > packet-type reception? I'd think this would perform better than the > "virtual device" scheme. A (minor?) drawback is updating both stack > and "driver family support" (e.g., ether_input()) to handle this. No, you will also need to rewrite route* procedures. And changes required to protocol stack(s) aren't "minor" in this case. -- 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 Tue Jun 15 20:51:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id C172E153AA for ; Tue, 15 Jun 1999 20:51:54 -0700 (PDT) (envelope-from justin@walker3.apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id UAA22468 for ; Tue, 15 Jun 1999 20:51:54 -0700 Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (mailgate2.apple.com- SMTPRS 2.0.15) with ESMTP id for ; Tue, 15 Jun 1999 20:51:47 -0700 Received: from walker3.apple.com (walker3.apple.com [17.219.24.201]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id UAA15080 for ; Tue, 15 Jun 1999 20:51:44 -0700 Received: by walker3.apple.com (8.9.1/8.9.1) id UAA00707 for freebsd-net@FreeBSD.ORG; Tue, 15 Jun 1999 20:51:40 -0700 (PDT) Message-Id: <199906160351.UAA00707@walker3.apple.com> To: freebsd-net@freebsd.org Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906160120.SAA00645@walker3.apple.com> Date: Tue, 15 Jun 1999 20:51:33 -0700 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 Boris, Thanks for the response; I have a few more questions: > From: Boris Popov > Date: 1999-06-15 19:28:08 -0700 > To: "Justin C. Walker" > Subject: Re: Multiple ethernet frames for IPX > Cc: freebsd-net@FreeBSD.ORG > In-reply-to: <199906160120.SAA00645@walker3.apple.com> > > On Tue, 15 Jun 1999, Justin C. Walker wrote: > > > > Yes, it is really works now. This is first public release of > > > if_ef driver which extends current functionality of existing ethernet > > > drivers. > > > > I have a couple of questions: > > > > How does this handle the problem of getting a forwarded packet back > > into the wrapper it needs (e.g., 802.3/SNAP)? > > Packet sended/forwarded to interface. Since frame type > determined from the interface it is not a problem for ether_output() > rotine to select appropriate frame to wrap in. I should be clearer. What I meant to ask is: given that you have a packet in the routing layer to forward, and that its incoming framing has been stripped, how does the routing layer decide what framing (E-II, 802.3/SNAP, ..) to use when sending it? > > Why is this better than, e.g., having stacks register for > > packet-type reception? I'd think this would perform better than the > > "virtual device" scheme. A (minor?) drawback is updating both stack > > and "driver family support" (e.g., ether_input()) to handle this. > > No, you will also need to rewrite route* procedures. And changes > required to protocol stack(s) aren't "minor" in this case. I don't understand this. If the route* procedures need rewriting in this case, why not in the "virtual device" case? Also, I don't see why the stack changes are a big deal. For each configured interface, the stack has to "register", which can be handled in the same "piece" of the stack that deals, e.g., with ARP and addressing issues. I'm trying to get a better handle on the issues, since we're trying to deal with this at Apple now. Thanks, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | When crypto is outlawed, Apple Computer, Inc. | Only outlaws will have crypto. 2 Infinite Loop | 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 Tue Jun 15 21:28:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from aludra.usc.edu (aludra.usc.edu [128.125.253.184]) by hub.freebsd.org (Postfix) with ESMTP id BA718150F6 for ; Tue, 15 Jun 1999 21:28:17 -0700 (PDT) (envelope-from grahamph@scf.usc.edu) Received: (from grahamph@localhost) by aludra.usc.edu (8.8.8/8.8.8/usc) id VAA29868 for freebsd-net@freeBSD.ORG; Tue, 15 Jun 1999 21:28:16 -0700 (PDT) From: Graham Phillips Message-Id: <199906160428.VAA29868@aludra.usc.edu> Subject: TCP debugging question To: freebsd-net@freeBSD.ORG Date: Tue, 15 Jun 1999 21:28:16 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I notice that the function tcp_trace (in tcp_debug.c) writes trace data to a kernel buffer. Is it possible for a user-process to extract this information from the buffer? If so, how does one do it? Thanks --Graham Phillips To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 15 22:20:34 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 4442A155BB for ; Tue, 15 Jun 1999 22:20:25 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10u87A-0003g1-00; Wed, 16 Jun 1999 12:19:56 +0700 Date: Wed, 16 Jun 1999 12:19:56 +0700 (ALMST) From: Boris Popov To: "Justin C. Walker" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906160351.UAA00707@walker3.apple.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, 15 Jun 1999, Justin C. Walker wrote: > Thanks for the response; I have a few more questions: > > > > How does this handle the problem of getting a forwarded packet back > > > into the wrapper it needs (e.g., 802.3/SNAP)? > > > > Packet sended/forwarded to interface. Since frame type > > determined from the interface it is not a problem for ether_output() > > rotine to select appropriate frame to wrap in. > I should be clearer. What I meant to ask is: given that you have > a packet in the routing layer to forward, and that its incoming > framing has been stripped, how does the routing layer decide what > framing (E-II, 802.3/SNAP, ..) to use when sending it? In case of IPX protocol you have network numbers as a routing and forwarding criteria, and since one frame have only one corresponding network number it is easy to select outgoing interface. If host have no direct connection to destination network it will use routing entries gathered from RIP packets. So, it doesn't matter which frame type was on incoming packet. As a special case consider routing between different frame types on a single ethernet segment. > > > > Why is this better than, e.g., having stacks register for > > > packet-type reception? I'd think this would perform better than > the > > > "virtual device" scheme. A (minor?) drawback is updating both > stack > > > and "driver family support" (e.g., ether_input()) to handle this. > > > > No, you will also need to rewrite route* procedures. And changes > > required to protocol stack(s) aren't "minor" in this case. > I don't understand this. If the route* procedures need rewriting > in this case, why not in the "virtual device" case? Because route includes destination interface and only virtual interface knows about frames. > Also, I don't see why the stack changes are a big deal. For each > configured interface, the stack has to "register", which can be > handled in the same "piece" of the stack that deals, e.g., with ARP > and addressing issues. May be this will be reasonable when you'll redesign stack/interface framework to include frames support. But as follows from README file I have tried to keep minimal changes to kernel files. -- 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 Wed Jun 16 1:33:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from verify.ipc.ru (mag.ipc.ru [195.133.114.68]) by hub.freebsd.org (Postfix) with ESMTP id A0E2214CFE for ; Wed, 16 Jun 1999 01:33:27 -0700 (PDT) (envelope-from mag@ipc.ru) Received: from ipc.ru (localhost [127.0.0.1]) by verify.ipc.ru (8.9.3/8.9.2) with ESMTP id LAA01343 for ; Wed, 16 Jun 1999 11:40:20 +0400 (MSD) (envelope-from mag@ipc.ru) Message-ID: <376754E3.66E6080@ipc.ru> Date: Wed, 16 Jun 1999 11:40:19 +0400 From: "Alexey G. Misurenko" Reply-To: mag@ipc.ru X-Mailer: Mozilla 4.5 [ru] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: telnet library Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Did any body know C library to programming telnet clinet minimal of features is struct telnet{ raddr, user, pass }; send (telnet* , char*); recv (telnet* , char*); 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 Wed Jun 16 7:51:17 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 1D4CA1523D for ; Wed, 16 Jun 1999 07:51:12 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 28125 invoked by uid 1001); 16 Jun 1999 14:51:10 -0000 Date: Wed, 16 Jun 1999 10:51:10 -0400 From: Brian Reichert To: freebsd-net@freebsd.org Subject: Re: telnet library Message-ID: <19990616105110.D23025@numachi.com> References: <376754E3.66E6080@ipc.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <376754E3.66E6080@ipc.ru>; from Alexey G. Misurenko on Wed, Jun 16, 1999 at 11:40:19AM +0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jun 16, 1999 at 11:40:19AM +0400, Alexey G. Misurenko wrote: > Hello! > > Did any body know C library to programming > telnet clinet > > minimal of features is > > struct telnet{ > raddr, > user, > pass > }; > > send (telnet* , char*); > recv (telnet* , char*); Not directly., that I'm aware of. I made a doctored version of telnet, that I could call as a subroutine. Not graceful, but I was trying to retain all of the command-mode features. I could dregde up the code if you want. Why must it be _telnet_, precisely? If you are connecting to a telnet server specifically, I could see that, but otherwise you can just talk through a fairly raw socket... > WBR, Alexey G. Misurenko > p.s. Sorry for my badly english No problem. :) You should see me before I've had coffee... > -- > ************************************************* > * 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 -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Current daytime number: (603)-434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 9: 2:46 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 1986E15216 for ; Wed, 16 Jun 1999 09:02:39 -0700 (PDT) (envelope-from justin@walker3.apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id JAA54724 for ; Wed, 16 Jun 1999 09:02:37 -0700 Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (mailgate2.apple.com- SMTPRS 2.0.15) with ESMTP id for ; Wed, 16 Jun 1999 09:02:29 -0700 Received: from walker3.apple.com (walker3.apple.com [17.219.24.201]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id JAA26174 for ; Wed, 16 Jun 1999 09:02:28 -0700 Received: by walker3.apple.com (8.9.1/8.9.1) id JAA00643 for freebsd-net@FreeBSD.ORG; Wed, 16 Jun 1999 09:02:35 -0700 (PDT) Message-Id: <199906161602.JAA00643@walker3.apple.com> To: freebsd-net@freebsd.org Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906160351.UAA00707@walker3.apple.com> Date: Wed, 16 Jun 1999 09:02:28 -0700 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 Hmmm... > From: Boris Popov > Date: 1999-06-15 22:20:36 -0700 > To: "Justin C. Walker" > Subject: Re: Multiple ethernet frames for IPX > Cc: freebsd-net@FreeBSD.ORG > In-reply-to: <199906160351.UAA00707@walker3.apple.com> > Delivered-to: freebsd-net@freebsd.org > X-Loop: FreeBSD.org > > On Tue, 15 Jun 1999, Justin C. Walker wrote: > > > Thanks for the response; I have a few more questions: > > > > > > How does this handle the problem of getting a forwarded packet back > > > > into the wrapper it needs (e.g., 802.3/SNAP)? > > > > > > Packet sended/forwarded to interface. Since frame type > > > determined from the interface it is not a problem for ether_output() > > > rotine to select appropriate frame to wrap in. > > I should be clearer. What I meant to ask is: given that you have > > a packet in the routing layer to forward, and that its incoming > > framing has been stripped, how does the routing layer decide what > > framing (E-II, 802.3/SNAP, ..) to use when sending it? > > In case of IPX protocol you have network numbers as a routing and > forwarding criteria, and since one frame have only one corresponding > network number it is easy to select outgoing interface. If host have no > direct connection to destination network it will use routing entries > gathered from RIP packets. So, it doesn't matter which frame type was on > incoming packet. As a special case consider routing between different > frame types on a single ethernet segment. I understand how routing works. What I'm missing is how the sending host (whether originator or forwarder) decides how to encapsulate a frame, i.e., in your case, how to chose which virtual device to use. Is it the case that the network number determines the encapsulation? Is ARP used, and if so, does the ARP reply dictate how to encapsulate? I never bothered to figure out the answers to these questions for IP (which can be encapsulated in E-2 or 802.3/SNAP). > > > > > Why is this better than, e.g., having stacks register for > > > > packet-type reception? I'd think this would perform better than > > the > > > > "virtual device" scheme. A (minor?) drawback is updating both > > stack > > > > and "driver family support" (e.g., ether_input()) to handle this. > > > > > > No, you will also need to rewrite route* procedures. And changes > > > required to protocol stack(s) aren't "minor" in this case. > > I don't understand this. If the route* procedures need rewriting > > in this case, why not in the "virtual device" case? > > Because route includes destination interface and only virtual > interface knows about frames. I guess this is an answer to the question: network numbers determine encapsulation. Is that true? Thanks for the clarification. 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 Wed Jun 16 9: 3:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from ppd00021.deutschepost.de (unknown [149.239.160.21]) by hub.freebsd.org (Postfix) with ESMTP id CAA7115460 for ; Wed, 16 Jun 1999 09:03:44 -0700 (PDT) (envelope-from M.Kurmies@deutschepost.de) Received: from ddaah016.dd.postag.de (DDAAH016.deutschepost.de [160.58.1.16]) by ppd00021.deutschepost.de (8.9.3/8.9.3) with ESMTP id SAA05088 for ; Wed, 16 Jun 1999 18:03:44 +0200 (METDST) Received: from ddaah014.dd.postag.de (unverified) by ddaah016.dd.postag.de (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Mi, 16 Jun 1999 17:57:54 +0200 Message-Id: Received: by DDAAH014.DeutschePost.de with Internet Mail Service (5.5.2448.0) id ; Wed, 16 Jun 1999 18:03:19 +0200 From: "Kurmies, K100, KTZ DA" To: "'freebsd-net@FreeBSD.ORG'" Subject: Date: Wed, 16 Jun 1999 18:03:33 +0200 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth ba9bd1a3 unsubscribe freebsd-net M.Paepcke@deutschepost.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 9:19:42 1999 Delivered-To: freebsd-net@freebsd.org Received: from ppd00021.deutschepost.de (unknown [149.239.160.21]) by hub.freebsd.org (Postfix) with ESMTP id D598315460 for ; Wed, 16 Jun 1999 09:19:34 -0700 (PDT) (envelope-from M.Kurmies@deutschepost.de) Received: from ddaah016.dd.postag.de (DDAAH016.deutschepost.de [160.58.1.16]) by ppd00021.deutschepost.de (8.9.3/8.9.3) with ESMTP id SAA06833 for ; Wed, 16 Jun 1999 18:19:34 +0200 (METDST) Received: from ddaah014.dd.postag.de (unverified) by ddaah016.dd.postag.de (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Mi, 16 Jun 1999 18:13:42 +0200 Message-Id: Received: by DDAAH014.DeutschePost.de with Internet Mail Service (5.5.2448.0) id ; Wed, 16 Jun 1999 18:19:07 +0200 From: "Kurmies, K100, KTZ DA" To: "'freebsd-net@FreeBSD.ORG'" Subject: Date: Wed, 16 Jun 1999 18:19:21 +0200 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth ba9bd1a3 unsubscribe freebsd-net M.Paepcke@deutschepost.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 9:23:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from ppd00021.deutschepost.de (unknown [149.239.160.21]) by hub.freebsd.org (Postfix) with ESMTP id 0112915460 for ; Wed, 16 Jun 1999 09:23:26 -0700 (PDT) (envelope-from M.Kurmies@deutschepost.de) Received: from ddaah016.dd.postag.de (DDAAH016.deutschepost.de [160.58.1.16]) by ppd00021.deutschepost.de (8.9.3/8.9.3) with ESMTP id SAA07447 for ; Wed, 16 Jun 1999 18:23:25 +0200 (METDST) Received: from ddaah014.dd.postag.de (unverified) by ddaah016.dd.postag.de (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Mi, 16 Jun 1999 18:17:32 +0200 Message-Id: Received: by DDAAH014.DeutschePost.de with Internet Mail Service (5.5.2448.0) id ; Wed, 16 Jun 1999 18:22:58 +0200 From: "Kurmies, K100, KTZ DA" To: "'freebsd-net@FreeBSD.ORG'" Subject: Date: Wed, 16 Jun 1999 18:22:46 +0200 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth ba9bd1a3 unsubscribe freebsd-net M.Paepcke@deutschepost.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 9:33:25 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 C432614F53 for ; Wed, 16 Jun 1999 09:33:18 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10uIcc-0004TO-00; Wed, 16 Jun 1999 23:33:06 +0700 Date: Wed, 16 Jun 1999 23:33:06 +0700 (ALMST) From: Boris Popov To: "Justin C. Walker" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906161602.JAA00643@walker3.apple.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, 16 Jun 1999, Justin C. Walker wrote: > > In case of IPX protocol you have network numbers as a routing and > > forwarding criteria, and since one frame have only one corresponding > > network number it is easy to select outgoing interface. If host have no > > direct connection to destination network it will use routing entries > > gathered from RIP packets. So, it doesn't matter which frame type > was on > > incoming packet. As a special case consider routing between different > > frame types on a single ethernet segment. > I understand how routing works. What I'm missing is how the > sending host (whether originator or forwarder) decides how to > encapsulate a frame, i.e., in your case, how to chose which virtual > device to use. Is it the case that the network number determines the > encapsulation? Is ARP used, and if so, does the ARP reply dictate > how to encapsulate? I'm playing with IP now (and don't like how arp subroutines create packets) so can spoke only for IPX. And yes, you are right - network number determines outgoing interface and, therefore - encapsulation. -- 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 Wed Jun 16 10:14:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id E45F414CEA for ; Wed, 16 Jun 1999 10:14:09 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id TAA13003; Wed, 16 Jun 1999 19:14:17 +0200 (CEST) To: Graham Phillips Cc: freebsd-net@FreeBSD.ORG Subject: Re: TCP debugging question References: <199906160428.VAA29868@aludra.usc.edu> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 16 Jun 1999 19:14:17 +0200 In-Reply-To: Graham Phillips's message of "Tue, 15 Jun 1999 21:28:16 -0700 (PDT)" Message-ID: <5laeu0kqza.fsf@assaris.sics.se> Lines: 7 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Graham Phillips writes: > Is it possible for a user-process to extract this information > from the buffer? If so, how does one do it? trpt(8) /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 11:47:35 1999 Delivered-To: freebsd-net@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id C8D911556F for ; Wed, 16 Jun 1999 11:47:32 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id NAA10349 for freebsd-net@freebsd.org; Wed, 16 Jun 1999 13:47:31 -0500 (CDT) Date: Wed, 16 Jun 1999 13:47:31 -0500 From: Tim Tsai To: freebsd-net@freebsd.org Subject: fast transmit, slow receive? Message-ID: <19990616134731.A10074@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have a machine that is fast when we initiate an FTP transfer to another machine but is VERY slow to receive it (a few KB per second on). All the machines are running 2.2.8-STABLE (around February) with Intel fxp0 cards on an Intel switch. I am not seeing any collisions or any other problems that I can tell. Any suggestions on where to start to find this problem? 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 Jun 16 13:24:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.eliancecorp.com (mail.eliancecorp.com [204.73.214.40]) by hub.freebsd.org (Postfix) with ESMTP id A477F14CEB for ; Wed, 16 Jun 1999 13:24:12 -0700 (PDT) (envelope-from guy.gustavson@eliancecorp.com) Received: from ggustavson (ggustavson.eliancecorp.com [204.73.212.24]) by mail.eliancecorp.com (8.9.3/8.9.3) with SMTP id PAA10122 for ; Wed, 16 Jun 1999 15:24:43 -0500 Message-ID: <00de01beb836$30e1c600$18d449cc@eliancecorp.com> From: "Guy W. Gustavson" To: Subject: multiple nics with different IP's on same subnet Date: Wed, 16 Jun 1999 15:24:09 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DB_01BEB80C.47E28B20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_00DB_01BEB80C.47E28B20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've got a server hosting pages for about 100 domains. They are all low = enough traffic that the box can easily handle the load, but the IP = aliasing is getting tricky. After about 80 IP's on the same NIC the IP = stack stops responding and we have to reboot the box. Here's an example of how I'm aliasing the IP's, just repeat the ifconfig = and the route add's about 80 times. ifconfig ep0 inet 206.191.205.6 alias ifconfig ep0 inet 206.191.205.9 alias=20 route add 206.191.205.6 127.0.0.1 route add 206.191.205.8 127.0.0.1 We're building a new server anyway, and I was thinking of adding another = NIC and hosting half the IP's one NIC and half on the other. The box has = a class C to itself. Both NIC's would be on the same network, I could = put in a switch if needed. If I setup things like this. ifconfig ep0 inet 206.191.205.6 alias ifconfig ep1 inet 206.191.205.9 alias . . . with a default route of 206.191.205.254 I get all the traffic coming = back through one NIC and the usual ARP complaints... /kernel: arp: 206.191.205.6 is on ep0 but got reply from xx:xx:xx:xx on = ep1 Is there anyway to interleave the IP's between the two NIC's and still = have things route back from the same NIC it came from, and to get rid of = the ARP complaints? The above configuration basically works, other than the ARP complaints = and all the traffic coming back to one NIC. ------=_NextPart_000_00DB_01BEB80C.47E28B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've got a server hosting pages for = about 100=20 domains. They are all low enough traffic that the box can easily handle = the=20 load, but the IP aliasing is getting tricky.  After about 80 IP's = on the=20 same NIC the IP stack stops responding and we have to reboot the=20 box.
 
Here's an example of how I'm aliasing = the IP's,=20 just repeat the ifconfig and the route add's about 80 = times.
 
ifconfig ep0 inet 206.191.205.6 = alias
ifconfig=20 ep0 inet 206.191.205.9 alias 
route add 206.191.205.6 = 127.0.0.1
route add=20 206.191.205.8 127.0.0.1
 
We're building a new server anyway, and = I was=20 thinking of adding another NIC and hosting half the IP's one NIC and = half on the=20 other. The box has a class C to itself. Both NIC's would be on the same = network,=20 I could put in a switch if needed.
 
If I setup things like = this.
 
ifconfig ep0 inet 206.191.205.6 = alias
ifconfig ep1 inet 206.191.205.9 = alias
.
.
.
 
 
with a default route=20 of 206.191.205.254 I get all the traffic coming back through one NIC and = the=20 usual ARP complaints...
/kernel: arp: 206.191.205.6 is on ep0 = but got reply=20 from xx:xx:xx:xx on ep1
 
Is there anyway to interleave the = IP's between=20 the two NIC's and still have things route back from the same NIC it came = from,=20 and to get rid of the ARP complaints?
 
The above configuration basically = works, other than=20 the ARP complaints and all the traffic coming back to one = NIC.
 
------=_NextPart_000_00DB_01BEB80C.47E28B20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 15:32: 5 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 15AE014EDF for ; Wed, 16 Jun 1999 15:31:59 -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 PAA00461; Wed, 16 Jun 1999 15:31:50 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA00329; Wed, 16 Jun 1999 15:31:48 -0700 Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA09400; Wed, 16 Jun 99 15:31:46 PDT Message-Id: <376825D2.375AE37@softweyr.com> Date: Wed, 16 Jun 1999 16:31:46 -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: Brian Reichert Cc: freebsd-net@FreeBSD.ORG Subject: Re: telnet library References: <376754E3.66E6080@ipc.ru> <19990616105110.D23025@numachi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian Reichert wrote: > > On Wed, Jun 16, 1999 at 11:40:19AM +0400, Alexey G. Misurenko wrote: > > Hello! > > > > Did any body know C library to programming > > telnet clinet > > > > minimal of features is > > > > struct telnet{ > > raddr, > > user, > > pass > > }; > > > > send (telnet* , char*); > > recv (telnet* , char*); > > Not directly., that I'm aware of. I made a doctored version of > telnet, that I could call as a subroutine. Not graceful, but I > was trying to retain all of the command-mode features. I could > dregde up the code if you want. If you program in C++, you may want to look into the socket++ library. It's in ports/devel, and I think is in package form on the CD-ROM too. -- "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 Jun 16 16:49:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id DD7C914D66 for ; Wed, 16 Jun 1999 16:49:25 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id IAA10200; Thu, 17 Jun 1999 08:48:02 +0900 (JST) To: Sebastien Maraux Cc: freebsd-net@freebsd.org In-reply-to: smaraux's message of Tue, 08 Jun 1999 17:03:11 +0100. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: a _good_ IPv6 browser From: itojun@iijlab.net Date: Thu, 17 Jun 1999 08:48:02 +0900 Message-ID: <10198.929576882@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Mozilla 5 recompiled for IPv6 with kame patch does not match my wishes. >Should I use kame IPv6 release because I'm currently using the one from >the INRIA? >Does it really make a big difference? (sorry for delayed reply) could be. Because IPv6 API is still a moving target (RFC is issued though) there are many differences in implementations (both visible differences and invisible - kernel internal design - differences). You cannot assume that userland code for KAME kernel/library to work on INRIA kernel/library, or the other way around. This is quite unfortunate to say this, but in reality you need some patch.... itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 16 22:55: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from mailhost.mlnet.net (mailhost.mlnet.net [193.116.163.156]) by hub.freebsd.org (Postfix) with ESMTP id A3BDC14C59 for ; Wed, 16 Jun 1999 22:55:01 -0700 (PDT) (envelope-from M@mlnet.net) Received: (from postie@localhost) by mailhost.mlnet.net (8.8.8/8.8.8) id FAA16326; Thu, 17 Jun 1999 05:50:12 GMT Received: from ip57.medsoft.org(193.116.163.57) by mailhost.mlnet.net via smap (V1.3.ML.3) id sma016324; Thu Jun 17 05:50:05 1999 Received: (from postie@localhost) by newgate.home.ml-associates.co.uk (8.8.8/8.8.8) id FAA13149; Thu, 17 Jun 1999 05:48:37 GMT Message-Id: <199906170548.FAA13149@newgate.home.ml-associates.co.uk> Received: from oban(192.168.191.2) by newgate.home.ml-associates.co.uk via smap (V1.3.ML.3) id sma013147; Thu Jun 17 05:48:23 1999 X-Sender: msmith!home.ml-associates.co.uk@192.168.191.10 X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 17 Jun 1999 06:54:02 +0000 To: "Guy W. Gustavson" , From: Matthew Smithshaw Subject: Re: multiple nics with different IP's on same subnet Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If it is just Web virtual hosting, using Apache you could just use one IP address..... Only really old browsers will be unable to view the web sites. -M At 15:24 16/06/1999 -0500, Guy W. Gustavson wrote: >I've got a server hosting pages for about 100 domains. They are all low enough traffic that the box can easily handle the load, but the IP aliasing is getting tricky. After about 80 IP's on the same NIC the IP stack stops responding and we have to reboot the box. > >Here's an example of how I'm aliasing the IP's, just repeat the ifconfig and the route add's about 80 times. > >ifconfig ep0 inet 206.191.205.6 alias >ifconfig ep0 inet 206.191.205.9 alias >route add 206.191.205.6 127.0.0.1 >route add 206.191.205.8 127.0.0.1 > >We're building a new server anyway, and I was thinking of adding another NIC and hosting half the IP's one NIC and half on the other. The box has a class C to itself. Both NIC's would be on the same network, I could put in a switch if needed. > >If I setup things like this. > >ifconfig ep0 inet 206.191.205.6 alias >ifconfig ep1 inet 206.191.205.9 alias > > > -- Matthew Smithshaw | ML Associates M@UK.COM or M@mlnet.net | P O Box 16076 tel:+44-141-951-2229 | Glasgow Scotland fax:+44-141-951-8877 | G11 7TL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 17 17:54:20 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.rdc1.bc.home.com (ha1.rdc1.bc.wave.home.com [24.2.10.66]) by hub.freebsd.org (Postfix) with ESMTP id 5A7B314D0F for ; Thu, 17 Jun 1999 17:54:17 -0700 (PDT) (envelope-from pangolin@home.com) Received: from cr1003333-a.crdva1.bc.wave.home.com ([24.113.51.240]) by mail.rdc1.bc.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990618005416.RUKU6363.mail.rdc1.bc.home.com@cr1003333-a.crdva1.bc.wave.home.com> for ; Thu, 17 Jun 1999 17:54:16 -0700 Content-Length: 1088 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: Thu, 17 Jun 1999 17:54:16 -0700 (PDT) Reply-To: Jonathan Hanna Organization: Pangolin Systems From: Jonathan Hanna To: freebsd-net@freebsd.org Subject: natd, libalias, and PKT_ALIAS_REVERSE Message-Id: <19990618005416.RUKU6363.mail.rdc1.bc.home.com@cr1003333-a.crdva1.bc.wave.home.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I tried natd -reverse and got a core dump due to infinite recursion. alias.c in libalias has this rather amusing code: int PacketAliasIn(char *ptr, int maxpacketsize) { struct in_addr alias_addr; struct ip *pip; int iresult; if (packetAliasMode & PKT_ALIAS_REVERSE) return PacketAliasOut(ptr, maxpacketsize); ... int PacketAliasOut(char *ptr, /* valid IP packet */ int maxpacketsize /* How much the packet data may grow (FTP and IRC inline changes) */ ) { int iresult; struct in_addr addr_save; struct ip *pip; if (packetAliasMode & PKT_ALIAS_REVERSE) return PacketAliasIn(ptr, maxpacketsize); ... I noticed also that PKT_ALIAS_REVERSE is not documented int libalias.3. What I actually want do to is redirect connections from my internal network to a certain external host to an ssh port (on 127.0.0.1). What's a good way of doing this? This is on reasonably up to date current and 3.2 stable. Jonathan Hanna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jun 19 19: 8:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (Postfix) with ESMTP id 9660114BE5 for ; Sat, 19 Jun 1999 19:08:37 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id XAA02886; Sat, 19 Jun 1999 23:08:32 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199906200208.XAA02886@roma.coe.ufrj.br> Subject: Re: Multiple ethernet frames for IPX In-Reply-To: <199906161602.JAA00643@walker3.apple.com> from "Justin C. Walker" at "Jun 16, 1999 09:02:28 am" To: justin@apple.com Date: Sat, 19 Jun 1999 23:08:32 -0300 (EST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org #define quoting(Justin C. Walker) // I understand how routing works. What I'm missing is how the // sending host (whether originator or forwarder) decides how to // encapsulate a frame, i.e., in your case, how to chose which virtual // device to use. Is it the case that the network number determines the // encapsulation? Is ARP used, and if so, does the ARP reply dictate // how to encapsulate? Routing choses interface, interface defines frame. Just think of diferent packet frames as virtual networks, completely isolated from each other. If you need to share traffic, you must use a (one armed) router. // I never bothered to figure out the answers to these questions for // IP (which can be encapsulated in E-2 or 802.3/SNAP). If routing decides to send via E-2 interface, it will receive an E-2 frame, and vice-versa. Note that each frame should have its own subnet, completely independent from each other. // > interface knows about frames. // I guess this is an answer to the question: network numbers // determine encapsulation. Is that true? Yes. Jonny -- João Carlos Mendes Luís jonny@jonny.eng.br Networking Engineer jcml@ieee.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message