From owner-freebsd-stable Sun Dec 15 11:00:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA21808 for stable-outgoing; Sun, 15 Dec 1996 11:00:09 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA21803 for ; Sun, 15 Dec 1996 11:00:06 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id MAA20064 for stable@freebsd.org; Sun, 15 Dec 1996 12:00:02 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id LAA01929 for ; Sun, 15 Dec 1996 11:59:14 -0700 (MST) Date: Sun, 15 Dec 1996 11:59:13 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: stable@freebsd.org Subject: someone please commit this fix for crontab hole Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can someone please commit this (well, I don't care what fix it is but this is just the fix from -current) to -stable. Tested, works. Index: crontab.c =================================================================== RCS file: /usr/cvs/src/usr.sbin/cron/crontab/crontab.c,v retrieving revision 1.4 retrieving revision 1.5 diff -c -r1.4 -r1.5 *** crontab.c 1996/04/09 20:28:16 1.4 --- crontab.c 1996/08/05 00:31:27 1.5 *************** *** 167,173 **** ProgramName, optarg); exit(ERROR_EXIT); } ! (void) strcpy(User, optarg); break; case 'l': if (Option != opt_unknown) --- 167,173 ---- ProgramName, optarg); exit(ERROR_EXIT); } ! (void) snprintf(User, sizeof(user), "%s", optarg); break; case 'l': if (Option != opt_unknown) *************** *** 198,204 **** } else { if (argv[optind] != NULL) { Option = opt_replace; ! (void) strcpy (Filename, argv[optind]); } else { usage("file name must be specified for replace"); } --- 198,205 ---- } else { if (argv[optind] != NULL) { Option = opt_replace; ! (void) snprintf(Filename, sizeof(Filename), "%s", ! argv[optind]); } else { usage("file name must be specified for replace"); } *************** *** 480,486 **** ProgramName, Filename); goto done; default: ! fprintf(stderr, "%s: panic: bad switch() in replace_cmd()\n"); goto fatal; } remove: --- 481,488 ---- ProgramName, Filename); goto done; default: ! fprintf(stderr, "%s: panic: bad switch() in replace_cmd()\n", ! ProgramName); goto fatal; } remove: From owner-freebsd-stable Mon Dec 16 06:14:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA05038 for stable-outgoing; Mon, 16 Dec 1996 06:14:27 -0800 (PST) Received: from fty-ss20.cisco.com (fty-ss20.cisco.com [171.69.162.81]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA05027 for ; Mon, 16 Dec 1996 06:14:25 -0800 (PST) Received: by fty-ss20.cisco.com (8.8.4/1.34) id OAA03180; Mon, 16 Dec 1996 14:12:49 GMT Date: Mon, 16 Dec 1996 14:12:49 GMT From: Frank Terhaar-Yonkers Message-Id: <199612161412.OAA03180@fty-ss20.cisco.com> To: freebsd-stable@freebsd.org Subject: VM bounce buffer panic in 2.6.1 CTM 232 X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k X-Mailer: [XMailTool v3.1.0] Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone else seen one of these? Happends EVERY time I try and dump /usr on my machine. I'm going to turn off ddb tonight and run it again to get a clean dump. Machine is an i200/32Mbyte, PCI video but ISA SCSI (adaptec) \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers Cisco Systems, Inc. Engineering Services, W2 F3 5 7025 Kit Creek Road PO Box 14987 Research Triangle Park, North Carolina 27709 fty@cisco.com voice (919)472-2101 FAX (919)472-2940 pager (800)796-7363 pin 1008366 -or- fty@airnote.net From owner-freebsd-stable Mon Dec 16 13:05:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02819 for stable-outgoing; Mon, 16 Dec 1996 13:05:17 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA02806; Mon, 16 Dec 1996 13:05:12 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id QAA24504; Mon, 16 Dec 1996 16:02:00 -0500 (EST) Date: Mon, 16 Dec 1996 16:03:42 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: Gary Roberts cc: DNEX , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 8 Dec 1996, Gary Roberts wrote: > On Sun, 8 Dec 1996, DNEX wrote: > > > Does FreeBSD support IP masquerading or are there plans to implement it? > > > > Yes. It does. Charles Mott. Nice piece of software. Anyways, it's not > a program like linux uses, it uses the PPP program. Check it out at: > > http://www.srv.net/~cmott/alias.html This looks nifty, but I'm interested in doing masquerading on a firewall for users on a large LAN, not dialing in via PPP. What's the status of doing _this_ with FreeBSD? --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-stable Mon Dec 16 14:49:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA10593 for stable-outgoing; Mon, 16 Dec 1996 14:49:03 -0800 (PST) Received: from Cypress.Com (janus.cypress.com [157.95.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA10569; Mon, 16 Dec 1996 14:48:59 -0800 (PST) Received: from diamond.cadc.cypress.com by Cypress.Com; Mon, 16 Dec 1996 14:48:02 -0800 Received: from onyx.cadc (onyx.cadc.cypress.com [157.95.15.17]) by diamond.cadc.cypress.com (8.8.2/8.8.2) with SMTP id QAA17214; Mon, 16 Dec 1996 16:47:52 -0600 (CST) Received: by onyx.cadc (SMI-8.6/SMI-SVR4) id QAA17614; Mon, 16 Dec 1996 16:47:51 -0600 Date: Mon, 16 Dec 1996 16:47:51 -0600 Message-Id: <199612162247.QAA17614@onyx.cadc> From: Barry Boes/CADC Datacomm CAD To: owensc@enc.edu, current@freebsd.org, stable@freebsd.org Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-Reply-To: References: Cc: bab@cypress.com Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need to do the same thing. I'm looking at using the 2.2 divert sockets and code like (or maybe borrowed from) the PPP masquerading code. Does anyone know if this is what Linux does? Is there anyone else out there who has already done this or are we exploring new frontiers? > From: Charles Owens > > On Sun, 8 Dec 1996, Gary Roberts wrote: > > > On Sun, 8 Dec 1996, DNEX wrote: > > > > > Does FreeBSD support IP masquerading or are there plans to implement it? > > > > > > > Yes. It does. Charles Mott. Nice piece of software. Anyways, it's not > > a program like linux uses, it uses the PPP program. Check it out at: > > > > http://www.srv.net/~cmott/alias.html > > > This looks nifty, but I'm interested in doing masquerading on a firewall > for users on a large LAN, not dialing in via PPP. What's the status of > doing _this_ with FreeBSD? From owner-freebsd-stable Mon Dec 16 14:58:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA11556 for stable-outgoing; Mon, 16 Dec 1996 14:58:58 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA11542; Mon, 16 Dec 1996 14:58:46 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id OAA06326; Mon, 16 Dec 1996 14:53:38 -0800 (PST) Message-ID: <32B5D2C4.41C67EA6@whistle.com> Date: Mon, 16 Dec 1996 14:52:52 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Charles Owens CC: Gary Roberts , DNEX , current@freebsd.org, stable@freebsd.org Subject: Re: IP masquerading (for a LAN, _not_ PPP) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Owens wrote: > > On Sun, 8 Dec 1996, Gary Roberts wrote: > > > On Sun, 8 Dec 1996, DNEX wrote: > > > > > Does FreeBSD support IP masquerading or are there plans to implement it? > > > > > > > Yes. It does. Charles Mott. Nice piece of software. Anyways, it's not > > a program like linux uses, it uses the PPP program. Check it out at: > > > > http://www.srv.net/~cmott/alias.html > > This looks nifty, but I'm interested in doing masquerading on a firewall > for users on a large LAN, not dialing in via PPP. What's the status of > doing _this_ with FreeBSD? FreeBSD 2.2 includes the feature "DIVERT SOCKETS" these can be used in conjunction with the ipfw code to create a translation feature. Use the 'divert' keyword with the Ipfw to divert a packet to a 'divert socket' that is openned by the translation daemon. the daemon monitors incoming packets and 'fiddles' the headers accordingly. It also dynamically changes the firewall rules depending on the sessions being translated. We have that runing here but unfortunatly, while we were able to give the divert code out, we can'r give out the daemon.. julian > > --- > - From owner-freebsd-stable Mon Dec 16 15:35:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA14048 for stable-outgoing; Mon, 16 Dec 1996 15:35:19 -0800 (PST) Received: from gate.lustig.com (116.san-francisco-003.ca.dial-access.att.net [207.147.234.116]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA13989; Mon, 16 Dec 1996 15:35:00 -0800 (PST) Received: from Lustig.COM (devious.lustig.com [192.168.1.3]) by gate.lustig.com (8.7.6/8.7.3) with ESMTP id PAA28983; Mon, 16 Dec 1996 15:34:45 -0800 (PST) Received: (from barry@localhost) by Lustig.COM (8.7.3/8.7.3) id PAA10158; Mon, 16 Dec 1996 15:34:50 -0800 (PST) Message-Id: <199612162334.PAA10158@Lustig.COM> MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In-Reply-To: X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2.RR) From: Barry Lustig Date: Mon, 16 Dec 96 15:34:48 -0800 To: Charles Owens Subject: Re: IP masquerading (for a LAN, _not_ PPP) cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Reply-To: barry@Lustig.COM References: X-Organizations: Barry Lustig & Associates Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Take a look at IP Filter http://coombs.anu.edu.au/~avalon/. barry > X-POP3-Rcpt: barry@rmc1.crocker.com > Date: Mon, 16 Dec 1996 16:03:42 -0500 (EST) > From: Charles Owens > X-Sender: owensc@dingo.its.enc.edu > To: Gary Roberts > cc: DNEX , current@FreeBSD.ORG, stable@FreeBSD.ORG > Subject: Re: IP masquerading (for a LAN, _not_ PPP) > In-Reply-To: > > Sender: owner-current@FreeBSD.ORG > X-Loop: FreeBSD.org > > On Sun, 8 Dec 1996, Gary Roberts wrote: > > > On Sun, 8 Dec 1996, DNEX wrote: > > > > > Does FreeBSD support IP masquerading or are there plans to implement > it? > > > > > > Yes. It does. Charles Mott. Nice piece of software. Anyways, it's > not > a program like linux uses, it uses the PPP program. Check it out > at: > > > > http://www.srv.net/~cmott/alias.html > > > This looks nifty, but I'm interested in doing masquerading on a firewall > for users on a large LAN, not dialing in via PPP. What's the status of > doing _this_ with FreeBSD? > > --- > ------------------------------------------------------------------------- > Charles Owens Email: owensc@enc.edu > "I read somewhere to learn is to > Information Technology Services remember... and I've learned that > Eastern Nazarene College we've all forgot..." - King's X > ------------------------------------------------------------------------- > > From owner-freebsd-stable Mon Dec 16 18:20:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA25873 for stable-outgoing; Mon, 16 Dec 1996 18:20:18 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA25866; Mon, 16 Dec 1996 18:20:16 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id TAA01403; Mon, 16 Dec 1996 19:19:53 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id TAA11581; Mon, 16 Dec 1996 19:19:38 -0700 (MST) Date: Mon, 16 Dec 1996 19:19:38 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: Warner Losh cc: freebsd-security@freebsd.org, stable@freebsd.org Subject: Re: why is -stable not secure? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [this may be the start of a nice long useless discussion that has been gone through 100x before; please followup only to the -stable list and NOT to freebsd-security. No, this spew isn't all a response to what Warner has said since he is just echoing reality but is a response to the way things seem to be and where I think it would be nice if they would be.] On Mon, 16 Dec 1996, Warner Losh wrote: > In message Marc Slemko writes: > : Because no one has put them there. They can be there the second after > : they are in -current if they are put there; that happens when the person > : committing them feels confident enough in the patch and has the time to. > > Likely because no one is confortable enough making blind commits to > the -stable branch. I've put a few deltas into the stable branch, but > only after finding people to test them. It is much harder than it > would appear. > > -stable is dead dead dead dead. (the CVS branch based on 2.1.x that > is). If you are worried about security, running 2.2 when it is > released may be your best bet. > > wish I had better news :-( This discussion was bound to come up. It has before, it will again; perhaps about 2.2 next time. Several points: - from a developer's perspective, -stable has been dead for a long time. To some degree it has held back -current developemnt and has resulted in the development version getting too far away from the latest release. This is bad. - from an admin's perspective, -stable is far from dead. There isn't even another release out yet; how can it be dead? We need something to run on our servers. If it were typical MicroSoft junk we may need to upgrade to try to make it work, but -stable works. Very very well. Too well to upgrade to 2.2 until it is proven. The first 2.2 release will have more bugs than -stable has now. More features, but more bugs; they will get worked out, but not overnight. Many people are using FreeBSD for servers because they see it as having more stability over time than the L word. For the people using -stable in a server features don't matter. Minor (in that they are a few lines of code, not that they are unimportant) security fixes are important. - There are many around who could maintain their own local security and serious bug fixes for -stable; many already do. I think there are a significant number of people to which things like security patches to -stable are of importance. - For a long time -stable was treated very carefully because, well, it is supposed to be stable. That caution was warranted and, to a large degree, still is. However, I think that perhaps at this point in -stable's life people should become less concerned about breaking the -stable tree if that means they are more willing to commit to it. Put all these things together, and I think it is worthwhile to keep minimal support for -stable going. Not normal bugfixes, but things like significant security holes. So I think the questions are: - how many existing committers are there that are willing to commit fixes to -stable? - if there isn't enough support on the existing team of committers (and I can certainly understand why that may be the case) for important patches to make it to -stable without special "outside" effort , would it help if someone took the role of "-stable patch dude"? He would take submissions and track -current changes for patches which should be backported to -stable and submit them in a nice, easy to commit well tested format to an existing committer willing to to deal with -stable at that level. If this is necessary, I would be willing to try doing something if no one more suitable is found. - if not, who will be the first to start a seperate repository of either -stable patches or a full -stable with pathes source tree? I realize that most developers want to let -stable die, and agree with their reasons for doing so. However, I have trouble with simply killing it with no alternatives present. From owner-freebsd-stable Mon Dec 16 20:01:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA24098 for stable-outgoing; Mon, 16 Dec 1996 20:01:57 -0800 (PST) Received: from eyelab.psy.msu.edu (root@eyelab.psy.msu.edu [35.8.64.179]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA24092 for ; Mon, 16 Dec 1996 20:01:54 -0800 (PST) Received: from logrus (pm097-17.dialip.mich.net [35.9.14.28]) by eyelab.psy.msu.edu (8.8.3/8.8.3) with SMTP id XAA16638 for ; Mon, 16 Dec 1996 23:17:45 -0500 Message-Id: <3.0.32.19961216230153.006a7190@eyelab.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 16 Dec 1996 23:01:55 -0500 To: freebsd-stable@freebsd.org From: Gary Schrock Subject: Re: why is -stable not secure? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 07:19 PM 12/16/96 -0700, you wrote: > - from an admin's perspective, -stable is far from dead. > There isn't even another release out yet; how can it be > dead? We need something to run on our servers. If it were > typical MicroSoft junk we may need to upgrade to try to > make it work, but -stable works. Very very well. Too > well to upgrade to 2.2 until it is proven. The first > 2.2 release will have more bugs than -stable has now. > More features, but more bugs; they will get worked out, but > not overnight. Many people are using FreeBSD for servers > because they see it as having more stability over time > than the L word. For the people using -stable in a server > features don't matter. Minor (in that they are a few > lines of code, not that they are unimportant) security > fixes are important. Personally I think this hits the nail on the head. Especially since there's no alternative at this point besides the -stable branch for those of us who need a solid server that's not undergoing constant change for adding/stabilizing features that by in large we don't have a need for immediately. I've seen a lot of 'the users this' and 'the developers that' about this issue, but let's face it: until there is a 2.2-stable, there is an absolute necessity for 2.1-stable, and that needs to include security patches. >I realize that most developers want to let -stable die, and agree >with their reasons for doing so. However, I have trouble with simply >killing it with no alternatives present. I completely agree with this statement. Gary Schrock root@eyelab.msu.edu From owner-freebsd-stable Mon Dec 16 21:13:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA28382 for stable-outgoing; Mon, 16 Dec 1996 21:13:01 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA28375 for ; Mon, 16 Dec 1996 21:12:57 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA07056; Mon, 16 Dec 1996 22:12:51 -0700 (MST) Date: Mon, 16 Dec 1996 22:12:51 -0700 (MST) Message-Id: <199612170512.WAA07056@rocky.mt.sri.com> From: Nate Williams To: Gary Schrock Cc: freebsd-stable@freebsd.org Subject: Re: why is -stable not secure? In-Reply-To: <3.0.32.19961216230153.006a7190@eyelab.msu.edu> References: <3.0.32.19961216230153.006a7190@eyelab.msu.edu> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > - from an admin's perspective, -stable is far from dead. > > There isn't even another release out yet; how can it be > > dead? We need something to run on our servers. If it were > > typical MicroSoft junk we may need to upgrade to try to > > make it work, but -stable works. Very very well. Too > > well to upgrade to 2.2 until it is proven. The first > > 2.2 release will have more bugs than -stable has now. > > More features, but more bugs; they will get worked out, but > > not overnight. Many people are using FreeBSD for servers > > because they see it as having more stability over time > > than the L word. For the people using -stable in a server > > features don't matter. Minor (in that they are a few > > lines of code, not that they are unimportant) security > > fixes are important. > > Personally I think this hits the nail on the head. Especially since > there's no alternative at this point besides the -stable branch for those > of us who need a solid server that's not undergoing constant change for > adding/stabilizing features that by in large we don't have a need for > immediately. I've seen a lot of 'the users this' and 'the developers that' > about this issue, but let's face it: until there is a 2.2-stable, there is > an absolute necessity for 2.1-stable, and that needs to include security > patches. Fine. Provide the resources for someone to patch 2.1. Nate From owner-freebsd-stable Mon Dec 16 22:41:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA03575 for stable-outgoing; Mon, 16 Dec 1996 22:41:24 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA03566 for ; Mon, 16 Dec 1996 22:41:22 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id XAA12403; Mon, 16 Dec 1996 23:41:11 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id XAA13068; Mon, 16 Dec 1996 23:40:59 -0700 (MST) Date: Mon, 16 Dec 1996 23:40:59 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: Nate Williams cc: freebsd-stable@freebsd.org Subject: Re: why is -stable not secure? In-Reply-To: <199612170512.WAA07056@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Dec 1996, Nate Williams wrote: > Fine. Provide the resources for someone to patch 2.1. Please elaborate on "resources". Do you not think it should be done in the main CVS repository, or are you referring to the manpower required to do the work? I agree that, unless they want to, it isn't desirable for developers to spend anything more than a trivial amount of time with the 2.1 branch. However, I think that setting up a seperate distribution method would be counterproductive. I started this thread for a reason. I'm trying to figure out the best way for me, and any other willing souls, to try to make this work. I am not interested in continuing 2.1 development but just maintainence in key areas. What I will probably end up doing is simply making patches and seeing what happens to them, since that is more often than not the way to get things accomplished, but first I wanted to get any input that anyone has to offer. Thanks. From owner-freebsd-stable Mon Dec 16 22:58:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA04560 for stable-outgoing; Mon, 16 Dec 1996 22:58:22 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA04553; Mon, 16 Dec 1996 22:58:17 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA03735; Tue, 17 Dec 1996 07:13:21 +0100 From: Luigi Rizzo Message-Id: <199612170613.HAA03735@labinfo.iet.unipi.it> Subject: Re: IP masquerading (for a LAN, _not_ PPP) To: julian@whistle.com (Julian Elischer) Date: Tue, 17 Dec 1996 07:13:21 +0100 (MET) Cc: owensc@enc.edu, wangel@wgrobez1.remote.louisville.edu, dnex@access.digex.net, current@freebsd.org, stable@freebsd.org In-Reply-To: <32B5D2C4.41C67EA6@whistle.com> from "Julian Elischer" at Dec 16, 96 02:52:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > FreeBSD 2.2 includes the feature "DIVERT SOCKETS" > these can be used in conjunction with the ipfw code to > create a translation feature. > > Use the 'divert' keyword with the Ipfw to divert a packet to > a 'divert socket' that is openned by the translation daemon. > the daemon monitors incoming packets and 'fiddles' the headers > accordingly. isn't it a bit expensive ? I mean, do all the packet go to userland where the daemon modifies them and then back to the kernel ? If this is the situation, it sounds like a significant overhead per packet, so you only want to do it at the slow side of a router. 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-stable Tue Dec 17 00:47:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA09037 for stable-outgoing; Tue, 17 Dec 1996 00:47:35 -0800 (PST) Received: from ns2.franke.ch ([195.212.125.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA09028 for ; Tue, 17 Dec 1996 00:47:30 -0800 (PST) Received: from ns2.franke.ch (localhost [127.0.0.1]) by ns2.franke.ch (8.7.5/8.7.3) with SMTP id JAA10052 for ; Tue, 17 Dec 1996 09:44:51 +0100 (MET) Message-ID: <32B65D83.167EB0E7@ns2.franke.ch> Date: Tue, 17 Dec 1996 09:44:51 +0100 From: Josef Egloff Organization: Franke AG, Schweiz X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: subscribe X-URL: http://www.freebsd.org/handbook/handbook224.html#468 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe josef@webstat1.franke.ch From owner-freebsd-stable Tue Dec 17 00:49:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA09144 for stable-outgoing; Tue, 17 Dec 1996 00:49:28 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA09133; Tue, 17 Dec 1996 00:49:23 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.3/8.7.3) id JAA18610; Tue, 17 Dec 1996 09:44:55 +0100 (MET) Message-Id: <199612170844.JAA18610@ravenock.cybercity.dk> Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-Reply-To: <199612170613.HAA03735@labinfo.iet.unipi.it> from Luigi Rizzo at "Dec 17, 96 07:13:21 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Tue, 17 Dec 1996 09:44:55 +0100 (MET) Cc: julian@whistle.com, owensc@enc.edu, wangel@wgrobez1.remote.louisville.edu, dnex@access.digex.net, current@freebsd.org, stable@freebsd.org From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Luigi Rizzo who wrote: > > FreeBSD 2.2 includes the feature "DIVERT SOCKETS" > > these can be used in conjunction with the ipfw code to > > create a translation feature. > > > > Use the 'divert' keyword with the Ipfw to divert a packet to > > a 'divert socket' that is openned by the translation daemon. > > the daemon monitors incoming packets and 'fiddles' the headers > > accordingly. > > isn't it a bit expensive ? I mean, do all the packet go to userland > where the daemon modifies them and then back to the kernel ? If this is > the situation, it sounds like a significant overhead per packet, so you > only want to do it at the slow side of a router. Exactly, thats why I did it in the kernel :) I've mesured the overhead long ago when I started this, and on my rusty old 25Mhz 386SX this works just dandy with 10MBps and multiple connections with kernel resident code. I tried a couple of simple attempts on a userland implementation, but it bailed out on ~100Kbps... (And for those wanting it, its not releasable, sorry) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-stable Tue Dec 17 06:56:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA27528 for stable-outgoing; Tue, 17 Dec 1996 06:56:58 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA27523 for ; Tue, 17 Dec 1996 06:56:55 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id GAA16734; Tue, 17 Dec 1996 06:56:46 -0800 (PST) To: Marc Slemko cc: Warner Losh , stable@freebsd.org Subject: Re: why is -stable not secure? In-reply-to: Your message of "Mon, 16 Dec 1996 19:19:38 MST." Date: Tue, 17 Dec 1996 06:56:46 -0800 Message-ID: <16730.850834606@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > - from an admin's perspective, -stable is far from dead. > There isn't even another release out yet; how can it be > dead? We need something to run on our servers. If it were And this is why I asked Richard Wackerbarth to put out a call among the -committers to see if someone wanted to be the contact person for changes to -stable. I agree that -stable is "dead" and should stay that way from the perspective of the main body of our developers, who really do need to put their time into moving forward. Paradoxically, I also agree that -stable probably has at least a year's worth of life left in it from the *user* perspective. We're downright encouraging people to stick with 2.1.6.1 and stay away from the 2.2 branch until 2.2.1 or thereabouts, so as Marc says, what are these folks expected to do until then? We're also still running CTM generation for -stable and haven't exactly turned out the lights there yet, so people might as well take advantage of the continuing infrastructure to syncronize their trees. However, one cautionary point: > - For a long time -stable was treated very carefully because, > well, it is supposed to be stable. That caution was > warranted and, to a large degree, still is. However, I > think that perhaps at this point in -stable's life people > should become less concerned about breaking the -stable tree > if that means they are more willing to commit to it. NO. I would say that the entire grounds for keeping -stable on life support on any terms would be that its charter be upheld even more strictly than before, if anything. Yes, that could have a chilling effect on commits, but if people are sloppy about maintaining -stable then what's the point? Customers might then as well then migrate to -current where their bug reports will at least be acted upon more quickly if -stable is going to start breaking. I agree that maintining 2.1-stable can have some positive benefits, but only if it's done with great care. Remember the people who you'd be supporting. Jordan From owner-freebsd-stable Tue Dec 17 07:29:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA29298 for stable-outgoing; Tue, 17 Dec 1996 07:29:58 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA29293 for ; Tue, 17 Dec 1996 07:29:55 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA08893; Tue, 17 Dec 1996 08:29:47 -0700 (MST) Date: Tue, 17 Dec 1996 08:29:47 -0700 (MST) Message-Id: <199612171529.IAA08893@rocky.mt.sri.com> From: Nate Williams To: Marc Slemko Cc: Nate Williams , freebsd-stable@freebsd.org Subject: Re: why is -stable not secure? In-Reply-To: References: <199612170512.WAA07056@rocky.mt.sri.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Fine. Provide the resources for someone to patch 2.1. > > Please elaborate on "resources". Do you not think it should be done in > the main CVS repository, or are you referring to the manpower required to > do the work? Manpower and/or incentives for manpower. In the past, I offered to integrate any/all changes to the -stable branch from the 'users', which include a large number of commercial folks who rely on FreeBSD for their business. I didn't receive *one* patch from anyone, and instead had to do all my own testing and such to bring in stability/security patches to stable that I felt were necessary. I thinks it's nice that everyone likes stable, but no-one was willing to do anything to keep it updated, so I withdrew my offer because of the obvious lack of interest in outside people doing work. I'm now focusing my energies on current. Nate From owner-freebsd-stable Tue Dec 17 07:41:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA00255 for stable-outgoing; Tue, 17 Dec 1996 07:41:07 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA00247 for ; Tue, 17 Dec 1996 07:41:03 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id HAA17015; Tue, 17 Dec 1996 07:41:00 -0800 (PST) To: Marc Slemko cc: Nate Williams , freebsd-stable@freebsd.org Subject: Re: why is -stable not secure? In-reply-to: Your message of "Mon, 16 Dec 1996 23:40:59 MST." Date: Tue, 17 Dec 1996 07:41:00 -0800 Message-ID: <17011.850837260@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I started this thread for a reason. I'm trying to figure out the best way > for me, and any other willing souls, to try to make this work. I am not Some committer agrees to act as front-man for the 2.1-stable branch, also working with Richard Wackerbarth in making sure that services like CTM delta generation and such continue to work. That's really all it's going to take. Jordan From owner-freebsd-stable Tue Dec 17 13:21:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA19961 for stable-outgoing; Tue, 17 Dec 1996 13:21:23 -0800 (PST) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA19943 for ; Tue, 17 Dec 1996 13:20:41 -0800 (PST) Received: from stuyts by ns.NL.net (5.65b/NLnet1.3) id AA24165; Tue, 17 Dec 1996 22:08:53 +0100 Received: by daneel.stuyts.nl (NX5.67f2/daneel940629) id AA22915; Tue, 17 Dec 96 22:00:16 +0100 Message-Id: <9612172100.AA22915@daneel.stuyts.nl> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Tue, 17 Dec 96 22:00:13 +0100 To: freebsd-stable@freebsd.org Subject: Install problem on second drive: panic can't mount / Reply-To: ben@stuyts.nl Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to install 2.1.5-Release on a system with three drives: - The first one is an IDE drive with Win95 (master on first IDE controller) - The second one is a SCSI drive with FreeBSD (scsi id 1) - The third one is a SCSI drive with WinNT (scsi id 2) The motherboard is a dual-pentium Giga-Byte DX586 with on-board 7880 scsi controller. I managed to get a bootmanager to boot FreeBSD, and it boots the kernel allright. After that, it panics and reboots because it cannot mount the / filesystem. If I disable the IDE drive in the bios, booting FreeBSD works just fine. I am not able to change the booting order in the bios so that the SCSI drives would be probed before the IDE drives. Any ideas? Thanks, Ben From owner-freebsd-stable Tue Dec 17 16:08:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02339 for stable-outgoing; Tue, 17 Dec 1996 16:08:26 -0800 (PST) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA02324 for ; Tue, 17 Dec 1996 16:08:22 -0800 (PST) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.4/8.7.5) id RAA14779; Tue, 17 Dec 1996 17:07:28 -0700 (MST) From: Softweyr LLC Message-Id: <199612180007.RAA14779@xmission.xmission.com> Subject: Re: why is -stable not secure? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 17 Dec 1996 17:07:27 -0700 (MST) Cc: stable@freebsd.org In-Reply-To: <16730.850834606@time.cdrom.com> from "Jordan K. Hubbard" at Dec 17, 96 06:56:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan Hubbard (we're not worthy, we're not worthy!) said: > And this is why I asked Richard Wackerbarth to put out a call among > the -committers to see if someone wanted to be the contact person for > changes to -stable. Yay, Jordan! Go Richard! I'm certain Richard will let us know as soon as he has this process ready to roll. If you want to help -stable continue to recieve security-related patches, contact Richard via the -stable mailing list. Now, can we put this issue to bed? > NO. I would say that the entire grounds for keeping -stable on life > support on any terms would be that its charter be upheld even more > strictly than before, if anything. Yes, that could have a chilling > effect on commits, but if people are sloppy about maintaining -stable > then what's the point? Customers might then as well then migrate to > -current where their bug reports will at least be acted upon more > quickly if -stable is going to start breaking. Amen. Security patches and crash fixes only, and the only when the patches have been tested by a reasonable subset of the beta testers Richard will be putting together (right, Richard? ;^) Once the patches have been commited, Richard and his minions will distribute source patches, and binaries for those who don't do sources, via some mechanism yet to be specified. Again, if you want to help, contact Richard via -stable. If you want the product, watch there. If you wanna gripe, > /dev/null. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com From owner-freebsd-stable Tue Dec 17 17:11:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA05704 for stable-outgoing; Tue, 17 Dec 1996 17:11:40 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA05699 for ; Tue, 17 Dec 1996 17:11:37 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA20353; Tue, 17 Dec 1996 17:11:21 -0800 (PST) To: Softweyr LLC cc: stable@freebsd.org Subject: Re: why is -stable not secure? In-reply-to: Your message of "Tue, 17 Dec 1996 17:07:27 MST." <199612180007.RAA14779@xmission.xmission.com> Date: Tue, 17 Dec 1996 17:11:21 -0800 Message-ID: <20349.850871481@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Richard will be putting together (right, Richard? ;^) Once the > patches have been commited, Richard and his minions will distribute > source patches, and binaries for those who don't do sources, via > some mechanism yet to be specified. Well, I may frown somewhat at the idea of binaries going out unless they're generated in a very careful fashion, but I also think that asking people who want to track -stable to carry a src tree is a more than reasonable prerequisite. > Again, if you want to help, contact Richard via -stable. If you want Or even just contact Richard via Richard. :-) I don't think that -stable need necessarily follow every twisty mechanation of the BETA process if everyone is careful about announcing the end results. Jordan From owner-freebsd-stable Tue Dec 17 19:28:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA13067 for stable-outgoing; Tue, 17 Dec 1996 19:28:39 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA13062; Tue, 17 Dec 1996 19:28:33 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.2/8.8.2) id WAA14546; Tue, 17 Dec 1996 22:28:32 -0500 (EST) Date: Tue, 17 Dec 1996 22:28:32 -0500 (EST) From: Charles Henrich Message-Id: <199612180328.WAA14546@crh.cl.msu.edu> To: sos@freebsd.org, freebsd-stable@freebsd.org Subject: Re: IP masquerading (for a LAN, _not_ PPP) Newsgroups: lists.freebsd.stable References: <595pjs$15ek@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.stable you write: >Exactly, thats why I did it in the kernel :) Do you still have this, and is it in a distributable form? Please? :) -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-stable Tue Dec 17 23:17:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA21362 for stable-outgoing; Tue, 17 Dec 1996 23:17:55 -0800 (PST) Received: from bofh.noc.best.net (rone@bofh.noc.best.net [205.149.163.54]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA21355 for ; Tue, 17 Dec 1996 23:17:53 -0800 (PST) Received: (from rone@localhost) by bofh.noc.best.net (8.8.3/8.7.3) id XAA25847 for stable@freebsd.org; Tue, 17 Dec 1996 23:17:45 -0800 (PST) From: Ron Echeverri Message-Id: <199612180717.XAA25847@bofh.noc.best.net> Subject: /usr/share/skel/dot.cshrc nitpick To: stable@freebsd.org Date: Tue, 17 Dec 1996 23:17:45 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From the forementioned file: ===== set path = (~/bin /bin /usr/{bin,games} /usr/local/bin /usr/X11R6/bin) if ($?prompt) then # An interactive shell -- set some stuff up set filec set history = 1000 set ignoreeof set mail = (/var/mail/$USER) set mch = `hostname -s` set prompt = "${mch:q}: {\!} " umask 2 endif ===== Is there a reason that /sbin, /usr/sbin, and /usr/local/sbin aren't in the path? Also, is a umask of 2 a good default? Shouldn't it be 22? Of course, i can set defaults for users on my system, but is there a reason for this stuff to be the FreeBSD default? (should this go to the doc list?) rone -- Ron Echeverri Best Internet Usenet Administration rone@best.net ---------------------------------------------------------------------------- And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "bloatware". From owner-freebsd-stable Wed Dec 18 05:00:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA05215 for stable-outgoing; Wed, 18 Dec 1996 05:00:09 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA05175; Wed, 18 Dec 1996 05:00:00 -0800 (PST) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id HAA27324; Wed, 18 Dec 1996 07:57:51 -0500 (EST) Date: Wed, 18 Dec 1996 08:00:23 -0500 (EST) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: sos@freebsd.org cc: Luigi Rizzo , julian@whistle.com, wangel@wgrobez1.remote.louisville.edu, dnex@access.digex.net, current@freebsd.org, stable@freebsd.org Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-Reply-To: <199612170844.JAA18610@ravenock.cybercity.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id FAA05209 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Dec 1996 sos@freebsd.org wrote: > In reply to Luigi Rizzo who wrote: > > > FreeBSD 2.2 includes the feature "DIVERT SOCKETS" > > > these can be used in conjunction with the ipfw code to > > > create a translation feature. > > > > > > Use the 'divert' keyword with the Ipfw to divert a packet to > > > a 'divert socket' that is openned by the translation daemon. > > > the daemon monitors incoming packets and 'fiddles' the headers > > > accordingly. > > > > isn't it a bit expensive ? I mean, do all the packet go to userland > > where the daemon modifies them and then back to the kernel ? If this is > > the situation, it sounds like a significant overhead per packet, so you > > only want to do it at the slow side of a router. > > Exactly, thats why I did it in the kernel :) > I've mesured the overhead long ago when I started this, and on my > rusty old 25Mhz 386SX this works just dandy with 10MBps and > multiple connections with kernel resident code. I tried a > couple of simple attempts on a userland implementation, but > it bailed out on ~100Kbps... > (And for those wanting it, its not releasable, sorry) > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end Ok... help me out here: the 'ipfilter' package is _not_ a userland implementation, right? (just trying to put all of the pieces to gether here...) Why do some folks consider the DIVERT sockets with userland daemon approach better than other existing options, such as ipfilter? Or, more directly, why might I not want to user ipfilter to build a firewall for a large (hundreds of users) LAN? (pssst... not trying to start a war here) I'm trying to discern which of the available options makes the most sense for me... at this instant ipfilter seems the best bet --- feature rich and good performance (I'm assuming... by virtue of it's kernel implementation... any testimonials?). I'd use the ipfw package but I really need NAT. If this should be moved out of -stable and -current then... sorry... :-) Thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-stable Wed Dec 18 07:35:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA11315 for stable-outgoing; Wed, 18 Dec 1996 07:35:43 -0800 (PST) Received: from fps.biblos.unal.edu.co ([168.176.37.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA11308 for ; Wed, 18 Dec 1996 07:35:24 -0800 (PST) Received: from unalmodem.usc.unal.edu.co by fps.biblos.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA14118; Wed, 18 Dec 1996 10:39:30 -0500 Message-Id: <32B8389C.AA3@fps.biblos.unal.edu.co> Date: Wed, 18 Dec 1996 10:31:56 -0800 From: "Pedro Giffuni S." Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: Ron Echeverri Cc: stable@freebsd.org Subject: Re: /usr/share/skel/dot.cshrc nitpick References: <199612180717.XAA25847@bofh.noc.best.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ron Echeverri wrote: > > >From the forementioned file: > > ===== > set path = (~/bin /bin /usr/{bin,games} /usr/local/bin /usr/X11R6/bin) > > > Is there a reason that /sbin, /usr/sbin, and /usr/local/sbin aren't in > the path? Probably because those dirs keep programs that concern to administrators only. It´s not good to have those paths for common users as it isn´t the best to have /usr/X11R6/bin in root´s path. Pedro. > rone > -- > Ron Echeverri Best Internet Usenet Administration rone@best.net > ---------------------------------------------------------------------------- > And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "bloatware". From owner-freebsd-stable Wed Dec 18 11:52:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23995 for stable-outgoing; Wed, 18 Dec 1996 11:52:28 -0800 (PST) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA23988 for ; Wed, 18 Dec 1996 11:52:25 -0800 (PST) Received: from stuyts by ns.NL.net (5.65b/NLnet1.3) id AA26369; Wed, 18 Dec 1996 20:48:13 +0100 Received: by daneel.stuyts.nl (NX5.67f2/daneel940629) id AA02152; Wed, 18 Dec 96 20:46:37 +0100 Message-Id: <9612181946.AA02152@daneel.stuyts.nl> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <20211.850869860@time.cdrom.com> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Wed, 18 Dec 96 20:46:32 +0100 To: freebsd-stable@FreeBSD.ORG Subject: Re: Solved: Install problem on second drive: panic can't mount / Reply-To: ben@stuyts.nl References: <20211.850869860@time.cdrom.com> Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks to all the people offering suggestions to the problem I described in an earlier mail. Just for the mailing list archives (I couldn't locate the problem there) I'll post the solution that Jordan K. Hubbard gave me: > Try the following line at the boot: prompt: > > 2:sd(0,a)/kernel > > I could be wrong about the offset, in which case try 1:sd(0,a)/kernel if > that doesn't work. In my case, I had to use 1:sd(0,a)/kernel. Best regards, Ben From owner-freebsd-stable Wed Dec 18 12:39:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA25585 for stable-outgoing; Wed, 18 Dec 1996 12:39:08 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA25566; Wed, 18 Dec 1996 12:38:53 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA03147; Wed, 18 Dec 1996 12:38:16 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma003145; Wed Dec 18 12:38:11 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id MAA19182; Wed, 18 Dec 1996 12:38:11 -0800 (PST) From: Archie Cobbs Message-Id: <199612182038.MAA19182@bubba.whistle.com> Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-Reply-To: from Charles Owens at "Dec 18, 96 08:00:23 am" To: owensc@enc.edu (Charles Owens) Date: Wed, 18 Dec 1996 12:38:11 -0800 (PST) Cc: sos@freebsd.org, luigi@labinfo.iet.unipi.it, julian@whistle.com, wangel@wgrobez1.remote.louisville.edu, dnex@access.digex.net, current@freebsd.org, stable@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-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ok... help me out here: the 'ipfilter' package is _not_ a userland > implementation, right? (just trying to put all of the pieces to gether > here...) > > Why do some folks consider the DIVERT sockets with userland daemon > approach better than other existing options, such as ipfilter? Or, more > directly, why might I not want to user ipfilter to build a firewall for a > large (hundreds of users) LAN? (pssst... not trying to start a war here) It depends on what you're doing... if you're only going to use it, then an integrated, debugged, fully functional kernel level implementation is ideal. If you plan on doing development, debugging, adding custom features, etc., or don't need high performance, then a user land version is probably preferable... at least until you get it all stable and working. The only point I would argue is that putting the filter/translation stuff inside the (user-land) ppp daemon combines the worst of both worlds. Rather than doing this, it would make more sense to separate it out into a standalone process (via divert sockets) so it can be used more generally than just with PPP (cf. subject line of this thread). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-stable Wed Dec 18 12:49:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA26359 for stable-outgoing; Wed, 18 Dec 1996 12:49:44 -0800 (PST) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA26342; Wed, 18 Dec 1996 12:49:35 -0800 (PST) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.4/8.7.5) id NAA04880; Wed, 18 Dec 1996 13:49:15 -0700 (MST) From: Softweyr LLC Message-Id: <199612182049.NAA04880@xmission.xmission.com> Subject: Re: IP masquerading (for a LAN, _not_ PPP) To: owensc@enc.edu (Charles Owens) Date: Wed, 18 Dec 1996 13:49:14 -0700 (MST) Cc: stable@freebsd.org, questions@freebsd.org Reply-To: questions@freebsd.org In-Reply-To: from "Charles Owens" at Dec 18, 96 08:00:23 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Owens recently asked: > Why do some folks consider the DIVERT sockets with userland daemon > approach better than other existing options, such as ipfilter? Or, more > directly, why might I not want to user ipfilter to build a firewall for a > large (hundreds of users) LAN? (pssst... not trying to start a war here) Simply because in userland, your filtering/forwarding rules can be much more complex. In kernel mode, all of the "options" for filtering or forwarding packets has to be available to the kernel code; in userland, the code can go "look up" things as it needs. If your needs for filter rules are pretty simple, a user-mode daemon is overkill. > I'm trying to discern which of the available options makes the most sense > for me... at this instant ipfilter seems the best bet --- feature rich and > good performance (I'm assuming... by virtue of it's kernel > implementation... any testimonials?). I'd use the ipfw package but I > really need NAT. If ipfilter meets your needs, you probably don't need the overhead of using divert sockets, yes. The divert socket mechanism is used for really complicated things, like creating a log of all traffic bound for network address 195.194.193.*. (Yow!) > If this should be moved out of -stable and -current then... sorry... :-) Followups in, and directed to, -questions. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com From owner-freebsd-stable Wed Dec 18 14:12:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA01233 for stable-outgoing; Wed, 18 Dec 1996 14:12:30 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA01228; Wed, 18 Dec 1996 14:12:21 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id OAA16528; Wed, 18 Dec 1996 14:11:47 -0800 (PST) To: Archie Cobbs cc: owensc@enc.edu (Charles Owens), sos@FreeBSD.org, luigi@labinfo.iet.unipi.it, julian@whistle.com, wangel@wgrobez1.remote.louisville.edu, dnex@access.digex.net, current@FreeBSD.org, stable@FreeBSD.org Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-reply-to: Your message of "Wed, 18 Dec 1996 12:38:11 PST." <199612182038.MAA19182@bubba.whistle.com> Date: Wed, 18 Dec 1996 14:11:46 -0800 Message-ID: <16515.850947106@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The only point I would argue is that putting the filter/translation > stuff inside the (user-land) ppp daemon combines the worst of both > worlds. Rather than doing this, it would make more sense to separate > it out into a standalone process (via divert sockets) so it can be > used more generally than just with PPP (cf. subject line of this thread). I don't think anyone has ever argued otherwise (conceptually, pulling NAT out of ppp makes sense for a lot of reasons!). This didn't stop a lot of people from needing something which worked in an adequate number of cases right now. :) Jordan From owner-freebsd-stable Wed Dec 18 19:42:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA27458 for stable-outgoing; Wed, 18 Dec 1996 19:42:19 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA27451; Wed, 18 Dec 1996 19:42:15 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.8.4/8.6.12) with SMTP id WAA14187; Wed, 18 Dec 1996 22:45:20 -0500 (EST) Date: Wed, 18 Dec 1996 22:45:19 -0500 (EST) From: Gary Roberts To: Charles Owens cc: DNEX , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: IP masquerading (for a LAN, _not_ PPP) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Dec 1996, Charles Owens wrote: > On Sun, 8 Dec 1996, Gary Roberts wrote: > > > On Sun, 8 Dec 1996, DNEX wrote: > > > > > Does FreeBSD support IP masquerading or are there plans to implement it? > > > > > > > Yes. It does. Charles Mott. Nice piece of software. Anyways, it's not > > a program like linux uses, it uses the PPP program. Check it out at: > > > > http://www.srv.net/~cmott/alias.html > > > This looks nifty, but I'm interested in doing masquerading on a firewall > for users on a large LAN, not dialing in via PPP. What's the status of > doing _this_ with FreeBSD? > > --- > ------------------------------------------------------------------------- > Charles Owens Email: owensc@enc.edu > "I read somewhere to learn is to > Information Technology Services remember... and I've learned that > Eastern Nazarene College we've all forgot..." - King's X > ------------------------------------------------------------------------- > That's exactly what I'm doing. Except I 'dial' out to the net with PPP. So, on my ISDN, I have like 25 machines firewalled, all routed via the ppp program. Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-stable Thu Dec 19 18:18:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA28864 for stable-outgoing; Thu, 19 Dec 1996 18:18:37 -0800 (PST) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA28859 for ; Thu, 19 Dec 1996 18:18:34 -0800 (PST) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.8.3/8.8.4) with SMTP id VAA20458 for ; Thu, 19 Dec 1996 21:18:32 -0500 (EST) Date: Thu, 19 Dec 1996 21:14:17 -0500 () From: Bradley Dunn To: freebsd-stable@freebsd.org Subject: "storage size of 'swaplist' is unknown' Message-ID: X-X-Sender: bradley@harborcom.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had a few ports (namely ucd-snmp and top) die during compile with the error referenced in the subject. Now I see pointers to swaplist referenced in the VM code, but I couldn't begin to understand that. I assume there is something with my kernel? The config is basically GENERIC with the unneeded devices commented out. This is a 2.1.6.1 box. Any tips? Thanks! -BD From owner-freebsd-stable Fri Dec 20 11:08:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA03524 for stable-outgoing; Fri, 20 Dec 1996 11:08:59 -0800 (PST) Received: from smtp02.worldbank.org (smtp02.worldbank.org [138.220.3.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA03476; Fri, 20 Dec 1996 11:08:47 -0800 (PST) Received: from bheema.worldbank.org by worldbank.org (PMDF V5.0-7 #16195) id <01ID8HVX3NFY9UNPZ6@worldbank.org>; Fri, 20 Dec 1996 14:07:51 -0500 (EST) Received: from localhost by bheema.worldbank.org; (5.65/1.1.8.2/28Jul95-0113PM) id AA04815; Fri, 20 Dec 1996 14:05:37 -0500 Date: Fri, 20 Dec 1996 15:05:36 -0400 (EDT) From: "Alok K. Dhir" Subject: Partitioning large disk for news... To: hackers@freebsd.org, questions@freebsd.org, stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all - I'm getting ready to install a Pro200 running FreeBSD 2.1.6.1 as our news server here at the World Bank, and have the following questions: I have a Seagate 9 gig disk to use as the news spool, and I'm wondering what the best way to use it will be (the / and /usr partitions are on a separate 2 gig disk). I remember in the past (way back in the 1.1.5.1 - 2.0 days) there was some trouble with partitions larger than 2 gigs. Is this still the case? If so, I'm thinking maybe I can use the ccd driver to serially concatenate 5 partitions on the disk together for use as one large news spool. Which of these options is likely to cause the least amount of headache for me? Thanks for any info - and please respond directly to me, if possible, since I am not subscribed to the lists (I get too much mail already...). Unrelated note: I recently had all sorts of trouble trying to get the BSDI version of Netscape 3.0 running on my 2.1.6.1 box. Turns out I had commented out the 'options "COMPAT_43"' line in my kernel conf file, and for some reason, BSDI (and Linux) compatibility won't work without it. Perhaps there should be mention of this in LINT. Thanks! -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ---------------------------------------------------------------------- | From owner-freebsd-stable Fri Dec 20 11:55:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA05591 for stable-outgoing; Fri, 20 Dec 1996 11:55:05 -0800 (PST) Received: from pegasus.my.domain (fish-13.ppp.hooked.net [206.80.10.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA05560; Fri, 20 Dec 1996 11:54:57 -0800 (PST) From: dicen@hooked.net Received: from pegasus.my.domain (localhost.my.domain [127.0.0.1]) by pegasus.my.domain (8.8.4/8.7.3) with SMTP id LAA21794; Fri, 20 Dec 1996 11:55:10 GMT Message-ID: <32BA7E9E.41C67EA6@hooked.net> Date: Fri, 20 Dec 1996 11:55:10 +0000 X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Problems with make world. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk make world fails for me on both the 2.2 alpha release and the current release. Output..... cc -O2 -m486 -pipe -I/usr/src_stable/src/usr.bin/make -c /usr/src_stable/src/usr.bin/make/lst.lib/lstSucc.c cc -O2 -m486 -pipe -I/usr/src_stable/src/usr.bin/make -o make arch.o buf.o compat.o cond.o dir.o for.o hash.o job.o main.o make.o parse.o str.o suff.o targ.o var.o util.o lstAppend.o lstAtEnd.o lstAtFront.o lstClose.o lstConcat.o lstDatum.o lstDeQueue.o lstDestroy.o lstDupl.o lstEnQueue.o lstFind.o lstFindFrom.o lstFirst.o lstForEach.o lstForEachFrom.o lstInit.o lstInsert.o lstIsAtEnd.o lstIsEmpty.o lstLast.o lstMember.o lstNext.o lstOpen.o lstRemove.o lstReplace.o lstSucc.o install -c -s -o bin -g bin -m 555 make /usr/bin pwd: No such file or directory *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I have a link for /usr/src_stable/src to /usr/src. It would do this even when the source was in /usr/src so that is not the problem. There is no pattern when the "pwd: No such file or directory" shows up. My path includes /bin /usr/bin /sbin /usr/sbin /usr/local/bin /usr/local/sbin. I have looked through the mk files but this has stumped me for a while now. dicen From owner-freebsd-stable Fri Dec 20 16:38:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA17213 for stable-outgoing; Fri, 20 Dec 1996 16:38:07 -0800 (PST) Received: from pegasus.my.domain (capt-4.ppp.hooked.net [206.80.9.132]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA17207; Fri, 20 Dec 1996 16:38:03 -0800 (PST) From: dicen@hooked.net Received: from pegasus.my.domain (localhost.my.domain [127.0.0.1]) by pegasus.my.domain (8.8.4/8.7.3) with SMTP id QAA24141; Fri, 20 Dec 1996 16:38:19 GMT Message-ID: <32BAC0FA.41C67EA6@hooked.net> Date: Fri, 20 Dec 1996 16:38:18 +0000 X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Problems with make world. References: <32BA7E9E.41C67EA6@hooked.net> <32BAFADA.62D5@netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Manfred Antar wrote: > > i have the same problem.it started when /bin/sh was changed a few days > ago.if you have a backup over a week old of /bin/sh use it . > hope this helps > Manfred > -- > |==============================| > | mantar@netcom.com | > | Ph. (415) 681-6235 | > |==============================| Just wanted to let everyone know /bin/sh is why a make world in current fails. However, it seams to be okay in 2.2alpha now that I got a make world to work from current down to 2.2alpha. A simple fix is this. make -DSHELL=/usr/local/bin/bash world. dicen From owner-freebsd-stable Fri Dec 20 22:39:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA28388 for stable-outgoing; Fri, 20 Dec 1996 22:39:18 -0800 (PST) Received: from pegasus.my.domain (bass-23.ppp.hooked.net [206.80.8.87]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA28377; Fri, 20 Dec 1996 22:39:13 -0800 (PST) From: dicen@hooked.net Received: from pegasus.my.domain (localhost.my.domain [127.0.0.1]) by pegasus.my.domain (8.8.4/8.7.3) with SMTP id WAA25823; Fri, 20 Dec 1996 22:39:30 GMT Message-ID: <32BB1559.41C67EA6@hooked.net> Date: Fri, 20 Dec 1996 22:39:30 +0000 X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: User ppp not hanging up modem. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk User ppp not hanging up modem. This seams to be a real annoying problem that a number of people have in current and 2.2alpha. I have read some posts on usenet about it. In relase 2.10 and 2.1.5 user ppp would hang up my modem on either a timeout or when I did a close command. Now it does neither. My hardware is an external SupraFaxModem 14.4k V.32bis connected on com2 with a DB25 cable. The modem will hangup fine in Windoze 95 but not in current or 2.2alpha. Since my modem is externel I can just turn it off to close a connect. I can't imagine what people do with internel modems. My system is top of the line, no crappy motherboard here. I just spent nearly 3 hours debuging user ppp. I can't find anything wrong with it. In ppp/modem.c HangupModem is called with the right argument value (flag) and as far as I can tell it is executing the code in the if then else blocks. However, it does appear the code has been changed (since the author) to make -dedicated ppp, which doesn't seam to work when you turn it on. There are comments in the function /* XXX */. I have sean that in the kernel code. Must be a call sign. To close the modem connection HangupModem calls close() (of course) and a number of termios routines. Man I hate termios. I haven't look in my Advanced Programming in the .... (Stevens book), the bible yet to figure out what they do. Have the libraries been touched? The termios stuff could be bugged. I need to add here that some peoples modems may be hanging up like they should. According to the logs and my debugging, user ppp is closing the ppp connection it just isn't hanging up the modem. If you have an Isp (I don't, but I used to) that is nice enough to hangup it's modem then yours will hangup too. I feel that this is something critical. Users with internel modems will not be able to terminate a connection without unpluging the modem cable from the back of their computers. dicen From owner-freebsd-stable Sat Dec 21 07:05:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA12162 for stable-outgoing; Sat, 21 Dec 1996 07:05:31 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA12123; Sat, 21 Dec 1996 07:05:24 -0800 (PST) Received: from professor.eng.umd.edu (professor.eng.umd.edu [129.2.103.23]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id KAA00896; Sat, 21 Dec 1996 10:05:21 -0500 (EST) Received: from localhost (chuckr@localhost) by professor.eng.umd.edu (8.8.3/8.7.3) with SMTP id KAA07408; Sat, 21 Dec 1996 10:05:21 -0500 (EST) X-Authentication-Warning: professor.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 21 Dec 1996 10:05:21 -0500 (EST) From: Chuck Robey X-Sender: chuckr@professor.eng.umd.edu To: dicen@hooked.net cc: freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. In-Reply-To: <32BB1559.41C67EA6@hooked.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Dec 1996 dicen@hooked.net wrote: > User ppp not hanging up modem. > > This seams to be a real annoying problem that a number of people have in > current and 2.2alpha. I have read some posts on usenet about it. In > relase 2.10 and 2.1.5 user ppp would hang up my modem on either a > timeout or when I did a close command. Now it does neither. > > My hardware is an external SupraFaxModem 14.4k V.32bis connected on com2 > with a DB25 cable. The modem will hangup fine in Windoze 95 but not in > current or 2.2alpha. Since my modem is externel I can just turn it off > to close a connect. I can't imagine what people do with internel modems. > My system is top of the line, no crappy motherboard here. > > I just spent nearly 3 hours debuging user ppp. I can't find anything > wrong with it. In ppp/modem.c HangupModem is called with the right > argument value (flag) and as far as I can tell it is executing the code > in the if then else blocks. However, it does appear the code has been > changed (since the author) to make -dedicated ppp, which doesn't seam to > work when you turn it on. There are comments in the function /* XXX */. > I have sean that in the kernel code. Must be a call sign. > > To close the modem connection HangupModem calls close() (of course) and > a number of termios routines. Man I hate termios. I haven't look in my > Advanced Programming in the .... (Stevens book), the bible yet to figure > out what they do. Have the libraries been touched? The termios stuff > could be bugged. > > I need to add here that some peoples modems may be hanging up like they > should. According to the logs and my debugging, user ppp is closing the > ppp connection it just isn't hanging up the modem. If you have an Isp (I > don't, but I used to) that is nice enough to hangup it's modem then > yours will hangup too. > > I feel that this is something critical. Users with internel modems will > not be able to terminate a connection without unpluging the modem cable > from the back of their computers. It hangs up fine for me, so what's the differences ... are you using DTR to hang up with? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-stable Sat Dec 21 09:14:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA16533 for stable-outgoing; Sat, 21 Dec 1996 09:14:18 -0800 (PST) Received: from pegasus.my.domain (tuna-41.ppp.hooked.net [206.80.8.169]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA16523; Sat, 21 Dec 1996 09:14:14 -0800 (PST) From: dicen@hooked.net Received: from pegasus.my.domain (localhost.my.domain [127.0.0.1]) by pegasus.my.domain (8.8.4/8.7.3) with SMTP id JAA00210; Sat, 21 Dec 1996 09:05:35 GMT Message-ID: <32BBA85F.41C67EA6@hooked.net> Date: Sat, 21 Dec 1996 09:05:35 +0000 X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-RELEASE i386) MIME-Version: 1.0 To: Chuck Robey CC: freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay I have an update on the modem. My modem is a SupraFaxModem 14.4k V.32bis externel sold for Macs. I got it not because I used to have a mac but because I needed that type of cable it came with. This modem is set by default not to do anything on a DTR transition. To hang it up you do the correct thing which is escape with "+++" and then execute ATH. User ppp only seams to cut the DTR. So I have now set the modem to be a PC type which will go into command state with a DTR transition. This introduces other problems. Since cutting DTR now doesn't reset the state of the modem, it just hangs it up, doing a redial right after will not work. You have to wait a couple seconds. I can issue special commands to the modem to fix this but these commands are not standard. Actually my modem practicaly has an OS in it, it is so complex. This really needs to be put in the FAQ. I would rather have an escape done "+++" and the an ATH to hang up the modem but atleast it works now. Is this code in the termios library? I haven't look in my books yet. I am posting this to questions, current and stable becuase it applies to all of them. You can configure majordomo not to send duplicate emails for different mail lists. It isn't that hard. Thanks for the help. dicen From owner-freebsd-stable Sat Dec 21 09:51:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA18134 for stable-outgoing; Sat, 21 Dec 1996 09:51:45 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA18096; Sat, 21 Dec 1996 09:51:36 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA27123; Sat, 21 Dec 1996 10:51:29 -0700 (MST) Date: Sat, 21 Dec 1996 10:51:29 -0700 (MST) Message-Id: <199612211751.KAA27123@rocky.mt.sri.com> From: Nate Williams To: dicen@hooked.net Cc: Chuck Robey , freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. In-Reply-To: <32BBA85F.41C67EA6@hooked.net> References: <32BBA85F.41C67EA6@hooked.net> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Okay I have an update on the modem. My modem is a SupraFaxModem 14.4k > V.32bis externel sold for Macs. I got it not because I used to have a > mac but because I needed that type of cable it came with. This modem is > set by default not to do anything on a DTR transition. To hang it up you > do the correct thing which is escape with "+++" and then execute ATH. > User ppp only seams to cut the DTR. That's *NOT* the correct thing. What happens when for some reason PPP happens to send the sequence '+++' to the modem? All of a sudden it'll drop into command mode and you're screwed. User-PPP (as well as all other PPP/SLIP implementations I've worked with) assumes that you've disabled the escape sequence at least temporarily. > So I have now set the modem to be a PC type which will go into command > state with a DTR transition. This introduces other problems. Since > cutting DTR now doesn't reset the state of the modem, it just hangs it > up, doing a redial right after will not work. You have to wait a couple > seconds. Umm, what's wrong with 'waiting' a couple of seconds? If the line goes down you should wait for the other end to clean up in any case, simply because you never know what caused the line to go down, and waiting 5-20 seconds might clear it up and allow you connect up the next time w/out having to retry. > I can issue special commands to the modem to fix this but these > commands are not standard. Actually my modem practicaly has an OS in > it, it is so complex. Umm, *every* modem that has been sold in the last couple years has the ability to reset itself when DTR goes low. That includes a *really* old Telebit modem from the late 80's or early 90's. > This really needs to be put in the FAQ. I would rather have an escape > done "+++" and the an ATH to hang up the modem but atleast it works now. > Is this code in the termios library? I haven't look in my books yet. This code isn't in any 'unix-like' system program that I'm aware of. The standard practice on unix machines 'since time began' has been to reset when DTR goes low. Most of this *is* already documented in the FreeBSD handbook. Nate From owner-freebsd-stable Sat Dec 21 09:58:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA18571 for stable-outgoing; Sat, 21 Dec 1996 09:58:25 -0800 (PST) Received: from pegasus.my.domain (tuna-41.ppp.hooked.net [206.80.8.169]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA18566; Sat, 21 Dec 1996 09:58:21 -0800 (PST) From: dicen@hooked.net Received: from pegasus.my.domain (localhost.my.domain [127.0.0.1]) by pegasus.my.domain (8.8.4/8.7.3) with SMTP id JAA16625; Sat, 21 Dec 1996 09:58:25 GMT Message-ID: <32BBB4C1.794BDF32@hooked.net> Date: Sat, 21 Dec 1996 09:58:25 +0000 X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-RELEASE i386) MIME-Version: 1.0 To: Nate Williams CC: Chuck Robey , freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. References: <32BBA85F.41C67EA6@hooked.net> <199612211751.KAA27123@rocky.mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > That's *NOT* the correct thing. What happens when for some reason > PPP happens to send the sequence '+++' to the modem? All of a sudden > it'll drop into command mode and you're screwed. User-PPP (as well as > all other PPP/SLIP implementations I've worked with) assumes that you've > disabled the escape sequence at least temporarily. > Interesting. But, what exactly is the prabobalitity of that? I will have think about this one. > Most of this *is* already documented in the FreeBSD handbook. > > Nate Nope. Nope. Nope. I have look through the entire /usr/share/doc tree and didn't find anything about ppp not hanging up modems, etc.. Someone please put this in the FAQ. I have read usenet posts about this one. Other people are going through the hell I did. I don't like spending hours debuging code only to discover the code is fine and my modem is misconfigured (sure I should have thought of it first). dicen From owner-freebsd-stable Sat Dec 21 15:02:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA06594 for stable-outgoing; Sat, 21 Dec 1996 15:02:24 -0800 (PST) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA06589 for ; Sat, 21 Dec 1996 15:02:22 -0800 (PST) Received: from baloon.mimi.com (sjx-ca25-02.ix.netcom.com [204.30.65.194]) by dfw-ix1.ix.netcom.com (8.6.13/8.6.12) with ESMTP id PAA26287; Sat, 21 Dec 1996 15:01:48 -0800 Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id PAA16541; Sat, 21 Dec 1996 15:01:45 -0800 (PST) Date: Sat, 21 Dec 1996 15:01:45 -0800 (PST) Message-Id: <199612212301.PAA16541@baloon.mimi.com> To: adhir@worldbank.org CC: stable@FreeBSD.ORG In-reply-to: (adhir@worldbank.org) Subject: Re: Partitioning large disk for news... From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (I don't know if you got any mail from -hackers or -questions readers, I trimmed the CC: down to -stable only. Please don't post a question to more than one list, thanks.) * I remember in the past (way back in the 1.1.5.1 - 2.0 days) there was some * trouble with partitions larger than 2 gigs. Is this still the case? I don't think so, we've been using some pretty big partitions (4 x 9GB, 16 x 9GB, etc.) and aside from the ahc-related crashes, haven't seen any problems. * If * so, I'm thinking maybe I can use the ccd driver to serially concatenate 5 * partitions on the disk together for use as one large news spool. (^_^;).... Whatever problems you may have, I'm pretty sure that using ccd that way won't help. The problems with large partitions were in the disklabel/filesystem code, which will still have to see the concatenated disk as one large partition anyway.... Satoshi From owner-freebsd-stable Sat Dec 21 15:52:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08436 for stable-outgoing; Sat, 21 Dec 1996 15:52:51 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08393; Sat, 21 Dec 1996 15:52:42 -0800 (PST) Received: from packet.eng.umd.edu (packet.eng.umd.edu [129.2.98.184]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id SAA06200; Sat, 21 Dec 1996 18:52:39 -0500 (EST) Received: from localhost (chuckr@localhost) by packet.eng.umd.edu (8.8.3/8.7.3) with SMTP id SAA24079; Sat, 21 Dec 1996 18:52:38 -0500 (EST) X-Authentication-Warning: packet.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 21 Dec 1996 18:52:38 -0500 (EST) From: Chuck Robey X-Sender: chuckr@packet.eng.umd.edu To: dicen@hooked.net cc: Nate Williams , freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. In-Reply-To: <32BBB4C1.794BDF32@hooked.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Dec 1996 dicen@hooked.net wrote: > Nate Williams wrote: > > > > > That's *NOT* the correct thing. What happens when for some reason > > PPP happens to send the sequence '+++' to the modem? All of a sudden > > it'll drop into command mode and you're screwed. User-PPP (as well as > > all other PPP/SLIP implementations I've worked with) assumes that you've > > disabled the escape sequence at least temporarily. > > > Interesting. But, what exactly is the prabobalitity of that? I will have > think about this one. Note that the standard command "&D3" tells the modem to reset itself when DTR drops. Nate's right, this _is_ standard. What he missed was that Hayes modems (Hayes originated the protocol that's now a defacto standard) used to get around the +++ transparency issue by requiring a 2 second dead time (either before or after the +++ code, I forget which). Hayes patented that delay, I think, which is why modems don't use it anymore. > > > > Most of this *is* already documented in the FreeBSD handbook. > > > > Nate > Nope. Nope. Nope. Yes, section 11.3.6. Nate's right. I have look through the entire /usr/share/doc tree and > didn't find anything about ppp not hanging up modems, etc.. Someone > please put this in the FAQ. I have read usenet posts about this one. > Other people are going through the hell I did. I don't like spending > hours debuging code only to discover the code is fine and my modem is > misconfigured (sure I should have thought of it first). > > dicen > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-stable Sat Dec 21 17:57:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA13257 for stable-outgoing; Sat, 21 Dec 1996 17:57:32 -0800 (PST) Received: from eldorado.net-tel.co.uk ([193.122.171.253]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA13252; Sat, 21 Dec 1996 17:57:27 -0800 (PST) From: Andrew.Gordon@net-tel.co.uk Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id BAA23200; Sun, 22 Dec 1996 01:56:52 GMT Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk (Route400-RFCGate); Sun, 22 Dec 96 1:55:15 +0000 X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Sun, 22 Dec 96 1:55:15 +0000 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Sun, 22 Dec 96 1:55:13 +0000 X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; Sun, 22 Dec 96 1:55:13 +0000 X400-MTS-Identifier: ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:21271-961222015513-12AB] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: non-disclosure:; Date: Sun, 22 Dec 96 1:55:13 +0000 X400-Content-Identifier: Re(2): User ppp Message-Id: <"84a-961222015526-FEB1*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS> To: list:; Cc: freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: Subject: Re(2): User ppp not hanging up modem. Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Sat, 21 Dec 1996 dicen@hooked.net wrote: > > Nate Williams wrote: > > > That's *NOT* the correct thing. What happens when for some reason > > > PPP happens to send the sequence '+++' to the modem? All of a sudden > > > it'll drop into command mode and you're screwed. User-PPP (as well as > > > all other PPP/SLIP implementations I've worked with) assumes that > you've > > > disabled the escape sequence at least temporarily. > > > > > Interesting. But, what exactly is the prabobalitity of that? I will have > > think about this one. > > Note that the standard command "&D3" tells the modem to reset itself when > DTR drops. Nate's right, this _is_ standard. What he missed was that > Hayes modems (Hayes originated the protocol that's now a defacto standard) > used to get around the +++ transparency issue by requiring a 2 second dead > time (either before or after the +++ code, I forget which). Before _and_ after - hence you are safe even if a packet begins or ends with "+++". > Hayes > patented that delay, I think, which is why modems don't use it anymore. Good modems still do (USR Courier for example) - presumably having licenced with Hayes. Some junk modems don't..... From owner-freebsd-stable Sat Dec 21 19:17:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA15720 for stable-outgoing; Sat, 21 Dec 1996 19:17:31 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA15678; Sat, 21 Dec 1996 19:17:18 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id OAA15734; Sun, 22 Dec 1996 14:17:00 +1100 (EST) Message-ID: Date: Sun, 22 Dec 1996 14:16:59 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: dicen@hooked.net Cc: nate@mt.sri.com (Nate Williams), chuckr@glue.umd.edu (Chuck Robey), freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. References: <32BBA85F.41C67EA6@hooked.net> <199612211751.KAA27123@rocky.mt.sri.com> <32BBB4C1.794BDF32@hooked.net> X-Mailer: Mutt 0.54 Mime-Version: 1.0 In-Reply-To: <32BBB4C1.794BDF32@hooked.net>; from dicen@hooked.net on Dec 21, 1996 09:58:25 +0000 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk dicen@hooked.net writes: >> That's *NOT* the correct thing. What happens when for some reason >> PPP happens to send the sequence '+++' to the modem? All of a sudden >> it'll drop into command mode and you're screwed. User-PPP (as well as >> all other PPP/SLIP implementations I've worked with) assumes that you've >> disabled the escape sequence at least temporarily. > > Interesting. But, what exactly is the prabobalitity of that? I will have > think about this one. The probability of it happening is very very small, given that there must also be a two minute "silence" from the DTE both before and after the '+++' sequence. The actual delay required is usually register configurable. David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-stable Sat Dec 21 19:50:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA16604 for stable-outgoing; Sat, 21 Dec 1996 19:50:31 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA16570; Sat, 21 Dec 1996 19:50:20 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id OAA15781; Sun, 22 Dec 1996 14:50:10 +1100 (EST) Message-ID: Date: Sun, 22 Dec 1996 14:50:10 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: davidn@sdev.usn.blaze.net.au (David Nugent) Cc: dicen@hooked.net, nate@mt.sri.com (Nate Williams), chuckr@glue.umd.edu (Chuck Robey), freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: User ppp not hanging up modem. References: <32BBA85F.41C67EA6@hooked.net> <199612211751.KAA27123@rocky.mt.sri.com> <32BBB4C1.794BDF32@hooked.net> X-Mailer: Mutt 0.54 Mime-Version: 1.0 In-Reply-To: ; from David Nugent on Dec 22, 1996 14:16:59 +1100 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Following up my own post. :-) David Nugent writes: > > Interesting. But, what exactly is the prabobalitity of that? I will have > > think about this one. > > The probability of it happening is very very small, given that > there must also be a two minute "silence" from the DTE both before two /minute/? Sheesh, get off the tap water. I meant seconds. And I believe Michael is correct that 0.5 seconds is the standard setting - I've always raised it as a matter of course. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/