From owner-freebsd-isp Sun May 17 04:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12543 for freebsd-isp-outgoing; Sun, 17 May 1998 04:43:42 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA12537 for ; Sun, 17 May 1998 04:43:40 -0700 (PDT) (envelope-from manar@ivision.co.uk) Received: from pretender.ivision.co.uk [195.50.91.43] by stingray.ivision.co.uk with smtp (Exim 1.62 #2) id 0yb1qq-0001dk-00; Sun, 17 May 1998 12:43:36 +0100 Message-Id: <3.0.5.32.19980517124233.00988780@stingray.ivision.co.uk> X-Sender: manarpop@stingray.ivision.co.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 17 May 1998 12:42:33 +0100 To: Mark Mayo From: Manar Hussain Subject: Re: virtusertable weirdness Cc: isp@FreeBSD.ORG In-Reply-To: <19980516002148.B25146@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 00:21 16/05/98 -0400, Mark Mayo wrote: >Hi all.. I'm having an odd problem with the virtuser feature in >sendmail.. Hoping someone has run into the same problem. > >Basically, it don't work. :) Can't help with this in sendmail but I can say that we've found all our mailserver tweeking a LOT easier and quicker since moving to Exim (www.exim.org). Having a file that lists the numebr of additional domains and then an extra alias file per domain is about 10 lines in the config file. Exim's a pretty easy drop in replacment for sendmail and focuses on ease of use ... you might also look at qmail which focuses more on security and performance (though exim is much better than sendmail on this too). Manar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 05:39:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16412 for freebsd-isp-outgoing; Sun, 17 May 1998 05:39:43 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16399 for ; Sun, 17 May 1998 05:39:40 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA05419; Sun, 17 May 1998 12:55:34 +0200 From: Luigi Rizzo Message-Id: <199805171055.MAA05419@labinfo.iet.unipi.it> Subject: Re: Bandwidth limiter available To: julian@whistle.com (Julian Elischer) Date: Sun, 17 May 1998 12:55:33 +0200 (MET DST) Cc: hsu@clinet.fi, freebsd-isp@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at May 16, 98 07:26:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > * uses ipfw for packet filtering, which makes it easier to configure ... > > It may be easy to use, but ipfw is too inefficient implementation for this ... > I have a change to IPWF that will allow this to be improved radically. > by making the SKIPTO much more efficient you will be able to in the current version of dummynet there is a similar (i believe) optimization for pipes. A "pipe" rule has both a pipe number and a pointer to the pipe descriptor. The pointer is initially NULL, but it is initialized at the first lookup so that next operations are fast. It requires some cleanup work when pipes are deleted, and no change on insertion. I suppose a similar thing can be done for skipto rules. The reason i haven't implemented it yet is that (for dummynet at least) I may need to pass a packet through the firewall code multiple times. So, i want to implement a "goto" field in each rule, so that after a match, and next time the packet goes through the filter, processing countinues from the rule in the 'goto' field. This costs 6 more bytes in the rule which are already too large, so i am first looking for a way to recover space (it could be by "compiling" interface names into pointers, since now they use strncmp() to find a match, another source of inefficiency.) cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 05:42:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16847 for freebsd-isp-outgoing; Sun, 17 May 1998 05:42:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16836 for ; Sun, 17 May 1998 05:42:11 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA05430; Sun, 17 May 1998 12:58:00 +0200 From: Luigi Rizzo Message-Id: <199805171058.MAA05430@labinfo.iet.unipi.it> Subject: Re: Bandwidth limiter available To: julian@whistle.com (Julian Elischer) Date: Sun, 17 May 1998 12:57:59 +0200 (MET DST) Cc: hsu@clinet.fi, freebsd-isp@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at May 16, 98 07:26:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > * uses ipfw for packet filtering, which makes it easier to configure and i forgot another motivation: all optimization and improvements to the ipfw code will come for free to dummynet :) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 05:43:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16992 for freebsd-isp-outgoing; Sun, 17 May 1998 05:43:06 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16965; Sun, 17 May 1998 05:42:56 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA05400; Sun, 17 May 1998 12:35:35 +0200 From: Luigi Rizzo Message-Id: <199805171035.MAA05400@labinfo.iet.unipi.it> Subject: Re: Bandwidth limiter available To: kjc@csl.sony.co.jp (Kenjiro Cho) Date: Sun, 17 May 1998 12:35:35 +0200 (MET DST) Cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199805161810.DAA00252@hotaka.csl.sony.co.jp> from "Kenjiro Cho" at May 17, 98 03:10:37 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thanks Luigi for the clarification. > > In addition, modification to IF_DEQUEUE isn't enough. > There are several drivers that peeks at if_snd or use IF_PREPEND; > these operations don't work with multiple queues. > If the drivers are written not to use these operations, replacing > IF_DEQUEUE works fine. of course. i was in a hurry writing the msg. so i forgot to mention the above. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 05:44:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17283 for freebsd-isp-outgoing; Sun, 17 May 1998 05:44:16 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA17269 for ; Sun, 17 May 1998 05:44:13 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA05443; Sun, 17 May 1998 13:00:15 +0200 From: Luigi Rizzo Message-Id: <199805171100.NAA05443@labinfo.iet.unipi.it> Subject: Re: Bandwidth limiter available To: hsu@clinet.fi (Heikki Suonsivu) Date: Sun, 17 May 1998 13:00:15 +0200 (MET DST) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Heikki Suonsivu" at May 17, 98 02:16:47 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > * device-indipendent, since it works at the IP level; ALTQ > > works at a lower level so it needs to be aware of the interface > > (and this could be a problem in some cases). > > This could be fixed in various ways, either by creating better device > driver interface or adding extra layer (this would need simple > modifications to devide driver interface to get a good result). as reported in another thread, the IF_DEQUEUE and related macros must be transformed in upcalls to the queue handler . luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 08:30:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01366 for freebsd-isp-outgoing; Sun, 17 May 1998 08:30:47 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01361 for ; Sun, 17 May 1998 08:30:41 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id LAA02350; Sun, 17 May 1998 11:37:36 -0400 (EDT) (envelope-from mark) Message-ID: <19980517113735.B2319@vmunix.com> Date: Sun, 17 May 1998 11:37:35 -0400 From: Mark Mayo To: Manar Hussain Cc: isp@FreeBSD.ORG Subject: Re: virtusertable weirdness References: <19980516002148.B25146@vmunix.com> <3.0.5.32.19980517124233.00988780@stingray.ivision.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <3.0.5.32.19980517124233.00988780@stingray.ivision.co.uk>; from Manar Hussain on Sun, May 17, 1998 at 12:42:33PM +0100 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 17, 1998 at 12:42:33PM +0100, Manar Hussain wrote: > At 00:21 16/05/98 -0400, Mark Mayo wrote: > >Hi all.. I'm having an odd problem with the virtuser feature in > >sendmail.. Hoping someone has run into the same problem. > > > >Basically, it don't work. :) Well, turns out it was supid pilot error.. The Parse1 ruleset which handles the virtuser stuff was commented out down in my sendmail.cf file.. :-) The Kvirtuser hash -o works like a charm now. > Can't help with this in sendmail but I can say that we've found all our > mailserver tweeking a LOT easier and quicker since moving to Exim > (www.exim.org). Having a file that lists the numebr of additional domains > and then an extra alias file per domain is about 10 lines in the config > file. Exim's a pretty easy drop in replacment for sendmail and focuses on > ease of use ... you might also look at qmail which focuses more on security > and performance (though exim is much better than sendmail on this too). Yes, I've hear good things about exim and qmail, but I'm waiting for vmailer to mature a bit before evaluating sendmail replacements.. Sendmail really isn't that bad once you commit a bit of time to learning it, and after you know sendmail, you've got once heck of a flexible MTA! -Mark > > Manar -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 08:50:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03117 for freebsd-isp-outgoing; Sun, 17 May 1998 08:50:00 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA03112 for ; Sun, 17 May 1998 08:49:56 -0700 (PDT) (envelope-from manar@ivision.co.uk) Received: from pretender.ivision.co.uk [195.50.91.43] by stingray.ivision.co.uk with smtp (Exim 1.62 #2) id 0yb5hG-0002Wo-00; Sun, 17 May 1998 16:49:58 +0100 Message-Id: <3.0.5.32.19980517164855.00950d60@stingray.ivision.co.uk> X-Sender: manarpop@stingray.ivision.co.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 17 May 1998 16:48:55 +0100 To: Mark Mayo From: Manar Hussain Subject: Re: virtusertable weirdness Cc: isp@FreeBSD.ORG In-Reply-To: <19980517113735.B2319@vmunix.com> References: <3.0.5.32.19980517124233.00988780@stingray.ivision.co.uk> <19980516002148.B25146@vmunix.com> <3.0.5.32.19980517124233.00988780@stingray.ivision.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Yes, I've hear good things about exim and qmail, but I'm waiting for vmailer >to mature a bit before evaluating sendmail replacements.. Sendmail really >isn't that bad once you commit a bit of time to learning it, and after >you know sendmail, you've got once heck of a flexible MTA! Yup - sendmail is a it of a pig to get to the guts of but can do most things once you get there. Still, the two people who I at least consider sendmail gurus who have tried exim have stuck with it and considered it a lot easier to configure even though they knew sendmail well. Manar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 09:18:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06308 for freebsd-isp-outgoing; Sun, 17 May 1998 09:18:33 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from uhf.wireless.net (uhf.wireless.net [209.189.23.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06303 for ; Sun, 17 May 1998 09:18:31 -0700 (PDT) (envelope-from bad@uhf.wireless.net) Received: from localhost (bad@localhost) by uhf.wireless.net (8.8.8/8.8.7) with SMTP id JAA00667; Sun, 17 May 1998 09:16:57 -0700 (PDT) Date: Sun, 17 May 1998 09:16:57 -0700 (PDT) From: Bernie Doehner To: Mark Mayo cc: Manar Hussain , isp@FreeBSD.ORG Subject: Re: virtusertable weirdness In-Reply-To: <19980517113735.B2319@vmunix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Well, turns out it was supid pilot error.. The Parse1 ruleset which handles > the virtuser stuff was commented out down in my sendmail.cf file.. :-) :) That got me too once. :) It would appear sendmail.cf is shipped with it turned off. > The Kvirtuser hash -o works like a charm now. Apparently the -o is optional... Does anyone know what it does/means? Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 09:46:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09464 for freebsd-isp-outgoing; Sun, 17 May 1998 09:46:51 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from azuret.rominet.net (azuret.rominet.net [194.2.236.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09456; Sun, 17 May 1998 09:46:48 -0700 (PDT) (envelope-from Alain.Thivillon@alma.fr) Received: from khany.rominet.net (khany.rominet.net [194.2.236.62]) by azuret.rominet.net (8.9.0.Beta5-Perl/8.9.0.Beta5/ROMINET-033198) with ESMTP id SAA21381; Sun, 17 May 1998 18:46:34 +0200 (CEST) Received: (from titi@localhost) by khany.rominet.net (8.9.0.Beta5-Perl/8.9.0.Beta5/DIAL-033198) id SAA19763; Sun, 17 May 1998 18:46:33 +0200 (CEST) Message-ID: <19980517184632.A19755@rominet.net> Date: Sun, 17 May 1998 18:46:32 +0200 From: Alain Thivillon To: freebsd-isp@FreeBSD.ORG Cc: Manar Hussain , isp@FreeBSD.ORG Subject: Re: virtusertable weirdness References: <19980517113735.B2319@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Bernie Doehner on Sun, May 17, 1998 at 09:16:57AM -0700 X-Organization: Rominet Networks Inc. Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernie Doehner ecrivait (wrote) : > :) That got me too once. :) It would appear sendmail.cf is shipped with > it turned off. The 'good' way to use virtusertable is to compile a new .cf file using M4 configuration kit with a .mc file containing: FEATURE(virtusertable) See cf/README in sendmail distribution. There are a lot of useful other features here (generics, mailertable, ...). > Apparently the -o is optional... Does anyone know what it does/means? It means : optional :) . Sendmail will not complain if the database file can not be loaded. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 10:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13021 for freebsd-isp-outgoing; Sun, 17 May 1998 10:23:44 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13012 for ; Sun, 17 May 1998 10:23:41 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.0.Beta3/8.9.0.Beta3) with SMTP id NAA14067 for ; Sun, 17 May 1998 13:23:41 -0400 (EDT) Date: Sun, 17 May 1998 13:23:41 -0400 (EDT) From: jack To: isp@FreeBSD.ORG Subject: Re: virtusertable weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 17 May 1998, Bernie Doehner wrote: > > The Kvirtuser hash -o works like a charm now. > > Apparently the -o is optional... Does anyone know what it does/means? Why is RingTFM becoming a lost art? Aside from the Bat book (which, IMO, anyone needing to run sendmail as a daemon should own, and have read) and the man pages, FreeBSD includes nearly 380K of documentation on sendmail. A quick grep for `-o' in /usr/share/doc/smm/08.sendmailop reveals the following: -o Indicates that this map is optional -- that is, if it cannot be opened, no error is pro- duced, and sendmail will behave as if the map existed but was empty. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null Mail from netcom.com blocked until they stop relaying SPAM -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 12:20:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03228 for freebsd-isp-outgoing; Sun, 17 May 1998 12:20:14 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from uhf.wireless.net (uhf.wireless.net [207.137.157.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03223 for ; Sun, 17 May 1998 12:20:12 -0700 (PDT) (envelope-from bad@uhf.wireless.net) Received: from localhost (bad@localhost) by uhf.wireless.net (8.8.8/8.8.7) with SMTP id MAA00518; Sun, 17 May 1998 12:18:15 -0700 (PDT) Date: Sun, 17 May 1998 12:18:14 -0700 (PDT) From: Bernie Doehner To: jack cc: isp@FreeBSD.ORG Subject: Re: virtusertable weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for so kindly pointing out that this documentation exists. I had looked in the handbook and the docs that come with sendmail-8.8.8 and hadn't found it there. Bernie > > Why is RingTFM becoming a lost art? > > Aside from the Bat book (which, IMO, anyone needing to run > sendmail as a daemon should own, and have read) and the man > pages, FreeBSD includes nearly 380K of documentation on sendmail. > > A quick grep for `-o' in /usr/share/doc/smm/08.sendmailop reveals > the following: > > -o Indicates that this map is optional -- that > is, if it cannot be opened, no error is pro- > duced, and sendmail will behave as if the > map existed but was empty. > > -------------------------------------------------------------------------- > Jack O'Neill Systems Administrator / Systems Analyst > jack@germanium.xtalwind.net Crystal Wind Communications, Inc. > Finger jack@germanium.xtalwind.net for my PGP key. > PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD > enriched, vcard, HTML messages > /dev/null > Mail from netcom.com blocked until they stop relaying SPAM > -------------------------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 12:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07488 for freebsd-isp-outgoing; Sun, 17 May 1998 12:56:05 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from db1.icorp.net ([204.107.221.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07381; Sun, 17 May 1998 12:55:56 -0700 (PDT) (envelope-from mlistbsd@icorp.net) Received: from paul.icorp.net (p614.accesscom.net [206.160.14.14] (may be forged)) by db1.icorp.net (8.8.6/8.8.6) with SMTP id TAA07456; Sun, 17 May 1998 19:55:57 GMT Message-Id: <3.0.1.32.19980517145521.0069e5b4@icorp.net> X-Sender: mlistbsd@icorp.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sun, 17 May 1998 14:55:21 -0500 To: freebsd-questions@FreeBSD.ORG From: MP Subject: too many open files problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I'm running into a problem with FreeBSD 2.2.6. I have two Class C's on my network and recently a hacker tunnelled into the backbone and masqueraded under an unused IP in my subnet to do spamming. As a result, I opted to bind all my IP addresses - used or not, to one of my servers. So I have about 400 or so IPs bound. When I boot FBSD 2.2.6, everything works, but if I -HUP the nameserver, I get this in the messages log: May 17 14:29:37 mysys named[1266]: starting. named 4.9.6-REL Wed Mar 25 00:29: 44 GMT 1998 jkh@time.cdrom.com:/usr/obj/usr/src/usr.sbin/named May 17 14:29:37 mysys named[1266]: fcntl(dfd, F_DUPFD, 20): Too many open files May 17 14:29:37 mysys last message repeated 15 times The hard limit on open files is set at 360 - this may be inadequate since I may have up to 512 domains mapped to my server. I assume there is a relationship between these two concepts. In scanning the archives on FreeBSD.org, none of the solutions worked for me (regarding setting ulimit ...) - and I didn't try anything regarding compiling the kernel - I'm using the generic compilation right now. What are my options? Do I need to tune the kernel to solve this problem? If so, would someone be so kind as to walk me through this process? Initial examinations showed a value OPEN_MAX, but it simply referenced some header file that I could not find on the system - I haven't done enough research yet to figure out what to do. Any help would be GREATLY appreciated - please direct e-mail to: mp@icorp.net Thanks very much!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 16:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10764 for freebsd-isp-outgoing; Sun, 17 May 1998 16:04:47 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from RWSystems.net (root@rwsystr.RWSystems.net [204.251.23.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA10660 for ; Sun, 17 May 1998 16:04:22 -0700 (PDT) (envelope-from jwyatt@rwsystr.RWSystems.net) Received: from rwsystr.RWSystems.net by RWSystems.net with smtp (Smail3.1.29.1 #3) id m0ybCQs-0001hLC; Sun, 17 May 98 18:01 CDT Date: Sun, 17 May 1998 18:01:28 -0500 (CDT) From: James Wyatt To: isp@FreeBSD.ORG Subject: Re: virtusertable weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It kinda feels that way, doesn't it. Sometimes it's because there are too many Fing Ms T R. 8{) Sendmail and smail are both complex packages with scattered docs that are very expert-friendly. I usually look far and wide, but sometimes miss buried or scattered files. Many excellent technical folk are ADHD, so sometimes it's just the lack of sleep, focus, or medication. (Jolt and coffee are medications...) 8{) On Sun, 17 May 1998, jack wrote: > On Sun, 17 May 1998, Bernie Doehner wrote: > > > The Kvirtuser hash -o works like a charm now. > > Apparently the -o is optional... Does anyone know what it does/means? > > Why is RingTFM becoming a lost art? > [ rest deleted ] -- jwyatt@rwsystems.net - KA5VJL - We use both sendmail and smail here too... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sun May 17 19:03:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10344 for freebsd-isp-outgoing; Sun, 17 May 1998 19:03:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from divre5.telkom.co.id ([202.134.0.55]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA10336; Sun, 17 May 1998 19:03:53 -0700 (PDT) (envelope-from sandy@divre5.telkom.co.id) Received: from dial-up by divre5.telkom.co.id (SMI-8.6/SMI-SVR4) id IAA24581; Mon, 18 May 1998 08:54:55 -0700 Message-ID: <031501bd8200$8b825fb0$7305600a@dial-up.divre5.net> From: "Arisandy" To: "Question" , "Isp" Subject: ppp -auto -alias Date: Mon, 18 May 1998 08:59:01 +0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I configure ppp.conf like..... http://www.freebsd.org/ in ppp - pedantic ppp primer there is warning..... add route 0.0.0.0 already exits... and then....nothing happen...? I want my client (Win95) connect to internet with FreeBSD as a gateway........ I already set tcp/ip client gateway as ip in FreeBSD.... I run IE in client....the FreeBSD stay cool and the client can't connect to internet ?? what's wrong?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 00:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23717 for freebsd-isp-outgoing; Mon, 18 May 1998 00:11:46 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from tc.nsc.ru (ns.tc.nsc.ru [194.226.168.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23677 for ; Mon, 18 May 1998 00:11:32 -0700 (PDT) (envelope-from vitaly@tc.nsc.ru) Received: from localhost (vitaly@localhost) by tc.nsc.ru (8.8.8/8.8.8) with SMTP id OAA09540 for ; Mon, 18 May 1998 14:10:14 +0700 (NSS) (envelope-from vitaly@tc.nsc.ru) Date: Mon, 18 May 1998 14:10:07 +0700 (NSS) From: "Vitaly V. Belekhov" To: isp@FreeBSD.ORG Subject: FrontPage extensions. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hello! Some time ago I saw there are messages about FronPage extensions for FreeBSD. Can anyone give me URL for tarball with it, and maybe some instructions/suggestions? And, please don't tell about Microsoft's site (its slow as hell). PS: I'm amused with micrososoft site today (18.05). Not even show anything else than errors/parts of HTML sources. ;-) - ------------------------------------------------------------- Best wishes, Vitaly Belekhov PGP public key - finger://vitaly@tc.nsc.ru http://www.tc.nsc.ru/~vitaly -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBNV/e1aYVFaFPa3hBAQE9NgP/WAXDvQWCedDa58oz9kxHJrGlZJVMZetL 4Pdx+mOQ4jsbuhvNhrnXqqGcy0kafI4yXyqNmJaPwFNKnYlGjbud5X10sDH9hFcf JbdWEoL8Iy8tMMbtLUG9GjnSiicbFACHCwHV1EpeC4neIDEi1sqXHXzkDTZtFU44 bbRpQ848/YI= =IXRb -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 01:03:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00842 for freebsd-isp-outgoing; Mon, 18 May 1998 01:03:27 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00833 for ; Mon, 18 May 1998 01:03:25 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.9.0.Beta5/8.8.8) id BAA20551; Mon, 18 May 1998 01:02:04 -0700 (PDT) Message-ID: <19980518010204.48625@cpl.net> Date: Mon, 18 May 1998 01:02:04 -0700 From: Shawn Ramsey To: isp@FreeBSD.ORG Subject: sendmail upgrade Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Im not sure if this is a FreeBSD problem or not... but I upgraded to sendmail-8.9.0.Beta5. We have cgi script that lets people send mail from a web page form. Now, when someone trys to use this script we get the following error in /var/log/maillog : sendmail[18619]: NOQUEUE: SYSERR(nobody): /etc/sendmail.cf: line 0: cannot open: Permission denied If I change the permissions of sendmail.cf to 777 it works, but obviosly that is not a fix! :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 01:41:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06586 for freebsd-isp-outgoing; Mon, 18 May 1998 01:41:40 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06577 for ; Mon, 18 May 1998 01:41:37 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA151; Mon, 18 May 1998 10:40:02 +0200 Message-ID: <355FF40E.8887B974@pipeline.ch> Date: Mon, 18 May 1998 10:40:46 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Shawn Ramsey CC: isp@FreeBSD.ORG Subject: Re: sendmail upgrade References: <19980518010204.48625@cpl.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Shawn Ramsey wrote: > > Im not sure if this is a FreeBSD problem or not... but I upgraded to > sendmail-8.9.0.Beta5. We have cgi script that lets people send mail from a > web page form. Now, when someone trys to use this script we get the > following error in /var/log/maillog : > > sendmail[18619]: NOQUEUE: SYSERR(nobody): /etc/sendmail.cf: line 0: cannot open: > Permission denied > > If I change the permissions of sendmail.cf to 777 it works, but obviosly > that is not a fix! :) Maybe it's a bug in sendmail, thats why they call it BETA5 ;) Go and tell them the problem. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 01:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06924 for freebsd-isp-outgoing; Mon, 18 May 1998 01:43:24 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06919 for ; Mon, 18 May 1998 01:43:21 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.9.0.Beta5/8.8.8) id BAA03643; Mon, 18 May 1998 01:41:57 -0700 (PDT) Message-ID: <19980518014157.05631@cpl.net> Date: Mon, 18 May 1998 01:41:57 -0700 From: Shawn Ramsey To: IBS / Andre Oppermann Cc: isp@FreeBSD.ORG Subject: Re: sendmail upgrade References: <19980518010204.48625@cpl.net> <355FF40E.8887B974@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <355FF40E.8887B974@pipeline.ch>; from IBS / Andre Oppermann on Mon, May 18, 1998 at 10:40:46AM +0200 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Im not sure if this is a FreeBSD problem or not... but I upgraded to > > sendmail-8.9.0.Beta5. We have cgi script that lets people send mail from a > > web page form. Now, when someone trys to use this script we get the > > following error in /var/log/maillog : > > > > sendmail[18619]: NOQUEUE: SYSERR(nobody): /etc/sendmail.cf: line 0: cannot open: > > Permission denied > > > > If I change the permissions of sendmail.cf to 777 it works, but obviosly > > that is not a fix! :) > > Maybe it's a bug in sendmail, thats why they call it BETA5 ;) Go and > tell > them the problem. Maybe it is. I will post it to comp.mail.sendmail as well, but the reason I upgrades was for the DontProbeInterface feature. Without that, certain domains are being delivered locally when they should not be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 02:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14202 for freebsd-isp-outgoing; Mon, 18 May 1998 02:34:25 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA14196 for ; Mon, 18 May 1998 02:34:22 -0700 (PDT) (envelope-from manar@ivision.co.uk) Received: from pretender.ivision.co.uk [195.50.91.43] by stingray.ivision.co.uk with smtp (Exim 1.62 #2) id 0ybMJK-0006LZ-00; Mon, 18 May 1998 10:34:22 +0100 Message-Id: <3.0.5.32.19980518103321.0097b600@stingray.ivision.co.uk> X-Sender: manarpop@stingray.ivision.co.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 18 May 1998 10:33:21 +0100 To: "Vitaly V. Belekhov" From: Manar Hussain Subject: Re: FrontPage extensions. Cc: isp@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Some time ago I saw there are messages about FronPage extensions >for FreeBSD. Can anyone give me URL for tarball with it, and >maybe some instructions/suggestions? And, please don't tell >about Microsoft's site (its slow as hell). http://www.thebestisp.com/freebsd/fpsetup.html and/or the "apache-fp" from the ports collection ... Manar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 03:55:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27234 for freebsd-isp-outgoing; Mon, 18 May 1998 03:55:31 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from ms.lawton.com.cn ([202.96.242.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27221 for ; Mon, 18 May 1998 03:55:21 -0700 (PDT) (envelope-from haifeng@ms.lawton.com.cn) Received: from jianping ([202.96.242.251]) by ms.lawton.com.cn (8.8.7/8.8.7) with SMTP id SAA00456 for ; Mon, 18 May 1998 18:56:56 +0800 (CST) (envelope-from haifeng@ms.lawton.com.cn) Message-ID: <009901bd8243$07e06c90$fbf260ca@jianping.lawton.com.cn> From: "Haifeng" To: Subject: remote annex ,freebsd and radius Date: Mon, 18 May 1998 18:55:04 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi guy: I use radius server and bay remote annex 2000 as the auth an account server, I meet a problem, I want to some user only can user e-mail or only can access one server, so I config the filter-id in ther radius "user" file, but I don't konw how to config a filter on the remote annex , anybody has experience on setting filter on the reomote annex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 04:39:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04111 for freebsd-isp-outgoing; Mon, 18 May 1998 04:39:49 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from link.cpt.nsc.iafrica.com (link.cpt.nsc.iafrica.com [196.31.1.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04098 for ; Mon, 18 May 1998 04:39:41 -0700 (PDT) (envelope-from khetan@link.freebsd.os.org.za) Received: from localhost (khetan@localhost) by link.cpt.nsc.iafrica.com (8.8.8+3.0Wbeta13/8.8.8) with SMTP id NAA05732; Mon, 18 May 1998 13:31:23 +0200 (SAT) Date: Mon, 18 May 1998 13:31:23 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@link.cpt.nsc.iafrica.com Reply-To: Khetan Gajjar To: Manar Hussain cc: "Vitaly V. Belekhov" , isp@FreeBSD.ORG Subject: Re: FrontPage extensions. In-Reply-To: <3.0.5.32.19980518103321.0097b600@stingray.ivision.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 May 1998, Manar Hussain wrote: >and/or the "apache-fp" from the ports collection ... There is no apache-fp in the ports collection. What _did_ work very well for me was http://www.westbend.net/~hetzels/apache-fp/ I had some problems initially, because I wanted to build Apache with both mod_perl _and_ Apache, but I got it working. If you build with just mod_frontpage, you shouldn't have any problems. --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za UUNET Internet Africa Support * FreeBSD enthusiast-www2.za.freebsd.org FreeBSD: Because rebooting is for adding new hardware To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 06:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10237 for freebsd-isp-outgoing; Mon, 18 May 1998 06:42:43 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mjhb.marina-del-rey.ca.us (mjhb.marina-del-rey.ca.us [204.254.69.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10231 for ; Mon, 18 May 1998 06:42:40 -0700 (PDT) (envelope-from marty@mjhb.marina-del-rey.ca.us) Received: from nt.mjhb.marina-del-rey.ca.us (pool042-maxa.gardena-ca-us.dialup.earthlink.net [207.217.20.192]) by mjhb.marina-del-rey.ca.us (8.8.5/8.8.5) with SMTP id GAA07616; Mon, 18 May 1998 06:42:30 -0700 (PDT) Date: Mon, 18 May 1998 06:45:07 -0700 (Pacific Daylight Time) From: Marty Bower Reply-To: Marty Bower To: Shawn Ramsey cc: isp@FreeBSD.ORG Subject: Re: sendmail upgrade In-Reply-To: <19980518010204.48625@cpl.net> Message-ID: X-mailer: Pine-3.96 (NT 4.0 i586) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 May 1998, Shawn Ramsey wrote: > sendmail[18619]: NOQUEUE: SYSERR(nobody): /etc/sendmail.cf: line 0: > cannot open: Permission denied Check/set permissions on /usr/sbin/sendmail: -r-sr-xr-x 2 root bin 323952 May 13 21:01 /usr/sbin/sendmail -- Marty Bower | marty@mjhb.mdr.ca.us | http://mjhb.mdr.ca.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 10:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14691 for freebsd-isp-outgoing; Mon, 18 May 1998 10:06:26 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mailhub.ainet.com (mailhub.ainet.com [204.30.40.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14673 for ; Mon, 18 May 1998 10:06:21 -0700 (PDT) (envelope-from jmscott@ainet.com) Received: from ainet.com (root@ainet.com [204.30.40.6]) by mailhub.ainet.com (8.8.8/8.8.7) with SMTP id KAA05142; Mon, 18 May 1998 10:02:40 -0700 (PDT) (envelope-from jmscott@ainet.com) Received: from perl.ainet.com () by ainet.com (4.1/SMI-4.1) id AA16156; Mon, 18 May 98 10:06:50 PDT Message-Id: <3.0.5.32.19980518100722.00ae5960@mail.ainet.com> X-Sender: jmscott@mail.ainet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 18 May 1998 10:07:22 -0700 To: "Vitaly V. Belekhov" , isp@FreeBSD.ORG From: "Joseph M. Scott" Subject: Re: FrontPage extensions. In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Check out http://www.westbend.net/~hetzels/apache-fp/ someone has been working on making apache and fp extensions a reasonably working port. I haven't tried it lately so be sure to read up on it first. Joseph Scott jmscott@ainet.com At 02:10 PM 5/18/98 +0700, Vitaly V. Belekhov wrote: >-----BEGIN PGP SIGNED MESSAGE----- > >Hello! > >Some time ago I saw there are messages about FronPage extensions >for FreeBSD. Can anyone give me URL for tarball with it, and >maybe some instructions/suggestions? And, please don't tell >about Microsoft's site (its slow as hell). > >PS: I'm amused with micrososoft site today (18.05). Not even >show anything else than errors/parts of HTML sources. ;-) > >- ------------------------------------------------------------- > Best wishes, Vitaly Belekhov > PGP public key - finger://vitaly@tc.nsc.ru > http://www.tc.nsc.ru/~vitaly > >-----BEGIN PGP SIGNATURE----- >Version: PGPfreeware 5.0i for non-commercial use >Charset: noconv > >iQCVAwUBNV/e1aYVFaFPa3hBAQE9NgP/WAXDvQWCedDa58oz9kxHJrGlZJVMZetL >4Pdx+mOQ4jsbuhvNhrnXqqGcy0kafI4yXyqNmJaPwFNKnYlGjbud5X10sDH9hFcf >JbdWEoL8Iy8tMMbtLUG9GjnSiicbFACHCwHV1EpeC4neIDEi1sqXHXzkDTZtFU44 >bbRpQ848/YI= >=IXRb >-----END PGP SIGNATURE----- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 13:01:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17211 for freebsd-isp-outgoing; Mon, 18 May 1998 13:01:17 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17185 for ; Mon, 18 May 1998 13:01:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA15573; Mon, 18 May 1998 12:51:38 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015566; Mon May 18 19:51:28 1998 Date: Mon, 18 May 1998 12:51:23 -0700 (PDT) From: Julian Elischer To: isp@FreeBSD.ORG cc: Kerri Kraft Subject: ISP Marketing Statistics (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [forwarded...] I am a Product Marketing Manager for Internet Commerce at VeriFone. I am looking for market statistics. Specifically, of the ISPs in the US, what is the number (or %) of FreeBSD installations and can that number be broken down by local, regional, and national ISPs? Is Linux considered a competitor? How do you compare with them in the ISP market place? Thank you, Kerri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 13:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20800 for freebsd-isp-outgoing; Mon, 18 May 1998 13:14:26 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20640; Mon, 18 May 1998 13:13:48 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id NAA09871; Mon, 18 May 1998 13:13:35 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 18 May 1998 13:13:35 -0700 (PDT) From: Doug White Reply-To: Doug White To: Arisandy cc: Isp , Question Subject: Re: ppp.conf sample? In-Reply-To: <000e01bd7f18$87190b30$7305600a@dial-up.divre5.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 14 May 1998, Arisandy wrote: > thanks everyone....my ppp sever run smoothly now :) > > now i want to connect 3 machines to internet using ppp -alias... > anyone have ppp.conf and ppp.linkup example....for that?? > > i use ppp.conf and ppp.linkup in pedantic ppp primer it's contain error :( > Warning :OK-AT-OK\\dATDT\\T : invalid command It looks like you wrapped the `set dial' command. It should be all on one line. > Warning :Add route failed: 0.0.0.0 already exits You already have a default route. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 15:37:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23904 for freebsd-isp-outgoing; Mon, 18 May 1998 15:37:05 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23892; Mon, 18 May 1998 15:37:02 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id PAA10272; Mon, 18 May 1998 15:37:01 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 18 May 1998 15:37:01 -0700 (PDT) From: Doug White Reply-To: Doug White To: Arisandy cc: Question , Isp Subject: Re: ppp -auto -alias In-Reply-To: <031501bd8200$8b825fb0$7305600a@dial-up.divre5.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 May 1998, Arisandy wrote: > I configure ppp.conf like..... > http://www.freebsd.org/ in ppp - pedantic ppp primer > > there is warning..... > add route 0.0.0.0 already exits... > and then....nothing happen...? Try running delete ALL and/or make sure your default route is removed before running ppp, and/or check /etc/ppp/ppp.linkup for correctness. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 16:09:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04063 for freebsd-isp-outgoing; Mon, 18 May 1998 16:09:59 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from br01.acw-web.com (br01.acw-web.com [156.46.248.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04032 for ; Mon, 18 May 1998 16:09:43 -0700 (PDT) (envelope-from webmaster@ac-ent.com) Received: from br02 (br02.acw-web.com [156.46.248.99]) by br01.acw-web.com (8.8.6/8.8.6) with SMTP id SAA27245 for ; Mon, 18 May 1998 18:18:00 -0500 (CDT) Message-Id: <3.0.5.32.19980518180945.00993100@acw-web.com> X-Sender: jwenger@acw-web.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 18 May 1998 18:09:45 -0500 To: FreeBSD ISP list From: Jack Wenger Subject: Hardware RAID and FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone running hardware raid on their FSBD system? If so, which adaptor(s) are supported? We have a client that wants us to bild them a mail server and wants us to use raid 1 or 0+1. This must also be implemented using interal drives on the server. I did a search of the FBSD site and handbook and only found mention of aftermarket arays using embedded FBSD. Also, I can't remember if I can use software raid in FBSD 2.2.7. Thanx! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jack Wenger - Webmaster webmaster@acw-web.com AC Enterprises - IBM Business Partner - Internet Specialist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 16:44:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11367 for freebsd-isp-outgoing; Mon, 18 May 1998 16:44:34 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from sulima.sulima.com (sulima.sulima.com [209.122.61.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11295; Mon, 18 May 1998 16:43:59 -0700 (PDT) (envelope-from ichi@sulima.sulima.com) Received: (from ichi@localhost) by sulima.sulima.com (8.8.8/8.8.8) id TAA08659; Mon, 18 May 1998 19:45:40 GMT (envelope-from ichi) From: bush doctor Ichi Message-Id: <199805181945.TAA08659@sulima.sulima.com> Subject: why doesn't MAKEDEV make ttyc[1-N]? To: questions@FreeBSD.ORG Date: Mon, 18 May 1998 19:45:40 +0000 (GMT) Cc: isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, I've searched high and I've searched low, now I'm searching in-between ... =;-) In looking to configure my Cyclades Cyclom 8yo for use with either ppp(8) or pppd(8) and mgetty I keep seeing references to /dev/ttyc?. Now MAKEDEV doesn't make these devices. Why? I know I can use mknod(8) to create them. Is this what we're suppose to do? I can't seem to find anything specific on this, so if someone in the know would enlighten me on this I'd appreciate it!!!! Thanxs in advance ... i'chi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 19:24:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13751 for freebsd-isp-outgoing; Mon, 18 May 1998 19:24:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from kaschynna.com (kaschynna.com [206.63.164.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13698 for ; Mon, 18 May 1998 19:23:55 -0700 (PDT) (envelope-from flerll@kaschynna.com) Received: from localhost (flerll@localhost) by kaschynna.com (8.8.8/8.8.8) with SMTP id TAA27764 for ; Mon, 18 May 1998 19:13:59 -0700 (PDT) Date: Mon, 18 May 1998 19:13:59 -0700 (PDT) From: Jerry Blancher To: isp@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe isp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 21:42:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05033 for freebsd-isp-outgoing; Mon, 18 May 1998 21:42:29 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from divre5.telkom.co.id ([202.134.0.55]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA04880; Mon, 18 May 1998 21:41:56 -0700 (PDT) (envelope-from sandy@divre5.telkom.co.id) Received: from dial-up by divre5.telkom.co.id (SMI-8.6/SMI-SVR4) id LAA06222; Tue, 19 May 1998 11:32:50 -0700 Message-ID: <018d01bd82df$c2b71c20$7305600a@dial-up.divre5.net> From: "Arisandy" To: "Question" , "Isp" Subject: ppp -auto -alias Date: Tue, 19 May 1998 11:36:55 +0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I run delete ALL in default section...still default route exits.... my local ipaddress is 10.96.5.180 (freeBSD) ....and my lan gateway is 10.96.5.1 my client is 10.96.5.181 and 10.96.5.182..... ip address from isp is dynamic..... if i try ppp -ddial demand.... add default route exits.... and then few seconds....there is messages like this... ppp[180] tun0: Error : OpemModem failed :/ dev/cuaa0 : Interrupt system call I use this line as dial in server....I try to kill getty in process.. but still the same problem.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 18 22:24:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14258 for freebsd-isp-outgoing; Mon, 18 May 1998 22:24:42 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from jaguar.ir.miami.edu (jaguar.ir.miami.edu [129.171.32.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14192; Mon, 18 May 1998 22:24:24 -0700 (PDT) (envelope-from marcus@miami.edu) Received: from localhost by jaguar.ir.miami.edu (PMDF V5.1-10 #24029) with SMTP id <0ET600D01V08R9@jaguar.ir.miami.edu>; Tue, 19 May 1998 01:24:08 -0400 (EDT) Date: Tue, 19 May 1998 01:24:08 -0400 (EDT) From: "Joe \"Marcus\" Clarke" Subject: Re: ppp -auto -alias In-reply-to: <018d01bd82df$c2b71c20$7305600a@dial-up.divre5.net> To: Arisandy Cc: Question , Isp Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a good deal of experience with ppp -auto -alias. Can you send me your ppp.conf and ppp.linkup files (with passwords and such omitted), and I'll see what I can do. Joe Clarke On Tue, 19 May 1998, Arisandy wrote: > I run delete ALL in default section...still default route exits.... > > my local ipaddress is 10.96.5.180 (freeBSD) ....and my lan gateway is > 10.96.5.1 > my client is 10.96.5.181 and 10.96.5.182..... > ip address from isp is dynamic..... > > if i try ppp -ddial demand.... > add default route exits.... > and then few seconds....there is messages like this... > > ppp[180] tun0: Error : OpemModem failed :/ dev/cuaa0 : Interrupt system call > > I use this line as dial in server....I try to kill getty in process.. > but still the same problem.... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 02:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01160 for freebsd-isp-outgoing; Tue, 19 May 1998 02:35:56 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from imap.ncsa.es (correo.nexus.es [194.179.50.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01128 for ; Tue, 19 May 1998 02:35:46 -0700 (PDT) (envelope-from jesusr@ncsa.es) Received: from jesus.nexus.es (piolin.ncsa.es [194.179.50.134]) by imap.ncsa.es (8.8.8/8.8.8) with SMTP id MAA26106 for ; Tue, 19 May 1998 12:02:36 +0200 (CEST) Reply-To: "Jesus Rodriguez" From: "Jesus Rodriguez" To: Subject: ISDN Pool Date: Tue, 19 May 1998 11:39:31 +0200 Message-ID: <01bd830a$0696ce20$8632b3c2@jesus.nexus.es> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello... I would like to know if someone is using freebsd like ppp server and isdn pool with a multiport serial card and isdn ta's. Wich multiport serial card and ta's are you using ?? At this moment we are using telebit Netblazer with isdn cards, but we would like moving to freebsd if possible. Thanks in advance. --------------------------------------------------------- Jesus Rodriguez (jesusr@ncsa.es) Dpto. Tecnico Nexus Comunicaciones, S.A. Telf. 902-466664 --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 03:58:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15256 for freebsd-isp-outgoing; Tue, 19 May 1998 03:58:34 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.bit-net.com ([208.146.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15244; Tue, 19 May 1998 03:58:31 -0700 (PDT) (envelope-from sderdau@bit-net.com) Received: from derdau.bit-net.com (derdau.bit-net.com [207.51.120.250]) by mail.bit-net.com (8.8.8/8.8.8) with SMTP id GAA00543; Tue, 19 May 1998 06:53:54 -0400 (EDT) Message-ID: <356164E5.446B9B3D@bit-net.com> Date: Tue, 19 May 1998 06:54:29 -0400 From: "Stephen A. Derdau" X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Arisandy CC: Question , Isp Subject: Re: ppp -auto -alias References: <018d01bd82df$c2b71c20$7305600a@dial-up.divre5.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm new to this FreeBSD stuff. Maybe this will help you....I start it by ppp -auto -alias derdau You may want to make some changes below. anyways it works for me. Hope it will work for you. After I start it I ping any address or callup netscape and it dials in automatically. My other machines on the my net use the FreeBSD machine as a gateway. default: set device /dev/cuaa1 set speed 115200 set log Phase Chat Connect Carrier lcp ipcp ccp command disable lqr deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 15 \"\" ATE1Q0 OK-AT-OK \\dATDT \\T TIMEOUT 40 CONNECT" #iij-demand: derdau: set authname USERNAME HERE * set authkey PASSWRD HERE * set phone ####### ISP PHONE NUMBER HERE * set openmode active # set openmode passive set timeout 0 accept pap set ifaddr 208.145.132.31/0 207.51.120.26/0 add 0 0 207.51.120.26 Arisandy wrote: > > I run delete ALL in default section...still default route exits.... > > my local ipaddress is 10.96.5.180 (freeBSD) ....and my lan gateway is > 10.96.5.1 > my client is 10.96.5.181 and 10.96.5.182..... > ip address from isp is dynamic..... > > if i try ppp -ddial demand.... > add default route exits.... > and then few seconds....there is messages like this... > > ppp[180] tun0: Error : OpemModem failed :/ dev/cuaa0 : Interrupt system call > > I use this line as dial in server....I try to kill getty in process.. > but still the same problem.... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- "FreeBSD It's That and Much Much More" Find out Why @ http://www.freebsd.org Stephen A. Derdau To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 09:01:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13686 for freebsd-isp-outgoing; Tue, 19 May 1998 09:01:02 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from iservern.teligent.se (iservern.teligent.se [194.17.198.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13665 for ; Tue, 19 May 1998 09:00:57 -0700 (PDT) (envelope-from jakob@teligent.se) Received: from datorn.teligent.se (datorn.teligent.se [192.168.2.31]) by iservern.teligent.se (8.8.7/8.8.7) with SMTP id SAA04265; Tue, 19 May 1998 18:00:39 +0200 (CEST) (envelope-from jakob@teligent.se) Date: Tue, 19 May 1998 18:00:39 +0200 (CEST) From: Jakob Alvermark To: Jack Wenger cc: FreeBSD ISP list Subject: Re: Hardware RAID and FreeBSD In-Reply-To: <3.0.5.32.19980518180945.00993100@acw-web.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id JAA13668 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 May 1998, Jack Wenger wrote: > Is anyone running hardware raid on their FSBD system? If so, which > adaptor(s) are supported? We have a client that wants us to bild them a > mail server and wants us to use raid 1 or 0+1. This must also be > implemented using interal drives on the server. I did a search of the FBSD > site and handbook and only found mention of aftermarket arays using > embedded FBSD. Hello. We use a few of CMD-tech's hardware SCSI RAID controllers. They appear on the SCSI-bus as a single large disk. /Jakob Alvermark ------------------------------------------------------- Teligent AB, P.O. Box 213, S-149 23 Nynäshamn, Sweden Telephone +46-(0)8 520 660 00 * Fax +46-(0)8 520 193 36 Direct +46-(0)8 520 660 32 * GSM +46-(0)70 792 16 57 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 11:25:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12232 for freebsd-isp-outgoing; Tue, 19 May 1998 11:25:55 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from huron.nvl.virginia.edu (adrian@mail.nvl.Virginia.EDU [128.143.244.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12200 for ; Tue, 19 May 1998 11:25:39 -0700 (PDT) (envelope-from adrian@nvl.virginia.edu) Received: from localhost (adrian@localhost) by huron.nvl.virginia.edu (8.8.6 (PHNE_14041)/8.8.6) with SMTP id OAA15378; Tue, 19 May 1998 14:25:16 -0400 (EDT) Date: Tue, 19 May 1998 14:25:16 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Jack Wenger cc: FreeBSD ISP list Subject: Re: Hardware RAID and FreeBSD In-Reply-To: <3.0.5.32.19980518180945.00993100@acw-web.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 May 1998, Jack Wenger wrote: > Is anyone running hardware raid on their FSBD system? If so, which > adaptor(s) are supported? We have a client that wants us to bild them a > mail server and wants us to use raid 1 or 0+1. This must also be > implemented using interal drives on the server. I did a search of the FBSD > site and handbook and only found mention of aftermarket arays using > embedded FBSD. > Also, I can't remember if I can use software raid in FBSD 2.2.7. > Thanx! I cannot personally vouch for this, but I understand a lot of people are very pleased with DPT devices. They support the maintenance of FreeBSD drivers. Check both the mailing list archives at www.freebsd.org and the DPT web site at www.dpt.com. cheers, Adrian -- adrian@virginia.edu ---->>>>| If I were stranded on a desert island, and System Administrator --->>>| I could only have one OS for my computer, Neurosurgical Visualization Lab ->>| it would be FreeBSD. Think about it..... http://www.nvl.virginia.edu/ ->| http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 11:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18081 for freebsd-isp-outgoing; Tue, 19 May 1998 11:54:14 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from cscfx.sytex.com (rwc@cscfx.sytex.com [205.147.190.131]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA17979 for ; Tue, 19 May 1998 11:53:43 -0700 (PDT) (envelope-from rwc@sytex.net) Received: (from rwc@localhost) by cscfx.sytex.com (8.6.12/8.6.9) id OAA25315; Tue, 19 May 1998 14:53:15 -0400 From: Richard Cramer Message-Id: <199805191853.OAA25315@cscfx.sytex.com> Subject: FnPage98 with Apache V1.3b6 To: hetzels@westbend.net, joe@thebestisp.com Date: Tue, 19 May 1998 14:53:15 -0400 (EDT) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Scott ... Taking a quick look at the FnPage extensions on your site it appears that they are all for Apache 1.2.6. Is anyone trying to use them or their own version with Apache 1.3b6? It also appears that the Microsoft patches (fp30...tar.Z) probably would not work either. Your thoughts. Is everyone using Apache 1.2.6? Is any attempt being made to work with Apache 1.3b6? Will the extensions at your site compile under native FreeBSD or are you running compat? If so to which version? Dick -- Richard Cramer rcramer@sytex.net Phone: 703-425-2515 President Fax: 703-425-4585 SytexNet(tm) Sytex Access Ltd. POB 2385, Fairfax, VA 22031-0385 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 12:36:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27986 for freebsd-isp-outgoing; Tue, 19 May 1998 12:36:27 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27919 for ; Tue, 19 May 1998 12:36:13 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id OAA03265; Tue, 19 May 1998 14:36:02 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <002d01bd835d$5b547220$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "Richard Cramer" Cc: Subject: Re: FnPage98 with Apache V1.3b6 Date: Tue, 19 May 1998 14:36:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Richard Cramer >Scott ... > >Taking a quick look at the FnPage extensions on your site it appears that >they are all for Apache 1.2.6. Is anyone trying to use them or their own >version with Apache 1.3b6? It also appears that the Microsoft patches >(fp30...tar.Z) probably would not work either. Your thoughts. > Currently, that is the case due to the way microsoft has packaged the mod_frontpage module (located in one big patch fp-patch-apache_1.2.5). Don't know if anyone using them with Apache 1.3b6. The frontpage extentions may work (fp30..tar.Z) with 1.3.b6, but frontpage module patch probably will not apply. >Is everyone using Apache 1.2.6? Is any attempt being made to work with >Apache 1.3b6? Will the extensions at your site compile under native >FreeBSD or are you running compat? If so to which version? > Currently the FP extensions and Apache w/FrontPage module will have to use Apache v1.2.6. Since there is a apache-current port (v1.3b6), I guess I'll have to give it a try and port the FrontPage module to it. Apache w/FrontPage Module compiles natively under FreeBSD, but the extensions are pre-compiled for BSDi (v3.0), I do have all 3 compat libraries installed on my system but don't believe they are required. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 17:03:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22146 for freebsd-isp-outgoing; Tue, 19 May 1998 17:03:37 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22082; Tue, 19 May 1998 17:03:12 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA21189; Wed, 20 May 1998 00:43:47 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805192343.AAA21189@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: "Arisandy" cc: "Question" , "Isp" Subject: Re: ppp -auto -alias In-reply-to: Your message of "Tue, 19 May 1998 11:36:55 +0700." <018d01bd82df$c2b71c20$7305600a@dial-up.divre5.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 May 1998 00:43:47 +0100 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I run delete ALL in default section...still default route exits.... `delete all' deletes all routes for the tun device that ppp owns. If you've got a default route via another interface that you want to remove, use `delete 0' or `delete default'. > my local ipaddress is 10.96.5.180 (freeBSD) ....and my lan gateway is > 10.96.5.1 > my client is 10.96.5.181 and 10.96.5.182..... > ip address from isp is dynamic..... > > if i try ppp -ddial demand.... > add default route exits.... > and then few seconds....there is messages like this... > > ppp[180] tun0: Error : OpemModem failed :/ dev/cuaa0 : Interrupt system call This is because opening /dev/cuaa0 is blocking. Why, I don't know. > I use this line as dial in server....I try to kill getty in process.. > but still the same problem.... I assume the getty's running on /dev/ttyd0. If not, that'll be the problem. It mustn't run on /dev/cuaa0 (unless it's mgetty). -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 17:41:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29449 for freebsd-isp-outgoing; Tue, 19 May 1998 17:41:17 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from divre5.telkom.co.id ([202.134.0.55]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA29412; Tue, 19 May 1998 17:41:04 -0700 (PDT) (envelope-from sandy@divre5.telkom.co.id) Received: from dial-up by divre5.telkom.co.id (SMI-8.6/SMI-SVR4) id HAA12237; Wed, 20 May 1998 07:32:11 -0700 Message-ID: <018701bd8387$50207550$7305600a@dial-up.divre5.net> From: "Arisandy" To: "Question" , "Isp" Subject: Digi Ports/8 EM Date: Wed, 20 May 1998 07:36:20 +0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have Digi Ports/8EM .... how can I use it in FreeBSD? is there any driver for FreeBSD? I check in www.digii.com there is only for Linux system ? thanks, <----, Arisandy <----|======================= <----' sandy@divre5.telkom.co.id To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 18:19:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05668 for freebsd-isp-outgoing; Tue, 19 May 1998 18:19:42 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05573 for ; Tue, 19 May 1998 18:19:10 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id UAA04054; Tue, 19 May 1998 20:18:38 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <008d01bd838d$37954a00$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "Richard Cramer" Cc: Subject: Re: FnPage98 with Apache V1.3b6 Date: Tue, 19 May 1998 20:18:37 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Scot W. Hetzel >Apache v1.2.6. Since there is a apache-current port (v1.3b6), I guess I'll >have to give it a try and port the FrontPage module to it. > I started the port to Apache v1.3b6 today, and have 4 patches from the apache-fp v1.26e port to still apply. Also, I'll need to look at the changes made by the fp-patch-apache_1.2.5 and apply them. Currently, the port isn't available to down load, but if you would like to have a look at the current state, you can view it on the web at: v1.3b6 http://www.westbend.net/~hetzels/apache-fp/apache-fp-cur.13b6 v1.2.6.e http://www.westbend.net/~hetzels/apache-fp/apache-fp.126.e Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 18:42:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11370 for freebsd-isp-outgoing; Tue, 19 May 1998 18:42:01 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from divre5.telkom.co.id ([202.134.0.55]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA11320; Tue, 19 May 1998 18:41:51 -0700 (PDT) (envelope-from sandy@divre5.telkom.co.id) Received: from dial-up by divre5.telkom.co.id (SMI-8.6/SMI-SVR4) id HAA12217; Wed, 20 May 1998 07:26:52 -0700 Message-ID: <017f01bd8386$9220a070$7305600a@dial-up.divre5.net> From: "Arisandy" To: "Question" , "Isp" Subject: Thanks....all Date: Wed, 20 May 1998 07:31:01 +0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My ppp on demand runs well now...... The problem..is....when I set /etc/rc.conf defaultroute=NO...it run before it, I set to my existing gateway :) thanks everyone ]:)......... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 20:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28634 for freebsd-isp-outgoing; Tue, 19 May 1998 20:25:02 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28619 for ; Tue, 19 May 1998 20:24:58 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id WAA04373 for ; Tue, 19 May 1998 22:24:56 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <00ec01bd839e$dd04e980$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: FnPage98 with Apache V1.3b6 Date: Tue, 19 May 1998 22:24:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Scot W. Hetzel >From: Scot W. Hetzel >>Apache v1.2.6. Since there is a apache-current port (v1.3b6), I guess I'll >>have to give it a try and port the FrontPage module to it. >> >I started the port to Apache v1.3b6 today, and have 4 patches from the >apache-fp v1.26e port to still apply. Also, I'll need to look at the >changes made by the fp-patch-apache_1.2.5 and apply them. > >Currently, the port isn't available to down load, but if you would like to >have a look at the current state, you can view it on the web at: > >v1.3b6 http://www.westbend.net/~hetzels/apache-fp/apache-fp-cur.13b6 > >v1.2.6.e http://www.westbend.net/~hetzels/apache-fp/apache-fp.126.e > I have completed moving all the patches over to 1.3b6, currently the port has not been compiled or tested. If anyone would like to try the port out, it is available at: http://www.westbend.net/~hetzels/apache-fp/apache-fp-cur.13b6.tgz Let me know of any problems with the port. Thanks, Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 23:37:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26877 for freebsd-isp-outgoing; Tue, 19 May 1998 23:37:32 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from divre5.telkom.co.id ([202.134.0.55]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA26851; Tue, 19 May 1998 23:37:14 -0700 (PDT) (envelope-from sandy@divre5.telkom.co.id) Received: from dial-up by divre5.telkom.co.id (SMI-8.6/SMI-SVR4) id NAA15323; Wed, 20 May 1998 13:28:14 -0700 Message-ID: <001601bd83b9$0e129850$7305600a@dial-up.divre5.net> From: "Arisandy" To: "Question" , "Isp" Subject: slow ppp? Date: Wed, 20 May 1998 13:32:24 +0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just reinstall my FreeBSD 2.2.6 I change my modem into Hayes 33.6 before it 28.8 I run ppp it runs....very slow.....it takes 5 minutes :( I upgrade it with ppp980424 still the same ? whats wrong ?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 19 23:46:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28483 for freebsd-isp-outgoing; Tue, 19 May 1998 23:46:15 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from divre5.telkom.co.id ([202.134.0.55]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA28353; Tue, 19 May 1998 23:45:50 -0700 (PDT) (envelope-from sandy@divre5.telkom.co.id) Received: from dial-up by divre5.telkom.co.id (SMI-8.6/SMI-SVR4) id NAA15395; Wed, 20 May 1998 13:36:55 -0700 Message-ID: <002501bd83ba$473d3030$7305600a@dial-up.divre5.net> From: "Arisandy" To: "Question" , "Isp" Subject: Modem speed? Date: Wed, 20 May 1998 13:41:04 +0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How can I know the modem speed while connections happens ? thanks, <----, Arisandy <----|======================= <----' sandy@divre5.telkom.co.id To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 06:53:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06943 for freebsd-isp-outgoing; Wed, 20 May 1998 06:53:49 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from fenchurch.k2net.co.uk (fenchurch.k2net.co.uk [194.164.132.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06934 for ; Wed, 20 May 1998 06:53:45 -0700 (PDT) (envelope-from andy@catherine.k2net.co.uk) Received: from catherine.k2net.co.uk (andy@catherine.k2net.co.uk [194.164.132.90]) by fenchurch.k2net.co.uk (8.8.8/8.8.8) with ESMTP id OAA29346 for ; Wed, 20 May 1998 14:55:26 +0100 (BST) Received: (from andy@localhost) by catherine.k2net.co.uk (8.8.8/8.8.8) id OAA16339 for freebsd-isp@freebsd.org; Wed, 20 May 1998 14:58:26 +0100 (BST) From: Andy Kirkham Message-Id: <199805201358.OAA16339@catherine.k2net.co.uk> Subject: Popper To: freebsd-isp@FreeBSD.ORG Date: Wed, 20 May 1998 14:58:26 +0100 (BST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all Popper question for the more knowledgable. I recently used the bulletin feature. It worked ok (bar a couple of jammed mailboxes). However, after reading the man pages it states that it creates a file in the users home directory called .popbull Well, I can find no such files in any of my users home directories. Popper has, however, only sent the message once (as expected). So where does popper store this info? Also, although it generally worked, the first attepmt to access the mail box fails and popper exited siganl 11. The second and subsequent access go ok. Andy K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 10:41:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09386 for freebsd-isp-outgoing; Wed, 20 May 1998 10:41:14 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09352; Wed, 20 May 1998 10:41:09 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id MAA06033; Wed, 20 May 1998 12:41:07 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <000501bd8416$787c4940$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "FreeBSD-Ports" , "FreeBSD-ISP" Subject: Apache v1.3b6 w/FrontPage Module Date: Wed, 20 May 1998 12:41:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just completed porting the FrontPage Module to work on Apache v1.3b6. The only question I have is where do you set SERVER_SUBVERSION. I tried setting it in ../src/main/Makefile.tmpl, but that didn't work. FrontPage Explorer shows "Server Version" as "Apache/1.3b6", and not as "Apache/1.3b6 FrontPage/3.0.4". The port is available only at: http://www.westbend.net/~hetzels/apach-fp/apache-fp.13b6.tgz Scot W. Hetzel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 10:57:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12370 for freebsd-isp-outgoing; Wed, 20 May 1998 10:57:21 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12356; Wed, 20 May 1998 10:57:14 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA112; Wed, 20 May 1998 19:55:10 +0200 Message-ID: <35631936.FAD649B0@pipeline.ch> Date: Wed, 20 May 1998 19:56:06 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: "Scot W. Hetzel" CC: FreeBSD-Ports , FreeBSD-ISP Subject: Re: Apache v1.3b6 w/FrontPage Module References: <000501bd8416$787c4940$c3e0d9cf@admin.westbend.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Scot W. Hetzel wrote: > > I just completed porting the FrontPage Module to work on Apache v1.3b6. The > only question I have is where do you set SERVER_SUBVERSION. I tried setting > it in ../src/main/Makefile.tmpl, but that didn't work. FrontPage Explorer > shows "Server Version" as "Apache/1.3b6", and not as "Apache/1.3b6 > FrontPage/3.0.4". There has changed somthing in 1.3b6. You might take a look into Apache- week.com. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 11:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19220 for freebsd-isp-outgoing; Wed, 20 May 1998 11:25:43 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from Rigel.orionsys.com (rigel.orionsys.com [205.148.224.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19179 for ; Wed, 20 May 1998 11:25:32 -0700 (PDT) (envelope-from dbabler@Rigel.orionsys.com) Received: from localhost (dbabler@localhost) by Rigel.orionsys.com (8.8.8/8.8.8) with SMTP id LAA07640 for ; Wed, 20 May 1998 11:25:28 -0700 (PDT) (envelope-from dbabler@Rigel.orionsys.com) Date: Wed, 20 May 1998 11:25:27 -0700 (PDT) From: David Babler To: freebsd-isp@FreeBSD.ORG Subject: M$ Personal Web Server vs PPP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a dedicated line customer who is having some problems and I thought I'd throw it on the table here to see if it sounds familiar to anyone else. I am running user PPP for this customer and he is connecting his Windows 95 machine running the Micro$oft Personal Web Server. He connects fine but after some indeterminate period of time, anywhere from 6-8 hours to a week, his server becomes very slow. When he's up and running normally, ping times are around 200ms (31.2k modem connection, on average) but when this condition starts, delays can be up to 9 seconds. Actually, what happens is that if you ping him, there will be no replies at all for around 8 seconds, then all of the accumulated pings are returned at once (in sequence), so you see ping times of 8,7,6,5,4,3,2 and 1 second and then the whole pause/return sequence repeats. When you actually try to download his web contents, you get a long initial delay, then a couple of hundred bytes transfer and another long wait (10-20 seconds), then a little more and so on. The modem is external, so when I ping him, I do see the outbound activity in sync with the stdout, so I have pretty much ruled out a problem on this end with PPP. It looks to me like his W95 box runs some application that produces a serious memory leak, forcing it to start swapping more and more, but I can't confirm that. When the user reboots and reconnects, everything is back to normal until the next time. My only "fix" for him is to run a cron job that pings him every 15 minutes and then email him when I see the response times go up. Anybody else seen this sort of behavior? Thanks! -Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 12:04:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29274 for freebsd-isp-outgoing; Wed, 20 May 1998 12:04:06 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from smtp.triax.com (smtp.triax.com [206.58.96.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29135 for ; Wed, 20 May 1998 12:03:14 -0700 (PDT) (envelope-from joer@triax.com) Received: from joe.triax.com (joe.triax.com [206.58.97.69]) by smtp.triax.com (8.9.0.Beta5/8.9.0.Beta5) with SMTP id MAA07480 for ; Wed, 20 May 1998 12:03:09 -0700 (PDT) Message-Id: <199805201903.MAA07480@smtp.triax.com> X-Sender: joer@mail.triax.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 20 May 1998 12:06:31 -0700 To: isp@FreeBSD.ORG From: Joe Read Subject: FreeBSD firewall Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Everyone, I'm trying to set up a simple little packet blocker box using two nics, once of which uses a crossover cable to the router, another which goes to our hub. I can't seem to route packets between the two, currently I can't tell you why since I plugged the router straight back into the hub to resume company productivity. :) Here's the setup I was trying: Subnet routed to us: 206.58.97.64/26 ed0 (crossover cable to router eth1 port) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 12:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00625 for freebsd-isp-outgoing; Wed, 20 May 1998 12:08:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from smtp.triax.com (smtp.triax.com [206.58.96.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00446 for ; Wed, 20 May 1998 12:08:07 -0700 (PDT) (envelope-from joer@triax.com) Received: from joe.triax.com (joe.triax.com [206.58.97.69]) by smtp.triax.com (8.9.0.Beta5/8.9.0.Beta5) with SMTP id MAA07730 for ; Wed, 20 May 1998 12:08:05 -0700 (PDT) Message-Id: <199805201908.MAA07730@smtp.triax.com> X-Sender: joer@mail.triax.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 20 May 1998 12:11:28 -0700 To: isp@FreeBSD.ORG From: Joe Read Subject: FreeBSD firewall Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (Ack, pine is not eudora. ctrl-e does NOT go to end of line.) Hello Everyone, I'm trying to set up a simple little packet blocker box using two nics, once of which uses a crossover cable to the router, another which goes to our hub. I can't seem to route packets between the two, currently I can't tell you why since I plugged the router straight back into the hub to resume company productivity. :) Here's the setup I was trying: Subnet routed to us: 206.58.97.64/26 Router eth1 IP address: 206.58.97.65 ed0 (crossover cable to router eth1 port): ifconfig ed0 206.58.97.66 netmask 255.255.255.192 route add -host 206.58.97.65 -interface ed0 route add -net default 0.0.0.0 206.58.97.65 ed1 (lan connection): ifconfig ed1 206.58.97.89 netmask 255.255.255.192 route add -net 206.58.97.64 255.255.255.192 206.58.97.66 When the internal 95 boxes set their gateway to 97.89, nothing happens. On the freebsd box I can ping 97.65, but I can't ping any of the 95 boxes. I assume my routing's correct, but I could be wrong. Ideas? Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 13:59:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24926 for freebsd-isp-outgoing; Wed, 20 May 1998 13:59:41 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24794; Wed, 20 May 1998 13:59:10 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id NAA29012; Wed, 20 May 1998 13:58:51 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 20 May 1998 13:58:51 -0700 (PDT) From: Doug White Reply-To: Doug White To: Arisandy cc: Question , Isp Subject: Re: slow ppp? In-Reply-To: <001601bd83b9$0e129850$7305600a@dial-up.divre5.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 20 May 1998, Arisandy wrote: > I just reinstall my FreeBSD 2.2.6 > I change my modem into Hayes 33.6 before it 28.8 > I run ppp it runs....very slow.....it takes 5 minutes :( huh? Please be very specific. Check that nameservice is working correctly. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 14:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25050 for freebsd-isp-outgoing; Wed, 20 May 1998 14:00:08 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24914; Wed, 20 May 1998 13:59:35 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id NAA29016; Wed, 20 May 1998 13:59:29 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 20 May 1998 13:59:29 -0700 (PDT) From: Doug White Reply-To: Doug White To: Arisandy cc: Question , Isp Subject: Re: Modem speed? In-Reply-To: <002501bd83ba$473d3030$7305600a@dial-up.divre5.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 20 May 1998, Arisandy wrote: > How can I know the modem speed while connections happens ? You don't, at least easily -- you have to have a way of grabbing the CONNECT string and usermode ppp can't do that at current (afaik). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 17:42:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05052 for freebsd-isp-outgoing; Wed, 20 May 1998 17:42:32 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04944 for ; Wed, 20 May 1998 17:41:40 -0700 (PDT) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.6/8.6.9) with SMTP id UAA00582; Wed, 20 May 1998 20:41:08 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: ak@k2net.co.uk (Andy Kirkham) Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Popper Date: Thu, 21 May 1998 00:43:21 GMT Message-ID: <356377ff.132754821@mail.sentex.net> References: <199805201358.OAA16339@catherine.k2net.co.uk> In-Reply-To: <199805201358.OAA16339@catherine.k2net.co.uk> X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 20 May 1998 14:58:26 +0100 (BST), in sentex.lists.freebsd.misc you wrote: > >only sent the message once (as expected). So >where does popper store this info? >Also, although it generally worked, the first >attepmt to access the mail box fails and popper >exited siganl 11. The second and subsequent access Hmmm.. Turn on debugging and add local0.* /var/log/popper (if you havent already) and see if there is anything in there. Qualcom's popper should create a .popbull in the user's home directory, although the newer version might create a master .db file somewhere... I recall hearing something about it a long time ago. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 20:09:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00895 for freebsd-isp-outgoing; Wed, 20 May 1998 20:09:27 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00749; Wed, 20 May 1998 20:08:20 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt1-226.HiWAAY.net [208.147.147.226]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id WAA24327; Wed, 20 May 1998 22:08:11 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id WAA03076; Wed, 20 May 1998 22:08:10 -0500 (CDT) Message-Id: <199805210308.WAA03076@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Arisandy , Question , Isp From: David Kelly Subject: Re: Modem speed? In-reply-to: Message from Doug White of "Wed, 20 May 1998 13:59:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 May 1998 22:08:10 -0500 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug White writes: > On Wed, 20 May 1998, Arisandy wrote: > > > How can I know the modem speed while connections happens ? > > You don't, at least easily -- you have to have a way of grabbing the > CONNECT string and usermode ppp can't do that at current (afaik). You could buy a SupraSonic with a 2-line LCD on the front. Then you'd know the rate you *connect* at is rarely the same speed you use a few minutes later. Am currently transmitting at 24.0k and receiving at 28.8k. Connection was negotiated at 31.?k for receive. Often I get 26.4k for transmit, but not tonight. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 21:30:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15024 for freebsd-isp-outgoing; Wed, 20 May 1998 21:30:03 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14873 for ; Wed, 20 May 1998 21:29:12 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.0.Beta3/8.9.0.Beta3) with SMTP id AAA09596; Thu, 21 May 1998 00:28:56 -0400 (EDT) Date: Thu, 21 May 1998 00:28:56 -0400 (EDT) From: jack To: David Babler cc: isp@FreeBSD.ORG Subject: Re: M$ Personal Web Server vs PPP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 20 May 1998, David Babler wrote: > I have a dedicated line customer who is having some problems and I thought > I'd throw it on the table here to see if it sounds familiar to anyone > else. > > I am running user PPP for this customer and he is connecting his Windows > 95 machine running the Micro$oft Personal Web Server. He connects fine but > after some indeterminate period of time, anywhere from 6-8 hours to a > week, his server becomes very slow. [snip] > The modem is external, so when I ping him, I do see the outbound activity > in sync with the stdout, so I have pretty much ruled out a problem on this > end with PPP. It looks to me like his W95 box runs some application that > produces a serious memory leak, forcing it to start swapping more and > more, but I can't confirm that. When the user reboots and reconnects, > everything is back to normal until the next time. My only "fix" for him is > to run a cron job that pings him every 15 minutes and then email him when > I see the response times go up. > > Anybody else seen this sort of behavior? If the customer is competent, you could check for memory leaks by having the customer set a amall fixed size for the swap file, rebooting, setting Win95 to manage swap, rebooting and have him watch the size of the swap file. Don't forget, Win95's TCP/IP stack sucks so bad it could suck the World Trade Towers through a garden hose. We've managed to train most of our users that when they start seeing bad net performance, `no DNS entry' response for known good sites, can't log on, etc., to reboot and try again before calling for tech support. Most of the time the reboot solves their problem. He may just have to reboot periodically, (that shouldn't be a foreign concept to a Windows user :}) or run a real OS. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null Mail from netcom.com blocked until they stop relaying SPAM -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 21:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18492 for freebsd-isp-outgoing; Wed, 20 May 1998 21:46:04 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mindcrime.termfrost.org (mindcrime.termfrost.org [208.141.2.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18368; Wed, 20 May 1998 21:45:23 -0700 (PDT) (envelope-from mandrews@termfrost.org) Received: from localhost (mandrews@localhost) by mindcrime.termfrost.org (8.8.8/8.8.8/mindcrime-19980218) with SMTP id AAA21394; Thu, 21 May 1998 00:44:29 -0400 (EDT) (envelope-from mandrews@termfrost.org) Date: Thu, 21 May 1998 00:44:29 -0400 (EDT) From: Mike Andrews To: David Kelly cc: Arisandy , Question , Isp Subject: Re: Modem speed? In-Reply-To: <199805210308.WAA03076@nospam.hiwaay.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On USR (now 3com) modems, doing +++ followed by ATI6 will tell you, but of course that's only helpful for a terminal session and doesn't help you for a PPP session... :) If you have Total Control hubs, you can get the ATI6 info out-of-band via SNMP. Portmaster 3's I think have something similar. But that's all on the server end. Other than that, or buying a modem with an LCD display as mentioned, there's not really any good way. Mike Andrews/MA12/ICQ 6602506 this chromosome intentionally left blank mandrews@dcr.net -- mandrews@termfrost.org -- http://www.termfrost.org/ Senior Systems & Network Administrator, Digital Crescent, Frankfort, KY v.90/x2/ISDN 'net Access in Franklin/Anderson/Shelby/Jefferson Counties On Wed, 20 May 1998, David Kelly wrote: > Doug White writes: > > On Wed, 20 May 1998, Arisandy wrote: > > > > > How can I know the modem speed while connections happens ? > > > > You don't, at least easily -- you have to have a way of grabbing the > > CONNECT string and usermode ppp can't do that at current (afaik). > > You could buy a SupraSonic with a 2-line LCD on the front. Then you'd > know the rate you *connect* at is rarely the same speed you use a few > minutes later. Am currently transmitting at 24.0k and receiving at > 28.8k. Connection was negotiated at 31.?k for receive. Often I get > 26.4k for transmit, but not tonight. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 20 23:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08029 for freebsd-isp-outgoing; Wed, 20 May 1998 23:42:23 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from agora.rdrop.com (0@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08012 for ; Wed, 20 May 1998 23:42:18 -0700 (PDT) (envelope-from batie@agora.rdrop.com) Received: (from batie@localhost) by agora.rdrop.com (8.8.5/8.8.5) id XAA04008; Wed, 20 May 1998 23:42:16 -0700 (PDT) Message-ID: <19980520234216.35613@rdrop.com> Date: Wed, 20 May 1998 23:42:16 -0700 From: Alan Batie To: freebsd-isp@FreeBSD.ORG Subject: very strange nameserver problem Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="tThc/1wpZn/ma/RB" X-Mailer: Mutt 0.88 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii I've got two virtual domains here; one is a clone of the other and the first one works and the second one gives "server failed". I even used this as an excuse to upgrade to 8.1.2, and it acts exactly the same way. Here are the two zone files: lubed.com is the one that works and val-med.com is the one that doesn't: ; ; Resource records for 'lubed.com' domain ; Contact: Littlejohn Keogh, lemon@agora.rdrop.com ; ; NOTE: Do NOT forget to update the serial number when updating this file! ; $ORIGIN lubed.com. @ IN SOA ns.rdrop.com. batie.rdrop.com. ( 97060501 ; Serial 7200 ; Refresh 600 ; Retry 3600000 ; Expire 14400 ) ; Minimum IN NS ns.rdrop.com. IN NS satisfied.apocalypse.org. IN MX 10 agora.rdrop.com. www IN A 199.2.212.146 ; ; Resource records for 'val-med.com' domain ; Contact: Littlejohn Keogh, lemon@agora.rdrop.com ; ; NOTE: Do NOT forget to update the serial number when updating this file! ; $ORIGIN val-med.com. @ IN SOA ns.rdrop.com. batie.rdrop.com. ( 98052002 ; Serial 7200 ; Refresh 600 ; Retry 3600000 ; Expire 14400 ) ; Minimum IN NS ns.rdrop.com. IN NS satisfied.apocalypse.org. IN MX 10 agora.rdrop.com. www IN A 199.2.212.162 -- Alan Batie ______ www.rdrop.com/users/batie Me batie@agora.rdrop.com \ / www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A \ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ www.anti-spam.net NO SPAM! --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNWPMx4v4wNua7QglAQE40AP+KegPDdMOFlMgJuiIDmaDs5jWuYo01Idp wKygEZrDS2v/XHZlxiwv1Ba3y8SDpXaG0xRvJu1YogtO7tRDgEAopF7qlJzSH9cj EAEvnJhqh9CWurdfQsH8llLEAj+L0Sq7O1s5gKpslejLpxpElzX8iX4kOQUv8mjK lRSWxtY3Hdg= =vgBy -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 00:45:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18174 for freebsd-isp-outgoing; Thu, 21 May 1998 00:45:17 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from support.euronet.nl (support.euronet.nl [194.134.32.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18158 for ; Thu, 21 May 1998 00:45:10 -0700 (PDT) (envelope-from sake@euronet.nl) Received: (from sake@localhost) by support.euronet.nl (8.8.5/8.6.12) id JAA00412; Thu, 21 May 1998 09:44:32 +0200 (CEST) From: Sake Blok Message-Id: <199805210744.JAA00412@support.euronet.nl> Subject: Re: FreeBSD firewall In-Reply-To: <199805201908.MAA07730@smtp.triax.com> from Joe Read at "May 20, 98 12:11:28 pm" To: joer@triax.com (Joe Read) Date: Thu, 21 May 1998 09:44:32 +0200 (CEST) Cc: isp@FreeBSD.ORG Reply-To: sake@nl.euro.net X-URL: http://www.euronet.nl/~sake/ X-quote: Experience is what you get when you were expecting something else. X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm trying to set up a simple little packet blocker box using two nics, > once of which uses a crossover cable to the router, another which goes > to our hub. I can't seem to route packets between the two, currently > I can't tell you why since I plugged the router straight back into the > hub to resume company productivity. :) > > Here's the setup I was trying: > > Subnet routed to us: 206.58.97.64/26 > Router eth1 IP address: 206.58.97.65 > > ed0 (crossover cable to router eth1 port): > ifconfig ed0 206.58.97.66 netmask 255.255.255.192 > route add -host 206.58.97.65 -interface ed0 > route add -net default 0.0.0.0 206.58.97.65 > > ed1 (lan connection): > ifconfig ed1 206.58.97.89 netmask 255.255.255.192 > route add -net 206.58.97.64 255.255.255.192 206.58.97.66 The netmask is used to determine whether a host is on the same physical network. Since you are splitting up your network into two physical networks, you also must split up your IP-range into two (smaller) subnets. Or better, ask for a /30 IP-range for your router and the ed0-interface. Sake P.S. Depending on the router you can also set up the packet-dropping on the router and have it log it's data to your freebsd-host -- Sake Blok * * EuroNet Internet * * Herengracht 208 - 214 * 1016 BS Amsterdam E-mail: sake@nl.euro.net * Tel: +31 20 535 55 55 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 01:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24597 for freebsd-isp-outgoing; Thu, 21 May 1998 01:29:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24591 for ; Thu, 21 May 1998 01:29:54 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id BAA22854; Thu, 21 May 1998 01:29:50 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <3563E5FD.49504753@san.rr.com> Date: Thu, 21 May 1998 01:29:49 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: Alan Batie CC: freebsd-isp@FreeBSD.ORG Subject: Re: very strange nameserver problem References: <19980520234216.35613@rdrop.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alan Batie wrote: > > I've got two virtual domains here; one is a clone of the other and the > first one works and the second one gives "server failed". I even used > this as an excuse to upgrade to 8.1.2, and it acts exactly the same way. > > Here are the two zone files: I don't see anything obviously wrong with the zone files. Are you watching the named.log when you reload the nameserver to see if it's giving you errors? I suspect an error in named.conf. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of one of the world's largest *** Internet Relay Chat server with 5,328 simultaneous connections *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 06:40:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09341 for freebsd-isp-outgoing; Thu, 21 May 1998 06:40:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09270 for ; Thu, 21 May 1998 06:40:00 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id IAA08757; Thu, 21 May 1998 08:39:55 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <003501bd84bd$f0ca0a20$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "Joe Read" Cc: Subject: Re: FreeBSD firewall Date: Thu, 21 May 1998 08:39:55 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Joe Read >(Ack, pine is not eudora. ctrl-e does NOT go to end of line.) > >Hello Everyone, > >I'm trying to set up a simple little packet blocker box using two nics, >once of which uses a crossover cable to the router, another which goes >to our hub. I can't seem to route packets between the two, currently >I can't tell you why since I plugged the router straight back into the >hub to resume company productivity. :) > >When the internal 95 boxes set their gateway to 97.89, >nothing happens. On the freebsd box I can ping 97.65, >but I can't ping any of the 95 boxes. I assume my >routing's correct, but I could be wrong. > In your rc.conf have you set the following: ### Network routing options: ### defaultrouter="206.58.97.66 " # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave empty). gateway_enable="YES" # Set to YES if this host will be a gateway. router_enable="YES" # Set to YES to enable a routing daemon. router="routed" # Name of routing daemon to use if enabled. router_flags="-q" # Flags for routing daemon. With out the above settings, the FreeBSD box will not know where to send packets. Also, as someone already pointed out, you may need to subnet you network. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 08:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27369 for freebsd-isp-outgoing; Thu, 21 May 1998 08:47:18 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from rfcnet.com (rfcnet.com [207.227.20.207]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27348 for ; Thu, 21 May 1998 08:47:15 -0700 (PDT) (envelope-from mattc@rfcnet.com) Received: (from mattc@localhost) by rfcnet.com (8.8.8/8.8.8) id KAA03795; Thu, 21 May 1998 10:46:27 -0500 (CDT) (envelope-from mattc) Message-ID: <19980521104627.A3204@rfcnet.com> Date: Thu, 21 May 1998 10:46:27 -0500 From: Matthew Cashdollar To: David Babler , freebsd-isp@FreeBSD.ORG Subject: Re: M$ Personal Web Server vs PPP References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from David Babler on Wed, May 20, 1998 at 11:25:27AM -0700 x-no-archive: yes Organization: RF Communications, Inc. http://www.rfcinc.com Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 20, 1998 at 11:25:27AM -0700, David Babler wrote: > > The modem is external, so when I ping him, I do see the outbound activity > in sync with the stdout, so I have pretty much ruled out a problem on this > end with PPP. It looks to me like his W95 box runs some application that > produces a serious memory leak, forcing it to start swapping more and > more, but I can't confirm that. When the user reboots and reconnects, > everything is back to normal until the next time. My only "fix" for him is > to run a cron job that pings him every 15 minutes and then email him when > I see the response times go up. There is a memory leak in the Windows 95 kernel involving programs that listen for incoming connections.. it is only a problem in older versions though (not in OSR2 or whatever). There are patches on www.microsoft.com somewhere.. -- Matthew Cashdollar RF Communications, Inc. -- http://www.rfcinc.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 09:25:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03074 for freebsd-isp-outgoing; Thu, 21 May 1998 09:25:49 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from agora.rdrop.com (0@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03054 for ; Thu, 21 May 1998 09:25:44 -0700 (PDT) (envelope-from batie@agora.rdrop.com) Received: (from batie@localhost) by agora.rdrop.com (8.8.5/8.8.5) id JAA02387; Thu, 21 May 1998 09:25:41 -0700 (PDT) Message-ID: <19980521092540.63599@rdrop.com> Date: Thu, 21 May 1998 09:25:40 -0700 From: Alan Batie To: Studded Cc: freebsd-isp@FreeBSD.ORG Subject: Re: very strange nameserver problem References: <19980520234216.35613@rdrop.com> <3563E5FD.49504753@san.rr.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=kGyHlBMXGt3Le3O1 X-Mailer: Mutt 0.88 In-Reply-To: <3563E5FD.49504753@san.rr.com>; from Studded on Thu, May 21, 1998 at 01:29:49AM -0700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --kGyHlBMXGt3Le3O1 Content-Type: text/plain; charset=us-ascii On Thu, May 21, 1998 at 01:29:49AM -0700, Studded wrote: > I don't see anything obviously wrong with the zone files. Are you > watching the named.log when you reload the nameserver to see if it's > giving you errors? I suspect an error in named.conf. I'm using named.conf as converted by the script with default logging. Nothing is turning up in syslog and there's no named.log. // generated by named-bootconf.pl options { directory "/etc/namedb"; listen-on { 199.2.210.241; 199.2.212.241; }; /* * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * directive below. Previous versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; }; // Template named.boot file for Primary NameServer // type domain file zone "." { type hint; file "named.ca"; }; zone "0.0.127.in-addr.arpa" { type master; file "named.local"; }; // Forward mappings for primary (2nd-level) domain zone "rdrop.com" { type master; file "zone/rdrop.com"; }; zone "placo.com" { type master; file "zone/placo.com"; }; zone "coredump.com" { type master; file "zone/coredump.com"; }; zone "sunlab.com" { type master; file "zone/sunlab.com"; }; zone "asian.com" { type master; file "zone/asian.com"; }; zone "interstage.com" { type master; file "zone/interstage.com"; }; zone "aha4kids.com" { type master; file "zone/aha4kids.com"; }; zone "davinci-framing.com" { type master; file "zone/davinci-framing.com"; }; zone "3e.org" { type master; file "zone/3e.org"; }; zone "dirtroad.com" { type master; file "zone/dirtroad.com"; }; zone "elemental.com" { type master; file "zone/elemental.com"; }; zone "highiq.com" { type master; file "zone/highiq.com"; }; zone "aboutgirls.com" { type master; file "zone/aboutgirls.com"; }; zone "aboutguys.com" { type master; file "zone/aboutguys.com"; }; zone "ambizcom.com" { type master; file "zone/ambizcom.com"; }; // primary intercultural.org zone/intercultural.org zone "ahealthyassociation.com" { type master; file "zone/ahealthyassociation.com"; }; zone "lghtspd.com" { type master; file "zone/lghtspd.com"; }; zone "grinningcarrot.com" { type master; file "zone/grinningcarrot.com"; }; zone "northwestfishing.com" { type master; file "zone/northwestfishing.com"; }; zone "eventzone.com" { type master; file "zone/eventzone.com"; }; zone "businessid.com" { type master; file "zone/businessid.com"; }; zone "teamaware.com" { type master; file "zone/teamaware.com"; }; zone "pdxs.com" { type master; file "zone/pdxs.com"; }; zone "atomicad.com" { type master; file "zone/atomicad.com"; }; zone "periodic.com" { type master; file "zone/periodic.com"; }; zone "berrybot.org" { type master; file "zone/berrybot.org"; }; zone "wildheart.org" { type master; file "zone/wildheart.org"; }; zone "nlgcdc.org" { type master; file "zone/nlgcdc.org"; }; zone "lgbt.org" { type master; file "zone/lgbt.org"; }; zone "fastenernews.com" { type master; file "zone/fastenernews.com"; }; zone "semi-retired.com" { type master; file "zone/semi-retired.com"; }; zone "gayportland.com" { type master; file "zone/gayportland.com"; }; zone "lubed.com" { type master; file "zone/lubed.com"; }; zone "empireaviation.com" { type master; file "zone/empireaviation.com"; }; zone "gayseattle.com" { type master; file "zone/gayseattle.com"; }; zone "gayoregon.com" { type master; file "zone/gayoregon.com"; }; zone "capportland.org" { type master; file "zone/capportland.org"; }; zone "variad.com" { type master; file "zone/variad.com"; }; zone "remindmail.com" { type master; file "zone/remindmail.com"; }; zone "maidenmothercrone.com" { type master; file "zone/maidenmothercrone.com"; }; zone "acumaster.com" { type master; file "zone/acumaster.com"; }; zone "moclamp.com" { type master; file "zone/moclamp.com"; }; zone "papamurphy.com" { type master; file "zone/papamurphy.com"; }; zone "visualaspect.com" { type master; file "zone/visualaspect.com"; }; zone "rcw.net" { type master; file "zone/rcw.net"; }; zone "ericdbrown.com" { type master; file "zone/ericdbrown.com"; }; zone "naftc.com" { type master; file "zone/naftc.com"; }; zone "twisty-little-maze.com" { type master; file "zone/twisty-little-maze.com"; }; zone "earthdyn.com" { type master; file "zone/earthdyn.com"; }; zone "concretize.com" { type master; file "zone/concretize.com"; }; zone "autosail.com" { type master; file "zone/autosail.com"; }; zone "dhxadv.com" { type master; file "zone/dhxadv.com"; }; zone "bratlee.com" { type master; file "zone/bratlee.com"; }; zone "kurl.com" { type master; file "zone/kurl.com"; }; zone "windbag.com" { type master; file "zone/windbag.com"; }; zone "dec-pt.com" { type master; file "zone/dec-pt.com"; }; zone "batie.org" { type master; file "zone/batie.org"; }; // Reverse mappings for primary (2nd-level) domain zone "210.2.199.in-addr.arpa" { type master; file "rev/210.2.199.rev"; }; zone "211.2.199.in-addr.arpa" { type master; file "rev/211.2.199.rev"; }; zone "212.2.199.in-addr.arpa" { type master; file "rev/212.2.199.rev"; }; // Load (secondary) off of ns.dev.com zone "dev.com" { type slave; file "zone.sec/dev.com"; masters { 198.145.88.1; }; }; zone "mbw.placo.com" { type slave; file "zone.sec/mbw.placo.com"; masters { 199.2.211.50; }; }; zone "afternet.org" { type slave; file "zone.sec/afternet.org"; masters { 208.149.154.15; }; }; zone "portsoft.com" { type slave; file "zone.sec/portsoft.com"; masters { 208.207.3.226; }; }; zone "auction-software.com" { type slave; file "zone.sec/auction-software.com"; masters { 137.112.203.220; }; }; // Use forwarders only if you can't talk to the Internet directly. // // forwarders 198.145.88.1 -- Alan Batie ______ www.rdrop.com/users/batie Me batie@agora.rdrop.com \ / www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A \ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ www.anti-spam.net NO SPAM! --kGyHlBMXGt3Le3O1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNWRVgYv4wNua7QglAQG96AQAsYuMUXzXM3z7f57tjhw7/0tMKOb+YERH bWDK7a7HvG90jKVcgXS8CrOHT/PRGv/9WVRWw8TV4p63laGWYLD/+3o3pGLwxL4v DlNOLtzqWi8W2LwLj7BDqmfZ9JQ8J+qoe8Q4VO8w74BXktE4pqJgeKy+nmAwdqlk hd08jmNNLjo= =mpgE -----END PGP SIGNATURE----- --kGyHlBMXGt3Le3O1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 09:42:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07108 for freebsd-isp-outgoing; Thu, 21 May 1998 09:42:05 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from value.net (dreed@value.net [204.188.125.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07055 for ; Thu, 21 May 1998 09:42:00 -0700 (PDT) (envelope-from dreed@value.net) Received: from localhost (dreed@localhost) by value.net (8.8.7/8.7.4) with SMTP id JAA17063 for ; Thu, 21 May 1998 09:42:00 -0700 (PDT) Date: Thu, 21 May 1998 09:42:00 -0700 (PDT) From: Damon Reed To: isp@FreeBSD.ORG Subject: Re: FreeBSD firewall In-Reply-To: <199805201908.MAA07730@smtp.triax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 20 May 1998, Joe Read wrote: > I'm trying to set up a simple little packet blocker box using two nics, > once of which uses a crossover cable to the router, another which goes > to our hub. I can't seem to route packets between the two, currently > I can't tell you why since I plugged the router straight back into the > hub to resume company productivity. :) > > Here's the setup I was trying: > > Subnet routed to us: 206.58.97.64/26 > Router eth1 IP address: 206.58.97.65 > > ed0 (crossover cable to router eth1 port): > ifconfig ed0 206.58.97.66 netmask 255.255.255.192 > route add -host 206.58.97.65 -interface ed0 > route add -net default 0.0.0.0 206.58.97.65 > > ed1 (lan connection): > ifconfig ed1 206.58.97.89 netmask 255.255.255.192 > route add -net 206.58.97.64 255.255.255.192 206.58.97.66 > > When the internal 95 boxes set their gateway to 97.89, > nothing happens. On the freebsd box I can ping 97.65, > but I can't ping any of the 95 boxes. I assume my > routing's correct, but I could be wrong. In theory this type of setup would be workable if you applied the right netmasks to the right interfaces (i.e.- The router and firewall shouldn't have the entire 64 addr netmask on their common interface. Otherwise they expect to be able to ARP the Win95 boxes on that segment.), and you set up the routing in the right order; configure all interfaces, set extraneous routes, hope gated doesn't stomp all over them. In practice, I would actually set the ed0-->router interface to a private network address, such as 192.168.1.0/30, like so: (Old timers may freely substitute 10.0.0 for 192.168.1) router:(for the ether if) ip addr 192.168.1.1 255.255.255.252 ip route 206.58.97.65 255.255.255.192 192.168.1.2 firewall: ifconfig ed0 192.168.1.2 netmask 255.255.255.252 ifconfig ed1 206.58.97.65 netmask 255.255.255.192 route add default 192.168.1.1 internal hosts: set addr on available addr in subnet (.66-.126) set def gateway to 206.58.97.65 Since the interface between the router and the firewall is only relevant to those two entities, you can get away with the non-public address without address translation; the router should have a public IP interface (On the WAN interface), and the firewall is reachable via its .65 address from the outside. The static route entry in the router may be extraneous if your routing (routed, gated) on the firewall box is working 100%, but since it's better to be paranoid than disconnected I put it in anyways. Damon Reed *Value Net Internetworking* -Network Administrator- dreed@value.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 10:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20055 for freebsd-isp-outgoing; Thu, 21 May 1998 10:39:28 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20038 for ; Thu, 21 May 1998 10:39:22 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id KAA13366; Thu, 21 May 1998 10:40:50 -0700 (PDT) Date: Thu, 21 May 1998 10:40:50 -0700 (PDT) From: Dan Busarow To: sake@nl.euro.net cc: Joe Read , isp@FreeBSD.ORG Subject: Re: FreeBSD firewall In-Reply-To: <199805210744.JAA00412@support.euronet.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 21 May 1998, Sake Blok wrote: > The netmask is used to determine whether a host is on the same > physical network. Since you are splitting up your network into > two physical networks, you also must split up your IP-range > into two (smaller) subnets. Or better, ask for a /30 IP-range > for your router and the ed0-interface. Just to exand on Sake's post, with your current setup you need to create two /27 subnets. One for your router's eth port and the FreeBSD nic atttached to it. The second for your internal hosts. If you can live with 30 internal hosts that's a viable (though wasteful) solution. And you'll be up in minutes. If you need more internal addresses you need to take his advice on getting a /30 for the router to FBSD connection and using your /26 for the internal hosts. Dan -- Dan Busarow 949 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 10:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23099 for freebsd-isp-outgoing; Thu, 21 May 1998 10:56:57 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23079 for ; Thu, 21 May 1998 10:56:53 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id KAA13468; Thu, 21 May 1998 10:58:20 -0700 (PDT) Date: Thu, 21 May 1998 10:58:20 -0700 (PDT) From: Dan Busarow To: Alan Batie cc: freebsd-isp@FreeBSD.ORG Subject: Re: very strange nameserver problem In-Reply-To: <19980520234216.35613@rdrop.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/SIGNED; PROTOCOL="application/pgp-signature"; MICALG=pgp-md5; BOUNDARY="tThc/1wpZn/ma/RB" Content-ID: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --tThc/1wpZn/ma/RB Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: On Wed, 20 May 1998, Alan Batie wrote: > lubed.com is the one that works and val-med.com is the one that doesn't: The zone file looks fine. What's named.conf look like? Your server does not believe that it's authoritative for val-med.com > val-med.com Server: ns.rdrop.com Address: 199.2.210.241 Non-authoritative answer: val-med.com nameserver = NS.RDROP.COM val-med.com nameserver = SATISFIED.APOCALYPSE.ORG Authoritative answers can be found from: val-med.com nameserver = NS.RDROP.COM val-med.com nameserver = SATISFIED.APOCALYPSE.ORG SATISFIED.APOCALYPSE.ORG internet address = 192.48.232.24 Dan -- Dan Busarow 949 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 11:34:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29327 for freebsd-isp-outgoing; Thu, 21 May 1998 11:34:52 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from agora.rdrop.com (0@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29305 for ; Thu, 21 May 1998 11:34:46 -0700 (PDT) (envelope-from batie@agora.rdrop.com) Received: (from batie@localhost) by agora.rdrop.com (8.8.5/8.8.5) id LAA16841; Thu, 21 May 1998 11:34:42 -0700 (PDT) Message-ID: <19980521113442.29410@rdrop.com> Date: Thu, 21 May 1998 11:34:42 -0700 From: Alan Batie To: Dan Busarow Cc: freebsd-isp@FreeBSD.ORG Subject: Re: very strange nameserver problem References: <19980520234216.35613@rdrop.com> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="k+w/mQv8wyuph6w0" X-Mailer: Mutt 0.88 In-Reply-To: ; from Dan Busarow on Thu, May 21, 1998 at 10:58:20AM -0700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii On Thu, May 21, 1998 at 10:58:20AM -0700, Dan Busarow wrote: > The zone file looks fine. What's named.conf look like? Your > server does not believe that it's authoritative for val-med.com Oh that's soooooo embarrassing. I would have *sworn* it was in ther. Sigh... Never mind... -- Alan Batie ______ www.rdrop.com/users/batie Me batie@agora.rdrop.com \ / www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A \ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ www.anti-spam.net NO SPAM! --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNWRzwYv4wNua7QglAQGAnAP+K6Z8kCKs6vvqIigKHrKKdBEyzOhEizN+ 6MWj97HKmDrfXunimJCuJSMnZBSqeEHYKWILu7BD7VMiSNyp+qzzWRGccJNA+3uV 6iRs//AI8UIQgDk+TTe/4Mv7QvnXdu4L7BZB8HTJzh7rnrLpAklbcLH2D7+8BBXL 5/qYV5w99z8= =OAK+ -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 11:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00547 for freebsd-isp-outgoing; Thu, 21 May 1998 11:39:15 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00528 for ; Thu, 21 May 1998 11:39:04 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA27537; Thu, 21 May 1998 11:38:35 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <356474AB.91CF5BED@san.rr.com> Date: Thu, 21 May 1998 11:38:35 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: Alan Batie CC: freebsd-isp@FreeBSD.ORG Subject: Re: very strange nameserver problem References: <19980520234216.35613@rdrop.com> <3563E5FD.49504753@san.rr.com> <19980521092540.63599@rdrop.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alan Batie wrote: > > On Thu, May 21, 1998 at 01:29:49AM -0700, Studded wrote: > > I don't see anything obviously wrong with the zone files. Are you > > watching the named.log when you reload the nameserver to see if it's > > giving you errors? I suspect an error in named.conf. > > I'm using named.conf as converted by the script with default logging. > Nothing is turning up in syslog and there's no named.log. Ok, then you want to check /var/log/messages. In any case, is it my imagination or is val-med.com not in your named.conf? :) Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of one of the world's largest *** Internet Relay Chat server with 5,328 simultaneous connections *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 16:27:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26427 for freebsd-isp-outgoing; Thu, 21 May 1998 16:27:17 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26124; Thu, 21 May 1998 16:25:33 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA23151; Fri, 22 May 1998 00:12:00 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805212312.AAA23151@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Doug White cc: Arisandy , Question , Isp Subject: Getty & CONNECT environment variable (was: Modem speed?) In-reply-to: Your message of "Wed, 20 May 1998 13:59:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 May 1998 00:12:00 +0100 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Wed, 20 May 1998, Arisandy wrote: > > > How can I know the modem speed while connections happens ? > > You don't, at least easily -- you have to have a way of grabbing the > CONNECT string and usermode ppp can't do that at current (afaik). It's possible to check the log file for outgoing connections. For incoming connections, mgetty (if you're using it) sets the CONNECT environment variable. Ppp picks this up and enters it in the host field of utmp. Maybe it would be work making the stock getty(8) set CONNECT too ? -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 20:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11100 for freebsd-isp-outgoing; Thu, 21 May 1998 20:02:16 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11064; Thu, 21 May 1998 20:02:08 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id XAA23289; Thu, 21 May 1998 23:09:49 -0400 (EDT) (envelope-from mark) Message-ID: <19980521230948.A23199@vmunix.com> Date: Thu, 21 May 1998 23:09:48 -0400 From: Mark Mayo To: isp@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: TIME_WAIT/FIN_WAIT_2... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all.. I have a few questions about large web servers. I've run a few relatively large web sites on freebsd in the past, but none that put out more than 300-400,000 objects per day (html+gif..). I've been looking at a Solaris machine today that's putting out about 2 million pages a day. The somewhat odd thing is the extraordinary number of sockets left open in TIME_WAIT and FIN_WAIT_2. I roughly understand what they mean, but we're talking about 3000 entries here (about 400-500 of which are FIN_WAIT_2, the rest are TIME_WAIT).. So I have ~3000 sockets in TIME_WAIT/FIN and only about 100 ESTABLISHED. Is this normal?? It doesn't seem like it to me. If not, what would be causing it, and what should I look at tuning on the Slowaris box?? TIA for any ideas! All I know is that I just don't trust sockets on Solaris... :-) -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 21:03:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20235 for freebsd-isp-outgoing; Thu, 21 May 1998 21:03:16 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles145.castles.com [208.214.165.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20165; Thu, 21 May 1998 21:03:03 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA06672; Thu, 21 May 1998 19:59:07 -0700 (PDT) Message-Id: <199805220259.TAA06672@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mark Mayo cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TIME_WAIT/FIN_WAIT_2... In-reply-to: Your message of "Thu, 21 May 1998 23:09:48 EDT." <19980521230948.A23199@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 May 1998 19:59:06 -0700 From: Mike Smith Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi all.. I have a few questions about large web servers. I've run a > few relatively large web sites on freebsd in the past, but none that > put out more than 300-400,000 objects per day (html+gif..). I've been > looking at a Solaris machine today that's putting out about 2 million > pages a day. The somewhat odd thing is the extraordinary number of > sockets left open in TIME_WAIT and FIN_WAIT_2. I roughly understand > what they mean, but we're talking about 3000 entries here (about 400-500 > of which are FIN_WAIT_2, the rest are TIME_WAIT).. So I have ~3000 > sockets in TIME_WAIT/FIN and only about 100 ESTABLISHED. > > Is this normal?? It doesn't seem like it to me. If not, what would be > causing it, and what should I look at tuning on the Slowaris box?? You might be able to tune down the closing delay, but in reality I can't see it as a "real" problem unless the number is growing or you are resource-starved because of it. Of course, the "correct" tuning action would be to replace Solaris with FreeBSD. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 21:38:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28176 for freebsd-isp-outgoing; Thu, 21 May 1998 21:38:35 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28014; Thu, 21 May 1998 21:38:05 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA28329; Thu, 21 May 1998 21:37:44 -0700 (PDT) Message-Id: <199805220437.VAA28329@implode.root.com> To: Mark Mayo cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TIME_WAIT/FIN_WAIT_2... In-reply-to: Your message of "Thu, 21 May 1998 23:09:48 EDT." <19980521230948.A23199@vmunix.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 21 May 1998 21:37:44 -0700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi all.. I have a few questions about large web servers. I've run a >few relatively large web sites on freebsd in the past, but none that >put out more than 300-400,000 objects per day (html+gif..). I've been >looking at a Solaris machine today that's putting out about 2 million >pages a day. The somewhat odd thing is the extraordinary number of >sockets left open in TIME_WAIT and FIN_WAIT_2. I roughly understand >what they mean, but we're talking about 3000 entries here (about 400-500 >of which are FIN_WAIT_2, the rest are TIME_WAIT).. So I have ~3000 >sockets in TIME_WAIT/FIN and only about 100 ESTABLISHED. > >Is this normal?? It doesn't seem like it to me. If not, what would be >causing it, and what should I look at tuning on the Slowaris box?? > >TIA for any ideas! All I know is that I just don't trust sockets on >Solaris... :-) It's normal and required by the TCP specification. FreeBSD will do the same thing in the this situation. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 22:15:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04408 for freebsd-isp-outgoing; Thu, 21 May 1998 22:15:15 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from eosnts2.ecc.tased.edu.au (eosnts2.ecc.tased.edu.au [147.41.64.67]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA04391; Thu, 21 May 1998 22:15:08 -0700 (PDT) (envelope-from Joe.Shevland@Central.tased.edu.au) Received: by eosnts2.ecc.tased.edu.au with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BD8594.5508B550@eosnts2.ecc.tased.edu.au>; Fri, 22 May 1998 15:14:36 +1000 Message-ID: From: "Shevland, Joe" To: "'Mark Mayo'" Cc: "'isp@freebsd.org'" , "'hackers@freebsd.org'" Subject: RE: TIME_WAIT/FIN_WAIT_2... Date: Fri, 22 May 1998 15:14:34 +1000 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Scuse any ignorance on these matters, but are the following true statements? (just curious): i) Sockets in a TIME_WAIT state do not have a (an open?) file descriptor associated with them ii) Sockets waiting for a FIN segment or in the FIN_WAIT_2 state do. >> [trimmed] So I have ~3000 >> sockets in TIME_WAIT/FIN and only about 100 ESTABLISHED. >> >> Is this normal?? It doesn't seem like it to me. If not, what would be >> causing it, and what should I look at tuning on the Slowaris box?? > >You might be able to tune down the closing delay, but in reality I >can't see it as a "real" problem unless the number is growing or you >are resource-starved because of it. > >Of course, the "correct" tuning action would be to replace Solaris with >FreeBSD. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 22:15:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04510 for freebsd-isp-outgoing; Thu, 21 May 1998 22:15:30 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA04491 for ; Thu, 21 May 1998 22:15:27 -0700 (PDT) (envelope-from michael@memra.com) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id WAA05996; Thu, 21 May 1998 22:15:19 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.9.0.Beta5/8.9.0.Beta5) with SMTP id WAA11352; Thu, 21 May 1998 22:15:17 -0700 (PDT) Date: Thu, 21 May 1998 22:15:15 -0700 (PDT) From: Michael Dillon To: nanog@merit.edu cc: inet-access@earth.com, linuxisp@friendly.jeffnet.org, freebsd-isp@FreeBSD.ORG Subject: Interweather source code Message-ID: Organization: Memra Communications Inc. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There is an article at the bottom of this page http://www.macosrumors.com/ about a distributed client system to gather standard, accurate statistics about the network. They are considering releasing the source code to this system similar to Netscape's release of Mozilla. -- Michael Dillon - Internet & ISP Consulting Memra Communications Inc. - E-mail: michael@memra.com http://www.memra.com - *check out the new name & new website* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu May 21 23:23:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17303 for freebsd-isp-outgoing; Thu, 21 May 1998 23:23:16 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17296; Thu, 21 May 1998 23:23:15 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id XAA24765; Thu, 21 May 1998 23:23:09 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd024739; Thu May 21 23:23:02 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id XAA11218; Thu, 21 May 1998 23:23:00 -0700 (MST) From: Terry Lambert Message-Id: <199805220623.XAA11218@usr04.primenet.com> Subject: Re: TIME_WAIT/FIN_WAIT_2... To: mark@vmunix.com (Mark Mayo) Date: Fri, 22 May 1998 06:23:00 +0000 (GMT) Cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <19980521230948.A23199@vmunix.com> from "Mark Mayo" at May 21, 98 11:09:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The somewhat odd thing is the extraordinary number of > sockets left open in TIME_WAIT and FIN_WAIT_2. I roughly understand > what they mean, but we're talking about 3000 entries here (about 400-500 > of which are FIN_WAIT_2, the rest are TIME_WAIT).. So I have ~3000 > sockets in TIME_WAIT/FIN and only about 100 ESTABLISHED. > > Is this normal?? It doesn't seem like it to me. If not, what would be > causing it, and what should I look at tuning on the Slowaris box?? This is a client bug, specifically with Windows WinSock clients, which do not call "shutdown(2)" in the following way: shutdown( s, 1); The '1' should be a '2', but many WinSock implementations fail to work correctly if it isn't a '1'. You should talk to Paul Vixie about this. The fix is to be bug-compatible with Windows NT as a server, and to, when you are in FIN_WAIT_2 state, back up to resend the FIN. The problem is the lack of an ACK needed for a state transition in the Windows TCP/IP implemenetation. The root cause is badly written client code that assumes that the system does resource tracking of sockets, such that when the client program exits, a resource-track cleanup occurs, and sockets are shut down correctly. Alternately, you could blame it on Microsoft for writing an OS that doesn't do resource tracking. But you could blame Apple for the same thing. In any case, Paul has hacked NetBSD to do the right thing. I've played with hacks to FreeBSD for the same thing. Basically, it times out and backs up, rememebring that it backed up, and if it gets an abort when the FIN is resent (ie: the machine has rebooted or the host is unreachable because it has disconnected from it's ISP), it needs to rush forward to completion. Obviously, it would have to be controlled via sysctl(2), since it violates the RFC's all to hell. This is a standard Windows "Denial of service to non-Windows OS's" attack. 8-|. FreeBSD pretends it has solved the problem with a timeout (Solaris has a similar "fix"), but the latency is too high. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 05:32:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11292 for freebsd-isp-outgoing; Fri, 22 May 1998 05:32:16 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11276; Fri, 22 May 1998 05:32:12 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id IAA25061; Fri, 22 May 1998 08:40:00 -0400 (EDT) (envelope-from mark) Message-ID: <19980522084000.A25049@vmunix.com> Date: Fri, 22 May 1998 08:40:00 -0400 From: Mark Mayo To: dg@root.com Cc: isp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: TIME_WAIT/FIN_WAIT_2... References: <19980521230948.A23199@vmunix.com> <199805220437.VAA28329@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199805220437.VAA28329@implode.root.com>; from David Greenman on Thu, May 21, 1998 at 09:37:44PM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 21, 1998 at 09:37:44PM -0700, David Greenman wrote: > >pages a day. The somewhat odd thing is the extraordinary number of > >sockets left open in TIME_WAIT and FIN_WAIT_2. I roughly understand > >what they mean, but we're talking about 3000 entries here (about 400-500 > >of which are FIN_WAIT_2, the rest are TIME_WAIT).. So I have ~3000 > >sockets in TIME_WAIT/FIN and only about 100 ESTABLISHED. > > > > It's normal and required by the TCP specification. FreeBSD will do the > same thing in the this situation. Okay. Good to hear. I've never personally seen a FreeBSD machine with such a high WAIT/ESTAB ratio, so I was curious is this was normal under high web traffic. :-) -Mark > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 06:38:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21179 for freebsd-isp-outgoing; Fri, 22 May 1998 06:38:24 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from sun-1.punkt.de (sun-1.punkt.de [194.77.232.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21152; Fri, 22 May 1998 06:38:17 -0700 (PDT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [194.77.233.242]) by sun-1.punkt.de (8.8.8/8.8.5) with ESMTP id PAA09042; Fri, 22 May 1998 15:38:13 +0200 (MET DST) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.8.7/8.8.7) id PAA28604; Fri, 22 May 1998 15:38:11 +0200 (CEST) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <199805221338.PAA28604@hugo10.ka.punkt.de> Subject: Problems connecting to AIX box with PPP To: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Date: Fri, 22 May 1998 15:38:10 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all! I'm trying to connect a FreeBSD 2.2.6 box to a AIX system with user PPP. The AIX box is setup as follows: - there's a user with a regular login - in his .profile there's: "exec /usr/sbin/pppattachd server 2>/dev/null" - the interface config for PPP is: interface server local_ip 10.8.11.240 remote_ip 10.8.11.245 netmask 255.155.155.0 It's AIX version 4.1.5.0 and the above is what the AIX manual suggested. This worked out of the box with Windows 95 as a client. I set up FreeBSD /etc/ppp/ppp.conf like this: default: set device /dev/cuaa0 set speed 19200 disable pred1 deny pred1 disable lqr deny lqr set redial 30 3 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT&FX3 OK-AT-OK \\dATDT\\T TIMEOUT 120 CONNECT" blabla: set log chat lcp ipcp set phone 0w0033387282534 set timeout 300 set openmode active set login "TIMEOUT 30 ogin:-\\r-ogin: blabla ennwort foobar" set ifaddr 10.8.11.245/32 10.8.11.240/32 255.255.255.0 (Don't be fooled by the "ennwort" - this stupid thing asks for the password in German ;-) Now, when I try to use 57600 or 38400 DTE speed, even the login fails. When I use 19200, login, lcp and ipcp seem to work: May 20 14:23:43 poseidon ppp[460]: Phase: Using interface: tun0 May 20 14:23:46 poseidon ppp[461]: Chat: Dial attempt 1 of 3 May 20 14:23:46 poseidon ppp[461]: Chat: Expecting: May 20 14:23:46 poseidon ppp[461]: Chat: Sending: AT&FX3^M May 20 14:23:46 poseidon ppp[461]: Chat: Expecting: OK-AT-OK May 20 14:23:46 poseidon ppp[461]: Chat: Wait for (5): OK May 20 14:23:48 poseidon ppp[461]: Chat: Sending: ATDT0w*************^M May 20 14:23:48 poseidon ppp[461]: Chat: Expecting: CONNECT May 20 14:23:48 poseidon ppp[461]: Chat: Wait for (120): CONNECT May 20 14:24:28 poseidon ppp[461]: Chat: Expecting: ogin:-\r-ogin: May 20 14:24:28 poseidon ppp[461]: Chat: Wait for (30): ogin: May 20 14:24:30 poseidon ppp[461]: Chat: Sending: blabla^M May 20 14:24:30 poseidon ppp[461]: Chat: Expecting: ennwort May 20 14:24:30 poseidon ppp[461]: Chat: Wait for (30): ennwort May 20 14:24:30 poseidon ppp[461]: Chat: Sending: foobar^M May 20 14:24:30 poseidon ppp[461]: LCP: State change Initial --> Closed May 20 14:24:30 poseidon ppp[461]: LCP: State change Closed --> Stopped May 20 14:24:31 poseidon ppp[461]: LCP: Received Configure Request (1) state = Stopped (3) May 20 14:24:31 poseidon ppp[461]: LCP: MRU[4] 1500 May 20 14:24:31 poseidon ppp[461]: LCP: ACCMAP[6] 0x00000000 May 20 14:24:31 poseidon ppp[461]: LCP: MAGICNUM[6] 0x3562ca23 May 20 14:24:31 poseidon ppp[461]: LCP: PROTOCOMP[2] May 20 14:24:31 poseidon ppp[461]: LCP: ACFCOMP[2] May 20 14:24:31 poseidon ppp[461]: LCP: LcpSendConfigReq May 20 14:24:31 poseidon ppp[461]: LCP: ACFCOMP[2] May 20 14:24:31 poseidon ppp[461]: LCP: PROTOCOMP[2] May 20 14:24:31 poseidon ppp[461]: LCP: ACCMAP[6] 0x00000000 May 20 14:24:31 poseidon ppp[461]: LCP: MRU[4] 1500 May 20 14:24:31 poseidon ppp[461]: LCP: MAGICNUM[6] 0x771eba49 May 20 14:24:31 poseidon ppp[461]: LCP: SendConfigAck(Stopped) May 20 14:24:31 poseidon ppp[461]: LCP: MRU[4] 1500 May 20 14:24:31 poseidon ppp[461]: LCP: ACCMAP[6] 0x00000000 May 20 14:24:31 poseidon ppp[461]: LCP: MAGICNUM[6] 0x3562ca23 May 20 14:24:31 poseidon ppp[461]: LCP: PROTOCOMP[2] May 20 14:24:31 poseidon ppp[461]: LCP: ACFCOMP[2] May 20 14:24:31 poseidon ppp[461]: LCP: State change Stopped --> Ack-Sent May 20 14:24:31 poseidon ppp[461]: LCP: Received Configure Ack (1) state = Ack-Sent (8) May 20 14:24:31 poseidon ppp[461]: LCP: State change Ack-Sent --> Opened May 20 14:24:31 poseidon ppp[461]: LCP: LcpLayerUp May 20 14:24:31 poseidon ppp[461]: IPCP: State change Initial --> Closed May 20 14:24:31 poseidon ppp[461]: IPCP: IPCP Up event!! May 20 14:24:31 poseidon ppp[461]: IPCP: IpcpSendConfigReq May 20 14:24:31 poseidon ppp[461]: IPCP: IPADDR[6] 10.8.11.245 May 20 14:24:31 poseidon ppp[461]: IPCP: COMPPROTO[6] 16 VJ slots with slot compres May 20 14:24:31 poseidon ppp[461]: IPCP: State change Closed --> Req-Sent May 20 14:24:31 poseidon ppp[461]: IPCP: Received Configure Request (1) state = Req-Sent (6) May 20 14:24:31 poseidon ppp[461]: IPCP: IPADDR[6] 10.8.11.240 May 20 14:24:31 poseidon ppp[461]: IPCP: COMPPROTO[6] 16 VJ slots with slot compression May 20 14:24:31 poseidon ppp[461]: IPCP: SendConfigAck(Req-Sent) May 20 14:24:31 poseidon ppp[461]: IPCP: IPADDR[6] 10.8.11.240 May 20 14:24:31 poseidon ppp[461]: IPCP: COMPPROTO[6] 16 VJ slots with slot compression May 20 14:24:31 poseidon ppp[461]: IPCP: State change Req-Sent --> Ack-Sent May 20 14:24:31 poseidon ppp[461]: IPCP: Received Configure Ack (1) state = Ack-Sent (8) May 20 14:24:31 poseidon ppp[461]: IPCP: State change Ack-Sent --> Opened May 20 14:24:31 poseidon ppp[461]: IPCP: IpcpLayerUp(9). May 20 14:24:31 poseidon ppp[461]: IPCP: myaddr = 10.8.11.245 hisaddr = 10.8.11.240 May 20 14:24:31 poseidon ppp[461]: LCP: OsLinkup: 10.8.11.240 May 20 14:24:31 poseidon ppp[461]: LCP: Received Protocol Reject (2) state = Opened (9) May 20 14:24:31 poseidon ppp[461]: LCP: -- Protocol (80fd) was rejected. But, when I try to ping, the modem transmit LED flashes, but i don't get an echo back. The admin on the other side isn't too Unix experienced, but from what he told me, his routing table looked OK. The interfaces on both sides seemed to be up, the routes correct - but noone could ping the other end. Any suggestions? Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 09:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20717 for freebsd-isp-outgoing; Fri, 22 May 1998 09:41:55 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20700; Fri, 22 May 1998 09:41:52 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA01914; Fri, 22 May 1998 09:43:04 -0700 (PDT) Date: Fri, 22 May 1998 09:43:04 -0700 (PDT) From: Jim Shankland Message-Id: <199805221643.JAA01914@biggusdiskus.flyingfox.com> To: mark@vmunix.com, tlambert@primenet.com Subject: Re: TIME_WAIT/FIN_WAIT_2... Cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [mark@vmunix.com (Mark Mayo) asks about large numbers of TCP connections in TIME_WAIT and FIN_WAIT_2 states on a busy Web server. Terry Lambert responds: > This is a client bug, specifically with Windows WinSock clients, which > do not call "shutdown(2)" in the following way: > > shutdown( s, 1); > > The '1' should be a '2', but many WinSock implementations fail to work > correctly if it isn't a '1'. > > [...] > > The fix is to be bug-compatible with Windows NT as a server, and to, > when you are in FIN_WAIT_2 state, back up to resend the FIN. > > The problem is the lack of an ACK needed for a state transition in > the Windows TCP/IP implemenetation. Terry, I think you have your TCP states mixed up. First, none of this applies to the TIME_WAIT connections. As for the FIN_WAIT_2 connections: FIN_WAIT_2 means, "I'm done sending, I've sent a FIN, the other side has ACKed my FIN, but the other side has not sent *me* a FIN to indicate that it is done sending." One would then expect the peer to be in CLOSE_WAIT state. This is a perfectly legal state that can persist indefinitely, with the CLOSE_WAIT end sending unbounded amounts of data to the FIN_WAIT_2 end for consumption. Why on earth would you "back up to resend [a] FIN" that has already been ACKed? I suspect what you really mean is that the client side never sends its FIN, even though it's really done sending, leaving the server-side hanging in FIN_WAIT_2 state, waiting for either more data or a close from the client, while the client wll never bother to send either.. This can happen due to application-layer or TCP-layer bugs on the client side, or because the client crashed or was powered off at an inopportune time. What BSD-based TCP stacks do is this: if the FIN_WAIT_2 socket has been closed by the application (i.e., there's no-one there to receive any data that might arrive), and no data arrives for about 11 minutes, then the connection is silently dropped. (Remember, if the FIN_WAIT_2 socket has not been closed, then data could arrive after an arbitrarily long silence, and there's a process there to read that data; so the connection *must not* be dropped.) So what you're really seeing, Mark, is connections in FIN_WAIT_2 state, where the web server has closed the socket, but the client has never indicated that it is done sending. These hang around for about 11 minutes, then disappear. (Of course, more take their place.) The reason for the 11 minute wait is so that if the client is just slow going through its shutdown stuff, the server can still walk the client through an orderly close. On the other hand, maybe 11 minutes is too long? I'll bet nothing terrible happens if that timeout drops to 1 minute ... or 30 seconds. Even 0 would at worst lead to some unnecessary RST's on closing connections. Anyone have any thoughts on this? Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 10:47:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05684 for freebsd-isp-outgoing; Fri, 22 May 1998 10:47:47 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05663; Fri, 22 May 1998 10:47:30 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id NAA26223; Fri, 22 May 1998 13:54:55 -0400 (EDT) (envelope-from mark) Message-ID: <19980522135455.A26169@vmunix.com> Date: Fri, 22 May 1998 13:54:55 -0400 From: Mark Mayo To: Jim Shankland , tlambert@primenet.com Cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: TIME_WAIT/FIN_WAIT_2... References: <199805221643.JAA01914@biggusdiskus.flyingfox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199805221643.JAA01914@biggusdiskus.flyingfox.com>; from Jim Shankland on Fri, May 22, 1998 at 09:43:04AM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 22, 1998 at 09:43:04AM -0700, Jim Shankland wrote: > [mark@vmunix.com (Mark Mayo) asks about large numbers of TCP connections > in TIME_WAIT and FIN_WAIT_2 states on a busy Web server. [in resonse to Terry's post, Jim writes:] > I suspect what you really mean is that the client side never sends its > FIN, even though it's really done sending, leaving the server-side > hanging in FIN_WAIT_2 state, waiting for either more data or a close > from the client, while the client wll never bother to send either.. > This can happen due to application-layer or TCP-layer bugs on the > client side, or because the client crashed or was powered off at an > inopportune time. Or IE 3.01 which just never sends it's FIN under "normal" conditions.. :-) > What BSD-based TCP stacks do is this: if the FIN_WAIT_2 socket has > been closed by the application (i.e., there's no-one there to receive > any data that might arrive), and no data arrives for about 11 minutes, > then the connection is silently dropped. (Remember, if the FIN_WAIT_2 > socket has not been closed, then data could arrive after an arbitrarily > long silence, and there's a process there to read that data; so the > connection *must not* be dropped.) > > So what you're really seeing, Mark, is connections in FIN_WAIT_2 state, > where the web server has closed the socket, but the client has never > indicated that it is done sending. These hang around for about 11 > minutes, then disappear. (Of course, more take their place.) Thanks. I read rfc793.txt which gives the definition. That combined with a review of the Steven's book about TCP closing handshakes brought me to the same conclusions. Very well stated though! Thanks for a super readable explantion. :-) > > The reason for the 11 minute wait is so that if the client is just > slow going through its shutdown stuff, the server can still walk the > client through an orderly close. On the other hand, maybe 11 minutes > is too long? I'll bet nothing terrible happens if that timeout drops > to 1 minute ... or 30 seconds. Even 0 would at worst lead to some > unnecessary RST's on closing connections. Anyone have any thoughts on > this? I'm thinking that setting it to 2MSL, like TIME_WAIT might be okay, and still relatively conservative. 4 minutes is not bad, and on a machine dedicated strictly to http shouldn't have any adverse affects. Anyone else have experience tweaking things like this to squeeze out extra http performance (apache BTW)?? I still think the ratio of TIME_WAIT/FIN_WAIT to ESTABLISHED is high, but apparently that's normal. Like I said, under previous machines I've seen doing fewer transfers, it wasn't nearly as bad.. Although I might not be able to do anything about it, it still irks me. 8-) -Mark > > Jim Shankland > Flying Fox Computer Systems, Inc. -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 11:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16828 for freebsd-isp-outgoing; Fri, 22 May 1998 11:46:00 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from postman.true.net (s1.admin.true.net [161.196.66.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16714; Fri, 22 May 1998 11:45:43 -0700 (PDT) (envelope-from lem@cantv.net) Received: from fwb-1.true.net (fwb-1.true.net [200.11.129.3]) by postman.true.net (8.8.7/8.6.12) with ESMTP id OAA09684; Fri, 22 May 1998 14:44:58 -0400 (VET) Received: from lem.cantv.net (root@localhost) by fwb-1.true.net (8.8.6/8.6.12) with SMTP id OAA14530; Fri, 22 May 1998 14:44:56 -0400 (VET) X-BlackMail: ws-7.chacao-1.cantv.net, lem.cantv.net, lem@cantv.net, 200.44.44.23 X-Authenticated-Timestamp: 14:44:57(VET) on May 22, 1998 Message-Id: <3.0.5.32.19980522144033.00827400@pop.cantv.net> X-Sender: lem@pop.cantv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 22 May 1998 14:40:33 -0400 To: Jim Shankland From: Luis Munoz Subject: Re: TIME_WAIT/FIN_WAIT_2... Cc: mark@vmunix.com, tlambert@primenet.com, hackers@FreeBSD.ORG, isp@FreeBSD.ORG In-Reply-To: <199805221643.JAA01914@biggusdiskus.flyingfox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:43 AM 22/05/1998 -0700, Jim Shankland wrote: [snip] >The reason for the 11 minute wait is so that if the client is just >slow going through its shutdown stuff, the server can still walk the >client through an orderly close. On the other hand, maybe 11 minutes >is too long? I'll bet nothing terrible happens if that timeout drops >to 1 minute ... or 30 seconds. Even 0 would at worst lead to some >unnecessary RST's on closing connections. Anyone have any thoughts on >this? IMHO, this should be configurable by a sysctl object. Those sockets are tying resources on the server and as someone else has told, most of them come from buggy client implementations, so they deserve the RST anyway :) -lem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 12:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20978 for freebsd-isp-outgoing; Fri, 22 May 1998 12:03:44 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20926; Fri, 22 May 1998 12:03:27 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 22 May 1998 14:52:07 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FA60@freya.circle.net> From: tcobb To: "'Jim Shankland'" , mark@vmunix.com, tlambert@primenet.com Cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: RE: TIME_WAIT/FIN_WAIT_2... Date: Fri, 22 May 1998 14:51:57 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Jim Shankland [mailto:jas@flyingfox.com] > Sent: Friday, May 22, 1998 12:43 PM > To: mark@vmunix.com; tlambert@primenet.com > Cc: hackers@FreeBSD.ORG; isp@FreeBSD.ORG > Subject: Re: TIME_WAIT/FIN_WAIT_2... [snip] > The reason for the 11 minute wait is so that if the client is just > slow going through its shutdown stuff, the server can still walk the > client through an orderly close. On the other hand, maybe 11 minutes > is too long? I'll bet nothing terrible happens if that timeout drops > to 1 minute ... or 30 seconds. Even 0 would at worst lead to some > unnecessary RST's on closing connections. Anyone have any thoughts on > this? I'd love to see it as a sysctl tuning option :) just $0.02 worth, -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 12:18:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24723 for freebsd-isp-outgoing; Fri, 22 May 1998 12:18:42 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA24700; Fri, 22 May 1998 12:18:34 -0700 (PDT) (envelope-from barney@databus.databus.com) From: Barney Wolff To: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Date: Fri, 22 May 1998 15:13 EDT Subject: Re: TIME_WAIT/FIN_WAIT_2... Content-Type: text/plain Message-ID: <3565cf630.1308@databus.databus.com> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Fri, 22 May 1998 09:43:04 -0700 (PDT) > From: Jim Shankland > > The reason for the 11 minute wait is so that if the client is just > slow going through its shutdown stuff, the server can still walk the > client through an orderly close. On the other hand, maybe 11 minutes > is too long? I'll bet nothing terrible happens if that timeout drops > to 1 minute ... or 30 seconds. Even 0 would at worst lead to some > unnecessary RST's on closing connections. Anyone have any thoughts on > this? See archives of the tcp-impl list. (majordomo@engr.sgi.com) ftp://ftp.sgi.com/other/tcp-impl/mail.archive Barney Wolff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 12:43:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01018 for freebsd-isp-outgoing; Fri, 22 May 1998 12:43:43 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00957; Fri, 22 May 1998 12:43:30 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA26156; Fri, 22 May 1998 12:43:25 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd026072; Fri May 22 12:43:15 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA00619; Fri, 22 May 1998 12:43:11 -0700 (MST) From: Terry Lambert Message-Id: <199805221943.MAA00619@usr02.primenet.com> Subject: Re: TIME_WAIT/FIN_WAIT_2... To: jas@flyingfox.com (Jim Shankland) Date: Fri, 22 May 1998 19:43:11 +0000 (GMT) Cc: mark@vmunix.com, tlambert@primenet.com, hackers@FreeBSD.ORG, isp@FreeBSD.ORG In-Reply-To: <199805221643.JAA01914@biggusdiskus.flyingfox.com> from "Jim Shankland" at May 22, 98 09:43:04 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > [mark@vmunix.com (Mark Mayo) asks about large numbers of TCP connections > in TIME_WAIT and FIN_WAIT_2 states on a busy Web server. > Terry Lambert responds: > > > This is a client bug, specifically with Windows WinSock clients, which > > do not call "shutdown(2)" in the following way: > > > > shutdown( s, 1); > > > > The '1' should be a '2', but many WinSock implementations fail to work > > correctly if it isn't a '1'. > > > > [...] > > > > The fix is to be bug-compatible with Windows NT as a server, and to, > > when you are in FIN_WAIT_2 state, back up to resend the FIN. > > > > The problem is the lack of an ACK needed for a state transition in > > the Windows TCP/IP implemenetation. > > Terry, I think you have your TCP states mixed up. First, none of this > applies to the TIME_WAIT connections. I think it's you that are mixed up... see the Apache FAQ on FIN_WAIT_2, and contact Paul Vixie, as I've suggested. > As for the FIN_WAIT_2 connections: FIN_WAIT_2 means, "I'm done sending, > I've sent a FIN, the other side has ACKed my FIN, but the other side > has not sent *me* a FIN to indicate that it is done sending." One > would then expect the peer to be in CLOSE_WAIT state. This is a > perfectly legal state that can persist indefinitely, with the > CLOSE_WAIT end sending unbounded amounts of data to the FIN_WAIT_2 > end for consumption. > > Why on earth would you "back up to resend [a] FIN" that has already > been ACKed? Because the peer is *NOT* in CLOSE_WAIT state, because the peer is a Windows box, and the socket descriptor was abandoned with the peer in CLOSE_WAIT, without a resource-track cleanup of the connection. Here is the relevent state diagram from RFC793: TCP A TCP B 1. ESTABLISHED ESTABLISHED 2. (Close) FIN-WAIT-1 --> --> CLOSE-WAIT 3. FIN-WAIT-2 <-- <-- CLOSE-WAIT 4. (Close) TIME-WAIT <-- <-- LAST-ACK 5. TIME-WAIT --> --> CLOSED 6. (2 MSL) CLOSED Here is what the Windows machine does, when you are not running WinSock 2.0, and you have not called "shutdown()" on the socket, as documented in: Windows Sockets Network Programming Bob Quinn, Dave Shute Addison-Wesley _Advanced Windows Series_ ISBN: 0-201-63372-8 TCP A TCP B 1. ESTABLISHED ESTABLISHED 2. (Close) FIN-WAIT-1 --> --> CLOSE-WAIT 3. FIN-WAIT-2 <-- <-- CLOSE-WAIT 4. (Exit) FIN-WAIT-2 5. FIN-WAIT-2 6. FIN-WAIT-2 ... In other words, the socket is torn down without a LAST-ACK. The "workaround" that you should use to deal with this is to: A) wait 2 MSL for the LAST-ACK. B) reset to FIN-WAIT-1; send the packet. C) if you get CLOSE-WAIT, then goto (A). D) if you get no response in 2 MSL, or RST, then act as if you had recieved the CLOSE-WAIT, transitioned to FIN-WAIT-2, and subsequently recieved the LAST-ACK. E) (potential "enhancement") If you get no response, rather than treating it as an RST, goto (A), but maintain the FIN_WAIT_2_TIMEOUT kludge currently in place. This keeps the buggered connections (which are buggered by the inability to restart a damaged client conversation at state 2) around for a max of 6 MSL, and unbuggered connections act normally (due to duplicate packet reception processing). The need for a LAST-ACK without a TCP A packet solcitation of some kind is arguably a bug in the design of TCP (otherwise people would not be bitching about the problem). Of of the main pains-in-the-ass in not calling "shutdown()" is Netscape, BTW. > I suspect what you really mean is that the client side never sends its > FIN, even though it's really done sending, leaving the server-side > hanging in FIN_WAIT_2 state, waiting for either more data or a close > from the client, while the client wll never bother to send either.. > This can happen due to application-layer or TCP-layer bugs on the > client side, or because the client crashed or was powered off at an > inopportune time. > > What BSD-based TCP stacks do is this: if the FIN_WAIT_2 socket has > been closed by the application (i.e., there's no-one there to receive > any data that might arrive), and no data arrives for about 11 minutes, > then the connection is silently dropped. (Remember, if the FIN_WAIT_2 > socket has not been closed, then data could arrive after an arbitrarily > long silence, and there's a process there to read that data; so the > connection *must not* be dropped.) 11 mintues is too long a time compared to 6 MSL. By sending a "duplicate packet" to test the lividity of the client, you can solicit a "keepalive" (or an RST). If you get the RST, then you recover from the client error. Paul Vixie had to do this modification to NetBSD Alpha in order to handle a very high hit rate of a WWW server by technically broken Windows clients. > So what you're really seeing, Mark, is connections in FIN_WAIT_2 state, > where the web server has closed the socket, but the client has never > indicated that it is done sending. These hang around for about 11 > minutes, then disappear. (Of course, more take their place.) And according to RFC793, they are not supposed to be timed out at all, ever, and FreeBSD's implementation is non-conforming for doing the 11 minute drop. Being non-conformant is being non-conformant. It doesn't matter how you implement the non-conformance. With Vixie's implementation, at least the non-conformance does not result in incorrect behaviour for slow clients which are *truly* intendinding to actually send the LAST-ACK, but have not closed, over a period of more than 11 minutes (FIN_WAIT_2_TIMEOUT). > The reason for the 11 minute wait is so that if the client is just > slow going through its shutdown stuff, the server can still walk the > client through an orderly close. On the other hand, maybe 11 minutes > is too long? I'll bet nothing terrible happens if that timeout drops > to 1 minute ... or 30 seconds. Even 0 would at worst lead to some > unnecessary RST's on closing connections. Anyone have any thoughts on > this? See the algorithm above. It is the Algorithm used by NT Server. Much as I hate the idea of being bug-compatible with NT, at the very least there should be a sysctl that acknowledges the fact that most client machines are Windows boxes with broken TCP implementations. This is roughly equivalent to the fact that FreeBSD allows RFC1323 & RFC1544 to be turned off to support non-conforming TCP implemetnations. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri May 22 21:02:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25472 for freebsd-isp-outgoing; Fri, 22 May 1998 21:02:04 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25359; Fri, 22 May 1998 21:01:49 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id CAA13839; Sat, 23 May 1998 02:57:37 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805230157.CAA13839@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: "Patrick M. Hausen" cc: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Problems connecting to AIX box with PPP In-reply-to: Your message of "Fri, 22 May 1998 15:38:10 +0200." <199805221338.PAA28604@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 May 1998 02:57:36 +0100 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, didn't I see this question on Usenet too ? You should really wait a bit to see if you get any answers..... > Hi all! > > I'm trying to connect a FreeBSD 2.2.6 box to a AIX system with user PPP. > > The AIX box is setup as follows: > > - there's a user with a regular login > > - in his .profile there's: > "exec /usr/sbin/pppattachd server 2>/dev/null" > > - the interface config for PPP is: > > interface > server > local_ip 10.8.11.240 > remote_ip 10.8.11.245 > netmask 255.155.155.0 > > It's AIX version 4.1.5.0 and the above is what the AIX manual suggested. > This worked out of the box with Windows 95 as a client. > > > I set up FreeBSD /etc/ppp/ppp.conf like this: > > default: > set device /dev/cuaa0 > set speed 19200 > disable pred1 > deny pred1 > disable lqr > deny lqr > set redial 30 3 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT&FX3 OK-AT-OK \\dATDT\\T TIMEOUT 120 CONNECT" > > blabla: > set log chat lcp ipcp > set phone 0w0033387282534 > set timeout 300 > set openmode active > set login "TIMEOUT 30 ogin:-\\r-ogin: blabla ennwort foobar" > set ifaddr 10.8.11.245/32 10.8.11.240/32 255.255.255.0 > > (Don't be fooled by the "ennwort" - this stupid thing asks for the > password in German ;-) > > Now, when I try to use 57600 or 38400 DTE speed, even the login fails. > When I use 19200, login, lcp and ipcp seem to work: > > May 20 14:23:43 poseidon ppp[460]: Phase: Using interface: tun0 > May 20 14:23:46 poseidon ppp[461]: Chat: Dial attempt 1 of 3 > May 20 14:23:46 poseidon ppp[461]: Chat: Expecting: > May 20 14:23:46 poseidon ppp[461]: Chat: Sending: AT&FX3^M > May 20 14:23:46 poseidon ppp[461]: Chat: Expecting: OK-AT-OK > May 20 14:23:46 poseidon ppp[461]: Chat: Wait for (5): OK > May 20 14:23:48 poseidon ppp[461]: Chat: Sending: ATDT0w*************^M > May 20 14:23:48 poseidon ppp[461]: Chat: Expecting: CONNECT > May 20 14:23:48 poseidon ppp[461]: Chat: Wait for (120): CONNECT > May 20 14:24:28 poseidon ppp[461]: Chat: Expecting: ogin:-\r-ogin: > May 20 14:24:28 poseidon ppp[461]: Chat: Wait for (30): ogin: > May 20 14:24:30 poseidon ppp[461]: Chat: Sending: blabla^M > May 20 14:24:30 poseidon ppp[461]: Chat: Expecting: ennwort > May 20 14:24:30 poseidon ppp[461]: Chat: Wait for (30): ennwort > May 20 14:24:30 poseidon ppp[461]: Chat: Sending: foobar^M > May 20 14:24:30 poseidon ppp[461]: LCP: State change Initial --> Closed > May 20 14:24:30 poseidon ppp[461]: LCP: State change Closed --> Stopped > May 20 14:24:31 poseidon ppp[461]: LCP: Received Configure Request (1) state = Stopped (3) > May 20 14:24:31 poseidon ppp[461]: LCP: MRU[4] 1500 > May 20 14:24:31 poseidon ppp[461]: LCP: ACCMAP[6] 0x00000000 > May 20 14:24:31 poseidon ppp[461]: LCP: MAGICNUM[6] 0x3562ca23 > May 20 14:24:31 poseidon ppp[461]: LCP: PROTOCOMP[2] > May 20 14:24:31 poseidon ppp[461]: LCP: ACFCOMP[2] > May 20 14:24:31 poseidon ppp[461]: LCP: LcpSendConfigReq > May 20 14:24:31 poseidon ppp[461]: LCP: ACFCOMP[2] > May 20 14:24:31 poseidon ppp[461]: LCP: PROTOCOMP[2] > May 20 14:24:31 poseidon ppp[461]: LCP: ACCMAP[6] 0x00000000 > May 20 14:24:31 poseidon ppp[461]: LCP: MRU[4] 1500 > May 20 14:24:31 poseidon ppp[461]: LCP: MAGICNUM[6] 0x771eba49 > May 20 14:24:31 poseidon ppp[461]: LCP: SendConfigAck(Stopped) > May 20 14:24:31 poseidon ppp[461]: LCP: MRU[4] 1500 > May 20 14:24:31 poseidon ppp[461]: LCP: ACCMAP[6] 0x00000000 > May 20 14:24:31 poseidon ppp[461]: LCP: MAGICNUM[6] 0x3562ca23 > May 20 14:24:31 poseidon ppp[461]: LCP: PROTOCOMP[2] > May 20 14:24:31 poseidon ppp[461]: LCP: ACFCOMP[2] > May 20 14:24:31 poseidon ppp[461]: LCP: State change Stopped --> Ack-Sent > May 20 14:24:31 poseidon ppp[461]: LCP: Received Configure Ack (1) state = Ack-Sent (8) > May 20 14:24:31 poseidon ppp[461]: LCP: State change Ack-Sent --> Opened > May 20 14:24:31 poseidon ppp[461]: LCP: LcpLayerUp > May 20 14:24:31 poseidon ppp[461]: IPCP: State change Initial --> Closed > May 20 14:24:31 poseidon ppp[461]: IPCP: IPCP Up event!! > May 20 14:24:31 poseidon ppp[461]: IPCP: IpcpSendConfigReq > May 20 14:24:31 poseidon ppp[461]: IPCP: IPADDR[6] 10.8.11.245 > May 20 14:24:31 poseidon ppp[461]: IPCP: COMPPROTO[6] 16 VJ slots with slot compres > May 20 14:24:31 poseidon ppp[461]: IPCP: State change Closed --> Req-Sent > May 20 14:24:31 poseidon ppp[461]: IPCP: Received Configure Request (1) state = Req-Sent (6) > May 20 14:24:31 poseidon ppp[461]: IPCP: IPADDR[6] 10.8.11.240 > May 20 14:24:31 poseidon ppp[461]: IPCP: COMPPROTO[6] 16 VJ slots with slot compression > May 20 14:24:31 poseidon ppp[461]: IPCP: SendConfigAck(Req-Sent) > May 20 14:24:31 poseidon ppp[461]: IPCP: IPADDR[6] 10.8.11.240 > May 20 14:24:31 poseidon ppp[461]: IPCP: COMPPROTO[6] 16 VJ slots with slot compression > May 20 14:24:31 poseidon ppp[461]: IPCP: State change Req-Sent --> Ack-Sent > May 20 14:24:31 poseidon ppp[461]: IPCP: Received Configure Ack (1) state = Ack-Sent (8) > May 20 14:24:31 poseidon ppp[461]: IPCP: State change Ack-Sent --> Opened > May 20 14:24:31 poseidon ppp[461]: IPCP: IpcpLayerUp(9). > May 20 14:24:31 poseidon ppp[461]: IPCP: myaddr = 10.8.11.245 hisaddr = 10.8.11.240 > May 20 14:24:31 poseidon ppp[461]: LCP: OsLinkup: 10.8.11.240 > May 20 14:24:31 poseidon ppp[461]: LCP: Received Protocol Reject (2) state = Opened (9) > May 20 14:24:31 poseidon ppp[461]: LCP: -- Protocol (80fd) was rejected. > > > But, when I try to ping, the modem transmit LED flashes, but i don't get > an echo back. The admin on the other side isn't too Unix experienced, > but from what he told me, his routing table looked OK. The interfaces > on both sides seemed to be up, the routes correct - but noone could > ping the other end. > > > Any suggestions? > > Patrick -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat May 23 05:48:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20601 for freebsd-isp-outgoing; Sat, 23 May 1998 05:48:50 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from heron.doc.ic.ac.uk (IyaysqvMP0eYKvfKQoE1v87Ow7fS0Bu3@heron.doc.ic.ac.uk [146.169.46.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20578; Sat, 23 May 1998 05:48:42 -0700 (PDT) (envelope-from njs3@doc.ic.ac.uk) Received: from oak67.doc.ic.ac.uk [146.169.33.67] ([a+uCvNv8PtCXHuJbZsFGfqEmGalMqQpD]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0ydDip-0000VP-00; Sat, 23 May 1998 13:48:23 +0100 Received: from njs3 by oak67.doc.ic.ac.uk with local (Exim 1.62 #3) id 0ydDio-0001gv-00; Sat, 23 May 1998 13:48:22 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Sat, 23 May 1998 13:48:21 +0100 In-Reply-To: Terry Lambert "Re: TIME_WAIT/FIN_WAIT_2..." (May 22, 7:43pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Terry Lambert , jas@flyingfox.com (Jim Shankland) Subject: Re: TIME_WAIT/FIN_WAIT_2... Cc: mark@vmunix.com, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Message-Id: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On May 22, 7:43pm, Terry Lambert wrote: } Subject: Re: TIME_WAIT/FIN_WAIT_2... > > [mark@vmunix.com (Mark Mayo) asks about large numbers of TCP connections > Because the peer is *NOT* in CLOSE_WAIT state, because the peer is > a Windows box, and the socket descriptor was abandoned with the > peer in CLOSE_WAIT, without a resource-track cleanup of the connection. [snip] > Here is what the Windows machine does, when you are not running > WinSock 2.0, and you have not called "shutdown()" on the socket, [snip] > TCP A TCP B > > 1. ESTABLISHED ESTABLISHED > > 2. (Close) > FIN-WAIT-1 --> --> CLOSE-WAIT > > 3. FIN-WAIT-2 <-- <-- CLOSE-WAIT > > 4. (Exit) > FIN-WAIT-2 > 5. > FIN-WAIT-2 > 6. > FIN-WAIT-2 > > In other words, the socket is torn down without a LAST-ACK. > The "workaround" that you should use to deal with this is to: > > A) wait 2 MSL for the LAST-ACK. > > B) reset to FIN-WAIT-1; send the packet. > > C) if you get CLOSE-WAIT, then goto (A). I'm a little unclear as to what exactly what should happen when a TCP stack receives a packet when it is in CLOSE-WAIT state. Are you relying on the following bahaviour documented in STD7, line ~2358? 3. If the connection is in a synchronized state (ESTABLISHED, FIN-WAIT-1, FIN-WAIT-2, CLOSE-WAIT, CLOSING, LAST-ACK, TIME-WAIT), any unacceptable segment (out of window sequence number or unacceptible acknowledgment number) must elicit only an empty acknowledgment segment containing the current send-sequence number and an acknowledgment indicating the next sequence number expected to be received, and the connection remains in the same state. > D) if you get no response in 2 MSL, or RST, then act as if > you had recieved the CLOSE-WAIT, transitioned to FIN-WAIT-2, > and subsequently recieved the LAST-ACK. Uh-huh. > E) (potential "enhancement") If you get no response, rather > than treating it as an RST, goto (A), but maintain the > FIN_WAIT_2_TIMEOUT kludge currently in place. Can I suggest that if you receive a response after step C, which you call the CLOSE-WAIT response, then the TCP stack should remain in FIN-WAIT-2 with an infinite timeout, because the response indicates that the remote TCP stack not broken and moreover that the remote client is not finished sending yet. (i.e. the 11 minute timeout you mention later would not be used) > Of of the main pains-in-the-ass in not calling "shutdown()" is > Netscape, BTW. Well, the Windows TCP/IP stack should be sending the FIN when the socket is closed. > 11 mintues is too long a time compared to 6 MSL. By sending a > "duplicate packet" to test the lividity of the client, you can > solicit a "keepalive" (or an RST). If you get the RST, then you > recover from the client error. And otherwise wait indefinately for the FIN? > And according to RFC793, they are not supposed to be timed out at > all, ever, and FreeBSD's implementation is non-conforming for doing > the 11 minute drop. [snip] > Much as I hate the idea of being bug-compatible with NT, at the very > least there should be a sysctl that acknowledges the fact that most > client machines are Windows boxes with broken TCP implementations. I think that this is a bug Microsoft would be eager to fix, after all, if it affects FreeBSD web servers it also affects NT web servers, as well as NT file servers, Exchange servers etc etc. Has anyone yet verified that this is indeed the observed behaviour with NT with all applied patches? If so perhaps we should try and convince Microsoft to fix the problem first. Although having said that, Terry's algorithm does have the nice side effect of allowing us to remove the 11 minute non-conformant FIN-WAIT-2 drop. Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat May 23 13:38:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28320 for freebsd-isp-outgoing; Sat, 23 May 1998 13:38:56 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28272; Sat, 23 May 1998 13:38:34 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA21323; Sat, 23 May 1998 13:38:32 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd021310; Sat May 23 13:38:28 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA12442; Sat, 23 May 1998 13:38:18 -0700 (MST) From: Terry Lambert Message-Id: <199805232038.NAA12442@usr07.primenet.com> Subject: Re: TIME_WAIT/FIN_WAIT_2... To: njs3@doc.ic.ac.uk (Niall Smart) Date: Sat, 23 May 1998 20:38:18 +0000 (GMT) Cc: tlambert@primenet.com, jas@flyingfox.com, mark@vmunix.com, hackers@FreeBSD.ORG, isp@FreeBSD.ORG In-Reply-To: from "Niall Smart" at May 23, 98 01:48:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > C) if you get CLOSE-WAIT, then goto (A). > > I'm a little unclear as to what exactly what should happen when > a TCP stack receives a packet when it is in CLOSE-WAIT state. Are > you relying on the following bahaviour documented in STD7, line ~2358? Yes. I should have said "if you think the client should be sending you the packet it should when it goes to CLOSE-WAIT state, but you aren't getting that packet" to be technically correct. > 3. If the connection is in a synchronized state (ESTABLISHED, > FIN-WAIT-1, FIN-WAIT-2, CLOSE-WAIT, CLOSING, LAST-ACK, TIME-WAIT), > any unacceptable segment (out of window sequence number or > unacceptible acknowledgment number) must elicit only an empty > acknowledgment segment containing the current send-sequence number > and an acknowledgment indicating the next sequence number expected > to be received, and the connection remains in the same state. > > > D) if you get no response in 2 MSL, or RST, then act as if > > you had recieved the CLOSE-WAIT, transitioned to FIN-WAIT-2, > > and subsequently recieved the LAST-ACK. > > Uh-huh. > > > E) (potential "enhancement") If you get no response, rather > > than treating it as an RST, goto (A), but maintain the > > FIN_WAIT_2_TIMEOUT kludge currently in place. > > Can I suggest that if you receive a response after step C, which you call > the CLOSE-WAIT response, then the TCP stack should remain in FIN-WAIT-2 > with an infinite timeout, because the response indicates that the remote > TCP stack not broken and moreover that the remote client is not finished > sending yet. (i.e. the 11 minute timeout you mention later would not > be used) You can't do this. You must constantly ask the client "Are you done yet? Are you done yet?" because you have no other method of distinguishing a broken client from a non-broken client. This sucks, but effectively, you have several problems that are intractable if you do this: 1) The Microsoft TCP stack client that isn't done the first time you ask it, but gets done later, and never calls shutdown like it should. 2) A client machine that is disconnected from the net because it has been shut off, rebooted, or physically disconnected (mobile, dialup, whatever). These will result in the same failure you are trying to avoid, and you've just killed the avoidance behaviour. I understand why you would want to suggest this: it narrows the non-compliance window considerably. As a practical consideration, I expect FreeBSD to ship a technically compliant configuration by default (like it does with the RFC's whose option negotiation breaks peoples hardware), and then have practically everyone in the known universe running FreeBSD turn on the workaround for the Microsoft brain damage. > > Of of the main pains-in-the-ass in not calling "shutdown()" is > > Netscape, BTW. > > Well, the Windows TCP/IP stack should be sending the FIN when the > socket is closed. Well, the Windows TCP/IP stack doesn't know that the socket is closed, because it's implemented un user space, does not use a resource tracked object (a WinSock socket is *not* a file descriptor), and basically *can't* do the right thing most of the time. It *could* do the right thing on explicit close (ie: imply a shutdown) or on program exit, but doesn't. And you can dictate standards to Microsoft until you are blue in the face, and it won't help. I could easily see this as being intentional as a denial of service attack to make non-NT server machines look bad. I could also see it as being a known bug that they are refusing to fix because it points out a deficiency in TCP with mobile and transiently running machines. In most cases, you won't get any response, instead of an RST, since the RST won't occur if there are zero WinSock applications running, since there is no code to field the packet and decide it's bogus loaded at all. > > 11 mintues is too long a time compared to 6 MSL. By sending a > > "duplicate packet" to test the lividity of the client, you can > > solicit a "keepalive" (or an RST). If you get the RST, then you > > recover from the client error. > > And otherwise wait indefinately for the FIN? Yes; if the client is alive, and not sending back zero sized window responses. > I think that this is a bug Microsoft would be eager to fix, after all, > if it affects FreeBSD web servers it also affects NT web servers, as > well as NT file servers, Exchange servers etc etc. I think you are wrong. Microsoft implements the "fix" I have stated, and is not affected by the problem. The "problem" would be that Microsoft clients cause UNIX servers to behave badly, but NT servers are unaffected. I would think that this would be a problem Microsoft would be eager to exacerbate in order to make UNIX servers look less viable than NT servers. > Has anyone yet > verified that this is indeed the observed behaviour with NT with all > applied patches? If so perhaps we should try and convince Microsoft to > fix the problem first. Although having said that, Terry's algorithm > does have the nice side effect of allowing us to remove the 11 minute > non-conformant FIN-WAIT-2 drop. I would keep it in there to prevent zero window size response based denial of service attacks on UNIX servers (enhancement "E"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat May 23 22:18:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11177 for freebsd-isp-outgoing; Sat, 23 May 1998 22:18:19 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from toronto.enoreo.on.ca (toronto.enoreo.on.ca [209.47.17.25]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA11172; Sat, 23 May 1998 22:18:17 -0700 (PDT) (envelope-from memmerto@undergrad.math.uwaterloo.ca) Received: from [209.82.52.19] by toronto.enoreo.on.ca id aa08632; 24 May 98 1:20 EDT Message-ID: <002201bd86d2$b4d8c080$0200000a@win95.gsicomp.on.ca> From: Matthew Emmerton To: , , , Subject: Microsoft Frontpage 98 Server Extensions Date: Sun, 24 May 1998 01:13:31 -0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_001E_01BD86B1.2A890C80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_001E_01BD86B1.2A890C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I recently got FreeBSD-2.2.6 running, and downloaded the most recent MS Frontpage Server extensions (version 3.0.4 according to the tarball I got) for BSD/OS 3.0 from the Microsoft site. However, I noticed a couple of problems that would be worthwhile to mention. First, the fp_install.sh script (obviously) doesn't support FreeBSD and dies horribly. So, rename the distribution to fp30.freebsd.tar.gz, and patch the fp_install.sh with fpext-3.0.4-freebsd-fp_install-patch. Also, the huge patchfile that patches Apache 1.2.5 contains a mistake (for bsdi users) and (of course) needs to be fixed up for us FreeBSD users. Apply the patch fpext-3.0.4-freebsd-fp-patch-apache_1.2.5-patch before patching the Apache server. I have submitted this information to RTR and (hopefully) they'll include some of it in the next release of the extensions. -- Matthew Emmerton GSI Computer Services, Consultant ------=_NextPart_000_001E_01BD86B1.2A890C80 Content-Type: application/octet-stream; name="fpext-3.0.4-freebsd-fp_install-patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="fpext-3.0.4-freebsd-fp_install-patch" --- fp_install.sh.orig Sat May 23 19:23:58 1998 +++ fp_install.sh Sat May 23 23:33:41 1998 @@ -72,7 +72,6 @@ *BSD/OS?3.0*) machine=3D"bsdi3" ;; BSD/OS*) machine=3D"bsdi" ;; SCO_SV*) machine=3D"sco5" ;; - FreeBSD*) machine=3D"freebsd" ;; *) echo "ERROR: Unsupported platform! Uname is = $system."=20 return 1 ;; ------=_NextPart_000_001E_01BD86B1.2A890C80 Content-Type: application/octet-stream; name="fpext-3.0.4-freebsd-fp-patch-apache_1.2.5-patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="fpext-3.0.4-freebsd-fp-patch-apache_1.2.5-patch" --- apache-fp/fp-patch-apache_1.2.5.orig Sat May 23 23:34:24 1998 +++ apache-fp/fp-patch-apache_1.2.5 Sat May 23 23:35:04 1998 @@ -477,7 +477,7 @@ +#ifdef LINUX +#define RAND_CMD "/bin/ps laxww | /usr/bin/sum ; /bin/ps laxww | = /usr/bin/sum" +#else -+#ifdef bsdi ++#if defined(__bsdi__) || defined(__FreeBSD__) +#define RAND_CMD "/bin/ps laxww | /usr/bin/cksum -o 1 ; /bin/ps laxww = | /usr/bin/cksum -o 1" +#else +#define RAND_CMD "/bin/ps -ea | /bin/sum ; /bin/ps -ea | /bin/sum" ------=_NextPart_000_001E_01BD86B1.2A890C80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message