From owner-freebsd-net@FreeBSD.ORG Sun Jul 13 07:00:20 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55EDF37B401; Sun, 13 Jul 2003 07:00:20 -0700 (PDT) Received: from mail.ludost.net (tonib-gw.customer.0rbitel.net [195.24.39.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7BAF43F3F; Sun, 13 Jul 2003 07:00:16 -0700 (PDT) (envelope-from maav@bastun.net) Received: from SABBATH (ozzy.ddns.cablebg.net [217.18.240.240]) by mail.ludost.net (Postfix) with ESMTP id 716DC4C518; Sun, 13 Jul 2003 17:00:14 +0300 (EEST) Message-ID: <000c01c34947$0b02e2b0$020aa8c0@SABBATH> From: "Boris Georgiev" To: , , Date: Sun, 13 Jul 2003 16:59:56 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 14:00:21 -0000 Hello All,=20 I've got a Compaq Evo N620c notebook, which comes with a built-in lan = network card - Broadcom NetXtreme BCM5705M. I researched on the hardware = support for this NIC in FreeBSD and noticed that there is no hardware = support for it either in the STABLE, or in the CURRENT distribution. I = found that there is Linux driver for this NIC, which can be downloaded = from the 3Com web site on the following address: http://support.3com.com/infodeli/tools/nic/linux/bcm5700-5.0.5.tar.gz The driver comes as a RedHat binary, Linux kernel patch and standalone = source.=20 Can you, please update me if there is an updated if_bge driver, which = includes hardware support for this new chip or if someone is porting = this driver for FreeBSD and there is a beta version, I can cooperate = with testing it.=20 Boris Georgiev From owner-freebsd-net@FreeBSD.ORG Sun Jul 13 12:01:35 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id D8A4A37B401; Sun, 13 Jul 2003 12:01:35 -0700 (PDT) To: freebsd-net@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Date: Sun, 13 Jul 2003 12:01:35 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030713190135.D8A4A37B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Call for testers: Broadcom 5705 gigabit ethernet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 19:01:36 -0000 While I still don't have any documentation for the BCM5705, I recently obtained a Broadcom driver with 5705 support. After scrutinizing it carefully, it looks like the differences between it and its predecessors are: - No jumbo frame support - RX return ring is limited in size to 512 entries - No support for DMA'ed statistics block (stats must be read from registers instead) - Initialization of certain on-chip blocks and parameters are skipped - 5705 rev A0 has a bug that requires a workaround: the driver has to poll the NIC's memory after setting up the RX descriptor ring to verify the chip has actually loaded it. I have merged all these changes into a copy of the bge(4) driver from -current (should also work with 5.1-RELEASE). You can get it from: http://www.freebsd.org/~wpaul/Broadcom/5705 To use it, just drop the supplied if_bge.c and if_bgereg.h files into /sys/dev/bge and recompile your kernel and/or if_bge.ko module. Unfortunately, I don't have a machine with a 5705 chip in it, so I need other people to help me test these changes. If you have avilable right now: - a laptop or other box with a 5705 gigE chip - FreeBSD 5.1-RELEASE or -CURRENT - another network interface that you can use to load this driver Then please test this updated driver for me and report back. Information that I would like to see: - Describe the system with the 5705 chip in it (I'm under the impression the 5705 is being used in embedded configurations only) - A copy of dmesg output showing the ASIC revision of your chip (doesn't have to be a verbose boot, though I won't mind if it is) - A detailed description of any problems you may observe while testing the driver Information I don't want to see: - Requests for help with other totally unrelated drivers - Requests for help transfering large sums of money out of Nigeria - Information about septic tank clealing - Pictures of people getting it on with barnyard animals - Bikeshed arguments Thanks in advance for any help anyone is able to provide. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-net@FreeBSD.ORG Sun Jul 13 13:29:47 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FF4637B401; Sun, 13 Jul 2003 13:29:47 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58A6C43FAF; Sun, 13 Jul 2003 13:29:46 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h6DKTdYU048328; Sun, 13 Jul 2003 14:29:39 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h6DKTcKZ048327; Sun, 13 Jul 2003 14:29:38 -0600 (MDT) (envelope-from ken) Date: Sun, 13 Jul 2003 14:29:38 -0600 From: "Kenneth D. Merry" To: Boris Georgiev Message-ID: <20030713142937.A48304@panzer.kdm.org> References: <000c01c34947$0b02e2b0$020aa8c0@SABBATH> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <000c01c34947$0b02e2b0$020aa8c0@SABBATH>; from maav@bastun.net on Sun, Jul 13, 2003 at 04:59:56PM +0300 cc: freebsd-net@freebsd.org cc: wpaul@windriver.com cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 20:29:47 -0000 On Sun, Jul 13, 2003 at 16:59:56 +0300, Boris Georgiev wrote: > Hello All, > > I've got a Compaq Evo N620c notebook, which comes with a built-in lan network card - Broadcom NetXtreme BCM5705M. I researched on the hardware support for this NIC in FreeBSD and noticed that there is no hardware support for it either in the STABLE, or in the CURRENT distribution. I found that there is Linux driver for this NIC, which can be downloaded from the 3Com web site on the following address: > > http://support.3com.com/infodeli/tools/nic/linux/bcm5700-5.0.5.tar.gz > > The driver comes as a RedHat binary, Linux kernel patch and standalone source. > Can you, please update me if there is an updated if_bge driver, which includes hardware support for this new chip or if someone is porting this driver for FreeBSD and there is a beta version, I can cooperate with testing it. > Please wrap your lines at something less than 80 columns. Bill Paul just posted a message to -current, -net and -mobile about some patches to the bge(4) driver to hopefully support that chip: http://www.freebsd.org/~wpaul/Broadcom/5705 Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-net@FreeBSD.ORG Sun Jul 13 14:02:33 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id C0DA337B401; Sun, 13 Jul 2003 14:02:33 -0700 (PDT) To: freebsd-net@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Date: Sun, 13 Jul 2003 14:02:33 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030713210233.C0DA337B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Broadcom 5705, addendum X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 21:02:34 -0000 Almost forgot: The BCM5705 also has a new PHY ID, which means an update to brgphy.c and miidevs is required. So, to test the 5705 driver update, do the following: - Download the files from http://www.freebsd.org/~wpaul/Broadcom/5705 - Put if_bge.c and if_bgereg.h into /sys/dev/bge - Put brgphy.c and miidevs into /sys/dev/mii - Recompile your kernel and/or if_bge.ko and miibus.ko modules. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-net@FreeBSD.ORG Sun Jul 13 17:26:59 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F04337B401 for ; Sun, 13 Jul 2003 17:26:59 -0700 (PDT) Received: from hysteria.spc.org (hysteria.spc.org [195.206.69.234]) by mx1.FreeBSD.org (Postfix) with SMTP id 08BBB43F85 for ; Sun, 13 Jul 2003 17:26:58 -0700 (PDT) (envelope-from bms@hysteria.spc.org) Received: (qmail 13980 invoked by uid 5013); 14 Jul 2003 00:24:52 -0000 Date: Mon, 14 Jul 2003 01:24:52 +0100 From: Bruce M Simpson To: freebsd-net@freebsd.org Message-ID: <20030714002452.GC11966@spc.org> Mail-Followup-To: Bruce M Simpson , freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Organization: SPC Subject: ether_resolvemulti() doesn't expire routes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 00:26:59 -0000 I noticed that if I do this:- # route add -net 224.0.0.0/4 -iface xl0 -expire 3000 The resultant cloned routes don't get given a lifetime, i.e. they're totally static and remain in the route table for the lifetime of the kernel. Either multicast designated receivers or IGMP aware routers are the two possible deployment scenarios I can think of which might want to hold on to multicast routes for a long period of time - but these same machines will probably be running mrouted, rather than using a simple primary-interface technique as above to leverage link-layer multicast. What's to stop a malicious user from writing a program which fills the routing table up with multicast routes which aren't actually used by the box? Would it not be a good idea to age these routes and thus prevent them from polluting the routing table in this case? BMS From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 03:48:22 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5AC337B401; Mon, 14 Jul 2003 03:48:22 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E8143F93; Mon, 14 Jul 2003 03:48:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6EAmMUp097160; Mon, 14 Jul 2003 03:48:22 -0700 (PDT) (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6EAmMu0097156; Mon, 14 Jul 2003 03:48:22 -0700 (PDT) Date: Mon, 14 Jul 2003 03:48:22 -0700 (PDT) From: Kris Kennaway Message-Id: <200307141048.h6EAmMu0097156@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: kern/46881: ether_input casts m_hdr to mbuf and causes bpf_mtap to access random data X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 10:48:23 -0000 Synopsis: ether_input casts m_hdr to mbuf and causes bpf_mtap to access random data Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: kris Responsible-Changed-When: Mon Jul 14 03:48:13 PDT 2003 Responsible-Changed-Why: Assign to networking developers http://www.freebsd.org/cgi/query-pr.cgi?pr=46881 From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 04:04:25 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FA8037B401; Mon, 14 Jul 2003 04:04:25 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ED9843FA3; Mon, 14 Jul 2003 04:04:24 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6EB4OUp002847; Mon, 14 Jul 2003 04:04:24 -0700 (PDT) (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6EB4OcX002843; Mon, 14 Jul 2003 04:04:24 -0700 (PDT) Date: Mon, 14 Jul 2003 04:04:24 -0700 (PDT) From: Kris Kennaway Message-Id: <200307141104.h6EB4OcX002843@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: kern/50803: mbuf-related kernel panic (sbappendaddr) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 11:04:25 -0000 Synopsis: mbuf-related kernel panic (sbappendaddr) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: kris Responsible-Changed-When: Mon Jul 14 04:04:13 PDT 2003 Responsible-Changed-Why: Assign to net mailing list for evaluation http://www.freebsd.org/cgi/query-pr.cgi?pr=50803 From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 04:20:41 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5952837B404; Mon, 14 Jul 2003 04:20:41 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E3DD43FD7; Mon, 14 Jul 2003 04:20:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6EBKeUp007695; Mon, 14 Jul 2003 04:20:40 -0700 (PDT) (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6EBKen8007691; Mon, 14 Jul 2003 04:20:40 -0700 (PDT) Date: Mon, 14 Jul 2003 04:20:40 -0700 (PDT) From: Kris Kennaway Message-Id: <200307141120.h6EBKen8007691@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: kern/37486: Bug in network stack in sending broadcast packets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 11:20:41 -0000 Synopsis: Bug in network stack in sending broadcast packets Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: kris Responsible-Changed-When: Mon Jul 14 04:20:31 PDT 2003 Responsible-Changed-Why: Assign to net mailing list for evaluation http://www.freebsd.org/cgi/query-pr.cgi?pr=37486 From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 04:21:01 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1A1237B401; Mon, 14 Jul 2003 04:21:01 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBEA43FBD; Mon, 14 Jul 2003 04:21:01 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6EBL1Up007747; Mon, 14 Jul 2003 04:21:01 -0700 (PDT) (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6EBL12A007743; Mon, 14 Jul 2003 04:21:01 -0700 (PDT) Date: Mon, 14 Jul 2003 04:21:01 -0700 (PDT) From: Kris Kennaway Message-Id: <200307141121.h6EBL12A007743@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: kern/37761: process exits but socket is still ESTABLISHED X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 11:21:02 -0000 Synopsis: process exits but socket is still ESTABLISHED Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: kris Responsible-Changed-When: Mon Jul 14 04:20:52 PDT 2003 Responsible-Changed-Why: Assign to net mailing list for evaluation http://www.freebsd.org/cgi/query-pr.cgi?pr=37761 From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 14:17:46 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A345937B404 for ; Mon, 14 Jul 2003 14:17:46 -0700 (PDT) Received: from ns1.interbgc.com (mail.interbgc.com [217.9.224.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A97B43FD7 for ; Mon, 14 Jul 2003 14:17:43 -0700 (PDT) (envelope-from maav@cablebg.net) Received: (qmail 68032 invoked from network); 14 Jul 2003 21:17:39 -0000 Received: from maav@cablebg.net by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.1.60/v4270. Clear:SA:0(-9.9/8.0):. Processed in 0.280619 secs); 14 Jul 2003 21:17:39 -0000 X-Spam-Status: No, hits=-9.9 required=8.0 Received: from ozzy.ddns.cablebg.net (HELO SABBATH) (217.18.240.240) by mail.cablebg.net with SMTP; 14 Jul 2003 21:17:38 -0000 Message-ID: <001701c34a4d$4f979fe0$020aa8c0@SABBATH> From: "Boris Georgiev" To: "Kenneth D. Merry" References: <000c01c34947$0b02e2b0$020aa8c0@SABBATH> <20030713142937.A48304@panzer.kdm.org> Date: Tue, 15 Jul 2003 00:17:20 +0300 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-net@freebsd.org cc: wpaul@windriver.com cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Boris Georgiev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 21:17:47 -0000 Kenneth, As I already posted William, I have bad news - it doesn't work for me. I rebuilt kernel yesterday with the patched sources and the only thing that happened is that the kernel recognised the LAN card and after that it tried to upload the firmware on the NIC chip, but unsuccessfully. It gave me out an timeout message and didn't load the driver at all. I am sorry that at this time I cannot send the exact message from the kernel, but the notbook is at my office, so I will post it tomorrow if the output will help for finding out what the problem is. Best regards, Boris Georgiev ----- Original Message ----- From: "Kenneth D. Merry" To: "Boris Georgiev" Cc: ; ; Sent: Sunday, July 13, 2003 11:29 PM Subject: Re: Broadcom NetXtreme BCM5705M support > On Sun, Jul 13, 2003 at 16:59:56 +0300, Boris Georgiev wrote: > > Hello All, > > > > I've got a Compaq Evo N620c notebook, which comes with a built-in lan network card - Broadcom NetXtreme BCM5705M. I researched on the hardware support for this NIC in FreeBSD and noticed that there is no hardware support for it either in the STABLE, or in the CURRENT distribution. I found that there is Linux driver for this NIC, which can be downloaded from the 3Com web site on the following address: > > > > http://support.3com.com/infodeli/tools/nic/linux/bcm5700-5.0.5.tar.gz > > > > The driver comes as a RedHat binary, Linux kernel patch and standalone source. > > Can you, please update me if there is an updated if_bge driver, which includes hardware support for this new chip or if someone is porting this driver for FreeBSD and there is a beta version, I can cooperate with testing it. > > > > Please wrap your lines at something less than 80 columns. > > Bill Paul just posted a message to -current, -net and -mobile about some > patches to the bge(4) driver to hopefully support that chip: > > http://www.freebsd.org/~wpaul/Broadcom/5705 > > Ken > -- > Kenneth Merry > ken@kdm.org > > From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 14:26:48 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F53437B401; Mon, 14 Jul 2003 14:26:48 -0700 (PDT) Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1AB343FAF; Mon, 14 Jul 2003 14:26:47 -0700 (PDT) (envelope-from wpaul@windriver.com) Received: from huisne.wrs.com (huisne [147.11.46.60]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA03762; Mon, 14 Jul 2003 14:26:37 -0700 (PDT) From: william paul Received: (from wpaul@localhost) by huisne.wrs.com (8.9.1/8.9.0) id OAA17158; Mon, 14 Jul 2003 14:26:46 -0700 (PDT) Message-Id: <200307142126.OAA17158@huisne.wrs.com> To: maav@cablebg.net Date: Mon, 14 Jul 2003 14:26:45 -0700 (PDT) In-Reply-To: <001701c34a4d$4f979fe0$020aa8c0@SABBATH> from "Boris Georgiev" at Jul 15, 2003 12:17:20 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 21:26:49 -0000 Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: > Kenneth, > > As I already posted William, I have bad news - it doesn't work for me. I > rebuilt kernel yesterday with > the patched sources and the only thing that happened is that the kernel > recognised the LAN card and > after that it tried to upload the firmware on the NIC chip, but > unsuccessfully. Uh.... First of all, the driver does not load any firmware into the chip. Second, you're not supposed to tell me your interpretation of what happened: you're supposed to cut&paste the messages into an e-mail so that I can see for myself what happened. Please show me all of the information that led you to your conclusion that this alleged firmware upload failed. > It gave me out > an timeout message and didn't load the driver at all. I am sorry that at > this time I cannot send > the exact message from the kernel, but the notbook is at my office, so I > will post it > tomorrow if the output will help for finding out what the problem is. > Best regards, Ok, note to all reading this: if I ask for information and you don't have the information available, don't bother sending me an e-mail just to tell me that you don't have the information available. Wait until you do have the information available, and then e-mail me. You'll save precious time and electrons. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-net@FreeBSD.ORG Mon Jul 14 22:57:07 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 0E1A137B401; Mon, 14 Jul 2003 22:57:07 -0700 (PDT) To: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Date: Mon, 14 Jul 2003 22:57:07 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030715055707.0E1A137B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: More Broadcom BCM5705 updates X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 05:57:07 -0000 I have merged in some additional updates provided by Paul Saab: - Support the BCM5782 chip (5705 workalike, new PCI ID) - Increase firmware handshake timeout - Always check for GMII PHYs at PHY address 1 (required for some chips, doesn't hurt on the others) - Add ASIC rev numbers for 5705_A1, 5705_A2 and 5705_A3 There may be some additional performance tweaks needed, but this should get the device attached and working. As before, download the new code from: http://www.freebsd.org/~wpaul/Broadcom/5705 - Copy if_bge.c and if_bgereg.h to /sys/dev/bge - Copy miidevs and brgphy.c to /sys/dev/mii - Rebuild your kernel and/or if_bge.ko and miibus.ko modules -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 02:50:58 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED75937B401 for ; Tue, 15 Jul 2003 02:50:58 -0700 (PDT) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A74143F85 for ; Tue, 15 Jul 2003 02:50:58 -0700 (PDT) (envelope-from sbuskens@wanadoo.nl) Received: from w2kwsbuskens (ip503d0ab6.speed.planet.nl [80.61.10.182]) by smtp05.wxs.nl (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0HI2002GM8W6HK@smtp05.wxs.nl> for freebsd-net@freebsd.org; Tue, 15 Jul 2003 11:55:18 +0200 (MEST) Date: Tue, 15 Jul 2003 11:50:18 +0200 From: Sander Buskens To: freebsd-net@freebsd.org Message-id: <001401c34ab6$80207560$6801a8c0@w2kwsbuskens> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-Priority: 3 X-MSMail-priority: Normal Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Realtek 8180 support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 09:50:59 -0000 I was wondering whether anyone is working on support for the Realtek 8180 chipset. This chipset is used on various wireless PCI and PCMCIA cards (I bought one and then found out FreeBSD doesn''t support it yet). Regards, Sander Buskens From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 05:04:18 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 520A737B401; Tue, 15 Jul 2003 05:04:18 -0700 (PDT) Received: from honolulu.procergs.com.br (honolulu.procergs.com.br [200.198.128.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECEB943F93; Tue, 15 Jul 2003 05:04:12 -0700 (PDT) (envelope-from marcelo-leal@procergs.rs.gov.br) Received: from ws-tor-0004.procergs (unknown [172.28.5.20]) by honolulu.procergs.com.br (Postfix) with ESMTP id E3E26AADC; Tue, 15 Jul 2003 09:04:10 -0300 (BRT) Received: from procergs.rs.gov.br (localhost [127.0.0.1]) by ws-tor-0004.procergs (Postfix) with ESMTP id B2E66C2FC87; Tue, 15 Jul 2003 09:03:12 -0300 (BRT) From: omestre@freeshell.org To: freebsd-net@freebsd.org Date: Tue, 15 Jul 2003 09:03:12 -0300 Sender: marcelo-leal@procergs.rs.gov.br Message-Id: <20030715120312.B2E66C2FC87@ws-tor-0004.procergs> cc: freebsd-hackers@freebsd.org Subject: pr 54383 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 12:04:18 -0000 Hello, I did some changes in my patch to FreeBSD kernel. I have changed my pr, and the new one is 54383. Now, only the diff is on the FreeBSD page. Take a look. If somebody knows who is the devel man, that can help me to add this patch as a new feature in FreeBSD kernel, please tell me. I think something like a new option to diskless machines, without dynamic protocols (dhcp, or bootp), for mount the rootfs. Sorry by the english. Thanks --- From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 10:06:57 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBA5437B401 for ; Tue, 15 Jul 2003 10:06:56 -0700 (PDT) Received: from hole.shrew.net (cs24354-246.austin.rr.com [24.243.54.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 117FA43F75 for ; Tue, 15 Jul 2003 10:06:56 -0700 (PDT) (envelope-from mgrooms@shrew.net) Received: from mail.shrew.net (localhost.shrew.net [127.0.0.1]) by hole.shrew.net (8.12.9/8.12.9) with SMTP id h6FH9UOW055742; Tue, 15 Jul 2003 17:09:35 GMT (envelope-from mgrooms@shrew.net) Message-Id: <200307151709.h6FH9UOW055742@hole.shrew.net> Received: from 65.118.63.254 (auth. user mgrooms@mail.shrew.net) by mail.shrew.net with HTTP; Tue, 15 Jul 2003 17:09:30 +0000 To: "Wes Peters" , "Chuck Swiger" Date: Tue, 15 Jul 2003 17:09:30 +0000 X-Mailer: IlohaMail/0.8.8 (On: mail.shrew.net) In-Reply-To: <200307111407.04591.wes@softweyr.com> From: "Matthew Grooms" Bounce-To: "Matthew Grooms" Errors-To: "Matthew Grooms" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: "freebsd-net@freebsd.org" Subject: Re: broadcast udp packets ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 17:06:57 -0000 Hmmm, >What we observed on our embedded system is the packet gets sent on all >attached interfaces, with dest IP 255.255.255.255, and a src IP of the >local address that has the default route. If there isn't a default >route, sending to 255.255.255.255 fails with "no route to host." > Maybe I am confused. When I use a udp socket bound to an interface, packets that are generated from that socket get thier dest address translated to a network specific broadcast address. Do I understad you correctly when you say that you can generate packets destined to 255.255.255.255? Am I doing somthing different then you are? ... int test_sock =3D socket( PF_INET, SOCK_DGRAM, 0 ); if( test_sock =3D=3D -1 ) return -1; struct ifreq ifr; memset( &ifr, 0, sizeof( struct ifreq ) ); strcpy( ifr.ifr_name, config.get_service_iface() ); if( ioctl( test_sock, SIOCGIFADDR, &ifr ) =3D=3D -1 ) return -1; uint32_t value =3D 1; if( setsockopt( test_sock, SOL_SOCKET, SO_BROADCAST, (char*) &value, sizeof( uint32_t ) ) =3D=3D -1 return -1; struct sockaddr_in serv_addr; memset( &serv_addr, 0, sizeof( struct sockaddr_in ) ); memcpy( &serv_addr, &ifr.ifr_addr, sizeof( struct sockaddr_in ) ); serv_addr.sin_family =3D AF_INET; serv_addr.sin_port =3D htons( config.get_service_port() ); if( bind( test_sock, ( struct sockaddr * ) &serv_addr, sizeof( struct sockaddr_in ) ) =3D=3D - 1) return -1; struct sockaddr_in bcast_addr; memset( &bcast_addr, 0, sizeof( struct sockaddr_in ) ); bcast_addr.sin_family =3D AF_INET; bcast_addr.sin_addr.s_addr =3D 0xffffffff; bcast_addr.sin_port =3D htons( 100 ); char test_buff[] =3D { "TEST123TEST123" }; if( sendto( test_sock, test_buff, sizeof( test_buff ), 0, ( const struct sockaddr * ) &bcast_addr, sizeof( const struct sockaddr_in ) ) =3D=3D -1 ) printf( "failed to generate broadcast packet( %d bytes )\n", sizeof( test_buff ) ); else printf( "broadcast packet generated ( %d bytes )\n", sizeof( test_buff ) ); >This is bogus, so I propose to change it to a special case, where >packets sent to 255.255.255.255 will be sent on each attached >interface, with src IP of the interface "primary" address. When you say attached, do you mean the socket is bound to the ip address of that interface or do you mean all configured interfaces on that host? Should this be affected by the MSG_DONTROUTE flag? It would seem that if you were requesting the packet be routed, that it would be emmitted on all network interfaces. If the MSG_DONTROUTE were passed, that the packet would only be generated on the interface the socket is bound to. Then again, maybe I don't understand the scope of your proposal from down here in userland. Im not a kernel hacker :( >sound reasonable? Should it work without a default route? (I think it >should, the special case of the all-call broadcast shouldn't even go >into rtalloc.) > >I hope to have a working prototype done, on either -STABLE or -CURRENT, >this weekend. If testers like the behavior, I'll commit to CURRENT and >MFC on a normal timeline; we'll want this fixed here before 5.2. > -Matthew From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 14:13:06 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7202F37B401; Tue, 15 Jul 2003 14:13:06 -0700 (PDT) Received: from mail.ludost.net (tonib-gw.customer.0rbitel.net [195.24.39.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0235643F75; Tue, 15 Jul 2003 14:13:05 -0700 (PDT) (envelope-from maav@bastun.net) Received: from SABBATH (ozzy.ddns.cablebg.net [217.18.240.240]) by mail.ludost.net (Postfix) with ESMTP id 098144C729; Wed, 16 Jul 2003 00:13:02 +0300 (EEST) Message-ID: <000901c34b15$d48db900$020aa8c0@SABBATH> From: "Boris Georgiev" To: "william paul" References: <200307142126.OAA17158@huisne.wrs.com> Date: Wed, 16 Jul 2003 00:12:41 +0300 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 21:13:06 -0000 Hi Bill, Sorry for the previous e-mail, but have in mind that I'm trying to cooperate by testing your drivers and I am not aware of the rules for declaring a hardware problem in the mailing lists. The only way I can send you the messages from the kernel is if I rewrite them from the console. Here is the information that you requested: bge0: mem 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 bge0: firmware handshake timed out bge0: RX CPU self-diagnostics failed! bge0: chip initialization failed device_probe_and_attach: bge0 attach returned 6 If you need more detailed information, I can send it to you on request. Boris Georgiev > Uh.... > > First of all, the driver does not load any firmware into the chip. > > Second, you're not supposed to tell me your interpretation of what > happened: you're supposed to cut&paste the messages into an e-mail > so that I can see for myself what happened. > > Please show me all of the information that led you to your conclusion > that this alleged firmware upload failed. > > > It gave me out > > an timeout message and didn't load the driver at all. I am sorry that at > > this time I cannot send > > the exact message from the kernel, but the notbook is at my office, so I > > will post it > > tomorrow if the output will help for finding out what the problem is. > > Best regards, > > Ok, note to all reading this: if I ask for information and you don't > have the information available, don't bother sending me an e-mail > just to tell me that you don't have the information available. Wait > until you do have the information available, and then e-mail me. You'll > save precious time and electrons. > > -Bill From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 14:22:58 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8788937B401 for ; Tue, 15 Jul 2003 14:22:58 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2CDF43FB1 for ; Tue, 15 Jul 2003 14:22:57 -0700 (PDT) (envelope-from sloach@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id <346X8VK5>; Tue, 15 Jul 2003 17:22:56 -0400 Message-ID: From: Scot Loach To: "'freebsd-net@freebsd.org'" Date: Tue, 15 Jul 2003 17:22:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 21:22:58 -0000 Currently, whenever maxsockets is increased, this causes kernel memory to be preallocated for each type of pcb (tcp, udp, raw, divert). The number of pcbs preallocated for each of these is always the same as maxsockets. This is probably a waste of memory for raw sockets and divert sockets, since they would not normally be used in large numbers. A large server could save kvm by reducing the number of divert and raw pcbs preallocated. For example, on a machine configured for 200,000 maxsockets we would save 75MB of kvm out of a total of 262MB that would have been preallocated. This kvm savings can be used to increase maxsockets even more. Is there any reason I should not modify the kernel code to only let a small, fixed number of raw and divert pcbs be preallocated instead of having them scale with maxsockets? Next, does this seem like a generally useful thing that could be rolled back into the source tree? I could make this a kernel option or a tunable sysctl variable. thanks Scot Loach From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 15:39:14 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 633BD37B401 for ; Tue, 15 Jul 2003 15:39:14 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9877643FB1 for ; Tue, 15 Jul 2003 15:39:13 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 71594 invoked from network); 15 Jul 2003 22:39:12 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 15 Jul 2003 22:39:12 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 15 Jul 2003 17:38:39 -0500 (CDT) From: Mike Silbersack To: Scot Loach In-Reply-To: Message-ID: <20030715173449.R18075@odysseus.silby.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "'freebsd-net@freebsd.org'" Subject: Re: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 22:39:14 -0000 On Tue, 15 Jul 2003, Scot Loach wrote: > Is there any reason I should not modify the kernel code to only let a small, > fixed number of raw and divert pcbs be preallocated instead of having them > scale with maxsockets? Your idea is sound. > Next, does this seem like a generally useful thing that could be rolled back > into the source tree? I could make this a kernel option or a tunable sysctl > variable. > > thanks > > Scot Loach A tunable maximum for each of those settings sounds good, that should fit well in subr_param.c. Send me your patch when it's done, and I'll look into incorporating it. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 15:48:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C59C37B401 for ; Tue, 15 Jul 2003 15:48:53 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD07543FA3 for ; Tue, 15 Jul 2003 15:48:52 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from salty.rapid.stbernard.com (corp-2.ipinc.com [199.245.188.2]) by smtp-relay.omnis.com (Postfix) with ESMTP id A51CA1B304; Tue, 15 Jul 2003 15:48:50 -0700 (PDT) From: Wes Peters Organization: Softweyr.com To: "Matthew Grooms" , "Chuck Swiger" Date: Tue, 15 Jul 2003 15:48:48 -0700 User-Agent: KMail/1.5.2 References: <200307151709.h6FH9UOW055742@hole.shrew.net> In-Reply-To: <200307151709.h6FH9UOW055742@hole.shrew.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307151548.48778.wes@softweyr.com> cc: "freebsd-net@freebsd.org" Subject: Re: broadcast udp packets ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 22:48:53 -0000 On Tuesday 15 July 2003 10:09, Matthew Grooms wrote: > Hmmm, > > >What we observed on our embedded system is the packet gets sent on > > all attached interfaces, with dest IP 255.255.255.255, and a src IP > > of the local address that has the default route. If there isn't a > > default route, sending to 255.255.255.255 fails with "no route to > > host." > > Maybe I am confused. When I use a udp socket bound to an interface, > packets that are generated from that socket get thier dest address > translated to a network specific broadcast address. Do I understad > you correctly when you say that you can generate packets destined to > 255.255.255.255? Am I doing somthing different then you are? ... > > int test_sock = socket( PF_INET, SOCK_DGRAM, 0 ); > if( test_sock == -1 ) > return -1; > > struct ifreq ifr; > memset( &ifr, 0, sizeof( struct ifreq ) ); > strcpy( ifr.ifr_name, config.get_service_iface() ); > if( ioctl( test_sock, SIOCGIFADDR, &ifr ) == -1 ) > return -1; > > uint32_t value = 1; > if( setsockopt( test_sock, SOL_SOCKET, SO_BROADCAST, > (char*) &value, sizeof( uint32_t ) ) == -1 > return -1; > > struct sockaddr_in serv_addr; > memset( &serv_addr, 0, sizeof( struct sockaddr_in ) ); > memcpy( &serv_addr, &ifr.ifr_addr, sizeof( struct sockaddr_in ) ); > serv_addr.sin_family = AF_INET; > serv_addr.sin_port = htons( config.get_service_port() ); > > if( bind( test_sock, ( struct sockaddr * ) &serv_addr, > sizeof( struct sockaddr_in ) ) == - 1) > return -1; > > struct sockaddr_in bcast_addr; > memset( &bcast_addr, 0, sizeof( struct sockaddr_in ) ); > bcast_addr.sin_family = AF_INET; > bcast_addr.sin_addr.s_addr = 0xffffffff; > bcast_addr.sin_port = htons( 100 ); > > char test_buff[] = { "TEST123TEST123" }; > if( sendto( test_sock, test_buff, sizeof( test_buff ), 0, > ( const struct sockaddr * ) &bcast_addr, > sizeof( const struct sockaddr_in ) ) == -1 ) > printf( "failed to generate broadcast packet( %d bytes )\n", > sizeof( test_buff ) ); > else > printf( "broadcast packet generated ( %d bytes )\n", > sizeof( test_buff ) ); > > >This is bogus, so I propose to change it to a special case, where > >packets sent to 255.255.255.255 will be sent on each attached > >interface, with src IP of the interface "primary" address. > > When you say attached, do you mean the socket is bound to the ip > address of that interface or do you mean all configured interfaces on > that host? Should this be affected by the MSG_DONTROUTE flag? It > would seem that if you were requesting the packet be routed, that it > would be emmitted on all network interfaces. If the MSG_DONTROUTE > were passed, that the packet would only be generated on the interface > the socket is bound to. It's a broadcast, the socket isn't bound to an interface. ;^) The idea is, we have listener on each ethernet interface listening via a bpf. The listener listens for an 'appliance discovery' packet which is broadcast by the console application running on the admin's workstation. When we receive this discovery packet, we're supposed to reply back with a broadcast packet that says 'here I am' so the console can get our MAC address. The console application does some special h0h0 magic of it's own then sends us back another broadcast message that has IP addresses for all 3 interfaces. It's a wonderful idea but it doesn't work. This seems in keeping with the spirit of BOOTP, DHCP, et al, but is explicitly designed to assign a permanent address to an appliance that cannot know it's boot address when configured and cannot really predict which of the 3 interfaces it might receive an address from. If the answer to this is 'ick, that's just not what IP broadcasting is supposed to do, get lost' I'm willing to accept that answer, but so far everyone seems to agree that what I proposed isn't that whacked out. Tell me if I'm wrong! ;^) So, in short, the IP address 255.255.255.255 is a special case that isn't handled as a special case by the ip_output code. I propose to change the code so that a packet sent to destination address 255.255.255.255 (aka INADDR_BROADCAST) be handled specially. Any such packet will be sent to destination address 255.255.255.255 on each interface that is marked UP and BROADCAST, with the ip src address set to the currently configured primary ip address of the interface, even if this is 0.0.0.0. This special case will not call rtalloc or do any other route lookups. Stop me if I'm violating specifications or even just common sense here... (I need to read the IP and UDP RFCs in a bit more detail, they seem pretty vague in this area.) I'd like to implement this if it's a sensible change, but will tell the application guys to rewrite their send code to use the BPF if it seems this is wrong. I don't feel the current implementation is right in any way, but I don't want to make it more wrong. -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 16:49:37 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0D9137B401 for ; Tue, 15 Jul 2003 16:49:37 -0700 (PDT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5FB743FBD for ; Tue, 15 Jul 2003 16:49:36 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out003.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030715234936.QBLL4805.out003.verizon.net@mac.com>; Tue, 15 Jul 2003 18:49:36 -0500 Message-ID: <3F149303.1010408@mac.com> Date: Tue, 15 Jul 2003 19:49:23 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wes Peters References: <200307151709.h6FH9UOW055742@hole.shrew.net> <200307151548.48778.wes@softweyr.com> In-Reply-To: <200307151548.48778.wes@softweyr.com> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [141.149.47.46] at Tue, 15 Jul 2003 18:49:35 -0500 cc: "freebsd-net@freebsd.org" Subject: Re: broadcast udp packets ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 23:49:38 -0000 Wes Peters wrote: [ ... ] > The idea is, we have listener on each ethernet interface listening via a > bpf. The listener listens for an 'appliance discovery' packet which is > broadcast by the console application running on the admin's > workstation. When we receive this discovery packet, we're supposed to > reply back with a broadcast packet that says 'here I am' so the console > can get our MAC address. The console application does some special > h0h0 magic of it's own then sends us back another broadcast message > that has IP addresses for all 3 interfaces. Is "h0h0 magic" another term for ARP and RARP? :-) Have you seen RFC-903? > It's a wonderful idea but it doesn't work. This seems in keeping with > the spirit of BOOTP, DHCP, et al, but is explicitly designed to assign > a permanent address to an appliance that cannot know it's boot address > when configured and cannot really predict which of the 3 interfaces it > might receive an address from. Yes, indeed. Of course, there is the issue of how an IP-based reply should be addressed to an interface which is UP but does not have an IP address configured as yet? [ ... ] > So, in short, the IP address 255.255.255.255 is a special case that > isn't handled as a special case by the ip_output code. I propose to > change the code so that a packet sent to destination address > 255.255.255.255 (aka INADDR_BROADCAST) be handled specially. Any such > packet will be sent to destination address 255.255.255.255 on each > interface that is marked UP and BROADCAST, with the ip src address set > to the currently configured primary ip address of the interface, even > if this is 0.0.0.0. This special case will not call rtalloc or do any > other route lookups. Agreed with regard to not performing any routing. I don't think of sending to INADDR_BROADCAST as a special case, so much as a generalization of sending to the network broadcast address, only for all networks. Or a single network with no routing and no subnet mask, which people using pure layer-2 switching instead of layer-3 routing sometimes do. [Such networks are wacky. You tend to identify machines by MAC or via non-IP protocols... ] One concern I have is thinking about too tricky special cases and not getting the basics correct. For instance, let's say I only have one interface up, and it's point-to-point, not broadcast: if something sends IP traffic to 255.255.255.255, shouldn't a packet go out with the DST address of the PTP peer? After all, the point of sending to 255.255.255.255 is that you are notationally trying to "send traffic to all hosts that localhost can reach" (and "are willing to hear"). The way to "send traffic to all hosts" on a subnetted network efficiently is via the network broadcast address, but that doesn't mean that there's nothing to talk to over a point-to-point link. -- -Chuck From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:00:52 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3978C37B401; Tue, 15 Jul 2003 17:00:52 -0700 (PDT) Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DB943F93; Tue, 15 Jul 2003 17:00:51 -0700 (PDT) (envelope-from wpaul@windriver.com) Received: from huisne.wrs.com (huisne [147.11.46.60]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA17374; Tue, 15 Jul 2003 17:00:40 -0700 (PDT) From: william paul Received: (from wpaul@localhost) by huisne.wrs.com (8.9.1/8.9.0) id RAA22276; Tue, 15 Jul 2003 17:00:48 -0700 (PDT) Message-Id: <200307160000.RAA22276@huisne.wrs.com> To: maav@bastun.net (Boris Georgiev) Date: Tue, 15 Jul 2003 17:00:48 -0700 (PDT) In-Reply-To: <000901c34b15$d48db900$020aa8c0@SABBATH> from "Boris Georgiev" at Jul 16, 2003 12:12:41 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:00:52 -0000 Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: > Hi Bill, > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > by testing your drivers and > I am not aware of the rules for declaring a hardware problem in the mailing > lists. The only way I can send > you the messages from the kernel is if I rewrite them from the console. I know that. But that's a small price to pay for free driver development. :) > Here is the information that you requested: > > bge0: mem > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_probe_and_attach: bge0 attach returned 6 > > If you need more detailed information, I can send it to you on request. Ok, the firmware handshake does not really load any firmware. This just checks that the firmware on the NIC has responded to a reset and is back up and running. The error here is due to the fact that the firmware initialization seems to take longer on the 5705, so the timeout has to be increased. Thanks for a couple of other people, I have made changes to deal with this. Please download the latest driver code from the same URL (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the problem with the timeout, as well as a few other things. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:01:32 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 035F337B41C; Tue, 15 Jul 2003 17:01:32 -0700 (PDT) Received: from laptop.LucidX.com (dsl093-033-033.snd1.dsl.speakeasy.net [66.93.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A41243F85; Tue, 15 Jul 2003 17:01:30 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: from laptop.LucidX.com (cp5@localhost [127.0.0.1]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G04ELk000366; Tue, 15 Jul 2003 17:04:14 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: (from nazguul@localhost) by laptop.LucidX.com (8.12.8p1/8.12.5/Submit) id h6G04EeH000365 for nazguul@9mm.com; Tue, 15 Jul 2003 17:04:14 -0700 (PDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G044Lk000360 for ; Tue, 15 Jul 2003 17:04:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 59C84566A6; Tue, 15 Jul 2003 17:01:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E4E2B37B416; Tue, 15 Jul 2003 17:00:59 -0700 (PDT) Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3978C37B401; Tue, 15 Jul 2003 17:00:52 -0700 (PDT) Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DB943F93; Tue, 15 Jul 2003 17:00:51 -0700 (PDT) (envelope-from wpaul@windriver.com) Received: from huisne.wrs.com (huisne [147.11.46.60]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA17374; Tue, 15 Jul 2003 17:00:40 -0700 (PDT) From: william paul Received: (from wpaul@localhost) by huisne.wrs.com (8.9.1/8.9.0) id RAA22276; Tue, 15 Jul 2003 17:00:48 -0700 (PDT) Message-Id: <200307160000.RAA22276@huisne.wrs.com> To: maav@bastun.net (Boris Georgiev) Date: Tue, 15 Jul 2003 17:00:48 -0700 (PDT) In-Reply-To: <000901c34b15$d48db900$020aa8c0@SABBATH> from "Boris Georgiev" at Jul 16, 2003 12:12:41 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-hackers@freebsd.org Errors-To: owner-freebsd-hackers@freebsd.org X-Spam-Status: No, hits=-12.0 required=5.0 tests=BAYES_01,IN_REP_TO,MSG_ID_ADDED_BY_MTA_3,QUOTED_EMAIL_TEXT, RCVD_IN_ORBS autolearn=ham version=2.52 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.52 (1.174.2.8-2003-03-24-exp) cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:01:32 -0000 Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: > Hi Bill, > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > by testing your drivers and > I am not aware of the rules for declaring a hardware problem in the mailing > lists. The only way I can send > you the messages from the kernel is if I rewrite them from the console. I know that. But that's a small price to pay for free driver development. :) > Here is the information that you requested: > > bge0: mem > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_probe_and_attach: bge0 attach returned 6 > > If you need more detailed information, I can send it to you on request. Ok, the firmware handshake does not really load any firmware. This just checks that the firmware on the NIC has responded to a reset and is back up and running. The error here is due to the fact that the firmware initialization seems to take longer on the 5705, so the timeout has to be increased. Thanks for a couple of other people, I have made changes to deal with this. Please download the latest driver code from the same URL (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the problem with the timeout, as well as a few other things. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:02:16 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B070D37B408; Tue, 15 Jul 2003 17:02:16 -0700 (PDT) Received: from laptop.LucidX.com (dsl093-033-033.snd1.dsl.speakeasy.net [66.93.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2D2C43FAF; Tue, 15 Jul 2003 17:02:14 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: from laptop.LucidX.com (cp5@localhost [127.0.0.1]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G04wLk000377; Tue, 15 Jul 2003 17:04:58 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: (from nazguul@localhost) by laptop.LucidX.com (8.12.8p1/8.12.5/Submit) id h6G04wm1000376 for nazguul@9mm.com; Tue, 15 Jul 2003 17:04:58 -0700 (PDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G04lLk000371 for ; Tue, 15 Jul 2003 17:04:47 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 8C93B55F7D; Tue, 15 Jul 2003 17:01:17 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D9E337B40C; Tue, 15 Jul 2003 17:01:12 -0700 (PDT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3978C37B401; Tue, 15 Jul 2003 17:00:52 -0700 (PDT) Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DB943F93; Tue, 15 Jul 2003 17:00:51 -0700 (PDT) (envelope-from wpaul@windriver.com) Received: from huisne.wrs.com (huisne [147.11.46.60]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA17374; Tue, 15 Jul 2003 17:00:40 -0700 (PDT) From: william paul Received: (from wpaul@localhost) by huisne.wrs.com (8.9.1/8.9.0) id RAA22276; Tue, 15 Jul 2003 17:00:48 -0700 (PDT) Message-Id: <200307160000.RAA22276@huisne.wrs.com> To: maav@bastun.net (Boris Georgiev) Date: Tue, 15 Jul 2003 17:00:48 -0700 (PDT) In-Reply-To: <000901c34b15$d48db900$020aa8c0@SABBATH> from "Boris Georgiev" at Jul 16, 2003 12:12:41 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Spam-Status: No, hits=-12.1 required=5.0 tests=BAYES_01,IN_REP_TO,MSG_ID_ADDED_BY_MTA_3,QUOTED_EMAIL_TEXT version=2.52 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.52 (1.174.2.8-2003-03-24-exp) cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:02:17 -0000 Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: > Hi Bill, > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > by testing your drivers and > I am not aware of the rules for declaring a hardware problem in the mailing > lists. The only way I can send > you the messages from the kernel is if I rewrite them from the console. I know that. But that's a small price to pay for free driver development. :) > Here is the information that you requested: > > bge0: mem > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_probe_and_attach: bge0 attach returned 6 > > If you need more detailed information, I can send it to you on request. Ok, the firmware handshake does not really load any firmware. This just checks that the firmware on the NIC has responded to a reset and is back up and running. The error here is due to the fact that the firmware initialization seems to take longer on the 5705, so the timeout has to be increased. Thanks for a couple of other people, I have made changes to deal with this. Please download the latest driver code from the same URL (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the problem with the timeout, as well as a few other things. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:04:07 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B77337B404; Tue, 15 Jul 2003 17:04:07 -0700 (PDT) Received: from laptop.LucidX.com (dsl093-033-033.snd1.dsl.speakeasy.net [66.93.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC97143FBD; Tue, 15 Jul 2003 17:03:59 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: from laptop.LucidX.com (cp5@localhost [127.0.0.1]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G06iLk000441; Tue, 15 Jul 2003 17:06:44 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: (from nazguul@localhost) by laptop.LucidX.com (8.12.8p1/8.12.5/Submit) id h6G06i3j000440 for nazguul@9mm.com; Tue, 15 Jul 2003 17:06:44 -0700 (PDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G06ALk000415 for ; Tue, 15 Jul 2003 17:06:10 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 941B857349; Tue, 15 Jul 2003 17:02:04 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 58B2337B409; Tue, 15 Jul 2003 17:02:03 -0700 (PDT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 035F337B41C; Tue, 15 Jul 2003 17:01:32 -0700 (PDT) Received: from laptop.LucidX.com (dsl093-033-033.snd1.dsl.speakeasy.net [66.93.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A41243F85; Tue, 15 Jul 2003 17:01:30 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: from laptop.LucidX.com (cp5@localhost [127.0.0.1]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G04ELk000366; Tue, 15 Jul 2003 17:04:14 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: (from nazguul@localhost) by laptop.LucidX.com (8.12.8p1/8.12.5/Submit) id h6G04EeH000365 for nazguul@9mm.com; Tue, 15 Jul 2003 17:04:14 -0700 (PDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G044Lk000360 for ; Tue, 15 Jul 2003 17:04:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 59C84566A6; Tue, 15 Jul 2003 17:01:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E4E2B37B416; Tue, 15 Jul 2003 17:00:59 -0700 (PDT) Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3978C37B401; Tue, 15 Jul 2003 17:00:52 -0700 (PDT) Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DB943F93; Tue, 15 Jul 2003 17:00:51 -0700 (PDT) (envelope-from wpaul@windriver.com) Received: from huisne.wrs.com (huisne [147.11.46.60]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA17374; Tue, 15 Jul 2003 17:00:40 -0700 (PDT) From: william paul Received: (from wpaul@localhost) by huisne.wrs.com (8.9.1/8.9.0) id RAA22276; Tue, 15 Jul 2003 17:00:48 -0700 (PDT) Message-Id: <200307160000.RAA22276@huisne.wrs.com> To: maav@bastun.net (Boris Georgiev) Date: Tue, 15 Jul 2003 17:00:48 -0700 (PDT) In-Reply-To: <000901c34b15$d48db900$020aa8c0@SABBATH> from "Boris Georgiev" at Jul 16, 2003 12:12:41 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list X-BeenThere: freebsd-current@freebsd.org Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Spam-Status: No, hits=-12.1 required=5.0 tests=BAYES_01,IN_REP_TO,MSG_ID_ADDED_BY_MTA_3,QUOTED_EMAIL_TEXT version=2.52 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.52 (1.174.2.8-2003-03-24-exp) cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:04:07 -0000 Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: > Hi Bill, > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > by testing your drivers and > I am not aware of the rules for declaring a hardware problem in the mailing > lists. The only way I can send > you the messages from the kernel is if I rewrite them from the console. I know that. But that's a small price to pay for free driver development. :) > Here is the information that you requested: > > bge0: mem > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_probe_and_attach: bge0 attach returned 6 > > If you need more detailed information, I can send it to you on request. Ok, the firmware handshake does not really load any firmware. This just checks that the firmware on the NIC has responded to a reset and is back up and running. The error here is due to the fact that the firmware initialization seems to take longer on the 5705, so the timeout has to be increased. Thanks for a couple of other people, I have made changes to deal with this. Please download the latest driver code from the same URL (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the problem with the timeout, as well as a few other things. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:06:17 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D685937B405; Tue, 15 Jul 2003 17:06:17 -0700 (PDT) Received: from laptop.LucidX.com (dsl093-033-033.snd1.dsl.speakeasy.net [66.93.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D96044027; Tue, 15 Jul 2003 17:04:34 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: from laptop.LucidX.com (cp5@localhost [127.0.0.1]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G07ILk000464; Tue, 15 Jul 2003 17:07:19 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: (from nazguul@localhost) by laptop.LucidX.com (8.12.8p1/8.12.5/Submit) id h6G07Iiv000463 for nazguul@9mm.com; Tue, 15 Jul 2003 17:07:18 -0700 (PDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G06eLk000429 for ; Tue, 15 Jul 2003 17:06:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 8EFF857431; Tue, 15 Jul 2003 17:02:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 736C937B401; Tue, 15 Jul 2003 17:02:25 -0700 (PDT) Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B070D37B408; Tue, 15 Jul 2003 17:02:16 -0700 (PDT) Received: from laptop.LucidX.com (dsl093-033-033.snd1.dsl.speakeasy.net [66.93.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2D2C43FAF; Tue, 15 Jul 2003 17:02:14 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: from laptop.LucidX.com (cp5@localhost [127.0.0.1]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G04wLk000377; Tue, 15 Jul 2003 17:04:58 -0700 (PDT) (envelope-from nazguul@cyclonic.storming.org) Received: (from nazguul@localhost) by laptop.LucidX.com (8.12.8p1/8.12.5/Submit) id h6G04wm1000376 for nazguul@9mm.com; Tue, 15 Jul 2003 17:04:58 -0700 (PDT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by laptop.LucidX.com (8.12.8p1/8.12.5) with ESMTP id h6G04lLk000371 for ; Tue, 15 Jul 2003 17:04:47 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 8C93B55F7D; Tue, 15 Jul 2003 17:01:17 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D9E337B40C; Tue, 15 Jul 2003 17:01:12 -0700 (PDT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3978C37B401; Tue, 15 Jul 2003 17:00:52 -0700 (PDT) Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DB943F93; Tue, 15 Jul 2003 17:00:51 -0700 (PDT) (envelope-from wpaul@windriver.com) Received: from huisne.wrs.com (huisne [147.11.46.60]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA17374; Tue, 15 Jul 2003 17:00:40 -0700 (PDT) From: william paul Received: (from wpaul@localhost) by huisne.wrs.com (8.9.1/8.9.0) id RAA22276; Tue, 15 Jul 2003 17:00:48 -0700 (PDT) Message-Id: <200307160000.RAA22276@huisne.wrs.com> To: maav@bastun.net (Boris Georgiev) Date: Tue, 15 Jul 2003 17:00:48 -0700 (PDT) In-Reply-To: <000901c34b15$d48db900$020aa8c0@SABBATH> from "Boris Georgiev" at Jul 16, 2003 12:12:41 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list X-BeenThere: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org Errors-To: owner-freebsd-hackers@freebsd.org X-Spam-Status: No, hits=-12.1 required=5.0 tests=BAYES_01,IN_REP_TO,MSG_ID_ADDED_BY_MTA_3,QUOTED_EMAIL_TEXT version=2.52 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.52 (1.174.2.8-2003-03-24-exp) cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:06:18 -0000 Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: > Hi Bill, > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > by testing your drivers and > I am not aware of the rules for declaring a hardware problem in the mailing > lists. The only way I can send > you the messages from the kernel is if I rewrite them from the console. I know that. But that's a small price to pay for free driver development. :) > Here is the information that you requested: > > bge0: mem > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_probe_and_attach: bge0 attach returned 6 > > If you need more detailed information, I can send it to you on request. Ok, the firmware handshake does not really load any firmware. This just checks that the firmware on the NIC has responded to a reset and is back up and running. The error here is due to the fact that the firmware initialization seems to take longer on the 5705, so the timeout has to be increased. Thanks for a couple of other people, I have made changes to deal with this. Please download the latest driver code from the same URL (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the problem with the timeout, as well as a few other things. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:47:52 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B02B37B40C for ; Tue, 15 Jul 2003 17:47:45 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD09C43F93 for ; Tue, 15 Jul 2003 17:47:44 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h6G0lZM7030892; Tue, 15 Jul 2003 17:47:40 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200307160047.h6G0lZM7030892@gw.catspoiler.org> Date: Tue, 15 Jul 2003 17:47:35 -0700 (PDT) From: Don Lewis To: silby@silby.com In-Reply-To: <20030715173449.R18075@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-net@FreeBSD.org Subject: Re: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:47:53 -0000 On 15 Jul, Mike Silbersack wrote: > > On Tue, 15 Jul 2003, Scot Loach wrote: > >> Is there any reason I should not modify the kernel code to only let a small, >> fixed number of raw and divert pcbs be preallocated instead of having them >> scale with maxsockets? > > Your idea is sound. > >> Next, does this seem like a generally useful thing that could be rolled back >> into the source tree? I could make this a kernel option or a tunable sysctl >> variable. >> >> thanks >> >> Scot Loach > > A tunable maximum for each of those settings sounds good, that should fit > well in subr_param.c. Send me your patch when it's done, and I'll look > into incorporating it. I'd prefer separate tunables. I suspect that it is also common to have vastly different requirements for the numbers of TCP and UDP sockets. From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 17:51:17 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0B3137B401; Tue, 15 Jul 2003 17:51:17 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCEF843FA3; Tue, 15 Jul 2003 17:51:16 -0700 (PDT) (envelope-from sloach@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id <305LFX67>; Tue, 15 Jul 2003 20:51:13 -0400 Message-ID: From: Scot Loach To: 'Don Lewis' , silby@silby.com Date: Tue, 15 Jul 2003 20:51:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: freebsd-net@FreeBSD.org Subject: RE: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 00:51:18 -0000 True, I can add a tunable for each of tcp, udp, raw, divert. What will happen when the system runs out of pcbs? -----Original Message----- From: Don Lewis [mailto:truckman@FreeBSD.org] Sent: Tuesday, July 15, 2003 8:48 PM To: silby@silby.com Cc: sloach@sandvine.com; freebsd-net@FreeBSD.org Subject: Re: Kernel tuning for large maxsockets On 15 Jul, Mike Silbersack wrote: > > On Tue, 15 Jul 2003, Scot Loach wrote: > >> Is there any reason I should not modify the kernel code to only let a small, >> fixed number of raw and divert pcbs be preallocated instead of having them >> scale with maxsockets? > > Your idea is sound. > >> Next, does this seem like a generally useful thing that could be rolled back >> into the source tree? I could make this a kernel option or a tunable sysctl >> variable. >> >> thanks >> >> Scot Loach > > A tunable maximum for each of those settings sounds good, that should fit > well in subr_param.c. Send me your patch when it's done, and I'll look > into incorporating it. I'd prefer separate tunables. I suspect that it is also common to have vastly different requirements for the numbers of TCP and UDP sockets. From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 19:15:48 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEF3137B401 for ; Tue, 15 Jul 2003 19:15:48 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0405243F85 for ; Tue, 15 Jul 2003 19:15:48 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6G2Fln8098799; Tue, 15 Jul 2003 22:15:47 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6G2FlII098798; Tue, 15 Jul 2003 22:15:47 -0400 (EDT) (envelope-from barney) Date: Tue, 15 Jul 2003 22:15:47 -0400 From: Barney Wolff To: Wes Peters Message-ID: <20030716021546.GB98170@pit.databus.com> References: <200307151709.h6FH9UOW055742@hole.shrew.net> <200307151548.48778.wes@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307151548.48778.wes@softweyr.com> User-Agent: Mutt/1.4.1i cc: "freebsd-net@freebsd.org" cc: Matthew Grooms Subject: Re: broadcast udp packets ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 02:15:49 -0000 On Tue, Jul 15, 2003 at 03:48:48PM -0700, Wes Peters wrote: > > It's a broadcast, the socket isn't bound to an interface. ;^) > > The idea is, we have listener on each ethernet interface listening via a > bpf. The listener listens for an 'appliance discovery' packet which is > broadcast by the console application running on the admin's > workstation. When we receive this discovery packet, we're supposed to > reply back with a broadcast packet that says 'here I am' so the console > can get our MAC address. The console application does some special > h0h0 magic of it's own then sends us back another broadcast message > that has IP addresses for all 3 interfaces. > > It's a wonderful idea but it doesn't work. This seems in keeping with > the spirit of BOOTP, DHCP, et al, but is explicitly designed to assign > a permanent address to an appliance that cannot know it's boot address > when configured and cannot really predict which of the 3 interfaces it > might receive an address from. I don't quite know why you need to reinvent bootp/dhcp, but adapting the isc-dhcp code would solve your problem without needing kernel mods. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 20:43:24 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 057FC37B42A for ; Tue, 15 Jul 2003 20:43:24 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D4A6243F93 for ; Tue, 15 Jul 2003 20:43:22 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 39206 invoked from network); 16 Jul 2003 03:43:21 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 16 Jul 2003 03:43:21 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 15 Jul 2003 22:42:47 -0500 (CDT) From: Mike Silbersack To: Scot Loach In-Reply-To: Message-ID: <20030715224117.E19149@odysseus.silby.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@FreeBSD.org cc: 'Don Lewis' Subject: RE: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 03:43:24 -0000 On Tue, 15 Jul 2003, Scot Loach wrote: > True, I can add a tunable for each of tcp, udp, raw, divert. That's probably a good idea, I'm sure I'll end up messing with it a bit once you send it to me. :) > What will happen when the system runs out of pcbs? I think it should handle everything fine. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 22:51:24 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D6C137B404; Tue, 15 Jul 2003 22:51:24 -0700 (PDT) Received: from mail.voor.deze.org (a177167.upc-a.chello.nl [62.163.177.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AB9043F85; Tue, 15 Jul 2003 22:51:22 -0700 (PDT) (envelope-from volf@oasis.IAEhv.nl) Received: by mail.voor.deze.org (Postfix, from userid 226) id CAA65FDFA; Wed, 16 Jul 2003 07:51:20 +0200 (CEST) To: freebsd-net@freebsd.org Date: Wed, 16 Jul 2003 07:51:20 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20030716055120.CAA65FDFA@mail.voor.deze.org> From: volf@oasis.IAEhv.nl (Frank Volf) cc: freebsd-stable@freebsd.org Subject: Reproducable panic with multicast on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 05:51:24 -0000 Hi, I have a problem with FreeBSD-4.8-STABLE in which the system panics when multicast definitions are being removed from an interface. The later is very easily reproduced by killing zebra. This is a rather serious problem because it makes FreeBSD unusable as a VLAN router in a data center. I filed a PR for this including the traceback (kern/54314), but on examination of the gnats database I found that this problem was also reported in (kern/40723) with a more accurate problem description than mine. I would like to resolve this issue but I do not know how to proceed: can someone help me with this and do they need more info to do so? Or is there are detailed description of this part of the kernel available, so I can look for the bug myself? Thanks for any advice. Frank From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 00:17:12 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94B3837B401; Wed, 16 Jul 2003 00:17:12 -0700 (PDT) Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E64343FAF; Wed, 16 Jul 2003 00:17:11 -0700 (PDT) (envelope-from ono@kame.net) Received: from m3.gw.fujitsu.co.jp ([10.0.50.73]) by fgwmail6.fujitsu.co.jp (8.12.9/Fujitsu Gateway) id h6G7H9Jf011439; Wed, 16 Jul 2003 16:17:09 +0900 (envelope-from ono@kame.net) Received: from s1.gw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.12.9/Fujitsu Domain Master) id h6G7H9PN008316; Wed, 16 Jul 2003 16:17:09 +0900 (envelope-from ono@kame.net) Received: from hogehoge.soft.net.fujitsu.co.jp (hogehoge.soft.net.fujitsu.co.jp [10.22.113.101]) by s1.gw.fujitsu.co.jp (8.12.9) id h6G7H8CV016183; Wed, 16 Jul 2003 16:17:08 +0900 (envelope-from ono@kame.net) Received: from hogehoge.soft.net.fujitsu.co.jp (IDENT:ono@localhost.localdomain [127.0.0.1])ESMTP id h6G7F4QE029206; Wed, 16 Jul 2003 16:15:04 +0900 Received: (from ono@localhost)h6G7F4gC029205; Wed, 16 Jul 2003 16:15:04 +0900 To: volf@oasis.IAEhv.nl (Frank Volf) In-Reply-To: <20030716055120.CAA65FDFA@mail.voor.deze.org> (Frank Volf's message of "Wed, 16 Jul 2003 07:51:20 +0200 (CEST)") MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Date: Wed, 16 Jul 2003 16:15:04 +0900 Message-ID: User-Agent: T-gnus/6.16.3 (based on Gnus v5.10.3) (revision 02) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.3 (i386-vine-linux-gnu) MULE/5.0 (SAKAKI) Lines: 13 From: Hideki ONO Sender: ono@soft.net.fujitsu.co.jp X-Moneko: DarkSlateGray cc: freebsd-net@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Reproducable panic with multicast on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 07:17:12 -0000 Try my patch which I posted to freebsd-bugs last month. http://lists.freebsd.org/pipermail/freebsd-bugs/2003-June/001407.html > I have a problem with FreeBSD-4.8-STABLE in which the system panics when > multicast definitions are being removed from an interface. The later is very > easily reproduced by killing zebra. > > This is a rather serious problem because it makes FreeBSD unusable as a VLAN > router in a data center. -- Hideki ONO From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 06:47:41 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6172D37B401 for ; Wed, 16 Jul 2003 06:47:41 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C75E43F75 for ; Wed, 16 Jul 2003 06:47:40 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h6G9pkEH013577; Wed, 16 Jul 2003 09:51:46 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h6G9pkCM013576; Wed, 16 Jul 2003 09:51:46 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Wed, 16 Jul 2003 09:51:46 +0000 From: Bosko Milekic To: Scot Loach Message-ID: <20030716095146.GB13330@technokratis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: "'freebsd-net@freebsd.org'" Subject: Re: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 13:47:41 -0000 On Tue, Jul 15, 2003 at 05:22:55PM -0400, Scot Loach wrote: > Currently, whenever maxsockets is increased, this causes kernel memory to be > preallocated for each type of pcb (tcp, udp, raw, divert). The number of > pcbs preallocated for each of these is always the same as maxsockets. > > This is probably a waste of memory for raw sockets and divert sockets, since > they would not normally be used in large numbers. A large server could > save kvm by reducing the number of divert and raw pcbs preallocated. For > example, on a machine configured for 200,000 maxsockets we would save 75MB > of kvm out of a total of 262MB that would have been preallocated. This kvm > savings can be used to increase maxsockets even more. What version of FreeBSD are you talking about here? In -current, the pcbs come off of zones which are capped at a maximum w.r.t. maxsockets. The kva space comes out of kmem_map and the objects are kept cached in their respective zones. One thing to note is that the zones are setup with UMA_ZONE_NOFREE, so the pages wired down for pcb use are probably never unwired. I don't know why, exactly, UMA_ZONE_NOFREE is required for all of the pcb zones in the netinet code. > Is there any reason I should not modify the kernel code to only let a small, > fixed number of raw and divert pcbs be preallocated instead of having them > scale with maxsockets? > > Next, does this seem like a generally useful thing that could be rolled back > into the source tree? I could make this a kernel option or a tunable sysctl > variable. > > thanks > > Scot Loach -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/ From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 06:52:52 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 813DD37B401; Wed, 16 Jul 2003 06:52:52 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD94F43F75; Wed, 16 Jul 2003 06:52:51 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h6G9uvEH013636; Wed, 16 Jul 2003 09:56:57 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h6G9uvgw013635; Wed, 16 Jul 2003 09:56:57 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Wed, 16 Jul 2003 09:56:57 +0000 From: Bosko Milekic To: Scot Loach Message-ID: <20030716095657.GC13330@technokratis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: 'Don Lewis' Subject: Re: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 13:52:52 -0000 On Tue, Jul 15, 2003 at 08:51:12PM -0400, Scot Loach wrote: > True, I can add a tunable for each of tcp, udp, raw, divert. > > What will happen when the system runs out of pcbs? You'll no longer be able to allocate and attach pcbs to sockets until one of the current pcb consumers returns that type of pcb back to the respective zone. -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/ From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 07:15:55 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AE0137B419; Wed, 16 Jul 2003 07:15:55 -0700 (PDT) Received: from mail.voor.deze.org (a177167.upc-a.chello.nl [62.163.177.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73B2543F93; Wed, 16 Jul 2003 07:15:52 -0700 (PDT) (envelope-from volf@oasis.IAEhv.nl) Received: by mail.voor.deze.org (Postfix, from userid 226) id 7F8BEFDFA; Wed, 16 Jul 2003 16:15:50 +0200 (CEST) In-Reply-To: To: Hideki ONO Date: Wed, 16 Jul 2003 16:15:50 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20030716141550.7F8BEFDFA@mail.voor.deze.org> From: volf@oasis.IAEhv.nl (Frank Volf) cc: freebsd-net@freebsd.org cc: freebsd-stable@freebsd.org cc: Frank Volf Subject: Re: Reproducable panic with multicast on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 14:15:56 -0000 Hideki ONO wrote: > Try my patch which I posted to freebsd-bugs last month. > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-June/001407.html Indeed this fixes my problem as well! I hope it will be integrated into the CVS tree soon. Thanks for you help. Frank > > > I have a problem with FreeBSD-4.8-STABLE in which the system panics when > > multicast definitions are being removed from an interface. The later is very > > easily reproduced by killing zebra. > > > > This is a rather serious problem because it makes FreeBSD unusable as a VLAN > > router in a data center. > > -- > Hideki ONO > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 08:08:05 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3BD137B401; Wed, 16 Jul 2003 08:08:04 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF1243F3F; Wed, 16 Jul 2003 08:08:04 -0700 (PDT) (envelope-from bmilekic@FreeBSD.org) Received: from freefall.freebsd.org (bmilekic@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6GF84Up052142; Wed, 16 Jul 2003 08:08:04 -0700 (PDT) (envelope-from bmilekic@freefall.freebsd.org) Received: (from bmilekic@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6GF84S6052138; Wed, 16 Jul 2003 08:08:04 -0700 (PDT) Date: Wed, 16 Jul 2003 08:08:04 -0700 (PDT) From: Bosko Milekic Message-Id: <200307161508.h6GF84S6052138@freefall.freebsd.org> To: bmilekic@FreeBSD.org, freebsd-net@FreeBSD.org, bmilekic@FreeBSD.org Subject: Re: kern/46881: ether_input casts m_hdr to mbuf and causes bpf_mtap to access random data X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 15:08:05 -0000 Synopsis: ether_input casts m_hdr to mbuf and causes bpf_mtap to access random data Responsible-Changed-From-To: freebsd-net->bmilekic Responsible-Changed-By: bmilekic Responsible-Changed-When: Wed Jul 16 08:07:36 PDT 2003 Responsible-Changed-Why: I'll follow-up on this. http://www.freebsd.org/cgi/query-pr.cgi?pr=46881 From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 08:17:53 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B43337B401; Wed, 16 Jul 2003 08:17:53 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA0D443FB1; Wed, 16 Jul 2003 08:17:52 -0700 (PDT) (envelope-from bmilekic@FreeBSD.org) Received: from freefall.freebsd.org (bmilekic@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6GFHqUp052834; Wed, 16 Jul 2003 08:17:52 -0700 (PDT) (envelope-from bmilekic@freefall.freebsd.org) Received: (from bmilekic@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6GFHqHn052830; Wed, 16 Jul 2003 08:17:52 -0700 (PDT) Date: Wed, 16 Jul 2003 08:17:52 -0700 (PDT) From: Bosko Milekic Message-Id: <200307161517.h6GFHqHn052830@freefall.freebsd.org> To: bmilekic@FreeBSD.org, freebsd-net@FreeBSD.org, bmilekic@FreeBSD.org Subject: Re: kern/50803: mbuf-related kernel panic (sbappendaddr) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 15:17:53 -0000 Synopsis: mbuf-related kernel panic (sbappendaddr) Responsible-Changed-From-To: freebsd-net->bmilekic Responsible-Changed-By: bmilekic Responsible-Changed-When: Wed Jul 16 08:16:48 PDT 2003 Responsible-Changed-Why: I'll look into this. It seems that the problem is not directly due to lack of mbufs, but instead due to sbappendaddr getting passed in a non-M_PKTHDR mbuf. http://www.freebsd.org/cgi/query-pr.cgi?pr=50803 From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 10:42:02 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 714B937B401; Wed, 16 Jul 2003 10:42:02 -0700 (PDT) Received: from util.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C45E43FA3; Wed, 16 Jul 2003 10:42:01 -0700 (PDT) (envelope-from spork@inch.com) Received: from shell.inch.com (www.inch.com [216.223.192.20]) h6GHfw3d091461; Wed, 16 Jul 2003 13:41:59 -0400 (EDT) (envelope-from spork@inch.com) Received: from shell.inch.com (localhost [127.0.0.1]) by shell.inch.com (8.12.8p1/8.12.8) with ESMTP id h6GHfwSM006200; Wed, 16 Jul 2003 13:41:58 -0400 (EDT) (envelope-from spork@inch.com) Received: from localhost (spork@localhost)h6GHfvQt006197; Wed, 16 Jul 2003 13:41:58 -0400 (EDT) X-Authentication-Warning: shell.inch.com: spork owned process doing -bs Date: Wed, 16 Jul 2003 13:41:57 -0400 (EDT) From: Charles Sprickman To: Hideki ONO In-Reply-To: Message-ID: <20030716134125.P20962@shell.inch.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-stable@freebsd.org cc: Frank Volf Subject: Re: Reproducable panic with multicast on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 17:42:02 -0000 On Wed, 16 Jul 2003, Hideki ONO wrote: > Try my patch which I posted to freebsd-bugs last month. > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-June/001407.html How about attaching that to one of the PRs open on this bug? Maybe someone will commit it then... Charles > > I have a problem with FreeBSD-4.8-STABLE in which the system panics when > > multicast definitions are being removed from an interface. The later is very > > easily reproduced by killing zebra. > > > > This is a rather serious problem because it makes FreeBSD unusable as a VLAN > > router in a data center. > > -- > Hideki ONO > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 10:48:33 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EF0637B401 for ; Wed, 16 Jul 2003 10:48:33 -0700 (PDT) Received: from paiol.terra.com.br (paiol.terra.com.br [200.176.3.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F6F443F3F for ; Wed, 16 Jul 2003 10:48:32 -0700 (PDT) (envelope-from eick.jac@terra.com.br) Received: from araci.terra.com.br (araci.terra.com.br [200.176.3.44]) by paiol.terra.com.br (Postfix) with ESMTP id 38C448482EA for ; Wed, 16 Jul 2003 14:48:31 -0300 (BRT) Received: from eicke (unknown [200.162.114.126]) (authenticated user eick.jac) by araci.terra.com.br (Postfix) with ESMTP id 9734321EFE0 for ; Wed, 16 Jul 2003 14:48:30 -0300 (BRT) Message-ID: <003701c34bc2$58c21980$0902a8c0@alellyxbr.com.br> From: "Eicke" To: References: <20030716141550.7F8BEFDFA@mail.voor.deze.org> Date: Wed, 16 Jul 2003 14:47:36 -0300 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 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Subject: FreeBSD netcraft X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 17:48:33 -0000 http://news.netcraft.com/archives/2003/07/12/nearly_2_million_active_sites_r unning_freebsd.html From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 11:28:32 2003 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A7FF37B401; Wed, 16 Jul 2003 11:28:32 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC76A43F3F; Wed, 16 Jul 2003 11:28:31 -0700 (PDT) (envelope-from wes@FreeBSD.org) Received: from freefall.freebsd.org (wes@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6GISVUp071399; Wed, 16 Jul 2003 11:28:31 -0700 (PDT) (envelope-from wes@freefall.freebsd.org) Received: (from wes@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6GISVrm071395; Wed, 16 Jul 2003 11:28:31 -0700 (PDT) Date: Wed, 16 Jul 2003 11:28:31 -0700 (PDT) From: Wes Peters Message-Id: <200307161828.h6GISVrm071395@freefall.freebsd.org> To: wes@FreeBSD.org, freebsd-net@FreeBSD.org, wes@FreeBSD.org Subject: Re: kern/37486: Bug in network stack in sending broadcast packets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 18:28:32 -0000 Synopsis: Bug in network stack in sending broadcast packets Responsible-Changed-From-To: freebsd-net->wes Responsible-Changed-By: wes Responsible-Changed-When: Wed Jul 16 11:26:15 PDT 2003 Responsible-Changed-Why: I'm working on all-call broadcasting code already, I'll fix this. http://www.freebsd.org/cgi/query-pr.cgi?pr=37486 From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 11:32:51 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29C9F37B401 for ; Wed, 16 Jul 2003 11:32:51 -0700 (PDT) Received: from bull.almonde.com (almonde.net2.nerim.net [62.212.111.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id A44BE43F93 for ; Wed, 16 Jul 2003 11:32:49 -0700 (PDT) (envelope-from yann.nottara@almonde.com) Received: from almonde.com (vulture.almonde.com [192.168.0.156]) by bull.almonde.com (8.12.6/8.12.6) with ESMTP id h6GIWii7057202 for ; Wed, 16 Jul 2003 20:32:44 +0200 (CEST) (envelope-from yann.nottara@almonde.com) Message-ID: <3F159A8C.9050204@almonde.com> Date: Wed, 16 Jul 2003 20:33:48 +0200 From: Yann Nottara Organization: Almonde User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr, en-us MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 18:32:51 -0000 Hello, I've been running a FreeBSD 4.7 box with a MPD 3.13 PPTP VPN server for quite some time now and, altough it mostly works, I'd like to iron out some problems we encounter. Configuration (that gives an IP address in a 192.168.0.0/24 local network to 16 Win2k clients at this moment) is done according to the following model : MPD PPTP, DNS & Samba server is 192.168.0.10 mpd.conf ***************************************** default: load pptp0 pptp0: new -i ng0 pptp0 pptp0 set iface route 192.168.0.10/24 set iface disable on-demand set iface enable proxy-arp set iface idle 3600 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 set ipcp yes vjcomp set ipcp ranges 192.168.0.10/32 192.168.0.204/32 set ipcp dns 192.168.0.10 set ipcp nbns 192.168.0.10 set bundle enable compression set ccp yes mppc set ccp no mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless ****************************************** mpd.links ****************************************** pptp0: set link type pptp set pptp self 192.168.0.10 set pptp enable incoming set pptp disable originate ****************************************** As you'll see in the logs below and from ifconfig output, altough the ngX interfaces MTU is set to 1460 with "set link mtu 1460", it stays at 1500. Any idea why ? *************************************** yann@bull ~ $ ifconfig fxp0: flags=8843 mtu 1500 inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::2b0:d0ff:fee1:4874%fxp0 prefixlen 64 scopeid 0x1 ether 00:b0:d0:e1:48:74 media: Ethernet autoselect (100baseTX ) status: active fxp1: flags=8802 mtu 1500 ether 00:b0:d0:e1:48:75 media: Ethernet autoselect (none) status: no carrier lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8002 mtu 1500 ng0: flags=88d1 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 inet 192.168.0.10 --> 192.168.0.204 netmask 0xffffffff ng1: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng1 prefixlen 64 scopeid 0x8 ng2: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng2 prefixlen 64 scopeid 0x9 ng3: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng3 prefixlen 64 scopeid 0xa ng4: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng4 prefixlen 64 scopeid 0xb ng5: flags=8890 mtu 1500 ng6: flags=8890 mtu 1500 ng7: flags=8890 mtu 1500 ng8: flags=8890 mtu 1500 ng9: flags=8890 mtu 1500 ng10: flags=8890 mtu 1500 ng11: flags=8890 mtu 1500 ng12: flags=8890 mtu 1500 ng13: flags=8890 mtu 1500 ng14: flags=8890 mtu 1500 ng15: flags=8890 mtu 1500 ng16: flags=8890 mtu 1500 mpd.log ******************************************* Jul 16 18:52:11 bull mpd: mpd: PPTP connection from 123.456.789.12:25833 Jul 16 18:52:11 bull mpd: pptp0: attached to connection with 123.456.789.12:25833 Jul 16 18:52:11 bull mpd: [pptp0] IFACE: Open event Jul 16 18:52:11 bull mpd: [pptp0] IPCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] IPCP: state change Initial --> Starting Jul 16 18:52:11 bull mpd: [pptp0] IPCP: LayerStart Jul 16 18:52:11 bull mpd: [pptp0] IPCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] bundle: OPEN event in state CLOSED Jul 16 18:52:11 bull mpd: [pptp0] opening link "pptp0"... Jul 16 18:52:11 bull mpd: [pptp0] link: OPEN event Jul 16 18:52:11 bull mpd: [pptp0] LCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] LCP: state change Initial --> Starting Jul 16 18:52:11 bull mpd: [pptp0] LCP: LayerStart Jul 16 18:52:11 bull mpd: [pptp0] device: OPEN event in state DOWN Jul 16 18:52:11 bull mpd: [pptp0] attaching to peer's outgoing call Jul 16 18:52:11 bull mpd: [pptp0] device is now in state OPENING Jul 16 18:52:11 bull mpd: [pptp0] device: UP event in state OPENING Jul 16 18:52:11 bull mpd: [pptp0] device is now in state UP Jul 16 18:52:11 bull mpd: [pptp0] link: UP event Jul 16 18:52:11 bull mpd: [pptp0] link: origination is remote Jul 16 18:52:11 bull mpd: [pptp0] LCP: Up event Jul 16 18:52:11 bull mpd: [pptp0] LCP: state change Starting --> Req-Sent Jul 16 18:52:11 bull mpd: [pptp0] LCP: phase shift DEAD --> ESTABLISH Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigReq #198 Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: MRU 1500 Jul 16 18:52:11 bull mpd: MAGICNUM e7805d68 Jul 16 18:52:11 bull mpd: AUTHPROTO CHAP MSOFTv2 Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: MP SHORTSEQ Jul 16 18:52:11 bull mpd: ENDPOINTDISC [802.1] 00 b0 d0 e1 48 74 Jul 16 18:52:11 bull mpd: pptp0-0: ignoring SetLinkInfo Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Configure Request #0 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MAGICNUM 278a44ec Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: CALLBACK Jul 16 18:52:11 bull mpd: Not supported Jul 16 18:52:11 bull mpd: MP MRRU 1614 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [LOCAL] a6 92 ca 2c f4 8b 47 51 b5 e1 9d da b3 7b 7b 3e 00 00 00 06 Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigRej #0 Jul 16 18:52:11 bull mpd: CALLBACK Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Configure Reject #198 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MP SHORTSEQ Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigReq #199 Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: MRU 1500 Jul 16 18:52:11 bull mpd: MAGICNUM e7805d68 Jul 16 18:52:11 bull mpd: AUTHPROTO CHAP MSOFTv2 Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [802.1] 00 b0 d0 e1 48 74 Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Configure Request #1 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MAGICNUM 278a44ec Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: MP MRRU 1614 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [LOCAL] a6 92 ca 2c f4 8b 47 51 b5 e1 9d da b3 7b 7b 3e 00 00 00 06 Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigNak #1 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [LOCAL] a6 92 ca 2c f4 8b 47 51 b5 e1 9d da b3 7b 7b 3e 00 00 00 06 Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigNak #1 Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Configure Ack #199 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: MRU 1500 Jul 16 18:52:11 bull mpd: MAGICNUM e7805d68 Jul 16 18:52:11 bull mpd: AUTHPROTO CHAP MSOFTv2 Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [802.1] 00 b0 d0 e1 48 74 Jul 16 18:52:11 bull mpd: [pptp0] LCP: state change Req-Sent --> Ack-Rcvd Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Configure Request #2 link 0 (Ack-Rcvd) Jul 16 18:52:11 bull mpd: MAGICNUM 278a44ec Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [LOCAL] a6 92 ca 2c f4 8b 47 51 b5 e1 9d da b3 7b 7b 3e 00 00 00 06 Jul 16 18:52:11 bull mpd: [pptp0] LCP: SendConfigAck #2 Jul 16 18:52:11 bull mpd: MAGICNUM 278a44ec Jul 16 18:52:11 bull mpd: PROTOCOMP Jul 16 18:52:11 bull mpd: ACFCOMP Jul 16 18:52:11 bull mpd: MP MRRU 1600 Jul 16 18:52:11 bull mpd: ENDPOINTDISC [LOCAL] a6 92 ca 2c f4 8b 47 51 b5 e1 9d da b3 7b 7b 3e 00 00 00 06 Jul 16 18:52:11 bull mpd: [pptp0] LCP: state change Ack-Rcvd --> Opened Jul 16 18:52:11 bull mpd: [pptp0] LCP: phase shift ESTABLISH --> AUTHENTICATE Jul 16 18:52:11 bull mpd: [pptp0] LCP: auth: peer wants nothing, I want CHAP Jul 16 18:52:11 bull mpd: [pptp0] CHAP: sending CHALLENGE Jul 16 18:52:11 bull mpd: [pptp0] LCP: LayerUp Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Ident #3 link 0 (Opened) Jul 16 18:52:11 bull mpd: MESG: MSRASV5.00 Jul 16 18:52:11 bull mpd: pptp0-0: ignoring SetLinkInfo Jul 16 18:52:11 bull mpd: [pptp0] LCP: rec'd Ident #4 link 0 (Opened) Jul 16 18:52:11 bull mpd: MESG: MSRAS-1-HINANO Jul 16 18:52:11 bull mpd: [pptp0] CHAP: rec'd RESPONSE #1 Jul 16 18:52:11 bull mpd: Name: "xxxx" Jul 16 18:52:11 bull mpd: Peer name: "xxxx" Jul 16 18:52:11 bull mpd: Response is valid Jul 16 18:52:11 bull mpd: [pptp0] CHAP: sending SUCCESS Jul 16 18:52:11 bull mpd: [pptp0] LCP: authorization successful Jul 16 18:52:11 bull mpd: [pptp0] LCP: phase shift AUTHENTICATE --> NETWORK Jul 16 18:52:11 bull mpd: [pptp0] setting interface ng0 MTU to 1500 bytes Jul 16 18:52:11 bull mpd: [pptp0] up: 1 link, total bandwidth 64000 bps Jul 16 18:52:11 bull mpd: [pptp0] IPCP: Up event Jul 16 18:52:11 bull mpd: [pptp0] IPCP: state change Starting --> Req-Sent Jul 16 18:52:11 bull mpd: [pptp0] IPCP: SendConfigReq #203 Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.10 Jul 16 18:52:11 bull mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jul 16 18:52:11 bull mpd: [pptp0] error writing len 20 frame to bypass: Network is down Jul 16 18:52:11 bull mpd: [pptp0] CCP: Open event Jul 16 18:52:11 bull mpd: [pptp0] CCP: state change Initial --> Starting Jul 16 18:52:11 bull mpd: [pptp0] CCP: LayerStart Jul 16 18:52:11 bull mpd: [pptp0] CCP: Up event Jul 16 18:52:11 bull mpd: [pptp0] CCP: state change Starting --> Req-Sent Jul 16 18:52:11 bull mpd: [pptp0] CCP: SendConfigReq #118 Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] error writing len 14 frame to bypass: Network is down Jul 16 18:52:11 bull mpd: [pptp0] CCP: rec'd Configure Request #5 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: [pptp0] CCP: rec'd Configure Request #5 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000041: MPPC MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] CCP: SendConfigNak #5 Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] IPCP: rec'd Configure Request #6 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: IPADDR 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.10 Jul 16 18:52:11 bull mpd: SECDNS 0.0.0.0 Jul 16 18:52:11 bull mpd: SECNBNS 0.0.0.0 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: SendConfigRej #6 Jul 16 18:52:11 bull mpd: SECDNS 0.0.0.0 Jul 16 18:52:11 bull mpd: SECNBNS 0.0.0.0 Jul 16 18:52:11 bull mpd: [pptp0] CCP: rec'd Configure Request #7 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] CCP: SendConfigAck #7 Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] CCP: state change Req-Sent --> Ack-Sent Jul 16 18:52:11 bull mpd: [pptp0] IPCP: rec'd Configure Request #8 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: IPADDR 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: SendConfigNak #8 Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: rec'd Configure Request #9 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.204 Jul 16 18:52:11 bull mpd: 192.168.0.204 is OK Jul 16 18:52:11 bull mpd: PRIDNS 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: SendConfigAck #9 Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: state change Req-Sent --> Ack-Sent Jul 16 18:52:13 bull mpd: [pptp0] IPCP: SendConfigReq #204 Jul 16 18:52:13 bull mpd: IPADDR 192.168.0.10 Jul 16 18:52:13 bull mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jul 16 18:52:13 bull mpd: [pptp0] CCP: SendConfigReq #119 Jul 16 18:52:13 bull mpd: MPPC Jul 16 18:52:13 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:13 bull mpd: [pptp0] IPCP: rec'd Configure Reject #204 link 0 (Ack-Sent) Jul 16 18:52:13 bull mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jul 16 18:52:13 bull mpd: [pptp0] IPCP: SendConfigReq #205 Jul 16 18:52:13 bull mpd: IPADDR 192.168.0.10 Jul 16 18:52:13 bull mpd: [pptp0] CCP: rec'd Configure Ack #119 link 0 (Ack-Sent) Jul 16 18:52:13 bull mpd: MPPC Jul 16 18:52:13 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:13 bull mpd: [pptp0] CCP: state change Ack-Sent --> Opened Jul 16 18:52:11 bull mpd: [pptp0] CCP: rec'd Configure Request #7 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] CCP: SendConfigAck #7 Jul 16 18:52:11 bull mpd: MPPC Jul 16 18:52:11 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:11 bull mpd: [pptp0] CCP: state change Req-Sent --> Ack-Sent Jul 16 18:52:11 bull mpd: [pptp0] IPCP: rec'd Configure Request #8 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: IPADDR 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 0.0.0.0 Jul 16 18:52:11 bull mpd: NAKing with 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: SendConfigNak #8 Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: rec'd Configure Request #9 link 0 (Req-Sent) Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.204 Jul 16 18:52:11 bull mpd: 192.168.0.204 is OK Jul 16 18:52:11 bull mpd: PRIDNS 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: SendConfigAck #9 Jul 16 18:52:11 bull mpd: IPADDR 192.168.0.204 Jul 16 18:52:11 bull mpd: PRIDNS 192.168.0.10 Jul 16 18:52:11 bull mpd: PRINBNS 192.168.0.10 Jul 16 18:52:11 bull mpd: [pptp0] IPCP: state change Req-Sent --> Ack-Sent Jul 16 18:52:13 bull mpd: [pptp0] IPCP: SendConfigReq #204 Jul 16 18:52:13 bull mpd: IPADDR 192.168.0.10 Jul 16 18:52:13 bull mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jul 16 18:52:13 bull mpd: [pptp0] CCP: SendConfigReq #119 Jul 16 18:52:13 bull mpd: MPPC Jul 16 18:52:13 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:13 bull mpd: [pptp0] IPCP: rec'd Configure Reject #204 link 0 (Ack-Sent) Jul 16 18:52:13 bull mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Jul 16 18:52:13 bull mpd: [pptp0] IPCP: SendConfigReq #205 Jul 16 18:52:13 bull mpd: IPADDR 192.168.0.10 Jul 16 18:52:13 bull mpd: [pptp0] CCP: rec'd Configure Ack #119 link 0 (Ack-Sent) Jul 16 18:52:13 bull mpd: MPPC Jul 16 18:52:13 bull mpd: 0x01000040: MPPE, 128 bit, stateless Jul 16 18:52:13 bull mpd: [pptp0] CCP: state change Ack-Sent --> Opened Jul 16 18:52:13 bull mpd: [pptp0] CCP: LayerUp Jul 16 18:52:13 bull mpd: Compress using: MPPE, 128 bit, stateless Jul 16 18:52:13 bull mpd: Decompress using: MPPE, 128 bit, stateless Jul 16 18:52:13 bull mpd: [pptp0] setting interface ng0 MTU to 1500 bytes Jul 16 18:52:13 bull mpd: [pptp0] IPCP: rec'd Configure Ack #205 link 0 (Ack-Sent) Jul 16 18:52:13 bull mpd: IPADDR 192.168.0.10 Jul 16 18:52:13 bull mpd: [pptp0] IPCP: state change Ack-Sent --> Opened Jul 16 18:52:13 bull mpd: [pptp0] IPCP: LayerUp Jul 16 18:52:13 bull mpd: 192.168.0.10 -> 192.168.0.204 Jul 16 18:52:13 bull mpd: [pptp0] IFACE: Up event Jul 16 18:52:13 bull mpd: [pptp0] setting interface ng0 MTU to 1500 bytes Jul 16 18:52:13 bull mpd: [pptp0] exec: /sbin/ifconfig ng0 192.168.0.10 192.168.0.204 netmask 0xffffffff -link0 Jul 16 18:52:13 bull mpd: [pptp0] exec: /usr/sbin/arp -s 192.168.0.204 0:b0:d0:e1:48:74 pub Jul 16 18:52:13 bull mpd: [pptp0] exec: /sbin/route add 192.168.0.10 -iface lo0 Jul 16 18:52:13 bull mpd: [pptp0] exec: /sbin/route add 192.168.0.0 192.168.0.204 -netmask 0xffffff00 Jul 16 18:52:13 bull mpd: [pptp0] exec: command returned 256 Jul 16 18:52:13 bull mpd: [pptp0] IFACE: Up event Jul 16 18:52:13 bull mpd: [pptp0] rec'd unexpected protocol IP on link -1 My other problem (maybe related to the previous one ?) is SMB browsing : PPTP clients connected through the VPN can see but not browse all the other machines on the local network. The only one that can be browsed is the one also hosting the PPTP server : routing problem ? By the way, is there a way to reduce mpd's log verbosity ? Thanks for your time & help. Regards, --Yann From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 19:39:15 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AEA837B401; Wed, 16 Jul 2003 19:39:15 -0700 (PDT) Received: from mail.ludost.net (tonib-gw.customer.0rbitel.net [195.24.39.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 933AE43F85; Wed, 16 Jul 2003 19:39:13 -0700 (PDT) (envelope-from maav@bastun.net) Received: from SABBATH (ozzy.ddns.cablebg.net [217.18.240.240]) by mail.ludost.net (Postfix) with ESMTP id D7B214C691; Thu, 17 Jul 2003 05:38:58 +0300 (EEST) Message-ID: <000701c34c0c$8a6b4430$020aa8c0@SABBATH> From: "Boris Georgiev" To: "william paul" References: <200307160000.RAA22276@huisne.wrs.com> Date: Thu, 17 Jul 2003 05:38:28 +0300 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 02:39:15 -0000 Hi Bill, I tested the driver with the new patch and everything works fine now. Thank you for your quick response. If you need more testing of this NIC, I can always cooperate. Boris Georgiev ----- Original Message ----- From: "william paul" To: "Boris Georgiev" Cc: ; ; ; Sent: Wednesday, July 16, 2003 3:00 AM Subject: Re: Broadcom NetXtreme BCM5705M support > Of all the gin joints in all the towns in all the world, Boris Georgiev > had to walk into mine and say: > > > Hi Bill, > > > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > > by testing your drivers and > > I am not aware of the rules for declaring a hardware problem in the mailing > > lists. The only way I can send > > you the messages from the kernel is if I rewrite them from the console. > > I know that. But that's a small price to pay for free driver development. :) > > > Here is the information that you requested: > > > > bge0: mem > > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > > bge0: firmware handshake timed out > > bge0: RX CPU self-diagnostics failed! > > bge0: chip initialization failed > > device_probe_and_attach: bge0 attach returned 6 > > > > If you need more detailed information, I can send it to you on request. > > Ok, the firmware handshake does not really load any firmware. This just > checks that the firmware on the NIC has responded to a reset and is back > up and running. The error here is due to the fact that the firmware > initialization seems to take longer on the 5705, so the timeout has to > be increased. > > Thanks for a couple of other people, I have made changes to deal with > this. Please download the latest driver code from the same URL > (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the > problem with the timeout, as well as a few other things. > From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 23:03:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 461D537B405 for ; Wed, 16 Jul 2003 23:03:53 -0700 (PDT) Received: from Draculina.otdel-1.org (draculina.otdel-1.org [195.230.89.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36DE343F93 for ; Wed, 16 Jul 2003 23:03:52 -0700 (PDT) (envelope-from nms@Draculina.otdel-1.org) Received: from Draculina.otdel-1.org (localhost [127.0.0.1]) by Draculina.otdel-1.org (8.12.9/8.12.9) with ESMTP id h6H63lfq022591 for ; Thu, 17 Jul 2003 10:03:47 +0400 (MSD) (envelope-from nms@Draculina.otdel-1.org) Received: (from nms@localhost) by Draculina.otdel-1.org (8.12.9/8.12.9/Submit) id h6H63lIn022590 for freebsd-net@freebsd.org; Thu, 17 Jul 2003 10:03:47 +0400 (MSD) Date: Thu, 17 Jul 2003 10:03:46 +0400 From: Nikolai SAOUKH To: freebsd-net@freebsd.org Message-ID: <20030717060346.GB22535@otdel1.org> Mail-Followup-To: freebsd-net@freebsd.org References: <3F159A8C.9050204@almonde.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F159A8C.9050204@almonde.com> User-Agent: Mutt/1.5.4i Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 06:03:53 -0000 | As you'll see in the logs below and from ifconfig output, altough the | ngX interfaces MTU is set to 1460 with "set link mtu 1460", it stays at | 1500. Any idea why ? The asked mtu size will be available (set) only when interface is in UP state. When the ngX is in down state it has default values. From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 00:57:18 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB93037B401 for ; Thu, 17 Jul 2003 00:57:17 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B6A843F3F for ; Thu, 17 Jul 2003 00:57:17 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from homer.softweyr.com (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id E3C101B37E; Thu, 17 Jul 2003 00:57:15 -0700 (PDT) From: Wes Peters Organization: Softweyr LLC To: Chuck Swiger Date: Thu, 17 Jul 2003 00:18:43 -0700 User-Agent: KMail/1.5 References: <200307151709.h6FH9UOW055742@hole.shrew.net> <200307151548.48778.wes@softweyr.com> <3F149303.1010408@mac.com> In-Reply-To: <3F149303.1010408@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307170018.43157.wes@softweyr.com> cc: "freebsd-net@freebsd.org" Subject: Re: broadcast udp packets ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 07:57:18 -0000 On Tuesday 15 July 2003 04:49 pm, Chuck Swiger wrote: > Wes Peters wrote: > [ ... ] > > > The idea is, we have listener on each ethernet interface listening > > via a bpf. The listener listens for an 'appliance discovery' > > packet which is broadcast by the console application running on the > > admin's workstation. When we receive this discovery packet, we're > > supposed to reply back with a broadcast packet that says 'here I > > am' so the console can get our MAC address. The console > > application does some special h0h0 magic of it's own then sends us > > back another broadcast message that has IP addresses for all 3 > > interfaces. > > Is "h0h0 magic" another term for ARP and RARP? :-) Have you seen > RFC-903? No, "h0h0 magic" is another term for having asked the user of the box a lot of questions about how he's going to use it and having gotten from him the IP addresses 1, 2, or all 3 of the physical interfaces will use. It's a box that in various configurations can be a host, a bridge, a router, or a proxy, each with a possible private "management" interface, or maybe a DMZ port. > > It's a wonderful idea but it doesn't work. This seems in keeping > > with the spirit of BOOTP, DHCP, et al, but is explicitly designed > > to assign a permanent address to an appliance that cannot know it's > > boot address when configured and cannot really predict which of the > > 3 interfaces it might receive an address from. > > Yes, indeed. Of course, there is the issue of how an IP-based reply > should be addressed to an interface which is UP but does not have an > IP address configured as yet? See RFC 919. > [ ... ] > > > So, in short, the IP address 255.255.255.255 is a special case that > > isn't handled as a special case by the ip_output code. I propose > > to change the code so that a packet sent to destination address > > 255.255.255.255 (aka INADDR_BROADCAST) be handled specially. Any > > such packet will be sent to destination address 255.255.255.255 on > > each interface that is marked UP and BROADCAST, with the ip src > > address set to the currently configured primary ip address of the > > interface, even if this is 0.0.0.0. This special case will not > > call rtalloc or do any other route lookups. > > Agreed with regard to not performing any routing. I don't think of > sending to INADDR_BROADCAST as a special case, so much as a > generalization of sending to the network broadcast address, only for > all networks. Or a single network with no routing and no subnet > mask, which people using pure layer-2 switching instead of layer-3 > routing sometimes do. [Such networks are wacky. You tend to > identify machines by MAC or via non-IP protocols... ] Again, see RFC 919. > One concern I have is thinking about too tricky special cases and not > getting the basics correct. For instance, let's say I only have one > interface up, and it's point-to-point, not broadcast: if something > sends IP traffic to 255.255.255.255, shouldn't a packet go out with > the DST address of the PTP peer? If it's not configured for BROADCASTing, it probably shouldn't get the packet at all. This probably includes all point-to-point links, but the only ptp configuration I have right now is a VPN. The VPN interface does not typically have the interface configured for BROADCAST. > After all, the point of sending to 255.255.255.255 is that you are > notationally trying to "send traffic to all hosts that localhost can > reach" (and "are willing to hear"). The way to "send traffic to all > hosts" on a subnetted network efficiently is via the network > broadcast address, but that doesn't mean that there's nothing to talk > to over a point-to-point link. Please read RFC 919 and see if your interpretation agrees with mine. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 01:43:43 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 095E337B404 for ; Thu, 17 Jul 2003 01:43:41 -0700 (PDT) Received: from hotmail.com (law15-f76.law15.hotmail.com [64.4.23.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25D2843FAF for ; Thu, 17 Jul 2003 01:43:41 -0700 (PDT) (envelope-from soheil_hh@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 17 Jul 2003 01:43:40 -0700 Received: from 62.217.112.162 by lw15fd.law15.hotmail.msn.com with HTTP; Thu, 17 Jul 2003 08:43:40 GMT X-Originating-IP: [62.217.112.162] X-Originating-Email: [soheil_hh@hotmail.com] From: "soheil soheil" To: freebsd-net@freebsd.org Date: Thu, 17 Jul 2003 08:43:40 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 17 Jul 2003 08:43:40.0992 (UTC) FILETIME=[85EAE400:01C34C3F] Subject: Divert Socket Ported to Windows X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 08:43:43 -0000 Dear All Is there any package like divert socket available or ported on windows ? Thanx Soheil Hassas Yeganeh _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 02:14:42 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49D7F37B401 for ; Thu, 17 Jul 2003 02:14:42 -0700 (PDT) Received: from web21008.mail.yahoo.com (web21008.mail.yahoo.com [216.136.227.62]) by mx1.FreeBSD.org (Postfix) with SMTP id 004FA43F3F for ; Thu, 17 Jul 2003 02:14:42 -0700 (PDT) (envelope-from vovanvinh2001@yahoo.com) Message-ID: <20030717091441.77257.qmail@web21008.mail.yahoo.com> Received: from [203.162.5.197] by web21008.mail.yahoo.com via HTTP; Thu, 17 Jul 2003 02:14:41 PDT Date: Thu, 17 Jul 2003 02:14:41 -0700 (PDT) From: Van Vinh Vo To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: tcp/ip linux and freeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 09:14:42 -0000 Hi all, i about the research, compare network layer of linux and freeBSD. i read many documennt, freeBSD have tcp/ip protocol stack faster and more stable than linux, but i don't know the how to explain for this evalation ! can you explain it for me ! Thanks, __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 05:28:03 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AE6237B401 for ; Thu, 17 Jul 2003 05:28:03 -0700 (PDT) Received: from webfw.progtech.net (webfw.progtech.net [195.226.167.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96B6243F85 for ; Thu, 17 Jul 2003 05:28:02 -0700 (PDT) (envelope-from grossman@webfw.progtech.net) Received: from isis.muc.progtech.intern (isis.muc.progtech.intern [10.25.0.100]) by webfw.progtech.net (8.12.9/8.12.9) with ESMTP id h6HCRrEK049878 for ; Thu, 17 Jul 2003 14:27:54 +0200 (CEST) (envelope-from grossman) Received: (from grossman@localhost) by isis.muc.progtech.intern (8.11.6/8.9.3) id h6HCRr601636; Thu, 17 Jul 2003 14:27:53 +0200 (CEST) Date: Thu, 17 Jul 2003 14:27:53 +0200 (CEST) Message-Id: <200307171227.h6HCRr601636@isis.muc.progtech.intern> From: Rolf Grossmann MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-net@freebsd.org X-Mailer: VM 7.04 under Emacs 21.2.1 X-Virus-Scanned: by amavisd-new Subject: Trouble with natd and path mtu discovery (ICMP_UNREACH_NEEDFRAG) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 12:28:03 -0000 Hi, I'm currently running into a problem using natd with a private network that does not have an overall mtu of 1500. Unfortunately the setup is quite complex and I'd like to get by without explaining it all. So for the moment I'll just ask about what I think is the problem and if you need more information, you tell me so, okay ;) The packet in question is here. This is what it looks like before natd (received on internal interface): 14:04:43.688857 10.128.10.100 > 172.21.30.170: icmp: 10.129.16.1 unreachable - need to frag (mtu 1400) (DF) (ttl 253, id 0) 10.128.10.100 is the gateway that has a smaller mtu. 172.21.30.170 is the external host that was sending the big packet 10.129.16.1 is the internal host behind the gateway that requested the packet Now when that packet passed natd it looks like this (transmitted on external interface): 14:04:43.689091 10.128.10.100 > 172.21.30.170: icmp: 192.168.89.1 unreachable - need to frag (mtu 1400) (DF) (ttl 252, id 0) As you can see, the requesting host's ip has been adjusted to the "external" address of the host running natd. Unfortunately, the gateway's ip has not. Now if any router on the external side is doing reverse path checking (and as it's not working I believe there is one doing that), it will just drop the packet. And rightfully so, because it has an illegal source address. Now my question is: Is that a bug in natd or is there some standard that mandates the original ip must be preserved? And can someone please point me at the code to change to get that packet aliased? (I've been looking at libalias, but so far I don't quite get it.) Thanks a lot, Rolf. From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 08:05:47 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D224037B401; Thu, 17 Jul 2003 08:05:47 -0700 (PDT) Received: from webfw.progtech.net (webfw.progtech.net [195.226.167.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8479943FAF; Thu, 17 Jul 2003 08:05:45 -0700 (PDT) (envelope-from grossman@webfw.progtech.net) Received: from isis.muc.progtech.intern (isis.muc.progtech.intern [10.25.0.100]) by webfw.progtech.net (8.12.9/8.12.9) with ESMTP id h6HF5cEK053449; Thu, 17 Jul 2003 17:05:38 +0200 (CEST) (envelope-from grossman) Received: (from grossman@localhost) by isis.muc.progtech.intern (8.11.6/8.9.3) id h6HF5cl01802; Thu, 17 Jul 2003 17:05:38 +0200 (CEST) Date: Thu, 17 Jul 2003 17:05:38 +0200 (CEST) Message-Id: <200307171505.h6HF5cl01802@isis.muc.progtech.intern> From: Rolf Grossmann MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-net@freebsd.org In-Reply-To: <200307171227.h6HCRr601636@isis.muc.progtech.intern> References: <200307171227.h6HCRr601636@isis.muc.progtech.intern> X-Mailer: VM 7.04 under Emacs 21.2.1 X-Virus-Scanned: by amavisd-new Subject: Re: Trouble with natd and path mtu discovery (ICMP_UNREACH_NEEDFRAG) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 15:05:48 -0000 Hi again, I've done some more research and I think I found the reason for my problem: It's in lib/libalias/alias.c rev 1.23: > Changed the way we handle outgoing ICMP error messages -- do > not alias `ip_src' unless it comes from the host an original > datagram that triggered this error message was destined for. > > PR: 20712 Now I guess something was mixed up here. The PR was talking about incoming ICMP error message, while the log message and my problem concerns outgoing ICMP messages. Am I all wrong here? Bye, Rolf From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 08:07:18 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FD1E37B401 for ; Thu, 17 Jul 2003 08:07:18 -0700 (PDT) Received: from webfw.progtech.net (webfw.progtech.net [195.226.167.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11E3243FB1 for ; Thu, 17 Jul 2003 08:07:17 -0700 (PDT) (envelope-from grossman@webfw.progtech.net) Received: from isis.muc.progtech.intern (isis.muc.progtech.intern [10.25.0.100]) by webfw.progtech.net (8.12.9/8.12.9) with ESMTP id h6HF79EK053516 for ; Thu, 17 Jul 2003 17:07:10 +0200 (CEST) (envelope-from grossman) Received: (from grossman@localhost) by isis.muc.progtech.intern (8.11.6/8.9.3) id h6HF79D01805; Thu, 17 Jul 2003 17:07:09 +0200 (CEST) Date: Thu, 17 Jul 2003 17:07:09 +0200 (CEST) Message-Id: <200307171507.h6HF79D01805@isis.muc.progtech.intern> From: Rolf Grossmann MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-net@freebsd.org In-Reply-To: <200307171227.h6HCRr601636@isis.muc.progtech.intern> References: <200307171227.h6HCRr601636@isis.muc.progtech.intern> X-Mailer: VM 7.04 under Emacs 21.2.1 X-Virus-Scanned: by amavisd-new Subject: Re: Trouble with natd and path mtu discovery (ICMP_UNREACH_NEEDFRAG) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 15:07:18 -0000 Hi again, sorry, I keep forgetting to say, this is 4.8-STABLE. And I also wanted to say, backing out the patch from alias.c rev. 1.23 solves my problem, but as a result I may get the problem described in the PR. Rolf From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 09:40:19 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05B9B37B404 for ; Thu, 17 Jul 2003 09:40:19 -0700 (PDT) Received: from bull.almonde.com (almonde.net2.nerim.net [62.212.111.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79D3F43F3F for ; Thu, 17 Jul 2003 09:40:17 -0700 (PDT) (envelope-from yann.nottara@almonde.com) Received: from almonde.com (vulture.almonde.com [192.168.0.156]) by bull.almonde.com (8.12.6/8.12.6) with ESMTP id h6HGeDi7072326 for ; Thu, 17 Jul 2003 18:40:13 +0200 (CEST) (envelope-from yann.nottara@almonde.com) Message-ID: <3F16D1AC.8070802@almonde.com> Date: Thu, 17 Jul 2003 18:41:16 +0200 From: Yann Nottara Organization: Almonde User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr, en-us MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org> In-Reply-To: <20030717060346.GB22535@otdel1.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 16:40:19 -0000 Nikolai SAOUKH wrote: > | As you'll see in the logs below and from ifconfig output, altough the > | ngX interfaces MTU is set to 1460 with "set link mtu 1460", it stays at > | 1500. Any idea why ? > > The asked mtu size will be available (set) only when interface is in UP > state. When the ngX is in down state it has default values. Thanks for your help. Zs you can see in the following real world example, ng0 (which IS up) MTU stays at 1500 although it's configured to be at 1460 in the mpd.conf configuration file : ng0: flags=8890 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 ng1: flags=8890 mtu 1500 ng2: flags=8890 mtu 1500 ng3: flags=8890 mtu 1500 ... Any idea ? --Yann From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 10:31:41 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EA3837B401 for ; Thu, 17 Jul 2003 10:31:41 -0700 (PDT) Received: from mx1.evo6.net (mx1.evo6.net [80.76.194.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 9BF1343F93 for ; Thu, 17 Jul 2003 10:31:39 -0700 (PDT) (envelope-from andy@evo6.org) Received: (qmail 78315 invoked from network); 17 Jul 2003 17:31:37 -0000 Received: from vx.wi.dhcp.evo6.net (HELO vx) (10.0.2.2) by mx1.evo6.net with SMTP; 17 Jul 2003 17:31:37 -0000 Message-ID: <000901c34c89$439bf270$0202000a@vx> From: "Andy Gilligan" To: References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org> <3F16D1AC.8070802@almonde.com> Date: Thu, 17 Jul 2003 18:31:32 +0100 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Status: No, hits=0.2 required=5.0 tests=QUOTED_EMAIL_TEXT,REFERENCES,UPPERCASE_25_50 version=2.55-evo6.net X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-evo6.net (1.174.2.19-2003-05-19-exp) Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 17:31:41 -0000 ----- Original Message ----- From: "Yann Nottara" To: Sent: Thursday, July 17, 2003 5:41 PM Subject: Re: MPD 3.13 PPTP server MTU problems & questions > Zs you can see in the following real world example, ng0 (which IS up) > MTU stays at 1500 although it's configured to be at 1460 in the mpd.conf > configuration file : > > ng0: flags=8890 mtu 1500 > inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 This doesn't look UP to me :) > ng1: flags=8890 mtu 1500 > ng2: flags=8890 mtu 1500 > ng3: flags=8890 mtu 1500 > ... > > Any idea ? Whenever MPD receives a connection, and assigns that interface to a client, it will change the MTU and mark it as UP. At least, it does for me... Interface down, mpd running, no client connected: ng0: flags=8890 mtu 1500 inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 Client connects: ng0: flags=88d1 mtu 1396 inet 192.168.0.1 --> 192.168.0.2 netmask 0xffffffff inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 Regards, -Andy From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 10:52:19 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CC5B37B401 for ; Thu, 17 Jul 2003 10:52:19 -0700 (PDT) Received: from bull.almonde.com (almonde.net2.nerim.net [62.212.111.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB3CE43FA3 for ; Thu, 17 Jul 2003 10:52:17 -0700 (PDT) (envelope-from yann.nottara@almonde.com) Received: from almonde.com (vulture.almonde.com [192.168.0.156]) by bull.almonde.com (8.12.6/8.12.6) with ESMTP id h6HHqDi7073110 for ; Thu, 17 Jul 2003 19:52:14 +0200 (CEST) (envelope-from yann.nottara@almonde.com) Message-ID: <3F16E28C.10105@almonde.com> Date: Thu, 17 Jul 2003 19:53:16 +0200 From: Yann Nottara Organization: Almonde User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr, en-us MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org> <3F16D1AC.8070802@almonde.com> <000901c34c89$439bf270$0202000a@vx> In-Reply-To: <000901c34c89$439bf270$0202000a@vx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 17:52:19 -0000 Andy Gilligan wrote: > ----- Original Message ----- > From: "Yann Nottara" >>Zs you can see in the following real world example, ng0 (which IS up) >>MTU stays at 1500 although it's configured to be at 1460 in the mpd.conf >>configuration file : >> >>ng0: flags=8890 mtu 1500 >> inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 > > > This doesn't look UP to me :) [...] > Whenever MPD receives a connection, and assigns that interface to a > client, it will change the MTU and mark it as UP. > > At least, it does for me... > > Interface down, mpd running, no client connected: > > ng0: flags=8890 mtu 1500 > inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 > > Client connects: > > ng0: flags=88d1 mtu 1396 > inet 192.168.0.1 --> 192.168.0.2 netmask 0xffffffff > inet6 fe80::209:5bff:fe2f:692c%ng0 prefixlen 64 scopeid 0x7 > > Regards, > -Andy Ok, my mistake on this one :) but now, what do you think of this ? ng0: flags=88d1 mtu 1500 inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 inet 192.168.0.10 --> 192.168.0.200 netmask 0xffffffff and here's the part from my mpd.conf that's related to this connection : pptp0: new -i ng0 pptp0 pptp0 set iface disable on-demand set iface enable proxy-arp set iface idle 3600 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 <----------------- ! set ipcp yes vjcomp set ipcp ranges 192.168.0.10/32 192.168.0.200/32 set ipcp dns 192.168.0.10 set ipcp nbns 192.168.0.10 So, where's the catch ? --Yann From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 12:36:27 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DC2437B401 for ; Thu, 17 Jul 2003 12:36:27 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9DE543F3F for ; Thu, 17 Jul 2003 12:36:26 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.org (8.9.3/8.9.3) id NAA03141 for net@freebsd.org; Thu, 17 Jul 2003 13:36:22 -0600 (MDT) Date: Thu, 17 Jul 2003 13:36:22 -0600 (MDT) From: Brett Glass Message-Id: <200307171936.NAA03141@lariat.org> To: net@freebsd.org Subject: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 19:36:27 -0000 FreeBSD makes a very good NAT router... for most applications. But a client of mine is having terrible trouble with it when trying to use NAT with one particular protocol: PPTP. Here's what's going on. A client has a FreeBSD box that's serving as a NAT router. He has one public IP, and lots of PCs behind the router on unregistered IPs. This works fine when they're doing browsing, etc., but fails horribly when users try to use PPTP to tunnel out into another LAN across the Internet. The problem appears to be that PPTP -- while it uses TCP for its control connection -- uses GRE to encapsulate an encrypted PPP session between the client and the server. GRE, like TCP and UDP, is in the IP protocol family and uses IP addressing. However, it doesn't use "ports," as IP and UDP do; instead, it has a different mechanism for identifying packets that belong to different sessions or connections, and the header fields that must be inspected vary depending upon the encapsulated protocol. FreeBSD's natd doesn't understand that mechanism, so it doesn't know how to route GRE packets from the outside world back to the correct client on the private LAN. Some NAT routers (including the DI-604 from D-Link; see http://www.dlink.com/products/?pid=62) are able to route PPTP's GRE packets correctly when multiple clients on the private LAN want to tunnel out, so it's obviously possible. Who is the current maintainer of FreeBSD's NAT code (including natd and the NAT libraries)? How difficult would it be to add PPTP support to them? --Brett Glass From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 12:44:12 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 918A237B401 for ; Thu, 17 Jul 2003 12:44:12 -0700 (PDT) Received: from jawa.at (jawa.at [213.229.17.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68CD743F3F for ; Thu, 17 Jul 2003 12:44:11 -0700 (PDT) (envelope-from mbretter@jawa.at) Received: from worf (worf.jawa.at [192.168.201.12]) by jawa.at (8.12.8p1/8.12.8) with ESMTP id h6HJi1vB019038; Thu, 17 Jul 2003 21:44:01 +0200 (CEST) (envelope-from mbretter@jawa.at) Date: Thu, 17 Jul 2003 21:44:03 +0200 (CEST) From: Michael Bretterklieber To: Brett Glass In-Reply-To: <200307171936.NAA03141@lariat.org> Message-ID: <20030717214046.D365@worf.jawa.at> References: <200307171936.NAA03141@lariat.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=-26.4 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES autolearn=ham version=2.53 X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) cc: net@freebsd.org Subject: Re: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 19:44:12 -0000 Hi, On Thu, 17 Jul 2003, Brett Glass wrote: > inspected vary depending upon the encapsulated protocol. FreeBSD's natd > doesn't understand that mechanism, so it doesn't know how to route GRE packets > from the outside world back to the correct client on the private LAN. that's not true, libalias (=natd) very well supports PPTP-nat. Maybe the problem is in your firewall. Firewalls have to pass protocl 47 (=GRE) in order to get PPTP to work. bye, -- ------------------------------- ---------------------------------- Michael Bretterklieber - http://www.bretterklieber.com JAWA Management Software GmbH - http://www.jawa.at Tel: ++43-(0)316-403274-12 - GSM: ++43-(0)676-84 03 15 712 ------------------------------- ---------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 12:47:14 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A08C237B401 for ; Thu, 17 Jul 2003 12:47:14 -0700 (PDT) Received: from hole.shrew.net (cs24354-246.austin.rr.com [24.243.54.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D04143FA3 for ; Thu, 17 Jul 2003 12:47:13 -0700 (PDT) (envelope-from mgrooms@shrew.net) Received: from mail.shrew.net (localhost.shrew.net [127.0.0.1]) by hole.shrew.net (8.12.9/8.12.9) with SMTP id h6HJoCOW063062; Thu, 17 Jul 2003 19:50:12 GMT (envelope-from mgrooms@shrew.net) Message-Id: <200307171950.h6HJoCOW063062@hole.shrew.net> Received: from 65.118.63.254 (auth. user mgrooms@mail.shrew.net) by mail.shrew.net with HTTP; Thu, 17 Jul 2003 19:50:12 +0000 To: soheil_hh@hotmail.com Date: Thu, 17 Jul 2003 19:50:12 +0000 X-Mailer: IlohaMail/0.8.8 (On: mail.shrew.net) From: "Matthew Grooms" Bounce-To: "Matthew Grooms" Errors-To: "Matthew Grooms" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-net@freebsd.org Subject: Re: Divert Socket Ported to Windows X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 19:47:15 -0000 >Dear All >Is there any package like divert socket available or ported on windows ? >Thanx >Soheil Hassas Yeganeh Soheil, Data is funneled to divert sockets by IPFW ( anyone, please correct me if Im wrong ) or a similar mechanism which are nonexistant on win32. The closest open-source thingy ( to my knowledge ) would be winpcap which is a port of libpcap. ( I believe on *nix this sits on top of BPF or LPF ) You can do raw netowrk data capture with it but not diversion. Win32 uses a layered protocol stack for network services. Its possible to insert a shim at any point that would potentialy be able to 'divert' communication streams ( perhapse via a named pipe ). IIRC, its not a walk in the park to pull off. They do have a downloadable DDK for this somewhere on the msdn site. I would suggest you start your search there. -Matthew From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 12:52:32 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1275E37B401 for ; Thu, 17 Jul 2003 12:52:32 -0700 (PDT) Received: from jawa.at (jawa.at [213.229.17.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C614343F3F for ; Thu, 17 Jul 2003 12:52:30 -0700 (PDT) (envelope-from mbretter@jawa.at) Received: from worf (worf.jawa.at [192.168.201.12]) by jawa.at (8.12.8p1/8.12.8) with ESMTP id h6HJqPvB019873; Thu, 17 Jul 2003 21:52:25 +0200 (CEST) (envelope-from mbretter@jawa.at) Date: Thu, 17 Jul 2003 21:52:27 +0200 (CEST) From: Michael Bretterklieber To: Matthew Grooms In-Reply-To: <200307171950.h6HJoCOW063062@hole.shrew.net> Message-ID: <20030717215004.L365@worf.jawa.at> References: <200307171950.h6HJoCOW063062@hole.shrew.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=-26.4 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES autolearn=ham version=2.53 X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) cc: freebsd-net@freebsd.org Subject: Re: Divert Socket Ported to Windows X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 19:52:32 -0000 Hi, On Thu, 17 Jul 2003, Matthew Grooms wrote: > >Dear All > >Is there any package like divert socket available or ported on windows ? > >Thanx > >Soheil Hassas Yeganeh > > Soheil, > > Data is funneled to divert sockets by IPFW ( anyone, please correct > me if Im wrong ) or a similar mechanism which are nonexistant on win32. > The closest open-source thingy ( to my knowledge ) would be winpcap > which is a port of libpcap. ( I believe on *nix this sits on top of BPF > or LPF ) You can do raw netowrk data capture with it but not diversion. > > Win32 uses a layered protocol stack for network services. Its AFAIK, there exists a device-driver-kit from Microsoft, or something like this, where you have the possibility to hook your app into the IP-stream. Usualy Personal-Firewall are using this. bye, -- ------------------------------- ---------------------------------- Michael Bretterklieber - http://www.bretterklieber.com JAWA Management Software GmbH - http://www.jawa.at Tel: ++43-(0)316-403274-12 - GSM: ++43-(0)676-84 03 15 712 ------------------------------- ---------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 13:20:09 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A4237B401 for ; Thu, 17 Jul 2003 13:20:09 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCB4E43F3F for ; Thu, 17 Jul 2003 13:20:08 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id OAA03516; Thu, 17 Jul 2003 14:19:51 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20030717141336.029bbb70@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 17 Jul 2003 14:19:47 -0600 To: Michael Bretterklieber From: Brett Glass In-Reply-To: <20030717214046.D365@worf.jawa.at> References: <200307171936.NAA03141@lariat.org> <200307171936.NAA03141@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: net@freebsd.org Subject: Re: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 20:20:10 -0000 At 01:44 PM 7/17/2003, Michael Bretterklieber wrote: >that's not true, libalias (=natd) very well supports PPTP-nat. Maybe the >problem is in your firewall. Firewalls have to pass protocl 47 (=GRE) in >order to get PPTP to work. It is. In fact, I think that may be part of the problem. I didn't set this firewall up, but I do see a rule in there, fairly early on, that says "allow gre from any to any". Apparently, the literature says to add this. It occurs to me that this rule may cause the packets to bypass natd. On the other hand, if it's removed, the GRE packets seem to get blocked. Hmmm. --Brett From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 13:25:20 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0433837B401 for ; Thu, 17 Jul 2003 13:25:20 -0700 (PDT) Received: from mx1.evo6.net (mx1.evo6.net [80.76.194.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 7AFE543F93 for ; Thu, 17 Jul 2003 13:25:18 -0700 (PDT) (envelope-from andy@evo6.org) Received: (qmail 15708 invoked from network); 17 Jul 2003 20:25:17 -0000 Received: from vx.wi.dhcp.evo6.net (HELO vx) (10.0.2.2) by mx1.evo6.net with SMTP; 17 Jul 2003 20:25:17 -0000 Message-ID: <006f01c34ca1$85ee79f0$0202000a@vx> From: "Andy Gilligan" To: References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org><3F16D1AC.8070802@almonde.com> <000901c34c89$439bf270$0202000a@vx> <3F16E28C.10105@almonde.com> Date: Thu, 17 Jul 2003 21:25:11 +0100 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Status: No, hits=-1.0 required=5.0 tests=QUOTED_EMAIL_TEXT,REFERENCES version=2.55-evo6.net X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-evo6.net (1.174.2.19-2003-05-19-exp) Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 20:25:20 -0000 ----- Original Message ----- From: "Yann Nottara" To: Sent: Thursday, July 17, 2003 6:53 PM Subject: Re: MPD 3.13 PPTP server MTU problems & questions > but now, what do you think of this ? > > ng0: flags=88d1 mtu 1500 > inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 > inet 192.168.0.10 --> 192.168.0.200 netmask 0xffffffff > > and here's the part from my mpd.conf that's related to this connection : > > pptp0: > new -i ng0 pptp0 pptp0 > set iface disable on-demand > set iface enable proxy-arp > set iface idle 3600 > set bundle enable multilink > set link yes acfcomp protocomp > set link no pap chap > set link enable chap > set link keep-alive 10 60 > set link mtu 1460 <----------------- ! > set ipcp yes vjcomp > set ipcp ranges 192.168.0.10/32 192.168.0.200/32 > set ipcp dns 192.168.0.10 > set ipcp nbns 192.168.0.10 > > So, where's the catch ? Pretty much the same config as myself, with the exeption that I have: set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless I've set the MTU to 1460 - as you have, which seems to give me 1396 when a client connects. So far, I've only tested this with Windows XP machines, so I'm not sure if anything OS-specific concerning the MTU is negotiated during the connect phase, or even if having MPPE enabled would affect it. I imagine you've tried setting the MTU to other values? Best regards, -Andy From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 13:34:56 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19B7537B401 for ; Thu, 17 Jul 2003 13:34:56 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8892743FA3 for ; Thu, 17 Jul 2003 13:34:55 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.233.125.100]) by attbi.com (rwcrmhc11) with ESMTP id <2003071720345401300l1eioe>; Thu, 17 Jul 2003 20:34:54 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA05722; Thu, 17 Jul 2003 13:34:47 -0700 (PDT) Date: Thu, 17 Jul 2003 13:34:45 -0700 (PDT) From: Julian Elischer To: Brett Glass In-Reply-To: <200307171936.NAA03141@lariat.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: net@freebsd.org Subject: Re: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 20:34:56 -0000 how is he doing pptp? On Thu, 17 Jul 2003, Brett Glass wrote: > FreeBSD makes a very good NAT router... for most applications. > But a client of mine is having terrible trouble with it when > trying to use NAT with one particular protocol: PPTP. > > Here's what's going on. A client has a FreeBSD box that's serving as a > NAT router. He has one public IP, and lots of PCs behind the router on > unregistered IPs. This works fine when they're doing browsing, etc., but > fails horribly when users try to use PPTP to tunnel out into another LAN > across the Internet. > > The problem appears to be that PPTP -- while it uses TCP for its control > connection -- uses GRE to encapsulate an encrypted PPP session between the > client and the server. GRE, like TCP and UDP, is in the IP protocol family and > uses IP addressing. However, it doesn't use "ports," as IP and UDP do; > instead, it has a different mechanism for identifying packets that belong to > different sessions or connections, and the header fields that must be > inspected vary depending upon the encapsulated protocol. FreeBSD's natd > doesn't understand that mechanism, so it doesn't know how to route GRE packets > from the outside world back to the correct client on the private LAN. > > Some NAT routers (including the DI-604 from D-Link; see > http://www.dlink.com/products/?pid=62) are able to route PPTP's GRE packets > correctly when multiple clients on the private LAN want to tunnel out, so it's > obviously possible. Who is the current maintainer of FreeBSD's NAT code > (including natd and the NAT libraries)? How difficult would it be to add > PPTP support to them? > > --Brett Glass > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 16:59:01 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE46C37B401 for ; Thu, 17 Jul 2003 16:59:01 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0FEF43F75 for ; Thu, 17 Jul 2003 16:59:00 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id RAA06558; Thu, 17 Jul 2003 17:58:48 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20030717175006.03309100@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 17 Jul 2003 17:58:31 -0600 To: Julian Elischer From: Brett Glass In-Reply-To: References: <200307171936.NAA03141@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: net@freebsd.org Subject: Re: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 23:59:02 -0000 Actually, in his case the PPTP clients are Windows machines inside the firewall, while the servers are outside and not under his control. The firewall itself isn't running PPTP. At least one of the servers is running pptpd + Somers PPP + natd. I can connect to it just fine from a machine with a "real" IP address. --Brett At 02:34 PM 7/17/2003, Julian Elischer wrote: >how is he doing pptp? From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 17:45:38 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A630837B401 for ; Thu, 17 Jul 2003 17:45:37 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DAFC43F3F for ; Thu, 17 Jul 2003 17:45:37 -0700 (PDT) (envelope-from sloach@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id <305LF8B2>; Thu, 17 Jul 2003 20:45:36 -0400 Message-ID: From: Scot Loach To: 'Bosko Milekic' , Scot Loach Date: Thu, 17 Jul 2003 20:45:29 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-net@freebsd.org'" Subject: RE: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 00:45:39 -0000 Bosko: The problem I have is that each of the four pcb types has its own zone that is preallocated to hold maxsockets pcbs. This is a waste of kva that could be better used. Since I'm not using divert sockets or raw sockets, I would rather cap these zones to a small constant number, and increase the others as much as possible. I should have a patch for this next week sometime. -----Original Message----- From: Bosko Milekic [mailto:bmilekic@technokratis.com] Sent: Wednesday, July 16, 2003 5:52 AM To: Scot Loach Cc: 'freebsd-net@freebsd.org' Subject: Re: Kernel tuning for large maxsockets On Tue, Jul 15, 2003 at 05:22:55PM -0400, Scot Loach wrote: > Currently, whenever maxsockets is increased, this causes kernel memory to be > preallocated for each type of pcb (tcp, udp, raw, divert). The number of > pcbs preallocated for each of these is always the same as maxsockets. > > This is probably a waste of memory for raw sockets and divert sockets, since > they would not normally be used in large numbers. A large server could > save kvm by reducing the number of divert and raw pcbs preallocated. For > example, on a machine configured for 200,000 maxsockets we would save 75MB > of kvm out of a total of 262MB that would have been preallocated. This kvm > savings can be used to increase maxsockets even more. What version of FreeBSD are you talking about here? In -current, the pcbs come off of zones which are capped at a maximum w.r.t. maxsockets. The kva space comes out of kmem_map and the objects are kept cached in their respective zones. One thing to note is that the zones are setup with UMA_ZONE_NOFREE, so the pages wired down for pcb use are probably never unwired. I don't know why, exactly, UMA_ZONE_NOFREE is required for all of the pcb zones in the netinet code. > Is there any reason I should not modify the kernel code to only let a small, > fixed number of raw and divert pcbs be preallocated instead of having them > scale with maxsockets? > > Next, does this seem like a generally useful thing that could be rolled back > into the source tree? I could make this a kernel option or a tunable sysctl > variable. > > thanks > > Scot Loach -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/ From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 20:15:07 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FDF337B401 for ; Thu, 17 Jul 2003 20:15:07 -0700 (PDT) Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75F4643FB1 for ; Thu, 17 Jul 2003 20:15:06 -0700 (PDT) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.2.2.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id UAA48082; Thu, 17 Jul 2003 20:05:08 -0700 (PDT) Received: from arch20m.dellroad.org (localhost [127.0.0.1]) by arch20m.dellroad.org (8.12.8/8.12.6) with ESMTP id h6I34kPd037557; Thu, 17 Jul 2003 20:04:46 -0700 (PDT) (envelope-from archie@arch20m.dellroad.org) Received: (from archie@localhost) by arch20m.dellroad.org (8.12.8/8.12.8/Submit) id h6I34jlr037556; Thu, 17 Jul 2003 20:04:45 -0700 (PDT) From: Archie Cobbs Message-Id: <200307180304.h6I34jlr037556@arch20m.dellroad.org> In-Reply-To: <3F16E28C.10105@almonde.com> To: Yann Nottara Date: Thu, 17 Jul 2003 20:04:45 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-net@FreeBSD.ORG Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 03:15:07 -0000 Yann Nottara wrote: > but now, what do you think of this ? > > ng0: flags=88d1 mtu 1500 > inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 > inet 192.168.0.10 --> 192.168.0.200 netmask 0xffffffff > > and here's the part from my mpd.conf that's related to this connection : > > pptp0: > new -i ng0 pptp0 pptp0 > set iface disable on-demand > set iface enable proxy-arp > set iface idle 3600 > set bundle enable multilink > set link yes acfcomp protocomp > set link no pap chap > set link enable chap > set link keep-alive 10 60 > set link mtu 1460 <----------------- ! > set ipcp yes vjcomp > set ipcp ranges 192.168.0.10/32 192.168.0.200/32 > set ipcp dns 192.168.0.10 > set ipcp nbns 192.168.0.10 > > So, where's the catch ? If what you want is to set a hard limit then "set iface mtu 1460" is the command to use. "set link mtu" just initializes the starting value for LCP negotiation. -Archie __________________________________________________________________________ Archie Cobbs * Halloo Communications * http://www.halloo.com From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 20:56:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2852637B401 for ; Thu, 17 Jul 2003 20:56:53 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 717C743F93 for ; Thu, 17 Jul 2003 20:56:52 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h6I00wEH024666; Fri, 18 Jul 2003 00:00:58 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h6I00vH8024665; Fri, 18 Jul 2003 00:00:57 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Fri, 18 Jul 2003 00:00:57 +0000 From: Bosko Milekic To: Scot Loach Message-ID: <20030718000057.GA24620@technokratis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: "'freebsd-net@freebsd.org'" Subject: Re: Kernel tuning for large maxsockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 03:56:53 -0000 On Thu, Jul 17, 2003 at 08:45:29PM -0400, Scot Loach wrote: > Bosko: > > The problem I have is that each of the four pcb types has its own zone that > is preallocated to hold maxsockets pcbs. This is a waste of kva that could > be better used. Since I'm not using divert sockets or raw sockets, I would > rather cap these zones to a small constant number, and increase the others > as much as possible. > > I should have a patch for this next week sometime. The kva is not pre-allocated. The more allocations you have for that pcb type, the more memory and kva space will be reserved for them. As I said, the kva used for the pcbs will come out of kmem_map. If you're allocating the pcbs, then you're not wasting the kva. When you free them, the kva and memory stayed reserved, but this is required for type stable storage, which the pcbs appear to be. -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/ From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 22:08:58 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9984A37B401 for ; Thu, 17 Jul 2003 22:08:58 -0700 (PDT) Received: from 203-134-120-146.cust.mel.iprimus.net.au (203-134-120-146.cust.mel.iprimus.net.au [203.134.120.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C59AA43FA3 for ; Thu, 17 Jul 2003 22:08:56 -0700 (PDT) (envelope-from jon.newson@sdrct.com) Received: (from smap@localhost)h6I59YV00766 for ; Fri, 18 Jul 2003 15:09:34 +1000 (EST) (envelope-from jon.newson@sdrct.com) X-Authentication-Warning: outgoing-a.fw.act.domain: smap set sender to using -f Received: from if-outdmz.fw.act.domain(192.168.130.1) by outgoing-a.fw.act.domain via smap (V2.1) id xma000762; Fri, 18 Jul 03 15:09:23 +1000 Received: (from amavis@localhost) by mailfwd.au.adcomtech.net (8.11.1/8.11.1) id h6I59UH61971 for net@freebsd.org; Fri, 18 Jul 2003 15:09:30 +1000 (EST) Received: from ntserver.act.domain (ntserver [192.168.1.1]) h6I59OV61956; Fri, 18 Jul 2003 15:09:24 +1000 (EST) Received: by ntserver.act.domain with Internet Mail Service (5.5.2650.21) id <3N64DJ8S>; Fri, 18 Jul 2003 15:09:17 +1000 Message-ID: <1379FE1A8B3ED71188B8009027732E1A02446A@ntserver.act.domain> From: Jon Newson To: "'Brett Glass'" , net@freebsd.org Date: Fri, 18 Jul 2003 15:09:16 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Virus-Scanned: by AMaViS perl-11 Subject: RE: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 05:08:58 -0000 A couple of thoughts: Is your client employing ipsec/isakmp? If so, has your client ensured that the setkey -P entries have been pushed into the kernel? Correct me if i'm wrong, but from (a foggy) memory GRE in a tunnel mode such as this, employs the gif device, is the routing/firewalling allowing for this? cheers, -jn -----Original Message----- From: Brett Glass [mailto:brett@lariat.org] Sent: Friday, July 18, 2003 5:36 AM To: net@freebsd.org Subject: NAT and PPTP FreeBSD makes a very good NAT router... for most applications. But a client of mine is having terrible trouble with it when trying to use NAT with one particular protocol: PPTP. Here's what's going on. A client has a FreeBSD box that's serving as a NAT router. He has one public IP, and lots of PCs behind the router on unregistered IPs. This works fine when they're doing browsing, etc., but fails horribly when users try to use PPTP to tunnel out into another LAN across the Internet. The problem appears to be that PPTP -- while it uses TCP for its control connection -- uses GRE to encapsulate an encrypted PPP session between the client and the server. GRE, like TCP and UDP, is in the IP protocol family and uses IP addressing. However, it doesn't use "ports," as IP and UDP do; instead, it has a different mechanism for identifying packets that belong to different sessions or connections, and the header fields that must be inspected vary depending upon the encapsulated protocol. FreeBSD's natd doesn't understand that mechanism, so it doesn't know how to route GRE packets from the outside world back to the correct client on the private LAN. Some NAT routers (including the DI-604 from D-Link; see http://www.dlink.com/products/?pid=62) are able to route PPTP's GRE packets correctly when multiple clients on the private LAN want to tunnel out, so it's obviously possible. Who is the current maintainer of FreeBSD's NAT code (including natd and the NAT libraries)? How difficult would it be to add PPTP support to them? --Brett Glass _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Jul 17 23:50:10 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A59D537B401 for ; Thu, 17 Jul 2003 23:50:10 -0700 (PDT) Received: from kommun.engelholm.se (iris.kommun.engelholm.se [195.216.51.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF60643F93 for ; Thu, 17 Jul 2003 23:50:08 -0700 (PDT) (envelope-from roger.olofsson@kommun.engelholm.se) Received: from rogers.kommun.engelholm.se (authenticated user ron3000@kommun.engelholm.se) by kommun.engelholm.se (MDaemon.PRO.v6.8.4.R) with ESMTP id 49-md50000000179.tmp for ; Fri, 18 Jul 2003 08:53:11 +0200 Message-Id: <5.2.0.9.1.20030718084604.01f95350@mail.kommun.engelholm.se> X-Sender: ron3000@mail.kommun.engelholm.se X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 18 Jul 2003 08:50:02 +0200 To: freebsd-net@freebsd.org From: Roger Olofsson Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: ron3000@kommun.engelholm.se X-Spam-Processed: kommun.engelholm.se, Fri, 18 Jul 2003 08:53:11 +0200 (not processed: message from valid local sender) X-Return-Path: roger.olofsson@kommun.engelholm.se X-MDaemon-Deliver-To: freebsd-net@freebsd.org Subject: FreeBSD 5.0 ncplib missing kernel module nwfs.ko? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: roger.olofsson@kommun.engelholm.se List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 06:50:11 -0000 Dear Mailinglist, My FreeBSD5.0 tells me "ncp_initlib: can't find kernel module" after doing= =20 a mount_nwfs. Kldstat -v tells me that nwfs.ko isn't there. The if_ef.ko is= =20 there though. I have options IPX in kernel and the IPXrouted is running= fine. Could the ncplib port be broken on 5.0? I'd be grateful for any help on the matter. /Roger Med v=E4nlig h=E4lsning Roger Olofsson From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 02:05:52 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05E6F37B401 for ; Fri, 18 Jul 2003 02:05:52 -0700 (PDT) Received: from bull.almonde.com (almonde.net2.nerim.net [62.212.111.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADDCE43FB1 for ; Fri, 18 Jul 2003 02:05:50 -0700 (PDT) (envelope-from yann.nottara@almonde.com) Received: from almonde.com (vulture.almonde.com [192.168.0.156]) by bull.almonde.com (8.12.6/8.12.6) with ESMTP id h6I95li7078465 for ; Fri, 18 Jul 2003 11:05:48 +0200 (CEST) (envelope-from yann.nottara@almonde.com) Message-ID: <3F17B8A9.5000405@almonde.com> Date: Fri, 18 Jul 2003 11:06:49 +0200 From: Yann Nottara Organization: Almonde User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr, en-us MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <3F159A8C.9050204@almonde.com> <20030717060346.GB22535@otdel1.org><3F16D1AC.8070802@almonde.com> <000901c34c89$439bf270$0202000a@vx> <3F16E28C.10105@almonde.com> <006f01c34ca1$85ee79f0$0202000a@vx> In-Reply-To: <006f01c34ca1$85ee79f0$0202000a@vx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: MPD 3.13 PPTP server MTU problems & questions X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 09:05:52 -0000 Andy Gilligan wrote: > ----- Original Message ----- > From: "Yann Nottara" > To: > Sent: Thursday, July 17, 2003 6:53 PM > Subject: Re: MPD 3.13 PPTP server MTU problems & questions > > > >>but now, what do you think of this ? >> >>ng0: flags=88d1 mtu 1500 >> inet6 fe80::2b0:d0ff:fee1:4874%ng0 prefixlen 64 scopeid 0x7 >> inet 192.168.0.10 --> 192.168.0.200 netmask 0xffffffff >> >>and here's the part from my mpd.conf that's related to this connection : >> >>pptp0: >> new -i ng0 pptp0 pptp0 >> set iface disable on-demand >> set iface enable proxy-arp >> set iface idle 3600 >> set bundle enable multilink >> set link yes acfcomp protocomp >> set link no pap chap >> set link enable chap >> set link keep-alive 10 60 >> set link mtu 1460 <----------------- ! >> set ipcp yes vjcomp >> set ipcp ranges 192.168.0.10/32 192.168.0.200/32 >> set ipcp dns 192.168.0.10 >> set ipcp nbns 192.168.0.10 >> >>So, where's the catch ? > > > Pretty much the same config as myself, with the exeption that I have: > > set bundle enable compression > set ccp yes mppc > set ccp yes mpp-e40 > set ccp yes mpp-e128 > set ccp yes mpp-stateless Sorry, I forgot to include that part but I use it too. > I've set the MTU to 1460 - as you have, which seems to give me 1396 > when a client connects. > > So far, I've only tested this with Windows XP machines, so I'm not sure > if anything OS-specific concerning the MTU is negotiated during the > connect phase, or even if having MPPE enabled would affect it. My PPTP clients are all Windows 2000 machines. > I imagine you've tried setting the MTU to other values? Right, and it's all the same (but now I understand why after reading a post from this thread by Archie Cobbs. > Best regards, > -Andy Thanks for you help & comments. --Yann From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 03:05:09 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7ACA37B401 for ; Fri, 18 Jul 2003 03:05:09 -0700 (PDT) Received: from exchange.wan.no (exchange.wan.no [80.86.128.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9750243F93 for ; Fri, 18 Jul 2003 03:05:08 -0700 (PDT) (envelope-from sten.daniel.sorsdal@wan.no) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 18 Jul 2003 12:03:43 +0200 Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F1F3DF4@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NAT and PPTP Thread-Index: AcNMmo3QJfAOFMqlRG2kR9U0vBGG/wAeQXUA From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: "Brett Glass" , Subject: RE: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 10:05:10 -0000 =20 > FreeBSD makes a very good NAT router... for most applications. > But a client of mine is having terrible trouble with it when > trying to use NAT with one particular protocol: PPTP. >=20 > Here's what's going on. A client has a FreeBSD box that's serving as a > NAT router. He has one public IP, and lots of PCs behind the router on > unregistered IPs. This works fine when they're doing=20 > browsing, etc., but > fails horribly when users try to use PPTP to tunnel out into=20 > another LAN > across the Internet. >=20 natd handles pptp. we have multiple clients who are NATed and they = connect to different pptp gateways (occasionally the same too). if you are running a poptop pptp server and you want multiple clients=20 connecting to this one pptp server; make sure you get the GRE ID update (poptop always sets the id to 0 - messes up two connections). make sure you divert gre packets on their way out as well. - sten From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 09:04:56 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BA5437B481 for ; Fri, 18 Jul 2003 09:04:56 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9212643F3F for ; Fri, 18 Jul 2003 09:04:55 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from root@localhost) by lariat.org (8.9.3/8.9.3) id KAA13438; Fri, 18 Jul 2003 10:04:52 -0600 (MDT) Date: Fri, 18 Jul 2003 10:04:52 -0600 (MDT) From: Brett Glass Message-Id: <200307181604.KAA13438@lariat.org> To: brett@lariat.org, net@freebsd.org, sten.daniel.sorsdal@wan.no In-Reply-To: <0AF1BBDF1218F14E9B4CCE414744E70F1F3DF4@exchange.wanglobal.net> Subject: RE: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 16:04:56 -0000 > if you are running a poptop pptp server and you want multiple clients > connecting to this one pptp server; make sure you get the GRE ID update > (poptop always sets the id to 0 - messes up two connections). Is this update in the FreeBSD port/package for poptop? (It should be.) If not, where can the update be obtained? --Brett Glass From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 09:49:57 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38BFC37B401 for ; Fri, 18 Jul 2003 09:49:56 -0700 (PDT) Received: from exchange.wan.no (exchange.wan.no [80.86.128.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D55F43F3F for ; Fri, 18 Jul 2003 09:49:55 -0700 (PDT) (envelope-from sten.daniel.sorsdal@wan.no) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 18 Jul 2003 18:48:30 +0200 Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DEF5@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NAT and PPTP Thread-Index: AcNNRicn56aZWoDhTmKcEF6i5wD09wABD8kA From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: "Brett Glass" , Subject: RE: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 16:49:57 -0000 >=20 > > if you are running a poptop pptp server and you want=20 > multiple clients > > connecting to this one pptp server; make sure you get the=20 > GRE ID update > > (poptop always sets the id to 0 - messes up two connections). >=20 > Is this update in the FreeBSD port/package for poptop? (It should be.) > If not, where can the update be obtained? >=20 You have to hunt the net, unless it's added=20 in the current (1.1.4) version available in ports. Contact the usergroup of poptop to find out more and help them to realize it's a Good Idea to add it to the next versions - if not already in. www.poptop.org is a good starting point - Sten From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 12:58:35 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0F2037B401 for ; Fri, 18 Jul 2003 12:58:35 -0700 (PDT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7AF943F75 for ; Fri, 18 Jul 2003 12:58:34 -0700 (PDT) (envelope-from zel@free.fr) Received: from impt3-2.proxad.net (impt3-2.free.fr [213.228.0.204]) by postfix4-1.free.fr (Postfix) with ESMTP id 8F7A14205F for ; Fri, 18 Jul 2003 21:58:33 +0200 (CEST) Received: by impt3-2.proxad.net (Postfix, from userid 33) id 87FB8C112; Fri, 18 Jul 2003 21:58:33 +0200 (MEST) Received: from AAmiens-107-1-4-173.w81-49.abo.wanadoo.fr (AAmiens-107-1-4-173.w81-49.abo.wanadoo.fr [81.49.111.173]) by impt3-2.free.fr (IMP) with HTTP for ; Fri, 18 Jul 2003 21:58:33 +0200 Message-ID: <1058558313.3f18516964d52@impt3-2.free.fr> Date: Fri, 18 Jul 2003 21:58:33 +0200 From: zel@free.fr To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 Subject: Problem of newbee !!! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 19:58:36 -0000 Here is my problem: My config is described below: P100 + FreeBSD 4.4 for DMZ job ep0 (10.0.0.1) to Internet ed1 (10.1.0.254) gateway for 10.1.0.0/24 network (servers...) ed2 (192.168.1.254) gateway for 192.168.1.0/24 network (workstations...) So currently, connected with an ethernet ADSL modem to the Internet, I 'natd' all packets out and incoming... But now, I would like transfer all ftp request to one server behind DMZ... ftpd is running (on 10.1.0.1) I read man and some informations on forums about natd and so, I tried: natd -redirect_port tcp 10.1.0.1:20-21 20-21 I tried few other commands but I always have the same answer: natd: aliasing address not given ... What can I do ? Is the soft I currently try to use, the good one to do what I want to do ??? Please, help... Thanks.. Sylvain From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 13:12:03 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41C7F37B401 for ; Fri, 18 Jul 2003 13:12:03 -0700 (PDT) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87ED743F85 for ; Fri, 18 Jul 2003 13:12:01 -0700 (PDT) (envelope-from sheepkiller@cultdeadsheep.org) Received: (qmail 31864 invoked from network); 18 Jul 2003 20:11:59 -0000 Received: from unknown (HELO chuck.cultdeadsheep.org) (192.168.0.12) by goofy.cultdeadsheep.org with SMTP; 18 Jul 2003 20:11:59 -0000 Date: Fri, 18 Jul 2003 22:12:17 +0200 From: Clement Laforet To: zel@free.fr Message-Id: <20030718221217.173fd08c.sheepkiller@cultdeadsheep.org> In-Reply-To: <1058558313.3f18516964d52@impt3-2.free.fr> References: <1058558313.3f18516964d52@impt3-2.free.fr> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i386-portbld-freebsd5.1) X-Face: ._cVVRDn#-2((lnfi^P7CoD4htI$4+#G/G)!w|,}H5yK~%(3-C.JlEYbOjJGFwJkt*7N^%z jYeu[;}]}F"3}l5R'l"X0HbvT^D\Q&%deCo)MayY`);TO Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Problem of newbee !!! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 20:12:03 -0000 On Fri, 18 Jul 2003 21:58:33 +0200 zel@free.fr wrote: > I read man and some informations on forums about natd and so, I tried: > natd -redirect_port tcp 10.1.0.1:20-21 20-21 you need to load natd like this : natd -dynamic -n tun0 -redirect_port tcp 10.1.0.1:20-21 20-21 regards, clem From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 17:11:52 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D4F737B401; Fri, 18 Jul 2003 17:11:52 -0700 (PDT) Received: from borg-cube.com (netblock-66-159-209-110.dslextreme.com [66.159.209.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7C0E43F75; Fri, 18 Jul 2003 17:11:50 -0700 (PDT) (envelope-from dburr@borg-cube.com) Received: from borg-cube.com (dburr@borg-cube.com [66.159.209.110]) by borg-cube.com (8.12.9/8.12.8) with ESMTP id h6J0Bi6M078747; Fri, 18 Jul 2003 17:11:45 -0700 (PDT) (envelope-from dburr@borg-cube.com) Date: Fri, 18 Jul 2003 17:11:44 -0700 (PDT) From: Donald Burr of Borg To: FreeBSD Questions Message-ID: <20030718171119.Y78744@borg-cube.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-99.5 required=3.0 tests=USER_IN_WHITELIST,WORK_AT_HOME version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-net@freebsd.org Subject: Setting up a multi-platform VPN? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 00:11:52 -0000 I am in business with a couple of friends of mine, and to that end we are sharing an office with a single high-speed DSL connection. We are using FreeBSD (4.8-RELEASE, soon to be upgraded to -STABLE) as our gateway for the ineternal network, as well as serving e-mail, Web, etc. Some of us like to work at home sometmes, and in fact there are even days when NO ONE is in the office and we're all working from our various homes. To that end, we would like to be able to set up a VPN, so that those people who are working from home can access the office network directly. Now here's the problem: all of us are using different OS's. I use FreeBSD on my desktop, but sometimes I like to work on the couch, in which case I use my Titanium PowerBook running Mac OS X (which is of course based on FreeBSD). My boss uses OS X on his iBook, and my other friend uses a Linux box. Now, with my (admittedly virtually nonexistant) knowledge of VPN, I know that Linux boxen tend to use FreeSWAN. FreeBSD, on the other hand, seems to use something called RACOON. And lord knows what OS X uses (although, since it's FreeBSD based, maybe RACOON can be compiled/adapted to use on it too?) (although I just did a Google search, and according to this O'Reilly Network article, it seesm that OS X has its own built-in PPTP implementation: http://www.macdevcenter.com/pub/a/mac/2002/12/20/vpn.html) Can anyone more knowledgable than I help me figure out how to get this multi-platform VPN monster going? Help! I need some backup!! Thanks, Donald dburr@borg-cube.com -- Donald Burr of Borg | FreeBSD: The Power to Serve! Website: http://www.borg-cube.com/ | http://www.freebsd.org/ PO Box 91212, Santa Barbara CA 93190-1212 \----------------------------- Tel: (805)563-0672 ICQ# 16997506 Present Day... Present Time! From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 18:03:40 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8565237B404 for ; Fri, 18 Jul 2003 18:03:40 -0700 (PDT) Received: from mx1.evo6.net (mx1.evo6.net [80.76.194.10]) by mx1.FreeBSD.org (Postfix) with SMTP id A933943FAF for ; Fri, 18 Jul 2003 18:03:38 -0700 (PDT) (envelope-from andy@mx1.evo6.net) Received: (qmail 16549 invoked by uid 1001); 19 Jul 2003 01:03:36 -0000 Date: 19 Jul 2003 01:03:36 -0000 Message-ID: <20030719010336.9667.qmail@mx1.evo6.net> To: FreeBSD-gnats-submit@freebsd.org From: Andy Gilligan X-send-pr-version: 3.113 X-GNATS-Notify: X-Spam-Status: No, hits=-0.5 required=5.0 tests=PATCH_UNIFIED_DIFF version=2.55-evo6.net X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-evo6.net (1.174.2.19-2003-05-19-exp) cc: freebsd-net@freebsd.org Subject: [PATCH] IPv6 stealth forwarding X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andy Gilligan List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 01:03:41 -0000 >Submitter-Id: current-users >Originator: Andy Gilligan >Confidential: no >Synopsis: [PATCH] IPv6 stealth forwarding >Severity: non-critical >Priority: low >Category: kern >Class: change-request >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD vega 4.8-STABLE FreeBSD 4.8-STABLE #6: Fri Jul 18 23:46:58 BST 2003 root@vega:/usr/obj/usr/src/sys/VEGA i386 >Description: This patch enables stealth forwarding for IPv6. Similar to the functionality found in IPv4. A new sysctl variable has been added to control this behaviour: net.inet6.ip6.stealth The desired effect of this patch is to remove the router from traceroutes, in both directions. >How-To-Repeat: sysctl net.inet6.ip6.stealth=1 >Fix: Index: sys/netinet6/in6.h =================================================================== RCS file: /data/cvs/freebsd/src/sys/netinet6/in6.h,v retrieving revision 1.7.2.7 diff -u -r1.7.2.7 in6.h --- sys/netinet6/in6.h 1 Aug 2002 19:38:50 -0000 1.7.2.7 +++ sys/netinet6/in6.h 18 Jul 2003 23:36:48 -0000 @@ -567,7 +567,8 @@ /* New entries should be added here from current IPV6CTL_MAXID value. */ /* to define items, should talk with KAME guys first, for *BSD compatibility */ -#define IPV6CTL_MAXID 37 +#define IPV6CTL_STEALTH 43 /* MAXID from KAME CVS 20030719 */ +#define IPV6CTL_MAXID 44 #endif /* !_XOPEN_SOURCE */ Index: sys/netinet6/in6_proto.c =================================================================== RCS file: /data/cvs/freebsd/src/sys/netinet6/in6_proto.c,v retrieving revision 1.6.2.9 diff -u -r1.6.2.9 in6_proto.c --- sys/netinet6/in6_proto.c 24 Jan 2003 05:11:35 -0000 1.6.2.9 +++ sys/netinet6/in6_proto.c 18 Jul 2003 19:20:02 -0000 @@ -68,6 +68,7 @@ #include "opt_inet.h" #include "opt_inet6.h" #include "opt_ipsec.h" +#include "opt_ipstealth.h" #include #include @@ -302,6 +303,9 @@ u_int32_t ip6_id = 0UL; int ip6_keepfaith = 0; time_t ip6_log_time = (time_t)0L; +#ifdef IPSTEALTH +int ip6stealth = 0; +#endif /* icmp6 */ /* @@ -432,6 +436,10 @@ auto_linklocal, CTLFLAG_RW, &ip6_auto_linklocal, 0, ""); SYSCTL_STRUCT(_net_inet6_ip6, IPV6CTL_RIP6STATS, rip6stats, CTLFLAG_RD, &rip6stat, rip6stat, ""); +#ifdef IPSTEALTH +SYSCTL_INT(_net_inet6_ip6, IPV6CTL_STEALTH, stealth, CTLFLAG_RW, + &ip6stealth, 0, ""); +#endif /* net.inet6.icmp6 */ SYSCTL_INT(_net_inet6_icmp6, ICMPV6CTL_REDIRACCEPT, Index: sys/netinet6/ip6_forward.c =================================================================== RCS file: /data/cvs/freebsd/src/sys/netinet6/ip6_forward.c,v retrieving revision 1.4.2.7 diff -u -r1.4.2.7 ip6_forward.c --- sys/netinet6/ip6_forward.c 24 Jan 2003 05:11:35 -0000 1.4.2.7 +++ sys/netinet6/ip6_forward.c 18 Jul 2003 23:40:49 -0000 @@ -34,6 +34,7 @@ #include "opt_inet.h" #include "opt_inet6.h" #include "opt_ipsec.h" +#include "opt_ipstealth.h" #include #include @@ -156,6 +157,9 @@ return; } +#ifdef IPSTEALTH + if (!ip6stealth) { +#endif if (ip6->ip6_hlim <= IPV6_HLIMDEC) { /* XXX in6_ifstat_inc(rt->rt_ifp, ifs6_in_discard) */ icmp6_error(m, ICMP6_TIME_EXCEEDED, @@ -164,6 +168,9 @@ } ip6->ip6_hlim -= IPV6_HLIMDEC; +#ifdef IPSTEALTH + } +#endif /* * Save at most ICMPV6_PLD_MAXLEN (= the min IPv6 MTU - * size of IPv6 + ICMPv6 headers) bytes of the packet in case Index: sys/netinet6/ip6_var.h =================================================================== RCS file: /data/cvs/freebsd/src/sys/netinet6/ip6_var.h,v retrieving revision 1.2.2.4 diff -u -r1.2.2.4 ip6_var.h --- sys/netinet6/ip6_var.h 23 Jan 2003 21:06:47 -0000 1.2.2.4 +++ sys/netinet6/ip6_var.h 18 Jul 2003 05:19:14 -0000 @@ -284,6 +284,9 @@ extern int ip6_lowportmax; /* maximum reserved port */ extern int ip6_use_tempaddr; /* whether to use temporary addresses. */ +#ifdef IPSTEALTH +extern int ip6stealth; +#endif extern struct pr_usrreqs rip6_usrreqs; struct sockopt; From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 21:24:15 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6029737B401 for ; Fri, 18 Jul 2003 21:24:15 -0700 (PDT) Received: from web21004.mail.yahoo.com (web21004.mail.yahoo.com [216.136.227.58]) by mx1.FreeBSD.org (Postfix) with SMTP id 1A85243FCB for ; Fri, 18 Jul 2003 21:24:15 -0700 (PDT) (envelope-from vovanvinh2001@yahoo.com) Message-ID: <20030719042414.37719.qmail@web21004.mail.yahoo.com> Received: from [203.162.5.197] by web21004.mail.yahoo.com via HTTP; Fri, 18 Jul 2003 21:24:14 PDT Date: Fri, 18 Jul 2003 21:24:14 -0700 (PDT) From: Van Vinh Vo To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: what developpement of network between BSD 4.3 et BSD 4.4 life X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 04:24:15 -0000 i am working the research about the network of freeBSD i want knowing the developpement of BSD4.4 life comparing the 4.3 BSD. Thanks for your reply Vinh __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From owner-freebsd-net@FreeBSD.ORG Fri Jul 18 23:32:40 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34D5637B401; Fri, 18 Jul 2003 23:32:40 -0700 (PDT) Received: from jawa.at (jawa.at [213.229.17.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id D510143FBF; Fri, 18 Jul 2003 23:32:38 -0700 (PDT) (envelope-from mbretter@jawa.at) Received: from worf (worf.jawa.at [192.168.201.12]) by jawa.at (8.12.8p1/8.12.8) with ESMTP id h6J6ZDKR057953; Sat, 19 Jul 2003 08:35:13 +0200 (CEST) (envelope-from mbretter@jawa.at) Date: Sat, 19 Jul 2003 08:32:18 +0200 (CEST) From: Michael Bretterklieber To: Donald Burr of Borg In-Reply-To: <20030718171119.Y78744@borg-cube.com> Message-ID: <20030719082957.U370@worf.jawa.at> References: <20030718171119.Y78744@borg-cube.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=-22.7 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.53 X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) cc: freebsd-net@freebsd.org cc: FreeBSD Questions Subject: Re: Setting up a multi-platform VPN? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 06:32:40 -0000 Hi, On Fri, 18 Jul 2003, Donald Burr of Borg wrote: > Now, with my (admittedly virtually nonexistant) knowledge of VPN, I know > that Linux boxen tend to use FreeSWAN. FreeBSD, on the other hand, seems > to use something called RACOON. And lord knows what OS X uses (although, > since it's FreeBSD based, maybe RACOON can be compiled/adapted to use on > it too?) (although I just did a Google search, and according to this > O'Reilly Network article, it seesm that OS X has its own built-in PPTP > implementation: http://www.macdevcenter.com/pub/a/mac/2002/12/20/vpn.html) > > Can anyone more knowledgable than I help me figure out how to get this > multi-platform VPN monster going? Help! I need some backup!! > You can use MPD as PPTP server on your 4.8 Box. (cd /usr/ports/net/mpd && make && make install) bye, -- ------------------------------- ---------------------------------- Michael Bretterklieber - http://www.bretterklieber.com JAWA Management Software GmbH - http://www.jawa.at Tel: ++43-(0)316-403274-12 - GSM: ++43-(0)676-84 03 15 712 ------------------------------- ---------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 From owner-freebsd-net@FreeBSD.ORG Sat Jul 19 01:58:00 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FA2837B401; Sat, 19 Jul 2003 01:58:00 -0700 (PDT) Received: from yt.88.net (h-66-134-174-190.NYCMNY83.covad.net [66.134.174.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54E1243FAF; Sat, 19 Jul 2003 01:57:59 -0700 (PDT) (envelope-from john@zog.net) Received: from zog.net (localhost [127.0.0.1]) by yt.88.net (Postfix) with ESMTP id 8DCCB1BE; Sat, 19 Jul 2003 08:57:57 +0000 (GMT) Message-ID: <3F190A4F.8050203@zog.net> Date: Sat, 19 Jul 2003 11:07:27 +0200 From: John Morgan Salomon Organization: ZOG Consulting Ltd. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030528 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <20030718171119.Y78744@borg-cube.com> <20030719082957.U370@worf.jawa.at> In-Reply-To: <20030719082957.U370@worf.jawa.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: Donald Burr of Borg cc: FreeBSD Questions Subject: Re: Setting up a multi-platform VPN? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 08:58:00 -0000 You want KAME (http://www.kame.net). It is in 4.x. RACCOON is just the key management/exchange component of KAME. IPSEC (read the RFCs) is your best bet for inter-platform vpn connections. There are a number of FreeBSD implementations, although kame is probably your best bet for connecting to FreeSWAN/Cisco/CheckPoint/whatever. I'd be happy to give you some tips on setting it up if you have specific questions. Cheers, -John Michael Bretterklieber wrote: >Hi, > >On Fri, 18 Jul 2003, Donald Burr of Borg wrote: > > >>Now, with my (admittedly virtually nonexistant) knowledge of VPN, I know >>that Linux boxen tend to use FreeSWAN. FreeBSD, on the other hand, seems >>to use something called RACOON. And lord knows what OS X uses (although, >>since it's FreeBSD based, maybe RACOON can be compiled/adapted to use on >>it too?) (although I just did a Google search, and according to this >>O'Reilly Network article, it seesm that OS X has its own built-in PPTP >>implementation: http://www.macdevcenter.com/pub/a/mac/2002/12/20/vpn.html) >> >>Can anyone more knowledgable than I help me figure out how to get this >>multi-platform VPN monster going? Help! I need some backup!! >> >> >> >You can use MPD as PPTP server on your 4.8 Box. >(cd /usr/ports/net/mpd && make && make install) > >bye, >-- >------------------------------- ---------------------------------- >Michael Bretterklieber - http://www.bretterklieber.com >JAWA Management Software GmbH - http://www.jawa.at >Tel: ++43-(0)316-403274-12 - GSM: ++43-(0)676-84 03 15 712 >------------------------------- ---------------------------------- >"...the number of UNIX installations has grown to 10, with more >expected..." - Dennis Ritchie and Ken Thompson, June 1972 >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > From owner-freebsd-net@FreeBSD.ORG Sat Jul 19 04:14:40 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 616AD37B401; Sat, 19 Jul 2003 04:14:40 -0700 (PDT) Received: from epita.fr (hermes.epita.fr [163.5.255.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3C0F43F3F; Sat, 19 Jul 2003 04:14:38 -0700 (PDT) (envelope-from le-hen_j@epita.fr) Received: from carpediem (carpediem.epita.fr [10.42.42.5]) by epita.fr id h6JBEQT17774 Sat, 19 Jul 2003 13:14:26 +0200 (CEST) Date: Sat, 19 Jul 2003 13:14:25 +0200 From: jeremie le-hen To: John Morgan Salomon Message-ID: <20030719111425.GA12739@carpediem.epita.fr> References: <20030718171119.Y78744@borg-cube.com> <20030719082957.U370@worf.jawa.at> <3F190A4F.8050203@zog.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F190A4F.8050203@zog.net> User-Agent: Mutt/1.4i cc: freebsd-net@freebsd.org cc: Donald Burr of Borg cc: FreeBSD Questions Subject: Re: Setting up a multi-platform VPN? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 11:14:40 -0000 On Sat, Jul 19, 2003 at 11:07:27AM +0200, John Morgan Salomon wrote: > You want KAME (http://www.kame.net). It is in 4.x. RACCOON is just > the key management/exchange component of KAME. > > IPSEC (read the RFCs) is your best bet for inter-platform vpn connections. > There are a number of FreeBSD implementations, although kame is probably > your best bet for connecting to FreeSWAN/Cisco/CheckPoint/whatever. Linux has two different implementations of IPSec, the most popular is FreeS/WAN. The other one is called USAGI (http://www.linux-ipv6.org/) and it is in a very close collaboration with the KAME project (see USAGI project overview). Indeed it uses the same IKE daemon (racoon) and its configuration is exactly the same as KAME's one. Furthermore, USAGI will be the official IPSec implementation for 2.6 kernel series (it is already merged in the 2.5 source tree). Of course USAGI is also available for 2.4 kernels. So I think using USAGI on your friend's Linux laptop is a good choice, because it will save you understanding one more IPSec implementation and configuration, in case you decide to use IPSec of course... :-) Regards, -- Jeremie aka TtZ jeremie.le-hen@epita.fr From owner-freebsd-net@FreeBSD.ORG Sat Jul 19 05:30:50 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0034F37B401 for ; Sat, 19 Jul 2003 05:30:49 -0700 (PDT) Received: from web21008.mail.yahoo.com (web21008.mail.yahoo.com [216.136.227.62]) by mx1.FreeBSD.org (Postfix) with SMTP id A6F9B43FA3 for ; Sat, 19 Jul 2003 05:30:49 -0700 (PDT) (envelope-from vovanvinh2001@yahoo.com) Message-ID: <20030719123049.82835.qmail@web21008.mail.yahoo.com> Received: from [203.162.5.197] by web21008.mail.yahoo.com via HTTP; Sat, 19 Jul 2003 05:30:49 PDT Date: Sat, 19 Jul 2003 05:30:49 -0700 (PDT) From: Van Vinh Vo To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: accept filters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 12:30:50 -0000 Hello all, I read the notation of accept filter from google, but i don't well understand, this text as following "Versions of FreeBSD from August 2000 onwards include a feature called "accept filters" which delay the return from accept() until a condition has been met, e.g. an HTTP request has arrived. This postpones the requirement for a child process to handle the new connection which therefore increases the number of connections that a given number of child processes can handle. It also allows a child process to accomplish more immediately after accept() returns (because the request is already available to be read) so there is less context switching. Accept filters provide the most benefit on servers that are already so busy that they are configured with "KeepAlive Off". HTTP KeepAlive (aka persistent connections) avoids the cost of setting up a new connection for every request, but connections that are being kept alive use up one of the available child processes. Since there is a limited number of child processes this can significantly reduce the capacity of the server. The viewers of a web site will still get a lot of the benefit of persistent connections even with a very small KeepAliveTimeout so you should try reducing it before turning it off altogether." from http://httpd.apache.org/docs/misc/perf-bsd44.html "accept filter delays the return from accept() until a condition has been met " does it mean that it delays the connection of sockct when the system is processing others instructions ? "it allows a process to accomplish more immediately after accept() returns ! what does it mean ? " does it mean that when a process is rruning, the system receive a connexion, it delay this connexion and continue running this process, after that it accept the connexion ! and how can we configure this accept filters ? please explain me Thanks for your helping Vinh __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From owner-freebsd-net@FreeBSD.ORG Sat Jul 19 09:48:50 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1334637B401; Sat, 19 Jul 2003 09:48:50 -0700 (PDT) Received: from cheer.mahoroba.org (flets19-022.kamome.or.jp [218.45.19.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EEE743F75; Sat, 19 Jul 2003 09:48:48 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from lyrics.mahoroba.org (IDENT:vHANt+xGY7fuGyHyEU7kPzdH0lvy/UGfJvgq3Jb05Jykp5fj+qB84VK6weD8Bla3@lyrics.mahoroba.org [IPv6:3ffe:501:185b:8010:280:88ff:fe03:4841]) (user=ume mech=CRAM-MD5 bits=0)h6JGmeRM083796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 Jul 2003 01:48:43 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 20 Jul 2003 01:48:39 +0900 Message-ID: From: Hajimu UMEMOTO To: volf@oasis.IAEhv.nl (Frank Volf) In-Reply-To: <20030716141550.7F8BEFDFA@mail.voor.deze.org> References: <20030716141550.7F8BEFDFA@mail.voor.deze.org> User-Agent: xcite1.38> Wanderlust/2.11.3 (Wonderwall) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.3 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 5.1-CURRENT MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=-2.5 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-net@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Reproducable panic with multicast on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 16:48:50 -0000 Hi, >>>>> On Wed, 16 Jul 2003 16:15:50 +0200 (CEST) >>>>> Frank Volf said: volf> Hideki ONO wrote: > Try my patch which I posted to freebsd-bugs last month. > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-June/001407.html volf> Indeed this fixes my problem as well! volf> I hope it will be integrated into the CVS tree soon. I've just committed it into 5-CURRENT. I'll do MFC ater 1 week. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-net@FreeBSD.ORG Sat Jul 19 12:17:39 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10F2837B401 for ; Sat, 19 Jul 2003 12:17:39 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B5F943F75 for ; Sat, 19 Jul 2003 12:17:38 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 74778 invoked from network); 19 Jul 2003 19:17:37 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 19 Jul 2003 19:17:37 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sat, 19 Jul 2003 14:17:10 -0500 (CDT) From: Mike Silbersack To: Van Vinh Vo In-Reply-To: <20030719123049.82835.qmail@web21008.mail.yahoo.com> Message-ID: <20030719141533.S4358@odysseus.silby.com> References: <20030719123049.82835.qmail@web21008.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: accept filters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 19:17:39 -0000 On Sat, 19 Jul 2003, Van Vinh Vo wrote: > does it mean that it delays the connection of sockct > when the system is processing others instructions ? > > does it mean that when a process is rruning, the > system receive a connexion, it delay this connexion > and continue running this process, after that it > accept the connexion ! > > and how can we configure this accept filters ? > > please explain me > > Thanks for your helping > Vinh man accept_filter and the two accf_* pages it references, and read the source code. You will learn much more by doing those two things than by us explaining the implementation to you. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Sat Jul 19 12:19:36 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 082DE37B401; Sat, 19 Jul 2003 12:19:36 -0700 (PDT) Received: from mail.voor.deze.org (a177167.upc-a.chello.nl [62.163.177.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FDE043F3F; Sat, 19 Jul 2003 12:19:34 -0700 (PDT) (envelope-from volf@oasis.IAEhv.nl) Received: by mail.voor.deze.org (Postfix, from userid 226) id EDE83FDFA; Sat, 19 Jul 2003 21:19:32 +0200 (CEST) In-Reply-To: To: Hajimu UMEMOTO Date: Sat, 19 Jul 2003 21:19:32 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20030719191932.EDE83FDFA@mail.voor.deze.org> From: volf@oasis.IAEhv.nl (Frank Volf) cc: freebsd-net@freebsd.org cc: freebsd-stable@freebsd.org cc: Frank Volf Subject: Re: Reproducable panic with multicast on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 19:19:36 -0000 Hi, Thank you very much! Since, I have confirmed that it works on FreeBSD 4.8 you are welcome to close my problem report kern/54314 as soon as the merge has been completed. Frank Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Wed, 16 Jul 2003 16:15:50 +0200 (CEST) > >>>>> Frank Volf said: > > volf> Hideki ONO wrote: > > Try my patch which I posted to freebsd-bugs last month. > > > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-June/001407.html > > volf> Indeed this fixes my problem as well! > volf> I hope it will be integrated into the CVS tree soon. > > I've just committed it into 5-CURRENT. I'll do MFC ater 1 week. > > Sincerely, > > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org > http://www.imasy.org/~ume/ >