From owner-freebsd-isp Sun Jun 15 04:18:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA06135 for isp-outgoing; Sun, 15 Jun 1997 04:18:55 -0700 (PDT) Received: from ez.eznetwork.com ([206.149.144.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA06130 for ; Sun, 15 Jun 1997 04:18:54 -0700 (PDT) Received: from ericson.encs.com ([207.182.103.49]) by ez.eznetwork.com (8.6.12/8.6.12) with SMTP id TAA01308; Sun, 15 Jun 1997 19:22:08 -0700 Message-ID: <33A3CEB4.24D1@eznetwork.com> Date: Sun, 15 Jun 1997 04:15:00 -0700 From: Suk Tsang Reply-To: suk@eznetwork.com Organization: ENCS X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: dave@illumen.net CC: freebsd-isp@freebsd.org Subject: Re: Email store-and-forward + SMTP finger References: <339DB082.46D1@illumen.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dave Richards wrote: > > Hi All, > I've heard that sendmail can be configured to do store-and-forward of > email for people/orgs who have a mail server without a full time > internet connection. example: company with a mail server in-house and a > dialup ISDN line. I know POP3 could be used in a situation like this but > alot of folks are asking for store-and-forward these days. Is this > right? Does anyone know where to start? A search of the FreeBSD mailing > list archives turned a blank. > bah bah bah ... Let me point you in the right direction: Go to www.sendmail.org, under the FAQ, read the "Virtual Hosting ..." page, pick up just that part you want. Don't miss the "etrn.pl" thing, although the syntax shown there is incorrect. Check out the FreeBSD handbook, try the online one. Under "Electronic Mail: FAQ:How can I ... PPP host?", at the end of the outdated material there is a neat trick you may want to use. From owner-freebsd-isp Sun Jun 15 08:56:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA14825 for isp-outgoing; Sun, 15 Jun 1997 08:56:30 -0700 (PDT) Received: from obiwan.psinet.net.au (adrian@for.a.good.time.call.adrian.austnet.org [203.19.28.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14820 for ; Sun, 15 Jun 1997 08:56:25 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.psinet.net.au (8.8.5/8.8.5) with SMTP id XAA08601; Sun, 15 Jun 1997 23:34:38 +0800 (WST) Date: Sun, 15 Jun 1997 23:34:38 +0800 (WST) From: Adrian Chadd To: "Victor A. Sudakov" cc: isp@FreeBSD.ORG Subject: Re: PPP problems. In-Reply-To: <199706141334.VAA04717@vas.tomsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Jun 1997, Victor A. Sudakov wrote: > > If they get shitty about it.. stick the RFC in their face and say "read > > and adhere". If they choose not to.. Well theres the problem. It works > > with the majority of their users (ie Windows) so why should they change > > anything? > > > > Sad, isn't it. > > Yes, this is exactly what I am afraid of. The reason of my having started this > thread is that I am trying to understand if ISPs can prevent this from > happening. :) Well, basically in my eyes it boils down to this: * We (ISP's) are out to provide a service to people, and make money. * In order to make money we have to cater for the majority of the market, unless of course the minority want to pay us huge amounts of money :) * The majority of users use a Microsoft-based OS, so the ISP which caters for the Microsoft-based OS, no matter how whacky Microsoft twist TCP/IP, PPP, or whatever into.. will be making the most money. Guess what the business-smart person would do, without thinking "standards" ? It comes down to the fact that we have to keep compatibility to Windows clients. Having to maintain compatibility to them AND the REAL standard can and will become a pain in the arse. Get UNIX into the homes is what I say. Dress it up, make it easy to use, make it pretty, make it do what people want. Once its out there, and its gained some popularity, people WILL start writing more applications for it. If I actually got off my arse and completed my "desktop customisation", my mum could walk up to my FreeBSD/X machine, login with her username/password, be dumped to an X session (which would be running Openlook). There would be icons on the desktop and folders too (yes, people like them :) and one would be "StarWrite 3.0".. she'd double click that, and up would pop swrite3. That in itself is a very nice piece of software (albeit a TAD slow, but hey.. Word 7 is still worse) and when I started it up for her, she sat right down and typed her resume out from scratch. She didn't even ASK me for help :) Problem is.. none of us have any TIME. If someone was going to PAY me to pretty up an X environment, write nice configuration scripts, write that file-manager/icon stuff, I'd do it for sure. But, since the "free unix" is generally powered by people who are doing it in their spare time.. well I'm surprised its gotten as far as it has today. Now Jordan, if this isn't far away from FreeBSD-related talk, I don't know what is :) Seriously though, whats happening with the user-friendly install of FreeBSD? Adrian -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-isp Sun Jun 15 13:39:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA24760 for isp-outgoing; Sun, 15 Jun 1997 13:39:47 -0700 (PDT) Received: from december.real.net.au (root@december.real.net.au [203.25.56.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA24755 for ; Sun, 15 Jun 1997 13:39:43 -0700 (PDT) Received: from pyromaniac (www.kemenys.com.au [203.17.240.90]) by december.real.net.au (8.6.12/8.6.9) with SMTP id GAA12569; Mon, 16 Jun 1997 06:39:28 +1000 Message-Id: <3.0.1.32.19970616063930.00b433d0@pop.real.net.au> X-Sender: richard@pop.real.net.au X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 16 Jun 1997 06:39:30 +1000 To: dg@root.com From: Richard Laxton Subject: Re: Intel EtherExpress vs DEC PCI chipsets Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <199706100055.RAA02337@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David, Thanks that is good news. Especially since I can get the intel for $5 *less* than a no-name brand DEC card... wierd. Richard. At 17:55 9/06/97 -0700, David Greenman wrote: >>Secondly, Do I use Intel EtherExpress 100B TX cards or the DEC 240xx type >>cards? Does either have a CPU advantage? Are there any stability issues >>with either card? What are people's experiences? I have seen conflicting >>reports from this list ranging from "don't get the intel" to ftp.cdrom.com >>uses the intel (so it must be good). > > The Intel Pro/100B driver is much more CPU efficient than the DEC driver >and is well supported by the author (me). The only known problem at the moment >is that the newer Pro/100B's have a different PHY chip that the driver doesn't >yet know about and this results in full duplex operation not working with >those cards. This is a temporary situation, however, and will be fixed as soon >as I get one of the newer cards, the proper documentation, and my ethernet >switch working again. > >-DG > >David Greenman >Core-team/Principal Architect, The FreeBSD Project > > From owner-freebsd-isp Sun Jun 15 13:46:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA25097 for isp-outgoing; Sun, 15 Jun 1997 13:46:04 -0700 (PDT) Received: from december.real.net.au (root@december.real.net.au [203.25.56.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA25092 for ; Sun, 15 Jun 1997 13:46:01 -0700 (PDT) Received: from pyromaniac (www.kemenys.com.au [203.17.240.90]) by december.real.net.au (8.6.12/8.6.9) with SMTP id GAA12595 for ; Mon, 16 Jun 1997 06:45:55 +1000 Message-Id: <3.0.1.32.19970616064557.0094c3a0@pop.real.net.au> X-Sender: richard@pop.real.net.au X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 16 Jun 1997 06:45:57 +1000 To: freebsd-isp@FreeBSD.ORG From: Richard Laxton Subject: Re: large number of file handles open In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We ran into problems with Linux when we ran over about 125 virtual WWW servers on one machine because of Linux's static file limit of 255 files open. I just changed this limit and recompiled the Kernel and apache and things work perfectly. Are FreeBSD's file tables static like this or are they completely dynamic? Richard. At 13:56 10/06/97 -0700, Randy Katz wrote: >Sounds interesting, theory and all, but who in their right mind would put >500 virtual servers on one machine? Sounds crazy to me... And 1000 file >handles doesn't seem to be a problem for MOST Unixes. > >On Tue, 10 Jun 1997, Manar Hussain wrote: > >> I've heard one can hit problems with some unices running a large number of >> virtual servers (with say apache) with different log files for each virtual >> server: the problem being that with 500 virtual servers configured you have >> say 1000 file handles you'd want open to the log files. Does anyone know if >> this problem would occur with FreeBSD ??? >> >> Manar >> > > >RAK > >--------------------------------------------------------------------------- ---- >Randy A. Katz >Computer Consultation & Sales >505 S. Beverly Drive, Suite 472 Beverly Hills, CA 90212 >(213) 307-9581 http://www.ccsales.com >--------------------------------------------------------------------------- ---- > > From owner-freebsd-isp Sun Jun 15 14:37:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA27254 for isp-outgoing; Sun, 15 Jun 1997 14:37:52 -0700 (PDT) Received: from ijs.com (ijs.com [205.149.188.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA27248 for ; Sun, 15 Jun 1997 14:37:49 -0700 (PDT) From: jivko@ijs.com Received: (from jivko@localhost) by ijs.com (8.6.9/8.6.9) id OAA18826; Sun, 15 Jun 1997 14:34:08 -0700 Message-Id: <3.0.32.19970615143908.0094ecc0@ijs.com> X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 15 Jun 1997 14:39:12 -0700 To: Richard Laxton , freebsd-isp@FreeBSD.ORG Subject: Re: large number of file handles open Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 06:45 AM 6/16/97 +1000, Richard Laxton wrote: >We ran into problems with Linux when we ran over about 125 virtual WWW >servers on one machine because of Linux's static file limit of 255 files >open. I just changed this limit and recompiled the Kernel and apache and >things work perfectly. Are FreeBSD's file tables static like this or are >they completely dynamic? I think I have seen this in the FreeBSD FAQ. One needs to do the same - recompile the kernel. On another topic: Have any of you had any problems running FreeBSD on a COMPAQ machine (P133)? I discovered yesterday that FreeBSD 2.1. would not read the memory size properly and would use only 16MB on a COMPAQ machine with 72MB. Recompiling the kernel with the memory size took care of the problem, but I was wondering if it is just me or a typical problem with COMPAQ. Jivko Regards, Jivko Koltchev From owner-freebsd-isp Sun Jun 15 17:11:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA02141 for isp-outgoing; Sun, 15 Jun 1997 17:11:31 -0700 (PDT) Received: from train.tgci.com (train.tgci.com [205.185.169.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA02136 for ; Sun, 15 Jun 1997 17:11:29 -0700 (PDT) Received: from emilyd ([206.250.85.68]) by train.tgci.com (8.6.12/8.6.9) with SMTP id RAA07571; Sun, 15 Jun 1997 17:10:50 -0700 Message-Id: <199706160010.RAA07571@train.tgci.com> Comments: Authenticated sender is From: "Riley J. McIntire" To: Richard Laxton Date: Sun, 15 Jun 1997 17:11:07 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: large number of file handles open Reply-to: chaos@tgci.com CC: freebsd-isp@FreeBSD.ORG Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: jivko@ijs.com > At 06:45 AM 6/16/97 +1000, Richard Laxton wrote: [snip] > On another topic: Have any of you had any problems running FreeBSD on a > COMPAQ machine (P133)? I discovered yesterday that FreeBSD 2.1. would not > read the memory size properly and would use only 16MB on a COMPAQ machine > with 72MB. Recompiling the kernel with the memory size took care of the > problem, but I was wondering if it is just me or a typical problem with > COMPAQ. > > Jivko > Regards, > > Jivko Koltchev I don't have any hands on experience with fbsd/compaq but do recall a similar problem on a Compaq with, I think, 32 MB ram. Additionally, doesn't any fbsd machine require a recompile for >64 MB? Cheers, Riley From owner-freebsd-isp Sun Jun 15 17:44:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA03551 for isp-outgoing; Sun, 15 Jun 1997 17:44:43 -0700 (PDT) Received: from router.besys.net.au (border.besys.net.au [203.30.15.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03544 for ; Sun, 15 Jun 1997 17:44:37 -0700 (PDT) Received: from ingold.besys.net.au (Ingold@ingold.besys.net.au [203.30.15.130]) by router.besys.net.au (8.8.5/8.7.3) with SMTP id KAA17730; Mon, 16 Jun 1997 10:38:21 +1000 (EST) Date: Mon, 16 Jun 1997 10:34:08 +1000 (Sydney Standard Time) From: Peter Champas To: chaos@tgci.com cc: Richard Laxton , freebsd-isp@FreeBSD.ORG Subject: Re: large number of file handles open In-Reply-To: <199706160010.RAA07571@train.tgci.com> Message-ID: X-X-Sender: ingold@router.besys.net.au MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Jun 1997, Riley J. McIntire wrote: > > From: jivko@ijs.com > > At 06:45 AM 6/16/97 +1000, Richard Laxton wrote: > [snip] > > > On another topic: Have any of you had any problems running FreeBSD on a > > COMPAQ machine (P133)? I discovered yesterday that FreeBSD 2.1. would not > > read the memory size properly and would use only 16MB on a COMPAQ machine > > with 72MB. Recompiling the kernel with the memory size took care of the > > problem, but I was wondering if it is just me or a typical problem with > > COMPAQ. > > > > Jivko > > Regards, > > > > Jivko Koltchev > > > I don't have any hands on experience with fbsd/compaq but do recall > a similar problem on a Compaq with, I think, 32 MB ram. > > Additionally, doesn't any fbsd machine require a recompile for >64 > MB? > Yep Put this options in the kernel.. :) options "MAXMEM=" Where n is your memory in Kilobytes. For a 128 MB machine, you'd want to use 131072 BTW: this is straght out of the faq: http://www.freebsd.org/FAQ/FAQ120.html *---------------------[ http://www.besys.net.au/ ]---------------------* | Peter Champas | peter@besys.net.au | | Business Environment Systems | ph: 0419 337 370 | |----------------------------------------------------------------------| | I don't demand perfection, just something that's reasonably reliable | *----------------------------------------------------------------------* From owner-freebsd-isp Sun Jun 15 17:50:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA03776 for isp-outgoing; Sun, 15 Jun 1997 17:50:44 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03770 for ; Sun, 15 Jun 1997 17:50:42 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA09084; Sun, 15 Jun 1997 17:50:21 -0700 (PDT) To: chaos@tgci.com cc: Richard Laxton , freebsd-isp@FreeBSD.ORG Subject: Re: large number of file handles open In-reply-to: Your message of "Sun, 15 Jun 1997 17:11:07 -0000." <199706160010.RAA07571@train.tgci.com> Date: Sun, 15 Jun 1997 17:50:21 -0700 Message-ID: <9080.866422221@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I don't have any hands on experience with fbsd/compaq but do recall > a similar problem on a Compaq with, I think, 32 MB ram. This is a known problem with Compaq machines and it really should be in the FAQ, next to section 7.6 (which probably need to be retitled also). Mumble. I might do it if nobody beats me to it. :) [though I really do wish that more people would submit entries to the FAQ :( ] Jordan From owner-freebsd-isp Sun Jun 15 19:21:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA10149 for isp-outgoing; Sun, 15 Jun 1997 19:21:22 -0700 (PDT) Received: from iectech.com (netgate.iectech.com [198.136.226.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA10144 for ; Sun, 15 Jun 1997 19:21:20 -0700 (PDT) Received: by netgate.iectech.com id <6182>; Sun, 15 Jun 1997 18:07:56 -0400 From: Chris Peltier To: "'freebsd-isp@FreeBSD.ORG'" Cc: Dean Romaniello Subject: FreeBSD 2.2.2 and Merit Gated Date: Sun, 15 Jun 1997 22:17:37 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 Encoding: 17 TEXT Message-Id: <97Jun15.180756edt.6182@netgate.iectech.com> Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does anybody have any experience running gated for BGP 4 on FreeBSD? I am interested in running full Internet routing tables and pushing several meg full duplex through a dual-homed box. I need to route to 5 differant IPs on one local network which map to 5 differant points on a global ATM network. It seems the Merit gated implementation should do the job on a Penitum Pro machine with 128Meg memory and two 10/100 Base T cards. Any comments or experiences? Sincerely, Chris Peltier * email: CPELTIER@IECTECH.COM * voice: 215-257-4917 * FAX: 215-257-4916 From owner-freebsd-isp Mon Jun 16 00:02:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA19174 for isp-outgoing; Mon, 16 Jun 1997 00:02:45 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA19169 for ; Mon, 16 Jun 1997 00:02:42 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id IAA05023; Mon, 16 Jun 1997 08:01:32 +0100 (BST) Date: Mon, 16 Jun 1997 08:01:32 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Chris Peltier cc: "'freebsd-isp@FreeBSD.ORG'" , Dean Romaniello Subject: Re: FreeBSD 2.2.2 and Merit Gated In-Reply-To: <97Jun15.180756edt.6182@netgate.iectech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Jun 1997, Chris Peltier wrote: > Does anybody have any experience running gated for BGP 4 > on FreeBSD? I am interested in running full Internet routing > tables and pushing several meg full duplex through a dual-homed > box. I need to route to 5 differant IPs on one local network which > map to 5 differant points on a global ATM network. > It seems the Merit gated implementation should do the job > on a Penitum Pro machine with 128Meg memory and two > 10/100 Base T cards. Any comments or experiences? We peer with 30+ networks at the LINX in London using a P120 with 64 MB of memory and three DEC 10/100 cards, two of which are connected to 100 Mbps Ethernet switches. We run gated with BGP4 and OSPF. The setup is very stable. We used to use a 486 but replaced it with the P120 a year or so ago because the Asus T2P4 motherboard supports ECC. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-isp Mon Jun 16 02:30:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24679 for isp-outgoing; Mon, 16 Jun 1997 02:30:41 -0700 (PDT) Received: from prova.iet.unipi.it (prova1.iet.unipi.it [131.114.9.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24561; Mon, 16 Jun 1997 02:28:30 -0700 (PDT) Received: (from luigi@localhost) by prova.iet.unipi.it (8.8.5/8.8.5) id LAA00577; Mon, 16 Jun 1997 11:27:25 +0200 (CEST) From: Luigi Rizzo Message-Id: <199706160927.LAA00577@prova.iet.unipi.it> Subject: rr queueing To: luigi@prova.iet.unipi.it (Luigi Rizzo) Date: Mon, 16 Jun 1997 11:27:25 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [I am sending this mail because you might be interested in the subject. You are on the Bcc list so you will not be bothered by replies from other recipients]. I have some preliminary code for implementing RR queueing and associated stuff (including bw allocation) in the bottom layers of the networking stack. When complete (although it pretty much works even now) it is meant to replace the IF_ENQUEUE/IF_DEQUEUE macros. As such, I have tried to make the code and the algorithms fast and efficient. The code includes some description on what it does and how, so if you have comments and suggestions on how to improve it or add more features, let me know. The code is at the following URL http://www.iet.unipi.it/~luigi/newifqueue.c in its current form, it compiles to a standalone program so as to check actual performance and be easily modifiable. 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/ ==================================================================== From owner-freebsd-isp Mon Jun 16 03:03:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26153 for isp-outgoing; Mon, 16 Jun 1997 03:03:17 -0700 (PDT) Received: from albert.osu.cz (albert.osu.cz [193.84.224.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26146; Mon, 16 Jun 1997 03:03:13 -0700 (PDT) Received: from localhost (belkovic@localhost) by albert.osu.cz (8.8.5/8.6.12) with SMTP id MAA01091; Mon, 16 Jun 1997 12:04:04 +0200 (MET DST) Date: Mon, 16 Jun 1997 12:04:04 +0200 (MET DST) From: Josef Belkovics To: freebsd-isp@FreeBSD.ORG, freebsd-question@FreeBSD.ORG Subject: DNS (glue record ?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Because nobody from SOA address of my isp answers, I try you. (I am not subscribed in freebsd-question). I have certainly registered second-level domain name (osu.cz.). Next, I have certainly assigned ip addresses from 193.84.224 to 193.84.232. But it seems, that nets 225-232 (not 224) are not in IN-ADDR.ARPA. I can resolve my_name->ip on every dns server in the world, but *****resolving my_ip->name is correct (with exception 224) only on my own dns servers*****. E. g. 'server oudec|albert|algernon|isac.osu.cz', 'set type=ptr', '30.226.84.193.in-addr.arpa' puts "ac030.osu.cz", but 'server ns.cesnet.cz', 'set type=ptr', '30.226.84.193.in-addr.arpa' issues error *****"non-existent domain"***** (oudec is my primary server, albert|algernon|isac are my secondary servers; ns.cesnet.cz is dns server of my isp). I have two questions: 1) Must my isp ask for something like 226.84.193.in-addr.arpa at NIC? 2) If not, where may be bug? Josef Belkovics From owner-freebsd-isp Mon Jun 16 04:40:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA00176 for isp-outgoing; Mon, 16 Jun 1997 04:40:33 -0700 (PDT) Received: from sys3.cambridge.uk.psi.net (sys3.cambridge.uk.psi.net [154.32.106.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA00169 for ; Mon, 16 Jun 1997 04:40:21 -0700 (PDT) Received: from sys4.cambridge.uk.psi.net (sys4.cambridge.uk.psi.net [154.32.106.14]) by sys3.cambridge.uk.psi.net (8.8.4/) with ESMTP id MAA02208; Mon, 16 Jun 1997 12:40:16 +0100 (BST) Received: by sys4.cambridge.uk.psi.net (8.7.5/SMI-5.5-UKPSINet) id MAA28749; Mon, 16 Jun 1997 12:10:45 +0100 (BST) Received: from infodev.nadt.org.uk (infodev.nadt.org.uk [194.155.224.205]) by charlie.nadt.org.uk (8.8.5/8.6.12) with SMTP id LAA05421; Mon, 16 Jun 1997 11:57:19 +0100 (BST) Message-Id: <1.5.4.32.19970616105714.006982d8@wrcmail> X-Sender: robmel@wrcmail X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Jun 1997 11:57:14 +0100 To: "Stephen A. Derdau" From: Robin Melville Subject: Re: Internet providers discouraging customers from unix Cc: listuser , isp@FreeBSD.ORG Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 16:22 12/06/97 -0400, Stephen A. Derdau wrote: >Is this true, " Mac is suppose to base their next version of their >OS on a more Unix like plateform? If so I think it will be the best >thing they can do right now........not really a techy here. But enjoy >learning this stuff. :) The next version of MacOS will be based around the NeXT Mach kernel (always supposing Apple survives the next year without going bust). They've planted the Mac [78].* API on top, but are hoping developers will migrate to the new "Yellow Box" API. I guess that if they get it right & get developer support that it'll be a big step up for them. I don't see any sign that there'll be a command line interface to Mach however... All this stuff is ad nauseam on www.apple.com. You might try a little surfing to learn the gory details... 8-) Robin. -------------------------------------------------------- Robin Melville, Addiction & Forensic Information Service Nottingham Alcohol & Drug Team (Extn. 49178) Vox: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 Email: robmel@nadt.org.uk WWW: http://www.innotts.co.uk/nadt/ --------------------------------------------------------- From owner-freebsd-isp Mon Jun 16 06:04:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04075 for isp-outgoing; Mon, 16 Jun 1997 06:04:59 -0700 (PDT) Received: from foo.primenet.com (ip196.sjc.primenet.com [206.165.96.196]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04057 for ; Mon, 16 Jun 1997 06:04:52 -0700 (PDT) Received: (from bkogawa@localhost) by foo.primenet.com (8.8.5/8.6.12) id GAA07799; Mon, 16 Jun 1997 06:08:04 -0700 (PDT) Date: Mon, 16 Jun 1997 06:08:04 -0700 (PDT) Message-Id: <199706161308.GAA07799@foo.primenet.com> To: isp@freebsd.org Subject: Re: Internet providers discouraging customers from unix Newsgroups: localhost.freebsd.isp References: <> <1.5.4.32.19970616105714.006982d8@wrcmail> From: "Bryan K. Ogawa" X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In localhost.freebsd.isp you write: [apple's trying to move to a Nextstep-based platform for MacOS] >that it'll be a big step up for them. I don't see any sign that there'll be >a command line interface to Mach however... Someone, somewhere, recently posted a url where a guy talked about Apple's presentation to some developers which sported a development version of the new MacOS in development. I think that page mentioned their intention to package the system with Lites (4.4BSD on top of Mach) for the interested (e.g. telnet to a Mac). The plans sound good from an "I like it" perspective; I sure hope Apple succeeds, since if they do, the results will almost surely extend Unix's visibility. -- bryan k ogawa http://www.primenet.com/~bkogawa/ From owner-freebsd-isp Mon Jun 16 07:22:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07729 for isp-outgoing; Mon, 16 Jun 1997 07:22:24 -0700 (PDT) Received: from Wicked.eaznet.com ([206.62.254.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA07724 for ; Mon, 16 Jun 1997 07:22:21 -0700 (PDT) Received: from Eddie.eaznet.com ([206.62.254.35]) by Wicked.eaznet.com (8.7.5/8.7.3) with SMTP id HAA03506 for ; Mon, 16 Jun 1997 07:23:42 -0700 (MST) Message-ID: <33A35515.402B@eaznet.com> Date: Sat, 14 Jun 1997 19:36:34 -0700 From: Eddie Fry Organization: Creative Solutions X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: spam mail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey, I just saw a .signature on the internet that may be usefull in stopping spam mail. Here it is. Do you think this would stand up in small claims court??? ------------------------------------------------------------------ Pursuant to US Code, Title 47, Chapter 5, Subchapter II, Sec. 227, any and all nonsolicited commercial E-mail sent to this address is subject to a download and archival fee in the amount of $500 US. E-mailing denotes acceptance of these terms. ------------------------------------------------------------------ Eddie From owner-freebsd-isp Mon Jun 16 08:28:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA11160 for isp-outgoing; Mon, 16 Jun 1997 08:28:03 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA11030 for ; Mon, 16 Jun 1997 08:25:35 -0700 (PDT) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.5) with SMTP id LAA01743; Mon, 16 Jun 1997 11:25:21 -0400 (EDT) Date: Mon, 16 Jun 1997 11:25:20 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: Eddie Fry cc: freebsd-isp@FreeBSD.ORG Subject: Re: spam mail In-Reply-To: <33A35515.402B@eaznet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is referring to the so-called junk-fax law. You can read it online at http://www.law.cornell.edu/uscode/47/227.shtml AFAIK, a court has never established that this can be applied to e-mail. Some theorize that it can be applied since computers are capable of performing the functions of a fax machine. IMHO a court would not side with that interpretation. Many people are proposing to amend that law to specifically address SPAM, though. Check out http://www.cauce.org pbd -- You can make it illegal, but you can't make it unpopular. On Sat, 14 Jun 1997, Eddie Fry wrote: > I just saw a .signature on the internet that may be usefull in stopping > spam mail. Here it is. Do you think this would stand up in small > claims court??? > > ------------------------------------------------------------------ > Pursuant to US Code, Title 47, Chapter 5, Subchapter II, Sec. 227, > any and all nonsolicited commercial E-mail sent to this address is > subject to a download and archival fee in the amount of $500 US. > E-mailing denotes acceptance of these terms. > ------------------------------------------------------------------ From owner-freebsd-isp Mon Jun 16 08:35:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA11730 for isp-outgoing; Mon, 16 Jun 1997 08:35:35 -0700 (PDT) Received: from ady.warp.starnets.ro (ady.warp.starnets.ro [193.226.124.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA11682; Mon, 16 Jun 1997 08:35:15 -0700 (PDT) Received: from localhost (ady@localhost) by ady.warp.starnets.ro (8.8.5/8.8.5) with SMTP id SAA01568; Mon, 16 Jun 1997 18:33:36 +0300 (EEST) Date: Mon, 16 Jun 1997 18:33:36 +0300 (EEST) From: Penisoara Adrian To: freebsd-isp@FreeBSD.org cc: freebsd-questions@FreeBSD.org Subject: Q) NNTP server / USENET News solution ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I have a bit of a problem choosing the server software for USENET news hosting. Which solution is best suited for a slow connection & limited amount of space of disk ? Any links to related documentation/FAQs is welcomed ! BTW, why didn't I find anything related to this in the FreeBSD handbook/FAQ ? Many thanx in advance ! Ady (@warp.starnets.ro) "Yes, I do believe in FreeBSD !" | Running SMP FreeBSD since April '97 :) From owner-freebsd-isp Mon Jun 16 08:44:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA12438 for isp-outgoing; Mon, 16 Jun 1997 08:44:46 -0700 (PDT) Received: from ady.warp.starnets.ro (ady.warp.starnets.ro [193.226.124.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA12407; Mon, 16 Jun 1997 08:44:18 -0700 (PDT) Received: from localhost (ady@localhost) by ady.warp.starnets.ro (8.8.5/8.8.5) with SMTP id SAA01583; Mon, 16 Jun 1997 18:42:49 +0300 (EEST) Date: Mon, 16 Jun 1997 18:42:49 +0300 (EEST) From: Penisoara Adrian Reply-To: Penisoara Adrian To: freebsd-isp@FreeBSD.org cc: freebsd-questions@FreeBSD.org Subject: Q) IRC server : &channels ?!? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi ! It's me again with another (probably stupid) question: I have installed the irc-2.9.1.16 port from the FreeBSD port collection and, after tweaking a bit the ircd.inf to kick it online, I faced a minor problem: doing a "/list" while logged in shows 8 channels starting with '&': &LOCAL 1 &HASH 1 &SERVERS 1 &NUMERICS 1 &CHANNEL 1 &KILLS 1 &NOTICES 1 &ERRORS 1 What do these channels stand for and can I hide them ? Any links to related documentation/FAQs are appreciated. Thanks in advance. Ady (@warp.starnets.ro) From owner-freebsd-isp Mon Jun 16 09:37:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14668 for isp-outgoing; Mon, 16 Jun 1997 09:37:46 -0700 (PDT) Received: from noc.demon.net (firewall-user@server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14611; Mon, 16 Jun 1997 09:36:32 -0700 (PDT) Received: by noc.demon.net; id RAA21546; Mon, 16 Jun 1997 17:35:18 +0100 (BST) Received: from stress.noc.demon.net(195.11.55.5) by inside.noc.demon.net via smap (3.2) id xma021538; Mon, 16 Jun 97 17:35:06 +0100 Received: from hdm by stress.noc.demon.net with local (Exim 1.61 #3) id 0wdekC-0005oW-00; Mon, 16 Jun 1997 17:35:04 +0100 To: Penisoara Adrian cc: freebsd-isp@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Q) IRC server : &channels ?!? X-Mailer: nmh v0.14, exmh 2.0gamma, gvim 4.5 X-Colour: Green In-reply-to: Date: Mon, 16 Jun 1997 17:35:04 +0100 From: Dom Mitchell Message-Id: Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Penisoara Adrian wrote: > Hi ! > > It's me again with another (probably stupid) question: > I have installed the irc-2.9.1.16 port from the FreeBSD port collection > and, after tweaking a bit the ircd.inf to kick it online, I faced a minor > problem: doing a "/list" while logged in shows 8 channels starting with > '&': > > &LOCAL 1 > &HASH 1 > &SERVERS 1 > &NUMERICS 1 > &CHANNEL 1 > &KILLS 1 > &NOTICES 1 > &ERRORS 1 > > What do these channels stand for and can I hide them ? Any links to > related documentation/FAQs are appreciated. Dunno about docs, but... These channels are a standard feature of 2.9.x servers. They are in place of various operator modes. -Dom From owner-freebsd-isp Mon Jun 16 09:59:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA15667 for isp-outgoing; Mon, 16 Jun 1997 09:59:28 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA15662; Mon, 16 Jun 1997 09:59:25 -0700 (PDT) Received: from group.groupnet.net (ali@group.groupnet.net [206.54.250.1]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id JAA16569; Mon, 16 Jun 1997 09:59:19 -0700 (PDT) Received: from localhost (ali@localhost) by group.groupnet.net (8.8.5/8.8.5) with SMTP id MAA16643; Mon, 16 Jun 1997 12:00:09 -0500 (CDT) Date: Mon, 16 Jun 1997 12:00:09 -0500 (CDT) From: Ali Lomonaco To: Penisoara Adrian cc: freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Q) IRC server : &channels ?!? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk & channels are channels that stay on a server they were started in and do not float accross the net.y On Mon, 16 Jun 1997, Penisoara Adrian wrote: > Hi ! > > It's me again with another (probably stupid) question: > I have installed the irc-2.9.1.16 port from the FreeBSD port collection > and, after tweaking a bit the ircd.inf to kick it online, I faced a minor > problem: doing a "/list" while logged in shows 8 channels starting with > '&': > > &LOCAL 1 > &HASH 1 > &SERVERS 1 > &NUMERICS 1 > &CHANNEL 1 > &KILLS 1 > &NOTICES 1 > &ERRORS 1 > > What do these channels stand for and can I hide them ? Any links to > related documentation/FAQs are appreciated. > > Thanks in advance. > > Ady (@warp.starnets.ro) > > > From owner-freebsd-isp Mon Jun 16 10:29:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17630 for isp-outgoing; Mon, 16 Jun 1997 10:29:05 -0700 (PDT) Received: from ultra.ts.kiev.ua (ultra.ts.kiev.ua [193.124.229.197]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA17594; Mon, 16 Jun 1997 10:28:51 -0700 (PDT) Received: from nbki.ipri.kiev.ua by ultra.ts.kiev.ua with SMTP id TAA29815; (8.8.3/zah/2.1) Mon, 16 Jun 1997 19:42:57 +0300 (EET DST) Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id TAA16339; (8.6.9/zah/1.1) Mon, 16 Jun 1997 19:20:41 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id TAA04066; Mon, 16 Jun 1997 19:16:15 +0300 (EET DST) Message-ID: <33A55918.70F8@cki.ipri.kiev.ua> Date: Mon, 16 Jun 1997 18:17:37 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Penisoara Adrian CC: freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Q) NNTP server / USENET News solution ? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Penisoara Adrian wrote: > > Hi ! > > I have a bit of a problem choosing the server software for USENET news > hosting. Which solution is best suited for a slow connection & limited > amount of space of disk ? > Any links to related documentation/FAQs is welcomed ! BTW, why didn't I > find anything related to this in the FreeBSD handbook/FAQ ? > INN is a standart solution. with slow connection better receive incoming news from UUCP. refer to INN is in FreeBSD FAQ > Many thanx in advance ! > > Ady (@warp.starnets.ro) > "Yes, I do believe in FreeBSD !" | Running SMP FreeBSD since April '97 :) From owner-freebsd-isp Mon Jun 16 11:02:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA19535 for isp-outgoing; Mon, 16 Jun 1997 11:02:44 -0700 (PDT) Received: from eternal.dusk.net (root@eternal.dusk.net [205.250.29.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA19473; Mon, 16 Jun 1997 11:02:28 -0700 (PDT) Received: (from hochhold@localhost) by eternal.dusk.net (8.8.4/8.8.4) id OAA03118; Mon, 16 Jun 1997 14:54:46 -0300 (ADT) From: Christian Hochhold Message-Id: <199706161754.OAA03118@eternal.dusk.net> Subject: Re: Q) IRC server : &channels ?!? To: ali@groupnet.net (Ali Lomonaco) Date: Mon, 16 Jun 1997 14:54:46 -0300 (ADT) Cc: ady@ady.warp.starnets.ro, freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG In-Reply-To: from Ali Lomonaco at "Jun 16, 97 12:00:09 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk &Channels are local server channels - meaning only people using -that particular- server can see & enter those channels, whilst #channel are globally accessable channels. Hope it helps =) Christian > & channels are channels that stay on a server they were started in > and do not float accross the net.y > > On Mon, 16 Jun 1997, Penisoara Adrian wrote: > > > Hi ! > > > > It's me again with another (probably stupid) question: > > I have installed the irc-2.9.1.16 port from the FreeBSD port collection > > and, after tweaking a bit the ircd.inf to kick it online, I faced a minor > > problem: doing a "/list" while logged in shows 8 channels starting with > > '&': > > > > &LOCAL 1 > > &HASH 1 > > &SERVERS 1 > > &NUMERICS 1 > > &CHANNEL 1 > > &KILLS 1 > > &NOTICES 1 > > &ERRORS 1 > > > > What do these channels stand for and can I hide them ? Any links to > > related documentation/FAQs are appreciated. > > > > Thanks in advance. > > > > Ady (@warp.starnets.ro) > > > > > > > > From owner-freebsd-isp Mon Jun 16 18:33:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA14670 for isp-outgoing; Mon, 16 Jun 1997 18:33:03 -0700 (PDT) Received: from linkou.trace.com.tw (ronald@linkou.trace.com.tw [203.67.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA14645 for ; Mon, 16 Jun 1997 18:32:54 -0700 (PDT) Received: from localhost (ronald@localhost) by linkou.trace.com.tw (8.8.4/8.8.4) with SMTP id JAA17094; Tue, 17 Jun 1997 09:32:28 +0800 Date: Tue, 17 Jun 1997 09:32:28 +0800 (CCT) From: Ronald Wiplinger To: Eddie Fry cc: freebsd-isp@FreeBSD.ORG Subject: Re: spam mail In-Reply-To: <33A35515.402B@eaznet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Jun 1997, Eddie Fry wrote: > Hey, > > I just saw a .signature on the internet that may be usefull in stopping > spam mail. Here it is. Do you think this would stand up in small > claims court??? > > ------------------------------------------------------------------ > Pursuant to US Code, Title 47, Chapter 5, Subchapter II, Sec. 227, > any and all nonsolicited commercial E-mail sent to this address is > subject to a download and archival fee in the amount of $500 US. > E-mailing denotes acceptance of these terms. > ------------------------------------------------------------------ > > Eddie > > I do not see here a way to stop it. The USA law is not valid outside. If you would like to enforce it though it cost you a lots more money and effort than just press the delete key. Beside this, I cannot imagine to sue an "e-mail", maybe even faked e-mail. An postal address you would not get anyway. Another example is "really damaging". I had a hacker in my system, I traced him back to the University in Estland. The result: 12000 US$ damage on my site, both students got suspended said the Universities "newspaper editor" (who knows if real). You have no real chance to get here something back. 12000 US$ is a real damage, an unsolicite e-mail is not really an damage, beside the anger and connection fee, most of the US sites have unlimited, so remains only the lowest phone rate on earth. I would like to see something that really help. Something like block a site, ... However even here it is difficult. As more users you get as more chance you have to get a spamer. Why should 99.99% users be punished for one a**** ? The second is, that many spamer do not use their own e-mail, most of them fake the senders address and/or relay them through. Frankly speaking I would not be able to find somebody who used my providers station as relay with a fake address of my station. My provider is "government", so the help is very limited. I guess the better way of the future will be, that you CANNOT send e-mails without 100% identification. Than maybe the USA law can be enforced even abroad. ... just my thinking, ... bye Ronald From owner-freebsd-isp Mon Jun 16 19:35:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA17883 for isp-outgoing; Mon, 16 Jun 1997 19:35:11 -0700 (PDT) Received: from dream.future.net (future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA17876 for ; Mon, 16 Jun 1997 19:35:05 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id VAA11730 for ; Mon, 16 Jun 1997 21:35:12 -0500 (CDT) Date: Mon, 16 Jun 1997 21:35:12 -0500 (CDT) From: "Tom T. Thai" To: freebsd-isp@FreeBSD.ORG Subject: Multilink PPP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Anyone know how to do MultiLink PPP in the BSD box? .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Tue Jun 17 07:50:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17786 for isp-outgoing; Tue, 17 Jun 1997 07:50:33 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17781 for ; Tue, 17 Jun 1997 07:50:31 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id KAA20884; Tue, 17 Jun 1997 10:59:23 -0400 (EDT) Message-Id: <3.0.32.19970617105009.00afa4e0@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 17 Jun 1997 10:50:12 -0400 To: "Miguel A.L. Paraz" From: dennis Subject: Re: Comparison Cc: isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:57 PM 6/17/97 +0800, you wrote: >Hi, > >Jon Lewis wrote: >> I wonder if ET has considered such a thing based on their sync cards? My >> guess is there's so much extra hardware and software involved that anyone >> making one of these as a PC card to be used under Unix or NT is unlikely. This is non-sense, but the market for unix is way too small and NT probably doesnt have the hooks to do it properly. It IS a big project, and to do EI would require getting tons of approvals and testing sites......but channelized T1 is more reasonable. We dont plan on doing it though. Can't do everything, and selling unix into high-end scenarios is a tough job. > >Perhaps. However I am interested, and I'm sure many other folks are, >in the interests of ease-of-management. Channelized E1 gear such as >the Ascend MAX 4000 support a whole lot of stuff like ISDN and frame >which we cannot use anyway, but add to the cost (fantastic!) > >I'm also appalled by the fact that the low-end MAX doesn't support >OSPF (as per their web site). This is a requirement for us since >the main application is for dial-up LAN routing and leased line >backup. Thats how they make money, but *assuming* that low-end and OSPF are in different genres. Dennis From owner-freebsd-isp Tue Jun 17 08:05:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA18432 for isp-outgoing; Tue, 17 Jun 1997 08:05:08 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA18424 for ; Tue, 17 Jun 1997 08:05:05 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id LAA20968; Tue, 17 Jun 1997 11:13:49 -0400 (EDT) Message-Id: <3.0.32.19970617110435.00afb750@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 17 Jun 1997 11:04:38 -0400 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: dennis Subject: Re: tar hangs 2.2.x system Cc: isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:38 PM 6/15/97 +0200, you wrote: >As Ruslan Shevchenko wrote: > >> > tar -cvf /dev/rfd0 somefiles >> > >> > Note the "raw" device. >> > >> >> But it is a bug. >> >> Anybody, do send_pr > >No, don't. For one, it was a known bug, so the PR wouldn't probably >have caused more reason for anybody at all, and now, Bruce has fixed >this bug a couple of days ago. > >Folks, nevertheless: > > Buffered devices (/dev/fd0) are JUST and ONLY for mounting > something (and for swapon(8)). > > Raw devices (/dev/rfd0) are FOR EVERYTHING ELSE. > > (The terms `block device' and `character device' are > misnomers you should never use. Historical errors.) > >Sorry for shouting, but from some non-newbie like dennis, i would have >expected to know this. I'm repeating this over and over again to my >clients on any Unix course i'm teaching. Perhaps true, but in the commercial world you cant instantaneously change all of your documents and procedures to fix something that has worked since the beginning of time. They both SHOULD work, and changing a basic procedure is quite painful. Dennis From owner-freebsd-isp Tue Jun 17 10:21:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA24221 for isp-outgoing; Tue, 17 Jun 1997 10:21:16 -0700 (PDT) Received: from rainey.blueneptune.com (root@rainey.blueneptune.com [207.104.147.225]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA24216 for ; Tue, 17 Jun 1997 10:21:12 -0700 (PDT) From: michael@blueneptune.com Received: (from michael@localhost) by rainey.blueneptune.com (8.6.12/8.6.12) id KAA19182 for isp@freebsd.org; Tue, 17 Jun 1997 10:21:24 -0700 Message-Id: <199706171721.KAA19182@rainey.blueneptune.com> Subject: Re: tar hangs 2.2.x system To: isp@freebsd.org Date: Tue, 17 Jun 1997 10:21:24 -0700 (PDT) In-Reply-To: <3.0.32.19970617110435.00afb750@etinc.com> from "dennis" at Jun 17, 97 11:04:38 am Reply-To: michael@blueneptune.com X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> tar -cvf /dev/rfd0 somefiles >>>> >>>> Note the "raw" device. >> >> Buffered devices (/dev/fd0) are JUST and ONLY for mounting >> something (and for swapon(8)). >> >> Raw devices (/dev/rfd0) are FOR EVERYTHING ELSE. >> >>Sorry for shouting, but from some non-newbie like dennis, i would have >>expected to know this. I'm repeating this over and over again to my >>clients on any Unix course i'm teaching. > > Perhaps true, but in the commercial world you cant instantaneously > change all of your documents and procedures to fix something that > has worked since the beginning of time. They both SHOULD work, and > changing a basic procedure is quite painful. Maybe I'm a special case, but in the 15+ years I've been working with Unix, I've -always- known to use the raw device for tape archives. And most system documentation I've looked at indicates that this is the case. I would never even try to use a buffered device for tar, and I wouldn't be surprised in any case where it didn't work the same as a raw device. Even if it did work on systems where you've been using it, I have a hard time buying the argument that something that has always worked should be maintained as working in the same fashion. If it's documented to work in a specific way, sure, I buy it then. But if it's an undocumented behaviour, and general knowledge for many years indicates that you shouldn't do it, then I think it's a bad practice to expect that behaviour to remain. On the flip side, it should not arbitrarily be removed, either, for pretty much the same reasons you state. But if a design change happens to make that undocumented feature break, then in general I think that's ok. [Sorta like "lseek(fd, 0, 0)" with no prototype in scope. It's neither wise nor recommended, but it works on nearly all flavors of Unix... until off_t is increased to 64 bits.] -- Michael Bryan michael@blueneptune.com From owner-freebsd-isp Tue Jun 17 13:05:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA03990 for isp-outgoing; Tue, 17 Jun 1997 13:05:05 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA03903 for ; Tue, 17 Jun 1997 13:03:21 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id QAA04744; Tue, 17 Jun 1997 16:06:23 -0400 (EDT) Date: Tue, 17 Jun 1997 16:06:23 -0400 (EDT) From: "John T. Farmer" Message-Id: <199706172006.QAA04744@sabre.goldsword.com> To: dennis@etinc.com, map@iphil.net Subject: Re: Comparison Cc: isp@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue Jun 17 11:06:51 1997 dennis said: >At 01:57 PM 6/17/97 +0800, you wrote: >>Hi, >> >>Jon Lewis wrote: >>> I wonder if ET has considered such a thing based on their sync cards? My >>> guess is there's so much extra hardware and software involved that anyone >>> making one of these as a PC card to be used under Unix or NT is unlikely. > >This is non-sense, but the market for unix is way too small and NT probably >doesnt have the hooks to do it properly. It IS a big project, and to do EI >would >require getting tons of approvals and testing sites......but channelized T1 is >more reasonable. We dont plan on doing it though. Can't do everything, and >selling unix into high-end scenarios is a tough job. > >> >>Perhaps. However I am interested, and I'm sure many other folks are, >>in the interests of ease-of-management. Channelized E1 gear such as >>the Ascend MAX 4000 support a whole lot of stuff like ISDN and frame >>which we cannot use anyway, but add to the cost (fantastic!) I'm coming into this in the middle so to speak, and so I'm not sure what exactly was being discussed but it sounds like it's related to something that I'm interested in, that is ISDN interfaces for BRI & PRI that will operate under FreeBSD. So far, what I've seen are some older cards that used to work under FreeBSD. What I would like to be able to do is to use it for PPP & MPP. If it could accept "voice/modem" calls (aka k56) that would be a win also. I suppose that what I want is to able to add the ability of an Ascend 1800 or 2000 to a FreeBSD box :^> (Max 1800 handles 8 BRI's, supports upto 16 64k ppp links for ~ $6k. Add ~$5k & it supports 16 k56/33.6 channels. The 2000 does the same using a PRI.) So any ideas? John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-isp Tue Jun 17 13:52:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06744 for isp-outgoing; Tue, 17 Jun 1997 13:52:19 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06738 for ; Tue, 17 Jun 1997 13:52:16 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA10067; Tue, 17 Jun 1997 22:52:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA19514; Tue, 17 Jun 1997 22:34:09 +0200 (MET DST) Message-ID: <19970617223408.HF45226@uriah.heep.sax.de> Date: Tue, 17 Jun 1997 22:34:08 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: dennis@etinc.com (dennis) Cc: isp@freebsd.org Subject: Re: tar hangs 2.2.x system References: <3.0.32.19970617110435.00afb750@etinc.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.32.19970617110435.00afb750@etinc.com>; from dennis on Jun 17, 1997 11:04:38 -0400 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As dennis wrote: > >Sorry for shouting, but from some non-newbie like dennis, i would have > >expected to know this. I'm repeating this over and over again to my > >clients on any Unix course i'm teaching. > Perhaps true, but in the commercial world you cant instantaneously > change all of your documents and procedures to fix something that > has worked since the beginning of time. They both SHOULD work, and > changing a basic procedure is quite painful. Sure, they should work. However, every system except Linux has raw devices, and they _always_ have been the first choice for such work. Don't blame us if you started with the wrong way (for whatever reason). You wouldn't suffer from the bug now otherwise. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-isp Tue Jun 17 14:00:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA07242 for isp-outgoing; Tue, 17 Jun 1997 14:00:54 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07233 for ; Tue, 17 Jun 1997 14:00:49 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA01245; Tue, 17 Jun 1997 13:53:59 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd001234; Tue Jun 17 20:53:49 1997 Message-ID: <33A6F91D.3F54BC7E@whistle.com> Date: Tue, 17 Jun 1997 13:52:45 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Tom T. Thai" CC: freebsd-isp@FreeBSD.ORG Subject: Re: Multilink PPP References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom T. Thai wrote: > > Anyone know how to do MultiLink PPP in the BSD box? > > .............. .................................... > Thomas T. Thai Infomedia Interactive Communications > tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 see 'mpd' which is now in the ports collection. From owner-freebsd-isp Tue Jun 17 14:11:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA07642 for isp-outgoing; Tue, 17 Jun 1997 14:11:34 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07625 for ; Tue, 17 Jun 1997 14:10:47 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id QAA00755; Tue, 17 Jun 1997 16:10:41 -0500 (CDT) Date: Tue, 17 Jun 1997 16:10:40 -0500 (CDT) From: "Tom T. Thai" To: "John T. Farmer" cc: dennis@etinc.com, map@iphil.net, isp@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: Comparison In-Reply-To: <199706172006.QAA04744@sabre.goldsword.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I believe you can with the right drivers. For instance, take a PRI/T1 card with MVIP interface and hook it up to a 24 highdensity card via the MVIP interface. ISDN is handled by the T1/PRI card and if it detects analog, it passes the call to the analog modem card. The hardware is out there, but no drivers. On Tue, 17 Jun 1997, John T. Farmer wrote: > > On Tue Jun 17 11:06:51 1997 dennis said: > >At 01:57 PM 6/17/97 +0800, you wrote: > >>Hi, > >> > >>Jon Lewis wrote: > >>> I wonder if ET has considered such a thing based on their sync cards? My > >>> guess is there's so much extra hardware and software involved that anyone > >>> making one of these as a PC card to be used under Unix or NT is unlikely. > > > >This is non-sense, but the market for unix is way too small and NT probably > >doesnt have the hooks to do it properly. It IS a big project, and to do EI > >would > >require getting tons of approvals and testing sites......but channelized T1 is > >more reasonable. We dont plan on doing it though. Can't do everything, and > >selling unix into high-end scenarios is a tough job. > > > >> > >>Perhaps. However I am interested, and I'm sure many other folks are, > >>in the interests of ease-of-management. Channelized E1 gear such as > >>the Ascend MAX 4000 support a whole lot of stuff like ISDN and frame > >>which we cannot use anyway, but add to the cost (fantastic!) > > I'm coming into this in the middle so to speak, and so I'm not sure what > exactly was being discussed but it sounds like it's related to something > that I'm interested in, that is ISDN interfaces for BRI & PRI that will > operate under FreeBSD. > > So far, what I've seen are some older cards that used to work under FreeBSD. > > What I would like to be able to do is to use it for PPP & MPP. If it could > accept "voice/modem" calls (aka k56) that would be a win also. I suppose > that what I want is to able to add the ability of an Ascend 1800 or 2000 > to a FreeBSD box :^> (Max 1800 handles 8 BRI's, supports upto 16 64k ppp > links for ~ $6k. Add ~$5k & it supports 16 k56/33.6 channels. The 2000 > does the same using a PRI.) > > So any ideas? > > John > > ------------------------------------------------------------------------- > John T. Farmer Proprietor, GoldSword Systems > jfarmer@goldsword.com Public Internet Access in East Tennessee > dial-in (423)470-9953 for info, e-mail to info@goldsword.com > Network Design, Internet Services & Servers, Consulting > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Tue Jun 17 14:35:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09770 for isp-outgoing; Tue, 17 Jun 1997 14:35:40 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09763 for ; Tue, 17 Jun 1997 14:35:36 -0700 (PDT) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.5) with SMTP id RAA25527; Tue, 17 Jun 1997 17:35:04 -0400 (EDT) Date: Tue, 17 Jun 1997 17:35:02 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: Jim Dixon cc: freebsd-isp@FreeBSD.ORG Subject: Re: FreeBSD 2.2.2 and Merit Gated In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Jun 1997, Jim Dixon wrote: > We peer with 30+ networks at the LINX in London using a P120 with > 64 MB of memory and three DEC 10/100 cards, two of which are > connected to 100 Mbps Ethernet switches. We run gated with BGP4 > and OSPF. If you don't mind me asking, what version of GateD are you using? pbd -- You can make it illegal, but you can't make it unpopular. From owner-freebsd-isp Tue Jun 17 14:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10099 for isp-outgoing; Tue, 17 Jun 1997 14:41:08 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10079 for ; Tue, 17 Jun 1997 14:41:01 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id WAA00871; Tue, 17 Jun 1997 22:40:13 +0100 (BST) Date: Tue, 17 Jun 1997 22:40:13 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Bradley Dunn cc: freebsd-isp@FreeBSD.ORG Subject: Re: FreeBSD 2.2.2 and Merit Gated In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Jun 1997, Bradley Dunn wrote: > > We peer with 30+ networks at the LINX in London using a P120 with > > 64 MB of memory and three DEC 10/100 cards, two of which are > > connected to 100 Mbps Ethernet switches. We run gated with BGP4 > > and OSPF. > > If you don't mind me asking, what version of GateD are you using? 3.6a2 with some mods. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-isp Tue Jun 17 16:33:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15569 for isp-outgoing; Tue, 17 Jun 1997 16:33:14 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15557 for ; Tue, 17 Jun 1997 16:33:10 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id TAA00843; Tue, 17 Jun 1997 19:36:36 -0400 (EDT) Message-Id: <3.0.32.19970617192917.00bf3ce0@etinc.com> X-Sender: dennis@etinc.com (Unverified) X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 17 Jun 1997 19:29:21 -0400 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: dennis Subject: Re: tar hangs 2.2.x system Cc: isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:34 PM 6/17/97 +0200, J Wunsch wrote: >> Perhaps true, but in the commercial world you cant instantaneously >> change all of your documents and procedures to fix something that >> has worked since the beginning of time. They both SHOULD work, and >> changing a basic procedure is quite painful. > >Sure, they should work. However, every system except Linux has raw >devices, and they _always_ have been the first choice for such work. >Don't blame us if you started with the wrong way (for whatever >reason). You wouldn't suffer from the bug now otherwise. I blame you for everything...its just my nature. :-) Dennis From owner-freebsd-isp Tue Jun 17 22:58:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29953 for isp-outgoing; Tue, 17 Jun 1997 22:58:42 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29945; Tue, 17 Jun 1997 22:58:32 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id PAA01924; Wed, 18 Jun 1997 15:54:03 +1000 (EST) Date: Wed, 18 Jun 1997 15:54:03 +1000 (EST) From: "Daniel O'Callaghan" To: Josef Belkovics cc: freebsd-isp@FreeBSD.ORG, freebsd-question@FreeBSD.ORG Subject: Re: DNS (glue record ?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1) Must my isp ask for something like 226.84.193.in-addr.arpa at NIC? These addresses are allocated to OSU. Because the IP addresses are described by 'dot' notation in a classful manner, and the DNS uses dots as domain separators, you must have a separate zone file for each of 193.84.224.0, 193.84.225.0, 193.84.226.0, 193.84.227.0 When you have set up the zone files and secondaries, register the new zones with RIPE. Your ISP is not involved. See www.ripe.net. regards Danny From owner-freebsd-isp Wed Jun 18 02:12:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA06886 for isp-outgoing; Wed, 18 Jun 1997 02:12:13 -0700 (PDT) Received: from albert.osu.cz (albert.osu.cz [193.84.224.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06879; Wed, 18 Jun 1997 02:12:07 -0700 (PDT) Received: from localhost (belkovic@localhost) by albert.osu.cz (8.8.5/8.6.12) with SMTP id LAA00748; Wed, 18 Jun 1997 11:12:17 +0200 (MET DST) Date: Wed, 18 Jun 1997 11:12:16 +0200 (MET DST) From: Josef Belkovics To: "Daniel O'Callaghan" cc: freebsd-isp@FreeBSD.ORG, freebsd-question@FreeBSD.ORG Subject: Re: DNS (glue record ?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Jun 1997, Daniel O'Callaghan wrote: > > > 1) Must my isp ask for something like 226.84.193.in-addr.arpa at NIC? > > These addresses are allocated to OSU. Because the IP addresses are > described by 'dot' notation in a classful manner, and the DNS uses dots > as domain separators, you must have a separate zone file for each of > 193.84.224.0, 193.84.225.0, 193.84.226.0, 193.84.227.0 > > When you have set up the zone files and secondaries, register the new > zones with RIPE. Your ISP is not involved. See www.ripe.net. > > regards > > Danny I now understand the problem with my LR (local registry authority). Thanks all for advices about dig, whois, RIPE NCC. Regards Josef From owner-freebsd-isp Wed Jun 18 02:37:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07573 for isp-outgoing; Wed, 18 Jun 1997 02:37:11 -0700 (PDT) Received: from stk_file.airtime.se ([193.14.64.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07568 for ; Wed, 18 Jun 1997 02:37:04 -0700 (PDT) Received: by STK_FILE with Internet Mail Service (5.0.1457.3) id ; Wed, 18 Jun 1997 11:35:35 +0200 Message-ID: <44F52736D0CBD011BA6200805FA6FE13BCB5@STK_FILE> From: =?iso-8859-1?Q?Patrik_=C5str=F6m?= To: "'freebsd-isp@freebsd.org'" Date: Wed, 18 Jun 1997 11:35:33 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-isp From owner-freebsd-isp Wed Jun 18 03:12:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA09130 for isp-outgoing; Wed, 18 Jun 1997 03:12:10 -0700 (PDT) Received: from icp.acquire.net.au (root@icp.acquire.net.au [203.24.197.97]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA09082 for ; Wed, 18 Jun 1997 03:11:54 -0700 (PDT) Received: from ppp3.acquire.net.au (ppp3.acquire.net.au [203.24.197.116]) by icp.acquire.net.au (8.8.5/8.8.3/BSD4.4) with SMTP id UAA05034 for ; Wed, 18 Jun 1997 20:11:22 +1000 (EST) Message-ID: <33A7B48C.2A9C@acquire.net.au> Date: Wed, 18 Jun 1997 20:12:28 +1000 From: John Wan X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe freebsd-isp From owner-freebsd-isp Wed Jun 18 07:17:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA18601 for isp-outgoing; Wed, 18 Jun 1997 07:17:44 -0700 (PDT) Received: from h2o.journey.net (h2o.journey.net [207.227.162.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA18595 for ; Wed, 18 Jun 1997 07:17:41 -0700 (PDT) Received: from localhost (listuser@localhost) by h2o.journey.net (8.8.5/8.8.5) with SMTP id KAA25916; Wed, 18 Jun 1997 10:15:01 -0400 (EDT) Date: Wed, 18 Jun 1997 10:15:01 -0400 (EDT) From: listuser To: "Tom T. Thai" cc: "John T. Farmer" , dennis@etinc.com, map@iphil.net, isp@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: Comparison In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The most cost effective Ascend MAX is the 4048.. It comes with T1/PRI software and 48 K56 modems and the CSU's for two T1's... (Infact it works great :) I also have 4002's and 4004's and have a MAX TNT on order for a large pop I am building.. --Matt On Tue, 17 Jun 1997, Tom T. Thai wrote: > I believe you can with the right drivers. For instance, take a PRI/T1 > card with MVIP interface and hook it up to a 24 highdensity card via the > MVIP interface. ISDN is handled by the T1/PRI card and if it detects > analog, it passes the call to the analog modem card. The hardware is out > there, but no drivers. > > On Tue, 17 Jun 1997, John T. Farmer wrote: > > > > > On Tue Jun 17 11:06:51 1997 dennis said: > > >At 01:57 PM 6/17/97 +0800, you wrote: > > >>Hi, > > >> > > >>Jon Lewis wrote: > > >>> I wonder if ET has considered such a thing based on their sync cards? My > > >>> guess is there's so much extra hardware and software involved that anyone > > >>> making one of these as a PC card to be used under Unix or NT is unlikely. > > > > > >This is non-sense, but the market for unix is way too small and NT probably > > >doesnt have the hooks to do it properly. It IS a big project, and to do EI > > >would > > >require getting tons of approvals and testing sites......but channelized T1 is > > >more reasonable. We dont plan on doing it though. Can't do everything, and > > >selling unix into high-end scenarios is a tough job. > > > > > >> > > >>Perhaps. However I am interested, and I'm sure many other folks are, > > >>in the interests of ease-of-management. Channelized E1 gear such as > > >>the Ascend MAX 4000 support a whole lot of stuff like ISDN and frame > > >>which we cannot use anyway, but add to the cost (fantastic!) > > > > I'm coming into this in the middle so to speak, and so I'm not sure what > > exactly was being discussed but it sounds like it's related to something > > that I'm interested in, that is ISDN interfaces for BRI & PRI that will > > operate under FreeBSD. > > > > So far, what I've seen are some older cards that used to work under FreeBSD. > > > > What I would like to be able to do is to use it for PPP & MPP. If it could > > accept "voice/modem" calls (aka k56) that would be a win also. I suppose > > that what I want is to able to add the ability of an Ascend 1800 or 2000 > > to a FreeBSD box :^> (Max 1800 handles 8 BRI's, supports upto 16 64k ppp > > links for ~ $6k. Add ~$5k & it supports 16 k56/33.6 channels. The 2000 > > does the same using a PRI.) > > > > So any ideas? > > > > John > > > > ------------------------------------------------------------------------- > > John T. Farmer Proprietor, GoldSword Systems > > jfarmer@goldsword.com Public Internet Access in East Tennessee > > dial-in (423)470-9953 for info, e-mail to info@goldsword.com > > Network Design, Internet Services & Servers, Consulting > > > > > .............. .................................... > Thomas T. Thai Infomedia Interactive Communications > tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 > > > From owner-freebsd-isp Wed Jun 18 07:31:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19307 for isp-outgoing; Wed, 18 Jun 1997 07:31:29 -0700 (PDT) Received: from rif.kconline.com (rif.kconline.com [207.51.167.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19300 for ; Wed, 18 Jun 1997 07:31:24 -0700 (PDT) Received: from localhost (rif@localhost) by rif.kconline.com (8.8.5/8.8.4) with SMTP id JAA29014 for ; Wed, 18 Jun 1997 09:31:09 -0500 (EST) Date: Wed, 18 Jun 1997 09:31:07 -0500 (EST) From: Jim Riffle X-Sender: rif@rif.kconline.com To: freebsd-isp@freebsd.org Subject: Does anyone filter e-mail headers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone out their use any kind of filtering mechanism for peoples incoming mail to strip the routing information from incoming e-mail? The other day I had a customer who though it was just terrible that we did not filter off all that information for them. Personally, I think it is very useful and was wondering if anybody actually does this kind of thing. Thank you, Jim --- Jim Riffle KC Online Unix Systems Administrator rif@nix.kconline.com From owner-freebsd-isp Wed Jun 18 08:02:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA20977 for isp-outgoing; Wed, 18 Jun 1997 08:02:01 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA20932 for ; Wed, 18 Jun 1997 08:01:30 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id KAA18800; Wed, 18 Jun 1997 10:01:27 -0500 (CDT) Date: Wed, 18 Jun 1997 10:01:27 -0500 (CDT) From: "Tom T. Thai" To: listuser cc: "John T. Farmer" , dennis@etinc.com, map@iphil.net, isp@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: Comparison In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I like the PM3s. On Wed, 18 Jun 1997, listuser wrote: > The most cost effective Ascend MAX is the 4048.. It comes with T1/PRI > software and 48 K56 modems and the CSU's for two T1's... > > (Infact it works great :) > > I also have 4002's and 4004's and have a MAX TNT on order for a large pop > I am building.. > > --Matt > > On Tue, 17 Jun 1997, Tom T. Thai wrote: > > > I believe you can with the right drivers. For instance, take a PRI/T1 > > card with MVIP interface and hook it up to a 24 highdensity card via the > > MVIP interface. ISDN is handled by the T1/PRI card and if it detects > > analog, it passes the call to the analog modem card. The hardware is out > > there, but no drivers. > > > > On Tue, 17 Jun 1997, John T. Farmer wrote: > > > > > > > > On Tue Jun 17 11:06:51 1997 dennis said: > > > >At 01:57 PM 6/17/97 +0800, you wrote: > > > >>Hi, > > > >> > > > >>Jon Lewis wrote: > > > >>> I wonder if ET has considered such a thing based on their sync cards? My > > > >>> guess is there's so much extra hardware and software involved that anyone > > > >>> making one of these as a PC card to be used under Unix or NT is unlikely. > > > > > > > >This is non-sense, but the market for unix is way too small and NT probably > > > >doesnt have the hooks to do it properly. It IS a big project, and to do EI > > > >would > > > >require getting tons of approvals and testing sites......but channelized T1 is > > > >more reasonable. We dont plan on doing it though. Can't do everything, and > > > >selling unix into high-end scenarios is a tough job. > > > > > > > >> > > > >>Perhaps. However I am interested, and I'm sure many other folks are, > > > >>in the interests of ease-of-management. Channelized E1 gear such as > > > >>the Ascend MAX 4000 support a whole lot of stuff like ISDN and frame > > > >>which we cannot use anyway, but add to the cost (fantastic!) > > > > > > I'm coming into this in the middle so to speak, and so I'm not sure what > > > exactly was being discussed but it sounds like it's related to something > > > that I'm interested in, that is ISDN interfaces for BRI & PRI that will > > > operate under FreeBSD. > > > > > > So far, what I've seen are some older cards that used to work under FreeBSD. > > > > > > What I would like to be able to do is to use it for PPP & MPP. If it could > > > accept "voice/modem" calls (aka k56) that would be a win also. I suppose > > > that what I want is to able to add the ability of an Ascend 1800 or 2000 > > > to a FreeBSD box :^> (Max 1800 handles 8 BRI's, supports upto 16 64k ppp > > > links for ~ $6k. Add ~$5k & it supports 16 k56/33.6 channels. The 2000 > > > does the same using a PRI.) > > > > > > So any ideas? > > > > > > John > > > > > > ------------------------------------------------------------------------- > > > John T. Farmer Proprietor, GoldSword Systems > > > jfarmer@goldsword.com Public Internet Access in East Tennessee > > > dial-in (423)470-9953 for info, e-mail to info@goldsword.com > > > Network Design, Internet Services & Servers, Consulting > > > > > > > > > .............. .................................... > > Thomas T. Thai Infomedia Interactive Communications > > tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 > > > > > > > > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Wed Jun 18 08:05:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21320 for isp-outgoing; Wed, 18 Jun 1997 08:05:39 -0700 (PDT) Received: from h2o.journey.net (h2o.journey.net [207.227.162.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21314 for ; Wed, 18 Jun 1997 08:05:36 -0700 (PDT) Received: from localhost (listuser@localhost) by h2o.journey.net (8.8.5/8.8.5) with SMTP id LAA27474; Wed, 18 Jun 1997 11:05:25 -0400 (EDT) Date: Wed, 18 Jun 1997 11:05:24 -0400 (EDT) From: listuser To: "Tom T. Thai" cc: "John T. Farmer" , dennis@etinc.com, map@iphil.net, isp@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: Comparison In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk So do I but they don't do dial-up frame-relay :) and some areas in which I am involved don't have PRI only channelized. By the way my cost on a Ascend Max4048 is 16,500 on the livingston PM-3 16,875 Both have 48modems (The Ascend ships with K56Flex cards) Both do PRI but the Ascend can do frame-relay and Channelized T1 service. --Matt From owner-freebsd-isp Wed Jun 18 08:09:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21477 for isp-outgoing; Wed, 18 Jun 1997 08:09:50 -0700 (PDT) Received: from adsight.com (adsight.com [207.86.2.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21471 for ; Wed, 18 Jun 1997 08:09:48 -0700 (PDT) Received: (from webadmin@localhost) by adsight.com (8.8.5/8.6.12) id LAA03277; Wed, 18 Jun 1997 11:08:51 -0400 (EDT) Date: Wed, 18 Jun 1997 11:08:51 -0400 (EDT) From: Sam Magee To: freebsd-isp@freebsd.org Subject: Live video feed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a web customer who wants a live video feed from their place of business to appear on their website. Has anyone done this, or have any suggestions as to the most economical way to go about this? Thanks, Sam Magee webadmin@adsight.com From owner-freebsd-isp Wed Jun 18 08:21:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22166 for isp-outgoing; Wed, 18 Jun 1997 08:21:58 -0700 (PDT) Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22129 for ; Wed, 18 Jun 1997 08:21:08 -0700 (PDT) Received: by noc.demon.net; id QAA01924; Wed, 18 Jun 1997 16:20:34 +0100 (BST) Received: from stress.noc.demon.net(195.11.55.5) by inside.noc.demon.net via smap (3.2) id xma001906; Wed, 18 Jun 97 16:20:28 +0100 Received: from hdm by stress.noc.demon.net with local (Exim 1.61 #3) id 0weMX4-0000o7-00; Wed, 18 Jun 1997 16:20:26 +0100 To: Jim Riffle cc: freebsd-isp@freebsd.org Subject: Re: Does anyone filter e-mail headers X-Mailer: nmh v0.14, exmh 2.0gamma, gvim 4.5 X-Colour: Green In-reply-to: Date: Wed, 18 Jun 1997 16:20:26 +0100 From: Dom Mitchell Message-Id: Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jim Riffle wrote: > > Does anyone out their use any kind of filtering mechanism for peoples > incoming mail to strip the routing information from incoming e-mail? The > other day I had a customer who though it was just terrible that we did > not filter off all that information for them. > > Personally, I think it is very useful and was wondering if anybody > actually does this kind of thing. Which kind of routing information is this? If he means the "Received:" lines, then strippping them out is a really, really, bad, non-standards conforming idea. If he means getting rid of route-addrs, then why are they there in the first place? -Dom From owner-freebsd-isp Wed Jun 18 09:22:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA25394 for isp-outgoing; Wed, 18 Jun 1997 09:22:38 -0700 (PDT) Received: from rainey.blueneptune.com (root@rainey.blueneptune.com [207.104.147.225]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA25382 for ; Wed, 18 Jun 1997 09:22:28 -0700 (PDT) From: michael@blueneptune.com Received: (from michael@localhost) by rainey.blueneptune.com (8.6.12/8.6.12) id JAA18842; Wed, 18 Jun 1997 09:23:02 -0700 Message-Id: <199706181623.JAA18842@rainey.blueneptune.com> Subject: Re: Does anyone filter e-mail headers To: rif@nix.kconline.com (Jim Riffle) Date: Wed, 18 Jun 1997 09:23:01 -0700 (PDT) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Jim Riffle" at Jun 18, 97 09:31:07 am Reply-To: michael@blueneptune.com X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anyone out their use any kind of filtering mechanism for peoples > incoming mail to strip the routing information from incoming e-mail? The > other day I had a customer who though it was just terrible that we did > not filter off all that information for them. I would never filter those headers. They can be extremely helpful for tracking down problems, especially when you get the inevitable complaint "My friend sent this four days ago, and I just got it today. Why are you delaying my mail?" A quick look at the Received headers will show who the most likely culprit is (and it's usually the sending site, the most common being a holdup in the internal forwarding of larger companies.) Besides, most end-user client email software these days will simply not display all of these headers when the user is reading mail. That's the proper place for filtering them --- just don't display them to the user! How different packages do this varies quite a bit --- some will let the user configure what headers are displayed, others just always filter everything except From/Subject/Date/To. Some even make it virtually -impossible- to see the headers. I'd recommend that you talk to your customer about various options in mail clients, and help him find one that filters headers the way he wants. -- Michael Bryan michael@blueneptune.com From owner-freebsd-isp Wed Jun 18 09:55:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27217 for isp-outgoing; Wed, 18 Jun 1997 09:55:36 -0700 (PDT) Received: from helpdesk.euronet.nl (helpdesk.euronet.nl [194.134.1.147]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27212 for ; Wed, 18 Jun 1997 09:55:27 -0700 (PDT) Received: (from sake@localhost) by helpdesk.euronet.nl (8.8.4/8.6.12) id SAA13924; Wed, 18 Jun 1997 18:55:00 +0200 (MET DST) From: Sake Blok Message-Id: <199706181655.SAA13924@helpdesk.euronet.nl> Subject: Re: Does anyone filter e-mail headers To: rif@nix.kconline.com (Jim Riffle) Date: Wed, 18 Jun 1997 18:55:00 +0200 (MET DST) Cc: freebsd-isp@FreeBSD.ORG Reply-To: sake@euronet.nl In-Reply-To: from "Jim Riffle" at Jun 18, 97 09:31:07 am X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does anyone out their use any kind of filtering mechanism for peoples > incoming mail to strip the routing information from incoming e-mail? The > other day I had a customer who though it was just terrible that we did > not filter off all that information for them. > > Personally, I think it is very useful and was wondering if anybody > actually does this kind of thing. After you strip them some other customer will complain about not being able to protest against spam-mail at the source. I'd suggest you'd keep'em in (and advice the user to deselect 'show all headers' ;-) Sake -- Sake Blok * * EuroNet Internet Client Services Team * * Herengracht 208 - 214 * 1016 BS Amsterdam E-mail: sake@nl.euro.net * Tel: +31 20 625 61 61 From owner-freebsd-isp Wed Jun 18 10:36:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29236 for isp-outgoing; Wed, 18 Jun 1997 10:36:07 -0700 (PDT) Received: from dilbert.iagnet.net (root@dilbert.iagnet.net [207.206.8.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29166 for ; Wed, 18 Jun 1997 10:35:59 -0700 (PDT) Received: (from jamie@localhost) by dilbert.iagnet.net (8.8.6/8.8.6) id NAA09335; Wed, 18 Jun 1997 13:35:40 -0400 (EDT) Message-Id: <199706181735.NAA09335@dilbert.iagnet.net> Subject: Re: Does anyone filter e-mail headers To: hdm@demon.net (Dom Mitchell) Date: Wed, 18 Jun 1997 13:35:39 -0400 (EDT) Cc: rif@nix.kconline.com, freebsd-isp@FreeBSD.ORG In-Reply-To: from Dom Mitchell at "Jun 18, 97 04:20:26 pm" RFC_Violation: You saw it here first! From: jamie@dilbert.iagnet.net (Jamie Rishaw) X-PGP-Fingerprint: <921C135D> C4 48 1B 26 18 7B 1F D9 BA C4 9C 7A B1 07 07 E8 Reply-To: jamie@dilbert.iagnet.net Organization: Internet Access Group, Inc. X-No-Archive: yes X-Face: >:-p X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Point out to him that RFC822 says you need Received in there: -snip- received = "Received" ":" ; one per relay ["from" domain] ; sending host ["by" domain] ; receiving host ["via" atom] ; physical path *("with" atom) ; link/mail protocol ["id" msg-id] ; receiver msg id ["for" addr-spec] ; initial form -snip- Tell him that if you take it out, the company that runs the InterNet might prosecute you or something ;-) > Jim Riffle wrote: > > > > Does anyone out their use any kind of filtering mechanism for peoples > > incoming mail to strip the routing information from incoming e-mail? The > > other day I had a customer who though it was just terrible that we did > > not filter off all that information for them. > > > > Personally, I think it is very useful and was wondering if anybody > > actually does this kind of thing. > > Which kind of routing information is this? If he means the "Received:" > lines, then strippping them out is a really, really, bad, non-standards > conforming idea. If he means getting rid of route-addrs, then why are > they there in the first place? > > -Dom > -- jamie g.k. rishaw dal/efnet:gavroche Internet Access Group 'whois JGR2' for PGP keyID/Fingerprint __ Network Operations/TSD DID:216.902.5455 FAX:216.623.3566 \/ 800.637.4IAGx5455 DES: Help Crack the code! http://www.frii.com/~rcv/deschall.htm From owner-freebsd-isp Wed Jun 18 12:51:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07230 for isp-outgoing; Wed, 18 Jun 1997 12:51:38 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07205 for ; Wed, 18 Jun 1997 12:51:24 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id OAA22870 for ; Wed, 18 Jun 1997 14:52:04 -0500 (CDT) Date: Wed, 18 Jun 1997 14:52:04 -0500 (CDT) From: "Tom T. Thai" To: freebsd-isp@FreeBSD.ORG Subject: Strange INN error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I got this error from /var/log/news/nntpsend: Can't authenticate with news-in.server.com, Numerical argument out of domain the same error in /var/log/messages: ...innxmit(15180) news-in.server.com authenticate failed Numerical arguement out of domain What does this mean? .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Thu Jun 19 00:05:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11831 for isp-outgoing; Thu, 19 Jun 1997 00:05:09 -0700 (PDT) Received: from unagi.cybernothing.org (unagi.cybernothing.org [207.96.1.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11808 for ; Thu, 19 Jun 1997 00:04:59 -0700 (PDT) Received: (from jdfalk@localhost) by unagi.cybernothing.org (8.8.5/8.8.5/JDF-9705.06) id DAA10380; Thu, 19 Jun 1997 03:04:51 -0400 (EDT) Message-ID: <19970619030451.41260@cybernothing.org> Date: Thu, 19 Jun 1997 03:04:51 -0400 From: "J.D. Falk" To: "Tom T. Thai" Cc: Dave Richards , freebsd-isp@FreeBSD.ORG Subject: Re: Email store-and-forward + SMTP finger References: <339DB082.46D1@illumen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 In-Reply-To: [9706.10] X-Editor: nvi X-Comment: Stop e-mail spam for good! http://www.cauce.org/ Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 10, "Tom T. Thai" wrote: > Hmm.. we have been doing UUCP for this.. maybe I'm missing something? > Does POP3 allow for different email accounts dumped to one "account?" And > how does the other end parse it out? POP3 certainly won't stop you. For example, you can have an entry in your virtusertable (assuming you compiled sendmail with that feature; I don't think it's default yet) such as: @mydomain.com mydomain@freebsd.org and then the company in question will retreive the mail via POP and sort it out somehow on their end. I've heard of a number of people doing this with such packages as Eudora Pro, but I haven't tried it myself. If you want to get semi-seriously into sendmail hacking then there are -- in theory -- a number of ways you could accomplish something like this. I think the book _Sendmail Theory & Practice_ has some info on it, but mine's packed up in a box right now (I just moved to California, yay!) so I'm not certain. -- J.D. Falk, Supervisor, Network Operations +1 (415) 482-2840 Priori Networks, Inc. http://www.priori.net "The people you know. The people you trust." From owner-freebsd-isp Thu Jun 19 00:07:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11918 for isp-outgoing; Thu, 19 Jun 1997 00:07:07 -0700 (PDT) Received: from unagi.cybernothing.org (unagi.cybernothing.org [207.96.1.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11911 for ; Thu, 19 Jun 1997 00:07:01 -0700 (PDT) Received: (from jdfalk@localhost) by unagi.cybernothing.org (8.8.5/8.8.5/JDF-9705.06) id DAA10393; Thu, 19 Jun 1997 03:06:29 -0400 (EDT) Message-ID: <19970619030628.00320@cybernothing.org> Date: Thu, 19 Jun 1997 03:06:28 -0400 From: "J.D. Falk" To: Bernie Doehner Cc: Dave Richards , freebsd-isp@FreeBSD.ORG Subject: Re: Email store-and-forward + SMTP finger References: <339DB082.46D1@illumen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 In-Reply-To: [9706.11] X-Editor: nvi X-Comment: Stop e-mail spam for good! http://www.cauce.org/ Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 11, Bernie Doehner wrote: > Actualy, I think I almost figured it out. > > In sendmail.cf, there is OT5d/4h > > Would setting this to OT5d/0h turn off the first warning message? Not exactly -- you'd want to get rid of the second entry altogether. I'd strongly suggest upgrading to a newer version of sendmail, though (8.8.x has those as two seperate settings, instead of the confusing slash thing.) -- J.D. Falk, Supervisor, Network Operations +1 (415) 482-2840 Priori Networks, Inc. http://www.priori.net "The people you know. The people you trust." From owner-freebsd-isp Thu Jun 19 01:27:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15982 for isp-outgoing; Thu, 19 Jun 1997 01:27:36 -0700 (PDT) Received: from topgun.asiapac.net (topgun.asiapac.net [202.188.0.106]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA15975 for ; Thu, 19 Jun 1997 01:27:27 -0700 (PDT) Received: from dogbert ([202.188.0.67]) by topgun.asiapac.net (Netscape Mail Server v2.0) with SMTP id AAA5224; Thu, 19 Jun 1997 16:25:46 +0800 Message-Id: <3.0.32.19970619162817.0069e848@pop.tm.net.my> X-Sender: sckhoo@pop.tm.net.my X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 19 Jun 1997 16:28:19 +0800 To: "J.D. Falk" , "Tom T. Thai" From: sckhoo@asiapac.net (Swee-Chuan Khoo) Subject: Re: Email store-and-forward + SMTP finger Cc: Dave Richards , freebsd-isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 03:04 AM 6/19/97 -0400, J.D. Falk wrote: >@mydomain.com mydomain@freebsd.org > > and then the company in question will retreive the mail > via POP and sort it out somehow on their end. I've heard > of a number of people doing this with such packages as > Eudora Pro, but I haven't tried it myself. yes, that will work if the mail is not coming from a mailing list, right? becos the mail will not contain any receiver's email id. I tried to do this using a pop server and popclient software on another machine, it works ok, but i need to fix the mailing list problem before i can sell the service. any idea? +-------------------------------------------+ | Swee-Chuan Khoo - sckhoo@asiapac.net | | 603-7337757 ( voice ) 603-7345577 ( fax ) | | sckhoo@tm.net.my, sckhoo@asiapac.net | | #include | +-------------------------------------------+ "Don't just do something, sit there" - anon From owner-freebsd-isp Thu Jun 19 04:30:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA23030 for isp-outgoing; Thu, 19 Jun 1997 04:30:39 -0700 (PDT) Received: from wireless.4d.net (wireless.4d.net [207.137.156.159]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA23025 for ; Thu, 19 Jun 1997 04:30:36 -0700 (PDT) Received: from uhf.wdc.net (uhf.4d.net [207.137.157.140]) by wireless.4d.net (8.8.4/8.8.4) with ESMTP id EAA07502; Thu, 19 Jun 1997 04:31:06 -0700 (PDT) Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id HAA06767; Thu, 19 Jun 1997 07:30:28 -0400 (EDT) Date: Thu, 19 Jun 1997 07:30:23 -0400 (EDT) From: Bernie Doehner To: "J.D. Falk" cc: Bernie Doehner , Dave Richards , freebsd-isp@FreeBSD.ORG Subject: Re: Email store-and-forward + SMTP finger In-Reply-To: <19970619030628.00320@cybernothing.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In sendmail.cf, there is OT5d/4h > > > > Would setting this to OT5d/0h turn off the first warning message? > > Not exactly -- you'd want to get rid of the second entry > altogether. I'd strongly suggest upgrading to a newer > version of sendmail, though (8.8.x has those as two > seperate settings, instead of the confusing slash thing.) I should have posted a followup. Yes, I turned off the second entry altogether, once I realized that the MX is using a 8.8.x ish sendmail.cf and it's working well. Thanks. Bernie From owner-freebsd-isp Thu Jun 19 13:26:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16056 for isp-outgoing; Thu, 19 Jun 1997 13:26:23 -0700 (PDT) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15938 for ; Thu, 19 Jun 1997 13:23:05 -0700 (PDT) Received: from mirage.nlink.com.br (localhost.nlink.com.br [127.0.0.1]) by mirage.nlink.com.br (8.8.5/8.8.5) with ESMTP id RAA27512 for ; Thu, 19 Jun 1997 17:15:26 -0300 (EST) Message-ID: <33A9935E.8BA55934@nlink.com.br> Date: Thu, 19 Jun 1997 17:15:26 -0300 From: Paulo Fragoso Organization: Nlink Com. & Cons. X-Mailer: Mozilla 4.0b5C (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: PPPD whith +pap and login (whoami?) X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I wuold like write a script for many things. But I don't know get UID when my users are logged whith pppd using "+pap login auth". This script is started from getty whith ":de#2:np:sp#115200:pp=/usr/local/etc/pwin:". Pppd write in the file wtmp the username but 'pwin' script has UID=0. Are there any solution whithout write anything in some file to get username? Thanks, Paulo. From owner-freebsd-isp Thu Jun 19 14:04:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA19255 for isp-outgoing; Thu, 19 Jun 1997 14:04:59 -0700 (PDT) Received: from lightning.tbe.net (qmailr@lightning.tbe.net [208.208.122.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA19223 for ; Thu, 19 Jun 1997 14:04:36 -0700 (PDT) Received: (qmail 21528 invoked by uid 1010); 19 Jun 1997 20:58:56 -0000 Date: Thu, 19 Jun 1997 16:58:56 -0400 (EDT) From: "Gary D. Margiotta" To: freebsd-isp@freebsd.org Subject: gigabyte motherboards Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just a quick (hopefully) question regarding gigabyte motherboards... We are currently running a Gigabyte GA-586HX board, and plan on getting another, but I wanted to know if anybody knew whether the GA-586-S board with the SIS chipset rather than the Intel was any better or worse. Personally, I think worse because it is cheaper, but you never know. TIA! -Gary Margiotta TBE Internet Services http://www.tbe.net From owner-freebsd-isp Thu Jun 19 17:10:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA28527 for isp-outgoing; Thu, 19 Jun 1997 17:10:42 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28510 for ; Thu, 19 Jun 1997 17:10:24 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id KAA10958; Fri, 20 Jun 1997 10:07:49 +1000 (EST) Date: Fri, 20 Jun 1997 10:07:47 +1000 (EST) From: "Daniel O'Callaghan" To: Paulo Fragoso cc: freebsd-isp@FreeBSD.ORG Subject: Re: PPPD whith +pap and login (whoami?) In-Reply-To: <33A9935E.8BA55934@nlink.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Paulo Fragoso wrote: > I wuold like write a script for many things. But I don't know get UID > when my users are logged whith pppd using "+pap login auth". This script > is started from getty whith > ":de#2:np:sp#115200:pp=/usr/local/etc/pwin:". > > Pppd write in the file wtmp the username but 'pwin' script has UID=0. > Are there any solution whithout write anything in some file to get > username? Think about it carefully. pwin is started by root, as is pppd. pppd does not know who is logging on until it has been started and negotiates a user/password. pwin *never* knows who is going to log on. Try using the ppp-up, ppp-down scripts for what you are trying to do, whatever that is. /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-isp Thu Jun 19 17:48:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA00415 for isp-outgoing; Thu, 19 Jun 1997 17:48:18 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00401 for ; Thu, 19 Jun 1997 17:48:12 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id KAA11120; Fri, 20 Jun 1997 10:47:59 +1000 (EST) Date: Fri, 20 Jun 1997 10:47:58 +1000 (EST) From: "Daniel O'Callaghan" To: "Gary D. Margiotta" cc: freebsd-isp@FreeBSD.ORG Subject: Re: gigabyte motherboards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Gary D. Margiotta wrote: > Just a quick (hopefully) question regarding gigabyte motherboards... > > We are currently running a Gigabyte GA-586HX board, and plan on getting > another, but I wanted to know if anybody knew whether the GA-586-S board > with the SIS chipset rather than the Intel was any better or worse. > Personally, I think worse because it is cheaper, but you never know. TIA! Have a look at the chipset comments at http://sysdoc.pair.com/chipset.html It is hard to make a direct comparison. It would be nice if Gigabyte published useful stuff on their site (www.giga-byte.com). Let me know if you try the 586-S. Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-isp Thu Jun 19 20:29:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA07222 for isp-outgoing; Thu, 19 Jun 1997 20:29:03 -0700 (PDT) Received: from npc.haplink.co.cn ([202.96.192.53]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07165 for ; Thu, 19 Jun 1997 20:28:04 -0700 (PDT) Received: (from xiyuan@localhost) by npc.haplink.co.cn (8.8.4/8.6.9) id IAA09890 for isp@freebsd.org; Fri, 20 Jun 1997 08:56:02 GMT Date: Fri, 20 Jun 1997 08:56:02 GMT From: xiyuan qian Message-Id: <199706200856.IAA09890@npc.haplink.co.cn> To: isp@freebsd.org Subject: crash? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, what's mean of the "crash" word in wtmp file? Today, I enter the last command to check the login and suddenly find there is many crashes in the last record. What's wrong about my host? My host acts as a mail server and DNS server and tacacs server. Best regards! --xiyuan From owner-freebsd-isp Thu Jun 19 21:56:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10935 for isp-outgoing; Thu, 19 Jun 1997 21:56:35 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10929 for ; Thu, 19 Jun 1997 21:56:28 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id OAA11963; Fri, 20 Jun 1997 14:53:35 +1000 (EST) Date: Fri, 20 Jun 1997 14:53:34 +1000 (EST) From: "Daniel O'Callaghan" To: xiyuan qian cc: isp@FreeBSD.ORG Subject: Re: crash? In-Reply-To: <199706200856.IAA09890@npc.haplink.co.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, xiyuan qian wrote: > Hi, what's mean of the "crash" word in wtmp file? Today, I enter the last > command to check the login and suddenly find there is many crashes in > the last record. What's wrong about my host? My host acts as a mail server > and DNS server and tacacs server. 'crash' means that there was no 'shutdown' entry in wtmp before a 'reboot' entry. It means that the system was rebooted without being shut down properly. What does uptime tell you? /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-isp Fri Jun 20 02:49:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24322 for isp-outgoing; Fri, 20 Jun 1997 02:49:22 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24315; Fri, 20 Jun 1997 02:49:08 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id KAA28868; Fri, 20 Jun 1997 10:48:29 +0100 (BST) Message-ID: <19970620104829.34842@pavilion.net> Date: Fri, 20 Jun 1997 10:48:29 +0100 From: Josef Karthauser To: questions@freebsd.org, hackers@freebsd.org Cc: isp@freebsd.org Subject: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The continuing saga of a sick web machine :( A brief history. We're running a P200pro FBSD2.2.2 machine here as a virtual web server. It currently has 130ish web servers running, each with their own IP address. Where did the problem start? I'm not sure, but it was some combination of reaching 124ish web servers, and hitting a certain number of active http connections. The web server is basically fine, until some limit gets reached and the server then just hangs, with lots of sockets still active. I've tried unlimiting the shell entirely, that we run the httpd from. I've tried adding an entry for the web user to /etc/login.conf: web:\ :path=/usr/local/news/bin /bin /sbin /usr/bin /usr/sbin:\ :cputime=infinity:\ :filesize=128M:\ :datasize-curr=64M:\ :stacksize-cur=32M:\ :coredumpsize-cur=0:\ :maxmemorysize-cur=128M:\ :memorylocked=32M:\ :maxproc=1000:\ :maxproc-cur=1000:\ :openfiles=2000:\ :openfiles-cur=2000:\ :tc=default: This has been bound to the web user in the password file: webboss:*:1011:1011:web:0:0:Web Boss:/nonexistent:/bin/false This still didn't solve the problem. (We'd find loads of sockets in FIN_WAIT_2 when the process hung.) Next stage was to recompile the kernel to raise SOMAXCONN. Here's a fragment from our config file: ----------------------------- machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident PAVILION maxusers 256 # joe/pavilion/19970529: Our machines have 96Mb of memory options "MAXMEM=96*1024" # joe/pavilion/19970619: jungled the maximum number of connections options SOMAXCONN=1024 options INET #InterNETworking options FFS #Berkeley Fast Filesystem ----------------------------- When I arrived this morning the web server had hung again. Looking at netstat it appears to be better, in as much as there are no FIN_WAIT2's. The whole netstat is included below. The apache that we're running at the moment is 1.1.3. I've tried running 1.2.0 under the above conditions, but it wont start with more than 124 virtual hosts defined. It just complains that it can't look up the name of the main server. It sounds like it's hit a file descriptor limit, but I know that this isn't the case because: dougal# unlimit dougal# limit cputime unlimited filesize unlimited datasize 131072 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited memorylocked unlimited maxproc 4115 openfiles 8232 Fun and games or what!! Any suggestions, other than a full frontal labotamy, would gratefully be received. Joe ------------------------------ Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 450 0 194.242.128.16.80 132.236.77.25.4902 ESTABLISHED tcp 0 2 194.242.128.16.23 194.242.128.8.54274 ESTABLISHED tcp 179 0 194.242.128.16.80 208.200.99.17.39158 CLOSE_WAIT tcp 0 0 194.242.132.36.21 195.92.128.66.2949 ESTABLISHED tcp 593 0 194.242.128.16.80 194.216.92.1.39331 ESTABLISHED tcp 448 0 194.242.128.16.80 132.236.77.25.2229 ESTABLISHED tcp 342 0 194.242.128.16.80 192.100.101.6.2769 CLOSE_WAIT tcp 190 0 194.242.128.16.80 194.238.8.2.4428 CLOSE_WAIT tcp 98 0 194.242.128.16.80 206.117.147.5.1540 CLOSE_WAIT tcp 183 0 194.242.132.94.80 158.152.68.58.1256 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1863 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1837 CLOSE_WAIT tcp 506 0 194.242.128.16.80 134.239.84.2.4479 CLOSE_WAIT tcp 183 0 194.242.132.94.80 158.152.68.58.1253 CLOSE_WAIT tcp 174 0 194.242.128.16.80 194.242.131.158.1028 ESTABLISHED tcp 256 0 194.242.132.15.80 194.170.1.141.35479 CLOSE_WAIT tcp 376 0 194.242.132.86.80 148.88.11.117.2246 CLOSE_WAIT tcp 219 0 194.242.128.16.80 194.74.164.12.53444 ESTABLISHED tcp 506 0 194.242.128.16.80 134.239.84.2.4474 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1812 CLOSE_WAIT tcp 434 0 194.242.128.16.80 134.239.84.2.4473 CLOSE_WAIT tcp 484 0 194.242.128.16.80 151.120.84.6.2817 ESTABLISHED tcp 237 0 194.242.128.16.80 195.86.14.170.4484 ESTABLISHED tcp 334 0 194.242.128.16.80 194.88.74.2.3506 CLOSE_WAIT tcp 232 0 194.242.128.16.80 202.219.149.5.1552 CLOSE_WAIT tcp 272 0 194.242.128.16.80 194.242.131.83.1030 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1786 CLOSE_WAIT tcp 219 0 194.242.128.16.80 194.74.164.12.53436 ESTABLISHED tcp 269 0 194.242.128.16.80 202.32.150.23.2872 ESTABLISHED tcp 181 0 194.242.132.73.80 209.1.12.107.44178 CLOSE_WAIT tcp 376 0 194.242.128.16.80 194.242.131.156.1837 ESTABLISHED tcp 368 0 194.242.128.16.80 207.139.25.25.1548 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1761 CLOSE_WAIT tcp 397 0 194.242.132.113.80 193.113.139.190.4681 CLOSE_WAIT tcp 259 0 194.242.132.77.80 158.152.170.36.2057 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.4477 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.4476 CLOSE_WAIT tcp 182 0 194.242.132.92.80 204.123.9.20.1689 CLOSE_WAIT tcp 386 0 194.242.128.16.80 129.194.12.50.44910 CLOSE_WAIT tcp 91 0 194.242.132.67.80 204.62.245.168.52059 CLOSE_WAIT tcp 259 0 194.242.132.77.80 158.152.170.36.2056 CLOSE_WAIT tcp 295 0 194.242.132.47.80 195.4.24.129.1232 ESTABLISHED tcp 0 0 194.242.128.16.80 194.242.128.24.1735 CLOSE_WAIT tcp 201 0 194.242.128.16.80 161.112.192.10.34007 CLOSE_WAIT tcp 240 0 194.242.132.61.80 194.152.71.133.1300 ESTABLISHED tcp 202 0 194.242.128.16.80 208.200.99.17.36367 CLOSE_WAIT tcp 201 0 194.242.128.16.80 208.200.99.17.36343 CLOSE_WAIT tcp 438 0 194.242.128.16.80 134.239.84.2.4429 CLOSE_WAIT tcp 353 0 194.242.132.47.80 195.4.24.129.1218 ESTABLISHED tcp 438 0 194.242.128.16.80 134.239.84.2.4404 CLOSE_WAIT tcp 234 0 194.242.132.12.80 193.190.194.200.2889 ESTABLISHED tcp 198 0 194.242.132.13.80 204.123.9.20.4438 CLOSE_WAIT tcp 195 0 194.242.128.16.80 208.200.99.17.36281 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1703 CLOSE_WAIT tcp 201 0 194.242.128.16.80 208.200.99.17.36271 CLOSE_WAIT tcp 90 0 194.242.128.16.80 206.249.9.2.2766 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.2014 CLOSE_WAIT tcp 90 0 194.242.128.16.80 206.249.9.2.2765 CLOSE_WAIT tcp 111 0 194.242.132.22.80 204.62.245.167.34399 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.1879 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.1813 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.1812 CLOSE_WAIT tcp 506 0 194.242.128.16.80 134.239.84.2.4371 CLOSE_WAIT tcp 236 0 194.242.132.16.80 152.163.207.135.48836 ESTABLISHED tcp 94 0 194.242.132.108.80 204.62.245.168.49494 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1678 CLOSE_WAIT tcp 458 0 194.242.128.16.80 134.239.84.2.4365 CLOSE_WAIT tcp 353 0 194.242.132.47.80 195.4.24.129.1119 ESTABLISHED tcp 257 0 194.242.132.92.80 192.195.167.3.41145 CLOSE_WAIT tcp 458 0 194.242.128.16.80 134.239.84.2.4363 CLOSE_WAIT tcp 353 0 194.242.132.47.80 195.4.24.129.1116 ESTABLISHED tcp 269 0 194.242.128.16.80 202.32.150.23.2869 CLOSE_WAIT tcp 458 0 194.242.128.16.80 134.239.84.2.4362 CLOSE_WAIT tcp 186 0 194.242.128.16.80 208.200.99.17.36063 CLOSE_WAIT tcp 293 0 194.242.132.16.80 152.163.207.135.45099 ESTABLISHED tcp 222 0 194.242.132.52.80 202.190.35.126.1144 ESTABLISHED tcp 183 0 194.242.132.94.80 158.152.68.58.1210 CLOSE_WAIT tcp 177 0 194.242.132.93.80 209.1.12.108.36299 CLOSE_WAIT tcp 221 0 194.242.132.10.80 192.71.13.14.47797 CLOSE_WAIT tcp 239 0 194.242.132.36.80 194.52.244.35.1049 ESTABLISHED tcp 505 0 194.242.128.16.80 193.63.255.1.53161 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1652 CLOSE_WAIT tcp 90 0 194.242.132.77.80 204.62.245.168.48250 CLOSE_WAIT tcp 269 0 194.242.128.16.80 202.32.150.23.2866 CLOSE_WAIT tcp 515 0 194.242.132.17.80 163.195.1.153.1522 CLOSE_WAIT tcp 199 0 194.242.128.16.80 208.200.99.17.35924 CLOSE_WAIT tcp 268 0 194.242.128.16.80 152.170.9.196.2927 CLOSE_WAIT tcp 469 0 194.242.128.16.80 134.239.84.2.4359 CLOSE_WAIT tcp 113 0 194.242.128.16.80 204.62.245.32.35501 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1520 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1627 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3369 CLOSE_WAIT tcp 243 0 194.242.128.16.80 195.232.30.131.2101 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1409 CLOSE_WAIT tcp 190 0 194.242.128.16.80 194.238.8.2.4308 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3368 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.2382 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.2358 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.2356 CLOSE_WAIT tcp 330 0 194.242.132.22.80 203.8.223.2.28346 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1601 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3367 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1190 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3366 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.1137 CLOSE_WAIT tcp 109 0 194.242.132.24.80 206.14.154.191.53983 ESTABLISHED tcp 152 0 194.242.128.16.80 193.133.92.249.1143 CLOSE_WAIT tcp 515 0 194.242.132.17.80 163.195.1.153.1195 CLOSE_WAIT tcp 263 0 194.242.128.16.80 206.173.210.46.1214 CLOSE_WAIT tcp 194 0 194.242.132.12.80 134.105.16.250.3365 CLOSE_WAIT tcp 469 0 194.242.132.22.80 203.8.223.2.25264 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1576 CLOSE_WAIT tcp 255 0 194.242.132.101.80 193.130.245.65.2034 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.4936 CLOSE_WAIT tcp 152 0 194.242.128.16.80 193.133.92.249.1136 CLOSE_WAIT tcp 328 0 194.242.128.16.80 192.100.101.6.3792 CLOSE_WAIT tcp 345 0 194.242.128.16.80 194.235.21.6.2010 CLOSE_WAIT tcp 288 0 194.242.132.33.80 194.164.0.34.1116 ESTABLISHED tcp 360 0 194.242.128.16.80 192.100.101.6.3667 CLOSE_WAIT tcp 284 0 194.242.128.16.80 194.238.50.8.2472 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1544 CLOSE_WAIT tcp 248 0 194.242.128.16.80 202.158.8.41.1036 CLOSE_WAIT tcp 275 0 194.242.132.96.80 198.242.49.1.2055 CLOSE_WAIT tcp 307 0 194.242.128.16.80 163.137.8.131.2098 CLOSE_WAIT tcp 297 0 194.242.132.10.80 198.164.97.26.1416 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1519 CLOSE_WAIT tcp 98 0 194.242.128.16.80 206.117.147.5.1501 CLOSE_WAIT tcp 342 0 194.242.128.16.80 192.100.101.6.3211 CLOSE_WAIT tcp 563 0 194.242.132.92.80 192.189.54.2.52946 CLOSE_WAIT tcp 98 0 194.242.128.16.80 206.117.147.3.4743 CLOSE_WAIT tcp 464 0 194.242.132.77.80 145.228.48.120.1190 CLOSE_WAIT tcp 243 0 194.242.128.16.80 193.133.92.249.4992 CLOSE_WAIT tcp 303 0 194.242.128.16.80 193.130.252.110.2757 CLOSE_WAIT tcp 302 0 194.242.128.16.80 152.163.197.35.54381 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1493 CLOSE_WAIT tcp 94 0 194.242.132.108.80 204.62.245.168.42228 CLOSE_WAIT tcp 302 0 194.242.128.16.80 152.163.197.35.53574 CLOSE_WAIT tcp 201 0 194.242.128.16.80 161.112.192.10.34006 CLOSE_WAIT tcp 299 0 194.242.128.16.80 152.163.197.35.51812 CLOSE_WAIT tcp 469 0 194.242.132.104.80 192.189.54.2.51384 CLOSE_WAIT tcp 412 0 194.242.132.86.80 193.113.139.190.4406 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1467 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.4365 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.4362 CLOSE_WAIT tcp 271 0 194.242.128.16.80 195.212.234.226.4412 CLOSE_WAIT tcp 191 0 194.242.132.92.80 203.102.82.2.3565 CLOSE_WAIT tcp 185 0 194.242.132.59.80 209.1.12.113.36894 CLOSE_WAIT tcp 114 0 194.242.132.22.80 204.62.245.32.64282 CLOSE_WAIT tcp 301 0 194.242.128.16.80 152.163.197.35.47158 CLOSE_WAIT tcp 248 0 194.242.132.77.80 158.152.170.36.1979 CLOSE_WAIT tcp 243 0 194.242.128.16.80 193.133.92.249.4954 CLOSE_WAIT tcp 266 0 194.242.128.16.80 152.163.205.34.36163 CLOSE_WAIT tcp 395 0 194.242.128.16.80 205.138.230.67.1657 ESTABLISHED tcp 0 0 194.242.128.16.80 194.242.128.24.1435 CLOSE_WAIT tcp 301 0 194.242.128.16.80 152.163.197.35.43958 CLOSE_WAIT tcp 219 0 194.242.132.22.80 203.2.193.70.3710 CLOSE_WAIT tcp 219 0 194.242.132.22.80 203.2.193.70.3667 CLOSE_WAIT tcp 180 0 194.242.132.41.80 209.1.12.108.35039 CLOSE_WAIT tcp 477 0 194.242.128.16.80 194.222.193.246.2374 ESTABLISHED tcp 339 0 194.242.132.96.80 198.242.49.1.2380 CLOSE_WAIT tcp 307 0 194.242.128.16.80 163.137.8.131.1800 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.2328 CLOSE_WAIT tcp 405 0 194.242.132.86.80 193.113.139.190.2314 CLOSE_WAIT tcp 411 0 194.242.132.86.80 193.113.139.190.2312 CLOSE_WAIT tcp 479 0 194.242.132.22.80 194.222.193.246.2372 ESTABLISHED tcp 0 0 194.242.128.16.80 194.242.128.24.1410 CLOSE_WAIT tcp 479 0 194.242.132.22.80 194.222.193.246.2369 ESTABLISHED tcp 222 0 194.242.128.16.80 136.152.64.115.1168 CLOSE_WAIT tcp 387 0 194.242.132.32.80 194.242.128.144.1363 ESTABLISHED tcp 299 0 194.242.132.22.80 203.2.193.70.3421 CLOSE_WAIT tcp 348 0 194.242.128.16.80 194.242.130.162.1029 ESTABLISHED tcp 463 0 194.242.128.16.80 194.222.193.246.2367 ESTABLISHED tcp 281 0 194.242.128.16.80 152.163.205.25.3792 ESTABLISHED tcp 299 0 194.242.132.22.80 203.2.193.70.3217 CLOSE_WAIT tcp 469 0 194.242.132.104.80 192.189.54.2.47330 CLOSE_WAIT tcp 423 0 194.242.128.16.80 194.235.21.6.1994 CLOSE_WAIT tcp 267 0 194.242.128.16.80 194.151.78.79.1074 ESTABLISHED tcp 272 0 194.242.128.16.80 194.151.78.79.1072 ESTABLISHED tcp 299 0 194.242.132.22.80 203.2.193.70.3153 CLOSE_WAIT tcp 314 0 194.242.128.16.80 194.74.164.12.53345 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1384 CLOSE_WAIT tcp 247 0 194.242.128.16.80 195.232.30.131.1093 CLOSE_WAIT tcp 245 0 194.242.128.16.80 195.232.30.131.1677 CLOSE_WAIT tcp 244 0 194.242.128.16.80 195.232.30.131.1568 CLOSE_WAIT tcp 422 0 194.242.128.16.80 202.96.65.30.1996 ESTABLISHED tcp 423 0 194.242.128.16.80 194.235.21.6.1993 CLOSE_WAIT tcp 98 0 194.242.132.36.80 204.62.245.32.62339 CLOSE_WAIT tcp 309 0 194.242.128.16.80 152.163.205.34.35414 CLOSE_WAIT tcp 410 0 194.242.132.86.80 193.113.139.190.3876 CLOSE_WAIT tcp 232 0 194.242.132.28.80 194.152.162.248.1183 ESTABLISHED tcp 235 0 194.242.132.28.80 194.152.162.248.1182 ESTABLISHED tcp 201 0 194.242.128.16.80 161.112.192.10.34005 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.242.128.24.1350 CLOSE_WAIT tcp 93 0 194.242.128.16.80 206.14.14.180.2538 CLOSE_WAIT tcp 258 0 194.242.128.16.80 130.54.61.13.1256 CLOSE_WAIT tcp 0 0 194.242.128.16.80 193.133.92.249.4784 CLOSE_WAIT tcp 0 0 194.242.128.16.80 163.137.8.131.4805 CLOSE_WAIT tcp 0 0 194.242.132.12.80 132.166.52.28.2199 CLOSE_WAIT tcp 0 0 194.242.128.16.80 193.133.96.130.2222 ESTABLISHED tcp 0 0 194.242.128.16.80 193.215.220.104.2231 ESTABLISHED tcp 0 0 194.242.128.16.80 138.25.2.20.51082 CLOSE_WAIT tcp 0 0 194.242.132.36.80 195.16.0.26.46365 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.119.231.99.1253 CLOSE_WAIT tcp 0 0 194.242.132.22.80 193.6.20.1.1088 CLOSE_WAIT tcp 0 0 194.242.128.16.80 194.30.38.200.62426 CLOSE_WAIT tcp 0 0 194.242.128.16.80 195.76.129.30.31184 CLOSE_WAIT tcp 0 0 194.242.132.66.80 163.119.254.17.1850 CLOSE_WAIT udp 0 0 194.242.128.16.3065 194.242.128.1.53 udp 0 0 194.242.128.16.2630 194.242.128.1.53 udp 0 0 194.242.128.16.2606 194.242.128.1.53 udp 0 0 194.242.128.16.2605 194.242.128.1.53 udp 0 0 194.242.128.16.2603 194.242.128.1.53 udp 0 0 194.242.128.16.2577 194.242.128.1.53 udp 0 0 194.242.128.16.2039 194.242.128.1.53 udp 0 0 194.242.128.16.2030 194.242.128.1.53 udp 0 0 194.242.128.16.2025 194.242.128.1.53 udp 0 0 194.242.128.16.2008 194.242.128.1.53 udp 0 0 194.242.128.16.1685 194.242.128.1.53 udp 0 0 194.242.128.16.1287 194.242.128.1.53 udp 0 0 194.242.128.16.1232 194.242.128.1.53 udp 0 0 194.242.128.16.1154 194.242.128.1.53 udp 0 0 194.242.128.16.4448 194.242.128.1.53 udp 0 0 194.242.128.16.4293 194.242.128.1.53 udp 0 0 194.242.128.16.4121 194.242.128.1.53 udp 0 0 194.242.128.16.3903 194.242.128.1.53 udp 0 0 194.242.128.16.1081 194.242.128.1.53 udp 0 0 194.242.128.16.3686 194.242.128.1.53 udp 0 0 194.242.128.16.2552 194.242.128.1.53 udp 0 0 194.242.128.16.2645 194.242.128.1.53 udp 0 0 194.242.128.16.1197 194.242.128.1.53 udp 0 0 194.242.128.16.4712 194.242.128.1.53 udp 0 0 194.242.128.16.3906 194.242.128.1.53 udp 0 0 194.242.128.16.3323 194.242.128.1.53 udp 0 0 194.242.128.16.2824 194.242.128.1.53 udp 0 0 194.242.128.16.4744 194.242.128.1.53 udp 0 0 194.242.128.16.3994 194.242.128.1.53 udp 0 0 194.242.128.16.2514 194.242.128.1.53 udp 0 0 194.242.128.16.2243 194.242.128.1.53 udp 0 0 194.242.128.16.3457 194.242.128.1.53 udp 0 0 194.242.128.16.1908 194.242.128.1.53 udp 0 0 194.242.128.16.1506 194.242.128.1.53 udp 0 0 194.242.128.16.4991 194.242.128.1.53 udp 0 0 194.242.128.16.4249 194.242.128.1.53 udp 0 0 194.242.128.16.1864 194.242.128.1.53 udp 0 0 194.242.128.16.1448 194.242.128.1.53 udp 0 0 194.242.128.16.3714 194.242.128.1.53 udp 0 0 194.242.128.16.3709 194.242.128.1.53 udp 0 0 194.242.128.16.3560 194.242.128.1.53 udp 0 0 194.242.128.16.3124 194.242.128.1.53 udp 0 0 194.242.128.16.2903 194.242.128.1.53 udp 0 0 194.242.128.16.1382 194.242.128.1.53 udp 0 0 194.242.128.16.1283 194.242.128.1.53 udp 0 0 194.242.128.16.4594 194.242.128.1.53 udp 0 0 194.242.128.16.2766 194.242.128.1.53 udp 0 0 194.242.128.16.1775 194.242.128.1.53 udp 0 0 194.242.128.16.4750 194.242.128.1.53 udp 0 0 194.242.128.16.4386 194.242.128.1.53 udp 0 0 194.242.128.16.2301 194.242.128.1.53 udp 0 0 194.242.128.16.1127 194.242.128.1.53 udp 0 0 194.242.128.16.2374 194.242.128.1.53 udp 0 0 194.242.128.16.1719 194.242.128.1.53 udp 0 0 194.242.128.16.3833 194.242.128.1.53 udp 0 0 194.242.128.16.3290 194.242.128.1.53 udp 0 0 194.242.128.16.2014 194.242.128.1.53 udp 0 0 194.242.128.16.1526 194.242.128.1.53 udp 0 0 194.242.128.16.3910 194.242.128.1.53 udp 0 0 194.242.128.16.1900 194.242.128.1.53 udp 0 0 194.242.128.16.1845 194.242.128.1.53 udp 0 0 194.242.128.16.4469 194.242.128.1.53 udp 0 0 194.242.128.16.3769 194.242.128.1.53 udp 0 0 194.242.128.16.3643 194.242.128.1.53 udp 0 0 194.242.128.16.3553 194.242.128.1.53 udp 0 0 194.242.128.16.2489 194.242.128.1.53 udp 0 0 194.242.128.16.4457 194.242.128.1.53 udp 0 0 194.242.128.16.2986 194.242.128.1.53 udp 0 0 194.242.128.16.2275 194.242.128.1.53 udp 0 0 194.242.128.16.2822 194.242.128.1.53 udp 0 0 194.242.128.16.1984 194.242.128.1.53 udp 0 0 194.242.128.16.1896 194.242.128.1.53 udp 0 0 194.242.128.16.3921 194.242.128.1.53 udp 0 0 194.242.128.16.2143 194.242.128.1.53 udp 0 0 194.242.128.16.1556 194.242.128.1.53 udp 0 0 194.242.128.16.1518 194.242.128.1.53 udp 0 0 194.242.128.16.4837 194.242.128.1.53 udp 0 0 194.242.128.16.3516 194.242.128.1.53 udp 0 0 194.242.128.16.4191 194.242.128.1.53 udp 0 0 194.242.128.16.2535 194.242.128.1.53 udp 0 0 194.242.128.16.1227 194.242.128.1.53 udp 0 0 194.242.128.16.4537 194.242.128.1.53 udp 0 0 194.242.128.16.3992 194.242.128.1.53 udp 0 0 194.242.128.16.3791 194.242.128.1.53 udp 0 0 194.242.128.16.3103 194.242.128.1.53 udp 0 0 194.242.128.16.2772 194.242.128.1.53 udp 0 0 194.242.128.16.1834 194.242.128.1.53 udp 0 0 194.242.128.16.1422 194.242.128.1.53 udp 0 0 194.242.128.16.3685 194.242.128.1.53 udp 0 0 194.242.128.16.3490 194.242.128.1.53 udp 0 0 194.242.128.16.3489 194.242.128.1.53 udp 0 0 194.242.128.16.2917 194.242.128.1.53 udp 0 0 194.242.128.16.2827 194.242.128.1.53 udp 0 0 194.242.128.16.2814 194.242.128.1.53 udp 0 0 194.242.128.16.1416 194.242.128.1.53 udp 0 0 194.242.128.16.1710 194.242.128.1.53 udp 0 0 194.242.128.16.1236 194.242.128.1.53 udp 0 0 194.242.128.16.1184 194.242.128.1.53 udp 0 0 194.242.128.16.4276 194.242.128.1.53 udp 0 0 194.242.128.16.3913 194.242.128.1.53 udp 0 0 194.242.128.16.3902 194.242.128.1.53 udp 0 0 194.242.128.16.3453 194.242.128.1.53 udp 0 0 194.242.128.16.2852 194.242.128.1.53 udp 0 0 194.242.128.16.2838 194.242.128.1.53 udp 0 0 194.242.128.16.2519 194.242.128.1.53 udp 0 0 194.242.128.16.2486 194.242.128.1.53 udp 0 0 194.242.128.16.1594 194.242.128.1.53 udp 0 0 194.242.128.16.1558 194.242.128.1.53 udp 0 0 194.242.128.16.1515 194.242.128.1.53 udp 0 0 194.242.128.16.1441 194.242.128.1.53 udp 0 0 194.242.128.16.1052 194.242.128.1.53 udp 0 0 194.242.128.16.4896 194.242.128.1.53 udp 0 0 194.242.128.16.4774 194.242.128.1.53 udp 0 0 194.242.128.16.4412 194.242.128.1.53 udp 0 0 194.242.128.16.4359 194.242.128.1.53 udp 0 0 194.242.128.16.3670 194.242.128.1.53 udp 0 0 194.242.128.16.1934 194.242.128.1.53 udp 0 0 194.242.128.16.1286 194.242.128.1.53 udp 0 0 194.242.128.16.1213 194.242.128.1.53 udp 0 0 194.242.128.16.2346 194.242.128.1.53 udp 0 0 194.242.128.16.2170 194.242.128.1.53 udp 0 0 194.242.128.16.2078 194.242.128.1.53 udp 0 0 194.242.128.16.1846 194.242.128.1.53 udp 0 0 194.242.128.16.1732 194.242.128.1.53 udp 0 0 194.242.128.16.1730 194.242.128.1.53 udp 0 0 194.242.128.16.1684 194.242.128.1.53 udp 0 0 194.242.128.16.1654 194.242.128.1.53 udp 0 0 194.242.128.16.1544 194.242.128.1.53 udp 0 0 194.242.128.16.1147 194.242.128.1.53 udp 0 0 194.242.128.16.4562 194.242.128.1.53 udp 0 0 194.242.128.16.3484 194.242.128.1.53 udp 0 0 194.242.128.2.53 *.* udp 0 0 194.242.128.16.123 *.* -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-isp Fri Jun 20 04:44:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA28232 for isp-outgoing; Fri, 20 Jun 1997 04:44:57 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA28227 for ; Fri, 20 Jun 1997 04:44:51 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id MAA01465; Fri, 20 Jun 1997 12:44:31 +0100 (BST) Date: Fri, 20 Jun 1997 12:44:31 +0100 (BST) From: Stephen Roome To: "Gary D. Margiotta" cc: freebsd-isp@FreeBSD.ORG Subject: Re: gigabyte motherboards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Gary D. Margiotta wrote: > Just a quick (hopefully) question regarding gigabyte motherboards... > > We are currently running a Gigabyte GA-586HX board, and plan on getting > another, but I wanted to know if anybody knew whether the GA-586-S board > with the SIS chipset rather than the Intel was any better or worse. > Personally, I think worse because it is cheaper, but you never know. TIA! I've got two GA-586DX boards here, which are the dual processor (hence Intel based) ones which work nicely. However don't put SIS out of the market, IMHO, the SIS chipsets are cheaper because of market forces not their capability. I still run an old SIS based Pentium mainboard at home and from experience SIS chipsets tend to do exactly the same job with similar performance as Intel equipment, but for less money. Beware of what happened with SIS based graphics cards though, which had no support from XFree86 or anyone else for ages. Anyway, you'd need some real benchmarks to make a good evaluation, but I wouldn't put them down just because they are cheaper/not Intel. -- Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-isp Fri Jun 20 05:05:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA28744 for isp-outgoing; Fri, 20 Jun 1997 05:05:12 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA28739; Fri, 20 Jun 1997 05:05:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id FAA12992; Fri, 20 Jun 1997 05:07:02 -0700 (PDT) Message-Id: <199706201207.FAA12992@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Josef Karthauser cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-reply-to: Your message of "Fri, 20 Jun 1997 10:48:29 BST." <19970620104829.34842@pavilion.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Jun 1997 05:07:02 -0700 Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Any suggestions, other than a full frontal labotamy, would gratefully >be received. What do you have NMBCLUSTERS set to? A busy WWW server needs a fairly high value for that - many times the default. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Fri Jun 20 07:30:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA05449 for isp-outgoing; Fri, 20 Jun 1997 07:30:40 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA05444; Fri, 20 Jun 1997 07:30:37 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id IAA02329; Fri, 20 Jun 1997 08:30:25 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id IAA17616; Fri, 20 Jun 1997 08:31:10 -0600 (MDT) Date: Fri, 20 Jun 1997 08:31:10 -0600 (MDT) From: Marc Slemko To: Josef Karthauser cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: Apache 1.1.3 and 1.2.0 problems under FBSD2.2.2 In-Reply-To: <19970620104829.34842@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Please, limit your crossposting. _ONE_ mailing list is appropriate. If something is appropriate to another list, it is almost never appropriate to questions. Also it is appreciated if you don't ask a question publicly and submit it as an Apache bug at the same time. Ask it publicly first and wait to get answers. It avoids wasting limited developer time. On Fri, 20 Jun 1997, Josef Karthauser wrote: > The continuing saga of a sick web machine :( > > A brief history. We're running a P200pro FBSD2.2.2 machine here as > a virtual web server. It currently has 130ish web servers running, > each with their own IP address. > > Where did the problem start? I'm not sure, but it was some combination > of reaching 124ish web servers, and hitting a certain number of active > http connections. > > The web server is basically fine, until some limit gets reached and the > server then just hangs, with lots of sockets still active. You are running out of file descriptors. Just because you change the ulimit does _NOT_ mean you can actually use all of them. You are probably running into the FD_SETSIZE limit, which limits (among other things) the number of fds that select() can handle. It is still 255. Under 2.2, I think you should be able to just redefine FD_SETSIZE before compiling Apache to increase that. The reason that 1.1 works and 1.2 doesn't is probably because file descriptors are allocated in a different order in 1.2 for various reasons. You don't make it entirely clear, but I am assuming that just Apache is hanging, not the whole machine. -- Marc Slemko | Apache team member marcs@znep.com | marc@apache.org From owner-freebsd-isp Fri Jun 20 09:03:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09130 for isp-outgoing; Fri, 20 Jun 1997 09:03:28 -0700 (PDT) Received: from msn2.globaldialog.com (root@ns1.globaldialog.com [156.46.122.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09122 for ; Fri, 20 Jun 1997 09:03:22 -0700 (PDT) Received: from br02 ([156.46.248.99]) by msn2.globaldialog.com (8.8.5/8.6.12) with SMTP id LAA09516 for ; Fri, 20 Jun 1997 11:03:20 -0500 (CDT) Date: Fri, 20 Jun 1997 11:03:20 -0500 (CDT) Message-Id: <199706201603.LAA09516@msn2.globaldialog.com> X-Sender: jwenger@globaldialog.com X-EUDORA-DEMO: NOT FOR RESALE - 90 DAY DEMONSTRATION COPY X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: FreeBSD ISP list From: Jack Wenger Subject: Q-MAIL Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm considering moving to Q-Mail. Is anyone using Q-Mail instead of Sendmail? If so, how come? Are there any major advantages? What popper are you using? TIA! Jack ~~~~~~~~~~~~~~~~~~~~~'-**-'~~~~~~~~~~~~~~~~~~~~~~~ Jack Wenger, Owner Bent Reality Graphics info@bentreality.com http://www.bentreality.com 1-888-701-1026 608-233-8571 ~~~~~~~~~~~~~~~~~~~~~'-**-'~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-isp Fri Jun 20 10:13:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13262 for isp-outgoing; Fri, 20 Jun 1997 10:13:56 -0700 (PDT) Received: from mail.intercenter.net (mir.intercenter.net [207.211.128.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA13257 for ; Fri, 20 Jun 1997 10:13:53 -0700 (PDT) Received: (qmail 25172 invoked from network); 20 Jun 1997 17:13:52 -0000 Received: from bigboy.intercenter.net (207.211.128.17) by mir.intercenter.net with SMTP; 20 Jun 1997 17:13:52 -0000 Date: Fri, 20 Jun 1997 13:13:52 -0400 (EDT) From: Ron Bickers To: Jack Wenger cc: FreeBSD ISP list Subject: Re: Q-MAIL In-Reply-To: <199706201603.LAA09516@msn2.globaldialog.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Jun 1997, Jack Wenger wrote: > I'm considering moving to Q-Mail. > Is anyone using Q-Mail instead of Sendmail? > If so, how come? > Are there any major advantages? > What popper are you using? We've been running qmail for many months now with zero problems. I got sick and tired of watching for the latest and greatest security notice on sendmail. Qmail is a very different beast so be prepared to unlearn most everything you know about sendmail. Read all of the FAQ! Qmail was designed from the ground up to be secure, NOT to be a sendmail look-a-like. It took some time unlearning sendmail, but it didn't take long to love it. We're running many virtual domains with great flexibility and ease. By default it delivers to the users home dir in mbox format so a slightly modified qpopper will do for the popper. The mods are in the FAQ that comes with the source. BTW, there have been at least half a dozen security problems found with sendmail since I've started using qmail. Needless to say, I rest much easier at night. :-) --- Ron From owner-freebsd-isp Fri Jun 20 11:30:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA16748 for isp-outgoing; Fri, 20 Jun 1997 11:30:05 -0700 (PDT) Received: from surf.pangea.ca (root@surf.pangea.ca [204.112.101.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA16742 for ; Fri, 20 Jun 1997 11:30:03 -0700 (PDT) Received: from surf.pangea.ca (tyrelb@surf.pangea.ca [204.112.101.109]) by surf.pangea.ca (8.8.6/8.8.5) with SMTP id NAA26204 for ; Fri, 20 Jun 1997 13:29:25 -0500 (CDT) Date: Fri, 20 Jun 1997 13:29:21 -0500 (CDT) From: Tyrel Burton To: freebsd-isp@freebsd.org In-Reply-To: <199706201603.LAA09516@msn2.globaldialog.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk does anyone know how to get off of this list? What address to I unsubscribe to? Thanks. ----- Tyrel Burton tyrelb@pangea.ca "Teachers open the door, but you must enter by yourself." -- Chinese Proverb From owner-freebsd-isp Fri Jun 20 13:12:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA22119 for isp-outgoing; Fri, 20 Jun 1997 13:12:55 -0700 (PDT) Received: from lightning.tbe.net (qmailr@lightning.tbe.net [208.208.122.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA22107 for ; Fri, 20 Jun 1997 13:12:50 -0700 (PDT) Received: (qmail 10186 invoked by uid 1010); 20 Jun 1997 20:07:55 -0000 Date: Fri, 20 Jun 1997 16:07:54 -0400 (EDT) From: "Gary D. Margiotta" To: Ron Bickers cc: Jack Wenger , FreeBSD ISP list Subject: Re: Q-MAIL In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We also run Q-Mail rather than sendmail, and will (hopefully) never go back. Q-Mail is a huge improvement in many ways over sendmail. For starters, it is much smaller and more streamlined. Second, the guy who wrote it was a security freak, and didn't release it until he couldn't hack into his own creation (or so the story goes, I really don't know how true that is). Q-Mail runs only a couple processes, and they are idle until they are needed, PLUS there are only a couple of processes who run as root, not the entire program like sendmail. The most important thing about it security wise is that it isn't well known yet, so it hasn't gotten the attention of to many hackers. It took a short while to get used to when we first did it because when we installed it it was still using /Maildir rather tham mbox format so we had to kludge things a bit. Also you have to modify the pop3 side of it a bit, but we are now working on fixing popper to work with it. We started with version .95, but now it is at 1.01, and has been great. Virtual domains are a joke to route mail for, and best of all, it is very non-CPU intensive, so you can run a full fledged mail server on a very minimal machine. IMHO, go with Q-Mail....we have been for about a year now, and couldn't be happier. -Gary Margiotta TBE Internet Services http://www.tbe.net From owner-freebsd-isp Fri Jun 20 16:35:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA02138 for isp-outgoing; Fri, 20 Jun 1997 16:35:02 -0700 (PDT) Received: from linus.intrastar.net (jsuter@linus.intrastar.net [206.136.25.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA02125 for ; Fri, 20 Jun 1997 16:34:58 -0700 (PDT) Received: from localhost (jsuter@localhost) by linus.intrastar.net (8.8.5/TerraNovaNet) with SMTP id SAA13299; Fri, 20 Jun 1997 18:34:57 -0500 (CDT) Date: Fri, 20 Jun 1997 18:34:57 -0500 (CDT) From: Jacob Suter To: Stephen Roome cc: "Gary D. Margiotta" , freebsd-isp@FreeBSD.ORG Subject: Re: gigabyte motherboards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've had great experience with the Gigabyte SiS Socket 7 (I refuse to call it a 'pentium' board) motherboard.... I've used a k5/166, 6x86/P150+, and mostly an Intel Pentium 100 (because well, all the GOOD chips get put to 'more important' uses... bleh!)... I've never had any incompatability with any FreeBSD (2.1.7, several 2.2-gamma's, and 2.2.1r) releases that I have ran on it... Its also a spectacular Win95 (bleh!) board. I have heard some horror stories about the 'mboard' SiS chipset socket 7 board, but from what I hear mboard doesn't have the best reputation all the way around. JS On Fri, 20 Jun 1997, Stephen Roome wrote: > On Thu, 19 Jun 1997, Gary D. Margiotta wrote: > > Just a quick (hopefully) question regarding gigabyte motherboards... > > > > We are currently running a Gigabyte GA-586HX board, and plan on getting > > another, but I wanted to know if anybody knew whether the GA-586-S board > > with the SIS chipset rather than the Intel was any better or worse. > > Personally, I think worse because it is cheaper, but you never know. TIA! > > I've got two GA-586DX boards here, which are the dual processor (hence > Intel based) ones which work nicely. However don't put SIS out of the > market, IMHO, the SIS chipsets are cheaper because of market forces not > their capability. > > I still run an old SIS based Pentium mainboard at home and from experience > SIS chipsets tend to do exactly the same job with similar performance as > Intel equipment, but for less money. > > Beware of what happened with SIS based graphics cards though, which had no > support from XFree86 or anyone else for ages. Anyway, you'd need some real > benchmarks to make a good evaluation, but I wouldn't put them down just > because they are cheaper/not Intel. > > -- > Steve Roome - Vision Interactive Ltd. > Tel:+44(0)117 9730597 Home:+44(0)976 241342 > WWW: http://dylan.visint.co.uk/ > > From owner-freebsd-isp Fri Jun 20 19:07:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA08500 for isp-outgoing; Fri, 20 Jun 1997 19:07:56 -0700 (PDT) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA08489 for ; Fri, 20 Jun 1997 19:07:51 -0700 (PDT) Received: from P1mpBSD (P1mpBSD.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.5/TerraNovaNet) with SMTP id WAA20964; Fri, 20 Jun 1997 22:08:11 -0400 (EDT) Message-ID: <33AB37D1.515A@TerraNova.net> Date: Fri, 20 Jun 1997 22:09:21 -0400 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 To: Jacob Suter CC: freebsd-isp@FreeBSD.ORG Subject: Re: gigabyte motherboards References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jacob Suter wrote: > > I've had great experience with the Gigabyte SiS Socket 7 (I refuse to call > it a 'pentium' board) motherboard.... I've used a k5/166, 6x86/P150+, and > mostly an Intel Pentium 100 (because well, all the GOOD chips get put to > 'more important' uses... bleh!)... I've never had any incompatability > with any FreeBSD (2.1.7, several 2.2-gamma's, and 2.2.1r) releases that I > have ran on it... Its also a spectacular Win95 (bleh!) board. I have > heard some horror stories about the 'mboard' SiS chipset socket 7 board, > but from what I hear mboard doesn't have the best reputation all the way > around. That's mtech, Jake. -T -- -=--==--===---====----======------=======------- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.TerraNova.net -------=======------======----====---===--==--=- Always remember that you are unique. Just like everyone else. From owner-freebsd-isp Fri Jun 20 19:24:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA08928 for isp-outgoing; Fri, 20 Jun 1997 19:24:57 -0700 (PDT) Received: from pooky.myhouse.com ([204.156.22.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA08923 for ; Fri, 20 Jun 1997 19:24:55 -0700 (PDT) Received: from localhost (zoonie@localhost) by pooky.myhouse.com (8.8.5/8.7.3) with SMTP id WAA07800 for ; Fri, 20 Jun 1997 22:25:19 -0400 (EDT) Date: Fri, 20 Jun 1997 22:25:19 -0400 (EDT) From: zoonie To: freebsd-isp@freebsd.org Subject: carrier loss with cyclades? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i have a cyclades cyclom 8yo card installed on a 2.1.7 system and i seem to be having a problem with line drops. at random times whether there is activity on the lines or not the lines just drop and pppd logs the following message: Jun 18 18:51:35 mail /kernel: ppp2: no carrier i know that i can set the modem to wait longer on loss of carrier in case it is line noise and i'm going to try that but one of these modems was attached to a plain old serial port before i got the cyclades card and this never happened when it was on the serial port. so i really don't think that setting the modem to wait longer for carrier is going to do anything. does anybody have any ideas? thanks.... From owner-freebsd-isp Sat Jun 21 00:39:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17815 for isp-outgoing; Sat, 21 Jun 1997 00:39:00 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17807 for ; Sat, 21 Jun 1997 00:38:56 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id CAA23546; Sat, 21 Jun 1997 02:39:28 -0500 (CDT) Date: Sat, 21 Jun 1997 02:39:28 -0500 (CDT) From: "Tom T. Thai" To: zoonie cc: freebsd-isp@FreeBSD.ORG Subject: Re: carrier loss with cyclades? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk check your modem init string and also check what the other modem is using at the other end. On Fri, 20 Jun 1997, zoonie wrote: > i have a cyclades cyclom 8yo card installed on a 2.1.7 system and i seem > to be having a problem with line drops. at random times whether there is > activity on the lines or not the lines just drop and pppd logs the > following message: > > Jun 18 18:51:35 mail /kernel: ppp2: no carrier > > i know that i can set the modem to wait longer on loss of carrier in case > it is line noise and i'm going to try that but one of these modems was > attached to a plain old serial port before i got the cyclades card and > this never happened when it was on the serial port. so i really don't > think that setting the modem to wait longer for carrier is going to do > anything. does anybody have any ideas? thanks.... > > > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Sat Jun 21 03:35:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA22702 for isp-outgoing; Sat, 21 Jun 1997 03:35:20 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22693 for ; Sat, 21 Jun 1997 03:35:13 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id FAA24421 for ; Sat, 21 Jun 1997 05:35:47 -0500 (CDT) Date: Sat, 21 Jun 1997 05:35:47 -0500 (CDT) From: "Tom T. Thai" To: freebsd-isp@FreeBSD.ORG Subject: ISDN Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a few questions regading ISDN: 1. If I had a BRI line and a TA attached to it, the TA can only handle one B channel at a time right? If yes, then would I be wasting the 2nd B channel if one of my users use only one B channel at a time? 2. If I had the same setup as #1, and a user want to do 128K (both B channels), do I have to setup anything special on the RAS? Or can I setup to handle the dynamic link automatically via the TA? 3. What is a good TA if I want to do 128K on the server side to a smart multiserial RAS? .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Sat Jun 21 04:15:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA25414 for isp-outgoing; Sat, 21 Jun 1997 04:15:23 -0700 (PDT) Received: from relay.amis.net (root@server.amis.net [193.77.234.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25409 for ; Sat, 21 Jun 1997 04:15:14 -0700 (PDT) Received: (from uucp@localhost) by relay.amis.net (8.8.6/8.8.6/970616) with UUCP id NAA16011; Sat, 21 Jun 1997 13:15:04 +0200 (CEST) Received: (from blaz@localhost) by gold.amis.net (8.8.5/8.8.5) id NAA00333; Sat, 21 Jun 1997 13:14:01 +0200 (CEST) From: Blaz Zupan Message-Id: <199706211114.NAA00333@gold.amis.net> Subject: Re: ISDN In-Reply-To: from "Tom T. Thai" at "Jun 21, 97 05:35:47 am" To: tomthai@future.net (Tom T. Thai) Date: Sat, 21 Jun 1997 13:14:00 +0200 (CEST) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1. If I had a BRI line and a TA attached to it, the TA can only handle > one B channel at a time right? If yes, then would I be wasting the 2nd B > channel if one of my users use only one B channel at a time? It depends on the TA. For example the Zyxel Omni TA128 has two serial ports, you connect each one to a serial port on your terminal server and use both channels at 64K (that's what I do, I have an Omni connected to a Cisco 2511, but am currently replacing this setup with a Livingston Portmaster 3). > 2. If I had the same setup as #1, and a user want to do 128K (both B > channels), do I have to setup anything special on the RAS? Or can I > setup to handle the dynamic link automatically via the TA? The Omni (and I guess other TA's as well) can handle this automagically so it looks to your terminal server just like a fast (128K) modem. > 3. What is a good TA if I want to do 128K on the server side to a smart > multiserial RAS? Zyel Omni TA128 (am I repeating myself?). But make sure to download firmware version 2.04 from ftp.zyxel.com, otherwise it will probably fail every day and you will have to turn it off :( -- Blaz Zupan, blaz@amis.net, http://www.amis.net/staff/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia From owner-freebsd-isp Sat Jun 21 05:20:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27041 for isp-outgoing; Sat, 21 Jun 1997 05:20:05 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27035 for ; Sat, 21 Jun 1997 05:20:03 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA10323; Sat, 21 Jun 1997 05:19:59 -0700 (PDT) To: "Tom T. Thai" cc: freebsd-isp@FreeBSD.ORG Subject: Re: ISDN In-reply-to: Your message of "Sat, 21 Jun 1997 05:35:47 CDT." Date: Sat, 21 Jun 1997 05:19:58 -0700 Message-ID: <10309.866895598@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1. If I had a BRI line and a TA attached to it, the TA can only handle > one B channel at a time right? If yes, then would I be wasting the 2nd B Wrong. You can bond two B channels just fine with a TA. I do it all the time. > 2. If I had the same setup as #1, and a user want to do 128K (both B > channels), do I have to setup anything special on the RAS? Or can I You can't do 128K, but you can do 115.2K. > 3. What is a good TA if I want to do 128K on the server side to a smart > multiserial RAS? Hard to say - depends on the RAS. Most modern TAs will do multilink PPP, but you'd need to make sure it's interoperable with the RAS. I just use a TA on each end for my link and let them speak their own bonding protocol ("bonding mode 1" for the ADTRAN L1) so it works seamlessly. Jordan From owner-freebsd-isp Sat Jun 21 05:50:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27920 for isp-outgoing; Sat, 21 Jun 1997 05:50:20 -0700 (PDT) Received: from pooky.myhouse.com ([204.156.22.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27915 for ; Sat, 21 Jun 1997 05:50:18 -0700 (PDT) Received: from localhost (zoonie@localhost) by pooky.myhouse.com (8.8.5/8.7.3) with SMTP id IAA12685; Sat, 21 Jun 1997 08:49:43 -0400 (EDT) Date: Sat, 21 Jun 1997 08:49:43 -0400 (EDT) From: zoonie To: "Tom T. Thai" cc: freebsd-isp@FreeBSD.ORG Subject: Re: carrier loss with cyclades? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i hate to tell you this but it can't be the modem init string because the only thing that has changed is the port the modem is attached to. plain serial port no problem, when the cyclades port is used then there is a problem. it is possible that the phone company screwed something up but i don't think that's it either. thanks.. On Sat, 21 Jun 1997, Tom T. Thai wrote: > check your modem init string and also check what the other modem is using > at the other end. > > On Fri, 20 Jun 1997, zoonie wrote: > > > i have a cyclades cyclom 8yo card installed on a 2.1.7 system and i seem > > to be having a problem with line drops. at random times whether there is > > activity on the lines or not the lines just drop and pppd logs the > > following message: > > > > Jun 18 18:51:35 mail /kernel: ppp2: no carrier > > > > i know that i can set the modem to wait longer on loss of carrier in case > > it is line noise and i'm going to try that but one of these modems was > > attached to a plain old serial port before i got the cyclades card and > > this never happened when it was on the serial port. so i really don't > > think that setting the modem to wait longer for carrier is going to do > > anything. does anybody have any ideas? thanks.... From owner-freebsd-isp Sat Jun 21 07:21:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA00453 for isp-outgoing; Sat, 21 Jun 1997 07:21:40 -0700 (PDT) Received: from lightning.tbe.net (qmailr@lightning.tbe.net [208.208.122.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA00448 for ; Sat, 21 Jun 1997 07:21:37 -0700 (PDT) Received: (qmail 21306 invoked by uid 1010); 21 Jun 1997 14:17:05 -0000 Date: Sat, 21 Jun 1997 10:17:05 -0400 (EDT) From: "Gary D. Margiotta" To: Blaz Zupan cc: "Tom T. Thai" , freebsd-isp@FreeBSD.ORG Subject: Re: ISDN In-Reply-To: <199706211114.NAA00333@gold.amis.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It depends on the TA. For example the Zyxel Omni TA128 has two serial > ports, you connect each one to a serial port on your terminal server > and use both channels at 64K (that's what I do, I have an Omni connected > to a Cisco 2511, but am currently replacing this setup with a Livingston > Portmaster 3). A good number of TA's will have dual ports on them to allow you to use two 64k channels in one unit, and also to allow bonding of the two channels to acheive the 128k speed. I'm not sure if you know this or not, but the PM3's are still using 33.6 cards due to the fact that Lucent/Rockwell still have not come out with good 56k code for their k56Flex modems. The Livingston people don't have a clue as to when they will get it, and all the customers who bought PM3's with the thought that they would have the 56k by now are in an uproar and very dissatisfied...I am on the mailing list for them too. I was going to go the PM3 route myself, but since all that is going on, I am going to USR x2 first because they at least have something that works. The USR Total control unit, however doesn't support ISDN though (AFAIK), so you would have to get an I-Modem rack, which from what I've heard aren't bad either. Just my $.02 -Gary Margiotta TBE Internet Services http://www.tbe.net From owner-freebsd-isp Sat Jun 21 07:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA01707 for isp-outgoing; Sat, 21 Jun 1997 07:51:04 -0700 (PDT) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA01702 for ; Sat, 21 Jun 1997 07:51:02 -0700 (PDT) Received: from localhost (dev@localhost) by wopr.inetu.net (8.8.5/8.8.5) with SMTP id KAA14406 for ; Sat, 21 Jun 1997 10:55:34 -0400 (EDT) Date: Sat, 21 Jun 1997 10:55:34 -0400 (EDT) From: Dev Chanchani To: freebsd-isp@freebsd.org Subject: Harware Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a Freebsd 2.2.1 server which keeps reporting corupted files during install (bad crc, etc). I have formatted the drive under dos and bios ensuring there are _no_ bad sectors. I have a QTI Motherboard with a Intel PCI X3 EIDE Controller and Maxtor 3.5 GB 83500A Drive Can anyone tell me if there are any hardware compadibility issues.. Dev From owner-freebsd-isp Sat Jun 21 10:16:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10132 for isp-outgoing; Sat, 21 Jun 1997 10:16:29 -0700 (PDT) Received: from relay.amis.net (root@server.amis.net [193.77.234.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10127 for ; Sat, 21 Jun 1997 10:16:26 -0700 (PDT) Received: (from uucp@localhost) by relay.amis.net (8.8.6/8.8.6/970616) with UUCP id TAA19589; Sat, 21 Jun 1997 19:16:20 +0200 (CEST) Received: (from blaz@localhost) by gold.amis.net (8.8.5/8.8.5) id TAA00255; Sat, 21 Jun 1997 19:16:28 +0200 (CEST) From: Blaz Zupan Message-Id: <199706211716.TAA00255@gold.amis.net> Subject: Re: ISDN In-Reply-To: from "Gary D. Margiotta" at "Jun 21, 97 10:17:05 am" To: gary@tbe.net (Gary D. Margiotta) Date: Sat, 21 Jun 1997 19:16:22 +0200 (CEST) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > A good number of TA's will have dual ports on them to allow you to use two > 64k channels in one unit, and also to allow bonding of the two channels to > acheive the 128k speed. Until now I did not find any other TA but the Omni 128. Which other TA's have two serial ports? > I'm not sure if you know this or not, but the PM3's are still using 33.6 > cards due to the fact that Lucent/Rockwell still have not come out with > good 56k code for their k56Flex modems. The Livingston people don't have Yeah, I just registered for the 56K modem cards on www.livingston.com. I'm not so eagerly waiting for those anyway, because most customers over here use USR modems that do X2 instead of K56flex and I do not intend to support them anyway (get ISDN if you want higher speed). > go the PM3 route myself, but since all that is going on, I am going to USR > x2 first because they at least have something that works. The USR Total Won't this be an expensive route? First buying the USR units, then switching to PM3? I think that 56K is just an intermediate step and it will die sooner or later. -- Blaz Zupan, blaz@amis.net, http://www.amis.net/staff/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia From owner-freebsd-isp Sat Jun 21 11:58:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13929 for isp-outgoing; Sat, 21 Jun 1997 11:58:33 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13924 for ; Sat, 21 Jun 1997 11:58:31 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id NAA28616; Sat, 21 Jun 1997 13:59:04 -0500 (CDT) Date: Sat, 21 Jun 1997 13:59:02 -0500 (CDT) From: "Tom T. Thai" To: "Jordan K. Hubbard" cc: freebsd-isp@FreeBSD.ORG Subject: Re: ISDN In-Reply-To: <10309.866895598@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Jun 1997, Jordan K. Hubbard wrote: > > 1. If I had a BRI line and a TA attached to it, the TA can only handle > > one B channel at a time right? If yes, then would I be wasting the 2nd B > > Wrong. You can bond two B channels just fine with a TA. I do it > all the time. what I meant to the above was one user per b channel. > > > 2. If I had the same setup as #1, and a user want to do 128K (both B > > channels), do I have to setup anything special on the RAS? Or can I > > You can't do 128K, but you can do 115.2K. > > > 3. What is a good TA if I want to do 128K on the server side to a smart > > multiserial RAS? > > Hard to say - depends on the RAS. Most modern TAs will do multilink > PPP, but you'd need to make sure it's interoperable with the RAS. I > just use a TA on each end for my link and let them speak their own > bonding protocol ("bonding mode 1" for the ADTRAN L1) so it works > seamlessly. > > Jordan > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Sat Jun 21 12:00:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13996 for isp-outgoing; Sat, 21 Jun 1997 12:00:01 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13952 for ; Sat, 21 Jun 1997 11:59:58 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id OAA28638; Sat, 21 Jun 1997 14:00:35 -0500 (CDT) Date: Sat, 21 Jun 1997 14:00:35 -0500 (CDT) From: "Tom T. Thai" To: zoonie cc: freebsd-isp@FreeBSD.ORG Subject: Re: carrier loss with cyclades? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Jun 1997, zoonie wrote: > i hate to tell you this but it can't be the modem init string because > the only thing that has changed is the port the modem is attached to. > plain serial port no problem, when the cyclades port is used then there is > a problem. it is possible that the phone company screwed something up but > i don't think that's it either. thanks.. then maybe it's the cylclade or the setup of pppd? > > On Sat, 21 Jun 1997, Tom T. Thai wrote: > > > check your modem init string and also check what the other modem is using > > at the other end. > > > > On Fri, 20 Jun 1997, zoonie wrote: > > > > > i have a cyclades cyclom 8yo card installed on a 2.1.7 system and i seem > > > to be having a problem with line drops. at random times whether there is > > > activity on the lines or not the lines just drop and pppd logs the > > > following message: > > > > > > Jun 18 18:51:35 mail /kernel: ppp2: no carrier > > > > > > i know that i can set the modem to wait longer on loss of carrier in case > > > it is line noise and i'm going to try that but one of these modems was > > > attached to a plain old serial port before i got the cyclades card and > > > this never happened when it was on the serial port. so i really don't > > > think that setting the modem to wait longer for carrier is going to do > > > anything. does anybody have any ideas? thanks.... > > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Sat Jun 21 12:02:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14149 for isp-outgoing; Sat, 21 Jun 1997 12:02:30 -0700 (PDT) Received: from lightning.tbe.net (qmailr@lightning.tbe.net [208.208.122.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA14144 for ; Sat, 21 Jun 1997 12:02:24 -0700 (PDT) Received: (qmail 23377 invoked by uid 1010); 21 Jun 1997 18:57:45 -0000 Date: Sat, 21 Jun 1997 14:57:45 -0400 (EDT) From: "Gary D. Margiotta" To: Blaz Zupan cc: freebsd-isp@FreeBSD.ORG Subject: Re: ISDN In-Reply-To: <199706211716.TAA00255@gold.amis.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Until now I did not find any other TA but the Omni 128. Which other TA's > have two serial ports? Well, the USR courier I-Modem does, and I believe there is one from Cardinal that does also, though I am not sure of the model #. > Yeah, I just registered for the 56K modem cards on www.livingston.com. > I'm not so eagerly waiting for those anyway, because most customers over > here use USR modems that do X2 instead of K56flex and I do not intend to > support them anyway (get ISDN if you want higher speed). True, but in my situation, I am getting a PRI, which from my understanding doesn't interface well with ISDN, and vice versa, though unfortunately I didn't have much time to do the reasearch, the quality of our phone lines is forcing my hands into going digital before we really wanted to. > Won't this be an expensive route? First buying the USR units, then switching > to PM3? I think that 56K is just an intermediate step and it will die sooner > or later. Actually we were and still are planning on supporting both standards until they come up with one mix, and that in the end would also allow us for more phone lines and modems in the end. I agree with you on that. -Gary Margiotta TBE Internet Services http://www.tbe.net From owner-freebsd-isp Sat Jun 21 12:15:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14794 for isp-outgoing; Sat, 21 Jun 1997 12:15:51 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14789 for ; Sat, 21 Jun 1997 12:15:46 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id PAA14068; Sat, 21 Jun 1997 15:19:05 -0400 (EDT) Date: Sat, 21 Jun 1997 15:19:05 -0400 (EDT) From: "John T. Farmer" Message-Id: <199706211919.PAA14068@sabre.goldsword.com> To: blaz@gold.amis.net, gary@tbe.net Subject: Re: ISDN Cc: freebsd-isp@FreeBSD.ORG, jfarmer@goldsword.com, tomthai@future.net Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Jun 1997 10:17:05 -0400 (EDT) "Gary D. Margiotta" said: >A good number of TA's will have dual ports on them to allow you to use two >64k channels in one unit, and also to allow bonding of the two channels to >acheive the 128k speed. > >I'm not sure if you know this or not, but the PM3's are still using 33.6 >cards due to the fact that Lucent/Rockwell still have not come out with >good 56k code for their k56Flex modems. The Livingston people don't have >a clue as to when they will get it, and all the customers who bought PM3's >with the thought that they would have the 56k by now are in an uproar and >very dissatisfied...I am on the mailing list for them too. I was going to >go the PM3 route myself, but since all that is going on, I am going to USR >x2 first because they at least have something that works. The USR Total >control unit, however doesn't support ISDN though (AFAIK), so you would >have to get an I-Modem rack, which from what I've heard aren't bad either. > Yeah, we're looking at doing the same type of thing. I looked into getting an Ascend box, but the cheapest path I could inch into it was with the Max 1800 (to support both ISDN and k56flex), and at +$8k won't fit in our current capital budget (very tight :^<). In our case, any route we take will be a pain since all our analog lines are just that, individual pots circuits (best route performance/cost when we put them in...). The headache & cost of installing PRI's just ain't goin' to happen soon. But since we found out that some/all of our analog lines are off a SLIC-96 rack & it's speed limiting our users connections, So we're installing BRI's in hunt groups & hanging USR I-couriers on our server ports. They'll handle 64/128k ISDN, x2, and 33.6. Granted, there'll be times where 1 BRI will be tied up handling 1 64k ISDN or 1 x2 call, but it beats nothing. Besides, we're "weaving" some 33.6 analogs to the POTS port on the I-couriers. We'll tie them at the end of our current analog group for overflow. Not the cleanest, most elegant solution, but it'll work now & buy us some time until the x2 / k56flex wars settle out... John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-isp Sat Jun 21 12:31:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15357 for isp-outgoing; Sat, 21 Jun 1997 12:31:59 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15351 for ; Sat, 21 Jun 1997 12:31:56 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.5-r-beta/8.6.10) with SMTP id OAA28956; Sat, 21 Jun 1997 14:32:30 -0500 (CDT) Date: Sat, 21 Jun 1997 14:32:29 -0500 (CDT) From: "Tom T. Thai" To: "Gary D. Margiotta" cc: Blaz Zupan , freebsd-isp@FreeBSD.ORG Subject: Re: ISDN In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Jun 1997, Gary D. Margiotta wrote: > > Until now I did not find any other TA but the Omni 128. Which other TA's > > have two serial ports? I've read and re-read all the specs on the i-modem and didn't find any mention of TWO SERIAL ports to handle two different users simultaneously on both B channels. > > Well, the USR courier I-Modem does, and I believe there is one from > Cardinal that does also, though I am not sure of the model #. > > > Yeah, I just registered for the 56K modem cards on www.livingston.com. > > I'm not so eagerly waiting for those anyway, because most customers over > > here use USR modems that do X2 instead of K56flex and I do not intend to > > support them anyway (get ISDN if you want higher speed). > > True, but in my situation, I am getting a PRI, which from my understanding > doesn't interface well with ISDN, and vice versa, though unfortunately I > didn't have much time to do the reasearch, the quality of our phone lines > is forcing my hands into going digital before we really wanted to. > > > Won't this be an expensive route? First buying the USR units, then switching > > to PM3? I think that 56K is just an intermediate step and it will die sooner > > or later. > > Actually we were and still are planning on supporting both standards until > they come up with one mix, and that in the end would also allow us for > more phone lines and modems in the end. I agree with you on that. > > -Gary Margiotta > TBE Internet Services > http://www.tbe.net > > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087 From owner-freebsd-isp Sat Jun 21 12:39:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15665 for isp-outgoing; Sat, 21 Jun 1997 12:39:19 -0700 (PDT) Received: from mail.westsound.com (root@mail.westsound.com [206.129.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15657 for ; Sat, 21 Jun 1997 12:39:15 -0700 (PDT) Received: from admin (annex-22.hctc.com [206.129.34.22]) by mail.westsound.com (8.8.5/8.6.9) with SMTP id MAA21407 for ; Sat, 21 Jun 1997 12:39:07 -0700 Message-Id: <3.0.1.32.19970621123658.00b5f9f8@mail.westsound.com> X-Sender: patrick@mail.westsound.com X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Sat, 21 Jun 1997 12:36:58 -0700 To: freebsd-isp@freebsd.org From: Patrick Vierheilig Subject: Wireless Services Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings All. I am new to FreeBSD, as well a this list (obviously :), and I have searched the relevant archives at FreeBSD, with little information being found on using FreeBSD in a wireless setup, so if there is another place I should look, please let me know. We want to setup a box as a wireless bridge to our ethernet for a point-to-multipoint system as opposed to buying a proprietary bridge. Any comments/thoughts would be appreciated or pointers to other resources. Sorry if this has been discussed already in detail, I just could not find it in the archives. TIA, Patrick From owner-freebsd-isp Sat Jun 21 13:17:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17273 for isp-outgoing; Sat, 21 Jun 1997 13:17:03 -0700 (PDT) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17268 for ; Sat, 21 Jun 1997 13:17:00 -0700 (PDT) Received: from Gatekeeper.Alameda.net (ulf@gatekeeper.Alameda.net [207.90.181.2]) by DNS.Lamb.net (8.8.5/8.8.5) with ESMTP id NAA01841; Sat, 21 Jun 1997 13:17:09 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.Alameda.net (8.8.5/8.7.6) id NAA11363; Sat, 21 Jun 1997 13:16:53 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199706212016.NAA11363@Gatekeeper.Alameda.net> Subject: Re: ISDN In-Reply-To: from "Gary D. Margiotta" at "Jun 21, 97 02:57:45 pm" To: gary@tbe.net (Gary D. Margiotta) Date: Sat, 21 Jun 1997 13:16:53 -0700 (PDT) Cc: blaz@gold.amis.net, freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Until now I did not find any other TA but the Omni 128. Which other TA's > > have two serial ports? > > Well, the USR courier I-Modem does, and I believe there is one from > Cardinal that does also, though I am not sure of the model #. > > > Yeah, I just registered for the 56K modem cards on www.livingston.com. > > I'm not so eagerly waiting for those anyway, because most customers over > > here use USR modems that do X2 instead of K56flex and I do not intend to > > support them anyway (get ISDN if you want higher speed). > > True, but in my situation, I am getting a PRI, which from my understanding > doesn't interface well with ISDN, and vice versa, though unfortunately I > didn't have much time to do the reasearch, the quality of our phone lines > is forcing my hands into going digital before we really wanted to. Looks like you have to very much research. PRI is ISDN. BRI is ISDN. It just gets delivered via different media (PRI = DS1, BRI = 1 pair twisted (like analog)) and PRI has more channels then BRI (24 (23 B channels, 1 D channel) against 3 (2 B channels, 1 D channel 16 kbp/sec)). > > > Won't this be an expensive route? First buying the USR units, then switching > > to PM3? I think that 56K is just an intermediate step and it will die sooner > > or later. > > Actually we were and still are planning on supporting both standards until > they come up with one mix, and that in the end would also allow us for > more phone lines and modems in the end. I agree with you on that. > > -Gary Margiotta > TBE Internet Services > http://www.tbe.net > > If you just need better phone lines, you can also go with phone lines delivered via T1 channelized and then either have the T1 going into a PBX or break out via a channel bank. T1 can also go directly into a PM3, but then only for analog calls. Or you use the PRI into a PM3 and can do ISDN and analog. Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 From owner-freebsd-isp Sat Jun 21 13:20:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17601 for isp-outgoing; Sat, 21 Jun 1997 13:20:49 -0700 (PDT) Received: from radford.i-plus.net (Radford.i-Plus.net [206.99.237.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17585 for ; Sat, 21 Jun 1997 13:20:43 -0700 (PDT) Received: from abyss.i-Plus.net (pitlord@Abyss.i-Plus.net [206.99.237.44]) by radford.i-plus.net (8.8.5/8.8.5) with SMTP id QAA01052; Sat, 21 Jun 1997 16:18:46 -0400 (EDT) Message-Id: <199706212018.QAA01052@radford.i-plus.net> X-Mailer: Microsoft Outlook Express 4.71.0544.0 From: "Troy Settle" To: "Blaz Zupan" , "Gary D. Margiotta" Cc: Subject: Re: ISDN Date: Sat, 21 Jun 1997 16:18:19 -0400 X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0 Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Gary D. Margiotta >True, but in my situation, I am getting a PRI, which from my understanding >doesn't interface well with ISDN, and vice versa, though unfortunately I >didn't have much time to do the reasearch, the quality of our phone lines >is forcing my hands into going digital before we really wanted to. PRI is a Primary Rate Interface BRI is a Basic Rate Interface both are ISDN, just the bandwidth is different. PRI has 23 B channels and 1 D channel, whereas BRI has 2 B channels and 1 D channel. There's lots of info about this on the web. You just gotta search for it. :) -- Troy Settle Network Administrator, iPlus Internet Services http://www.i-Plus.net From owner-freebsd-isp Sat Jun 21 14:49:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA21201 for isp-outgoing; Sat, 21 Jun 1997 14:49:43 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA21191 for ; Sat, 21 Jun 1997 14:49:32 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id OAA00698; Sat, 21 Jun 1997 14:49:23 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199706212149.OAA00698@GndRsh.aac.dev.com> Subject: Re: Wireless Services In-Reply-To: <3.0.1.32.19970621123658.00b5f9f8@mail.westsound.com> from Patrick Vierheilig at "Jun 21, 97 12:36:58 pm" To: patrick@mail.westsound.com (Patrick Vierheilig) Date: Sat, 21 Jun 1997 14:49:23 -0700 (PDT) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Greetings All. > > I am new to FreeBSD, as well a this list (obviously :), and I have searched > the relevant archives at FreeBSD, with little information being found on > using FreeBSD in a wireless setup, so if there is another place I should > look, please let me know. > > We want to setup a box as a wireless bridge to our ethernet for a ^^^^^^ > point-to-multipoint system as opposed to buying a proprietary bridge. Any > comments/thoughts would be appreciated or pointers to other resources. Your not going to make a ``bridge'' out of FreeBSD, unless you want to write your own bridging code (you have to run the interfaces in promiscous mode, collect MAC addresses and implement spanning tree or some other bridge forwarding code). You could make a wireless ``router'' out of FreeBSD very easily, I have had fairly good luck with the AT&T/Lucent Wavelan cards and FreeBSD as a router (the multicast code in the if_wl.c driver does not seem to be up to snuff as I had to convert OSPF/multicast to OSPF/nonbroadcast to make it work right.) But other than that snag it seems to be working quite well. > Sorry if this has been discussed already in detail, I just could not find > it in the archives. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-isp Sat Jun 21 15:36:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23507 for isp-outgoing; Sat, 21 Jun 1997 15:36:29 -0700 (PDT) Received: from uhf.wdc.net (uhf.wdc.net [198.147.74.44]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23498 for ; Sat, 21 Jun 1997 15:36:23 -0700 (PDT) Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id SAA03830; Sat, 21 Jun 1997 18:35:53 -0400 (EDT) Date: Sat, 21 Jun 1997 18:34:30 -0400 (EDT) From: Bernie Doehner To: "Rodney W. Grimes" cc: freebsd-isp@FreeBSD.ORG Subject: Re: Wireless Services In-Reply-To: <199706212149.OAA00698@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You could make a wireless ``router'' out of FreeBSD very easily, > I have had fairly good luck with the AT&T/Lucent Wavelan cards and > FreeBSD as a router (the multicast code in the if_wl.c driver does > not seem to be up to snuff as I had to convert OSPF/multicast to > OSPF/nonbroadcast to make it work right.) But other than that snag > it seems to be working quite well. > Which version of the driver are you running? Is this with Peter Wemm's MULTICAST mods in -current? I haven't had much time to devote to this lately, but I promised jrb@cs.pdx.edu and miff@spam.frisbee.net.au to also test the Multicasting mods that Peter Wemm added to the original miff driver. Looks like you beat me too it. Also, I have yet another version of the driver that supports the 2.4 Ghz. half-height with EEPROM/daughter card. Should test those so that miff can comit them soon. Bernie From owner-freebsd-isp Sat Jun 21 15:38:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23610 for isp-outgoing; Sat, 21 Jun 1997 15:38:15 -0700 (PDT) Received: from uhf.wdc.net (uhf.wdc.net [198.147.74.44]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23604 for ; Sat, 21 Jun 1997 15:38:08 -0700 (PDT) Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id SAA03844 for ; Sat, 21 Jun 1997 18:38:07 -0400 (EDT) Date: Sat, 21 Jun 1997 18:36:45 -0400 (EDT) From: Bernie Doehner To: isp@freebsd.org Subject: Re: Wireless Services Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Patrick: > I am new to FreeBSD, as well a this list (obviously :), and I have searched > the relevant archives at FreeBSD, with little information being found on > using FreeBSD in a wireless setup, so if there is another place I should > look, please let me know. > We want to setup a box as a wireless bridge to our ethernet for a > point-to-multipoint system as opposed to buying a proprietary bridge. Any > comments/thoughts would be appreciated or pointers to other resources. Outdoor or indoor? If indoor the easiest solution is to buy some NCR wavelan or DEC roamabout cards (http://www.wavelan.com, or http://www.networks.dec.com and search for RoamAbout). > Sorry if this has been discussed already in detail, I just could not find > it in the archives. > Well yes it has, but I personaly don't mind getting you started with this. Regarding Wavelan: jrb@cs.pdx.edu and miff@spam.frisbee.net.au have both worked hard at a 2.2-R compliant driver (actualy there is something submited to the 3.0 sources right now, and it works, except I haven't had time to test the multicasting part which has changed from the original driver. buaas@wireless.wdc.net has also made a few mods necessary to make the new 2.4 GHz. wavelans with dautherboard work. I am in the process of recompiling to test his new code with my (very old) 900 MHz. full height wavelan cards. What's your situation like? Bernie From owner-freebsd-isp Sat Jun 21 17:27:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA28113 for isp-outgoing; Sat, 21 Jun 1997 17:27:54 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28104 for ; Sat, 21 Jun 1997 17:27:43 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id TAA14578; Sat, 21 Jun 1997 19:56:42 -0400 (EDT) Date: Sat, 21 Jun 1997 19:56:42 -0400 (EDT) From: "John T. Farmer" Message-Id: <199706212356.TAA14578@sabre.goldsword.com> To: blaz@gold.amis.net, gary@tbe.net Subject: Re: ISDN Cc: freebsd-isp@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Jun 1997 14:57:45 -0400 (EDT) "Gary D. Margiotta" said: >Well, the USR courier I-Modem does, and I believe there is one from >Cardinal that does also, though I am not sure of the model #. > I didn't realize the I-courier has the 2 serial ports (our first ones to evaluate are not here yet :^<). > >True, but in my situation, I am getting a PRI, which from my understanding >doesn't interface well with ISDN, and vice versa, though unfortunately I >didn't have much time to do the reasearch, the quality of our phone lines >is forcing my hands into going digital before we really wanted to. > ??? PRI is ISDN. Primary Rate Interface is 23 B channels with 1 64k D channel. It is delivered on a T-1 (European has 30 B channels & is delivered on an E-1 channel.) to your location from the telco's switch. >> Won't this be an expensive route? First buying the USR units, then switching >> to PM3? I think that 56K is just an intermediate step and it will die sooner >> or later. > Actually, I've found that _everything_ is expensive. It's just that sometimes the downside is worst !! John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-isp Sat Jun 21 19:52:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02981 for isp-outgoing; Sat, 21 Jun 1997 19:52:17 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02969 for ; Sat, 21 Jun 1997 19:52:06 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id TAA00982; Sat, 21 Jun 1997 19:50:02 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199706220250.TAA00982@GndRsh.aac.dev.com> Subject: Re: Wireless Services In-Reply-To: from Bernie Doehner at "Jun 21, 97 06:34:30 pm" To: bad@uhf.wireless.net (Bernie Doehner) Date: Sat, 21 Jun 1997 19:50:02 -0700 (PDT) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > You could make a wireless ``router'' out of FreeBSD very easily, > > I have had fairly good luck with the AT&T/Lucent Wavelan cards and > > FreeBSD as a router (the multicast code in the if_wl.c driver does > > not seem to be up to snuff as I had to convert OSPF/multicast to > > OSPF/nonbroadcast to make it work right.) But other than that snag > > it seems to be working quite well. > > > > Which version of the driver are you running? Is this with Peter Wemm's > MULTICAST mods in -current? Hummm... actually I am still running on the jrb/msmith version that was up for ftp at pdx.edu someplace under FreeBSD 2.2-stable (about 2 week old buy now). The problem seems to be that the card(s) [I am running multiple cards in the same box] are either a) hearing each other (how can that be, they are on different NWID's) or b) the multicast code is sending the same packets out all interfaces (gated/ospf could be in error here, but it works just fine when I replace all the wl cards with de cards.) > I haven't had much time to devote to this lately, but I promised > jrb@cs.pdx.edu and miff@spam.frisbee.net.au to also test the Multicasting > mods that Peter Wemm added to the original miff driver. Looks like you > beat me too it. :-). Too bad the router had to go into production use, or I could have done some more debugging. As is I just undef'ed MULTICAST and mark the interfaces non-broadcast in /etc/gated.conf and added a few router records to the ospf config section and it is working like a champ so far. The next task is multipath routing with a mesh configuration, that should be real interesting.... > Also, I have yet another version of the driver that supports the 2.4 Ghz. > half-height with EEPROM/daughter card. Should test those so that miff can > comit them soon. Ohh.. gee... I didn't realize the 2.4Ghz cards where different, arghh.. well... I might be an alpha/beta tester for that code as there are suppose to be some of these on the way here. One other thing... these cards don't seem to be to good at Collision Avodiance when you have a routing type of setup (ie, you have a central node with 2 cards in it talking to 2 other sites and are trying to ftp packets (gee, maybe a stick drawing would be better:)) A/wl0 <-----> wl0/B/wl1 <-----> wl0/C 18mi 12mi You can ftp really nice between A and B or B and C, but try to go from A to C and your bandwidth goes in the dump. I worked around it with some realy bad kludges, there has to be a better way! [Yes, folks you can make a wavelan go 18 miles.... how is left up as an exercise I don't care to repeat :-)] -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD