From owner-freebsd-net Sun Dec 13 20:24:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22854 for freebsd-net-outgoing; Sun, 13 Dec 1998 20:24:02 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from i.caniserv.com (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA22820 for ; Sun, 13 Dec 1998 20:24:00 -0800 (PST) (envelope-from Darcy@ok-connect.com) Received: (qmail 25424 invoked from network); 14 Dec 1998 04:23:57 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 14 Dec 1998 04:23:57 -0000 Message-Id: <3.0.32.19981213202407.02362040@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 13 Dec 1998 20:24:08 -0800 To: freebsd-net@FreeBSD.ORG From: Darcy Buskermolen Subject: IP aliasing and source IP's Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a FreeBSD 2.2.x with a few IPs aliased to it. I'd like to configure it so that certain users always have all of their source address be a specific IP (not the main IP of the box) regardless of what application they run. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 13 22:26:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05305 for freebsd-net-outgoing; Sun, 13 Dec 1998 22:26:13 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05125 for ; Sun, 13 Dec 1998 22:25:46 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA07707 for ; Mon, 14 Dec 1998 07:25:38 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18284 for ; Mon, 14 Dec 1998 07:25:37 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA09094 for freebsd-net@FreeBSD.org; Mon, 14 Dec 1998 06:55:44 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:44 +0100 (CET) From: List User Message-Id: <199812140555.GAA09094@doorway.home.lan> To: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Newsgroups: freebsd.net Path: root From: Darcy Buskermolen Subject: IP aliasing and source IP's Content-Type: text/plain; charset="us-ascii" Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 14 Dec 1998 04:23:57 -0000 To: freebsd-net Sender: owner-freebsd-net@FreeBSD.ORG Organization: Private News Host Message-ID: <3.0.32.19981213202407.02362040@mail.ok-connect.com> X-Mailer: Windows Eudora Pro Version 3.0 (32) X-Uidl: f2cf417dadb1f43b2753e37ec1620a22 X-Loop: FreeBSD.org Mime-Version: 1.0 X-Sender: darcyb@mail.ok-connect.com Date: Mon, 14 Dec 1998 04:24:08 GMT I have a FreeBSD 2.2.x with a few IPs aliased to it. I'd like to configure it so that certain users always have all of their source address be a specific IP (not the main IP of the box) regardless of what application they run. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 00:38:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25252 for freebsd-net-outgoing; Mon, 14 Dec 1998 00:38:07 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from tron.jplt.com (tron.jplt.com [207.44.231.183]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25191 for ; Mon, 14 Dec 1998 00:38:03 -0800 (PST) (envelope-from gmo@tron.jplt.com) Received: from localhost (gmo@localhost) by tron.jplt.com (8.9.1/8.9.1) with ESMTP id AAA12520 for ; Mon, 14 Dec 1998 00:38:05 -0800 (PST) (envelope-from gmo@tron.jplt.com) Date: Mon, 14 Dec 1998 00:38:05 -0800 (PST) From: Greg To: freebsd-net@FreeBSD.ORG Subject: Network accounting software Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know of any good and free network accounting software? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 09:28:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14487 for freebsd-net-outgoing; Mon, 14 Dec 1998 09:28:56 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14419; Mon, 14 Dec 1998 09:28:43 -0800 (PST) (envelope-from wpeters@xylan.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id JAA25638; Mon, 14 Dec 1998 09:28:28 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA04386; Mon, 14 Dec 1998 09:28:28 -0800 Received: from xylan.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id KAA28905; Mon, 14 Dec 1998 10:28:27 -0700 Message-ID: <36754AC1.5F05F9F1@xylan.com> Date: Mon, 14 Dec 1998 10:28:33 -0700 From: Wes Peters Organization: Xylan Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: ISDN for FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My PPP dial-in server is now working quite well. So well, in fact, that the user who is sponsoring it (and buying all the hardware) wants to upgrade to ISDN. This shouldn't be a problem, we already have a couple of ISDN lines here that aren't being used. Her ISDN line is in, but hasn't been tested yet. I need to equip my FreeBSD server for ISDN, so I'm looking for suggestions. I use user-mode PPP, and would like to support either bonding or MP so I can give her 128K throughput. Please advise on TAs, internal or external, that work well with PPP on FreeBSD. If I get an external TA, do I need to get either a sync serial card or a 16750 based async card? -- Wes Peters Who's going to save you Principal Engineer When you're a slave to Xylan Corporation A diamond as big as the Ritz wpeters@xylan.com -- Jimmy Buffett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 10:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24962 for freebsd-net-outgoing; Mon, 14 Dec 1998 10:49:01 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA24947; Mon, 14 Dec 1998 10:48:53 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA05342; Mon, 14 Dec 1998 17:38:35 +0100 From: Luigi Rizzo Message-Id: <199812141638.RAA05342@labinfo.iet.unipi.it> Subject: dummynet almost in -current To: current@FreeBSD.ORG, net@FreeBSD.ORG Date: Mon, 14 Dec 1998 17:38:35 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org excuse the crosspost, but as the subject says, i think i have committed all the relevant pieces to have dummynet in -current. While i look for the manpages (I could swear i had committed them to -stable, but i cannot find them!) can people have a try ? It should work by simply putting options DUMMYNET options BRIDGE in your kernel config file. Remember you need IPFIREWALL. More info at the usual place http://www.iet.unipi.it/~luigi/ip_dummynet/ dummynet should also work on alpha architecture (I cannot test it) whereas bridging will not because some macros are missing in bridge.h i think. if there is some obvious mistake (my 3.0 disk is a bit outdated) feel free to fix things. Also, if someone wants to compile a LINT kernel with both options that would make me feel safer in adding those options uncommented in LINT. thanks luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 13:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14334 for freebsd-net-outgoing; Mon, 14 Dec 1998 13:22:17 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14312; Mon, 14 Dec 1998 13:22:13 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA29094; Mon, 14 Dec 1998 13:20:46 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma029088; Mon, 14 Dec 98 13:20:39 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA22342; Mon, 14 Dec 1998 13:20:39 -0800 (PST) From: Archie Cobbs Message-Id: <199812142120.NAA22342@bubba.whistle.com> Subject: Re: ISDN for FreeBSD In-Reply-To: <36754AC1.5F05F9F1@xylan.com> from Wes Peters at "Dec 14, 98 10:28:33 am" To: wpeters@xylan.com (Wes Peters) Date: Mon, 14 Dec 1998 13:20:39 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wes Peters writes: > I use user-mode PPP, and would like to support either bonding or MP so > I can give her 128K throughput. Please advise on TAs, internal or > external, that work well with PPP on FreeBSD. > > If I get an external TA, do I need to get either a sync serial card or > a 16750 based async card? BitSURFR Pro EZ works pretty well.. also 3Com Impact IQ. You can do up to 115Kbps on a standard 16550A, which is close to 128Kbps.. No US-ISDN internal (ie, non-TA) ISDN cards are supported. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 17:34:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15758 for freebsd-net-outgoing; Mon, 14 Dec 1998 17:34:50 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from thunder.thumbs.org (thunder.thumbs.org [194.217.125.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15752 for ; Mon, 14 Dec 1998 17:34:48 -0800 (PST) (envelope-from russ@thumbs.org) Received: from russ by thunder.thumbs.org with local (Exim 2.05 #1) id 0zpjRU-0002aZ-00 for freebsd-net@freebsd.org; Tue, 15 Dec 1998 01:38:28 +0000 Message-ID: <19981215013828.B9933@thumbs.org> Date: Tue, 15 Dec 1998 01:38:28 +0000 From: Russ Paton To: freebsd-net@FreeBSD.ORG Subject: ISDN, FreeBSD and ITK Columbus World Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, Quick question... Has anyone had any experience/joy getting the above ISDN ISA card to work with FreeBSD? Comments/responses would be appreicated. TIA Russ -- Russ Paton russ@thumbs.org http://www.thumbs.org eWay'eray onlyway umanhay afterway allway To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 18:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23166 for freebsd-net-outgoing; Mon, 14 Dec 1998 18:20:52 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ts.shopnet.com (ts.shopnet.com [208.131.136.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23126; Mon, 14 Dec 1998 18:20:43 -0800 (PST) (envelope-from deichert@wildponies.org) Received: (from deichert@localhost) by ts.shopnet.com (8.8.4/8.6.12) id TAA29931; Mon, 14 Dec 1998 19:22:49 -0700 (MST) Date: Mon, 14 Dec 1998 19:22:49 -0700 (MST) From: Diana Eichert X-Sender: deichert@ts.shopnet.com To: Archie Cobbs cc: Wes Peters , freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: ISDN for FreeBSD In-Reply-To: <199812142120.NAA22342@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org there is a patch for higher speed serial cards, Zyxel for one. dod a search through the archives. I jusst posted the URL a couple of weeks ago. diana On Mon, 14 Dec 1998, Archie Cobbs wrote: > Wes Peters writes: > > I use user-mode PPP, and would like to support either bonding or MP so > > I can give her 128K throughput. Please advise on TAs, internal or > > external, that work well with PPP on FreeBSD. > > > > If I get an external TA, do I need to get either a sync serial card or > > a 16750 based async card? > > BitSURFR Pro EZ works pretty well.. also 3Com Impact IQ. > You can do up to 115Kbps on a standard 16550A, which is close > to 128Kbps.. > > No US-ISDN internal (ie, non-TA) ISDN cards are supported. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > Diana Eichert IT Manager McKinley Paper Company deeiche@mckinleypaper.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 20:52:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09501 for freebsd-net-outgoing; Mon, 14 Dec 1998 20:52:55 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA09496 for ; Mon, 14 Dec 1998 20:52:54 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <55339(5)>; Mon, 14 Dec 1998 20:52:49 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Mon, 14 Dec 1998 20:52:41 -0800 To: Michael Robinson cc: freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Mon, 14 Dec 98 06:37:09 PST." <199812141437.OAA00472@netrinsics.com> Date: Mon, 14 Dec 1998 20:52:38 PST From: Bill Fenner Message-Id: <98Dec14.205241pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [redirected to freebsd-net] In message <199812141437.OAA00472@netrinsics.com> you write: > 1. This isn't a bug. It's a performance tradeoff of memory efficiency > (allocating an mbuf cluster) versus protocol efficiency (sending > two packets). I still think it's a bug; that's why I wrote the (buggy) patch referred to in the Squid FAQ. See my discussion at http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c#rev1.41 (and in particular, the paragraph labelled "The real fix"...) Perhaps someday someone will figure out why X starts acting so funny with this patch and we can put it back, or perhaps someday someone will have time to implement "the real fix". Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 21:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14500 for freebsd-net-outgoing; Mon, 14 Dec 1998 21:44:22 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([210.74.175.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14479; Mon, 14 Dec 1998 21:44:12 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id NAA07127; Tue, 15 Dec 1998 13:40:42 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 13:40:42 GMT From: Michael Robinson Message-Id: <199812151340.NAA07127@netrinsics.com> To: fenner@parc.xerox.com, robinson@netrinsics.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec14.205241pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fenner writes: >In message <199812141437.OAA00472@netrinsics.com> you write: >> 1. This isn't a bug. It's a performance tradeoff of memory efficiency >> (allocating an mbuf cluster) versus protocol efficiency (sending >> two packets). > >I still think it's a bug; that's why I wrote the (buggy) patch referred >to in the Squid FAQ. See my discussion at >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c#rev1.41 >(and in particular, the paragraph labelled "The real fix"...) Well, I've explained the problem, and given a fix (reduce MINCLSIZE to MHLEN+1). You can try my fix, and if it causes any problems for you (other than causing your Squid server to run out of mbuf clusters), then I'll go back to the drawing board. Your "real fix" (accumulate an mbuf chain until it exceeded the "requested transfer size") seems unlikely to fix the problem for Squid and IIOP, because the problem is that writes which are bigger than one mbuf, but smaller than two, don't get sent atomically and immediately (causing protocol latency). Your discussion overlooks the fact that these are client-server protocols that are going to write a request on a socket and then wait for a response. "Accumulating mbufs" until they exceed the TCP MSS is a recipe for deadlock. In such a situation, the only acceptable "requested transfer size" is the length of the write itself, and my fix implements that. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 21:52:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15737 for freebsd-net-outgoing; Mon, 14 Dec 1998 21:52:08 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA15732; Mon, 14 Dec 1998 21:52:07 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <55377(4)>; Mon, 14 Dec 1998 21:52:01 PST Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id VAA17801; Mon, 14 Dec 1998 21:52:00 -0800 (PST) (envelope-from fenner) Date: Mon, 14 Dec 1998 21:52:00 PST From: Bill Fenner Message-Id: <199812150552.VAA17801@mango.parc.xerox.com> To: fenner@parc.xerox.com, robinson@netrinsics.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <199812151340.NAA07127@netrinsics.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You misunderstand. The fix is to accumulate mbufs in a chain until either a) The protocol gets all of the data that it wanted, or b) All of the data that the user has provided has been copied into mbufs. (b) is what sosend() used to do. The URL referenced (the one with "vanj88" in it) describes why sosend() was changed to use only a single mbuf at a time, but this performance problem was not envisioned at the time. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 22:18:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18613 for freebsd-net-outgoing; Mon, 14 Dec 1998 22:18:17 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18606 for ; Mon, 14 Dec 1998 22:18:13 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id HAA06273; Tue, 15 Dec 1998 07:16:44 +0100 (CET) Message-ID: <3675FECC.6CA55E61@simultan.ch> Date: Tue, 15 Dec 1998 07:16:44 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Wes Peters CC: freebsd-net@FreeBSD.ORG Subject: Re: ISDN for FreeBSD References: <36754AC1.5F05F9F1@xylan.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wes Peters wrote: > I use user-mode PPP, and would like to support either bonding or MP so > I can give her 128K throughput. Please advise on TAs, internal or > external, that work well with PPP on FreeBSD. I'm using FreeBSD with an external TA omniNet LCD from ZyXel. It works like a charm. > If I get an external TA, do I need to get either a sync serial card or > a 16750 based async card? You just need a usual async serial port. Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 14 23:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25382 for freebsd-net-outgoing; Mon, 14 Dec 1998 23:32:10 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA25376; Mon, 14 Dec 1998 23:32:09 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <55452(1)>; Mon, 14 Dec 1998 23:32:03 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Mon, 14 Dec 1998 22:19:11 -0800 To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 98 05:40:42 PST." <199812151340.NAA07127@netrinsics.com> Date: Mon, 14 Dec 1998 22:17:03 PST From: Bill Fenner Message-Id: <98Dec14.221911pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hm. After looking into this a little further, I discovered that I've been running a slightly modified version of my original patch on my home 2.2.6 machine (running X and everything) for about 5 months and haven't noticed any of the problems that people were reporting. Would you mind trying this patch? Bill --- uipc_socket.c.orig Tue Jun 30 23:03:30 1998 +++ uipc_socket.c Sat Jul 18 12:32:26 1998 @@ -340,6 +340,7 @@ register long space, len, resid; int clen = 0, error, s, dontroute, mlen; int atomic = sosendallatonce(so) || top; + int small = 0; if (uio) resid = uio->uio_resid; @@ -443,6 +444,7 @@ mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { + small = 1; nopages: len = min(min(mlen, resid), space); /* @@ -466,7 +468,7 @@ top->m_flags |= M_EOR; break; } - } while (space > 0 && atomic); + } while (space > 0 && (atomic || small)); if (dontroute) so->so_options |= SO_DONTROUTE; s = splnet(); /* XXX */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 00:06:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29194 for freebsd-net-outgoing; Tue, 15 Dec 1998 00:06:32 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([210.74.179.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29162; Tue, 15 Dec 1998 00:06:17 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id QAA07493; Tue, 15 Dec 1998 16:03:03 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 16:03:03 GMT From: Michael Robinson Message-Id: <199812151603.QAA07493@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec14.221911pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fenner writes: >Hm. After looking into this a little further, I discovered that I've >been running a slightly modified version of my original patch on my >home 2.2.6 machine (running X and everything) for about 5 months and >haven't noticed any of the problems that people were reporting. > >Would you mind trying this patch? I'll do that and get back to you. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 02:22:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10112 for freebsd-net-outgoing; Tue, 15 Dec 1998 02:22:02 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from voyager.planb.com.au (voyager.planb.com.au [203.35.172.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10098 for ; Tue, 15 Dec 1998 02:21:59 -0800 (PST) (envelope-from kevin@planb.net.au) Received: from fossil.planb.com.au (fossil.planb.com.au [203.35.172.145]) by voyager.planb.com.au (8.8.7/8.8.8) with SMTP id VAA20156; Tue, 15 Dec 1998 21:21:50 +1100 (EST) Received: by fossil.planb.com.au with Microsoft Mail id <01BE2868.A6D2DF60@fossil.planb.com.au>; Tue, 15 Dec 1998 20:22:35 +1100 Message-ID: <01BE2868.A6D2DF60@fossil.planb.com.au> From: Kevin Sheehan To: "freebsd-net@FreeBSD.ORG" , "'Russ Paton'" Subject: RE: ISDN, FreeBSD and ITK Columbus World Date: Tue, 15 Dec 1998 20:22:33 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Russ Paton writes: >Has anyone had any experience/joy getting the above ISDN ISA card to >work with FreeBSD? Keep an eye on FreeBSD-ISDN@FreeBSD.ORG. i4b is on it's way to supporting the ITK ix1-micro (the card in at least one of the Columbus packages). In case you were wondering.... (straight from the FAQ). 12. Where can i get ISDN4BSD ? ------------------------------ The ISDN4BSD package is available from: isdn4bsd@ftp.consol.de/pub -------------------------- you have to log in as user isdn4bsd -------- and give your mail address as the password. Then change to the "pub" directory. Cheers. ---------- From: Sent: Tuesday, 15 December 1998 12:38 To: freebsd-net@FreeBSD.ORG Subject: ISDN, FreeBSD and ITK Columbus World Hi there, Quick question... Has anyone had any experience/joy getting the above ISDN ISA card to work with FreeBSD? Comments/responses would be appreicated. TIA Russ -- Russ Paton russ@thumbs.org http://www.thumbs.org eWay'eray onlyway umanhay afterway allway To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 03:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16445 for freebsd-net-outgoing; Tue, 15 Dec 1998 03:46:40 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([210.74.178.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16427; Tue, 15 Dec 1998 03:46:31 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id PAA07456; Tue, 15 Dec 1998 15:55:17 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 15:55:17 GMT From: Michael Robinson Message-Id: <199812151555.PAA07456@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <199812150552.VAA17801@mango.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fenner writes: >You misunderstand. The fix is to accumulate mbufs in a chain until either >a) The protocol gets all of the data that it wanted, or >b) All of the data that the user has provided has been copied into mbufs. > >(b) is what sosend() used to do. The URL referenced (the one with >"vanj88" in it) describes why sosend() was changed to use only a single >mbuf at a time, but this performance problem was not envisioned at >the time. Ok, I misunderstood. But I still disagree it's a bug. Or, more precisely, it would be a bug if the socket API and the TCP protocol were seen as one inseparable entity, which is not the case. There does not seem to me to be anything inherently broken at the socket abstraction layer with the practice of writing one "write" out to a streaming protocol in multiple packets. Nor does there seem to be anything inherently broken at the TCP abstraction layer with buffering streamed input until an ACK is received. Together, these performance optimizations at different levels of abstraction can interact badly, under a particular set of circumstances, but is that really a bug, per se? Having read the Van Jacobson argument for parallelism, though, I have to wonder how that relates to the current implementation of sosend in FreeBSD. It seems that we only get the "parallelism" if the write length is more than one mbuf and less than two. A write of two mbufs plus one byte is copied into a cluster, which gives you all the non-parallelism of the original "chain mbufs" solution, and all the memory inefficiency of cluster allocation. Is there any documentation on why MINCLSIZE is currently set to the value it is? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 05:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27466 for freebsd-net-outgoing; Tue, 15 Dec 1998 05:29:20 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from msf1.swe.ids.dps.casa.es (h029206.nexo.es [195.235.29.206]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27458 for ; Tue, 15 Dec 1998 05:29:07 -0800 (PST) (envelope-from jlfreniche@acm.org) Received: from is1.casa.es (is1.casa.es [192.168.254.2]) by msf1.swe.ids.dps.casa.es (8.8.8/8.8.8) with ESMTP id OAA02104 for ; Tue, 15 Dec 1998 14:28:07 +0100 (CET) (envelope-from jlfreniche@acm.org) Received: from acm.org (localhost [127.0.0.1]) by is1.casa.es (8.8.8/8.8.8) with ESMTP id OAA20289 for ; Tue, 15 Dec 1998 14:27:18 +0100 (CET) (envelope-from jlfreniche@acm.org) Message-ID: <367663B6.518CE524@acm.org> Date: Tue, 15 Dec 1998 14:27:18 +0100 From: "Juan L. Freniche" X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: net@FreeBSD.ORG Subject: Passing Parameters to Remote Printers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have several FreeBSD (2.2.7) boxes in the same LAN shared with the print server (which is HP-UX). I have defined all necessary printers in FreeBSD as remote, being the remote host the HP-UX one. However, the HP-UX supports controlling the local printer by setting some options in the lp command (yes, lpr in HP-UX is "lp"). Examples: lp -d hp5p -oeconoon -oduplex -odpi300 -oyb some_file lp -d hp5p -oeconooff -osimplex -odpi600 -onb some_file lp -d hp5p -oeconooff -oduplex -odpi300 -onb some_file lp -d hp5p -oeconooff -oduplex -odpi300 -oyb some_file lp -d hp5p -oeconooff -osimplex -odpi600 -oyb some_file where hp5p is the printer (attached to HP-UX). The FreeBSD printcap relevant part is: hp5p|ps|remote postscript printer:\ :lf=/var/log/lpd-errs:sh:sc:rs:lp=:\ :sd=/var/spool/output/lpd/hp5p:\ :rm=hp-ux:\ :rp=hp5p: And this is working if the lpr command (in FreeBSD) has FreeBSD-lpr-options: lpr -h -P hp5p some_file However lpr displays error messages with lpr -P hp5p -oeconoon -oduplex -odpi300 -oyb some_file which is obvious as it does not support -o The question is that I need to pass -o parameters to the remote printer. How can this be done? -- Juan L. Freniche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 08:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15316 for freebsd-net-outgoing; Tue, 15 Dec 1998 08:30:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15311 for ; Tue, 15 Dec 1998 08:30:44 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id IAA05778; Tue, 15 Dec 1998 08:30:13 -0800 (PST) (envelope-from marcs@znep.com) Date: Tue, 15 Dec 1998 08:30:12 -0800 (PST) From: Marc Slemko To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-Reply-To: <199812151555.PAA07456@netrinsics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (-stable removed from the cc list, since this isn't particular to stable in any way) On Tue, 15 Dec 1998, Michael Robinson wrote: > Bill Fenner writes: > >You misunderstand. The fix is to accumulate mbufs in a chain until either > >a) The protocol gets all of the data that it wanted, or > >b) All of the data that the user has provided has been copied into mbufs. > > > >(b) is what sosend() used to do. The URL referenced (the one with > >"vanj88" in it) describes why sosend() was changed to use only a single > >mbuf at a time, but this performance problem was not envisioned at > >the time. > > Ok, I misunderstood. But I still disagree it's a bug. Or, more precisely, > it would be a bug if the socket API and the TCP protocol were seen as one > inseparable entity, which is not the case. No, it really is a bug. It is inherently broken to write multiple packets for one write() when the size of the write is far less than the MTU (well, the "effective MTU") unless you have extreme extenuating circumstances. It may not be a bug covered by any spec, but for people trying to write useful network apps it shoots them in the head. It is still a bug. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 08:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19351 for freebsd-net-outgoing; Tue, 15 Dec 1998 08:57:32 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA19346; Tue, 15 Dec 1998 08:57:31 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <55530(5)>; Tue, 15 Dec 1998 08:57:24 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177535>; Tue, 15 Dec 1998 08:57:14 -0800 To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 98 07:55:17 PST." <199812151555.PAA07456@netrinsics.com> Date: Tue, 15 Dec 1998 08:42:29 PST From: Bill Fenner Message-Id: <98Dec15.085714pst.177535@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199812151555.PAA07456@netrinsics.com> you write: >Together, these performance optimizations at different >levels of abstraction can interact badly, under a particular set of >circumstances, but is that really a bug, per se? Ok, it's a performance problem, which was introduced by a performance enhancement. Therefore, it's a bug in the original enhancement. =) >It seems that we only get the "parallelism" if the write length is more >than one mbuf and less than two. You get it also if it's more than the length of a cluster (and particularly multiples of the length of a cluster, e.g. a 64k write). >Is there any documentation on why MINCLSIZE is currently set to the value it >is? Not that I know of, but I can't say for sure that there's not something in the 4.4 daemon book. You know what the main tradeoff is of reducing MINCLSIZE (and there are some subtle ones too - set your socket buffer to 64k and start writing in 120-byte chunks and see when the socket buffer fills up). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 09:42:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26117 for freebsd-net-outgoing; Tue, 15 Dec 1998 09:42:49 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([202.99.61.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26086; Tue, 15 Dec 1998 09:42:37 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id BAA02158; Wed, 16 Dec 1998 01:39:17 GMT (envelope-from robinson) Date: Wed, 16 Dec 1998 01:39:17 GMT From: Michael Robinson Message-Id: <199812160139.BAA02158@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec15.085714pst.177535@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fenner writes: >>Is there any documentation on why MINCLSIZE is currently set to the value it >>is? > >Not that I know of, but I can't say for sure that there's not something >in the 4.4 daemon book. You know what the main tradeoff is of reducing >MINCLSIZE (and there are some subtle ones too - set your socket buffer >to 64k and start writing in 120-byte chunks and see when the socket >buffer fills up). Well, I just discovered another interesting effect of the smaller MINCLSIZE. After exhaustive testing with the standard X benchmarking utility (xmame), I've discovered a significant performance improvement for graphics- intensive X applications. -Michael Robinson P.S. It may be a while before I get around to testing your "short" patch ;-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 10:04:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28839 for freebsd-net-outgoing; Tue, 15 Dec 1998 10:04:02 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA28831; Tue, 15 Dec 1998 10:04:01 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <55775(1)>; Tue, 15 Dec 1998 10:03:55 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Tue, 15 Dec 1998 10:03:38 -0800 To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 98 17:39:17 PST." <199812160139.BAA02158@netrinsics.com> Date: Tue, 15 Dec 1998 10:03:36 PST From: Bill Fenner Message-Id: <98Dec15.100338pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199812160139.BAA02158@netrinsics.com> you write: >After exhaustive testing with the standard X benchmarking utility (xmame), >I've discovered a significant performance improvement for graphics- >intensive X applications. I'm not surprised -- since the "atomic" patch confused X, it was clear that X was in this range of small writes. I think that X sets TCP_NODELAY so it shouldn't be subject to the extra round trip in this case, but it still ends up being less packets. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 10:15:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00416 for freebsd-net-outgoing; Tue, 15 Dec 1998 10:15:02 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from cobxchg.ci.bryan.tx.us (xs.ci.bryan.tx.us [198.183.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00405 for ; Tue, 15 Dec 1998 10:15:00 -0800 (PST) (envelope-from dparker@ci.bryan.tx.us) Received: by xs.ci.bryan.tx.us with Internet Mail Service (5.5.2232.9) id ; Tue, 15 Dec 1998 12:14:53 -0600 Message-ID: <6C94DFBFD20ED211A8E3006097A1760F02A136@xs.ci.bryan.tx.us> From: "Parker, David K" To: freebsd-net@FreeBSD.ORG Subject: FreeBSD & CableModem Date: Tue, 15 Dec 1998 12:14:52 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope I'm posting this to the correct list... I have a PC setup with FreeBSD version 3.0. My problem is with the TCP/IP Configuration and CableModem. If I place the PC on my internal network using an IP Address/SM/GW for a Class C network, it works fine. I can resolve other host names, ping, etc... When I configure for our ISP using a cablemodem I have no such luck. Here is the IP info... IP: 208.162.121.228 SM: 255.255.254.0 GW: 208.162.120.1 I can ping the loopback and 208.162.121.228 but nothing else. This same configuration works fine when I use an NT Box. Any help would be greatly appreciated. Thanks, David Parker System/Network Administrator Computer Services City of Bryan (409) 821-5780 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 10:15:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00625 for freebsd-net-outgoing; Tue, 15 Dec 1998 10:15:32 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00611 for ; Tue, 15 Dec 1998 10:15:30 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA17430; Tue, 15 Dec 1998 11:15:10 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <3676A72D.E5FDF673@softweyr.com> Date: Tue, 15 Dec 1998 11:15:09 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Slemko CC: Michael Robinson , fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc Slemko wrote: > > No, it really is a bug. > > It is inherently broken to write multiple packets for one write() when the > size of the write is far less than the MTU (well, the "effective MTU") > unless you have extreme extenuating circumstances. I think you're confusing your ASSUMPTION that 1 write == 1 packet with any requirement for this to be true. Nothing in the code or the doco promises this behavior, so it's not a bug, it's just a design decision. > It may not be a bug covered by any spec, but for people trying to write > useful network apps it shoots them in the head. It is still a bug. In the vast majority of cases, it's the right choice to make, too. In the few examples of network code that need to be highly responsive, it's a terrible choice. These applications seem to be in the minority, since so many find the system useful as it is. I've followed this discussion and strongly agree that the "right way" to do this is to provide a socket option to turn off the default buffering on a per-socket basis. This would make my packet-throughput program actually WORK. ;^) Since the default is right for the vast majority of network programs, the small added complexity of the sock option shouldn't be too horrible to address. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 10:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01665 for freebsd-net-outgoing; Tue, 15 Dec 1998 10:19:47 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from poboxer.pobox.com (port25.prairietech.net [208.141.230.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01659 for ; Tue, 15 Dec 1998 10:19:42 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.9.1) id MAA02473; Tue, 15 Dec 1998 12:19:28 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 15 Dec 1998 12:19:28 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: net@FreeBSD.ORG Subject: ppp stopped bringing up link X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13942.38873.292291.452580@avalon.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Fishing for suggestions: I'm linking a solaris machine running pppd with with options like passive proxyarp asyncmap a00a0000 local 10.0.0.1:10.0.0.2 to a FreeBSD server using pppd options like set escape 0xff set timeout 0 set login set dial set log +phase +async +hdlc +lcp +ipcp +ccp +tun disable PAP disable CHAP accept PAP accept CHAP enable vjcomp accept vjcomp set ifaddr 10.0.0.1 10.0.0.2 running over a telnet link, which worked well until yesterday's make world. Now the connection never comes up. But reverting ppp to 12/13/98 doesn't help, so I can't blame ppp that easily! Dec 15 11:45:13 foo ppp[2291]: Phase: Using interface: tun1 Dec 15 11:45:13 foo ppp[2291]: Phase: deflink: Created in closed state Dec 15 11:45:13 foo ppp[2291]: Warning: Local: bind: Address already in use Dec 15 11:45:13 foo ppp[2291]: Warning: set server: Failed 4 Dec 15 11:45:13 foo ppp[2291]: tun1: Phase: PPP Started (direct mode). Dec 15 11:45:13 foo ppp[2291]: tun1: Phase: bundle: Establish Dec 15 11:45:13 foo ppp[2291]: tun1: Phase: deflink: closed -> opening Dec 15 11:45:13 foo ppp[2291]: tun1: Phase: deflink: Connected! Dec 15 11:45:13 foo ppp[2291]: tun1: Phase: deflink: opening -> lcp Dec 15 11:45:13 foo ppp[2291]: tun1: LCP: FSM: Using "deflink" as a transport Dec 15 11:45:13 foo ppp[2291]: tun1: LCP: deflink: State change Initial --> Closed Dec 15 11:45:13 foo ppp[2291]: tun1: LCP: deflink: State change Closed --> Stopped Then nothing. Any (preferrably polite) suggestions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 10:28:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03379 for freebsd-net-outgoing; Tue, 15 Dec 1998 10:28:58 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA03368 for ; Tue, 15 Dec 1998 10:28:54 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <55917(3)>; Tue, 15 Dec 1998 10:28:48 PST Received: by crevenia.parc.xerox.com id <177534>; Tue, 15 Dec 1998 10:23:36 -0800 From: Bill Fenner To: marcs@znep.com, wes@softweyr.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, robinson@netrinsics.com Message-Id: <98Dec15.102336pst.177534@crevenia.parc.xerox.com> Date: Tue, 15 Dec 1998 10:23:22 PST Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >it's not a bug, it's just a design decision. A poor design decision, which are sometimes called "bugs" by people who aren't trying to be precise. (buggy design vs. buggy implementation) A workaround, like the one I posted last night, would be even better than a socket option. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 10:57:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06485 for freebsd-net-outgoing; Tue, 15 Dec 1998 10:57:55 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06480 for ; Tue, 15 Dec 1998 10:57:52 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id KAA06285; Tue, 15 Dec 1998 10:57:19 -0800 (PST) (envelope-from marcs@znep.com) Date: Tue, 15 Dec 1998 10:57:19 -0800 (PST) From: Marc Slemko To: Wes Peters cc: Michael Robinson , fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-Reply-To: <3676A72D.E5FDF673@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 15 Dec 1998, Wes Peters wrote: > Marc Slemko wrote: > > > > No, it really is a bug. > > > > It is inherently broken to write multiple packets for one write() when the > > size of the write is far less than the MTU (well, the "effective MTU") > > unless you have extreme extenuating circumstances. > > I think you're confusing your ASSUMPTION that 1 write == 1 packet with > any requirement for this to be true. Nothing in the code or the doco > promises this behavior, so it's not a bug, it's just a design decision. Erm... "it is a design decision that any user can crash the kernel by doing xxx." You can call that a design decision, I call it a bug in the same way that this is a bug. You can't pretend bugs don't exist by calling them "design decisions". > > > It may not be a bug covered by any spec, but for people trying to write > > useful network apps it shoots them in the head. It is still a bug. > > In the vast majority of cases, it's the right choice to make, too. In > the few examples of network code that need to be highly responsive, it's > a terrible choice. These applications seem to be in the minority, since > so many find the system useful as it is. > > I've followed this discussion and strongly agree that the "right way" to > do this is to provide a socket option to turn off the default buffering > on a per-socket basis. This would make my packet-throughput program > actually WORK. ;^) > > Since the default is right for the vast majority of network programs, > the small added complexity of the sock option shouldn't be too horrible > to address. What on earth are you talking about? The "default" is NOT right. There are almost NO programs that benefit at ALL from having a write() of a few hundred bytes split into two TCP packets! It is completely nonsensical to talk about having a socket option to disable this. Now, this doesn't currently cause a major issue with all of the programs around. That doesn't mean it is the right thing to do for them! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 11:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11896 for freebsd-net-outgoing; Tue, 15 Dec 1998 11:23:37 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11890 for ; Tue, 15 Dec 1998 11:23:35 -0800 (PST) (envelope-from justin@scv4.apple.com) Received: from mailgate.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.8.5/8.8.5) with ESMTP id LAA19682 for ; Tue, 15 Dec 1998 11:14:04 -0800 Received: from scv4.apple.com (scv4.apple.com) by mailgate.apple.com (mailgate.apple.com - SMTPRS 2.0.15) with ESMTP id for ; Tue, 15 Dec 1998 11:13:57 -0800 Received: from localhost (grinch.apple.com [17.202.43.163]) by scv4.apple.com (8.8.5/8.8.5) with ESMTP id LAA12518 for ; Tue, 15 Dec 1998 11:13:38 -0800 Received: (from justin@localhost) by localhost (8.8.5/8.8.5) id LAA00996 for freebsd-net@freebsd.org; Tue, 15 Dec 1998 11:06:00 -0800 Message-Id: <19981215110600.D652@apple.com> Date: Tue, 15 Dec 1998 11:06:00 -0800 From: "Justin C. Walker" To: freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" Reply-To: justin@apple.com References: <199812151555.PAA07456@netrinsics.com> MIME-Version: 1.0 X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Marc Slemko on Tue, Dec 15, 1998 at 08:30:12AM -0800 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If I can horn in on the discussion, we have seen the problems you're debating, particularly when using request/response interactions over TCP. After beating our heads against a few walls, we came to the following conclusion: this is due (as has been observed before in this thread) to the separation between the job that the socket layer is doing, and the job that the TCP (or, generally, transport protocol) layer is doing. One way to smooth over the bump in the road is to provide a hint to the lower layer, so we have a socket state bit (SS_MORETOCOME) that we turn on (in so_state) just before calling the protocol send routine (PRU_SEND, ...), and turn off after the call returns. The hint is turned on only if resid is positive. In tcp_output(), in the 'if len { ...}' (following the comment on silly window avoidaince), we check for the bit: if (len) { if (len == tp->t_maxseg) goto send; if (!(so->so_state & SS_MORETOCOME)) { if ((idle || tp->t_flags & TF_NODELAY) && len + off >= so->so_snd.sb_cc) goto send; } if (tp->t_force) goto send; if (len >= tp->max_sndwnd / 2) goto send; if (SEQ_LT(tp->snd_nxt, tp->snd_max)) goto send; } Essentially, if there's more to come, we hold off sending; and we only believe there's more to come if the user has committed to it (in the form of a write request). This seems to smooth out (some of) the bumps caused by the user buffer/mbuf/cluster size differences and the request/response effects on the TCP state machines. Regards, Justin On Tue, Dec 15, 1998 at 08:30:12AM -0800, Marc Slemko wrote: > (-stable removed from the cc list, since this isn't particular to stable > in any way) > > On Tue, 15 Dec 1998, Michael Robinson wrote: > > > Bill Fenner writes: > > >You misunderstand. The fix is to accumulate mbufs in a chain until either > > >a) The protocol gets all of the data that it wanted, or > > >b) All of the data that the user has provided has been copied into mbufs. > > > > > >(b) is what sosend() used to do. The URL referenced (the one with > > >"vanj88" in it) describes why sosend() was changed to use only a single > > >mbuf at a time, but this performance problem was not envisioned at > > >the time. > > > > Ok, I misunderstood. But I still disagree it's a bug. Or, more precisely, > > it would be a bug if the socket API and the TCP protocol were seen as one > > inseparable entity, which is not the case. > > No, it really is a bug. > > It is inherently broken to write multiple packets for one write() when the > size of the write is far less than the MTU (well, the "effective MTU") > unless you have extreme extenuating circumstances. > > It may not be a bug covered by any spec, but for people trying to write > useful network apps it shoots them in the head. It is still a bug. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *---------------------------------------*------------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 12:48:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22741 for freebsd-net-outgoing; Tue, 15 Dec 1998 12:48:57 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22734 for ; Tue, 15 Dec 1998 12:48:55 -0800 (PST) (envelope-from wpeters@xylan.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id MAA10622; Tue, 15 Dec 1998 12:48:15 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA21840; Tue, 15 Dec 1998 12:48:15 -0800 Received: from xylan.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id NAA13973; Tue, 15 Dec 1998 13:48:14 -0700 Message-ID: <3676CB13.F97D4FA8@xylan.com> Date: Tue, 15 Dec 1998 13:48:19 -0700 From: Wes Peters Organization: Xylan Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Seidmann CC: freebsd-net@FreeBSD.ORG Subject: Re: ISDN for FreeBSD References: <36754AC1.5F05F9F1@xylan.com> <3675FECC.6CA55E61@simultan.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Seidmann wrote: > > Wes Peters wrote: > > I use user-mode PPP, and would like to support either bonding or MP so > > I can give her 128K throughput. Please advise on TAs, internal or > > external, that work well with PPP on FreeBSD. > > I'm using FreeBSD with an external TA omniNet LCD from ZyXel. It works > like a charm. > > > If I get an external TA, do I need to get either a sync serial card or > > a 16750 based async card? > > You just need a usual async serial port. Anyone know an special incantations to make a 3com Impact IQ work with mgetty? The Impact was a breeze to configure, but mgetty keeps complaining: 12/15 13:46:03 aa1 mgetty: experimental test release 1.1.11-Dec16 12/15 13:46:03 aa1 check for lockfiles 12/15 13:46:03 aa1 locking the line 12/15 13:46:06 aa1 WARNING: DSR is off - modem turned off or bad cable? 12/15 13:46:06 aa1 lowering DTR to reset Modem 12/15 13:46:07 aa1 send: ATS0=0Q0&D3&C1[0d] 12/15 13:46:07 aa1 waiting for ``OK'' 12/15 13:46:27 aa1 timeout in chat script, waiting for `OK' 12/15 13:46:27 aa1 init chat timed out, trying force-init-chat 12/15 13:46:27 aa1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d] 12/15 13:46:31 aa1 waiting for ``OK'' 12/15 13:46:51 aa1 timeout in chat script, waiting for `OK' 12/15 13:46:51 aa1 init chat failed, exiting...: Interrupted system call 12/15 13:46:51 ##### failed in mg_init_data, dev=cuaa1, pid=1228 Apparently the DSR problem is really giving mgetty fits. Any suggestions? -- Wes Peters Who's going to save you Principal Engineer When you're a slave to Xylan Corporation A diamond as big as the Ritz wpeters@xylan.com -- Jimmy Buffett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 13:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24778 for freebsd-net-outgoing; Tue, 15 Dec 1998 13:05:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24773 for ; Tue, 15 Dec 1998 13:05:44 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <57249(5)>; Tue, 15 Dec 1998 13:05:37 PST Received: from mango.parc.xerox.com (localhost.parc.xerox.com [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id NAA02831; Tue, 15 Dec 1998 13:05:31 -0800 (PST) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199812152105.NAA02831@mango.parc.xerox.com> To: justin@apple.com cc: freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 1998 11:06:00 PST." <19981215110600.D652@apple.com> Date: Tue, 15 Dec 1998 13:05:30 PST From: Bill Fenner Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A flag saying "more to come" was one of the other ways that I considered to fix this problem but never finished implementing. In FreeBSD, the usrreq functions have been split out and the individual functions accept flags, so in that case this flag can be passed as an argument to pru_send(). This gets around the requirement to set the flag before the call and reset it afterwards. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 13:21:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26900 for freebsd-net-outgoing; Tue, 15 Dec 1998 13:21:08 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26844 for ; Tue, 15 Dec 1998 13:21:06 -0800 (PST) (envelope-from justin@scv4.apple.com) Received: from mailgate.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.8.5/8.8.5) with ESMTP id NAA21248 for ; Tue, 15 Dec 1998 13:10:55 -0800 Received: from scv4.apple.com (scv4.apple.com) by mailgate.apple.com (mailgate.apple.com - SMTPRS 2.0.15) with ESMTP id ; Tue, 15 Dec 1998 13:10:49 -0800 Received: from localhost (grinch.apple.com [17.202.43.163]) by scv4.apple.com (8.8.5/8.8.5) with ESMTP id NAA60630; Tue, 15 Dec 1998 13:10:30 -0800 Received: (from justin@localhost) by localhost (8.8.5/8.8.5) id NAA01441; Tue, 15 Dec 1998 13:02:51 -0800 Message-Id: <19981215130251.N652@apple.com> Date: Tue, 15 Dec 1998 13:02:51 -0800 From: "Justin C. Walker" To: Bill Fenner Cc: freebsd-net@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" Reply-To: justin@apple.com References: <19981215110600.D652@apple.com> <199812152105.NAA02831@mango.parc.xerox.com> MIME-Version: 1.0 X-Mailer: Mutt 0.93.2i In-Reply-To: <199812152105.NAA02831@mango.parc.xerox.com>; from Bill Fenner on Tue, Dec 15, 1998 at 01:05:30PM -0800 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 15, 1998 at 01:05:30PM -0800, Bill Fenner wrote: > A flag saying "more to come" was one of the other ways that I > considered to fix this problem but never finished implementing. > In FreeBSD, the usrreq functions have been split out and the > individual functions accept flags, so in that case this flag can > be passed as an argument to pru_send(). This gets around the > requirement to set the flag before the call and reset it afterwards. Sounds like a good change; should we move to the 3.0 base, we'll probably use that mechanism instead of the 'so_state' hack. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *---------------------------------------*------------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 17:00:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26055 for freebsd-net-outgoing; Tue, 15 Dec 1998 17:00:12 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26050 for ; Tue, 15 Dec 1998 17:00:11 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA13448; Tue, 15 Dec 1998 16:59:31 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA01056; Tue, 15 Dec 1998 16:59:29 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id RAA16509; Tue, 15 Dec 1998 17:59:27 -0700 Message-ID: <367705EF.E1F3579F@softweyr.com> Date: Tue, 15 Dec 1998 17:59:27 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Wes Peters CC: Thomas Seidmann , freebsd-net@FreeBSD.ORG Subject: Re: ISDN for FreeBSD References: <36754AC1.5F05F9F1@xylan.com> <3675FECC.6CA55E61@simultan.ch> <3676CB13.F97D4FA8@xylan.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wes Peters wrote: > > Anyone know an special incantations to make a 3com Impact IQ work > with mgetty? The Impact was a breeze to configure, but mgetty > keeps complaining: Sorry to reply to my own message, but the above problem was caused by the Impact IQ "forgetting" the settings installed with the windows configuration program. The local IIQ whiz kid poked at it with CU and setup the SPIDs again; everything is fine now. It's answering calls and everything. Now if that serial port card would just show up... ;^) -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 17:21:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28790 for freebsd-net-outgoing; Tue, 15 Dec 1998 17:21:30 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from pth.com (pault.dca.primenet.com [206.165.112.189]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA28778 for ; Tue, 15 Dec 1998 17:21:25 -0800 (PST) (envelope-from paul@pth.com) Received: from pentium by pth.com (NX5.67g/NX3.0M) id AA14991; Tue, 15 Dec 98 20:25:12 -0500 X-Mailer: PopOver 2.0.131b (Windows NT; i386) From: "Paul T. Haddad" Date: Tue, 15 Dec 1998 20:20:56 -0500 To: freebsd-net@FreeBSD.ORG Subject: Connecting two separate nets via ppp Message-Id: <9812152020.AA564383@pentium> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Mime-Version: 1.0 X-Image-Url: http://www.primenet.com/~pault/paul.tiff Received: by NeXT.Mailer (PopOver.2.0.131b.RR) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA28784 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, Here's my situation I have two machines with the following IPs 1.1.1.1 and 1.1.1.2 I have a machine that I need to ppp into whose address is 2.2.2.100, now I want all traffic coming from the 1.1.1.X machines and going to 2.X.X.X to appear like it is coming from 2.2.2.1 and 2.2.2.2. For all other destinations the 1.1.1.X address should remain the same. Now 1.1.1.1 is the ppp client and its very easy to have that appear as 2.2.2.1 on the 2.X.X.X network, but any traffic coming from 1.1.1.2 appears to be coming from that direction and gets lost (since there is no route from 2.X to that machine). So what do I need to do the 1.1.1.1 and 2.2.2.100 machines so that packets leaving 1.1.1.2 and destined for 2.X get translated to 2.2.2.2 and packets going to 2.2.2.2 get translated/routed to 1.1.1.2? I think 2.2.2.100 needs an arp for the 1.1.1.2 and then a route from 2.2.2.2 to 2.2.2.1, but I'm not sure what to do on the 1.1.1.1 machine to have it translate the ip address from 1.X to 2.X. I hope this all made sense, I've been playing around with this most of the day and still haven't been able to figure it out. --- Paul (NeXTmail preferred) # Paul T. Haddad (paul@pth.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 17:24:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29360 for freebsd-net-outgoing; Tue, 15 Dec 1998 17:24:10 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([210.74.172.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29351 for ; Tue, 15 Dec 1998 17:24:03 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id JAA02496; Wed, 16 Dec 1998 09:20:58 GMT (envelope-from robinson) Date: Wed, 16 Dec 1998 09:20:58 GMT From: Michael Robinson Message-Id: <199812160920.JAA02496@netrinsics.com> To: marcs@znep.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, robinson@netrinsics.com In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc Slemko writes: >It is inherently broken to write multiple packets for one write() when the >size of the write is far less than the MTU (well, the "effective MTU") >unless you have extreme extenuating circumstances. Don't tell me. Tell Van Jacobson. It was his idea. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 15 19:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14378 for freebsd-net-outgoing; Tue, 15 Dec 1998 19:43:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt3-33.HiWAAY.net [208.147.146.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14356 for ; Tue, 15 Dec 1998 19:43:42 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id VAA69947; Tue, 15 Dec 1998 21:21:09 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199812160321.VAA69947@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Parker, David K" cc: freebsd-net@FreeBSD.ORG From: David Kelly Subject: Re: FreeBSD & CableModem In-reply-to: Message from "Parker, David K" of "Tue, 15 Dec 1998 12:14:52 CST." <6C94DFBFD20ED211A8E3006097A1760F02A136@xs.ci.bryan.tx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 21:21:09 -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Parker, David K" writes: > I hope I'm posting this to the correct list... > I have a PC setup with FreeBSD version 3.0. > My problem is with the TCP/IP Configuration and CableModem. > > If I place the PC on my internal network using an IP Address/SM/GW for a > Class C network, it works fine. I can resolve other host names, ping, etc... > > When I configure for our ISP using a cablemodem I have no such luck. Here is > the IP info... > IP: 208.162.121.228 > SM: 255.255.254.0 > GW: 208.162.120.1 > > I can ping the loopback and 208.162.121.228 but nothing else. > This same configuration works fine when I use an NT Box. You are running FreeBSD and NT different systems, right? I have been told that most cable modem boxes have a very limited IP protocol stack and are not intended to be placed on a multihost ethernet. After reset they grab the first hardware ethernet address and lock on to it. And will not talk to any other host until the next reset. If this is the case then your cable modem locked onto the NT box. Make a direct connection to your FreeBSD system from the cable modem. Then power cycle the cable modem. See if that works. Based on your discription I'd guess you are plugging your cable modem into a hub? Probably the Right Thing To Do would be to put two ethernet cards in your FreeBSD system and let FreeBSD be a NAT gateway and firewall for your other systems. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 16 05:04:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09790 for freebsd-net-outgoing; Wed, 16 Dec 1998 05:04:39 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from courier01.adinet.com.uy (mail.adinet.com.uy [206.99.44.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09783 for ; Wed, 16 Dec 1998 05:04:36 -0800 (PST) (envelope-from ang@adinet.com.uy) Received: from adinet.com.uy (tc2-166.w3.com.uy [207.3.118.166]) by courier01.adinet.com.uy (8.9.0/8.9.0) with ESMTP id KAA09669 for ; Wed, 16 Dec 1998 10:05:47 -0300 (GMT) Message-ID: <3677AFF5.46215126@adinet.com.uy> Date: Wed, 16 Dec 1998 10:04:53 -0300 From: Angelo Nardone X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" Subject: Hylafax modem ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a ActionTec ISA PnP modem, and I want to use in hylafax system. But I have some problem with the reception of the faxes. Have anybody a stable configuration for this modem ? Thank in advance Angelo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 16 06:27:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19745 for freebsd-net-outgoing; Wed, 16 Dec 1998 06:27:13 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19726; Wed, 16 Dec 1998 06:26:57 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id OAA02221; Wed, 16 Dec 1998 14:26:48 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma002206; Wed, 16 Dec 98 14:26:35 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zqHzA-0000Le-00; Wed, 16 Dec 1998 14:31:32 +0000 To: robinson@netrinsics.com, fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG From: Tony Finch Subject: Re: MLEN < write length < MINCLSIZE "bug" Newsgroups: chiark.mail.freebsd.net In-Reply-To: Organization: Deliberate Obfuscation To Amuse Tony References: <199812151555.PAA07456@netrinsics.com> Message-Id: Date: Wed, 16 Dec 1998 14:31:32 +0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fenner wrote: >In message <199812151555.PAA07456@netrinsics.com> you write: >> >>Is there any documentation on why MINCLSIZE is currently set to the value it >>is? > >Not that I know of, but I can't say for sure that there's not something >in the 4.4 daemon book. Having read this bit of the red demon book recently (although I can't find the precise reference again at the moment), ISTR that the heuristic is that since allocating an mbuf with a cluster takes two allocations, MINCLSIZE is just bigger than two mbufs. Tony. -- f.a.n.finch**waster dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 16 10:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20185 for freebsd-net-outgoing; Wed, 16 Dec 1998 10:18:13 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([210.74.175.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20079 for ; Wed, 16 Dec 1998 10:17:49 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id CAA00532; Thu, 17 Dec 1998 02:13:10 GMT (envelope-from robinson) Date: Thu, 17 Dec 1998 02:13:10 GMT From: Michael Robinson Message-Id: <199812170213.CAA00532@netrinsics.com> To: dot@dotat.at Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tony Finch writes: >Having read this bit of the red demon book recently (although I can't >find the precise reference again at the moment), ISTR that the >heuristic is that since allocating an mbuf with a cluster takes two >allocations, MINCLSIZE is just bigger than two mbufs. So it is as I suspected. MINCLSIZE is a parameter for a classic time/space performance tradeoff. A small MINCLSIZE gives you fewer mbuf allocations, but with lots of unused space in mbuf clusters. A big MINCLSIZE gives you more mbuf allocations, and more copy operations, but with more efficient memory use. As such, MINCLSIZE seems like a good candidate for a sysctl (a patch for which can be found at the end of this message). People running heavily-used dedicated network servers may find it useful to be able to tune this parameter. It seems to me that this is largely orthogonal, though, to the issue of segmenting writes in sosend before sending them to the protocol. That is more an issue of hardware speed vs. kernel speed. For example, on a dialup PPP connection, the additional packet header overhead vastly outweighs the mostly non-existent parallelism of the serial interface. However, a 100Mhz 64-bit PCI gigabit Ethernet controller can process buffers faster than the CPU can spit them out, so segmenting the writes could result in significant improvements in throughput and latency. So I think this behavior is something that one should be able to turn on and off. The question is with what granularity: kernel, interface, or socket? A socket option would be trivial to implement, but wouldn't work for existing code until it was retrofitted in. A sysctl would also be trivial to implement, would work with existing code, but the granularity is probably to coarse. A new option for ifconfig would work at the interface level, but I don't know if that's what people want or will accept. Comments? -Michael Robinson Index: sys/mbuf.h =================================================================== RCS file: /cdrom/CVSROOT/src/sys/sys/mbuf.h,v retrieving revision 1.18 diff -u -r1.18 mbuf.h --- mbuf.h 1996/08/19 18:30:15 1.18 +++ mbuf.h 1998/12/17 01:39:44 @@ -52,7 +52,8 @@ #define MLEN (MSIZE - sizeof(struct m_hdr)) /* normal data len */ #define MHLEN (MLEN - sizeof(struct pkthdr)) /* data len w/pkthdr */ -#define MINCLSIZE (MHLEN + MLEN) /* smallest amount to put in cluster */ +extern int minclsize; +#define MINCLSIZE minclsize /* smallest amount to put in cluster */ #define M_MAXCOMPRESS (MHLEN / 2) /* max amount to copy for compression */ /* Index: sys/sysctl.h =================================================================== RCS file: /cdrom/CVSROOT/src/sys/sys/sysctl.h,v retrieving revision 1.48.2.2 diff -u -r1.48.2.2 sysctl.h --- sysctl.h 1997/08/30 14:08:56 1.48.2.2 +++ sysctl.h 1998/12/17 01:39:58 @@ -231,6 +231,7 @@ #define KERN_PS_STRINGS 32 /* int: address of PS_STRINGS */ #define KERN_USRSTACK 33 /* int: address of USRSTACK */ #define KERN_MAXID 34 /* number of valid kern ids */ +#define KERN_MINCLSIZE 35 /* minumum size for mbuf cluster */ #define CTL_KERN_NAMES { \ { 0, 0 }, \ @@ -267,6 +268,7 @@ { "maxsockbuf", CTLTYPE_INT }, \ { "ps_strings", CTLTYPE_INT }, \ { "usrstack", CTLTYPE_INT }, \ + { "minclsize", CTLTYPE_INT }, \ } /* Index: kern/uipc_socket.c =================================================================== RCS file: /cdrom/CVSROOT/src/sys/kern/uipc_socket.c,v retrieving revision 1.20.2.5 diff -u -r1.20.2.5 uipc_socket.c --- uipc_socket.c 1998/03/02 07:58:12 1.20.2.5 +++ uipc_socket.c 1998/12/17 01:40:26 @@ -53,6 +53,9 @@ static int somaxconn = SOMAXCONN; SYSCTL_INT(_kern, KERN_SOMAXCONN, somaxconn, CTLFLAG_RW, &somaxconn, 0, ""); +int minclsize = (MHLEN + MLEN); +SYSCTL_INT(_kern, KERN_MINCLSIZE, minclsize, CTLFLAG_RW, &minclsize, 0, ""); + /* * Socket operation routines. * These routines are called by the routines in To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 17 07:10:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06972 for freebsd-net-outgoing; Thu, 17 Dec 1998 07:10:53 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA06966 for ; Thu, 17 Dec 1998 07:10:52 -0800 (PST) (envelope-from Jean-Marc.Fenart@France.Sun.COM) Received: from France.Sun.COM ([129.157.188.1]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id HAA15483 for ; Thu, 17 Dec 1998 07:10:38 -0800 Received: from sunchorus.france.sun.com by France.Sun.COM (SMI-8.6/SMI-SVR4-sd.fkk200) id QAA26773 for ; Thu, 17 Dec 1998 16:10:35 +0100 Received: from bagana.France.Sun.COM by sunchorus.france.sun.com (SMI-8.6/SMI-SVR4) id QAA23487; Thu, 17 Dec 1998 16:10:34 +0100 Received: from bagana by bagana.France.Sun.COM (SMI-8.6/SMI-SVR4) id QAA29170; Thu, 17 Dec 1998 16:09:09 +0100 Message-Id: <199812171509.QAA29170@bagana.France.Sun.COM> Date: Thu, 17 Dec 1998 16:09:09 +0100 (MET) From: Jean-Marc Fenart Reply-To: Jean-Marc Fenart Subject: PPP post-dialup To: freebsd-net@FreeBSD.ORG Cc: =?US-ASCII?Q?fenart=10?=@sunchorus.France.Sun.COM MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: Tpe0VASYWHcY5sOA4EgbRw== X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear all I've a problem trying to find a solution implementing a post-dialup on PPP. I should like to dialup and get the IPCP dynamic IP address after the initial configuration of the interface and during a sento/connect of an application. The ppp ifnet would notice that the dialup has not been done and might trigger an upcall to the pppd for dialup and IPCP negotiation. The overall algorithm might look like : 1/ configure PPP ifnet with a dummy IP local address. 2/ application performs a socket call on it. 3/ PPP interface triggers the dialup, 4/ get the dynamic IP address 5/ re-configure the interface The PPP deamon/ifnet etc.. on FreeBSD does not know to do this, are you aware of a good way (better way ?) to implement this. Thank's for your help. - JM Fenart - _________________________________________________________________ Sun Microsystems, Inc. Embedded Systems Software Group (was Chorus Systems, Inc.) Jean-Marc Fenart 6, ave Gustave Eiffel Tel: +33 1 30 64 82 23 78182 Saint Quentin en Yvelines Fax: +33 1 30 57 00 66 France email: fenart@France.Sun.Com http://www.chorus.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 17 08:48:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17713 for freebsd-net-outgoing; Thu, 17 Dec 1998 08:48:33 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from chappe.cnes.fr (chappe.cnes.fr [132.149.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17705 for ; Thu, 17 Dec 1998 08:48:30 -0800 (PST) (envelope-from kevin.choi@cnes.fr) Received: from pasteur.cst.cnes.fr (pasteur.cnes.fr [132.149.22.8]) by chappe.cnes.fr (8.9.1a/1a/981005) with ESMTP id RAA29862 for ; Thu, 17 Dec 1998 17:48:05 +0100 (MET) Received: from imhotep.cst.cnes.fr (unverified) by pasteur.cst.cnes.fr (Content Technologies SMTPRS 2.0.15) with SMTP id for ; Thu, 17 Dec 1998 17:47:19 +0100 Received: from pc-kichoi (pc-kichoi.cst.cnes.fr [132.149.9.82]) by imhotep.cst.cnes.fr (8.6.12/MH-19960223.01) with SMTP id RAA06661 for ; Thu, 17 Dec 1998 17:48:57 +0100 Message-Id: <199812171648.RAA06661@imhotep.cst.cnes.fr> From: "Kevin Kyeong-il CHOI" To: "FreeBSD Net" Date: Thu, 17 Dec 1998 17:48:18 +0100 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth d921fa1f unsubscribe freebsd-net kevin.choi@cnes.fr auth b0053cb6 unsubscribe freebsd-small kevin.choi@cnes.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 17 13:53:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22680 for freebsd-net-outgoing; Thu, 17 Dec 1998 13:53:54 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22639; Thu, 17 Dec 1998 13:53:42 -0800 (PST) (envelope-from wpeters@xylan.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id NAA02739; Thu, 17 Dec 1998 13:53:26 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id NAA02962; Thu, 17 Dec 1998 13:53:26 -0800 Received: from xylan.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id OAA03688; Thu, 17 Dec 1998 14:53:25 -0700 Message-ID: <36797D5B.B6E00968@xylan.com> Date: Thu, 17 Dec 1998 14:53:31 -0700 From: Wes Peters Organization: Xylan Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: PPP and mgetty vs. MicroSloth Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a user attempting to dial in via ISDN from an NoTworkstation 4.0 machine. We've switched her connection from analog modems to ISDN, using two 3Com Impact IQ TAs. mgetty, which has been working flawlessly until now, will not start AutoPPP for love nor money. I'm at my wits end, and she's driving me crazy wanting to have this working tomorrow, so she can spend the day at home cooking and (ahem) working from home. Any help? Any magic incantations? Another engineer in the office has been able to dial in easily using Linux, so this appears to be associated with MicroSloth's infamously screwed PPP startup. Curiously, though, the same configuration work(ed) via analog modem. Help! -- Wes Peters Who's going to save you Principal Engineer When you're a slave to Xylan Corporation A diamond as big as the Ritz wpeters@xylan.com -- Jimmy Buffett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 17 15:57:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07543 for freebsd-net-outgoing; Thu, 17 Dec 1998 15:57:23 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from dnai.com (dnai.com [207.181.194.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07522; Thu, 17 Dec 1998 15:57:21 -0800 (PST) (envelope-from miket@dnai.com) Received: from desktop (dnai-207-181-255-44.dialup.dnai.com [207.181.255.44]) by dnai.com (8.8.8/8.8.8) with SMTP id PAA00540; Thu, 17 Dec 1998 15:55:49 -0800 (PST) Message-Id: <199812172355.PAA00540@dnai.com> X-Sender: miket@mail.dnai.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Thu, 17 Dec 1998 15:54:30 -0800 To: Wes Peters , freebsd-net@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG From: Mike Thompson Subject: Re: PPP and mgetty vs. MicroSloth In-Reply-To: <36797D5B.B6E00968@xylan.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 02:53 PM 12/17/98 -0700, Wes Peters wrote: >I have a user attempting to dial in via ISDN from an NoTworkstation 4.0 >machine. We've switched her connection from analog modems to ISDN, >using two 3Com Impact IQ TAs. Wes, Try adding the "-D 9" setting to the mgetty entry in your /etc/ttys file and then signal init "kill -1 1" and restart mgetty. This should create a debug file in the /tmp directory where you can do a "tail -f" command to follow the communication sequence between the serial port and the 3Com Impact. You will probably see something pretty obvious in the AT commands that are exchanged between mgetty and the 3Com Impact. If I had to guess, I would bet the 3Com Impact may not be returning a "RING" string that mgetty uses to trigger the "ATA" command for the Impact to pick up the line. Or, the Impact is not returning a proper "CONNECT" once the line is answered for mgetty to continue the login sequence. The debug log should make the problem obvious. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 18 11:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15769 for freebsd-net-outgoing; Fri, 18 Dec 1998 11:12:46 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ns1.raymondkarsan.com ([208.193.103.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA15763 for ; Fri, 18 Dec 1998 11:12:44 -0800 (PST) (envelope-from JJaapar@RaymondKarsan.com) Received: from rkawa1ex01.rka.net by ns1.raymondkarsan.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 18 Dec 1998 19:10:55 UT Received: (private information removed) Message-ID: <1078975B4A4FD211846200805F85D59F6C7EA3@RKAWA1EX01> From: "Jaapar, Jazzery" To: freebsd-net@FreeBSD.ORG Subject: IPFW-Newbie Question-Request For Assistance Date: Fri, 18 Dec 1998 14:11:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To Whom It May Concern, I need/want to setup a PC as a gateway for our local lan. There's 3 NICs:- fxp0: Internet Interface (lets say 111.111.111.1) fxp1: DMZ Interface (192.XXX.XXX.XXX) ep0: LAN Interface (10.XXX.XXX.XXX) fxp0 is connected to our router. fxp1 is connected to a hub which connects to the www,dns,ftp and mail server. ep0 is connected to the LAN. I need to allow 1) internal ip to internet(ftp/www/etc) and dmz servers 2) internet to dmz servers 3) block certain internal ip from the internet and dmz servers I've read the documentation on ipfw and frankly I'm stumped. I have a general idea of how to set it up but it would help me greatly if someone could offer any ideas or suggestions. Please reply by e-mail as i have not yet subscribe to the mailing list. Thank You. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message