From owner-freebsd-isp Sun May 28 8:57:24 2000 Delivered-To: freebsd-isp@freebsd.org Received: from MexComUSA.Net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 33B4D37BC8F for ; Sun, 28 May 2000 08:57:21 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from EnContacto.Net (adsl-63-205-16-202.dsl.mtry01.pacbell.net [63.205.16.202]) by MexComUSA.Net (8.9.3/8.9.3) with ESMTP id IAA95277; Sun, 28 May 2000 08:56:57 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Message-ID: <393141D9.D688E8CF@EnContacto.Net> Date: Sun, 28 May 2000 08:57:13 -0700 From: Edwin Culp Organization: MexComUSA.Net/EnContacto.Net X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Danny Cc: "freebsd-isp@FreeBSD.ORG" Subject: Re: Alternate solution to Verisign References: <392FEB00.91085948@EnContacto.Net> <00052910310901.00361@freebsd.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks, Danny. There are a world of shopping cart applications out there. I have been looking at fishcart but this one also looks interesting and I haven't seen it before. I do tend to favor php. Thanks again, ed Danny wrote: > phpshop.org > www.freecode.com > > They are all over the place once you understand some php3 and perl. > > On Sun, 28 May 2000, Edwin Culp wrote: > > Does anyone have a suggestion for an alternate/better value solution to > > Verisign/Signio certificate/ on-line credit card processing? > > > > Thanks, > > > > ed > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 5:11:16 2000 Delivered-To: freebsd-isp@freebsd.org Received: from odin.activeisp.no (odin.activeisp.com [213.188.133.110]) by hub.freebsd.org (Postfix) with ESMTP id 2A21A37B7C7 for ; Mon, 29 May 2000 05:11:11 -0700 (PDT) (envelope-from nc@collector.org) Received: from kekar (kekar.activeisp.com [213.188.133.26]) by odin.activeisp.no (8.9.3/8.9.3) with SMTP id OAA86264 for ; Mon, 29 May 2000 14:11:07 +0200 (CEST) Message-ID: <014101bfc966$fd55f7a0$1a85bcd5@kekar.dhs.org> From: "odin" To: Subject: Default stack size Date: Mon, 29 May 2000 14:11:15 +0200 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org stack size (kbytes) 65536 Is there a convenient way to increase the default stack size limit (64MB) in the kernel configuration? I've failed to located any such parameters in the LINT-conf file. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 7:15:41 2000 Delivered-To: freebsd-isp@freebsd.org Received: from internet.conectividad.com.mx (internet.conectividad.com.mx [200.23.128.241]) by hub.freebsd.org (Postfix) with ESMTP id B3A9137BC6B for ; Mon, 29 May 2000 07:15:37 -0700 (PDT) (envelope-from dperez@conectividad.com.mx) Received: by INTERNET with Internet Mail Service (5.5.2650.21) id ; Mon, 29 May 2000 09:16:37 -0500 Message-ID: From: David Perez Marfil To: "'freebsd-isp@FreeBSD.ORG'" Subject: RE: Alternate solution to Verisign Date: Mon, 29 May 2000 09:16:37 -0500 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org http://www.thawte.com/ -----Mensaje original----- De: Edwin Culp [mailto:eculp@EnContacto.Net] Enviado el: S=E1bado, 27 de Mayo de 2000 10:34 a.m. Para: freebsd-isp@FreeBSD.ORG Asunto: Alternate solution to Verisign Does anyone have a suggestion for an alternate/better value solution to Verisign/Signio certificate/ on-line credit card processing? Thanks, ed David Perez To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 8:24:59 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mooseriver.com (superior.mooseriver.com [209.249.56.198]) by hub.freebsd.org (Postfix) with ESMTP id E71D137BA06 for ; Mon, 29 May 2000 08:24:50 -0700 (PDT) (envelope-from jgrosch@mooseriver.com) Received: (from jgrosch@localhost) by mooseriver.com (8.9.3/8.9.3) id IAA07035; Mon, 29 May 2000 08:24:44 -0700 (PDT) (envelope-from jgrosch) Date: Mon, 29 May 2000 08:24:44 -0700 From: Josef Grosch To: David Perez Marfil Cc: "'freebsd-isp@FreeBSD.ORG'" Subject: Re: Alternate solution to Verisign Message-ID: <20000529082444.A6984@mooseriver.com> Reply-To: jgrosch@mooseriver.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: ; from dperez@conectividad.com.mx on Mon, May 29, 2000 at 09:16:37AM -0500 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, May 29, 2000 at 09:16:37AM -0500, David Perez Marfil wrote: > http://www.thawte.com/ > > > -----Mensaje original----- > De: Edwin Culp [mailto:eculp@EnContacto.Net] > Enviado el: Sábado, 27 de Mayo de 2000 10:34 a.m. > Para: freebsd-isp@FreeBSD.ORG > Asunto: Alternate solution to Verisign > > > Does anyone have a suggestion for an alternate/better value solution to > Verisign/Signio certificate/ on-line credit card processing? Thawte just got bought by Verisign. Jsef -- Josef Grosch | Another day closer to a | FreeBSD 4.0 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 10:57:30 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ns2.jjsoft.com (fig2.figdav.com [208.152.114.19]) by hub.freebsd.org (Postfix) with ESMTP id 0682637B6AD for ; Mon, 29 May 2000 10:57:27 -0700 (PDT) (envelope-from jahanur@jjsoft.com) Received: from ns2.jjsoft.com (ns2.jjsoft.com [208.152.114.19]) by ns2.jjsoft.com (8.9.0/8.9.0) with SMTP id MAA08032 for ; Mon, 29 May 2000 12:48:51 -0500 (CDT) Date: Mon, 29 May 2000 12:48:50 -0500 (CDT) From: Jahanur R Subedar To: freebsd-isp@freebsd.org Subject: Apache modssl fp Help 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 Hi folks, I am strugling for a while to install the Apache SSL and Front page. Finally was able install only the Apache with SSL without any trouble. How do I install the Frontpage extension? Or do I need to go back to installing the three of them togather. Jahanur R Subedar WWW.JJSOFT.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 12:27:23 2000 Delivered-To: freebsd-isp@freebsd.org Received: from priv-edtnes04-hme0.telusplanet.net (edtnes04.telus.net [199.185.220.104]) by hub.freebsd.org (Postfix) with ESMTP id 8787337B5F0 for ; Mon, 29 May 2000 12:27:21 -0700 (PDT) (envelope-from james@aspert.com) Received: from james ([209.53.43.91]) by priv-edtnes04-hme0.telusplanet.net (InterMail vM.4.01.02.11 201-229-116-111) with SMTP id <20000529192720.PRTM4208.priv-edtnes04-hme0.telusplanet.net@james> for ; Mon, 29 May 2000 13:27:20 -0600 Message-ID: <003101bfc9a3$c9aa59e0$5b2b35d1@aspert.com> From: "James A. Peltier" To: Subject: subscribe Date: Mon, 29 May 2000 12:26:28 -0700 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 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 13:11: 9 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id B414837BD21 for ; Mon, 29 May 2000 13:10:59 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id PAA18938; Mon, 29 May 2000 15:10:53 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <008601bfc9a9$fdbc5f20$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Jahanur R Subedar" , References: Subject: Re: Apache modssl fp Help Date: Mon, 29 May 2000 15:10:53 -0500 Organization: West Bend Internet 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 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "Jahanur R Subedar" > I am strugling for a while to install the Apache SSL and Front page. > Finally was able install only the Apache with SSL without any trouble. > How do I install the Frontpage extension? > Or do I need to go back to installing the three of them togather. > Try the FreeBSD Apache ports collection at: http://www.westbend.net/~hetzels/mod_apache13.tgz Untar the collection into your /usr/port/www directory, then either use apache13-base to select the server and modules, or cd into the apache13*, mod_ssl (if not using apache13-ssl), mod_frontpage directories to build and install. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 16:20:14 2000 Delivered-To: freebsd-isp@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 4172D37B58B for ; Mon, 29 May 2000 16:20:11 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id DB400B423; Mon, 29 May 2000 19:20:09 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id C2EECB422; Mon, 29 May 2000 19:20:09 -0400 (EDT) Date: Mon, 29 May 2000 19:20:09 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Scot W. Hetzel" Cc: Jahanur R Subedar , freebsd-isp@FreeBSD.ORG Subject: Re: Apache modssl fp Help In-Reply-To: <008601bfc9a9$fdbc5f20$8dfee0d1@westbend.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 A quick question on frontpage... I seem to recall that the ports use the bsdi version of frontpage. Looking at the distro site, there now appears to be a freebsd version. So far I've had little luck with their install script, as it's from '98 and does not seem to include FreeBSD as a platform... Anyone else given this a spin? Thanks, Charles On Mon, 29 May 2000, Scot W. Hetzel wrote: > From: "Jahanur R Subedar" > > I am strugling for a while to install the Apache SSL and Front page. > > Finally was able install only the Apache with SSL without any trouble. > > How do I install the Frontpage extension? > > Or do I need to go back to installing the three of them togather. > > > Try the FreeBSD Apache ports collection at: > > http://www.westbend.net/~hetzels/mod_apache13.tgz > > Untar the collection into your /usr/port/www directory, then either use > apache13-base to select the server and modules, or cd into the apache13*, > mod_ssl (if not using apache13-ssl), mod_frontpage directories to build and > install. > > Scot > > > > 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 29 16:50: 5 2000 Delivered-To: freebsd-isp@freebsd.org Received: from cfdnet.me.tuns.ca (CFDnet.me.TUNS.Ca [134.190.50.164]) by hub.freebsd.org (Postfix) with ESMTP id B3E1E37BC3A for ; Mon, 29 May 2000 16:50:00 -0700 (PDT) (envelope-from bbmail@cfdnet.me.tuns.ca) Received: from localhost (bbmail@localhost) by cfdnet.me.tuns.ca (8.9.3/8.9.3) with ESMTP id UAA16256; Mon, 29 May 2000 20:46:43 -0300 (ADT) (envelope-from bbmail@cfdnet.me.tuns.ca) Date: Mon, 29 May 2000 20:46:43 -0300 (ADT) From: Bryan Bursey To: "Scot W. Hetzel" Cc: Jahanur R Subedar , freebsd-isp@FreeBSD.ORG Subject: Re: Apache modssl fp Help 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 Mon, 29 May 2000, Scot W. Hetzel wrote: > > > From: "Jahanur R Subedar" > > > I am strugling for a while to install the Apache SSL and Front page. > > > Finally was able install only the Apache with SSL without any trouble. > > > How do I install the Frontpage extension? > > > Or do I need to go back to installing the three of them togather. > > > > > Try the FreeBSD Apache ports collection at: > > > > http://www.westbend.net/~hetzels/mod_apache13.tgz > > What an excellent tool... and one I've been wishing for since finding the _nearly_ complete script with the apache13+mod_php3 port. When can we expect to see this tarball unleased into the 'official' FreeBSD ports collection? Yeah. I'm just a little weary of unofficial ports... Regards, Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Mon May 29 20:55: 3 2000 Delivered-To: freebsd-isp@freebsd.org Received: from casa.encontacto.net (adsl-63-205-16-202.dsl.mtry01.pacbell.net [63.205.16.202]) by hub.freebsd.org (Postfix) with ESMTP id 8B23F37B63F for ; Mon, 29 May 2000 20:54:59 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from EnContacto.Net (localhost [127.0.0.1]) by local-27.local.net (8.9.3/8.9.3) with ESMTP id HAA58739 for ; Sat, 27 May 2000 07:43:21 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Message-ID: <392FDF06.BF8A3BFA@EnContacto.Net> Date: Sat, 27 May 2000 07:43:18 -0700 From: Edwin Culp Organization: MexComUSA.Net/EnContacto.Net X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-isp@FreeBSD.ORG" Subject: Alternate solution to Verisign Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have a suggestion for an alternate/better value solution to Verisign/Signio certificate/ on-line credit card processing? Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 9:58:16 2000 Delivered-To: freebsd-isp@freebsd.org Received: from bigu.msen.com (bigu.msen.com [148.59.19.36]) by hub.freebsd.org (Postfix) with ESMTP id E673837B76D for ; Tue, 30 May 2000 09:58:10 -0700 (PDT) (envelope-from mbl@bigu.msen.com) Received: (from mbl@localhost) by bigu.msen.com (8.9.3/8.9.3) id MAA48665; Tue, 30 May 2000 12:59:40 -0400 (EDT) (envelope-from mbl) X-Sent-To: freebsd-isp@FreeBSD.ORG Date: Tue, 30 May 2000 12:59:40 -0400 From: Matthew Landry To: Josef Grosch Cc: David Perez Marfil , "'freebsd-isp@FreeBSD.ORG'" Subject: Re: Alternate solution to Verisign Message-ID: <20000530125940.A37609@bigu.msen.com> References: <20000529082444.A6984@mooseriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000529082444.A6984@mooseriver.com>; from jgrosch@mooseriver.com on Mon, May 29, 2000 at 08:24:44AM -0700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thawte just got bought by Verisign. "Just" is probably the wrong word...they've been owned by VeriSign for a while now. Equifax seems to be the best deal currently. The $45 promotion is over, but their regular $75/yr rate is still better than anyone else we've seen. -- Matthew Landry O- LEL Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 13: 7: 5 2000 Delivered-To: freebsd-isp@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 7873237B75C for ; Tue, 30 May 2000 13:07:01 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 94FE0B423; Tue, 30 May 2000 16:06:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 7EE3DB422 for ; Tue, 30 May 2000 16:06:58 -0400 (EDT) Date: Tue, 30 May 2000 16:06:58 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: freebsd-isp@freebsd.org Subject: Cucipop port/source 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 Hello, With yet another QPopper bug, we're thinking of moving to cucipop. I have a few questions for anyone who may be using it: -how do you like it? -any gotchas or incompatibilities in your userbase when you made the move? -did you get db support working? I'm currently running into this error (2.2-stable) with sleepycat's db stuff in /usr/local/lib and /usr/local/include/db2: c -O -DUSE_DB -I /usr/local/include -c dbops.c dbops.c: In function `getstate': dbops.c:120: too few arguments to function *** Error code 1 Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 13:13: 6 2000 Delivered-To: freebsd-isp@freebsd.org Received: from hindenburg.eboai.org (hindenburg.eboai.org [205.181.254.190]) by hub.freebsd.org (Postfix) with ESMTP id A80AB37B6DC for ; Tue, 30 May 2000 13:12:59 -0700 (PDT) (envelope-from chip@chocobo.cx) Received: by hindenburg.eboai.org (Postfix, from userid 1000) id 77C853D59; Tue, 30 May 2000 16:12:56 -0400 (EDT) Date: Tue, 30 May 2000 16:12:56 -0400 From: Chip Marshall To: spork Cc: freebsd-isp@freebsd.org Subject: Re: Cucipop port/source Message-ID: <20000530161256.A17694@setzer.chocobo.cx> Reply-To: chip@chocobo.cx References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i In-Reply-To: ; from spork@super-g.com on Tue, May 30, 2000 at 04:06:58PM -0400 X-URL: http://www.chocobo.cx/chip/ X-OS: FreeBSD 3.4-RELEASE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On May 30, 2000, spork sent me the following: > With yet another QPopper bug, we're thinking of moving to cucipop. I have > a few questions for anyone who may be using it: > > -how do you like it? > -any gotchas or incompatibilities in your userbase when you made the move? > -did you get db support working? We switched over to it a while back after we had a break in involving one of the older versions of qpopper, and it seems to be doing quite well. We had no problem moving over at all, just killed qpopper, started cucipop, and everything worked fine. Never tried setting up the db support though... -- Chip Marshall http://www.chocobo.cx/chip/ Finger for PGP GCM/CS d+(-) s+:++ a18>? C++ UB++++$ P+++$ L- E--- W++ N+@ o K- w O M+ V-- PS PE Y? PGP++ t+@ 5 X R>+ tv+() b++>+++ DI++++ D(-) G++ e>++ h!>++ r-- y- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 13:26: 4 2000 Delivered-To: freebsd-isp@freebsd.org Received: from zoe2.qserve.net (zoe2.qserve.net [207.250.219.4]) by hub.freebsd.org (Postfix) with ESMTP id 5722B37BD7B for ; Tue, 30 May 2000 13:25:55 -0700 (PDT) (envelope-from rch@qserve.net) Received: from acidic.qserve.net (acidic.qserve.net [207.250.219.40]) by zoe2.qserve.net (8.10.1/8.10.1) with ESMTP id e4UKRe332598 for ; Tue, 30 May 2000 15:27:40 -0500 (EST) Message-Id: <4.3.1.2.20000530152814.01faa3f0@qserve.net> X-Sender: rch@qserve.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Tue, 30 May 2000 15:33:41 -0500 To: freebsd-isp@FreeBSD.ORG From: Robert Hough Subject: Re: Cucipop port/source In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 04:06 PM 5/30/00 -0400, you wrote: >With yet another QPopper bug, we're thinking of moving to cucipop. I did the same thing yesterday... >-how do you like it? So far, it's been great (The whole 24 hours we've had it running). In fact, it's already proven to me that it's faster under heavier loads. It also seems to be faster if the mail has large file attachments as well. Though, it could just be that "new toy syndrome" I tend to get when I install something with little to no problems in the process. :) >-any gotchas or incompatibilities in your userbase when you made the move? I just replaced the proper lines in my inetd.conf, restarted inetd, and away it went. Haven't had any problems as of yet. >-did you get db support working? No. I got the same error you got. I didn't play with this too much though, as this really didn't seem to add any serious benefits that I needed. All said and done, I think this was a pretty good move on my part, and I'm still wondering why I've allowed qpopper to infest my system for so long. -- Robert Hough (rch@qserve.net) Qserve Internet, Inc. http://www.qserve.net/ Ph: (317)802-3036 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 13:27: 0 2000 Delivered-To: freebsd-isp@freebsd.org Received: from troi.csw.net (troi.csw.net [209.136.192.23]) by hub.freebsd.org (Postfix) with ESMTP id 10F7637B91B for ; Tue, 30 May 2000 13:26:54 -0700 (PDT) (envelope-from lambert@cswnet.com) Received: from ssaos2 (ssaos2.csw.net [209.136.201.13]) by troi.csw.net (8.9.3/8.9.3) with SMTP id PAA06858 for ; Tue, 30 May 2000 15:26:51 -0500 (CDT) (envelope-from lambert@cswnet.com) Message-Id: <200005302026.PAA06858@troi.csw.net> From: lambert@cswnet.com Date: Tue, 30 May 2000 15:24:19 -0500 To: freebsd-isp@FreeBSD.ORG In-Reply-To: <20000530161256.A17694@setzer.chocobo.cx> Subject: Re: Cucipop port/source X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v2.10a c10 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In <20000530161256.A17694@setzer.chocobo.cx>, on 05/30/2000 at 04:12 PM, Chip Marshall said: >On May 30, 2000, spork sent me the following: >> With yet another QPopper bug, we're thinking of moving to cucipop. I have >> a few questions for anyone who may be using it: >> >> -how do you like it? >> -any gotchas or incompatibilities in your userbase when you made the move? >> -did you get db support working? >We switched over to it a while back after we had a break in involving one >of the older versions of qpopper, and it seems to be doing quite well. We >had no problem moving over at all, just killed qpopper, started cucipop, >and everything worked fine. We tried Cucipop on our 3.2-STABLE mail server. It worked until we added a second CPU. At that point Cucipop would work fine for a couple of days and then just quit. We didn't have time to debug it so we just went back to QPopper. I would be interested in hearing from people with SMP systems and Cucipop. -- Scott Lambert lambert@cswnet.com Systems and Security Administrator CSW Net, Inc. ================================================================ Written: Tuesday, May 30, 2000 - 03:24 PM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 13:41: 0 2000 Delivered-To: freebsd-isp@freebsd.org Received: from c1mailgw1.prontomail.com (c1mailgw1.prontomail.com [208.178.29.197]) by hub.freebsd.org (Postfix) with ESMTP id D126837B6DC for ; Tue, 30 May 2000 13:40:58 -0700 (PDT) (envelope-from giffunip@asme.org) Received: from c1mail01.prontomail.com (208.178.29.101) by c1mailgw1.prontomail.com (NPlex 4.5.049) id 39089AB3002F3418 for freebsd-ISP@FreeBSD.org; Tue, 30 May 2000 13:40:54 -0700 Received: by c1mail01.prontomail.com (NPlex 2.0.123); Tue, 30 May 2000 13:40:46 -0700 Received: from 216.252.134.50 by SmtpServer for ; Tue, 30 May 2000 20:35:13 +0000 Message-ID: <39342868.CFAB8C5@asme.org> Date: Tue, 30 May 2000 15:45:29 -0500 From: "Pedro F. Giffuni" Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 4.5 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-ISP@FreeBSD.org Subject: Internet Regulations Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi; I just accepted a consulting job for some people that are preparing the regulations for ISPs in Bolivia. I will rely heavily on what the US and Europe have done up till now, but hopefully I can also include something to help against DOS attacks and the issues that affect the Internet community. If you have links for the proper regulations, or suggestions on how these can be improved I will be very interested to receive them (private email please, I don't want to start a flamewars or neverending threads on the lists). best regards, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 13:53:59 2000 Delivered-To: freebsd-isp@freebsd.org Received: from tusk.mountain-inter.net (tusk.mountain-inter.net [204.244.200.1]) by hub.freebsd.org (Postfix) with ESMTP id 0205C37B53A for ; Tue, 30 May 2000 13:53:56 -0700 (PDT) (envelope-from sreid@sea-to-sky.net) Received: from grok.localnet (unknown@analog27.sq.mntn.net [204.244.200.36]) by tusk.mountain-inter.net (8.10.0/8.10.0) with ESMTP id e4UKrjr14668; Tue, 30 May 2000 13:53:46 -0700 Received: by grok.localnet (Postfix, from userid 1000) id 6873C212E07; Tue, 30 May 2000 13:55:39 -0700 (PDT) Date: Tue, 30 May 2000 13:55:38 -0700 From: Steve Reid To: spork Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source Message-ID: <20000530135538.A1171@grok.localnet> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from spork on Tue, May 30, 2000 at 04:06:58PM -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 30, 2000 at 04:06:58PM -0400, spork wrote: > With yet another QPopper bug, we're thinking of moving to cucipop. I have > a few questions for anyone who may be using it: If security is your concern, consider popa3d by Solar Designer. Security is stated as the primary design goal. /usr/ports/mail/popa3d and http://www.openwall.com/popa3d/ Unfortunately it is feature-limited. Now if we could just find an attractive IMAP server... :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 14: 5:44 2000 Delivered-To: freebsd-isp@freebsd.org Received: from aspenworks.com (netdev.aspenworks.com [192.94.236.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B57737B766 for ; Tue, 30 May 2000 14:05:39 -0700 (PDT) (envelope-from alex@aspenworks.com) Received: from aspenworks.com (s29-g-lv4.sopris.net [208.47.129.189]) by aspenworks.com (8.9.3/8.9.3) with ESMTP id PAA38222; Tue, 30 May 2000 15:05:25 -0600 (MDT) (envelope-from alex@aspenworks.com) Message-ID: <39342CFC.7065E720@aspenworks.com> Date: Tue, 30 May 2000 15:05:00 -0600 From: Alex Reply-To: alex@aspenworks.com X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Robert Hough Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source References: <4.3.1.2.20000530152814.01faa3f0@qserve.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert, It is faster. cucipop does not copy the mail file to a tmp file like qpopper does. The trade off to consider is that cucipop will not re-synch after abnormal disconnects as well qpopper does. It appears that the temp file qpopper uses keeps better track of the individual mail messages downloaded. I settled on cucipop for speed once our system needed to support more than 2,000 mailboxes. We never did much with DB files, but the control aspects of cucipop turned out easier to manage. -Alex Robert Hough wrote: > > At 04:06 PM 5/30/00 -0400, you wrote: > >With yet another QPopper bug, we're thinking of moving to cucipop. > > I did the same thing yesterday... > > >-how do you like it? > > So far, it's been great (The whole 24 hours we've had it running). In fact, > it's already proven to me that it's faster under heavier loads. It also > seems to be faster if the mail has large file attachments as well. Though, > it could just be that "new toy syndrome" I tend to get when I install > something with little to no problems in the process. :) > > >-any gotchas or incompatibilities in your userbase when you made the move? > > I just replaced the proper lines in my inetd.conf, restarted inetd, and > away it went. Haven't had any problems as of yet. > > >-did you get db support working? > > No. I got the same error you got. I didn't play with this too much though, > as this really didn't seem to add any serious benefits that I needed. > > All said and done, I think this was a pretty good move on my part, and I'm > still wondering why I've allowed qpopper to infest my system for so long. > > -- > Robert Hough (rch@qserve.net) Qserve Internet, Inc. > http://www.qserve.net/ Ph: (317)802-3036 > > 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 Tue May 30 14:28:57 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.ahnet.net (mail.ahnet.net [207.213.224.25]) by hub.freebsd.org (Postfix) with ESMTP id A757D37BE3A for ; Tue, 30 May 2000 14:28:55 -0700 (PDT) (envelope-from sumbry@affinity.net) Received: from sql.ahnet.net (control.ahnet.net [207.213.224.10]) by mail.ahnet.net (Postfix) with ESMTP id 4599B5EED; Tue, 30 May 2000 14:23:36 -0700 (PDT) Date: Tue, 30 May 2000 14:23:36 -0700 (PDT) From: "Sumbry][" X-Sender: sumbry@sql.ahnet.net To: Robert Hough Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source In-Reply-To: <4.3.1.2.20000530152814.01faa3f0@qserve.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 > I just replaced the proper lines in my inetd.conf, restarted inetd, and > away it went. Haven't had any problems as of yet. You'll get much better performance with Cucipop if you remove it from inetd, and let it run in Standalone mode. We use cucipop here, with about 30k POP users, and it performs wonderfully. We've used it for over a year now, under FreeBSD 3.3 w/no problems at all. Granted, we skipped compiling in the db support as well. Not really needed. ----- Sumbry][ | Affinity Internet Inc | http://affinity.net | sumbry@affinity.net I'll believe psychics when one phones me, just in the nick of time, yelling, "Duck!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 14:29:20 2000 Delivered-To: freebsd-isp@freebsd.org Received: from laf.cioe.com (laf.cioe.com [204.120.165.33]) by hub.freebsd.org (Postfix) with ESMTP id B4CD537BE3F for ; Tue, 30 May 2000 14:29:09 -0700 (PDT) (envelope-from steve@ns1.cioe.com) Received: from ny1wsh031 (blackhole.cioe.com [204.120.165.44]) by laf.cioe.com (8.9.3/8.9.3) with SMTP id QAA63254; Tue, 30 May 2000 16:28:38 -0500 (EST) (envelope-from steve@ns1.cioe.com) Message-ID: <070f01bfca7e$040f39e0$851a050a@winstar.com> From: "Steven E. Ames" To: "Steve Reid" , "spork" Cc: References: <20000530135538.A1171@grok.localnet> Subject: Re: Cucipop port/source Date: Tue, 30 May 2000 16:28:33 -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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Isn't 'cucipop' commercial? I remember trying it once and seeing a $200 registration fee... or I could have been offending the sleep gods at that point and just hallucinated it? -Steve ----- Original Message ----- From: "Steve Reid" To: "spork" Cc: Sent: Tuesday, May 30, 2000 3:55 PM Subject: Re: Cucipop port/source > On Tue, May 30, 2000 at 04:06:58PM -0400, spork wrote: > > With yet another QPopper bug, we're thinking of moving to cucipop. I have > > a few questions for anyone who may be using it: > > If security is your concern, consider popa3d by Solar Designer. Security > is stated as the primary design goal. /usr/ports/mail/popa3d and > http://www.openwall.com/popa3d/ > > Unfortunately it is feature-limited. > > > Now if we could just find an attractive IMAP server... :( > > > > 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 Tue May 30 14:30:27 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.ahnet.net (mail.ahnet.net [207.213.224.25]) by hub.freebsd.org (Postfix) with ESMTP id AEA9C37BC51 for ; Tue, 30 May 2000 14:30:25 -0700 (PDT) (envelope-from sumbry@affinity.net) Received: from sql.ahnet.net (control.ahnet.net [207.213.224.10]) by mail.ahnet.net (Postfix) with ESMTP id E4E295ECA; Tue, 30 May 2000 14:25:10 -0700 (PDT) Date: Tue, 30 May 2000 14:25:11 -0700 (PDT) From: "Sumbry][" X-Sender: sumbry@sql.ahnet.net To: lambert@cswnet.com Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source In-Reply-To: <200005302026.PAA06858@troi.csw.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 > We tried Cucipop on our 3.2-STABLE mail server. It worked until we added > a second CPU. At that point Cucipop would work fine for a couple of days > and then just quit. We didn't have time to debug it so we just went back > to QPopper. > > I would be interested in hearing from people with SMP systems and Cucipop. Re my previous message, we also are running cucipop on a Dual P3 processor box, running 3.3. No problems at all. ----- Sumbry][ | Affinity Internet Inc | http://affinity.net | sumbry@affinity.net I'll believe psychics when one phones me, just in the nick of time, yelling, "Duck!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 14:45:50 2000 Delivered-To: freebsd-isp@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 3E00F37B61B for ; Tue, 30 May 2000 14:45:46 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 4B38FB423; Tue, 30 May 2000 17:45:45 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 32E36B422; Tue, 30 May 2000 17:45:45 -0400 (EDT) Date: Tue, 30 May 2000 17:45:45 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Steven E. Ames" Cc: Steve Reid , freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source In-Reply-To: <070f01bfca7e$040f39e0$851a050a@winstar.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 That's a good question, the license is a bit dodgy, so I've emailed the author. He requests you apply the following formula to determine cost: US$ 200 * ( 1 - ( 0.995 ^ N ) ) Where "N" is the number of users. If you do this, you get subscribed to a list with patches, announcements, etc... I'll post back the reply I get from the author. Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On Tue, 30 May 2000, Steven E. Ames wrote: > Isn't 'cucipop' commercial? I remember trying it once and seeing a $200 > registration fee... or I could have been offending the sleep gods at > that point and just hallucinated it? > > -Steve > > ----- Original Message ----- > From: "Steve Reid" > To: "spork" > Cc: > Sent: Tuesday, May 30, 2000 3:55 PM > Subject: Re: Cucipop port/source > > > > On Tue, May 30, 2000 at 04:06:58PM -0400, spork wrote: > > > With yet another QPopper bug, we're thinking of moving to cucipop. > I have > > > a few questions for anyone who may be using it: > > > > If security is your concern, consider popa3d by Solar Designer. > Security > > is stated as the primary design goal. /usr/ports/mail/popa3d and > > http://www.openwall.com/popa3d/ > > > > Unfortunately it is feature-limited. > > > > > > Now if we could just find an attractive IMAP server... :( > > > > > > > > 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 Tue May 30 14:46:14 2000 Delivered-To: freebsd-isp@freebsd.org Received: from epsilon.lucida.qc.ca (epsilon.lucida.qc.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id DE05537B57F for ; Tue, 30 May 2000 14:46:10 -0700 (PDT) (envelope-from matt@ARPA.MAIL.NET) Received: (qmail 3666 invoked by uid 1000); 30 May 2000 21:46:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 May 2000 21:46:09 -0000 Date: Tue, 30 May 2000 17:46:06 -0400 (EDT) From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: FreeBSD-ISP Subject: Re: Cucipop port/source Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I as well switched to cucipop after the qpopper nonesense. I'm quite happy with it, for my situation it was a straight drop in replacement. I do not require the function of it's database handlings though, just simple pop3. I only server approximately 200 users, but it runs great nonetheless. I am more impressed by the 24 Kbyte size of the binary. You can tell that it is not loaded with bloat/hard to audit code. Regards, Matt Heckaman matt@arpa.mail.net http://www.lucida.qc.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE5NDahdMMtMcA1U5ARAm5XAKCCZ11/gfgb+a/h4Acvgn0YKZ9DpwCgpMcL Omfj1W0ULykq7a8r8TrBB4Y= =ynRb -----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 Tue May 30 15:43:46 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id A330A37B912 for ; Tue, 30 May 2000 15:43:40 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id RAA31941; Tue, 30 May 2000 17:43:35 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <000c01bfca88$7da08ca0$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "spork" Cc: References: Subject: Re: Apache modssl fp Help Date: Tue, 30 May 2000 17:43:35 -0500 Organization: West Bend Internet 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 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "spork" > A quick question on frontpage... I seem to recall that the ports use the > bsdi version of frontpage. Looking at the distro site, there now appears > to be a freebsd version. So far I've had little luck with their install > script, as it's from '98 and does not seem to include FreeBSD as a > platform... Anyone else given this a spin? > Currently, the port uses the BSDI port, but I have a patch that will be changing it to use the FreeBSD FP exts. There is a small problem with the FreeBSD FP exts. If you have your crypt library linked to the scrypt library ( libcrypt -> libscrypt), then fpsrvadm.exe creates an invalid MD5 password. I believe this problem is because fpsrvadm.exe doesn't allocate a large enough buffer in order to store the encrypted password. This means that the FreeBSD FP exts will only work on a system that has libcrypt -> libdescrypt. For those that have libcrypt -> libscrypt, they would still need to use the BSDI FP exts, and make sure that libdescrypt.a is compiled into the apache server. I informed RTR of the problem, and hopefully they will be able to provide a fix. 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 30 15:47:54 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id E463637B912 for ; Tue, 30 May 2000 15:47:48 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id RAA32022; Tue, 30 May 2000 17:47:46 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <001301bfca89$12e08ea0$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Bryan Bursey" Cc: References: Subject: Re: Apache modssl fp Help Date: Tue, 30 May 2000 17:47:46 -0500 Organization: West Bend Internet 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 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "Bryan Bursey" > > > Try the FreeBSD Apache ports collection at: > > > > > > http://www.westbend.net/~hetzels/mod_apache13.tgz > > > > > What an excellent tool... and one I've been wishing for since finding the > _nearly_ complete script with the apache13+mod_php3 port. When can we > expect to see this tarball unleased into the 'official' FreeBSD ports > collection? > I have already submitted it as a problem report, so hopefully it will be included in the next FreeBSD release. 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 30 16:15:34 2000 Delivered-To: freebsd-isp@freebsd.org Received: from tigger.key.co.za (tigger.key.co.za [196.2.147.10]) by hub.freebsd.org (Postfix) with ESMTP id 5265737BE20 for ; Tue, 30 May 2000 16:14:53 -0700 (PDT) (envelope-from peter@tigger.key.co.za) Received: from peter (helo=localhost) by tigger.key.co.za with local-esmtp (Exim 3.14 #1) id 12wvCi-0002l7-00; Wed, 31 May 2000 01:13:44 +0200 Date: Wed, 31 May 2000 01:13:44 +0200 (SAST) From: Peter Lockhart To: Alex Cc: Robert Hough , freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source In-Reply-To: <39342CFC.7065E720@aspenworks.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 Tue, 30 May 2000, Alex wrote: > Robert, > > It is faster. cucipop does not copy the mail file to a tmp file like > qpopper does. The trade off to consider is that cucipop will not > re-synch after abnormal disconnects as well qpopper does. It appears > that the temp file qpopper uses keeps better track of the individual > mail messages downloaded. I actually switched from cucipop to qpopper for this reason. It was becoming a hassle having clients complain of duplicate mails being recieved. The reasons seeming to be mail clients not issuing disconnects properly (all Outlook) and hence cucipop not removing them. Also, mysql patches are available for qpopper :) Cheers Peter Lockhart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Tue May 30 19:32:59 2000 Delivered-To: freebsd-isp@freebsd.org Received: from enya.clari.net.au (enya.clari.net.au [203.8.14.116]) by hub.freebsd.org (Postfix) with ESMTP id 714EA37B7BC for ; Tue, 30 May 2000 19:32:55 -0700 (PDT) (envelope-from danny@freebsd.org) Received: from localhost (danny@localhost) by enya.clari.net.au (8.9.2/8.9.1) with ESMTP id MAA15661 for ; Wed, 31 May 2000 12:32:51 +1000 (EST) (envelope-from danny@freebsd.org) X-Authentication-Warning: enya.clari.net.au: danny owned process doing -bs Date: Wed, 31 May 2000 12:32:51 +1000 (EST) From: "Daniel O'Callaghan" X-Sender: danny@enya.clari.net.au To: freebsd-isp@freebsd.org Subject: Austrian ISP wanted 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 Could Austrian ISPs who are willing to sign up 3 people for 1 month or so, please contact me as soon as possible. Thanks Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 1: 5:57 2000 Delivered-To: freebsd-isp@freebsd.org Received: from net-tech.com.au (redback.net-tech.com.au [203.87.28.11]) by hub.freebsd.org (Postfix) with SMTP id 8EAD037B7D1 for ; Wed, 31 May 2000 01:05:52 -0700 (PDT) (envelope-from corey@net-tech.com.au) Received: (qmail 95232 invoked by uid 71); 25 May 2000 08:17:59 -0000 Received: from unknown (HELO coreyx.net-tech.com.au) (203.36.214.208) by 203.87.28.11 with SMTP; 25 May 2000 08:17:59 -0000 Received: from corey by coreyx.net-tech.com.au with local (Exim 3.12 #1 (Debian)) id 12uspJ-0000hp-00 for ; Thu, 25 May 2000 18:17:09 +1000 Date: Thu, 25 May 2000 18:17:09 +1000 To: freebsd-isp@freebsd.org Subject: Using radius to NT server? Message-ID: <20000525181709.C2615@coreyx.net-tech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i From: Corey Ralph Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I am attempting to set up a freebsd 4.0 box for a ppp dialin server. I am using mgetty and pppd 2.3.10 with the radius patch. The problem is with the radius. Our radius server is NT, it doesn't seem to respond. pppd is reporting 'RADIUS: No valid RADIUS responses recieved'. Possibly a compatibility issue? I have been told that there is something non-standard in the NT radius server, our 3com boxes need to be configured differently to use it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 4:44: 1 2000 Delivered-To: freebsd-isp@freebsd.org Received: from durango.picus.com (durango.picus.com [209.100.20.19]) by hub.freebsd.org (Postfix) with ESMTP id 1FF3F37B751 for ; Wed, 31 May 2000 04:43:58 -0700 (PDT) (envelope-from troy@picus.com) Received: from abyss [209.100.22.250] by durango.picus.com (SMTPD32-5.05) id AAA14050214; Wed, 31 May 2000 07:42:25 -0400 From: "Troy Settle" To: "Corey Ralph" , Subject: RE: Using radius to NT server? Date: Wed, 31 May 2000 07:43:07 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <20000525181709.C2615@coreyx.net-tech.com.au> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Corey, You're not alone here. A few days ago, I tried enabling pam_radius for authentication on 4.0-STABLE, but had 0 luck with it. I got the same errors: No valid RADIUS response recieved. Rather frustrating when I run Radius in debug mode, and *never* even see the connection coming in. I just chalked it up to either PAM or the Radius module not being quite ready for production and moved on to other stuff. -- Troy Settle Network Analyst Picus Communications 540.633.6327 ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Corey Ralph ** Sent: Thursday, May 25, 2000 4:17 AM ** To: freebsd-isp@freebsd.org ** Subject: Using radius to NT server? ** ** ** Hi. ** ** I am attempting to set up a freebsd 4.0 box for a ppp dialin ** server. I am ** using mgetty and pppd 2.3.10 with the radius patch. ** ** The problem is with the radius. Our radius server is NT, it ** doesn't seem to ** respond. ** ** pppd is reporting 'RADIUS: No valid RADIUS responses recieved'. ** ** Possibly a compatibility issue? I have been told that there ** is something ** non-standard in the NT radius server, our 3com boxes need to ** be configured ** differently to use it. ** ** ** 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 Wed May 31 7:41:36 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.wzrd.com (mail.wzrd.com [206.99.165.3]) by hub.freebsd.org (Postfix) with ESMTP id 607EA37BC60 for ; Wed, 31 May 2000 07:41:34 -0700 (PDT) (envelope-from danh@wzrd.com) Received: by mail.wzrd.com (Postfix, from userid 91) id B63175D015; Wed, 31 May 2000 10:41:32 -0400 (EDT) Date: Wed, 31 May 2000 10:41:32 -0400 From: Dan Harnett To: Corey Ralph Cc: freebsd-isp@freebsd.org Subject: Re: Using radius to NT server? Message-ID: <20000531104132.A2010@mail.wzrd.com> References: <20000525181709.C2615@coreyx.net-tech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000525181709.C2615@coreyx.net-tech.com.au>; from corey@net-tech.com.au on Thu, May 25, 2000 at 06:17:09PM +1000 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, On Thu, May 25, 2000 at 06:17:09PM +1000, Corey Ralph wrote: > Hi. > > I am attempting to set up a freebsd 4.0 box for a ppp dialin server. I am > using mgetty and pppd 2.3.10 with the radius patch. > > The problem is with the radius. Our radius server is NT, it doesn't seem to > respond. > > pppd is reporting 'RADIUS: No valid RADIUS responses recieved'. > > Possibly a compatibility issue? I have been told that there is something > non-standard in the NT radius server, our 3com boxes need to be configured > differently to use it. > You might want to check what port the radius server is listening on. By default, FreeBSD uses the port defined in the RFC, udp port 1812. A lot of equipment and vendors use a non-standard port, usually 1645. Take a look at radius.conf(5) for how to make use of it. -- Dan Harnett Wizard Communication Systems, Inc. Email: danh@wzrd.com 2 Main Street Phone: (716) 743-0091 Tonawanda, NY 14150 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 7:43:36 2000 Delivered-To: freebsd-isp@freebsd.org Received: from galt.slap.net (galt.slap.net [206.123.11.197]) by hub.freebsd.org (Postfix) with ESMTP id 633D537BE40 for ; Wed, 31 May 2000 07:43:29 -0700 (PDT) (envelope-from wlloyd@galt.slap.net) Received: (from wlloyd@localhost) by galt.slap.net (8.9.3/8.9.3) id KAA14308; Wed, 31 May 2000 10:42:53 -0400 (EDT) (envelope-from wlloyd) Date: Wed, 31 May 2000 10:42:53 -0400 From: William Lloyd To: Troy Settle Cc: Corey Ralph , freebsd-isp@FreeBSD.ORG Subject: Re: Using radius to NT server? Message-ID: <20000531104253.C12953@galt.slap.net> References: <20000525181709.C2615@coreyx.net-tech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from troy@picus.com on Wed, May 31, 2000 at 07:43:07 -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Troy! On Wed, 31 May 2000, Troy Settle wrote: > > Corey, > > You're not alone here. A few days ago, I tried enabling pam_radius for > authentication on 4.0-STABLE, but had 0 luck with it. I got the same > errors: No valid RADIUS response recieved. Rather frustrating when I run > Radius in debug mode, and *never* even see the connection coming in. > > I just chalked it up to either PAM or the Radius module not being quite > ready for production and moved on to other stuff. > I've not tried it with a NT radius server but the pam_radius stuff requires that a full user account be setup on the freebsd box. The pam_radius module will ignore the password part of the account and verify against the other (in your case NT) radius box. Don't think of it as a replacement for NIS/YP in this case. You might check the TCP port that radius is using. Different radius servers seem to use different default ports. I think Livingston changed the radius default port somewhere along the line a while back. -bill -- William Lloyd mailto:wlloyd@slap.net | No stuff here To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 7:51:38 2000 Delivered-To: freebsd-isp@freebsd.org Received: from durango.picus.com (durango.picus.com [209.100.20.19]) by hub.freebsd.org (Postfix) with ESMTP id 7F60B37B6B3 for ; Wed, 31 May 2000 07:51:34 -0700 (PDT) (envelope-from troy@picus.com) Received: from arcadia [209.100.20.198] by durango.picus.com (SMTPD32-5.05) id A69AA20208; Wed, 31 May 2000 10:50:02 -0400 From: "Troy Settle" To: "William Lloyd" Cc: "Corey Ralph" , Subject: RE: Using radius to NT server? Date: Wed, 31 May 2000 10:54:07 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <20000531104253.C12953@galt.slap.net> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** I've not tried it with a NT radius server but the pam_radius ** stuff requires ** that a full user account be setup on the freebsd box. The pam_radius ** module will ignore the password part of the account and verify against ** the other (in your case NT) radius box. ** ** Don't think of it as a replacement for NIS/YP in this case. I really wish it was a complete replacement for NIS/YP and/or the passwd file, but I accept these limitations for now. ** ** You might check the TCP port that radius is using. Different ** radius servers ** seem to use different default ports. I think Livingston changed ** the radius ** default port somewhere along the line a while back. The entry in /etc/radius.conf looks like this: auth 192.168.10.2:1645 secret It's correct according to the docs, and matches up with what 60 or so NAS are using :) Thanks, -Troy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 8:19:46 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.bfm.org (mail.bfm.org [216.127.218.26]) by hub.freebsd.org (Postfix) with ESMTP id 6024937BE97 for ; Wed, 31 May 2000 08:19:40 -0700 (PDT) (envelope-from Ryugen@palaver.org) Received: from primo.bfm.org ([216.127.218.20]) by mail.bfm.org (Post.Office MTA v3.5.3 release 223 ID# 0-52399U2500L250S0V35) with SMTP id org for ; Wed, 31 May 2000 10:20:42 -0500 Received: from porta-pad.palaver.org (unverified [24.217.51.231]) by primo.bfm.org (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 31 May 2000 10:19:37 -0500 Message-Id: <4.3.1.2.20000531101912.00a98a10@mail.palaver.org> X-Sender: rfisher@mail.palaver.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 31 May 2000 10:19:33 -0500 To: Dan Harnett From: Ryugen@palaver.org (Ryugen C. Fisher) Subject: Re: Using radius to NT server? Cc: Corey Ralph , freebsd-isp@freebsd.org In-Reply-To: <20000531104132.A2010@mail.wzrd.com> References: <20000525181709.C2615@coreyx.net-tech.com.au> <20000525181709.C2615@coreyx.net-tech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org IIRC the port 1645 for Radius is the port that is used by Livingston for there Portmaster Routers, etc. Livingston (now a div of AT&T) is the shop where Radius was first drafted, written and implemented. As a result most "older" radius software and hardware use the 1645 port... I have not read the RFC and would frankly be curious as to how the port got changed from the "factory' spec to port 1812. At 09:41 AM 5/31/00, Dan Harnett wrote: >Hello, > >On Thu, May 25, 2000 at 06:17:09PM +1000, Corey Ralph wrote: > > Hi. > > > > I am attempting to set up a freebsd 4.0 box for a ppp dialin server. I am > > using mgetty and pppd 2.3.10 with the radius patch. > > > > The problem is with the radius. Our radius server is NT, it doesn't > seem to > > respond. > > > > pppd is reporting 'RADIUS: No valid RADIUS responses recieved'. > > > > Possibly a compatibility issue? I have been told that there is something > > non-standard in the NT radius server, our 3com boxes need to be configured > > differently to use it. > > > >You might want to check what port the radius server is listening on. By >default, FreeBSD uses the port defined in the RFC, udp port 1812. A lot of >equipment and vendors use a non-standard port, usually 1645. Take a look at >radius.conf(5) for how to make use of it. > >-- > Dan Harnett Wizard Communication Systems, > Inc. > Email: danh@wzrd.com 2 Main Street > Phone: (716) 743-0091 Tonawanda, NY 14150 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message Ryugen, that "Old Frog" hisself Ryugen@palaver.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 8:30:16 2000 Delivered-To: freebsd-isp@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 8B63837BE87 for ; Wed, 31 May 2000 08:30:09 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.af.speednet.com.au (andyf@backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id BAA93220; Thu, 1 Jun 2000 01:29:44 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Thu, 1 Jun 2000 01:29:43 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Dan Harnett Cc: Corey Ralph , freebsd-isp@FreeBSD.ORG Subject: Re: Using radius to NT server? In-Reply-To: <20000531104132.A2010@mail.wzrd.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, 31 May 2000, Dan Harnett wrote: > You might want to check what port the radius server is listening on. By > default, FreeBSD uses the port defined in the RFC, udp port 1812. A lot of > equipment and vendors use a non-standard port, usually 1645. Take a look at > radius.conf(5) for how to make use of it. See also /etc/services, which says: # IMPORTANT NOTE: Ports 1645/1646 are the traditional radius ports used by # many vendors without obtaining official IANA assignment. The official # assignment is now ports 1812/1813 and users are encouraged to migrate # when possible to these new ports. #radius 1645/udp #RADIUS authentication protocol (old) #radacct 1646/udp #RADIUS accounting pcotocol (old) > > -- > Dan Harnett Wizard Communication Systems, Inc. > Email: danh@wzrd.com 2 Main Street > Phone: (716) 743-0091 Tonawanda, NY 14150 > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 8:30:52 2000 Delivered-To: freebsd-isp@freebsd.org Received: from durango.picus.com (durango.picus.com [209.100.20.19]) by hub.freebsd.org (Postfix) with ESMTP id 1E07437BEAB for ; Wed, 31 May 2000 08:30:41 -0700 (PDT) (envelope-from troy@picus.com) Received: from arcadia [209.100.20.198] by durango.picus.com (SMTPD32-5.05) id AFC515F0208; Wed, 31 May 2000 11:29:09 -0400 From: "Troy Settle" To: "Ryugen C. Fisher" , "Dan Harnett" Cc: "Corey Ralph" , Subject: RE: Using radius to NT server? Date: Wed, 31 May 2000 11:33:14 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <4.3.1.2.20000531101912.00a98a10@mail.palaver.org> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** IIRC the port 1645 for Radius is the port that is used by Livingston for ** there Portmaster Routers, etc. Livingston (now a div of AT&T) is Livingston was borged by Lucent, not AT&T. Lucent was spun from AT&T after the breakup (IIRC). ** the shop ** where Radius was first drafted, written and implemented. As a ** result most ** "older" radius software and hardware use the 1645 port... I ** have not read ** the RFC and would frankly be curious as to how the port got changed from ** the "factory' spec to port 1812. Livingston used 1645/1646 because they thought those ports were availiable. In reality, those ports were reserved for some obscure service. When the IETF(?) got ahold of the Radius RFC, they found a pair of ports more suitable for the application. 1812/1813. -Troy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 9: 2:14 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.bfm.org (mail.bfm.org [216.127.218.26]) by hub.freebsd.org (Postfix) with ESMTP id 24B0A37BDE6 for ; Wed, 31 May 2000 09:02:11 -0700 (PDT) (envelope-from Ryugen@palaver.org) Received: from primo.bfm.org ([216.127.218.20]) by mail.bfm.org (Post.Office MTA v3.5.3 release 223 ID# 0-52399U2500L250S0V35) with SMTP id org for ; Wed, 31 May 2000 11:03:12 -0500 Received: from porta-pad.palaver.org (unverified [24.217.51.231]) by primo.bfm.org (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 31 May 2000 11:02:03 -0500 Message-Id: <4.3.1.2.20000531110133.00a9c310@mail.palaver.org> X-Sender: rfisher@mail.palaver.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 31 May 2000 11:01:57 -0500 To: "Troy Settle" From: Ryugen@palaver.org (Ryugen C. Fisher) Subject: RE: Using radius to NT server? Cc: "Dan Harnett" , "Corey Ralph" , In-Reply-To: References: <4.3.1.2.20000531101912.00a98a10@mail.palaver.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ah... I probably need a firmware upgrade... I can't remember if Lucent was AT&T's child at the time they bought Livingston and Ascend, or whether they were split before the purchase(s).. thanks you all for the update on why the ports were changed... At 10:33 AM 5/31/00, Troy Settle wrote: >** IIRC the port 1645 for Radius is the port that is used by Livingston for >** there Portmaster Routers, etc. Livingston (now a div of AT&T) is > >Livingston was borged by Lucent, not AT&T. Lucent was spun from AT&T after >the breakup (IIRC). > >** the shop >** where Radius was first drafted, written and implemented. As a >** result most >** "older" radius software and hardware use the 1645 port... I >** have not read >** the RFC and would frankly be curious as to how the port got changed from >** the "factory' spec to port 1812. > >Livingston used 1645/1646 because they thought those ports were availiable. >In reality, those ports were reserved for some obscure service. When the >IETF(?) got ahold of the Radius RFC, they found a pair of ports more >suitable for the application. 1812/1813. > >-Troy Ryugen, that "Old Frog" hisself Ryugen@palaver.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 14: 5:18 2000 Delivered-To: freebsd-isp@freebsd.org Received: from hindenburg.eboai.org (hindenburg.eboai.org [205.181.254.190]) by hub.freebsd.org (Postfix) with ESMTP id 9859337B77F for ; Wed, 31 May 2000 14:05:14 -0700 (PDT) (envelope-from chip@chocobo.cx) Received: by hindenburg.eboai.org (Postfix, from userid 1000) id C168B3D5D; Wed, 31 May 2000 17:05:08 -0400 (EDT) Date: Wed, 31 May 2000 17:05:08 -0400 From: Chip Marshall To: freebsd-isp@freebsd.org Subject: DigiBoard AccelePort Xr Message-ID: <20000531170508.A31302@setzer.chocobo.cx> Reply-To: chip@chocobo.cx Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i X-URL: http://www.chocobo.cx/chip/ X-OS: FreeBSD 3.4-RELEASE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a DigiBoard AccelePort Xr (8-port PCI version) that I would like to start using to do some PPP dial-in service. Is anyone using these cards in a FreeBSD box? Are they supported at all? I can't seem to tell what cards are and are not supported under the dgb driver. Thanks in advance. -- Chip Marshall http://www.chocobo.cx/chip/ Finger for PGP GCM/CS d+(-) s+:++ a18>? C++ UB++++$ P+++$ L- E--- W++ N+@ o K- w O M+ V-- PS PE Y? PGP++ t+@ 5 X R>+ tv+() b++>+++ DI++++ D(-) G++ e>++ h!>++ r-- y- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 14:48:14 2000 Delivered-To: freebsd-isp@freebsd.org Received: from priv-edtnes11-hme0.telusplanet.net (edtnes11.telus.net [199.185.220.111]) by hub.freebsd.org (Postfix) with ESMTP id 304D037B917 for ; Wed, 31 May 2000 14:48:13 -0700 (PDT) (envelope-from james@aspert.com) Received: from james ([209.53.43.91]) by priv-edtnes11-hme0.telusplanet.net (InterMail vM.4.01.02.11 201-229-116-111) with SMTP id <20000531214807.SIBN625.priv-edtnes11-hme0.telusplanet.net@james> for ; Wed, 31 May 2000 15:48:07 -0600 Message-ID: <00e601bfcb49$c45020e0$5b2b35d1@aspert.com> From: "James A. Peltier" To: Subject: cucipop Date: Wed, 31 May 2000 14:47:06 -0700 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 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone using cucipop with the APOP functionality.. if so what software are you using for e-mail? - James A. Peltier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Wed May 31 16:19:11 2000 Delivered-To: freebsd-isp@freebsd.org Received: from net-tech.com.au (redback.net-tech.com.au [203.87.28.11]) by hub.freebsd.org (Postfix) with SMTP id 401CF37B852 for ; Wed, 31 May 2000 16:19:07 -0700 (PDT) (envelope-from corey@net-tech.com.au) Received: (qmail 73286 invoked by uid 71); 31 May 2000 23:24:34 -0000 Received: from unknown (HELO coreyx.net-tech.com.au) (203.36.214.208) by 203.87.28.11 with SMTP; 31 May 2000 23:24:34 -0000 Received: from corey by coreyx.net-tech.com.au with local (Exim 3.12 #1 (Debian)) id 12xHok-0002Ux-00 for ; Thu, 01 Jun 2000 09:22:30 +1000 Date: Thu, 1 Jun 2000 09:22:30 +1000 To: freebsd-isp@freebsd.org Subject: Re: Using radius to NT server? Message-ID: <20000601092230.A9532@coreyx.net-tech.com.au> References: <20000525181709.C2615@coreyx.net-tech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: ; from tim@spanner.net on Wed, May 31, 2000 at 09:13:50PM +1000 From: Corey Ralph Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks everyone for your help. Just to clarify, the 3com boxes are the 56k systems, this is for a 33k. From what I've read elsewhere, the NT radius server uses non-standard encryption so probably isn't supported in libradius. I ended up setting up cistron radiusd on another box, and with pam_smb got it to authenticate off the nt domain. I then made a perl script to convert its logs to the same format as the nt ones to work it into our billing software. It is much more powerful anyway, makes it easier to do static ip's etc. Cheers. On Wed, May 31, 2000 at 09:13:50PM +1000, Tim Kent wrote: > If you have 3Com terminal servers, why are you using pppd? > Shouldn't the request be passed directly to the NT box? > > Tim > > On Thu, 25 May 2000, Corey Ralph wrote: > > > Hi. > > > > I am attempting to set up a freebsd 4.0 box for a ppp dialin server. I am > > using mgetty and pppd 2.3.10 with the radius patch. > > > > The problem is with the radius. Our radius server is NT, it doesn't seem to > > respond. > > > > pppd is reporting 'RADIUS: No valid RADIUS responses recieved'. > > > > Possibly a compatibility issue? I have been told that there is something > > non-standard in the NT radius server, our 3com boxes need to be configured > > differently to use it. > > > > > > 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 Thu Jun 1 1:18:40 2000 Delivered-To: freebsd-isp@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 6747937B557 for ; Thu, 1 Jun 2000 01:18:36 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA94347; Thu, 1 Jun 2000 09:20:04 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA27169; Thu, 1 Jun 2000 09:19:59 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006010819.JAA27169@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: chip@chocobo.cx Cc: freebsd-isp@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: DigiBoard AccelePort Xr In-Reply-To: Message from Chip Marshall of "Wed, 31 May 2000 17:05:08 EDT." <20000531170508.A31302@setzer.chocobo.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jun 2000 09:19:59 +0100 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a DigiBoard AccelePort Xr (8-port PCI version) that I would > like to start using to do some PPP dial-in service. Is anyone using > these cards in a FreeBSD box? Are they supported at all? I can't seem > to tell what cards are and are not supported under the dgb driver. I'm in the process of getting a ``digi'' driver up & running. It'll do the PC/Xr ASIC and PLX cards. I don't believe any PCI digiboards are supported at the moment. > Thanks in advance. > > -- > Chip Marshall http://www.chocobo.cx/chip/ Finger for PGP > GCM/CS d+(-) s+:++ a18>? C++ UB++++$ P+++$ L- E--- W++ N+@ o K- w O M+ V-- > PS PE Y? PGP++ t+@ 5 X R>+ tv+() b++>+++ DI++++ D(-) G++ e>++ h!>++ r-- y- -- 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 Jun 1 10:22:22 2000 Delivered-To: freebsd-isp@freebsd.org Received: from MexComUSA.Net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 5EBBD37BEC3 for ; Thu, 1 Jun 2000 10:22:18 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from EnContacto.Net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by MexComUSA.Net (8.9.3/8.9.3) with ESMTP id KAA48409; Thu, 1 Jun 2000 10:21:35 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Message-ID: <39369B9F.73945132@EnContacto.Net> Date: Thu, 01 Jun 2000 10:21:35 -0700 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Landry Cc: Josef Grosch , David Perez Marfil , "'freebsd-isp@FreeBSD.ORG'" Subject: Re: Alternate solution to Verisign References: <20000529082444.A6984@mooseriver.com> <20000530125940.A37609@bigu.msen.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This seems to be the best. I'm going to give it a try. They are still advertising the $45 promotion. I'm going to see if we can take advantange of it. Thanks, ed Matthew Landry wrote: > > Thawte just got bought by Verisign. > "Just" is probably the wrong word...they've been owned by VeriSign > for a while now. > Equifax seems to be the best deal currently. The $45 promotion is > over, but their regular $75/yr rate is still better than anyone else we've > seen. > -- > Matthew Landry O- > LEL Network Services > > 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 Thu Jun 1 10:46:16 2000 Delivered-To: freebsd-isp@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 6EF9337B6D4 for ; Thu, 1 Jun 2000 10:46:10 -0700 (PDT) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id 4C35EB423; Thu, 1 Jun 2000 13:46:09 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 3617EB422; Thu, 1 Jun 2000 13:46:09 -0400 (EDT) Date: Thu, 1 Jun 2000 13:46:09 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Sumbry][" Cc: lambert@cswnet.com, freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source 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 I just gave cucipop a quick trial and it just about cut the load on the machine in half. Response in my pop client was quite zippy. I did run into a few problems, the most annoying being the difference in UIDLs returned between Qpopper and cucipop: cucipop - UIDL 1 +OK 1 982b3d94590d0000 Qpopper - uidl 1 +OK 1 7717bd7ef97667003d730748e3987af1 This basically made everyone download all mail again as if it were new. It also doesn't seem to play well with our webmail interface... Anyone have any tips on this or understand a bit more how the UIDL feature is implemented? Has anyone ever found a cucipop mailing list? Thanks, Charles On Tue, 30 May 2000, Sumbry][ wrote: > > We tried Cucipop on our 3.2-STABLE mail server. It worked until we added > > a second CPU. At that point Cucipop would work fine for a couple of days > > and then just quit. We didn't have time to debug it so we just went back > > to QPopper. > > > > I would be interested in hearing from people with SMP systems and Cucipop. > > Re my previous message, we also are running cucipop on a Dual P3 processor > box, running 3.3. No problems at all. > > ----- > Sumbry][ | Affinity Internet Inc | http://affinity.net | sumbry@affinity.net > I'll believe psychics when one phones me, just in the nick of time, > yelling, "Duck!" > > > > 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 Thu Jun 1 11:41:50 2000 Delivered-To: freebsd-isp@freebsd.org Received: from durango.picus.com (durango.picus.com [209.100.20.19]) by hub.freebsd.org (Postfix) with ESMTP id CF1FF37B97A for ; Thu, 1 Jun 2000 11:41:42 -0700 (PDT) (envelope-from troy@picus.com) Received: from arcadia [209.100.20.198] by durango.picus.com (SMTPD32-5.05) id AE0011B0170; Thu, 01 Jun 2000 14:40:00 -0400 From: "Troy Settle" To: "spork" , "Sumbry][" Cc: , Subject: RE: Cucipop port/source Date: Thu, 1 Jun 2000 14:44:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Charles, Not to throw a wrench in your wheels, but have you considered changing around your whole back-end system? It's too late for me (we just switched to Imail *YUCK*), but if I had everything to do over again, I think that Cyrus would be the obvious choice. It's got support for both POP3, IMAP, and quotas. It's got all the popper features that you're used to (maybe not bulletins, I've never used those), and with the IMAP support, webmail would be a breeze (much better than doing it through POP3). About the only disadvantage I've seen with Cyrus, is that it's designed to work on a closed system. You would need to treat your mail server as a remote server, even if you're running a client on the local machine. Anyways, I thought I'd comment, -Troy PS: When I did switch from Qpopper to Cucipop some years ago, there were a few problems initially, but they went away quickly. When implementing webmail, I switched (rather stupidly) to the UW Imapd and popper. ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of spork ** Sent: Thursday, June 01, 2000 1:46 PM ** To: Sumbry][ ** Cc: lambert@cswnet.com; freebsd-isp@FreeBSD.ORG ** Subject: Re: Cucipop port/source ** ** ** I just gave cucipop a quick trial and it just about cut the load on the ** machine in half. Response in my pop client was quite zippy. ** ** I did run into a few problems, the most annoying being the difference in ** UIDLs returned between Qpopper and cucipop: ** ** cucipop - UIDL 1 ** +OK 1 982b3d94590d0000 ** ** Qpopper - uidl 1 ** +OK 1 7717bd7ef97667003d730748e3987af1 ** ** This basically made everyone download all mail again as if it were new. ** It also doesn't seem to play well with our webmail interface... ** ** Anyone have any tips on this or understand a bit more how the ** UIDL feature ** is implemented? Has anyone ever found a cucipop mailing list? ** ** Thanks, ** ** Charles ** ** On Tue, 30 May 2000, Sumbry][ wrote: ** ** > > We tried Cucipop on our 3.2-STABLE mail server. It worked ** until we added ** > > a second CPU. At that point Cucipop would work fine for a ** couple of days ** > > and then just quit. We didn't have time to debug it so we ** just went back ** > > to QPopper. ** > > ** > > I would be interested in hearing from people with SMP ** systems and Cucipop. ** > ** > Re my previous message, we also are running cucipop on a Dual ** P3 processor ** > box, running 3.3. No problems at all. ** > ** > ----- ** > Sumbry][ | Affinity Internet Inc | http://affinity.net | ** sumbry@affinity.net ** > I'll believe psychics when one phones me, just in the nick of time, ** > yelling, "Duck!" ** > ** > ** > ** > 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 ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 12:11: 4 2000 Delivered-To: freebsd-isp@freebsd.org Received: from oberon.wwwnexus.com (oberon.wwwnexus.com [216.71.84.174]) by hub.freebsd.org (Postfix) with ESMTP id DFBAF37B81B for ; Thu, 1 Jun 2000 12:10:59 -0700 (PDT) (envelope-from jan@smartsoft.cc) Received: from smartsoft.cc (client-209-158-92-24.bellatlantic.net [209.158.92.24]) by oberon.wwwnexus.com (8.8.5/8.8.5) with ESMTP id NAA02372 for ; Thu, 1 Jun 2000 13:52:56 -0500 Message-ID: <3936B4DF.B9471CD2@smartsoft.cc> Date: Thu, 01 Jun 2000 15:09:19 -0400 From: Jan Knepper Organization: Smartsoft, LLC X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-ISP@FreeBSD.org Subject: Burstable T1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, What do you guys think about "Burstable T1" to setup an Internet Host with FreeBSD? I asked a couple of weeks ago about Frame Relay. Frame Relay however is rather expensive compared to "Burstable T1". DSL is not available where I want to have the host. Too far away from a CO. The only one is IDSL (DSL over ISDN), but since we've already ISDN-2 I don't think that would be a real solution. Don't worry, be Kneppie! Jan -- =============================================================== Jan Knepper Smartsoft, LLC 88 Petersburg Road Petersburg, NJ 08270 U.S.A. Phone: 609-628-4260 FAX : 609-628-1267 http://www.smartsoft.cc/ --------------------------------------------------------------- http://www.pianoprincess.com/ http://www.mp3.com/pianoprincess http://www.riffage.com/Bands/0,2939,2859,00.html http://pianoprincess.iuma.com/ http://www.changemusic.com/piano_princess =============================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 13:44:56 2000 Delivered-To: freebsd-isp@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id E8A5E37B933 for ; Thu, 1 Jun 2000 13:44:50 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id QAA03620; Thu, 1 Jun 2000 16:49:34 -0400 (EDT) Message-Id: <200006012049.QAA03620@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 01 Jun 2000 16:49:21 -0400 To: Jan Knepper , FreeBSD-ISP@FreeBSD.ORG From: Dennis Subject: Re: Burstable T1 In-Reply-To: <3936B4DF.B9471CD2@smartsoft.cc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:09 PM 6/1/00 -0400, Jan Knepper wrote: >Hi, > >What do you guys think about "Burstable T1" to setup an Internet Host with >FreeBSD? >I asked a couple of weeks ago about Frame Relay. Frame Relay however is rather >expensive compared to "Burstable T1". DSL is not available where I want to have >the host. Too far away from a CO. The only one is IDSL (DSL over ISDN), but >since we've already ISDN-2 I don't think that would be a real solution. Regardless of what they call it, "burstable" is totally meaningless. All it means is that they reserve the right to give you any grade of service that they want, so depending on how many hundreds of customers are sharing the bandwidth., your results will vary depending on what others are doing. On frame, for example, if you have a T1 and the provider only sells 24 T1s on their T3, then you should get the same throughput as you would on a dedicated T1. The danger of frame is that you normally will be sharing the "backbone leg", that is, the aggregate line going to the provider, with a lot more than 24 customers (typically 2-3 to one, at least). Burstable T1 (or DSL...same difference)..the provider simply puts a lot more customers on the line. You may see 250 "burstable T1" customers on a single T1. So if you are the only one active, you'll get T1. But there are no guarantees that you wont get absolutely terrible service also. Some providers will bandwidth limit you also, which will differ depending on the method. Our product, for example, allows you to "burst" when overall traffic levels are below a certain threshhold. After that you will be limited to a lower bandwidth. Dennis > >Don't worry, be Kneppie! >Jan > > > >-- >=============================================================== >Jan Knepper >Smartsoft, LLC >88 Petersburg Road >Petersburg, NJ 08270 >U.S.A. > >Phone: 609-628-4260 >FAX : 609-628-1267 > >http://www.smartsoft.cc/ >--------------------------------------------------------------- >http://www.pianoprincess.com/ >http://www.mp3.com/pianoprincess >http://www.riffage.com/Bands/0,2939,2859,00.html >http://pianoprincess.iuma.com/ >http://www.changemusic.com/piano_princess >=============================================================== > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-isp" in the body of the message > Emerging Technologies, Inc. ---------------------------------------------------------------------------- --------- http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 14:18:27 2000 Delivered-To: freebsd-isp@freebsd.org Received: from federation.addy.com (federation.addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id 385A437B57B for ; Thu, 1 Jun 2000 14:18:23 -0700 (PDT) (envelope-from jim@federation.addy.com) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id RAA99758 for ; Thu, 1 Jun 2000 17:18:21 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Thu, 1 Jun 2000 17:18:21 -0400 (EDT) From: Jim Sander Cc: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 In-Reply-To: <200006012049.QAA03620@etinc.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 > Burstable T1 (or DSL...same difference)..the provider simply puts a lot > more customers on the line. From what I have been told, this is not the case. Of course talking to network reps is always entertaining, and not necessarily enlightening, so any input from others would be welcome. When talking to one I refered to TCP/IP and he asked me if that was like voice over IP- yeah, we'll buy our network service from him! :) But anyway, this is what was described to me by one I sort of trust at least minimally... The difference between a "full" T1 and a burstable T1 is simply the way you are billed. You still have a wire run into your location that is dedicated- you can "burst" up to the full T1 bandwidth, and you are billed according to some usage formula usually involving 95th percentile use or some-such "logic." Of course it works out so that even an unused line costs some amount, and that if you exceed their max limit that you pay more for your burstable than a normal full-rate line. This may be a different service than was described to anyone else- and such an animal may not be available in your area, but that's my potentially flawed understanding of "burstable." If anyone has an "official" definition I'd like to hear. -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 14:26:19 2000 Delivered-To: freebsd-isp@freebsd.org Received: from blizzard.lightning.net (blizzard.lightning.net [209.51.160.5]) by hub.freebsd.org (Postfix) with ESMTP id 962D937B5F1 for ; Thu, 1 Jun 2000 14:26:16 -0700 (PDT) (envelope-from jreddy@lightning.net) Received: from nut.lightning.net (nut.lightning.net [209.51.160.16]) by blizzard.lightning.net (8.9.3/8.9.3) with ESMTP id RAA01826; Thu, 1 Jun 2000 17:26:13 -0400 (EDT) Message-Id: <4.3.2.7.2.20000601165517.00af89f0@mail.lightning.net> X-Sender: jreddy@mail.lightning.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 01 Jun 2000 17:23:05 -0400 To: Jan Knepper From: John Reddy Subject: Re: Burstable T1 Cc: FreeBSD-ISP@FreeBSD.ORG In-Reply-To: <3936B4DF.B9471CD2@smartsoft.cc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:09 PM 6/1/00 -0400, Jan Knepper wrote: >What do you guys think about "Burstable T1" to setup an Internet Host with >FreeBSD? >I asked a couple of weeks ago about Frame Relay. Frame Relay however is rather >expensive compared to "Burstable T1". DSL is not available where I want to >have >the host. Too far away from a CO. The only one is IDSL (DSL over ISDN), but >since we've already ISDN-2 I don't think that would be a real solution. I would find out how the ISP defines "Burstable". Some companies refer to rate limiting, or to the CIR of Frame circuits when saying their lines are burstable. Other companies use "Burstable" in reference to billing, where they bill based on your actually usage of the line. -John Reddy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 14:46:10 2000 Delivered-To: freebsd-isp@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B724037B5D7 for ; Thu, 1 Jun 2000 14:45:53 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA03790; Thu, 1 Jun 2000 17:50:36 -0400 (EDT) Message-Id: <200006012150.RAA03790@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 01 Jun 2000 17:50:23 -0400 To: Jim Sander From: Dennis Subject: Re: Burstable T1 Cc: isp@freebsd.org In-Reply-To: References: <200006012049.QAA03620@etinc.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 05:18 PM 6/1/00 -0400, you wrote: >> Burstable T1 (or DSL...same difference)..the provider simply puts a lot >> more customers on the line. > > From what I have been told, this is not the case. Of course talking to >network reps is always entertaining, and not necessarily enlightening, so >any input from others would be welcome. Our building was recently wired by "onsite access" and I had 3 salesman call on me (not knowing what ET does) and I got 3 different stories. Going into the equipment room I found they were all lying (or they just didnt know). > The difference between a "full" T1 and a burstable T1 is simply the way >you are billed. You still have a wire run into your location that is >dedicated- you can "burst" up to the full T1 bandwidth, and you are billed >according to some usage formula usually involving 95th percentile use or >some-such "logic." In our building a "burstable" T1 is $400/mo, flat rate and its 1200. for a "dedicated T1", whcih kind of shoots your definition in the foot. Of course there are only 2 T1s coming into the building, so there is no way for them to give anyone a dedicated T1 in reality. It appears that they rate limit everyone, and just use different settings (since everyone actually gets connected via 10baseT). In their case, "burstable" is just a term for a lower grade of service and you're not allowed to complain if the throughput sucks. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 15: 1:31 2000 Delivered-To: freebsd-isp@freebsd.org Received: from oberon.wwwnexus.com (oberon.wwwnexus.com [216.71.84.174]) by hub.freebsd.org (Postfix) with ESMTP id 8013A37B720 for ; Thu, 1 Jun 2000 15:01:24 -0700 (PDT) (envelope-from jan@smartsoft.cc) Received: from smartsoft.cc (client-209-158-92-170.bellatlantic.net [209.158.92.170]) by oberon.wwwnexus.com (8.8.5/8.8.5) with ESMTP id QAA27365 for ; Thu, 1 Jun 2000 16:43:18 -0500 Message-ID: <3936DCD4.C8C68F4B@smartsoft.cc> Date: Thu, 01 Jun 2000 17:59:48 -0400 From: Jan Knepper Organization: Smartsoft, LLC X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 References: <3936B4DF.B9471CD2@smartsoft.cc> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What I understand from the docco is: * Burstable T1 is a T1 * It comes in basic contracts as: * 0 - 128 Kbps sustained use * 128 - 156 Kbps sustained use * 256 - 384 Kbps sustained use * 384 - 512 Kbps sustained use * 512 - Kbps sustained use Calculation is done in such a way that the sustained use is being determined. They take the highest 5% of the top and charge you for what you used. I discussed a simple example with them. Suppose I have 1 hour a day 1.5 Mbps load and the rest of the day nothing. This would means a sustained use of 1.5 Mbps / 24 hours for day is 64 Kbps per hour which would fall half way the 0 - 128 Kbps sustained use. The guy I talked with actually got a technical guy on the phone who confirmed that this example indeed would be covered by the first scale. Thus in basic they charge you for the "usage" not for the available capacity. Also, when assigned to the first scale, service has to overrun for two months in a row before they change to the next scale. Once going over 512 Kbps it's better to change to a "Price Protected T1". What I actually meant to ask is does any one of you have experience with Burstable T1 and how it turns out. Did you stay in the scale assigned or turned it out to be uncontrolable? Don't worry, be Kneppie! Jan -- =============================================================== Jan Knepper Smartsoft, LLC 88 Petersburg Road Petersburg, NJ 08270 U.S.A. Phone: 609-628-4260 FAX : 609-628-1267 http://www.smartsoft.cc/ --------------------------------------------------------------- http://www.pianoprincess.com/ http://www.mp3.com/pianoprincess http://www.riffage.com/Bands/0,2939,2859,00.html http://pianoprincess.iuma.com/ http://www.changemusic.com/piano_princess =============================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 15:31:15 2000 Delivered-To: freebsd-isp@freebsd.org Received: from epsilon.lucida.qc.ca (epsilon.lucida.qc.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id 0BACB37B7DE for ; Thu, 1 Jun 2000 15:31:09 -0700 (PDT) (envelope-from matt@ARPA.MAIL.NET) Received: (qmail 5711 invoked by uid 1000); 1 Jun 2000 22:31:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Jun 2000 22:31:06 -0000 Date: Thu, 1 Jun 2000 18:31:04 -0400 (EDT) From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Jan Knepper Cc: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 In-Reply-To: <3936DCD4.C8C68F4B@smartsoft.cc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 1 Jun 2000, Jan Knepper wrote: [...] : What I actually meant to ask is does any one of you have experience : with Burstable T1 and how it turns out. Did you stay in the scale : assigned or turned it out to be uncontrolable? I'm on a burstable T1 from UUnet here. They bill on 95th percentile as usual, however you have to be over your billing teir for two months in a row before you are billed at the higher teir. This provides some safety in that there's never a surprise about a billing increase. However, if you are not careful you will end up paying them far more than they should get. Once you get over the 384Kbit teir, it costs you more than a flat rate T1. : Don't worry, be Kneppie! : Jan Matt Heckaman matt@arpa.mail.net http://www.lucida.qc.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE5NuQpdMMtMcA1U5ARAsJ5AKCR2CW6DE52q+73tu1FNZmJOJffAACgsE/C fDGaUT3hYfoXIItMzd8x+8I= =+NHu -----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 Thu Jun 1 16:16:19 2000 Delivered-To: freebsd-isp@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3925137B69A for ; Thu, 1 Jun 2000 16:16:10 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id TAA04008; Thu, 1 Jun 2000 19:21:00 -0400 (EDT) Message-Id: <200006012321.TAA04008@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 01 Jun 2000 19:20:46 -0400 To: Jan Knepper , FreeBSD-ISP@FreeBSD.ORG From: Dennis Subject: Re: Burstable T1 In-Reply-To: <3936DCD4.C8C68F4B@smartsoft.cc> References: <3936B4DF.B9471CD2@smartsoft.cc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 05:59 PM 6/1/00 -0400, Jan Knepper wrote: >What I understand from the docco is: >* Burstable T1 is a T1 >* It comes in basic contracts as: > * 0 - 128 Kbps sustained use > * 128 - 156 Kbps sustained use > * 256 - 384 Kbps sustained use > * 384 - 512 Kbps sustained use > * 512 - Kbps sustained use > >Calculation is done in such a way that the sustained use is being determined. They >take the highest 5% of the top and charge you for what you used. > >I discussed a simple example with them. Suppose I have 1 hour a day 1.5 Mbps load >and the rest of the day nothing. This would means a sustained use of 1.5 Mbps / 24 >hours for day is 64 Kbps per hour which would fall half way the 0 - 128 Kbps >sustained use. The guy I talked with actually got a technical guy on the phone who >confirmed that this example indeed would be covered by the first scale. which has nothing to do with "burstability". Doesnt surprise me. Noone understands anything anymore :-( DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 17:22:24 2000 Delivered-To: freebsd-isp@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id 9158D37BA7E for ; Thu, 1 Jun 2000 17:22:18 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id UAA16666; Thu, 1 Jun 2000 20:22:10 -0400 (EDT) Date: Thu, 1 Jun 2000 20:22:09 -0400 (EDT) From: Jim Flowers To: Jan Knepper Cc: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 In-Reply-To: <3936DCD4.C8C68F4B@smartsoft.cc> 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 Yes, burstable is one of those terms defined by the people who use it so, of course, it depends on your provider. We use burstable T-1 to refer to both our wireless and wireline accounts. We monitor usage and apply a filter to obtain a 5 minute average. We discard an occasional peak and ignore others during off-peak hours to determine the billing rate to apply. We counsel users to help them avoid high billings and, if requested by the customer we will place a bandwidth limit on his circuit to avoid overruns. This does mean that they share capacity with other users and the cost of Internet access and VPN service reflects that sharing. Many of our customers would not find the Internet affordable without this type of service. The statistical multiplexing of TDM streams occurs throughout the Internet and is one of the reasons for the low cost to reach all the way around the world. Want to pay for a full wired T-1 from here to India? It is interesting that quite good service can result, even at the 128KB level. Companies doing occasional file transfers and responsible business browsing with 20 to 30 computers don't seem to have much of a problem staying within their desired bandwidth limits. When we review the graphs of the users and at several layers back we get a good idea of how the multiplexing works and what "natural" bandwidth limiting occurs due to tcp/ip operation. The response from your proposed ISP is worrisome. If they calculate the way you suggest, it is not a good business model for them and therefore, I think it may be an answer given out too quickly by a sales agent. If that's what it says in the contract, and the cost is reasonable - go for it. Jim Flowers #4 ISP on C|NET, #1 in Ohio On Thu, 1 Jun 2000, Jan Knepper wrote: > What I understand from the docco is: > * Burstable T1 is a T1 > * It comes in basic contracts as: > * 0 - 128 Kbps sustained use > * 128 - 156 Kbps sustained use > * 256 - 384 Kbps sustained use > * 384 - 512 Kbps sustained use > * 512 - Kbps sustained use > > Calculation is done in such a way that the sustained use is being determined. They > take the highest 5% of the top and charge you for what you used. > > I discussed a simple example with them. Suppose I have 1 hour a day 1.5 Mbps load > and the rest of the day nothing. This would means a sustained use of 1.5 Mbps / 24 > hours for day is 64 Kbps per hour which would fall half way the 0 - 128 Kbps > sustained use. The guy I talked with actually got a technical guy on the phone who > confirmed that this example indeed would be covered by the first scale. > > Thus in basic they charge you for the "usage" not for the available capacity. Also, > when assigned to the first scale, service has to overrun for two months in a row > before they change to the next scale. > Once going over 512 Kbps it's better to change to a "Price Protected T1". > > What I actually meant to ask is does any one of you have experience with Burstable > T1 and how it turns out. Did you stay in the scale assigned or turned it out to be > uncontrolable? > > Don't worry, be Kneppie! > Jan > > > -- > =============================================================== > Jan Knepper > Smartsoft, LLC > 88 Petersburg Road > Petersburg, NJ 08270 > U.S.A. > > Phone: 609-628-4260 > FAX : 609-628-1267 > > http://www.smartsoft.cc/ > --------------------------------------------------------------- > http://www.pianoprincess.com/ > http://www.mp3.com/pianoprincess > http://www.riffage.com/Bands/0,2939,2859,00.html > http://pianoprincess.iuma.com/ > http://www.changemusic.com/piano_princess > =============================================================== > > > > > 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 Thu Jun 1 19: 0:42 2000 Delivered-To: freebsd-isp@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id C3F5C37B590 for ; Thu, 1 Jun 2000 19:00:38 -0700 (PDT) (envelope-from forrestc@IMACH.COM) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id SAA20826; Thu, 1 Jun 2000 18:54:23 -0600 (MDT) Date: Thu, 1 Jun 2000 18:54:23 -0600 (MDT) From: "Forrest W. Christian" To: Dennis Cc: Jim Sander , isp@FreeBSD.ORG Subject: Re: Burstable T1 In-Reply-To: <200006012150.RAA03790@etinc.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 Thu, 1 Jun 2000, Dennis wrote: > Our building was recently wired by "onsite access" and I had 3 salesman > call on me (not knowing what ET does) and I got 3 different stories. Going > into the equipment room I found they were all lying (or they just didnt know). Do you know the difference between a Used Car Salesman and an ISP Salesman? The Used Car Salesman knows he's lying. - Forrest W. Christian (forrestc@imach.com) AC7DE ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Thu Jun 1 20: 8:36 2000 Delivered-To: freebsd-isp@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 0D5D637BD80 for ; Thu, 1 Jun 2000 20:08:30 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA65970; Fri, 2 Jun 2000 12:36:01 +0930 (CST) (envelope-from newton) Date: Fri, 2 Jun 2000 12:36:01 +0930 From: Mark Newton To: "Forrest W. Christian" Cc: Dennis , Jim Sander , isp@FreeBSD.ORG Subject: Re: Burstable T1 Message-ID: <20000602123601.D65737@internode.com.au> References: <200006012150.RAA03790@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jun 01, 2000 at 06:54:23PM -0600, Forrest W. Christian wrote: > On Thu, 1 Jun 2000, Dennis wrote: > > > Our building was recently wired by "onsite access" and I had 3 salesman > > call on me (not knowing what ET does) and I got 3 different stories. Going > > into the equipment room I found they were all lying (or they just didnt > > know). > > Do you know the difference between a Used Car Salesman and an ISP > Salesman? > The Used Car Salesman knows he's lying. The used car salesman knows how to drive a car. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 3:40:59 2000 Delivered-To: freebsd-isp@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id B13CC37B529 for ; Fri, 2 Jun 2000 03:40:56 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id GAA69637; Fri, 2 Jun 2000 06:40:55 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id GAA17750; Fri, 2 Jun 2000 06:40:54 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: dwplists@loop.com ("D. W. Piper") Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Interface alias accounting? Date: Fri, 02 Jun 2000 10:37:04 GMT Message-ID: <39378e11.164105511@mail.sentex.net> References: <00bb01bfc1ab$b141a160$213cd3cf@loop.com> <20000519121531.A73613@setzer.chocobo.cx> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25 May 2000 11:16:52 -0400, in sentex.lists.freebsd.isp you wrote: >I just wanted to say thanks to everyone who replied. > >The consensus was to use ipfw count rules for each IP address, which >I've found does the job quite well. > >Thanks again, folks. :) Or, try ipfm from the ports ipfm is a bandwidth analysis tool. It counts how much data was send and received by specified hosts through an Inter- net link. ipfm is based on the libpcap (ftp://ftp.ee.lbl.gov/libp- capi-0.4.tar.Z) and should be portable. It was tested under Linux, Free BSD and IRIX. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 5:31:40 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.polytechnic.edu.na (mail.polytechnic.edu.na [196.31.225.2]) by hub.freebsd.org (Postfix) with ESMTP id EFC0537BE80 for ; Fri, 2 Jun 2000 05:31:27 -0700 (PDT) (envelope-from tim@polytechnic.edu.na) Received: from [196.31.225.199] (helo=polytechnic.edu.na) by mail.polytechnic.edu.na with esmtp (Exim 3.02 #2) id 12xsOw-0004sK-00; Fri, 02 Jun 2000 12:26:18 -0200 Message-ID: <3937A7AB.16555BEB@polytechnic.edu.na> Date: Fri, 02 Jun 2000 13:25:15 +0100 From: Tim Priebe Reply-To: tim@iafrica.com.na X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: spork Cc: "Sumbry][" , lambert@cswnet.com, freebsd-isp@FreeBSD.ORG Subject: Re: Cucipop port/source References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork wrote: > I just gave cucipop a quick trial and it just about cut the load on the > machine in half. Response in my pop client was quite zippy. > > I did run into a few problems, the most annoying being the difference in > UIDLs returned between Qpopper and cucipop: > > cucipop - UIDL 1 > +OK 1 982b3d94590d0000 > > Qpopper - uidl 1 > +OK 1 7717bd7ef97667003d730748e3987af1 > > This basically made everyone download all mail again as if it were new. > It also doesn't seem to play well with our webmail interface... The webmail problem is probably the same one I had, and could possibly explain the downloading of old mail. The problem is that when you list the mail in your mail box, cucipop claims it is going to send you 9 bytes more than it acctually does. The web mail client I am using then times out waiting for the final 9 bytes. I have reported the problem this week, but have not recieved a response. The work around I have implemented is to subtract 9 from the expected number of bytes in the webmail software. > Anyone have any tips on this or understand a bit more how the UIDL feature > is implemented? Has anyone ever found a cucipop mailing list? As far as I can tell when you pay for the product you get added to the mailing list. Tim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 6:15:58 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.polytechnic.edu.na (mail.polytechnic.edu.na [196.31.225.2]) by hub.freebsd.org (Postfix) with ESMTP id BB27137B644 for ; Fri, 2 Jun 2000 06:15:34 -0700 (PDT) (envelope-from tim@polytechnic.edu.na) Received: from [196.31.225.199] (helo=polytechnic.edu.na) by mail.polytechnic.edu.na with esmtp (Exim 3.02 #2) id 12xtBQ-0001ux-00; Fri, 02 Jun 2000 13:16:24 -0200 Message-ID: <3937B36A.8E4DA483@polytechnic.edu.na> Date: Fri, 02 Jun 2000 14:15:22 +0100 From: Tim Priebe Reply-To: tim@iafrica.com.na X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim Flowers Cc: Jan Knepper , FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jim Flowers wrote: [...] > The statistical multiplexing of TDM streams occurs throughout the > Internet and is one of the reasons for the low cost to reach all the way > around the world. Want to pay for a full wired T-1 from here to India? Actually this is only a small part of why it costs you so little to "reach all the way around the world". The biggest is that you do not pay anything for the line to India from the US. The people in India pay for it all. Tim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 8:24:40 2000 Delivered-To: freebsd-isp@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D090A37B64F for ; Fri, 2 Jun 2000 08:24:34 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA05702; Fri, 2 Jun 2000 11:29:18 -0400 (EDT) Message-Id: <200006021529.LAA05702@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 02 Jun 2000 11:28:56 -0400 To: Jim Flowers , Jan Knepper From: Dennis Subject: Re: Burstable T1 Cc: FreeBSD-ISP@FreeBSD.ORG In-Reply-To: References: <3936DCD4.C8C68F4B@smartsoft.cc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:22 PM 6/1/00 -0400, Jim Flowers wrote: >Yes, burstable is one of those terms defined by the people who use it so, >of course, it depends on your provider. We use burstable T-1 to refer to >both our wireless and wireline accounts. We monitor usage and apply a >filter to obtain a 5 minute average. We discard an occasional peak and >ignore others during off-peak hours to determine the billing rate to >apply. We counsel users to help them avoid high billings and, if >requested by the customer we will place a bandwidth limit on his circuit >to avoid overruns. I was referring to the meaning ot the term, which has nothing to do with what you are talking about. "burstable" implies that it "has the capability to burst to" T1, which is patently wrong. The implication that an HDLC frame is a "burst" is such an ignorant concept that its laughable. Nothing in the term "burstable" even remotely implies averaging or anything of the sort. Its as flagrantly wrong as CIR, "latency" and all of the other terms used by the people running the internet that have no clue what they are talking about. Luckly for them the demand is so high you dont have to know what you're talking about anymore. Techs at telcos seem dumbfounded when you talk about CSU/DSUs providing clocking...they are totally ignorant of the technologies that they earn a living supporting. Its beyond mind-boggling. db > >This does mean that they share capacity with other users and the cost of >Internet access and VPN service reflects that sharing. Many of our >customers would not find the Internet affordable without this type of >service. > >The statistical multiplexing of TDM streams occurs throughout the >Internet and is one of the reasons for the low cost to reach all the way >around the world. Want to pay for a full wired T-1 from here to India? > >It is interesting that quite good service can result, even at the 128KB >level. Companies doing occasional file transfers and responsible >business browsing with 20 to 30 computers don't seem to have much of a >problem staying within their desired bandwidth limits. > >When we review the graphs of the users and at several layers back we get >a good idea of how the multiplexing works and what "natural" bandwidth >limiting occurs due to tcp/ip operation. > >The response from your proposed ISP is worrisome. If they calculate the >way you suggest, it is not a good business model for them and therefore, >I think it may be an answer given out too quickly by a sales agent. If >that's what it says in the contract, and the cost is reasonable - go for >it. > >Jim Flowers >#4 ISP on C|NET, #1 in Ohio > >On Thu, 1 Jun 2000, Jan Knepper wrote: > >> What I understand from the docco is: >> * Burstable T1 is a T1 >> * It comes in basic contracts as: >> * 0 - 128 Kbps sustained use >> * 128 - 156 Kbps sustained use >> * 256 - 384 Kbps sustained use >> * 384 - 512 Kbps sustained use >> * 512 - Kbps sustained use >> >> Calculation is done in such a way that the sustained use is being determined. They >> take the highest 5% of the top and charge you for what you used. >> >> I discussed a simple example with them. Suppose I have 1 hour a day 1.5 Mbps load >> and the rest of the day nothing. This would means a sustained use of 1.5 Mbps / 24 >> hours for day is 64 Kbps per hour which would fall half way the 0 - 128 Kbps >> sustained use. The guy I talked with actually got a technical guy on the phone who >> confirmed that this example indeed would be covered by the first scale. >> >> Thus in basic they charge you for the "usage" not for the available capacity. Also, >> when assigned to the first scale, service has to overrun for two months in a row >> before they change to the next scale. >> Once going over 512 Kbps it's better to change to a "Price Protected T1". >> >> What I actually meant to ask is does any one of you have experience with Burstable >> T1 and how it turns out. Did you stay in the scale assigned or turned it out to be >> uncontrolable? >> >> Don't worry, be Kneppie! >> Jan >> >> >> -- >> =============================================================== >> Jan Knepper >> Smartsoft, LLC >> 88 Petersburg Road >> Petersburg, NJ 08270 >> U.S.A. >> >> Phone: 609-628-4260 >> FAX : 609-628-1267 >> >> http://www.smartsoft.cc/ >> --------------------------------------------------------------- >> http://www.pianoprincess.com/ >> http://www.mp3.com/pianoprincess >> http://www.riffage.com/Bands/0,2939,2859,00.html >> http://pianoprincess.iuma.com/ >> http://www.changemusic.com/piano_princess >> =============================================================== >> >> >> >> >> 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 8:34:36 2000 Delivered-To: freebsd-isp@freebsd.org Received: from federation.addy.com (federation.addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id DF2ED37BDEB for ; Fri, 2 Jun 2000 08:34:33 -0700 (PDT) (envelope-from jim@federation.addy.com) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id LAA81264 for ; Fri, 2 Jun 2000 11:34:33 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Fri, 2 Jun 2000 11:34:32 -0400 (EDT) From: Jim Sander Cc: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 In-Reply-To: <3937B36A.8E4DA483@polytechnic.edu.na> 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 OK, so the moral of the story seems to be- never believe the salesman, caveat emptor, etc. and so forth. I kind of figured that, and it was extremely interesting to hear what (definitely emphasize quotes) "standard practices" there are. It's also good to hear from people who know a lot more than I do that network co. salesmen are idiots- sometimes it's obvious, but I'm a software tech and only begrudgingly have learned about networking's inner mechanisms, and am thus vulnerable to their buzzwords of doom. :) Where we're located there are very few high-rate data customers, so the options available are probably less extensive than in more populated areas. (there really isn't anyone to share a line with) That would explain as well as any why I heard what I did. Oh- and about "bandwidth management" (answering the poor gentleman's question that sparked this whole thing) it's definitely possible to choke your usage down below bps if you want, probably without drastic consequences unless you are truly over capacity. Dummynet and the fine family of etinc products all allow you to do that to various degrees. I'm far from an expert on that front, but plenty of people here do it all the time and can be more helpful. -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 10: 4:33 2000 Delivered-To: freebsd-isp@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by hub.freebsd.org (Postfix) with ESMTP id BD32337BA67 for ; Fri, 2 Jun 2000 10:04:18 -0700 (PDT) (envelope-from wayne@staff.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.9.3/8.9.3) id NAA80200 for FreeBSD-ISP@FreeBSD.ORG; Fri, 2 Jun 2000 13:04:16 -0400 (EDT) (envelope-from wayne) Date: Fri, 2 Jun 2000 13:04:16 -0400 From: "Michael R. Wayne" To: FreeBSD-ISP@FreeBSD.ORG Subject: Re: Burstable T1 Message-ID: <20000602130416.T55169@staff.msen.com> References: <3936DCD4.C8C68F4B@smartsoft.cc> <200006021529.LAA05702@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200006021529.LAA05702@etinc.com>; from dennis@etinc.com on Fri, Jun 02, 2000 at 11:28:56AM -0400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 02, 2000 at 11:28:56AM -0400, Dennis wrote: > > "burstable" implies that it "has the capability > to burst to" T1, which is patently wrong. I guess it depends on the provider. We sell burstable T1s, starting at $150 per month billed at 95% utilization. They are real, clear channel T1 circuits with plenty of back end bandwidth that each customer customer can nail at 100% 24x7 with no problems. If someone is trying to sell you a "burstable" circuit and it can't sustain the burst rate, walk away. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Fri Jun 2 23:40:57 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2715237BAE4 for ; Fri, 2 Jun 2000 23:40:51 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id IAA52667 for freebsd-isp@FreeBSD.ORG; Sat, 3 Jun 2000 08:40:45 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id IAA63725 for ; Sat, 3 Jun 2000 08:21:53 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <004101bfcd23$cadd1860$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: cistron-radiusd: no acct Date: Sat, 3 Jun 2000 08:19:10 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to use cistron-radius from the ports, because of its ability to limit simultaneous use of an account. So I installed it from ports. It authenticates nicely, but I get no accounting information, and radwtmp/radutmp is empty. I have verified by netstat that something is listening on udp 1645/1646 and the portmaster is using these ports. This also could account for the difference in the detail of the detail-file: No start-stop info. The "old radius": Merit AAA server Version 3.6B , licensed software COPYRIGHT 1992, 1993, 1994, 1995, 1996, 1997, 1998 THE REGENTS OF THE UNIVERSITY OF MICHIGAN ALL RIGHTS RESERVED Use -h for help Version 3.6B NDBM NOSHADOW linux ASCEND BINARY_FILTERS directory = /usr/local/etc/raddb Produces this: Tue May 30 23:55:22 2000 Acct-Session-Id = "1A09EFB1" User-Name = "idk43807" NAS-IP-Address = 194.19.140.23 NAS-Port = 0 NAS-Port-Type = ISDN-Sync Acct-Status-Type = Stop Acct-Session-Time = 93 Acct-Authentic = RADIUS Acct-Input-Octets = 1025 Acct-Output-Octets = 1515 Called-Station-Id = "33361515" Calling-Station-Id = "44831791" Acct-Terminate-Cause = User-Request LE-Terminate-Detail = "User Request - Call Circuit Closed" Service-Type = Framed Framed-Protocol = PPP Framed-IP-Address = 194.255.12.212 Acct-Delay-Time = 0 The cistron is: radiusd: RADIUS version cistron-1.6.3 02-Apr-2000 Compilation flags: NOSHADOW ATTRIB_NMC COMPAT_1543 Cistron produces only this: Fri Jun 2 01:09:27 2000 User-Name = "idk70678" NAS-IP-Address = 194.19.140.23 NAS-Port-Id = 0 NAS-Port-Type = ISDN Service-Type = Framed-User Framed-Protocol = PPP Called-Station-Id = "33361515" Calling-Station-Id = "43427036" Timestamp = 959900967 There is no accounting information here. Coherent with it is only logging auth, not acct. Any clues where I should start looking? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Jun 3 12:39:48 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ux.accesscom.net (ux.accesscom.net [204.181.176.2]) by hub.freebsd.org (Postfix) with SMTP id 2C6F537B7AB; Sat, 3 Jun 2000 12:39:44 -0700 (PDT) (envelope-from mlistbsd@icorp.net) Received: from unknown (icorp.net [206.160.4.95]) by ux(smtpd 2.1.3) with SMTP id smtp002375 for ; Sat, 3 Jun 00 19:39:34 GMT (envelope-from ) Message-ID: <39395E61.909E59DC@icorp.net> Date: Sat, 03 Jun 2000 14:37:05 -0500 From: James X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en Mime-Version: 1.0 To: freebsd-isp@freebsd.org, freebsd-questions@freebsd.org Subject: Compaq Proliant 3000 & RAID Content-Length: 370 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just purchased a Compaq Proliant 3000 and want to set up a RAID system for it. Has anyone run FreeBSD on this hardware - any comments? Does FreeBSD support Compaq's RAID hardware? Which is better: AMI or Mylex for RAID 5? Can anyone recommend a particular high-end model that performs well and is supported by the latest version of FreeBSD? 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 Sat Jun 3 12:47: 5 2000 Delivered-To: freebsd-isp@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 2DA7C37B7AB for ; Sat, 3 Jun 2000 12:46:57 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 68921 invoked by uid 1001); 3 Jun 2000 19:46:54 +0000 (GMT) To: mlistbsd@icorp.net Cc: freebsd-isp@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Compaq Proliant 3000 & RAID From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 03 Jun 2000 14:37:05 -0500" References: <39395E61.909E59DC@icorp.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 03 Jun 2000 21:46:54 +0200 Message-ID: <68919.960061614@verdi.nethelp.no> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I just purchased a Compaq Proliant 3000 and want to set up a RAID system > for it. Has anyone run FreeBSD on this hardware - any comments? Running 3.4-STABLE with the sym driver here, on a dual processor Proliant 3000 system. It's working very well. I have no experience with RAID on this hardware, though. If you use the builtin SCSI controllers: Please use the sym driver, not the ncr driver. The difference in stability is significant (currently 104 days uptime with the sym driver - we used to have a crash about once per week or so with the ncr driver). Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-20000124-STABLE #0: Sat Feb 19 23:14:12 CET 2000 sthaug@newsfeed1.telia.no:/local/freebsd/src/sys/compile/NEWSFEED1_SYM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 603979776 (589824K bytes) avail memory = 584105984 (570416K bytes) Programming 28 pins in IOAPIC #0 EISA INTCONTROL = 00000620 IOAPIC #0 intpint 24 -> irq 5 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 8, version: 0x001b0011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02d6000. Pentium Pro MTRR support enabled eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 vga0: rev 0x22 int a irq 255 on pci0.6.0 chip1: rev 0x07 on pci0.15.0 chip2: rev 0x03 on pci0.17.0 Probing for devices on PCI bus 1: sym0: <875> rev 0x14 int a irq 19 on pci1.4.0 sym0: No NVRAM, ID 7, Fast-20, parity checking sym1: <875> rev 0x14 int b irq 18 on pci1.4.1 sym1: No NVRAM, ID 7, Fast-20, parity checking fxp0: rev 0x05 int a irq 18 on pci1.7.0 fxp0: Ethernet address 00:90:27:13:f6:21 tl0: rev 0x10 int a irq 17 on pci1.8.0 tl0: Ethernet address: 00:08:c7:1e:a7:35 tl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 2: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0: failed to get data. psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 1378KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 ccd0-3: Concatenated disk drivers Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changida0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da2 at sym0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da3 at sym0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Jun 3 18:44:16 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ux.accesscom.net (ux.accesscom.net [204.181.176.2]) by hub.freebsd.org (Postfix) with SMTP id 164CF37B6B1 for ; Sat, 3 Jun 2000 18:44:14 -0700 (PDT) (envelope-from mlistbsd@icorp.net) Received: from unknown (icorp.net [206.160.4.95]) by ux(smtpd 2.1.3) with SMTP id smtp013606 for ; Sun, 4 Jun 00 01:44:01 GMT (envelope-from ) Message-ID: <3939B3BB.3E3E9FD7@icorp.net> Date: Sat, 03 Jun 2000 20:41:16 -0500 From: James X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en Mime-Version: 1.0 To: freebsd-isp@freebsd.org Subject: RAID: AMI or Mylex Content-Length: 384 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, forget software RAID. Hardware-wise, which is the best controller to use for FreeBSD? I keep asking this question and every time the thread mutates into an argument about vinum. Anyone using hardware RAID under FreeBSD? If so, please give me the dirt on what you use, what you like, and what you don't like. MUCH appreciated... Lots of good kharma for helpful responses! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message From owner-freebsd-isp Sat Jun 3 18:59:48 2000 Delivered-To: freebsd-isp@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id BB05C37B6B1 for ; Sat, 3 Jun 2000 18:59:45 -0700 (PDT) (envelope-from simon@optinet.com) Received: from pinky (adsl-151-202-94-150.bellatlantic.net [151.202.94.150]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id OAA15885; Sat, 3 Jun 2000 14:03:56 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200006032003.OAA15885@mail.fpsn.net> From: "Simon" To: "freebsd-isp@FreeBSD.ORG" , "James" Date: Sat, 03 Jun 2000 22:03:37 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: <3939B3BB.3E3E9FD7@icorp.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: RAID: AMI or Mylex Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey, Mylex makes good ones. Unfortunately, they stopped making AcceleRAID 250, but you can still get AcceleRAID 150 which will do the trick unless you need something more powerful. What do you need this controller for? How many drives, etc... -Simon On Sat, 03 Jun 2000 20:41:16 -0500, James wrote: > >Ok, forget software RAID. Hardware-wise, which is the best controller >to use for FreeBSD? I keep asking this question and every time the >thread mutates into an argument about vinum. Anyone using hardware RAID >under FreeBSD? If so, please give me the dirt on what you use, what you >like, and what you don't like. MUCH appreciated... Lots of good kharma >for helpful responses! > > > > > >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