From owner-freebsd-net Sun Feb 11 1:55:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C65DF37B401; Sun, 11 Feb 2001 01:55:16 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1B9tGn18831; Sun, 11 Feb 2001 01:55:16 -0800 (PST) Date: Sun, 11 Feb 2001 01:55:16 -0800 From: Alfred Perlstein To: net@freebsd.org Cc: jlemon@freebsd.org Subject: somaxconn and foot removal Message-ID: <20010211015516.J3274@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The sysctl for somaxconn is an int, however the queue limits in the socket structures are 'short' this can cause some bad behavior if one sets somaxconn to more than 32k. A) So, do we bump the sockets to use 'int' for so->so_qlimit? B) Do we fix solisten() to compensate? C) Or de we fix the sysctl (patch below)? I have patches for A and C. (untested patch for A) Index: socketvar.h =================================================================== RCS file: /home/ncvs/src/sys/sys/socketvar.h,v retrieving revision 1.55 diff -u -r1.55 socketvar.h --- socketvar.h 2001/01/09 04:33:49 1.55 +++ socketvar.h 2001/02/11 09:52:58 @@ -31,7 +31,7 @@ * SUCH DAMAGE. * * @(#)socketvar.h 8.3 (Berkeley) 2/19/95 - * $FreeBSD: src/sys/sys/socketvar.h,v 1.55 2001/01/09 04:33:49 wollman Exp $ + * $FreeBSD: src/sys/sys/socketvar.h,v 1.54 2000/12/31 10:23:24 phk Exp $ */ #ifndef _SYS_SOCKETVAR_H_ @@ -73,10 +73,10 @@ TAILQ_HEAD(, socket) so_incomp; /* queue of partial unaccepted connections */ TAILQ_HEAD(, socket) so_comp; /* queue of complete unaccepted connections */ TAILQ_ENTRY(socket) so_list; /* list of unaccepted connections */ - short so_qlen; /* number of unaccepted connections */ - short so_incqlen; /* number of unaccepted incomplete + int so_qlen; /* number of unaccepted connections */ + int so_incqlen; /* number of unaccepted incomplete connections */ - short so_qlimit; /* max number queued connections */ + int so_qlimit; /* max number queued connections */ short so_timeo; /* connection timeout */ u_short so_error; /* error affecting connection */ struct sigio *so_sigio; /* information for async I/O or @@ -153,9 +153,9 @@ caddr_t so_pcb; /* another convenient handle */ int xso_protocol; int xso_family; - short so_qlen; - short so_incqlen; - short so_qlimit; + int so_qlen; + int so_incqlen; + int so_qlimit; short so_timeo; u_short so_error; pid_t so_pgid; C) Index: uipc_socket.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.87 diff -u -r1.87 uipc_socket.c --- uipc_socket.c 2001/01/21 22:23:10 1.87 +++ uipc_socket.c 2001/02/11 09:41:56 @@ -89,8 +89,31 @@ SYSCTL_DECL(_kern_ipc); static int somaxconn = SOMAXCONN; -SYSCTL_INT(_kern_ipc, KIPC_SOMAXCONN, somaxconn, CTLFLAG_RW, - &somaxconn, 0, "Maximum pending socket connection queue size"); + +/* + * since sockets have a short for queue len, don't allow + * sysadmins to outsmart themselves and overflow somaxconn + */ +static int +sysctl_handle_somaxconn(SYSCTL_HANDLER_ARGS) +{ + int error, newval; + short trunc; + + newval = somaxconn; + error = sysctl_handle_int(oidp, &newval, sizeof(newval), req); + if (error == 0 && req->newptr != NULL) { + trunc = newval; + if (trunc <= 0) + return (EINVAL); + somaxconn = newval; + } + return (error); +} + +SYSCTL_PROC(_kern_ipc, KIPC_SOMAXCONN, somaxconn, CTLFLAG_RW, + 0, sizeof(somaxconn), sysctl_handle_somaxconn, "I", + "Maximum pending socket connection queue size"); /* * Socket operation routines. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 2: 0: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4F2B837B401; Sun, 11 Feb 2001 01:59:49 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1B9xnA18904; Sun, 11 Feb 2001 01:59:49 -0800 (PST) Date: Sun, 11 Feb 2001 01:59:49 -0800 From: Alfred Perlstein To: net@FreeBSD.ORG Cc: jlemon@FreeBSD.ORG Subject: Re: somaxconn and foot removal Message-ID: <20010211015949.K3274@fw.wintelcom.net> References: <20010211015516.J3274@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010211015516.J3274@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Feb 11, 2001 at 01:55:16AM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Alfred Perlstein [010211 01:55] wrote: > The sysctl for somaxconn is an int, however the queue limits in the > socket structures are 'short' this can cause some bad behavior if > one sets somaxconn to more than 32k. > > A) So, do we bump the sockets to use 'int' for so->so_qlimit? > B) Do we fix solisten() to compensate? > C) Or de we fix the sysctl (patch below)? > > I have patches for A and C. Also note that I'd like to MFC this shortly which is why i'm a bit worried about mucking with socket/xsocket. I could use A for -current and C for -stable though. Let me know what sounds the best, also for C should I log(LOG_NOTICE or something? EINVAL is a bit cryptic. > (untested patch for A) > Index: socketvar.h > =================================================================== > RCS file: /home/ncvs/src/sys/sys/socketvar.h,v > retrieving revision 1.55 > diff -u -r1.55 socketvar.h -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 5:30:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 7548337B401; Sun, 11 Feb 2001 05:30:19 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f1BDUGU36650; Sun, 11 Feb 2001 05:30:16 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102111330.f1BDUGU36650@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alfred Perlstein Cc: net@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: somaxconn and foot removal In-Reply-To: <20010211015949.K3274@fw.wintelcom.net> Date: Sun, 11 Feb 2001 05:30:16 -0800 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein wrote: > * Alfred Perlstein [010211 01:55] wrote: > > The sysctl for somaxconn is an int, however the queue limits in the > > socket structures are 'short' this can cause some bad behavior if > > one sets somaxconn to more than 32k. > > > > A) So, do we bump the sockets to use 'int' for so->so_qlimit? > > B) Do we fix solisten() to compensate? > > C) Or de we fix the sysctl (patch below)? > > > > I have patches for A and C. > > Also note that I'd like to MFC this shortly which is why i'm a bit > worried about mucking with socket/xsocket. I could use A for -current > and C for -stable though. Let me know what sounds the best, also > for C should I log(LOG_NOTICE or something? EINVAL is a bit cryptic. For what it's worth, we found (at Yahoo) that excessively large listen queues tend to cause more problems than they solve. The circumstances are probably different, but we found that on one particular application, a queue of 10 was better than the queue of 1024 that they had been using. This particular application is probably quite different to yours, but we found that it was generally bad to accept more than about a second or two's worth of connections. ie: this particular group of systems were processing 7-8 connections per second, so a queue depth of 1024 was about 140 seconds. Most of them would time out when they waited that long (30 or 60 second protocol timeout) so when the machine was overloaded and backing up, it was being made worse by accepting all these connections, doing processing to get them in the listen queue, then timing out. What we ended up with was a LOT of races where sockets would get to the head of the queue right as the remote was in the process of initiating a timeout, so we got large numbers of 'connection reset by peer' type problems being reported by accept and getsockname()/getpeername() etc. It was also bad because the userland app then wasted time processing a dying connection, thus contributing further to the overload. Anyway, just be careful, ok? larger listen queues are not a magic solution for all problems. At 100 connections per second, the current limit is about 327 seconds worth of delay. at 500 per second, it is 65 seconds delay. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 10:29: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id EC15F37B401; Sun, 11 Feb 2001 10:29:00 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA09777; Sun, 11 Feb 2001 13:28:52 -0500 (EST) (envelope-from wollman) Date: Sun, 11 Feb 2001 13:28:52 -0500 (EST) From: Garrett Wollman Message-Id: <200102111828.NAA09777@khavrinen.lcs.mit.edu> To: Alfred Perlstein Cc: net@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: somaxconn and foot removal In-Reply-To: <20010211015516.J3274@fw.wintelcom.net> References: <20010211015516.J3274@fw.wintelcom.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > A) So, do we bump the sockets to use 'int' for so->so_qlimit? Make it be `u_short'. (Actually, I'm not sure why all three of those members aren't unsigned. It would make more sense that way.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 10:50:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AF06B37B491; Sun, 11 Feb 2001 10:50:30 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1BIoRZ01014; Sun, 11 Feb 2001 10:50:27 -0800 (PST) Date: Sun, 11 Feb 2001 10:50:27 -0800 From: Alfred Perlstein To: Garrett Wollman Cc: net@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: somaxconn and foot removal Message-ID: <20010211105027.P3274@fw.wintelcom.net> References: <20010211015516.J3274@fw.wintelcom.net> <200102111828.NAA09777@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102111828.NAA09777@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Sun, Feb 11, 2001 at 01:28:52PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Garrett Wollman [010211 10:29] wrote: > < said: > > > A) So, do we bump the sockets to use 'int' for so->so_qlimit? > > Make it be `u_short'. (Actually, I'm not sure why all three of those > members aren't unsigned. It would make more sense that way.) This still gives misleading results from sysctl, ie sysctl allows setting to 65539 which results in a real somaxconn of 3. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 13:23:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 7B4D537B491 for ; Sun, 11 Feb 2001 13:23:36 -0800 (PST) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust224.tnt19.rtm1.nl.uu.net [213.116.132.224] with SMTP for id WAA28160 (8.8.8/1.3); Sun, 11 Feb 2001 22:23:35 +0100 (MET) Reply-To: From: "Peter Blok" To: Subject: netgraph-mpd Date: Sun, 11 Feb 2001 22:21:56 +0100 Message-ID: <000201c09470$a9f222c0$8a00a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, My DSL provider (KPN - mxstream) needs a PPTP connection. I am trying to use netgraph-mpd to make this work. Any experience good or bad with this? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 15: 2:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (10dyn30.dh.casema.net [212.64.31.30]) by hub.freebsd.org (Postfix) with ESMTP id DC20E37B491 for ; Sun, 11 Feb 2001 15:02:09 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.2/8.11.1) with ESMTP id f1BNPMo23593 for ; Mon, 12 Feb 2001 00:25:24 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010212000150.00adec60@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 12 Feb 2001 00:01:58 +0100 To: freebsd-net@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: call for testers: port aggregation netgraph module Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I actually tried to set the ports on the 3COM switch up as trunk > > ports, it didn't work right. Maybe 3COM is doing something entirely > > different. >Prolly. FEC is cisco-specific thingy, like ISL... There's a IEEE standard these days for link aggregation. 802.3AD if I'm not mistaken. When my workload at work lightens up I'll be spending time on this. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 16:56:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id A637A37B401 for ; Sun, 11 Feb 2001 16:56:53 -0800 (PST) Received: from xor.obsecurity.org ([63.207.60.67]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G8M00KDMD517X@mta6.snfc21.pbi.net> for net@freebsd.org; Sun, 11 Feb 2001 16:53:25 -0800 (PST) Received: by xor.obsecurity.org (Postfix, from userid 1000) id 8BA4E66B32; Sun, 11 Feb 2001 16:56:12 -0800 (PST) Date: Sun, 11 Feb 2001 16:56:12 -0800 From: Kris Kennaway Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-reply-to: <20010208123239.P650@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Thu, Feb 08, 2001 at 12:32:39PM -0600 To: Jonathan Lemon Cc: Archie Cobbs , net@freebsd.org Message-id: <20010211165612.A3148@mollari.cthul.hu> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200102081701.f18H1Vp17229@prism.flugsvamp.com> <200102081812.KAA56568@curve.dellroad.org> <20010208123239.P650@prism.flugsvamp.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Did you guys agree on a commit-worthy fix yet? Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6hzSsWry0BWjoQKURAtjPAKDko0n40etHmlXm+HlciJIr5bfPSQCfceu7 ISH5b7W1fUoNK6AQiyDiPNU= =WjVG -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 18:17:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id A24AD37B491; Sun, 11 Feb 2001 18:17:45 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA85245; Sun, 11 Feb 2001 18:17:45 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id SAA68930; Sun, 11 Feb 2001 18:17:44 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102120217.SAA68930@curve.dellroad.org> Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: <20010208212509.E8D7D37B6AA@hub.freebsd.org> "from Bill Paul at Feb 8, 2001 01:25:09 pm" To: Bill Paul Date: Sun, 11 Feb 2001 18:17:44 -0800 (PST) Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Paul writes: > http://www.freebsd.org/~wpaul/FEC/4.x/fec.tar.gz > http://www.freebsd.org/~wpaul/FEC/5.x/fec.tar.gz > > This is a call for testers for a netgraph module that can be used to > aggregate 2 or 4 ethernet interfaces into a single interface. Basically, > it lets you do things like the following: > > # kldload ./ng_fec.ko > # ngctl mkpeer fec dummy fec > # ngctl msg fec0: add_iface '"dc0"' > # ngctl msg fec0: add_iface '"dc1"' > # ngctl msg fec0: add_iface '"dc2"' > # ngctl msg fec0: add_iface '"dc3"' > # ngctl msg fec0: set_mode_inet Bill, Just curious.. did you consider adding this functionality to the ng_one2many(4) node type? I suppose the ifmedia would have to be done more indirectly, eg., by adding a new control message supporting it to ng_ether(4). -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 18:33:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 13EC837B401 for ; Sun, 11 Feb 2001 18:33:23 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA85323; Sun, 11 Feb 2001 18:33:22 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id SAA68980; Sun, 11 Feb 2001 18:33:20 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102120233.SAA68980@curve.dellroad.org> Subject: Re: pptp (mpd-netgraph) through a firewall In-Reply-To: "from Dan Larsson at Feb 9, 2001 12:30:39 pm" To: Dan Larsson Date: Sun, 11 Feb 2001 18:33:20 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dan Larsson writes: > Are the following ipfw lines sufficent to allow pptp?: > > ${fwcmd} add pass tcp from any to any established > ${fwcmd} add pass tcp from any to ${EXT_IF} pptp setup > ${fwcmd} add pass gre from any to any Yes, should be. In any case you can always tell if it's not by using "ipfw log" rules. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 18:34:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id C09BA37B401 for ; Sun, 11 Feb 2001 18:34:11 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA85330; Sun, 11 Feb 2001 18:34:11 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id SAA68990; Sun, 11 Feb 2001 18:34:07 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102120234.SAA68990@curve.dellroad.org> Subject: Re: pptp server In-Reply-To: "from Olivier Cherrier at Feb 8, 2001 08:20:35 pm" To: Olivier Cherrier Date: Sun, 11 Feb 2001 18:34:07 -0800 (PST) Cc: "'freebsd-net'" X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Olivier Cherrier writes: > >It should work with all Windows clients as long as they don't > >require MS-CHAP version 2 authentication. > > Yes, it works. > It works fine. > But there is no encryption of data between MPD and windows clients... When I > do some work in a such connection, I can read data with a tcpdump ... You should be able to do MPPE, assuming everything is properly configured. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 18:56:15 2001 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id F37C937B401; Sun, 11 Feb 2001 18:56:10 -0800 (PST) Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: <200102120217.SAA68930@curve.dellroad.org> from Archie Cobbs at "Feb 11, 2001 06:17:44 pm" To: archie@dellroad.org (Archie Cobbs) Date: Sun, 11 Feb 2001 18:56:10 -0800 (PST) Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG 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: <20010212025610.F37C937B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Bill Paul writes: > > http://www.freebsd.org/~wpaul/FEC/4.x/fec.tar.gz > > http://www.freebsd.org/~wpaul/FEC/5.x/fec.tar.gz > > > > This is a call for testers for a netgraph module that can be used to > > aggregate 2 or 4 ethernet interfaces into a single interface. Basically, > > it lets you do things like the following: You know, so far I've gotten close to a dozen replies to this e-mail, but none of contain the one thing I really wanted, namely test results. Look. I said this was a call for *testers*. Not kibitzers, not criticizers, not commenters, not lamers -- *testers*. I want you to try out the code and tell me if it works or not, and if not, describe the bugs so I can fix them. I don't want to hear anything else. If your e-mail concerns any other topic, it will be summarily ignored. Got it people? Good. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 21:15:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from taka.swcp.com (taka.swcp.com [198.59.115.12]) by hub.freebsd.org (Postfix) with ESMTP id 2A10937B491 for ; Sun, 11 Feb 2001 21:15:56 -0800 (PST) Received: from argotsoft.com (argotsoft.com [198.59.115.127]) by taka.swcp.com (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id f1C5F2046672 for ; Sun, 11 Feb 2001 22:15:03 -0700 (MST) Received: from rincon (rincon.argotsoft.com [192.168.3.102]) by argotsoft.com (8.9.3/8.8.7) with SMTP id WAA07759 for ; Sun, 11 Feb 2001 22:13:59 -0700 (MST) (envelope-from msommer@argotsoft.com) Message-Id: <3.0.3.32.20010211221423.00a5db40@mail> X-Sender: msommer@mail X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 11 Feb 2001 22:14:23 -0700 To: freebsd-net@FreeBSD.ORG From: "Mark J. Sommer" Subject: Re: pptp (mpd-netgraph) through a firewall In-Reply-To: <200102120233.SAA68980@curve.dellroad.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Regarding the rule with "established": doesn't the recent security advisory regarding the established keyword apply here to this IPFW rule? From the advisory: II. Problem Description Due to overloading of the TCP reserved flags field, ipfw and ip6fw incorrectly treat all TCP packets with the ECE flag set as being part of an established TCP connection, which will therefore match a corresponding ipfw rule containing the 'established' qualifier, even if the packet is not part of an established connection. The ECE flag is not believed to be in common use on the Internet at present, but is part of an experimental extension to TCP for congestion notification. At least one other major operating system will emit TCP packets with the ECE flag set under certain operating conditions. Only systems which have enabled ipfw or ip6fw and use a ruleset containing TCP rules which make use of the 'established' qualifier, such as "allow tcp from any to any established", are vulnerable. The exact impact of the vulnerability on such systems is undetermined and depends on the exact ruleset in use. All released versions of FreeBSD prior to the correction date including FreeBSD 3.5.1 and FreeBSD 4.2 are vulnerable, but it was corrected prior to the (future) release of FreeBSD 4.3. At 06:33 PM 2/11/01 -0800, you wrote: >Dan Larsson writes: >> Are the following ipfw lines sufficent to allow pptp?: >> >> ${fwcmd} add pass tcp from any to any established >> ${fwcmd} add pass tcp from any to ${EXT_IF} pptp setup >> ${fwcmd} add pass gre from any to any > >Yes, should be. In any case you can always tell if it's not by >using "ipfw log" rules. > >-Archie > >__________________________________________________________________________ >Archie Cobbs * Packet Design * http://www.packetdesign.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message > > ~Mark -------------------------------------------------------------------------------- Mark J. Sommer ARGOT Software Corporation, P.O. Box 92020, Albuquerque, New Mexico 87199-2020 FAX: 505-771-0274 PHONE: 505-867-6750 E-MAIL: msommer@argotsoft.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 22:16:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id B5AE037B401; Sun, 11 Feb 2001 22:16:13 -0800 (PST) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id OAA13582; Mon, 12 Feb 2001 14:16:10 +0800 Received: from elischer.org (reggae-15-178.nv.iinet.net.au [203.59.74.178]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id OAA23564; Mon, 12 Feb 2001 14:13:33 +0800 Message-ID: <3A877F9C.9641A97F@elischer.org> Date: Sun, 11 Feb 2001 22:15:56 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Bill Paul Cc: Archie Cobbs , hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: call for testers: port aggregation netgraph module References: <20010212025610.F37C937B401@hub.freebsd.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Paul wrote: > > > > You know, so far I've gotten close to a dozen replies to this e-mail, > but none of contain the one thing I really wanted, namely test results. actually I saw one person say it worked flawlessly for them (see mail from: Rainer Clasen ) (working in 4.2) > > Look. I said this was a call for *testers*. Not kibitzers, not criticizers, > not commenters, not lamers -- *testers*. I want you to try out the code > and tell me if it works or not, and if not, describe the bugs so I can > fix them. I don't want to hear anything else. If your e-mail concerns > any other topic, it will be summarily ignored. Got it people? Good. Ok well how about code suggestions from the netgraph writers? Put me in your position.. You are one of the first people to use netgraph so I and interested in hearing results from YOU.. now as for the code.. in the 5.0 version you may add the following code to the ng_fec_free_unit() function.. (you took it from 4.x ng_iface.c but this snippet was added to 5.x) /* * XXX We could think about reducing the size of ng_iface_units[] * XXX here if the last portion is all ones * XXX At least free it if no more units. * Needed if we are to eventually be able to unload. */ ng_units_in_use--; if (ng_units_in_use == 0) { /* XXX make SMP safe */ FREE(ng_iface_units, M_NETGRAPH_IFACE); ng_iface_units_len = 0; ng_iface_units = NULL; } > in 5.x SMP you may have trouble with synchronising the timout callout and normal activity, especially removal of a port. I am still working on the 'right' way to do this, so I'll let you know when I have the 'correct' answer. You have allowed any hooks to be added yet you don't use hooks. (something I have issues with, but hey, it's your node) This is ok except that you will leak mbufs badly if anything is ever sent to the node via a hook you have allowed to be created, because you just accept the packet and then leak it. You should add in the 5.x version: NG_FREE_ITEM(item); and in the 4.x version: NG_FREE_DATA(m, meta); OR alernatively you could NOT DECLARE a rcvdata method (leave it NULL), in which case this will be done automatically. All ethernet class interfaces grow a ng_ether interface automaticaly when ng_ether.c is modloaded, so I would have used and extended that interface to connect to the drivers rather than the way you did. The reason is that it allows arbitrary stacking of protocol elements rather than just a direct version such as you have done. You've used the netgraph infrastructure very well, yet somehow completely avoided the aim of netgraph which is to allow objects to be connected together in arbitrary fashion. You've got the 'net' but completely closed off the 'graph' part.. I would have added some control messages to the ng_ether class to handle the specific functions needed to do this sort of thing. still what you did works just fine, and with the caveat of the suggestions I made re: leaking mbufs, and synchronisation, I see no real problems > -Bill > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 22:20:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id D50A737B491; Sun, 11 Feb 2001 22:20:15 -0800 (PST) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.9.3/8.9.3) with ESMTP id UAA38620; Sun, 11 Feb 2001 20:19:36 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sun, 11 Feb 2001 20:19:35 -1000 (HST) From: Vincent Poy To: Luigi Rizzo Cc: Masachika ISHIZUKA , , Subject: Re: BRIDGE breaks ARP? In-Reply-To: <200102051155.f15Bt0p20537@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 5 Feb 2001, Luigi Rizzo wrote: > > I cvsuped three hours ago and the same ARP troubles happened. > > can you repeat exactly what the problem was (bridge machine not > responding to ARP requests ?) and what is your exact setup (i > am interested in ipfw config, and the following sysctl vars: > > net.link.ether.bridge > net.link.ether.bridge_ipfw > net.link.ether.bridge_cfg > > so i can try to reproduce the problem locally. I'm not sure if this is related but we're using FreeBSD with a Emerging Technologies T1 card to do ADSL Bridging and ran into a problem where for example, if a bridge group was like... 216.235.44.1 255.255.255.0 All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it nothing in 216.235.44.2 - 254 can see each other. It seems to be they can't see each other if they are in the same subnet. So it seems all machines in the bridge group can see the gateway and the rest of the world but not each other. Is there a way around this? This is with 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 22:26:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 5973E37B491; Sun, 11 Feb 2001 22:26:05 -0800 (PST) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id OAA14774; Mon, 12 Feb 2001 14:26:04 +0800 Received: from elischer.org (reggae-15-178.nv.iinet.net.au [203.59.74.178]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id OAA24252; Mon, 12 Feb 2001 14:23:27 +0800 Message-ID: <3A8781EE.8AEA1351@elischer.org> Date: Sun, 11 Feb 2001 22:25:50 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Bill Paul Cc: Archie Cobbs , hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: call for testers: port aggregation netgraph module References: <20010212025610.F37C937B401@hub.freebsd.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Paul wrote: > one other thing.. In ng_fec.h you have kept the same cookie number as ng_iface which means that messages for these two can be confused. You should use a differnt cookie by tradition we use date -u +'%s' to generate or change the cookie. Since the first 3 commands you have are actually the same as the first 3 commands from ng_iface, you might actually think of using them direct and actually implementing them directly rather than duplicating them. i.e, include ng_iface.h, and accept 'ng_iface' cookies and respond to those commands rather than have them as part of your own set. (this makes an fec interface in some ways a 'sub-class' of the generic interface node type) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 22:31:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6C1AC37B491; Sun, 11 Feb 2001 22:31:54 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1C6VfI74774; Sun, 11 Feb 2001 22:31:41 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102120631.f1C6VfI74774@iguana.aciri.org> Subject: Re: BRIDGE breaks ARP? In-Reply-To: from Vincent Poy at "Feb 11, 2001 8:19:35 pm" To: vince@oahu.WURLDLINK.NET (Vincent Poy) Date: Sun, 11 Feb 2001 22:31:41 -0800 (PST) Cc: rizzo@aciri.org, ishizuka@ish.org, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pardon me, but what bridging code are you using ? Is it from Etinc or it is the std FreeBSD bridging code ? luigi > > I'm not sure if this is related but we're using FreeBSD with a > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > where for example, if a bridge group was like... > > 216.235.44.1 255.255.255.0 > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > can't see each other if they are in the same subnet. So it seems all > machines in the bridge group can see the gateway and the rest of the > world but not each other. Is there a way around this? This is with > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > Cheers, > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > WurldLink Corporation / / / / | / | __] ] > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 22:37:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id BC08137B401; Sun, 11 Feb 2001 22:37:08 -0800 (PST) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.9.3/8.9.3) with ESMTP id UAA40469; Sun, 11 Feb 2001 20:36:50 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sun, 11 Feb 2001 20:36:50 -1000 (HST) From: Vincent Poy To: Luigi Rizzo Cc: , , Subject: Re: BRIDGE breaks ARP? In-Reply-To: <200102120631.f1C6VfI74774@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 11 Feb 2001, Luigi Rizzo wrote: > Pardon me, but what bridging code are you using ? Is it from Etinc > or it is the std FreeBSD bridging code ? I'm not sure if the bridging code is from ET or if it's the standard FreeBSD but it seems to be standard FreeBSD bridging code. root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 bg0: flags=8843 mtu 1500 inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 ether 00:00:00:03:00:00 I've asked Dennis at ETinc the question and his response was: if you want to route from one DLCI to the other then you have to put them in separate bridge groups with their own subnet. You are creating isolated segments with the ipmap functionality...the mechanism is designed for end users who get 1 or 2 addresses. You COULD fix the O/S to route back to the same interface, but I dont know how complicated that would be. I dont think there is an easy way to disable split-horizon. Dennis Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > I'm not sure if this is related but we're using FreeBSD with a > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > where for example, if a bridge group was like... > > > > 216.235.44.1 255.255.255.0 > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > can't see each other if they are in the same subnet. So it seems all > > machines in the bridge group can see the gateway and the rest of the > > world but not each other. Is there a way around this? This is with > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > Cheers, > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > WurldLink Corporation / / / / | / | __] ] > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 22:40:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6E4DE37B491; Sun, 11 Feb 2001 22:40:14 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1C6e4R76338; Sun, 11 Feb 2001 22:40:04 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102120640.f1C6e4R76338@iguana.aciri.org> Subject: Re: BRIDGE breaks ARP? In-Reply-To: from Vincent Poy at "Feb 11, 2001 8:36:50 pm" To: vince@oahu.WURLDLINK.NET (Vincent Poy) Date: Sun, 11 Feb 2001 22:40:04 -0800 (PST) Cc: rizzo@aciri.org, ishizuka@ish.org, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 11 Feb 2001, Luigi Rizzo wrote: > > > Pardon me, but what bridging code are you using ? Is it from Etinc > > or it is the std FreeBSD bridging code ? > > I'm not sure if the bridging code is from ET or if it's the > standard FreeBSD but it seems to be standard FreeBSD bridging code. the output from /var/log/dmesg.boot should clarify this. cheers luigi > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > bg0: flags=8843 mtu 1500 > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > ether 00:00:00:03:00:00 > > I've asked Dennis at ETinc the question and his response was: > > if you want to route from one DLCI to the other then you have to put them > in separate bridge groups with their own subnet. You are creating isolated > segments with the ipmap functionality...the mechanism is designed for end > users who get 1 or 2 addresses. > > You COULD fix the O/S to route back to the same interface, but I dont know > how complicated that would be. I dont think there is an easy way to > disable > split-horizon. > > Dennis > > > Cheers, > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > WurldLink Corporation / / / / | / | __] ] > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > where for example, if a bridge group was like... > > > > > > 216.235.44.1 255.255.255.0 > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > can't see each other if they are in the same subnet. So it seems all > > > machines in the bridge group can see the gateway and the rest of the > > > world but not each other. Is there a way around this? This is with > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > Cheers, > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > WurldLink Corporation / / / / | / | __] ] > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 23:39:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 7960937B401; Sun, 11 Feb 2001 23:38:58 -0800 (PST) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.9.3/8.9.3) with ESMTP id VAA05857; Sun, 11 Feb 2001 21:38:38 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sun, 11 Feb 2001 21:38:38 -1000 (HST) From: Vincent Poy To: Luigi Rizzo Cc: , , Subject: Re: BRIDGE breaks ARP? In-Reply-To: <200102120640.f1C6e4R76338@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 11 Feb 2001, Luigi Rizzo wrote: > > On Sun, 11 Feb 2001, Luigi Rizzo wrote: > > > > > Pardon me, but what bridging code are you using ? Is it from Etinc > > > or it is the std FreeBSD bridging code ? > > > > I'm not sure if the bridging code is from ET or if it's the > > standard FreeBSD but it seems to be standard FreeBSD bridging code. > > the output from /var/log/dmesg.boot should clarify this. I don't have a dmesg.boot, only a dmesg.yesterday and dmesg.today. What specifically should I be looking for? Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > > bg0: flags=8843 mtu 1500 > > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > > ether 00:00:00:03:00:00 > > > > I've asked Dennis at ETinc the question and his response was: > > > > if you want to route from one DLCI to the other then you have to put them > > in separate bridge groups with their own subnet. You are creating isolated > > segments with the ipmap functionality...the mechanism is designed for end > > users who get 1 or 2 addresses. > > > > You COULD fix the O/S to route back to the same interface, but I dont know > > how complicated that would be. I dont think there is an easy way to > > disable > > split-horizon. > > > > Dennis > > > > > > Cheers, > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > WurldLink Corporation / / / / | / | __] ] > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > > where for example, if a bridge group was like... > > > > > > > > 216.235.44.1 255.255.255.0 > > > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > > can't see each other if they are in the same subnet. So it seems all > > > > machines in the bridge group can see the gateway and the rest of the > > > > world but not each other. Is there a way around this? This is with > > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > > > > Cheers, > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > WurldLink Corporation / / / / | / | __] ] > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Feb 11 23:45:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 9F4C737B401; Sun, 11 Feb 2001 23:45:47 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1C7jXN84390; Sun, 11 Feb 2001 23:45:33 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102120745.f1C7jXN84390@iguana.aciri.org> Subject: Re: BRIDGE breaks ARP? In-Reply-To: from Vincent Poy at "Feb 11, 2001 9:38:38 pm" To: vince@oahu.WURLDLINK.NET (Vincent Poy) Date: Sun, 11 Feb 2001 23:45:33 -0800 (PST) Cc: rizzo@aciri.org, ishizuka@ish.org, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I don't have a dmesg.boot, only a dmesg.yesterday and dmesg.today. > What specifically should I be looking for? whether or not you have "options BRIDGE' in your kernel config file. (or a message saying "BRIDGE ..." when the system boots) luigi > > Cheers, > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > WurldLink Corporation / / / / | / | __] ] > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > > > bg0: flags=8843 mtu 1500 > > > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > > > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > > > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > > > ether 00:00:00:03:00:00 > > > > > > I've asked Dennis at ETinc the question and his response was: > > > > > > if you want to route from one DLCI to the other then you have to put them > > > in separate bridge groups with their own subnet. You are creating isolated > > > segments with the ipmap functionality...the mechanism is designed for end > > > users who get 1 or 2 addresses. > > > > > > You COULD fix the O/S to route back to the same interface, but I dont know > > > how complicated that would be. I dont think there is an easy way to > > > disable > > > split-horizon. > > > > > > Dennis > > > > > > > > > Cheers, > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > WurldLink Corporation / / / / | / | __] ] > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > > > where for example, if a bridge group was like... > > > > > > > > > > 216.235.44.1 255.255.255.0 > > > > > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > > > can't see each other if they are in the same subnet. So it seems all > > > > > machines in the bridge group can see the gateway and the rest of the > > > > > world but not each other. Is there a way around this? This is with > > > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > > > > > > > Cheers, > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 0:23:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 44CD137B491; Mon, 12 Feb 2001 00:23:20 -0800 (PST) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.9.3/8.9.3) with ESMTP id WAA11515; Sun, 11 Feb 2001 22:23:07 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sun, 11 Feb 2001 22:23:07 -1000 (HST) From: Vincent Poy To: Luigi Rizzo Cc: , , Subject: Re: BRIDGE breaks ARP? In-Reply-To: <200102120745.f1C7jXN84390@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 11 Feb 2001, Luigi Rizzo wrote: > > I don't have a dmesg.boot, only a dmesg.yesterday and dmesg.today. > > What specifically should I be looking for? > > whether or not you have "options BRIDGE' in your kernel config file. > (or a message saying "BRIDGE ..." when the system boots) My kernel config doesn't have the BRIDGE option so I guess the bridging code is part of ET's drivers. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > > > > bg0: flags=8843 mtu 1500 > > > > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > > > > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > > > > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > > > > ether 00:00:00:03:00:00 > > > > > > > > I've asked Dennis at ETinc the question and his response was: > > > > > > > > if you want to route from one DLCI to the other then you have to put them > > > > in separate bridge groups with their own subnet. You are creating isolated > > > > segments with the ipmap functionality...the mechanism is designed for end > > > > users who get 1 or 2 addresses. > > > > > > > > You COULD fix the O/S to route back to the same interface, but I dont know > > > > how complicated that would be. I dont think there is an easy way to > > > > disable > > > > split-horizon. > > > > > > > > Dennis > > > > > > > > > > > > Cheers, > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > WurldLink Corporation / / / / | / | __] ] > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > > > > where for example, if a bridge group was like... > > > > > > > > > > > > 216.235.44.1 255.255.255.0 > > > > > > > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > > > > can't see each other if they are in the same subnet. So it seems all > > > > > > machines in the bridge group can see the gateway and the rest of the > > > > > > world but not each other. Is there a way around this? This is with > > > > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 0:25:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id C1F0137B491; Mon, 12 Feb 2001 00:25:31 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1C8PLH84645; Mon, 12 Feb 2001 00:25:21 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102120825.f1C8PLH84645@iguana.aciri.org> Subject: Re: BRIDGE breaks ARP? In-Reply-To: from Vincent Poy at "Feb 11, 2001 10:23: 7 pm" To: vince@oahu.WURLDLINK.NET (Vincent Poy) Date: Mon, 12 Feb 2001 00:25:21 -0800 (PST) Cc: rizzo@aciri.org, ishizuka@ish.org, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > whether or not you have "options BRIDGE' in your kernel config file. > > (or a message saying "BRIDGE ..." when the system boots) > > My kernel config doesn't have the BRIDGE option so I guess the > bridging code is part of ET's drivers. yes, i suspected so... luigi > > Cheers, > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > WurldLink Corporation / / / / | / | __] ] > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > > > > > bg0: flags=8843 mtu 1500 > > > > > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > > > > > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > > > > > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > > > > > ether 00:00:00:03:00:00 > > > > > > > > > > I've asked Dennis at ETinc the question and his response was: > > > > > > > > > > if you want to route from one DLCI to the other then you have to put them > > > > > in separate bridge groups with their own subnet. You are creating isolated > > > > > segments with the ipmap functionality...the mechanism is designed for end > > > > > users who get 1 or 2 addresses. > > > > > > > > > > You COULD fix the O/S to route back to the same interface, but I dont know > > > > > how complicated that would be. I dont think there is an easy way to > > > > > disable > > > > > split-horizon. > > > > > > > > > > Dennis > > > > > > > > > > > > > > > Cheers, > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > > > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > > > > > where for example, if a bridge group was like... > > > > > > > > > > > > > > 216.235.44.1 255.255.255.0 > > > > > > > > > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > > > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > > > > > can't see each other if they are in the same subnet. So it seems all > > > > > > > machines in the bridge group can see the gateway and the rest of the > > > > > > > world but not each other. Is there a way around this? This is with > > > > > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 0:28:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 82F5237B401; Mon, 12 Feb 2001 00:28:15 -0800 (PST) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.9.3/8.9.3) with ESMTP id WAA11585; Sun, 11 Feb 2001 22:28:01 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sun, 11 Feb 2001 22:28:01 -1000 (HST) From: Vincent Poy To: Luigi Rizzo Cc: , , Subject: Re: BRIDGE breaks ARP? In-Reply-To: <200102120825.f1C8PLH84645@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Feb 2001, Luigi Rizzo wrote: > > > whether or not you have "options BRIDGE' in your kernel config file. > > > (or a message saying "BRIDGE ..." when the system boots) > > > > My kernel config doesn't have the BRIDGE option so I guess the > > bridging code is part of ET's drivers. > > yes, i suspected so... Thanks Luigi for confirming it isn't FreeBSD that's the problem... Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > root@oahu [8:24pm][/usr/temp/zebra] >> ifconfig bg0 > > > > > > bg0: flags=8843 mtu 1500 > > > > > > inet 216.235.44.1 netmask 0xffffff00 broadcast 216.235.44.255 > > > > > > inet 216.235.45.1 netmask 0xffffff00 broadcast 216.235.45.255 > > > > > > inet 216.235.56.193 netmask 0xffffffe0 broadcast 216.235.56.223 > > > > > > ether 00:00:00:03:00:00 > > > > > > > > > > > > I've asked Dennis at ETinc the question and his response was: > > > > > > > > > > > > if you want to route from one DLCI to the other then you have to put them > > > > > > in separate bridge groups with their own subnet. You are creating isolated > > > > > > segments with the ipmap functionality...the mechanism is designed for end > > > > > > users who get 1 or 2 addresses. > > > > > > > > > > > > You COULD fix the O/S to route back to the same interface, but I dont know > > > > > > how complicated that would be. I dont think there is an easy way to > > > > > > disable > > > > > > split-horizon. > > > > > > > > > > > > Dennis > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > I'm not sure if this is related but we're using FreeBSD with a > > > > > > > > Emerging Technologies T1 card to do ADSL Bridging and ran into a problem > > > > > > > > where for example, if a bridge group was like... > > > > > > > > > > > > > > > > 216.235.44.1 255.255.255.0 > > > > > > > > > > > > > > > > All the nodes 216.235.44.2-254 can see 216.235.44.1 fine but it > > > > > > > > nothing in 216.235.44.2 - 254 can see each other. It seems to be they > > > > > > > > can't see each other if they are in the same subnet. So it seems all > > > > > > > > machines in the bridge group can see the gateway and the rest of the > > > > > > > > world but not each other. Is there a way around this? This is with > > > > > > > > 4.1-RELEASE, 4.1.1-RELEASE and even 4.2-RELEASE. > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > > > > > > > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > > > > > > > WurldLink Corporation / / / / | / | __] ] > > > > > > > > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > > > > > > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 6: 9:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1CF9E37B491; Mon, 12 Feb 2001 06:09:32 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Feb 2001 14:09:31 +0000 (GMT) To: Boris Popov Cc: freebsd-arch@freebsd.org, freebsd-net@freebsd.org, iedowse@maths.tcd.ie Subject: Re: CFR: Sequential mbuf read/write extensions In-Reply-To: Your message of "Fri, 09 Feb 2001 08:30:48 +0600." Date: Mon, 12 Feb 2001 14:09:30 +0000 From: Ian Dowse Message-ID: <200102121409.aa34378@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Boris Popo v writes: > No, in the current implementation mb_get* functions will work >properly. But mb_put* will fail. This can be avoided by implementing >alignment-safe set* macros (which can be written in two variants - first >form is for aligned objects and second for bad aligned ones). Ah, I missed the details of how the mb_get functions work - you just perform a byte-by-byte copy into the destination. Great! I wonder if it makes sense to do something similar for the mb_put functions too? BTW, I'd recommend making MB_PUT() a more 'normal' macro, or even calling mb_fit directly from the mb_put functions - the implicit declaration of 'p' and use of 'mbp' is confusing. If mb_fit was changed to return a void *, the code wouldn't look too bad, and would be less magic. e.g.: int mb_put_byte(struct mbdata *mbp, u_int8_t x) { u_int8_t *p; if ((p = mb_fit(mbp, sizeof(*p))) == NULL) return (ENUBUFS); *p = x; return (0); } > Hmm, since so_send() can fail and some erros can be recovered by >another call to so_send(), I'm just called m_copym() to duplicate the mbuf >chain and give it to so_send(). This is reasonable for a client of an RPC-type protocol, but the server side may wish to give the reply to the sosend function and ignore errors - NFS does this for example. It seems natural to call the _init function to clobber any state, though the semantics aren't that important. There just needs to be a defined way of disassociating the chain from the mbdata struct so that mb_done will not free it. If you are going to split struct mbdata into two structs, you can probably optimise operations a bit by storing the right information for each case. For the build case, maybe: struct mbuf *mb_top; /* head of chain */ struct mbuf *mb_cur; /* current (last) mbuf in chain */ int mb_mleft; /* bytes remaining in mb_cur */ int mb_count; /* total bytes in chain */ Storing the number of bytes remaining in the current mbuf as 'mb_mleft' avoids using M_TRAILINGSPACE() which expands to quite a complex expression. The current offset is not explicitly stored in mbdata, but evaluating 'mtod(m, char *) + m->m_len' is cheap. An optimised case at the start of mb_fit could look like m = mbp->mb_cur; if (mbp->mb_top != NULL && size <= mbp->mb_mleft) { mbp->mb_mleft -= size; mbp->mb_count += size; bpos = mtod(m, char *) + m->m_len; m->m_len += size; return (bpos); } but I guess worrying about minor optimisations like these probably isn't too important now :-) For the breakdown, you probably only need: struct mbuf *mb_top; /* head of chain */ struct mbuf *mb_cur; /* current mbuf in chain */ u_char *mb_pos; /* current position in mb_cur */ Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 6:22:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from fat.ti.ru (fat.ti.ru [212.1.224.35]) by hub.freebsd.org (Postfix) with ESMTP id 48E0F37B401 for ; Mon, 12 Feb 2001 06:22:38 -0800 (PST) Received: from martin (hilldale.kurgan.ru [212.1.224.61]) by fat.ti.ru (Postfix) with ESMTP id 21125D92B; Mon, 12 Feb 2001 17:22:34 +0300 (MSK) Date: Mon, 12 Feb 2001 17:22:28 +0300 From: Martin McFlySr X-Mailer: The Bat! (v1.49) Personal Reply-To: Martin McFlySr Organization: Back To The Future X-Priority: 3 (Normal) Message-ID: <136341398034.20010212172228@McFlySr.Kurgan.Ru> To: Peter Blok Cc: net@freebsd.org Subject: Re: netgraph-mpd In-reply-To: <000201c09470$a9f222c0$8a00a8c0@ntpc> References: <000201c09470$a9f222c0$8a00a8c0@ntpc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Peter Blok, Monday, February 12, 2001, 00:21:56, you wrote: PB> My DSL provider (KPN - mxstream) needs a PPTP connection. I am trying to PB> use netgraph-mpd to make this work. Any experience good or bad with this? mpd-netgraph _really_ _good_ software, ...but need some patches. I'm right, Archie? :) -- Monday, February 12, 2001, 17:20 Best regards from future, Martin McFlySr, HillDale. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 6:46:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 6895137B401; Mon, 12 Feb 2001 06:46:22 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1CEkvH89288; Mon, 12 Feb 2001 08:46:57 -0600 (CST) (envelope-from jlemon) Date: Mon, 12 Feb 2001 08:46:57 -0600 From: Jonathan Lemon To: Alfred Perlstein Cc: net@freebsd.org, jlemon@freebsd.org Subject: Re: somaxconn and foot removal Message-ID: <20010212084657.U650@prism.flugsvamp.com> References: <20010211015516.J3274@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010211015516.J3274@fw.wintelcom.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 11, 2001 at 01:55:16AM -0800, Alfred Perlstein wrote: > The sysctl for somaxconn is an int, however the queue limits in the > socket structures are 'short' this can cause some bad behavior if > one sets somaxconn to more than 32k. > > A) So, do we bump the sockets to use 'int' for so->so_qlimit? > B) Do we fix solisten() to compensate? > C) Or de we fix the sysctl (patch below)? I'd patch sysctl. I can't imagine a listen queue > u_short actually being all that useful; at some point it is better to just start shedding load instead of queuing up numerous connections. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 7:47:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from spider.suxx.eu.org (os-kam.cust.kks.net [213.161.4.225]) by hub.freebsd.org (Postfix) with ESMTP id C6F8537B401 for ; Mon, 12 Feb 2001 07:47:06 -0800 (PST) Received: by spider.suxx.eu.org (Postfix, from userid 1000) id 2C4B4179AA; Mon, 12 Feb 2001 16:47:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by spider.suxx.eu.org (Postfix) with ESMTP id 9D2A332BAE for ; Mon, 12 Feb 2001 16:47:00 +0100 (CET) Date: Mon, 12 Feb 2001 16:47:00 +0100 (CET) From: David Delibasic To: freebsd-net@freebsd.org Subject: Bridging question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a question about brigding in FreeBSD: I'm running a server with 3 NICs. I'd like to bridge packets only between two interfaces, while the third one could still be used as interface that is not bridged. Interfaces are: ep0,xl0,de0. Now i'd like to bridge packets only between xl0 and de0, while the interface ep0 can still be used as a uplink interface to cable internet provider. I tried: sysctl -w net.link.ether.bridge_cfg="xl0:0,de0:0," sysctl -w net.net.link.ether.bridge="1" But all my intefaces including ep0 are put into PROMISC mode. How do i fix that ? Best Regards, David > FreeBSD < -- > Power so serve < > Line noise provided by Telekom Slovenia < To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 9: 4:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 2E0FA37B65D for ; Mon, 12 Feb 2001 09:04:12 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1CH3ss88856; Mon, 12 Feb 2001 09:03:54 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102121703.f1CH3ss88856@iguana.aciri.org> Subject: Re: Bridging question In-Reply-To: from David Delibasic at "Feb 12, 2001 4:47: 0 pm" To: maddave@suxx.eu.org (David Delibasic) Date: Mon, 12 Feb 2001 09:03:54 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org the method you suggest should work but you need a recent -stable (as of feb.10 2001) to make it work as expected cheers luigi > > I'm running a server with 3 NICs. I'd like to bridge packets only between > two interfaces, while the third one could still be used as interface that > is not bridged. > > Interfaces are: ep0,xl0,de0. > > Now i'd like to bridge packets only between xl0 and de0, while the > interface ep0 can still be used as a uplink interface to cable internet > provider. > > I tried: > sysctl -w net.link.ether.bridge_cfg="xl0:0,de0:0," > sysctl -w net.net.link.ether.bridge="1" > > But all my intefaces including ep0 are put into PROMISC mode. > > How do i fix that ? > > Best Regards, > David > > > FreeBSD < -- > Power so serve < > > Line noise provided by Telekom Slovenia < > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 9:44:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id CF45A37B491; Mon, 12 Feb 2001 09:44:35 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA90088; Mon, 12 Feb 2001 09:44:35 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id JAA71455; Mon, 12 Feb 2001 09:44:34 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102121744.JAA71455@curve.dellroad.org> Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: <20010212025610.F37C937B401@hub.freebsd.org> "from Bill Paul at Feb 11, 2001 06:56:10 pm" To: Bill Paul Date: Mon, 12 Feb 2001 09:44:34 -0800 (PST) Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Paul writes: > > > This is a call for testers for a netgraph module that can be used to > > > aggregate 2 or 4 ethernet interfaces into a single interface. Basically, > > > it lets you do things like the following: > > You know, so far I've gotten close to a dozen replies to this e-mail, > but none of contain the one thing I really wanted, namely test results. > > Look. I said this was a call for *testers*. Not kibitzers, not criticizers, > not commenters, not lamers -- *testers*. I want you to try out the code > and tell me if it works or not, and if not, describe the bugs so I can > fix them. I don't want to hear anything else. If your e-mail concerns > any other topic, it will be summarily ignored. Got it people? Good. Sorry.. I guess we all simultaneously forgot that you were the center of the universe. What's wrong with a little discussion? If you're not interested in it, that's fine, but can't the rest of us be? -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 9:56:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id F3D8237B503 for ; Mon, 12 Feb 2001 09:56:27 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA90169; Mon, 12 Feb 2001 09:56:26 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id JAA71541; Mon, 12 Feb 2001 09:56:26 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102121756.JAA71541@curve.dellroad.org> Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <20010211165612.A3148@mollari.cthul.hu> "from Kris Kennaway at Feb 11, 2001 04:56:12 pm" To: Kris Kennaway Date: Mon, 12 Feb 2001 09:56:26 -0800 (PST) Cc: Jonathan Lemon , net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kennaway writes: > Did you guys agree on a commit-worthy fix yet? I wasn't party to the issue that generated this thread in the first place, but.. I think the concensus is that if accept(2) returns an error then this will break some applications, so instead it should return a socket which will itself return an error on the first operation. Somebody correct me if I'm wrong. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 10:28:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id E21D637B491 for ; Mon, 12 Feb 2001 10:28:29 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1CISt697030; Mon, 12 Feb 2001 12:28:55 -0600 (CST) (envelope-from jlemon) Date: Mon, 12 Feb 2001 12:28:55 -0600 From: Jonathan Lemon To: Archie Cobbs Cc: Kris Kennaway , Jonathan Lemon , net@freebsd.org Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] Message-ID: <20010212122855.A92213@prism.flugsvamp.com> References: <20010211165612.A3148@mollari.cthul.hu> <200102121756.JAA71541@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200102121756.JAA71541@curve.dellroad.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 12, 2001 at 09:56:26AM -0800, Archie Cobbs wrote: > Kris Kennaway writes: > > Did you guys agree on a commit-worthy fix yet? > > I wasn't party to the issue that generated this thread in the first > place, but.. I think the concensus is that if accept(2) returns > an error then this will break some applications, so instead it > should return a socket which will itself return an error on the > first operation. Somebody correct me if I'm wrong. No, as this is the current behavior. The change will be for accept to return an error, on the basis that 1) most apps already do the wrong thing now anyway, and 2) it brings us closer to a 'standard', e.g.: what other systems are doing as well. I was planning on committing the change soon, but there isn't really any hurry; effectively all it does is change the mechanism of error reporting from one form to another. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 10:52: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D3DC537B491 for ; Mon, 12 Feb 2001 10:52:01 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1CIpws03695; Mon, 12 Feb 2001 10:51:58 -0800 (PST) Date: Mon, 12 Feb 2001 10:51:58 -0800 From: Alfred Perlstein To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: somaxconn and foot removal Message-ID: <20010212105158.B3274@fw.wintelcom.net> References: <20010211015516.J3274@fw.wintelcom.net> <20010212084657.U650@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010212084657.U650@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Mon, Feb 12, 2001 at 08:46:57AM -0600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Jonathan Lemon [010212 06:46] wrote: > On Sun, Feb 11, 2001 at 01:55:16AM -0800, Alfred Perlstein wrote: > > The sysctl for somaxconn is an int, however the queue limits in the > > socket structures are 'short' this can cause some bad behavior if > > one sets somaxconn to more than 32k. > > > > A) So, do we bump the sockets to use 'int' for so->so_qlimit? > > B) Do we fix solisten() to compensate? > > C) Or de we fix the sysctl (patch below)? > > I'd patch sysctl. I can't imagine a listen queue > u_short actually > being all that useful; at some point it is better to just start > shedding load instead of queuing up numerous connections. It's for accept filters, I didn't expect to actually get that many connections however: 1) I shouldn't shoot myself in the foot by dinking this to a 'reasonable' number 2) aren't 16 bit ops more expensive on things like the Alpha? I think I have a generic way to implement a SYSCTL_LIMIT type thing, but it'll be a couple of days before I can present it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 10:53:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 026F637B491; Mon, 12 Feb 2001 10:53:36 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1CIrVn03733; Mon, 12 Feb 2001 10:53:31 -0800 (PST) Date: Mon, 12 Feb 2001 10:53:30 -0800 From: Alfred Perlstein To: Peter Wemm Cc: net@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: somaxconn and foot removal Message-ID: <20010212105330.C3274@fw.wintelcom.net> References: <20010211015949.K3274@fw.wintelcom.net> <200102111330.f1BDUGU36650@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102111330.f1BDUGU36650@mobile.wemm.org>; from peter@netplex.com.au on Sun, Feb 11, 2001 at 05:30:16AM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Peter Wemm [010211 05:30] wrote: > > For what it's worth, we found (at Yahoo) that excessively large listen > queues tend to cause more problems than they solve. The circumstances are > probably different, but we found that on one particular application, a > queue of 10 was better than the queue of 1024 that they had been using. > This particular application is probably quite different to yours, but we > found that it was generally bad to accept more than about a second or two's > worth of connections. ie: this particular group of systems were processing > 7-8 connections per second, so a queue depth of 1024 was about 140 seconds. > Most of them would time out when they waited that long (30 or 60 second > protocol timeout) so when the machine was overloaded and backing up, it was > being made worse by accepting all these connections, doing processing to get > them in the listen queue, then timing out. What we ended up with was a LOT > of races where sockets would get to the head of the queue right as the > remote was in the process of initiating a timeout, so we got large numbers > of 'connection reset by peer' type problems being reported by accept and > getsockname()/getpeername() etc. It was also bad because the userland app > then wasted time processing a dying connection, thus contributing further > to the overload. > > Anyway, just be careful, ok? larger listen queues are not a magic solution > for all problems. At 100 connections per second, the current limit is about > 327 seconds worth of delay. at 500 per second, it is 65 seconds delay. I'm a bit past 500 connections per second. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 11: 2:56 2001 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 2430F37B491; Mon, 12 Feb 2001 11:02:52 -0800 (PST) Subject: Re: call for testers: port aggregation netgraph module (fwd) In-Reply-To: from Robert Watson at "Feb 11, 2001 10:21:40 pm" To: bj@zuto.de Date: Mon, 12 Feb 2001 11:02:52 -0800 (PST) Cc: ticso@cicely.de, net@FreeBSD.ORG 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: <20010212190252.2430F37B491@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Sat, 10 Feb 2001 15:29:17 +0100 > From: Rainer Clasen > To: net@FreeBSD.ORG > Cc: ticso@cicely.de > Subject: Re: call for testers: port aggregation netgraph module > > On Thu, Feb 08, 2001 at 01:25:09PM -0800, Bill Paul wrote: > > http://www.freebsd.org/~wpaul/FEC/4.x/fec.tar.gz > > I've tried this with 4.2-RELEASE on a single PIII-500 with 128 MB RAM and > 2 fxp0 Interfaces. It was attached to a Nortel Baystack 450 running a 2 > port "Multinlink Trunk" Configuration. > > It worked absolutely flawlessly. Ok... > When downloading a single 60MB file to 3 clients by FTP, it achieved > ~21 MB/sek output (netstat -I fec0 -w10). I had to use 3 clients due to > lack of a second speedy client. > > I'm impressed. So am I. > Am I right that a single transfer is always limited to the bandwidth of a > single interface? The above mentioned Switch and Linux ditribute traffic > in a round robbing manner. Both cooperate with Cisco's Etherchannel > (tested against a Catalyst 2924). How about adding a round robbing > distribution, too? This is epecially usefull for getting higher throughput > when traffic mostly takes place between 2 hosts. You are correct in your assumption. The port selection is done by XORing the lower bits of the source and destination addresses in the packet (either MAC address or IP address). So all packets transmitted to a given host will always be sent over the same interface in the bundle (unless it's down, in which case it'll use the next one over). As for using a round-robin distribution... well, the idea behind etherchannel is to distribute the traffic across multiple links while preventing any out-of-order packet transmissions with minimal work. Using a round-robin scheme would require some sort of mechanism to deal with preserving packet ordering. Adding another port selection scheme should be pretty simple as long as somebody can point me at the right algorithm. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 16:51:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 4C2AF37B684 for ; Mon, 12 Feb 2001 16:51:49 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id QAA92368; Mon, 12 Feb 2001 16:51:48 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id QAA72498; Mon, 12 Feb 2001 16:51:48 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102130051.QAA72498@curve.dellroad.org> Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <20010212122855.A92213@prism.flugsvamp.com> "from Jonathan Lemon at Feb 12, 2001 12:28:55 pm" To: Jonathan Lemon Date: Mon, 12 Feb 2001 16:51:48 -0800 (PST) Cc: kris@obsecurity.org, net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonathan Lemon writes: > > > Did you guys agree on a commit-worthy fix yet? > > > > I wasn't party to the issue that generated this thread in the first > > place, but.. I think the concensus is that if accept(2) returns > > an error then this will break some applications, so instead it > > should return a socket which will itself return an error on the > > first operation. Somebody correct me if I'm wrong. > > No, as this is the current behavior. The change will be for accept > to return an error, on the basis that 1) most apps already do the > wrong thing now anyway, and 2) it brings us closer to a 'standard', > e.g.: what other systems are doing as well. I don't understand then. What is the problem with the current behavior? Is this just an optimization or a real bug fix? I'd say it's not worth changing if it's just an optimization, because too many things will break. Several apps have already been pointed out. And what do you mean by ``most apps already do the wrong thing now''? -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 17:20:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 23E3937B491 for ; Mon, 12 Feb 2001 17:20:09 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA06292; Tue, 13 Feb 2001 10:19:43 +0900 (JST) To: Archie Cobbs Cc: Jonathan Lemon , kris@obsecurity.org, net@freebsd.org In-reply-to: archie's message of Mon, 12 Feb 2001 16:51:48 PST. <200102130051.QAA72498@curve.dellroad.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] From: itojun@iijlab.net Date: Tue, 13 Feb 2001 10:19:42 +0900 Message-ID: <6290.982027182@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> No, as this is the current behavior. The change will be for accept >> to return an error, on the basis that 1) most apps already do the >> wrong thing now anyway, and 2) it brings us closer to a 'standard', >> e.g.: what other systems are doing as well. > >I don't understand then. > >What is the problem with the current behavior? Is this just an >optimization or a real bug fix? I'd say it's not worth changing >if it's just an optimization, because too many things will break. >Several apps have already been pointed out. > >And what do you mean by ``most apps already do the wrong thing now''? for background (like when this happens) see previous articles on this thread. current behavior: return 0-length sockaddr. many of the existing applications assumes to get valid sockaddr to the address family of the socket (like sockaddr_in for AF_INET socket). so if they do that, they will access uninitialized memory region, die with assert(), whatever (BIND 9.1.0 dies with assert()). it is rather questionable if the kernel can return 0-length sockaddr, standard-wise, at least for connection-oriented socket. new behavior: return ECONNABORTED. SUSv2 suggests this behavior. it is much safer as accept(2) will fail so almost every application will go to error case (if you don't have error check in userland appication, that's problem in application). itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 17:40:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 1FAD137B4EC for ; Mon, 12 Feb 2001 17:40:34 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1D1ewA11874; Mon, 12 Feb 2001 19:40:58 -0600 (CST) (envelope-from jlemon) Date: Mon, 12 Feb 2001 19:40:58 -0600 From: Jonathan Lemon To: Archie Cobbs Cc: Jonathan Lemon , kris@obsecurity.org, net@freebsd.org Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] Message-ID: <20010212194058.A1479@prism.flugsvamp.com> References: <20010212122855.A92213@prism.flugsvamp.com> <200102130051.QAA72498@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200102130051.QAA72498@curve.dellroad.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 12, 2001 at 04:51:48PM -0800, Archie Cobbs wrote: > Jonathan Lemon writes: > > > > Did you guys agree on a commit-worthy fix yet? > > > > > > I wasn't party to the issue that generated this thread in the first > > > place, but.. I think the concensus is that if accept(2) returns > > > an error then this will break some applications, so instead it > > > should return a socket which will itself return an error on the > > > first operation. Somebody correct me if I'm wrong. > > > > No, as this is the current behavior. The change will be for accept > > to return an error, on the basis that 1) most apps already do the > > wrong thing now anyway, and 2) it brings us closer to a 'standard', > > e.g.: what other systems are doing as well. > > I don't understand then. > > What is the problem with the current behavior? Is this just an > optimization or a real bug fix? I'd say it's not worth changing > if it's just an optimization, because too many things will break. > Several apps have already been pointed out. > > And what do you mean by ``most apps already do the wrong thing now''? Consider the following bit of "canonical" code, of which some variant is probably found in almost all network programs: struct sockaddr_in sin; len = sizeof(sin); fd = accept(s, (struct sockaddr *)&sin, &len); if (fd == -1) err(1, "accept"); printf("peer address: %s\n", inet_ntoa(sin.sin_addr)); The bug with this code is that it blindly uses ``sin'' after accept returns, since the usage of the returned sockaddr must first be qualified by checking the returned value of len. Current behavior is for accept to return a valid fd, and set len to 0. To my knowledge, most applications (certainly those I inspected) do not bother to check 'len' before using 'sin', and thus do the wrong thing; this is the bug that BIND ran into. (just to be clear, this is a bug in the application code, not the kernel; although you could make the case that it is a documentation bug as well). It seems that other systems (and maybe the SuS?) expect accept to return ECONNABORTED in this case. Both BIND and Apache expect this, at least. It seems to me that the odds of an application being able to correctly handle an error return from accept() are far greater than the odds that the code correctly checks 'len' upon return from accept. This, combined with the standard, seems to be rationale enough to make the change. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 17:50:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 11C9837B491 for ; Mon, 12 Feb 2001 17:50:17 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA07151; Tue, 13 Feb 2001 10:50:06 +0900 (JST) To: Jonathan Lemon Cc: Archie Cobbs , kris@obsecurity.org, net@freebsd.org In-reply-to: jlemon's message of Mon, 12 Feb 2001 19:40:58 CST. <20010212194058.A1479@prism.flugsvamp.com> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] From: itojun@iijlab.net Date: Tue, 13 Feb 2001 10:50:06 +0900 Message-ID: <7149.982029006@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > struct sockaddr_in sin; > > len = sizeof(sin); > fd = accept(s, (struct sockaddr *)&sin, &len); > if (fd == -1) > err(1, "accept"); > printf("peer address: %s\n", inet_ntoa(sin.sin_addr)); > >The bug with this code is that it blindly uses ``sin'' after accept >returns, since the usage of the returned sockaddr must first be qualified >by checking the returned value of len. Current behavior is for accept >to return a valid fd, and set len to 0. > >To my knowledge, most applications (certainly those I inspected) do not >bother to check 'len' before using 'sin', and thus do the wrong thing; >this is the bug that BIND ran into. (just to be clear, this is a bug >in the application code, not the kernel; although you could make the >case that it is a documentation bug as well). I wonder if we can call it an "application bug". yes, it was application's fault that it did not check sa_len. from the text below: http://www.opengroup.org/onlinepubs/007908799/xns/accept.html i'm not sure if it is legal to return zero-length sockaddr when the kernel is given enough space to return the sockaddr. (the last paragraph do not fit to TCP) itojun If address is not a null pointer, the address of the peer for the accepted connection is stored in the sockaddr structure pointed to by address, and the length of this address is stored in the object pointed to by address_len. If the actual length of the address is greater than the length of the supplied sockaddr structure, the stored address will be truncated. If the protocol permits connections by unbound clients, and the peer is not bound, then the value stored in the object pointed to by address is unspecified. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 18:31:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 5281237B4EC for ; Mon, 12 Feb 2001 18:31:35 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA93059; Mon, 12 Feb 2001 18:31:34 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id SAA72979; Mon, 12 Feb 2001 18:31:33 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102130231.SAA72979@curve.dellroad.org> Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <6290.982027182@coconut.itojun.org> "from itojun@iijlab.net at Feb 13, 2001 10:19:42 am" To: itojun@iijlab.net Date: Mon, 12 Feb 2001 18:31:33 -0800 (PST) Cc: jlemon@flugsvamp.com, kris@obsecurity.org, net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org itojun@iijlab.net writes: > >And what do you mean by ``most apps already do the wrong thing now''? > > for background (like when this happens) see previous articles > on this thread. > > current behavior: return 0-length sockaddr. Yeah, that is totally broken. Hmm.. how long has this been the "current behavior" ? ISTR at one time you would instead get the actual sockaddr of the just-closed socket, rather than a bogus sockaddr... and that is the behavior one would expect. > new behavior: return ECONNABORTED. > SUSv2 suggests this behavior. it is much safer as accept(2) will fail > so almost every application will go to error case (if you don't have > error check in userland appication, that's problem in application). Why does SUSv2 suggest this when so many applications would break? And they work fine doing the old behavior (returning a real sockaddr)? -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 18:34:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 15DE037B491 for ; Mon, 12 Feb 2001 18:34:30 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id SAA93066; Mon, 12 Feb 2001 18:34:29 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id SAA73072; Mon, 12 Feb 2001 18:34:29 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102130234.SAA73072@curve.dellroad.org> Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <20010212194058.A1479@prism.flugsvamp.com> "from Jonathan Lemon at Feb 12, 2001 07:40:58 pm" To: Jonathan Lemon Date: Mon, 12 Feb 2001 18:34:29 -0800 (PST) Cc: kris@obsecurity.org, net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonathan Lemon writes: > It seems to me that the odds of an application being able to correctly > handle an error return from accept() are far greater than the odds that > the code correctly checks 'len' upon return from accept. This, combined > with the standard, seems to be rationale enough to make the change. True.. but even greater still are the chances that an application will correctly handle accept() returning a *real* sockaddr that corresponds to an already closed connection. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 18:54:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 9D20437B4EC for ; Mon, 12 Feb 2001 18:54:45 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f1D2t6E14468; Mon, 12 Feb 2001 20:55:06 -0600 (CST) (envelope-from jlemon) Date: Mon, 12 Feb 2001 20:55:06 -0600 From: Jonathan Lemon To: Archie Cobbs Cc: Jonathan Lemon , kris@obsecurity.org, net@freebsd.org Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] Message-ID: <20010212205506.B1479@prism.flugsvamp.com> References: <20010212194058.A1479@prism.flugsvamp.com> <200102130234.SAA73072@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200102130234.SAA73072@curve.dellroad.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 12, 2001 at 06:34:29PM -0800, Archie Cobbs wrote: > Jonathan Lemon writes: > > It seems to me that the odds of an application being able to correctly > > handle an error return from accept() are far greater than the odds that > > the code correctly checks 'len' upon return from accept. This, combined > > with the standard, seems to be rationale enough to make the change. > > True.. but even greater still are the chances that an application will > correctly handle accept() returning a *real* sockaddr that corresponds > to an already closed connection. Please review the earlier postings in this thread. While this would probably be nice, it isn't possible with our current internals; the sockaddr is stored in the inpcb, which is destroyed when the connection is torn down. So by the time the user gets around to calling accept, the sockaddr is long gone. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Feb 12 19:48:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from starfruit.itojun.org (kame202.kame.net [203.178.141.202]) by hub.freebsd.org (Postfix) with ESMTP id 6605537B491 for ; Mon, 12 Feb 2001 19:48:23 -0800 (PST) Received: from itojun.org (localhost [127.0.0.1]) by starfruit.itojun.org (Postfix) with ESMTP id 8881A7E2A; Tue, 13 Feb 2001 12:48:20 +0900 (JST) To: Archie Cobbs Cc: jlemon@flugsvamp.com, kris@obsecurity.org, net@freebsd.org In-reply-to: archie's message of Mon, 12 Feb 2001 18:31:33 PST. <200102130231.SAA72979@curve.dellroad.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] From: Jun-ichiro itojun Hagino Date: Tue, 13 Feb 2001 12:48:20 +0900 Message-Id: <20010213034820.8881A7E2A@starfruit.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> for background (like when this happens) see previous articles >> on this thread. >> current behavior: return 0-length sockaddr. >Yeah, that is totally broken. >Hmm.. how long has this been the "current behavior" ? >ISTR at one time you would instead get the actual sockaddr of the >just-closed socket, rather than a bogus sockaddr... and that is the >behavior one would expect. No, i guess your memory is wrong (or remember something different). Before sys/kern/uipc_socket.c 1.52, 4.4BSD-based systems hanged up when: - TCP handshake is done - RST is issued before accept(2) after 1.52 to current, zero-length sockaddr is returned. none of these are correct. >> new behavior: return ECONNABORTED. >> SUSv2 suggests this behavior. it is much safer as accept(2) will fail >> so almost every application will go to error case (if you don't have >> error check in userland appication, that's problem in application). >Why does SUSv2 suggest this when so many applications would break? >And they work fine doing the old behavior (returning a real sockaddr)? again, *BSD never worked right (in terms of SUSv2 definition of "right"). see Stevens "unix network programming" section I mentioned earlier in this thread. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 7:23:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from natan.teuto.de (natan.teuto.de [212.8.199.33]) by hub.freebsd.org (Postfix) with ESMTP id C5A7F37B491 for ; Tue, 13 Feb 2001 07:23:32 -0800 (PST) Received: from ag.intra (ag.intra [10.0.0.10]) by natan.teuto.de (Postfix) with ESMTP id DCD51DC04 for ; Tue, 13 Feb 2001 16:23:26 +0100 (CET) Date: Tue, 13 Feb 2001 16:22:02 +0100 From: Andreas Gerstenberg To: freebsd-net@FreeBSD.ORG Subject: which ethernet-card for vlan support ? Message-ID: <56520000.982077722@ag.intra> X-Mailer: Mulberry/2.0.6b4 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have to set up a FreeBSD Box which have to support IEEE 802.1Q VLANs. From the past I know that there are limitations in the hardware and the fixed MTU of 1500 Bytes (fixed size of receiving buffer, etc) I'm free in the choice of Hardware. Which cards will run smothly with freebsd and vlan support? regards, Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 8:11:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id E59F437B491 for ; Tue, 13 Feb 2001 08:11:22 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA30820; Tue, 13 Feb 2001 11:11:16 -0500 (EST) (envelope-from wollman) Date: Tue, 13 Feb 2001 11:11:16 -0500 (EST) From: Garrett Wollman Message-Id: <200102131611.LAA30820@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: net@FreeBSD.ORG Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <200102130231.SAA72979@curve.dellroad.org> References: <6290.982027182@coconut.itojun.org> <200102130231.SAA72979@curve.dellroad.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > ISTR at one time you would instead get the actual sockaddr of the > just-closed socket, rather than a bogus sockaddr... and that is the > behavior one would expect. As itojun pointed out, accept() used to just block if the socket it thought it was going to give you turned out not to be there at the last moment. This was a killer for applications which expected return from select() to be a reliable indicator of connections waiting. I think the proposed fix is the best one we can get right now. Restructuring the TCP code to handle this case doesn't make a whole lot of sense to me (or apparently to itojun or jlemon either). -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 8:18:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from illustrious.cnchost.com (illustrious.concentric.net [207.155.252.7]) by hub.freebsd.org (Postfix) with ESMTP id 5E83D37B491 for ; Tue, 13 Feb 2001 08:18:34 -0800 (PST) Received: from auvo.com (4032268D.ptr.dia.nextlink.net [64.50.38.141]) by illustrious.cnchost.com id LAA18512; Tue, 13 Feb 2001 11:18:32 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Message-ID: <3A895E3D.439DCCF3@auvo.com> Date: Tue, 13 Feb 2001 10:18:05 -0600 From: Mike Bytnar Reply-To: mbytnar@auvo.com Organization: Auvo X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: ipfw command "in xmit " and "out recv " invalid? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is this a bug or have I misunderstood? Why is it possible to say "out recv "? Or for that matter, "in xmit "? bridge# ipfw add 500 pipe 2 ip from any to any out recv xl1 00500 pipe 5 ip from any to any out recv xl1 bridge# ipfw add 600 pipe 3 ip from any to any in xmit xl1 [ipfw usage displayed] (Using 4.2-STABLE from a week ago.) Thanks, --Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 8:30:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id F36C037B4EC for ; Tue, 13 Feb 2001 08:30:31 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1DGU0M30692; Tue, 13 Feb 2001 08:30:00 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102131630.f1DGU0M30692@iguana.aciri.org> Subject: Re: ipfw command "in xmit " and "out recv " invalid? In-Reply-To: <3A895E3D.439DCCF3@auvo.com> from Mike Bytnar at "Feb 13, 2001 10:18: 5 am" To: mbytnar@auvo.com Date: Tue, 13 Feb 2001 08:29:23 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is this a bug or have I misunderstood? > Why is it possible to say "out recv "? Or for that matter, "in > xmit "? > > bridge# ipfw add 500 pipe 2 ip from any to any out recv xl1 > 00500 pipe 5 ip from any to any out recv xl1 > bridge# ipfw add 600 pipe 3 ip from any to any in xmit xl1 > [ipfw usage displayed] it's a bit tricky. The same ruleset is applied on input and output. Rule 500 would never match on the input branch, and on the output branch you know what the input interface was so it makes sense to say "i want to select output packets which are coming from this interface". In rule 600, "in" would match on the input branch, but at that point you do not know what the output interface will be so the match will fail. So the rule in this form does not make sense. At least, so I think... cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 9: 1:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id D4C4037B4EC for ; Tue, 13 Feb 2001 09:01:45 -0800 (PST) Received: from elischer.org (reggae-03-89.nv.iinet.net.au [203.59.78.89]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id BAA01912; Wed, 14 Feb 2001 01:01:34 +0800 Message-ID: <3A896861.94465630@elischer.org> Date: Tue, 13 Feb 2001 09:01:21 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: mbytnar@auvo.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: ipfw command "in xmit " and "out recv " invalid? References: <3A895E3D.439DCCF3@auvo.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Bytnar wrote: > > Is this a bug or have I misunderstood? > Why is it possible to say "out recv "? Or for that matter, "in > xmit "? > > bridge# ipfw add 500 pipe 2 ip from any to any out recv xl1 > 00500 pipe 5 ip from any to any out recv xl1 if the filter is called from ip_output() and the packet was received on xl1 (then we must be routing it) > bridge# ipfw add 600 pipe 3 ip from any to any in xmit xl1 > [ipfw usage displayed] if we were called from ip_input() then we have not yet decided if it will be retransmitted from an interface, let alone which one.. so this makes no sense. > > (Using 4.2-STABLE from a week ago.) > > Thanks, > --Mike > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 9:21:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 5250037B4EC for ; Tue, 13 Feb 2001 09:21:49 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA97475; Tue, 13 Feb 2001 09:21:45 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id JAA75141; Tue, 13 Feb 2001 09:21:44 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102131721.JAA75141@curve.dellroad.org> Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <200102131611.LAA30820@khavrinen.lcs.mit.edu> "from Garrett Wollman at Feb 13, 2001 11:11:16 am" To: Garrett Wollman Date: Tue, 13 Feb 2001 09:21:44 -0800 (PST) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman writes: > > ISTR at one time you would instead get the actual sockaddr of the > > just-closed socket, rather than a bogus sockaddr... and that is the > > behavior one would expect. > > As itojun pointed out, accept() used to just block if the socket it > thought it was going to give you turned out not to be there at the > last moment. This was a killer for applications which expected > return from select() to be a reliable indicator of connections > waiting. > > I think the proposed fix is the best one we can get right now. > Restructuring the TCP code to handle this case doesn't make a whole > lot of sense to me (or apparently to itojun or jlemon either). Ah, my apologies for being foggy on the prior behavior. Given the circumstances, I agree returning the error from accept(2) seems like the best option. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 16:53:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id BF03B37B491 for ; Tue, 13 Feb 2001 16:53:14 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1E0rET55388; Tue, 13 Feb 2001 16:53:14 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102140053.f1E0rET55388@iguana.aciri.org> Subject: fxp performance ? To: net@freebsd.org Date: Tue, 13 Feb 2001 16:53:13 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, don't know how many of you have ever tried this... I am trying to generate (send only) packets at maximum rate on a 100Mbit ethernet, which means using 64-byte packets and, once you do the math (counting preamble, packet and inter-packet gap), results in some 148.000 packets-per-second (and just to get the idea, this also means that a new packet is transmitted every 6.72us). Note, the above is not trivial as you need a fast CPU, and probably some tricks in order to avoid parf of the overhead of ip_output(). In any case, on botu a P3-650 and an Athlon-750, I managed to achieve this speed using the "dc" driver. When i tried the same with the 'fxp' driver, there was no way i managed to go above 105-110.000 packets per second (meaning an average of 9.1us/packet). Any idea on what is going on ? I have spent quite some time in the fxp driver and cannot really tell where the problem is. Unfortunately my diagnostic tools do not let me see what is going on on the wire, whether the spacing is larger than it should be, etc. etc. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 17:31:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from overlord.e-gerbil.net (e-gerbil.net [207.91.110.247]) by hub.freebsd.org (Postfix) with ESMTP id 31B7537B491 for ; Tue, 13 Feb 2001 17:31:36 -0800 (PST) Received: by overlord.e-gerbil.net (Postfix, from userid 1001) id 7DB93E4BB9; Tue, 13 Feb 2001 20:31:34 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by overlord.e-gerbil.net (Postfix) with ESMTP id 58E05E4BB8; Tue, 13 Feb 2001 20:31:34 -0500 (EST) Date: Tue, 13 Feb 2001 20:31:33 -0500 (EST) From: "Richard A. Steenbergen" To: Luigi Rizzo Cc: net@freebsd.org Subject: Re: fxp performance ? In-Reply-To: <200102140053.f1E0rET55388@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 13 Feb 2001, Luigi Rizzo wrote: > Hi, > don't know how many of you have ever tried this... > > I am trying to generate (send only) packets at maximum rate on a > 100Mbit ethernet, which means using 64-byte packets and, once you > do the math (counting preamble, packet and inter-packet gap), > results in some 148.000 packets-per-second (and just to get the > idea, this also means that a new packet is transmitted every 6.72us). > > Note, the above is not trivial as you need a fast CPU, and probably > some tricks in order to avoid parf of the overhead of ip_output(). > > In any case, on botu a P3-650 and an Athlon-750, I managed to > achieve this speed using the "dc" driver. When i tried the same > with the 'fxp' driver, there was no way i managed to go above > 105-110.000 packets per second (meaning an average of 9.1us/packet). > > Any idea on what is going on ? I have spent quite some time in > the fxp driver and cannot really tell where the problem is. > Unfortunately my diagnostic tools do not let me see what is going > on on the wire, whether the spacing is larger than it should be, > etc. etc. I have had no problem doing line rate w/fxp and a p3 500 (well not to say no problem, but it is achievable). In my experience the biggest overheads are ip_output() and routing lookups. If you can't push past a certain amount and you're not CPU bound, check the device you're connected to because often times its inability to transmit the packet. Were both cards connected to the same device outputting to the same destination under the same lan conditions? -- Richard A Steenbergen http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 17:44:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 4890F37B65D for ; Tue, 13 Feb 2001 17:44:10 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1E1i8I57239; Tue, 13 Feb 2001 17:44:08 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102140144.f1E1i8I57239@iguana.aciri.org> Subject: Re: fxp performance ? In-Reply-To: from "Richard A. Steenbergen" at "Feb 13, 2001 8:31:33 pm" To: ras@e-gerbil.net (Richard A. Steenbergen) Date: Tue, 13 Feb 2001 17:44:03 -0800 (PST) Cc: rizzo@aciri.org, net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have had no problem doing line rate w/fxp and a p3 500 (well not to say > no problem, but it is achievable). In my experience the biggest overheads you mean with min-sized packets ? what version of freebsd ? I'd be interested to repeat this. > are ip_output() and routing lookups. If you can't push past a certain > amount and you're not CPU bound, check the device you're connected to > because often times its inability to transmit the packet. Were both cards > connected to the same device outputting to the same destination under the > same lan conditions? i tried with back-to-back cards using a cross-over cable, full duplex. dc --> dc and dc --> fxp gives ~143Kpkts/s over long term, fxp --> fxp and fxp --> fxp gives ~105Kpkts/s over long term, in both cases counted with netstat on the source side, in both cases changing the receiver and the source box makes no difference. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 18:23:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from inetfw.csl.sony.co.jp (inetfw.SonyCSL.CO.JP [203.137.129.4]) by hub.freebsd.org (Postfix) with ESMTP id 31A2437B503 for ; Tue, 13 Feb 2001 18:23:13 -0800 (PST) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57] (may be forged)) by inetfw.csl.sony.co.jp (8.11.2+3.4W/3.7Ws3/inetfw/2001012518/smtpfeed 1.08) with ESMTP id f1E2NBu09425; Wed, 14 Feb 2001 11:23:11 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.9.3+3.2W/3.7Ws3/hotaka/2000061722) with ESMTP id LAA84977; Wed, 14 Feb 2001 11:23:10 +0900 (JST) To: rizzo@aciri.org Cc: net@freebsd.org Subject: Re: fxp performance ? In-Reply-To: <200102140053.f1E0rET55388@iguana.aciri.org> References: <200102140053.f1E0rET55388@iguana.aciri.org> X-Mailer: Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010214112310G.kjc@csl.sony.co.jp> Date: Wed, 14 Feb 2001 11:23:10 +0900 From: Kenjiro Cho X-Dispatcher: imput version 20000228(IM140) Lines: 40 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo wrote: > I am trying to generate (send only) packets at maximum rate on a > 100Mbit ethernet, which means using 64-byte packets and, once you > do the math (counting preamble, packet and inter-packet gap), > results in some 148.000 packets-per-second (and just to get the > idea, this also means that a new packet is transmitted every 6.72us). > > Note, the above is not trivial as you need a fast CPU, and probably > some tricks in order to avoid parf of the overhead of ip_output(). > > In any case, on botu a P3-650 and an Athlon-750, I managed to > achieve this speed using the "dc" driver. When i tried the same > with the 'fxp' driver, there was no way i managed to go above > 105-110.000 packets per second (meaning an average of 9.1us/packet). > > Any idea on what is going on ? I have spent quite some time in > the fxp driver and cannot really tell where the problem is. > Unfortunately my diagnostic tools do not let me see what is going > on on the wire, whether the spacing is larger than it should be, > etc. etc. It might be related to the fact that the fxp driver doesn't generate a transmission complete interrupt unless the interface queue length is exactly 119. Does the following change make any difference? --- if_fxp.c- Wed Feb 14 11:13:42 2001 +++ if_fxp.c Wed Feb 14 11:14:27 2001 @@ -1183,6 +1183,7 @@ * going again if suspended. */ if (txp != NULL) { + txp->cb_command |= FXP_CB_COMMAND_I; fxp_scb_wait(sc); CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_RESUME); } -Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 18:28:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from kies.co.kr (sky.kies.co.kr [203.236.114.1]) by hub.freebsd.org (Postfix) with ESMTP id 13C4037B4EC for ; Tue, 13 Feb 2001 18:28:00 -0800 (PST) Received: from narai (jupiter-ex.kies.co.kr [203.236.114.148]) by kies.co.kr (8.9.3+Sun/8.9.3) with SMTP id LAA11432 for ; Wed, 14 Feb 2001 11:29:01 +0900 (KST) Message-ID: <002201c0962d$aa0bf920$d30110ac@narai> From: =?ks_c_5601-1987?B?wMy/ucfP?= To: Subject: How to get AH working? Date: Wed, 14 Feb 2001 11:27:23 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C09679.19DB3720" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C09679.19DB3720 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 aGkNCiANCmkgaW5zdGFsbGVkIGZyZWVic2Q0LjIgYW5kIGthbWUtMjAwMTAyMTItZnJlZWJzZDQy LXNuYXAgYW5kIHRyaWVkIElQU0VDIGNvbm5lY3Rpb25zLg0KRVNQIG1vZGUgd29ya2VkIGZpbmUg d2l0aCBrYW1lKHJhY29vbikgYnV0IEkgY291bGRuJ3QgZ2V0IEFIIG1vZGUgY29ubmVjdGlvbi4N CkZvbGxvd2luZyBpcyB0aGUgZXJyb3IgbWVzc2FnZXMuDQogDQprZVRlc3QjIEZlYiAxNCAxMDo0 ODozMSBJa2VUZXN0IC9rZXJuZWw6IGNoZWNrc3VtIG1pc21hdGNoIGluIElQdjQgDQpBSCBpbnB1 dDogcGFja2V0KFNQST0yMjU2Njc1OTUgc3JjPTE3Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEuMjEw KSANClNBKFNQST0yMjU2Njc1OTUgc3JjPTE3Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEuMjEwKQ0K IA0KRmViIDE0IDEwOjQ4OjMyIElrZVRlc3QgL2tlcm5lbDogY2hlY2tzdW0gbWlzbWF0Y2ggaW4g SVB2NCANCkFIIGlucHV0OiBwYWNrZXQoU1BJPTIyNTY2NzU5NSBzcmM9MTcyLjE2LjEuMjExIGRz dD0xNzIuMTYuMS4yMTApIA0KU0EoU1BJPTIyNTY2NzU5NSBzcmM9MTcyLjE2LjEuMjExIGRzdD0x NzIuMTYuMS4yMTApDQogDQpGZWIgMTQgMTA6NDg6MzMgSWtlVGVzdCAva2VybmVsOiBjaGVja3N1 bSBtaXNtYXRjaCBpbiBJUHY0IA0KQUggaW5wdXQ6IHBhY2tldChTUEk9MjI1NjY3NTk1IHNyYz0x NzIuMTYuMS4yMTEgZHN0PTE3Mi4xNi4xLjIxMCkgDQpTQShTUEk9MjI1NjY3NTk1IHNyYz0xNzIu MTYuMS4yMTEgZHN0PTE3Mi4xNi4xLjIxMCkNCiANCkZlYiAxNCAxMDo0ODozNCBJa2VUZXN0IC9r ZXJuZWw6IGNoZWNrc3VtIG1pc21hdGNoIGluIElQdjQgDQpBSCBpbnB1dDogcGFja2V0KFNQST0y MjU2Njc1OTUgc3JjPTE3Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEuMjEwKSANClNBKFNQST0yMjU2 Njc1OTUgc3JjPTE3Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEuMjEwKQ0KIA0KV2hhdCdzIHRoZSBw cm9ibGVtPyBBbmQgaG93IGNhbiBJIGZpeCBpdD8NCiANCg== ------=_NextPart_000_001F_01C09679.19DB3720 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWtz X2NfNTYwMS0xOTg3IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1T SFRNTCA1LjAwLjI5MjAuMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVB RD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPg0KPERJVj48Rk9O VCBzaXplPTI+PFNQQU4gY2xhc3M9NjEwMTUxNDAyLTE0MDIyMDAxPmhpPC9TUEFOPjwvRk9OVD48 L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDBmZj48Rk9OVCBzaXplPTI+PFNQQU4gDQpjbGFz cz02MTAxNTE0MDItMTQwMjIwMDE+PC9TUEFOPjwvRk9OVD48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8 RElWPjxGT05UIHNpemU9Mj48U1BBTiBjbGFzcz02MTAxNTE0MDItMTQwMjIwMDE+aSBpbnN0YWxs ZWQgZnJlZWJzZDQuMiBhbmQgDQprYW1lLTIwMDEwMjEyLWZyZWVic2Q0Mi1zbmFwIGFuZCB0cmll ZCBJUFNFQyBjb25uZWN0aW9ucy48L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXpl PTI+PFNQQU4gY2xhc3M9NjEwMTUxNDAyLTE0MDIyMDAxPkVTUCBtb2RlIHdvcmtlZCBmaW5lIHdp dGggDQprYW1lKHJhY29vbikgYnV0IEkmbmJzcDtjb3VsZG4ndCBnZXQgQUggbW9kZSBjb25uZWN0 aW9uLjwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48U1BBTiBjbGFzcz02 MTAxNTE0MDItMTQwMjIwMDE+Rm9sbG93aW5nIGlzIHRoZSBlcnJvciANCm1lc3NhZ2VzLjwvU1BB Tj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48U1BBTiBjbGFzcz02MTAxNTE0MDIt MTQwMjIwMDE+PC9TUEFOPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9NjEw MTUxNDAyLTE0MDIyMDAxPg0KPERJVj48Rk9OVCBzaXplPTI+a2VUZXN0IyBGZWIgMTQgMTA6NDg6 MzEgSWtlVGVzdCAva2VybmVsOiBjaGVja3N1bSBtaXNtYXRjaCBpbiANCklQdjQgPEJSPkFIIGlu cHV0OiBwYWNrZXQoU1BJPTIyNTY2NzU5NSBzcmM9MTcyLjE2LjEuMjExIGRzdD0xNzIuMTYuMS4y MTApIA0KPEJSPlNBKFNQST0yMjU2Njc1OTUgc3JjPTE3Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEu MjEwKTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDBmZiBzaXplPTI+PC9GT05U PiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+RmViIDE0IDEwOjQ4OjMyIElrZVRlc3Qg L2tlcm5lbDogY2hlY2tzdW0gbWlzbWF0Y2ggaW4gSVB2NCANCjxCUj5BSCBpbnB1dDogcGFja2V0 KFNQST0yMjU2Njc1OTUgc3JjPTE3Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEuMjEwKSANCjxCUj5T QShTUEk9MjI1NjY3NTk1IHNyYz0xNzIuMTYuMS4yMTEgZHN0PTE3Mi4xNi4xLjIxMCk8L0ZPTlQ+ PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJ Vj4NCjxESVY+PEZPTlQgc2l6ZT0yPkZlYiAxNCAxMDo0ODozMyBJa2VUZXN0IC9rZXJuZWw6IGNo ZWNrc3VtIG1pc21hdGNoIGluIElQdjQgDQo8QlI+QUggaW5wdXQ6IHBhY2tldChTUEk9MjI1NjY3 NTk1IHNyYz0xNzIuMTYuMS4yMTEgZHN0PTE3Mi4xNi4xLjIxMCkgDQo8QlI+U0EoU1BJPTIyNTY2 NzU5NSBzcmM9MTcyLjE2LjEuMjExIGRzdD0xNzIuMTYuMS4yMTApPC9GT05UPjwvRElWPg0KPERJ Vj48Rk9OVCBjb2xvcj0jMDAwMGZmIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxG T05UIHNpemU9Mj5GZWIgMTQgMTA6NDg6MzQgSWtlVGVzdCAva2VybmVsOiBjaGVja3N1bSBtaXNt YXRjaCBpbiBJUHY0IA0KPEJSPkFIIGlucHV0OiBwYWNrZXQoU1BJPTIyNTY2NzU5NSBzcmM9MTcy LjE2LjEuMjExIGRzdD0xNzIuMTYuMS4yMTApIA0KPEJSPlNBKFNQST0yMjU2Njc1OTUgc3JjPTE3 Mi4xNi4xLjIxMSBkc3Q9MTcyLjE2LjEuMjEwKTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgY29s b3I9IzAwMDBmZiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48U1BBTiBjbGFzcz02 MTAxNTE0MDItMTQwMjIwMDE+PEZPTlQgc2l6ZT0yPldoYXQncyB0aGUgcHJvYmxlbT8gQW5kIGhv dyBjYW4gDQpJIGZpeCBpdD88L0ZPTlQ+PC9TUEFOPjwvRElWPg0KPERJVj48U1BBTiBjbGFzcz02 MTAxNTE0MDItMTQwMjIwMDE+PEZPTlQgDQpzaXplPTI+PC9GT05UPjwvU1BBTj4mbmJzcDs8L0RJ Vj48L1NQQU4+PC9ESVY+PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_001F_01C09679.19DB3720-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Feb 13 18:36:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 9B55E37B503 for ; Tue, 13 Feb 2001 18:36:18 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1E2aCU57546; Tue, 13 Feb 2001 18:36:12 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102140236.f1E2aCU57546@iguana.aciri.org> Subject: Re: fxp performance ? In-Reply-To: <20010214112310G.kjc@csl.sony.co.jp> from Kenjiro Cho at "Feb 14, 2001 11:23:10 am" To: kjc@csl.sony.co.jp (Kenjiro Cho) Date: Tue, 13 Feb 2001 18:36:07 -0800 (PST) Cc: rizzo@aciri.org, net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Unfortunately my diagnostic tools do not let me see what is going > > on on the wire, whether the spacing is larger than it should be, actually i managed to instrument the driver and the spacing between interrupts (with a change similar to the one you proposed -- i make them occur every N packets ) is approx (N*9)us which seems to suggest a larger spacing than it should be. Wonder if the interframe spacing or the preamble lenght is incorrect... cheers luigi > > It might be related to the fact that the fxp driver doesn't generate > a transmission complete interrupt unless the interface queue length is > exactly 119. > > Does the following change make any difference? > > --- if_fxp.c- Wed Feb 14 11:13:42 2001 > +++ if_fxp.c Wed Feb 14 11:14:27 2001 > @@ -1183,6 +1183,7 @@ > * going again if suspended. > */ > if (txp != NULL) { > + txp->cb_command |= FXP_CB_COMMAND_I; > fxp_scb_wait(sc); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_RESUME); > } > > -Kenjiro > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 8: 0:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 7364737B401 for ; Wed, 14 Feb 2001 08:00:49 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1EG0i522876; Wed, 14 Feb 2001 17:00:44 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1EFio433027; Wed, 14 Feb 2001 16:44:50 +0100 (CET) (envelope-from asmodai) Date: Wed, 14 Feb 2001 16:44:49 +0100 From: Jeroen Ruigrok/Asmodai To: Luigi Rizzo Cc: net@freebsd.org Subject: Re: dead code in ip_output.c and udp_var.h Message-ID: <20010214164449.A32946@daemon.ninth-circle.org> References: <200102090046.f190k6K06283@iguana.aciri.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200102090046.f190k6K06283@iguana.aciri.org>; from rizzo@aciri.org on Thu, Feb 08, 2001 at 04:46:06PM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20010209 02:00], Luigi Rizzo (rizzo@aciri.org) wrote: >and maybe it would be the case to remove the first block and the >conditionals on the second one. I don't think we plan a port to the >vax, am i wrong ? Personally I'd be happier if this got removed. We don't intend to port to VAX, and the only thing I can think of is that it might make diffing a bit easier, which is a mootpoint anyway nowadays with SMPng touching the whole of the kernel. So, I'd ACK that. I am personally pondering to removal hacks like this from the telnet(d) synching I am doing. >udp_var.h contains a definition of "struct udpcb" and "inptoudpcb()" >which are never used anywhere. Again if there are no objections i >would like to nuke them. I only see a reference to udpcb in udp_usrreq.c, but that's a zinit() label name. So you have my ACK. Not sure what wollman or jlemon think? ACK on the inptudpcb() removal. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 8:19:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id BC5FD37B491 for ; Wed, 14 Feb 2001 08:19:43 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f1EGJdT77181; Wed, 14 Feb 2001 17:19:39 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1EGGQa33181; Wed, 14 Feb 2001 17:16:26 +0100 (CET) (envelope-from asmodai) Date: Wed, 14 Feb 2001 17:16:26 +0100 From: Jeroen Ruigrok/Asmodai To: Luigi Rizzo Cc: net@freebsd.org Subject: Re: dead code in ip_output.c and udp_var.h Message-ID: <20010214171626.B32946@daemon.ninth-circle.org> References: <200102090046.f190k6K06283@iguana.aciri.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200102090046.f190k6K06283@iguana.aciri.org>; from rizzo@aciri.org on Thu, Feb 08, 2001 at 04:46:06PM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Speaking of dead code: sys/netinet/tcpip.h: struct full_tcpiphdr{} appears to not be used. It was added in 1995 for some T/TCP stuff. Anyone know if this is used outside of our sources? ipfilter seemingly defines its own version of it in the contrib directory, but it also doesn't use it. :P -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 13:18:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id BA4EC37B4EC for ; Wed, 14 Feb 2001 13:18:20 -0800 (PST) Received: by mailman.thenap.com with Internet Mail Service (5.5.2650.21) id ; Wed, 14 Feb 2001 16:30:39 -0500 Message-ID: From: "Drew J. Weaver" To: net@freebsd.org Subject: Adding IP aliases Date: Wed, 14 Feb 2001 16:30:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C096CD.5F9133EC" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C096CD.5F9133EC Content-Type: text/plain; charset="iso-8859-1" Does anyone know of a FAQ or HOWTO for adding IP aliases to a FreeBSD box? I can do it under linux and Im just wondering if there are any differences or what-not. Thanks, -Drew ------_=_NextPart_001_01C096CD.5F9133EC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Adding IP aliases

        Does = anyone know of a FAQ or HOWTO for adding IP aliases to a FreeBSD box? I = can do it under linux and Im just wondering if there are any = differences or what-not.

Thanks,
-Drew

------_=_NextPart_001_01C096CD.5F9133EC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 13:24: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from cartman.cisp.cc (mail.cisp.cc [63.174.69.7]) by hub.freebsd.org (Postfix) with ESMTP id 6745A37B65D for ; Wed, 14 Feb 2001 13:24:00 -0800 (PST) Received: by cartman.cisp.cc with Internet Mail Service (5.5.2650.21) id <1L28M0CV>; Wed, 14 Feb 2001 16:20:11 -0500 Message-ID: From: Aaron Weiker To: "'Drew J. Weaver'" , "'net@freebsd.org'" Subject: RE: Adding IP aliases Date: Wed, 14 Feb 2001 16:20:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C096CB.E97EC260" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C096CB.E97EC260 Content-Type: text/plain; charset="iso-8859-1" Best place to look is check out the man of ifconfig This will give you the syntax for it. I then edited my /etc/rc.network and put that command in there to create the alias when the server was rebooted. Aaron Weiker Programmer CISP - Changing Internet Speed & Performance Phone: 419.724.5351 aweiker@cisp.cc Pager: 419.218.0013 http://www.cisp.cc Cell: 419.304.0323 web search: http://www.allthesites.com -----Original Message----- From: Drew J. Weaver [mailto:drew.weaver@thenap.com] Sent: Wednesday, February 14, 2001 4:31 PM To: net@freebsd.org Subject: Adding IP aliases Does anyone know of a FAQ or HOWTO for adding IP aliases to a FreeBSD box? I can do it under linux and Im just wondering if there are any differences or what-not. Thanks, -Drew ------_=_NextPart_001_01C096CB.E97EC260 Content-Type: text/html; charset="iso-8859-1" Adding IP aliases
Best place to look is check out the man of ifconfig
 
This will give you the syntax for it. I then edited my /etc/rc.network and put that command in there to create the alias when the server was rebooted.
 

Aaron Weiker
Programmer
CISP - Changing Internet Speed & Performance

Phone: 419.724.5351                     aweiker@cisp.cc
Pager: 419.218.0013                     http://www.cisp.cc
Cell:    419.304.0323                   web search: http://www.allthesites.com

-----Original Message-----
From: Drew J. Weaver [mailto:drew.weaver@thenap.com]
Sent: Wednesday, February 14, 2001 4:31 PM
To: net@freebsd.org
Subject: Adding IP aliases

        Does anyone know of a FAQ or HOWTO for adding IP aliases to a FreeBSD box? I can do it under linux and Im just wondering if there are any differences or what-not.

Thanks,
-Drew

------_=_NextPart_001_01C096CB.E97EC260-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 13:27:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from daemon.best.ca (cr262311-a.lngly1.bc.wave.home.com [24.113.173.186]) by hub.freebsd.org (Postfix) with ESMTP id A654537B401 for ; Wed, 14 Feb 2001 13:27:44 -0800 (PST) Received: by daemon.best.ca (Postfix, from userid 1000) id 6409FD7108; Wed, 14 Feb 2001 13:27:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daemon.best.ca (Postfix) with ESMTP id A8DCDC9820; Wed, 14 Feb 2001 13:27:42 -0800 (PST) Date: Wed, 14 Feb 2001 13:27:42 -0800 (PST) From: Richard Furda To: Aaron Weiker Cc: "'Drew J. Weaver'" , "'net@freebsd.org'" Subject: RE: Adding IP aliases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, On Wed, 14 Feb 2001, Aaron Weiker wrote: > Best place to look is check out the man of ifconfig > > This will give you the syntax for it. I then edited my /etc/rc.network and > put that command in there to create the alias when the server was rebooted. /etc/rc.network is not the place to add aliases. Please look at the examples in /etc/defaults/rc.conf ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. these should be placed into /etc/rc.conf > Does anyone know of a FAQ or HOWTO for adding IP aliases to a > FreeBSD box? I can do it under linux and Im just wondering if there are any > differences or what-not. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 13:32: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from mario.zyan.com (mario.zyan.com [209.250.96.140]) by hub.freebsd.org (Postfix) with ESMTP id 3C65837B401 for ; Wed, 14 Feb 2001 13:32:02 -0800 (PST) Received: from dopey.weyrich.com (orville@node-64-249-12-250.dslspeed.zyan.com [64.249.12.250]) by mario.zyan.com (8.9.3/8.9.3) with ESMTP id NAA18532 for ; Wed, 14 Feb 2001 13:32:01 -0800 (PST) (envelope-from orville@weyrich.com) Received: from localhost (orville@localhost) by dopey.weyrich.com (8.9.3/8.6.9) with ESMTP id OAA25405; Wed, 14 Feb 2001 14:30:41 -0700 Date: Wed, 14 Feb 2001 14:30:41 -0700 (MST) From: "Orville R. Weyrich.Jr" To: "Drew J. Weaver" Cc: net@FreeBSD.ORG Subject: Re: Adding IP aliases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I recall, with FreeBSD you just use ifconfig. How do you do it with Linux? orville. On Wed, 14 Feb 2001, Drew J. Weaver wrote: > Does anyone know of a FAQ or HOWTO for adding IP aliases to a > FreeBSD box? I can do it under linux and Im just wondering if there are any > differences or what-not. > > Thanks, > -Drew > =================================================================== IF YOU WANT REFORM >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> VOTE REFORM ------------------------------------------------------------------- Orville R. Weyrich, Jr. Weyrich Computer Consulting mailto:orville@weyrich.com KD7HJV http://www.weyrich.com ------------------------------------------------------------------- Visit our online collection of book reviews: http://www.weyrich.com/book_reviews/ Ask about our world wide web services! ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 13:38:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 179BF37B491 for ; Wed, 14 Feb 2001 13:38:29 -0800 (PST) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f1ELagi69797; Wed, 14 Feb 2001 16:36:42 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <002c01c096ce$04f7c530$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "'Drew J. Weaver'" , "'net@freebsd.org'" References: Subject: Re: Adding IP aliases Date: Wed, 14 Feb 2001 16:35:15 -0500 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone know of a FAQ or HOWTO for adding IP aliases to a > FreeBSD box? I can do it under linux and Im just wondering if there are any > differences or what-not. In /etc/rc.conf, add or edit lines like this (I have an 'ed0' network card): network_interfaces="lo0 ed0" ifconfig_lo0="inet 127.0.0.1 netmask 255.0.0.0" ifconfig_ed0="inet 192.168.0.2 netmask 255.255.255.0" ifconfig_ed0_alias0="inet 192.168.0.10 netmask 255.255.255.255" ifconfig_ed0_alias1="inet 192.168.0.11 netmask 255.255.255.255" You need to set the netmask of the aliases to what I have above, otherwise you won't be able to use the aliased IPs. If you want to do it from the command line (note that your aliases will be lost when you reboot unless you do the above), do this: ifconfig ed0 alias 192.168.0.10 netmask 255.255.255.255 -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 13:38:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from cartman.cisp.cc (mail.cisp.cc [63.174.69.7]) by hub.freebsd.org (Postfix) with ESMTP id 62D8D37B401 for ; Wed, 14 Feb 2001 13:38:51 -0800 (PST) Received: by cartman.cisp.cc with Internet Mail Service (5.5.2650.21) id <1L28M01R>; Wed, 14 Feb 2001 16:35:04 -0500 Message-ID: From: Aaron Weiker To: "'net@freebsd.org'" Subject: RE: Adding IP aliases Date: Wed, 14 Feb 2001 16:35:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C096CD.FE2CB9E0" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C096CD.FE2CB9E0 Content-Type: text/plain; charset="iso-8859-1" Well, that's very helpful...Can't believe I didn't see that when I was looking for it. I guess I just always do things the hard way. Aaron Weiker Programmer CISP - Changing Internet Speed & Performance Phone: 419.724.5351 aweiker@cisp.cc Pager: 419.218.0013 http://www.cisp.cc Cell: 419.304.0323 web search: http://www.allthesites.com -----Original Message----- From: Richard Furda [mailto:riso@best.ca] Sent: Wednesday, February 14, 2001 4:28 PM To: Aaron Weiker Cc: 'Drew J. Weaver'; 'net@freebsd.org' Subject: RE: Adding IP aliases Hello, On Wed, 14 Feb 2001, Aaron Weiker wrote: > Best place to look is check out the man of ifconfig > > This will give you the syntax for it. I then edited my /etc/rc.network and > put that command in there to create the alias when the server was rebooted. /etc/rc.network is not the place to add aliases. Please look at the examples in /etc/defaults/rc.conf ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. these should be placed into /etc/rc.conf > Does anyone know of a FAQ or HOWTO for adding IP aliases to a > FreeBSD box? I can do it under linux and Im just wondering if there are any > differences or what-not. Rich ------_=_NextPart_001_01C096CD.FE2CB9E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Adding IP aliases

Well, that's very helpful...Can't believe I didn't = see that when I was looking for it. I guess I just always do things the = hard way.

Aaron Weiker
Programmer
CISP - Changing Internet Speed & = Performance

Phone: 419.724.5351     =         =         aweiker@cisp.cc
Pager: 419.218.0013     =         =         http://www.cisp.cc
Cell:    419.304.0323   =         =         web search: http://www.allthesites.com

-----Original Message-----
From: Richard Furda [mailto:riso@best.ca]
Sent: Wednesday, February 14, 2001 4:28 PM
To: Aaron Weiker
Cc: 'Drew J. Weaver'; 'net@freebsd.org'
Subject: RE: Adding IP aliases



Hello,

On Wed, 14 Feb 2001, Aaron Weiker wrote:
> Best place to look is check out the man of = ifconfig
> 
> This will give you the syntax for it. I then = edited my /etc/rc.network and
> put that command in there to create the alias = when the server was rebooted.

/etc/rc.network is not the place to add aliases. = Please look at the
examples in /etc/defaults/rc.conf

ifconfig_lo0_alias0=3D"inet 127.0.0.254 netmask = 0xffffffff" # Sample alias entry.

these should be placed into /etc/rc.conf

>         = Does anyone know of a FAQ or HOWTO for adding IP aliases to a
> FreeBSD box? I can do it under linux and Im = just wondering if there are any
> differences or what-not.

        Rich

------_=_NextPart_001_01C096CD.FE2CB9E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Feb 14 23:39: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id EB86337B4EC; Wed, 14 Feb 2001 23:38:55 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id NAA23978; Thu, 15 Feb 2001 13:08:48 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Thu, 15 Feb 2001 13:08:47 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id NAA27120; Thu, 15 Feb 2001 13:08:40 +0530 (IST) Date: Thu, 15 Feb 2001 13:08:40 +0530 (IST) From: Satyajeet Seth To: Cc: Subject: KLD'fying PCI device driver! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I am trying to convert my PCI device driver into a KLD. So far I have done the following: 1. Built the kernel without the static linked device driver. 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. 3. Did "make all install" in /sys/modules directory. 4. Tried loading the KLD. I got the following error: "Fatal trap 12: page fault while in kernel mode" Any ideas as to what could be going wrong? Thanks Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 0:33: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 70B8137B491; Thu, 15 Feb 2001 00:32:55 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f1F8Vat39751; Thu, 15 Feb 2001 03:31:36 -0500 (EST) (envelope-from arr@watson.org) Date: Thu, 15 Feb 2001 03:31:35 -0500 (EST) From: "Andrew R. Reiter" To: Satyajeet Seth Cc: freebsd-net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: KLD'fying PCI device driver! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Could you send the load handler function src? On Thu, 15 Feb 2001, Satyajeet Seth wrote: > Hi > > I am trying to convert my PCI device driver into a KLD. > > So far I have done the following: > 1. Built the kernel without the static linked device driver. > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. > 3. Did "make all install" in /sys/modules directory. > 4. Tried loading the KLD. I got the following error: > "Fatal trap 12: page fault while in kernel mode" > > Any ideas as to what could be going wrong? > > Thanks > Satya > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 2:14:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from mass.dis.org (c228380-a.sfmissn1.sfba.home.com [24.20.90.44]) by hub.freebsd.org (Postfix) with ESMTP id 2EC3437B491; Thu, 15 Feb 2001 02:14:53 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f1FAEbV09259; Thu, 15 Feb 2001 02:14:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200102151014.f1FAEbV09259@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Satyajeet Seth Cc: freebsd-net@freebsd.org, hackers@freebsd.org Subject: Re: KLD'fying PCI device driver! In-reply-to: Your message of "Thu, 15 Feb 2001 13:08:40 +0530." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Feb 2001 02:14:36 -0800 From: Mike Smith Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi > > I am trying to convert my PCI device driver into a KLD. > > So far I have done the following: > 1. Built the kernel without the static linked device driver. > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. > 3. Did "make all install" in /sys/modules directory. > 4. Tried loading the KLD. I got the following error: > "Fatal trap 12: page fault while in kernel mode" > > Any ideas as to what could be going wrong? Too many. You haven't really given anything like enough detail here. - What FreeBSD version? - Build the kernel with DDB and symbols, and show us the backtrace. - How is your module attached to the rest of the system? Broadly: - You may not have specified the module correctly. - Your hardware init function may not work properly in the case where the system is already up and running (eg. you may be generating interrupts before you are ready to handle them). - You may be building against sources that don't match your running kernel. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 2:50:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id DF2DE37B401; Thu, 15 Feb 2001 02:50:44 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id QAA09301; Thu, 15 Feb 2001 16:20:36 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Thu, 15 Feb 2001 16:20:35 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id QAA01583; Thu, 15 Feb 2001 16:20:35 +0530 (IST) Date: Thu, 15 Feb 2001 16:20:35 +0530 (IST) From: Satyajeet Seth To: "Andrew R. Reiter" Cc: , Subject: Re: KLD'fying PCI device driver! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi > Could you send the load handler function src? My code does not contain a load handler function. I did not add a load handler function, because none of the files in /sys/pci directory like if_fxp.c, if_vr.c seemed to contain contain a load handler function. To the best of my knowledge, all the pci device driver modules use the function pci_modevent() in /sys/pci/pci.c > > I am trying to convert my PCI device driver into a KLD. > > > > So far I have done the following: > > 1. Built the kernel without the static linked device driver. > > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. > > 3. Did "make all install" in /sys/modules directory. > > 4. Tried loading the KLD. I got the following error: > > "Fatal trap 12: page fault while in kernel mode" > > > > Any ideas as to what could be going wrong? Thanks Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 5:20:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 82D7637B4EC; Thu, 15 Feb 2001 05:20:36 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id SAA17767; Thu, 15 Feb 2001 18:50:30 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Thu, 15 Feb 2001 18:50:30 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id SAA04947; Thu, 15 Feb 2001 18:50:27 +0530 (IST) Date: Thu, 15 Feb 2001 18:50:27 +0530 (IST) From: Satyajeet Seth To: Mike Smith Cc: , Subject: Re: KLD'fying PCI device driver! In-Reply-To: <200102151014.f1FAEbV09259@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Please see my comments below: On Thu, 15 Feb 2001, Mike Smith wrote: > > I am trying to convert my PCI device driver into a KLD. > > > > So far I have done the following: > > 1. Built the kernel without the static linked device driver. > > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. > > 3. Did "make all install" in /sys/modules directory. > > 4. Tried loading the KLD. I got the following error: > > "Fatal trap 12: page fault while in kernel mode" > > > > Any ideas as to what could be going wrong? > > Too many. You haven't really given anything like enough detail here. > > - What FreeBSD version? Satya-> 4.0 > - Build the kernel with DDB and symbols, and show us the backtrace. Satya-> The trace is given below: (kgdb) where #0 0xc018cf3c in boot () #1 0xc018d2d9 in panic () #2 0xc0137c39 in db_panic () #3 0xc0137bd9 in db_command () #4 0xc0137c9e in db_command_loop () #5 0xc0139daf in db_trap () #6 0xc02c229d in kdb_trap () #7 0xc02d14b4 in trap_fatal () #8 0xc02d118d in trap_pfault () #9 0xc02d0cd3 in trap () #10 0xc01909a4 in sysctl_register_oid () #11 0xc0190a51 in sysctl_register_set () #12 0xc017f5d3 in linker_file_register_sysctls () #13 0xc017f670 in linker_load_file () #14 0xc017feae in kldload () #15 0xc02d1712 in syscall () #16 0xc02c2ba6 in Xint0x80_syscall () #17 0x80480f9 in ?? () > - Your hardware init function may not work properly in the case where > the system is already up and running (eg. you may be generating > interrupts before you are ready to handle them). > - You may be building against sources that don't match your running > kernel. Satya-> The driver works properly when statically linked. Thanks Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 6:15:36 2001 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 753) id B0F5A37B65D; Thu, 15 Feb 2001 06:15:33 -0800 (PST) Date: Thu, 15 Feb 2001 06:15:33 -0800 From: Adrian Chadd To: freebsd-net@freebsd.org Subject: vlan panics? Message-ID: <20010215061533.A68002@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm using the vlan code in FreeBSD-stable. I've discovered that on the fxp, if I ifconfig a vlan up without ifconfig'ing the parent interface (fxp) up, I'll get a panic. I don't have the bt handy at the moment but basically the codepath is bringing the vlan interface up, sending the gratuituous(sp)? arp request out the vlan interface, which sends it out the parent interface. The fxp code doesn't check whether the interface has been initialised when it attempts to queue a packet for outbound, and you get a panic. When I try the same thing on a machine with a tl interface it works fine. Now, I can hear people shouting "fix the fxp driver!", but I'm not sure that is the right solution. (However I do believe the fxp driver should have a check in there in any case.) I believe that if a vlan interface is attached to a device and configured up the device itself should also be configured up. This way the initial gratuituous(sp?) arp request will make it on to the wire. Opinions? Thanks! Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 7:33: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 88D6137B401 for ; Thu, 15 Feb 2001 07:32:57 -0800 (PST) Received: (qmail 28878 invoked by uid 666); 15 Feb 2001 15:45:10 -0000 Received: from i076-013.nv.iinet.net.au (HELO elischer.org) (203.59.76.13) by mail.m.iinet.net.au with SMTP; 15 Feb 2001 15:45:10 -0000 Message-ID: <3A8BF697.DE9D4C72@elischer.org> Date: Thu, 15 Feb 2001 07:32:39 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Satyajeet Seth Cc: "Andrew R. Reiter" , freebsd-net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: KLD'fying PCI device driver! References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satyajeet Seth wrote: > > Hi > > > Could you send the load handler function src? > > My code does not contain a load handler function. > > I did not add a load handler function, because none of the files in > /sys/pci directory like if_fxp.c, if_vr.c seemed to contain contain a load > handler function. > To the best of my knowledge, all the pci device driver modules use the > function pci_modevent() in /sys/pci/pci.c > > > > I am trying to convert my PCI device driver into a KLD. > > > > > > So far I have done the following: > > > 1. Built the kernel without the static linked device driver. > > > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. > > > 3. Did "make all install" in /sys/modules directory. > > > 4. Tried loading the KLD. I got the following error: > > > "Fatal trap 12: page fault while in kernel mode" > > > > > > Any ideas as to what could be going wrong? Assuming -current. (if 4.2, start with the one from -current) start with /usr/share/examples/drivers/make_device_driver.sh it at least compiles and loads. modify it to include your code.. > > Thanks > Satya > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 8:39: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id CE98C37B4EC; Thu, 15 Feb 2001 08:39:03 -0800 (PST) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id AAA24228; Fri, 16 Feb 2001 00:39:01 +0800 Received: from elischer.org (i076-013.nv.iinet.net.au [203.59.76.13]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id AAA16282; Fri, 16 Feb 2001 00:36:20 +0800 Message-ID: <3A8C0614.3131FB3@elischer.org> Date: Thu, 15 Feb 2001 08:38:44 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Adrian Chadd Cc: freebsd-net@FreeBSD.org Subject: Re: vlan panics? References: <20010215061533.A68002@hub.freebsd.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Adrian Chadd wrote: > > Hi, > > I'm using the vlan code in FreeBSD-stable. > > I've discovered that on the fxp, if I ifconfig a vlan up without > ifconfig'ing the parent interface (fxp) up, I'll get a panic. > I don't have the bt handy at the moment but basically the codepath > is bringing the vlan interface up, sending the gratuituous(sp)? arp > request out the vlan interface, which sends it out the parent interface. > The fxp code doesn't check whether the interface has been initialised > when it attempts to queue a packet for outbound, and you get a panic. > > When I try the same thing on a machine with a tl interface it works > fine. > > Now, I can hear people shouting "fix the fxp driver!", but I'm not > sure that is the right solution. (However I do believe the fxp > driver should have a check in there in any case.) > > I believe that if a vlan interface is attached to a device and configured > up the device itself should also be configured up. This way the initial > gratuituous(sp?) arp request will make it on to the wire. there's an fxp-Vlan patch floating around somewhere. > > Opinions? > > Thanks! > > Adrian > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 11:21: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id D576837B67D for ; Thu, 15 Feb 2001 11:20:56 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f1FJKuG28946; Thu, 15 Feb 2001 11:20:56 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102151920.f1FJKuG28946@iguana.aciri.org> Subject: etherboot on a hard disk howto ? To: net@freebsd.org Date: Thu, 15 Feb 2001 11:20:56 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, does anyone know how to install etherboot onto a hard disk instead of a floppy ? Plainly copying the floppy image into a slice does not seem to work (the boot manager does not even let you choose it, despite it lists the slice as accessible). cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 15: 8:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D1F2537B67D; Thu, 15 Feb 2001 15:08:36 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f1FN97w00534; Thu, 15 Feb 2001 15:09:07 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200102152309.f1FN97w00534@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Satyajeet Seth Cc: freebsd-net@freebsd.org, hackers@freebsd.org Subject: Re: KLD'fying PCI device driver! In-reply-to: Your message of "Thu, 15 Feb 2001 18:50:27 +0530." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Feb 2001 15:09:07 -0800 From: Mike Smith Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I am trying to convert my PCI device driver into a KLD. > > > > > > So far I have done the following: > > > 1. Built the kernel without the static linked device driver. > > > 2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx. > > > 3. Did "make all install" in /sys/modules directory. > > > 4. Tried loading the KLD. I got the following error: > > > "Fatal trap 12: page fault while in kernel mode" > > > > > > Any ideas as to what could be going wrong? > > > > Too many. You haven't really given anything like enough detail here. > > > > - What FreeBSD version? > > Satya-> 4.0 > > > - Build the kernel with DDB and symbols, and show us the backtrace. > Satya-> The trace is given below: > > #9 0xc02d0cd3 in trap () > #10 0xc01909a4 in sysctl_register_oid () > #11 0xc0190a51 in sysctl_register_set () > #12 0xc017f5d3 in linker_file_register_sysctls () > #13 0xc017f670 in linker_load_file () > #14 0xc017feae in kldload () > #15 0xc02d1712 in syscall () > #16 0xc02c2ba6 in Xint0x80_syscall () > #17 0x80480f9 in ?? () Ok. It looks like you have some sysctls in your driver. Comment them all out, then un-comment them one at a time, rebuilding and reloading until you find the one that causes the trap. Then we can have a look at it and see if we can work out what's wrong with it. > > - Your hardware init function may not work properly in the case where > > the system is already up and running (eg. you may be generating > > interrupts before you are ready to handle them). > > - You may be building against sources that don't match your running > > kernel. > Satya-> The driver works properly when statically linked. Yes, I was assuming this. At the moment, you're not even getting your module fully loaded; it's dying during the load phase. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 15:17:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from ambrisko.com (adsl-216-103-208-74.dsl.snfc21.pacbell.net [216.103.208.74]) by hub.freebsd.org (Postfix) with ESMTP id 94A3937B401 for ; Thu, 15 Feb 2001 15:17:42 -0800 (PST) Received: (from ambrisko@localhost) by ambrisko.com (8.11.2/8.11.1) id f1FNHRo13180; Thu, 15 Feb 2001 15:17:27 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200102152317.f1FNHRo13180@ambrisko.com> Subject: Re: etherboot on a hard disk howto ? In-Reply-To: <200102151920.f1FJKuG28946@iguana.aciri.org> "from Luigi Rizzo at Feb 15, 2001 11:20:56 am" To: Luigi Rizzo Date: Thu, 15 Feb 2001 15:17:27 -0800 (PST) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo writes: | Hi, | does anyone know how to install etherboot onto a hard disk instead | of a floppy ? | | Plainly copying the floppy image into a slice does not seem | to work (the boot manager does not even let you choose it, despite | it lists the slice as accessible). Unfortunately this is a re-direct. You could try to send this question to etherboot-developers@lists.sourceforge.net someone might come up with an answer since it is not FreeBSD specific. The other thing you could look at is grub. I see there is a grub in ports (don't know how current) grub uses Etherboot's drivers for it's netboot. I haven't tried it to netboot FreeBSD but that might help or give clues. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 19:11: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from web3301.mail.yahoo.com (web3301.mail.yahoo.com [204.71.201.24]) by hub.freebsd.org (Postfix) with SMTP id 749BD37B4EC for ; Thu, 15 Feb 2001 19:11:04 -0800 (PST) Message-ID: <20010216031103.9300.qmail@web3301.mail.yahoo.com> Received: from [12.22.60.1] by web3301.mail.yahoo.com; Thu, 15 Feb 2001 19:11:03 PST Date: Thu, 15 Feb 2001 19:11:03 -0800 (PST) From: Howard Lin Subject: Do I need to run RouteD/GateD? To: freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there, I am trying to set up a simple net work at home. Here is my exisiting setup: 1) I have a DSL router which does NAT which everyone on the LAN connects to. The address for the DSL router is 1.2.3.1 2) Everyone on the LAN connects to the router and uses 1.2.3.1 as gateway (net mast 255.255.255.0) 3) I have a FreeBSD box (1.2.3.10), which I have my mail server, webserver, and other goodies on it, which everyone is happily connected to. 4) I set up DHCPD already, so everyone is getting their addresses in the range I specified. Now, I want to use my FreeBSD box as a public wireless base station using Orinoco card (wi0). In theory, everyone close to me can connect to the wireless interface. So, here is what I am thinking about doing: 1) I have recompiled my BSD box with ipfw on, and ipfw working, and I have set "gateway_enable=YES" in my rc.conf 2) I want to take my laptop and connect to my BSD box wirelessly and get address from the DHCPD, and I want to be able to access all the resource on my wired LAN. e.g. the mail server, webserver, or chat with another person on the wired LAN. 3) I am semi paranoid about all the hackers in my neighborhood, so, I want to use IPFW on some of the traffic from my wireless interface. And since IPFW can ony block base on IP addresses, not ETHERNET address, this basically forced me to use DHCPD to assign FIXED ADDRESS to known ETHERNET ADDRESS. (this makes DHCPD looks like an overkill.) So, now I can finally use IPFW rules to block evil traffics from the wireless interface So, finally, my question: on the wireless side, everyone uses the FREEBSD as the gateway, so I can see the traffic can go from wireless side->FreeBSD->DSL Router->Internet. But, how about coming back? Do I need to run routed, or gated so that everyone on the wired LAN knows to use the BSD box as a router? How does the DSL router know how to send packets back to the wireless side? Thanks, Howard P.S : Any good security suggestions are welcomed as well. :) __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 20:30:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from ceasefire.bitstream.net (ceasefire.bitstream.net [216.243.128.220]) by hub.freebsd.org (Postfix) with SMTP id DCB2237B491 for ; Thu, 15 Feb 2001 20:30:12 -0800 (PST) Received: (qmail 55270 invoked from network); 16 Feb 2001 04:30:11 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by ceasefire with SMTP; 16 Feb 2001 04:30:11 -0000 Date: Thu, 15 Feb 2001 22:22:05 -0600 (CST) From: Dan Debertin To: "net@freebsd.org" Subject: buffer problems with ep Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a busy 4.1.1-RELEASE nfs server that stops responding at its ep interface every hour or so. Pings to hosts on that network respond with "sendto: no buffer space available". I've recompiled with MAXUSERS up at 128 and NMBCLUSTERS at 32768, both of which seem plenty high. The problem goes away, to return an hour later, after a quick 'ifconfig ep0 down; ifconfig ep0 up'. Other people seem to have run into this problem as well, but there is no sign of a fix in the archives anywhere. Here's netstat -m when it's working: 194/320/131072 mbufs in use (current/peak/max): 179 mbufs allocated to data 1 mbufs allocated to packet headers 14 mbufs allocated to fragment reassembly queue headers 176/254/32768 mbuf clusters in use (current/peak/max) 588 Kbytes allocated to network (68% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines and when it isn't: 172/320/131072 mbufs in use (current/peak/max): 134 mbufs allocated to data 38 mbufs allocated to packet headers 52/254/32768 mbuf clusters in use (current/peak/max) 588 Kbytes allocated to network (25% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Thanks for any help you an render, Dan Debertin -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 21:19:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 1F72337B491 for ; Thu, 15 Feb 2001 21:19:46 -0800 (PST) Received: from jehovah ([24.202.203.190]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G8U43X04.X5E; Fri, 16 Feb 2001 00:19:09 -0500 Message-ID: <002301c097d8$4b9f6000$becbca18@jehovah> From: "Bosko Milekic" To: "Dan Debertin" , "net@freebsd.org" References: Subject: Re: buffer problems with ep Date: Fri, 16 Feb 2001 00:21:19 -0500 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dan Debertin wrote: > I have a busy 4.1.1-RELEASE nfs server that stops responding at its ep > interface every hour or so. Pings to hosts on that network respond with > "sendto: no buffer space available". I've recompiled with MAXUSERS up at > 128 and NMBCLUSTERS at 32768, both of which seem plenty high. The problem > goes away, to return an hour later, after a quick 'ifconfig ep0 down; > ifconfig ep0 up'. > > Other people seem to have run into this problem as well, but > there is no sign of a fix in the archives anywhere. Can you try placing a "#define EP_LOCAL_STATS" at the _top_ of if_epvar.h and rebuilding+reinstalling the ep driver? See if you get anything printed to the console from the ep driver. If you get something that begins with "Status:" then look under it for "NOMB=" and take note of it. > Here's netstat -m when it's working: > > 194/320/131072 mbufs in use (current/peak/max): > 179 mbufs allocated to data > 1 mbufs allocated to packet headers > 14 mbufs allocated to fragment reassembly queue headers > 176/254/32768 mbuf clusters in use (current/peak/max) > 588 Kbytes allocated to network (68% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > and when it isn't: > 172/320/131072 mbufs in use (current/peak/max): > 134 mbufs allocated to data > 38 mbufs allocated to packet headers > 52/254/32768 mbuf clusters in use (current/peak/max) > 588 Kbytes allocated to network (25% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > Thanks for any help you an render, > > Dan Debertin > -- > ++ Unix is the worst operating system, except for all others. > > ++ Dan Debertin > ++ Senior Systems Administrator > ++ Bitstream Underground, LLC > ++ airboss@bitstream.net > ++ (612)321-9290 x108 > ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 Regards, Bosko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Feb 15 21:38:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from barabas.bitstream.net (barabas.bitstream.net [216.243.128.159]) by hub.freebsd.org (Postfix) with SMTP id 9A16A37B401 for ; Thu, 15 Feb 2001 21:38:43 -0800 (PST) Received: (qmail 32181 invoked from network); 16 Feb 2001 05:38:42 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by barabas with SMTP; 16 Feb 2001 05:38:42 -0000 Date: Thu, 15 Feb 2001 23:30:35 -0600 (CST) From: Dan Debertin To: Bosko Milekic Cc: "net@freebsd.org" Subject: Re: buffer problems with ep In-Reply-To: <002301c097d8$4b9f6000$becbca18@jehovah> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 16 Feb 2001, Bosko Milekic wrote: > Can you try placing a "#define EP_LOCAL_STATS" at the _top_ of > if_epvar.h and rebuilding+reinstalling the ep driver? See if you get > anything printed to the console from the ep driver. If you get > something that begins with "Status:" then look under it for > "NOMB=" and take note of it. Sure thing. Here's what I get when I add that #define: ../../dev/ep/if_ep.c: In function `ep_attach': ../../dev/ep/if_ep.c:325: structure has no member named `rx_bpf_disc' ../../dev/ep/if_ep.c: In function `ep_intr': ../../dev/ep/if_ep.c:591: warning: int format, long int arg (arg 2) ../../dev/ep/if_ep.c:591: warning: int format, long int arg (arg 3) and then an abort. I'm going to make clean and give it another go, though. Dan Debertin -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 6:17:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from ceasefire.bitstream.net (ceasefire.bitstream.net [216.243.128.220]) by hub.freebsd.org (Postfix) with SMTP id 2B42B37B4EC for ; Fri, 16 Feb 2001 06:17:49 -0800 (PST) Received: (qmail 70552 invoked from network); 16 Feb 2001 14:17:43 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by ceasefire with SMTP; 16 Feb 2001 14:17:43 -0000 Date: Fri, 16 Feb 2001 08:09:34 -0600 (CST) From: Dan Debertin To: Bosko Milekic Cc: "net@freebsd.org" Subject: Re: buffer problems with ep In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 15 Feb 2001, Dan Debertin wrote: > Sure thing. Here's what I get when I add that #define: > > ../../dev/ep/if_ep.c: In function `ep_attach': > ../../dev/ep/if_ep.c:325: structure has no member named `rx_bpf_disc' > ../../dev/ep/if_ep.c: In function `ep_intr': > ../../dev/ep/if_ep.c:591: warning: int format, long int arg (arg 2) > ../../dev/ep/if_ep.c:591: warning: int format, long int arg (arg 3) > > and then an abort. I'm going to make clean and give it another go, though. Bosko, make clean didn't change anything. It looks like the line in question, sc->rx_no_first = sc->rx_no_mbuf = sc->rx_bpf_disc = sc->rx_overrunf = sc->rx_overrunl = sc->tx_underrun = 0; is just zeroing these out, so I removed sc->rx_bpf_disc, and it compiled fine. However, no Status: messages (or messages of any kind) on the console or anywhere. Let me know if there's anything else I can do to help find the problem. Thanks, Dan Debertin -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 6:52:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from ceasefire.bitstream.net (ceasefire.bitstream.net [216.243.128.220]) by hub.freebsd.org (Postfix) with SMTP id 50E9F37B4EC for ; Fri, 16 Feb 2001 06:52:34 -0800 (PST) Received: (qmail 85501 invoked from network); 16 Feb 2001 14:52:26 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by ceasefire with SMTP; 16 Feb 2001 14:52:26 -0000 Date: Fri, 16 Feb 2001 08:44:16 -0600 (CST) From: Dan Debertin To: Bosko Milekic Cc: "net@freebsd.org" Subject: Re: buffer problems with ep In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Okay, one more clue. When it's working, the interface flags are as follows: flags=8843 mtu 1500 And when it stops, the OACTIVE flag is added: flags=8c43 mtu 1500 Dan Debertin -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 7:39:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57]) by hub.freebsd.org (Postfix) with ESMTP id 53F0137B4EC for ; Fri, 16 Feb 2001 07:39:05 -0800 (PST) Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com; Fri, 16 Feb 2001 10:11:54 -0500 Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <1MM3L7RC>; Fri, 16 Feb 2001 10:11:56 -0500 Message-ID: From: "Matthew Koivisto" To: "'freebsd-net@freebsd.org'" Subject: Disabling IPv6 on a single interface Date: Fri, 16 Feb 2001 10:11:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0982A.CA6EC7C0" X-Orig: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0982A.CA6EC7C0 Content-Type: text/plain; charset="iso-8859-1" Does anyone know how to disable IPv6 on a single interface, but leave the other interfaces IPv6 enabled? Is this even possible under freeBSD 4.2? Thanks, Matt ------_=_NextPart_001_01C0982A.CA6EC7C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Disabling IPv6 on a single interface

Does = anyone know how to disable IPv6 on a single interface, but leave the = other interfaces IPv6 enabled? Is this even possible under freeBSD 4.2?

Thanks,

Matt

------_=_NextPart_001_01C0982A.CA6EC7C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 7:58:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 6558537B67D for ; Fri, 16 Feb 2001 07:58:14 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id AAA21002; Sat, 17 Feb 2001 00:49:57 +0900 (JST) To: "Matthew Koivisto" Cc: "'freebsd-net@freebsd.org'" In-reply-to: mkoivist's message of Fri, 16 Feb 2001 10:11:51 EST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Disabling IPv6 on a single interface From: itojun@iijlab.net Date: Sat, 17 Feb 2001 00:49:57 +0900 Message-ID: <21000.982338597@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Does anyone know how to disable IPv6 on a single interface, but leave the >other interfaces IPv6 enabled? Is this even possible under freeBSD 4.2? I've sent you a reply to your message on snap-users@kame.net. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 17:59:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 0715937B491 for ; Fri, 16 Feb 2001 17:59:09 -0800 (PST) Received: (from cjsabatier@localhost) by cx344940-a.meta1.la.home.com (8.11.2/8.11.2) id f1H22IK53015 for freebsd-net@freebsd.org; Fri, 16 Feb 2001 20:02:18 -0600 (CST) (envelope-from cjsabatier) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 16 Feb 2001 20:02:18 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: freebsd-net@freebsd.org Subject: Using pppd to gateway another box via null modem serial line Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone offer some tips on how to go about setting up pppd to act as: 1) An address server, i.e. assigning an IP address to another machine connected via null modem to a serial port (ttyd0) 2) Providing a gateway for the null-modem connected box to enable it to connect to external (Internet) hosts I'm thinking the best way would be to edit the ttyd0 line in /etc/ttys, but I'm not sure what would be the best options to use. Authentication is not needed, as the only machine that will ever be connected to the serial port is local. I'm also not sure if any special routing setup is needed. And I'd like the connection to stay up as long as both machines are up. Thanks in advance for any help. -- Conrad Sabatier cjsabatier@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 21:43:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id A9BCE37B4EC for ; Fri, 16 Feb 2001 21:43:28 -0800 (PST) Received: (qmail 25827 invoked by uid 666); 17 Feb 2001 05:56:23 -0000 Received: from i079-180.nv.iinet.net.au (HELO elischer.org) (203.59.79.180) by mail.m.iinet.net.au with SMTP; 17 Feb 2001 05:56:23 -0000 Message-ID: <3A8E0F6B.B364EB77@elischer.org> Date: Fri, 16 Feb 2001 21:43:07 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Conrad Sabatier Cc: freebsd-net@freebsd.org Subject: Re: Using pppd to gateway another box via null modem serial line References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Conrad Sabatier wrote: > > Can anyone offer some tips on how to go about setting up pppd to act as: > > 1) An address server, i.e. assigning an IP address to another machine connected > via null modem to a serial port (ttyd0) pppd is fine, but ppp (a differnt program) has more features to allow what you want. > > 2) Providing a gateway for the null-modem connected box to enable it to connect > to external (Internet) hosts > > I'm thinking the best way would be to edit the ttyd0 line in /etc/ttys, but I'm > not sure what would be the best options to use. Authentication is not needed, > as the only machine that will ever be connected to the serial port is local. > I'm also not sure if any special routing setup is needed. And I'd like the > connection to stay up as long as both machines are up. > > Thanks in advance for any help. > > -- > Conrad Sabatier > cjsabatier@home.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 22:19:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id D519937B491 for ; Fri, 16 Feb 2001 22:19:41 -0800 (PST) Received: from jehovah ([24.202.203.190]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G8W1KT04.FZ2; Sat, 17 Feb 2001 01:19:41 -0500 Message-ID: <003a01c098a9$ec4da3a0$becbca18@jehovah> From: "Bosko Milekic" To: "Dan Debertin" Cc: "net@freebsd.org" References: Subject: Re: buffer problems with ep Date: Sat, 17 Feb 2001 01:21:54 -0500 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What type of card is this, exactly? (i.e. name, model number, etc.) There is some trickery in the NetBSD driver that involves "Vortex-based (3c59x pci, eisa) and Boomerang (3c900)" which allow FDDI-sized 4500 byte packets. According to the NetBSD driver's comments, these cards commands dealing with sizes (such as setting threshold, for example) upshift the size value by 2 bits in order to accomodate the full-size packet length (because the 11bits usually provided to store the command argument isn't enough to span the full length). If this may indeed be a problem, we can try right (down) shifting all the ORed in length values by 2 bits, thus expecting the card to interpret the lengths as whatever the value we or'ed in is << 2. If you have one of these cards, let me know and I'll send you a diff off-list. Regards, Bosko. Dan Debertin wrote: > Okay, one more clue. When it's working, the interface flags are as > follows: > > flags=8843 mtu 1500 > > And when it stops, the OACTIVE flag is added: > > flags=8c43 mtu 1500 > > Dan Debertin > -- > ++ Unix is the worst operating system, except for all others. > > ++ Dan Debertin > ++ Senior Systems Administrator > ++ Bitstream Underground, LLC > ++ airboss@bitstream.net > ++ (612)321-9290 x108 > ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Feb 16 22:50:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from barabas.bitstream.net (barabas.bitstream.net [216.243.128.159]) by hub.freebsd.org (Postfix) with SMTP id 76D0E37B65D for ; Fri, 16 Feb 2001 22:50:08 -0800 (PST) Received: (qmail 55712 invoked from network); 17 Feb 2001 06:50:03 -0000 Received: from unknown (HELO chicka) (216.243.128.155) by barabas with SMTP; 17 Feb 2001 06:50:03 -0000 Date: Sat, 17 Feb 2001 00:50:04 -0600 (CST) From: Dan Debertin To: Bosko Milekic Cc: "net@freebsd.org" Subject: Re: buffer problems with ep In-Reply-To: <003a01c098a9$ec4da3a0$becbca18@jehovah> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Feb 2001, Bosko Milekic wrote: > If you have one of these cards, let me know and I'll send you a diff > off-list. No, it's none of those; It's a 3c509 isa card. FWIW, I have six of them laying about, and they all display the same behavior. ~Dan D. -- ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 17 0:37:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from shell.youareata.org (youareata.org [209.99.47.122]) by hub.freebsd.org (Postfix) with ESMTP id E193937B4EC for ; Sat, 17 Feb 2001 00:37:54 -0800 (PST) Received: (from bsd-mail@localhost) by shell.youareata.org (8.11.1/8.11.1) id f1H6gPJ04521 for freebsd-net@freebsd.org; Sat, 17 Feb 2001 00:42:25 -0600 (CST) (envelope-from bsd-mail) Date: Sat, 17 Feb 2001 00:42:25 -0600 From: Michael Chavez To: freebsd-net@freebsd.org Subject: subscribe Message-ID: <20010217004225.E4488@youareata.org> Reply-To: Michael Chavez Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 17 5:48: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id C92E437B491 for ; Sat, 17 Feb 2001 05:47:58 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id TAA27061 for ; Sat, 17 Feb 2001 19:17:52 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Sat, 17 Feb 2001 19:17:51 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id TAA23244 for ; Sat, 17 Feb 2001 19:17:50 +0530 (IST) Date: Sat, 17 Feb 2001 19:17:50 +0530 (IST) From: Satyajeet Seth To: Subject: Using netgraph to implement pseudo interfaces Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I wished to implement pseudo interfaces with the following requirements: 1. There is a ethernet interface fxp0 having MAC address MAC0. It also receives packets with destination MAC address MAC1 and MAC2. 2. The packets with destination MAC address MAC1 are sent to a pseudo interface 1 and packets with destination MAC address MAC2 are sent to pseudo interface 2. 3. The packets addressed to MAC0 should be sent to sent to fxp0. I plan to design a netgraph as follows: iface1 / fxp0 <-> bpf \ iface2 fxp0, iface1, iface2, bpf are nodes of type ng_ether, ng_iface, ng_iface and ng_bpf respectively. The packets with destination addresses MAC1 and MAC2 are sent to interfaces iface1 and iface2 respectively by bpf. Remaining are sent to fxp0. Could you suggest some pitfalls/improvements in the above scheme? I am using FreeBSD 4.0. Thanks Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 17 8: 6:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 09C3537B491 for ; Sat, 17 Feb 2001 08:06:16 -0800 (PST) Received: (qmail 29476 invoked by uid 666); 17 Feb 2001 16:19:07 -0000 Received: from i091-059.nv.iinet.net.au (HELO elischer.org) (203.59.91.59) by mail.m.iinet.net.au with SMTP; 17 Feb 2001 16:19:07 -0000 Message-ID: <3A8EA162.559507D6@elischer.org> Date: Sat, 17 Feb 2001 08:05:54 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Satyajeet Seth Cc: net@freebsd.org Subject: Re: Using netgraph to implement pseudo interfaces References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satyajeet Seth wrote: > > Hi > > I wished to implement pseudo interfaces with the following requirements: > > 1. There is a ethernet interface fxp0 having MAC address MAC0. It also > receives packets with destination MAC address MAC1 and MAC2. > > 2. The packets with destination MAC address MAC1 are sent to a pseudo > interface 1 and packets with destination MAC address MAC2 are sent to > pseudo interface 2. > > 3. The packets addressed to MAC0 should be sent to sent to fxp0. > > I plan to design a netgraph as follows: > > iface1 > / > fxp0 <-> bpf > \ > iface2 > > fxp0, iface1, iface2, bpf are nodes of type ng_ether, ng_iface, ng_iface > and ng_bpf respectively. > > The packets with destination addresses MAC1 and MAC2 are sent to > interfaces iface1 and iface2 respectively by bpf. Remaining are sent to > fxp0. > > Could you suggest some pitfalls/improvements in the above scheme? should work, though 'ng_iface' nodes are 'point-to-point' nodes and as such do not support netmasks. you probably want to use the 'eiface' node which can be found at: http://www.riss-telecom.ru/~vitaly/ that node looks like an ethernet interface. I am not sure how the ARP side of things will work in your setup and I have a headache so I will not look at it now :-( > > I am using FreeBSD 4.0. 4.2 would be better of course, but netgraph is pretty similar.. > > Thanks > Satya > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Feb 17 11:48:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (Postfix) with ESMTP id 83E4E37B4EC; Sat, 17 Feb 2001 11:48:34 -0800 (PST) Received: from jardan.infowest.com (jardan.infowest.com [216.190.28.251]) by ns1.infowest.com (Postfix) with SMTP id 6194B2101A; Sat, 17 Feb 2001 12:48:32 -0700 (MST) From: Aaron D.Gifford To: freebsd-gnats-submit@FreeBSD.org, freebsd-net@freebsd.org Subject: Re: kern/22065: Patch to add support to ipfw for per rule overriding of dynamic keep-state rule expiration lifetimes Date: Sat, 17 Feb 2001 12:48:52 -0700 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01021712485208.38959@jardan.infowest.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Looks like this proposed patch (PR 22065) is still open. I suppose that means no one has decided whether it is useful or not, or (far more likely) folks are extremely busy doing other fun and useful stuff for FreeBSD. The patch in the PR is still mostly valid for FreeBSD 4.2-STABLE with a few line offset changes. I've got an updated version of the patch against 4.2-STABLE as of 17 FEB 2001 at the following web address: http://www.aarongifford.com/computers/ipfwpatch.html I have been using the patch successfully on several moderate-traffic hosts with no noticable problems. I do still have two questions that no one has yet answered. Still, it would be nice to know the following (with regard to the patch): 1. Am I safe using the union fw_un in the ip_fw structure (in ip_fw.h) to store the dynamic rule's lifetime setting or will this overlap with one of the other uses of that union and thus require that I modify the patch to create a new structure member for storing the setting? 2. Am I correct in assuming that in ip_fw.c at roughly line 800 where UDP and TCP matches to the dynamic rule extend the rule expiration by the dyn_syn_lifetime amount that this should instead only extend TCP matches by dyn_syn_lifetime and should extend UDP matches by dyn_short_lifetime instead? I believe this to be the case. The snippet of code from ip_fw.c in question looks like (beginning at line 800 of ip_fw.c as of FreeBSD 4.2-STABLE on 17 FEB 2001): } bzero (r, sizeof (*r) ); if (mask) r->mask = *mask ; r->id = *id ; r->expire = time_second + dyn_syn_lifetime ; /*<<chain = chain ; r->type = ((struct ip_fw_ext *)chain->rule)->dyn_type ; r->bucket = i ; r->next = ipfw_dyn_v[i] ; ipfw_dyn_v[i] = r ; dyn_count++ ; DEB(printf("-- add entry 0x%08x %d -> 0x%08x %d, %d left\n", (r->id.src_ip), (r->id.src_port), (r->id.dst_ip), (r->id.dst_port), dyn_count ); ) } I assume that the line above (flagged above with "<<expire = time_second + (r->id.proto == IPPROTO_TCP ? dyn_syn_lifetime : dyn_short_lifetime) ; My patch assumes that this is the case and modifies the behavior so that non-TCP rule match expiration lifetimes are incremented by the dyn_short_lifetime sysctl setting (if no per-rule lifetime is specified). I would appreciate any answers to the two above questions, question #1 in particular, as well as any other commentary or suggestions. Thanks, Aaron out. -- InfoWest, Inc. * 596 E. Tabernacle * St. George, UT 84790 Voice: 435-674-0165 * FAX: 435-674-9654 Web: www.infowest.com * E-mail: support@infowest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message