From owner-freebsd-isp Sun Mar 17 16:01:33 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15938 for isp-outgoing; Sun, 17 Mar 1996 16:01:33 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA15927 Sun, 17 Mar 1996 16:01:31 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id SAA25321; Sun, 17 Mar 1996 18:00:15 -0600 From: Joe Greco Message-Id: <199603180000.SAA25321@brasil.moneng.mei.com> Subject: Re: comtrol rocketports To: michael@memra.com (Michael Dillon) Date: Sun, 17 Mar 1996 18:00:15 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, erich@basenet.com, freebsd-hardware@FreeBSD.org, freebsd-isp@FreeBSD.org In-Reply-To: from "Michael Dillon" at Mar 16, 96 11:39:35 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > And what's wrong with building special-purpose terminal servers out of > Linux boxes and using FreeBSD for all the other servers? After all, Linux > is UNIX too and all a terminal server needs to do is run a bunch of serial > ports and maybe a few rlogins to a FreeBSD shell server. In a word: "reliability". ... JG From owner-freebsd-isp Mon Mar 18 07:56:52 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA01289 for isp-outgoing; Mon, 18 Mar 1996 07:56:52 -0800 (PST) Received: from bacall.lodgenet.com ([205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA01262 Mon, 18 Mar 1996 07:56:37 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA07629; Mon, 18 Mar 1996 09:51:49 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma007627; Mon Mar 18 09:51:40 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id IAA26905; Mon, 18 Mar 1996 08:52:09 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.4/8.6.12) with SMTP id JAA04029; Mon, 18 Mar 1996 09:04:13 -0600 (CST) Message-Id: <199603181504.JAA04029@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Joe Greco cc: erich@basenet.com (Eric Hester), freebsd-hardware@FreeBSD.org, freebsd-isp@FreeBSD.org Subject: Re: comtrol rocketports In-reply-to: Your message of "Sat, 16 Mar 1996 09:45:46 CST." <199603161545.JAA24201@brasil.moneng.mei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Mar 1996 09:04:13 -0600 From: "Eric L. Hernes" Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk We've been bombarded by serial vendors in the last 4 months or so. We are currently buying digi pc/8e's; we buy between 75 - 100 cards a month for our systems. We're in the process of migrating from SCO to FreeBSD. We've talked to digi, stallion, equinox, and comtrol, and maybe others. The salesman from comtrol was really excited about his card and wanted to send an engineer up to visit us and really show off their cards, I told him that he'd do better to get me a FreeBSD driver before he sent an engineer here; we haven't heard from him since :( At any rate I've personally seen the following intelligent serial cards work: Digi: PC/8e -- works quite well from what I've seen; a little more cpu intensive under FBSD than SCO, but works good. I've used both 64k and 8k windowed cards. Stallion: EasyConnect AT and PCI -- works very well, driver is actively worked on by a stallion employee! I'm gonna push for a switch to this one when we finally make the switch to FBSD. These support up to 32 ports from one isa/pci slot. EasyIO -- This is the moderately intelligent card based on the Cirrus CD1440 chip. The card is very similar to the Cyclades 8Y, RJ12's off the back (probably available in db{9,25} too). this card is cheap $200/8ports. Cyclades: 8Y -- I've seen it work. Didn't really beat on it, but it works. It's in the $200 price range. I've seen a few messages regarding the comtrol cards. Someone (julian?) indicated that comtrol isn't too bad a company to work with as far as getting programming specs and sample sources. Getting a working driver should only be a 2-3 week project provided one is a driver hacker, and has access to hardware and docs; oh yea and has that much free time. ;-) eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-isp Mon Mar 18 12:25:27 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07327 for isp-outgoing; Mon, 18 Mar 1996 12:25:27 -0800 (PST) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA07306 Mon, 18 Mar 1996 12:25:22 -0800 (PST) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id PAA01382; Mon, 18 Mar 1996 15:25:38 -0500 Date: Mon, 18 Mar 1996 15:25:38 -0500 Message-Id: <199603182025.PAA01382@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (dennis) Subject: Re: Microsoft "Get ISDN"? Cc: hackers@freebsd.org, freebsd-isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> On Sat, 16 Mar 1996, dennis wrote: >> > >> > I still find it terribly interesting that people will spend a fortune >> > on horsepower of questionable necessity (like P6s and 166Mhz cpus to >> > run a terminal server) but want to use $30. async cards for the most >> > important bottleneck in their network. >> >> People will always be doing this because the level of knowledge >> required to make intelligent hardware purchases is beyond the average >> consumer. I agree with you, an ISP who sticks a bunch of high-speed >> serial ports connected to a bunch of Bitsurfrs to provide ISDN access >> is just asking for trouble. > There's nothing wrong with using bitsurfer....the issue that we were talking about was whether you run the data piece of the puzzle at 115,200 (minus the overhead) async or 128kbs sync. Same physical issues...just a different scenario. If I thought that people would use them I think a $195. sync solution (paired with a $265. bitsurfer would be a very efficient full 128kbs solution). But I don't think enough people would use it. Noone understands sync....and most isps wouldnt know how to sell it. Its amazing how many people pay lots extra for 28.8 modems but you cant convince them to pay (anything hardly) to get 30% more throughput. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-isp Mon Mar 18 13:04:46 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA14853 for isp-outgoing; Mon, 18 Mar 1996 13:04:46 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA14838 for ; Mon, 18 Mar 1996 13:04:42 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA26269; Mon, 18 Mar 1996 15:02:50 -0600 From: Joe Greco Message-Id: <199603182102.PAA26269@brasil.moneng.mei.com> Subject: Re: Microsoft "Get ISDN"? To: dennis@etinc.com (dennis) Date: Mon, 18 Mar 1996 15:02:49 -0600 (CST) Cc: isp@freebsd.org In-Reply-To: <199603182025.PAA01382@etinc.com> from "dennis" at Mar 18, 96 03:25:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ cc: list trimmed somewhat ] > >> People will always be doing this because the level of knowledge > >> required to make intelligent hardware purchases is beyond the average > >> consumer. I agree with you, an ISP who sticks a bunch of high-speed > >> serial ports connected to a bunch of Bitsurfrs to provide ISDN access > >> is just asking for trouble. > > There's nothing wrong with using bitsurfer....the issue that we were talking > about > was whether you run the data piece of the puzzle at 115,200 (minus the overhead) > async or 128kbs sync. Same physical issues...just a different scenario. > > If I thought that people would use them I think a $195. sync solution > (paired with a > $265. bitsurfer would be a very efficient full 128kbs solution). But I don't > think enough > people would use it. Noone understands sync....and most isps wouldnt know how > to sell it. Its amazing how many people pay lots extra for 28.8 modems but > you cant > convince them to pay (anything hardly) to get 30% more throughput. Yes, this is very true. I'd love to see folks selling sync ISDN connections. Perhaps part of the problem is that it isn't readily apparent to folks that the difference isn't just between "115k" and "128k", which at first glance seems to be a 13k (~1K/s) difference. With async requiring 10 bits and sync requiring 8 bits, it is more like a 4K/s difference, and the difference between 10K/s and 14K/s is appreciable. At that point, considering the cost of the communications equipment itself is about $300, arguing an additional $200 for a sync serial card to gain roughly 40% more (66% more cost for 40% return) bandwidth would not be totally out of line. Arguing an additional $440 - the lowest currently priced ET card, discounted, I could find - would be unreasonable, since it would be adding 146% more cost for a 40% return... at that point, it's easier to buy a second TA and ISDN circuit for 230k bandwidth. Other issues potentially include authentication questions (which are easy to deal with via 'login')... people don't like change. :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-isp Mon Mar 18 13:35:38 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21319 for isp-outgoing; Mon, 18 Mar 1996 13:35:38 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21286 for ; Mon, 18 Mar 1996 13:35:31 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA26418; Mon, 18 Mar 1996 15:32:25 -0600 From: Joe Greco Message-Id: <199603182132.PAA26418@brasil.moneng.mei.com> Subject: Re: Microsoft "Get ISDN"? To: dennis@etinc.com (dennis) Date: Mon, 18 Mar 1996 15:32:25 -0600 (CST) Cc: freebsd-isp@freefall.FreeBSD.org In-Reply-To: <199603182118.QAA01485@etinc.com> from "dennis" at Mar 18, 96 04:18:42 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Other issues potentially include authentication questions (which are easy to > >deal with via 'login')... people don't like change. :-) > > Is this what you're doing? Why wouldnt you just use PAP? Because the whole world is NOT PPP. Some is SLIP - some is direct dialin - etc. For example, I run all my dedicated connections via SLIP. Or... it's really nice to be able to dial into Exec-PC (world's largest BBS) and download files at ISDN speeds. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-isp Mon Mar 18 16:48:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA17424 for isp-outgoing; Mon, 18 Mar 1996 16:48:35 -0800 (PST) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA17415 for ; Mon, 18 Mar 1996 16:48:27 -0800 (PST) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id TAA02045 for ; Mon, 18 Mar 1996 19:50:43 -0500 Date: Mon, 18 Mar 1996 19:50:43 -0500 Message-Id: <199603190050.TAA02045@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-isp@freebsd.org From: dennis@etinc.com (dennis) Subject: Advanced Bandwidth and Traffic Mgt Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Emerging Technologies today announces the release of new software which adds several powerful management features to their line of synchronous router cards. The new software substantially increases the control of traffic and bandwidth for both internet service providers and end users. New features include: - Non-destructive Bandwidth Limiting control (Simulation) on a Line/DLCI basis - Highly selective data prioritization and 3-tier priority queuing - TOS queue prioritization - queuing thresholds - Intelligent DE-bit enable for Frame Relay data packets - Adaptive frame relay congestion management and improved CIR adaptation - Throughput and Utilization monitoring on a line/DLCI basis - Selective, ultra-low overhead data filtering on a line/DLCI basis for firewalling - Intruder logging by data type - bpfilters are now working properly Coming Soon: Load Balancing and Multilink PPP (MP) for high speed sync lines. The new software is currently available for FreeBSD 2.1R, Linux 1.2.13 and BSD/OS 2.1 operating systems Additional information is available at www.etinc.com From owner-freebsd-isp Mon Mar 18 17:57:07 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA21395 for isp-outgoing; Mon, 18 Mar 1996 17:57:07 -0800 (PST) Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA21390 Mon, 18 Mar 1996 17:57:05 -0800 (PST) Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id SAA20972; Mon, 18 Mar 1996 18:01:50 -0800 From: Brian Litzinger Message-Id: <199603190201.SAA20972@MediaCity.com> Subject: Re: sync To: dennis@etinc.com (dennis) Date: Mon, 18 Mar 1996 18:01:49 -0800 (PST) Cc: jgreco@brasil.moneng.mei.com, hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-Reply-To: <199603182025.PAA01382@etinc.com> from dennis at "Mar 18, 96 03:25:38 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk dennis wrote: > >> > I still find it terribly interesting that people will spend a fortune > >> > on horsepower of questionable necessity (like P6s and 166Mhz cpus to > >> > run a terminal server) but want to use $30. async cards for the most > >> > important bottleneck in their network. > > If I thought that people would use them I think a $195. sync solution > (paired with a > $265. bitsurfer would be a very efficient full 128kbs solution). But I don't > think enough > Dennis I do. Used to program Z8530's in my sleep for DUAL DMA operation to run video teleconferencing at 3MBits/sec via satelite. was real cool. I was thinking of the doing a driver for the Z8530, there is support for it in Linux. On the other hand, how much trouble would it be to hook a BSPro to one of your cards? I was going to try, but now I can just ask you. -- Brian Litzinger Powered by FreeBSD http[s]://www.mpress.com Unlike Hitler, who brought the Jews to the furnace, Clinton brought the furnace to the Branch Davidians. From owner-freebsd-isp Mon Mar 18 20:37:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA04114 for isp-outgoing; Mon, 18 Mar 1996 20:37:23 -0800 (PST) Received: from fyeung5.netific.com (netific.vip.best.com [205.149.182.145]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA04014 Mon, 18 Mar 1996 20:35:59 -0800 (PST) Received: (from fyeung@localhost) by fyeung5.netific.com (8.6.11/8.6.9) id UAA18714; Mon, 18 Mar 1996 20:35:10 GMT From: francis yeung Message-Id: <199603182035.UAA18714@fyeung5.netific.com> Subject: DHCP To: freebsd-questions@freebsd.org Date: Mon, 18 Mar 1996 20:35:10 +0000 () Cc: freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Does any one has any experience running DHCP in FreeBSD serving Windows 3.11 or Windows 95 clients ? All the packets exchange seems to be normal but Windows does not like the response message from FreeBSD's DHCP ? Francis From owner-freebsd-isp Tue Mar 19 00:06:28 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13083 for isp-outgoing; Tue, 19 Mar 1996 00:06:28 -0800 (PST) Received: from tyger.inna.net (root@tyger.inna.net [206.151.66.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA13078 for ; Tue, 19 Mar 1996 00:06:25 -0800 (PST) Received: from caught.inna.net (caught.inna.net [206.151.66.7]) by tyger.inna.net (8.7.3/8.7.3) with SMTP id DAA12621; Tue, 19 Mar 1996 03:06:31 -0500 (EST) Date: Tue, 19 Mar 1996 03:04:07 -0500 (EST) From: Thomas Arnold To: Joe Greco cc: dennis , freebsd-isp@freefall.freebsd.org Subject: Re: Microsoft "Get ISDN"? In-Reply-To: <199603182132.PAA26418@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Mar 1996, Joe Greco wrote: > Because the whole world is NOT PPP. Some is SLIP - some is direct dialin - > etc. For example, I run all my dedicated connections via SLIP. Or... > it's really nice to be able to dial into Exec-PC (world's largest BBS) and > download files at ISDN speeds. I am curious, why do you use SLIP for your dedicated connections? +-----------------------------------------------+ : Tom Arnold - No relation to Rosanne : : SysAdmin/Pres - TBI, Ltd ( inna.net ) : : An ISP serving the Virginia Middle Penninsula : +-----------------------------------------------+ From owner-freebsd-isp Tue Mar 19 00:50:07 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA15018 for isp-outgoing; Tue, 19 Mar 1996 00:50:07 -0800 (PST) Received: from asia2.aan.net (tsuwei@aaa.net [206.135.33.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA15013 Tue, 19 Mar 1996 00:50:05 -0800 (PST) Received: (from tsuwei@localhost) by asia2.aan.net (8.6.12/8.6.9) id AAA11393; Tue, 19 Mar 1996 00:52:50 -0800 From: Tsuwei Chen Message-Id: <199603190852.AAA11393@asia2.aan.net> Subject: Re: DHCP To: fyeung@fyeung5.netific.com (francis yeung) Date: Tue, 19 Mar 1996 00:52:49 -0800 (PST) Cc: freebsd-questions@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: <199603182035.UAA18714@fyeung5.netific.com> from "francis yeung" at Mar 18, 96 08:35:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Greetings, > > Does any one has any experience running DHCP in FreeBSD serving > Windows 3.11 or Windows 95 clients ? > > All the packets exchange seems to be normal but Windows does > not like the response message from FreeBSD's DHCP ? > > Francis > > We use FreeBSD with BOOTP-DD2.4.3 to serve as DHCP server for our PCs that runing WFW and Win95. We only installed it less then a week. All the Win95 PC seem running well, but some of WFW PCs give us error messages from time to time. They complain that they can't lease an IP from DHCP server, while the server is always running. I noticed that most of time it happened when user run DOS shell but it also happens when user runing memory intensive applications. I doubt this might be caused by not enough CPU time allocated to background process. Any one has similar experience? Thanks, Tsuwei From owner-freebsd-isp Tue Mar 19 06:22:17 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02803 for isp-outgoing; Tue, 19 Mar 1996 06:22:17 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA02797 for ; Tue, 19 Mar 1996 06:22:14 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA27222; Tue, 19 Mar 1996 08:20:57 -0600 From: Joe Greco Message-Id: <199603191420.IAA27222@brasil.moneng.mei.com> Subject: Re: Microsoft "Get ISDN"? To: tom@inna.net (Thomas Arnold) Date: Tue, 19 Mar 1996 08:20:56 -0600 (CST) Cc: freebsd-isp@freefall.FreeBSD.org In-Reply-To: from "Thomas Arnold" at Mar 19, 96 03:04:07 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, 18 Mar 1996, Joe Greco wrote: > > Because the whole world is NOT PPP. Some is SLIP - some is direct dialin - > > etc. For example, I run all my dedicated connections via SLIP. Or... > > it's really nice to be able to dial into Exec-PC (world's largest BBS) and > > download files at ISDN speeds. > > I am curious, why do you use SLIP for your dedicated connections? Less potential BS to debug. I like the interface afforded by "startslip" and "sliplogin". It (used to be?) is very difficult to do all sorts of nifty routing things with PPP that I find relatively easy to do with SLIP. And maybe I just really really don't like gratuitous change. I hacked startslip to do all the things I wanted, and I made it work with FreeBSD (it came along for free from 4.4-Lite, but it was quite busted). It works great, it's reliable, and I have yet to hear a convincing reason to go to all sorts of work to re-engineer things to work with PPP, which I have witnessed in the past to be mildly buggy and problematic. Userland PPP can only do a small number of interfaces, handles flooding poorly, etc. Kernelland PPP used to panic my boxes, although admittedly that was under 2.0R. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-isp Tue Mar 19 07:47:31 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA10019 for isp-outgoing; Tue, 19 Mar 1996 07:47:31 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA10012 for ; Tue, 19 Mar 1996 07:47:27 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA04017; Tue, 19 Mar 1996 08:50:13 -0700 Date: Tue, 19 Mar 1996 08:50:13 -0700 From: Nate Williams Message-Id: <199603191550.IAA04017@rocky.sri.MT.net> To: Thomas Arnold Cc: Joe Greco , freebsd-isp@freefall.freebsd.org Subject: Re: Microsoft "Get ISDN"? In-Reply-To: References: <199603182132.PAA26418@brasil.moneng.mei.com> Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thomas Arnold writes: > On Mon, 18 Mar 1996, Joe Greco wrote: > > Because the whole world is NOT PPP. Some is SLIP - some is direct dialin - > > etc. For example, I run all my dedicated connections via SLIP. Or... > > it's really nice to be able to dial into Exec-PC (world's largest BBS) and > > download files at ISDN speeds. > > I am curious, why do you use SLIP for your dedicated connections? I don't speak for Joe, but I use SLIP (w/VJ compression) whenever possible since it uses less overhead and I seem to have lower latency and higher throughput than using both user-mode and kernel-mode PPP on FreeBSD boxes. Nate From owner-freebsd-isp Tue Mar 19 08:35:44 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA13609 for isp-outgoing; Tue, 19 Mar 1996 08:35:44 -0800 (PST) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA13485 Tue, 19 Mar 1996 08:34:53 -0800 (PST) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA03328; Tue, 19 Mar 1996 11:37:15 -0500 Date: Tue, 19 Mar 1996 11:37:15 -0500 Message-Id: <199603191637.LAA03328@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (dennis) Subject: Re: ISDN: "modem" or board? (Was: Microsoft "Get ISDN"?) Cc: freebsd-isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Well, I've been away from the list for a few days, and so much has >come in that I don't think it would make sense to respond to each >message individually, so here's a summary: > >1. Speed of a connection. Some people say "the bottleneck is the B > channel, so you can use async instead". This is the funniest thing I've ever heard......LOL dennis From owner-freebsd-isp Tue Mar 19 18:06:04 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA20877 for isp-outgoing; Tue, 19 Mar 1996 18:06:04 -0800 (PST) Received: from solar.os.com (root@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA20872 for ; Tue, 19 Mar 1996 18:06:00 -0800 (PST) Received: from jupiter (jupiter.os.com [199.232.136.66]) by solar.os.com (8.7/8.7.0) with SMTP id VAA18547 for ; Tue, 19 Mar 1996 21:27:39 -0500 Message-Id: <199603200227.VAA18547@solar.os.com> X-Sender: craigs@solar X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 19 Mar 1996 21:03:16 -0500 To: freebsd-isp@freebsd.org From: craigs@os.com (Craig Shrimpton) Subject: Re: ISDN: "modem" or board? (Was: Microsoft "Get ISDN"?) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Well, I've been away from the list for a few days, and so much has >>come in that I don't think it would make sense to respond to each >>message individually, so here's a summary: >> >>1. Speed of a connection. Some people say "the bottleneck is the B >> channel, so you can use async instead". > >This is the funniest thing I've ever heard......LOL > I can't for the life of me figure out what he meant by that. Maybe it has something to do with running the B channel in voice mode and having the Bitsurfer refuse to switch to 64K on both channels. The comment is a complete non-sequiter! -Craig =================================================================== Orbit Internet Email: craigs@os.com 400 Grove Street Phone: (508) 753-8776 Worcester, MA 01605 http://www.os.com/ From owner-freebsd-isp Wed Mar 20 10:21:11 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22375 for isp-outgoing; Wed, 20 Mar 1996 10:21:11 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA22365 for ; Wed, 20 Mar 1996 10:20:39 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA29896; Wed, 20 Mar 1996 12:19:41 -0600 From: Joe Greco Message-Id: <199603201819.MAA29896@brasil.moneng.mei.com> Subject: Re: Microsoft "Get ISDN"? To: nate@sri.MT.net (Nate Williams) Date: Wed, 20 Mar 1996 12:19:40 -0600 (CST) Cc: freebsd-isp@freefall.FreeBSD.org In-Reply-To: <199603191550.IAA04017@rocky.sri.MT.net> from "Nate Williams" at Mar 19, 96 08:50:13 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I am curious, why do you use SLIP for your dedicated connections? > > I don't speak for Joe, but I use SLIP (w/VJ compression) whenever > possible since it uses less overhead and I seem to have lower latency > and higher throughput than using both user-mode and kernel-mode PPP on > FreeBSD boxes. I don't have anything to say about higher throughput since in my experience it's only a mild difference, but the latency issue is mainly due to ppp's default 1500 mtu. Lowering that (I know one fella who uses 296) will help latency issues quite a bit. With 1500, you only get two or three packets per second through the link if somebody is running a large transfer of some sort. Most sites which run dedicated connections will have multiple people using the link simultaneously, so the lower mtu gives the impression of faster response. This hurts overall throughput mildly, buuuuut there's always a tradeoff to be made. fyi: SLIP uses a 552 mtu. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-isp Wed Mar 20 11:28:29 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA26303 for isp-outgoing; Wed, 20 Mar 1996 11:28:29 -0800 (PST) Received: from itchy.mosquito.com (itchy.mosquito.com [206.205.132.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA26298 for ; Wed, 20 Mar 1996 11:28:27 -0800 (PST) Received: (from boot@localhost) by itchy.mosquito.com (8.6.11/8.6.12) id OAA25770; Wed, 20 Mar 1996 14:29:18 -0500 From: Bruce Bauman Message-Id: <199603201929.OAA25770@itchy.mosquito.com> Subject: Netscape 2 question To: freebsd-isp@freebsd.org Date: Wed, 20 Mar 1996 14:29:18 -0500 (EST) Cc: boot@itchy.mosquito.com (Bruce Bauman) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I run Netscape 2.0 on my 2.1-stable system, the w command shows the command name as gibberish. Is there a fix for this? Here's the output on my system: 2:26PM up 8 days, 6:59, 4 users, load averages: 0.08, 0.02, 0.01 USER TTY FROM LOGIN@ IDLE WHAT boot p0 :0.0 12Mar96 - (w) boot p1 :0.0 12Mar96 1:55 (csh) boot p2 :0.0 12Mar96 3:12 U\M^I\M-eWVS\M^M]\^D\M^Ms\^D\M^I\M-w <- this is Netscape boot p3 :0.0 12Mar96 2:39 (csh) This is a machine running a 2.1-stable kernel, but most of the commands and libraries are still 2.0.5. From owner-freebsd-isp Wed Mar 20 12:16:24 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA00778 for isp-outgoing; Wed, 20 Mar 1996 12:16:24 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA00751 for ; Wed, 20 Mar 1996 12:16:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id MAA03338; Wed, 20 Mar 1996 12:14:40 -0800 Message-Id: <199603202014.MAA03338@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Joe Greco cc: nate@sri.MT.net (Nate Williams), freebsd-isp@freefall.freebsd.org Subject: Re: Microsoft "Get ISDN"? In-reply-to: Your message of "Wed, 20 Mar 1996 12:19:40 CST." <199603201819.MAA29896@brasil.moneng.mei.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 20 Mar 1996 12:14:40 -0800 Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > I am curious, why do you use SLIP for your dedicated connections? >> >> I don't speak for Joe, but I use SLIP (w/VJ compression) whenever >> possible since it uses less overhead and I seem to have lower latency >> and higher throughput than using both user-mode and kernel-mode PPP on >> FreeBSD boxes. > >I don't have anything to say about higher throughput since in my experience >it's only a mild difference, but the latency issue is mainly due to ppp's >default 1500 mtu. Lowering that (I know one fella who uses 296) will help >latency issues quite a bit. With 1500, you only get two or three packets >per second through the link if somebody is running a large transfer of some >sort. > >Most sites which run dedicated connections will have multiple people using >the link simultaneously, so the lower mtu gives the impression of faster >response. This hurts overall throughput mildly, buuuuut there's always a >tradeoff to be made. > >fyi: SLIP uses a 552 mtu. While this is true when using traditional modems, it is far less true when using modern modems with data compression. The modems themselves buffer a potentially large amount of data (1Kb or more of compressed data), and this will often make small MTUs perform worse in all respects because of the higher packet overhead. I know this through direct experimentation with different MTU values on several different 28.8K modems and the results of that are how I came up with the 552 value that we are currently using in FreeBSD. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Wed Mar 20 13:10:10 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA04040 for isp-outgoing; Wed, 20 Mar 1996 13:10:10 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA04033 for ; Wed, 20 Mar 1996 13:10:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id NAA03434; Wed, 20 Mar 1996 13:09:55 -0800 Message-Id: <199603202109.NAA03434@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Bruce Bauman cc: freebsd-isp@FreeBSD.ORG Subject: Re: Netscape 2 question In-reply-to: Your message of "Wed, 20 Mar 1996 14:29:18 EST." <199603201929.OAA25770@itchy.mosquito.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 20 Mar 1996 13:09:55 -0800 Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >When I run Netscape 2.0 on my 2.1-stable system, the w command shows the >command name as gibberish. Is there a fix for this? > >Here's the output on my system: > > 2:26PM up 8 days, 6:59, 4 users, load averages: 0.08, 0.02, 0.01 > USER TTY FROM LOGIN@ IDLE WHAT > boot p0 :0.0 12Mar96 - (w) > boot p1 :0.0 12Mar96 1:55 (csh) > boot p2 :0.0 12Mar96 3:12 U\M^I\M-eWVS\M^M]\^D\M^Ms\^D\M^I\M-w <- this is Netscape > boot p3 :0.0 12Mar96 2:39 (csh) > >This is a machine running a 2.1-stable kernel, but most of the commands and libraries >are still 2.0.5. You need to rebuild/install libkvm, w, and ps. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-isp Wed Mar 20 15:21:30 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA13720 for isp-outgoing; Wed, 20 Mar 1996 15:21:30 -0800 (PST) Received: from heather.greatbasin.com (heather.greatbasin.com [140.174.194.41]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA13715 for ; Wed, 20 Mar 1996 15:21:27 -0800 (PST) Received: from euterpe (euterpe.sierrawave.com [207.33.38.69]) by heather.greatbasin.com (8.7.1/8.7.1) with SMTP id PAA10403 for < freebsd-isp@FreeBSD.ORG>; Wed, 20 Mar 1996 15:21:25 -0800 (PST) Message-Id: <199603202321.PAA10403@heather.greatbasin.com> Date: Wed, 20 Mar 96 15:21:09 PST From: jpaterson@sierrawave.com (Jim Paterson) Reply-To: jpaterson@sierrawave.com (Jim Paterson) To: freebsd-isp@FreeBSD.ORG X-Mailer: Jim Paterson's PMMail v1.1 Subject: Uninterruptable power supplies Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I haven't seen it so I thought I'd ask -- is there driver support for any of the low cost UPS'es like APC, Tripplite or Best? I believe these all use either contact closure signals or RS-232 async messages to let the computer know it is running on a battery. Thanks, Jim Paterson jpaterson@sierrawave.com From owner-freebsd-isp Wed Mar 20 19:49:56 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA03241 for isp-outgoing; Wed, 20 Mar 1996 19:49:56 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA03235 for ; Wed, 20 Mar 1996 19:49:49 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id TAA23201; Wed, 20 Mar 1996 19:47:58 -0800 From: "Rodney W. Grimes" Message-Id: <199603210347.TAA23201@GndRsh.aac.dev.com> Subject: Re: Microsoft "Get ISDN"? To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 20 Mar 1996 19:47:58 -0800 (PST) Cc: nate@sri.MT.net, freebsd-isp@freefall.freebsd.org In-Reply-To: <199603201819.MAA29896@brasil.moneng.mei.com> from "Joe Greco" at Mar 20, 96 12:19:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > I am curious, why do you use SLIP for your dedicated connections? > > > > I don't speak for Joe, but I use SLIP (w/VJ compression) whenever > > possible since it uses less overhead and I seem to have lower latency > > and higher throughput than using both user-mode and kernel-mode PPP on > > FreeBSD boxes. > > I don't have anything to say about higher throughput since in my experience > it's only a mild difference, but the latency issue is mainly due to ppp's > default 1500 mtu. Lowering that (I know one fella who uses 296) will help > latency issues quite a bit. With 1500, you only get two or three packets > per second through the link if somebody is running a large transfer of some > sort. > > Most sites which run dedicated connections will have multiple people using > the link simultaneously, so the lower mtu gives the impression of faster > response. This hurts overall throughput mildly, buuuuut there's always a > tradeoff to be made. > > fyi: SLIP uses a 552 mtu. FYI: SLIP and PPP can use what ever MTU you decided to set them up for, I use 296 mtu on any connection that has interactive trafic on it, and crank it out to 1500 on connections that are computers talking to computers only. This is not a ppp vs slip issue, both can be changed (ppp is much easier to change infact since only one end, the end you control, has to be changed, slip requires that both ends agree on what the mtu is by ifconfig options. I agree with Joe in the use of SLIP for dedicated connections, it just seems easier to me to get them up and working (but then, probably much like Joe, I have been doing slip connections far longer than I have been doing ppp connections and my experience is far deeper). I also have not had to deal with the flakeness there has been over the last year or so in ppp implementations, slip is old, but tried and true technology that does IP very well over a serial line. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-isp Thu Mar 21 12:57:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA25360 for isp-outgoing; Thu, 21 Mar 1996 12:57:26 -0800 (PST) Received: from kirk.edmweb.com ([204.244.190.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA25351 for ; Thu, 21 Mar 1996 12:57:20 -0800 (PST) Received: (from steve@localhost) by kirk.edmweb.com (8.6.12/8.6.12) id MAA02865; Thu, 21 Mar 1996 12:56:49 -0800 Date: Thu, 21 Mar 1996 12:56:49 -0800 (PST) From: Steve Reid To: isp@freebsd.org Subject: PPP (iijppp) proxy ARP bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I seem to have found a bug in iijppp. It doesn't always delete the ARP entry when the connection is closed. Further connections on that IP address don't work until I manually arp -d the entry. The server is a FreeBSD 2.1-R system, and the client is a 2.0.5-R machine. Both are using iijppp. Static IP address. Nothing out of the ordinary. Right now, I am the only person who uses the system for dialin, so this isn't exactly high-load. Has anyone else had this problem? Does anyone have a fix? From owner-freebsd-isp Thu Mar 21 16:50:13 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA00693 for isp-outgoing; Thu, 21 Mar 1996 16:50:13 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA00688 for ; Thu, 21 Mar 1996 16:50:10 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA17905; Thu, 21 Mar 1996 17:50:02 -0700 Date: Thu, 21 Mar 1996 17:50:02 -0700 From: Nate Williams Message-Id: <199603220050.RAA17905@rocky.sri.MT.net> To: Steve Reid Cc: isp@FreeBSD.org Subject: Re: PPP (iijppp) proxy ARP bug? In-Reply-To: References: Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I seem to have found a bug in iijppp. It doesn't always delete the ARP > entry when the connection is closed. Further connections on that IP > address don't work until I manually arp -d the entry. This is a kernel bug which is fixed in -stable. Upgrade your kernel sources to -stable and all will be well. Nate From owner-freebsd-isp Thu Mar 21 23:03:22 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA20419 for isp-outgoing; Thu, 21 Mar 1996 23:03:22 -0800 (PST) Received: from xs1.simplex.nl (xs1.simplex.NL [193.78.46.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA20412 for ; Thu, 21 Mar 1996 23:03:17 -0800 (PST) X-Organisation-1: Simplex Networking Amsterdam X (Inter)Network X-Organisation-2: Kruislaan 419-38a 1098 VA Amsterdam X Solutions & X-Organisation-3: tel:+31(20)-6932433 fax:+31(20)-6685486 X Access Provider Received: (from rob@localhost) by xs1.simplex.nl (8.7.5/8.7.3-RS) id IAA04095; Fri, 22 Mar 1996 08:04:09 +0100 (MET) Date: Fri, 22 Mar 1996 08:04:09 +0100 (MET) From: Rob Simons Message-Id: <199603220704.IAA04095@xs1.simplex.nl> To: nate@sri.MT.net, steve@edmweb.com Subject: Re: PPP (iijppp) proxy ARP bug? Cc: isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk | > I seem to have found a bug in iijppp. It doesn't always delete the ARP | > entry when the connection is closed. Further connections on that IP | > address don't work until I manually arp -d the entry. | | This is a kernel bug which is fixed in -stable. Upgrade your kernel | sources to -stable and all will be well. Can anyone upgrade the kernel sources of 2.1-RELEASE to 2.2-stable (I assume you meant that) without expecting problems ? And, is it really fixed, or do you mean that ugly hack about first checking if there still is an old arp entry before setting up a new one ? Regards, - Rob. /*--------------------------------------------------------------*\ /* Rob Simons | rob@simplex.nl *\ /* ------------ | ------------- | -------- | ------- *\ /* Novell Netware System Operator | UNIX system operator *\ /*--------------------------------------------------------------*\ From owner-freebsd-isp Fri Mar 22 08:18:59 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA13418 for isp-outgoing; Fri, 22 Mar 1996 08:18:59 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA13413 for ; Fri, 22 Mar 1996 08:18:55 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA18897; Fri, 22 Mar 1996 08:52:14 -0700 Date: Fri, 22 Mar 1996 08:52:14 -0700 From: Nate Williams Message-Id: <199603221552.IAA18897@rocky.sri.MT.net> To: Rob Simons Cc: nate@sri.MT.net, steve@edmweb.com, isp@freebsd.org Subject: Re: PPP (iijppp) proxy ARP bug? In-Reply-To: <199603220704.IAA04095@xs1.simplex.nl> References: <199603220704.IAA04095@xs1.simplex.nl> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > | > I seem to have found a bug in iijppp. It doesn't always delete the ARP > | > entry when the connection is closed. Further connections on that IP > | > address don't work until I manually arp -d the entry. > | > | This is a kernel bug which is fixed in -stable. Upgrade your kernel > | sources to -stable and all will be well. > > Can anyone upgrade the kernel sources of 2.1-RELEASE to 2.2-stable (I > assume you meant that) without expecting problems ? It's actually 2.1-stable, and 2.2-current. The next release of -stable will be 2.1.1, so it's much more like 2.1 than 2.2. > And, is it really fixed, or do you mean that ugly hack about first > checking if there still is an old arp entry before setting up a new > one ? Umm, it's really fixed, but it involves deleting the bogus entry. The system creating an unresolved entry is correct behavior, and deleting the unresolved entry when a valid entry is found is correct behavior. This is done in the kernel though, so it's not a user-land hack to work around kernel bugs. Nate From owner-freebsd-isp Fri Mar 22 09:17:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15977 for isp-outgoing; Fri, 22 Mar 1996 09:17:09 -0800 (PST) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA15969 Fri, 22 Mar 1996 09:17:00 -0800 (PST) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.12/8.6.9) with SMTP id LAA21575; Fri, 22 Mar 1996 11:16:57 -0600 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 22 Mar 96 11:16 CST Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 22 Mar 96 11:16 CST Message-Id: From: sigma@mcs.com (Kevin Martin) Subject: RTM_LOSING "Kernel suspects partitioning" To: freebsd-isp@freebsd.org Date: Fri, 22 Mar 1996 11:16:49 -0600 (CST) Cc: freebsd-questions@freebsd.org Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have FreeBSD running on a Pentium-120, 128Mb RAM, SMC NIC (de0), with over two hundred virtual domains. A while ago, we were having unusual network storms, and I did lots of experimentation with the virtual domain set up to see if it was related. In the end, I changed so many things (eliminating the specific "route add" commands, for example), that I'm not sure exactly what has cleared up the problem. But in any case, I saw at the time, and have continued to see, this message on "route -n monitor": RTM_LOSING: Kernel Suspects Partitioning: len 124, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: Followed by IP addresses of the remote and the local host. This seems to happen for *any* connection to the machines, so there are a lot of these messages. I looked through the source, a few books, and on the net, but I can't find the meaning of this. Does it represent a problem? It seems to. I think the thing that actually fixed the network hangs was increasing NMBCLUSTERS to 4096; there were occasional "mb_map full" messages before that. Please reply by e-mail, I'll summarize later. Thanks, Kevin Martin sigma@mcs.com From owner-freebsd-isp Fri Mar 22 10:59:30 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21487 for isp-outgoing; Fri, 22 Mar 1996 10:59:30 -0800 (PST) Received: from pc40-203.dev.oclc.org (pc40-203.dev.oclc.org [132.174.40.203]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21482 for ; Fri, 22 Mar 1996 10:59:28 -0800 (PST) Received: (from ilko@localhost) by pc40-203.dev.oclc.org (8.6.12/8.6.12) id NAA13376 for freebsd-isp@freebsd.org; Fri, 22 Mar 1996 13:58:24 GMT Message-ID: X-Mailer: XFMail 0.3 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Reply-To: ilko@oclc.org Organization: Online Computer Library Center Date: Fri, 22 Mar 1996 13:52:04 From: "Jon T. Ilko" To: freebsd-isp@freebsd.org Subject: SDL RISCom/N2csu Frame Relay? Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Will the SDL RISCom/N2csu Frame Relay option for BSD/OS work with FreeBSD 2.1.0-R? SDL suggested that if I want to use a free OS, to use Linux and their N2csu Linux driver. I'd rather use FreeBSD. From owner-freebsd-isp Fri Mar 22 14:22:23 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA05218 for isp-outgoing; Fri, 22 Mar 1996 14:22:23 -0800 (PST) Received: from wizard.pn.com (root@wizard.pn.com [204.96.36.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA05208 for ; Fri, 22 Mar 1996 14:22:19 -0800 (PST) Received: from auntiem.pn.com (bb@auntiem.pn.com [205.136.64.14]) by wizard.pn.com (8.6.12) with ESMTP id RAA11474; Fri, 22 Mar 1996 17:22:09 -0500 Received: (bb@localhost) by auntiem.pn.com (8.6.12/8.6.12) id RAA13628; Fri, 22 Mar 1996 17:24:02 -0500 Date: Fri, 22 Mar 1996 17:24:02 -0500 Message-Id: <199603222224.RAA13628@auntiem.pn.com> From: Brian Bartholomew To: freebsd-isp@freebsd.org Subject: snmpd daemon Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know of an snmp daemon that has been ported to FreeBSD? Another member of the League for Programming Freedom (LPF) lpf@uunet.uu.net ------------------------------------------------------------------------------- Brian Bartholomew - bb@pn.com - Pioneer Global Telecommunications Inc. From owner-freebsd-isp Fri Mar 22 20:52:32 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA28770 for isp-outgoing; Fri, 22 Mar 1996 20:52:32 -0800 (PST) Received: from okjunc.junction.net (root@okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA28758 for ; Fri, 22 Mar 1996 20:52:28 -0800 (PST) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id VAA18672; Fri, 22 Mar 1996 21:02:55 -0800 Date: Fri, 22 Mar 1996 21:52:55 -0800 (PST) From: Michael Dillon To: Brian Bartholomew cc: freebsd-isp@FreeBSD.org Subject: Re: snmpd daemon In-Reply-To: <199603222224.RAA13628@auntiem.pn.com> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 22 Mar 1996, Brian Bartholomew wrote: > Does anyone know of an snmp daemon that has been ported to FreeBSD? CMU SNMPD has been ported Michael Dillon Voice: +1-604-546-8022 Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com From owner-freebsd-isp Sat Mar 23 07:30:17 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA25429 for isp-outgoing; Sat, 23 Mar 1996 07:30:17 -0800 (PST) Received: from fyeung5.netific.com (netific.vip.best.com [205.149.182.145]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA25422 for ; Sat, 23 Mar 1996 07:30:13 -0800 (PST) Received: (from fyeung@localhost) by fyeung5.netific.com (8.6.11/8.6.9) id HAA03175; Sat, 23 Mar 1996 07:28:58 GMT From: francis yeung Message-Id: <199603230728.HAA03175@fyeung5.netific.com> Subject: Re: PPP (iijppp) proxy ARP bug? To: nate@sri.MT.net (Nate Williams) Date: Sat, 23 Mar 1996 07:28:58 +0000 () Cc: rob@xs1.simplex.nl, nate@sri.MT.net, steve@edmweb.com, isp@FreeBSD.org In-Reply-To: <199603221552.IAA18897@rocky.sri.MT.net> from "Nate Williams" at Mar 22, 96 08:52:14 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Nate's fix also works for 2.0.5 release too. Let me know if anyone needs it. Francis > > | > I seem to have found a bug in iijppp. It doesn't always delete the ARP > > | > entry when the connection is closed. Further connections on that IP > > | > address don't work until I manually arp -d the entry. > > | > > | This is a kernel bug which is fixed in -stable. Upgrade your kernel > > | sources to -stable and all will be well. > > > > Can anyone upgrade the kernel sources of 2.1-RELEASE to 2.2-stable (I > > assume you meant that) without expecting problems ? > > It's actually 2.1-stable, and 2.2-current. The next release of -stable > will be 2.1.1, so it's much more like 2.1 than 2.2. > > > And, is it really fixed, or do you mean that ugly hack about first > > checking if there still is an old arp entry before setting up a new > > one ? > > Umm, it's really fixed, but it involves deleting the bogus entry. > The system creating an unresolved entry is correct behavior, and > deleting the unresolved entry when a valid entry is found is correct > behavior. > > This is done in the kernel though, so it's not a user-land hack to work > around kernel bugs. > > > Nate > >