From owner-freebsd-isp Sun Sep 15 04:18:07 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA15264 for isp-outgoing; Sun, 15 Sep 1996 04:18:07 -0700 (PDT) Received: from grumpy.net.na (grumpy.net.na [196.20.23.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA15194 for ; Sun, 15 Sep 1996 04:17:31 -0700 (PDT) Received: from by grumpy.net.na with cbsmtp (Linux 1.0.8 Smail3.1.29.1 #9) id m0v2504-000pvPC; Sun, 15 Sep 96 02:23 GMT+0200 Received: (from el@localhost) by linux.lisse.NA (8.7.5/8.7.3/el) id XAA04224; Sat, 14 Sep 1996 23:02:23 +0100 From: Dr Eberhard W Lisse Message-Id: <199609142202.XAA04224@linux.lisse.NA> Subject: Re: Internet MELTS DOWN AT END 1996?? To: jay@result.com (Jay Thorne) Date: Sat, 14 Sep 1996 23:02:22 +0100 (GMT+0100) Cc: michael@memra.com, IAP@VMA.CC.ND.EDU, inet-access@earth.com, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com In-Reply-To: from "Jay Thorne" at Sep 14, 96 01:34:39 am Organization: Swakopmund State Hospital Reply-To: X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jay, > The thing that pisses me off the _most_? Idiots who write _about_ > tech the same way that the writers for 'Baywatch' write about search > and rescue operations. Ie, the "Internet Meltdown" article was the > same level of sensationalized fiction. But he is right in some ways, isn't he? I have had a very interesting dogfight some three years ago with an eminent chap from Orgeon about Autonomous System Numbers and who assigns IP numbers to independent countries. Now he is a member of the engineering task force and all, but I maintained that national networks in such countries should get the numbers from NIC. I also think we should get our own ASN, but this is much, much less of an issue and can be easily resolved once technically required so I never pursued this line of argument. However they feel that either we should get them from RIPE (why Europe's NIC is supposed to do this for Africa is beyond my and others' comprehension, not withstanding the fact that those RIPErs are very nice, helpful and extremely competent people) or and that was advanced stronger that we should get the IP numbers from our access provider, currently the academic network in South Africa. Non withstanding the fact that that would require renumbering if we changed our access provider. It was already then said that the biggies would not route ASNs *BEHIND* ASNs connected to them, in other words if we got us one we'd not be routed. Now the reason advanced was: "Do you want to route packets, or what?" Then already I was quite irritated by the fact that those biggies send their staff to the IETF and so on and make the rules to suit themselves. The Internet is a non entity, legally speaking. In other words, it's not so that small developing countries, such as Namibia, and Lesotho which was the origin of the argument by the way, have to go on the knees and beg to have a multinational company allow us to connect. It just aint so. There is just no technical reason for this refusal to route. It is purely a financial matter, and multinational companies having a monopoly with their brigades of ruthless marketing and ligitation staff of course try to maximise profits. And of course they send their technical staff to IETF and write the rules the way they want. I maintain that those small networks allow the Internet to connect to us as much as we are allowed to connect to the Internet. *AND*, they can do whatever they want, once they start turning off non-customers, they will be hit with anti trust suits that will drive them out of business, or at least it will drive this nonsense out of their heads very, very quickly. The domain name court cases are examples in kind, they have just no leg to stand on. Nobody denies the problems we all face, and the fact that we must fix them somehow, very very urgently, but this must be done fairly. el -- Dr. Eberhard W. Lisse \ / Swakopmund State Hospital * | Resident Medical Officer Private Bag 5004 \ / +264 64 461503 (pager) 461005 (h) 461004 (f) Swakopmund, Namibia ;____/ Zone/Domain Contact for the NA-DOM Vice-Chairman, Board of Trustees, Namibian Internet Development Foundation, an Association not for Gain. NAMIDEF is the Namibian Internet Service Provider. From owner-freebsd-isp Sun Sep 15 04:19:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA15382 for isp-outgoing; Sun, 15 Sep 1996 04:19:37 -0700 (PDT) Received: from grumpy.net.na (grumpy.net.na [196.20.23.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA15370 for ; Sun, 15 Sep 1996 04:19:23 -0700 (PDT) Received: from by grumpy.net.na with cbsmtp (Linux 1.0.8 Smail3.1.29.1 #9) id m0v25CB-000pzIC; Sun, 15 Sep 96 02:36 GMT+0200 Received: (from el@localhost) by linux.lisse.NA (8.7.5/8.7.3/el) id XAA04286; Sat, 14 Sep 1996 23:30:13 +0100 From: Dr Eberhard W Lisse Message-Id: <199609142230.XAA04286@linux.lisse.NA> Subject: Re: Internet MELTS DOWN AT END 1996?? To: michael@memra.com (Michael Dillon) Date: Sat, 14 Sep 1996 23:30:11 +0100 (GMT+0100) Cc: IAP@VMA.CC.ND.EDU, inet-access@earth.com, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com In-Reply-To: from "Michael Dillon" at Sep 14, 96 00:35:42 am Organization: Swakopmund State Hospital Reply-To: X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael, you make some very good points... > G) This thing about trade laws is silly. Trade laws have no effect > whatsoever on technology and technical capability. If there was > a law that an airline could not refuse you a seat on an airline > if you were there an hour ahead of time, would it make any difference? > No, because when the plane is full, it is full and laws cannot > change that. Ah well, if it's a train that the law says has to take you on board if it is full, they just hang on another wagon. > I) The Internet has *ALWAYS* been on the verge of collapse and > probably always will be. This is better known as the free market > as opposed to a monopoly market. The telcos have a monopoly > so they can make you pay big bucks for an over-engineered network. > But in a free market situation, the tier 1 NSP's, the tier 2 RNP's > (Regional Network Providers) and the ISP's at tier 3 only add > capacity when customers are ready to order and pay for that > capacity. This is good because it keeps prices under control and > relatively flat rate. This is hardly free market, the tier 1 NSPs have a monoploy. > Q) The column talks about Sprint's route filters as if they target small > ISP's when in reality they target small networks who also have the > mistaken idea that they can bypass the address allocation hierarchy and > still get working addresses. Then it talks about address crowding which > has nothing whatsoever to do with Sprint's filters. The filters are > there as part of the impetus to reduce the size of the global routing > table so it is not filled with garbage like this: > > 208.10.16/24 Fred's ISP --> send to Big ISP > 208.10.17/24 Widget World --> send to Big ISP > 208.10.18/24 Malls Electric --> send to Big ISP > 208.10.19/24 Billy's BBS --> send to Big ISP > > Instead it should look like this > > 208.10.16/22 Some BIG ISP customers --> send to Big ISP > > which takes up less global routing table space and still > gets the traffic where it is supposed to go. But this is not a technical requirement, this is a financial matter. *AND* in order to make these decisions one must have a mandate. In other words, *WHO* authorized the IETF to make such decisions? I certainly didn't. > U) The hierarchical IP numbering scheme being discussed is in fact the > scheme in place today and it has been so for some time. The IETF and > IANA merely want to document this scheme and clarify it by publishing > a Best Common Practices RFC so that it is easier for everybody to > understand and explain what is going one. If this would cause you > hardship, tough bananas! That's life. This is how things are in order > to make the Internet operate effectively and if you didn't know this > and make engineering and business plans accordingly then that's > your problem. But it's never too late to educate yourself and to > adjust your engineering and your policies to lessen the negative > impact of hierarchical addressing. It's not life. It's not how things are. It's how companies with leverage find it expedient to enforce. > Z) There is no power in owning IP address blocks because at the > present time IP addresses are not owned. Right now the power > is in having a *WORKING* IP address block and that is intimately tied > in to your choice of upstream provider. And if you change providers > then you will have to change IP address blocks in order to retain > that power of having a working address. Well, again, no mythical body, or a NIC that I did not authorize to do so can decide what I have to do with my CIDR block(s). And fortunately ours is allocated by NIC (as it should) and not by our upstream provider, who however announces the aggregate. Again, I do understand the reason for the way they are going about it, but I don't agree with them. And just because they have leverage doesn't make it right. And I would think sooner or later an ISP will ask a federal judge what he thinks about it. el -- Dr. Eberhard W. Lisse \ / Swakopmund State Hospital * | Resident Medical Officer Private Bag 5004 \ / +264 64 461503 (pager) 461005 (h) 461004 (f) Swakopmund, Namibia ;____/ Zone/Domain Contact for the NA-DOM Vice-Chairman, Board of Trustees, Namibian Internet Development Foundation, an Association not for Gain. NAMIDEF is the Namibian Internet Service Provider. From owner-freebsd-isp Sun Sep 15 08:25:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22929 for isp-outgoing; Sun, 15 Sep 1996 08:25:35 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22918 for ; Sun, 15 Sep 1996 08:25:31 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id RAA04048 for ; Sun, 15 Sep 1996 17:22:57 +0200 Message-Id: <199609151522.RAA04048@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.Org" Date: Sun, 15 Sep 96 16:32:50 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Denying expired users POP? Sender: owner-isp@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk Is there any pop daemons/patches for qpopper that checks if the user is expired or not before sending out the mail? --------------------------------- Frode Nordahl From owner-freebsd-isp Sun Sep 15 11:11:10 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05022 for isp-outgoing; Sun, 15 Sep 1996 11:11:10 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA05016 for ; Sun, 15 Sep 1996 11:11:08 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id KAA18423; Sun, 15 Sep 1996 10:24:26 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id LAA13136; Sun, 15 Sep 1996 11:08:39 -0700 Date: Sun, 15 Sep 1996 11:08:36 -0700 (PDT) From: Michael Dillon To: IAP@VMA.CC.ND.EDU cc: inet-access@earth.com, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Re: Internet MELTS DOWN AT END 1996?? In-Reply-To: <199609142202.XAA04224@linux.lisse.NA> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Sep 1996, Dr Eberhard W Lisse wrote: > Now he is a member of the engineering task force and all, but I You could be too. Just attend two meetings, I believe, and you are a member. > Then already I was quite irritated by the fact that those biggies send > their staff to the IETF and so on and make the rules to suit > themselves. The IETF consists of individuals who do *NOT* represent their companies or organizations. If they change jobs they still maintain any IETF positions they hold. > It just aint so. There is just no technical reason for this refusal to > route. It is purely a financial matter, and multinational companies > having a monopoly with their brigades of ruthless marketing and > ligitation staff of course try to maximise profits. And of course they > send their technical staff to IETF and write the rules the way they > want. You are seriously confused here as is most of Africa no doubt. This is probably a result of the colonial legacy and in your case your German background. You are looking for an official hierarchy, for official channels, for bosses who have the power to say yes. Unfortunately these do not exist. If you want an African NIC, you can have one. It is a publicly stated policy that there will be NIC's for continent sized areas. To get a NIC for Africa you need to do several things. 1) Get a majority of the countries to agree. This is not political or government issue. Just get the significant people who are doing internetworking to agree to make use of and support an Africa-NIC. 2) Learn how to allocate IP addresses properly. Especially, understand the limits of portability and understand how organizations can use RFC1918 addresses along with NAT (Network Address Translation) and ALG's (Application Layer Gateways) to achieve immunity from renumbering. Cisco will have NAT in IOS 11.2 for all its routers. Linux and FreeBSD already have it. A prominent free ALG is TIS Firewalls Toolkit. Read this ftp://rs.internic.net/policy/internic/internic-ip-1.txt and read this ftp://ietf.org/internet-drafts/draft-hubbard-registry-guidelines-05.txt and send some email to kimh@internic.net for advice. 3) Then with knowledge and with the consensus of most of Africa's internetworking community, apply to IANA iana@isi.edu for the rights to operate your Africa-NIC. You will get those rights. Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com From owner-freebsd-isp Sun Sep 15 11:17:05 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05438 for isp-outgoing; Sun, 15 Sep 1996 11:17:05 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA05431 for ; Sun, 15 Sep 1996 11:17:03 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id KAA18508; Sun, 15 Sep 1996 10:30:36 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id LAA13184; Sun, 15 Sep 1996 11:14:49 -0700 Date: Sun, 15 Sep 1996 11:14:47 -0700 (PDT) From: Michael Dillon To: IAP@VMA.CC.ND.EDU cc: inet-access@earth.com, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Re: Internet MELTS DOWN AT END 1996?? In-Reply-To: <199609142230.XAA04286@linux.lisse.NA> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Sep 1996, Dr Eberhard W Lisse wrote: > > No, because when the plane is full, it is full and laws cannot > > change that. > > Ah well, if it's a train that the law says has to take you on board if > it is full, they just hang on another wagon. There are no more wagons and every square inch of the roof is already packed and people are already hanging on the sides of the wagons. > > there as part of the impetus to reduce the size of the global routing > > table so it is not filled with garbage like this: > > > > 208.10.16/24 Fred's ISP --> send to Big ISP > > 208.10.17/24 Widget World --> send to Big ISP > > 208.10.18/24 Malls Electric --> send to Big ISP > > 208.10.19/24 Billy's BBS --> send to Big ISP > > > > Instead it should look like this > > > > 208.10.16/22 Some BIG ISP customers --> send to Big ISP > > > > which takes up less global routing table space and still > > gets the traffic where it is supposed to go. > > But this is not a technical requirement, this is a financial > matter. No, it's a technical matter. If the global routing tables get too big then the routers that depend on them have a harder time doing their job. And if four consecutive IP numbers all go out the same interface it makes technical sense to aggregate them from four 24-bit prefixes to one 22-bit prefix. Study that example carefully and you will understand. It may help to write out the IP numbers in binary and look at the bits. > *AND* in order to make these decisions one must have a > mandate. In other words, *WHO* authorized the IETF to make such > decisions? I certainly didn't. It has nothing to do with IETF. The people who operate the networks don't want their routing tables full of unneccessary junk. Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com From owner-freebsd-isp Sun Sep 15 12:42:42 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10160 for isp-outgoing; Sun, 15 Sep 1996 12:42:42 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10041 for ; Sun, 15 Sep 1996 12:39:44 -0700 (PDT) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id VAA01298 for ; Sun, 15 Sep 1996 21:38:38 +0200 (MET DST) X-Sender: petzi@mail.zit.th-darmstadt.de Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 15 Sep 1996 21:38:40 +0200 To: isp@freebsd.org From: petzi@zit.th-darmstadt.de (Michael Beckmann) Subject: INN history file and disk I/O Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello ISPs, I have run into a problem with one of my newsservers recently. It is a P120, 64 MB, Adaptec 2940, 3 SCSI drives running FreeBSD 980801-SNAP. INN version 1.4unoff4. It receives and sends several full feeds, but is hardly used by readers. In general, the performance of this system is good; I see about 5 - 10 % cpu load and almost no swap usage. I get immediate response from the system, except when I try to telnet to the nntp port. nntp readers simply time out; it takes forever until the INN prompt appears, if it appears at all. This situation changes when I throttle the INN. Then I get the INN prompt immediately. Using systat -vm, I have found out that it has 80 - 100 disk seeks per second on the disk that carries the history file (which is about 90 MB large). When I move the history file, it is the other disk that gets hit, so it definitely is the history file that causes this I/O. Could this be the reason for my problem ? Sometimes I see messages like this in the log: Sep 15 21:07:00 news innd: ME cant sendto CCreader bytes 4 No such file or directory I don't know if this is relevant here. Any experiences on how to deal with that ? Suggestions are welcome. Michael From owner-freebsd-isp Sun Sep 15 13:45:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13092 for isp-outgoing; Sun, 15 Sep 1996 13:45:04 -0700 (PDT) Received: from bbs.mpcs.com (hgoldste@bbs.mpcs.com [204.215.226.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13080 for ; Sun, 15 Sep 1996 13:44:58 -0700 (PDT) Received: (from hgoldste@localhost) by bbs.mpcs.com (8.7.5/8.7.3/MPCS) id QAA08224; Sun, 15 Sep 1996 16:44:47 -0400 Date: Sun, 15 Sep 1996 16:44:47 -0400 From: Howard Goldstein Message-Id: <199609152044.QAA08224@bbs.mpcs.com> To: freebsd-isp@freebsd.org Subject: Re: INN history file and disk I/O In-Reply-To: Reply-To: hgoldste@bbs.mpcs.com Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , you wrote: : I have run into a problem with one of my newsservers recently. It is a : P120, 64 MB, Adaptec 2940, 3 SCSI drives running FreeBSD 980801-SNAP. INN : version 1.4unoff4. It receives and sends several full feeds, but is hardly : used by readers. same config here except kernel and ide (echhh) drives : Using systat -vm, I have found out that it has 80 - 100 disk seeks per : second on the disk that carries the history file (which is about 90 MB : large). When I move the history file, it is the other disk that gets hit, : so it definitely is the history file that causes this I/O. Could this be : the reason for my problem ? I see a similar hit on history, maybe 10x as many seeks as compared to the drives holding overview and spool. : : Sometimes I see messages like this in the log: : Sep 15 21:07:00 news innd: ME cant sendto CCreader bytes 4 No such file or : directory : I don't know if this is relevant here. Got these too, many of them, just before the news.daily report is generated. : : Any experiences on how to deal with that ? Suggestions are welcome. First try hardcoding IP addresses in nnrp.access in case you're getting killed during the hostbyaddress lookup. You didn't mention if you have MMAP turned on anywhere (we don't), or running any non standard stuff like shared active, nntplink, etc. Last resort might be to back off of SNAP. 2.1.5R Release kernel works fine with an acceptable reader startup delay. -- Howard Goldstein From owner-freebsd-isp Sun Sep 15 15:53:00 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA20286 for isp-outgoing; Sun, 15 Sep 1996 15:53:00 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA20280 for ; Sun, 15 Sep 1996 15:52:58 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id SAA21893; Sun, 15 Sep 1996 18:52:30 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: petzi@zit.th-darmstadt.de (Michael Beckmann) cc: isp@freebsd.org From: "Gary Palmer" Subject: Re: INN history file and disk I/O In-reply-to: Your message of "Sun, 15 Sep 1996 21:38:40 +0200." Date: Sun, 15 Sep 1996 18:52:30 -0400 Message-ID: <21889.842827950@orion.webspan.net> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Beckmann wrote in message ID : > Hello ISPs, > > I have run into a problem with one of my newsservers recently. It is a > P120, 64 MB, Adaptec 2940, 3 SCSI drives running FreeBSD 980801-SNAP. INN > version 1.4unoff4. It receives and sends several full feeds, but is hardly > used by readers. > In general, the performance of this system is good; I see about 5 - 10 % > cpu load and almost no swap usage. I get immediate response from the > system, except when I try to telnet to the nntp port. nntp readers simply > time out; it takes forever until the INN prompt appears, if it appears at > all. This situation changes when I throttle the INN. Then I get the INN > prompt immediately. > Using systat -vm, I have found out that it has 80 - 100 disk seeks per > second on the disk that carries the history file (which is about 90 MB > large). When I move the history file, it is the other disk that gets hit, > so it definitely is the history file that causes this I/O. Could this be > the reason for my problem ? You could probably use more memory, since innd will try to keep the history file in memory. Also, if the machine(s) are receiving full feeds, there will be quite a lot of data being written to the history file. It could be thrashing however (since 90Mb > 64Mb) I only see (on average) < 20 seeks/sec on my history partition, except when update(8) does its job. > Sometimes I see messages like this in the log: > Sep 15 21:07:00 news innd: ME cant sendto CCreader bytes 4 No such file or > directory > I don't know if this is relevant here. Dunno about this. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-isp Sun Sep 15 16:01:55 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20723 for isp-outgoing; Sun, 15 Sep 1996 16:01:55 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20716 for ; Sun, 15 Sep 1996 16:01:39 -0700 (PDT) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id BAA12075 for ; Mon, 16 Sep 1996 01:01:00 +0200 (MET DST) X-Sender: michael@mail.zit.th-darmstadt.de Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 01:01:02 +0200 To: isp@freebsd.org From: petzi@zit.th-darmstadt.de (Michael Beckmann) Subject: Re: INN history file and disk I/O Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, >You didn't mention if you have MMAP turned on anywhere (we don't), or >running any non standard stuff like shared active, nntplink, etc. Thanks for the hints. No, I'm not running anything non standard, this is still a vanilla setup. I want to run nntplink / innfeed / whatever for my downstream fullfeeds, but as of yet, I'm using nntpsend. INN is compiled with MMAP turned off in config.data : ## 6. MISCELLANEOUS CONFIG DATA ## Use read/write to update the active file, or mmap? Pick READ or MMAP. #### =()@>()= ACT_STYLE READ Don't know if this should be on for FreeBSD, I will give it a try. The INN FAQ says: "FreeBSD users shouldn't use mmap(). There are serious problems and the performance without is quite good." but I assume that was meant for some old version of FreeBSD. >Last resort might be to back off of SNAP. 2.1.5R Release kernel works fine >with an acceptable reader startup delay. Yes, that would be a last resort. I have now reniced innd to -16, but it didn't help too much. If I don't find a solution until Monday, I will actually go back to 2.1.5-RELEASE (sigh). If I knew for sure that THAT helped, I would do it immediately. Michael From owner-freebsd-isp Sun Sep 15 16:51:15 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA23662 for isp-outgoing; Sun, 15 Sep 1996 16:51:15 -0700 (PDT) Received: from salsa.gv.ssi1.com (salsa.gv.ssi1.com [146.252.44.194]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA23655 for ; Sun, 15 Sep 1996 16:51:13 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.ssi1.com (8.7.5/8.7.3) id QAA04166; Sun, 15 Sep 1996 16:50:44 -0700 (PDT) From: Don Lewis Message-Id: <199609152350.QAA04166@salsa.gv.ssi1.com> Date: Sun, 15 Sep 1996 16:50:43 -0700 In-Reply-To: petzi@zit.th-darmstadt.de (Michael Beckmann) "INN history file and disk I/O" (Sep 15, 9:38pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: petzi@zit.th-darmstadt.de (Michael Beckmann), isp@freebsd.org Subject: Re: INN history file and disk I/O Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sep 15, 9:38pm, Michael Beckmann wrote: } Subject: INN history file and disk I/O } In general, the performance of this system is good; I see about 5 - 10 % } cpu load and almost no swap usage. I get immediate response from the } system, except when I try to telnet to the nntp port. nntp readers simply } time out; it takes forever until the INN prompt appears, if it appears at } all. This situation changes when I throttle the INN. Then I get the INN } prompt immediately. Are you receiving any streaming feeds? There are problems with INN that cause it become unresponsive because it can be monopolized by a streaming feed. --- Truck From owner-freebsd-isp Sun Sep 15 17:59:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA29684 for isp-outgoing; Sun, 15 Sep 1996 17:59:16 -0700 (PDT) Received: from npc.haplink.co.cn ([202.96.192.53]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA29609; Sun, 15 Sep 1996 17:58:40 -0700 (PDT) Received: (from xiyuan@localhost) by npc.haplink.co.cn (8.6.11/8.6.9) id JAA14492; Mon, 16 Sep 1996 09:05:21 GMT Date: Mon, 16 Sep 1996 09:05:21 GMT From: xiyuan qian Message-Id: <199609160905.JAA14492@npc.haplink.co.cn> To: isp@freebsd.org Subject: Can I limit the size of incoming mail message? Cc: questions@freebsd.org, steve@cioe.com Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, my problem is: when someone send one message large than 12M to my customer, it can NOT been recieved by the customer with some email software such as Eudora. I think someone can help me limit this happen. Best regaurds! --xiyuan From owner-freebsd-isp Sun Sep 15 19:18:06 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA04129 for isp-outgoing; Sun, 15 Sep 1996 19:18:06 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA04123 for ; Sun, 15 Sep 1996 19:18:02 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30 † id TAA08443; Sun, 15 Sep 1996 19:18:06 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id TAA14538; Sun, 15 Sep 1996 19:17:08 -0700 (PDT) Message-Id: <199609160217.TAA14538@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: hgoldste@bbs.mpcs.com cc: freebsd-isp@freebsd.org Subject: Re: INN history file and disk I/O In-reply-to: Your message of Sun, 15 Sep 96 16:44:47 -0400. <199609152044.QAA08224@bbs.mpcs.com> Date: Sun, 15 Sep 1996 19:17:08 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In article , you wrote: > : I have run into a problem with one of my newsservers recently. It is a > : P120, 64 MB, Adaptec 2940, 3 SCSI drives running FreeBSD 980801-SNAP. INN > : version 1.4unoff4. It receives and sends several full feeds, but is hardly > : used by readers. >same config here except kernel and ide (echhh) drives Ouch! I feel extremely sorry for anyone attempting to run a news feed on IDE drives... ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Sun Sep 15 20:15:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA06494 for isp-outgoing; Sun, 15 Sep 1996 20:15:48 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA06489 for ; Sun, 15 Sep 1996 20:15:46 -0700 (PDT) Received: from scapa.cs.ualberta.ca (root@scapa.cs.ualberta.ca [129.128.4.44]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id UAA18877 for ; Sun, 15 Sep 1996 20:15:41 -0700 (PDT) Received: from ve6kik by scapa.cs.ualberta.ca with UUCP id <13064-25190>; Sun, 15 Sep 1996 21:14:04 -0600 Received: by ve6kik.ampr.ab.ca (Smail3.1.28.1 #5) id m0v2TLG-000O5tC; Sun, 15 Sep 96 20:23 WET DST Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id UAA11560; Sun, 15 Sep 1996 20:08:15 -0600 (MDT) Date: Sun, 15 Sep 1996 20:08:14 -0600 (MDT) From: Marc Slemko To: Michael Beckmann cc: isp@FreeBSD.ORG Subject: Re: INN history file and disk I/O In-Reply-To: <199609152350.QAA04166@salsa.gv.ssi1.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Sep 1996, Don Lewis wrote: > On Sep 15, 9:38pm, Michael Beckmann wrote: > } Subject: INN history file and disk I/O > } In general, the performance of this system is good; I see about 5 - 10 % > } cpu load and almost no swap usage. I get immediate response from the > } system, except when I try to telnet to the nntp port. nntp readers simply > } time out; it takes forever until the INN prompt appears, if it appears at > } all. This situation changes when I throttle the INN. Then I get the INN > } prompt immediately. How long is forever? 10 seconds? 30 seconds? five minutes? > > Are you receiving any streaming feeds? There are problems with INN that > cause it become unresponsive because it can be monopolized by a streaming > feed. ...and if that is the problem, and you are running 1.4unoff4, applying the patch available at ftp://ftp.math.psu.edu/pub/INN/patches/apb-stream-prio.patch could possibly help. From owner-freebsd-isp Sun Sep 15 22:07:06 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11435 for isp-outgoing; Sun, 15 Sep 1996 22:07:06 -0700 (PDT) Received: from mail.greennet.net ([208.192.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA11429 for ; Sun, 15 Sep 1996 22:06:59 -0700 (PDT) Received: from admin (admin.greennet.net [208.192.4.5]) by mail.greennet.net (post.office MTA v1.9.3b ID# 0-16941) with SMTP id AAA170; Mon, 16 Sep 1996 01:05:19 -0400 Message-Id: <1.5.4.32.19960916050336.006b8b04@mail.greennet.net> X-Sender: valverde@mail.greennet.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 01:03:36 -0400 To: inet-access@earth.com, Small Internet Access Providers From: "Nelson Valverde" Subject: Re: Internet MELTS DOWN AT END 1996?? Cc: inet-access@earth.com, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:35 AM 9/14/96 -0700, Michael Dillon wrote: >*sigh* >That guy gets paid for writing his confusing mish-mash of a column >and I get paid nothing for writing this explanation which I have >gone to some trouble in making as accurate as possible. > Michael, Thank you for your generosity and willingness to share your knowledge without pay. This will not buy you groceries, but it will certainly make you a better person. -Nelson * GreenNet=================================mail.greennet.net===============* * "Link Locally ~ Surf Globally" http://www.greennet.net * * ` * * Serving the greater Pentucket, Newburyport and Haverhill areas in Mass. * * TEL: 508-363-8898 FAX: 508-363-1225 * *==========================================================================* From owner-freebsd-isp Sun Sep 15 22:34:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12299 for isp-outgoing; Sun, 15 Sep 1996 22:34:25 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12293 for ; Sun, 15 Sep 1996 22:34:20 -0700 (PDT) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id HAA02995; Mon, 16 Sep 1996 07:34:04 +0200 (MET DST) X-Sender: petzi@mail.zit.th-darmstadt.de Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 07:34:05 +0200 To: Marc Slemko , isp@freebsd.org From: petzi@zit.th-darmstadt.de (Michael Beckmann) Subject: Re: INN history file and disk I/O Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Sun, 15 Sep 1996, Don Lewis wrote: >> Are you receiving any streaming feeds? There are problems with INN that >> cause it become unresponsive because it can be monopolized by a streaming >> feed. > >...and if that is the problem, and you are running 1.4unoff4, applying the I do. >patch available at >ftp://ftp.math.psu.edu/pub/INN/patches/apb-stream-prio.patch could >possibly help. I will definitely try that out today. Thanks a lot for the valuable hint. Michael From owner-freebsd-isp Sun Sep 15 22:34:28 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12319 for isp-outgoing; Sun, 15 Sep 1996 22:34:28 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12298 for ; Sun, 15 Sep 1996 22:34:24 -0700 (PDT) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id HAA02944; Mon, 16 Sep 1996 07:32:49 +0200 (MET DST) X-Sender: petzi@mail.zit.th-darmstadt.de Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 07:32:50 +0200 To: Don Lewis , isp@freebsd.org From: petzi@zit.th-darmstadt.de (Michael Beckmann) Subject: Re: INN history file and disk I/O Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Are you receiving any streaming feeds? There are problems with INN that >cause it become unresponsive because it can be monopolized by a streaming >feed. Exactly. I'm getting a full streaming feed from Primenet, and they manage to send me > 10 articles per second at times... Michael From owner-freebsd-isp Sun Sep 15 23:11:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA13879 for isp-outgoing; Sun, 15 Sep 1996 23:11:25 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA13874 for ; Sun, 15 Sep 1996 23:11:21 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA05108; Mon, 16 Sep 96 01:11:13 -0500 Received: from fergus-17.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA16464; Mon, 16 Sep 96 01:11:11 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id QAA05113; Sun, 15 Sep 1996 16:48:04 -0500 (CDT) Date: Sun, 15 Sep 1996 16:48:04 -0500 (CDT) From: Tony Kimball Message-Id: <199609152148.QAA05113@compound.Think.COM> To: jgreco@brasil.moneng.mei.com Cc: isp@FreeBSD.ORG Subject: Re: Lame Server References: <1.5.4.32.19960913194022.0068c72c@nwpros.com> <199609132114.QAA03993@brasil.moneng.mei.com> Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Joe Greco on Fri, 13 September: : (But we all run DOC, etc, right?) What is that? From owner-freebsd-isp Sun Sep 15 23:20:21 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14378 for isp-outgoing; Sun, 15 Sep 1996 23:20:21 -0700 (PDT) Received: from wave.cyberbeach.net (wave.cyberbeach.net [205.150.79.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA14370 for ; Sun, 15 Sep 1996 23:20:18 -0700 (PDT) Received: from sail ([207.176.149.24]) by wave.cyberbeach.net (8.6.12/8.6.12) with SMTP id CAA01939 for ; Mon, 16 Sep 1996 02:20:16 -0400 Message-Id: <1.5.4.32.19960916182112.008c6ab0@post.cyberbeach.net> X-Sender: kurt@post.cyberbeach.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 14:21:12 -0400 To: freebsd-isp@freebsd.org From: Kurt Schafer Subject: Could use a favor Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been having problems getting some 2.1.5-RELEASE systems outputting data to the net. I've since brought up a machine on 2.1-RELEASE and put a plain-jane default apache process on the box. If people could try resolving http://wave.cyberbeach.net and drop me a message outlining their success/failure I would be appreciative. -Kurt From owner-freebsd-isp Mon Sep 16 05:59:00 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA02279 for isp-outgoing; Mon, 16 Sep 1996 05:59:00 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA02274 for ; Mon, 16 Sep 1996 05:58:58 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (zit1.zit.th-darmstadt.de [130.83.63.20]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id FAA19638 for ; Mon, 16 Sep 1996 05:58:25 -0700 (PDT) Received: from localhost (petzi@localhost) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id OAA28324; Mon, 16 Sep 1996 14:50:26 +0200 (MET DST) Date: Mon, 16 Sep 1996 14:50:25 +0200 (MET DST) From: Michael Beckmann To: Marc Slemko cc: isp@FreeBSD.ORG Subject: Re: INN history file and disk I/O In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Sep 1996, Marc Slemko wrote: > ...and if that is the problem, and you are running 1.4unoff4, applying the > patch available at > ftp://ftp.math.psu.edu/pub/INN/patches/apb-stream-prio.patch could > possibly help. Thanks a lot ! This was the solution. I applied that patch and recompiled innd, no problem with that. INN now gives me the prompt after a few seconds. This was several minutes before, and the readers timed out before the prompt appeared. It would be great if that patch could be included with the FreeBSD port of inn-current, so that noone else runs into that problem again. Michael From owner-freebsd-isp Mon Sep 16 07:41:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA07813 for isp-outgoing; Mon, 16 Sep 1996 07:41:23 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA07804 for ; Mon, 16 Sep 1996 07:41:19 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id QAA08913; Mon, 16 Sep 1996 16:38:48 +0200 Message-Id: <199609161438.QAA08913@login.bigblue.no> From: "Frode Nordahl" To: "Swee-Chuan Khoo" Cc: "isp@freebsd.org" Date: Mon, 16 Sep 96 15:48:33 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Denying expired users POP? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996 08:27:51 +0800, Swee-Chuan Khoo wrote: >At 04:32 PM 9/15/96 +0100, you wrote: >>Is there any pop daemons/patches for qpopper that checks if the user is >expired or not before sending out the >>mail? >>--------------------------------- >>Frode Nordahl >> >> >> > >yes, for expired user, we normally change their login shell, when compiling >qpopper, >make that shell to deny mail. That is not a option. I want it to use the expire date field in the passwd file. Changing the shell is just extra labour. --------------------------------- Frode Nordahl From owner-freebsd-isp Mon Sep 16 08:17:42 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA10372 for isp-outgoing; Mon, 16 Sep 1996 08:17:42 -0700 (PDT) Received: from radio.nwpros.com (nwpros.com [205.229.128.214]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA10367 for ; Mon, 16 Sep 1996 08:17:37 -0700 (PDT) Received: from rickbox.nwpros.com (rickbox.nwpros.com [205.229.128.217]) by radio.nwpros.com (8.6.12/8.6.12) with SMTP id KAA17274 for ; Mon, 16 Sep 1996 10:20:37 -0500 Message-Id: <1.5.4.32.19960916152842.0068ad1c@nwpros.com> X-Sender: rickg@nwpros.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 10:28:42 -0500 To: isp@freebsd.org From: Rick Gray Subject: Internet Explorer bug? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. It's me again. ;-) I know I have asked some foolish questions before and I know this one does not pretain to FBSD at all. I was hoping maybe another IP has ever run across this problem. I created a customer's home page. On it is a Swedish word with which I had to use Å to denote an accent. Now the customer and a few others when viewing the page see only the first part of the word up to the symbol. The remainder of the word is missing. I use both Netscape and Explorer and I have no problem seeing the whole word. Anyone ever have this problem? If you are interested in seeing the page and using Explorer, the address is http://www.oralimplant.com. The word(s) is Branemark with the accent on the "A". Could this be a bug or has my customer misconfigured something in Explorer? If any one can help me, I would be greatly in their debt. Again I apologize if this is not the correct place for such a question. Thanks for listening! ************************************************ Rick Gray Director of Internet Services Network Pros, Inc. rickg@nwpros.com (713)780-5900 "It is a good day to die." ----Klingon Philosophy ************************************************ From owner-freebsd-isp Mon Sep 16 08:56:36 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA12388 for isp-outgoing; Mon, 16 Sep 1996 08:56:36 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA12367 for ; Mon, 16 Sep 1996 08:56:32 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id RAA09216; Mon, 16 Sep 1996 17:53:06 +0200 Message-Id: <199609161553.RAA09216@login.bigblue.no> From: "Frode Nordahl" To: "David Nugent" Cc: "isp@freebsd.org" Date: Mon, 16 Sep 96 17:02:51 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Denying expired users POP? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996 01:47:16 +1000 (EST), David Nugent wrote: >-----BEGIN PGP SIGNED MESSAGE----- > >On Mon, 16 Sep 1996, Frode Nordahl wrote: > >>>yes, for expired user, we normally change their login shell, when compiling >>>qpopper, make that shell to deny mail. >> >>That is not a option. I want it to use the expire date field in the passwd file. Changing the shell is just extra >>labour. > >Well, I certainly agree it isn't optimal. But writing a script to >change the passwd file (after looking at the expiry date) >wouldn't be particularly difficult. If there is no other option, I guess I have to do that then :-( --------------------------------- Frode Nordahl From owner-freebsd-isp Mon Sep 16 09:13:32 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13520 for isp-outgoing; Mon, 16 Sep 1996 09:13:32 -0700 (PDT) Received: from glacier.cold.org (glacier.sunrem.com [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA13500 for ; Mon, 16 Sep 1996 09:13:26 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id KAA07234; Mon, 16 Sep 1996 10:14:32 -0600 (MDT) Date: Mon, 16 Sep 1996 10:14:31 -0600 (MDT) From: Brandon Gillespie To: Rick Gray cc: isp@freebsd.org Subject: Re: Internet Explorer bug? In-Reply-To: <1.5.4.32.19960916152842.0068ad1c@nwpros.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I created a customer's home page. On it is a Swedish word with which I had > to use Å to denote an accent. Now the customer and a few others when > viewing the page see only the first part of the word up to the symbol. The > remainder of the word is missing. I use both Netscape and Explorer and I > have no problem seeing the whole word. Å is invalid, you need to terminate it with a semi-colon, ala: Å From owner-freebsd-isp Mon Sep 16 10:28:31 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA19737 for isp-outgoing; Mon, 16 Sep 1996 10:28:31 -0700 (PDT) Received: from i-gw.dalsys.com (i-gw.dalsys.com [207.42.153.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA19729 for ; Mon, 16 Sep 1996 10:28:26 -0700 (PDT) Received: (from smap@localhost) by i-gw.dalsys.com (8.6.9/8.6.9) id MAA06765; Mon, 16 Sep 1996 12:28:13 -0500 Received: from future.dsc.dalsys.com(199.170.161.3) by i-gw.dalsys.com via smap (V1.3) id sma006763; Mon Sep 16 12:28:05 1996 Received: from richards.dsc.dalsys.com by future.dsc.dalsys.com (AIX 3.2/UCB 5.64/8.6.12) id AA31559; Mon, 16 Sep 1996 12:32:53 -0500 Message-Id: <323DAB73.3BF2@herald.net> Date: Mon, 16 Sep 1996 12:33:07 -0700 From: Richard Stanford Reply-To: richards@herald.net Organization: Herald Communications X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: Rick Gray Cc: isp@freebsd.org Subject: Re: Internet Explorer bug? References: <1.5.4.32.19960916152842.0068ad1c@nwpros.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rick Gray wrote: > I created a customer's home page. On it is a Swedish word with which I had > to use Å to denote an accent. Now the customer and a few others when > viewing the page see only the first part of the word up to the symbol. The > remainder of the word is missing. I use both Netscape and Explorer and I > have no problem seeing the whole word. Internet Explorer and Netscape Navigator will do their best to "fix" broken HTML. This can lead to certain errors being masked, until the page is viewed by lynx or another more literal browser. The problem here is that any key-sequence beginning with & ( < & © ... ) should end with a semicolon ( ; ). I would suggest testing all pages with lynx as a matter of course (and every other browser you can get your hands on). This "feature" of Netscape and Microsoft browsers can cause some horrendous mistakes to appear correct. For instance, on a couple of occasions I've accidentally written: ... word word emphasized-word word word ... Netscape 2.0+ will interpret the as a for me. Gee, thanks. I can see why they do this, but it means that you should always double-check everything you do (MSIE1.x for WIN16 shows the error as an error, other browsers may too). Caveat Emptor, indeed. -Richard From owner-freebsd-isp Mon Sep 16 10:54:45 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21753 for isp-outgoing; Mon, 16 Sep 1996 10:54:45 -0700 (PDT) Received: from radio.nwpros.com (nwpros.com [205.229.128.214]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA21744 for ; Mon, 16 Sep 1996 10:54:43 -0700 (PDT) Received: from rickbox.nwpros.com (rickbox.nwpros.com [205.229.128.217]) by radio.nwpros.com (8.6.12/8.6.12) with SMTP id MAA17666 for ; Mon, 16 Sep 1996 12:57:47 -0500 Message-Id: <1.5.4.32.19960916180552.006a098c@nwpros.com> X-Sender: rickg@nwpros.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 13:05:52 -0500 To: isp@freebsd.org From: Rick Gray Subject: Re: Internet Explorer bug? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the quick and many responses to my dilemna. I'm not sure if it works yet since for some odd reason I was able to see the entire word with either my Netscape or Explorer. The solutions suggested by everyone has been that the correct protocol should be Å instead of just Å. I will await my customer and see if this fixes his viewing problem. Thanks again for the help. The FBSD community has been great in solving my problems. Keep up the good work everyone! :-) ************************************************ Rick Gray Director of Internet Services Network Pros, Inc. rickg@nwpros.com (713)780-5900 "It is a good day to die." ----Klingon Philosophy ************************************************ From owner-freebsd-isp Mon Sep 16 11:33:03 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25721 for isp-outgoing; Mon, 16 Sep 1996 11:33:03 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA25710 for ; Mon, 16 Sep 1996 11:33:00 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA05985; Mon, 16 Sep 1996 13:30:50 -0500 From: Joe Greco Message-Id: <199609161830.NAA05985@brasil.moneng.mei.com> Subject: Re: Denying expired users POP? To: froden@bigblue.no Date: Mon, 16 Sep 1996 13:30:50 -0500 (CDT) Cc: davidn@blaze.net.au, isp@freebsd.org In-Reply-To: <199609161553.RAA09216@login.bigblue.no> from "Frode Nordahl" at Sep 16, 96 05:02:51 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >-----BEGIN PGP SIGNED MESSAGE----- > > > >On Mon, 16 Sep 1996, Frode Nordahl wrote: > > > >>>yes, for expired user, we normally change their login shell, when compiling > >>>qpopper, make that shell to deny mail. > >> > >>That is not a option. I want it to use the expire date field in the passwd file. Changing the shell is just extra > >>labour. > > > >Well, I certainly agree it isn't optimal. But writing a script to > >change the passwd file (after looking at the expiry date) > >wouldn't be particularly difficult. > > If there is no other option, I guess I have to do that then :-( Would it be smarter to create a patch to do the expiration thing, and then submit it someplace where folks are likely to find it useful? I don't know who maintains qpopper, but if they're not willing to support a vendor specific extension, it would still be nice to have it as a "patch" that got bundled along with the FreeBSD port. ... JG From owner-freebsd-isp Mon Sep 16 11:51:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA27306 for isp-outgoing; Mon, 16 Sep 1996 11:51:25 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA27297 for ; Mon, 16 Sep 1996 11:51:22 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA06046; Mon, 16 Sep 1996 13:48:57 -0500 From: Joe Greco Message-Id: <199609161848.NAA06046@brasil.moneng.mei.com> Subject: Re: INN history file and disk I/O To: petzi@zit.th-darmstadt.de (Michael Beckmann) Date: Mon, 16 Sep 1996 13:48:57 -0500 (CDT) Cc: isp@freebsd.org In-Reply-To: from "Michael Beckmann" at Sep 15, 96 09:38:40 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hello ISPs, > > I have run into a problem with one of my newsservers recently. It is a > P120, 64 MB, Adaptec 2940, 3 SCSI drives running FreeBSD 980801-SNAP. INN > version 1.4unoff4. It receives and sends several full feeds, but is hardly > used by readers. Not enough RAM. > In general, the performance of this system is good; I see about 5 - 10 % > cpu load and almost no swap usage. I get immediate response from the > system, except when I try to telnet to the nntp port. nntp readers simply > time out; it takes forever until the INN prompt appears, if it appears at > all. This situation changes when I throttle the INN. Then I get the INN > prompt immediately. > > Using systat -vm, I have found out that it has 80 - 100 disk seeks per > second on the disk that carries the history file (which is about 90 MB > large). When I move the history file, it is the other disk that gets hit, > so it definitely is the history file that causes this I/O. Could this be > the reason for my problem ? Not enough RAM. You are probably caching _nothing_, not even the history index, with only 64MB. I am upgrading my dedicated feeds box from 128MB to 256MB RAM because there is not enough caching going on. I only have 20MB cached (as reported by top) after several days of running, and INN bloating to its maximum extent. A 90MB history is pretty small. :-) However, the history file per se is less important than the history.pag file. This is what you REALLY want to keep in core because it contains pointers AND hints about the history file, and accesses to history.pag tend to outnumber accesses to the history file. -rw-rw-r-- 1 news news 38315624 Sep 16 13:39 /usr/local/news/history.pag My formula for RAM on a news server: 16MB system RAM 1MB RAM for each feed _channel_, inbound AND outbound 1MB RAM for each simultaneous NNRP session 2 x sizeof(history.pag) And then probably throw some extra in on top of that. So... Ok, let's see how many inbound... Parameters c 14 i 0 (16) l 1000000 o 1011 t 300 normal specified And there is 22 outbound... no readers though. So .. the machine I am looking at needs a MINIMUM 16MB + 1MB * (16 + 22) + 1MB * 0 + 2 * 39MB = 132MB Which is consistent with what I've seen... 128MB is a bit tight and I am pushing it to 256MB. Lesson #1: YOU CAN NEVER HAVE TOO MUCH RAM IN A NEWS SERVER :-) (ok, well, if you have 20GB of disk and 10GB of RAM, I might argue you were approaching having enough RAM). ... JG From owner-freebsd-isp Mon Sep 16 12:08:14 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA28927 for isp-outgoing; Mon, 16 Sep 1996 12:08:14 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA28910 for ; Mon, 16 Sep 1996 12:08:10 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA06118; Mon, 16 Sep 1996 14:06:59 -0500 From: Joe Greco Message-Id: <199609161906.OAA06118@brasil.moneng.mei.com> Subject: Re: Lame Server To: alk@Think.COM (Tony Kimball) Date: Mon, 16 Sep 1996 14:06:59 -0500 (CDT) Cc: isp@freebsd.org In-Reply-To: <199609152148.QAA05113@compound.Think.COM> from "Tony Kimball" at Sep 15, 96 04:48:04 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Quoth Joe Greco on Fri, 13 September: > : (But we all run DOC, etc, right?) > > What is that? Domain Obscenity Checker. I take it we don't all run DOC, etc. ftp to ftp.uu.net, take the obligatory ten minutes to log in, and cd /networking/ip/dns.. Check out doc.2.0, dig.2.0, and some of the other nifty DNS administration tools. Make them part of your DNS ritual and life will be good. ... JG From owner-freebsd-isp Mon Sep 16 12:50:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02764 for isp-outgoing; Mon, 16 Sep 1996 12:50:19 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02758 for ; Mon, 16 Sep 1996 12:50:17 -0700 (PDT) Received: from i-gw.dalsys.com (i-gw.dalsys.com [207.42.153.1]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id MAA20152 for ; Mon, 16 Sep 1996 12:49:55 -0700 (PDT) Received: (from smap@localhost) by i-gw.dalsys.com (8.6.9/8.6.9) id OAA01602 for ; Mon, 16 Sep 1996 14:48:23 -0500 Received: from future.dsc.dalsys.com(199.170.161.3) by i-gw.dalsys.com via smap (V1.3) id sma001599; Mon Sep 16 14:48:14 1996 Received: from richards.dsc.dalsys.com by future.dsc.dalsys.com (AIX 3.2/UCB 5.64/8.6.12) id AA49823; Mon, 16 Sep 1996 14:26:45 -0500 Message-Id: <323DC627.756B@herald.net> Date: Mon, 16 Sep 1996 14:27:03 -0700 From: Richard Stanford Reply-To: richards@herald.net Organization: Herald Communications X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: isp@freebsd.org Subject: INN drive configuration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm currently setting up a dedicated news machine running 2.1.5-R, and have a quick question to some of the other people here: For every 4GB of data storage on the box, would you recommend 1 4GB 7200 RPM drive (Barracuda) or 2 2GB 5400 RPM drives (Hawk)? I realize that I should spread the data between as many disks as possible, and also make sure that those disks are as fast as possible, and would like to hear opinions as to which factor is more important. This machine will have 1 (maybe 2) full-ish incoming feeds, and feed several shell accounts on one machine along with dialup users. If it makes a difference. I'm also on a bit of a budget setting it up, which is why I've identified my $/GB limit and am now looking at the choices within that constraint. Power, cooling, etc are not going to be issues. TIA! -Richard From owner-freebsd-isp Mon Sep 16 12:56:03 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03128 for isp-outgoing; Mon, 16 Sep 1996 12:56:03 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA03103 for ; Mon, 16 Sep 1996 12:56:00 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA06188; Mon, 16 Sep 1996 14:54:29 -0500 From: Joe Greco Message-Id: <199609161954.OAA06188@brasil.moneng.mei.com> Subject: Re: SYN attacks in the Washington Post To: steve@edmweb.com (Steve Reid) Date: Mon, 16 Sep 1996 14:54:29 -0500 (CDT) Cc: didier@omnix.fr.org, iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com In-Reply-To: from "Steve Reid" at Sep 13, 96 02:30:15 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 3- Set your router so that it will _not_ allow packets to be sent from > your network with an address that doesn't match your network. For > instance, if your network is 198.41.0.*, don't allow your router to > send out packets unless the source address matches 198.41.0.*. This > doesn't offer any protection to you, but it will prevent your network from > being used to launch a SYN bombing attack. If someone does attempt it, > they will be limited to forging adresses in your subnet (such as > 198.41.0.253) which the victim can easily block, and you can easily > trace. You could even go so far as to only allow addresses from valid > hosts on your network, which will make SYN bombing from your network > impossible. No, not "impossible". In my opinion, all ISP's should do everything they can to reject bogus addresses from originating at their site. Anything less is incompetence. My standard filtering firewall does numerous things, including: Block all traffic with RFC1918 addresses as source or destination. These never have a valid reason for passing through a border router. Block all inbound traffic with source addresses that are in my CIDR blocks. Block all inbound traffic with destination addresses not in my CIDR blocks. This is explicitly reinforcing the RFC1918 rule :-) but that is OK. Block all outbound traffic except traffic with a source address in my CIDR blocks. Block all outbound traffic except traffic with a destination address NOT in my CIDR blocks (generally: routing errors). You can never be too paranoid. ... JG From owner-freebsd-isp Mon Sep 16 13:25:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05304 for isp-outgoing; Mon, 16 Sep 1996 13:25:19 -0700 (PDT) Received: from alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA05292 for ; Mon, 16 Sep 1996 13:25:17 -0700 (PDT) Received: from hmmm.alaska.net by alaska.net (5.x/SMI-SVR4) id AA26778; Mon, 16 Sep 1996 12:25:00 -0800 Message-Id: <323DAA61.2FC0@alaska.net> Date: Mon, 16 Sep 1996 12:28:33 -0700 From: hmmm X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: richards@herald.net Cc: Rick Gray , isp@FreeBSD.org Subject: Re: Internet Explorer bug? References: <1.5.4.32.19960916152842.0068ad1c@nwpros.com> <323DAB73.3BF2@herald.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Richard Stanford wrote: > > Rick Gray wrote: > > Internet Explorer and Netscape Navigator will do their best to "fix" > broken HTML. This can lead to certain errors being masked, until the > page is viewed by lynx or another more literal browser. The problem > here is that any key-sequence beginning with & ( < & © ... ) > should end with a semicolon ( ; ). not according to my specs. a lack of a semicolon means a space. From owner-freebsd-isp Mon Sep 16 15:54:00 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17702 for isp-outgoing; Mon, 16 Sep 1996 15:54:00 -0700 (PDT) Received: from adsight.com (adsight.com [207.86.2.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA17690 for ; Mon, 16 Sep 1996 15:53:55 -0700 (PDT) Received: (from webadmin@localhost) by adsight.com (8.7.5/8.6.12) id SAA13184; Mon, 16 Sep 1996 18:49:18 -0400 (EDT) Date: Mon, 16 Sep 1996 18:49:18 -0400 (EDT) From: Sam Magee To: freebsd-isp@FreeBSD.org Subject: Mail aliases Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is anyone using virtual homing with the same e-mail address available to each -- such as info, sales, etc. If I want info@company1.com and info@company2.com, is there a way to set this up in sendmail's aliases. Thanks Sam (smagee@adsight.com) From owner-freebsd-isp Mon Sep 16 17:37:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24219 for isp-outgoing; Mon, 16 Sep 1996 17:37:08 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA24213 for ; Mon, 16 Sep 1996 17:37:06 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id TAA21372; Mon, 16 Sep 1996 19:38:09 -0500 (CDT) Date: Mon, 16 Sep 1996 19:38:09 -0500 (CDT) From: "Matthew N. Dodd" To: Sam Magee cc: freebsd-isp@FreeBSD.org Subject: Re: Mail aliases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Sam Magee wrote: > Is anyone using virtual homing with the same e-mail address available > to each -- such as info, sales, etc. > > If I want info@company1.com and info@company2.com, is there a way to > set this up in sendmail's aliases. http://www.jurai.net/~winter/virtual/email.html | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-isp Mon Sep 16 17:47:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24593 for isp-outgoing; Mon, 16 Sep 1996 17:47:13 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA24586 for ; Mon, 16 Sep 1996 17:47:09 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id TAA06779; Mon, 16 Sep 1996 19:46:05 -0500 From: Joe Greco Message-Id: <199609170046.TAA06779@brasil.moneng.mei.com> Subject: Re: INN drive configuration To: richards@herald.net Date: Mon, 16 Sep 1996 19:46:05 -0500 (CDT) Cc: isp@freebsd.org In-Reply-To: <323DC627.756B@herald.net> from "Richard Stanford" at Sep 16, 96 02:27:03 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm currently setting up a dedicated news machine running 2.1.5-R, and > have a quick question to some of the other people here: > > For every 4GB of data storage on the box, would you recommend 1 4GB 7200 > RPM drive (Barracuda) or 2 2GB 5400 RPM drives (Hawk)? I realize that I > should spread the data between as many disks as possible, and also make > sure that those disks are as fast as possible, and would like to hear > opinions as to which factor is more important. 2 2GB drives will be faster than 1 4GB drive... as long as the average head seek time is reasonably similar. The Barra's are 8ms drives and the Hawks are 9ms drives... I usually consider that the two Hawks will not be equivalent to a 4.5ms drive (9ms / 2 drives) but more like 6ms average. Ideally you could even shy away from the 2GB drives and go for the 31055N's (1GB Hawk Ultra) ... they are faster at some operations than the Barra's. You might want to go look through the mailing list archives, I have gone on and on about this sort of stuff in the past... > This machine will have 1 (maybe 2) full-ish incoming feeds, and feed > several shell accounts on one machine along with dialup users. If it > makes a difference. I'm also on a bit of a budget setting it up, which > is why I've identified my $/GB limit and am now looking at the choices > within that constraint. Power, cooling, etc are not going to be issues. > > TIA! > > -Richard > From owner-freebsd-isp Mon Sep 16 19:18:14 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA28992 for isp-outgoing; Mon, 16 Sep 1996 19:18:14 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA28980 for ; Mon, 16 Sep 1996 19:18:07 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id TAA03291; Mon, 16 Sep 1996 19:15:28 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609170215.TAA03291@GndRsh.aac.dev.com> Subject: Re: INN drive configuration In-Reply-To: <199609170046.TAA06779@brasil.moneng.mei.com> from Joe Greco at "Sep 16, 96 07:46:05 pm" To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Mon, 16 Sep 1996 19:15:28 -0700 (PDT) Cc: richards@herald.net, isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ... > > You might want to go look through the mailing list archives, I have gone > on and on about this sort of stuff in the past... Any up and coming ISP types out there should take this suggestion very seriously. Joe has posted more useful information on many aspects of how to make a ``Real NewsEngine'' and for that matter just on how to be a very good ISP. This is _free_ advice that you should be paying contractor fees to get, and even at that it would be more than worth it. My hats off to Joe Greco and his infinite depth of wisdom he has so genoursly shared with us all. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Mon Sep 16 19:49:55 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01204 for isp-outgoing; Mon, 16 Sep 1996 19:49:55 -0700 (PDT) Received: from gateway.net.hk (bmf@router.gateway.net.hk [202.76.7.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01195 for ; Mon, 16 Sep 1996 19:49:48 -0700 (PDT) Received: (from bmf@localhost) by gateway.net.hk (8.7.4/8.7.3) id KAA25230; Tue, 17 Sep 1996 10:44:32 +0800 (HKT) Date: Tue, 17 Sep 1996 10:44:32 +0800 (HKT) From: Bo Fussing To: isp@freebsd.org Subject: EmpLink using BSD UNIX? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We just received some marketing material from EMPaC who sell the EmpView Internet/Intranet Server Operating System. I was very interested to find out that the Operating System is described as 4.4 BSD Unix based! Has anybody got any idea if this is just rehashed Free/Net/OpenBSD or BSD/OS. Have a look at http://www.empac.com TIA Bo Fussing Gateway Internet - Hong Kong Tel : +852 2963 7354 MIME & PGP Mailing OK Fax : +852 2963 7353 From owner-freebsd-isp Mon Sep 16 21:12:56 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06022 for isp-outgoing; Mon, 16 Sep 1996 21:12:56 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA06017 for ; Mon, 16 Sep 1996 21:12:52 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id UAA10844; Mon, 16 Sep 1996 20:26:26 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id VAA13546; Mon, 16 Sep 1996 21:07:02 -0700 Date: Mon, 16 Sep 1996 21:07:01 -0700 (PDT) From: Michael Dillon To: inet-access@earth.com cc: iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Filter outgoing spoofed SYN's on BAY routers Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following fragment is from the NANOG list archived at http://www.merit.edu I changed the IP address to 10.14.22.0 You should use your own real IP address Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com ---------- Fragment of message ---------- Filters for Bay routers are not very difficult, owing to the graphical configuration tools. On one of my ethernet segments, all source addresses should be in the 10.14.22.0 range. Here is how I built a filter for this interface: In Site Manager, select the circuit that the filter will be applied to. Filters are built for traffic coming IN to the interface, so in this case I applied the filter to my ethernet interface. Once the interface is selected, select "Edit Circuit", then pull down Protocols->Edit IP->Traffic Filters. If this is the first filter of this type that you're creating, you'll need to create a filter template first. This template gets stored on your hard drive, so you can jump over to another router and apply the same filter template, just changing the appropriate addresses. Once you create a new template, you'll want to choose the following: Condition->IP Source Address 0.0.0.0 - 10.14.22.0 10.14.22.255 - 255.255.255.255 Action->Drop Action->Detailed Log (this is optional.. I use it) That's all there is to it. Once you create this template, then go back to the "IP Filters" screen and actually create the filter. When prompted for a template, use the one you just created. This method tells the router to allow that which you do not specifically deny. You can also create two filters, one saying "drop everything" and the other one telling it specifically what you want to allow. Personally, I prefer the first method because it seems more efficient.. Perhaps someone from Bay will comment on the optimal way to do this. From owner-freebsd-isp Mon Sep 16 21:16:36 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06230 for isp-outgoing; Mon, 16 Sep 1996 21:16:36 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA06225 for ; Mon, 16 Sep 1996 21:16:32 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id UAA10885; Mon, 16 Sep 1996 20:29:31 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id VAA13581; Mon, 16 Sep 1996 21:10:06 -0700 Date: Mon, 16 Sep 1996 21:10:06 -0700 (PDT) From: Michael Dillon To: inet-access@earth.com cc: iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Filtering spoofed SYN packets on Livingston's Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a fragment from the NANOG list archived at http://www.merit.edu It will work on Livingston IRX routers as well as PM2e and PM2eR terminal servers. Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com ----------- Fragment of message --------------- create a filter "internet.out" Contents: three lines for each net block you have: permit 1.2.3.4/20 tcp permit 1.2.3.4/20 udp permit 1.2.3.4/20 icmp final line to log (optional) MUST COME AFTER permit list for netblocks: deny log The final line will have the router syslog a message any time someone tries to send from an address outside your blocks, as defined in the rest of the filter. This is optional. Keep in mind that the panix attack would probably have flooded your syslog machine's disk space with syslog info in this case. Hardening that is an issue for another day, however. Apply this to all outbound ports on your gateway IRX routers. You can do similar things with inbound ports on customer connections or other internal routers if you desire to start filtering earlier than your border gateway machines. For example, if 1.2.3.0/21 is your block for your St Louis hub and 2.3.11.0/24 and 2.3.22.0/26 are customer nets there, then the outbound interface for your St Louis IRX could have the following filter on its outbound interface(s): permit 1.2.3.0/21 tcp permit 1.2.3.0/21 udp permit 1.2.3.0/21 icmp permit 2.3.11.0/24 tcp permit 2.3.11.0/24 udp permit 2.3.11.0/24 icmp permit 2.3.22.0/26 tcp permit 2.3.22.0/26 udp permit 2.3.22.0/26 icmp deny log Alternatively you can filter on incoming ports with the same syntax. From owner-freebsd-isp Mon Sep 16 21:39:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07398 for isp-outgoing; Mon, 16 Sep 1996 21:39:18 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA07393 for ; Mon, 16 Sep 1996 21:39:14 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id OAA01639; Tue, 17 Sep 1996 14:38:44 +1000 (EST) Date: Tue, 17 Sep 1996 14:38:42 +1000 (EST) From: "Daniel O'Callaghan" To: Frode Nordahl cc: David Nugent , "isp@freebsd.org" Subject: Re: Denying expired users POP? In-Reply-To: <199609161553.RAA09216@login.bigblue.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Frode Nordahl wrote: > On Tue, 17 Sep 1996 01:47:16 +1000 (EST), David Nugent wrote: > >Well, I certainly agree it isn't optimal. But writing a script to > >change the passwd file (after looking at the expiry date) > >wouldn't be particularly difficult. > > If there is no other option, I guess I have to do that then :-( What about modifying popper to look at the expiry time? Danny From owner-freebsd-isp Mon Sep 16 22:06:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08604 for isp-outgoing; Mon, 16 Sep 1996 22:06:04 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08599 for ; Mon, 16 Sep 1996 22:05:58 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id WAA09429; Mon, 16 Sep 1996 22:06:05 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA21901; Mon, 16 Sep 1996 22:05:48 -0700 (PDT) Message-Id: <199609170505.WAA21901@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: petzi@zit.th-darmstadt.de (Michael Beckmann), isp@freebsd.org Subject: Re: INN history file and disk I/O In-reply-to: Your message of Mon, 16 Sep 96 13:48:57 -0500. <199609161848.NAA06046@brasil.moneng.mei.com> Date: Mon, 16 Sep 1996 22:05:47 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Lesson #1: YOU CAN NEVER HAVE TOO MUCH RAM IN A NEWS SERVER :-) >(ok, well, if you have 20GB of disk and 10GB of RAM, I might argue you >were approaching having enough RAM). Or, approaching bankruptcy... ;-) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Mon Sep 16 22:56:30 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA10957 for isp-outgoing; Mon, 16 Sep 1996 22:56:30 -0700 (PDT) Received: from nanguo.chalmers.com.au (chalmers.com.au [203.1.96.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA10952 for ; Mon, 16 Sep 1996 22:56:26 -0700 (PDT) Received: by nanguo.chalmers.com.au (Smail3.1.28.1 #8) id m0v2tJx-0003A8C; Tue, 17 Sep 96 16:07 EST Message-Id: From: robert@chalmers.com.au (Robert Chalmers) Subject: how do I set SCSI ID to 0? To: freebsd-isp@freebsd.org Date: Tue, 17 Sep 1996 16:07:44 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hi folks, > does anyone know how to set the SCSI ID on a SEAGATE ST-41601N > to id#0 ? > > It "defaults" to id#3, and I can't see any way of changing it. The > jumpers on the back don't give any indication, and the SEAGATE docs, > indicat an id of 1,2,4 ?? don't even mention 3. > > Does anyone have any clues on how to set it to 0? > > thanks > Robert -- The China House Sheng Huo Jiu Shi Dou Zheng robert@chalmers.com.au for Whirled Peas http://chalmers.com.au Location: Web Works Whitsunday. 21'7" S, 149'14" E. From owner-freebsd-isp Mon Sep 16 22:59:59 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA11059 for isp-outgoing; Mon, 16 Sep 1996 22:59:59 -0700 (PDT) Received: from shadow.apana.org.au (shadow.apana.org.au [202.12.88.82]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA11043 for ; Mon, 16 Sep 1996 22:59:46 -0700 (PDT) Received: (from bradf@localhost) by shadow.apana.org.au (8.6.12/8.6.9) id QAA13835; Tue, 17 Sep 1996 16:06:38 +1000 Date: Tue, 17 Sep 1996 16:06:35 +1000 (EST) From: bradf To: isp@freebsd.org Subject: ppp connection problems. Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="214585944-1145013221-842940395=:13820" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --214585944-1145013221-842940395=:13820 Content-Type: TEXT/PLAIN; charset=US-ASCII Greetings, i've got a small problem in connecting to my isp via ppp. please help me. this is how i (attemnpt) to start a ppp session: pppd /dev/cua2 38400 defaultroute noipdefault --214585944-1145013221-842940395=:13820 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=debug Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: QXVnIDE4IDE1OjMyOjU0IGJsYWggcHBwZFs2OF06IHNldF94YWNjbTogMDAw MDAwMDAgMDAwMDAwMDAgMDAwMDAwMDAgNjAwMDAwMDAgDQpBdWcgMTggMTU6 MzI6NTQgYmxhaCBwcHBkWzY4XTogc2VuZF9jb25maWc6IG10dSA9IDE1MDAg DQpBdWcgMTggMTU6MzI6NTQgYmxhaCBwcHBkWzY4XTogc2VuZF9jb25maWc6 IGFzeW5jbWFwID0gZmZmZmZmZmYgDQpBdWcgMTggMTU6MzI6NTQgYmxhaCBw cHBkWzY4XTogc2VuZF9jb25maWc6IGZsYWdzID0gMCANCkF1ZyAxOCAxNToz Mjo1NCBibGFoIHBwcGRbNjhdOiByZWN2X2NvbmZpZzogbXJ1ID0gMTUwMCAN CkF1ZyAxOCAxNTozMjo1NCBibGFoIHBwcGRbNjhdOiByZWN2X2NvbmZpZzog YXN5bmNtYXAgPSAwIA0KQXVnIDE4IDE1OjMyOjU0IGJsYWggcHBwZFs2OF06 IHJlY3ZfY29uZmlnOiBmbGFncyA9IDEwIA0KQXVnIDE4IDE1OjMyOjU0IGJs YWggcHBwZFs2OF06IHNlbnQgW0xDUCBDb25mUmVxIGlkPTB4MSA8bXJ1IDE1 MDA+IDxtYWdpYyAweDMyMTFjMDQyPiA8cGNvbXA+IDxhY2NvbXA+XQ0KQXVn IDE4IDE1OjMyOjU0IGJsYWggcHBwZFs2OF06IFRpbWVvdXQgODAwMzNmMDo4 MDEzNDhjIGluIDMgc2Vjb25kcy4NCkF1ZyAxOCAxNTozMjo1NCBibGFoIHBw cGRbNjhdOiBTZXR0aW5nIGl0aW1lciBmb3IgMyBzZWNvbmRzIGluIHRpbWVv dXQuDQpBdWcgMTggMTU6MzI6NTcgYmxhaCBwcHBkWzY4XTogQWxhcm0NCkF1 ZyAxOCAxNTozMjo1NyBibGFoIHBwcGRbNjhdOiBzZW50IFtMQ1AgQ29uZlJl cSBpZD0weDEgPG1ydSAxNTAwPiA8bWFnaWMgMHgzMjExYzA0Mj4gPHBjb21w PiA8YWNjb21wPl0NCkF1ZyAxOCAxNTozMjo1NyBibGFoIHBwcGRbNjhdOiBU aW1lb3V0IDgwMDMzZjA6ODAxMzQ4YyBpbiAzIHNlY29uZHMuDQpBdWcgMTgg MTU6MzI6NTcgYmxhaCBwcHBkWzY4XTogU2V0dGluZyBpdGltZXIgZm9yIDMg c2Vjb25kcyBpbiB0aW1lb3V0Lg0KQXVnIDE4IDE1OjMzOjAwIGJsYWggcHBw ZFs2OF06IEFsYXJtDQpBdWcgMTggMTU6MzM6MDAgYmxhaCBwcHBkWzY4XTog c2VudCBbTENQIENvbmZSZXEgaWQ9MHgxIDxtcnUgMTUwMD4gPG1hZ2ljIDB4 MzIxMWMwNDI+IDxwY29tcD4gPGFjY29tcD5dDQpBdWcgMTggMTU6MzM6MDAg YmxhaCBwcHBkWzY4XTogVGltZW91dCA4MDAzM2YwOjgwMTM0OGMgaW4gMyBz ZWNvbmRzLg0KQXVnIDE4IDE1OjMzOjAwIGJsYWggcHBwZFs2OF06IFNldHRp bmcgaXRpbWVyIGZvciAzIHNlY29uZHMgaW4gdGltZW91dC4NCkF1ZyAxOCAx NTozMzowMyBibGFoIHBwcGRbNjhdOiBBbGFybQ0KQXVnIDE4IDE1OjMzOjAz IGJsYWggcHBwZFs2OF06IHNlbnQgW0xDUCBDb25mUmVxIGlkPTB4MSA8bXJ1 IDE1MDA+IDxtYWdpYyAweDMyMTFjMDQyPiA8cGNvbXA+IDxhY2NvbXA+XQ0K QXVnIDE4IDE1OjMzOjAzIGJsYWggcHBwZFs2OF06IFRpbWVvdXQgODAwMzNm MDo4MDEzNDhjIGluIDMgc2Vjb25kcy4NCkF1ZyAxOCAxNTozMzowMyBibGFo IHBwcGRbNjhdOiBTZXR0aW5nIGl0aW1lciBmb3IgMyBzZWNvbmRzIGluIHRp bWVvdXQuDQpBdWcgMTggMTU6MzM6MDYgYmxhaCBwcHBkWzY4XTogQWxhcm0N CkF1ZyAxOCAxNTozMzowNiBibGFoIHBwcGRbNjhdOiBzZW50IFtMQ1AgQ29u ZlJlcSBpZD0weDEgPG1ydSAxNTAwPiA8bWFnaWMgMHgzMjExYzA0Mj4gPHBj b21wPiA8YWNjb21wPl0NCkF1ZyAxOCAxNTozMzowNiBibGFoIHBwcGRbNjhd OiBUaW1lb3V0IDgwMDMzZjA6ODAxMzQ4YyBpbiAzIHNlY29uZHMuDQpBdWcg MTggMTU6MzM6MDYgYmxhaCBwcHBkWzY4XTogU2V0dGluZyBpdGltZXIgZm9y IDMgc2Vjb25kcyBpbiB0aW1lb3V0Lg0KQXVnIDE4IDE1OjMzOjA5IGJsYWgg cHBwZFs2OF06IEFsYXJtDQpBdWcgMTggMTU6MzM6MDkgYmxhaCBwcHBkWzY4 XTogc2VudCBbTENQIENvbmZSZXEgaWQ9MHgxIDxtcnUgMTUwMD4gPG1hZ2lj IDB4MzIxMWMwNDI+IDxwY29tcD4gPGFjY29tcD5dDQpBdWcgMTggMTU6MzM6 MDkgYmxhaCBwcHBkWzY4XTogVGltZW91dCA4MDAzM2YwOjgwMTM0OGMgaW4g MyBzZWNvbmRzLg0KQXVnIDE4IDE1OjMzOjA5IGJsYWggcHBwZFs2OF06IFNl dHRpbmcgaXRpbWVyIGZvciAzIHNlY29uZHMgaW4gdGltZW91dC4NCkF1ZyAx OCAxNTozMzoxMiBibGFoIHBwcGRbNjhdOiBBbGFybQ0KQXVnIDE4IDE1OjMz OjEyIGJsYWggcHBwZFs2OF06IHNlbnQgW0xDUCBDb25mUmVxIGlkPTB4MSA8 bXJ1IDE1MDA+IDxtYWdpYyAweDMyMTFjMDQyPiA8cGNvbXA+IDxhY2NvbXA+ XQ0KQXVnIDE4IDE1OjMzOjEyIGJsYWggcHBwZFs2OF06IFRpbWVvdXQgODAw MzNmMDo4MDEzNDhjIGluIDMgc2Vjb25kcy4NCkF1ZyAxOCAxNTozMzoxMiBi bGFoIHBwcGRbNjhdOiBTZXR0aW5nIGl0aW1lciBmb3IgMyBzZWNvbmRzIGlu IHRpbWVvdXQuDQpBdWcgMTggMTU6MzM6MTUgYmxhaCBwcHBkWzY4XTogQWxh cm0NCkF1ZyAxOCAxNTozMzoxNSBibGFoIHBwcGRbNjhdOiBzZW50IFtMQ1Ag Q29uZlJlcSBpZD0weDEgPG1ydSAxNTAwPiA8bWFnaWMgMHgzMjExYzA0Mj4g PHBjb21wPiA8YWNjb21wPl0NCkF1ZyAxOCAxNTozMzoxNSBibGFoIHBwcGRb NjhdOiBUaW1lb3V0IDgwMDMzZjA6ODAxMzQ4YyBpbiAzIHNlY29uZHMuDQpB dWcgMTggMTU6MzM6MTUgYmxhaCBwcHBkWzY4XTogU2V0dGluZyBpdGltZXIg Zm9yIDMgc2Vjb25kcyBpbiB0aW1lb3V0Lg0KQXVnIDE4IDE1OjMzOjE4IGJs YWggcHBwZFs2OF06IEFsYXJtDQpBdWcgMTggMTU6MzM6MTggYmxhaCBwcHBk WzY4XTogc2VudCBbTENQIENvbmZSZXEgaWQ9MHgxIDxtcnUgMTUwMD4gPG1h Z2ljIDB4MzIxMWMwNDI+IDxwY29tcD4gPGFjY29tcD5dDQpBdWcgMTggMTU6 MzM6MTggYmxhaCBwcHBkWzY4XTogVGltZW91dCA4MDAzM2YwOjgwMTM0OGMg aW4gMyBzZWNvbmRzLg0KQXVnIDE4IDE1OjMzOjE4IGJsYWggcHBwZFs2OF06 IFNldHRpbmcgaXRpbWVyIGZvciAzIHNlY29uZHMgaW4gdGltZW91dC4NCkF1 ZyAxOCAxNTozMzoyMSBibGFoIHBwcGRbNjhdOiBBbGFybQ0KQXVnIDE4IDE1 OjMzOjIxIGJsYWggcHBwZFs2OF06IHNlbnQgW0xDUCBDb25mUmVxIGlkPTB4 MSA8bXJ1IDE1MDA+IDxtYWdpYyAweDMyMTFjMDQyPiA8cGNvbXA+IDxhY2Nv bXA+XQ0KQXVnIDE4IDE1OjMzOjIxIGJsYWggcHBwZFs2OF06IFRpbWVvdXQg ODAwMzNmMDo4MDEzNDhjIGluIDMgc2Vjb25kcy4NCkF1ZyAxOCAxNTozMzoy MSBibGFoIHBwcGRbNjhdOiBTZXR0aW5nIGl0aW1lciBmb3IgMyBzZWNvbmRz IGluIHRpbWVvdXQuDQpBdWcgMTggMTU6MzM6MjUgYmxhaCBwcHBkWzY4XTog QWxhcm0NCg== --214585944-1145013221-842940395=:13820-- From owner-freebsd-isp Mon Sep 16 23:33:22 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA13606 for isp-outgoing; Mon, 16 Sep 1996 23:33:22 -0700 (PDT) Received: from nanguo.chalmers.com.au (chalmers.com.au [203.1.96.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA13601 for ; Mon, 16 Sep 1996 23:33:18 -0700 (PDT) Received: by nanguo.chalmers.com.au (Smail3.1.28.1 #8) id m0v2tth-00024wC; Tue, 17 Sep 96 16:44 EST Message-Id: From: robert@chalmers.com.au (Robert Chalmers) Subject: Seeing the SCSI, and ID# cont... To: freebsd-isp@freebsd.org Date: Tue, 17 Sep 1996 16:44:41 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I found the correct jumpers. No jumper configs ID#0, hwever now the install cant see the sd0 device anyway. Its on a Adaptec AHA-1540C. Its a Seagate 1.3Gb SCSI drive. The cable has a terminator at the end, so should I disable the terminators on the SCSI Drive? thanks, Robert -- The China House Sheng Huo Jiu Shi Dou Zheng robert@chalmers.com.au for Whirled Peas http://chalmers.com.au Location: Web Works Whitsunday. 21'7" S, 149'14" E. From owner-freebsd-isp Mon Sep 16 23:35:01 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA13779 for isp-outgoing; Mon, 16 Sep 1996 23:35:01 -0700 (PDT) Received: from escape.cs.ibank.ru (igor@escape.cs.ibank.ru [194.58.131.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA13757 for ; Mon, 16 Sep 1996 23:34:54 -0700 (PDT) Received: (from igor@localhost) by escape.cs.ibank.ru (8.7.5/8.7.3/Zynaps) id KAA04900 for isp@freebsd.org; Tue, 17 Sep 1996 10:34:42 +0400 (MSD) From: Igor Vinokurov Message-Id: <199609170634.KAA04900@escape.cs.ibank.ru> Subject: POP3/SMTP mail client for DOS To: isp@freebsd.org Date: Tue, 17 Sep 1996 10:34:42 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk re, Anyone can recommend POP3/SMTP client for DOS? Shareware/freeware prefered. From owner-freebsd-isp Mon Sep 16 23:36:54 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA13926 for isp-outgoing; Mon, 16 Sep 1996 23:36:54 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA13915 for ; Mon, 16 Sep 1996 23:36:47 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id XAA03827; Mon, 16 Sep 1996 23:36:31 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609170636.XAA03827@GndRsh.aac.dev.com> Subject: Re: how do I set SCSI ID to 0? In-Reply-To: from Robert Chalmers at "Sep 17, 96 04:07:44 pm" To: robert@chalmers.com.au (Robert Chalmers) Date: Mon, 16 Sep 1996 23:36:31 -0700 (PDT) Cc: freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > Hi folks, > > does anyone know how to set the SCSI ID on a SEAGATE ST-41601N > > to id#0 ? > > > > It "defaults" to id#3, and I can't see any way of changing it. The > > jumpers on the back don't give any indication, and the SEAGATE docs, > > indicat an id of 1,2,4 ?? don't even mention 3. The jumpers are binary, to get ID 3 set jumper 1 and 2, to get ID 5 set jumper 1 and 4. > > > > Does anyone have any clues on how to set it to 0? Remove all jumpers. > > > > thanks > > Robert > -- > The China House Sheng Huo Jiu Shi Dou Zheng > robert@chalmers.com.au for Whirled Peas http://chalmers.com.au > Location: Web Works Whitsunday. 21'7" S, 149'14" E. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Mon Sep 16 23:50:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14702 for isp-outgoing; Mon, 16 Sep 1996 23:50:25 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA14691 for ; Mon, 16 Sep 1996 23:50:20 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id QAA01868; Tue, 17 Sep 1996 16:50:08 +1000 (EST) Date: Tue, 17 Sep 1996 16:50:07 +1000 (EST) From: "Daniel O'Callaghan" To: Robert Chalmers cc: freebsd-isp@freebsd.org Subject: Re: how do I set SCSI ID to 0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Robert Chalmers wrote: > > > > Hi folks, > > does anyone know how to set the SCSI ID on a SEAGATE ST-41601N > > to id#0 ? > > > > It "defaults" to id#3, and I can't see any way of changing it. The > > jumpers on the back don't give any indication, and the SEAGATE docs, > > indicat an id of 1,2,4 ?? don't even mention 3. Usually the jumpers are labelled A0, A1, A2, which represent 1, 2 and 4 in binary. To set ID to 3, jumper A0 and A1 (1+2=3). To use 6, jumper A1 and A2. Danny From owner-freebsd-isp Mon Sep 16 23:51:12 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14773 for isp-outgoing; Mon, 16 Sep 1996 23:51:12 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA14766 for ; Mon, 16 Sep 1996 23:51:10 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA11476; Mon, 16 Sep 1996 23:51:14 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id XAA22440; Mon, 16 Sep 1996 23:50:56 -0700 (PDT) Message-Id: <199609170650.XAA22440@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: robert@chalmers.com.au (Robert Chalmers) cc: freebsd-isp@freebsd.org Subject: Re: how do I set SCSI ID to 0? In-reply-to: Your message of Tue, 17 Sep 96 16:07:44 +1000. Date: Mon, 16 Sep 1996 23:50:56 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> does anyone know how to set the SCSI ID on a SEAGATE ST-41601N >> to id#0 ? >> It "defaults" to id#3, and I can't see any way of changing it. The >> jumpers on the back don't give any indication, and the SEAGATE docs, >> indicat an id of 1,2,4 ?? don't even mention 3. >> Does anyone have any clues on how to set it to 0? Forgive me if this is obvious, and you've already tried it. Have you tried finding these settings on their web site? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Tue Sep 17 00:06:15 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA15908 for isp-outgoing; Tue, 17 Sep 1996 00:06:15 -0700 (PDT) Received: from nanguo.chalmers.com.au (chalmers.com.au [203.1.96.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA15900 for ; Tue, 17 Sep 1996 00:06:10 -0700 (PDT) Received: by nanguo.chalmers.com.au (Smail3.1.28.1 #8) id m0v2uPY-000283C; Tue, 17 Sep 96 17:17 EST Message-Id: From: robert@chalmers.com.au (Robert Chalmers) Subject: how do I set SCSI. update. To: freebsd-isp@freebsd.org Date: Tue, 17 Sep 1996 17:17:35 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the help everyone. I continue on the trail of this beastie. The HDD is second hand, and here's what I have tried so far, wit hmixed success. The Controller is fine. everything checks out. The HDD is fine, it is verifying now. The jumper pins had been soldered together into id#3 config. I split the solder joints, so the pins are now free, and have ID#0. Silly me. I should know that. So, now I discover that there are no terminators on the SCSI board. The cable that came with the controller has multiple drops, and a correct terminator on the end. The HDD docs indicate a number of options related to terminator configuration, so I opted to take the 2+4 and 1+3 jumpered option, "Drive supplies power for external terminator at end of the daisy-chain. Resistor paks must be removed" It seems to fit the bill. The drive is responding to the SCSISelect software accessed with the Ctl-A option, and is now Verifying the surface of the drive. So I live in hope. If it does that, surely the Install for FreeBSD will find it???? thanks for the help Bob -- The China House Sheng Huo Jiu Shi Dou Zheng robert@chalmers.com.au for Whirled Peas http://chalmers.com.au Location: Web Works Whitsunday. 21'7" S, 149'14" E. From owner-freebsd-isp Tue Sep 17 00:21:51 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA16902 for isp-outgoing; Tue, 17 Sep 1996 00:21:51 -0700 (PDT) Received: from nanguo.chalmers.com.au (chalmers.com.au [203.1.96.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA16895 for ; Tue, 17 Sep 1996 00:21:47 -0700 (PDT) Received: by nanguo.chalmers.com.au (Smail3.1.28.1 #8) id m0v2uef-00027mC; Tue, 17 Sep 96 17:33 EST Message-Id: From: robert@chalmers.com.au (Robert Chalmers) Subject: SCSI configuration still To: freebsd-isp@freebsd.org Date: Tue, 17 Sep 1996 17:33:13 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, continuing the saga. The drive verified ok. formatted ok, so the controller can see it and deal with it. but the FreeBSD boot disk gives me a sd0(aha0:0:0): timed out sd0(aha0:0:0): timed out AGAIN 4 times in all, then goes on with a probe of other stuff, then into the menu. But it doesn't find the SCSI drive? any clues gurus? cheers, Bob -- The China House Sheng Huo Jiu Shi Dou Zheng robert@chalmers.com.au for Whirled Peas http://chalmers.com.au Location: Web Works Whitsunday. 21'7" S, 149'14" E. From owner-freebsd-isp Tue Sep 17 01:19:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA20010 for isp-outgoing; Tue, 17 Sep 1996 01:19:16 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA20004 for ; Tue, 17 Sep 1996 01:19:07 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.5/8.7.3) id RAA22268; Tue, 17 Sep 1996 17:47:52 +0930 (CST) Date: Tue, 17 Sep 1996 17:47:52 +0930 (CST) From: Peter Childs Message-Id: <199609170817.RAA22268@al.imforei.apana.org.au> To: bradf@shadow.apana.org.au, freebsd-isp@freebsd.org Subject: Re: ppp connection problems. X-Newsreader: TIN [version 1.2 PL2] Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <51li8k$ktg@al.imforei.apana.org.au> you wrote: : This message is in MIME format. The first part should be readable text, : while the remaining parts are likely unreadable without MIME-aware tools. : Send mail to mime@docserver.cac.washington.edu for more info. Oh please throw this MIME shit in the bin :) Ta. : Greetings, Gday! : i've got a small problem in connecting to my isp via ppp. please help me. : this is how i (attemnpt) to start a ppp session: : pppd /dev/cua2 38400 defaultroute noipdefault You have a /dev/cua2 device? Don't you mean /dev/cuaa2 or the like? I couldn't read the rest of your information because it looked like what appears below.. I'm sure it contains all the other details so if you can send it on in text i'm sure you'll get some more help. : --214585944-1145013221-842940395=:13820 : Content-Type: TEXT/PLAIN; charset=US-ASCII; name=debug : Content-Transfer-Encoding: BASE64 : Content-ID: : Content-Description: : QXVnIDE4IDE1OjMyOjU0IGJsYWggcHBwZFs2OF06IHNldF94YWNjbTogMDAw : MDAwMDAgMDAwMDAwMDAgMDAwMDAwMDAgNjAwMDAwMDAgDQpBdWcgMTggMTU6 : MzI6NTQgYmxhaCBwcHBkWzY4XTogc2VuZF9jb25maWc6IG10dSA9IDE1MDAg [20 tonnes of shit deleted] Regards, Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object! From owner-freebsd-isp Tue Sep 17 01:49:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21445 for isp-outgoing; Tue, 17 Sep 1996 01:49:26 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA21439 for ; Tue, 17 Sep 1996 01:49:21 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id BAA00269; Tue, 17 Sep 1996 01:49:12 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609170849.BAA00269@GndRsh.aac.dev.com> Subject: Re: SCSI configuration still In-Reply-To: from Robert Chalmers at "Sep 17, 96 05:33:13 pm" To: robert@chalmers.com.au (Robert Chalmers) Date: Tue, 17 Sep 1996 01:49:11 -0700 (PDT) Cc: freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, continuing the saga. The drive verified ok. formatted ok, so > the controller can see it and deal with it. > but the FreeBSD boot disk gives me a > > sd0(aha0:0:0): timed out > sd0(aha0:0:0): timed out AGAIN > > 4 times in all, then goes on with a probe of other stuff, then > into the menu. But it doesn't find the SCSI drive? > > any clues gurus? Lets see... did it find the aha1540? Is your aha1540 set for I/O address 0x330, irq 11, dma 5? If not FreeBSD can't find your controller, if it can't find the controller it can't find the disks. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Tue Sep 17 01:49:36 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21462 for isp-outgoing; Tue, 17 Sep 1996 01:49:36 -0700 (PDT) Received: from nanguo.chalmers.com.au (chalmers.com.au [203.1.96.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA21457 for ; Tue, 17 Sep 1996 01:49:32 -0700 (PDT) Received: by nanguo.chalmers.com.au (Smail3.1.28.1 #8) id m0v2w1a-000283C; Tue, 17 Sep 96 19:00 EST Message-Id: From: robert@chalmers.com.au (Robert Chalmers) Subject: Found the problem. SCSI irq conflict To: freebsd-isp@freebsd.org Date: Tue, 17 Sep 1996 19:00:58 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to all those helping. The mumboard was using irq11, in conflict with the card. set the card to 12, and all is well. now to finish the install.... what color did you say red was ? bc -- The China House Sheng Huo Jiu Shi Dou Zheng robert@chalmers.com.au for Whirled Peas http://chalmers.com.au Location: Web Works Whitsunday. 21'7" S, 149'14" E. From owner-freebsd-isp Tue Sep 17 02:33:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA23481 for isp-outgoing; Tue, 17 Sep 1996 02:33:09 -0700 (PDT) Received: from nanguo.chalmers.com.au (chalmers.com.au [203.1.96.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA23472 for ; Tue, 17 Sep 1996 02:33:05 -0700 (PDT) Received: by nanguo.chalmers.com.au (Smail3.1.28.1 #8) id m0v2whk-00036nC; Tue, 17 Sep 96 19:44 EST Message-Id: From: robert@chalmers.com.au (Robert Chalmers) Subject: atapi.flp To: freebsd-isp@freebsd.org Date: Tue, 17 Sep 1996 19:44:32 +1000 (EST) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know where the atapi.flp image is please ? thanks Bob -- The China House Sheng Huo Jiu Shi Dou Zheng robert@chalmers.com.au for Whirled Peas http://chalmers.com.au Location: Web Works Whitsunday. 21'7" S, 149'14" E. From owner-freebsd-isp Tue Sep 17 04:07:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA27350 for isp-outgoing; Tue, 17 Sep 1996 04:07:25 -0700 (PDT) Received: from synwork.com (root@synwork.com [199.3.234.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA27341 for ; Tue, 17 Sep 1996 04:07:23 -0700 (PDT) Received: from synwork.com (flaq@ns1.synwork.com [204.120.255.17]) by synwork.com (8.7.5/8.6.12) with SMTP id GAA08389; Tue, 17 Sep 1996 06:06:31 -0500 (CDT) Date: Tue, 17 Sep 1996 06:06:31 -0500 (CDT) From: Mike To: Igor Vinokurov cc: isp@freebsd.org Subject: Re: POP3/SMTP mail client for DOS In-Reply-To: <199609170634.KAA04900@escape.cs.ibank.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try Pegasus...do a search for it :) Mike On Tue, 17 Sep 1996, Igor Vinokurov wrote: > re, > > Anyone can recommend POP3/SMTP client for DOS? > Shareware/freeware prefered. > > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Syn-Work Media, Inc. | WWW Development & Hosting | Life Safety http://www.synwork.com | Systems Integration | CCTV mike@synwork.com | Voice/Data/Fiber | Access Control Flaq on IRC | Dukane Distributor | BICSI/RCDD :|:|:|: Powered By FreeBSD :|:|:|: Turning PC's Into Workstations ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ From owner-freebsd-isp Tue Sep 17 04:51:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29247 for isp-outgoing; Tue, 17 Sep 1996 04:51:37 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA29240 for ; Tue, 17 Sep 1996 04:51:33 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id VAA02192; Tue, 17 Sep 1996 21:49:13 +1000 (EST) Date: Tue, 17 Sep 1996 21:49:12 +1000 (EST) From: "Daniel O'Callaghan" To: Igor Vinokurov cc: isp@freebsd.org Subject: Re: POP3/SMTP mail client for DOS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Mike wrote: > On Tue, 17 Sep 1996, Igor Vinokurov wrote: > > > re, > > > > Anyone can recommend POP3/SMTP client for DOS? > > Shareware/freeware prefered. POPmail and Minuet, from ftp://boombox.micro.umn.edu/somewhere... Require packet drivers. Danny From owner-freebsd-isp Tue Sep 17 08:01:59 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA15799 for isp-outgoing; Tue, 17 Sep 1996 08:01:59 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA15562; Tue, 17 Sep 1996 07:59:13 -0700 (PDT) Received: from campa.panke.de (anonymous229.ppp.cs.tu-berlin.de [130.149.17.229]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id QAA05148; Tue, 17 Sep 1996 16:34:30 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id QAA01476; Tue, 17 Sep 1996 16:03:46 +0200 Date: Tue, 17 Sep 1996 16:03:46 +0200 From: Wolfram Schneider Message-Id: <199609171403.QAA01476@campa.panke.de> To: xiyuan qian Cc: isp@freebsd.org, questions@freebsd.org, steve@cioe.com Subject: Can I limit the size of incoming mail message? In-Reply-To: <199609160905.JAA14492@npc.haplink.co.cn> References: <199609160905.JAA14492@npc.haplink.co.cn> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk xiyuan qian writes: >Hi, my problem is: when someone send one message large than 12M to my customer, it can NOT been recieved by the customer with some email software such as Eudora. I think someone can help me limit this happen. src/usr.sbin/sendmail/cf/README confMAX_MESSAGE_SIZE MaxMessageSize [infinite] The maximum size of messages that will be accepted (in bytes). Wolfram From owner-freebsd-isp Tue Sep 17 08:22:49 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17033 for isp-outgoing; Tue, 17 Sep 1996 08:22:49 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17027 for ; Tue, 17 Sep 1996 08:22:46 -0700 (PDT) Received: from glacier.cold.org (glacier.sunrem.com [206.81.134.54]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id IAA21784 for ; Tue, 17 Sep 1996 08:22:45 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id JAA01906; Tue, 17 Sep 1996 09:22:14 -0600 (MDT) Date: Tue, 17 Sep 1996 09:22:12 -0600 (MDT) From: Brandon Gillespie To: hmmm cc: richards@herald.net, Rick Gray , isp@freebsd.org Subject: Re: Internet Explorer bug? In-Reply-To: <323DAA61.2FC0@alaska.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, hmmm wrote: > Richard Stanford wrote: > > > > Rick Gray wrote: > > > > Internet Explorer and Netscape Navigator will do their best to "fix" > > broken HTML. This can lead to certain errors being masked, until the > > page is viewed by lynx or another more literal browser. The problem > > here is that any key-sequence beginning with & ( < & © ... ) > > should end with a semicolon ( ; ). > > not according to my specs. a lack of a semicolon means a space. Semicolon is required. Because using something other than a semi-colon may work with Netscape and other browsers does NOT mean it is correct. When in doubt, reference _the_ only spec you should trust (do not trust anything from books or other FAQ's). The HTML 2.0 spec: http://www.w3.org/pub/WWW/MarkUp/html-spec/html-spec_9.html From owner-freebsd-isp Tue Sep 17 08:29:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17358 for isp-outgoing; Tue, 17 Sep 1996 08:29:24 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17353 for ; Tue, 17 Sep 1996 08:29:21 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA07339; Tue, 17 Sep 1996 10:20:08 -0500 From: Joe Greco Message-Id: <199609171520.KAA07339@brasil.moneng.mei.com> Subject: Re: INN history file and disk I/O To: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com) Date: Tue, 17 Sep 1996 10:20:08 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, petzi@zit.th-darmstadt.de, isp@freebsd.org In-Reply-To: <199609170505.WAA21901@MindBender.serv.net> from "Michael L. VanLoon -- HeadCandy.com" at Sep 16, 96 10:05:47 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Lesson #1: YOU CAN NEVER HAVE TOO MUCH RAM IN A NEWS SERVER :-) > >(ok, well, if you have 20GB of disk and 10GB of RAM, I might argue you > >were approaching having enough RAM). > > Or, approaching bankruptcy... ;-) Maybe not, at today's RAM prices. Under $1000 for 128MB RAM? There's no excuse any longer not to fill these machines up to capacity. ... JG From owner-freebsd-isp Tue Sep 17 08:29:46 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17386 for isp-outgoing; Tue, 17 Sep 1996 08:29:46 -0700 (PDT) Received: from radio.nwpros.com (nwpros.com [205.229.128.214]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA17381 for ; Tue, 17 Sep 1996 08:29:44 -0700 (PDT) Received: from rickbox.nwpros.com (rickbox.nwpros.com [205.229.128.217]) by radio.nwpros.com (8.6.12/8.6.12) with SMTP id KAA20192 for ; Tue, 17 Sep 1996 10:33:14 -0500 Message-Id: <1.5.4.32.19960917154122.0067c7f0@nwpros.com> X-Sender: rickg@nwpros.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Sep 1996 10:41:22 -0500 To: isp@freebsd.org From: Rick Gray Subject: Re:Internet Explorer Bug? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Once more thanks for all the responses I have received. It appears everyone is correct--use a semicolon at the end of all &# entities. My customer has confirmed that now he can read the whole word. Once again thanks. Keep up the great work, gang! :-) ************************************************ Rick Gray Director of Internet Services Network Pros, Inc. rickg@nwpros.com (713)780-5900 "It is a good day to die." ----Klingon Philosophy ************************************************ From owner-freebsd-isp Tue Sep 17 09:02:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19132 for isp-outgoing; Tue, 17 Sep 1996 09:02:53 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19126 for ; Tue, 17 Sep 1996 09:02:47 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA07397; Tue, 17 Sep 1996 10:58:09 -0500 From: Joe Greco Message-Id: <199609171558.KAA07397@brasil.moneng.mei.com> Subject: Re: INN drive configuration To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 17 Sep 1996 10:58:09 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, richards@herald.net, isp@FreeBSD.ORG In-Reply-To: <199609170215.TAA03291@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 16, 96 07:15:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ... > > > You might want to go look through the mailing list archives, I have gone > > on and on about this sort of stuff in the past... > > Any up and coming ISP types out there should take this suggestion very > seriously. Joe has posted more useful information on many aspects of > how to make a ``Real NewsEngine'' and for that matter just on how to > be a very good ISP. HA! I am just a crazy old sysadmin who has been doing this stuff so long it becomes "common sense" :-) Thanks for the kind words, Rod, but the reality is simply that I have seen so many people do it _wrong_ (including one major ISP who I do lots of work for) and it just seems silly to allow other people to repeat the same mistakes (particularly when big bucks hardware is concerned). I _promise_ anybody who wants to undertake the burden of Usenet news that if you do NOT do the hardware right, you are in for a world of hurt. And the hardware is not easy to get right... Rod of all people knows this (and I will "scratch his back" and mention that Rod is _the_ person I trust as THE authority on server class motherboards/etc. You will not find more value for your dollars buying anywhere else!) Even after that, though, the software lessons and hurdles are very large. > This is _free_ advice that you should be paying contractor fees to get, > and even at that it would be more than worth it. > > My hats off to Joe Greco and his infinite depth of wisdom he has so > genoursly shared with us all. Ohhhh I am gonna be sick I think :-) But thanks Rod. And I in turn would like to thank all the FreeBSD folks for all of this, all my best machines and systems run FreeBSD, and over the years, so many FreeBSDers have been so helpful... the support available under FreeBSD has generally surpassed what I've seen from many commercial entities such as SCO and SunSoft, and the technical competence and excellence of ANY of these folks is hard to beat. What relatively little advice I can offer is in no way sufficient repayment to all of these folks for this wonderful OS. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-isp Tue Sep 17 09:32:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21119 for isp-outgoing; Tue, 17 Sep 1996 09:32:23 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA21102 for ; Tue, 17 Sep 1996 09:32:19 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id JAA19824; Tue, 17 Sep 1996 09:32:18 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id JAA25400; Tue, 17 Sep 1996 09:32:12 -0700 (PDT) Message-Id: <199609171632.JAA25400@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: petzi@zit.th-darmstadt.de, isp@freebsd.org Subject: Re: INN history file and disk I/O In-reply-to: Your message of Tue, 17 Sep 96 10:20:08 -0500. <199609171520.KAA07339@brasil.moneng.mei.com> Date: Tue, 17 Sep 1996 09:32:12 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Lesson #1: YOU CAN NEVER HAVE TOO MUCH RAM IN A NEWS SERVER :-) >> >(ok, well, if you have 20GB of disk and 10GB of RAM, I might argue you >> >were approaching having enough RAM). >> >> Or, approaching bankruptcy... ;-) > >Maybe not, at today's RAM prices. Under $1000 for 128MB RAM? There's >no excuse any longer not to fill these machines up to capacity. Oh, I agree. Definitely. I was just referring to 10GB of RAM... Roughly $51,000 at todays prices. Of course, about seven months ago, that would have been closer to $275,000! ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Tue Sep 17 09:49:20 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21983 for isp-outgoing; Tue, 17 Sep 1996 09:49:20 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA21974 for ; Tue, 17 Sep 1996 09:49:15 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA07494; Tue, 17 Sep 1996 11:39:53 -0500 From: Joe Greco Message-Id: <199609171639.LAA07494@brasil.moneng.mei.com> Subject: Re: INN history file and disk I/O To: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com) Date: Tue, 17 Sep 1996 11:39:53 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, petzi@zit.th-darmstadt.de, isp@freebsd.org In-Reply-To: <199609171632.JAA25400@MindBender.serv.net> from "Michael L. VanLoon -- HeadCandy.com" at Sep 17, 96 09:32:12 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> >Lesson #1: YOU CAN NEVER HAVE TOO MUCH RAM IN A NEWS SERVER :-) > >> >(ok, well, if you have 20GB of disk and 10GB of RAM, I might argue you > >> >were approaching having enough RAM). > >> > >> Or, approaching bankruptcy... ;-) > > > >Maybe not, at today's RAM prices. Under $1000 for 128MB RAM? There's > >no excuse any longer not to fill these machines up to capacity. > > Oh, I agree. Definitely. > > I was just referring to 10GB of RAM... Roughly $51,000 at todays > prices. Of course, about seven months ago, that would have been > closer to $275,000! I know people that have paid $51,000 for their news operations :-) It is not that much of a stretch... but somebody has to show me a MB that can handle it first ;-) ... JG From owner-freebsd-isp Tue Sep 17 11:52:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05540 for isp-outgoing; Tue, 17 Sep 1996 11:52:18 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA05535 for ; Tue, 17 Sep 1996 11:52:17 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id LAA21192; Tue, 17 Sep 1996 11:05:33 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id LAA20648; Tue, 17 Sep 1996 11:46:10 -0700 Date: Tue, 17 Sep 1996 11:46:09 -0700 (PDT) From: Michael Dillon To: inet-access@earth.com cc: iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Livingston and spoofed source SYN attacks Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Seems there was a little problem with the Livingston filter that I posted ---------- fragment of message ---------- I have to stand somewhat corrected. >create a filter "internet.out" >Contents: >three lines for each net block you have: > > permit 1.2.3.4/20 tcp > permit 1.2.3.4/20 udp > permit 1.2.3.4/20 icmp The more appropriate format would be: permit 1.2.3.4/20 0.0.0.0/0 tcp permit 1.2.3.4/20 0.0.0.0/0 udp permit 1.2.3.4/20 0.0.0.0/0 icmp You are *supposed* to use a src/dest netblock pair, though I have set up and used w/o a dest address and it worked. >final line to log (optional) MUST COME AFTER permit list for netblocks: > deny log If you choose not to log, then you need a line: deny Otherwise that which falls through isn't denied, obviously. From owner-freebsd-isp Tue Sep 17 11:58:03 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05773 for isp-outgoing; Tue, 17 Sep 1996 11:58:03 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA05768 for ; Tue, 17 Sep 1996 11:58:00 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id LAA21235; Tue, 17 Sep 1996 11:11:29 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id LAA20715; Tue, 17 Sep 1996 11:52:05 -0700 Date: Tue, 17 Sep 1996 11:52:05 -0700 (PDT) From: Michael Dillon To: inet-access@earth.com cc: iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Livingston source spoofed SYN filters Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---------- fragment of a message ---------- > permit 1.2.3.4/20 tcp > permit 1.2.3.4/20 udp > permit 1.2.3.4/20 icmp Actually, a single "permit 1.2.3.4/20" line will do. In Livingston command line syntax: set filter internet.out 1 permit 1.2.3.4/20 > rest of the filter. This is optional. Keep in mind that the panix > attack would probably have flooded your syslog machine's disk space > with syslog info in this case. Hardening that is an issue for another day, > however. Logging denies will fill up your log anyway. Packets arriving for a dialup user after he/she hangs up fall through to the default route back out of the box. They are then _outbound_ packets with source address off the network and destination address on the network. Dialup providers who want to log denies based on a source address being on their network should have a preceding unlogged deny based on the destination address being on their network: set filter internet.out 1 permit 1.2.3.4/20 set filter internet.out 2 deny 0.0.0.0/0 1.2.3.4/20 set filter internet.out 3 deny log From owner-freebsd-isp Tue Sep 17 12:37:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08634 for isp-outgoing; Tue, 17 Sep 1996 12:37:37 -0700 (PDT) Received: from patty.loop.net (patty.loop.net [204.179.169.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA08629 for ; Tue, 17 Sep 1996 12:37:35 -0700 (PDT) Received: (from cassy@localhost) by patty.loop.net (8.6.12/8.6.12) id MAA24087; Tue, 17 Sep 1996 12:37:04 -0700 Date: Tue, 17 Sep 1996 12:37:04 -0700 (PDT) From: Cassandra Perkins X-Sender: cassy@patty.loop.net To: Robert Chalmers cc: freebsd-isp@freebsd.org Subject: Re: SCSI configuration still In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I not sure about your particular drive, but Seagate Barracuda drives have a jumper setting that inserts a startup delay based on the id# of the drive. There is also a setting that prevents the drives from starting up until they receive a signal from the host adapter. If you have similar settings on your drive, try disabling them. Cassandra The Loop ISC On Tue, 17 Sep 1996, Robert Chalmers wrote: > Well, continuing the saga. The drive verified ok. formatted ok, so > the controller can see it and deal with it. > but the FreeBSD boot disk gives me a > > sd0(aha0:0:0): timed out > sd0(aha0:0:0): timed out AGAIN > > 4 times in all, then goes on with a probe of other stuff, then > into the menu. But it doesn't find the SCSI drive? > > any clues gurus? > > cheers, > Bob > > -- > The China House Sheng Huo Jiu Shi Dou Zheng > robert@chalmers.com.au for Whirled Peas http://chalmers.com.au > Location: Web Works Whitsunday. 21'7" S, 149'14" E. > From owner-freebsd-isp Tue Sep 17 13:10:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11253 for isp-outgoing; Tue, 17 Sep 1996 13:10:39 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11244 for ; Tue, 17 Sep 1996 13:10:33 -0700 (PDT) Received: from localhost (petzi@localhost) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id WAA23338; Tue, 17 Sep 1996 22:08:59 +0200 (MET DST) Date: Tue, 17 Sep 1996 22:08:59 +0200 (MET DST) From: Michael Beckmann To: Joe Greco cc: isp@freebsd.org Subject: Re: INN history file and disk I/O In-Reply-To: <199609171520.KAA07339@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > Maybe not, at today's RAM prices. Under $1000 for 128MB RAM? There's > no excuse any longer not to fill these machines up to capacity. Right, but I didn't buy the machine. My predecessor put 4 x 16 MB in it, so the SIMM slots were full. I wouldn't have bought a P120 either. However, I will upgrade the newsserver to 160 MB EDO RAM this week (it has 6 SIMM slots, now that I gave it a decent mainboard)... Michael From owner-freebsd-isp Tue Sep 17 16:01:05 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20030 for isp-outgoing; Tue, 17 Sep 1996 16:01:05 -0700 (PDT) Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20016 for ; Tue, 17 Sep 1996 16:00:56 -0700 (PDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.7.5/8.6.9) with ESMTP id QAA01790; Tue, 17 Sep 1996 16:00:50 -0700 (PDT) Received: (from jgt10@localhost) by server.livingston.com (8.7.1/8.6.9) id QAA26482; Tue, 17 Sep 1996 16:00:06 -0700 (PDT) Date: Tue, 17 Sep 1996 16:00:06 -0700 (PDT) From: "John G. Thompson" X-Sender: jgt10@server To: inet-access@earth.com cc: inet-access@earth.com, iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Re: Livingston and spoofed source SYN attacks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Michael Dillon wrote: > Seems there was a little problem with the Livingston filter that I posted > > ---------- fragment of message ---------- > > I have to stand somewhat corrected. > > >create a filter "internet.out" > >Contents: > >three lines for each net block you have: > > > > permit 1.2.3.4/20 tcp > > permit 1.2.3.4/20 udp > > permit 1.2.3.4/20 icmp > > The more appropriate format would be: > permit 1.2.3.4/20 0.0.0.0/0 tcp This can be shortened to permit 1.2.3.4/20 0.0.0.0/0 which will show up on the filter display as permit 1.2.3.4/20 0.0.0.0/0 ip > permit 1.2.3.4/20 0.0.0.0/0 udp > permit 1.2.3.4/20 0.0.0.0/0 icmp > > You are *supposed* to use a src/dest netblock pair, though I have > set up and used w/o a dest address and it worked. > > >final line to log (optional) MUST COME AFTER permit list for netblocks: > > deny log > > If you choose not to log, then you need a line: > deny > > Otherwise that which falls through isn't denied, obviously. Portmaster filtering is evaluation is in order of rules and an implicit deny if no matching rule is found. You don't need the final deny when you don't want to log, but it isn't going to hurt anything. JGT -- John G. Thompson Livingston Enterprises Inc. Phone: (800) 458-9966 JOAT(MON) 6920-220 Koll Centre Pkwy. Fax: (510) 426-8951 support@livingston.com Pleasanton, CA 94566 http://www.livingston.com From owner-freebsd-isp Tue Sep 17 16:12:58 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20553 for isp-outgoing; Tue, 17 Sep 1996 16:12:58 -0700 (PDT) Received: from sumter.awod.com (awod.com [198.81.225.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA20547 for ; Tue, 17 Sep 1996 16:12:56 -0700 (PDT) Received: from tsunami..awod.com (chs0088.awod.com [198.81.225.197]) by sumter.awod.com (8.6.12/8.6.12) with SMTP id TAA20318; Tue, 17 Sep 1996 19:12:39 -0400 Message-Id: <199609172312.TAA20318@sumter.awod.com> Comments: Authenticated sender is From: "Ken Lam" To: Bo Fussing Date: Tue, 17 Sep 1996 19:12:38 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: EmpLink using BSD UNIX? CC: isp@freebsd.org Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: Bo Fussing > We just received some marketing material from EMPaC who sell the EmpView > Internet/Intranet Server Operating System. I was very interested to find > out that the Operating System is described as 4.4 BSD Unix based! > > Has anybody got any idea if this is just rehashed Free/Net/OpenBSD or > BSD/OS. It is BSDI (a few revs back--as it doesn't support AHA2940s like BSDI 2.1 does). -k --- Ken Lam lam@awod.com Integrated Technical Systems Systems, Networks, and Internet Solutions -- Defining Technology Today "'Plug and Play' was only applicable to the original ATARI(tm)" From owner-freebsd-isp Tue Sep 17 20:09:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA04851 for isp-outgoing; Tue, 17 Sep 1996 20:09:04 -0700 (PDT) Received: from saturn.col.com.hk ([203.83.252.38]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA04817 for ; Tue, 17 Sep 1996 20:08:58 -0700 (PDT) Received: from localhost by saturn.col.com.hk; (5.65v3.2/1.1.8.2/23Mar96-1150AM) id AA21303; Wed, 18 Sep 1996 11:10:25 +0800 Date: Wed, 18 Sep 1996 11:10:25 +0800 (HKT) From: Joe Lee To: Joe Greco Cc: isp@FreeBSD.org Subject: Re: INN history file and disk I/O In-Reply-To: <199609171520.KAA07339@brasil.moneng.mei.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Joe Greco wrote: > > >Lesson #1: YOU CAN NEVER HAVE TOO MUCH RAM IN A NEWS SERVER :-) > > >(ok, well, if you have 20GB of disk and 10GB of RAM, I might argue you > > >were approaching having enough RAM). > > > > Or, approaching bankruptcy... ;-) > > Maybe not, at today's RAM prices. Under $1000 for 128MB RAM? There's > no excuse any longer not to fill these machines up to capacity. > > ... JG > But i don't think you can put more than 4GB memory to a i386 arch PC. From owner-freebsd-isp Wed Sep 18 01:53:21 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12655 for isp-outgoing; Wed, 18 Sep 1996 01:53:21 -0700 (PDT) Received: from npc.haplink.co.cn ([202.96.192.53]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA12572; Wed, 18 Sep 1996 01:53:06 -0700 (PDT) Received: (from xiyuan@localhost) by npc.haplink.co.cn (8.6.11/8.6.9) id QAA22974; Wed, 18 Sep 1996 16:59:31 GMT Date: Wed, 18 Sep 1996 16:59:31 GMT From: xiyuan qian Message-Id: <199609181659.QAA22974@npc.haplink.co.cn> To: isp@freebsd.org Subject: Can FreeBSD be setup on IBM PC 320? Cc: questions@freebsd.org, steve@cioe.com Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I need help on install FreeBSD2.1.5 on an IBM PC 320. If someone has the experience, would you please show me some lint. I had trouble with install it on IBM PC 300, no scsi disk support of FreeBSD2.0.5. I do not know how is now? With PC 320, it's scsi adapter is Adaptec AHA2940, any problem? Best regaurds! --xiyuan From owner-freebsd-isp Wed Sep 18 02:38:59 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28018 for isp-outgoing; Wed, 18 Sep 1996 02:38:59 -0700 (PDT) Received: from freebsd.gaffaneys.com (dialup4.gaffaneys.com [134.129.252.23]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27992 for ; Wed, 18 Sep 1996 02:38:51 -0700 (PDT) Received: (from zach@localhost) by freebsd.gaffaneys.com (8.7.5/8.7.3) id EAA01881; Wed, 18 Sep 1996 04:40:10 -0500 (CDT) To: Joe Lee Cc: Joe Greco , isp@FreeBSD.org Subject: Re: INN history file and disk I/O References: From: Zach Heilig Date: 18 Sep 1996 04:40:09 -0500 In-Reply-To: Joe Lee's message of Wed, 18 Sep 1996 11:10:25 +0800 (HKT) Message-ID: <87d8zkrwjq.fsf@freebsd.gaffaneys.com> Lines: 16 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Joe Lee writes: > But i don't think you can put more than 4GB memory to a i386 arch PC. There is a 48-bit virtual address space on the i386+ cpus. Even if there aren't pins labled a32->a47, I suspect there is some way to get those addresses out of the chip. Failing that, you could use an expanded memory type of scheme, and theoretically add as much memory as you want. But that might be considered cheating... -- Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email Support bacteria -- it's the | is unwelcome. I avoid dealing only culture some people have! | with companies that email ads. From owner-freebsd-isp Wed Sep 18 03:22:34 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA15835 for isp-outgoing; Wed, 18 Sep 1996 03:22:34 -0700 (PDT) Received: from guava.blueberry.co.uk ([194.70.52.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15800 for ; Wed, 18 Sep 1996 03:22:28 -0700 (PDT) Received: (from nik@localhost) by guava.blueberry.co.uk (8.7.5/8.7.3) id LAA26906 for isp@freebsd.org; Wed, 18 Sep 1996 11:19:05 +0100 (BST) From: Nik Clayton Message-Id: <199609181019.LAA26906@guava.blueberry.co.uk> Subject: Routers - hardware received wisdom To: isp@freebsd.org Date: Wed, 18 Sep 1996 11:19:05 +0100 (BST) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm going to be requiring two network routers, and since FreeBSD is more than capable of the task, I figured I'd go for the cheap 486 option. One of these routers will be sat between a 2Mb/s leased line and a 10Mb/s ethernet, and the other will be between 2 10Mb/s ethernets. As far as I can tell, FreeBSD 2.1.5, a PCI based 66MHz 486DX with 16MB RAM and 2 DC201040 PCI network cards should be sufficient. But can I drop it any lower than that? Would the boxes be fine with 8MB RAM? What about 33MHz machines? Basically, I want to get this done on the lowest spec possible, because if I don't, I know that someone will say "Hey, those machines aren't doing much, can we run J. Random application on them as well?", and on the whole, I don't want that. I've hunted the mailing lists, and haven't seen anything that's that specific on this topic. Cheers, N -- --+=[ Blueberry Hill Blueberry Design ]=+-- --+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+-- --+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+-- --+=[ Somedays, I wonder why I even bother chewing through the straps. ]ENTP From owner-freebsd-isp Wed Sep 18 06:58:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA02713 for isp-outgoing; Wed, 18 Sep 1996 06:58:53 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA02694 for ; Wed, 18 Sep 1996 06:58:50 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA08874; Wed, 18 Sep 1996 08:57:44 -0500 From: Joe Greco Message-Id: <199609181357.IAA08874@brasil.moneng.mei.com> Subject: Re: Routers - hardware received wisdom To: nik@blueberry.co.uk (Nik Clayton) Date: Wed, 18 Sep 1996 08:57:43 -0500 (CDT) Cc: isp@freebsd.org In-Reply-To: <199609181019.LAA26906@guava.blueberry.co.uk> from "Nik Clayton" at Sep 18, 96 11:19:05 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > I'm going to be requiring two network routers, and since FreeBSD is more > than capable of the task, I figured I'd go for the cheap 486 option. > > One of these routers will be sat between a 2Mb/s leased line and a 10Mb/s > ethernet, and the other will be between 2 10Mb/s ethernets. > > As far as I can tell, FreeBSD 2.1.5, a PCI based 66MHz 486DX with 16MB RAM > and 2 DC201040 PCI network cards should be sufficient. > > But can I drop it any lower than that? Would the boxes be fine with 8MB > RAM? What about 33MHz machines? > > Basically, I want to get this done on the lowest spec possible, because if > I don't, I know that someone will say "Hey, those machines aren't doing > much, can we run J. Random application on them as well?", and on the whole, > I don't want that. > > I've hunted the mailing lists, and haven't seen anything that's that specific > on this topic. My experiences - and I am very familiar with doing things on a budget, since I run Milwaukee's only free public access UNIX system :-) : I ran a T1 gateway for a year on a 386DX/40, 8MB RAM, ET50XX and NE2000. Worked GREAT, did firewalling, and the line was fairly busy. However, once you got past about 300 pkts/sec (total as reported by netstat), the box started to get a little sluggish and idle CPU started to drop below "acceptable" (I want 70% average idle on a router). It could saturate the T1 with large packet traffic like FTP, etc., no problem though. I currently run this same box on a 486DX5/133, PCI, 16MB RAM, ET50XX, and two DC21041 Ethernets. Still works great, handles 500-600 pkts/sec with 88% idle. The 16MB was convenience not necessity. One of my main routers is a 386DX/40, 8MB RAM, and six (count: six) SMC Elite and Ultra Ethernets. It is in the "red zone" most of the time these days, varying between 40% and 70% idle, and handling an average of about 300 pkts/sec, and I am looking to replace it with something faster. The main problem is that I run news.sol.net on one side of it and all the traffic must go through it... but I refuse to allow hardware to dictate my network architecture, so I will fix the router :-) 8MB RAM is perfectly sufficient for a pure router. I used to use 4MB, and only raised it to 8MB because FreeBSD 2.0R would occasionally freak and lock on 4MB due to some forgotten problem. However, once you start running userland programs (including things like gated), your memory requirements may go up. As for your specific problem: Do not play games with the CPU. If you are buying new stuff, there is no excuse to buy anything other than a 486DX5/133. I highly(!!!!!) recommend the AMD 486/133 "ADZ" variant, it does not even need a heat sink to run cool, and I have always hated having moving parts on a critical component. The cost of doing this as opposed to something else is very small. If you are afraid other people will run things on the box, be a jerk: partition the system with as little disk space as possible, making it less tempting to use. Don't provide them with user accounts. And simply tell them that the machine isn't equipped to handle it, and it is cheap to build another box for their needs. Routers should be utility boxes that you jam in a closet in a forgotten area, and you should be able to forget that they exist. They absolutely should not be running anything other than the bare essentials needed to make them route. I know some people do not share this point of view, but I feel that if I ever _lose_ a router (happened once, hard drive developed an entire bad track), I want to be able to be up and running within the hour. Incidentally: since I keep a custom variant ("cookie cutter router") of FreeBSD around, when the 386DX/40 with six SMC's I discussed above did fail, it took me a very short amount of time to have the machine back on line, reconfigured, and routing. ... JG From owner-freebsd-isp Wed Sep 18 08:17:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA06670 for isp-outgoing; Wed, 18 Sep 1996 08:17:37 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA06640 for ; Wed, 18 Sep 1996 08:17:32 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA03226; Wed, 18 Sep 1996 11:23:06 -0400 Date: Wed, 18 Sep 1996 11:23:06 -0400 Message-Id: <199609181523.LAA03226@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Nik Clayton From: dennis@etinc.com (Dennis) Subject: Re: Routers - hardware received wisdom Cc: isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi, > >I'm going to be requiring two network routers, and since FreeBSD is more >than capable of the task, I figured I'd go for the cheap 486 option. > >One of these routers will be sat between a 2Mb/s leased line and a 10Mb/s >ethernet, and the other will be between 2 10Mb/s ethernets. > >As far as I can tell, FreeBSD 2.1.5, a PCI based 66MHz 486DX with 16MB RAM >and 2 DC201040 PCI network cards should be sufficient. > >But can I drop it any lower than that? Would the boxes be fine with 8MB >RAM? What about 33MHz machines? Its totally dependent on how much local ethernet traffic you have. If you will be switching lots of traffic locally, you might be unhappy with a 33Mhz box. But at today's prices, what are you going to save? $10.? Its not worth it. 100Mhz processars are only $32 or so....you're spending more than that thinking about it. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-isp Wed Sep 18 08:26:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA09806 for isp-outgoing; Wed, 18 Sep 1996 08:26:35 -0700 (PDT) Received: from super-g.inch.com (spork@super-g.com [204.178.32.161]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA09785 for ; Wed, 18 Sep 1996 08:26:31 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.6.12/8.6.9) with SMTP id JAA13904; Wed, 18 Sep 1996 09:24:37 -0500 Date: Wed, 18 Sep 1996 09:24:37 -0500 (CDT) From: "S(pork)" X-Sender: spork@super-g.inch.com To: Michael Beckmann cc: Joe Greco , isp@FreeBSD.org Subject: Re: INN history file and disk I/O In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello, We'll be building a new news server here rather soon, and I was wondering if anyone in on this discussion has any preferences in motherboards and dealers... Our usual supplier is having some trouble coming up with a recommendation on a RAM-packed motherboard... Thanks, Charles On Tue, 17 Sep 1996, Michael Beckmann wrote: > Hi, > > > Maybe not, at today's RAM prices. Under $1000 for 128MB RAM? There's > > no excuse any longer not to fill these machines up to capacity. > > Right, but I didn't buy the machine. My predecessor put 4 x 16 MB in it, > so the SIMM slots were full. I wouldn't have bought a P120 either. > However, I will upgrade the newsserver to 160 MB EDO RAM this week (it has > 6 SIMM slots, now that I gave it a decent mainboard)... > > Michael > From owner-freebsd-isp Wed Sep 18 09:19:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05791 for isp-outgoing; Wed, 18 Sep 1996 09:19:08 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA05766 for ; Wed, 18 Sep 1996 09:19:02 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA09163; Wed, 18 Sep 1996 11:17:16 -0500 From: Joe Greco Message-Id: <199609181617.LAA09163@brasil.moneng.mei.com> Subject: Re: INN history file and disk I/O To: spork@super-g.com (S) Date: Wed, 18 Sep 1996 11:17:15 -0500 (CDT) Cc: petzi@zit.th-darmstadt.de, jgreco@brasil.moneng.mei.com, isp@FreeBSD.org In-Reply-To: from "S" at Sep 18, 96 09:24:37 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Hello, > > We'll be building a new news server here rather soon, and I was wondering > if anyone in on this discussion has any preferences in motherboards and > dealers... Our usual supplier is having some trouble coming up with a > recommendation on a RAM-packed motherboard... > > Thanks, > > Charles Contact: Rod Grimes, Accurate Automation Company. . You want a Triton-II based board. Rod sells at least two decent boards. Rod is god on any motherboard issues, listen to what he has to say. I have had some trouble stuffing boards with RAM too, it seems that contemporary RAM is not up to the task :-( This is not necessarily an "easy" thing to do. Curt found an expensive source for 64MB SIMM modules that are working just fine in one of Rod's EISA boards. Let me see.. (Oh damn it, Netcrap just expired... time to use a real Web browser) While I am trying to play Guess the MB with ASUS's slow Web site, I will refer to one board as "ISA" and the other as "EISA".. Neither the ISA nor the EISA board would accept 36-chip 64MB SIMM modules we tried, and we had some custom 12-chip 64MB SIMM modules manufactured that did not work either. The machine regularly freaked on a daily basis. Finding 64MB SIMM modules with <= 24 chips (as recommended by the ASUS manual) has been virtually impossible. The EISA board has accepted 4 very expensive SIMM modules and works fine. We have not tried them in the ISA board but will shortly. I believe that they are 36-chip modules but they do work. The EISA board rejected various combinations of 32MB parity SIMM modules once more than 4 were installed. It accepted a specific type of 32MB EDO modules when 6 were installed (192MB) but not 8 of them. Anyways... the EISA board is: ASUS P/E-P55T2P4D which has 8 SIMM slots and the ISA board is: ASUS P/I-P55T2P4 which has 4 SIMM slots. ... JG From owner-freebsd-isp Wed Sep 18 10:12:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26427 for isp-outgoing; Wed, 18 Sep 1996 10:12:19 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA26395 for ; Wed, 18 Sep 1996 10:12:15 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id TAA25046; Wed, 18 Sep 1996 19:08:50 +0200 Message-Id: <199609181708.TAA25046@login.bigblue.no> From: "Frode Nordahl" To: "Joe Greco" Cc: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 18:18:19 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Denying expired users POP? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996 13:30:50 -0500 (CDT), Joe Greco wrote: >> >Well, I certainly agree it isn't optimal. But writing a script to >> >change the passwd file (after looking at the expiry date) >> >wouldn't be particularly difficult. >> >> If there is no other option, I guess I have to do that then :-( > >Would it be smarter to create a patch to do the expiration thing, and >then submit it someplace where folks are likely to find it useful? > >I don't know who maintains qpopper, but if they're not willing to support >a vendor specific extension, it would still be nice to have it as a >"patch" that got bundled along with the FreeBSD port. I agree! Should be a part of a port in the ports collection or something... I'll try to contact the maintainers of qpopper and see if they are interested in implementing such a feature. If not I would be more than glad if someone would like to patch it for us... I'm not a C programmer, so It's not likelly that I can do such a thing... --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 10:12:31 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26524 for isp-outgoing; Wed, 18 Sep 1996 10:12:31 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA26480 for ; Wed, 18 Sep 1996 10:12:25 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id TAA25071; Wed, 18 Sep 1996 19:10:09 +0200 Message-Id: <199609181710.TAA25071@login.bigblue.no> From: "Frode Nordahl" To: "Daniel O'Callaghan" Cc: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 18:19:38 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Denying expired users POP? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996 14:38:42 +1000 (EST), Daniel O'Callaghan wrote: > > >On Mon, 16 Sep 1996, Frode Nordahl wrote: > >> On Tue, 17 Sep 1996 01:47:16 +1000 (EST), David Nugent wrote: >> >Well, I certainly agree it isn't optimal. But writing a script to >> >change the passwd file (after looking at the expiry date) >> >wouldn't be particularly difficult. >> >> If there is no other option, I guess I have to do that then :-( > >What about modifying popper to look at the expiry time? I'm no C programmer, so someone else would have to do that :) I'll send a mail to the qpopper maintainers and see if they are interested. --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 10:31:59 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA07759 for isp-outgoing; Wed, 18 Sep 1996 10:31:59 -0700 (PDT) Received: from hon.hn ([206.48.105.210]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA07703 for ; Wed, 18 Sep 1996 10:31:53 -0700 (PDT) Received: from hon.hn.hon.hn (si1.hon.hn [206.48.253.70]) by hon.hn (8.7.5/8.7.3) with SMTP id LAA27578 for ; Wed, 18 Sep 1996 11:31:13 -0600 (CST) Message-ID: <323F8984.5166@hon.hn> Date: Wed, 18 Sep 1996 11:32:52 +0600 From: "Samuel E. Romero" Organization: Soluciones Internacionales X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: FreeBSD ISP Mailing List Subject: NNTP Feeder somewhere? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Where can I get an NNTP feeder?. Somebody knows where can I get this type of service. I don't have news access right now (nobody has one here in my country), and I want to setup a news server here. Somebody knows?. -- Samuel E. Romero Soluciones Internacionales ser@hon.hn Honduras On Net Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D -- From owner-freebsd-isp Wed Sep 18 10:39:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12103 for isp-outgoing; Wed, 18 Sep 1996 10:39:04 -0700 (PDT) Received: from plato.oneworld.net (paul@plato.oneworld.net [204.176.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA12080 for ; Wed, 18 Sep 1996 10:39:02 -0700 (PDT) Received: (from paul@localhost) by plato.oneworld.net (8.7.5/8.7.1) id NAA18970 for isp@freebsd.org; Wed, 18 Sep 1996 13:38:59 -0400 (EDT) From: Paul Nash Message-Id: <199609181738.NAA18970@plato.oneworld.net> Subject: CERN errors To: isp@freebsd.org Date: Wed, 18 Sep 1996 13:38:58 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I recently switched one of our client's websites onto one of our FreeBSD boxes and have noticed alot more /kernel errors.. Sep 18 12:50:36 lennon /kernel: pid 4053 (bostonapartments), uid 65534: exited on signal 10 Sep 18 13:16:16 lennon /kernel: pid 4700 (bostonapartments), uid 65534: exited on signal 10 Sep 18 13:24:26 lennon /kernel: pid 4781 (bostonapartments), uid 65534: exited on signal 10 Sep 18 13:24:29 lennon /kernel: pid 4783 (bostonapartments), uid 65534: exited on signal 10 The webserver doesn't die, it just spits out errors.. All of the other webservers that are homed on the box are running flawlessly.. Anyone else run into this kind of situation and know of a remedy? Thanks, -Paul From owner-freebsd-isp Wed Sep 18 10:41:27 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13741 for isp-outgoing; Wed, 18 Sep 1996 10:41:27 -0700 (PDT) Received: from plato.oneworld.net (paul@plato.oneworld.net [204.176.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA13720 for ; Wed, 18 Sep 1996 10:41:24 -0700 (PDT) Received: (from paul@localhost) by plato.oneworld.net (8.7.5/8.7.1) id NAA19029 for isp@freebsd.org; Wed, 18 Sep 1996 13:41:22 -0400 (EDT) From: Paul Nash Message-Id: <199609181741.NAA19029@plato.oneworld.net> Subject: CERN errors (fwd) To: isp@freebsd.org Date: Wed, 18 Sep 1996 13:41:22 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Forwarded message: > Hi, > I recently switched one of our client's websites onto one of our FreeBSD boxes > and have noticed alot more /kernel errors.. > > Sep 18 12:50:36 lennon /kernel: pid 4053 (bostonapartments), uid 65534: exited on signal 10 > Sep 18 13:16:16 lennon /kernel: pid 4700 (bostonapartments), uid 65534: exited on signal 10 > Sep 18 13:24:26 lennon /kernel: pid 4781 (bostonapartments), uid 65534: exited on signal 10 > Sep 18 13:24:29 lennon /kernel: pid 4783 (bostonapartments), uid 65534: exited on signal 10 > > The webserver doesn't die, it just spits out errors.. All of the other > webservers that are homed on the box are running flawlessly.. Anyone else run > into this kind of situation and know of a remedy? > Gak.. I forgot the useful information: FreeBSD 2.1.5-stable CERN 3.0 w/multi-homing patch i'm homing about 10 other sites on the box aswell w/32mb ram (its going to 64mb in the next couple of days). -Paul From owner-freebsd-isp Wed Sep 18 10:49:40 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18454 for isp-outgoing; Wed, 18 Sep 1996 10:49:40 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA18433 for ; Wed, 18 Sep 1996 10:49:36 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id TAA25218 for ; Wed, 18 Sep 1996 19:47:31 +0200 Message-Id: <199609181747.TAA25218@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 18:56:59 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: telnetd and available network tty's Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is it possible to increase the number of network ttys in FreeBSD? (/dev/ttyp*) I see there are devices for ttyp0 - ttypv. Is it possible to increase this? And I have noticed that telnetd only uses ttyp0 to ttypf. Is it possible to change that? Also. Screen on FreeBSD uses network ttys :-(( Is it possible to make it use other devices? If not, what is the upper limit of network tty's (/dev/ttyp*) ? --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 10:59:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23962 for isp-outgoing; Wed, 18 Sep 1996 10:59:24 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA23945 for ; Wed, 18 Sep 1996 10:59:21 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id TAA25256 for ; Wed, 18 Sep 1996 19:57:15 +0200 Message-Id: <199609181757.TAA25256@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 19:06:44 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Denying expired users POP? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996 18:47:43 +1000 (EST), Daniel O'Callaghan wrote: >[ Words to the effect that he wanted popper to use the expire fields in ] >[ password file. ] > >Done! > >ftp://ftp.hilink.com.au/FreeBSD/contrib/ > >I extracted the relevant code from usr.bin/login/login.c > >Please test it before I announce. > >cheers, Thanks to Danny's patch the qpopper expiry problem is now solved for me. I've tested it briefly, and it works. Thanks for all help on the subject from all of you! --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 11:02:50 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25550 for isp-outgoing; Wed, 18 Sep 1996 11:02:50 -0700 (PDT) Received: from tchnet.tchnet.com (tchnet.tchnet.com [198.109.196.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA25525 for ; Wed, 18 Sep 1996 11:02:46 -0700 (PDT) Received: (from rnet@localhost) by tchnet.tchnet.com (8.6.12/8.6.9) id OAA12879; Wed, 18 Sep 1996 14:03:05 -0400 Date: Wed, 18 Sep 1996 14:03:05 -0400 (EDT) From: "R. A. Nethercott" To: isp@freebsd.com Subject: Dual Processer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a dual Pentium processer machine that is running FreeBSD on it. I was just wondering if there is a patch out there so that I may utilize my dual Pentium configuration? Any help would be appreciated! Roy R A Nethercott System Administrator Technet, Inc rnet@tchnet.com From owner-freebsd-isp Wed Sep 18 11:06:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA27018 for isp-outgoing; Wed, 18 Sep 1996 11:06:19 -0700 (PDT) Received: from ns.cityscape.co.uk (ns.cityscape.co.uk [194.159.0.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA26942; Wed, 18 Sep 1996 11:06:06 -0700 (PDT) Received: from ns.cityscape.co.uk (ns.cityscape.co.uk [194.159.0.5]) by ns.cityscape.co.uk (8.6.4/8.6.4) with SMTP id SAA06763; Wed, 18 Sep 1996 18:47:32 +0100 Date: Wed, 18 Sep 1996 18:47:32 +0100 (BST) From: Bernard Jauregui To: isp@FreeBSD.ORG, questions@FreeBSD.ORG cc: douglas@cityscape.co.uk, Bernard Jauregui Subject: Postgres95 under FreeBSD 2.1.5R Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dear All Has anyone managed to run Postgres 1.05 under FreeBSD 2.1.5R. I'm helping a colleague write an ISP management suite running under FreeBSD (2.1.5R). Running under SunOS we had no problems using Postgres95 (1.05) as a backend to RADIUS, NIS and other user management functions. Compiling under FreeBSD comes up with a few more compiler warnings and a memory error at runtime : % postmaster -S IpcMemoryCreate: memKey=155356396 , size=760632 , permission=384IpcMemoryCreate: shmget(..., create, ...) failed: Invalid argument My guess is that we need another patch or library include. Any help appreciated. Bernard Jauregui CamNet - The Cambridge FreeNet bj@cam.net.uk From owner-freebsd-isp Wed Sep 18 11:30:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08951 for isp-outgoing; Wed, 18 Sep 1996 11:30:09 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA08904 for ; Wed, 18 Sep 1996 11:30:05 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id UAA25420 for ; Wed, 18 Sep 1996 20:27:59 +0200 Message-Id: <199609181827.UAA25420@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 19:37:28 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: UPS's supported by FreeBSD?? Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Does anyone have a clue what UPS'es or what UPS protocols that are supported by FreeBSD to do a controlled system shutdown whenever the power fails? Our news server just died because of a "spike", so we're thinking of getting a UPS for it :) --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 11:35:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11625 for isp-outgoing; Wed, 18 Sep 1996 11:35:24 -0700 (PDT) Received: from relay.mfa.com (MFA.COM [199.88.143.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA11508 for ; Wed, 18 Sep 1996 11:35:11 -0700 (PDT) Received: from stimpy.mfa.com ([192.168.1.10]) by relay.mfa.com via smtpd (for freefall.FreeBSD.ORG [204.216.27.18]) with SMTP; 18 Sep 1996 18:30:15 UT Received: from fifield-pc (fifield-pc.mfa.com) by stimpy.mfa.com with SMTP (1.37.109.16/16.2) id AA095411369; Wed, 18 Sep 1996 13:29:29 -0500 Message-Id: <3240417A.6B36@mfa.com> Date: Wed, 18 Sep 1996 13:37:46 -0500 From: "Daniel C. Fifield" Organization: McHugh Freeman X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: freebsd-isp@freebsd.org Subject: Silo Overflows? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Help Please, I have read through all the mail archives and tried to adjust my silo trigger down to 8 in sio.c. My server goes crazy and starts reporting silo overflows on all the serial ports on the BOCA 16. I am running 2.1.0 on a P90 with 48MB of ram. I did not see this problem until I switched from user ppp to the kernel ppp. Could this have anything to do with it? I also installed the modified getty to allow direct PAP authentication. Please help! Sincerely, Daniel C. Fifield From owner-freebsd-isp Wed Sep 18 11:41:47 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15095 for isp-outgoing; Wed, 18 Sep 1996 11:41:47 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15061 for ; Wed, 18 Sep 1996 11:41:44 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id UAA25478 for ; Wed, 18 Sep 1996 20:39:38 +0200 Message-Id: <199609181839.UAA25478@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 19:49:06 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: News server... Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk We was forced to reinstall our news server and I just wonder if anyone have any comments/suggestions to our current setup: Machine: P/133 64MB ram (Soon to be 128 MB) 4x Quantum Empire (2GB) 1x Quantum Fireball (500MB) Disk configuration 1x Quantum Empire - root device 3x Quantum Empire striped with ccd (Ileave: 16 = 8kb) for /var/spool/news 1x Quantum Fireball - /usr/lib/news (News configuration to avoid excessive I/O on the root dev.) The disks are connected to two Adaptec 7850 controllers. the news related disks alone on the second adaptec and the root dev on the first. Inn is configured with the default setup from the FreeBSD ports collection (Except for pathnames etc etc). Does this look like a reasonable setup? This news server does not handle any feeds (Except for the incoming feed from our provider). Only client access. (For now). --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 11:57:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23228 for isp-outgoing; Wed, 18 Sep 1996 11:57:13 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA23212 for ; Wed, 18 Sep 1996 11:57:10 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA09544; Wed, 18 Sep 1996 13:56:00 -0500 From: Joe Greco Message-Id: <199609181856.NAA09544@brasil.moneng.mei.com> Subject: Re: NNTP Feeder somewhere? To: ser@hon.hn (Samuel E. Romero) Date: Wed, 18 Sep 1996 13:55:59 -0500 (CDT) Cc: freebsd-isp@freebsd.org In-Reply-To: <323F8984.5166@hon.hn> from "Samuel E. Romero" at Sep 18, 96 11:32:52 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Where can I get an NNTP feeder?. Somebody knows where can I get this > type of service. I don't have news access right now (nobody has one > here in my country), and I want to setup a news server here. > Somebody knows?. Usenet typically works on a "mutually beneficial" paradigm. If I feed you, you feed me too, and hopefully both parties benefit from the exchange. Of course, this assumes that you exchange news with multiple peers. If that isn't the case, usually you have to pay someone to feed you news. ... JG From owner-freebsd-isp Wed Sep 18 12:06:01 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27557 for isp-outgoing; Wed, 18 Sep 1996 12:06:01 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA27534 for ; Wed, 18 Sep 1996 12:05:58 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id VAA25671 for ; Wed, 18 Sep 1996 21:03:52 +0200 Message-Id: <199609181903.VAA25671@login.bigblue.no> From: "Frode Nordahl" To: "isp@FreeBSD.org" Date: Wed, 18 Sep 96 20:13:20 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: IP Aliasing... Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I wonder if there is any way to see what IP aliases is configured for one machine? I see that ifconfig does not list this... --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 12:10:34 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00132 for isp-outgoing; Wed, 18 Sep 1996 12:10:34 -0700 (PDT) Received: from ns.cityscape.co.uk (ns.cityscape.co.uk [194.159.0.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA29940; Wed, 18 Sep 1996 12:10:25 -0700 (PDT) Received: from ns.cityscape.co.uk (ns.cityscape.co.uk [194.159.0.5]) by ns.cityscape.co.uk (8.6.4/8.6.4) with SMTP id UAA12818; Wed, 18 Sep 1996 20:10:34 +0100 Date: Wed, 18 Sep 1996 20:10:33 +0100 (BST) From: Bernard Jauregui To: isp@FreeBSD.ORG, questions@FreeBSD.ORG cc: Bernard Jauregui , Douglas Reay Subject: Re: Postgres95 under FreeBSD 2.1.5R Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks to everyone who pointed out that Postgres95 required the SYS V messaging and memory options set in the kernel. Unfortunately I had already though of that and they were present. Any more suggestions, or do I need to move to FreeBSD 2.2 as Glen Foster suggests ? Hint : This would be a major pain :-) Bernard From owner-freebsd-isp Wed Sep 18 12:48:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19908 for isp-outgoing; Wed, 18 Sep 1996 12:48:26 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19883 for ; Wed, 18 Sep 1996 12:48:24 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA09709; Wed, 18 Sep 1996 14:47:20 -0500 From: Joe Greco Message-Id: <199609181947.OAA09709@brasil.moneng.mei.com> Subject: Re: News server... To: froden@bigblue.no Date: Wed, 18 Sep 1996 14:47:20 -0500 (CDT) Cc: isp@FreeBSD.org In-Reply-To: <199609181839.UAA25478@login.bigblue.no> from "Frode Nordahl" at Sep 18, 96 07:49:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > We was forced to reinstall our news server and I just wonder if anyone have any comments/suggestions to our > current setup: > > Machine: > P/133 > 64MB ram (Soon to be 128 MB) More RAM, definitely. :-) > 4x Quantum Empire (2GB) > 1x Quantum Fireball (500MB) > > Disk configuration > 1x Quantum Empire - root device > 3x Quantum Empire striped with ccd (Ileave: 16 = 8kb) for /var/spool/news Too small an interleave. You want each drive to be able to complete a transaction on its own... and I am not talking about a single read, I mean (minimally) the terminal directory traversal and file read for the article in question. You do not want two or three drives participating in this operation. Search the mailing list archives, I am tired of explaining it. I use an interleave size equal to the number of blocks in a _CYLINDER_GROUP_. That is a BIG number. > 1x Quantum Fireball - /usr/lib/news (News configuration to avoid excessive I/O on the root dev.) Good idea. > The disks are connected to two Adaptec 7850 controllers. the news related disks alone on the second > adaptec and the root dev on the first. So you have one "underutilized" SCSI bus... the first one. Spread the disks out between the busses. > Inn is configured with the default setup from the FreeBSD ports collection (Except for pathnames etc etc). Don't know what that is because I've never done it. Sorry... > Does this look like a reasonable setup? This news server does not handle any feeds (Except for the incoming > feed from our provider). Only client access. (For now). How many simultaneous clients do you expect to be able to handle? How long do you keep news? Etc. ... JG From owner-freebsd-isp Wed Sep 18 12:48:40 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA20049 for isp-outgoing; Wed, 18 Sep 1996 12:48:40 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19958; Wed, 18 Sep 1996 12:48:31 -0700 (PDT) Received: from localhost (petzi@localhost) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id VAA14169; Wed, 18 Sep 1996 21:48:00 +0200 (MET DST) Date: Wed, 18 Sep 1996 21:48:00 +0200 (MET DST) From: Michael Beckmann To: "S(pork)" cc: isp@FreeBSD.org, hardware@FreeBSD.org Subject: Re: INN history file and disk I/O In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi there, > We'll be building a new news server here rather soon, and I was wondering > if anyone in on this discussion has any preferences in motherboards and > dealers... Our usual supplier is having some trouble coming up with a > recommendation on a RAM-packed motherboard... I have made very good experiences with the Gigabyte 586 HX mainboard. I have built several machines with it. It has 6 SIMM slots. I have only used it with 32 MB SIMMs so far, and it works very well. According to a test in a very reputable German computer magazine, it performs slightly better than the Asus counterpart, which has only 4 SIMM slots. The test also says that this board is among the few that boot with 64 MB SIMMs installed. If you equip the board with a 16 kbyte Tag RAM it will extend the L2 cacheable area to 512 MB. The cacheable area becomes important when you have that much RAM. Almost all motherboards do not L2 cache more than 64 megabytes. I think that 6 x 64 MB = 384 MB will make a good newsserver :-) With a P 166 or P 200 it outperforms e.g. a SPARC 20 easily. Another option is the Asus Double Pentium board, which has 8 SIMM slots. The second Pentium is not supported by FreeBSD (and you don't need it for a news server), but I would still consider it because of the 8 SIMM slots and the good Asus support and quality. Hope this helps. Don't buy crap. Michael From owner-freebsd-isp Wed Sep 18 13:23:39 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07276 for isp-outgoing; Wed, 18 Sep 1996 13:23:39 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07206; Wed, 18 Sep 1996 13:23:27 -0700 (PDT) Received: (from abial@localhost) by korin.warman.org.pl (8.7.5/8.7.3) id WAA23789; Wed, 18 Sep 1996 22:28:46 +0200 (MET DST) Date: Wed, 18 Sep 1996 22:28:46 +0200 (MET DST) From: Andrzej Bialecki To: Bernard Jauregui cc: isp@freebsd.org, questions@freebsd.org, Bernard Jauregui , Douglas Reay Subject: Re: Postgres95 under FreeBSD 2.1.5R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Bernard Jauregui wrote: > > Thanks to everyone who pointed out that Postgres95 required the SYS V > messaging and memory options set in the kernel. > > Unfortunately I had already though of that and they were present. This is most interesting thing... I compiled Postgres95 1.05 on FreeBSD 2.1.5 with virtually *no errors*, and now it's up and running (let me see... yes, it still runs). Maybe you forgot to install newly compiled kernel? Oh, yes, and as I see your postmaster tried to get a big chunk of shared memory and got choked. I'd suggest trying to increase maximum size of shared memory (it's an option during compile - I forgot the name). > > Any more suggestions, or do I need to move to FreeBSD 2.2 as Glen Foster > suggests ? Hint : This would be a major pain :-) Don't do this (especially if it hurts ;-). I tell you, it can be done - we may further elaborate on configurations/options/whatnot, but eventually it WILL work. Andy, +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-isp Wed Sep 18 13:25:54 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08193 for isp-outgoing; Wed, 18 Sep 1996 13:25:54 -0700 (PDT) Received: from hon.hn ([206.48.105.210]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08123 for ; Wed, 18 Sep 1996 13:25:45 -0700 (PDT) Received: from hon.hn.hon.hn (si1.hon.hn [206.48.253.70]) by hon.hn (8.7.5/8.7.3) with SMTP id OAA29081 for ; Wed, 18 Sep 1996 14:25:13 -0600 (CST) Message-ID: <323FB24C.1DC6@hon.hn> Date: Wed, 18 Sep 1996 14:26:52 +0600 From: "Samuel E. Romero" Organization: Soluciones Internacionales X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: FreeBSD ISP Mailing List Subject: Re: NNTP Feeder somewhere? References: <199609181856.NAA09544@brasil.moneng.mei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Joe Greco wrote: > > Usenet typically works on a "mutually beneficial" paradigm. > > If I feed you, you feed me too, and hopefully both parties benefit from > the exchange. Of course, this assumes that you exchange news with multiple > peers. Ok, where can I contact them?. Is there a mailing list or something like that?. > If that isn't the case, usually you have to pay someone to feed you news. > > ... JG -- Samuel E. Romero Soluciones Internacionales ser@hon.hn Honduras On Net Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D -- From owner-freebsd-isp Wed Sep 18 13:43:34 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15716 for isp-outgoing; Wed, 18 Sep 1996 13:43:34 -0700 (PDT) Received: from boris.clintondale.com (boris.clintondale.com [206.88.120.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA15685 for ; Wed, 18 Sep 1996 13:43:29 -0700 (PDT) Received: from localhost (matt@localhost) by boris.clintondale.com (8.7.5/8.7.3) with SMTP id QAA23702 for ; Wed, 18 Sep 1996 16:42:51 -0400 (EDT) Date: Wed, 18 Sep 1996 16:42:51 -0400 (EDT) From: Matt Hamilton To: freebsd-isp@freebsd.org Subject: Backup strategies Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello All, I currently use Amanda to do backups of our system every night. Amanda calls dump and dump uses the Modified Tower of Hanoi algorhythm for backups. I do not know anything really about this method and I need to know more about it. If there is a FAQ on Backups in general and the Tower of Hanoi please let me know... We have just moved a financial system over to our FreeBSD machine and we need to back it up. However we need to be able to restore from the backups, not just the latest material, but also (if something REALLY goes wrong) restore from a couple of days or weeks ago. Is this possible using the Tower of Hanoi? I know I could get Amanda to do a level 0 dump everynight... but want to try and avoid that if possible. If so how would I implement a weekly cycle in which we have tapes Mon, Tue, Wen, Thu, Fri in which a full backup is done every Friday and then taken offsite and new tape replaces it? Hmmm.... I have just read back what I have typed and noticed that it is very confusing, but I can't word it any better, sorry :) Can anyone help me out here? Matt From owner-freebsd-isp Wed Sep 18 14:06:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA24139 for isp-outgoing; Wed, 18 Sep 1996 14:06:24 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA24059; Wed, 18 Sep 1996 14:06:08 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id OAA04861; Wed, 18 Sep 1996 14:04:27 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609182104.OAA04861@GndRsh.aac.dev.com> Subject: Re: INN history file and disk I/O In-Reply-To: from Michael Beckmann at "Sep 18, 96 09:48:00 pm" To: petzi@zit.th-darmstadt.de (Michael Beckmann) Date: Wed, 18 Sep 1996 14:04:26 -0700 (PDT) Cc: spork@super-g.com, isp@freebsd.org, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi there, > > > We'll be building a new news server here rather soon, and I was wondering > > if anyone in on this discussion has any preferences in motherboards and > > dealers... Our usual supplier is having some trouble coming up with a > > recommendation on a RAM-packed motherboard... > > I have made very good experiences with the Gigabyte 586 HX mainboard. I > have built several machines with it. It has 6 SIMM slots. I have only used Buyer beware, Gigabyte is playing games with the specifications and register usage of the Triton-I and Triton-II chipsets to get away with these 6 SIMM slots. These chip sets have 8 programmable DRAM row size registers, each _SIDE_ of a SIMM requires one of them to be programmed, you can _ONLY_ run 4 double sided simms with these chip sets. Gigabyte dirty little move is to _ONLY_ allow single sided SIMMS in 2 of the sockets, thus the max memory is REALLY 4 * 32MB + 2 * 16MB == 160MB for Triton-I and 64MB * 6 == 384MB for Triton-II (64MB simms are single row simms if they use 64MB technology chips on them). > it with 32 MB SIMMs so far, and it works very well. According to a test in > a very reputable German computer magazine, it performs slightly better > than the Asus counterpart, which has only 4 SIMM slots. The test also says > that this board is among the few that boot with 64 MB SIMMs installed. > If you equip the board with a 16 kbyte Tag RAM it will extend the > L2 cacheable area to 512 MB. The cacheable area becomes important when you It's not 16kbyte of tag you need, it is 11 bit wide tags you need, see the Intel 439HX databooks. ASUS also supports this, but it is a little trickier to do and I am trying to accertain some optional ways of doing it. > have that much RAM. Almost all motherboards do not L2 cache more than 64 > megabytes. I think that 6 x 64 MB = 384 MB will make a good newsserver :-) > With a P 166 or P 200 it outperforms e.g. a SPARC 20 easily. > > Another option is the Asus Double Pentium board, which has 8 SIMM slots. > The second Pentium is not supported by FreeBSD (and you don't need it for > a news server), but I would still consider it because of the 8 SIMM slots > and the good Asus support and quality. My experience with the PCI/E-P55T2P4D is that it won't reliably run more than 6 simms unless they happen to be single sided 12 chip or less simm modules. :-(. > > Hope this helps. Don't buy crap. And as a final note, AAC has disqualified Gigabyte as a MB supplier 4 times. Every time a new board comes out from them my local distributor swears it is the best thing since sliced bread, so I bring in a couple of them for my 2 week eval process... welll... Gigabyte has never made it to my qualified parts list :-( Oh, and of course YMMV... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Wed Sep 18 14:14:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA26853 for isp-outgoing; Wed, 18 Sep 1996 14:14:35 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA26824 for ; Wed, 18 Sep 1996 14:14:29 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id QAA09849; Wed, 18 Sep 1996 16:13:20 -0500 From: Joe Greco Message-Id: <199609182113.QAA09849@brasil.moneng.mei.com> Subject: Re: NNTP Feeder somewhere? To: ser@hon.hn (Samuel E. Romero) Date: Wed, 18 Sep 1996 16:13:20 -0500 (CDT) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <323FB24C.1DC6@hon.hn> from "Samuel E. Romero" at Sep 18, 96 02:26:52 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Joe Greco wrote: > > > > Usenet typically works on a "mutually beneficial" paradigm. > > > > If I feed you, you feed me too, and hopefully both parties benefit from > > the exchange. Of course, this assumes that you exchange news with multiple > > peers. > > Ok, where can I contact them?. Is there a mailing list or something > like that?. You can beg and grovel on news.software.nntp... :-) It is not pretty but it works. ... JG From owner-freebsd-isp Wed Sep 18 14:16:56 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA27612 for isp-outgoing; Wed, 18 Sep 1996 14:16:56 -0700 (PDT) Received: from garion.hq.ferg.com (pm3-09.wmbg.widomaker.com [204.17.220.169]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA27581 for ; Wed, 18 Sep 1996 14:16:50 -0700 (PDT) Received: from garion.hq.ferg.com (localhost.hq.ferg.com [127.0.0.1]) by garion.hq.ferg.com (8.7.5/8.6.12) with SMTP id RAA20503; Wed, 18 Sep 1996 17:16:06 -0400 (EDT) Date: Wed, 18 Sep 1996 17:16:03 -0400 (EDT) From: Branson Matheson X-Sender: branson@garion.hq.ferg.com To: Matt Hamilton cc: freebsd-isp@FreeBSD.org Subject: Re: Backup strategies In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Matt Hamilton wrote: > However we need to be able to restore from the > backups, not just the latest material, but also (if something REALLY goes > wrong) restore from a couple of days or weeks ago. Is this possible using > the Tower of Hanoi? I know I could get Amanda to do a level 0 dump > everynight... but want to try and avoid that if possible. > If so how would I implement a weekly cycle in which we have tapes > Mon, Tue, Wen, Thu, Fri in which a full backup is done every Friday and > then taken offsite and new tape replaces it? Hmmm.. mabey you don't understand how amanda works... it will do a complete level 0 once per dumpcycle and the rest of the time it will do incrementals... that means that you _can_ restore using the full backups and the incrimentals. And if you need to go back further.. just keep more tapes in rotation.. I have 60 tapes here with a 5 day backup cycle so that means I can go 12 weeks and restore a file. > Can anyone help me out here? Hope this helps. -branson ============================================================================= Branson Matheson | Ferguson Enterprises | If Pete and Repeat were System Administrator | W: (804) 874-7795 | sittin on a fence and Pete Unix, Perl, WWW | branson@widomaker.com | fell off, who is left? From owner-freebsd-isp Wed Sep 18 14:20:21 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28672 for isp-outgoing; Wed, 18 Sep 1996 14:20:21 -0700 (PDT) Received: from boris.clintondale.com (boris.clintondale.com [206.88.120.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28636 for ; Wed, 18 Sep 1996 14:20:15 -0700 (PDT) Received: from localhost (matt@localhost) by boris.clintondale.com (8.7.5/8.7.3) with SMTP id RAA24036; Wed, 18 Sep 1996 17:19:40 -0400 (EDT) Date: Wed, 18 Sep 1996 17:19:40 -0400 (EDT) From: Matt Hamilton To: Branson Matheson cc: freebsd-isp@FreeBSD.org Subject: Re: Backup strategies In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Branson Matheson wrote: > Hmmm.. mabey you don't understand how amanda works... it will do a > complete level 0 once per dumpcycle and the rest of the time it will > do incrementals... that means that you _can_ restore using the full So does it do incrementals from the last level 0 dump or from the last incremental ie. if I do a level 0 on Monday and incrementals tue, wed, thu, fri and it crashes friday do I need tapes Monday and Friday or tapes Mon, tue, wed,thu, fri? -Matt From owner-freebsd-isp Wed Sep 18 15:09:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21603 for isp-outgoing; Wed, 18 Sep 1996 15:09:19 -0700 (PDT) Received: from hon.hn ([206.48.105.210]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA21548 for ; Wed, 18 Sep 1996 15:09:12 -0700 (PDT) Received: from hon.hn.hon.hn (si1.hon.hn [206.48.253.70]) by hon.hn (8.7.5/8.7.3) with SMTP id QAA00897; Wed, 18 Sep 1996 16:07:57 -0600 (CST) Message-ID: <323FCA61.BD2@hon.hn> Date: Wed, 18 Sep 1996 16:09:37 +0600 From: "Samuel E. Romero" Organization: Soluciones Internacionales X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: "Daniel C. Fifield" CC: FreeBSD ISP Mailing List Subject: Re: [Fwd: Silo Overflows?] References: <324041CA.4806@mfa.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Daniel C. Fifield wrote: > > I have read through all the mail archives and tried to adjust my silo > trigger down to 8 in sio.c. My server goes crazy and starts reporting > silo overflows on all the serial ports on the BOCA 16. > > I am running 2.1.0 on a P90 with 48MB of ram. I did not see this problem Why don't you switch to 2.1.5R?. I'm using this card/box in my system and doesn't have that problem with modems running @28.8Kbps. > until I switched from user ppp to the kernel ppp. Could this have > anything to do with it? I also installed the modified getty to allow > direct PAP authentication. Can your users connect to the system, even with the silo overflows or nothing gets transfered to the system because of that?. -- Samuel E. Romero Soluciones Internacionales ser@hon.hn Honduras On Net Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D -- From owner-freebsd-isp Wed Sep 18 15:12:20 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22808 for isp-outgoing; Wed, 18 Sep 1996 15:12:20 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22750; Wed, 18 Sep 1996 15:12:11 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA09657; Wed, 18 Sep 1996 18:12:07 -0400 (EDT) Date: Wed, 18 Sep 1996 18:12:07 -0400 (EDT) From: Brian Tao Reply-To: FREEBSD-SCSI-L To: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Streamlogic RAID array benchmarks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I now have a P166 equipped with an Adaptec AHA-2940UW controller and a 3x4GB RAID 5 subsystem from Streamlogic (kindly lent to us by Tenex Data Systems here in Toronto). The drive comes preformatted and preconfigured with two data drives and one parity drive. It has two 68-pin wide connectors on the back and a nifty little pop-up LCD panel on the front to control various aspects of the RAID. There is also a 9-pin male serial port on the back if you want to hook up a VT-100 terminal to it. The RAID worked right out of the box. I have a narrow 4GB Barracuda plugged into the 50-pin connector on the Adaptec, and the RAID on the external 68-pin connector. The RAID drives themselves are connected via a 10MB/s narrow SCSI bus to the Streamlogic RAID controller, which then interfaces with the host via a F/W bus. It has four narrow busses, allowing for up to 28 drives per RAID controller. The GENERIC kernel recognizes this setup: FreeBSD 2.2-960801-SNAP #0: Sat Aug 3 15:18:25 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC Calibrating clock(s) relative to mc146818A clock... i586 clock: 133663775 Hz, i8254 clock: 1193428 Hz CPU: Pentium (133.63-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62947328 (61472K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 pci0:7:1: Intel Corporation, device=0x7010, class=storage (ide) [no driver assigned] ahc0 rev 0 int a irq 11 on pci0:8 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST15150N 0022" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) (ahc0:2:0): "MICROP LTX 011000 7t38" type 0 fixed SCSI 2 sd1(ahc0:2:0): Direct-Access 8189MB (16772017 512 byte sectors) [...] All the usual tools under FreeBSD treat the RAID as a single drive. The default stripe size is 8K, RAID 5 (striping with parity). This can be changed via the LCD keypad on the unit itself, or with a VT-100 interface via the serial port. The problem I have is that it isn't particularly fast on the raw throughput tests. Granted, there is some overhead in calculating the parity, but I would expect it to go at least as fast as the single 4GB drive. Results from various benchmarks are included below. The tests were conducted on newly newfs'd filesystems. sd0 is the single 4GB drive and sd1 is the RAID. A unit from CMD should be arriving next week, so I'll have another product to benchmark. Comments welcome, and please note the Reply-To. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" >>>>> Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0s1d 2847603 4 2619791 0% /single /dev/sd1s1a 8135644 10 7484783 0% /raid Bonnie 1.0 output is shown here. The single drive easily outpaces the RAID for both linear and random accesses. -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU raid 100 1354 25.1 1308 4.5 1056 7.3 3059 55.9 3190 11.5 139.0 5.1 single 100 3506 66.8 3429 12.0 1848 12.5 5367 99.1 6462 25.6 202.5 7.1 Iozone 2.01 from the packages collection showed a dramatic difference in favour of the non-RAID drive. It was over twice as fast as the RAID both in block reads and block writes. I'm a little suspicious of the read numbers for the single drive... I thought the ST15150N's maxed out at around 6.5MB/s (at least on narrow controllers)? I'm seeing over 8MB/s on a single drive. Does the 2940UW make that much difference even on narrow drives? The test file size was 128MB. Size is the data block size, Write and Read are in bytes per second. -------- RAID -------- ------- SINGLE ------- Size Write Read Size Write Read 256 1334877 3420921 256 3551027 7683304 512 1398101 3477002 512 3312101 8134407 1024 1410614 3519022 1024 3372569 8458822 2048 1413748 3575415 2048 3369923 8646134 4096 1414563 3585862 4096 3360694 8729608 8192 1421233 3568730 8192 3356754 8769713 16384 1419941 3554700 16384 3374556 8347847 32768 1419354 3469979 32768 3375219 8751843 65536 1420176 3408028 65536 3367281 8774192 I then ran a simple test that should take advantage of the 4MB write cache on the RAID controller. Create 10000 files in an empty directory, then retouch their inodes, then delete them all. I performed this on synchronously and asynchronously mounted filesystems on both types of drives. The RAID drive is as fast as an async-mounted single drive filesystem. Times are in min:sec. ----- RAID ----- ---- SINGLE ---- Sync Async Sync Async touch 1:42.24 1:23.95 3:57.62 1:27.80 retouch 0:12.37 0:03.24 1:23.72 0:03.26 remove 0:17.58 0:08.55 1:25.80 0:10.19 Synchronous (RAID): # time touch `jot 10000 1` 0.4u 84.6s 1:42.24 83.2% 10+170k 143+20315io 0pf+0w # time touch `jot 10000 1` 0.3u 3.6s 0:12.37 32.8% 22+193k 0+10000io 0pf+0w # time rm * 0.4u 10.0s 0:17.58 59.6% 184+252k 0+10000io 0pf+0w Asynchronous (RAID): # time touch `jot 10000 1` 0.4u 83.3s 1:23.95 99.7% 10+170k 159+315io 0pf+0w # time touch `jot 10000 1` 0.3u 3.2s 0:03.24 110.8% 22+191k 0+0io 0pf+0w # time rm * 0.2u 9.5s 0:08.55 115.2% 186+253k 0+305io 0pf+0w Synchronous (single): # time touch `jot 10000 1` 0.4u 86.9s 3:57.62 36.7% 10+170k 162+20314io 0pf+0w # time touch `jot 10000 1` 0.4u 3.8s 1:23.72 5.1% 21+191k 0+10000io 0pf+0w # time rm * 0.4u 10.4s 1:25.80 12.6% 186+251k 0+10000io 0pf+0w Asynchronous (single): # time touch `jot 10000 1` 0.4u 82.3s 1:27.80 94.3% 10+170k 159+315io 0pf+0w # time touch `jot 10000 1` 0.3u 3.2s 0:03.26 111.0% 22+191k 0+0io 0pf+0w # time rm * 0.4u 9.4s 0:10.19 96.2% 187+254k 0+305io 0pf+0w The last benchmark was to untar the contents of the /usr filesystem (15330 files, 78469120 bytes). The tar file was located on the same filesystem to which it was untarred. As in the previous benchmark, the RAID is much faster with numerous small file operations. RAID: # time tar xf usr-test.tar 1.7u 20.4s 5:02.25 7.3% 285+329k 2472+51582io 0pf+0w # time rm -rf usr 0.5u 11.3s 2:57.98 6.6% 163+569k 2132+29479io 0pf+0w Single: # time tar xf usr-test.tar 1.6u 18.0s 8:49.25 3.7% 287+329k 1995+49819io 10pf+0w # time rm -rf usr 0.5u 9.1s 4:44.14 3.4% 164+569k 2462+29479io 1pf+0w <<<<< From owner-freebsd-isp Wed Sep 18 15:27:41 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29244 for isp-outgoing; Wed, 18 Sep 1996 15:27:41 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA29222 for ; Wed, 18 Sep 1996 15:27:36 -0700 (PDT) Received: from i-gw.dalsys.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v3V5G-0008uYC; Wed, 18 Sep 96 15:27 PDT Received: (from smap@localhost) by i-gw.dalsys.com (8.6.9/8.6.9) id RAA09302; Wed, 18 Sep 1996 17:23:15 -0500 Received: from future.dsc.dalsys.com(199.170.161.3) by i-gw.dalsys.com via smap (V1.3) id sma009300; Wed Sep 18 17:23:12 1996 Received: from richards.dsc.dalsys.com by future.dsc.dalsys.com (AIX 3.2/UCB 5.64/8.6.12) id AA93148; Wed, 18 Sep 1996 17:28:01 -0500 Message-Id: <32409340.7F49@herald.net> Date: Wed, 18 Sep 1996 17:26:40 -0700 From: Richard Stanford Reply-To: richards@herald.net Organization: Herald Communications X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: "Rodney W. Grimes" Cc: isp@freebsd.org Subject: Re: INN history file and disk I/O References: <199609182104.OAA04861@GndRsh.aac.dev.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes wrote: > > .... Every time a new board comes out from them my local distributor > swears it is the best thing since sliced bread, so I bring in a couple > of them for my 2 week eval process .... Do you have any comments about the Tyan S1562 (?) motherboards? They seem nicely laid out, 8 SIMM slots (only used 32MB simms so far)... I just have one system with it now, and like it, and am trying to standardize all my systems, so would appreciate any feedback (positive or negative) that you have about this board. > Accurate Automation Company Reliable computers for FreeBSD Do you have any information available? Or a web site? -Richard From owner-freebsd-isp Wed Sep 18 15:30:29 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00254 for isp-outgoing; Wed, 18 Sep 1996 15:30:29 -0700 (PDT) Received: from homer.alpha.net (homer.alpha.net [156.46.10.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00218 for ; Wed, 18 Sep 1996 15:30:22 -0700 (PDT) Received: from relay (relay.mfa.com [199.88.143.1]) by homer.alpha.net (8.7.5/8.7.3) with SMTP id RAA24410 for ; Wed, 18 Sep 1996 17:28:47 -0500 (CDT) Received: from stimpy.mfa.com by relay (5.x/SMI-SVR4) id AA00305; Wed, 18 Sep 1996 17:25:13 -0500 Received: from localhost by stimpy.mfa.com with SMTP (1.37.109.16/16.2) id AA139454453; Wed, 18 Sep 1996 17:07:33 -0500 Date: Wed, 18 Sep 1996 17:07:32 -0500 (CDT) From: Dan Fifield To: "Samuel E. Romero" Cc: FreeBSD ISP Mailing List Subject: Re: [Fwd: Silo Overflows?] In-Reply-To: <323FCA61.BD2@hon.hn> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Samuel E. Romero wrote: > Daniel C. Fifield wrote: > > > > I have read through all the mail archives and tried to adjust my silo > > trigger down to 8 in sio.c. My server goes crazy and starts reporting > > silo overflows on all the serial ports on the BOCA 16. > > > > I am running 2.1.0 on a P90 with 48MB of ram. I did not see this problem > > Why don't you switch to 2.1.5R?. I'm using this card/box in my system > and doesn't have that problem with modems running @28.8Kbps. I was not having this problem until I made the changes indicated below, so I am not sure upgrading will fix the problem. Tonight I am going to attempt to switch back to user ppp and see if that helps. > > > until I switched from user ppp to the kernel ppp. Could this have > > anything to do with it? I also installed the modified getty to allow > > direct PAP authentication. > > Can your users connect to the system, even with the silo overflows or > nothing gets transfered to the system because of that?. No, It stops all serial line activity on the boca box! > > -- > Samuel E. Romero Soluciones Internacionales > ser@hon.hn Honduras On Net > Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. > PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D > -- > From owner-freebsd-isp Wed Sep 18 15:31:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00603 for isp-outgoing; Wed, 18 Sep 1996 15:31:37 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00572; Wed, 18 Sep 1996 15:31:31 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id RAA01314; Wed, 18 Sep 1996 17:31:29 -0500 (EST) From: "John S. Dyson" Message-Id: <199609182231.RAA01314@dyson.iquest.net> Subject: Re: Streamlogic RAID array benchmarks To: freebsd-scsi@freebsd.org Date: Wed, 18 Sep 1996 17:31:29 -0500 (EST) Cc: freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: from "Brian Tao" at Sep 18, 96 06:12:07 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Iozone 2.01 from the packages collection showed a dramatic > difference in favour of the non-RAID drive. It was over twice as fast > as the RAID both in block reads and block writes. I'm a little > suspicious of the read numbers for the single drive... I thought the > ST15150N's maxed out at around 6.5MB/s (at least on narrow > controllers)? I'm seeing over 8MB/s on a single drive. Does the > 2940UW make that much difference even on narrow drives? The test file > size was 128MB. Size is the data block size, Write and Read are in > bytes per second. > If you are running -current (I forgot to check), and since you have 64MBytes, the buffer cache will help even though it is overrun. The buffer cache policy is NOT pure LRU, and you will see the effects of it on a 64MByte system even for a 100MByte benchmark. John From owner-freebsd-isp Wed Sep 18 15:43:07 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04566 for isp-outgoing; Wed, 18 Sep 1996 15:43:07 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA04545 for ; Wed, 18 Sep 1996 15:43:04 -0700 (PDT) Received: from hon.hn ([206.48.105.210]) by mail.crl.com with SMTP id AA00779 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 15:43:33 -0700 Received: from hon.hn.hon.hn (si1.hon.hn [206.48.253.70]) by hon.hn (8.7.5/8.7.3) with SMTP id QAA01124; Wed, 18 Sep 1996 16:39:48 -0600 (CST) Message-Id: <323FD1D8.66F3@hon.hn> Date: Wed, 18 Sep 1996 16:41:28 +0600 From: "Samuel E. Romero" Organization: Soluciones Internacionales X-Mailer: Mozilla 3.0 (Win95; I) Mime-Version: 1.0 To: Dan Fifield Cc: FreeBSD ISP Mailing List Subject: Re: [Fwd: Silo Overflows?] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dan Fifield wrote: > > Can your users connect to the system, even with the silo overflows or > > nothing gets transfered to the system because of that?. > > No, It stops all serial line activity on the boca box! Are you allowed to login using a terminal program. No a burst type talk (like the ppp or zmodem), just a terminal program with a standard login shell?. -- Samuel E. Romero Soluciones Internacionales ser@hon.hn Honduras On Net Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D -- From owner-freebsd-isp Wed Sep 18 15:56:28 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA09492 for isp-outgoing; Wed, 18 Sep 1996 15:56:28 -0700 (PDT) Received: from salsa.gv.ssi1.com (salsa.gv.ssi1.com [146.252.44.194]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA09463 for ; Wed, 18 Sep 1996 15:56:22 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.ssi1.com (8.7.5/8.7.3) id PAA10710; Wed, 18 Sep 1996 15:56:03 -0700 (PDT) From: Don Lewis Message-Id: <199609182256.PAA10710@salsa.gv.ssi1.com> Date: Wed, 18 Sep 1996 15:56:03 -0700 In-Reply-To: Matt Hamilton "Re: Backup strategies" (Sep 18, 5:19pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matt Hamilton , Branson Matheson Subject: Re: Backup strategies Cc: freebsd-isp@FreeBSD.ORG Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 18, 5:19pm, Matt Hamilton wrote: } Subject: Re: Backup strategies } On Wed, 18 Sep 1996, Branson Matheson wrote: } } > Hmmm.. mabey you don't understand how amanda works... it will do a } > complete level 0 once per dumpcycle and the rest of the time it will } > do incrementals... that means that you _can_ restore using the full } } So does it do incrementals from the last level 0 dump or from the last } incremental ie. if I do a level 0 on Monday and incrementals tue, wed, } thu, fri and it crashes friday do I need tapes Monday and Friday or tapes } Mon, tue, wed,thu, fri? It always does at least two backups in a row at each incremental level, and only goes on to the next incremental level if it determines that this will reduce the amount of data backed up by a "sufficient" amount. If a lot of data is modified each day, the backup schedule will look like: 0 1 1 2 2 3 3 If the disk is mostly static, the schedule will look like: 0 1 1 1 1 1 1 If you need to do a complete restore, run "amadmin config find host disk" which will tell you what backups are stored on each tape, then restore the latest level 0, and the latest incremental at each level that is newer than the level 0. --- Truck From owner-freebsd-isp Wed Sep 18 16:30:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26314 for isp-outgoing; Wed, 18 Sep 1996 16:30:48 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA26284 for ; Wed, 18 Sep 1996 16:30:44 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id BAA26857; Thu, 19 Sep 1996 01:28:35 +0200 Message-Id: <199609182328.BAA26857@login.bigblue.no> From: "Frode Nordahl" To: "Jeff Hupp" Cc: "isp@FreeBSD.org" Date: Thu, 19 Sep 96 00:38:01 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: IP Aliasing... Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996 15:03:30 -0500 (CDT), Jeff Hupp wrote: >Frode Nordahl bound electrons in the following form:: >: I wonder if there is any way to see what IP aliases is configured for one machine? I see that ifconfig does not list >: this... >: --------------------------------- >: Frode Nordahl >: > > But `netstat -i` does Aha! Thanks --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 16:31:28 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26748 for isp-outgoing; Wed, 18 Sep 1996 16:31:28 -0700 (PDT) Received: from login.bigblue.no (root@login.bigblue.no [194.19.68.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA26701 for ; Wed, 18 Sep 1996 16:31:24 -0700 (PDT) Received: from eagle.bigblue.no (froden@eagle.bigblue.no [194.19.68.13]) by login.bigblue.no (8.6.12/8.6.12) with SMTP id BAA26853; Thu, 19 Sep 1996 01:27:45 +0200 Message-Id: <199609182327.BAA26853@login.bigblue.no> From: "Frode Nordahl" To: "Joe Greco" Cc: "isp@FreeBSD.org" Date: Thu, 19 Sep 96 00:37:11 +0100 Reply-To: "Frode Nordahl" Priority: Normal X-Mailer: Frode Nordahl's Registered PMMail 1.52 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: News server... Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996 14:47:20 -0500 (CDT), Joe Greco wrote: >> Machine: >> P/133 >> 64MB ram (Soon to be 128 MB) > >More RAM, definitely. :-) Thought you would say that :-)) >> 4x Quantum Empire (2GB) >> 1x Quantum Fireball (500MB) >> >> Disk configuration >> 1x Quantum Empire - root device >> 3x Quantum Empire striped with ccd (Ileave: 16 = 8kb) for /var/spool/news > >Too small an interleave. You want each drive to be able to complete a >transaction on its own... and I am not talking about a single read, >I mean (minimally) the terminal directory traversal and file read for the >article in question. You do not want two or three drives participating >in this operation. Search the mailing list archives, I am tired of >explaining it. Ok... >I use an interleave size equal to the number of blocks in a >_CYLINDER_GROUP_. That is a BIG number. 32MB in this case. But that wil not help on performance, or would it? The optimum stripe size for RAID in hardware is 8kb... >> 1x Quantum Fireball - /usr/lib/news (News configuration to avoid excessive I/O on the root dev.) > >Good idea. Yeah.. Since this computer is going to do other stuff than news too, slowing down the root device with I/O is not a smart idea.. :) >> The disks are connected to two Adaptec 7850 controllers. the news related disks alone on the second >> adaptec and the root dev on the first. > >So you have one "underutilized" SCSI bus... the first one. Spread the disks >out between the busses. Ok... >> Does this look like a reasonable setup? This news server does not handle any feeds (Except for the incoming >> feed from our provider). Only client access. (For now). > >How many simultaneous clients do you expect to be able to handle? The maximum peak we expect (For now) is 16*3 clients (16 clients using 3 connections each). >How long do you keep news? We keep news for 5 days except for alt.binaries.* that we keep for 3 days maximum. Thanks for the info! --------------------------------- Frode Nordahl From owner-freebsd-isp Wed Sep 18 17:27:21 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA00127 for isp-outgoing; Wed, 18 Sep 1996 17:27:21 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA29987 for ; Wed, 18 Sep 1996 17:27:17 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id UAA21659; Wed, 18 Sep 1996 20:27:32 -0400 (EDT) Date: Wed, 18 Sep 1996 20:27:32 -0400 (EDT) From: "John T. Farmer" Message-Id: <199609190027.UAA21659@sabre.goldsword.com> To: dennis@etinc.com, nik@blueberry.co.uk Subject: Re: Routers - hardware received wisdom Cc: isp@freebsd.org, jfarmer@goldsword.com Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From owner-freebsd-isp@freefall.freebsd.org Wed Sep 18 12:04:46 1996 >Date: Wed, 18 Sep 1996 11:23:06 -0400 >X-Sender: dennis@etinc.com >X-Mailer: Windows Eudora Version 2.0.3 >Mime-Version: 1.0 >Content-Type: text/plain; charset="us-ascii" >To: Nik Clayton >From: dennis@etinc.com (Dennis) >Subject: Re: Routers - hardware received wisdom >Cc: isp@freebsd.org >Sender: owner-isp@freebsd.org >X-Loop: FreeBSD.org On 18 Sept 1996 dennis@etinc.com (Dennis) was quoted as saying: > Nik Clayton asjed: >>I'm going to be requiring two network routers, and since FreeBSD is more >>than capable of the task, I figured I'd go for the cheap 486 option. >> >>One of these routers will be sat between a 2Mb/s leased line and a 10Mb/s >>ethernet, and the other will be between 2 10Mb/s ethernets. >> >>As far as I can tell, FreeBSD 2.1.5, a PCI based 66MHz 486DX with 16MB RAM >>and 2 DC201040 PCI network cards should be sufficient. >> >>But can I drop it any lower than that? Would the boxes be fine with 8MB >>RAM? What about 33MHz machines? > >Its totally dependent on how much local ethernet traffic you have. If you will >be switching lots of traffic locally, you might be unhappy with a 33Mhz box. > >But at today's prices, what are you going to save? $10.? Its not worth it. >100Mhz processars are only $32 or so....you're spending more than that >thinking about it. > >Dennis I think that Dennis' comment & what Joe said in his note answered a question that I've had lurking in the back of my mind, "Just what is sufficient to run a FreeBSD T-1 capable router?" Granted that a no-name MB & 133Mhz 486 is running around $120, but I "happen to have" a 386/33, 8mb, 300mb disk sitting in the corner, with an ethernet card in it (isa only :^,). And I have a need for a T-1 capable box soon. Since it would be a fairly un-saturated T-1, I suspect that I will be able to get away with it for a while... Then the question becomes, how many 56/64k/128/256k frame relay links could a "little" box like that handle? (Must be the Scots in me, I hate to throw away anything!) Thanks John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-isp Wed Sep 18 18:26:55 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05860 for isp-outgoing; Wed, 18 Sep 1996 18:26:55 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA05748; Wed, 18 Sep 1996 18:26:44 -0700 (PDT) Received: from localhost (petzi@localhost) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with SMTP id DAA05761; Thu, 19 Sep 1996 03:26:10 +0200 (MET DST) Date: Thu, 19 Sep 1996 03:26:10 +0200 (MET DST) From: Michael Beckmann To: "Rodney W. Grimes" cc: spork@super-g.com, isp@freebsd.org, hardware@freebsd.org Subject: Re: INN history file and disk I/O In-Reply-To: <199609182104.OAA04861@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > Buyer beware, Gigabyte is playing games with the specifications and > register usage of the Triton-I and Triton-II chipsets to get away with > these 6 SIMM slots. These chip sets have 8 programmable DRAM row size > registers, each _SIDE_ of a SIMM requires one of them to be programmed, > you can _ONLY_ run 4 double sided simms with these chip sets. According to the HX manual you can use 6 SIMMs with 8 MB each in it, and these are double-sided. OTOH, who cares whether one can put 6 double sided SIMMs in it. There are so many valid combinations that I don't see this as a problem. The 586 ATE and HX mainboards I have used work just fine, I haven't seen one fail yet. That's just my personal experience. I'm not religious about mainboards, but I don't have the impression that Asus boards have significantly fewer bugs and problems. Gigabyte definitely belongs to the good equipment. > Gigabyte dirty little move is to _ONLY_ allow single sided SIMMS in 2 Wow, you make it sound as if Gigabyte were posessed by the wicked one ;-) Cheers, Michael From owner-freebsd-isp Wed Sep 18 18:28:54 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06869 for isp-outgoing; Wed, 18 Sep 1996 18:28:54 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA06847 for ; Wed, 18 Sep 1996 18:28:51 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id RAA11008; Wed, 18 Sep 1996 17:42:05 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id SAA06281; Wed, 18 Sep 1996 18:22:43 -0700 Date: Wed, 18 Sep 1996 18:22:41 -0700 (PDT) From: Michael Dillon To: inet-access@earth.com cc: iap@vma.cc.nd.edu, linuxisp@jeffnet.org, freebsd-isp@freebsd.org, os2-isp@dental.stat.com Subject: Cisco addresses SYN attacks? (fwd) Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >====================================================================== > > SAN JOSE, Calif.--(BUSINESS WIRE)--Sept. 17, 1996--Following >several reports of assaults on commercial Web sites and network >devices by anonymous hacker(s), Cisco Systems, Inc. is taking >several steps to inform its customers regarding how they might >address a potential threat to their networks. > Cisco called more than 40 leading Internet service providers >(ISPs) worldwide Monday to notify them of the possibility of isolated >electronic attacks targeted at Web sites and network devices >connected to the Internet. Cisco informed the ISPs of software >capabilities that could be implemented to resist attacks of the type >seen recently. > One problem occurs when a hacker floods a Web server or network >device with a huge volume of requests for connection. Because these >messages have false return addresses, however, the connections cannot >be established. The large volume of unresolved open connections >eventually overwhelms the server or network device and may cause the >server or network device to deny service. > In the past week, Cisco has collaborated with ISP customers to >understand the implications of potential attacks and share >information on how they can be resisted. At least one ISP has >installed a Cisco-recommended software implementation that >successfully restored network service after having been attacked. > The same implementation is currently in place to resist future >attacks on the same system. This implementation has been shared with >ISPs as a preventive measure. > "We view it as our responsibility to lead the industry in helping >customers resist malicious attacks," said Don Listwin, senior vice >president of Cisco IOS development and marketing for Cisco Systems. >"We are applying our expertise in Internet technology and large-scale >networking to help ISPs develop both short- and long-term solutions >for increased network security and reliability." > Web sites on the Internet are typically connected by network >devices called routers. Thus, Cisco engineers believe an ISP or >corporate network could be targeted by attacks at the network level >in addition to the server level. Because of the potential threat to >their networks, Cisco has initiated discussions with ISPs to share >what Cisco knows and suggest immediate steps that can be taken to >reduce vulnerability. > Cisco has existing security products throughout networks >worldwide and is continuously developing new products to continue to >address the need for increased network security. > Due to the intelligence of routers and firewall products, they >are key technologies for resisting attacks of the nature that have >been launched in recent days. By design, routers and firewalls are >intelligent devices with the ability to examine the source of traffic >and block traffic from unauthorized sources. > The ubiquitous role routers play in the Internet makes them a >natural place to implement security capabilities. Cisco provides >more than 80 percent of the routers in the global Internet. > In addition to working with ISPs, Cisco also has initiated >contacts with other networking device and server manufacturers, to >share information and coordinate activity. > Cisco Systems (NASDAQ:CSCO) is the leading global supplier of >internetworking solutions for corporate intranets and the global >Internet. Cisco's products -- including routers, LAN and WAN >switches, dial-up access servers and network management software -- >are integrated by Cisco IOS software to link geographically >dispersed LANs, WANs and IBM networks. > Company news and product/service information are available at >World Wide Web site http://www.cisco.com. Cisco is headquartered in >San Jose, Calif. > Note to Editors: Cisco IOS and Cisco Systems are trademarks, and >Cisco and the Cisco Systems logo are registered trademarks of Cisco >Systems, Inc. All other trademarks, service marks, registered >trademarks or registered service marks mentioned in this document are >the property of their respective owners. > > CONTACT: Cisco Systems, Inc. > Bob Michelet, 408/526-6636 > bmichele@cisco.com > Adam Stein, 408/526-7388 > astein@cisco.com > or > Cunningham Communication, Inc. > Lisa Hempel, 408/764-0738 > lisah@ccipr.com > > KEYWORD: CALIFORNIA > INDUSTRY KEYWORD: COMED COMPUTERS/ELECTRONICS >INTERACTIVE/MULTIMEDIA/INTERNET > > From owner-freebsd-isp Wed Sep 18 18:49:34 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA19121 for isp-outgoing; Wed, 18 Sep 1996 18:49:34 -0700 (PDT) Received: from pegasus.com (pegasus.com [140.174.243.13]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA19068 for ; Wed, 18 Sep 1996 18:49:23 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id PAA10000; Wed, 18 Sep 1996 15:49:02 -1000 Date: Wed, 18 Sep 1996 15:49:02 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199609190149.PAA10000@pegasus.com> In-Reply-To: "Frode Nordahl" "Re: Denying expired users POP?" (Sep 18, 7:06pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "isp@FreeBSD.org" Subject: Re: Denying expired users POP? [theft!] Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This is criminal! } >[ Words to the effect that he wanted popper to use the expire fields in ] } >[ password file. ] } > } >Done! } > } >ftp://ftp.hilink.com.au/FreeBSD/contrib/ } > } >I extracted the relevant code from usr.bin/login/login.c } > } >Please test it before I announce. } > } >cheers, } } Thanks to Danny's patch the qpopper expiry problem is now solved for me. I've tested it briefly, and it works. } } Thanks for all help on the subject from all of you! } --------------------------------- } Frode Nordahl } It's all because of this freely distributable stuff. The whole OS is there for the taking -- source code. When somebody wants a new feature they can *steal* it from one place and stuff it into another, wherever they please! How could someone let this happen?! Richard From owner-freebsd-isp Wed Sep 18 18:59:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA24178 for isp-outgoing; Wed, 18 Sep 1996 18:59:04 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA24098; Wed, 18 Sep 1996 18:58:56 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id UAA10222; Wed, 18 Sep 1996 20:57:52 -0500 From: Joe Greco Message-Id: <199609190157.UAA10222@brasil.moneng.mei.com> Subject: Re: News server... To: froden@bigblue.no Date: Wed, 18 Sep 1996 20:57:52 -0500 (CDT) Cc: isp@freebsd.org, doc@freebsd.org In-Reply-To: <199609182327.BAA26853@login.bigblue.no> from "Frode Nordahl" at Sep 19, 96 00:37:11 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Maybe the DOC guys could throw the "long" part of this message into the FreeBSD handbook someplace... please? :-) I took a little extra time to explain in detail. > >More RAM, definitely. :-) > > Thought you would say that :-)) It is a given no matter how much RAM you have :-) But here you REALLY need it. > >> 4x Quantum Empire (2GB) > >> 1x Quantum Fireball (500MB) > >> > >> Disk configuration > >> 1x Quantum Empire - root device > >> 3x Quantum Empire striped with ccd (Ileave: 16 = 8kb) for /var/spool/news > > > >Too small an interleave. You want each drive to be able to complete a > >transaction on its own... and I am not talking about a single read, > >I mean (minimally) the terminal directory traversal and file read for the > >article in question. You do not want two or three drives participating > >in this operation. Search the mailing list archives, I am tired of > >explaining it. > > Ok... > > >I use an interleave size equal to the number of blocks in a > >_CYLINDER_GROUP_. That is a BIG number. > > 32MB in this case. But that wil not help on performance, or would it? The optimum stripe size for RAID in > hardware is 8kb... That is because "optimum" is defined to be "fastest throughput for a large sequential transaction" for many RAID's. The heads on all N drives move "in sync", so that Drive 0 is reading Block "B * N + 0", Drive 1 is reading Block "B * N + 1", etc, etc. This means that while one drive may only be able to feed data at 2.5MB/sec, all N drives together will feed data to the host at about 2.5MB/sec TIMES N. Great! For sequential accesses. If all the heads on your news server disks are moving "in sync", you lose the advantage of multiple spindles and you might as well get a single 9GB Barracuda drive. And news articles are small anyways, so you are not buying anything in terms of speed - the article most likely will come off one drive. People who have not thought it through will argue that this means an interleave of 8K is great for news. But it's not. What you want is for each spindle to be able to handle a separate transaction on its own. By increasing the size of the interleave to a LARGE number, you increase the likelihood that the one drive will complete an entire operation on its own. Consider the case of reading alt.sex article #12345. On a machine that holds alt 7 days, the directory is daily-bugle# ls -ld /news/alt/sex drwxrwxr-x 133 news news 50688 Sep 18 20:31 /news/alt/sex 50K. If you stripe 8K, and assuming the directory is stored in sequential blocks (valid enough assumption - the disk blocks are _nearby_ if not sequential).. First we read the directory. Get the first 8K from Drive 0.. scan.. nope. Get the second 8K from Drive 1.. scan.. nope.. Get the third 8K from Drive 2... scan.. nope.. Get the fourth 8K from Drive 3... scan.. ah, we found it. The article is stored "nearby", thanks to FFS optimizations.. hmm.. ok get the 4K of article data from Drive 2. Does this seem stupid? We have forced all 4 drives to position their heads in the same area. Now let's repeat with a LARGE stripe size. First we read the directory. We iterate through 26K of data on Drive 0 and we find the article. The article is stored "nearby" and happens to be within this cylinder group, thanks to FFS optimizations.. so we go read that 4K of data with Drive 0, and voila, magically that ONE drive head is already in the general area of the needed access. What are your other three drives doing? Why, they are concurrently getting three OTHER articles needed by other readers. Three other articles, that, in the 8K scenario would have to be fetched sequentially. All of a sudden it looks like it is really nice to have many drives, because if you configure your system correctly, you can get "N" simultaneous accesses where N is number of drives you have. > >> 1x Quantum Fireball - /usr/lib/news (News configuration to avoid excessive I/O on the root dev.) > > > >Good idea. > > Yeah.. Since this computer is going to do other stuff than news too, slowing down the root device with I/O is not a > smart idea.. :) Oooooooooooooooh..... bad idea. Dedicate the machine to news. > >> The disks are connected to two Adaptec 7850 controllers. the news related disks alone on the second > >> adaptec and the root dev on the first. > > > >So you have one "underutilized" SCSI bus... the first one. Spread the disks > >out between the busses. > > Ok... > > >> Does this look like a reasonable setup? This news server does not handle any feeds (Except for the > incoming > >> feed from our provider). Only client access. (For now). > > > >How many simultaneous clients do you expect to be able to handle? > > The maximum peak we expect (For now) is 16*3 clients (16 clients using 3 connections each). 3 connections each? You really should discourage that. You eat a LOT of resources to do that. > >How long do you keep news? > > We keep news for 5 days except for alt.binaries.* that we keep for 3 days maximum. You do not have enough space for alt.binaries. I just filled up a pair of 4GB drives (CCD 8GB) on a system that holds binaries for 2 days.. sigh You will be tight holding the remainder of Usenet for 5 days in only 6GB. > Thanks for the info! > --------------------------------- > Frode Nordahl No problem. ... JG From owner-freebsd-isp Wed Sep 18 19:07:46 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA27961 for isp-outgoing; Wed, 18 Sep 1996 19:07:46 -0700 (PDT) Received: from homer.alpha.net (homer.alpha.net [156.46.10.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA27920 for ; Wed, 18 Sep 1996 19:07:39 -0700 (PDT) Received: from relay (relay.mfa.com [199.88.143.1]) by homer.alpha.net (8.7.5/8.7.3) with SMTP id VAA28271 for ; Wed, 18 Sep 1996 21:06:05 -0500 (CDT) Received: from stimpy.mfa.com by relay (5.x/SMI-SVR4) id AA04400; Wed, 18 Sep 1996 21:02:25 -0500 Received: from localhost by stimpy.mfa.com with SMTP (1.37.109.16/16.2) id AA264108503; Wed, 18 Sep 1996 21:01:43 -0500 Date: Wed, 18 Sep 1996 21:01:43 -0500 (CDT) From: Dan Fifield To: "Samuel E. Romero" Cc: FreeBSD ISP Mailing List Subject: Re: [Fwd: Silo Overflows?] In-Reply-To: <323FD1D8.66F3@hon.hn> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Samuel E. Romero wrote: > Dan Fifield wrote: > > > > Can your users connect to the system, even with the silo overflows or > > > nothing gets transfered to the system because of that?. > > > > No, It stops all serial line activity on the boca box! > > Are you allowed to login using a terminal program. No a burst type talk > (like the ppp or zmodem), just a terminal program with a standard login > shell?. > No I attempted to use Win95's hyperterm and it would not even give me a login prompt. > -- > Samuel E. Romero Soluciones Internacionales > ser@hon.hn Honduras On Net > Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. > PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D > -- > From owner-freebsd-isp Wed Sep 18 19:18:00 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA02065 for isp-outgoing; Wed, 18 Sep 1996 19:18:00 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA02022 for ; Wed, 18 Sep 1996 19:17:54 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id MAA05334; Thu, 19 Sep 1996 12:17:33 +1000 (EST) Date: Thu, 19 Sep 1996 12:17:31 +1000 (EST) From: "Daniel O'Callaghan" To: Frode Nordahl cc: "isp@FreeBSD.org" Subject: Re: Denying expired users POP? In-Reply-To: <199609181757.TAA25256@login.bigblue.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Frode Nordahl wrote: > On Tue, 17 Sep 1996 18:47:43 +1000 (EST), Daniel O'Callaghan wrote: > > >[ Words to the effect that he wanted popper to use the expire fields in ] > >[ password file. ] > > Thanks to Danny's patch the qpopper expiry problem is now solved for me. > I've tested it briefly, and it works. *sigh* On closer inspection of the FreeBSD ports package, the supplied patch patches/patch-ad already has this code in it, as well as the code for SKEY support. Ah well, it's interesting that so much discussion ensued, and no-one noticed that the code was supposedly already there. I'll investigate this further, I think. Danny From owner-freebsd-isp Wed Sep 18 19:30:15 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07349 for isp-outgoing; Wed, 18 Sep 1996 19:30:15 -0700 (PDT) Received: from zeus.xtalwind.net (h-adult.x31.infi.net [206.27.115.53]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07317 for ; Wed, 18 Sep 1996 19:30:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zeus.xtalwind.net (8.7.5/8.7.3) with SMTP id WAA02053; Wed, 18 Sep 1996 22:29:51 -0400 (EDT) Date: Wed, 18 Sep 1996 22:29:51 -0400 (EDT) From: jack To: Paul Nash cc: isp@freebsd.org Subject: Re: CERN errors In-Reply-To: <199609181738.NAA18970@plato.oneworld.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Paul Nash wrote: > I recently switched one of our client's websites onto one of our FreeBSD boxes > and have noticed alot more /kernel errors.. > > Sep 18 12:50:36 lennon /kernel: pid 4053 (bostonapartments), uid 65534: The UID looks bogus to me. ??? -------------------------------------------------------------------------- Jack O'Neill Finger jacko@onyx.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD -------------------------------------------------------------------------- From owner-freebsd-isp Thu Sep 19 00:10:41 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA11610 for isp-outgoing; Thu, 19 Sep 1996 00:10:41 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA11578; Thu, 19 Sep 1996 00:10:38 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id CAA15277; Thu, 19 Sep 1996 02:11:51 -0500 (CDT) Date: Thu, 19 Sep 1996 02:11:50 -0500 (CDT) From: "Matthew N. Dodd" To: Brian Tao cc: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You said you only had 4 meg of write cache on the Streamlogic. I'd be intrested to see the same tests run with 16 or 32 megs of R/W cache on the RAID. I know the CMD 5400s and 5300s support 128m of RAM, and the 5500 supports 512 meg. More RAM should change those numbers a bit. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-isp Thu Sep 19 00:23:43 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA16420 for isp-outgoing; Thu, 19 Sep 1996 00:23:43 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA16399; Thu, 19 Sep 1996 00:23:39 -0700 (PDT) Received: from GndRsh.aac.dev.com by mail.crl.com with SMTP id AA12790 (5.65c/IDA-1.5); Wed, 18 Sep 1996 21:29:10 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id VAA05547; Wed, 18 Sep 1996 21:23:44 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609190423.VAA05547@GndRsh.aac.dev.com> Subject: Re: INN history file and disk I/O In-Reply-To: from Michael Beckmann at "Sep 19, 96 03:26:10 am" To: petzi@zit.th-darmstadt.de (Michael Beckmann) Date: Wed, 18 Sep 1996 21:23:44 -0700 (PDT) Cc: spork@super-g.com, isp@freebsd.org, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > > Buyer beware, Gigabyte is playing games with the specifications and > > register usage of the Triton-I and Triton-II chipsets to get away with > > these 6 SIMM slots. These chip sets have 8 programmable DRAM row size > > registers, each _SIDE_ of a SIMM requires one of them to be programmed, > > you can _ONLY_ run 4 double sided simms with these chip sets. > > According to the HX manual you can use 6 SIMMs with 8 MB each in it, and > these are double-sided. Then Gigabytes HX manual is in conflict with the Intel 82439HX databook, and somehow I trust the databook far more than I do Gigabyte MB manual. > OTOH, who cares whether one can put 6 double sided SIMMs in it. Anyone who is buying this board thinking they can load it with 6 32MB simms for a total memory capacity of 192MB, thats who cares!! > There are > so many valid combinations that I don't see this as a problem. Trust me, as a system builder, it _IS_ a problem. Both at initial machine configuration time (if I preload the system with 4 32MB simms there is no way to field expand the memory without tossing what is already in it away). Now your clone a day shop down the street wouldn't think twice about doing that because he usually doesn't really care about the customer 3 to 6 months down the road. I do care, and don't like to give customers false senses of upgradeabiliy. > The 586 ATE and HX mainboards I have used work just fine, I haven't > seen one fail yet. The 586ATE board does infact run just fine, and I can't recall exactly what it was about it that stopped me from adding it to my product line, perhaps that it offered nothing over my current product line. > That's just my personal experience. I'm not religious about mainboards, > but I don't have the impression that Asus boards have significantly fewer > bugs and problems. Gigabyte definitely belongs to the good equipment. I can agree that buying Gigabyte would be better than buying a lot of other boards out there. > > > Gigabyte dirty little move is to _ONLY_ allow single sided SIMMS in 2 > > Wow, you make it sound as if Gigabyte were posessed by the wicked one ;-) I consider miss leading datasheets to be wicked, yes I do consider Gigabytes marking department to be ``posessed by the wicked one'' for the particular way the use the 6 simm trick to fool people into thinking they can get more memory on there boards than any one elses. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Thu Sep 19 01:16:43 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10207 for isp-outgoing; Thu, 19 Sep 1996 01:16:43 -0700 (PDT) Received: from gargoyle.carpe.net (root@gargoyle.carpe.net [194.162.243.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA10179; Thu, 19 Sep 1996 01:16:36 -0700 (PDT) Received: from helva.grefen.carpe.net (helva.grefen.carpe.net [194.162.243.129]) by gargoyle.carpe.net (8.7.4/8.7.3) with ESMTP id KAA01437; Thu, 19 Sep 1996 10:19:24 +0200 (MET DST) Received: from hex.grefen.carpe.net (root@hex [194.162.243.130]) by helva.grefen.carpe.net (8.7.5/8.7.3) with ESMTP id KAA04849; Thu, 19 Sep 1996 10:21:02 +0200 (MET DST) Received: from hex.grefen.carpe.net (grefen@localhost [127.0.0.1]) by hex.grefen.carpe.net (8.7.3/8.7.3) with ESMTP id KAA03416; Thu, 19 Sep 1996 10:20:59 +0200 (MET DST) To: FREEBSD-SCSI-L Cc: FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks Reply-To: grefen@carpe.net In-reply-to: Brian Tao's message of Wed, 18 Sep 96 18:12:07 EDT. References: Date: Thu, 19 Sep 1996 10:20:56 +0200 Message-ID: <3409.843121256@hex.grefen.carpe.net> From: Stefan Grefen Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message Brian Tao wrote: [...] > > All the usual tools under FreeBSD treat the RAID as a single > drive. The default stripe size is 8K, RAID 5 (striping with parity). > This can be changed via the LCD keypad on the unit itself, or with a > VT-100 interface via the serial port. > > The tests were conducted on newly newfs'd filesystems. sd0 is the > single 4GB drive and sd1 is the RAID. A unit from CMD should be > arriving next week, so I'll have another product to benchmark. > Comments welcome, and please note the Reply-To. You see the benefits of a RAID array only if you access it with stripe-block size or multiple of it. Especially writes suffer from bad performance if you write fractions of a stripe-block (since it first has to read the the remainder of it or the parity block (or both) depending on implementation and where the fractional access occurred). This gives you a high latency which is results in poor performance at least for single-stream access. I assume from your statements that they use the 3 disks as "Data Data Parity" not as a 'true' RAID 5 "Data Data Data Data Parity" (this would have other side effects too). Assuming that 'stripe size is 8K' means that it has 4K blocks on each drive, Every request <8K is SLOW. (it can also mean 8k blocks on each drive which will demand 16k blocks, the phrase 'stripe size' is used different by different vendors). Some of the RAID drives can be configured to complete the SCSI operation when the block is in memory instead when it is commited to disk. This has the same effect as a disk write buffer (with the disadvanatge that it isn't written in case of a power failure). This can't be turned of on some CMD arrays (the recommend to only use it with an UPS). You need to newfs your filesystem to at least 8 (or 16k) blocksize in the default configuration. This ensures that the majority of writes are as fast as possible. If you have large files and writes you can go for even bigger blocksizes. If you have lots of small files reduce the RAID block to the minimum value and use smaller blocksizes. For 'normally' used filesystems a 1-1 mapping of stripe-blocks to filesystem blocks gives (on most systems) the best overall performance. (You have to balance bandwidth versus latency). On the other hand if the Seagate uses a write buffer and tagged queuing and the RAID doesn't it'll loose on any non purely sequential access. To figure out how fast the RAID can go just dd a huge file (/dev/zero) to and from the raw partition with different blocksizes. $ time dd if=/dev/zero of=/dev/rsd1a bs=4196 count=5120 # this will be SLOW $ time dd if=/dev/zero of=/dev/rsd1a bs=8192 count=10240 $ time dd if=/dev/zero of=/dev/rsd1a bs=16384 count=5120 ... Another good test is to talk to Arrays Cache (turn on every bit of performance switch you can find regardless of data-security) and write as above with the minmum possible request size to it. (512). This gives you the upper-limit on scsi-transaction the drives can handle on your bus. (don't be suprised if it maxes out at 500 (250 k) or so :-) )). Stefan > -- > Brian Tao (BT300, taob@io.org, taob@ican.net) > Senior Systems and Network Administrator, Internet Canada Corp. > "Though this be madness, yet there is method in't" > > -- Stefan Grefen Am Grossberg 16, 55130 Mainz, Germany grefen@carpe.net +49 6131 998566 Fax:+49 6131 998568 Living on Earth may be expensive, but it includes an annual free trip around the Sun. From owner-freebsd-isp Thu Sep 19 01:38:44 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA18665 for isp-outgoing; Thu, 19 Sep 1996 01:38:44 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA18642 for ; Thu, 19 Sep 1996 01:38:41 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id EAA25606; Thu, 19 Sep 1996 04:38:37 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Paul Nash cc: isp@freebsd.org From: "Gary Palmer" Subject: Re: CERN errors In-reply-to: Your message of "Wed, 18 Sep 1996 13:38:58 EDT." <199609181738.NAA18970@plato.oneworld.net> Date: Thu, 19 Sep 1996 04:38:37 -0400 Message-ID: <25602.843122317@orion.webspan.net> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Nash wrote in message ID <199609181738.NAA18970@plato.oneworld.net>: > Hi, > I recently switched one of our client's websites onto one of our FreeBSD box > es > and have noticed alot more /kernel errors.. > > Sep 18 12:50:36 lennon /kernel: pid 4053 (bostonapartments), uid 65534: exite > d on signal 10 > Sep 18 13:16:16 lennon /kernel: pid 4700 (bostonapartments), uid 65534: exite > d on signal 10 > Sep 18 13:24:26 lennon /kernel: pid 4781 (bostonapartments), uid 65534: exite > d on signal 10 > Sep 18 13:24:29 lennon /kernel: pid 4783 (bostonapartments), uid 65534: exite > d on signal 10 > > The webserver doesn't die, it just spits out errors.. All of the other > webservers that are homed on the box are running flawlessly.. Anyone else run > into this kind of situation and know of a remedy? signal 10 is a bus error, so it sounds like bad programming to me. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-isp Thu Sep 19 01:44:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21172 for isp-outgoing; Thu, 19 Sep 1996 01:44:25 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA21140 for ; Thu, 19 Sep 1996 01:44:19 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id EAA25789; Thu, 19 Sep 1996 04:44:11 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: "Frode Nordahl" cc: "isp@FreeBSD.org" From: "Gary Palmer" Subject: Re: IP Aliasing... In-reply-to: Your message of "Wed, 18 Sep 1996 20:13:20 BST." <199609181903.VAA25671@login.bigblue.no> Date: Thu, 19 Sep 1996 04:44:11 -0400 Message-ID: <25786.843122651@orion.webspan.net> Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk "Frode Nordahl" wrote in message ID <199609181903.VAA25671@login.bigblue.no>: > I wonder if there is any way to see what IP aliases is configured > for one machine? I see that ifconfig does not list this... For FreeBSD before 2.2-current, `netstat -i'. For -current, ifconfig -a lists the aliases too. (I've got a patch which adds this functionality into -stable too, which I was thinking about seeing if I could get it into 2.1.5-RELEASE, but I had too much on my plate). Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-isp Thu Sep 19 01:45:33 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21622 for isp-outgoing; Thu, 19 Sep 1996 01:45:33 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA21518; Thu, 19 Sep 1996 01:45:18 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id EAA25821; Thu, 19 Sep 1996 04:44:52 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Bernard Jauregui cc: isp@FreeBSD.ORG, questions@FreeBSD.ORG, Douglas Reay From: "Gary Palmer" Subject: Re: Postgres95 under FreeBSD 2.1.5R In-reply-to: Your message of "Wed, 18 Sep 1996 20:10:33 BST." Date: Thu, 19 Sep 1996 04:44:52 -0400 Message-ID: <25818.843122692@orion.webspan.net> Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bernard Jauregui wrote in message ID : > > Thanks to everyone who pointed out that Postgres95 required the SYS V > messaging and memory options set in the kernel. > > Unfortunately I had already though of that and they were present. What does `ipcs' say? Anything lying around claiming lots of SYS V memory? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-isp Thu Sep 19 02:13:27 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA02798 for isp-outgoing; Thu, 19 Sep 1996 02:13:27 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA02771 for ; Thu, 19 Sep 1996 02:13:23 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id FAA27077; Thu, 19 Sep 1996 05:13:13 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: jack cc: Paul Nash , isp@FreeBSD.org From: "Gary Palmer" Subject: Re: CERN errors In-reply-to: Your message of "Wed, 18 Sep 1996 22:29:51 EDT." Date: Thu, 19 Sep 1996 05:13:13 -0400 Message-ID: <27073.843124393@orion.webspan.net> Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk jack wrote in message ID : > On Wed, 18 Sep 1996, Paul Nash wrote: > > > I recently switched one of our client's websites onto one of our FreeBSD b > oxes > > and have noticed alot more /kernel errors.. > > > > Sep 18 12:50:36 lennon /kernel: pid 4053 (bostonapartments), uid 65534: > The UID looks bogus to me. ??? Mo, that's `nobody'... From my box: nobody:*:65534:65534:Unprivileged user:/nonexistent:/nonexistent Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-isp Thu Sep 19 05:48:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA08705 for isp-outgoing; Thu, 19 Sep 1996 05:48:18 -0700 (PDT) Received: from dreamlabs.dreaming.org (root@dreamlabs.dreaming.org [207.107.8.200]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA08637; Thu, 19 Sep 1996 05:48:09 -0700 (PDT) Received: from dreamlabs.dreaming.org (mitayai@dreamlabs.dreaming.org [207.107.8.200]) by dreamlabs.dreaming.org (8.7.5/8.6.12) with SMTP id IAA23431; Thu, 19 Sep 1996 08:47:23 -0400 (EDT) Date: Thu, 19 Sep 1996 08:47:19 -0400 (EDT) From: Will Mitayai Keeso Rowe To: Bernard Jauregui cc: isp@FreeBSD.ORG, questions@FreeBSD.ORG, Douglas Reay Subject: Re: Postgres95 under FreeBSD 2.1.5R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Bernard Jauregui wrote: > > Thanks to everyone who pointed out that Postgres95 required the SYS V > messaging and memory options set in the kernel. > > Unfortunately I had already though of that and they were present. > > Any more suggestions, or do I need to move to FreeBSD 2.2 as Glen Foster > suggests ? Hint : This would be a major pain :-) > > Bernard > You need to check your flex version too... check out ftp://ftp.ki.net/postgres95 or http://www.ki.net/poestgres95, or maybe email scrappy@freebsd.org since he's one of the co-ordinators of Postgres, and also runs it on FreeBSD :) -Mit Will Mitayai Keeso Rowe The DreamLabs Network http://www.dreaming.org (905)725-9139 From owner-freebsd-isp Thu Sep 19 06:34:44 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA05899 for isp-outgoing; Thu, 19 Sep 1996 06:34:44 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA05879 for ; Thu, 19 Sep 1996 06:34:41 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id JAA11336; Thu, 19 Sep 1996 09:34:35 -0400 (EDT) Date: Thu, 19 Sep 1996 09:34:35 -0400 (EDT) From: Charles Henrich Message-Id: <199609191334.JAA11336@crh.cl.msu.edu> To: jgreco@brasil.moneng.mei.com, freebsd-isp@freebsd.org Subject: Re: News server... Newsgroups: lists.freebsd.isp References: <51qe2j$1j1h@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Joe, what parameters do you give to newfs for your news spools? (And Im still skeptical on your stripe size of a CG, but im being convinced slowly :) The problem as I see it is that we have millions of 4k articles. Okay, so maybe a stripe size of 4k is poor because of directory look ups and what not, but why not a stripe size in the range of 128k or 256k, why jump all the way up to 32MB, seems that you will miss the "sweet" spot that striping can get you.. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-isp Thu Sep 19 07:22:30 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29384 for isp-outgoing; Thu, 19 Sep 1996 07:22:30 -0700 (PDT) Received: from hon.hn ([206.48.105.210]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA29343 for ; Thu, 19 Sep 1996 07:22:22 -0700 (PDT) Received: from hon.hn.hon.hn (si1.hon.hn [206.48.253.70]) by hon.hn (8.7.5/8.7.3) with SMTP id IAA07763; Thu, 19 Sep 1996 08:21:47 -0600 (CST) Message-ID: <3240AE9F.1AA8@hon.hn> Date: Thu, 19 Sep 1996 08:23:27 +0600 From: "Samuel E. Romero" Organization: Soluciones Internacionales X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: Dan Fifield CC: FreeBSD ISP Mailing List Subject: Re: [Fwd: Silo Overflows?] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dan Fifield wrote: > > On Wed, 18 Sep 1996, Samuel E. Romero wrote: > > > Dan Fifield wrote: > > > > > > Can your users connect to the system, even with the silo overflows or > > > > nothing gets transfered to the system because of that?. > > > > > > No, It stops all serial line activity on the boca box! > > > > Are you allowed to login using a terminal program. No a burst type talk > > (like the ppp or zmodem), just a terminal program with a standard login > > shell?. > > > > No I attempted to use Win95's hyperterm and it would not even give me a > login prompt. > Ok, I had a similar problem with that card, just a check: Does the irq setting is ok in the kernel config file, in the last sio line?. If you left out that setting, the probes will check the board with all the ports, but as soon as something goes trough the line it will give silo overflows. :-). (Yes, it happened when I was just copying the previous line, instead of type them, so I forgot to place it there). Hope that helps. -- Samuel E. Romero Soluciones Internacionales ser@hon.hn Honduras On Net Tel. CC:(504)39-0547 Tegucigalpa, M.D.C. Honduras, C.A. PGP Signature: D7 89 28 FE 34 19 DE FE 8D 05 D5 36 86 88 DD 6D -- From owner-freebsd-isp Thu Sep 19 07:27:58 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA01192 for isp-outgoing; Thu, 19 Sep 1996 07:27:58 -0700 (PDT) Received: from mail.id.net (mail.id.net [199.125.1.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA01162 for ; Thu, 19 Sep 1996 07:27:50 -0700 (PDT) Received: from server.id.net (rls@server.id.net [199.125.1.10]) by mail.id.net (8.7.5/ID-Net) with ESMTP id KAA02847; Thu, 19 Sep 1996 10:29:53 -0400 (EDT) Received: (from rls@localhost) by server.id.net (8.7.5/8.7.3) id KAA09043; Thu, 19 Sep 1996 10:27:20 -0400 (EDT) From: Robert Shady Message-Id: <199609191427.KAA09043@server.id.net> Subject: Re: Routers - hardware received wisdom In-Reply-To: <199609190027.UAA21659@sabre.goldsword.com> from "John T. Farmer" at "Sep 18, 96 08:27:32 pm" To: jfarmer@sabre.goldsword.com (John T. Farmer) Date: Thu, 19 Sep 1996 10:27:20 -0400 (EDT) Cc: dennis@etinc.com, nik@blueberry.co.uk, isp@freebsd.org, jfarmer@goldsword.com X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think that Dennis' comment & what Joe said in his note answered a question > that I've had lurking in the back of my mind, "Just what is sufficient to run > a FreeBSD T-1 capable router?" > > Granted that a no-name MB & 133Mhz 486 is running around $120, but I > "happen to have" a 386/33, 8mb, 300mb disk sitting in the corner, with > an ethernet card in it (isa only :^,). And I have a need for a T-1 capable > box soon. Since it would be a fairly un-saturated T-1, I suspect that > I will be able to get away with it for a while... Then the question becomes, > how many 56/64k/128/256k frame relay links could a "little" box like that > handle? (Must be the Scots in me, I hate to throw away anything!) Let's think about this logically people.. We're only talking about a MAX of 187 Kilo-Bytes per second for a single T1 line... I've got calculators that could max that out! Now.. When you start throwing multiple ethernet devices in there, and you want to provide wire-to-wire speed acrossed those, that is another story.. We're using a 486DX4-120Mhz w/32MB of RAM here, and it is running 3 100Mb Intel Etherexpress cards, and 2 10Mb SMC Elite Ultra cards.. It does a decent job, although I don't know that I would expect to be able to get full wire speeds on all ethernet cards simultaneously.. But luckily, we have enough segments and switches that we don't need to worry about that, yet. -- Rob === _/_/_/_/_/ _/_/_/_/ _/_/ _/ _/_/_/_/_/ _/_/_/_/_/ _/ _/ _/ _/_/_/ _/ _/ _/ _/_/_/_/ _/ _/_/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/_/ _/ Innovative Data Services Serving South-Eastern Michigan Internet Service Provider / Hardware Sales / Consulting Services Voice: (810)855-0404 / Fax: (810)855-3268 / Web: http://www.id.net From owner-freebsd-isp Thu Sep 19 07:44:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA07355 for isp-outgoing; Thu, 19 Sep 1996 07:44:53 -0700 (PDT) Received: from house.multinet.net (house.multinet.net [204.138.173.37]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA07305 for ; Thu, 19 Sep 1996 07:44:39 -0700 (PDT) Received: (from graydon@localhost) by house.multinet.net (8.6.12/8.6.12) id KAA25323; Thu, 19 Sep 1996 10:44:30 -0400 Date: Thu, 19 Sep 1996 10:44:30 -0400 (EDT) From: Graydon Hoare To: jack cc: Paul Nash , isp@freebsd.org Subject: Re: CERN errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, jack wrote: > On Wed, 18 Sep 1996, Paul Nash wrote: > > > I recently switched one of our client's websites onto one of our FreeBSD boxes > > and have noticed alot more /kernel errors.. > > > > Sep 18 12:50:36 lennon /kernel: pid 4053 (bostonapartments), uid 65534: > > The UID looks bogus to me. ??? 65534 is often used for the nobody account your web server runs as. what sort of server are you running? I've been on freeBSD/apache 1.1.1 for a few months now and it handles it without a hitch. -graydon From owner-freebsd-isp Thu Sep 19 07:48:11 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA08221 for isp-outgoing; Thu, 19 Sep 1996 07:48:11 -0700 (PDT) Received: from radio.nwpros.com (nwpros.com [205.229.128.214]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA08174 for ; Thu, 19 Sep 1996 07:48:03 -0700 (PDT) Received: from rickbox.nwpros.com (rickbox.nwpros.com [205.229.128.217]) by radio.nwpros.com (8.6.12/8.6.12) with SMTP id JAA27483 for ; Thu, 19 Sep 1996 09:52:28 -0500 Message-Id: <1.5.4.32.19960919150042.0068b63c@nwpros.com> X-Sender: rickg@nwpros.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 19 Sep 1996 10:00:42 -0500 To: isp@freebsd.org From: Rick Gray Subject: Ytalk Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have downloaded Ytalk from the FBSD FTP site and when I try a make or make install I get the error of xmkmf:not found, Error Code 2, then I get 2 unexplained Error Code 1. Any ideas what I'm doing wrong? What is this xmkmf? Thanks. ************************************************ Rick Gray Director of Internet Services Network Pros, Inc. rickg@nwpros.com (713)780-5900 "It is a good day to die." ----Klingon Philosophy ************************************************ From owner-freebsd-isp Thu Sep 19 07:52:47 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA09848 for isp-outgoing; Thu, 19 Sep 1996 07:52:47 -0700 (PDT) Received: from plato.oneworld.net (paul@plato.oneworld.net [204.176.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA09818 for ; Thu, 19 Sep 1996 07:52:41 -0700 (PDT) Received: (from paul@localhost) by plato.oneworld.net (8.7.6/8.7.1) id KAA02091; Thu, 19 Sep 1996 10:52:34 -0400 (EDT) From: Paul Nash Message-Id: <199609191452.KAA02091@plato.oneworld.net> Subject: Re: CERN errors To: admin@multinet.net (Graydon Hoare) Date: Thu, 19 Sep 1996 10:52:33 -0400 (EDT) Cc: jack@xtalwind.net, isp@freebsd.org In-Reply-To: from "Graydon Hoare" at Sep 19, 96 10:44:30 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 65534 is often used for the nobody account your web server runs as. what > sort of server are you running? I've been on freeBSD/apache 1.1.1 for a few > months now and it handles it without a hitch. > -graydon > Basically it's a box running with about 6 other websites all multi-homed using a patched CERN3.0 httpd. I've been kicking around the move to Apache, but am a bit hesitant.. CERN3.0 is a nice stable (hrm, well it used to be) package where-as the ncsa/apache line has had some problems in the past.. What's everyone else's view on Apache? -Paul From owner-freebsd-isp Thu Sep 19 08:31:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25045 for isp-outgoing; Thu, 19 Sep 1996 08:31:35 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25018 for ; Thu, 19 Sep 1996 08:31:30 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA10968; Thu, 19 Sep 1996 10:27:38 -0500 From: Joe Greco Message-Id: <199609191527.KAA10968@brasil.moneng.mei.com> Subject: Re: Routers - hardware received wisdom To: rls@mail.id.net (Robert Shady) Date: Thu, 19 Sep 1996 10:27:37 -0500 (CDT) Cc: jfarmer@sabre.goldsword.com, dennis@etinc.com, nik@blueberry.co.uk, isp@freebsd.org, jfarmer@goldsword.com In-Reply-To: <199609191427.KAA09043@server.id.net> from "Robert Shady" at Sep 19, 96 10:27:20 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I think that Dennis' comment & what Joe said in his note answered a question > > that I've had lurking in the back of my mind, "Just what is sufficient to run > > a FreeBSD T-1 capable router?" > > > > Granted that a no-name MB & 133Mhz 486 is running around $120, but I > > "happen to have" a 386/33, 8mb, 300mb disk sitting in the corner, with > > an ethernet card in it (isa only :^,). And I have a need for a T-1 capable > > box soon. Since it would be a fairly un-saturated T-1, I suspect that > > I will be able to get away with it for a while... Then the question becomes, > > how many 56/64k/128/256k frame relay links could a "little" box like that > > handle? (Must be the Scots in me, I hate to throw away anything!) > > Let's think about this logically people.. We're only talking about a MAX > of 187 Kilo-Bytes per second for a single T1 line... I've got calculators > that could max that out! Now.. When you start throwing multiple ethernet > devices in there, and you want to provide wire-to-wire speed acrossed those, > that is another story.. We're using a 486DX4-120Mhz w/32MB of RAM here, and > it is running 3 100Mb Intel Etherexpress cards, and 2 10Mb SMC Elite Ultra > cards.. It does a decent job, although I don't know that I would expect to > be able to get full wire speeds on all ethernet cards simultaneously.. But > luckily, we have enough segments and switches that we don't need to worry > about that, yet. Rob, With all due respect it is not that simple. I suspect that with MTU-sized packets, I can easily go wire to wire with 10baseT at peak speeds even on a 386DX/40 with SMC ISA cards. Actually I was doing that at one point, IIRC, and it worked fine. I suspect that with very small packets, the same machine will have abysmal performance. Dennis' T1 sync serial cards are most similar to an Ethernet card, and I will flat out state that I can saturate your DX4/120 CPU before I hit T1 saturation if I attempt to saturate that T1 link with miniature packets. I have saturated a DX5/133 with this test and it is ugly. On the other hand, the router on the other end was clearly swamped and was only returning one packet for every three I sent (I could see it on the CSU/DSU lights, it was not due to my local CPU being saturated). Some Livingston piece of junk, I believe. It is clearly very dependent on the kind of data you send. I think I can floor even a large Cisco with the right kind of abuse so maybe it's a pointless discussion. I will certainly be the first in line to say that I was pretty happy with a 386DX/40 as a T1-Ethernet router... but I will also be the first to properly qualify that statement. ... JG From owner-freebsd-isp Thu Sep 19 08:39:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28379 for isp-outgoing; Thu, 19 Sep 1996 08:39:26 -0700 (PDT) Received: from glacier.cold.org (glacier.sunrem.com [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA28342 for ; Thu, 19 Sep 1996 08:39:22 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id JAA14427; Thu, 19 Sep 1996 09:40:36 -0600 (MDT) Date: Thu, 19 Sep 1996 09:40:34 -0600 (MDT) From: Brandon Gillespie To: FreeBSD ISP Mailing List Subject: Re: [Fwd: Silo Overflows?] In-Reply-To: <3240AE9F.1AA8@hon.hn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ok, I had a similar problem with that card, just a check: Does the irq > setting is ok in the kernel config file, in the last sio line?. If you > left out that setting, the probes will check the board with all the > ports, but as soon as something goes trough the line it will give silo > overflows. :-). (Yes, it happened when I was just copying the previous > line, instead of type them, so I forgot to place it there). Hope that > helps. We run a in-house dialup server off a BOCA 16 port board (BB2016). When we started there were only 8 modems on the board, but as we have expanded and as they are all used the board continues to freeze up all of the serial ports off the board. The only way to un-freeze is to shutoff all getty's on the serial ports, give it a few and turn them back on (via /etc/ttys). The kernel has been patched in sio.c to set ftl_init to 8 instead of 14, and we seem to have fewer overflows, but they still occur, and when they do the entire board freezes. With our increased usage it is to the point now that there are one to two freezes a day. We need to find a solution, any suggestions? BOCA did tell us the UART on the card is fast enough to handle what we are doing, so I dont suspect that as a problem. The machine is a 486DX2 on an ISA/EISA MB with 20MB RAM. It is not used for much else, and is running 2.1.0 (when I attempted to upgrade to 2.1.5 the kernel paniced after probing all of the devices, on the SCSI card--which, oddly enough, identified differently than it does is 2.1.0--it is an Adaptec 2740A/42A/40AT/42AT). Enjoy; From owner-freebsd-isp Thu Sep 19 08:40:14 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28830 for isp-outgoing; Thu, 19 Sep 1996 08:40:14 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA28765 for ; Thu, 19 Sep 1996 08:40:07 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA10990; Thu, 19 Sep 1996 10:38:44 -0500 From: Joe Greco Message-Id: <199609191538.KAA10990@brasil.moneng.mei.com> Subject: Re: News server... To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Thu, 19 Sep 1996 10:38:43 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, freebsd-isp@freebsd.org In-Reply-To: <199609191334.JAA11336@crh.cl.msu.edu> from "Charles Henrich" at Sep 19, 96 09:34:35 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Joe, what parameters do you give to newfs for your news spools? I used to use -b 4096 -f 512... the Usenet traditional... but I am going to be doing some tests this week because I am seeing some unusual bottlenecking in article throughput on some of the systems I maintain.. > (And Im still skeptical on your stripe size of a CG, but im being convinced > slowly :) The problem as I see it is that we have millions of 4k articles. > Okay, so maybe a stripe size of 4k is poor because of directory look ups and > what not, but why not a stripe size in the range of 128k or 256k, why jump all > the way up to 32MB, seems that you will miss the "sweet" spot that striping can > get you.. You can experiment if you want :-) Yes, 128k or 256k may be better (bear in mind that many binaries articles are 1_MB_) and I have seen 1.5MB junk directories.. so I would probably not select a number < 2MB. Obviously the sweet spot is probably going to be someplace between 1MB and the size of the disk ;-) But I suspect it is somehow going to be tied to how ffs works internally. I also do not have a GOOD set of tools with which to measure concurrency within a news filesystem. I have some basic programs that I run several of simultaneously, but how fair they are? Dunno. It is certainly a problem that could use a researcher. All I am interested in is convincing people that a stripe size of 8K is _foolish_. :-) ... JG From owner-freebsd-isp Thu Sep 19 08:54:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05705 for isp-outgoing; Thu, 19 Sep 1996 08:54:24 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05680 for ; Thu, 19 Sep 1996 08:54:19 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA11109; Thu, 19 Sep 1996 10:53:02 -0500 From: Joe Greco Message-Id: <199609191553.KAA11109@brasil.moneng.mei.com> Subject: Re: [Fwd: Silo Overflows?] To: brandon@glacier.cold.org (Brandon Gillespie) Date: Thu, 19 Sep 1996 10:53:02 -0500 (CDT) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: from "Brandon Gillespie" at Sep 19, 96 09:40:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Ok, I had a similar problem with that card, just a check: Does the irq > > setting is ok in the kernel config file, in the last sio line?. If you > > left out that setting, the probes will check the board with all the > > ports, but as soon as something goes trough the line it will give silo > > overflows. :-). (Yes, it happened when I was just copying the previous > > line, instead of type them, so I forgot to place it there). Hope that > > helps. > > We run a in-house dialup server off a BOCA 16 port board (BB2016). When > we started there were only 8 modems on the board, but as we have expanded > and as they are all used the board continues to freeze up all of the > serial ports off the board. The only way to un-freeze is to shutoff all > getty's on the serial ports, give it a few and turn them back on (via > /etc/ttys). The kernel has been patched in sio.c to set ftl_init to 8 > instead of 14, and we seem to have fewer overflows, but they still occur, > and when they do the entire board freezes. With our increased usage it > is to the point now that there are one to two freezes a day. We need to > find a solution, any suggestions? BOCA did tell us the UART on the card > is fast enough to handle what we are doing, so I dont suspect that as a > problem. I have seen that problem. The interrupt gets stuck "on" - you can see it with a logic probe. We called it "red light syndrome". I never found a solution for it, however you can detect the condition in software: When you connect to a port, and type "AT" to the modem, you do not get a response... but if you hit "" again, you will get the "OK". I hacked up a monitor that detected when the damn thing wedged. ... JG From owner-freebsd-isp Thu Sep 19 10:30:08 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA08792 for isp-outgoing; Thu, 19 Sep 1996 10:30:08 -0700 (PDT) Received: from ns.frihet.com (root@frihet.bayarea.net [205.219.92.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA08732; Thu, 19 Sep 1996 10:29:59 -0700 (PDT) Received: from ns.frihet.com (tweten@localhost [127.0.0.1]) by ns.frihet.com (8.7.5/8.6.12) with ESMTP id KAA06675; Thu, 19 Sep 1996 10:29:20 -0700 (PDT) Message-Id: <199609191729.KAA06675@ns.frihet.com> X-Mailer: exmh version 1.6.7 5/3/96 Reply-To: "David E. Tweten" To: grefen@carpe.net cc: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks Date: Thu, 19 Sep 1996 10:29:20 -0700 From: "David E. Tweten" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk grefen@carpe.net said: >I assume from your statements that they use the 3 disks as "Data >Data Parity" not as a 'true' RAID 5 "Data Data Data Data Parity" >(this would have other side effects too). If I read this right, it is an interesting, though incorrect, interpretation of the meaning of the various levels of RAID. Garth Gibson's definition, in the original RAID paper written while he was a Berkeley PhD. student, required that RAID 5 have no disk devoted exclusively either to data or to parity. Instead, the responsibility for parity rotated through all disks in the array as a function of sequential block on disk. That way the potential for concentrating parity block accesses on one disk could be avoided in the presence of small writes. Small writes can be handled by reading all the blocks in a parity group that aren't going to be written and combining all data blocks to get a new parity block. They can also be handled by reading (or remembering) the original data and reading the original parity, followed by combining old data, new data, and old parity to get new parity. The statistical effect of it all is to generate more disk traffic for "the parity disk". The "5" had nothing to do with the number of disks. The numbers, 1 through 5 had everything to do with various disk array architectures. If my memory can be trusted (a dubious proposition), it went something like this: RAID 1 mirroring (ie, write the same block on n disks) RAID 2 bitwise SECDED (eg., Thinking Machines Data Vault) RAID 3 multi-disk array with dedicated parity disk RAID 4 ? (something truly awful that I can't remember) RAID 5 multi-disk array with rotating parity assignment So, while designating three disks as "data, data, parity" is certainly not RAID 5, neither is designating five disks as "data, data, data, data, parity". They are both RAID 3 architecture. -- David E. Tweten | 2047-bit PGP Key fingerprint: | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 Those who make good products sell products; those who don't, sell solutions. From owner-freebsd-isp Thu Sep 19 11:01:49 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA21506 for isp-outgoing; Thu, 19 Sep 1996 11:01:49 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA21430 for ; Thu, 19 Sep 1996 11:01:37 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id LAA18823; Thu, 19 Sep 1996 11:01:04 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id KAA11272; Thu, 19 Sep 1996 10:52:19 -0700 (PDT) Message-Id: <199609191752.KAA11272@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: henrich@crh.cl.msu.edu (Charles Henrich), freebsd-isp@freebsd.org Subject: Re: News server... In-reply-to: Your message of Thu, 19 Sep 96 10:38:43 -0500. <199609191538.KAA10990@brasil.moneng.mei.com> Date: Thu, 19 Sep 1996 10:52:19 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [...] >I also do not have a GOOD set of tools with which to measure concurrency >within a news filesystem. I have some basic programs that I run several >of simultaneously, but how fair they are? Dunno. It is certainly a >problem that could use a researcher. All I am interested in is convincing >people that a stripe size of 8K is _foolish_. :-) I am about half way though writing a little benchmarking tool that works a lot more like news (lots of files in lots of directories, being read and written simultaneously). I would be "done" by now if I had more time... Is there anything specific you would like to see in something like this? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Thu Sep 19 11:02:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA21606 for isp-outgoing; Thu, 19 Sep 1996 11:02:04 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA21565 for ; Thu, 19 Sep 1996 11:01:58 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id LAA07104; Thu, 19 Sep 1996 11:00:22 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609191800.LAA07104@GndRsh.aac.dev.com> Subject: Re: News server... In-Reply-To: <199609191538.KAA10990@brasil.moneng.mei.com> from Joe Greco at "Sep 19, 96 10:38:43 am" To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Thu, 19 Sep 1996 11:00:22 -0700 (PDT) Cc: henrich@crh.cl.msu.edu, jgreco@brasil.moneng.mei.com, freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Joe, what parameters do you give to newfs for your news spools? > > I used to use -b 4096 -f 512... the Usenet traditional... but I am > going to be doing some tests this week because I am seeing some unusual > bottlenecking in article throughput on some of the systems I maintain.. > > > > (And Im still skeptical on your stripe size of a CG, but im being convinced > > slowly :) The problem as I see it is that we have millions of 4k articles. > > Okay, so maybe a stripe size of 4k is poor because of directory look ups and > > what not, but why not a stripe size in the range of 128k or 256k, why jump all > > the way up to 32MB, seems that you will miss the "sweet" spot that striping can > > get you.. > > You can experiment if you want :-) Yes, 128k or 256k may be better (bear in > mind that many binaries articles are 1_MB_) and I have seen 1.5MB junk > directories.. so I would probably not select a number < 2MB. > > Obviously the sweet spot is probably going to be someplace between > 1MB and the size of the disk ;-) But I suspect it is somehow going to > be tied to how ffs works internally. > > I also do not have a GOOD set of tools with which to measure concurrency > within a news filesystem. I have some basic programs that I run several > of simultaneously, but how fair they are? Dunno. It is certainly a > problem that could use a researcher. All I am interested in is convincing > people that a stripe size of 8K is _foolish_. :-) Perhaps some one should dig up the 1987 UCB paper by Patterson, Gibson and Katz titled ``A Case for Redundant Arrays of Inexpensive Disks (RAID)'', I am sure they covered something about configuring the stripe size very large for high TPS rates, and very small for high bandwidth. Ah.. I did find the UCB report number: UCB/CSD 87/391. I did find this in some other sales lit I have: ``In I/O intensive environments, performance is optimized by striping the drives in the array with stripes large enough so that each record potentially falls entierely within on stripe.'' ... Unfortunately, small stripes rule out multiple overlapped I/O operations, since each I/O will typically involve all drives.'' I think in the usenet news engine case we can safely call the update record a ``cylinder group'', since any file add/remove/read is almost always going to fall within 1 cylinder group (except when UFS's optimizations fail.) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Thu Sep 19 12:17:44 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA28081 for isp-outgoing; Thu, 19 Sep 1996 12:17:44 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA28058 for ; Thu, 19 Sep 1996 12:17:41 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA11376; Thu, 19 Sep 1996 14:13:52 -0500 From: Joe Greco Message-Id: <199609191913.OAA11376@brasil.moneng.mei.com> Subject: Re: News server... To: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com) Date: Thu, 19 Sep 1996 14:13:52 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, henrich@crh.cl.msu.edu, freebsd-isp@freebsd.org In-Reply-To: <199609191752.KAA11272@MindBender.serv.net> from "Michael L. VanLoon -- HeadCandy.com" at Sep 19, 96 10:52:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > [...] > >I also do not have a GOOD set of tools with which to measure concurrency > >within a news filesystem. I have some basic programs that I run several > >of simultaneously, but how fair they are? Dunno. It is certainly a > >problem that could use a researcher. All I am interested in is convincing > >people that a stripe size of 8K is _foolish_. :-) > > I am about half way though writing a little benchmarking tool that > works a lot more like news (lots of files in lots of directories, > being read and written simultaneously). I would be "done" by now if I > had more time... Is there anything specific you would like to see in > something like this? We would all be "done" by now if we had more time. My ideal benchmarking tool? Hmmmmmmmm... If you really want to be faithful to news, it would have to have 25000 hierarchically stacked directories... and it is hard to do it the way news does it... basically the two big "fan outs" are at /news and /news/alt, each of which generally hold hundreds of subdirectories... daily-planet# ls /news|wc 777 777 4260 daily-planet# ls /news/alt|wc 1158 1158 9477 This is quite a thing to try to allow for... it would maybe be easiest to generate a dir pathname using something like char pathname[]; sprintf(pathname, "%d/%d/%d/%d", n > 10000 ? 1 : 0, thousands-digit- of-n * 10 + hundreds-digit-of-n, tens-digit-of-n, ones-digit-of-n)... which might weight the first digits in a similar fashion.. *shrug* It would also be beneficial to weight different directories with different numbers of articles to be "held"... hmmm argh does that ever get complex! Anyways. My thoughts: 1) It would have to be repeatable. Use a seeded random function generator. While I am willing to run a test long enough to judge "average" behavior, there is no reason I can think of not to use a seeded random generator. 2) Multiple(!!) readers, single writer. Single writer adds file "N+1" to "random" directory, some size between 1K-16K, at the rate of five per second. Multiple readers read random articles out of random directories, but may have a tendency to read two or three articles out of the same directory. This might be something to make a configurable parameter... i.e. 50% chance the next article comes out of same directory. This is particularly important due to the fact that behavior on a reader machine and on a feeder machine is very different. Actually it would really be good to provide that same capability for the writer too. I have seen some behavior that I am trying to explain, related to writers and pre-sorted article lists. 3) Maybe an "expire" process that walks through and removes oldest article(s) in a directory. 4) The minimum, average, and maximum times to perform a specific type of operation. I see four operations: a) article write in different dir b) article write in same dir c) article read in different dir d) article read in same dir 5) Number of readers configurable. Potentially to a fairly large number (worst case saturation testing). Michael, I do not expect your tool to do all these things, but if it did, it would answer a lot of "fine tuning" questions I personally have (but have not taken the time to find the answers to because a tool did not exist). I could have written one but I do not place THAT much value on squeezing another 10-15% out of the system. ... JG From owner-freebsd-isp Thu Sep 19 12:54:56 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17677 for isp-outgoing; Thu, 19 Sep 1996 12:54:56 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA17647 for ; Thu, 19 Sep 1996 12:54:53 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA11437; Thu, 19 Sep 1996 14:53:04 -0500 From: Joe Greco Message-Id: <199609191953.OAA11437@brasil.moneng.mei.com> Subject: Re: News server... To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 19 Sep 1996 14:53:04 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, henrich@crh.cl.msu.edu, freebsd-isp@FreeBSD.ORG In-Reply-To: <199609191800.LAA07104@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 19, 96 11:00:22 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Perhaps some one should dig up the 1987 UCB paper by Patterson, Gibson > and Katz titled ``A Case for Redundant Arrays of Inexpensive Disks (RAID)'', > I am sure they covered something about configuring the stripe size > very large for high TPS rates, and very small for high bandwidth. Ah.. > I did find the UCB report number: UCB/CSD 87/391. FOUND it! THANKS Rod, you are always a wealth of valuable knowledge... http://cs-tr.cs.berkeley.edu/Dienst/UI/2.0/Page/ncstrl.ucb/csd-87-391/10?npages=26 "A better measure for database systems is the number of _individual_ reads or writes per second. [...] Ideally during small transfers each disk in a group can act independently, either reading or writing independent information." http://cs-tr.cs.berkeley.edu/Dienst/UI/2.0/Page/ncstrl.ucb/csd-87-391/11?npages=26 (nice picture) However, the paper is entirely too preoccupied with the "R" in RAID, and does not give a lot of information about stripe sizes, etc. http://cs-tr.cs.berkeley.edu/Dienst/UI/2.0/Page/ncstrl.ucb/csd-87-391/22?npages=26 is probably the most "useful" if you simply look at the grey bars in the data plot, but is still comparing mirrored or redundant disks... > I did find this in some other sales lit I have: > ``In I/O intensive environments, performance is optimized by striping > the drives in the array with stripes large enough so that each record > potentially falls entierely within on stripe.'' > ... > > Unfortunately, small stripes rule out multiple overlapped I/O operations, > since each I/O will typically involve all drives.'' Big nod. > I think in the usenet news engine case we can safely call the update > record a ``cylinder group'', since any file add/remove/read is almost > always going to fall within 1 cylinder group (except when UFS's optimizations > fail.) Well, that was MY logic...! :-) And I know it is not "perfect", but it is the best tradeoff I could envision. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-isp Thu Sep 19 13:19:12 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28183 for isp-outgoing; Thu, 19 Sep 1996 13:19:12 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28099 for ; Thu, 19 Sep 1996 13:19:00 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA29075; Thu, 19 Sep 96 15:16:49 -0500 Received: from fergus-18.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA12748; Thu, 19 Sep 96 15:16:46 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id PAA10332; Thu, 19 Sep 1996 15:18:40 -0500 (CDT) Date: Thu, 19 Sep 1996 15:18:40 -0500 (CDT) From: Tony Kimball Message-Id: <199609192018.PAA10332@compound.Think.COM> To: jgreco@brasil.moneng.mei.com Cc: michaelv@MindBender.serv.net, henrich@crh.cl.msu.edu Subject: Re: News server... References: <199609191752.KAA11272@MindBender.serv.net> <199609191913.OAA11376@brasil.moneng.mei.com> Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk : > I would be "done" by now if I had more time... : : We would all be "done" by now if we had more time. A point of philosophy to cheer the day: We're never "done" until we run *out* of time. ______ / \ | 0 0 | \ || / /| | | 'MMMM / ,--' / / "Alas, poor Yorick, I knew him well..." --chuckles From owner-freebsd-isp Thu Sep 19 14:48:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07814 for isp-outgoing; Thu, 19 Sep 1996 14:48:18 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07749 for ; Thu, 19 Sep 1996 14:48:09 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id RAA23438; Thu, 19 Sep 1996 17:48:53 -0400 (EDT) Date: Thu, 19 Sep 1996 17:48:53 -0400 (EDT) From: "John T. Farmer" Message-Id: <199609192148.RAA23438@sabre.goldsword.com> To: jgreco@brasil.moneng.mei.com, rls@mail.id.net Subject: Re: Routers - hardware received wisdom Cc: dennis@etinc.com, isp@freebsd.org, jfarmer@goldsword.com, nik@blueberry.co.uk Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Spoken by jgreco@brasil.moneng.mei.com on Thu Sep 19 11:30:01 1996: >Quoting rls@mail.id.net (Robert Shady): >> Let's think about this logically people.. We're only talking about a MAX >> of 187 Kilo-Bytes per second for a single T1 line... I've got calculators >> that could max that out! Now.. When you start throwing multiple ethernet >> devices in there, and you want to provide wire-to-wire speed acrossed those, >> that is another story.. We're using a 486DX4-120Mhz w/32MB of RAM here, and >> it is running 3 100Mb Intel Etherexpress cards, and 2 10Mb SMC Elite Ultra >> cards.. It does a decent job, although I don't know that I would expect to >> be able to get full wire speeds on all ethernet cards simultaneously.. But >> luckily, we have enough segments and switches that we don't need to worry >> about that, yet. > >Rob, > >With all due respect it is not that simple. > >I suspect that with MTU-sized packets, I can easily go wire to wire >with 10baseT at peak speeds even on a 386DX/40 with SMC ISA cards. >Actually I was doing that at one point, IIRC, and it worked fine. > >I suspect that with very small packets, the same machine will have >abysmal performance. > >Dennis' T1 sync serial cards are most similar to an Ethernet card, and >I will flat out state that I can saturate your DX4/120 CPU before I hit >T1 saturation if I attempt to saturate that T1 link with miniature packets. >I have saturated a DX5/133 with this test and it is ugly. > >On the other hand, the router on the other end was clearly swamped and >was only returning one packet for every three I sent (I could see it >on the CSU/DSU lights, it was not due to my local CPU being saturated). >Some Livingston piece of junk, I believe. > >It is clearly very dependent on the kind of data you send. I think I can >floor even a large Cisco with the right kind of abuse so maybe it's a >pointless discussion. I will certainly be the first in line to say that >I was pretty happy with a 386DX/40 as a T1-Ethernet router... but I will >also be the first to properly qualify that statement. True! True! Joe is exactly right! Of course, if I had remembered a tech report that I wrote 10 years ago, I wouldn't had to asked my question... Ancient history (those who are easily bored can leave the room...). About 1987, I was contracted to the local DOE site (Oak Ridge National Labs) to do some studies on ethernet bridging via a broadband CATV network. We were testing some company's (since disappeared) and boxes from Bridge Communications (now a part of 3com, the basis of the NetBuilder series). The boxes were simple multibus, 68000@8MHz, Lance chipset ethernet, feeding a 5mb/sec channel on the CATV net. We used Vax's & Decnet to create protocol loads and a couple of ethernet analyzers (lanalyzer & a _nice_ HP one) to monitor & to do raw loading. By varying the packet sizes, I could saturate the 5mb link, one of the other bridge, or the local ethernet, again depending on the size of packets. (I, of course used this data & some "fancy" statistical functions to show what would happen in the real world with a varied packet stream...) If a 68000/8Mhz box could do that, then the 386/33 is not so unreasonable after all. Granted, I wouldn't go _buy_ one for the task, but since it's idle... John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-isp Thu Sep 19 16:28:32 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24794 for isp-outgoing; Thu, 19 Sep 1996 16:28:32 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA24759; Thu, 19 Sep 1996 16:28:29 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id TAA26927; Thu, 19 Sep 1996 19:28:30 -0400 (EDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.3) with SMTP id TAA19956; Thu, 19 Sep 1996 19:28:16 -0400 (EDT) X-Authentication-Warning: ki.net: scrappy owned process doing -bs Date: Thu, 19 Sep 1996 19:28:14 -0400 (EDT) From: "Marc G. Fournier" To: Andrzej Bialecki cc: Bernard Jauregui , isp@freebsd.org, questions@freebsd.org, Douglas Reay Subject: Re: Postgres95 under FreeBSD 2.1.5R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Andrzej Bialecki wrote: > On Wed, 18 Sep 1996, Bernard Jauregui wrote: > > > > > Thanks to everyone who pointed out that Postgres95 required the SYS V > > messaging and memory options set in the kernel. > > > > Unfortunately I had already though of that and they were present. > > This is most interesting thing... I compiled Postgres95 1.05 on FreeBSD > 2.1.5 with virtually *no errors*, and now it's up and running (let me > see... yes, it still runs). > > Maybe you forgot to install newly compiled kernel? > > Oh, yes, and as I see your postmaster tried to get a big chunk of shared > memory and got choked. I'd suggest trying to increase maximum size of > shared memory (it's an option during compile - I forgot the name). > Here's what I'm using under FreeBSD 2.2-not-so-current-anymore... options "SHMMAXPGS=1280" options SYSVSHM options SYSVSEM options SYSVMSG Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-isp Thu Sep 19 16:33:06 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA27652 for isp-outgoing; Thu, 19 Sep 1996 16:33:06 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA27619; Thu, 19 Sep 1996 16:33:01 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id TAA27004; Thu, 19 Sep 1996 19:33:26 -0400 (EDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.3) with SMTP id TAA19996; Thu, 19 Sep 1996 19:33:13 -0400 (EDT) X-Authentication-Warning: ki.net: scrappy owned process doing -bs Date: Thu, 19 Sep 1996 19:33:11 -0400 (EDT) From: "Marc G. Fournier" To: Will Mitayai Keeso Rowe cc: Bernard Jauregui , isp@FreeBSD.ORG, questions@FreeBSD.ORG, Douglas Reay Subject: Re: Postgres95 under FreeBSD 2.1.5R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Will Mitayai Keeso Rowe wrote: > On Wed, 18 Sep 1996, Bernard Jauregui wrote: > > > > > Thanks to everyone who pointed out that Postgres95 required the SYS V > > messaging and memory options set in the kernel. > > > > Unfortunately I had already though of that and they were present. > > > > Any more suggestions, or do I need to move to FreeBSD 2.2 as Glen Foster > > suggests ? Hint : This would be a major pain :-) > > > > Bernard > > > You need to check your flex version too... check out > ftp://ftp.ki.net/postgres95 or http://www.ki.net/poestgres95, or maybe > email scrappy@freebsd.org since he's one of the co-ordinators of Postgres, > and also runs it on FreeBSD :) > re: flex... There was a bug known to the 'flex-dev' team in v2.5.3, whcih caused them to supposedly *pull* 2.5.3 from the archives until it was/is fixed... Essentially, if you are going to install Postgres95, either use Flex v2.5.2 or grab README.flex from ftp.://ftp.ki.net/pub/postgres95, which has a patch to v2.5.3 (supplied by Vern Paxson, flex maintainer). Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-isp Fri Sep 20 00:18:50 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25303 for isp-outgoing; Fri, 20 Sep 1996 00:18:50 -0700 (PDT) Received: from gargoyle.carpe.net (root@gargoyle.carpe.net [194.162.243.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA25263; Fri, 20 Sep 1996 00:18:45 -0700 (PDT) Received: from helva.grefen.carpe.net (helva.grefen.carpe.net [194.162.243.129]) by gargoyle.carpe.net (8.7.4/8.7.3) with ESMTP id JAA04536; Fri, 20 Sep 1996 09:19:25 +0200 (MET DST) Received: from hex.grefen.carpe.net (root@hex [194.162.243.130]) by helva.grefen.carpe.net (8.7.5/8.7.3) with ESMTP id JAA07099; Fri, 20 Sep 1996 09:21:21 +0200 (MET DST) Received: from hex.grefen.carpe.net (grefen@localhost [127.0.0.1]) by hex.grefen.carpe.net (8.7.3/8.7.3) with ESMTP id JAA06410; Fri, 20 Sep 1996 09:21:19 +0200 (MET DST) To: "David E. Tweten" Cc: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks Reply-To: grefen@carpe.net In-reply-to: "David E. Tweten"'s message <199609191729.KAA06675@ns.frihet.com> of Thu, 19 Sep 96 10:29:20 PDT. References: <199609191729.KAA06675@ns.frihet.com> Date: Fri, 20 Sep 1996 09:21:17 +0200 Message-ID: <6407.843204077@hex.grefen.carpe.net> From: Stefan Grefen Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609191729.KAA06675@ns.frihet.com> "David E. Tweten" wrote: > grefen@carpe.net said: > >I assume from your statements that they use the 3 disks as "Data > >Data Parity" not as a 'true' RAID 5 "Data Data Data Data Parity" > >(this would have other side effects too). > > If I read this right, it is an interesting, though incorrect, > interpretation of the meaning of the various levels of RAID. It didn't wanted to imply that the parity is always on the same disk. As "Data Data Data Data Parity" on a 3 disk system rotes the parity through the disks !!. [...] Stefan -- Stefan Grefen Am Grossberg 16, 55130 Mainz, Germany grefen@carpe.net +49 6131 998566 Fax:+49 6131 998568 Living on Earth may be expensive, but it includes an annual free trip around the Sun. From owner-freebsd-isp Fri Sep 20 00:51:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA14023 for isp-outgoing; Fri, 20 Sep 1996 00:51:23 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA13997 for ; Fri, 20 Sep 1996 00:51:20 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id AAA07117; Fri, 20 Sep 1996 00:51:23 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id AAA14502; Fri, 20 Sep 1996 00:51:03 -0700 (PDT) Message-Id: <199609200751.AAA14502@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: henrich@crh.cl.msu.edu, freebsd-isp@freebsd.org Subject: Re: News server... In-reply-to: Your message of Thu, 19 Sep 96 14:13:52 -0500. <199609191913.OAA11376@brasil.moneng.mei.com> Date: Fri, 20 Sep 1996 00:50:58 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [...] >> being read and written simultaneously). I would be "done" by now if I >> had more time... Is there anything specific you would like to see in >> something like this? >We would all be "done" by now if we had more time. That was my point. :-) There are lots of things I intended to have done by now. Real time doesn't seem to follow virtual time very well, however... >If you really want to be faithful to news, it would have to have >25000 hierarchically stacked directories... and it is hard to >do it the way news does it... basically the two big "fan outs" >are at /news and /news/alt, each of which generally hold hundreds >of subdirectories... Well, I was thinking a little more like this: There would be three stages -- populate, run, and cleanup. Populate would create a specified number of directories in a specified depth, but randomly. Although you could set the seed. It would also create a specified number of files of random size at the same time it's doing directories. It would do these at the same time to perturb the FFS behavior so that it hopefully wouldn't operate in a completely "perfect" fashion (i. e. fragment a few cylinder grouped directories to mirror more "real life" used filesystems). This would mainly apply to testing on a clean drive, of course. Run would spawn a specified number of writer processes and a specified number of reader processes. The "root" process would talk to them all via full-duplex pipes. It would keep track of the known heirarchy of directories and files, and would issue the commands to each of the readers and writers as they came up for another task. (This would really be cool with a single process and multiple non-blocking threads, but....) The readers/writers would just execute a wait for a task, execute it, send the result back, and wait for the next task. File sizes would be random, but from a weighted scale (so you could specify any mix you like). I would also like to put the task ratios on a weighted scale, as well. For the writer, you would have 1) write a file, 2) create a new directory, 3) delete a file. For the readers, of course, you would just read a specified file from a specified location, after a specified "random" sleep. I figured you could tell it to run until: 1) a certain amount of time had elapsed, 2) a certain number of files/directories had been read, written, and/or created, and/or 3) the disk becomes less than X% full. Of course, cleanup would just undo the whole mess. >It would also be beneficial to weight different directories with different >numbers of articles to be "held"... hmmm argh does that ever get complex! I was hoping the random number generator would just do this for me. >1) It would have to be repeatable. Use a seeded random function generator. > While I am willing to run a test long enough to judge "average" > behavior, there is no reason I can think of not to use a seeded random > generator. Yes, I agree. My only concern is the multiple asynchronous processes. But, since the "root" process issues all commands, I figure the order should stay fairly predictable. >2) Multiple(!!) readers, single writer. Actually, I intended that you specify the number of each. > Single writer adds file "N+1" > to "random" directory, some size between 1K-16K, at the rate of > five per second. I had intended that the writer(s) would be able to write as fast as they could get CPU and disk. That would be the closest thing to a full incoming feed, don't you think? > Multiple readers read random articles out of > random directories, but may have a tendency to read two or three > articles out of the same directory. This might be something to make > a configurable parameter... i.e. 50% chance the next article comes > out of same directory. This is particularly important due to the > fact that behavior on a reader machine and on a feeder machine is > very different. Actually it would really be good to provide that > same capability for the writer too. I have seen some behavior that > I am trying to explain, related to writers and pre-sorted article > lists. Hmmm... Interesting. I hadn't thought of this, but it's worth thinking about. >3) Maybe an "expire" process that walks through and removes oldest > article(s) in a directory. I figured that "expire" would be represented by the "delete a file" task in the writer. The frequency controlled by the weighted ratio. >4) The minimum, average, and maximum times to perform a specific type > of operation. I see four operations: > a) article write in different dir > b) article write in same dir > c) article read in different dir > d) article read in same dir I think you want to break it down into tasks for the reader, and tasks for the writer. The question is whether to have a separate "expirer", or to just let that be another task for the writer. Speaking of which, it might not be a bad idea to add a "stat" before each delete operation. One thing I want to measure accurately, in addition to "speed", is the latency from the time each command is issued to the time control is returned to that process to do something else. >5) Number of readers configurable. Potentially to a fairly large number > (worst case saturation testing). This thing is anything, if configurable. :-) >Michael, I do not expect your tool to do all these things, but if it >did, it would answer a lot of "fine tuning" questions I personally have >(but have not taken the time to find the answers to because a tool did not >exist). I could have written one but I do not place THAT much value on >squeezing another 10-15% out of the system. I'm a benchmark freak. I just love to know exactly how things interact and behave. There is really no "logical" reason for me to write this. I just want to know... :-) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Fri Sep 20 03:14:50 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA15170 for isp-outgoing; Fri, 20 Sep 1996 03:14:50 -0700 (PDT) Received: from gds.de (ns.gds.de [194.77.222.14]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15128 for ; Fri, 20 Sep 1996 03:14:43 -0700 (PDT) Received: from pluto.gds.de (pluto.gds.de [194.77.222.13]) by gds.de (8.7.5/8.6.12) with SMTP id MAA01399 for ; Fri, 20 Sep 1996 12:08:47 GMT Message-Id: <199609201208.MAA01399@gds.de> Comments: Authenticated sender is From: "Richard Gresek" Organization: GDS To: freebsd-isp@freebsd.org Date: Fri, 20 Sep 1996 12:04:03 +0000 Subject: IP-Header Log Priority: normal X-mailer: Pegasus Mail for Windows (v2.40) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hallo, Is it possible to log the IP-headers taht are going through one interface? (Need to see the source- and the destination ip-address + the port) We are running several FreeBSD-servers for our customers as ISDN-Routers (with bisdn). The routers setup the ISDN-line once per hour, even during the night. I d like to find which workstation on which port is sending the packets that cause the dialout. Thanks in advance. Richard +-------------------------------------------------------------------+ : Plus.Net Internet PoP fuer : Oppenheimer Landstr. 55 Frankfurt & Westerwald : 60596 Frankfurt : Tel.: +49 69 61991275 http://www.plusnet.de : Fax : +49 69 610238 +-------------------------------------------------------------------+ From owner-freebsd-isp Fri Sep 20 04:27:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA16131 for isp-outgoing; Fri, 20 Sep 1996 04:27:57 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA16027 for ; Fri, 20 Sep 1996 04:27:35 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.6/8.7.3) id UAA11709; Fri, 20 Sep 1996 20:56:54 +0930 (CST) Date: Fri, 20 Sep 1996 20:56:54 +0930 (CST) From: Peter Childs Message-Id: <199609201126.UAA11709@al.imforei.apana.org.au> To: brandon@glacier.cold.org, freebsd-isp@freebsd.org Subject: Re: [Fwd: Silo Overflows?] X-Newsreader: TIN [version 1.2 PL2] Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <51rrim$oq6@al.imforei.apana.org.au> you wrote: : The machine is a 486DX2 on an ISA/EISA MB with 20MB RAM. It is not used : for much else, and is running 2.1.0 (when I attempted to upgrade to 2.1.5 : the kernel paniced after probing all of the devices, on the SCSI : card--which, oddly enough, identified differently than it does is : 2.1.0--it is an Adaptec 2740A/42A/40AT/42AT). Just FWIW we run a FreeBSD based (2.1-stable) terminal server here running user-ppp and slip connections (dialup and semi-perminent). The machine is a 486sx machine with 8mb RAM, 1 AST 4-port type serial board, and two Cyclades 16Ye 16port cards (for total 38 ports). All ports are locked at 38400 DTE. The ethernet card is just a cheap NE2000 clone. We don't seem to have any problems with this baby, and since its gone to 2.1-stable its been up, which impresses us because our previous commercial 16 port terminal server (chase iolan) couldn't last more than about 18 days without a lockup/reboot (and the one 16 port unit cost about the same as the 38port machine we put together!) pasa: {4} uptime 8:48PM up 51 days, 12:26, 14 users, load averages: 0.27, 0.23, 0.15 Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object! From owner-freebsd-isp Fri Sep 20 05:44:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA29215 for isp-outgoing; Fri, 20 Sep 1996 05:44:48 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA29181 for ; Fri, 20 Sep 1996 05:44:45 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA23333 for isp@freebsd.org; Fri, 20 Sep 1996 14:18:58 +0200 From: Luigi Rizzo Message-Id: <199609201218.OAA23333@labinfo.iet.unipi.it> Subject: IP queues -- how to limit their size ? To: isp@freebsd.org Date: Fri, 20 Sep 1996 14:18:58 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, (with reference to BSD implementations of TCP, but I'd be curious to know how routers approach this problem): is there any way to limit the amount of packets queued for delivery on a given interface ? I am asking because I notice an annoying problem when using PPP over a 14.4 line (easily reproducible when using a WWW browser). When one or more connections are transferring data, queues tend to pile up segments, up to the maximum window size for each connection (16K default). Since the bandwidth is so low, the queues are not very long (10-12 segments per connection) but take a long time to flush (4..12 sec per 16k, depending on the effectiveness of compression). The connections end up with an RTT constantly growing, up to unacceptable values (10s or more), and the RTT is totally dominated by the queueing delay. All this is totally pointless (as it delays other data, causes reduced control over the line, etc.) but since TCP as it is now does not stop expanding windows until a drop occurs, the only solution would be to avoid that a queue on an interface contains more than X seconds of data (related to its speed). So, any idea on how to set this limitation ? Thanks Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-isp Fri Sep 20 07:00:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA17598 for isp-outgoing; Fri, 20 Sep 1996 07:00:23 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA17557 for ; Fri, 20 Sep 1996 07:00:19 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id JAA06966 for ; Fri, 20 Sep 1996 09:00:22 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id JAA06960 for ; Fri, 20 Sep 1996 09:00:21 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id IAA08917; Fri, 20 Sep 1996 08:59:26 -0500 (CDT) Date: Fri, 20 Sep 1996 08:59:26 -0500 (CDT) From: Alex Nash To: Richard Gresek cc: freebsd-isp@FreeBSD.org Subject: Re: IP-Header Log In-Reply-To: <199609201208.MAA01399@gds.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Richard Gresek wrote: > Is it possible to log the IP-headers taht are going through one interface? > (Need to see the source- and the destination ip-address + the port) > > We are running several FreeBSD-servers for our customers as > ISDN-Routers (with bisdn). The routers setup the ISDN-line once per > hour, even during the night. > > I d like to find which workstation on which port is sending the > packets that cause the dialout. How about using ipfw? [The following rules create a wide open firewall because I have assumed that you are not currently using this box as a firewall.] ipfw add accept log all from any to any via xy0 Where xy0 is replaced with your interface name. Naturally, you can expect a *lot* of logging information from this. You could cut it down by specifying the rule to only match packets with the SYN flag set (if you were willing to monitor TCP connections only): ipfw add accept log tcp from any to any setup via xy0 [Note: older versions of ipfw were picky about the order of via and setup, so the above may need to be reversed.] Going a step further, you could also watch for ICMP packets (if someone was keeping a connection alive with ping for instance): ipfw add accept log icmp from any to any via xy0 Don't forget, ipfw blocks everything by default. So if you're using the last two rules, you'll also need to explicitly pass UDP packets and established TCP packets: ipfw add accept all from any to any The interface specification has been dropped to allow localhost/other network communications. Alex From owner-freebsd-isp Fri Sep 20 07:15:52 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA24292 for isp-outgoing; Fri, 20 Sep 1996 07:15:52 -0700 (PDT) Received: from ns.cityscape.co.uk (ns.cityscape.co.uk [194.159.0.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA24184; Fri, 20 Sep 1996 07:15:37 -0700 (PDT) Received: from ns.cityscape.co.uk (ns.cityscape.co.uk [194.159.0.5]) by ns.cityscape.co.uk (8.6.4/8.6.4) with SMTP id PAA03976; Fri, 20 Sep 1996 15:13:59 +0100 Date: Fri, 20 Sep 1996 15:13:59 +0100 (BST) From: Bernard Jauregui To: "Marc G. Fournier" cc: Will Mitayai Keeso Rowe , isp@FreeBSD.ORG, questions@FreeBSD.ORG, Douglas Reay Subject: Re: Postgres95 under FreeBSD 2.1.5R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Again many thanks to all (sounds like the Masons) We now have a happy Postgres95 installation. The flex version is very important, but the ultimate problem was with some orphaned memory blocks preventing the use of new pages (??). A reboot finally cured this and it has not re-occured (yet). Now to decide which version of md5 to standardise on :-( Bernard From owner-freebsd-isp Fri Sep 20 08:33:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA27908 for isp-outgoing; Fri, 20 Sep 1996 08:33:37 -0700 (PDT) Received: from gage.com (auth.gage.com [205.217.2.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA27846; Fri, 20 Sep 1996 08:33:30 -0700 (PDT) Received: from octopus by gage.com (NX5.67d/NX4.2M) id AA09224; Fri, 20 Sep 96 10:31:59 -0500 Received: from squid by octopus.gage.com (NX5.67e/NX3.0S) id AA05226; Fri, 20 Sep 96 10:26:47 -0500 Received: from insomnia by squid.gage.com (NX5.67e/NX3.0S) id AA17329; Fri, 20 Sep 96 10:33:13 -0500 Message-Id: <9609201533.AA17329@squid.gage.com> Received: by insomnia.gage.com (NX5.67g/NX3.0X) id AA00835; Fri, 20 Sep 96 10:32:33 -0500 Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 4.0 v146.2) In-Reply-To: X-Nextstep-Mailer: Mail 3.3 (Enhance 1.3) Received: by NeXT.Mailer (1.146.2) From: Ben Black Date: Fri, 20 Sep 96 10:32:31 -0500 To: Bernard Jauregui Subject: Re: Postgres95 under FreeBSD 2.1.5R Cc: "Marc G. Fournier" , Will Mitayai Keeso Rowe , isp@freebsd.org, questions@freebsd.org, Douglas Reay References: Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Now to decide which version of md5 to standardise on :-( i suggest none. use sha. read the latest cryptobytes from rsa to see why... http://www.rsa.com/rsalabs/cryptobytes/ b3n From owner-freebsd-isp Fri Sep 20 08:40:22 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01314 for isp-outgoing; Fri, 20 Sep 1996 08:40:22 -0700 (PDT) Received: from bud.indirect.com (sfox@bud.indirect.com [165.247.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01281 for ; Fri, 20 Sep 1996 08:40:16 -0700 (PDT) Received: (from sfox@localhost) by bud.indirect.com (8.7.6/8.6.6) id IAA17618 for freebsd-isp@FreeBSD.ORG; Fri, 20 Sep 1996 08:40:13 -0700 (MST) From: Steve Fox Message-Id: <199609201540.IAA17618@bud.indirect.com> Subject: Password Changes To: freebsd-isp@FreeBSD.ORG Date: Fri, 20 Sep 1996 08:40:11 -0700 (MST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings, I'm doing some consulting for a local ISP that is using FreeBSD 2.1.5 for their servers. One of their programmers has come up with a plan to use an alternate password file for Radius, POP, and personal Web page access. His reasoning for doing this is to speed up password access and database updates for large (100K entries) password files and Radius dbm files, and for security in personal Web pages. Rather than use the password database and a Radius database, the password entries now go into a directory structure like /etc/password.dir/X/Y. Where 'X' is the first character of the user name and 'Y' is the last character of the username. The 'Y' file would then contain the encrypted password entry and the Radius User file entries for all user names beginning with 'X' and ending with 'Y'. To accomplish this, he's modified getpwnam, mail.local, Qpopper, Radius, and Sendmail's recipients.c to look in this new directory structure for the password entry. All this sounds reasonable for a Pop only ISP system and it seems to work OK. I just have this uneasy feeling about making changes that affect password access. Is this an unfounded fear or does anyone see any holes in this plan ? Thanks, Steve From owner-freebsd-isp Fri Sep 20 09:53:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA03025 for isp-outgoing; Fri, 20 Sep 1996 09:53:13 -0700 (PDT) Received: from revelstone.jvm.com (revelstone.jvm.com [207.98.213.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA03001 for ; Fri, 20 Sep 1996 09:53:10 -0700 (PDT) Received: (from fbsdlist@localhost) by revelstone.jvm.com (8.7.5/8.6.12) id MAA06892; Fri, 20 Sep 1996 12:52:21 -0400 (EDT) Date: Fri, 20 Sep 1996 12:52:21 -0400 (EDT) From: Cliff Addy To: freebsd-isp@freebsd.org Subject: Reverse name lookup fails on *one* domain Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We run the apache web server on fbsd 2.1.5. We have a recurring problem where we cannot get reverse name lookup on one particular domain. We can reverse anyone else we've tried and others can get reverse name lookups from them. It wouldn't be such a big deal except this domain is one of the biggest ISPs in the area and lots of visitors come from there. When this problem kicks in, folks dialing in on their lines get huge wait times while the reverse service times out. This same problem affects nslookup, ftp, telnet, etc, so its not a webserver-specific thing. The puzzling part is the intermittancy, it works fine for days, then dies for anything from a few minutes to several hours. Rebooting does not clear the problem. This problem's appearance seemed to coincide with the upgrade to 2.1.5, along with the inability for certain other formerly working programs to fork. Any ideas at all? The other guys are running BSDI and are willing to work with us, if we can give them a line of investigation. Cliff From owner-freebsd-isp Fri Sep 20 10:15:42 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13941 for isp-outgoing; Fri, 20 Sep 1996 10:15:42 -0700 (PDT) Received: from hmmm.alaska.net (hmmm.alaska.net [206.149.69.94]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA13833 for ; Fri, 20 Sep 1996 10:15:33 -0700 (PDT) Received: from localhost (hmmm@localhost) by hmmm.alaska.net (8.7.5/8.7.3) with SMTP id RAA00339; Fri, 20 Sep 1996 17:15:17 GMT X-Authentication-Warning: hmmm.alaska.net: hmmm owned process doing -bs Date: Fri, 20 Sep 1996 17:15:16 +0000 () From: Steve Howe To: Paul Nash cc: Graydon Hoare , jack@xtalwind.net, isp@freebsd.org Subject: Re: CERN errors In-Reply-To: <199609191452.KAA02091@plato.oneworld.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Paul Nash wrote: > everyone else's view on Apache? > > -Paul 1/3 Inet sites surveyed use it! (me too!) :) From owner-freebsd-isp Fri Sep 20 11:04:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12540 for isp-outgoing; Fri, 20 Sep 1996 11:04:25 -0700 (PDT) Received: from glacier.cold.org (glacier.cold.org [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA12516 for ; Fri, 20 Sep 1996 11:04:22 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id MAA01286; Fri, 20 Sep 1996 12:06:21 -0600 (MDT) Date: Fri, 20 Sep 1996 12:06:19 -0600 (MDT) From: Brandon Gillespie To: Cliff Addy cc: freebsd-isp@freebsd.org Subject: Re: Reverse name lookup fails on *one* domain In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Any ideas at all? The other guys are running BSDI and are willing to > work with us, if we can give them a line of investigation. quick fix: turn off reverse name lookups, you really dont want it on-the-fly anyway (most log analasys programs can lookup names now). Assuming you are running a recent version of apache (1.1) you can do this by simply adding the config line: 'HostnameLookups off' to httpd.conf. As for longterm fixes, dunno. Perhaps look at the configuration of your named (specifically your 'forwarders'). I doubt the problem is specific to 2.1.5, and it could even be caused by one of your forwarders up the line. If the problem persisted you could hardcode their NS domain in your boot file (cache or secondary--not suggested, but would likely solv the problem). -Brandon Gillespie From owner-freebsd-isp Fri Sep 20 12:27:12 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01877 for isp-outgoing; Fri, 20 Sep 1996 12:27:12 -0700 (PDT) Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01812; Fri, 20 Sep 1996 12:27:07 -0700 (PDT) Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.7.5/8.6.12) id MAA14507; Fri, 20 Sep 1996 12:24:09 -0700 (PDT) Date: Fri, 20 Sep 1996 12:24:09 -0700 (PDT) Message-Id: <199609201924.MAA14507@sunrise.cs.berkeley.edu> To: freebsd-scsi@freebsd.org CC: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-reply-to: (message from Brian Tao on Wed, 18 Sep 1996 18:12:07 -0400 (EDT)) Subject: Re: Streamlogic RAID array benchmarks From: asami@freebsd.org (Satoshi Asami) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >raid 100 1354 25.1 1308 4.5 1056 7.3 3059 55.9 3190 11.5 139.0 5.1 >single 100 3506 66.8 3429 12.0 1848 12.5 5367 99.1 6462 25.6 202.5 7.1 Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You need two 2940?W's (or one 3940?W) and at least four disks though. Satoshi From owner-freebsd-isp Fri Sep 20 13:54:28 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA16588 for isp-outgoing; Fri, 20 Sep 1996 13:54:28 -0700 (PDT) Received: from mail.id.net (mail.id.net [199.125.1.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA16553 for ; Fri, 20 Sep 1996 13:54:25 -0700 (PDT) Received: from server.id.net (rls@server.id.net [199.125.1.10]) by mail.id.net (8.7.5/ID-Net) with ESMTP id QAA14435; Fri, 20 Sep 1996 16:57:18 -0400 (EDT) Received: (from rls@localhost) by server.id.net (8.7.5/8.7.3) id QAA16851; Fri, 20 Sep 1996 16:54:26 -0400 (EDT) From: Robert Shady Message-Id: <199609202054.QAA16851@server.id.net> Subject: Re: Password Changes In-Reply-To: <199609201540.IAA17618@bud.indirect.com> from Steve Fox at "Sep 20, 96 08:40:11 am" To: sfox@indirect.com (Steve Fox) Date: Fri, 20 Sep 1996 16:54:26 -0400 (EDT) Cc: freebsd-isp@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'm doing some consulting for a local ISP that is using FreeBSD 2.1.5 > for their servers. One of their programmers has come up with a plan to > use an alternate password file for Radius, POP, and personal Web page > access. His reasoning for doing this is to speed up password access and > database updates for large (100K entries) password files and Radius dbm > files, and for security in personal Web pages. Rather than use the > password database and a Radius database, the password entries now go into > a directory structure like /etc/password.dir/X/Y. Where 'X' is the first > character of the user name and 'Y' is the last character of the username. > The 'Y' file would then contain the encrypted password entry and the > Radius User file entries for all user names beginning with 'X' and ending > with 'Y'. > > To accomplish this, he's modified getpwnam, mail.local, Qpopper, Radius, > and Sendmail's recipients.c to look in this new directory structure for > the password entry. All this sounds reasonable for a Pop only ISP system > and it seems to work OK. I just have this uneasy feeling about making > changes that affect password access. Is this an unfounded fear or does > anyone see any holes in this plan ? I personally believe that this is a rediculous way of doing it.. If you have 100 people logging in simultaneously (10% of your users? Not that unreasonable), the hard drive head is going to be fluttering all over the place to read the information for that user. I think that some sort of queued synchronus database would be a much better approach. -- Rob === _/_/_/_/_/ _/_/_/_/ _/_/ _/ _/_/_/_/_/ _/_/_/_/_/ _/ _/ _/ _/_/_/ _/ _/ _/ _/_/_/_/ _/ _/_/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/_/ _/ Innovative Data Services Serving South-Eastern Michigan Internet Service Provider / Hardware Sales / Consulting Services Voice: (810)855-0404 / Fax: (810)855-3268 / Web: http://www.id.net From owner-freebsd-isp Fri Sep 20 18:06:37 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA26395 for isp-outgoing; Fri, 20 Sep 1996 18:06:37 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA26272; Fri, 20 Sep 1996 18:06:26 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id SAA25861; Fri, 20 Sep 1996 18:06:21 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id SAA19669; Fri, 20 Sep 1996 18:01:52 -0700 (PDT) Message-Id: <199609210101.SAA19669@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: asami@freebsd.org (Satoshi Asami) cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Streamlogic RAID array benchmarks In-reply-to: Your message of Fri, 20 Sep 96 12:24:09 -0700. <199609201924.MAA14507@sunrise.cs.berkeley.edu> Date: Fri, 20 Sep 1996 18:01:51 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> -------Sequential Output-------- ---Sequential Input-- --Random-- >> -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >>Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >>raid 100 1354 25.1 1308 4.5 1056 7.3 3059 55.9 3190 11.5 139.0 5.1 >>single 100 3506 66.8 3429 12.0 1848 12.5 5367 99.1 6462 25.6 202.5 7.1 >Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You >need two 2940?W's (or one 3940?W) and at least four disks though. Just for our edification, what kind of CPU did you use? Also For Everyones' Information, you won't get close to that on a real filesystem unless you use a Pentium or better. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Fri Sep 20 18:44:29 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA20915 for isp-outgoing; Fri, 20 Sep 1996 18:44:29 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA20765; Fri, 20 Sep 1996 18:44:16 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id SAA13100; Fri, 20 Sep 1996 18:43:44 -0700 (PDT) Date: Fri, 20 Sep 1996 18:43:44 -0700 (PDT) Message-Id: <199609210143.SAA13100@silvia.HIP.Berkeley.EDU> To: michaelv@MindBender.serv.net CC: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-reply-to: <199609210101.SAA19669@MindBender.serv.net> (michaelv@MindBender.serv.net) Subject: Re: Streamlogic RAID array benchmarks From: asami@freebsd.org (Satoshi Asami) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * >Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You * >need two 2940?W's (or one 3940?W) and at least four disks though. * * Just for our edification, what kind of CPU did you use? * * Also For Everyones' Information, you won't get close to that on a real * filesystem unless you use a Pentium or better. Yeah, it's a P5 (133MHz). We got pretty much the same result with the P6 (200MHz) too (which is kinda surprising, given that their memory system is so much slower). Satoshi P.S. http://now.cs.berkeley.edu/Td/bcopy.html for more on the memory thing. From owner-freebsd-isp Fri Sep 20 20:27:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA10432 for isp-outgoing; Fri, 20 Sep 1996 20:27:16 -0700 (PDT) Received: from gandalf.asiapac.net (gandalf.asiapac.net [202.188.0.130]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA10388 for ; Fri, 20 Sep 1996 20:27:11 -0700 (PDT) Received: from klj-7-39.tm.net.my (klj-7-39.tm.net.my [202.188.7.39]) by gandalf.asiapac.net (8.6.12/8.6.12) with SMTP id LAA29693 for ; Sat, 21 Sep 1996 11:09:19 +0800 Date: Sat, 21 Sep 1996 11:09:19 +0800 Message-Id: <199609210309.LAA29693@gandalf.asiapac.net> X-Sender: sckhoo@mail.asiapac.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: isp@freebsd.org From: Swee-Chuan Khoo Subject: mulltiple domain?? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi, I have a bsd machine running 2.1.5 and receiving email for mydomain.com I got a request from marketting people who wanted to create another domain which is vip.mydomain.com Other than having another machine to handle that, which is not what i want as radius will be a mess, how can i modify sendmail to handle that and not letting other non-vip people able to use the vip.mydomain.com domain in their emial address? Thanx and have a nice weekend. +-----------------------------------------------------------------------+ | Khoo Swee Chuan ( The Network Connections ) - system administrator | | http://www.asiapac.net/~sckhoo/ sckhoo@asiapac.net | | tel:603-7337757 fax:603-7345577 #include | | ****** To join MYISOC mailing list, try majordomo@tm.net.my ******** | | +-----------------------------------------------------------------------+ "if you eliminate the impossible, whatever remains - however improbable - must be the truth." From owner-freebsd-isp Fri Sep 20 20:56:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA24689 for isp-outgoing; Fri, 20 Sep 1996 20:56:18 -0700 (PDT) Received: from linkou.trace.com.tw (ronald@[192.72.68.166]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA24593 for ; Fri, 20 Sep 1996 20:56:04 -0700 (PDT) Received: (from ronald@localhost) by linkou.trace.com.tw (8.6.12/8.6.9) id LAA23158; Sat, 21 Sep 1996 11:54:50 +0800 Date: Sat, 21 Sep 1996 11:54:50 +0800 (CCT) From: Ronald Wiplinger To: Swee-Chuan Khoo cc: isp@FreeBSD.org Subject: Re: mulltiple domain?? In-Reply-To: <199609210309.LAA29693@gandalf.asiapac.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Swee-Chuan Khoo wrote: > hi, > > I have a bsd machine running 2.1.5 and receiving email > for mydomain.com > > I got a request from marketting people who wanted to > create another domain which is vip.mydomain.com > > Other than having another machine to handle that, which > is not what i want as radius will be a mess, how can i modify > sendmail to handle that and not letting other non-vip people > able to use the vip.mydomain.com domain in their emial address? > > Thanx and have a nice weekend. I suggest a nice weekend with: sendmail O'Reilly & Associates, Inc. page 127 .... (Multiple Known Names for the Local Host) From owner-freebsd-isp Fri Sep 20 21:12:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01774 for isp-outgoing; Fri, 20 Sep 1996 21:12:04 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01616; Fri, 20 Sep 1996 21:11:47 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA29382; Fri, 20 Sep 1996 21:11:53 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA20862; Fri, 20 Sep 1996 21:11:37 -0700 (PDT) Message-Id: <199609210411.VAA20862@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: asami@freebsd.org (Satoshi Asami) cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Streamlogic RAID array benchmarks In-reply-to: Your message of Fri, 20 Sep 96 18:43:44 -0700. <199609210143.SAA13100@silvia.HIP.Berkeley.EDU> Date: Fri, 20 Sep 1996 21:11:37 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * >Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You > * >need two 2940?W's (or one 3940?W) and at least four disks though. > * > * Just for our edification, what kind of CPU did you use? > * > * Also For Everyones' Information, you won't get close to that on a real > * filesystem unless you use a Pentium or better. >Yeah, it's a P5 (133MHz). We got pretty much the same result with the >P6 (200MHz) too (which is kinda surprising, given that their memory >system is so much slower). How is that surprising? The SCSI controller lives on the other side of the bus, and does the bus-mastering irrespective of the CPU. The CPU does not do bcopies for bus-mastering SCSI transfers. The problems with the 486 is that its slowness causes too great a latency between when work becomes available, and when it has something ready to keep the disk subsystem working, causing less than 100% efficiency. If all have a (working) PCI bus, what happens on the SCSI controller side should not be affected by the CPU, except for how busy the CPU can keep the SCSI controller. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-isp Fri Sep 20 21:30:40 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA09188 for isp-outgoing; Fri, 20 Sep 1996 21:30:40 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA09059; Fri, 20 Sep 1996 21:30:21 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id VAA14425; Fri, 20 Sep 1996 21:29:42 -0700 (PDT) Date: Fri, 20 Sep 1996 21:29:42 -0700 (PDT) Message-Id: <199609210429.VAA14425@silvia.HIP.Berkeley.EDU> To: michaelv@MindBender.serv.net CC: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-reply-to: <199609210411.VAA20862@MindBender.serv.net> (michaelv@MindBender.serv.net) Subject: Re: Streamlogic RAID array benchmarks From: asami@freebsd.org (Satoshi Asami) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * >Yeah, it's a P5 (133MHz). We got pretty much the same result with the * >P6 (200MHz) too (which is kinda surprising, given that their memory * >system is so much slower). * * How is that surprising? The SCSI controller lives on the other side * of the bus, and does the bus-mastering irrespective of the CPU. The * CPU does not do bcopies for bus-mastering SCSI transfers. It does, because this is a bufferred I/O. We were measuring this through the filesystem, remember? An interesting sidenote of this is that when we were using the same P5-133 with the regular (rep/movsl) copyin/copyout, we got only about 20MB/s. We changed it to the Pentium-optimized copy, and managed to push it up close to 30MB/s. The slow bcopy can move about 40MB/s, the fast one 80MB/s. However, the P6-200, despite its 45MB/s bcopy speed, gives us the same 30MB/s through the filesystem. (For those you like math, 45MB/s is 22.2ns/byte, and 30MB/s is 33.3ns/B, and given that the max transfer rate on of 33MHz PCI is 132MB/s, or 7.5 ns/B, this is really close to the limit (22.2 + 7.5 = 29.7 =~ 33.3)....) Satoshi P.S. Doing parallel reads from raw devices, I could get about 65MB/s on the P5...haven't tried that on the P6. From owner-freebsd-isp Fri Sep 20 21:53:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA17730 for isp-outgoing; Fri, 20 Sep 1996 21:53:26 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA17697 for ; Fri, 20 Sep 1996 21:53:20 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id OAA10732; Sat, 21 Sep 1996 14:52:59 +1000 (EST) Date: Sat, 21 Sep 1996 14:52:57 +1000 (EST) From: "Daniel O'Callaghan" To: Ronald Wiplinger cc: Swee-Chuan Khoo , isp@FreeBSD.org Subject: Re: mulltiple domain?? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Ronald Wiplinger wrote: > > create another domain which is vip.mydomain.com > > > > Other than having another machine to handle that, which > > is not what i want as radius will be a mess, how can i modify > > sendmail to handle that and not letting other non-vip people > > able to use the vip.mydomain.com domain in their emial address? > > I suggest a nice weekend with: > sendmail O'Reilly & Associates, Inc. > page 127 .... (Multiple Known Names for the Local Host) But that will allow anyone@anydomain to be anyone@another.domain. Danny From owner-freebsd-isp Fri Sep 20 22:40:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA15527 for isp-outgoing; Fri, 20 Sep 1996 22:40:04 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA15510 for ; Fri, 20 Sep 1996 22:40:02 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id VAA18487 for ; Fri, 20 Sep 1996 21:53:33 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id WAA02269 for ; Fri, 20 Sep 1996 22:34:17 -0700 Date: Fri, 20 Sep 1996 22:34:16 -0700 (PDT) From: Michael Dillon To: isp@FreeBSD.org Subject: Re: mulltiple domain?? In-Reply-To: Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Daniel O'Callaghan wrote: > > > Other than having another machine to handle that, which > > > is not what i want as radius will be a mess, how can i modify > > > sendmail to handle that and not letting other non-vip people > > > able to use the vip.mydomain.com domain in their emial address? > > > > I suggest a nice weekend with: > > sendmail O'Reilly & Associates, Inc. > > page 127 .... (Multiple Known Names for the Local Host) > > But that will allow anyone@anydomain to be anyone@another.domain. Not if you modify the lookup rules and use a database. Check http://www.mtiweb.com/isp for ideas on how to do this. But it really helps to have the book as a reference while you do this kind of thing. Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com From owner-freebsd-isp Sat Sep 21 00:19:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA21030 for isp-outgoing; Sat, 21 Sep 1996 00:19:57 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA20988 for ; Sat, 21 Sep 1996 00:19:53 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id RAA10897; Sat, 21 Sep 1996 17:19:35 +1000 (EST) Date: Sat, 21 Sep 1996 17:19:34 +1000 (EST) From: "Daniel O'Callaghan" To: Richard Gresek cc: freebsd-isp@freebsd.org Subject: Re: IP-Header Log In-Reply-To: <199609201208.MAA01399@gds.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Richard Gresek wrote: > Is it possible to log the IP-headers taht are going through one interface? > (Need to see the source- and the destination ip-address + the port) > > We are running several FreeBSD-servers for our customers as > ISDN-Routers (with bisdn). The routers setup the ISDN-line once per > hour, even during the night. > > I d like to find which workstation on which port is sending the > packets that cause the dialout. Use ipfw (options IPFIREWALL) or Berkeley Packet Filter and tcpdump (pseudo-device bpf 4) Danny From owner-freebsd-isp Sat Sep 21 01:16:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA23713 for isp-outgoing; Sat, 21 Sep 1996 01:16:25 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA23690 for ; Sat, 21 Sep 1996 01:16:22 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id DAA06464; Sat, 21 Sep 1996 03:17:46 -0500 (CDT) Date: Sat, 21 Sep 1996 03:17:45 -0500 (CDT) From: "Matthew N. Dodd" To: Swee-Chuan Khoo cc: isp@FreeBSD.org Subject: Re: mulltiple domain?? In-Reply-To: <199609210309.LAA29693@gandalf.asiapac.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Swee-Chuan Khoo wrote: > I have a bsd machine running 2.1.5 and receiving email > for mydomain.com > > I got a request from marketting people who wanted to > create another domain which is vip.mydomain.com > > Other than having another machine to handle that, which > is not what i want as radius will be a mess, how can i modify > sendmail to handle that and not letting other non-vip people > able to use the vip.mydomain.com domain in their emial address? http://www.jurai.net/~winter/virtual/email.html | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-isp Sat Sep 21 01:20:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25538 for isp-outgoing; Sat, 21 Sep 1996 01:20:26 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25516 for ; Sat, 21 Sep 1996 01:20:23 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id DAA06601; Sat, 21 Sep 1996 03:21:17 -0500 (CDT) Date: Sat, 21 Sep 1996 03:21:17 -0500 (CDT) From: "Matthew N. Dodd" To: Michael Dillon cc: isp@freebsd.org Subject: Re: mulltiple domain?? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Michael Dillon wrote: > Not if you modify the lookup rules and use a database. > Check http://www.mtiweb.com/isp for ideas on how to do this. > > But it really helps to have the book as a reference while you do this kind > of thing. I wrote a complete package that I use on our boxes to do virtual email for customers. I'll probably mess with it later on to add more features and make the config file parsing a bit more robust, but it works like a charm and is easy to setup. Add this to your faq or something. http://www.jurai.net/~winter/virtual/email.html | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-isp Sat Sep 21 01:54:19 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10479 for isp-outgoing; Sat, 21 Sep 1996 01:54:19 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA10383; Sat, 21 Sep 1996 01:54:03 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA25194; Sat, 21 Sep 1996 10:28:08 +0200 Date: Sat, 21 Sep 1996 10:28:08 +0200 (MET DST) From: Luigi Rizzo To: freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org cc: Luigi Rizzo Subject: Re: IP queue size limitations. (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---------- Forwarded message ---------- Date: Sat, 21 SEP 1996 10:14:49 +0200 From: Luigi Rizzo Newgroups: comp.protocols.tcp-ip Subject: Re: IP queue size limitations. On 20 Sep 1996, Vernon Schryver wrote: > In article <51ub5h$8ul@noao.edu>, W. Richard Stevens wrote: > >> Now my question(s): > >> > >> + is it possible, in IP implementations (e.g. BSD), to set the > >> size of output queues differently on each interface ? > > > >It's certainly "possible" since each interface has its own ifq_maxlen > >value (in the ifqueue{} in the ifnet{}), but I've never seen an > >implementation that does this. You could always patch this by hand > At least one UNIX vendor's SLIP and PPP implementations bring > control of ifq_maxlen out to the user interface. I also think the (very clear and detailed explaination omitted -- thanks for including that, it is important that people becomes aware of this problem) I have digged through the FreeBSD sources (should not be much different from 4.4Lite2). ifq_maxlen is, for most interfaces, set to the global varialbe ifqmaxlen which in turn is set to IFQ_MAXLEN which defaults to 50. (this kind of chains is very usual in the BSD code). IFQ_MAXLEN can be defined in the configuration file, but it is the same for all interfaces. The exceptions (from memory) are slip and ppp (ifq_maxlen hardwired to explicit constants in the code, 32 and 50 I believe). At first sight, iijppp (user space ppp via the tun device) uses a queue length of 20. The approximate time needed to flush a queue is as follows: Interface MTU b/s qlen T (1 MSS) T (qlen MSS) ==================================================================== Ethernet 1500 10M 50 1.25ms 62.5ms FDDI ~4KB ~100M 50 330us 16.5ms Fast Ethernet 1500(?) 100M 50 125us 6.25ms T1 1500(?) 1.5M 50 8ms 400ms ISDN 1500 64K 50 188ms 9.4s ISDN 576 64K 50 72ms 3.6s PPP 1500 28.8 20 415ms 8.3s PPP 576 28.8 20 160ms 3.2s PPP 576 28.8 20 320ms 6.4s PPP 1500 14.4 20 830ms 16.6s Considering the default timer granularity, I believe that a queue lenght of up to 1s is acceptable for the slowest networks, but not much more than that. On the other hand, a busy router connecting networks of different speeds could benefit from larger sizes on the faster interfaces. For the slowest networks, I think it is fundamental to compute queue lengths in bytes (after compression, if available), not in maximum sized packets. Note that while this is a router issue, if the bottleneck is at the source more efficient solutions are available, such as a modified quench() call which shrinks the congestion window to a small (but larger than 1) segment. > fills and the delays increase. When the queue finially overflows, > it generally does more than than fast-retransmission can recover, > forcing a timeout and a slow-start, which causes the measured > latency on the link to drop to only the transmission delay. of course, all traffic is delayed by such long queues, the loss is detected after a *long* timeout and the process repeats forever. Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ====================================================================