From owner-freebsd-isp Sun Jan 21 04:57:46 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA15034 for isp-outgoing; Sun, 21 Jan 1996 04:57:46 -0800 (PST) Received: from Aspen.Woc.Atinc.COM ([198.138.38.206]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA15023 Sun, 21 Jan 1996 04:57:39 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id HAA02254; Sun, 21 Jan 1996 07:58:17 -0500 Date: Sun, 21 Jan 1996 07:58:17 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Andreas Klemm cc: isp@freebsd.org, jkh@freebsd.org, joerg@freebsd.org Subject: Re: FreeBSD-current Proxy Server in our company (vs. Sun) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk is the FreeBSD box a firewall or just an application server? will it control access or provide logins to the users? if its a firewall, you need to rethink your design. either way a 3C509 MAY not be good enough. the driver in 1.1.5.1 lost interrupts occasionally. i dont know if this has been fixed or not. > And now ... The disk configuration ... > Imagine ... the machine also will act as a News Server > in the company for about 10 concurrent people. > So basically I would tend to put Operating system, > News Server and WWW server onto 3 different disks. > > I'd like to get three 2GB Wide SCSI disks, but I think > this would be overkill. And would cost *too much*. > > What would be better ... generally ... > To buy 3 or 4 1GB Harddisks at 5400rpm to distribute > the SCSI workload onto 3 or four different disks > (those drives are sooo inexpensive now ...) for a news server, the more disks the better. split the history, index, spool areas up. this was covered recently in freebsd-isp, you may want to check the mail archives via www.freebsd.org. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-isp Sun Jan 21 06:35:07 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA18081 for isp-outgoing; Sun, 21 Jan 1996 06:35:07 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA18075 Sun, 21 Jan 1996 06:35:02 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id PAA29609; Sun, 21 Jan 1996 15:30:15 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id QAA10963; Sun, 21 Jan 1996 16:19:08 +0100 (MET) Date: Sun, 21 Jan 1996 16:19:08 +0100 (MET) From: Andreas Klemm To: "Jonathan M. Bresler" cc: isp@freebsd.org, jkh@freebsd.org, joerg@freebsd.org Subject: Re: FreeBSD-current Proxy Server in our company (vs. Sun) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk On Sun, 21 Jan 1996, Jonathan M. Bresler wrote: > either way a 3C509 MAY not be good enough. the driver in 1.1.5.1 > lost interrupts occasionally. i dont know if this has been fixed or not. So what other 10MBit TP ethernet card (PCI or ISA) would be recommended ? -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-isp Sun Jan 21 07:08:15 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA19328 for isp-outgoing; Sun, 21 Jan 1996 07:08:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA19249 Sun, 21 Jan 1996 07:08:00 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA07163; Sun, 21 Jan 1996 16:07:57 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id QAA06196; Sun, 21 Jan 1996 16:07:57 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id PAA25034; Sun, 21 Jan 1996 15:33:51 +0100 (MET) From: J Wunsch Message-Id: <199601211433.PAA25034@uriah.heep.sax.de> Subject: Re: FreeBSD-current Proxy Server in our company (vs. Sun) To: jmb@freebsd.org (Jonathan M. Bresler) Date: Sun, 21 Jan 1996 15:33:50 +0100 (MET) Cc: andreas@knobel.gun.de, isp@freebsd.org, jkh@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Jonathan M. Bresler" at Jan 21, 96 07:58:17 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-isp@freebsd.org Precedence: bulk As Jonathan M. Bresler wrote: > > > either way a 3C509 MAY not be good enough. the driver in 1.1.5.1 > lost interrupts occasionally. i dont know if this has been fixed or not. I remember some trouble reports for 3C5x9 cards, too. I had to setup a customer's machine a couple of days ago. It will be run under (ick!) Winglows later, but first it has to be a demonstrat- ion machine for heavy network load, running FreeBSD. (This is to diagnose their network.) The data pump is an oldish PeeCee with an even more oldish Lance card (Isolink 4110 or so), this box has a 3c590 card and an X11 display to run xperfmon++. The first tests were impressive: i'm getting a constant rate between 900 and 1000 KB/s by simply piping /dev/zero through an rsh. :-) The if_vx driver out of -current fits cleanly into 2.1R, as somebody else noted, too. It doesn't seem to count the collisions, however. Other than this, it seems to be a fine card, PCI-based. So i would either pick this one, or one of the 2104X-based boards for a new PCI machine, Andreas. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-isp Sun Jan 21 07:22:03 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA19916 for isp-outgoing; Sun, 21 Jan 1996 07:22:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA19906 Sun, 21 Jan 1996 07:21:56 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA07461; Sun, 21 Jan 1996 16:21:54 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id QAA06358; Sun, 21 Jan 1996 16:21:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id QAA25643; Sun, 21 Jan 1996 16:17:15 +0100 (MET) From: J Wunsch Message-Id: <199601211517.QAA25643@uriah.heep.sax.de> Subject: Re: FreeBSD-current Proxy Server in our company (vs. Sun) To: andreas@knobel.gun.de (Andreas Klemm) Date: Sun, 21 Jan 1996 16:17:14 +0100 (MET) Cc: jmb@freebsd.org, isp@freebsd.org, jkh@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Andreas Klemm" at Jan 21, 96 04:19:08 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-isp@freebsd.org Precedence: bulk As Andreas Klemm wrote: > > > either way a 3C509 MAY not be good enough. the driver in 1.1.5.1 > > lost interrupts occasionally. i dont know if this has been fixed or not. > > So what other 10MBit TP ethernet card (PCI or ISA) would > be recommended ? For ISA, the beloved SMC 8013 card seems to be the overall best choice. The Lance chips are also fine (Am7990-based boards), they are heavily used in many workstations. PC NIC's with them are rather rare. For PCI, the DEC 2104X-based cards are certainly the first choice, or the 3c590 with the `vx' driver pulled out of -current. See my other mail. I've heard that the 3c595 doesn't run well yet (it's a 10/100 Mbit/s board). I would generally avoid NE1000, NE2000, 3C503, 3C509 for heavy-loaded servers. Note that not all 8013 clones are of good quality. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-isp Sun Jan 21 11:07:02 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01170 for isp-outgoing; Sun, 21 Jan 1996 11:07:02 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA01161 Sun, 21 Jan 1996 11:06:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id LAA00853; Sun, 21 Jan 1996 11:05:19 -0800 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: andreas@knobel.gun.de (Andreas Klemm), jmb@FreeBSD.ORG, isp@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: FreeBSD-current Proxy Server in our company (vs. Sun) In-reply-to: Your message of "Sun, 21 Jan 1996 16:17:14 +0100." <199601211517.QAA25643@uriah.heep.sax.de> Date: Sun, 21 Jan 1996 11:05:19 -0800 Message-ID: <851.822251119@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-isp@FreeBSD.ORG Precedence: bulk > As Andreas Klemm wrote: > For PCI, the DEC 2104X-based cards are certainly the first choice, or > the 3c590 with the `vx' driver pulled out of -current. See my other > mail. I've heard that the 3c595 doesn't run well yet (it's a 10/100 > Mbit/s board). Check this out: Subject: Patch and manual page for if_vx driver To: core@freebsd.org Date: Tue, 16 Jan 1996 00:43:43 -0600 (CST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I have a patch for the if_vx driver for the 3Com 3c590/3c595 cards which I submitted a few months ago. I also have written a short manual page. I have appended both of these files to this message. You may also wish to add these cards to your list of supported devices, and especially you may want to add the driver to the kernel supplied on the boot floppy. Thanks for your help. -- Fred Gray -- fgray@owlnet.rice.edu ----- ----- cut here for if_vx.c.diff ----- ----- *** if_vx.c.orig Tue Jan 16 00:30:15 1996 --- if_vx.c Tue Jan 16 00:30:02 1996 *************** *** 173,178 **** --- 173,181 ---- { if(device_id == 0x590010b7ul) return "3Com 3c590 EtherLink III PCI"; + if(device_id == 0x595010b7ul || device_id == 0x595110b7ul || + device_id == 0x595210b7ul) + return "3Com 3c595 Fast EtherLink III PCI"; return NULL; } *************** *** 185,191 **** { struct vx_softc *sc; struct ifnet *ifp; ! u_short i, j, *p; struct ifaddr *ifa; struct sockaddr_dl *sdl; --- 188,195 ---- { struct vx_softc *sc; struct ifnet *ifp; ! u_short i, *p; ! u_long j; struct ifaddr *ifa; struct sockaddr_dl *sdl; *************** *** 205,211 **** sc->vx_connectors = 0; i = pci_conf_read(config_id, 0x48); ! j = inw(BASE + VX_W3_INTERNAL_CFG) >> INTERNAL_CONNECTOR_BITS; if (i & RS_AUI) { printf("aui"); sc->vx_connectors |= AUI; --- 209,216 ---- sc->vx_connectors = 0; i = pci_conf_read(config_id, 0x48); ! GO_WINDOW(3); ! j = inl(BASE + VX_W3_INTERNAL_CFG) >> INTERNAL_CONNECTOR_BITS; if (i & RS_AUI) { printf("aui"); sc->vx_connectors |= AUI; *************** *** 251,257 **** ifp->if_unit = unit; ifp->if_name = "vx"; ifp->if_mtu = ETHERMTU; ! ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_NOTRAILERS; ifp->if_init = vxinit; ifp->if_output = ether_output; ifp->if_start = vxstart; --- 256,262 ---- ifp->if_unit = unit; ifp->if_name = "vx"; ifp->if_mtu = ETHERMTU; ! ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX /*| IFF_NOTRAILERS*/; ifp->if_init = vxinit; ifp->if_output = ether_output; ifp->if_start = vxstart; *************** *** 403,410 **** outw(BASE + VX_W4_MEDIA_TYPE, ENABLE_UTP); GO_WINDOW(1); } else { ! GO_WINDOW(0); ! j = inw(BASE + VX_W3_INTERNAL_CFG) >> INTERNAL_CONNECTOR_BITS; GO_WINDOW(1); switch(j) { case ACF_CONNECTOR_UTP: --- 408,415 ---- outw(BASE + VX_W4_MEDIA_TYPE, ENABLE_UTP); GO_WINDOW(1); } else { ! GO_WINDOW(3); ! j = inl(BASE + VX_W3_INTERNAL_CFG) >> INTERNAL_CONNECTOR_BITS; GO_WINDOW(1); switch(j) { case ACF_CONNECTOR_UTP: ----- ----- cut here for vx.4 ----- ----- .\" .\" Copyright (c) 1996, Fred Gray .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by David Greenman. .\" 4. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .Dd January 15, 1996 .Dt VX 4 i386 .Os .Sh NAME .Nm vx .Nd PCI Ethernet device driver .Sh SYNOPSIS .Cd "device vx0 at pci? port? net irq? vector vxintr" .Cd "device vx1 at pci? port? net irq? vector vxintr" .Cd "device vx2 at pci? port? net irq? vector vxintr" .Sh DESCRIPTION The .Nm vx driver provides support for the 3Com 3c590 and 3c595 EtherLink III and Fast EtherLink III PCI Ethernet cards in 10 Mbps mode. .Sh DIAGNOSTICS .Bl -diag .It "vx%d: not configured; kernel is built for only %d devices." There are not enough devices in the kernel configuration file for the number of adapters present in the system. Add devices to the configuration file, rebuild the kernel, and reboot. .Pp All other diagnostics indicate either a hardware problem or a bug in the driver. .Sh CAVEATS Some early-revision 3c590 cards are defective and suffer from many receive overruns, which cause lost packets. The author has attempted to implement a test for it based on the information supplied by 3Com, but the test resulted mostly in spurious warnings. .Pp The performance of this driver is somewhat limited by the fact that it uses only polled-mode I/O and does not make use of the bus-mastering capability of the cards. .Sh BUGS The .Nm vx driver is known not to reset the adapter correctly following a warm boot on some systems. .Pp The .Nm vx driver has not been exhaustively tested with all the models of cards that it claims to support. .Sh HISTORY The .Nm vx device driver first appeared in FreeBSD 2.1.0. It was derived from the .Nm ep driver, from which it inheirits most of its limitations. .Sh AUTHOR The .Nm vx device driver and this manual page were written by Fred Gray (fgray@rice.edu), based on the work of Herb Peyerl and with the assistance of numerous others. From owner-freebsd-isp Mon Jan 22 04:52:47 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA08579 for isp-outgoing; Mon, 22 Jan 1996 04:52:47 -0800 (PST) Received: from ns.vbc.net (ns.vbc.net [194.207.0.129]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA08574 for ; Mon, 22 Jan 1996 04:52:45 -0800 (PST) Received: (from jdd@localhost) by ns.vbc.net (8.6.12/8.6.9) id MAA04025; Mon, 22 Jan 1996 12:53:42 GMT Date: Mon, 22 Jan 1996 12:53:40 +0000 (GMT) From: Jim Dixon To: FreeBSD-isp@FreeBSD.org Subject: SMDS? DS3-capable sync cards? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org Precedence: bulk Does anyone know of a source for PC-compatible (EISA or PCI) sync serial cards that can handle data at DS3 speeds (34 Mbps), preferably with SMDS drivers, preferably for FreeBSD?? -- Jim Dixon VBCnet GB Ltd +44 117 929 1316 fax +44 117 927 2015 VBCnet West +1 408 971 2682 fax +1 408 971 2684 From owner-freebsd-isp Mon Jan 22 05:54:06 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA12280 for isp-outgoing; Mon, 22 Jan 1996 05:54:06 -0800 (PST) Received: from itchy.mosquito.com (itchy.mosquito.com [206.205.132.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA12275 for ; Mon, 22 Jan 1996 05:54:04 -0800 (PST) Received: (from boot@localhost) by itchy.mosquito.com (8.6.11/8.6.9) id IAA29999; Mon, 22 Jan 1996 08:55:12 -0500 From: Bruce Bauman Message-Id: <199601221355.IAA29999@itchy.mosquito.com> Subject: in_rtqtimo: adjusted rtq_reallyold to 1600 To: freebsd-isp@freebsd.org Date: Mon, 22 Jan 1996 08:55:12 -0500 (EST) Cc: boot@itchy.mosquito.com (Bruce Bauman) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org Precedence: bulk We have a web/authentication server which serves our small ISP business. Currently, we handle 30 dialup lines via a Livingston portmaster. On our primary server (running FreeBSD 2.1), we see: in_rtqtimo: adjusted rtq_reallyold to 2400 in_rtqtimo: adjusted rtq_reallyold to 1600 in_rtqtimo: adjusted rtq_reallyold to 1066 in_rtqtimo: adjusted rtq_reallyold to 710 This server sees moderate web traffic, but is otherwise lightly used. Perhaps 2 or 3 shell accounts logged in at a time. It's also our mail hub. Should we be concerned about this? Are there any config file changes we might want to make to increase the amount of space for routes? Also, is it possible to get a copy of the config file for the ftp server used at Walnut Creek? I would imagine it's tuned for heavy network demand, which is probably applicable to us. Thanks in advance. -- Bruce Bauman Mosquito Net, Inc. From owner-freebsd-isp Mon Jan 22 06:09:42 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA14022 for isp-outgoing; Mon, 22 Jan 1996 06:09:42 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA14000 for ; Mon, 22 Jan 1996 06:09:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id GAA15312; Mon, 22 Jan 1996 06:09:33 -0800 Message-Id: <199601221409.GAA15312@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Bruce Bauman cc: freebsd-isp@freebsd.org Subject: Re: in_rtqtimo: adjusted rtq_reallyold to 1600 In-reply-to: Your message of "Mon, 22 Jan 1996 08:55:12 EST." <199601221355.IAA29999@itchy.mosquito.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 22 Jan 1996 06:09:33 -0800 Sender: owner-isp@freebsd.org Precedence: bulk >We have a web/authentication server which serves our small ISP business. >Currently, we handle 30 dialup lines via a Livingston portmaster. On our >primary server (running FreeBSD 2.1), we see: > >in_rtqtimo: adjusted rtq_reallyold to 2400 >in_rtqtimo: adjusted rtq_reallyold to 1600 >in_rtqtimo: adjusted rtq_reallyold to 1066 >in_rtqtimo: adjusted rtq_reallyold to 710 > >This server sees moderate web traffic, but is otherwise lightly used. Perhaps >2 or 3 shell accounts logged in at a time. It's also our mail hub. > >Should we be concerned about this? Are there any config file changes we might >want to make to increase the amount of space for routes? The messages can be ignored. >Also, is it possible to get a copy of the config file for the ftp server >used at Walnut Creek? I would imagine it's tuned for heavy network demand, >which is probably applicable to us. I'll attach a copy, but it likely will be only marginally useful without the kernel source changes I've made as well. It's also been tuned to the hardware configuration - especially the amount of RAM, 256MB, and may not work correctly on machines with less memory. Handling 650 users is a difficult thing to do. :-) Over the past 12 months, I've turned many of the tweaks into config-file controllable things and have been slowly trickling them into the main (-current) source tree. Wcarchive has proven to be a good place to expose stress related bugs and performance problems. -DG David Greenman Core Team/Principal Architect, The FreeBSD Project # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.41 1995/04/10 19:13:51 phk Exp $ # machine "i386" cpu "I586_CPU" ident WCARCHIVE maxusers 300 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=10" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options DDB options "NMBCLUSTERS=8192" options KTRACE options "MAXMEM=262144" options DODUMP options "TCBHASHSIZE=1024" options AHC_TAGENABLE options "AUTO_EOI_1" config kernel root on sd0 dumps on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #controller ncr0 # The three PCI 2940 controllers controller ahc0 controller ahc1 controller ahc2 controller ahc3 controller ahc4 controller scbus0 at ahc0 controller scbus1 at ahc1 controller scbus2 at ahc4 device sd0 device st0 #device cd0 disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 disk sd4 at scbus0 target 4 disk sd5 at scbus0 target 5 disk sd6 at scbus0 target 6 disk sd10 at scbus1 target 0 disk sd11 at scbus1 target 1 disk sd12 at scbus1 target 2 disk sd13 at scbus1 target 3 disk sd14 at scbus1 target 4 disk sd15 at scbus1 target 5 disk sd16 at scbus1 target 6 disk sd20 at scbus2 target 0 disk sd21 at scbus2 target 1 disk sd22 at scbus2 target 2 disk sd23 at scbus2 target 3 disk sd24 at scbus2 target 4 disk sd25 at scbus2 target 5 disk sd26 at scbus2 target 6 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device de0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pty 32 pseudo-device speaker pseudo-device snp 3 From owner-freebsd-isp Mon Jan 22 06:22:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA14817 for isp-outgoing; Mon, 22 Jan 1996 06:22:57 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA14810 for ; Mon, 22 Jan 1996 06:22:54 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA26703; Mon, 22 Jan 1996 08:21:51 -0600 From: Joe Greco Message-Id: <199601221421.IAA26703@brasil.moneng.mei.com> Subject: Re: SMDS? DS3-capable sync cards? To: jdd@vbc.net (Jim Dixon) Date: Mon, 22 Jan 1996 08:21:50 -0600 (CST) Cc: FreeBSD-isp@freebsd.org In-Reply-To: from "Jim Dixon" at Jan 22, 96 12:53:40 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org Precedence: bulk > Does anyone know of a source for PC-compatible (EISA or PCI) > sync serial cards that can handle data at DS3 speeds (34 Mbps), > preferably with SMDS drivers, preferably for FreeBSD?? No, Emerging Technologies (dennis@etinc.com ?) makes sync serial cards for E1/T1 speeds. Most people who have the need for a DS3 circuit don't seem to mind popping for a Cisco router and the other trimmings... I don't think anybody has such a product. ... JG From owner-freebsd-isp Mon Jan 22 08:31:43 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA24592 for isp-outgoing; Mon, 22 Jan 1996 08:31:43 -0800 (PST) Received: from nevis.oss.uswest.net (nevis.oss.uswest.net [204.147.85.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA24580 Mon, 22 Jan 1996 08:31:36 -0800 (PST) Received: (from greg@localhost) by nevis.oss.uswest.net (8.6.12/8.6.12) id KAA29506; Mon, 22 Jan 1996 10:31:01 -0600 From: "Greg Rowe" Message-Id: <9601221031.ZM29504@nevis.oss.uswest.net> Date: Mon, 22 Jan 1996 10:31:00 -0600 X-Mailer: Z-Mail (3.2.1 10oct95) To: freebsd-security@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Netscape & S/Key Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-isp@FreeBSD.ORG Precedence: bulk I currently have a FreeBSD system that allows users to update/create their WEB pages via S/Key access to a virtual FTP server. I'm now looking at creating another similar system that allows a Netscape user to retrieve files based on a one time password. I currently use the Apache server. Since users would only access the server once to download updates, and I need to control the access, none of the HTTPD password utilities really apply. It's much nicer to just print out a list of one time passwords once and a while and not have to worry about managing databases. The virtual FTP seems to be out due to Netscape setting "annonymous" as the default login user. Has anyone tried to interface the Apache server to FreeBSD's S/Key login so that rather than use the htpassword routines it uses S/Key? Thanks, Greg Rowe -- Greg Rowe | U S West - Interact Services | INTERNET greg@uswest.net 111 Washington Ave. South | Fax: (612) 672-8537 Minneapolis, MN USA 55401 | Voice: (612) 672-8535 Never trust an operating system you don't have source for.... From owner-freebsd-isp Mon Jan 22 08:47:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA25656 for isp-outgoing; Mon, 22 Jan 1996 08:47:39 -0800 (PST) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA25649 for ; Mon, 22 Jan 1996 08:47:35 -0800 (PST) Received: by haven.uniserve.com id <30755-4>; Mon, 22 Jan 1996 08:50:11 -0000 Date: Mon, 22 Jan 1996 08:50:07 -0800 (PST) From: Tom Samplonius To: Bruce Bauman cc: freebsd-isp@freebsd.org Subject: Re: in_rtqtimo: adjusted rtq_reallyold to 1600 In-Reply-To: <199601221355.IAA29999@itchy.mosquito.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk On Mon, 22 Jan 1996, Bruce Bauman wrote: > We have a web/authentication server which serves our small ISP business. > Currently, we handle 30 dialup lines via a Livingston portmaster. On our > primary server (running FreeBSD 2.1), we see: > > in_rtqtimo: adjusted rtq_reallyold to 2400 > in_rtqtimo: adjusted rtq_reallyold to 1600 > in_rtqtimo: adjusted rtq_reallyold to 1066 > in_rtqtimo: adjusted rtq_reallyold to 710 Completely harmless. This is more a debug message only. Basically, what is happening, is that the timeout for clone-routes is increasing. Tom From owner-freebsd-isp Mon Jan 22 09:26:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA29153 for isp-outgoing; Mon, 22 Jan 1996 09:26:57 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA29032 Mon, 22 Jan 1996 09:25:48 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id RAA21441; Mon, 22 Jan 1996 17:24:01 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 22 Jan 1996 17:24:11 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id RAA09401; Mon, 22 Jan 1996 17:24:12 GMT From: Paul Richards Message-Id: <199601221724.RAA09401@cadair.elsevier.co.uk> Subject: Re: Netscape & S/Key To: greg@uswest.net (Greg Rowe) Date: Mon, 22 Jan 1996 17:24:12 +0000 (GMT) Cc: freebsd-security@FreeBSD.org, freebsd-isp@FreeBSD.org In-Reply-To: <9601221031.ZM29504@nevis.oss.uswest.net> from "Greg Rowe" at Jan 22, 96 10:31:00 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.org Precedence: bulk In reply to Greg Rowe who said > > The virtual FTP seems to be out due to Netscape setting "annonymous" as the > default login user. Has anyone tried to interface the Apache server to > FreeBSD's S/Key login so that rather than use the htpassword routines it uses > S/Key? You would be better off talking to the apache guys about this. Apache has a nice modular approach so you can replace the existing authentication with a module based on what you want fairly easily I think. Take a look at the Apache home page (apache.org) and find out how to contact them. I don't think the development list allows open mailing but the web pages should explain how to contact the group. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-isp Mon Jan 22 12:57:05 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA12893 for isp-outgoing; Mon, 22 Jan 1996 12:57:05 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA12885 Mon, 22 Jan 1996 12:56:55 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA08064; Mon, 22 Jan 1996 21:55:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA09034; Mon, 22 Jan 1996 21:55:45 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id VAA06998; Mon, 22 Jan 1996 21:46:01 +0100 (MET) From: J Wunsch Message-Id: <199601222046.VAA06998@uriah.heep.sax.de> Subject: Re: FreeBSD-current Proxy Server in our company (vs. Sun) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 22 Jan 1996 21:46:01 +0100 (MET) Cc: joerg_wunsch@uriah.heep.sax.de, andreas@knobel.gun.de, jmb@FreeBSD.org, isp@FreeBSD.org, jkh@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <851.822251119@time.cdrom.com> from "Jordan K. Hubbard" at Jan 21, 96 11:05:19 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-isp@FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > > For PCI, the DEC 2104X-based cards are certainly the first choice, or > > the 3c590 with the `vx' driver pulled out of -current. See my other > > mail. I've heard that the 3c595 doesn't run well yet (it's a 10/100 > > Mbit/s board). > > Check this out: > > Subject: Patch and manual page for if_vx driver Forwarded to the guy who has been reporting the problems to me. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-isp Wed Jan 24 09:35:15 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA07573 for isp-outgoing; Wed, 24 Jan 1996 09:35:15 -0800 (PST) Received: from em.parsec.it (root@[194.177.110.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA07517 for ; Wed, 24 Jan 1996 09:34:32 -0800 (PST) Received: from localhost.dnet.it ([151.99.214.108]) by em.parsec.it (8.6.9/8.6.9) with ESMTP id SAA08367 for ; Wed, 24 Jan 1996 18:38:51 +0100 Received: (from andi@localhost) by localhost.dnet.it (8.7.2/8.7.2) id SAA00185; Wed, 24 Jan 1996 18:33:38 +0100 (MET) Date: Wed, 24 Jan 1996 18:33:38 +0100 (MET) From: Andreas Mutschlechner To: freebsd-isp@freebsd.org Subject: sendmail, pop and uucp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk HallO! Some of our clients have an own domain (or subdomain). The mail-exchanger for them is our mailserver because they are connected offline to the internet. The problem is how they can retrieve the mail from our mailserver. With uucp shouldn't be a great problem (if I manage to configure sendmail) but I have heard that other ISP use a modified spop. Some ideas? greets andi From owner-freebsd-isp Wed Jan 24 11:05:38 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA12730 for isp-outgoing; Wed, 24 Jan 1996 11:05:38 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12714 for ; Wed, 24 Jan 1996 11:05:20 -0800 (PST) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0tfAUF-000AmWC; Wed, 24 Jan 96 11:04 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Re: sendmail, pop and uucp To: andi@dnet.it (Andreas Mutschlechner) Date: Wed, 24 Jan 1996 11:04:03 -0800 (PST) Cc: freebsd-isp@freebsd.org In-Reply-To: from "Andreas Mutschlechner" at Jan 24, 96 06:33:38 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org Precedence: bulk > The problem is how they can retrieve the mail from our mailserver. I have a hack in my smail transports file: localuser: driver=appendfile, # append message to a file return_path, # include a Return-Path: field from, # supply a From_ envelope line unix_from_hack, # insert > before From in body local; # use local forms for delivery file=/var/mail/localuser, # location of mailbox files # group=mail, # group to own file for System V user=localuser, mode=0600, # For BSD: only the user can # read and write file # mode=0660, # under System V, group mail can access # use this for SCO UNIX, as well suffix="\n" # append an extra newline Then I just use the usual forwarding mechanism to route their domain to this transport. -- Alan Batie ______ batie@agora.rdrop.com \ / Freedom for me to be and do +1 503 452-0960 \ / only what *you* approve of 45 28 59 N / 122 43 20 W / 440' MSL \/ is no freedom at all. It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. From owner-freebsd-isp Wed Jan 24 12:25:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA17477 for isp-outgoing; Wed, 24 Jan 1996 12:25:48 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA17464 for ; Wed, 24 Jan 1996 12:25:25 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA00447; Wed, 24 Jan 1996 13:34:58 -0600 From: Joe Greco Message-Id: <199601241934.NAA00447@brasil.moneng.mei.com> Subject: Re: sendmail, pop and uucp To: andi@dnet.it (Andreas Mutschlechner) Date: Wed, 24 Jan 1996 13:34:57 -0600 (CST) Cc: freebsd-isp@freebsd.org In-Reply-To: from "Andreas Mutschlechner" at Jan 24, 96 06:33:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org Precedence: bulk > HallO! > > Some of our clients have an own domain (or subdomain). The mail-exchanger > for them is our mailserver because they are connected offline to the > internet. The problem is how they can retrieve the mail from our > mailserver. With uucp shouldn't be a great problem (if I manage to > configure sendmail) but I have heard that other ISP use a modified spop. > Some ideas? Add FEATURE(mailertable) to your mc file and use UUCP. It avoids the headaches of having to maintain information on your client user populations, you are simply concerned with forwarding them their mail, regardless of usernames and the rest. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-isp Thu Jan 25 15:11:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA15881 for isp-outgoing; Thu, 25 Jan 1996 15:11:48 -0800 (PST) Received: from mail.vividnet.com (mail.vividnet.com [206.149.144.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA15875 for ; Thu, 25 Jan 1996 15:11:43 -0800 (PST) Received: from aquarius.vividnet.com (postmaster@mail.vividnet.com) by mail.vividnet.com (8.6.12/8.6.9) with ESMTP id PAA07399 for ; Thu, 25 Jan 1996 15:09:43 -0800 Received: (postmaster@aquarius.vividnet.com) by aquarius.vividnet.com (8.6.12/8.6.9) id PAA07575; Thu, 25 Jan 1996 15:10:08 -0800 Date: Thu, 25 Jan 1996 15:10:08 -0800 (PST) From: Brian Wang To: freebsd-isp@freebsd.org Subject: restrict user ftp access Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk Hi, We are using wu-ftpd2.4 on our shell account server for users to do file transfers, and it is working just fine. However, they are able to browse/cd the system freely. Is there a patch available to restrict users to their $HOME directory while in ftp? Thanks, Sincerely, Brian Wang From owner-freebsd-isp Sat Jan 27 05:06:15 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA09805 for isp-outgoing; Sat, 27 Jan 1996 05:06:15 -0800 (PST) Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA09800 Sat, 27 Jan 1996 05:06:11 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id IAA09325; Sat, 27 Jan 1996 08:03:21 -0500 From: Peter Dufault Message-Id: <199601271303.IAA09325@hda.com> Subject: DIGI drivers again To: tim@sssun.spb.su Date: Sat, 27 Jan 1996 08:03:20 -0500 (EST) Cc: dennis@etinc.com, hackers@FreeBSD.org, isp@FreeBSD.org In-Reply-To: from "Andrew Timonin" at Jan 27, 96 09:47:51 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.org Precedence: bulk > I think no. Linux have just the same problems with multiport cards as > FreeBSD. From technical point of view I myself would prefer some > Digiboard, but because of a very restrictive policy of this company > on the design of inner parts of card design it's nearly impossible to > implement a good driver without a NDA. Anyone interested in full DIGI support and willing to spend some money please send me private e-mail. If we can get together enough to offset the problems associated with a binary only NDA driver, e.g., tracking the OS releases, HDA being the soul support point for problems with the drivers, and HDA having to purchase the hardware, then I'll implement an NDA binary only driver. Let me know what product you are interested and how much you're willing to spend per year for a DIGI driver support contract. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267