From owner-freebsd-net Mon Aug 31 04:14:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02728 for freebsd-net-outgoing; Mon, 31 Aug 1998 04:14:00 -0700 (PDT) (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 EAA02721 for ; Mon, 31 Aug 1998 04:13:58 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA07622; Mon, 31 Aug 1998 11:17:29 +0200 From: Luigi Rizzo Message-Id: <199808310917.LAA07622@labinfo.iet.unipi.it> Subject: picobsd+bridging To: net@FreeBSD.ORG Date: Mon, 31 Aug 1998 11:17:29 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, for those who want to try the bridging code without messing up with compiles etc, i have put up a picobsd version (based on 2.2.6) with bridging enabled -- it supports various cards natively and it boots up with userconfig. Do whatever card config you need (or just type "quit"), then the system boots up with bridging enabled. http://www.iet.unipi.it/~luigi/picobdg980831.bin (it's a picobsd image, 1.44MB, dd it to a floppy and boot from it). Support is for the following cards: ed tested lnc tested de tested fxp untested -- feedback required cheers 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 Tue Sep 1 02:32:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17869 for freebsd-net-outgoing; Tue, 1 Sep 1998 02:32:45 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ultra.ultra.net.au (ultra.ultra.net.au [203.20.237.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17864 for <"freebsd-net@"@FreeBSD.ORG>; Tue, 1 Sep 1998 02:32:43 -0700 (PDT) (envelope-from lbarton@ultra.net.au) Received: from lbarton.ultra.net.au (cadmium.elemental.ultra.net.au [203.20.237.68]) by ultra.ultra.net.au (8.8.8/8.8.8) with SMTP id TAA15245 for <"freebsd-net@"@FreeBSD.ORG>; Tue, 1 Sep 1998 19:35:35 +1000 (EST) Message-ID: <007f01bdd58c$65d15fc0$44ed14cb@lbarton.ultra.net.au> From: "Lee-Ann Barton" To: "freebsd-net@\"@FreeBSD.ORG" <"freebsd-net@"@FreeBSD.ORG> Subject: NOVELL AND FREEBSD Date: Tue, 1 Sep 1998 19:39:19 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007C_01BDD5E0.362DBE40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_007C_01BDD5E0.362DBE40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi=20 My freebsd box is attached via UTP to my hub which connects to my Novell = server. All the users log in as Novell users. They connect to the internet via the freebsd box. I want the other novell file servers in other buildings which are all = connected via fibre optic. The fibre optic is connected to a hub which = is connected to the novell file server. I want workstations which log on = to the novell server to communicate with the freebsd box in another = building. When I ping the freebsd box from a workstation in another building, = configured with IP address, it " requests time out". Can anyone provide assistance lee-ann barton ------=_NextPart_000_007C_01BDD5E0.362DBE40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hi
My freebsd box is attached via UTP = to my hub=20 which connects to my Novell server.
All the users log in as Novell=20 users.
They connect to the internet via the = freebsd=20 box.
I want the other novell file servers = in other=20 buildings which are all connected via fibre optic. The fibre optic is = connected=20 to a hub which is connected to the novell file server. I want = workstations which=20 log on to the novell server to communicate with the freebsd box in = another=20 building.
 
When I ping the freebsd box from a workstation in = another=20 building, configured with IP address, it " requests time=20 out".
Can anyone provide assistance
 
lee-ann barton
------=_NextPart_000_007C_01BDD5E0.362DBE40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 1 03:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23453 for freebsd-net-outgoing; Tue, 1 Sep 1998 03:33:14 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ii.pilsnet.sunet.se (ii.pilsnet.sunet.se [192.36.125.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23448 for <"freebsd-net@"@FreeBSD.ORG>; Tue, 1 Sep 1998 03:33:10 -0700 (PDT) (envelope-from bengan@ii.pilsnet.sunet.se) Received: (from bengan@localhost) by ii.pilsnet.sunet.se (8.8.8/8.8.5) id MAA01625; Tue, 1 Sep 1998 12:31:07 +0200 (CEST) Message-ID: <19980901123107.A1560@sunet.se> Date: Tue, 1 Sep 1998 12:31:07 +0200 From: Bengt Gorden To: Lee-Ann Barton , "freebsd-net@@FreeBSD.ORG" <"freebsd-net@"@FreeBSD.ORG> Subject: Re: NOVELL AND FREEBSD References: <007f01bdd58c$65d15fc0$44ed14cb@lbarton.ultra.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <007f01bdd58c$65d15fc0$44ed14cb@lbarton.ultra.net.au>; from Lee-Ann Barton on Tue, Sep 01, 1998 at 07:39:19PM +1000 X-Mutt-References: <007f01bdd58c$65d15fc0$44ed14cb@lbarton.ultra.net.au> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 01, 1998 at 07:39:19PM +1000, Lee-Ann Barton wrote: > hi > My freebsd box is attached via UTP to my hub which connects to my Novell server. > All the users log in as Novell users. > They connect to the internet via the freebsd box. > I want the other novell file servers in other buildings which are all connected via fibre optic. The fibre optic is connected to a hub which is connected to the novell file server. I want workstations which log on to the novell server to communicate with the freebsd box in another building. > > When I ping the freebsd box from a workstation in another building, configured with IP address, it " requests time out". > Can anyone provide assistance It seems that you have two interfaces in your fileserver, is that right? If so, you need to turn on IP-routing on the fileserver, if it can handle that. I don't know the Novell fileserver, so I cant provide any help for that. -- /Bengan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 1 09:36:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07103 for freebsd-net-outgoing; Tue, 1 Sep 1998 09:36:46 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07097 for <"freebsd-net@"@FreeBSD.ORG>; Tue, 1 Sep 1998 09:36:44 -0700 (PDT) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.8.8/8.8.8) with SMTP id MAA09720; Tue, 1 Sep 1998 12:33:17 -0500 (EST) (envelope-from jim@web-ex.com) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Tue, 1 Sep 1998 12:33:17 -0500 (EST) From: Jim Cassata To: Lee-Ann Barton cc: "freebsd-net@\"@FreeBSD.ORG" <"freebsd-net@"@FreeBSD.ORG> Subject: Re: NOVELL AND FREEBSD In-Reply-To: <007f01bdd58c$65d15fc0$44ed14cb@lbarton.ultra.net.au> 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 I can help you, but it sounds like it might be easier to troubleshoot over the phone. Jim Cassata 516.421.6000x203 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Tue, 1 Sep 1998, Lee-Ann Barton wrote: > hi > My freebsd box is attached via UTP to my hub which connects to my Novell server. > All the users log in as Novell users. > They connect to the internet via the freebsd box. > I want the other novell file servers in other buildings which are all connected via fibre optic. The fibre optic is connected to a hub which is connected to the novell file server. I want workstations which log on to the novell server to communicate with the freebsd box in another building. > > When I ping the freebsd box from a workstation in another building, configured with IP address, it " requests time out". > Can anyone provide assistance > > lee-ann barton > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 1 10:31:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16780 for freebsd-net-outgoing; Tue, 1 Sep 1998 10:31:59 -0700 (PDT) (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 KAA16677; Tue, 1 Sep 1998 10:31:32 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09416; Tue, 1 Sep 1998 17:35:33 +0200 From: Luigi Rizzo Message-Id: <199809011535.RAA09416@labinfo.iet.unipi.it> Subject: Announce: BRIDGE/IPFW/DUMMYNET PicoBSD stuff... To: net@FreeBSD.ORG Date: Tue, 1 Sep 1998 17:35:32 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, lot of stuff to announce... (Bcc to -hackers and -committers...) My dear committers: is there anyone out there who is willing to revise the code and import it into -current and/or -stable ??? http://www.iet.unipi.it/~luigi/ip_dummynet/bridge.html i have mostly finished and tested the bridging patches for FreeBSD, a diff file for 2.2.x (and might even work on -current if someone wants to try...) is available. http://www.iet.unipi.it/~luigi/ip_dummynet/ I have also cleaned up dummynet for 2.2.7 (lots of people asking...) removing the last few bugs (now it works with natd, thanks to Philippe Regnauld who tested it extensively). This code includes a significant performance improvement in SKIPTO instructions. Patches and docs available at the above URL. http://www.iet.unipi.it/~luigi/ip_dummynet/bridge.html And since i was at it... i decided to build a PicoBSD floppy with BRIDGING, IPFW, and DUMMYNET on it... on 2.2.6 At the above URL you can find both the diffs to make PicoBSD compile on 2.2.6/2.2.7 (small enough) and a floppy image with the above. Want to know more ? Check the URLs... cheers 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 Tue Sep 1 15:51:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10922 for freebsd-net-outgoing; Tue, 1 Sep 1998 15:51:12 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10905; Tue, 1 Sep 1998 15:50:59 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA14301; Tue, 1 Sep 1998 23:57:34 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA29423; Wed, 2 Sep 1998 00:51:10 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id AAA03809; Wed, 2 Sep 1998 00:36:29 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Wed, 2 Sep 1998 00:36:28 +0200 (CEST) From: Stefan Bethke Reply-To: Stefan Bethke To: net@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with MGET(m, M_WAIT, *) [was: Semantics of ...] In-Reply-To: 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, 25 Aug 1998, Stefan Bethke wrote: > On Tue, 25 Aug 1998, Garrett Wollman wrote: > > > < > > said: > > > > > What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest > > > that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes > > > available, as it is already the case if the vm map must be extended. > > > > It should sleep, but actually doing so while avoiding deadlocks is > > problematic. Since the mbuf allocator as currently formulated is > > going away, callers to mget should expect that the allocation might > > fail, but that M_WAIT makes it ``try harder'' as it were. According to TCP Illustrated Vol II, p. 42: Even though the caller specifies M_WAIT, ther return value must still be checked, since [...] waiting for an mbuf does not guarantee that one will be available. Although our mbuf allocator is modified, it pretty much describes the semantics. I've tried to locate pieces of code in a recent -current that use M_WAIT, but don't check for the return value. Interestingly enought, only 23 occurences of 160 total in the source use M_WAIT at all. For m_get(), its 22 to 110. Checking the 45 hits for pieces of code shows the following problem areas: For a total of 22 occurences, the return value isn't checked, in: kern/uipc_socket:479 and :484, :1059 (including sosend()) netinet/ip_output.c:869, :884, :927, and :1345 netinet/raw_ip.c:285 netinet/tcp_usrreq.c:641 netkey/key.c:2199 nfs/krpc_subr.c:283 and :474 nfs/nfs_serv.c:517 and :685 nfs/nfs_socket.c:285 and :1188 nfs/nfs_subs.c:589, :684, :713, :746, :889, :921, :970, and :1063 In additional two occurences, I'm not sure, but I regard it as quite likely that the function called will stumble over a NULL mbuf pointer, or a pointer to it: kern/uipc_socket.c:597 netinet/ip_mroute.c:425 So I have the following questions: As Garrett said, the current mbuf allocator is going to go away. Is it? I tried to find anything about it in the list archives, but to no avail. Will the semantics of the new mbuf allocator be the same (M_WAIT may return 0)? I guess so, but the one(s) working on the new allocator might want to confirm that. If so, should I start on trying to fix it, or will it be easy enougth to fix these bugs when the new allocator is coming? At least some these occurences seam to be fixable quite easily. Thanks, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 1 20:30:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24424 for freebsd-net-outgoing; Tue, 1 Sep 1998 20:30:55 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24419 for ; Tue, 1 Sep 1998 20:30:53 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id XAA02805; Tue, 1 Sep 1998 23:29:42 -0400 (EDT) (envelope-from wollman) Date: Tue, 1 Sep 1998 23:29:42 -0400 (EDT) From: Garrett Wollman Message-Id: <199809020329.XAA02805@khavrinen.lcs.mit.edu> To: Stefan Bethke Cc: net@FreeBSD.ORG Subject: Re: Problems with MGET(m, M_WAIT, *) [was: Semantics of ...] In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > As Garrett said, the current mbuf allocator is going to go away. Is > it? Yes -- but it will take some time. The eventual goal is for interfaces to manage their own memory allocation -- some interfaces may have unusual requirements for memory which is being used as a buffer. (Something like the current mbuf allocator will probably remain to service those interfaces which don't have any special requirements. Even for those interfaces, however, it would be more memory-efficient to only allocate 1536 bytes per buffer (assuming Ethernet) than a full 2K cluster -- the current scheme wastes 25% on Ethernet-sized packets.) > Will the semantics of the new mbuf allocator be the same (M_WAIT may > return 0)? I guess so, but the one(s) working on the new allocator might > want to confirm that. This seems likely, although we ought to be able to do a bit better than the fixed-size map we have now. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 1 22:11:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10280 for freebsd-net-outgoing; Tue, 1 Sep 1998 22:11:12 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from word.smith.net.au (castles304.castles.com [208.214.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10202; Tue, 1 Sep 1998 22:11:01 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id WAA00723; Tue, 1 Sep 1998 22:07:52 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809012207.WAA00723@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Bethke cc: net@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Problems with MGET(m, M_WAIT, *) [was: Semantics of ...] In-reply-to: Your message of "Wed, 02 Sep 1998 00:36:28 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Sep 1998 22:07:51 +0000 From: Mike Smith Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest > > > > that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes > > > > available, as it is already the case if the vm map must be extended. > > > > > > It should sleep, but actually doing so while avoiding deadlocks is > > > problematic. Since the mbuf allocator as currently formulated is > > > going away, callers to mget should expect that the allocation might > > > fail, but that M_WAIT makes it ``try harder'' as it were. This comment is significant in the context of a question you ask later. > According to TCP Illustrated Vol II, p. 42: > > Even though the caller specifies M_WAIT, ther return value must still be > checked, since [...] waiting for an mbuf does not guarantee that one > will be available. > > Although our mbuf allocator is modified, it pretty much describes the > semantics. Yes. > I've tried to locate pieces of code in a recent -current that use M_WAIT, > but don't check for the return value. Interestingly enought, only 23 > occurences of 160 total in the source use M_WAIT at all. For m_get(), its 22 > to 110. How many of those that don't wait handle a NULL return correctly? Any idea how many of them *might* be able to wait? > Checking the 45 hits for pieces of code shows the following problem > areas: > > For a total of 22 occurences, the return value isn't checked, in: > kern/uipc_socket:479 and :484, :1059 (including sosend()) > netinet/ip_output.c:869, :884, :927, and :1345 > netinet/raw_ip.c:285 > netinet/tcp_usrreq.c:641 > netkey/key.c:2199 > nfs/krpc_subr.c:283 and :474 > nfs/nfs_serv.c:517 and :685 > nfs/nfs_socket.c:285 and :1188 > nfs/nfs_subs.c:589, :684, :713, :746, :889, :921, :970, and :1063 > > In additional two occurences, I'm not sure, but I regard it as quite likely > that the function called will stumble over a NULL mbuf pointer, or a pointer > to it: > kern/uipc_socket.c:597 > netinet/ip_mroute.c:425 > > So I have the following questions: > As Garrett said, the current mbuf allocator is going to go away. Is it? I > tried to find anything about it in the list archives, but to no avail. I believe that Garrett is working on a replacement. It's possible that it will be using the zone allocator, but I don't remember why I thought that. > Will the semantics of the new mbuf allocator be the same (M_WAIT may > return 0)? I guess so, but the one(s) working on the new allocator might > want to confirm that. If I read the comment I referenced above correctly, it's describing how consumers should behave in order to work with the pending new allocator. > If so, should I start on trying to fix it, or will it be easy enougth to > fix these bugs when the new allocator is coming? At least some these > occurences seam to be fixable quite easily. Definitely fix them. If you run into ones that might need more attention (ie. not an easy fix), then applying either a warning comment or a #warning diagnostic to them to flag the problems might actually be a very good idea. Thanks for the analysis! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 2 07:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24544 for freebsd-net-outgoing; Wed, 2 Sep 1998 07:11:10 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24529 for ; Wed, 2 Sep 1998 07:11:07 -0700 (PDT) (envelope-from dennis@bbn.com) Received: from bbn.com (DROCKWELL.BBN.COM [128.89.31.139]) by po1.bbn.com (8.8.6/8.8.6) with ESMTP id KAA06312; Wed, 2 Sep 1998 10:10:02 -0400 (EDT) Message-Id: <199809021410.KAA06312@po1.bbn.com> To: Garrett Wollman cc: net@FreeBSD.ORG Subject: Re: Problems with MGET(m, M_WAIT, *) [was: Semantics of ...] In-reply-to: Message from Garrett Wollman <199809020329.XAA02805@khavrinen.lcs.mit.edu> . X-face: &R'hN{mZu#r@8b_JU\bn"!fYpP{?5k4p/(|]?.2'6;>Dc9}~t*vY=/#-:"63ya.%)%o`Kv$ u&'Ff5k&n[}QC;j7YYsR5Hl]G"E:*9Zmw;dx[sw&9Tmx_PB/7B`RdFW;#@49hJU&kW+J"<[`9^?.dQ 3]L$zK,4'=tThX$wC!M\`e*@1y Date: Wed, 02 Sep 1998 10:10:04 -0400 From: Dennis Rockwell Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1 Sep, Garrett Wollman wrote: > Yes -- but it will take some time. The eventual goal is for > interfaces to manage their own memory allocation -- some interfaces > may have unusual requirements for memory which is being used as a > buffer. How will you be dealing with consumers that don't consume quickly? An interface-dedicated buffer, holding a single character of payload, sitting on somebody's TCP input queue doesn't seem very efficient, either. Just curious -- I've done some similar work myself in former lives. Dennis Rockwell dennis@bbn.com GTE Internetworking Powered by BBN +1-617-873-5745 Cambridge, MA +1-617-873-6091 (Fax) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 2 18:53:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19498 for freebsd-net-outgoing; Wed, 2 Sep 1998 18:53:09 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19458; Wed, 2 Sep 1998 18:52:53 -0700 (PDT) (envelope-from kwanalex@hkstar.com) Received: from home ([202.82.192.62]) by smtp.hkstar.com (8.8.8/8.8.4) with SMTP id JAA21723; Thu, 3 Sep 1998 09:51:31 +0800 (HKT) X-Authentication-Warning: cassiopeia.hkstar.com: Host [202.82.192.62] claimed to be home Message-ID: <000b01bdd6dd$90fa9660$0300a8c0@home> From: "Alex Kwan" To: Cc: Subject: How to add route Date: Thu, 3 Sep 1998 09:52:43 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I am building a LAN with FreeBSD, and that is no need to connect to another LAN, I alreay have setup the hosts, and I ping the loopback, it is o.k. but I can't ping the host the error is being that I have not add route I use the linux command (I was a linux user before) : route add -net 192.168.1.0 netmask 255.255.255.0 ed0 but it is not work with FreeBSD, how to add route in FreeBSD? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 2 19:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25596 for freebsd-net-outgoing; Wed, 2 Sep 1998 19:29:18 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from calis.BlackSun.org (slip-ppp-4-198.escape.com [205.160.46.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25577; Wed, 2 Sep 1998 19:29:15 -0700 (PDT) (envelope-from don@calis.BlackSun.org) Received: from localhost (don@localhost) by calis.BlackSun.org (8.8.8/8.8.7) with SMTP id WAA10097; Wed, 2 Sep 1998 22:28:24 -0400 (EDT) (envelope-from don@calis.BlackSun.org) Date: Wed, 2 Sep 1998 22:28:24 -0400 (EDT) From: Don To: Alex Kwan cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: How to add route In-Reply-To: <000b01bdd6dd$90fa9660$0300a8c0@home> 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 > I use the linux command (I was a linux user before) : > route add -net 192.168.1.0 netmask 255.255.255.0 ed0 the command should be: route add -net -netmask -interface or in your case: route add -net 192.168.1.0 -netmask 255.255.255.0 -interface ed0 the -interface flag is required for the route addition and netmask requires a - in front of it to signal the flag. -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 2 20:03:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00937 for freebsd-net-outgoing; Wed, 2 Sep 1998 20:03:43 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA00932; Wed, 2 Sep 1998 20:03:42 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zEPeg-0006uF-00; Wed, 2 Sep 1998 20:01:50 -0700 Date: Wed, 2 Sep 1998 20:01:47 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Don cc: Alex Kwan , freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: How to add route In-Reply-To: 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 Wed, 2 Sep 1998, Don wrote: > > I use the linux command (I was a linux user before) : > > route add -net 192.168.1.0 netmask 255.255.255.0 ed0 > the command should be: > route add -net -netmask -interface > or in your case: > route add -net 192.168.1.0 -netmask 255.255.255.0 -interface ed0 In most cases the "-net" bit is not required. "Classic UNIX" route syntax is: route add 192.168.1.0 192.168.1.1 (where 192.168.1.1 is the gateway). When UNIX went classless, the "-netmask" param was added, so the netmask of the route could be specified. Since then most Unixes have adopted (including FreeBSD) the more convienent, "/bits" syntax: route add 192.168.1.0/24 192.168.1.1 > the -interface flag is required for the route addition and netmask Interface flags is NOT required. The interface should always be implied by the gateway address anyhow. Using the "-interface" flag can do funny things. In fact, it is only recent that "-interface" even works on FreeBSD. > requires a - in front of it to signal the flag. > > -don Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 2 20:26:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03903 for freebsd-net-outgoing; Wed, 2 Sep 1998 20:26:26 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03897 for ; Wed, 2 Sep 1998 20:26:23 -0700 (PDT) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.8.8/8.8.8) with SMTP id XAA02354 for ; Wed, 2 Sep 1998 23:23:25 -0500 (EST) (envelope-from jim@web-ex.com) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Wed, 2 Sep 1998 23:23:25 -0500 (EST) From: Jim Cassata To: FreeBSD Net Subject: Re: How to add route In-Reply-To: <000b01bdd6dd$90fa9660$0300a8c0@home> 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 If you have a simple lan with no connection to other networks, you do not need a route. Do you have the proper netmask for all of your interfaces? Are they numbered correctly? Jim Cassata 516.421.6000 jim@web-ex.com Web Express 20 Broadhollow Road Suite 3011 Melville, NY 11747 On Thu, 3 Sep 1998, Alex Kwan wrote: > Hi! > > I am building a LAN with FreeBSD, and that is no need > to connect to another LAN, I alreay have setup the hosts, > and I ping the loopback, it is o.k. but I can't ping the host > the error is being that I have not add route > I use the linux command (I was a linux user before) : > route add -net 192.168.1.0 netmask 255.255.255.0 ed0 > but it is not work with FreeBSD, how to add route in FreeBSD? > > > Alex > > > > > 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 Thu Sep 3 06:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15055 for freebsd-net-outgoing; Thu, 3 Sep 1998 06:29:32 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15049 for ; Thu, 3 Sep 1998 06:29:30 -0700 (PDT) (envelope-from kwanalex@hkstar.com) Received: from home ([202.82.193.42]) by smtp.hkstar.com (8.8.8/8.8.4) with SMTP id VAA00941; Thu, 3 Sep 1998 21:28:14 +0800 (HKT) X-Authentication-Warning: cassiopeia.hkstar.com: Host [202.82.193.42] claimed to be home Message-ID: <006701bdd73e$e37546e0$0300a8c0@home> From: "Alex Kwan" To: "Tom" Subject: Re: How to add route Date: Thu, 3 Sep 1998 21:29:30 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Tom, Many thanks for your help of add route Would you please explain that what is the meaning of the /24 at network address? do you recommend added it on route command line? > >route add 192.168.1.0/24 192.168.1.1 > Regards, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 4 00:59:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19376 for freebsd-net-outgoing; Fri, 4 Sep 1998 00:59:49 -0700 (PDT) (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 AAA19348 for ; Fri, 4 Sep 1998 00:59:38 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA12680; Fri, 4 Sep 1998 06:17:27 +0200 Newsgroups: comp.unix.bsd.freebsd.misc Date: Fri, 4 Sep 1998 06:17:23 +0200 (MET DST) From: Luigi Rizzo cc: net@FreeBSD.ORG Subject: Re: FreeBSD router performance In-Reply-To: <6s9bnj$34e@walton.maths.tcd.ie> 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 [Cc to net@freebsd.org since i think it is somewhat interesting there] On 29 Aug 1998, David Malone wrote: > Subject: Re: FreeBSD router performance ... > >host and the router. However, when I measure throughput from one host to > >the other, I'm only getting ~200Kbps. The router is obviously the ... > You'd probably get a big improvement by buying two good PCI > ethernet cards. The Digital tulip cards and the Intel Etherexpress as others probably commented, in the above case there is some severe misconfiguration problem. This said, in the last days i have instrumented the networking code to see how long it takes to output a packet (roughtly the last part of ether_output() with the call to if_start, which is what you generally get). Measured in Pentium 90 timer ticks, here are the results: 1K pkt, NE2000-PCI ("ed" driver) 25.000 ticks 512B pkt, NE2000-PCI ("ed" driver) 15.000 ticks 1K pkt, LANCE-PCI ("lnc" driver) 5.000 ticks 1K pkt, DE21140-PCI 100Mbit ("de" driver) 1.000 ticks as a reference, a call to m_copy() on the same machine for a 1K pkt all in an mbuf cluster takes about 700ticks. On the "ed" driver, the driver itself has to make a copy of the packet to the card using outsw(), so the time scales approx. linearly with pkt size. The "lnc" driver is slightly better (although i am not sure if it used a shared memory buffer on the card or direct DMA). Finally, the 21140 uses direct dma from the mbuf so it saves a lot of the copy overhead. If i can put my hands on other cards I will try to produce more numbers. Assuming you can expect an equivalent number of ticks in the receive processing path and another 1000 or so ticks for forwarding (actually, for bridging i have measured a shorter time), you can derive that on a P5-90 you cannot expect to forward more than some 30.000 pkts/s (very optimistic) with a "de" card, and more like 8-9000 pkts/s with a LANCE (or a n "ed" and short pkts). A faster machine might improve performance but not certainly by more than 1 order of magnitude. cheers -----------------------------+-------------------------------------- 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 Fri Sep 4 06:21:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20146 for freebsd-net-outgoing; Fri, 4 Sep 1998 06:21:31 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20140 for ; Fri, 4 Sep 1998 06:21:29 -0700 (PDT) (envelope-from kwanalex@hkstar.com) Received: from home ([202.82.192.58]) by smtp.hkstar.com (8.8.8/8.8.4) with SMTP id VAA09650 for ; Fri, 4 Sep 1998 21:20:22 +0800 (HKT) X-Authentication-Warning: cassiopeia.hkstar.com: Host [202.82.192.58] claimed to be home Message-ID: <000301bdd806$f39259a0$0300a8c0@home> From: "Alex Kwan" To: Subject: How to check dial out service of Modem Date: Fri, 4 Sep 1998 21:21:37 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! What is the simplest way to check that the dial out service of modem is in order. (step by step please) regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 4 12:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16194 for freebsd-net-outgoing; Fri, 4 Sep 1998 12:19:11 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16186 for ; Fri, 4 Sep 1998 12:19:09 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA13868; Fri, 4 Sep 1998 15:17:57 -0400 (EDT) (envelope-from wollman) Date: Fri, 4 Sep 1998 15:17:57 -0400 (EDT) From: Garrett Wollman Message-Id: <199809041917.PAA13868@khavrinen.lcs.mit.edu> To: net@FreeBSD.ORG Subject: Changes to pru_sosend() interface Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As near as I can tell, only NFS uses the version of the sosend() interface which passes a complete mbuf chain rather than an iovec.(*) Since the demands of NFS are rather different from those of the user-mode interface, I intend to make the following change: - Create a new interface, sosend_bufs() (I was going to call it sosend_nfs(), but the interface is not that specific yet) which takes an mbuf chain rather than a uio. - Modify NFS to use this interface. - Delete support for passing an mbuf chain to the regular sosend(). This should make both interfaces faster, and opens up the possibility of making further changes to the interface to improve NFS's interaction with the socket layer. -GAWollman (*)Oops, I just discovered another one, because tegge didn't fix the direct call to sosend when he imported nfs/krpc_subr.c back in 1997-07. -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 4 12:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18617 for freebsd-net-outgoing; Fri, 4 Sep 1998 12:30:15 -0700 (PDT) (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 MAA18608; Fri, 4 Sep 1998 12:30:12 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.1 [OUT])) id MAA10800; Fri, 4 Sep 1998 12:30:56 -0700 (PDT) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA08223; Fri, 4 Sep 1998 12:28:01 -0700 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id NAA14177; Fri, 4 Sep 1998 13:28:00 -0600 Message-ID: <35F19004.88A643C0@softweyr.com> Date: Sat, 05 Sep 1998 13:24:52 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: Vincent Poy CC: freebsd-stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: How to add route References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Vincent Poy wrote: > > On Thu, 3 Sep 1998, Stuart Henderson wrote: > > > Vincent Poy wrote: > > > > > each T1 is on a separate interface. What I meant to say was is there a > > > way around the route add default to be pointing to only one interface or > > > IP like making all packets from 208.164.68.0/24 go out of eth0 and > > > 209.84.252.0/24 go out of eth1. Each interface does have it's own IP. > > > > have you read http://www.netaxs.com/~freedman/multi.html? > > (that and other links at http://www.mindspring.com/~jlindsay/bgp.html) > > Just read it... My concerns is not incoming packets not coming in > correctly since each CIDR/24 block comes in on the correct circuit as the > IPs belong to each provider. What I want to know is how to set routes so > that depending on which CIDR/24 block a packet from my LAN is coming from, > which circuit it will use to get the packet out since right now, all > packets going out would be using only one circuit. One simple way to do this is to use two routers, one for each external interface. You can then select which circuit is used by pointing the default route on the client machines at the appropriate router. When using old PC hardware and FreeBSD, routers become pretty cheap. ;^) The other solution would be to NOT define a default route on the router, but rather to configure gated with both interfaces in Silent or Active mode, and let the learned routes take care of the problem for you. These would still be routed by destination, not by source, but the overall effect should be to balance the load according to the "costs" of the routes. This conversation is much more appropriate for the freebsd-net mailing list, so I've cc'ed it over there. Please rejoin the thread there, if necessary. -- 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 Fri Sep 4 12:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20711 for freebsd-net-outgoing; Fri, 4 Sep 1998 12:45:03 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20703 for ; Fri, 4 Sep 1998 12:44:58 -0700 (PDT) (envelope-from kwanalex@hkstar.com) Received: from hkstar.com ([202.82.241.114]) by smtp.hkstar.com (8.8.8/8.8.4) with ESMTP id DAA04483 for ; Sat, 5 Sep 1998 03:43:42 +0800 (HKT) X-Authentication-Warning: cassiopeia.hkstar.com: Host [202.82.241.114] claimed to be hkstar.com Message-ID: <35F04339.87337EB2@hkstar.com> Date: Sat, 05 Sep 1998 03:44:58 +0800 From: kwanalex X-Mailer: Mozilla 4.5b1 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Please help! I can't dialup to my ISP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I can't dialup to my ISP, please give me some hints to solve the problem. Informations are as follow: alex# ppp Working in interactive mode. Using interface tun0 ppp ON alex>dial hkstar Dial attempt 1 of 1 Phone: 30062500 dial OK! login OK! ppp ON alex>Packet Mode ppp ON alex> the prompt (ppp) have not changed to upper case PPP, also when I ping the DNS (202.82.1.1) of ISP, the following message shown: Warning: ping: Invalid Command Warning: ping: Failed. ppp.conf is: deault: I USE THE SAMPLE hkstar: set phone 30062500 set login "TIMEOUT 5 ogin:-ogin: myname word: myword" set timeout 120 set ifaddr 0 0 add 0 0 HISADDR and the ppp.linkup is: hkstar: delete ALL add 0 0 HISADDR Sorry this mail is too long, but I am afraid that I was missed something. Regards, ALEX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 4 16:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26909 for freebsd-net-outgoing; Fri, 4 Sep 1998 16:42:34 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26868 for ; Fri, 4 Sep 1998 16:42:26 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA08189; Fri, 4 Sep 1998 16:33:47 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdBP8187; Fri Sep 4 23:33:44 1998 Date: Fri, 4 Sep 1998 16:33:41 -0700 (PDT) From: Julian Elischer To: Garrett Wollman cc: net@FreeBSD.ORG Subject: Re: Changes to pru_sosend() interface In-Reply-To: <199809041917.PAA13868@khavrinen.lcs.mit.edu> 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 this sounds good to me. The specific support for NFS in sosend and friends really does complicate the picture. julian On Fri, 4 Sep 1998, Garrett Wollman wrote: > As near as I can tell, only NFS uses the version of the sosend() > interface which passes a complete mbuf chain rather than an iovec.(*) > Since the demands of NFS are rather different from those of the > user-mode interface, I intend to make the following change: > > - Create a new interface, sosend_bufs() (I was going to call it > sosend_nfs(), but the interface is not that specific yet) which takes > an mbuf chain rather than a uio. > > - Modify NFS to use this interface. > > - Delete support for passing an mbuf chain to the regular sosend(). > > This should make both interfaces faster, and opens up the possibility > of making further changes to the interface to improve NFS's > interaction with the socket layer. > > -GAWollman > > (*)Oops, I just discovered another one, because tegge didn't fix the > direct call to sosend when he imported nfs/krpc_subr.c back in > 1997-07. > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > 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 Fri Sep 4 20:19:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00840 for freebsd-net-outgoing; Fri, 4 Sep 1998 20:19:08 -0700 (PDT) (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 UAA00835 for ; Fri, 4 Sep 1998 20:19:06 -0700 (PDT) (envelope-from Darcy@ok-connect.com) Received: (qmail 1384 invoked from network); 5 Sep 1998 03:32:59 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (139.142.95.253) by 139.142.95.10 with SMTP; 5 Sep 1998 03:32:59 -0000 Message-Id: <3.0.32.19980904201648.018c2100@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 04 Sep 1998 20:16:49 -0700 To: freebsd-net@FreeBSD.ORG From: Darcy Buskermolen Subject: xl0: transmission error: 82 Fatal trap12: Cc: wpaul@ctr.columbia.edu 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 2.2.7-stable which is acting up on me I recently changed to a 3com 905B which was in a windows box with no errors and now during heavy network access the 2.2.7-stable box dies with the followng error: xl0: transmission error: 82 Fatal trap12: page fault while in kernal mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xf019b372 stack pointer = 0x10:0xf0209f90 code segment = base 0x0, limit 0xf0209f9c = DPL 0, pres 1, def32 1 gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = Idle interupt mask = net tty panic: page fault The card is running in 10Mb Half duplex mode, and I just CVSUP'd the source and made a new kernal using the xl dated 1998/09/01 Any ideas ? or is this really a bug ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 4 23:50:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20727 for freebsd-net-outgoing; Fri, 4 Sep 1998 23:50:04 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20714 for ; Fri, 4 Sep 1998 23:50:00 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.8.7/8.8.7) with SMTP id XAA11660; Fri, 4 Sep 1998 23:49:09 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Fri, 4 Sep 1998 23:49:07 -0700 (PDT) From: Vincent Poy To: Wes Peters cc: freebsd-net@FreeBSD.ORG Subject: Re: How to add route In-Reply-To: <35F19004.88A643C0@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 Sat, 5 Sep 1998, Wes Peters wrote: > > > > each T1 is on a separate interface. What I meant to say was is there a > > > > way around the route add default to be pointing to only one interface or > > > > IP like making all packets from 208.164.68.0/24 go out of eth0 and > > > > 209.84.252.0/24 go out of eth1. Each interface does have it's own IP. > > > > > > have you read http://www.netaxs.com/~freedman/multi.html? > > > (that and other links at http://www.mindspring.com/~jlindsay/bgp.html) > > > > Just read it... My concerns is not incoming packets not coming in > > correctly since each CIDR/24 block comes in on the correct circuit as the > > IPs belong to each provider. What I want to know is how to set routes so > > that depending on which CIDR/24 block a packet from my LAN is coming from, > > which circuit it will use to get the packet out since right now, all > > packets going out would be using only one circuit. > > One simple way to do this is to use two routers, one for each external > interface. > You can then select which circuit is used by pointing the default route > on the client machines at the appropriate router. When using old PC hardware > and FreeBSD, routers become pretty cheap. ;^) I wouldn't say it's cheap since the ET 4 Port PCI card costed close to $2500 plus the cost of the AMD K6-233 Machine with 128 megs of RAM. The interfaces are all part of the machine so it's not really possible to use two routers unless each router did it's own T1. > The other solution would be to NOT define a default route on the router, > but rather to configure gated with both interfaces in Silent or Active > mode, and let the learned routes take care of the problem for you. > These would still be routed by destination, not by source, but the > overall effect should be to balance the load according to the "costs" of > the routes. Hmmm, this sounds like a idea but is there a good Gated resource around? > This conversation is much more appropriate for the freebsd-net mailing > list, so I've cc'ed it over there. Please rejoin the thread there, if > necessary. This is a good point since it was on the wrong list originally. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 03:12:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09716 for freebsd-net-outgoing; Sat, 5 Sep 1998 03:12:09 -0700 (PDT) (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 DAA09697; Sat, 5 Sep 1998 03:12:03 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA14166; Sat, 5 Sep 1998 10:16:50 +0200 Newsgroups: comp.unix.bsd.freebsd.misc Date: Sat, 5 Sep 1998 10:16:48 +0200 (MET DST) From: Luigi Rizzo cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: DEC NIC fixes for 2.2.x 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 A few days ago there was a thread on the "de" driver not putting the link back up in case of a network problem. I think i have found the fix, which is already in -current, and seems to work fine here on a -stable system. The following patch to if_de.c seems to work... @@ -447,8 +448,8 @@ * No reason to change media if we have the right media. */ tulip_reset(sc); - tulip_init(sc); } + tulip_init(sc); } it is one of the changes done between 1.81 and 1.82 of the driver. cheers 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 Sat Sep 5 04:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18644 for freebsd-net-outgoing; Sat, 5 Sep 1998 04:59:43 -0700 (PDT) (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 EAA18639 for ; Sat, 5 Sep 1998 04:59:41 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA14217; Sat, 5 Sep 1998 12:04:41 +0200 From: Luigi Rizzo Message-Id: <199809051004.MAA14217@labinfo.iet.unipi.it> Subject: Re: Announce: BRIDGE/IPFW/DUMMYNET PicoBSD stuff... To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Sat, 5 Sep 1998 12:04:41 +0200 (MET DST) Cc: net@FreeBSD.ORG In-Reply-To: <199809011535.RAA09416@labinfo.iet.unipi.it> from "Luigi Rizzo" at Sep 1, 98 05:35:13 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have updated the bridge code and picobsd binary image at the url below. There new code includes a serious bugfix (m_copy was not checked for failures), and some significant performance improvements, avoiding most unnecessary packet copies. The patches also include a fix for the "de" problem (not bringing interface back up after a cable problem) on 2.2.x and an improvements to the "ns" program to display statistics in real time. > http://www.iet.unipi.it/~luigi/ip_dummynet/bridge.html cheers 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 Sat Sep 5 05:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20546 for freebsd-net-outgoing; Sat, 5 Sep 1998 05:32:10 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20541 for ; Sat, 5 Sep 1998 05:32:07 -0700 (PDT) (envelope-from kwanalex@hkstar.com) Received: from hkstar.com ([202.82.241.90]) by smtp.hkstar.com (8.8.8/8.8.4) with ESMTP id UAA19538 for ; Sat, 5 Sep 1998 20:30:58 +0800 (HKT) X-Authentication-Warning: cassiopeia.hkstar.com: Host [202.82.241.90] claimed to be hkstar.com Message-ID: <35F12F4F.523D43D7@hkstar.com> Date: Sat, 05 Sep 1998 20:32:15 +0800 From: kwanalex X-Mailer: Mozilla 4.5b1 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: How to Kill "Add route failed" 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 make a dialup connection to my ISP, and I get the following error: ppp on alex > Packet Mode ppp on alex > PPP ON alex > Add route failed: 0.0.0.0 already exists. How to kill this error? Best regards, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 07:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28471 for freebsd-net-outgoing; Sat, 5 Sep 1998 07:44:20 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28465 for ; Sat, 5 Sep 1998 07:44:18 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: from advent.ctr.columbia.edu (advent.ctr.columbia.edu [128.59.66.9]) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id KAA06044; Sat, 5 Sep 1998 10:43:11 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Received: (wpaul@localhost) by advent.ctr.columbia.edu (8.9.1/8.6.4.788743) id KAA07955; Sat, 5 Sep 1998 10:43:11 -0400 (EDT) Message-Id: <199809051443.KAA07955@advent.ctr.columbia.edu> Subject: Re: xl0: transmission error: 82 Fatal trap12: To: Darcy@ok-connect.com (Darcy Buskermolen) Date: Sat, 5 Sep 1998 10:43:11 -0400 (EDT) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <3.0.32.19980904201648.018c2100@mail.ok-connect.com> from "Darcy Buskermolen" at Sep 4, 98 08:16:49 pm X-Mailer: ELM [version 2.4 PL25] 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 Of all the gin joints in all the towns in all the world, Darcy Buskermolen had to walk into mine and say: > I have a 2.2.7-stable which is acting up on me > I recently changed to a 3com 905B which was in a windows box with no errors > and now during heavy network access > the 2.2.7-stable box dies with the followng error: > > xl0: transmission error: 82 > > Fatal trap12: page fault while in kernal mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf019b372 > stack pointer = 0x10:0xf0209f90 > code segment = base 0x0, limit 0xf0209f9c > = DPL 0, pres 1, def32 1 gran 1 > processor eflags = interupt enabled, resume, IOPL = 0 > current process = Idle > interupt mask = net tty > panic: page fault > > The card is running in 10Mb Half duplex mode, and I just CVSUP'd the source > and made a new kernal using the xl dated 1998/09/01 > > Any ideas ? or is this really a bug ? I think it's a bug. I'm including a small patch with this e-mail. To apply it, do the following: - save this e-mail to /tmp/xl.patch - cd /sys/pci - patch < /tmp/xl.patch - compile a new kernel image and reboot This patch is against the 2.2.x driver version but should work on 3.0 too. Let me know if this makes a difference. I think the problem is that the code is blindly assuming that there's always a packet in the transmit queue when a transmission error occurs, but in this case there may not be. That being the case, sc->xl_cdata.xl_tx_head is a NULL pointer, and dereferencing it could be causing the panic. I don't have the manual in front of me, but I think 82 means a transmit FIFO reclaim error (which only happens on the 3c905B). I believe it means that a transmit error occured after part of the transmit FIFO had already been reclaimed. In other words, the packet was already most of the way out the door before the chip noticed an error condition, possibly too many collisions or deferals. Let me know if this patch stops the panic. You may still see the transmission error message. Let me know how frequently the message occurs. If the driver recovers from the error condition properly then I can just hide the printf() under #ifdef DIAGNOSTIC. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= *** if_xl.c 1998/09/04 15:31:48 1.38 --- if_xl.c 1998/09/05 14:33:25 *************** *** 1884,1890 **** sc->xl_unit, txstat); CSR_WRITE_2(sc, XL_COMMAND, XL_CMD_TX_RESET); xl_wait(sc); ! CSR_WRITE_4(sc, XL_DOWNLIST_PTR, vtophys(sc->xl_cdata.xl_tx_head->xl_ptr)); /* * Remember to set this for the --- 1884,1891 ---- sc->xl_unit, txstat); CSR_WRITE_2(sc, XL_COMMAND, XL_CMD_TX_RESET); xl_wait(sc); ! if (sc->xl_cdata.xl_tx_head != NULL) ! CSR_WRITE_4(sc, XL_DOWNLIST_PTR, vtophys(sc->xl_cdata.xl_tx_head->xl_ptr)); /* * Remember to set this for the To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 08:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01545 for freebsd-net-outgoing; Sat, 5 Sep 1998 08:25:08 -0700 (PDT) (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 IAA01540 for ; Sat, 5 Sep 1998 08:25:04 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA14455 for net@freebsd.org; Sat, 5 Sep 1998 15:30:09 +0200 From: Luigi Rizzo Message-Id: <199809051330.PAA14455@labinfo.iet.unipi.it> Subject: netstat request... To: net@FreeBSD.ORG Date: Sat, 5 Sep 1998 15:30:09 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well i need to add an option to netstat to display bridging statistics. In the PicoBSD version i just overloaded the "protocol" flag so that netstat -p bdg shows bridging stats. Any objections to do the same in the standard netstat (it is a hack, because bridging is not really a protocol...) ? Any better alternative ? cheers 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 Sat Sep 5 08:46:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04727 for freebsd-net-outgoing; Sat, 5 Sep 1998 08:46:51 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04721 for ; Sat, 5 Sep 1998 08:46:46 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA20027; Sat, 5 Sep 1998 11:45:35 -0400 (EDT) (envelope-from wollman) Date: Sat, 5 Sep 1998 11:45:35 -0400 (EDT) From: Garrett Wollman Message-Id: <199809051545.LAA20027@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: netstat request... In-Reply-To: <199809051330.PAA14455@labinfo.iet.unipi.it> References: <199809051330.PAA14455@labinfo.iet.unipi.it> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > shows bridging stats. Any objections to do the same in the standard > netstat (it is a hack, because bridging is not really a protocol...) ? > Any better alternative ? I'd rather see `-f link' (with an additional `-s' to show the stats). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 09:52:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12904 for freebsd-net-outgoing; Sat, 5 Sep 1998 09:52:39 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12892 for ; Sat, 5 Sep 1998 09:52:37 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA01437 for ; Sat, 5 Sep 1998 12:51:30 -0400 (EDT) Date: Sat, 5 Sep 1998 12:51:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-net@FreeBSD.ORG Subject: netmask of 0 not permitted (3.0-current) 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 This morning I was plugged into a network, and wanted to figure out what hosts on the network were in which subnets. In particular, I knew that several hosts on the subnet believed they were on different subnets due to a configuration problem. Well, I thought, I'll just set up my ethernet device to believe that all IP addresses are local so I don't get a "no route to host" without a default router set. But then I ran into a problem: ifconfig ep0 netmask 0.0.0.0 ifconfig ep0 ep0: flags=a843 mtu 1500 inet 192.168.10.21 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:a0:24:60:31:9c I can ifconfig to almost 0: ep0: flags=a843 mtu 1500 inet 192.168.10.21 netmask 0x80000000 broadcast 255.255.255.255 ether 00:a0:24:60:31:9c but not to 0 itself. It seems to me that a netmask of 0 is not illegitimate, as I might want to have all packets go to the local network. Am I doing something wrong? :) Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 09:57:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13459 for freebsd-net-outgoing; Sat, 5 Sep 1998 09:57:30 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13449 for ; Sat, 5 Sep 1998 09:57:28 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) with SMTP id JAA10321; Sat, 5 Sep 1998 09:56:13 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Sat, 5 Sep 1998 09:56:13 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: kwanalex cc: freebsd-net@FreeBSD.ORG Subject: Re: How to Kill "Add route failed" In-Reply-To: <35F12F4F.523D43D7@hkstar.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 You can't. This basically tells you that default route alreday exists and ppp can't add another default route (well, you can have more then one default route but this is not what is going on here). If you want ppp to add route for you when it connects, before you fire up ppp do # route delete default this will delete default route which in turn will allow ppp to add it's own default route upon connect. One can "man route" for more info also. Hope this helps, -- Yan I don't have the password + Jan Koum But the path is chainlinked | Spelled Jan, pronounced Yan. There. So if you've got the time | Web: http://www.best.com/~jkb Set the tone to sync + OS: http://www.FreeBSD.org On Sat, 5 Sep 1998, kwanalex wrote: >I have make a dialup connection to my ISP, >and I get the following error: >ppp on alex > Packet Mode >ppp on alex > >PPP ON alex > Add route failed: 0.0.0.0 already exists. > >How to kill this error? > >Best regards, >Alex > > > > >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 Sat Sep 5 10:03:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15127 for freebsd-net-outgoing; Sat, 5 Sep 1998 10:03:46 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15121 for ; Sat, 5 Sep 1998 10:03:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA14484; Sat, 5 Sep 1998 10:02:32 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Jan B. Koum " cc: kwanalex , freebsd-net@FreeBSD.ORG Subject: Re: How to Kill "Add route failed" In-reply-to: Your message of "Sat, 05 Sep 1998 09:56:13 PDT." Date: Sat, 05 Sep 1998 10:02:32 -0700 Message-ID: <14481.905014952@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You can't. This basically tells you that default route alreday > exists and ppp can't add another default route (well, you can have more > then one default route but this is not what is going on here). If you want > ppp to add route for you when it connects, before you fire up ppp do > > # route delete default No. That's the backwards way to do it and suffers from a distinct lack of automation. :-) Put something instead in the ppp config file which says "delete ALL" to achieve the same effect right before your "add 0 0 HISADDR" - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 19:08:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08904 for freebsd-net-outgoing; Sat, 5 Sep 1998 19:08:27 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08899 for ; Sat, 5 Sep 1998 19:08:25 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id WAA21401; Sat, 5 Sep 1998 22:06:36 -0400 (EDT) (envelope-from wollman) Date: Sat, 5 Sep 1998 22:06:36 -0400 (EDT) From: Garrett Wollman Message-Id: <199809060206.WAA21401@khavrinen.lcs.mit.edu> To: Robert Watson Cc: freebsd-net@FreeBSD.ORG Subject: netmask of 0 not permitted (3.0-current) In-Reply-To: References: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > ifconfig ep0 netmask 0.0.0.0 > inet 192.168.10.21 netmask 0xffffff00 broadcast 192.168.10.255 Right. You have discovered that the flag to SIOCAIFADDR which means `I don't know the netmask, take a wild guess' happens to have the bit pattern all-bits-zero. > It seems to me that a netmask of 0 is not illegitimate, as I might want to > have all packets go to the local network. The only legitimate route with a netmask of zero is the default route. > Am I doing something wrong? :) Pretty evil, if you ask me, but I suspect `route add default -interface ed0 -cloning' might do the trick. It sounds like what you really wanted was a script which analyzed tcpdump output to see who is arping for whom. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 21:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14755 for freebsd-net-outgoing; Sat, 5 Sep 1998 21:10:37 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14750 for ; Sat, 5 Sep 1998 21:10:35 -0700 (PDT) (envelope-from kwanalex@hkstar.com) Received: from hkstar.com (ip-53-165.dialup.hkstar.com [202.82.53.165]) by smtp.hkstar.com (8.8.8/8.8.4) with ESMTP id MAA15866; Sun, 6 Sep 1998 12:09:16 +0800 (HKT) X-Authentication-Warning: cassiopeia.hkstar.com: Host ip-53-165.dialup.hkstar.com [202.82.53.165] claimed to be hkstar.com Message-ID: <35F20B38.DD0A60E2@hkstar.com> Date: Sun, 06 Sep 1998 12:10:33 +0800 From: kwanalex X-Mailer: Mozilla 4.5b1 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" , "freebsd-net@FreeBSD.ORG" Subject: Re: another question about user PPP References: <14481.905014952@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Jordan, I do it now! Thank You Very Much! but when I use ping to test the connection the following messages are shown: PPP ON alex> ping www.cdrom.com Warning: ping: Invalid command Warning: ping: Failed 1 When I execute "Ctrl+Alt+F2" to changed to another console, everything like ping, ftp....are o.k. If I want to use ftp, Do I must need to change to another console to do it? Have other ways to solve it? Best Regards, Alex Jordan K. Hubbard wrote: > No. That's the backwards way to do it and suffers from a distinct > lack of automation. :-) > > Put something instead in the ppp config file which says "delete ALL" > to achieve the same effect right before your "add 0 0 HISADDR" > > - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 5 21:24:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15778 for freebsd-net-outgoing; Sat, 5 Sep 1998 21:24:49 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15771 for ; Sat, 5 Sep 1998 21:24:47 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA16337; Sat, 5 Sep 1998 21:23:34 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: kwanalex cc: "freebsd-net@FreeBSD.ORG" Subject: Re: another question about user PPP In-reply-to: Your message of "Sun, 06 Sep 1998 12:10:33 +0800." <35F20B38.DD0A60E2@hkstar.com> Date: Sat, 05 Sep 1998 21:23:34 -0700 Message-ID: <16334.905055814@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ping is not a ppp command so I don't see why you think you can do it from the ppp> prompt. Use a shell for better results. :) - Jordan > Hi! Jordan, > > I do it now! Thank You Very Much! > but when I use ping to test the connection > the following messages are shown: > PPP ON alex> ping www.cdrom.com > Warning: ping: Invalid command > Warning: ping: Failed 1 > When I execute "Ctrl+Alt+F2" to changed to another > console, everything like ping, ftp....are o.k. > If I want to use ftp, Do I must need to change to > another console to do it? > Have other ways to solve it? > > Best Regards, > Alex > > > Jordan K. Hubbard wrote: > > > No. That's the backwards way to do it and suffers from a distinct > > lack of automation. :-) > > > > Put something instead in the ppp config file which says "delete ALL" > > to achieve the same effect right before your "add 0 0 HISADDR" > > > > - Jordan > > > 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