From owner-freebsd-net@FreeBSD.ORG Sun Oct 2 02:11:00 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D671416A41F for ; Sun, 2 Oct 2005 02:11:00 +0000 (GMT) (envelope-from dave-sender-1932b5@seddon.ca) Received: from seddon.ca (seddon.ca [203.209.212.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 0D62743D48 for ; Sun, 2 Oct 2005 02:10:59 +0000 (GMT) (envelope-from dave-sender-1932b5@seddon.ca) Received: (qmail 30147 invoked by uid 89); 2 Oct 2005 02:10:56 -0000 Received: by seddon.ca (tmda-sendmail, from uid 89); Sun, 02 Oct 2005 12:10:55 +1000 (EST) References: In-Reply-To: To: freebsd-net@freebsd.org Date: Sun, 02 Oct 2005 12:10:54 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit From: Dave+Seddon Message-ID: <1128219055.30071.TMDA@seddon.ca> X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) Subject: Re: tcpdump based packet generator X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: das-keyword-net.6770cb@seddon.ca List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 02:11:01 -0000 Greetings, Yes I was wondering about doing that the other day. I'd like to here how you go if you do get somewhere. Perhaps this is how the load generators work? I've been using one based on SmartBits, which seems to be linux. Dave Nickolay Kritsky writes: > combination of tcpdump and nemesis may do the trick > > Nick > > -----Original Message----- > From: det_re [mailto:det_re@yahoo.com] > Sent: Friday, September 30, 2005 7:53 AM > To: freebsd-net@freebsd.org > Subject: tcpdump based packet generator > > has anyone seen or implemented packet generator > capable of reading tcpdump trace file and resend the > packets back into the wire through bpf in freebsd box? > > > > > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun Oct 2 15:53:03 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AA416A41F; Sun, 2 Oct 2005 15:53:03 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mrout1-b.corp.dcn.yahoo.com (mrout1-b.corp.dcn.yahoo.com [216.109.112.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A67D43D5A; Sun, 2 Oct 2005 15:52:58 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1-b.corp.dcn.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j92FqYjU012051; Sun, 2 Oct 2005 08:52:34 -0700 (PDT) Date: Sun, 02 Oct 2005 16:52:38 +0100 Message-ID: From: gnn@FreeBSD.org To: Andre Oppermann In-Reply-To: <433ABC12.948DA54D@freebsd.org> References: <20050927222634.GA46375@xor.obsecurity.org> <20050928151319.GA27347@xor.obsecurity.org> <433ABC12.948DA54D@freebsd.org> User-Agent: Wanderlust/2.12.2 (99 Luftballons) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin8.1.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: SUZUKI Shinsuke , net@FreeBSD.org, Kris Kennaway Subject: Re: ipv6 panic in 6.0 ([kris@FreeBSD.org: kern/85780: 'panic:bogus refcnt 0' in routing/ipv6]) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 15:53:03 -0000 Hi, I am working, very slowly, through this bug, but in the hopes that others might know something and chime in the packet that caused this is an ICMPv6 packet for neighbor solicitation (type 135, code 0), directed at the machine which paniced, i.e. not broadcast or multicast and is attempting to look up a network route, or at least that's what it looks like. I say that it is looking up a network route because the target address portion of the packet includes only the first 8 bytes, which in this case are the 64 bits of prefix for the IPv6 network which the interface is on. I'll keep digging but figured I'd throw this out there to anyone who might have more clue. Later, George From owner-freebsd-net@FreeBSD.ORG Sun Oct 2 19:18:07 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBE6B16A41F for ; Sun, 2 Oct 2005 19:18:07 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C957843D48 for ; Sun, 2 Oct 2005 19:18:06 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j92JI486061836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Oct 2005 23:18:05 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j92JHxb2061835; Sun, 2 Oct 2005 23:17:59 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sun, 2 Oct 2005 23:17:59 +0400 From: Gleb Smirnoff To: Mao Shou Yan Message-ID: <20051002191759.GZ45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Mao Shou Yan , freebsd-net@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: problems with em(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 19:18:07 -0000 On Fri, Aug 12, 2005 at 01:48:59PM +0800, Mao Shou Yan wrote: M> I have a machine running 5.4 stable, with 3 em cards: M> M> (1) Two 82543GC with fiber M> M> (2) One 82544 M> M> All of them are shared irq 11( from vmstat -i) M> M> M> M> The problem is: M> M> After the system run about 3 hours, there will be large "Ierrs" M> with the em0(BTW, em0 is in promisc mode). M> M> I use "sysctl hw.em0.stats=1", found there are a lot of "missed M> packets" and some "Receive with no buffers". M> M> Em0 is in polling mode, and hz is 2000, burst_max and M> each_burst is the default value. M> M> The system is not heavy loaded, incoming rates of em0 is less M> than 150Mbits/s. em1 and em2 are not connected. M> M> And pps is less than 30k. M> M> After 3 hours, the ierrs raise quickly every 1 minutes! M> M> From pciconf, I found the driver version is "1.7.35". M> M> M> M> I think is a problem with em(4) driver. M> M> Anyone meet such condition? Do you have ip fastforwarding enabled? Do you use any firewall filtering or any other additional packet processing on your router? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Sun Oct 2 19:22:16 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36ED816A41F; Sun, 2 Oct 2005 19:22:16 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 772FA43D45; Sun, 2 Oct 2005 19:22:15 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j92JMDrW061863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Oct 2005 23:22:14 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j92JMDHw061862; Sun, 2 Oct 2005 23:22:13 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sun, 2 Oct 2005 23:22:13 +0400 From: Gleb Smirnoff To: noname , julian@FreeBSD.org Message-ID: <20051002192213.GA45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , noname , julian@FreeBSD.org, freebsd-net@freebsd.org References: <46a3a47205081415122806a653@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <46a3a47205081415122806a653@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: why ng_bridge does not like DHCP? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 19:22:16 -0000 On Mon, Aug 15, 2005 at 01:12:31AM +0300, noname wrote: n> freebsd 5.4 stable. xl0 is connected via ng_bridge to ngeth0 in this way: n> n> [root@asd:~]# ifconfig xl0 up n> [root@asd:~]# ngctl mkpeer . eiface hook ether n> [root@asd:~]# ifconfig ngeth0 up n> [root@asd:~]# ngctl mkpeer xl0: bridge lower link0 n> [root@asd:~]# ngctl name xl0:lower mybridge n> [root@asd:~]# ngctl connect ngeth0: mybridge: lower link1 n> [root@asd:~]# ngctl connect ngeth0: mybridge: upper link2 n> [root@asd:~]# ngctl msg xl0: setautosrc 0 n> [root@asd:~]# ngctl msg xl0: setpromisc 1 n> [root@asd:~]# ifconfig ngeth0 ether 00:12:12:12:12:12 n> [root@asd:~]# dhclient ngeth0 n> n> using tcpdump I can see dhcp request leaving from ngeth0, passing n> through xl0, dhcp reply comes back through xl0 but it doesn't reach n> ngeth0. Why? n> n> If I give ip-address with ifconfig, everything works fine. Also n> getting ip with dhcp to xl0, without touching netgraph works fine. Any n> clues? Do not use ngeth0: node. This is a ng_ether node, attached to Ethernet interface created by your ng_eiface. After your second command you have created ng_eiface node, and it is left unnamed. Then you use not correct node, but its ng_ether fantom. Probably we should add a protection to avoid ng_ether nodes autocreate theirselves attached to ng_eiface nodes. This is useless and confuses people. Julian, what do you think? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Sun Oct 2 22:14:37 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 733B316A41F for ; Sun, 2 Oct 2005 22:14:37 +0000 (GMT) (envelope-from dave-sender-1932b5@seddon.ca) Received: from seddon.ca (seddon.ca [203.209.212.18]) by mx1.FreeBSD.org (Postfix) with SMTP id A0DAA43D46 for ; Sun, 2 Oct 2005 22:14:36 +0000 (GMT) (envelope-from dave-sender-1932b5@seddon.ca) Received: (qmail 77110 invoked by uid 89); 2 Oct 2005 22:14:34 -0000 Received: by seddon.ca (tmda-sendmail, from uid 89); Mon, 03 Oct 2005 08:14:33 +1000 (EST) References: <20051002191759.GZ45345@cell.sick.ru> In-Reply-To: <20051002191759.GZ45345@cell.sick.ru> To: freebsd-net@FreeBSD.org Date: Mon, 03 Oct 2005 08:14:31 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit From: Dave+Seddon Message-ID: <1128291273.77082.TMDA@seddon.ca> X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) Cc: Subject: Re: problems with em(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: das-keyword-net.6770cb@seddon.ca List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 22:14:37 -0000 Greetings, > M> The problem is: > M> > M> After the system run about 3 hours, there will be large "Ierrs" > M> The system is not heavy loaded, incoming rates of em0 is less > M> than 150Mbits/s. em1 and em2 are not connected. > M> > M> After 3 hours, the ierrs raise quickly every 1 minutes! > M> > M> I think is a problem with em(4) driver. > M> > M> Anyone meet such condition? Yes. Lots of people. 3 hours does seem to be the magic number, regardless of the volumne of traffic. I'm interested in what you do sniffing 150MB/s. Normally libpcap can't handle that amount of traffic. Regards, Dave Seddon From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 06:37:57 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3907316A41F for ; Mon, 3 Oct 2005 06:37:57 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E6BF43D48 for ; Mon, 3 Oct 2005 06:37:56 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j936brID066837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 10:37:53 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j936brRF066836; Mon, 3 Oct 2005 10:37:53 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 10:37:52 +0400 From: Gleb Smirnoff To: Dominic Marks Message-ID: <20051003063752.GB45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Dominic Marks , freebsd-net@freebsd.org References: <4452.195.12.22.194.1126884783.squirrel@www.helenmarks.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4452.195.12.22.194.1126884783.squirrel@www.helenmarks.co.uk> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: Packet loss with ng_one2many X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 06:37:57 -0000 On Fri, Sep 16, 2005 at 04:33:03PM +0100, Dominic Marks wrote: D> I'm trying to use two gigabit links together using ng_one2many. D> D> I haven't done this before, so here is the environment: D> D> FreeBSD 6 system with four gigabit interfaces, two of the four are going D> to be used a single interface. I've attached em0 and em1 to a gigabit D> switch and read manual pages / googled for information on how to configure D> this. D> D> I have the following script to set things up: D> D> ngctl mkpeer em0: one2many upper one D> ngctl connect em0: em0:upper lower many0 D> ngctl connect em1: em0:upper lower many1 D> ngctl msg em1: setpromisc 1 D> ngctl msg em1: setautosrc 0 D> ngctl msg em0:upper \ D> setconfig "{ xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 ] }" D> D> I get 50% packet loss when using this. It seems to me like only the em0 D> interface is operating properly, although both NICs are connected and work D> alright without ng_one2many. D> D> Any clues as to what I am doing wrong / guides to implementation D> ng_one2many? Is this email related to my problem? Is your em1 interface UP? Have you configured trunk group on the switch? D> http://lists.freebsd.org/pipermail/freebsd-net/2005-February/006500.html May be. To make ng_one2many notice link state changes on Ethernet interfaces you need to set failAlg=2. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 06:39:17 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBEBA16A41F for ; Mon, 3 Oct 2005 06:39:17 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 138B843D45 for ; Mon, 3 Oct 2005 06:39:14 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j936d5iL066876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 10:39:06 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j936d0l3066875; Mon, 3 Oct 2005 10:39:00 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 10:39:00 +0400 From: Gleb Smirnoff To: n0g0013 Message-ID: <20051003063900.GC45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , n0g0013 , freebsd-net@freebsd.org References: <20050918003946.GM6440@eyore.cobbled.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20050918003946.GM6440@eyore.cobbled.net> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: the purpose/use of "opt_netgraph.h" ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 06:39:17 -0000 On Sun, Sep 18, 2005 at 01:39:46AM +0100, n0g0013 wrote: n> could anybody enlighten me as to the purpose of the "opt_netgraph.h" n> dependancy in a netgraph module? n> n> got some errors, added it to SRCS and it gets generated as an empty n> file. think there is a minimal one in "sr" driver but can't guess n> it's intent. It may define NETGRAPH_DEBUG. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 06:44:40 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3BD716A41F for ; Mon, 3 Oct 2005 06:44:40 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267EB43D4C for ; Mon, 3 Oct 2005 06:44:39 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j936icqI066942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 10:44:38 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j936icNA066941; Mon, 3 Oct 2005 10:44:38 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 10:44:37 +0400 From: Gleb Smirnoff To: ComteZero _ Message-ID: <20051003064437.GD45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , ComteZero _ , freebsd-net@freebsd.org References: <1d881b2f050914072350d79a65@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1d881b2f050914072350d79a65@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: PPPoE (STABLE 5) : two PADI packets emitted and then nothing... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 06:44:40 -0000 On Wed, Sep 14, 2005 at 04:23:30PM +0200, ComteZero _ wrote: C> Hello, C> C> I already posted this thread in freebsd-stable but seems that this list is C> more appropriate. C> C> it's been two weeks I try to find out what's wrong. Clean install from cvsup C> STABLE (5). C> my ADSL account works fine with REL. 4.4+rp_pppoe but not with my new STABLE C> (5) (without using rp_pppoe). C> could someone help me on this issue (logs provided here, ppp.log in attached C> file)... C> two PADI are emitted but nothing happens after. C> (i saw that someone had a similar problem, but with previous netgraph C> revisions). C> C> thank you. C> C> Since my ADSL modem is 3Com HomeConnect, I've set the C> net.graph.nonstandard_pppoe=1 This interface is deprecated in 5-STABLE. The correct way is to set this via ppp.conf. C> ng_pppoe.c rev. is 1.67.2.1 C> ng_socket.c rev. is 1.53.2.3 C> C> my ppp.conf is : C> default: C> set log all C> set ifaddr X.X.X.X/0 10.0.0.2/0 C> C> my_isp : C> set device PPPoE:xl0 C> set authname MY_USER C> set authkey MY_PWD C> set dial C> #set login C> add default HISADDR C> C> C> here is a tcpdump -vv -i xl0 : C> C> 18:48:40.808687 PPPoE PADI [Host-Uniq 0x00E654C1] C> 18:48:42.807533 PPPoE PADI [Host-Uniq 0x00E654C1] C> 18:51:44.010839 PPPoE PADI [Host-Uniq 0x40F195C1] C> 18:51:46.009639 PPPoE PADI [Host-Uniq 0x40F195C1] It is strange, that your box sends standard PPPoE packets. May be you have set net.graph.nonstandard_pppoe=1 _after_ starting ppp(8)? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 06:45:31 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3846916A41F for ; Mon, 3 Oct 2005 06:45:31 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C65F43D45 for ; Mon, 3 Oct 2005 06:45:30 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j936jS0s066978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 10:45:29 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j936jSkj066977; Mon, 3 Oct 2005 10:45:28 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 10:45:28 +0400 From: Gleb Smirnoff To: David Vos Message-ID: <20051003064528.GE45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , David Vos , freebsd-net@freebsd.org References: <16e39c510509191327197c2c44@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <16e39c510509191327197c2c44@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: ng_split.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 06:45:31 -0000 On Mon, Sep 19, 2005 at 02:27:11PM -0600, David Vos wrote: D> The version of ng_split.c packaged with 5.4 Release has a bug in it D> that causes items to get lost (not freed) if there are no nodes D> connected on the other end. D> D> This has been fixed in the CVS, Revision 1.7 D> D> Would it be possible to bring this 1.7 revision into FreeBSD 5.4 Release? We can't bring anything into release after one is shipped. We don't have a time machine, sorry. :) -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 07:19:00 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4360D16A41F for ; Mon, 3 Oct 2005 07:19:00 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EB7E43D46 for ; Mon, 3 Oct 2005 07:18:59 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru (8.13.0/vak/3.0) id j937FuZn049961 for freebsd-net@FreeBSD.org.checked; Mon, 3 Oct 2005 11:15:56 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from [144.206.181.94] (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru (8.13.0/vak/3.0) with ESMTP id j937FoWn049948; Mon, 3 Oct 2005 11:15:50 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <4340DAAF.1020509@cronyx.ru> Date: Mon, 03 Oct 2005 11:15:59 +0400 From: Roman Kurakin User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <16e39c510509191327197c2c44@mail.gmail.com> <20051003064528.GE45345@cell.sick.ru> In-Reply-To: <20051003064528.GE45345@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: David Vos , freebsd-net@FreeBSD.org Subject: Re: ng_split.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 07:19:00 -0000 Gleb Smirnoff wrote: >On Mon, Sep 19, 2005 at 02:27:11PM -0600, David Vos wrote: >D> The version of ng_split.c packaged with 5.4 Release has a bug in it >D> that causes items to get lost (not freed) if there are no nodes >D> connected on the other end. >D> >D> This has been fixed in the CVS, Revision 1.7 >D> >D> Would it be possible to bring this 1.7 revision into FreeBSD 5.4 Release? > >We can't bring anything into release after one is shipped. We don't have >a time machine, sorry. :) > > Gleb, is it on RELENG_5 ? rik From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 07:22:44 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 474FC16A41F for ; Mon, 3 Oct 2005 07:22:44 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DA1943D45 for ; Mon, 3 Oct 2005 07:22:43 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j937MWlI067851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 11:22:33 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j937MWHO067850; Mon, 3 Oct 2005 11:22:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 11:22:32 +0400 From: Gleb Smirnoff To: Roman Kurakin Message-ID: <20051003072232.GI45345@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Roman Kurakin , David Vos , freebsd-net@FreeBSD.org References: <16e39c510509191327197c2c44@mail.gmail.com> <20051003064528.GE45345@cell.sick.ru> <4340DAAF.1020509@cronyx.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4340DAAF.1020509@cronyx.ru> User-Agent: Mutt/1.5.6i Cc: David Vos , freebsd-net@FreeBSD.org Subject: Re: ng_split.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 07:22:44 -0000 On Mon, Oct 03, 2005 at 11:15:59AM +0400, Roman Kurakin wrote: R> >D> The version of ng_split.c packaged with 5.4 Release has a bug in it R> >D> that causes items to get lost (not freed) if there are no nodes R> >D> connected on the other end. R> >D> R> >D> This has been fixed in the CVS, Revision 1.7 R> >D> R> >D> Would it be possible to bring this 1.7 revision into FreeBSD 5.4 R> >Release? R> > R> >We can't bring anything into release after one is shipped. We don't have R> >a time machine, sorry. :) R> > R> > R> Gleb, is it on RELENG_5 ? Yes. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 09:16:21 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70C8716A41F for ; Mon, 3 Oct 2005 09:16:21 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C0043D48 for ; Mon, 3 Oct 2005 09:16:18 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id j939GGWc055168 for ; Mon, 3 Oct 2005 13:16:16 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id j939GGiP055167 for net@freebsd.org; Mon, 3 Oct 2005 13:16:16 +0400 (MSD) (envelope-from yar) Date: Mon, 3 Oct 2005 13:16:15 +0400 From: Yar Tikhiy To: net@freebsd.org Message-ID: <20051003091615.GB50141@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Cc: Subject: Easily fixable nge(4) issue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 09:16:21 -0000 Folks, Has anybody looked at kern/86618? It looks like a piece of cake. Yuriy, the originator, tells that nge(4) panics his RELENG_6 and HEAD systems, but adding M_ZERO to contigmalloc() flags at one spot in if_nge.c is enough to get rid of the trouble (patch included.) Yuriy and yours truly were communicating over a VLAN issue and he drew my attention to the PR, but unfortunately I don't have any nge(4) hardware. If there is consensus that the problem description and fix are correct, I can back the solution with my commit bit. -- Yar From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 10:32:06 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3791E16A41F for ; Mon, 3 Oct 2005 10:32:06 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BBA543D45 for ; Mon, 3 Oct 2005 10:32:04 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j93AVuIB044821 for ; Mon, 3 Oct 2005 12:31:57 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id D86E5228019 for ; Mon, 3 Oct 2005 12:31:56 +0200 (CEST) Message-ID: <4341089F.7010504@jku.at> Date: Mon, 03 Oct 2005 12:31:59 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 10:32:06 -0000 Hello All! We are using a 1.2GHz xSeries machine to do poor man's traffic shaping for the student hostels connected to our campus. We are using dummynet to do shaping, there is no stateful filtering, there are however several filter rules to lock out people and to do MAC based filtering. Number of users is ranging from several hundred up to 2-3000. We are running a recent 5.4-STABLE. The machine is fitted with two onboard Intel 100Mbit interfaces. One of the two was running on very high load (the internal interface acting as gateway for all of the hostels, where no shaping is done), so we put in a spare Intel Gbit card: em0@pci1:5:0: class=0x020000 card=0x10028086 chip=0x10268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82545GM Gigabit Ethernet Controller' Initial observations showed that the system had a very high interrupt load, most of the times > 50%, and lagged a little bit. Plus, performance-testing with tcpspray yielded bad results at around 10MB/s, or even worse. So we tried enabling device polling on the em0 interface. After some testing, we set HZ=1000 and kern.polling.burst_max: 300. This made things slightly better, our tcpspray tests now reaching a ~13MB/s throughput. However, now the input errors on the em0 interface were rapidly rising: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll em0 1500 00:0e:0c:6d:4c:f9 3738461290 8605788 3613603979 0 0 So for now, the polling is disabled again. On the mailing list, I have read about performance problems with the em driver, and problems with device polling as well. * are there any magic performance tips for use with the em driver? Any way to eliminate the input errors while using device polling? Or is all of this code too broken at the moment? * is there a driver by Intel which will work well? Has anyone tested such a driver with a network-performance hungry application? For now, the machine seems to run stable, no more errors with device polling disabled. But performance is far lower than it should be. :-( Kind regards and thanks for any input! -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 10:45:52 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBDBE16A41F for ; Mon, 3 Oct 2005 10:45:52 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A36843D45 for ; Mon, 3 Oct 2005 10:45:51 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j93AjnLQ071927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 14:45:49 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j93AjmOc071926; Mon, 3 Oct 2005 14:45:48 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 14:45:48 +0400 From: Gleb Smirnoff To: Ferdinand Goldmann Message-ID: <20051003104548.GB70355@cell.sick.ru> References: <4341089F.7010504@jku.at> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4341089F.7010504@jku.at> User-Agent: Mutt/1.5.6i Cc: net@FreeBSD.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 10:45:52 -0000 On Mon, Oct 03, 2005 at 12:31:59PM +0200, Ferdinand Goldmann wrote: F> Initial observations showed that the system had a very high interrupt load, F> most of the times > 50%, and lagged a little bit. Plus, performance-testing F> with tcpspray yielded bad results at around 10MB/s, or even worse. So we F> tried enabling device polling on the em0 interface. After some testing, we F> set HZ=1000 and kern.polling.burst_max: 300. This made things slightly F> better, our tcpspray tests now reaching a ~13MB/s throughput. F> F> However, now the input errors on the em0 interface were rapidly rising: F> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs F> Coll F> em0 1500 00:0e:0c:6d:4c:f9 3738461290 8605788 3613603979 F> 0 0 F> F> So for now, the polling is disabled again. All I can say: I have faced this problem, too. :( This is not problem in polling, but in em. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 11:02:30 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E93616A42A for ; Mon, 3 Oct 2005 11:02:30 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDFA043D5D for ; Mon, 3 Oct 2005 11:02:17 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j93B2H6v066329 for ; Mon, 3 Oct 2005 11:02:17 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j93B2GdE066323 for freebsd-net@freebsd.org; Mon, 3 Oct 2005 11:02:16 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 3 Oct 2005 11:02:16 GMT Message-Id: <200510031102.j93B2GdE066323@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 11:02:30 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations wit 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 12:29:43 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8D3516A41F; Mon, 3 Oct 2005 12:29:43 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F97243D45; Mon, 3 Oct 2005 12:29:42 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j93CTX7U072073; Mon, 3 Oct 2005 14:29:33 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id C7D31228019; Mon, 3 Oct 2005 14:29:32 +0200 (CEST) Message-ID: <4341242F.9060602@jku.at> Date: Mon, 03 Oct 2005 14:29:35 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: Gleb Smirnoff References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> In-Reply-To: <20051003104548.GB70355@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: net@FreeBSD.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 12:29:44 -0000 Gleb Smirnoff wrote: > All I can say: I have faced this problem, too. :( This is not problem in > polling, but in em. > Thank you! Just now I downloaded the driver from the Intel website; seems to compile fine, but I'll have to wait at least until tomorrow morning to test it. Do you have any experiences with the Intel driver? -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 12:32:13 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA35016A41F for ; Mon, 3 Oct 2005 12:32:13 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39AD743D46 for ; Mon, 3 Oct 2005 12:32:12 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j93CWAcs073262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 16:32:11 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j93CWANw073261; Mon, 3 Oct 2005 16:32:10 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 16:32:10 +0400 From: Gleb Smirnoff To: Ferdinand Goldmann Message-ID: <20051003123210.GF70355@cell.sick.ru> References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4341242F.9060602@jku.at> User-Agent: Mutt/1.5.6i Cc: net@FreeBSD.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 12:32:14 -0000 On Mon, Oct 03, 2005 at 02:29:35PM +0200, Ferdinand Goldmann wrote: F> Gleb Smirnoff wrote: F> F> >All I can say: I have faced this problem, too. :( This is not problem in F> >polling, but in em. F> > F> F> Thank you! Just now I downloaded the driver from the Intel website; seems F> to compile fine, but I'll have to wait at least until tomorrow morning to F> test it. F> F> Do you have any experiences with the Intel driver? Please share your results with community. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 13:07:38 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48AC816A4FE for ; Mon, 3 Oct 2005 13:07:38 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-3-1-cust208.cdif.cable.ntl.com [82.31.78.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEE0843D46 for ; Mon, 3 Oct 2005 13:07:37 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.53 (FreeBSD)) id 1EMQ2V-000Pmn-IJ; Mon, 03 Oct 2005 14:07:31 +0100 Date: Mon, 3 Oct 2005 14:07:31 +0100 From: Ceri Davies To: net@FreeBSD.org Message-ID: <20051003130731.GF56760@submonkey.net> Mail-Followup-To: Ceri Davies , net@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hoZxPH4CaxYzWscb" Content-Disposition: inline X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.11 Sender: Ceri Davies Cc: Subject: ng_tee, right2left, et al X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 13:07:38 -0000 --hoZxPH4CaxYzWscb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've discovered an application for which netgraph looks perfect, so have just started reading the docs whilst paying proper attention. I started out with ng_tee as it looked the simplest, but I've found myself confused already. The manpage for ng_tee says: Tee nodes have four hooks, right, left, right2left, and left2right. All data received on right is sent unmodified to both hooks left and right2left. Similarly, all data received on left is sent unmodified to both right and left2right. Packets may also be received on right2left and left2right; if so, they are forwarded unchanged out hooks right and left, respectively. Now that last bit looked wrong to me; I would have though that a packet received on right2left would be copied to left. Checking the code shows that the manpage is correct, though Archie Cobbs' article at http://ezine.daemonnews.org/200003/netgraph.html says that the opposite is true. Is this behaviour that was changed for some reason, or has it always been "wrong"? Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --hoZxPH4CaxYzWscb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDQS0TocfcwTS3JF8RAlKOAJ9GMSjNNfKzfVLkZpXpOgvrIpAUEwCfRFcJ TzljDgbsmBU1ntEzGw+rTuE= =L6UP -----END PGP SIGNATURE----- --hoZxPH4CaxYzWscb-- From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 13:41:37 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A4B816A420 for ; Mon, 3 Oct 2005 13:41:37 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89DC243D48 for ; Mon, 3 Oct 2005 13:41:35 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j93DfW0g074597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Oct 2005 17:41:33 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j93DfWqx074596; Mon, 3 Oct 2005 17:41:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 3 Oct 2005 17:41:32 +0400 From: Gleb Smirnoff To: Ceri Davies , net@FreeBSD.org Message-ID: <20051003134132.GE73935@cell.sick.ru> References: <20051003130731.GF56760@submonkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051003130731.GF56760@submonkey.net> User-Agent: Mutt/1.5.6i Cc: Subject: Re: ng_tee, right2left, et al X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 13:41:37 -0000 Ceri, On Mon, Oct 03, 2005 at 02:07:31PM +0100, Ceri Davies wrote: C> I've discovered an application for which netgraph looks perfect, so have C> just started reading the docs whilst paying proper attention. I started C> out with ng_tee as it looked the simplest, but I've found myself C> confused already. C> C> The manpage for ng_tee says: C> C> Tee nodes have four hooks, right, left, right2left, and left2right. C> All data received on right is sent unmodified to both hooks left and C> right2left. Similarly, all data received on left is sent unmodified C> to both right and left2right. C> C> Packets may also be received on right2left and left2right; if so, they C> are forwarded unchanged out hooks right and left, respectively. C> C> Now that last bit looked wrong to me; I would have though that a packet C> received on right2left would be copied to left. Checking the code shows C> that the manpage is correct, though Archie Cobbs' article at C> http://ezine.daemonnews.org/200003/netgraph.html says that the opposite C> is true. C> C> Is this behaviour that was changed for some reason, or has it always C> been "wrong"? I don't understand why you call current behavior wrong. I think that this is intuitive, that any packet received on "left side of the node" will be forwarded to hook right. As well as any packets received on "right side of the node" will be forwarded to hook left. I've checked Archie's article. What is said here is not true nowadays. You are right, before revision 1.17 of ng_tee.c the node treated l2r and r2l hooks counterwise. There is no comment, why Julian has changed the behavior. However, I agree with him. The current behavior is more intuitive. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 13:53:29 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EA1816A41F; Mon, 3 Oct 2005 13:53:29 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-3-1-cust208.cdif.cable.ntl.com [82.31.78.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFB0A43D62; Mon, 3 Oct 2005 13:53:27 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.53 (FreeBSD)) id 1EMQku-0008j3-93; Mon, 03 Oct 2005 14:53:24 +0100 Date: Mon, 3 Oct 2005 14:53:24 +0100 From: Ceri Davies To: Gleb Smirnoff Message-ID: <20051003135324.GH56760@submonkey.net> Mail-Followup-To: Ceri Davies , Gleb Smirnoff , net@FreeBSD.org References: <20051003130731.GF56760@submonkey.net> <20051003134132.GE73935@cell.sick.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ULyIDA2m8JTe+TiX" Content-Disposition: inline In-Reply-To: <20051003134132.GE73935@cell.sick.ru> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.11 Sender: Ceri Davies Cc: net@FreeBSD.org Subject: Re: ng_tee, right2left, et al X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 13:53:29 -0000 --ULyIDA2m8JTe+TiX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 03, 2005 at 05:41:32PM +0400, Gleb Smirnoff wrote: Hi Gleb, > On Mon, Oct 03, 2005 at 02:07:31PM +0100, Ceri Davies wrote: > C> I've discovered an application for which netgraph looks perfect, so ha= ve > C> just started reading the docs whilst paying proper attention. I start= ed > C> out with ng_tee as it looked the simplest, but I've found myself > C> confused already. > C>=20 > C> The manpage for ng_tee says: > C>=20 > C> Tee nodes have four hooks, right, left, right2left, and left2right. > C> All data received on right is sent unmodified to both hooks left and > C> right2left. Similarly, all data received on left is sent unmodified > C> to both right and left2right. > C>=20 > C> Packets may also be received on right2left and left2right; if so, they > C> are forwarded unchanged out hooks right and left, respectively. > C>=20 > C> Now that last bit looked wrong to me; I would have though that a packet > C> received on right2left would be copied to left. Checking the code sho= ws > C> that the manpage is correct, though Archie Cobbs' article at > C> http://ezine.daemonnews.org/200003/netgraph.html says that the opposite > C> is true. > C>=20 > C> Is this behaviour that was changed for some reason, or has it always > C> been "wrong"? >=20 > I don't understand why you call current behavior wrong. I think that this= is > intuitive, that any packet received on "left side of the node" will be > forwarded to hook right. As well as any packets received on "right side o= f the > node" will be forwarded to hook left. I only call it "wrong" as it didn't agree with Archie's article or my expectations, hence the quotes - I realise that it's subjective. It just seems to me that packets leaving left2right would go to right, as the name implies. I don't really mind either way, it's simply that I found it confusing. > I've checked Archie's article. What is said here is not true nowadays. Yo= u are > right, before revision 1.17 of ng_tee.c the node treated l2r and r2l hooks > counterwise. There is no comment, why Julian has changed the behavior. Ho= wever, > I agree with him. The current behavior is more intuitive. Perhaps as I learn more about it I will come to agree ;-) Thanks. Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --ULyIDA2m8JTe+TiX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDQTfUocfcwTS3JF8RAuvLAKCMvex6HAO3QGE/KrL5zojd0EG/8ACgnf54 Fy1kTWVdVKRcl6mLhG38LTU= =7q6h -----END PGP SIGNATURE----- --ULyIDA2m8JTe+TiX-- From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 15:31:13 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F22D316A41F; Mon, 3 Oct 2005 15:31:12 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from fep19.inet.fi (fep19.inet.fi [194.251.242.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF4F443D45; Mon, 3 Oct 2005 15:31:11 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [192.168.0.20] ([84.249.3.49]) by fep19.inet.fi with ESMTP id <20051003153110.LIZE20628.fep19.inet.fi@[192.168.0.20]>; Mon, 3 Oct 2005 18:31:10 +0300 Message-ID: <43414EBE.1060500@pp.nic.fi> Date: Mon, 03 Oct 2005 18:31:10 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 6.0-BETA5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-current@freebsd.org" , net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: send_query: No buffer space available X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 15:31:13 -0000 What should i do to avoid these messages from MRTG and dhclient? This happens with some network load on xl0 interface and pf+altq or ipfw+dummynet+statefull rules enabled, even with simple pass rules. Increasing kern.ipc.nmbclusters, kern.ipc.nsfbufs, kern.ipc.somaxconn and net.inet.tcp.sendspace doesn't seem to help. FreeBSD 5.3-RELEASE to 6.0-BETA5 have this problem. SNMP Error: send_query: No buffer space available dhclient: send_packet: No buffer space available netstat -m 1108/572/1680 mbufs in use (current/cache/total) 975/351/1326/17216 mbuf clusters in use (current/cache/total/max) 0/12/4560 sfbufs in use (current/peak/max) 2227K/845K/3072K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 94 requests for I/O initiated by sendfile 766 calls to protocol drain routines From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 19:17:06 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9336616A41F for ; Mon, 3 Oct 2005 19:17:06 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: from web30308.mail.mud.yahoo.com (web30308.mail.mud.yahoo.com [68.142.200.101]) by mx1.FreeBSD.org (Postfix) with SMTP id 1E7C243D46 for ; Mon, 3 Oct 2005 19:17:05 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 39156 invoked by uid 60001); 3 Oct 2005 19:17:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=BXPdPXK/JYn3PlPfTgGnbgIecY4re0HWRQAY5ARGSj0C7vn1Z4EBw5KpMrbd3jJmQ4OXy9Mw+Er/djg4BkNc54LGW+I0AjEhuXw1F7+PnB2huo+PJSDF+kjyYAtmAIAMXvzdswoSAyDS4hNmo73xrDIQrMttzs2vsmjXc8VHXmk= ; Message-ID: <20051003191704.39154.qmail@web30308.mail.mud.yahoo.com> Received: from [213.54.67.241] by web30308.mail.mud.yahoo.com via HTTP; Mon, 03 Oct 2005 12:17:04 PDT Date: Mon, 3 Oct 2005 12:17:04 -0700 (PDT) From: Arne "Wörner" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: pf / queue+stateful / r generated rules assigned to the right queue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 19:17:06 -0000 Hiho! I use pf. Since my server cannot process gracefully a 20Mb/s stream on one NIC, while ntpd (or ping) runs on the other NIC (round trip times increase from about 60msec to 300msec), I tried to limit the sporadic big data stream to not more than 9Mb/s. When I look at "pfctl -s queue -vv" it looks like, just one way is mentioned in the statistic, while the generated corresponding rule (I use "keep state") isn't a member of any queue, which would be a bug... I would be glad, if somebody could help me, 1. to understand this, 2. to do some tests, that make clear, if pf's queue implementation is buggy, and 3. to fix a problem, if there is a problem... :-)) Bye Arne ______________________________________________________ Yahoo! for Good Donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 20:47:04 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C945D16A41F for ; Mon, 3 Oct 2005 20:47:04 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 328E743D45 for ; Mon, 3 Oct 2005 20:47:03 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3DC90.dip.t-dialin.net [84.163.220.144] (helo=donor.laier.local) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKxQS-1EMXDA0yMB-0001Li; Mon, 03 Oct 2005 22:47:00 +0200 From: Max Laier To: freebsd-net@freebsd.org Date: Mon, 3 Oct 2005 22:46:43 +0200 User-Agent: KMail/1.8.2 References: <20051003191704.39154.qmail@web30308.mail.mud.yahoo.com> In-Reply-To: <20051003191704.39154.qmail@web30308.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2469819.RaaeHssqsM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510032246.57786.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Arne =?utf-8?q?W=F6rner?= Subject: Re: pf / queue+stateful / r generated rules assigned to the right queue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 20:47:04 -0000 --nextPart2469819.RaaeHssqsM Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Arne, On Monday 03 October 2005 21:17, Arne W=F6rner wrote: > Since my server cannot process gracefully a 20Mb/s stream on one > NIC, while ntpd (or ping) runs on the other NIC (round trip times > increase from about 60msec to 300msec), I tried to limit the > sporadic big data stream to not more than 9Mb/s. it is impossible to limit incoming traffic! In order to limit this, you ne= ed=20 to queue on a gateway "in front" of the server. > When I look at "pfctl -s queue -vv" it looks like, just one way is > mentioned in the statistic, while the generated corresponding rule > (I use "keep state") isn't a member of any queue, which would be a > bug... I have problems to understand what you are saying here. Keep some things i= n=20 mind: 1) One can only queue *OUT*going traffic 2) All unclassified outgoing traffic ends up in the default queue 3) Don't forget about 1) I might, however, completely misunderstand you problem/question. In any ca= se=20 you could try to take this to freebsd-pf@ which is a more specialized=20 mailinglist. The people there can certainly help you with your setup. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2469819.RaaeHssqsM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDQZjBXyyEoT62BG0RAsiSAJ46W2m15+BXhFwsm5ptNlNnsG+oxACeNzYF BehDWg7lt4S+An1Z8wn5M6Q= =aYt1 -----END PGP SIGNATURE----- --nextPart2469819.RaaeHssqsM-- From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 21:21:34 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D94FD16A420 for ; Mon, 3 Oct 2005 21:21:34 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: from web30310.mail.mud.yahoo.com (web30310.mail.mud.yahoo.com [68.142.200.103]) by mx1.FreeBSD.org (Postfix) with SMTP id 4DDF543D48 for ; Mon, 3 Oct 2005 21:21:34 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 84977 invoked by uid 60001); 3 Oct 2005 21:21:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hQUuKVx6txhkLBTnqFUCzRQzZhAEb1Tju5Vh77FBWZFv5CHocKaUvF0sIYsDLWOJWYFxz65D7fuRmxh4vUiMRWwNvL7hSZhP/hJ+ukF1Yirz+5pwqQQNwM3UOiz4zufn54UJiW3KhOXkVqeBVSbb0kOmqdsSBMSqEdRELwZRsnc= ; Message-ID: <20051003212133.84975.qmail@web30310.mail.mud.yahoo.com> Received: from [213.54.67.241] by web30310.mail.mud.yahoo.com via HTTP; Mon, 03 Oct 2005 14:21:33 PDT Date: Mon, 3 Oct 2005 14:21:33 -0700 (PDT) From: Arne "Wörner" To: Max Laier , freebsd-net@freebsd.org In-Reply-To: <200510032246.57786.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: pf / queue+stateful / r generated rules assigned to the right queue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 21:21:35 -0000 Dear Max, Thank u for ur answer... --- Max Laier wrote: > 1) One can only queue *OUT*going traffic > 2) All unclassified outgoing traffic ends up in the default > queue > 3) Don't forget about 1) > Hmm... Isn't it possible to tell the sender of a stream to slow down? In case of TCP I could think of a quite easy way to do so: 1. ipfw does it... 2. I would just delay the processing of the packet by the packet filter after the apropriate rule has been identified as long as necessary to reach the right bandwidth ratio... 3. Right now I did it with ipfw... Seems to work... Although it looks like up to 20 packets are waiting for the right bandwidth... Maybe the server even re-sends some packets, when the TCP-handshaking is missed? So I should do the traffic shaping on the server side? Since this seems to be more TCP/IP related, I would like to keep this in the -net@ list... Bye Arne __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 21:44:59 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D58D916A41F for ; Mon, 3 Oct 2005 21:44:59 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 439B243D45 for ; Mon, 3 Oct 2005 21:44:59 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j93Liw3h008594; Mon, 3 Oct 2005 14:44:58 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j93Liv3M008593; Mon, 3 Oct 2005 14:44:57 -0700 (PDT) (envelope-from jmg) Date: Mon, 3 Oct 2005 14:44:57 -0700 From: John-Mark Gurney To: Arne =?iso-8859-1?Q?W=F6rner?= Message-ID: <20051003214457.GM716@funkthat.com> Mail-Followup-To: Arne =?iso-8859-1?Q?W=F6rner?= , Max Laier , freebsd-net@freebsd.org References: <200510032246.57786.max@love2party.net> <20051003212133.84975.qmail@web30310.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051003212133.84975.qmail@web30310.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Max Laier , freebsd-net@freebsd.org Subject: Re: pf / queue+stateful / r generated rules assigned to the right queue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 21:44:59 -0000 Arne Wrner wrote this message on Mon, Oct 03, 2005 at 14:21 -0700: > Thank u for ur answer... > > --- Max Laier wrote: > > 1) One can only queue *OUT*going traffic > > 2) All unclassified outgoing traffic ends up in the default > > queue > > 3) Don't forget about 1) > > > Hmm... > > Isn't it possible to tell the sender of a stream to slow down? > > In case of TCP I could think of a quite easy way to do so: > 1. ipfw does it... > 2. I would just delay the processing of the packet by the packet > filter after the apropriate rule has been identified as long as > necessary to reach the right bandwidth ratio... > 3. Right now I did it with ipfw... Seems to work... Although it > looks like up to 20 packets are waiting for the right bandwidth... > Maybe the server even re-sends some packets, when the > TCP-handshaking is missed? > > So I should do the traffic shaping on the server side? > > Since this seems to be more TCP/IP related, I would like to keep > this in the -net@ list... I have written a python script using divert sockets will only pass ack's to achieve the specified download rate... The problem with this is that it won't take into account retransmits, etc, but I feel it's acceptable.. It also will limit uploads, it won't reorder packets, so ack's have zero value against your upload rate, and upload's that don't ack data have zero value against the download rate... so, an example ./ratelimit.py -p 38345 -m 65536 -a $((128*1024)) -m 32768 -u 65536 & ipfw add divert 38345 tcp from any to any out xmit sk0 The -p sets the divert port, and the -m sets the queue depth of the next -a (ack) or -u (upload) stage... I've uploaded the scripts to: http://people.FreeBSD.org/~jmg/ratelimit/ You do need Dug Song's dpkt, though I'm not sure if 1.2 fixed the tcp checksum bug that was in 1.1 (or if it's even necessary since I'm not modifing the packet). -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 02:50:12 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1903116A420 for ; Tue, 4 Oct 2005 02:50:12 +0000 (GMT) (envelope-from david.vos@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C70143D45 for ; Tue, 4 Oct 2005 02:50:09 +0000 (GMT) (envelope-from david.vos@gmail.com) Received: by wproxy.gmail.com with SMTP id i21so227626wra for ; Mon, 03 Oct 2005 19:50:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gKI3TPgENTnG5PTB1jNGuYP8J8SFN26o2g16IsNc7P3my2NZ+35EelkOIb5Etxh0Iwo9ogB7Nhsn5ZserdR3zhnZwAZiZuRn8Jtj3mui6yvVQO+RqR1SS9uStqMPE6chijVzMWBNvpHruxIZywDCU0Tzkv/JoaYIfZZyYpd8mDU= Received: by 10.54.126.19 with SMTP id y19mr1939111wrc; Mon, 03 Oct 2005 19:50:08 -0700 (PDT) Received: by 10.54.98.2 with HTTP; Mon, 3 Oct 2005 19:50:08 -0700 (PDT) Message-ID: <16e39c510510031950x3c73009bo47b07b31424cef78@mail.gmail.com> Date: Mon, 3 Oct 2005 20:50:08 -0600 From: David Vos To: freebsd-net@freebsd.org In-Reply-To: <20051003072232.GI45345@cell.sick.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <16e39c510509191327197c2c44@mail.gmail.com> <20051003064528.GE45345@cell.sick.ru> <4340DAAF.1020509@cronyx.ru> <20051003072232.GI45345@cell.sick.ru> Subject: Re: ng_split.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Vos List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 02:50:12 -0000 On 10/3/05, Gleb Smirnoff wrote: > R> Gleb, is it on RELENG_5 ? > > Yes. That's what I meant. Either it wasn't marked as such when I checked, or I just didn't see it (quite possible). Thanks. David From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 03:28:28 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 885A716A41F for ; Tue, 4 Oct 2005 03:28:28 +0000 (GMT) (envelope-from ddg@yan.com.br) Received: from zeus.yan.com.br (zeus.yan.com.br [200.202.253.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 475FB43D5A for ; Tue, 4 Oct 2005 03:28:24 +0000 (GMT) (envelope-from ddg@yan.com.br) Received: (qmail 22207 invoked by uid 1023); 4 Oct 2005 03:28:12 -0000 Received: from ddg@yan.com.br by zeus by uid 1023 with qmail-scanner-1.22 (uvscan: v4.1.60/v4366. fsecure: 4.11/3190/2003-09-23/2002-12-17. 2003-09-22/. Clear:RC:1(200.243.216.34):. Processed in 0.489591 secs); 04 Oct 2005 03:28:12 -0000 Received: from unknown (HELO ?192.168.0.240?) (daniel@dgnetwork.com.br@200.243.216.34) by zeus.yan.com.br with SMTP; 4 Oct 2005 03:28:11 -0000 Message-ID: <4341F6D2.3020301@yan.com.br> Date: Tue, 04 Oct 2005 00:28:18 -0300 From: =?UTF-8?B?RGFuaWVsIERpYXMgR29uw6dhbHZlcw==?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: pt-br, pt MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org, freebsd-net@freebsd.org References: <433AE838.4000606@yan.com.br> <20051002190231.GY45345@cell.sick.ru> In-Reply-To: <20051002190231.GY45345@cell.sick.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Re: FreeBSD 5.4 AMD64 & MPD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ddg@yan.com.br List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 03:28:28 -0000 Gleb Smirnoff escreveu: >On Wed, Sep 28, 2005 at 04:00:08PM -0300, Daniel Dias Gon?alves wrote: >D> I installed MPD and it doesn't start, NETGRAPH is enable on kernel. > >mpd-3.18 doesn't work on AMD64. Future mpd-3.19 will work. However, >the problem is already fixed in mpd port. You need to update your >ports tree and resintall mpd. > > > Thanks, but look for this patch: http://sourceforge.net/tracker/index.php?func=detail&aid=1263766&group_id=14145&atid=314145 -- Daniel Dias Gonçalves DGNET Network Solutions daniel@dgnetwork.com.br (37) 99824809 From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 06:26:50 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E98C16A41F for ; Tue, 4 Oct 2005 06:26:50 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13E3643D49 for ; Tue, 4 Oct 2005 06:26:50 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from [80.82.44.194] (port=37870 helo=192.168.168.7) by mx3.mail.ru with esmtp id 1EMgGF-000I8d-00; Tue, 04 Oct 2005 10:26:47 +0400 Date: Tue, 4 Oct 2005 10:25:40 +0400 From: Andrey Smagin X-Mailer: The Bat! (v1.62r) Organization: DiP X-Priority: 3 (Normal) Message-ID: <372828116.20051004102540@mail.ru> To: Marcin Jessa In-Reply-To: <20050930095743.402e56cd.lists@yazzy.org> References: <20050926195807.GD95971@sandvine.com> <17208.30606.117170.36398@khavrinen.csail.mit.edu> <20050927001650.GA9994@sandvine.com> <20050927180021.GB9994@sandvine.com> <433A2882.4030003@freebsd.org> <433A2D6E.7020205@freebsd.org> <20050928152112.GC9994@sandvine.com> <2262110.20050928194326@mail.ru> <584642479.20050930101019@mail.ru> <20050930095743.402e56cd.lists@yazzy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: How connect 2 PC with ath in hostap mode ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: SAMU List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 06:26:50 -0000 Hello Marcin, MJ> man ifconfig should be the place to start. :) re read it 2 year, for information about MJ> Anyway, you can connect two PCs when one of them runs in MJ> hostap and the other one in ad-hoc mode. MJ> This will set up one of them as AP: MJ> ifconfig_ath0="inet 12.23.34.1 netmask 255.255.255.0 ssid Andrey mode MJ> 11g mediaopt hostap" MJ> And one in adhoc: MJ> ifconfig_ath0="inet 12.23.34.1 netmask 255.255.255.0 ssid Andrey MJ> channel 6 mode 11g mediaopt adhoc" MJ> You can also run both atheros nics in ad-hoc mode and bridge their MJ> interfaces with wired nics. My most qestion - how increase speed for ad-hoc<=>ad-hoc connection. It mode have very small speed(40KBy/s) . For me important bridge on both sides for connect 2 wired LAN segments through air. When i connect client<=>hostup bridging not work (but speed 2MBy/s between this hosts). I am will try ad-hoc<=>hostap. MJ> And you can set up your atheros access point as apbridge which will MJ> pass packets between wireless clients directly. For me not enough for connect another WiFi clients, now configured -apbridge. MJ> You cannot connect two APs in hostap mode as they will never associate MJ> to one another. Thank you. -- Best regards, Andrey mailto:samspeedu@mail.ru From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 07:35:22 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDD6B16A446 for ; Tue, 4 Oct 2005 07:35:22 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B3CD43D46 for ; Tue, 4 Oct 2005 07:35:22 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=marcin) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1EMhK1-0003aw-C3; Tue, 04 Oct 2005 09:34:46 +0200 Date: Tue, 4 Oct 2005 09:35:17 +0200 From: Marcin Jessa To: SAMU Message-Id: <20051004093517.15e368f2.lists@yazzy.org> In-Reply-To: <372828116.20051004102540@mail.ru> References: <20050926195807.GD95971@sandvine.com> <17208.30606.117170.36398@khavrinen.csail.mit.edu> <20050927001650.GA9994@sandvine.com> <20050927180021.GB9994@sandvine.com> <433A2882.4030003@freebsd.org> <433A2D6E.7020205@freebsd.org> <20050928152112.GC9994@sandvine.com> <2262110.20050928194326@mail.ru> <584642479.20050930101019@mail.ru> <20050930095743.402e56cd.lists@yazzy.org> <372828116.20051004102540@mail.ru> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: freebsd-net@freebsd.org Subject: Re: How connect 2 PC with ath in hostap mode ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 07:35:22 -0000 On Tue, 4 Oct 2005 10:25:40 +0400 Andrey Smagin wrote: > Hello Marcin, > > MJ> man ifconfig should be the place to start. > :) re read it 2 year, for information about > MJ> Anyway, you can connect two PCs when one of them runs in > MJ> hostap and the other one in ad-hoc mode. > MJ> This will set up one of them as AP: > MJ> ifconfig_ath0="inet 12.23.34.1 netmask 255.255.255.0 ssid Andrey > MJ> mode 11g mediaopt hostap" > > MJ> And one in adhoc: > MJ> ifconfig_ath0="inet 12.23.34.1 netmask 255.255.255.0 ssid Andrey > MJ> channel 6 mode 11g mediaopt adhoc" > > MJ> You can also run both atheros nics in ad-hoc mode and bridge their > MJ> interfaces with wired nics. > > My most qestion - how increase speed for ad-hoc<=>ad-hoc connection. > It mode have very small speed(40KBy/s) . For me important bridge on > both sides for connect 2 wired LAN segments through air. When i > connect client<=>hostup bridging not work (but speed 2MBy/s between > this hosts). I am will try ad-hoc<=>hostap. How are you bridging the interfaces? What kind of bridging mechanism are you using? Anyway, the difference in speed is indeed strange. Try to set following: sysctl dev.ath.0.tpscale=1 sysctl dev.ath.0.tpc=1 sysctl dev.ath.0.diversity=0 ifconfig ath0 protmode off ifconfig ath0 mtu 2290 You could also use device tap (virtual ethernet) and connect two lan's that way running one link in hostap and the other bss mode. Check out the vtun port. > MJ> And you can set up your atheros access point as apbridge which > MJ> will pass packets between wireless clients directly. > > For me not enough for connect another WiFi clients, now configured > -apbridge. > > MJ> You cannot connect two APs in hostap mode as they will never > MJ> associate to one another. > I am not sure why you have such a speed loss running in adhoc mode. What I noticed on NetBSD (where the ath driver is not yet fully ported) was I got pretty decent speed with the same setup as yours (2xath in adhoc bridged with wired nics) but my embedded devices allways crashed when I sent over many small packets. Cheers Marcin From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 11:32:09 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37E8316A41F for ; Tue, 4 Oct 2005 11:32:09 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96FFF43D45 for ; Tue, 4 Oct 2005 11:32:05 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id j94BW0lU033642; Tue, 4 Oct 2005 15:32:00 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id j94BW0ik033637; Tue, 4 Oct 2005 15:32:00 +0400 (MSD) (envelope-from yar) Date: Tue, 4 Oct 2005 15:31:59 +0400 From: Yar Tikhiy To: Gavin Atkinson Message-ID: <20051004113159.GB28705@comp.chem.msu.su> References: <1128196122.7015.38.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1128196122.7015.38.camel@buffy.york.ac.uk> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org Subject: Re: vlan(4), bge(4) and bringing parent interface up X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 11:32:09 -0000 On Sat, Oct 01, 2005 at 08:48:42PM +0100, Gavin Atkinson wrote: > > It seems to me that assigning an IP address to a vlan device (parent > device bge0) isn't enough to get the interface working - I need to > manually bring the parent interface up. Yes you need. The UP flag on an interface is administrative; that is, it is you who is in control of the flag. Some interfaces try to frob UP theirselves, but it is bogus and will be gone some day. > Is this expected? I suspect it's a bug in either the vlan layer, or the > bge interface code, but if it is expected it would be good to see this > documented. I don't ever remember having to do anything special to get > fxp cards working with vlans. I always bring an fxp up before attaching vlans to it, so I've never noticed fxp to touch its UP flag. If fxp does so, it is buggy and in need of fixing. -- Yar From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 11:51:50 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CB1416A41F; Tue, 4 Oct 2005 11:51:50 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEFEE43D45; Tue, 4 Oct 2005 11:51:41 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id j94Bpa1Q034832; Tue, 4 Oct 2005 15:51:36 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id j94BpZmp034831; Tue, 4 Oct 2005 15:51:35 +0400 (MSD) (envelope-from yar) Date: Tue, 4 Oct 2005 15:51:35 +0400 From: Yar Tikhiy To: Gavin Atkinson Message-ID: <20051004115135.GA34584@comp.chem.msu.su> References: <20050922104104.GA13539@comp.chem.msu.su> <20050925213741.GG15981@odin.ac.hmc.edu> <1127686105.23447.35.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1127686105.23447.35.camel@buffy.york.ac.uk> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: "ifconfig -vlandev" syntax X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 11:51:50 -0000 On Sun, Sep 25, 2005 at 11:08:25PM +0100, Gavin Atkinson wrote: > > There's also the issue that the "vlan" and "vlandev" options have to be > specified in that order, which is counter-intuitive and undocumented. I've committed a change to ifconfig(8) that makes the order arbitrary. Please test it if you can. I hope to merge it to RELENG_6 after a period of testing. -- Yar From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 12:01:01 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AFED16A41F for ; Tue, 4 Oct 2005 12:01:01 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C6DB43D49 for ; Tue, 4 Oct 2005 12:00:59 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j94C0olg056601 for ; Tue, 4 Oct 2005 14:00:52 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id DE834228019 for ; Tue, 4 Oct 2005 14:00:47 +0200 (CEST) Message-ID: <43426EF3.3020404@jku.at> Date: Tue, 04 Oct 2005 14:00:51 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> In-Reply-To: <20051003123210.GF70355@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 12:01:01 -0000 Gleb Smirnoff wrote: > On Mon, Oct 03, 2005 at 02:29:35PM +0200, Ferdinand Goldmann wrote: > F> Gleb Smirnoff wrote: > F> > F> >All I can say: I have faced this problem, too. :( This is not problem in > F> >polling, but in em. > F> > > F> > F> Thank you! Just now I downloaded the driver from the Intel website; seems > F> to compile fine, but I'll have to wait at least until tomorrow morning to > F> test it. > F> > F> Do you have any experiences with the Intel driver? > > Please share your results with community. > Ok, to followup on this issue: Today I installed the driver which I had downloaded from the Intel website (em-3.2.15.tar.gz). This driver does not solve the issue with Ierrs rising rapidly when polling is enabled (I tried HZ=1000 and burst_max 300 and 600). Neither throughput nor interrupt load were any better than with the old driver; in fact I'd say they were worse. :-( So we ended up rebooting with the old kernel. This is pretty bad, because we did assume that Intel cards are among the ones well supported by FreeBSD. Can anyone give recommendations on copper Gbit cards that work _well_ with recent FreeBSD 5-STABLE? -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 12:38:31 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4544F16A41F for ; Tue, 4 Oct 2005 12:38:31 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id A984343D49 for ; Tue, 4 Oct 2005 12:38:30 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from [80.82.44.194] (port=2638 helo=192.168.168.7) by mx1.mail.ru with esmtp id 1EMm3w-000Exo-00; Tue, 04 Oct 2005 16:38:28 +0400 Date: Tue, 4 Oct 2005 16:37:21 +0400 From: Andrey Smagin X-Mailer: The Bat! (v1.62r) Organization: DiP X-Priority: 3 (Normal) Message-ID: <1721705859.20051004163721@mail.ru> To: Marcin Jessa In-Reply-To: <20051004093517.15e368f2.lists@yazzy.org> References: <20050926195807.GD95971@sandvine.com> <17208.30606.117170.36398@khavrinen.csail.mit.edu> <20050927001650.GA9994@sandvine.com> <20050927180021.GB9994@sandvine.com> <433A2882.4030003@freebsd.org> <433A2D6E.7020205@freebsd.org> <20050928152112.GC9994@sandvine.com> <2262110.20050928194326@mail.ru> <584642479.20050930101019@mail.ru> <20050930095743.402e56cd.lists@yazzy.org> <372828116.20051004102540@mail.ru> <20051004093517.15e368f2.lists@yazzy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: How connect 2 PC with ath in hostap mode ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: SAMU List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 12:38:31 -0000 Hello Marcin, Tuesday, October 4, 2005, 11:35:17 AM, you wrote: MJ> How are you bridging the interfaces? What kind of bridging mechanism MJ> are you using? In FreeBSD: kldload ath, ath_hal, bridge, fxp On both host: ifconfig_ath0="inet ssid 1234 channel 6 mode 11g mediaopt adhoc" in sysctl.conf hw....bridge.config=ath0:1,fxp0:1 hw....bridge.enable=1 ipfw allow ip from any to any in this mode speed about 8KBy/s ifconfig_ath0="inet ssid 1234 channel 6 media OFDM54 mode 11g mediaopt adhoc" increase speed up to 45-50 KBy/s Bridging work fine and uptime for both host more wheek under full load :) (40KBy/s over wireless) Some strange - ping report low average delay about 0.700ms for any host in another net segment. MJ> Anyway, the difference in speed is indeed strange. MJ> Try to set following: MJ> sysctl dev.ath.0.tpscale=1 MJ> sysctl dev.ath.0.tpc=1 MJ> sysctl dev.ath.0.diversity=0 MJ> ifconfig ath0 protmode off MJ> ifconfig ath0 mtu 2290 MJ> You could also use device tap (virtual ethernet) and connect two lan's MJ> that way running one link in hostap and the other bss mode. Check out MJ> the vtun port. Thanks i will try it. MJ> I am not sure why you have such a speed loss running in adhoc mode. MJ> What I noticed on NetBSD (where the ath driver is not yet fully ported) MJ> was I got pretty decent speed with the same setup as yours (2xath in MJ> adhoc bridged with wired nics) but my embedded devices allways crashed MJ> when I sent over many small packets. I think this is a driver problem, two ap sucessfully connect with each other, why hostap can't do this ? I tested D-Link 624 WiFi router, D-Link 2100AP, DWL-520+, DWL-G520. On DWL-520+ - acx chipset, it speed not more 8KBy/s with adhoc<=>adhoc connection(but under W2K it have fullspeed 800KBy/s in this mode). I bought DWL-G520 on ath chipset, upgraded hosts hardware up 850MHz processor, new MB, more RAM, but it not resolve the problem, with 54MBit/s connection, speed is too small. D-Link AP, with WiFi router have good connection and speed 38MBit/s(2MBy/s). -- Best regards, Andrey mailto:samspeedu@mail.ru From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 12:44:55 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFBA716A41F for ; Tue, 4 Oct 2005 12:44:55 +0000 (GMT) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70C9843D45 for ; Tue, 4 Oct 2005 12:44:55 +0000 (GMT) (envelope-from toasty@dragondata.com) Received: from mail.dragondata.com (server3-b.your.org [64.202.113.67]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id C88982AD5BDF; Tue, 4 Oct 2005 13:07:10 +0000 (UTC) Received: from [69.31.99.45] (pool045.dhcp.your.org [69.31.99.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.dragondata.com (Postfix) with ESMTP id A97CA3D181F; Tue, 4 Oct 2005 07:44:52 -0500 (CDT) In-Reply-To: <43426EF3.3020404@jku.at> References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> Content-Transfer-Encoding: 7bit From: Kevin Day Date: Tue, 4 Oct 2005 07:45:08 -0500 To: ferdinand.goldmann@jku.at X-Mailer: Apple Mail (2.734) Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 12:44:55 -0000 On Oct 4, 2005, at 7:00 AM, Ferdinand Goldmann wrote: > > Ok, to followup on this issue: > > Today I installed the driver which I had downloaded from the Intel > website (em-3.2.15.tar.gz). This driver does not solve the issue > with Ierrs rising rapidly when polling is enabled (I tried HZ=1000 > and burst_max 300 and 600). > > Neither throughput nor interrupt load were any better than with the > old driver; in fact I'd say they were worse. :-( So we ended up > rebooting with the old kernel. > > This is pretty bad, because we did assume that Intel cards are > among the ones well supported by FreeBSD. > > Can anyone give recommendations on copper Gbit cards that work > _well_ with recent FreeBSD 5-STABLE? This is pretty odd. We've got dozens of servers using various versions of 5.x, and many different em cards, and have no problem, even when shoving near line rate speeds out of them. Add in cards like: em0: port 0xccc0-0xccff mem 0xfcd20000-0xfcd3ffff irq 24 at device 6.0 on pci2 and built in to newer Dell servers: em0: port 0xecc0-0xecff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 After you experience your problems, can you do "sysctl -w hw.em0.stats=1" and "sysctl -w hw.em0.debug_info=1" and post what gets dumped to your syslog/dmesg output? We're using polling on nearly all the servers, and don't see ierrs at all. Have you tried contacting Intel directly about this? freebsdnic@mailbox.intel.com has been pretty helpful with em specific problems in the past. From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 13:18:44 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14F5B16A41F for ; Tue, 4 Oct 2005 13:18:44 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D02E43D45 for ; Tue, 4 Oct 2005 13:18:43 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=marcin) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1EMmgI-0001Sp-Jv; Tue, 04 Oct 2005 15:18:09 +0200 Date: Tue, 4 Oct 2005 15:18:42 +0200 From: Marcin Jessa To: SAMU Message-Id: <20051004151842.66ffca58.lists@yazzy.org> In-Reply-To: <1721705859.20051004163721@mail.ru> References: <20050926195807.GD95971@sandvine.com> <17208.30606.117170.36398@khavrinen.csail.mit.edu> <20050927001650.GA9994@sandvine.com> <20050927180021.GB9994@sandvine.com> <433A2882.4030003@freebsd.org> <433A2D6E.7020205@freebsd.org> <20050928152112.GC9994@sandvine.com> <2262110.20050928194326@mail.ru> <584642479.20050930101019@mail.ru> <20050930095743.402e56cd.lists@yazzy.org> <372828116.20051004102540@mail.ru> <20051004093517.15e368f2.lists@yazzy.org> <1721705859.20051004163721@mail.ru> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: freebsd-net@freebsd.org Subject: Re: How connect 2 PC with ath in hostap mode ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 13:18:44 -0000 On Tue, 4 Oct 2005 16:37:21 +0400 Andrey Smagin wrote: > Hello Marcin, > > Tuesday, October 4, 2005, 11:35:17 AM, you wrote: > > > MJ> How are you bridging the interfaces? What kind of bridging > MJ> mechanism are you using? > > In FreeBSD: > kldload ath, ath_hal, bridge, fxp Recompile your kernel with following options. device wlan # 802.11 support device ath device ath_hal device ath_rate_sample > On both host: > ifconfig_ath0="inet ssid 1234 channel 6 mode 11g mediaopt adhoc" > in sysctl.conf > hw....bridge.config=ath0:1,fxp0:1 > hw....bridge.enable=1 > > ipfw allow ip from any to any > in this mode speed about 8KBy/s Try to use if_bridge instead ifconfig bridge0 create up ifconfig bridge0 addm ath0 fxp0 etc... The "old" bridge code is removed from CURRENT anyway. Try to play with different sysctl values for ath as well, it may or may not have an impact on your performance. > ifconfig_ath0="inet ssid 1234 channel 6 media OFDM54 mode 11g > mediaopt adhoc" increase speed up to 45-50 KBy/s Right, still pretty little. You should get between 2-7 MB/s > Bridging work fine and uptime for both host more > wheek under full load :) (40KBy/s over wireless) > Some strange - ping report low average delay about > 0.700ms for any host in another net segment. Try to adjust values of ACK timing, I have made a table with some proposed values: http://www.wifibsd.org/docs/atheros.php > MJ> Anyway, the difference in speed is indeed strange. > MJ> Try to set following: > MJ> sysctl dev.ath.0.tpscale=1 > MJ> sysctl dev.ath.0.tpc=1 > MJ> sysctl dev.ath.0.diversity=0 > MJ> ifconfig ath0 protmode off > MJ> ifconfig ath0 mtu 2290 > MJ> You could also use device tap (virtual ethernet) and connect two > MJ> lan's that way running one link in hostap and the other bss mode. > MJ> Check out the vtun port. > Thanks i will try it. > > MJ> I am not sure why you have such a speed loss running in adhoc > MJ> mode. What I noticed on NetBSD (where the ath driver is not yet > MJ> fully ported) was I got pretty decent speed with the same setup > MJ> as yours (2xath in adhoc bridged with wired nics) but my embedded > MJ> devices allways crashed when I sent over many small packets. > I think this is a driver problem, two ap sucessfully connect > with each other, why hostap can't do this ? That's becouse FreeBSD ath hostap is for access points , not for interaction between two APs. >I tested D-Link 624 WiFi > router, D-Link 2100AP, DWL-520+, DWL-G520. On DWL-520+ - acx chipset, > it speed not more 8KBy/s with adhoc<=>adhoc connection(but under W2K > it have fullspeed 800KBy/s in this mode). I bought DWL-G520 on ath > chipset, upgraded hosts hardware up 850MHz processor, new MB, more > RAM, but it not resolve the problem, with 54MBit/s connection, speed > is too small. D-Link AP, with WiFi router have good connection and > speed 38MBit/s(2MBy/s). Did you run tcpdump on both the hosts to find out what may be causing your problems? I will test adhoc between two atheros boxes at home today. From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 14:27:43 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C35BF16A41F for ; Tue, 4 Oct 2005 14:27:43 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42DD343D46 for ; Tue, 4 Oct 2005 14:27:42 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j94ERWpK093090 for ; Tue, 4 Oct 2005 16:27:32 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id 272A6228019 for ; Tue, 4 Oct 2005 16:27:32 +0200 (CEST) Message-ID: <43429157.90606@jku.at> Date: Tue, 04 Oct 2005 16:27:35 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> In-Reply-To: <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 14:27:44 -0000 Kevin Day wrote: > This is pretty odd. We've got dozens of servers using various versions > of 5.x, and many different em cards, and have no problem, even when > shoving near line rate speeds out of them. Maximum transfer rates we see in MRTG were around 320Mbit/s (with polling disabled) > em0: port > 0xecc0-0xecff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 em0: port 0x2280-0x22bf mem 0xeffc0000-0xeffdffff irq 20 at device 5.0 on pci1 Pretty much the same here, even the driver version. em0@pci1:5:0: class=0x020000 card=0x10028086 chip=0x10268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82545GM Gigabit Ethernet Controller' > After you experience your problems, can you do "sysctl -w > hw.em0.stats=1" and "sysctl -w hw.em0.debug_info=1" and post what gets > dumped to your syslog/dmesg output? em0: Excessive collisions = 0 em0: Symbol errors = 0 em0: Sequence errors = 0 em0: Defer count = 11 em0: Missed Packets = 0 em0: Receive No Buffers = 0 em0: Receive length errors = 0 em0: Receive errors = 0 em0: Crc errors = 0 em0: Alignment errors = 0 em0: Carrier extension errors = 0 em0: XON Rcvd = 11 em0: XON Xmtd = 0 em0: XOFF Rcvd = 11 em0: XOFF Xmtd = 0 em0: Good Packets Rcvd = 283923273 em0: Good Packets Xmtd = 272613648 em0: Adapter hardware address = 0xc12cfb48 em0:CTRL = 0x58f00249 em0:RCTL = 0x8002 PS=(0x8402) em0:tx_int_delay = 66, tx_abs_int_delay = 66 em0:rx_int_delay = 0, rx_abs_int_delay = 66 em0: fifo workaround = 0, fifo_reset = 0 em0: hw tdh = 173, hw tdt = 173 em0: Num Tx descriptors avail = 256 em0: Tx Descriptors not avail1 = 0 em0: Tx Descriptors not avail2 = 0 em0: Std mbuf failed = 0 em0: Std mbuf cluster failed = 0 em0: Driver dropped packets = 0 > We're using polling on nearly all the servers, and don't see ierrs at > all. Hm. That's strange. The above values were gathered with polling disabled. As soon as I enable polling, ierrs on the em0 interface are rising: em0: Excessive collisions = 0 em0: Symbol errors = 0 em0: Sequence errors = 0 em0: Defer count = 11 em0: Missed Packets = 39 em0: Receive No Buffers = 2458 em0: Receive length errors = 0 em0: Receive errors = 0 em0: Crc errors = 0 em0: Alignment errors = 0 em0: Carrier extension errors = 0 em0: XON Rcvd = 11 em0: XON Xmtd = 4 em0: XOFF Rcvd = 11 em0: XOFF Xmtd = 43 em0: Good Packets Rcvd = 315880003 em0: Good Packets Xmtd = 303985941 em0: Adapter hardware address = 0xc12cfb48 em0:CTRL = 0x58f00249 em0:RCTL = 0x8002 PS=(0x8402) em0:tx_int_delay = 66, tx_abs_int_delay = 66 em0:rx_int_delay = 0, rx_abs_int_delay = 66 em0: fifo workaround = 0, fifo_reset = 0 em0: hw tdh = 57, hw tdt = 57 em0: Num Tx descriptors avail = 249 em0: Tx Descriptors not avail1 = 0 em0: Tx Descriptors not avail2 = 0 em0: Std mbuf failed = 0 em0: Std mbuf cluster failed = 0 em0: Driver dropped packets = 0 Can you tell me what settings you are using for polling? I have set it to HZ=1000 and burst_max=300. I have now noticed another thing which might indicate one of the possible causes for the problem - this box until now ran FreeBSD 4.x and did not support ipfw tables to lock out whole lists of IP adresses. So there were quite a few inefficient rules for this. I now put all the locked IP addresses in a table which is referenced by only one rule. Since I did this, the ierrs seem to rise slower with polling enabled. > Have you tried contacting Intel directly about this? > freebsdnic@mailbox.intel.com has been pretty helpful with em specific > problems in the past. Not yet, thank you for the hint. -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 14:58:11 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4158816A41F for ; Tue, 4 Oct 2005 14:58:11 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from mta3.srv.hcvlny.cv.net (mta3.srv.hcvlny.cv.net [167.206.4.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id D904143D45 for ; Tue, 4 Oct 2005 14:58:10 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from [127.0.0.1] (ool-18bbf604.dyn.optonline.net [24.187.246.4]) by mta3.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-2.06 (built May 11 2005)) with ESMTP id <0INU00FP7C8WONS0@mta3.srv.hcvlny.cv.net> for net@freebsd.org; Tue, 04 Oct 2005 10:58:10 -0400 (EDT) Date: Tue, 04 Oct 2005 10:58:05 -0400 From: Benjamin Rosenblum In-reply-to: <43429157.90606@jku.at> To: net@freebsd.org Message-id: <4342987D.7000200@benswebs.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 14:58:11 -0000 i have been messing with the em driver now for over a month, ive come to the conclusion is a piece of crap. if you watch on this list every other day you have someone saying there em driver is causing some sort of error, this should not be on a nic from a company like intel. im saddly contimplating moving over to fedora right now just so i can work until 6.0 comes out (which i doubt will solve the problem anyway since im using the drivers from 6.0 now and there not helping out either). somebody really needs to look into this and find out what the hell is going on as i consider this a major problem right now. Ferdinand Goldmann wrote: > Kevin Day wrote: > >> This is pretty odd. We've got dozens of servers using various >> versions of 5.x, and many different em cards, and have no problem, >> even when shoving near line rate speeds out of them. > > > Maximum transfer rates we see in MRTG were around 320Mbit/s (with > polling disabled) > >> em0: port >> 0xecc0-0xecff mem 0xdfae0000-0xdfafffff irq 64 at device 7.0 on pci6 > > > em0: port > 0x2280-0x22bf mem 0xeffc0000-0xeffdffff > irq 20 at device 5.0 on pci1 > > Pretty much the same here, even the driver version. > > em0@pci1:5:0: class=0x020000 card=0x10028086 chip=0x10268086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = '82545GM Gigabit Ethernet Controller' > >> After you experience your problems, can you do "sysctl -w >> hw.em0.stats=1" and "sysctl -w hw.em0.debug_info=1" and post what >> gets dumped to your syslog/dmesg output? > > > em0: Excessive collisions = 0 > em0: Symbol errors = 0 > em0: Sequence errors = 0 > em0: Defer count = 11 > em0: Missed Packets = 0 > em0: Receive No Buffers = 0 > em0: Receive length errors = 0 > em0: Receive errors = 0 > em0: Crc errors = 0 > em0: Alignment errors = 0 > em0: Carrier extension errors = 0 > em0: XON Rcvd = 11 > em0: XON Xmtd = 0 > em0: XOFF Rcvd = 11 > em0: XOFF Xmtd = 0 > em0: Good Packets Rcvd = 283923273 > em0: Good Packets Xmtd = 272613648 > em0: Adapter hardware address = 0xc12cfb48 > em0:CTRL = 0x58f00249 > em0:RCTL = 0x8002 PS=(0x8402) > em0:tx_int_delay = 66, tx_abs_int_delay = 66 > em0:rx_int_delay = 0, rx_abs_int_delay = 66 > em0: fifo workaround = 0, fifo_reset = 0 > em0: hw tdh = 173, hw tdt = 173 > em0: Num Tx descriptors avail = 256 > em0: Tx Descriptors not avail1 = 0 > em0: Tx Descriptors not avail2 = 0 > em0: Std mbuf failed = 0 > em0: Std mbuf cluster failed = 0 > em0: Driver dropped packets = 0 > >> We're using polling on nearly all the servers, and don't see ierrs at >> all. > > > Hm. That's strange. The above values were gathered with polling > disabled. As soon as I enable polling, ierrs on the em0 interface are > rising: > > em0: Excessive collisions = 0 > em0: Symbol errors = 0 > em0: Sequence errors = 0 > em0: Defer count = 11 > em0: Missed Packets = 39 > em0: Receive No Buffers = 2458 > em0: Receive length errors = 0 > em0: Receive errors = 0 > em0: Crc errors = 0 > em0: Alignment errors = 0 > em0: Carrier extension errors = 0 > em0: XON Rcvd = 11 > em0: XON Xmtd = 4 > em0: XOFF Rcvd = 11 > em0: XOFF Xmtd = 43 > em0: Good Packets Rcvd = 315880003 > em0: Good Packets Xmtd = 303985941 > em0: Adapter hardware address = 0xc12cfb48 > em0:CTRL = 0x58f00249 > em0:RCTL = 0x8002 PS=(0x8402) > em0:tx_int_delay = 66, tx_abs_int_delay = 66 > em0:rx_int_delay = 0, rx_abs_int_delay = 66 > em0: fifo workaround = 0, fifo_reset = 0 > em0: hw tdh = 57, hw tdt = 57 > em0: Num Tx descriptors avail = 249 > em0: Tx Descriptors not avail1 = 0 > em0: Tx Descriptors not avail2 = 0 > em0: Std mbuf failed = 0 > em0: Std mbuf cluster failed = 0 > em0: Driver dropped packets = 0 > > > Can you tell me what settings you are using for polling? I have set it > to HZ=1000 and burst_max=300. > > I have now noticed another thing which might indicate one of the > possible causes for the problem - this box until now ran FreeBSD 4.x > and did not support ipfw tables to lock out whole lists of IP > adresses. So there were quite a few inefficient rules for this. I now > put all the locked IP addresses in a table which is referenced by only > one rule. Since I did this, the ierrs seem to rise slower with polling > enabled. > >> Have you tried contacting Intel directly about this? >> freebsdnic@mailbox.intel.com has been pretty helpful with em specific >> problems in the past. > > > Not yet, thank you for the hint. > From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 15:22:32 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF0C816A41F for ; Tue, 4 Oct 2005 15:22:32 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 855AB43D45 for ; Tue, 4 Oct 2005 15:22:32 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id B9A815CDE; Tue, 4 Oct 2005 11:22:31 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45154-09; Tue, 4 Oct 2005 11:22:29 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-71-31.ny325.east.verizon.net [68.161.71.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 0AB835CE3; Tue, 4 Oct 2005 11:22:29 -0400 (EDT) Message-ID: <43429E3B.1080900@mac.com> Date: Tue, 04 Oct 2005 11:22:35 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Benjamin Rosenblum References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> In-Reply-To: <4342987D.7000200@benswebs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 15:22:33 -0000 Benjamin Rosenblum wrote: > i have been messing with the em driver now for over a month, ive come to > the conclusion is a piece of crap. if you watch on this list every > other day you have someone saying there em driver is causing some sort > of error, this should not be on a nic from a company like intel. This is known as "selection bias". People who have em NICs, and who do not have problems, probably do not report regularly that their Intel 10/100/1000 NIC works fine, even though it does, at least for them. I've got a dozen or so machines with that hardware, and I haven't seen any problems with them. > im saddly contimplating moving over to fedora right now just so i can work > until 6.0 comes out (which i doubt will solve the problem anyway since > im using the drivers from 6.0 now and there not helping out either). If you want to use Fedora instead, go right ahead and do so... > somebody really needs to look into this and find out what the hell is > going on as i consider this a major problem right now. Are you volunteering? -- -Chuck From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 16:00:59 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47F0C16A420 for ; Tue, 4 Oct 2005 16:00:59 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from mta9.srv.hcvlny.cv.net (mta9.srv.hcvlny.cv.net [167.206.4.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id E227043D45 for ; Tue, 4 Oct 2005 16:00:58 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from [127.0.0.1] (ool-18bbf604.dyn.optonline.net [24.187.246.4]) by mta9.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-2.06 (built May 11 2005)) with ESMTP id <0INU00HEDF4ZFV51@mta9.srv.hcvlny.cv.net> for net@freebsd.org; Tue, 04 Oct 2005 12:00:36 -0400 (EDT) Date: Tue, 04 Oct 2005 12:00:32 -0400 From: Benjamin Rosenblum In-reply-to: <43429E3B.1080900@mac.com> To: Chuck Swiger Message-id: <4342A720.5060600@benswebs.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <43429E3B.1080900@mac.com> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 16:00:59 -0000 yea i have been messing with the driver for about a month now to try to atleast target where the failure is, ive probably put about 25-30 hours in now modifying the code and recompiling and testing it. best i have gotten is to figure out its a problem with the cache becoming full and not sending it to the system in a timely fassion and the card panicing when the cache gets full. so yes, i have volunteered to do it and i have been trying but my knowledge of how freebsd handles drivers and hardware is somewhat limited since this is my first time experimenting with them hence why im on here. also something that should be noted its not very common for someone to be running the type of constant load that i do on my system and thats probably why more people arent reporting this issue. Chuck Swiger wrote: > Benjamin Rosenblum wrote: > >> i have been messing with the em driver now for over a month, ive come >> to the conclusion is a piece of crap. if you watch on this list >> every other day you have someone saying there em driver is causing >> some sort of error, this should not be on a nic from a company like >> intel. > > > This is known as "selection bias". > > People who have em NICs, and who do not have problems, probably do not > report regularly that their Intel 10/100/1000 NIC works fine, even > though it does, at least for them. I've got a dozen or so machines > with that hardware, and I haven't seen any problems with them. > >> im saddly contimplating moving over to fedora right now just so i can >> work until 6.0 comes out (which i doubt will solve the problem anyway >> since im using the drivers from 6.0 now and there not helping out >> either). > > > If you want to use Fedora instead, go right ahead and do so... > >> somebody really needs to look into this and find out what the hell is >> going on as i consider this a major problem right now. > > > Are you volunteering? > From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 16:12:23 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FC5716A41F for ; Tue, 4 Oct 2005 16:12:23 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A7CE43D46 for ; Tue, 4 Oct 2005 16:12:22 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by smtp3-g19.free.fr (Postfix) with ESMTP id 2A82C2710C; Tue, 4 Oct 2005 18:12:21 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 365114080; Tue, 4 Oct 2005 18:12:17 +0200 (CEST) Date: Tue, 4 Oct 2005 18:12:17 +0200 From: Jeremie Le Hen To: Benjamin Rosenblum Message-ID: <20051004161217.GB43195@obiwan.tataz.chchile.org> References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4342987D.7000200@benswebs.com> User-Agent: Mutt/1.5.10i Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 16:12:23 -0000 Hi Benjamin, Ferdinant, (Please avoid top-posting, this reverts the flow of the conversation and make the whole thread difficult to follow.) > i have been messing with the em driver now for over a month, ive come to > the conclusion is a piece of crap. if you watch on this list every > other day you have someone saying there em driver is causing some sort > of error, this should not be on a nic from a company like intel. im > saddly contimplating moving over to fedora right now just so i can work > until 6.0 comes out (which i doubt will solve the problem anyway since > im using the drivers from 6.0 now and there not helping out either). > somebody really needs to look into this and find out what the hell is > going on as i consider this a major problem right now. em(4) is known to be full of problems, it would indeed require someone taking the maintainership of the driver and then reworking it a bit. > >>After you experience your problems, can you do "sysctl -w > >>hw.em0.stats=1" and "sysctl -w hw.em0.debug_info=1" and post what > >>gets dumped to your syslog/dmesg output? > > > > > >em0: Excessive collisions = 0 > >em0: Symbol errors = 0 > >em0: Sequence errors = 0 > >em0: Defer count = 11 > >em0: Missed Packets = 0 > >em0: Receive No Buffers = 0 > >em0: Receive length errors = 0 > >em0: Receive errors = 0 > >em0: Crc errors = 0 > >em0: Alignment errors = 0 > >em0: Carrier extension errors = 0 > >em0: XON Rcvd = 11 > >em0: XON Xmtd = 0 > >em0: XOFF Rcvd = 11 > >em0: XOFF Xmtd = 0 > >em0: Good Packets Rcvd = 283923273 > >em0: Good Packets Xmtd = 272613648 > >em0: Adapter hardware address = 0xc12cfb48 > >em0:CTRL = 0x58f00249 > >em0:RCTL = 0x8002 PS=(0x8402) > >em0:tx_int_delay = 66, tx_abs_int_delay = 66 > >em0:rx_int_delay = 0, rx_abs_int_delay = 66 > >em0: fifo workaround = 0, fifo_reset = 0 > >em0: hw tdh = 173, hw tdt = 173 > >em0: Num Tx descriptors avail = 256 > >em0: Tx Descriptors not avail1 = 0 > >em0: Tx Descriptors not avail2 = 0 > >em0: Std mbuf failed = 0 > >em0: Std mbuf cluster failed = 0 > >em0: Driver dropped packets = 0 > > > >>We're using polling on nearly all the servers, and don't see ierrs at > >>all. > > > > > >Hm. That's strange. The above values were gathered with polling > >disabled. As soon as I enable polling, ierrs on the em0 interface are > >rising: > > > >em0: Excessive collisions = 0 > >em0: Symbol errors = 0 > >em0: Sequence errors = 0 > >em0: Defer count = 11 > >em0: Missed Packets = 39 > >em0: Receive No Buffers = 2458 > >em0: Receive length errors = 0 > >em0: Receive errors = 0 > >em0: Crc errors = 0 > >em0: Alignment errors = 0 > >em0: Carrier extension errors = 0 > >em0: XON Rcvd = 11 > >em0: XON Xmtd = 4 > >em0: XOFF Rcvd = 11 > >em0: XOFF Xmtd = 43 > >em0: Good Packets Rcvd = 315880003 > >em0: Good Packets Xmtd = 303985941 > >em0: Adapter hardware address = 0xc12cfb48 > >em0:CTRL = 0x58f00249 > >em0:RCTL = 0x8002 PS=(0x8402) > >em0:tx_int_delay = 66, tx_abs_int_delay = 66 > >em0:rx_int_delay = 0, rx_abs_int_delay = 66 > >em0: fifo workaround = 0, fifo_reset = 0 > >em0: hw tdh = 57, hw tdt = 57 > >em0: Num Tx descriptors avail = 249 > >em0: Tx Descriptors not avail1 = 0 > >em0: Tx Descriptors not avail2 = 0 > >em0: Std mbuf failed = 0 > >em0: Std mbuf cluster failed = 0 > >em0: Driver dropped packets = 0 > > > > > >Can you tell me what settings you are using for polling? I have set it > >to HZ=1000 and burst_max=300. > > > >I have now noticed another thing which might indicate one of the > >possible causes for the problem - this box until now ran FreeBSD 4.x > >and did not support ipfw tables to lock out whole lists of IP > >adresses. So there were quite a few inefficient rules for this. I now > >put all the locked IP addresses in a table which is referenced by only > >one rule. Since I did this, the ierrs seem to rise slower with polling > >enabled. "Receive No Buffers" grows when polling is enabled and it's somewhat a normal behaviour. When polling is not enabled, an interrupt will be generated for each incoming packet and the latter will be soon removed from the NIC buffer space, whereas when polling is enabled I think the kernel will check the NIC state upon each soft clock interrupt (HZ) and fetch them into the memory if any. If too much packets were received during a period, then the overflow of packets will be discarded, incrementing the "Receive No Buffers" error count. I think you can slightly increase the HZ value to decrease this error count, but I'm not sure this will improve the bandwidth in a great order of magnitude. I know that Intel GigE NICs have a smart way to to interrupt throttling (that's what tx_int_delay, tx_abs_int_delay, rx_int_delay and rx_abs_int_delay stand for). You should try to tune them through dev.em.[0-9]+. sysctl tree. These tresholds are very well explained here : http://www.intel.com/design/network/applnots/ap450.pdf I hope this will help. Please let us know about the results. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 17:00:14 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E673D16A420; Tue, 4 Oct 2005 17:00:13 +0000 (GMT) (envelope-from raglon@packetfront.com) Received: from mail.packetfront.com (mail.packetfront.com [212.247.6.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65DA843D45; Tue, 4 Oct 2005 17:00:12 +0000 (GMT) (envelope-from raglon@packetfront.com) Received: from localhost (localhost [127.0.0.1]) by mail.packetfront.com (Postfix) with ESMTP id 9E9F1A3F71; Tue, 4 Oct 2005 19:00:10 +0200 (CEST) Received: from mail.packetfront.com ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30061-03; Tue, 4 Oct 2005 19:00:10 +0200 (CEST) Received: from [192.168.1.159] (pf-raglon.int.packetfront.com [192.168.1.159]) by mail.packetfront.com (Postfix) with ESMTP id 6A3CFA3F68; Tue, 4 Oct 2005 19:00:10 +0200 (CEST) Message-ID: <4342B4BE.1040304@packetfront.com> Date: Tue, 04 Oct 2005 18:58:38 +0200 From: Ragnar Lonn User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ceri Davies References: <20051003130731.GF56760@submonkey.net> <20051003134132.GE73935@cell.sick.ru> <20051003135324.GH56760@submonkey.net> In-Reply-To: <20051003135324.GH56760@submonkey.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at packetfront.com Cc: Gleb Smirnoff , net@FreeBSD.org Subject: Re: ng_tee, right2left, et al X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 17:00:14 -0000 Ceri Davies wrote: >I only call it "wrong" as it didn't agree with Archie's article or my >expectations, hence the quotes - I realise that it's subjective. > >It just seems to me that packets leaving left2right would go to right, >as the name implies. I don't really mind either way, it's simply that >I found it confusing. > > It's not, really. A good idea is to draw the tee node and its hooks on a piece of paper. Here is an ASCII attempt: left --- right \ / x / \ r2l l2r The drawing shows that the left hook is associated with the left2right hook: When packets come in on the left hook they are forwarded to the left2right hook. Logically, that means they are connected, like in the drawing above, and that also means that packets can go in the other direction - i.e. from the left2right hook and to the left hook. /Ragnar From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 18:08:08 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C8A616A41F; Tue, 4 Oct 2005 18:08:08 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from fep19.inet.fi (fep19.inet.fi [194.251.242.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2393543D45; Tue, 4 Oct 2005 18:08:06 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [192.168.0.20] ([84.249.3.49]) by fep19.inet.fi with ESMTP id <20051004180805.RNGN20628.fep19.inet.fi@[192.168.0.20]>; Tue, 4 Oct 2005 21:08:05 +0300 Message-ID: <4342C505.7070205@pp.nic.fi> Date: Tue, 04 Oct 2005 21:08:05 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 6.0-BETA5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-current@freebsd.org" References: <43414EBE.1060500@pp.nic.fi> In-Reply-To: <43414EBE.1060500@pp.nic.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: send_query: No buffer space available [SOLVED] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 18:08:08 -0000 Pertti Kosunen wrote: > What should i do to avoid these messages from MRTG and dhclient? This > happens with some network load on xl0 interface and pf+altq or > ipfw+dummynet+statefull rules enabled, even with simple pass rules. > > Increasing kern.ipc.nmbclusters, kern.ipc.nsfbufs, kern.ipc.somaxconn > and net.inet.tcp.sendspace doesn't seem to help. FreeBSD 5.3-RELEASE to > 6.0-BETA5 have this problem. > > SNMP Error: > send_query: No buffer space available > > dhclient: send_packet: No buffer space available Increasing kern.ipc.maxsockbuf seem to solve the problem. From owner-freebsd-net@FreeBSD.ORG Tue Oct 4 20:36:48 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16B9716A41F; Tue, 4 Oct 2005 20:36:48 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 609F443D49; Tue, 4 Oct 2005 20:36:47 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j94Kak1u038944; Tue, 4 Oct 2005 13:36:46 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j94Kaj8j038943; Tue, 4 Oct 2005 13:36:45 -0700 (PDT) (envelope-from jmg) Date: Tue, 4 Oct 2005 13:36:45 -0700 From: John-Mark Gurney To: Ragnar Lonn Message-ID: <20051004203645.GO716@funkthat.com> Mail-Followup-To: Ragnar Lonn , Ceri Davies , Gleb Smirnoff , net@FreeBSD.org References: <20051003130731.GF56760@submonkey.net> <20051003134132.GE73935@cell.sick.ru> <20051003135324.GH56760@submonkey.net> <4342B4BE.1040304@packetfront.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4342B4BE.1040304@packetfront.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Ceri Davies , Gleb Smirnoff , net@FreeBSD.org Subject: Re: ng_tee, right2left, et al X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 20:36:48 -0000 Ragnar Lonn wrote this message on Tue, Oct 04, 2005 at 18:58 +0200: > Ceri Davies wrote: > > >I only call it "wrong" as it didn't agree with Archie's article or my > >expectations, hence the quotes - I realise that it's subjective. > > > >It just seems to me that packets leaving left2right would go to right, > >as the name implies. I don't really mind either way, it's simply that > >I found it confusing. > > > > > > It's not, really. A good idea is to draw the tee node and its hooks on a > piece of paper. > Here is an ASCII attempt: > > > left --- right > \ / > x > / \ > r2l l2r > > The drawing shows that the left hook is associated with the left2right hook: > When packets come in on the left hook they are forwarded to the left2right > hook. Logically, that means they are connected, like in the drawing above, > and that also means that packets can go in the other direction - i.e. from > the left2right hook and to the left hook. I personally imagined the picture like: l2r >>>>^>>>> / \ left right \ / << X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B544716A41F for ; Tue, 4 Oct 2005 23:56:35 +0000 (GMT) (envelope-from dave-dated-1128902191.bcc743@seddon.ca) Received: from seddon.ca (seddon.ca [203.209.212.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 0521743D45 for ; Tue, 4 Oct 2005 23:56:34 +0000 (GMT) (envelope-from dave-dated-1128902191.bcc743@seddon.ca) Received: (qmail 75516 invoked by uid 89); 4 Oct 2005 23:56:32 -0000 Received: by seddon.ca (tmda-sendmail, from uid 89); Wed, 05 Oct 2005 09:56:31 +1000 (EST) References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> In-Reply-To: <20051004161217.GB43195@obiwan.tataz.chchile.org> To: net@freebsd.org Date: Wed, 05 Oct 2005 09:56:30 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit From: Dave+Seddon Message-ID: <1128470191.75484.TMDA@seddon.ca> X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 23:56:35 -0000 Jeremie, Sorry for "top posting". My time machine is broken :) Kevin, You mention your running at "near" line rate. What are you pushing or pulling? Whats the rough spec of these machines pushing out this much data? What setting do you have for the polling? I've been trying to do near line rate and can't even get close with new HP-DL380s (Single 3.4 Ghz Xeon). I think the PCI bus might be the problem. The em Intel NICs I found to be very slow and stop after about 3 hours. - The Intel NICs I have are dual port, although they end up on seperate IRQs. --------------------------------- cat /var/run/dmesg | grep em em0: Ethernet address: 00:11:0a:57:70:fa em0: Speed:N/A Duplex:N/A em1: port 0x5040-0x507f mem 0xfde60000-0xfde7ffff irq 73 at device 1.1 on pci6 em1: Ethernet address: 00:11:0a:57:70:fb em1: Speed:N/A Duplex:N/A em2: port 0x6000-0x603f mem 0xfdf80000-0xfdfbffff,0xfdfe0000-0xfdffffff irq 97 at device 1.0 on pci10 em2: Ethernet address: 00:11:0a:57:73:6a em2: Speed:N/A Duplex:N/A em3: port 0x6040-0x607f mem 0xfdf60000-0xfdf7ffff irq 98 at device 1.1 on pci10 em3: Ethernet address: 00:11:0a:57:73:6b em3: Speed:N/A Duplex:N/A --------------------------------- ps ax | grep em 84 ?? WL 0:00.00 [irq73: em1] 85 ?? WL 0:00.00 [irq74: em0] 108 ?? WL 0:00.00 [irq97: em2] 109 ?? WL 0:00.00 [irq98: em3] ------------------ Ferdinand, After giving up on the Intel cards in the DL380s I started using the onboard broadcom cards (bge). They work great, although I don't seem to be able to get near line rate either. I've been severing up < 10 files from MFS via thttpd. I get about 80MB/s only. :( Regards, Dave Jeremie Le Hen writes: > Hi Benjamin, Ferdinant, > > (Please avoid top-posting, this reverts the flow of the conversation > and make the whole thread difficult to follow.) > >> i have been messing with the em driver now for over a month, ive come to >> the conclusion is a piece of crap. if you watch on this list every >> other day you have someone saying there em driver is causing some sort >> of error, this should not be on a nic from a company like intel. im >> saddly contimplating moving over to fedora right now just so i can work >> until 6.0 comes out (which i doubt will solve the problem anyway since >> im using the drivers from 6.0 now and there not helping out either). >> somebody really needs to look into this and find out what the hell is >> going on as i consider this a major problem right now. > > em(4) is known to be full of problems, it would indeed require someone > taking the maintainership of the driver and then reworking it a bit. > > >> >>After you experience your problems, can you do "sysctl -w >> >>hw.em0.stats=1" and "sysctl -w hw.em0.debug_info=1" and post what >> >>gets dumped to your syslog/dmesg output? >> > >> > >> >em0: Excessive collisions = 0 >> >em0: Symbol errors = 0 >> >em0: Sequence errors = 0 >> >em0: Defer count = 11 >> >em0: Missed Packets = 0 >> >em0: Receive No Buffers = 0 >> >em0: Receive length errors = 0 >> >em0: Receive errors = 0 >> >em0: Crc errors = 0 >> >em0: Alignment errors = 0 >> >em0: Carrier extension errors = 0 >> >em0: XON Rcvd = 11 >> >em0: XON Xmtd = 0 >> >em0: XOFF Rcvd = 11 >> >em0: XOFF Xmtd = 0 >> >em0: Good Packets Rcvd = 283923273 >> >em0: Good Packets Xmtd = 272613648 >> >em0: Adapter hardware address = 0xc12cfb48 >> >em0:CTRL = 0x58f00249 >> >em0:RCTL = 0x8002 PS=(0x8402) >> >em0:tx_int_delay = 66, tx_abs_int_delay = 66 >> >em0:rx_int_delay = 0, rx_abs_int_delay = 66 >> >em0: fifo workaround = 0, fifo_reset = 0 >> >em0: hw tdh = 173, hw tdt = 173 >> >em0: Num Tx descriptors avail = 256 >> >em0: Tx Descriptors not avail1 = 0 >> >em0: Tx Descriptors not avail2 = 0 >> >em0: Std mbuf failed = 0 >> >em0: Std mbuf cluster failed = 0 >> >em0: Driver dropped packets = 0 >> > >> >>We're using polling on nearly all the servers, and don't see ierrs at >> >>all. >> > >> > >> >Hm. That's strange. The above values were gathered with polling >> >disabled. As soon as I enable polling, ierrs on the em0 interface are >> >rising: >> > >> >em0: Excessive collisions = 0 >> >em0: Symbol errors = 0 >> >em0: Sequence errors = 0 >> >em0: Defer count = 11 >> >em0: Missed Packets = 39 >> >em0: Receive No Buffers = 2458 >> >em0: Receive length errors = 0 >> >em0: Receive errors = 0 >> >em0: Crc errors = 0 >> >em0: Alignment errors = 0 >> >em0: Carrier extension errors = 0 >> >em0: XON Rcvd = 11 >> >em0: XON Xmtd = 4 >> >em0: XOFF Rcvd = 11 >> >em0: XOFF Xmtd = 43 >> >em0: Good Packets Rcvd = 315880003 >> >em0: Good Packets Xmtd = 303985941 >> >em0: Adapter hardware address = 0xc12cfb48 >> >em0:CTRL = 0x58f00249 >> >em0:RCTL = 0x8002 PS=(0x8402) >> >em0:tx_int_delay = 66, tx_abs_int_delay = 66 >> >em0:rx_int_delay = 0, rx_abs_int_delay = 66 >> >em0: fifo workaround = 0, fifo_reset = 0 >> >em0: hw tdh = 57, hw tdt = 57 >> >em0: Num Tx descriptors avail = 249 >> >em0: Tx Descriptors not avail1 = 0 >> >em0: Tx Descriptors not avail2 = 0 >> >em0: Std mbuf failed = 0 >> >em0: Std mbuf cluster failed = 0 >> >em0: Driver dropped packets = 0 >> > >> > >> >Can you tell me what settings you are using for polling? I have set it >> >to HZ=1000 and burst_max=300. >> > >> >I have now noticed another thing which might indicate one of the >> >possible causes for the problem - this box until now ran FreeBSD 4.x >> >and did not support ipfw tables to lock out whole lists of IP >> >adresses. So there were quite a few inefficient rules for this. I now >> >put all the locked IP addresses in a table which is referenced by only >> >one rule. Since I did this, the ierrs seem to rise slower with polling >> >enabled. > > "Receive No Buffers" grows when polling is enabled and it's somewhat > a normal behaviour. When polling is not enabled, an interrupt will > be generated for each incoming packet and the latter will be soon > removed from the NIC buffer space, whereas when polling is enabled > I think the kernel will check the NIC state upon each soft clock > interrupt (HZ) and fetch them into the memory if any. If too much > packets were received during a period, then the overflow of packets > will be discarded, incrementing the "Receive No Buffers" error count. > I think you can slightly increase the HZ value to decrease this > error count, but I'm not sure this will improve the bandwidth in a > great order of magnitude. > > I know that Intel GigE NICs have a smart way to to interrupt throttling > (that's what tx_int_delay, tx_abs_int_delay, rx_int_delay and > rx_abs_int_delay stand for). You should try to tune them through > dev.em.[0-9]+. sysctl tree. > These tresholds are very well explained here : > http://www.intel.com/design/network/applnots/ap450.pdf > > I hope this will help. > > Please let us know about the results. > > Regards, > -- > Jeremie Le Hen > < jeremie at le-hen dot org >< ttz at chchile dot org > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 02:45:36 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D89616A41F for ; Wed, 5 Oct 2005 02:45:36 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46EA043D45 for ; Wed, 5 Oct 2005 02:45:36 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id C285F19F2C; Tue, 4 Oct 2005 19:50:50 -0700 (PDT) From: "Darren Pilgrim" To: "'Chuck Swiger'" , "'Benjamin Rosenblum'" Date: Tue, 4 Oct 2005 19:45:26 -0700 Message-ID: <000e01c5c956$daca7940$662a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <43429E3B.1080900@mac.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: net@freebsd.org Subject: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 02:45:36 -0000 From: Chuck Swiger > > People who have em NICs, and who do not have problems, probably do not > report regularly that their Intel 10/100/1000 NIC works fine, even > though it does, at least for them. I've got a dozen or so machines > with that hardware, and I haven't seen any problems with them. I'd be interested in finding out the specific chips with which people are (not) having success. As em(4) supports an entire family of products, rather than a single chip, it may be that some chips have quirks or other gotchas the driver needs to address. It certainly wouldn't be the first occurance of revision-specific bugs. From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 02:48:29 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 567D216A41F for ; Wed, 5 Oct 2005 02:48:29 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from mta5.srv.hcvlny.cv.net (mta5.srv.hcvlny.cv.net [167.206.4.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7764B43D6B for ; Wed, 5 Oct 2005 02:48:21 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from [127.0.0.1] (ool-18bbf604.dyn.optonline.net [24.187.246.4]) by mta5.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-2.06 (built May 11 2005)) with ESMTP id <0INV00A9294KRSC1@mta5.srv.hcvlny.cv.net> for net@freebsd.org; Tue, 04 Oct 2005 22:48:21 -0400 (EDT) Date: Tue, 04 Oct 2005 22:48:31 -0400 From: Benjamin Rosenblum In-reply-to: <000e01c5c956$daca7940$662a15ac@smiley> To: net@freebsd.org Message-id: <43433EFF.8040007@benswebs.com> MIME-version: 1.0 X-Accept-Language: en-us, en References: <000e01c5c956$daca7940$662a15ac@smiley> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 02:48:29 -0000 my non working card is 82547EI aka 1000CT. Darren Pilgrim wrote: >From: Chuck Swiger > > >>People who have em NICs, and who do not have problems, probably do not >>report regularly that their Intel 10/100/1000 NIC works fine, even >>though it does, at least for them. I've got a dozen or so machines >>with that hardware, and I haven't seen any problems with them. >> >> > >I'd be interested in finding out the specific chips with which people are >(not) having success. As em(4) supports an entire family of products, >rather than a single chip, it may be that some chips have quirks or other >gotchas the driver needs to address. It certainly wouldn't be the first >occurance of revision-specific bugs. > > > > > > From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 03:34:54 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E900416A41F for ; Wed, 5 Oct 2005 03:34:54 +0000 (GMT) (envelope-from daemon@foxchat.net) Received: from foxsurfer.com (dns1.foxsurfer.com [205.134.229.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2EF043D45 for ; Wed, 5 Oct 2005 03:34:54 +0000 (GMT) (envelope-from daemon@foxchat.net) Received: from [24.172.9.74] (zapper@rrcs-24-172-9-74.midsouth.biz.rr.com [24.172.9.74]) by foxsurfer.com (8.13.3/8.13.3) with ESMTP id j953Yjjr080731 for ; Tue, 4 Oct 2005 20:34:45 -0700 (PDT) (envelope-from daemon@foxchat.net) Message-ID: <434349DA.3070203@foxchat.net> Date: Tue, 04 Oct 2005 23:34:50 -0400 From: Daemon User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930) X-Accept-Language: en-us, en MIME-Version: 1.0 To: net@freebsd.org References: <000e01c5c956$daca7940$662a15ac@smiley> <43433EFF.8040007@benswebs.com> In-Reply-To: <43433EFF.8040007@benswebs.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=9.5 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on FoxSurfer.Com Cc: Subject: Re: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 03:34:55 -0000 Benjamin Rosenblum wrote: > my non working card is 82547EI aka 1000CT. > > Darren Pilgrim wrote: > >> From: Chuck Swiger >> >> >>> People who have em NICs, and who do not have problems, probably do not >>> report regularly that their Intel 10/100/1000 NIC works fine, even >>> though it does, at least for them. I've got a dozen or so machines >>> with that hardware, and I haven't seen any problems with them. >>> >> >> >> I'd be interested in finding out the specific chips with which people are >> (not) having success. As em(4) supports an entire family of products, >> rather than a single chip, it may be that some chips have quirks or other >> gotchas the driver needs to address. It certainly wouldn't be the first >> occurance of revision-specific bugs. >> >> >> >> >> >> > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > I think someone might have already asked this question but I don't recall seeing an answer. I don't mean to stir up a big debate by asking this question but rather to get objective professional opinions from the more experienced FreeBSD users of this list. Given the issues that "seem" to be centered around the em(4) cards, I'd really like to know which 1G brand nic ( or 10/100 for that matter ) card/s has/have a proven track record to work "best" with FreeBSD? From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 03:42:27 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE81416A41F for ; Wed, 5 Oct 2005 03:42:27 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97EF043D46 for ; Wed, 5 Oct 2005 03:42:27 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id C228819F2C; Tue, 4 Oct 2005 20:47:42 -0700 (PDT) From: "Darren Pilgrim" To: "'Benjamin Rosenblum'" , Date: Tue, 4 Oct 2005 20:42:21 -0700 Message-ID: <000f01c5c95e$cddeb2c0$662a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <43433EFF.8040007@benswebs.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: Subject: RE: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 03:42:28 -0000 [Reflowed] From: Benjamin Rosenblum > Darren Pilgrim wrote: >> >> I'd be interested in finding out the specific chips with which people >> are (not) having success. As em(4) supports an entire family of >> products, rather than a single chip, it may be that some chips have >> quirks or other gotchas the driver needs to address. It certainly >> wouldn't be the first occurance of revision-specific bugs. > > my non working card is 82547EI aka 1000CT. Under which version(s) of FreeBSD is it not working? Would an official person care to chime in about putting together a = card/chip vs. em(4) bugs matrix? From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 04:08:42 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D97EC16A41F for ; Wed, 5 Oct 2005 04:08:42 +0000 (GMT) (envelope-from dave-dated-1128917317.27d977@seddon.ca) Received: from seddon.ca (seddon.ca [203.209.212.18]) by mx1.FreeBSD.org (Postfix) with SMTP id CFB4243D45 for ; Wed, 5 Oct 2005 04:08:41 +0000 (GMT) (envelope-from dave-dated-1128917317.27d977@seddon.ca) Received: (qmail 80821 invoked by uid 89); 5 Oct 2005 04:08:37 -0000 Received: by seddon.ca (tmda-sendmail, from uid 89); Wed, 05 Oct 2005 14:08:35 +1000 (EST) References: <000f01c5c95e$cddeb2c0$662a15ac@smiley> In-Reply-To: <000f01c5c95e$cddeb2c0$662a15ac@smiley> To: "Darren Pilgrim" Date: Wed, 05 Oct 2005 14:08:34 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <1128485315.80787.TMDA@seddon.ca> X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Dave+Seddon Cc: 'Benjamin Rosenblum' , net@freebsd.org Subject: Re: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 04:08:43 -0000 Under 5.4 this revision of the em card doesn't work: 82546EB -------------------- em0@pci6:1:0: class=0x020000 card=0x00db0e11 chip=0x10108086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet -------------------- Dave Darren Pilgrim writes: > [Reflowed] > > From: Benjamin Rosenblum >> Darren Pilgrim wrote: >>> >>> I'd be interested in finding out the specific chips with which people >>> are (not) having success. As em(4) supports an entire family of >>> products, rather than a single chip, it may be that some chips have >>> quirks or other gotchas the driver needs to address. It certainly >>> wouldn't be the first occurance of revision-specific bugs. >> >> my non working card is 82547EI aka 1000CT. > > Under which version(s) of FreeBSD is it not working? > > Would an official person care to chime in about putting together a card/chip > vs. em(4) bugs matrix? > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 05:52:33 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6690616A41F for ; Wed, 5 Oct 2005 05:52:33 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from rms06.rommon.net (rms06.rommon.net [212.54.5.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 061D843D46 for ; Wed, 5 Oct 2005 05:52:32 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.234] (dyn234.helenius.fi [193.64.42.234]) by rms06.rommon.net (Postfix) with ESMTP id 50E7733C6F; Wed, 5 Oct 2005 08:52:12 +0300 (EEST) Message-ID: <43436A0E.1060004@he.iki.fi> Date: Wed, 05 Oct 2005 08:52:14 +0300 From: Petri Helenius User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <000e01c5c956$daca7940$662a15ac@smiley> In-Reply-To: <000e01c5c956$daca7940$662a15ac@smiley> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 'Benjamin Rosenblum' , net@freebsd.org Subject: Re: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 05:52:33 -0000 Darren Pilgrim wrote: >I'd be interested in finding out the specific chips with which people are >(not) having success. As em(4) supports an entire family of products, >rather than a single chip, it may be that some chips have quirks or other >gotchas the driver needs to address. It certainly wouldn't be the first >occurance of revision-specific bugs. > > > I would also not discount motherboard / PCI speed related issues. Pete From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 06:05:01 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BD2616A41F for ; Wed, 5 Oct 2005 06:05:01 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF4E043D4C for ; Wed, 5 Oct 2005 06:05:00 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id F0AC219F2C; Tue, 4 Oct 2005 23:10:15 -0700 (PDT) From: "Darren Pilgrim" To: "'Petri Helenius'" Date: Tue, 4 Oct 2005 23:04:54 -0700 Message-ID: <000001c5c972$b7cf0660$662a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <43436A0E.1060004@he.iki.fi> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: net@freebsd.org Subject: RE: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 06:05:01 -0000 From: Petri Helenius [mailto:pete@he.iki.fi]=20 >=20 > Darren Pilgrim wrote: >=20 >> I'd be interested in finding out the specific chips with which people = are >> (not) having success. As em(4) supports an entire family of = products, >> rather than a single chip, it may be that some chips have quirks or = other >> gotchas the driver needs to address. It certainly wouldn't be the = first >> occurance of revision-specific bugs. > > I would also not discount motherboard / PCI speed related issues. Indeed. I've only had a few replies and already have opposing reports. = I'm volunteering to collect the data, but I'll have to talk to someone in a position to do code work about what data should be tracked. From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 06:26:51 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CF1616A41F for ; Wed, 5 Oct 2005 06:26:51 +0000 (GMT) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C507A43D45 for ; Wed, 5 Oct 2005 06:26:50 +0000 (GMT) (envelope-from toasty@dragondata.com) Received: from mail.dragondata.com (server3-b.your.org [64.202.113.67]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id 80DC02AD5591; Wed, 5 Oct 2005 06:49:16 +0000 (UTC) Received: from [69.31.99.45] (pool045.dhcp.your.org [69.31.99.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.dragondata.com (Postfix) with ESMTP id 660AE3D183D; Wed, 5 Oct 2005 01:26:48 -0500 (CDT) In-Reply-To: <1128470191.75484.TMDA@seddon.ca> References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> Content-Transfer-Encoding: 7bit From: Kevin Day Date: Wed, 5 Oct 2005 01:27:09 -0500 To: Dave+Seddon X-Mailer: Apple Mail (2.734) Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 06:26:51 -0000 On Oct 4, 2005, at 6:56 PM, Dave+Seddon wrote: > You mention your running at "near" line rate. What are you pushing > or pulling? Whats the rough spec of these machines pushing out > this much data? What setting do you have for the polling? I've > been trying to do near line rate and can't even get close with new > HP-DL380s (Single 3.4 Ghz Xeon). I think the PCI bus might be the > problem. The em Intel NICs I found to be very slow and stop after > about 3 hours. - The Intel NICs I have are dual port, although > they end up on seperate IRQs. > In one case, we had a system acting as a router. It was a Dell PowerEdge 2650, with two dual "server" adapters. each were on separate PCI busses. 3 were "lan" links, and one was a "wan" link. The lan links were receiving about 300mbps each, all going out the "wan" link at near 900mbps at peak. We were never able to get above 944mbps, but I never cared enough to figure out where the bottleneck was there. This was with PCI-X, and a pretty stripped config on the server side. Nothing fancy on polling, i think we set HZ to 10000, turned on idle_poll, and set user_frac to 10 because we had some cpu hungry tasks that were not a high priority. For anyone watching, the config we had there that we were successful with was: em0@pci2:6:0: class=0x020000 card=0x10118086 chip=0x10108086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet em1@pci2:6:1: class=0x020000 card=0x10118086 chip=0x10108086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet em2@pci1:8:0: class=0x020000 card=0x10128086 chip=0x10128086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller (Fiber)' class = network subclass = ethernet em3@pci1:8:1: class=0x020000 card=0x10128086 chip=0x10128086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller (Fiber)' class = network subclass = ethernet We also have some web servers that are sending 300-400mbps each at peak using thttpd or lighttpd, with the built in Dell 2850 em parts. They also are connected via PCI-X speed buses internally. From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 08:53:58 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F0316A41F; Wed, 5 Oct 2005 08:53:57 +0000 (GMT) (envelope-from raglon@packetfront.com) Received: from mail.packetfront.com (mail.packetfront.com [212.247.6.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3034043D45; Wed, 5 Oct 2005 08:53:56 +0000 (GMT) (envelope-from raglon@packetfront.com) Received: from localhost (localhost [127.0.0.1]) by mail.packetfront.com (Postfix) with ESMTP id 40C86A3F73; Wed, 5 Oct 2005 10:53:55 +0200 (CEST) Received: from mail.packetfront.com ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05474-09; Wed, 5 Oct 2005 10:53:54 +0200 (CEST) Received: from [192.168.1.159] (pf-raglon.int.packetfront.com [192.168.1.159]) by mail.packetfront.com (Postfix) with ESMTP id E98ABA3F68; Wed, 5 Oct 2005 10:53:54 +0200 (CEST) Message-ID: <43439446.7090400@packetfront.com> Date: Wed, 05 Oct 2005 10:52:22 +0200 From: Ragnar Lonn User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John-Mark Gurney References: <20051003130731.GF56760@submonkey.net> <20051003134132.GE73935@cell.sick.ru> <20051003135324.GH56760@submonkey.net> <4342B4BE.1040304@packetfront.com> <20051004203645.GO716@funkthat.com> In-Reply-To: <20051004203645.GO716@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at packetfront.com Cc: Ceri Davies , Gleb Smirnoff , net@FreeBSD.org Subject: Re: ng_tee, right2left, et al X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 08:53:58 -0000 John-Mark Gurney wrote: >Ragnar Lonn wrote this message on Tue, Oct 04, 2005 at 18:58 +0200: > > >>Ceri Davies wrote: >> >> >> >>>I only call it "wrong" as it didn't agree with Archie's article or my >>>expectations, hence the quotes - I realise that it's subjective. >>> >>>It just seems to me that packets leaving left2right would go to right, >>>as the name implies. I don't really mind either way, it's simply that >>>I found it confusing. >>> >>> >>> >>> >>It's not, really. A good idea is to draw the tee node and its hooks on a >>piece of paper. >>Here is an ASCII attempt: >> >> >>left --- right >> \ / >> x >> / \ >> r2l l2r >> >>The drawing shows that the left hook is associated with the left2right hook: >>When packets come in on the left hook they are forwarded to the left2right >>hook. Logically, that means they are connected, like in the drawing above, >>and that also means that packets can go in the other direction - i.e. from >>the left2right hook and to the left hook. >> >> > >I personally imagined the picture like: > l2r > >>>>^>>>> > / \ > left right > \ / > << r2l > >where the l2r and r2l are taps into the line that goes a certain way... and >so, it'd mean that sending a package on the r2l hook goes to left instead >of right.. not that I use net graph much, but just thought I'd show how >I thought of it... > >Though if the behavior matches what the man page states, that's all that >matters, and my drawing is invalidated... > > > For me, the behaviour was intuitive. Maybe it depends on whether you're familiar with the Unix "tee" command or not, how you look at it? "tee" is used to duplicate a one-way (output) stream, so I've always thought of the hooks right2left and left2right as one-way output hooks. Think of the tee node as a connector between left and right, with the option to "wiretap" traffic going either from right to left, or from left to right. To do this wiretapping you have two hooks where you can snoop the traffic going in either direction. One hook for snooping traffic left->right and one hook for snooping traffic right->left. The option to input traffic into one of these "tap" hooks is just a bonus feature. And maybe it's more confusing than useful, I'm not sure. It seems that if you want to output traffic on the right hook, all you have to do is input it on the left hook, and vice versa. Of course, you'd have to use a hub or bridge to connect more than one node to the hook then. /Ragnar From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 10:47:54 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AC2C16A426; Wed, 5 Oct 2005 10:47:54 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23E1143D48; Wed, 5 Oct 2005 10:47:52 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (xabufw@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j95Alpku091129; Wed, 5 Oct 2005 12:47:51 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j95Alp81091128; Wed, 5 Oct 2005 12:47:51 +0200 (CEST) (envelope-from olli) Date: Wed, 5 Oct 2005 12:47:51 +0200 (CEST) Message-Id: <200510051047.j95Alp81091128@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <43439F3B.1040903@axis.nl> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: Re: How to best set-up a small local 'sync' network next to the live network? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 10:47:54 -0000 Hi, (This doesn't seem to be AMD64-specific, so I think it should be moved to the -net mailing list.) Olaf Greve wrote: > [Setting up two machines with fall-back] > > Primary server: > - Runs FreeBSD 5.4-Release AMD64 > - Connected to outside world via NIC 1 @ a real IP address; say > 123.45.67.89, publicly available as webserver incl. DNS mappings, etc. > - Connected via a cross-wire cable to fall-back machine via NIC 2 ; > using address 192.168.1.1 > > Fall-back server: > - Runs FreeBSD 5.2.1-Release i386 > - Connected to outside world via NIC 1 @ a real IP address; say > 123.45.67.88, "privately" available by IP address only (mainly for SSH > access, serves as fall-back and staging machine) > - Connected via a cross-wire cable to primary server machine via NIC 2 ; > using address 192.168.1.2 > > [...] > -How can I best set-up such a dual network configuration, such that one > network will not interfere with the other? You machines have different IP addresses, so there is no conflict. It should work fine. > -Can I somehow 'force' the machines to automatically interpret anything > in the 192.168.1.x range to be local, and hence automatically use NIC 2, > instead of using the NIC 1 adapter (which handles my outside world traffic)? That will happen automatically. When you ifconfig an IP on your NIC 2, it will automatically add an appropriate route for that subnet on that NIC. > -Is it sufficient to set-up the Rsync daemon on the primary machine to > only allow connections from 192.168.1.2, and to run as root, such that I > can easily use the cross-wire as a kind of direct tunnel to perform the > syncing? Yes. You should make sure that rsync is blocked on the outside interfaces (using IPFW, IPFilter or PF). Personally I don't think that rsync is the best way to perform such a mirror. There are other possibilities. But if you prefer rsync, it should work. > -What is the nicest MySQL replication mechanism? Presently I use a > mechanism that dumps the MySQL DB instances, and will then push them > over an SSH tunnel to the fall-back machine, directly loading them into > the MySQL DB on that machine. Is MySQL's master-slave syncing perhaps a > better choice? My personal recommendation is to use PostgreSQL 8. Its WAL logging feature is very well suited to synchronize one or more slave machines, and it's rock stable and fast. However, if you application is Mysql-specific and cannot easily be ported to PostgreSQL, then I'm afraid that wasn't the answer you expected. :-) Mysql supports some sort of replication, too, though. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies." -- C.A.R. Hoare, ACM Turing Award Lecture, 1980 From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 10:48:07 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FA5316A420 for ; Wed, 5 Oct 2005 10:48:07 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EB2843D48 for ; Wed, 5 Oct 2005 10:48:05 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j95Am0f5038407 for ; Wed, 5 Oct 2005 12:48:00 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id 01FF4228019 for ; Wed, 5 Oct 2005 12:47:59 +0200 (CEST) Message-ID: <4343AF62.7030701@jku.at> Date: Wed, 05 Oct 2005 12:48:02 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org References: <000e01c5c956$daca7940$662a15ac@smiley> In-Reply-To: <000e01c5c956$daca7940$662a15ac@smiley> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 10:48:07 -0000 Darren Pilgrim wrote: > I'd be interested in finding out the specific chips with which people are > (not) having success. As em(4) supports an entire family of products, > rather than a single chip, it may be that some chips have quirks or other > gotchas the driver needs to address. It certainly wouldn't be the first > occurance of revision-specific bugs. My troublesome card is a device = '82545GM Gigabit Ethernet Controller' But I am not sure if it is of any use compiling such a list, because the various hardware platforms and network requirements on which people test their cards are very different. -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 10:58:21 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19AB216A41F for ; Wed, 5 Oct 2005 10:58:21 +0000 (GMT) (envelope-from babolo@cicuta.babolo.ru) Received: from ints.mail.pike.ru (ints.mail.pike.ru [85.30.199.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC7A43D46 for ; Wed, 5 Oct 2005 10:58:17 +0000 (GMT) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 54963 invoked from network); 5 Oct 2005 10:58:01 -0000 Received: from cicuta.babolo.ru (85.30.224.245) by ints.mail.pike.ru with SMTP; 5 Oct 2005 10:58:01 -0000 Received: (nullmailer pid 8754 invoked by uid 136); Wed, 05 Oct 2005 11:01:38 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <1128485315.80787.TMDA@seddon.ca> To: "Dave+Seddon" Date: Wed, 5 Oct 2005 15:01:38 +0400 (MSD) From: .@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1128510098.391180.8753.nullmailer@cicuta.babolo.ru> Cc: 'Benjamin Rosenblum' , Darren Pilgrim , net@freebsd.org Subject: Re: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 10:58:21 -0000 [ Charset UTF-8 unsupported, converting... ] > > Would an official person care to chime in about putting together a card/chip > > vs. em(4) bugs matrix? No sense, because bugs depend not on/only card/chip, but at least load. In my expierence quality of em interface depends on quantity of ipfw rules, pipes and on traffic load. From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 11:04:44 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7FB516A41F for ; Wed, 5 Oct 2005 11:04:44 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A3AD43D48 for ; Wed, 5 Oct 2005 11:04:43 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j95B4drL043047 for ; Wed, 5 Oct 2005 13:04:39 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id 48808228019 for ; Wed, 5 Oct 2005 13:04:39 +0200 (CEST) Message-ID: <4343B34A.6020308@jku.at> Date: Wed, 05 Oct 2005 13:04:42 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> In-Reply-To: <20051004161217.GB43195@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 11:04:44 -0000 Jeremie Le Hen wrote: >>> em0: Missed Packets = 39 >>> em0: Receive No Buffers = 2458 > > "Receive No Buffers" grows when polling is enabled and it's somewhat > a normal behaviour. After running with polling enabled for two hours, the statistics were: em0: Missed Packets = 2159959 em0: Receive No Buffers = 32458174 em0: Good Packets Rcvd = 499051709 em0: Good Packets Xmtd = 466744805 That's quite a lot of missed packets in only ~two hours :-( > I think you can slightly increase the HZ value to decrease this > error count, but I'm not sure this will improve the bandwidth in a > great order of magnitude. Hm it would be interesting how to optimize the HZ value in order to prevent lost packets, because this is not good at all. > I know that Intel GigE NICs have a smart way to to interrupt throttling > (that's what tx_int_delay, tx_abs_int_delay, rx_int_delay and > rx_abs_int_delay stand for). You should try to tune them through > dev.em.[0-9]+. sysctl tree. > These tresholds are very well explained here : > http://www.intel.com/design/network/applnots/ap450.pdf Thank you for the pointer, I will have a look at this and see whether this helps, and post the results. -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 11:49:09 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A70816A41F; Wed, 5 Oct 2005 11:49:09 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 778C743D48; Wed, 5 Oct 2005 11:49:08 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j95Bn5Fe004979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 15:49:06 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j95Bn5Sw004978; Wed, 5 Oct 2005 15:49:05 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 5 Oct 2005 15:49:05 +0400 From: Gleb Smirnoff To: thompsa@FreeBSD.org, mlaier@FreeBSD.org Message-ID: <20051005114905.GB4291@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.6i Cc: net@FreeBSD.org Subject: bridge and ng_ether deja vu X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 11:49:09 -0000 Andrew, Max, exactly after one year I see if_bridge(4) having the same problem with ng_ether(4) as old bridge(4) had. The problem is that packets flowed thru ng_ether miss bridge processing. The problem is explained well in this mail: http://lists.freebsd.org/mailman/htdig/freebsd-net/2004-May/003881.html It applies to if_bridge, too. There was two ways to fix the problem: 1) Split ether_input() into ether_input()+ether_input_frame(), like to ether_output is split. In this case ether_input() must end up with ng_ether call and ether_input_frame(). ether_input_frame() does all bridge(4) processing and calls ether_demux(). ng_ether_rcv_upper() simply calls ether_input_frame(). 2) Copy and paste the bridge processing into ng_ether_rcv_upper(). We (me, sam, andre) have choosed the second way: http://lists.freebsd.org/pipermail/cvs-src/2004-October/033496.html However, I have cut all the bridge stuff from if_ethersubr.c and moved it into bridge.c. This is how it looked like: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/net/if_ethersubr.c.diff?r1=1.178&r2=1.179&f=h Now I notice the same problem with if_bridge. And I decided to go second way again, but noticed that unfortunately I again have to copy and paste > 20 lines from if_ethersubr.c to ng_ether.c. So, the question is: is it possible to push the block about ETHER_IS_MULTICAST into bridge_input()? This will make copy and paste region smaller. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 12:21:50 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B6D116A41F for ; Wed, 5 Oct 2005 12:21:50 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC6A443D45 for ; Wed, 5 Oct 2005 12:21:48 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j95CLhv4062106 for ; Wed, 5 Oct 2005 14:21:43 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id 2DB75228019 for ; Wed, 5 Oct 2005 14:21:43 +0200 (CEST) Message-ID: <4343C559.5000000@jku.at> Date: Wed, 05 Oct 2005 14:21:45 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> In-Reply-To: <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 12:21:50 -0000 Kevin Day wrote: > In one case, we had a system acting as a router. It was a Dell PowerEdge > 2650, with two dual "server" adapters. each were on separate PCI busses. > 3 were "lan" links, and one was a "wan" link. The lan links were > receiving about 300mbps each, all going out the "wan" link at near > 900mbps at peak. We were never able to get above 944mbps, but I never > cared enough to figure out where the bottleneck was there. 944mbps is a very good value, anyway. What we see in our setup are throuput rates around 300mbps or below. When testing with tcpspray, throughput hardly exceeded 13MB/s. Are you running vlans on your interface? Our em0-card connects several sites together, which are all sitting on separate vlan interfaces for which the em0 acts as parent interface. > This was with PCI-X, and a pretty stripped config on the server side. Maybe this makes a difference, too. We only have a quite old xSeries 330 with PCI and a 1.2GHz CPU. > > Nothing fancy on polling, i think we set HZ to 10000 Ten-thousand? Or is this a typo, and did you mean thousand? This is weird. :-( Please, is there any good documentation on tuning device polling? The man page does not give any useful pointers about values to use for Gbit cards. I have already read things about people using 2000, 4000HZ ... Gaaah! I tried with 1000 and 2000 so far, without good results. It seems like everybody makes wild assumptions on what values to use for polling. >, turned on > idle_poll, and set user_frac to 10 because we had some cpu hungry tasks > that were not a high priority. I think I red somewhere about problems with idle_poll. How high is your burst_max value? Are you seeing a lot of ierrs? *sigh* :-( confusing. -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 12:24:25 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F3C916A41F for ; Wed, 5 Oct 2005 12:24:25 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from mail2.edvz.uni-linz.ac.at (mail2.edvz.uni-linz.ac.at [140.78.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2277A43D68 for ; Wed, 5 Oct 2005 12:24:23 +0000 (GMT) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mail2.edvz.uni-linz.ac.at (8.13.3/8.13.3) with ESMTP id j95COIQH062651 for ; Wed, 5 Oct 2005 14:24:18 +0200 (CEST) (envelope-from ferdinand.goldmann@jku.at) Received: from [140.78.164.13] (jku006048.edvz.uni-linz.ac.at [140.78.6.48]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTP id F1F4C228019 for ; Wed, 5 Oct 2005 14:24:17 +0200 (CEST) Message-ID: <4343C5F4.5060805@jku.at> Date: Wed, 05 Oct 2005 14:24:20 +0200 From: Ferdinand Goldmann Organization: Johannes Kepler University User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: net@freebsd.org References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> In-Reply-To: <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ferdinand.goldmann@jku.at List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 12:24:25 -0000 Kevin Day wrote: > In one case, we had a system acting as a router. It was a Dell PowerEdge > 2650, with two dual "server" adapters. each were on separate PCI busses. > 3 were "lan" links, and one was a "wan" link. The lan links were > receiving about 300mbps each, all going out the "wan" link at near > 900mbps at peak. We were never able to get above 944mbps, but I never > cared enough to figure out where the bottleneck was there. Forgot to ask - do you have fastforwarding enabled in your sysctl? -- >> Ferdinand Goldmann //// | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 12:51:57 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A681116A41F for ; Wed, 5 Oct 2005 12:51:57 +0000 (GMT) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C739043D46 for ; Wed, 5 Oct 2005 12:51:56 +0000 (GMT) (envelope-from toasty@dragondata.com) Received: from mail.dragondata.com (server3-b.your.org [64.202.113.67]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id 33D322AD55EF; Wed, 5 Oct 2005 13:14:26 +0000 (UTC) Received: from [69.31.99.45] (pool045.dhcp.your.org [69.31.99.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.dragondata.com (Postfix) with ESMTP id 78FDF3D1848; Wed, 5 Oct 2005 07:51:54 -0500 (CDT) In-Reply-To: <4343C559.5000000@jku.at> References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> <4343C559.5000000@jku.at> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kevin Day Date: Wed, 5 Oct 2005 07:52:16 -0500 To: ferdinand.goldmann@jku.at X-Mailer: Apple Mail (2.734) Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 12:51:57 -0000 On Oct 5, 2005, at 7:21 AM, Ferdinand Goldmann wrote: > >> In one case, we had a system acting as a router. It was a Dell >> PowerEdge 2650, with two dual "server" adapters. each were on >> separate PCI busses. 3 were "lan" links, and one was a "wan" link. >> The lan links were receiving about 300mbps each, all going out the >> "wan" link at near 900mbps at peak. We were never able to get >> above 944mbps, but I never cared enough to figure out where the >> bottleneck was there. >> > > 944mbps is a very good value, anyway. What we see in our setup are > throuput rates around 300mbps or below. When testing with tcpspray, > throughput hardly exceeded 13MB/s. > > Are you running vlans on your interface? Our em0-card connects > several sites together, which are all sitting on separate vlan > interfaces for which the em0 acts as parent interface. > Two of the interfaces had vlans, two didn't. > >> This was with PCI-X, and a pretty stripped config on the server side. >> > > Maybe this makes a difference, too. We only have a quite old > xSeries 330 with PCI and a 1.2GHz CPU. > I think that's a really important key. If you're running a "normal" 32 bit 33MHz PCI bus, the math just doesn't work for high speeds. The entire bandwidth of the bus is just a tad over 1gbps. Assuming 100% efficiency (you receive a packet, then turn around and resend it immediately) you'll only be able to reach 500mbps. When you add in the overhead of each PCI transaction, the fact that the CPU can't instantly turn around and send data out the same cycle that the last packet was finished being received, and other inefficiencies you will probably only see something in the 250-300mbps range at MOST, if that. I believe the xSeries 330 uses 64 bit 33MHz slots though. That gives you double the bandwidth to play with. But, I'm still not convinced that the CPU isn't the bottleneck there. If you know you're running 64/33 in the slot you have the card in, I'd be willing to say you could do 500mbps or so at peak. A bunch of IPFW rules, the CPU just not being able to keep up, other activity on the system, or a complex routing table will reduce that. Just to sum up: A 64/33MHz bus has the theoretical speed of 2gbps. If you're forwarding packets in one interface then out another, you have to cut that in half. PCI is half duplex, you can't receive and send at the same time. This leaves 1gbps left. PCI itself isn't 100% efficient. You burn cycles setting up each PCI transaction. When the card busmasters to dump the packet into RAM, it frequently will have to wait for the memory controller to proceed. The ethernet card itself requires some PCI bandwidth to operate - the kernel needs to check its registers, the card has to update pointers in ram for the busmaster circular buffer, etc. All those things take time on the PCI bus, leaving maybe 750-800mbps left for actual data. The rest of the system isn't 100% efficient either. The CPU/kernel/ etc can't immediately turn around a packet to send out the instant it's received, further lowering your overall bandwidth limit. I've done a lot of work on custom ethernet interfaces both in FreeBSD and in custom embedded OS projects. The safe bet is to assume that you can route/forward 250mbps on 32/33 and 500mbps on 64/33 if you have enough CPU efficiency to fill the bus. > >> Nothing fancy on polling, i think we set HZ to 10000 >> > > Ten-thousand? Or is this a typo, and did you mean thousand? > > This is weird. :-( Please, is there any good documentation on > tuning device polling? The man page does not give any useful > pointers about values to use for Gbit cards. I have already read > things about people using 2000, 4000HZ ... Gaaah! > > I tried with 1000 and 2000 so far, without good results. It seems > like everybody makes wild assumptions on what values to use for > polling. > We arrived at 10000 by experimentation. A large number of interfaces, a ton of traffic... I'm not sure the complete reasons why it helped, but it did. > >> , turned on idle_poll, and set user_frac to 10 because we had some >> cpu hungry tasks that were not a high priority. >> > > I think I red somewhere about problems with idle_poll. How high is > your burst_max value? Are you seeing a lot of ierrs? > No ierrs at all, and we never touched burst_max. In the end, if you're getting "Receive No Buffers" incrementing, that basically means what it implies. The ethernet chip received a packet and was out of room to store it because the CPU hadn't dumped the receive buffers from previous packets yet. Either the CPU is too busy and can't keep up, the PCI bus is being saturated and the ethernet chip can't move packets out of its tiny internal memory fast enough, or there is some polling problem that's being hit here. If I had to bet, what I think is happening is that you've got a bottleneck somewhere (ipfw rules, not enough CPU, too much PCI activity, or you're in a 32/33 PCI slot) and it can't keep up with what you're doing. Turning polling on is exposing different symptoms of this than having polling off. Polling may be increasing your overall speed enough that instead of having packets getting backed up in the kernel and stopping you from going higher than XXmbps, with polling you're getting to XXXmbps and seeing a new symptom of a bottleneck. > Forgot to ask - do you have fastforwarding enabled in your sysctl? No. But we were running either 2.8 or 3.2GHz P4 Xeons, so we had the CPU to burn. From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 12:58:45 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8172816A41F for ; Wed, 5 Oct 2005 12:58:45 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from fep16.inet.fi (fep16.inet.fi [194.251.242.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99BE243D48 for ; Wed, 5 Oct 2005 12:58:44 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [192.168.0.20] ([84.249.3.49]) by fep16.inet.fi with ESMTP id <20051005125843.YCNV26717.fep16.inet.fi@[192.168.0.20]>; Wed, 5 Oct 2005 15:58:43 +0300 Message-ID: <4343CE03.7090008@pp.nic.fi> Date: Wed, 05 Oct 2005 15:58:43 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 6.0-BETA5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ferdinand.goldmann@jku.at References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> <4343C559.5000000@jku.at> In-Reply-To: <4343C559.5000000@jku.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 12:58:45 -0000 Ferdinand Goldmann wrote: > 944mbps is a very good value, anyway. What we see in our setup are > throuput rates around 300mbps or below. When testing with tcpspray, > throughput hardly exceeded 13MB/s. Increasing MTU should help to get better results, as long all devices in network support jumbo frames (at least on large files). 9k or even 16k might be supported. From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 13:14:01 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F230B16A4C8 for ; Wed, 5 Oct 2005 13:14:00 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A7B743D53 for ; Wed, 5 Oct 2005 13:13:59 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j95DDvFx006607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 17:13:58 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j95DDvls006606; Wed, 5 Oct 2005 17:13:57 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 5 Oct 2005 17:13:57 +0400 From: Gleb Smirnoff To: Ferdinand Goldmann Message-ID: <20051005131357.GC5066@cell.sick.ru> References: <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> <4343C5F4.5060805@jku.at> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4343C5F4.5060805@jku.at> User-Agent: Mutt/1.5.6i Cc: net@FreeBSD.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 13:14:01 -0000 On Wed, Oct 05, 2005 at 02:24:20PM +0200, Ferdinand Goldmann wrote: F> >In one case, we had a system acting as a router. It was a Dell PowerEdge F> >2650, with two dual "server" adapters. each were on separate PCI busses. F> >3 were "lan" links, and one was a "wan" link. The lan links were F> >receiving about 300mbps each, all going out the "wan" link at near F> >900mbps at peak. We were never able to get above 944mbps, but I never F> >cared enough to figure out where the bottleneck was there. F> F> Forgot to ask - do you have fastforwarding enabled in your sysctl? If you enable fastforwarding, but do not disable polling, thiw won't lead to any difference. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 16:12:15 2005 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAE4516A41F; Wed, 5 Oct 2005 16:12:15 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C07643D45; Wed, 5 Oct 2005 16:12:15 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 83C5C46BA4; Wed, 5 Oct 2005 12:12:14 -0400 (EDT) Date: Wed, 5 Oct 2005 17:12:14 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: performance@FreeBSD.org Message-ID: <20051005133730.R87201@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: net@FreeBSD.org Subject: Call for performance evaluation: net.isr.direct X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 16:12:16 -0000 In 2003, Jonathan Lemon added initial support for direct dispatch of netisr handlers from the calling thread, as part of his DARPA/NAI Labs contract in the DARPA CHATS research program. Over the last two years since then, Sam Leffler and I have worked to refine this implementation, removing a number of ordering related issues, opportunities for excessive parallelism, recursion issues, and testing with a broad range of network components. There has also been a significant effort to complete MPSAFE locking work throughout the network stack. Combined with the earlier move to ithreads and a functional direct dispatch ("process to completion" implementation), there are a number of exciting possible benefits. - Possible parallelism by packet source -- ithreads can dispatch simultaenously into the higher level network stack layers. Since ithreads can execute in parallel on different CPU, so can code they invoke directly. - Elimination of context switches in the network receive path -- rather than context switching to the netisr thread from the ithread, we can now directly execute netisr code from the ithread. - A CPU-bound netisr thread on a multi-processor system will no longer rate limit traffic to the available resources on one CPU. - Eliminating the additional queueing in the handoff reduces the opportunity for queues to overfill as a result of scheduling delays. There are, however, some possible downsides and/or trade-offs: - Higher level network processing will now compete with the interrupt handler for CPU resources available to the ithread. This means less time for the interrupt code to execute in the thread if the thread is CPU-bound. - Lower levels of parallelism between portions of the inbound packet processing path. Without direct dispatch, there is possible parallelism between receive network driver execution and higher level stack layers, whereas with direct dispatch they can no longer execute in parallel. - Re-queued packets from tunnel and encapsulation processing will now require a context switch to process, since they will be processed in the netisr proper rather than in the ithread, whereas before the netisr thread would pick them up immediately after completing the current processing without a context switch. - Code that previously ran in the SWI at a SWI priority now runs in the ithread at an ithread priority, elevating the general priority at which network processing takes place. And there are a few mixed things, that can offer good and bad elements: - Less queueing takes place in the network stack in in-bound processing: packets are taken directly from the driver and processed to completion one by one, rather than queued for batch processing. Packets will be dropped before the link layer, rather than on the boundary between the link and protocol layers. This is good in that we invest less work in packets we were going to drop anyway, but bad in that less queueing means less room for scheduling delays. In previous FreeBSD releases, such as several 5.x series releases, net.isr.enable could not be turned on by default because there was insufficient synchronization in the network stack. As of 5.5 and 6.0, I believe there is sufficient synchronization, especially given that we force non-MPSAFE protocol handlers to run in the netisr without direct dispatch. As such, there has been a gradual conversation going on about making direct dispatch the default behavior in the 7.x development series, and more publically documenting and supporting the use of direct dispatch in the 6.x release engineering series. Obviously, this is about two things: performance, and stability. Many of us have been running with direct dispatch on by default for quite some time, so it passes some of the basic "does it run" tests. However, since it significantly increases the opportunity for parallelism in the receive path of the network stack, it likely will trigger otherwise latent or infrequent races and bugs to occur more frequently. The second aspect is performance: many results suggest that direct dispatch has a significant performance benefit. However, evaluating the impact on a broad range of results is required in order for us to go ahead with what is effectively a significant architectural change in how we perform network stack processing. To give you a sense of some of the performance effect I've measured recently, using the netperf measurement tool (with -DHISTOGRAM removed from the FreeBSD port build), here are some results. In each case, I've put parenthesis around host or router to indicate which is the host where the configuration change is being tested. These tests were performed using dual Xeon systems, and using back-to-back gigabit ethernet cards and the if_em driver: TCP round trip benchmark (TCP_RR), host-(host): 7.x UP: 0.9% performance improvement 7.x SMP: 0.7% performance improvement TCP round trip benchmark (TCP_RR), host-(router)-host: 7.x UP: 2.4% performance improvement 7.x SMP: 2.9% performance improvement UDP round trip benchmark (UDP_RR), host-(host): 7.x UP: 0.7% performance improvement 7.x SMP: 0.6% performance improvement UDP round trip benchmark (UDP_RR), host-(router)-host: 7.x UP: 2.2% performance improvement 7.x SMP: 3.0% performance improvement TCP stream banchmark (TCP_STREAM), host-(host): 7.x UP: 0.8% performance improvement 7.x SMP: 1.8% performance improvement TCP stream benchmark (TCP_STREAM), host-(router)-host: 7.x UP: 13.6% performance improvement 7.x SMP: 15.7% performance improvement UDP stream benchmark (UDP_STREAM), host-(host): 7.x UP: none 7.x SMP: none UDP stream benchmark (UDP_STREAM), host-(router)-host: 7.x UP: none 7.x SMP: none TCP connect benchmark (src/tools/tools/netrate/tcpconnect) 7.x UP: 7.90383% +/- 0.553773% 7.x SMP: 12.2391% +/- 0.500561% So in some cases, the impact is negligible -- in other places, it is quite significant. So far, I've not measured a case where performance has gotten worse, but that's probably because I've only been measuring a limited number of cases, and with a fairly limited scope of configurations, especially given that the hardware I have is pushing the limits of what the wire supports, so minor changes in latency are possible, but not large changes in throughput. So other than a summary of the status quo, this is also a call to action. I would like to get more widespread benchmarking of the impact of direct dispatch on network-related workloads. This means a variety of things: (1) Performance of low level network services, such as routing, bridging, and filtering. (2) Performance of high level application servces, such as web and database. (3) Performance of integrated kernel network services, such as the NFS client and server. (4) Performance of user space distributed file systems, such as Samba and AFS. All you need to do to switch to direct dispatch mode is set the sysctl or tunable "net.isr.dispatch" to 1. To disable it again, remove the setting, or set it to 0. It can be modified at run-time, although during the transition from one mode to the other, there may be a small quantity of packet misordering, so benchmarking over the transition is discouraged. FYI: as of 6.0-RC1 and recent 7.0, net.isr.dispatch is the name of the variable. In earlier releases, the name of this variable was net.isr.enable. Some important details: - Only non-local protocol traffic is affected: loopback traffic still goes via the netisr to avoid issues of recursion and lock order. - In the general case, only in-bound traffic is directly affected by this change. As such, send-only benchmarks may reveal little change. They are still interesting, however. - However, the send path is indirectly affected due to changes in scheduling, workload, interrupt handling, and so on. - Because network benchmarks, especially micro-benchmarks, are especially sensitive to minor perturbations, I highly recommend running in a minimal multi-user or ideally single-user environment, and suggest isolating undesired sources of network traffic from segments where testing is occuring. For macro-benchmarks this can be less important, but should be paid attention to. - Please make sure debugging features are turned off when running tests -- especially WITNESS, INVARIANTS, INVARIANT_SUPPORT, and user space malloc debugging. These can have a significant impact on performance, both potentially overshadowing changes, and in some cases, actually reversing results (due to higher overhead under locks, for example). - Do not use net.isr.enable in the 5.x line unless you know what you are doing. While it is reasonably safe with 5.4 forwards, it is not a supported configuration, and may cause stability issues with specific workloads. - What we're particularly interested in is a statistically meaningful comparison of the "before" and "after" case. When doing measurements, I like to run 10-12 samples, and usually discard the first one or two, depending on the details of the benchmark. I'll then use src/tools/tools/ministat to compare the data sets. Running a number of samples is quite important, because the variance in many tests can be significant, and if the two sample sets overlap, you can quite easily draw the entirely wrong conclusion about the results from a small number of measurements in a sample. Assuming you have a fixed width font, typicaly output from ministat looks something like the following and may be human readable: x 7SMP/tcpconnect_queue + 7SMP/tcpconnect_direct +--------------------------------------------------------------------------+ |x xx + +| |xxxxx xx ++ +++++ +| ||__A__| |___A__| | +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 10 5425 5503 5460 5456.3 26.284977 + 10 6074 6169 6126 6124.1 31.606785 Difference at 95.0% confidence 667.8 +/- 27.3121 12.2391% +/- 0.500561% (Student's t, pooled s = 29.0679) Of particular interest is if changing to direct dispatch hurts performance in your environment, and understanding why that is. Thanks, Robert N M Watson From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 20:32:05 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEC2A16A41F for ; Wed, 5 Oct 2005 20:32:05 +0000 (GMT) (envelope-from daniel@dgnetwork.com.br) Received: from zeus.yan.com.br (zeus.yan.com.br [200.202.253.10]) by mx1.FreeBSD.org (Postfix) with SMTP id A69D343D4C for ; Wed, 5 Oct 2005 20:32:01 +0000 (GMT) (envelope-from daniel@dgnetwork.com.br) Received: (qmail 2073 invoked by uid 1023); 5 Oct 2005 20:31:43 -0000 Received: from daniel@dgnetwork.com.br by zeus by uid 1023 with qmail-scanner-1.22 (uvscan: v4.1.60/v4366. fsecure: 4.11/3190/2003-09-23/2002-12-17. 2003-09-22/. Clear:RC:1(200.202.253.197):. Processed in 0.648481 secs); 05 Oct 2005 20:31:43 -0000 Received: from unknown (HELO ?192.168.1.1?) (daniel@dgnetwork.com.br@200.202.253.197) by zeus.yan.com.br with SMTP; 5 Oct 2005 20:31:42 -0000 Message-ID: <4344383B.4000405@dgnetwork.com.br> Date: Wed, 05 Oct 2005 17:31:55 -0300 From: =?ISO-8859-1?Q?Daniel_Dias_Gon=E7alves?= Organization: DGNET Network Solutions User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: pt-br, pt MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: IPFW+DUMMYNET UPLOAD PROBLEM X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: daniel@dgnetwork.com.br List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 20:32:06 -0000 I have the following rules: $fwcmd add 600 pipe 602 src-ip 192.168.0.0/24 out $fwcmd add 601 pipe 603 dst-ip 192.168.0.0/24 in $fwcmd pipe 602 config mask src-ip 0x000000ff bw 128Kbit/s queue 10KBytes $fwcmd pipe 603 config mask dst-ip 0x000000ff bw 128Kbit/s queue 10KBytes And my test speed from ip 192.168.0.5 is: Down 123.66kbps Up 766.24kbps Which the problem? -- Daniel Dias Gonçalves DGNET Network Solutions daniel@dgnetwork.com.br (37) 99824809 From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 23:22:25 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78BD316A41F for ; Wed, 5 Oct 2005 23:22:25 +0000 (GMT) (envelope-from dave-dated-1128986539.c8b6a2@seddon.ca) Received: from seddon.ca (seddon.ca [203.209.212.18]) by mx1.FreeBSD.org (Postfix) with SMTP id D033B43D46 for ; Wed, 5 Oct 2005 23:22:24 +0000 (GMT) (envelope-from dave-dated-1128986539.c8b6a2@seddon.ca) Received: (qmail 19963 invoked by uid 89); 5 Oct 2005 23:22:20 -0000 Received: by seddon.ca (tmda-sendmail, from uid 89); Thu, 06 Oct 2005 09:22:19 +1000 (EST) References: <4341089F.7010504@jku.at> <20051003104548.GB70355@cell.sick.ru> <4341242F.9060602@jku.at> <20051003123210.GF70355@cell.sick.ru> <43426EF3.3020404@jku.at> <9CD8C672-1EF2-42FE-A61E-83DC684C893D@dragondata.com> <43429157.90606@jku.at> <4342987D.7000200@benswebs.com> <20051004161217.GB43195@obiwan.tataz.chchile.org> <1128470191.75484.TMDA@seddon.ca> <979B163D-7078-4558-9095-DC329707A5B4@dragondata.com> <4343C559.5000000@jku.at> In-Reply-To: <4343C559.5000000@jku.at> To: ferdinand.goldmann@jku.at Date: Thu, 06 Oct 2005 09:22:17 +1000 Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <1128554539.19942.TMDA@seddon.ca> X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Dave+Seddon Cc: net@freebsd.org Subject: Re: dummynet, em driver, device polling issues :-(( X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 23:22:25 -0000 Greetings, The default values are based on 100 MB/s fxp driver. Luigi did heaps of work a few years ago on this, and arrived at these values after lots of testing (i think). (I also remember reading some interesting stuff where he had fxp and a 3com card and was testing to see how many frames he could push out of each differnet card - fxp won!). Given we're now running 1000MB/s em cards, it might be safe to say you can increase the defaults by 10. You have to edit the source to change some of the defaults: /usr/src/sys/kern/kern_poll.c #define MIN_POLL_BURST_MAX 100 #define MAX_POLL_BURST_MAX 10000 I tried doing this, but encountered the problems with the throughput somehow related to the em cards and gave up. Maybe you're results will be better. Regards, Dave Seddon Ferdinand Goldmann writes: > Kevin Day wrote: > >> In one case, we had a system acting as a router. It was a Dell PowerEdge >> 2650, with two dual "server" adapters. each were on separate PCI busses. >> 3 were "lan" links, and one was a "wan" link. The lan links were >> receiving about 300mbps each, all going out the "wan" link at near >> 900mbps at peak. We were never able to get above 944mbps, but I never >> cared enough to figure out where the bottleneck was there. > > 944mbps is a very good value, anyway. What we see in our setup are > throuput rates around 300mbps or below. When testing with tcpspray, > throughput hardly exceeded 13MB/s. > > Are you running vlans on your interface? Our em0-card connects several > sites together, which are all sitting on separate vlan interfaces for > which the em0 acts as parent interface. > >> This was with PCI-X, and a pretty stripped config on the server side. > > Maybe this makes a difference, too. We only have a quite old xSeries 330 > with PCI and a 1.2GHz CPU. > >> >> Nothing fancy on polling, i think we set HZ to 10000 > > Ten-thousand? Or is this a typo, and did you mean thousand? > > This is weird. :-( Please, is there any good documentation on tuning > device polling? The man page does not give any useful pointers about > values to use for Gbit cards. I have already read things about people > using 2000, 4000HZ ... Gaaah! > > I tried with 1000 and 2000 so far, without good results. It seems like > everybody makes wild assumptions on what values to use for polling. > >> , turned on idle_poll, and set user_frac to 10 because we had some cpu >> hungry tasks that were not a high priority. > > I think I red somewhere about problems with idle_poll. How high is your > burst_max value? Are you seeing a lot of ierrs? > > *sigh* :-( confusing. > > -- > >> Ferdinand Goldmann //// | | > >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at |--00 | UNIX | > >> Tel. : +43/732/2468/9398 Fax. : +43/732/2468/9397 C ^ | | > >> EMail: Ferdinand.Goldmann@zid.uni-linz.ac.at \ ~/ ~~~|~~~~~~~~ > >> PGP D4CF 8AA4 4B2A 7B88 65CA 5EDC 0A9B FA9A 13EA B993| |-----3 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Oct 6 07:13:31 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1294716A420; Thu, 6 Oct 2005 07:13:31 +0000 (GMT) (envelope-from jura@networks.ru) Received: from networks.ru (orange.networks.ru [80.249.138.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3648843D48; Thu, 6 Oct 2005 07:13:29 +0000 (GMT) (envelope-from jura@networks.ru) Received: from [81.195.67.217] (HELO Jura) by networks.ru (CommuniGate Pro SMTP 4.3.8) with ESMTPS id 1984457; Thu, 06 Oct 2005 11:13:28 +0400 Message-ID: <069d01c5ca45$30825850$6504010a@Jura> From: "Yuriy N. Shkandybin" To: Date: Thu, 6 Oct 2005 11:11:32 +0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Cc: freebsd-net@freebsd.org Subject: pf synproxy broken X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 07:13:31 -0000 Hello. Please look at PR 86072. I've confirm that this issue exist in latest STABLE and HEAD. How it looks: 1) without synproxy telnet localhost 22 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-2.0-OpenSSH_4.2p1 FreeBSD-20050903 2) with synproxy pass in log on lo0 proto tcp from any to any port 22 flags S/SA synproxy state telnet localhost 22 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. That's all no actual connection. netstat: tcp4 0 0 127.0.0.1.45427 127.0.0.1.22 ESTABLISHED pfÓtl -s state self tcp 127.0.0.1:22 <- 127.0.0.1:45427 PROXY:DST Jura From owner-freebsd-net@FreeBSD.ORG Thu Oct 6 08:18:39 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D9BC16A41F; Thu, 6 Oct 2005 08:18:39 +0000 (GMT) (envelope-from bsd@roamingsolutions.net) Received: from basillia.speedxs.net (basillia.speedxs.net [83.98.255.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDC6843D6B; Thu, 6 Oct 2005 08:18:27 +0000 (GMT) (envelope-from bsd@roamingsolutions.net) Received: from ongers.net (ongers.speedxs.nl [83.98.237.210]) by basillia.speedxs.net (Postfix) with ESMTP id 5C4D17034; Thu, 6 Oct 2005 10:06:36 +0200 (CEST) Received: from (66.110.35.16 [66.110.35.16]) by MailEnable Inbound Mail Agent with ESMTP; Thu, 06 Oct 2005 10:23:48 +0200 Received: from 127.0.0.1 (AVG SMTP 7.0.344 [267.11.10]); Thu, 06 Oct 2005 10:18:47 +0200 Message-ID: <4344DDE5.1070301@roamingsolutions.net> Date: Thu, 06 Oct 2005 10:18:45 +0200 From: G Bryant User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD , FreeBSD Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 2 uplinks with bandwidth management, load splitting and fail-over. Working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 08:18:39 -0000 Greetings, 2 uplinks with bandwidth management, load splitting and fail-over. Working For those interested in an alternate method of doing the same thing - here are some basics. You could probably modify the script rules and sets to do crude load balancing between the lines too - but more of that later. The Setup: FreeBSD 5.4 - Stable ipfw, natd, natd2, ng_one2many, squid, jftpgw. 2 dsl links to the internet. 3 network cards ( 1 per dsl modem, 1 for lan) Learning curve: After much reading and testing, I found that the way to use both dsl lines was to use ipfw prob, ipfw fwd, and divert to seperate natd 's. Basically: a natd with alias_address associated with each of the boxes external ip's. ipfw rules as follows: #------------------------ route add default $ext_gw1 <--snip--> ipfw add allow ip from any to any via $int_if ipfw add divert natd1 ip from any to $ext_ip1 in ipfw add divert natd2 ip from any to $ext_ip2 in # Simple version ipfw add skipto 8000 ip from $lan to any out ipfw add allow ip from any to $lan in ipfw add 8000 prob 0.5 skipto 8500 ip from any to any out ipfw add 8100 divert natd1 ip from any to any out ipfw add 8200 allow ip from $ext_ip1 to any out ipfw add 8500 divert natd2 ip from any to any out ipfw add 8600 fwd $ext_gw2 ip from $ext_ip2 to any out ipfw add deny ip from any to any out #------------------------ This didn't work for 2 reasons. Packets exiting with a fwd command to ext_gw2 didn't get to exit the correct interface as routed had already set them up to exit via the default route. Second reason was that tcp sessions really like all sequenced packets, and ack replies to come from the same source it started talking with initially. The keep-state unfortunately only creates a dynamic rule using ip and port for source and destination, and the interface. This does not help as I would like the rule to remember which packets to skipto 8500 (same as before) - but the keep-state (dynamic rule for that session) seems to think it's a free-for-all and only sees it as an allow rule, to send the packets directly out. This doesn't help as the packets have not yet been natted, and so exit with a private source ip (up, up and away - never to be seen again). Current (dirty) working Solution: rc.conf: (relevant entries) hostname="fw.xx.yy.zz" # Configure the internal network ifconfig_vr0="inet 192.168.1.1 netmask 255.255.255.0" # Configure the external networks (connected to the internet) ifconfig_rl0="inet 192.168.8.70 netmask 255.255.255.0" ifconfig_rl0_alias0="inet 192.168.0.99 netmask 255.255.255.0" defaultrouter="192.168.8.1" # - Enabling the FreeBSD Firewall gateway_enable="YES" firewall_enable="YES" firewall_script="/etc/ipfw.rules" firewall_logging="YES" # Enabling natd for the 2 external interfaces natd_enable="YES" natd_flags="-f /etc/natd1.conf" # Remember to specify the natd2 port in /etc/services # To start this, the easiest way is to cp /etc/rc.d/natd /usr/local/etc/rc.d/natd2.sh and then edit it. natd2_enable="YES" natd2_flags="-f /etc/natd2.conf" #Enable the proxy server squid_enable="YES" # Sync server time from internet ntpd_enable="YES" ntpd_flags="-c /etc/ntp.conf" # Bandwidth monitoring with html graphs bandwidthd_enable="YES" # jftpgw ftp proxy for anonymous ftp proxy-cache jftpgw_enable="YES" # Load the script to hook the two external nic's together # Add the actual script file to /usr/local/etc/rc.d/netmon1.sh netmon1_enable="YES" I found the fwd command in the above ipfw rules wasn't working for me - even tried different network cards, but the packets still didn't exit the correct interface correctly. So I decided to try force them out whether they liked it or not. (Hence the dirty part - as you will see) Used ng_one2many to hookboth external nic's onto the first one, and configured it for "transmit all." i.e. all packets leaving interface0 get forced out of interface1 as well. Just ran a script at startup to get this setup: (Yes I know it can be done a lot better - for now it works!!!) #---------------------------- #!/bin/sh # Load the kernel modules kldload ng_ether kldload ng_one2many ifconfig rl0 down ifconfig rl1 down # Plumb nodes together ngctl mkpeer rl0: one2many upper one ngctl connect rl0: rl0:upper lower many0 ngctl connect rl1: rl0:upper lower many1 # Allow rl1 to xmit / recv rl0 frames ifconfig rl1 promisc ngctl msg rl1: setautosrc 0 # Configure to transmit to all interfaces ngctl msg rl0:upper setconfig "{xmitAlg=2 failAlg=1 enabledLinks =[ 1 1 ] }" echo "Now up the interfaces again" ifconfig rl0 up ifconfig rl1 up ifconfig rl0 inet 192.168.8.70 netmask 255.255.255.0 ifconfig rl0 inet 192.168.0.99 netmask 255.255.255.0 alias Make sure the default route is correct. route delete default route add default 192.168.0.1 echo "Done" #---------------------------- Weird thing was that using default route 192.168.8.1 (via the interface directly linked to $ext_if1) didn't work. It was only when I tried with the default route set to $ext_gw2 that everything started working. Still figuring that one, but reckon it was prayers that give God the honours here. ipfw rules: #!/bin/sh ################ Start of IPFW rules file ############################### # Flush out the list before we begin. ipfw -q -f flush # Set rules command prefix cmd="ipfw -q add" bwm="ipfw -q pipe" skip="skipto 8000" ext_if1="rl0" # public interface name of NIC ext_if2="rl0" lan="192.168.1.0/24" int_if="vr0" # private interface name of NIC ext_ip1="192.168.8.70" ext_ip2="192.168.0.99" ext_gw1="192.168.8.1" ext_gw2="192.168.0.1" # Setup the different Sets to be used for different connection options ipfw -q set disable 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 # Initially enable set 1 and 2 and 12 assuming we have 2 WAN links up and working ipfw -q set enable 1 2 12 # Specify which ip addresses get what bandwidth # Can also tell this dhcp server to give certain addresses to selected mac # addresses in file /usr/local/etc/dhcpd.conf u512k="" # Users given 512kb/s link u256k="192.168.1.0/24{2-254}" # Users given 256kb/s link u128k="" # Users given 128kb/s link u64k="" # Users given 64kb/s link # squid and jftpgw have to be configured seperately to provide the same # bandwidth management as what is configured here. See their config/man pages. # Check and drop packets that are appearing to come from # the destination LAN i.e. a spoofed source ip address $cmd deny ip from any to any not antispoof in # No restrictions on Loopback Interface # Protect spoofing to localhost $cmd allow ip from any to any via lo0 $cmd deny ip from any to 127.0.0.0/8 $cmd deny ip from 127.0.0.0/8 to any # check if packet is inbound and nat address if it is $cmd 1000 divert natd1 ip from any to $ext_ip1 in $cmd 1000 divert natd2 ip from any to $ext_ip2 in # Divert incoming http and ftp traffic to the proxy (squid and jftpgw) $cmd fwd 192.168.1.1,3128 tcp from $lan to any 80 in via $int_if $cmd fwd 192.168.1.1,2370 tcp from $lan to any 21 via $int_if # Allow the rest of the LAN traffic in and out $cmd allow ip from any to any via $int_if ################ Bandwidth Management ############################ # Setup up pipes for each of the user groups # Users with 512Kb / 256Kb access (in / out) $cmd pipe 10 ip from any to $u512k in via $ext_if1 $cmd pipe 11 ip from $u512k to any out via $ext_if1 $bwm 10 config mask dst-ip 0x000000ff bw 512Kbit/s queue 4KBytes $bwm 11 config mask src-ip 0x000000ff bw 256Kbit/s queue 3KBytes # Users with 256Kb / 128Kb access $cmd pipe 20 ip from any to $u256k in via $ext_if1 $cmd pipe 21 ip from $u256k to any out via $ext_if1 $bwm 20 config mask dst-ip 0x000000ff bw 256Kbit/s queue 4KBytes $bwm 21 config mask src-ip 0x000000ff bw 128Kbit/s queue 3KBytes # Users with 128Kb / 64Kb access $cmd pipe 30 ip from any to $u128k in via $ext_if1 $cmd pipe 31 ip from $u128k to any out via $ext_if1 $bwm 30 config mask dst-ip 0x000000ff bw 128Kbit/s queue 4KBytes $bwm 31 config mask src-ip 0x000000ff bw 64Kbit/s queue 3KBytes # Users with 64Kb / 56Kb access $cmd pipe 40 ip from any to $u64k in via $ext_if1 $cmd pipe 41 ip from $u64k to any out via $ext_if1 $bwm 40 config mask dst-ip 0x000000ff bw 64Kbit/s queue 3KBytes $bwm 41 config mask src-ip 0x000000ff bw 56Kbit/s queue 2KBytes ################################################################# # Interface facing Public Internet (Outbound Section) # Allow out access to my ISP's Domain name server. # Get the IP addresses from /etc/resolv.conf file #$cmd $skip UDP from any to { 196.7.0.138 or 196.28.86.2 or 196.28.86.3 or 196.25.1.1 } 53 out $cmd $skip UDP from any to any 53 out # Allow this box out access to my ISP's DHCP server (or adsl router) $cmd $skip udp from me to any 67 out # Allow skype connections out # Allow ntp time server out $cmd $skip UDP from any to any 80,443,123,1024-65535 out $cmd $skip UDP from any 80,443,1024-65535 to any out $cmd $skip tcp from any 1024-65535 to any 1024-65535 out # Allow out non-secure standard www function - via proxy $cmd $skip tcp from me to any 80 # Allow out secure www function https over TLS SSL # Allow out send & get email function (GMail uses ports 587, 995) # Allow out MSN messenger # Allow out Time, nntp news (i.e. news groups), # SSH (secure FTP, Telnet, and SCP), whois $cmd $skip tcp from any to any 443,25,110,587,995,1863,37,119,22,43 out # Allow out regular http and ftp access (for if proxy and fwd cmd's above are off) $cmd $skip tcp from $lan 1024-65535 to any 20,21,80 out # Allow out ping $cmd $skip icmp from $lan to any out icmptypes 8 $cmd allow icmp from me to 192.168.0.0/16 out icmptypes 8 $cmd allow icmp from $ext_ip1,$ext_ip2 to any out icmptypes 8 # Allow www and ftp proxy out $cmd $skip tcp from me to any 20,21,80 out uid squid # Allow out FreeBSD (make install & CVSUP) functions # Give user root "GOD" privileges. $cmd allow ip from me to any out uid root # Deny the rest out $cmd deny log ip from any to any out ################################################################# # Interface facing Public Internet (Inbound Section) # Interrogate packets originating from the public Internet # destine for this gateway server or the private network. # Deny all inbound traffic from non-routable reserved address spaces #$cmd 300 deny all from 192.168.0.0/16 to any in via $ext_if1 #RFC 1918 private IP $cmd deny all from 172.16.0.0/12,10.0.0.0/8,0.0.0.0/8,169.254.0.0/16,192.0.2.0/24,204.152.64.0/23,224.0.0.0/3 to any in #RFC 1918 private IP #DHCP auto-config #reserved for docs #Sun cluster #Class D & E multicast # Deny ident # Deny all Netbios service. 137=name, 138=datagram, 139=session # Netbios is MS/Windows sharing services. # Block MS/Windows hosts2 name server requests 81 $cmd deny all from any to any 113,137,138,139,81 in # Allow traffic in from ISP's DHCP server. This rule must contain # the IP address of your ISP's DHCP server as it's the only # authorized source to send this packet type. $cmd allow udp from 192.168.8.1,192.168.0.1 to any 68,5678 in # Allow dns lookups back in $cmd allow udp from any 53,67 to $lan in $cmd allow udp from any 53,67 to me in # Allow skype connections in $cmd allow udp from any 80,123,443,1024-655353 to $lan in $cmd allow udp from any to $lan 80,443,1024-655353 in $cmd deny log udp from any to any in # Deny the rest $cmd allow tcp from any 1024-65535 to $lan 1024-65535 in # Allow in SecureFTP and SSH from public Internet $cmd allow tcp from { 192.168.0.0/24 or $lan or 192.168.8.0/24 } to me 22 in #setup limit src-addr 3 $cmd allow tcp from any to me 22 in setup limit src-addr 1 # Allow in standard www function because I have Apache server - or is there an internal webserver? # Allow Webmin connections from close-by $cmd allow tcp from { 192.168.8.0/24 or 192.168.0.0/24 } to me 80,10000 in $cmd allow tcp from any to $lan 80,10000 in # Allow outgoing web traffic (via proxy) back in $cmd allow tcp from any 20,21,80 to me 1024-65535 in # Deny the rest to me $cmd deny log tcp from any to me in # Allow out regular ftp, http access if proxy is off $cmd allow tcp from any 20,21,80 to $lan 1024-65535 in # Allow in secure www function https over TLS SSL # Allow in send & get email function (GMail uses ports 587, 995) # Allow in MSN messenger # Allow in Time, nntp news (i.e. news groups), # SSH (secure FTP, Telnet, and SCP), whois $cmd allow tcp from any 443,25,110,587,995,1863,37,119,22,43 to any in #Allow in ICMP (ping) from public networks close by only. $cmd allow icmp from 192.168.0.0/16 to me in icmptypes 0,3,11 $cmd allow icmp from any to $lan in icmptypes 0,3,11 # Used for testing network connections $cmd allow icmp from 196.7.0.138,196.25.1.1,196.4.160.7 to me in icmptypes 0,3,11 #Deny the rest $cmd deny icmp from any to any in # Reject & Log all unauthorized incoming connections from the public Internet (/var/log/security) $cmd deny log all from any to any in # This is skipto location for outbound stateful rules $cmd 8000 skipto 9000 tcp from any to any out setup $cmd 8010 skipto 9000 udp from any to any out $cmd 8020 skipto 9000 icmp from any to any out $cmd 8100 tee natd1 ip from any to any out $cmd 8150 check-state $cmd 8200 divert natd2 ip from any to any out $cmd 8250 check-state $cmd 8400 deny ip from any to any out $cmd 9000 set 12 prob 0.5 skipto 9500 ip from any to any out $cmd 9100 set 1 divert natd1 ip from any to any out $cmd 9200 set 1 allow ip from any to any out keep-state $cmd 9500 set 2 divert natd2 ip from any to any out $cmd 9600 set 2 allow ip from any to any out keep-state # deny and log all packets that fell through to see what they are $cmd 9999 deny log all from any to any ################ End of IPFW rules file ############################### What this effectively does is send packets destined for either of the $ext_gw's out over both the external lines. This is a terrible way of spamming these external lines with traffic that doesn't belong there, but then again it's only a single link between your ext_if and the ext_gw with nothing else on that link. It's also not holding much traffic as it's the limited internet link which (here in .za) is only 512k per line. (although they have just recently brought out a 1M link, available in certain areas) Anyway, the 100M link should handle the extra noise on the line. If someone has a nicer solution for me - I'm all ears. Last thing to do was to setup fail-over of some sort. Again, I thought myself some sh scripting in a day, so this isn't the prettiest, but it works. I added an entry to crontab to have this script run every 2 minutes. Basically it adds a specific (pingable) host to the route, and then pings it via the defined path (1st dsl line). Then changes the route and pings it via the 2nd path (2nd dsl line). #----------------------------------------- #!/bin/sh target="196.7.0.138" ext_gw1="192.168.8.1" ext_gw2="192.168.0.1" # Setup route to ping through route -q add -host $target $ext_gw1 # Test link one through ext_gw1 to see if any packets get returned ping1=$( ping -q -c 3 -f -s 8 -o -t 2 196.7.0.138 | grep "packet loss" | cut -c24-24 ) # Test link two through ext_gw2 to see if any packets get returned route -q delete $target route -q add -host $target $ext_gw2 ping2=$( ping -q -c 3 -f -s 8 -o -t 2 196.7.0.138 | grep "packet loss" | cut -c24-24 ) # Remove route route -q delete $target # Configure the ipfw sets as per network route availability if [ "$ping1" != "0" ]; then if [ "$ping2" = "1" ]; then ipfw set enable 1 2 12 else ipfw set enable 1 ipfw set disable 2 12 fi else if [ "$ping2" != "0" ]; then ipfw set disable 1 12 ipfw set enable 2 else # echo "enabling everything to wait for network recovery" ipfw set enable 1 2 12 fi fi #-------------------------------------- This could be expanded to some sort of crude bandwidth management system if you add some rules to the ipfw that specify probability of 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8 with each rule associated with a different ipfw set. Then you parse the ping replies (you would now need an average for the pings, not just a single ping) for the average time on each route and do some math to enable the correct ipfw set with the correct ipfw prob ratio. It's dirty, but it should (in theory) work. I haven't gotten this far - currently happy with what I have so far and time to earn some money again. Maybe later. Feel free to post any comments / queries. Feedback welcome. I hope this helps some people save some of the hours and hours I spent on trial and error. Regards Graham From owner-freebsd-net@FreeBSD.ORG Thu Oct 6 12:46:32 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4B0216A420; Thu, 6 Oct 2005 12:46:32 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27A6F43D46; Thu, 6 Oct 2005 12:46:31 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by smtp4-g19.free.fr (Postfix) with ESMTP id A40432CC59; Thu, 6 Oct 2005 14:46:30 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 6A8014083; Thu, 6 Oct 2005 14:46:25 +0200 (CEST) Date: Thu, 6 Oct 2005 14:46:25 +0200 From: Jeremie Le Hen To: Daniel Dias =?iso-8859-1?Q?Gon=E7alves?= Message-ID: <20051006124625.GZ43195@obiwan.tataz.chchile.org> References: <4344383B.4000405@dgnetwork.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4344383B.4000405@dgnetwork.com.br> User-Agent: Mutt/1.5.10i Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: IPFW+DUMMYNET UPLOAD PROBLEM X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 12:46:32 -0000 Hi Daniel, > I have the following rules: > > $fwcmd add 600 pipe 602 src-ip 192.168.0.0/24 out > $fwcmd add 601 pipe 603 dst-ip 192.168.0.0/24 in > $fwcmd pipe 602 config mask src-ip 0x000000ff bw 128Kbit/s queue 10KBytes > $fwcmd pipe 603 config mask dst-ip 0x000000ff bw 128Kbit/s queue 10KBytes > > And my test speed from ip 192.168.0.5 is: > Down 123.66kbps > Up 766.24kbps What's the output of % ipfw show 600 601 Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-net@FreeBSD.ORG Thu Oct 6 12:58:53 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6D6B16A41F for ; Thu, 6 Oct 2005 12:58:53 +0000 (GMT) (envelope-from daniel@dgnetwork.com.br) Received: from zeus.yan.com.br (zeus.yan.com.br [200.202.253.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 37E5C43D5D for ; Thu, 6 Oct 2005 12:58:50 +0000 (GMT) (envelope-from daniel@dgnetwork.com.br) Received: (qmail 4822 invoked by uid 1023); 6 Oct 2005 12:58:30 -0000 Received: from daniel@dgnetwork.com.br by zeus by uid 1023 with qmail-scanner-1.22 (uvscan: v4.1.60/v4366. fsecure: 4.11/3190/2003-09-23/2002-12-17. 2003-09-22/. Clear:RC:1(200.202.253.197):. Processed in 0.694949 secs); 06 Oct 2005 12:58:30 -0000 Received: from unknown (HELO ?192.168.1.1?) (daniel@dgnetwork.com.br@200.202.253.197) by zeus.yan.com.br with SMTP; 6 Oct 2005 12:58:30 -0000 Message-ID: <43451F84.5070406@dgnetwork.com.br> Date: Thu, 06 Oct 2005 09:58:44 -0300 From: =?ISO-8859-1?Q?Daniel_Dias_Gon=E7alves?= Organization: DGNET Network Solutions User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: pt-br, pt MIME-Version: 1.0 To: Jeremie Le Hen References: <4344383B.4000405@dgnetwork.com.br> <20051006124625.GZ43195@obiwan.tataz.chchile.org> In-Reply-To: <20051006124625.GZ43195@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: IPFW+DUMMYNET UPLOAD PROBLEM X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: daniel@dgnetwork.com.br List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 12:58:54 -0000 Jeremie Le Hen escreveu: >Hi Daniel, > > > >>I have the following rules: >> >>$fwcmd add 600 pipe 602 src-ip 192.168.0.0/24 out >>$fwcmd add 601 pipe 603 dst-ip 192.168.0.0/24 in >>$fwcmd pipe 602 config mask src-ip 0x000000ff bw 128Kbit/s queue 10KBytes >>$fwcmd pipe 603 config mask dst-ip 0x000000ff bw 128Kbit/s queue 10KBytes >> >>And my test speed from ip 192.168.0.5 is: >>Down 123.66kbps >>Up 766.24kbps >> >> > >What's the output of >% ipfw show 600 601 > >Regards, > > # ipfw show 600 601 00600 2 210 pipe 602 ip from any to any src-ip 192.168.0.0/24 out 00601 26 9301 pipe 603 ip from any to any dst-ip 192.168.0.0/24 in # -- Daniel Dias Gonçalves DGNET Network Solutions daniel@dgnetwork.com.br (37) 99824809 From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 00:53:56 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2305F16A41F for ; Fri, 7 Oct 2005 00:53:55 +0000 (GMT) (envelope-from kapiltj@yahoo.com) Received: from web81102.mail.yahoo.com (web81102.mail.yahoo.com [206.190.37.161]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E73C43D46 for ; Fri, 7 Oct 2005 00:53:55 +0000 (GMT) (envelope-from kapiltj@yahoo.com) Received: (qmail 92131 invoked by uid 60001); 7 Oct 2005 00:53:54 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=WEcrmcm7uEhWUq2s5STFm9giUW345aJR7O3wDzzysGvk9CPooKM9TjfQFTwJ6FWunKoyXwhD3d3IPR3mPRqFHyQyWF9lw87ltRbwdCtSwJranfPxUZzSRGpabhcAZpx9QrZki6cndcPSxe1m9VHwvcTrL9emFydRuewbv92pPa0= ; Message-ID: <20051007005354.92129.qmail@web81102.mail.yahoo.com> Received: from [66.129.224.36] by web81102.mail.yahoo.com via HTTP; Thu, 06 Oct 2005 17:53:54 PDT Date: Thu, 6 Oct 2005 17:53:54 -0700 (PDT) From: kapil jain To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: telnetd hang X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 00:53:56 -0000 Hello, I am seeing this problem in all versions of telnet: If some characters and a cntrl C is entered on a telnet session before the child for slave tty is forked, the ptyflush will hang on write call, since slave tty is not open and will just wait there. An easy way to reproduce this problem is: set connection limit on telnet to 1 (using inetd.conf). Connect the 1st and 2nd session. 2nd session will not show the login prompt. Here enter one or more characters and then ctrl C. Now exit the 1st session. The second sessions telentd is spawned but hangs on ptcout. Even if you exit the session, no more telnet sessions are allowed (unless connection limit is increased or telentd is killed) - My question is: does a change need to be made in telnetd to handle this case or should this have already been done in the kernel to wake up the process when the connection on the remote end closes. thanks kapil From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 01:59:42 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FDA516A41F; Fri, 7 Oct 2005 01:59:42 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE70143D48; Fri, 7 Oct 2005 01:59:41 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id 9DC251CCD4; Fri, 7 Oct 2005 14:59:40 +1300 (NZDT) Date: Fri, 7 Oct 2005 14:59:40 +1300 From: Andrew Thompson To: freebsd-net@freebsd.org Message-ID: <20051007015940.GA82509@heff.fud.org.nz> References: <200510070032.j970WGtd001243@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510070032.j970WGtd001243@repoman.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: brooks@freebsd.org Subject: Re: cvs commit: src/sbin/ifconfig ifbridge.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 01:59:42 -0000 Hi, I'd really like to get this into 6.0. When setting up a bridge with spanning tree its essential to know what state each port is in (forwarding, blocked, ...) I cant think of any bad things this will do (to scripts and such) but its getting so close to the release... Does anyone object to this change? > thompsa 2005-10-07 00:32:16 UTC > > FreeBSD src repository > > Modified files: > sbin/ifconfig ifbridge.c > Log: > Display the status of the spanning tree for each port. > > member: xl0 flags=7 > member: gem0 flags=7 > to: > member: xl0 flags=7 > port 3 priority 128 path cost 55 forwarding > member: gem0 flags=7 > port 1 priority 128 path cost 55 learning > > Revision Changes Path > 1.2 +16 -8 src/sbin/ifconfig/ifbridge.c From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 05:01:51 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1503316A41F for ; Fri, 7 Oct 2005 05:01:51 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: from mail.lrtc.lt (pegasus.lrtc.lt [217.9.240.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3569743D45 for ; Fri, 7 Oct 2005 05:01:49 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: (qmail 2526 invoked from network); 7 Oct 2005 04:54:58 -0000 Received: from p2p-241-242-ird.vln0.lrtc.net (HELO donatas) (d.gendvilas@[217.9.241.242]) (envelope-sender ) by mail.lrtc.lt (qmail-ldap-1.03) with SMTP for ; 7 Oct 2005 04:54:58 -0000 Message-ID: <020201c5cafc$3806b460$9f90a8c0@donatas> From: "Donatas" To: Date: Fri, 7 Oct 2005 08:01:46 +0300 Organization: AB Lietuvos Radijo ir Televizijos Centras MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: double tagged vlans on 6.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Donatas List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 05:01:51 -0000 Just wonder - what is the major reason double vlan support (also known = as q-in-q or nested vlan) is still not included in freebsd. The need = for this feature is growing parallely with new L3 switches being = available (cisco, allied telesyn, foundry networks etc...). Enabling = this in some cases could make freebsd the only solution for backbone = operators.=20 Brook Davis mentioned q-in-q would make inefficient vlan code even = worse...but that was some time ago...hope the situation changed nowdays From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 07:42:17 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBAAC16A41F for ; Fri, 7 Oct 2005 07:42:17 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45F0543D46 for ; Fri, 7 Oct 2005 07:42:17 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (qxabuf@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j977gEgg099724; Fri, 7 Oct 2005 09:42:15 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j977gEqi099723; Fri, 7 Oct 2005 09:42:14 +0200 (CEST) (envelope-from olli) Date: Fri, 7 Oct 2005 09:42:14 +0200 (CEST) Message-Id: <200510070742.j977gEqi099723@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG, Donatas In-Reply-To: <020201c5cafc$3806b460$9f90a8c0@donatas> X-Newsgroups: list.freebsd-net User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: Re: double tagged vlans on 6.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG, Donatas List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 07:42:18 -0000 Donatas wrote: > Just wonder - what is the major reason double vlan support (also known as q-in-q > or nested vlan) is still not included in freebsd. It is supported, for years already (even in FreeBSD 4.x). See ng_vlan(4). You can even do q-in-q-in-q if you want (do Cisco etc. support that?). ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "What is this talk of 'release'? We do not make software 'releases'. Our software 'escapes', leaving a bloody trail of designers and quality assurance people in its wake." From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 08:07:54 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9801C16A41F; Fri, 7 Oct 2005 08:07:54 +0000 (GMT) (envelope-from jura@networks.ru) Received: from networks.ru (orange.networks.ru [80.249.138.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C7CC43D48; Fri, 7 Oct 2005 08:07:53 +0000 (GMT) (envelope-from jura@networks.ru) Received: from [81.195.67.217] (HELO Jura) by networks.ru (CommuniGate Pro SMTP 4.3.8) with ESMTPS id 1987193; Fri, 07 Oct 2005 12:07:51 +0400 Message-ID: <092e01c5cb15$f7fe5840$6504010a@Jura> From: "Yuriy N. Shkandybin" To: Date: Fri, 7 Oct 2005 12:06:05 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_092B_01C5CB37.7E6C8C50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Cc: jhb@freebsd.org Subject: if_nge & if_lge drivers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 08:07:54 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_092B_01C5CB37.7E6C8C50 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit Hello. I saw John Baldwin commit to if_lge.c rev 1.43 and perform same changes for if_nge.c I've tested it and it works. Patch in attachment or available from http://www.netams.com/if_nge.c.patch Also i've noticed if_lge affected same problem i've met nge. In if_lgereg.h we have struct lge_list_data { struct lge_rx_desc lge_rx_list[LGE_RX_LIST_CNT]; struct lge_tx_desc lge_tx_list[LGE_TX_LIST_CNT]; }; In if_lge.c 524: sc->lge_ldata = contigmalloc(sizeof(struct lge_list_data), M_DEVBUF, M_NOWAIT, 0, 0xffffffff, PAGE_SIZE, 0); So lge_rx_list and lge_tx_list might be initialized with garbage in it. But in lge_stop() there is: /* * Free data in the RX lists. */ for (i = 0; i < LGE_RX_LIST_CNT; i++) { if (sc->lge_ldata->lge_rx_list[i].lge_mbuf != NULL) { m_freem(sc->lge_ldata->lge_rx_list[i].lge_mbuf); sc->lge_ldata->lge_rx_list[i].lge_mbuf = NULL; } } And lge_stop() called from lge_init() (if_lge.c line 1242) So m_freem() called on garbage from lge_rx_list! I suggest to add M_ZERO to contigmalloc() flags for both if_nge.c and if_lge.c Jura ------=_NextPart_000_092B_01C5CB37.7E6C8C50 Content-Type: application/octet-stream; name="if_nge.c.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="if_nge.c.patch" --- if_nge.c.orig Fri Oct 7 10:51:29 2005=0A= +++ if_nge.c Fri Oct 7 11:49:09 2005=0A= @@ -742,7 +742,7 @@=0A= }=0A= =0A= if (i =3D=3D NGE_TIMEOUT)=0A= - printf("nge%d: reset never completed\n", sc->nge_unit);=0A= + if_printf(sc->nge_ifp, "reset never completed\n");=0A= =0A= /* Wait a little while for the chip to get its brains in order. */=0A= DELAY(1000);=0A= @@ -791,13 +791,10 @@=0A= {=0A= u_char eaddr[ETHER_ADDR_LEN];=0A= struct nge_softc *sc;=0A= - struct ifnet *ifp;=0A= - int unit, error =3D 0, rid;=0A= - const char *sep =3D "";=0A= + struct ifnet *ifp=3DNULL;=0A= + int error =3D 0, rid;=0A= =0A= sc =3D device_get_softc(dev);=0A= - unit =3D device_get_unit(dev);=0A= - bzero(sc, sizeof(struct nge_softc));=0A= =0A= NGE_LOCK_INIT(sc, device_get_nameunit(dev));=0A= /*=0A= @@ -809,7 +806,7 @@=0A= sc->nge_res =3D bus_alloc_resource_any(dev, NGE_RES, &rid, RF_ACTIVE);=0A= =0A= if (sc->nge_res =3D=3D NULL) {=0A= - printf("nge%d: couldn't map ports/memory\n", unit);=0A= + device_printf(dev, "couldn't map ports/memory\n");=0A= error =3D ENXIO;=0A= goto fail;=0A= }=0A= @@ -823,11 +820,20 @@=0A= RF_SHAREABLE | RF_ACTIVE);=0A= =0A= if (sc->nge_irq =3D=3D NULL) {=0A= - printf("nge%d: couldn't map interrupt\n", unit);=0A= - bus_release_resource(dev, NGE_RES, NGE_RID, sc->nge_res);=0A= + device_printf(dev, "couldn't map interrupt\n");=0A= error =3D ENXIO;=0A= goto fail;=0A= }=0A= + =0A= + /*=0A= + * Hookup IRQ last.=0A= + */=0A= + error =3D bus_setup_intr(dev, sc->nge_irq, INTR_TYPE_NET | INTR_MPSAFE,=0A= + nge_intr, sc, &sc->nge_intrhand);=0A= + if (error) {=0A= + device_printf(dev, "couldn't set up irq\n");=0A= + goto fail;=0A= + }=0A= =0A= /* Reset the adapter. */=0A= nge_reset(sc);=0A= @@ -839,25 +845,19 @@=0A= nge_read_eeprom(sc, (caddr_t)&eaddr[2], NGE_EE_NODEADDR + 1, 1, 0);=0A= nge_read_eeprom(sc, (caddr_t)&eaddr[0], NGE_EE_NODEADDR + 2, 1, 0);=0A= =0A= - sc->nge_unit =3D unit;=0A= -=0A= /* XXX: leaked on error */=0A= sc->nge_ldata =3D contigmalloc(sizeof(struct nge_list_data), M_DEVBUF,=0A= - M_NOWAIT, 0, 0xffffffff, PAGE_SIZE, 0);=0A= + M_NOWAIT|M_ZERO, 0, 0xffffffff, PAGE_SIZE, 0);=0A= =0A= if (sc->nge_ldata =3D=3D NULL) {=0A= - printf("nge%d: no memory for list buffers!\n", unit);=0A= - bus_release_resource(dev, SYS_RES_IRQ, 0, sc->nge_irq);=0A= - bus_release_resource(dev, NGE_RES, NGE_RID, sc->nge_res);=0A= + device_printf(dev, "no memory for list buffers!\n");=0A= error =3D ENXIO;=0A= goto fail;=0A= }=0A= =0A= ifp =3D sc->nge_ifp =3D if_alloc(IFT_ETHER);=0A= if (ifp =3D=3D NULL) {=0A= - printf("nge%d: can not if_alloc()\n", unit);=0A= - bus_release_resource(dev, SYS_RES_IRQ, 0, sc->nge_irq);=0A= - bus_release_resource(dev, NGE_RES, NGE_RID, sc->nge_res);=0A= + device_printf(dev, "can not if_alloc()\n");=0A= error =3D ENOSPC;=0A= goto fail;=0A= }=0A= @@ -893,19 +893,13 @@=0A= ifmedia_init(&sc->nge_ifmedia, 0, nge_ifmedia_upd, =0A= nge_ifmedia_sts);=0A= #define ADD(m, c) ifmedia_add(&sc->nge_ifmedia, (m), (c), NULL)=0A= -#define PRINT(s) printf("%s%s", sep, s); sep =3D ", "=0A= ADD(IFM_MAKEWORD(IFM_ETHER, IFM_NONE, 0, 0), 0);=0A= - device_printf(dev, " ");=0A= ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_SX, 0, 0), 0);=0A= - PRINT("1000baseSX");=0A= ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_SX, IFM_FDX, 0),0);=0A= - PRINT("1000baseSX-FDX");=0A= ADD(IFM_MAKEWORD(IFM_ETHER, IFM_AUTO, 0, 0), 0);=0A= - PRINT("auto");=0A= - =0A= - printf("\n");=0A= #undef ADD=0A= -#undef PRINT=0A= + device_printf(dev, " 1000baseSX, 1000baseSX-FDX, auto\n");=0A= + =0A= ifmedia_set(&sc->nge_ifmedia, =0A= IFM_MAKEWORD(IFM_ETHER, IFM_AUTO, 0, 0));=0A= =0A= @@ -916,11 +910,7 @@=0A= | NGE_GPIO_GP3_IN | NGE_GPIO_GP4_IN);=0A= =0A= } else {=0A= - printf("nge%d: MII without any PHY!\n", sc->nge_unit);=0A= - if_free(ifp);=0A= - bus_release_resource(dev, SYS_RES_IRQ, 0, sc->nge_irq);=0A= - bus_release_resource(dev, NGE_RES, NGE_RID, =0A= - sc->nge_res);=0A= + device_printf(dev, "MII without any PHY!\n");=0A= error =3D ENXIO;=0A= goto fail;=0A= }=0A= @@ -931,24 +921,21 @@=0A= */=0A= ether_ifattach(ifp, eaddr);=0A= callout_init(&sc->nge_stat_ch, CALLOUT_MPSAFE);=0A= + return (0);=0A= =0A= - /*=0A= - * Hookup IRQ last.=0A= - */=0A= - error =3D bus_setup_intr(dev, sc->nge_irq, INTR_TYPE_NET | INTR_MPSAFE,=0A= - nge_intr, sc, &sc->nge_intrhand);=0A= - if (error) {=0A= - /* XXX: resource leaks */=0A= +fail:=0A= + if (sc->nge_ldata)=0A= + contigfree(sc->nge_ldata,=0A= + sizeof(struct nge_list_data), M_DEVBUF);=0A= + if (ifp)=0A= if_free(ifp);=0A= + if (sc->nge_intrhand)=0A= + bus_teardown_intr(dev, sc->nge_irq, sc->nge_intrhand);=0A= + if (sc->nge_irq)=0A= bus_release_resource(dev, SYS_RES_IRQ, 0, sc->nge_irq);=0A= + if (sc->nge_res)=0A= bus_release_resource(dev, NGE_RES, NGE_RID, sc->nge_res);=0A= - printf("nge%d: couldn't set up irq\n", unit);=0A= - }=0A= -=0A= -fail:=0A= -=0A= - if (error)=0A= - NGE_LOCK_DESTROY(sc);=0A= + NGE_LOCK_DESTROY(sc);=0A= return(error);=0A= }=0A= =0A= @@ -1345,8 +1332,8 @@=0A= if (CSR_READ_4(sc, NGE_TBI_BMSR) =0A= & NGE_TBIBMSR_ANEG_DONE) {=0A= if (bootverbose)=0A= - printf("nge%d: gigabit link up\n",=0A= - sc->nge_unit);=0A= + if_printf(sc->nge_ifp, =0A= + "gigabit link up\n");=0A= nge_miibus_statchg(sc->nge_miibus);=0A= sc->nge_link++;=0A= if (ifp->if_snd.ifq_head !=3D NULL)=0A= @@ -1363,8 +1350,8 @@=0A= sc->nge_link++;=0A= if (IFM_SUBTYPE(mii->mii_media_active) =0A= =3D=3D IFM_1000_T && bootverbose)=0A= - printf("nge%d: gigabit link up\n",=0A= - sc->nge_unit);=0A= + if_printf(sc->nge_ifp, =0A= + "gigabit link up\n");=0A= if (ifp->if_snd.ifq_head !=3D NULL)=0A= nge_start_locked(ifp);=0A= }=0A= @@ -1682,6 +1669,7 @@=0A= * Cancel pending I/O and free all RX/TX buffers.=0A= */=0A= nge_stop(sc);=0A= + nge_reset(sc);=0A= =0A= if (sc->nge_tbi) {=0A= mii =3D NULL;=0A= @@ -1702,8 +1690,8 @@=0A= =0A= /* Init circular RX list. */=0A= if (nge_list_rx_init(sc) =3D=3D ENOBUFS) {=0A= - printf("nge%d: initialization failed: no "=0A= - "memory for rx buffers\n", sc->nge_unit);=0A= + if_printf(sc->nge_ifp, "initialization failed: no "=0A= + "memory for rx buffers\n");=0A= nge_stop(sc);=0A= return;=0A= }=0A= @@ -2086,7 +2074,7 @@=0A= sc =3D ifp->if_softc;=0A= =0A= ifp->if_oerrors++;=0A= - printf("nge%d: watchdog timeout\n", sc->nge_unit);=0A= + if_printf(sc->nge_ifp, "watchdog timeout\n");=0A= =0A= NGE_LOCK(sc);=0A= nge_stop(sc);=0A= ------=_NextPart_000_092B_01C5CB37.7E6C8C50-- From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 14:10:12 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4389516A41F for ; Fri, 7 Oct 2005 14:10:12 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: from mail.lrtc.lt (pegasus.lrtc.lt [217.9.240.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6050D43D49 for ; Fri, 7 Oct 2005 14:10:11 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: (qmail 3928 invoked from network); 7 Oct 2005 14:03:17 -0000 Received: from p2p-241-242-ird.vln0.lrtc.net (HELO donatas) (d.gendvilas@[217.9.241.242]) (envelope-sender ) by mail.lrtc.lt (qmail-ldap-1.03) with SMTP for ; 7 Oct 2005 14:03:17 -0000 Message-ID: <006101c5cb48$d3126890$9f90a8c0@donatas> From: "Donatas" To: , References: <200510070742.j977gEqi099723@lurza.secnetix.de> Date: Fri, 7 Oct 2005 17:10:08 +0300 Organization: AB Lietuvos Radijo ir Televizijos Centras MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1257" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: Subject: Re: double tagged vlans on 6.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Donatas List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 14:10:12 -0000 netgraph sweet netgraph... think you understand on my mind was a liitle bit different solution of = the problem :] ifconfig vlan 10 create && ifconfig vlan10 vlan 10 vlandev fxp0 ifconfig vlan 111 create && ifconfig vlan111 vlan 111vlandev vlan10 > Donatas wrote: > > Just wonder - what is the major reason double vlan support (also = known as q-in-q > > or nested vlan) is still not included in freebsd. >=20 > It is supported, for years already (even in FreeBSD 4.x). > See ng_vlan(4). You can even do q-in-q-in-q if you want > (do Cisco etc. support that?). ;-) >=20 > Best regards > Oliver >=20 > --=20 > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. >=20 > "What is this talk of 'release'? We do not make software 'releases'. > Our software 'escapes', leaving a bloody trail of designers and = quality > assurance people in its wake." > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 14:56:35 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4978416A41F for ; Fri, 7 Oct 2005 14:56:35 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 889D943D4C for ; Fri, 7 Oct 2005 14:56:34 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (slghcx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j97EuWPM015057; Fri, 7 Oct 2005 16:56:32 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j97EuWFK015056; Fri, 7 Oct 2005 16:56:32 +0200 (CEST) (envelope-from olli) Date: Fri, 7 Oct 2005 16:56:32 +0200 (CEST) Message-Id: <200510071456.j97EuWFK015056@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG, Donatas In-Reply-To: <006101c5cb48$d3126890$9f90a8c0@donatas> X-Newsgroups: list.freebsd-net User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: Re: double tagged vlans on 6.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG, Donatas List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 14:56:35 -0000 [broken quoting fixed] Donatas wrote: > Oliver Fromme wrote: > > Donatas wrote: > > > Just wonder - what is the major reason double vlan support > > > (also known as q-in-q or nested vlan) is still not included > > > in freebsd. > > > > It is supported, for years already (even in FreeBSD 4.x). > > See ng_vlan(4). You can even do q-in-q-in-q if you want > > (do Cisco etc. support that?). ;-) > > netgraph sweet netgraph... > > think you understand on my mind was a liitle bit different > solution of the problem :] > > ifconfig vlan 10 create && ifconfig vlan10 vlan 10 vlandev fxp0 > ifconfig vlan 111 create && ifconfig vlan111 vlan 111vlandev vlan10 Well, then you should switch your mind to the solution using netgraph. ;-) Anyway -- You asked "what is the major reason double vlan support is still not included", and the answer simply is: 1. It _is_ included (only in a way different from what you were thinking -- but nevertheless, it _is_ there). 2. The major reason that nobody has implemented a way to do it with ifconfig (like you proposed), is probably the fact that there's already a different way (using netgraph). So nobody was motivated to implement yet another way to do it, I guess. If you don't like to do it with netgraph, I suggest you write some patches and submit them with send-pr(1). If the patches are good, they will certainly get committed. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Perl will consistently give you what you want, unless what you want is consistency." -- Larry Wall From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 14:58:59 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87C9E16A41F for ; Fri, 7 Oct 2005 14:58:59 +0000 (GMT) (envelope-from tbyte@otel.net) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1661443D48 for ; Fri, 7 Oct 2005 14:58:58 +0000 (GMT) (envelope-from tbyte@otel.net) Received: from dragon.otel.net ([212.36.8.135] helo=DraGoN.OTEL.net.) by mail.otel.net with esmtp (Exim 4.30; FreeBSD) id 1ENtgV-000Dtx-Vl for freebsd-net@freebsd.org; Fri, 07 Oct 2005 17:58:55 +0300 From: Iasen Kostov To: freebsd-net@freebsd.org Content-Type: multipart/mixed; boundary="=-ZBrDdf1kBks9icJtvY6g" Date: Fri, 07 Oct 2005 17:58:55 +0300 Message-Id: <1128697135.71975.24.camel@DraGoN.OTEL.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Subject: Proxy arp should only replay on specified interface. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 14:58:59 -0000 --=-ZBrDdf1kBks9icJtvY6g Content-Type: text/plain Content-Transfer-Encoding: 7bit IMHO proxy arp should only replay on specified interface not on every arp capable interface which recieved request for the proxied address. If lets say host A have arp capable if0 and if1 interfaces and U set: route add -host 1.0.0.2 -iface if1 -proxy and then a request is recieved on if0 for 1.0.0.2, host A will replay that it has it (which IMHO is wrong as the proxy route is set for if1). This sometimes is a big problem for our PPPoE/VPN server when the client uses linux or some small routers (e.g Linksys or something) probably linux based. It happen that sometimes (when the link is down or god knows why) it broadcasts arp "who-has" and the gateway replays. Then this host try to use ethernet path and not the (right) tunnel path until arp cache expires (which is not real fun as there is firewall rules blocking ethernet path :)). And even worse :) - I can think of ways to bypass routing protocols using proxy-arp routes like the one mentioned above. But it will not work if proxy-arp behaves the way it does now. And 1 thing more - there could be a switch which restores (or turns on) old behavior. (patch agains 5.4-STABLE is attached) regards. --=-ZBrDdf1kBks9icJtvY6g Content-Disposition: attachment; filename=if_ether.c.diff Content-Type: text/x-patch; name=if_ether.c.diff; charset=UTF-8 Content-Transfer-Encoding: 7bit --- if_ether.c.orig Fri Apr 1 23:18:43 2005 +++ if_ether.c Fri Oct 7 16:56:19 2005 @@ -796,6 +796,13 @@ #endif } else { rt = la->la_rt; + if (rt->rt_ifp != ifp) { +#ifdef DEBUG_PROXY + printf("arp: droped proxy request for %s on wrong interface %s\n", + inet_ntoa(itaddr), ifp->if_xname); +#endif + goto drop; + } (void)memcpy(ar_tha(ah), ar_sha(ah), ah->ar_hln); sdl = SDL(rt->rt_gateway); (void)memcpy(ar_sha(ah), LLADDR(sdl), ah->ar_hln); --=-ZBrDdf1kBks9icJtvY6g-- From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 15:53:07 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F68F16A41F for ; Fri, 7 Oct 2005 15:53:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ADEC43D45 for ; Fri, 7 Oct 2005 15:53:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.71.31]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0INZ00AUXYS6WIV0@vms046.mailsrvcs.net> for freebsd-net@freebsd.org; Fri, 07 Oct 2005 10:52:55 -0500 (CDT) Date: Fri, 07 Oct 2005 11:52:56 -0400 From: Chuck Swiger In-reply-to: <1128697135.71975.24.camel@DraGoN.OTEL.net> To: Iasen Kostov Message-id: <434699D8.7000306@mac.com> Organization: The Courts of Chaos MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en References: <1128697135.71975.24.camel@DraGoN.OTEL.net> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Cc: freebsd-net@freebsd.org Subject: Re: Proxy arp should only replay on specified interface. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 15:53:07 -0000 Iasen Kostov wrote: > IMHO proxy arp should only replay on specified interface not on every > arp capable interface which recieved request for the proxied address. This is an interesting idea, but shouldn't it at least take into consideration whether some interfaces are being bridged...? -- -Chuck From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 16:34:14 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E0BC16A41F for ; Fri, 7 Oct 2005 16:34:14 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCFA643D45 for ; Fri, 7 Oct 2005 16:34:13 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j97GYDvJ015221; Fri, 7 Oct 2005 09:34:13 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j97GYDRX015220; Fri, 7 Oct 2005 09:34:13 -0700 Date: Fri, 7 Oct 2005 09:34:13 -0700 From: Brooks Davis To: freebsd-net@freebsd.org, Donatas Message-ID: <20051007163413.GC12691@odin.ac.hmc.edu> References: <006101c5cb48$d3126890$9f90a8c0@donatas> <200510071456.j97EuWFK015056@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WfZ7S8PLGjBY9Voh" Content-Disposition: inline In-Reply-To: <200510071456.j97EuWFK015056@lurza.secnetix.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Subject: Re: double tagged vlans on 6.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 16:34:14 -0000 --WfZ7S8PLGjBY9Voh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 07, 2005 at 04:56:32PM +0200, Oliver Fromme wrote: > [broken quoting fixed] >=20 > Donatas wrote: > > Oliver Fromme wrote: > > > Donatas wrote: > > > > Just wonder - what is the major reason double vlan support > > > > (also known as q-in-q or nested vlan) is still not included > > > > in freebsd. > > >=20 > > > It is supported, for years already (even in FreeBSD 4.x). > > > See ng_vlan(4). You can even do q-in-q-in-q if you want > > > (do Cisco etc. support that?). ;-) > >=20 > > netgraph sweet netgraph... > >=20 > > think you understand on my mind was a liitle bit different > > solution of the problem :] > >=20 > > ifconfig vlan 10 create && ifconfig vlan10 vlan 10 vlandev fxp0 > > ifconfig vlan 111 create && ifconfig vlan111 vlan 111vlandev vlan10 >=20 > Well, then you should switch your mind to the solution > using netgraph. ;-) >=20 > Anyway -- You asked "what is the major reason double vlan > support is still not included", and the answer simply is: >=20 > 1. It _is_ included (only in a way different from what > you were thinking -- but nevertheless, it _is_ there). >=20 > 2. The major reason that nobody has implemented a way to > do it with ifconfig (like you proposed), is probably > the fact that there's already a different way (using > netgraph). So nobody was motivated to implement yet > another way to do it, I guess. >=20 > If you don't like to do it with netgraph, I suggest you > write some patches and submit them with send-pr(1). > If the patches are good, they will certainly get committed. The real reason the normal vlan framework doens't support it is that they framework is not all that well designed. It meets the requirements to simple handling of a trunked port, but little else. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --WfZ7S8PLGjBY9Voh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDRqOEXY6L6fI4GtQRAokwAJ9NrGSQHi6eQuxm+m3Fd/PpiBu9SwCfeE2P vUU3P2kBSfh4ZxNYUfoUDdI= =oGnn -----END PGP SIGNATURE----- --WfZ7S8PLGjBY9Voh-- From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 18:05:54 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A84C216A41F for ; Fri, 7 Oct 2005 18:05:54 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A87743D48 for ; Fri, 7 Oct 2005 18:05:53 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (hcxina@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j97I5pAu022268 for ; Fri, 7 Oct 2005 20:05:52 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j97I5pI7022267; Fri, 7 Oct 2005 20:05:51 +0200 (CEST) (envelope-from olli) Date: Fri, 7 Oct 2005 20:05:51 +0200 (CEST) Message-Id: <200510071805.j97I5pI7022267@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG In-Reply-To: <200509231024.j8NAOEK0008037@lurza.secnetix.de> X-Newsgroups: list.freebsd-net User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: Re: VIA VT6103 support (VIA EPIA PD) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 18:05:54 -0000 Oliver Fromme wrote: > Antony Mawer wrote: > > I'm using one of the PD10000 EPIA machines as a mail > > server/router/firewall/etc at home and it performs quite nicely at the > > job. I haven't noticed any problems with the network on it...: > > Cool, thanks! I just ordered mine. :-) It arrived last week, I installed it in a standard ATX Midi- tower, plugged a DDR DIMM and a hard disk to it, and it ran flawlessly out of the box. Every single on-board component is supported by FreeBSD. :) It has survived several buildworlds and network activity without any problems. It's now running today's 6.0-BETA5. Here's a copy of dmesg, if someone's interested: http://www.secnetix.de/~olli/dmesg/epia.6.0-BETA5.txt > > It's currently running 6.0-BETA2 (although I'll be bringing it > > up-to-date with the latest RELENG_6 shortly; buildworld on the machine > > does take a while so I'll probably NFS mount it off another faster machine!) > > How long does a buildworld take? Now I can answer my question myself: The buildworld of 6.0-BETA5 takes 1 hour 50 minutes (I excluded Kerberos and a few other small parts, though). > PS: An related question (although off-topic here): > I assume a Mini-ITX board fits into a standard ATX Midi- > tower without problems, right? At least it fits perfectly into the ATX Midi tower that I bought. A pretty cheap one even (but still good). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 20:38:20 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD6CF16A41F for ; Fri, 7 Oct 2005 20:38:20 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61E7243D46 for ; Fri, 7 Oct 2005 20:38:20 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so689164qbd for ; Fri, 07 Oct 2005 13:38:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ZFINr4t/ZyAD9kAQ9RnD/UqaErsg1rUKQMHIlxpOPt46MyaSR7kKRxqQGhvfSAraF1hHcTaLMjyCMhQ/GMbQc1T81KbMUXfWrKE0dQv9hmic1x5w6J9QjTpi8VUo8uQHkcVd0A809NgGusCS7aYs7+COoM2XQFjR2tPMyxgVW3I= Received: by 10.65.123.10 with SMTP id a10mr1691117qbn; Fri, 07 Oct 2005 13:32:13 -0700 (PDT) Received: by 10.65.151.20 with HTTP; Fri, 7 Oct 2005 13:32:13 -0700 (PDT) Message-ID: <35de0c300510071332p78a23c4bjd764fd21689cec0e@mail.gmail.com> Date: Fri, 7 Oct 2005 16:32:13 -0400 From: Bryan Fullerton To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: if_re.c build error on RELENG_6 (rev 1.46.2.5) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bryan Fullerton List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 20:38:20 -0000 This was reported by someone else to -stable, but seems more appropriate here. if_re.c breaks buildkernel on a RELENG_6 system that was just cvsup'ed. Was not broken yesterday. % grep FreeBSD /build/src/sys/dev/re/if_re.c __FBSDID("$FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.5 2005/10/07 14:00:04 glebius Exp $"); % make buildkernel KERNCONF=3DSAMURAI [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -g -nostdinc -I- -I. -I/build/src/sys -I/build/src/sys/contrib/dev/acpica -I/build/src/sys/contrib/altq -I/build/src/sys/contrib/ipfilter -I/build/src/sys/contrib/pf -I/build/src/sys/contrib/dev/ath -I/build/src/sys/contrib/dev/ath/freebsd -I/build/src/sys/contrib/ngatm -I/build/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=3D8000 --param inline-unit-growth=3D100 --param large-function-growth=3D1000 -mno-align-long-strings -mpreferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /build/src/sys/dev/re/if_re.c /build/src/sys/dev/re/if_re.c: In function `re_ioctl': /build/src/sys/dev/re/if_re.c:2286: warning: 'error' might be used uninitialized in this function *** Error code 1 Stop in /build/obj/build/src/sys/SAMURAI. *** Error code 1 Stop in /build/src. *** Error code 1 Stop in /build/src. Thanks, Bryan From owner-freebsd-net@FreeBSD.ORG Fri Oct 7 21:02:22 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6C6416A41F for ; Fri, 7 Oct 2005 21:02:22 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B72A43D45 for ; Fri, 7 Oct 2005 21:02:21 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by qproxy.gmail.com with SMTP id a39so692440qbd for ; Fri, 07 Oct 2005 14:02:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dZX9iSBQF+Pm6OuGXahENXiIMDhrVfSw54CJQ7hf5aG/hGKH++Y4Na8uetUHtU2T0GhScBZ6PGOxwV55fzXIbxtmW4uGQdVvxX4n6m6XAPK7QDAaH9+z06duBEW/uFM6T7j+f0xU0CfdGdK+wfwRS0SZKAMC3pDBGC/h95SLckA= Received: by 10.65.107.14 with SMTP id j14mr1690758qbm; Fri, 07 Oct 2005 14:02:20 -0700 (PDT) Received: by 10.65.151.20 with HTTP; Fri, 7 Oct 2005 14:02:20 -0700 (PDT) Message-ID: <35de0c300510071402r2825cf42g3252daeedb0bab4f@mail.gmail.com> Date: Fri, 7 Oct 2005 17:02:20 -0400 From: Bryan Fullerton To: freebsd-net@freebsd.org In-Reply-To: <35de0c300510071332p78a23c4bjd764fd21689cec0e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <35de0c300510071332p78a23c4bjd764fd21689cec0e@mail.gmail.com> Subject: Re: if_re.c build error on RELENG_6 (rev 1.46.2.5) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bryan Fullerton List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2005 21:02:22 -0000 On 10/7/05, Bryan Fullerton wrote: > This was reported by someone else to -stable, but seems more > appropriate here. if_re.c breaks buildkernel on a RELENG_6 system that > was just cvsup'ed. Was not broken yesterday. [snip] Ah, I see on -stable that the alpha tinderbox just barfed with this same error. I expect the others will follow shortly... Bryan From owner-freebsd-net@FreeBSD.ORG Sat Oct 8 02:04:12 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E59716A41F; Sat, 8 Oct 2005 02:04:12 +0000 (GMT) (envelope-from david.mao@thomson.net) Received: from dmzraw4.extranet.tce.com (dmzraw4.extranet.tce.com [157.254.234.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id F105443D46; Sat, 8 Oct 2005 02:04:11 +0000 (GMT) (envelope-from david.mao@thomson.net) Received: from indyvss1.am.thmulti.com (unknown [157.254.92.60]) by dmzraw4.extranet.tce.com (Postfix) with ESMTP id B4CD116E8; Sat, 8 Oct 2005 02:04:10 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by indyvss1.am.thmulti.com (Postfix) with ESMTP id 71545BBB02; Sat, 8 Oct 2005 02:04:10 +0000 (GMT) Received: from indyvss1.am.thmulti.com ([127.0.0.1]) by localhost (indyvss1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 09466-01-55; Sat, 8 Oct 2005 02:04:08 +0000 (GMT) Received: from smtprelay2.indy.tce.com (smtprelay2.indy.tce.com [157.254.96.95]) by indyvss1.am.thmulti.com (Postfix) with ESMTP id 0E4D9BBAF1; Sat, 8 Oct 2005 02:04:08 +0000 (GMT) Received: from boulsmailbh01.eu.thmulti.com (localhost [127.0.0.1]) by smtprelay2.indy.tce.com (8.12.9/8.12.8) with ESMTP id j98245gt011929; Sat, 8 Oct 2005 02:04:06 GMT Received: from TAHKSMAILBH01.ap.thmulti.com ([141.11.13.33]) by boulsmailbh01.eu.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 8 Oct 2005 04:04:05 +0200 Received: from bjngsmail01.ap.thmulti.com ([10.11.70.35]) by TAHKSMAILBH01.ap.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 8 Oct 2005 10:04:01 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Sat, 8 Oct 2005 10:03:56 +0800 Message-ID: <31021C278A7A6B4AB95E9A085C3552181F78F4@bjngsmail01> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: problems with em(4) Thread-Index: AcXHhgz2MBOlXufvRq+pHaQo2HVt7AEJl23A From: "Mao Shou Yan" To: "Gleb Smirnoff" X-OriginalArrivalTime: 08 Oct 2005 02:04:01.0791 (UTC) FILETIME=[8D73B0F0:01C5CBAC] X-Virus-Scanned: amavisd-new at thomson.net Cc: freebsd-net@freebsd.org Subject: RE: problems with em(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 02:04:12 -0000 I enable fast forwarding! With or without ipfw, result is the same. -----Original Message----- From: Gleb Smirnoff [mailto:glebius@FreeBSD.org]=20 Sent: 2005=C4=EA10=D4=C23=C8=D5 3:18 To: Mao Shou Yan Cc: freebsd-net@FreeBSD.org Subject: Re: problems with em(4) On Fri, Aug 12, 2005 at 01:48:59PM +0800, Mao Shou Yan wrote: M> I have a machine running 5.4 stable, with 3 em cards: M>=20 M> (1) Two 82543GC with fiber=20 M>=20 M> (2) One 82544 M>=20 M> All of them are shared irq 11( from vmstat -i) M>=20 M> =20 M>=20 M> The problem is: M>=20 M> After the system run about 3 hours, there will be large = "Ierrs" M> with the em0(BTW, em0 is in promisc mode). M>=20 M> I use "sysctl hw.em0.stats=3D1", found there are a lot of = "missed M> packets" and some "Receive with no buffers". M>=20 M> Em0 is in polling mode, and hz is 2000, burst_max and M> each_burst is the default value. M>=20 M> The system is not heavy loaded, incoming rates of em0 is = less M> than 150Mbits/s. em1 and em2 are not connected. M>=20 M> And pps is less than 30k. M>=20 M> After 3 hours, the ierrs raise quickly every 1 minutes! M>=20 M> From pciconf, I found the driver version is "1.7.35". M>=20 M> =20 M>=20 M> I think is a problem with em(4) driver. M>=20 M> Anyone meet such condition? Do you have ip fastforwarding enabled? Do you use any firewall filtering or any other additional packet processing on your router? --=20 Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Sat Oct 8 02:05:14 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7329B16A41F for ; Sat, 8 Oct 2005 02:05:14 +0000 (GMT) (envelope-from david.mao@thomson.net) Received: from dmzraw4.extranet.tce.com (dmzraw4.extranet.tce.com [157.254.234.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E0E443D55 for ; Sat, 8 Oct 2005 02:05:12 +0000 (GMT) (envelope-from david.mao@thomson.net) Received: from indyvss2.am.thmulti.com (unknown [157.254.92.61]) by dmzraw4.extranet.tce.com (Postfix) with ESMTP id 275021191; Sat, 8 Oct 2005 02:05:11 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by indyvss2.am.thmulti.com (Postfix) with ESMTP id 12AA48A157; Sat, 8 Oct 2005 02:05:11 +0000 (GMT) Received: from indyvss2.am.thmulti.com ([127.0.0.1]) by localhost (indyvss2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12540-01-96; Sat, 8 Oct 2005 02:05:08 +0000 (GMT) Received: from smtprelay2.indy.tce.com (smtprelay2.indy.tce.com [157.254.96.95]) by indyvss2.am.thmulti.com (Postfix) with ESMTP id D0A308A1FA; Sat, 8 Oct 2005 02:05:07 +0000 (GMT) Received: from boulsmailbh02.eu.thmulti.com (localhost [127.0.0.1]) by smtprelay2.indy.tce.com (8.12.9/8.12.8) with ESMTP id j98255gt012062; Sat, 8 Oct 2005 02:05:06 GMT Received: from TAHKSMAILBH01.ap.thmulti.com ([141.11.13.33]) by boulsmailbh02.eu.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 8 Oct 2005 04:05:05 +0200 Received: from bjngsmail01.ap.thmulti.com ([10.11.70.35]) by TAHKSMAILBH01.ap.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 8 Oct 2005 10:05:02 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Sat, 8 Oct 2005 10:04:58 +0800 Message-ID: <31021C278A7A6B4AB95E9A085C3552181F78FA@bjngsmail01> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: problems with em(4) Thread-Index: AcXHnrcg5cHczS7QSc25wjJYSS8WKQEDeHRA From: "Mao Shou Yan" To: X-OriginalArrivalTime: 08 Oct 2005 02:05:02.0072 (UTC) FILETIME=[B161D780:01C5CBAC] X-Virus-Scanned: amavisd-new at thomson.net Cc: freebsd-net@freebsd.org Subject: RE: problems with em(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 02:05:14 -0000 I modify kernel codes to stat that. And it's test in a real telecom environment. -----Original Message----- From: owner-freebsd-net@freebsd.org = [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Dave+Seddon Sent: 2005=C4=EA10=D4=C23=C8=D5 6:15 To: freebsd-net@FreeBSD.org Subject: Re: problems with em(4) Greetings,=20 > M> The problem is: > M>=20 > M> After the system run about 3 hours, there will be large = "Ierrs" > M> The system is not heavy loaded, incoming rates of em0 is = less > M> than 150Mbits/s. em1 and em2 are not connected. > M>=20 > M> After 3 hours, the ierrs raise quickly every 1 minutes! > M>=20 > M> I think is a problem with em(4) driver. > M>=20 > M> Anyone meet such condition? Yes. Lots of people. 3 hours does seem to be the magic number, = regardless=20 of the volumne of traffic.=20 I'm interested in what you do sniffing 150MB/s. Normally libpcap can't=20 handle that amount of traffic.=20 Regards, Dave Seddon _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sat Oct 8 07:42:17 2005 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CD3F16A41F for ; Sat, 8 Oct 2005 07:42:17 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F60843D45 for ; Sat, 8 Oct 2005 07:42:16 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id j987gEwp048221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Oct 2005 11:42:15 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id j987gE4X048220; Sat, 8 Oct 2005 11:42:14 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 8 Oct 2005 11:42:14 +0400 From: Gleb Smirnoff To: Mao Shou Yan Message-ID: <20051008074214.GI14542@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Mao Shou Yan , freebsd-net@FreeBSD.org References: <31021C278A7A6B4AB95E9A085C3552181F78F4@bjngsmail01> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <31021C278A7A6B4AB95E9A085C3552181F78F4@bjngsmail01> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: problems with em(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 07:42:17 -0000 On Sat, Oct 08, 2005 at 10:03:56AM +0800, Mao Shou Yan wrote: M> On Fri, Aug 12, 2005 at 01:48:59PM +0800, Mao Shou Yan wrote: M> M> I have a machine running 5.4 stable, with 3 em cards: M> M> M> M> (1) Two 82543GC with fiber M> M> M> M> (2) One 82544 M> M> M> M> All of them are shared irq 11( from vmstat -i) M> M> M> M> M> M> M> M> The problem is: M> M> M> M> After the system run about 3 hours, there will be large "Ierrs" M> M> with the em0(BTW, em0 is in promisc mode). M> M> M> M> I use "sysctl hw.em0.stats=1", found there are a lot of "missed M> M> packets" and some "Receive with no buffers". M> M> M> M> Em0 is in polling mode, and hz is 2000, burst_max and M> M> each_burst is the default value. M> M> M> M> The system is not heavy loaded, incoming rates of em0 is less M> M> than 150Mbits/s. em1 and em2 are not connected. M> M> M> M> And pps is less than 30k. M> M> M> M> After 3 hours, the ierrs raise quickly every 1 minutes! M> M> M> M> From pciconf, I found the driver version is "1.7.35". M> M> M> M> M> M> M> M> I think is a problem with em(4) driver. M> M> M> M> Anyone meet such condition? M> M> Do you have ip fastforwarding enabled? Do you use any firewall filtering M> or any other additional packet processing on your router? M> M> I enable fast forwarding! M> With or without ipfw, result is the same. Can you please try to disable fast forwarding and see whether this helps or not? P.S. Please do not use top quoting, it make email hard to read. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Sat Oct 8 10:13:13 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6190616A41F; Sat, 8 Oct 2005 10:13:13 +0000 (GMT) (envelope-from david.mao@thomson.net) Received: from dmzraw4.extranet.tce.com (dmzraw4.extranet.tce.com [157.254.234.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id D07C443D45; Sat, 8 Oct 2005 10:13:12 +0000 (GMT) (envelope-from david.mao@thomson.net) Received: from indyvss4.am.thmulti.com (unknown [157.254.92.63]) by dmzraw4.extranet.tce.com (Postfix) with ESMTP id B9E16150D; Sat, 8 Oct 2005 10:13:11 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by indyvss4.am.thmulti.com (Postfix) with ESMTP id 1F1E96DA09; Sat, 8 Oct 2005 10:10:07 +0000 (GMT) Received: from indyvss4.am.thmulti.com ([127.0.0.1]) by localhost (indyvss4 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20603-01-76; Sat, 8 Oct 2005 10:10:03 +0000 (GMT) Received: from indysmailcs01.am.thmulti.com (indysmailcs01.am.thmulti.com [157.254.96.5]) by indyvss4.am.thmulti.com (Postfix) with ESMTP id 4FABC6D9C1; Sat, 8 Oct 2005 10:10:03 +0000 (GMT) Received: from INDYSMAILBH02.am.thmulti.com ([157.254.96.2]) by indysmailcs01.am.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 8 Oct 2005 05:13:07 -0500 Received: from tahkexch2k.ap.thmulti.com ([141.11.13.12]) by INDYSMAILBH02.am.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 8 Oct 2005 05:13:07 -0500 Received: from bjngsmail01.ap.thmulti.com ([10.11.70.35]) by tahkexch2k.ap.thmulti.com with Microsoft SMTPSVC(5.0.2195.6713); Sat, 8 Oct 2005 18:13:04 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Sat, 8 Oct 2005 18:13:02 +0800 Message-ID: <31021C278A7A6B4AB95E9A085C35521821EC0B@bjngsmail01> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: problems with em(4) Thread-Index: AcXL3FNkRJf62ufURNSNa0yTEXSiJgAFBglw From: "Mao Shou Yan" To: "Gleb Smirnoff" X-OriginalArrivalTime: 08 Oct 2005 10:13:04.0679 (UTC) FILETIME=[DF2D1370:01C5CBF0] X-Virus-Scanned: amavisd-new at thomson.net Cc: freebsd-net@freebsd.org Subject: RE: problems with em(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 10:13:13 -0000 My testing is not related with fast forwarding. It only runs on layer 2(bridge). But the bridge and fast forwarding are in the same style. Both of them run in the same path as driver. I think it's not a problem with fast forwarding. -----Original Message----- From: owner-freebsd-net@freebsd.org = [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Gleb Smirnoff Sent: 2005=C4=EA10=D4=C28=C8=D5 15:42 To: Mao Shou Yan Cc: freebsd-net@FreeBSD.org Subject: Re: problems with em(4) On Sat, Oct 08, 2005 at 10:03:56AM +0800, Mao Shou Yan wrote: M> On Fri, Aug 12, 2005 at 01:48:59PM +0800, Mao Shou Yan wrote: M> M> I have a machine running 5.4 stable, with 3 em cards: M> M>=20 M> M> (1) Two 82543GC with fiber=20 M> M>=20 M> M> (2) One 82544 M> M>=20 M> M> All of them are shared irq 11( from vmstat -i) M> M>=20 M> M> =20 M> M>=20 M> M> The problem is: M> M>=20 M> M> After the system run about 3 hours, there will be large = "Ierrs" M> M> with the em0(BTW, em0 is in promisc mode). M> M>=20 M> M> I use "sysctl hw.em0.stats=3D1", found there are a lot of = "missed M> M> packets" and some "Receive with no buffers". M> M>=20 M> M> Em0 is in polling mode, and hz is 2000, burst_max and M> M> each_burst is the default value. M> M>=20 M> M> The system is not heavy loaded, incoming rates of em0 is = less M> M> than 150Mbits/s. em1 and em2 are not connected. M> M>=20 M> M> And pps is less than 30k. M> M>=20 M> M> After 3 hours, the ierrs raise quickly every 1 minutes! M> M>=20 M> M> From pciconf, I found the driver version is "1.7.35". M> M>=20 M> M> =20 M> M>=20 M> M> I think is a problem with em(4) driver. M> M>=20 M> M> Anyone meet such condition? M>=20 M> Do you have ip fastforwarding enabled? Do you use any firewall = filtering M> or any other additional packet processing on your router? M>=20 M> I enable fast forwarding! M> With or without ipfw, result is the same. Can you please try to disable fast forwarding and see whether this helps or not? P.S. Please do not use top quoting, it make email hard to read. --=20 Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sat Oct 8 14:02:41 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D434716A41F for ; Sat, 8 Oct 2005 14:02:41 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BBC143D45 for ; Sat, 8 Oct 2005 14:02:41 +0000 (GMT) (envelope-from mike@sentex.net) Received: from BLUELAPIS.sentex.ca (cage.simianscience.com [64.7.134.1]) by smarthost2.sentex.ca (8.13.4/8.13.4) with SMTP id j98E2d7F020852; Sat, 8 Oct 2005 10:02:39 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: Oliver Fromme Date: Sat, 08 Oct 2005 10:02:50 -0400 Message-ID: <05kfk11pk1o960o0bro2lr7d7jhi5l28et@4ax.com> References: <200509231024.j8NAOEK0008037@lurza.secnetix.de> <200510071805.j97I5pI7022267@lurza.secnetix.de> In-Reply-To: <200510071805.j97I5pI7022267@lurza.secnetix.de> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: freebsd-net@freebsd.org Subject: Re: VIA VT6103 support (VIA EPIA PD) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 14:02:42 -0000 On Fri, 7 Oct 2005 20:05:51 +0200 (CEST), in sentex.lists.freebsd.net you wrote: > >It has survived several buildworlds and network activity >without any problems. It's now running today's 6.0-BETA5. >Here's a copy of dmesg, if someone's interested: > >http://www.secnetix.de/~olli/dmesg/epia.6.0-BETA5.txt > IF you use FAST_IPSEC, load the padlock.,ko as it makes a nice speed boost! Also, you will need to use the patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/86598 otherwise you will get the odd SSH problem when using AES ---Mike -------------------------------------------------------- Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 mike@sentex.net, (http://www.tancsa.com)