From owner-freebsd-net@FreeBSD.ORG Sun Nov 23 00:13:25 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A6641065670; Sun, 23 Nov 2008 00:13:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5E5FE8FC13; Sun, 23 Nov 2008 00:13:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAN0DPYg062803; Sun, 23 Nov 2008 00:13:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAN0DP7H062799; Sun, 23 Nov 2008 00:13:25 GMT (envelope-from linimon) Date: Sun, 23 Nov 2008 00:13:25 GMT Message-Id: <200811230013.mAN0DP7H062799@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/129074: [ppp] [panic] kernel panic with pppoe_server 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, 23 Nov 2008 00:13:25 -0000 Old Synopsis: kernel panic New Synopsis: [ppp] [panic] kernel panic with pppoe_server Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Nov 23 00:12:30 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=129074 From owner-freebsd-net@FreeBSD.ORG Sun Nov 23 15:40:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24C0E1065673 for ; Sun, 23 Nov 2008 15:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 17A958FC1A for ; Sun, 23 Nov 2008 15:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mANFe3jI098313 for ; Sun, 23 Nov 2008 15:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mANFe3Dt098312; Sun, 23 Nov 2008 15:40:03 GMT (envelope-from gnats) Date: Sun, 23 Nov 2008 15:40:03 GMT Message-Id: <200811231540.mANFe3Dt098312@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Marius Strobl Cc: Subject: Re: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Nov 2008 15:40:04 -0000 The following reply was made to PR kern/128833; it has been noted by GNATS. From: Marius Strobl To: David Christensen Cc: bug-followup@FreeBSD.org Subject: Re: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot Date: Sun, 23 Nov 2008 16:34:59 +0100 On Mon, Nov 17, 2008 at 11:37:19AM -0800, David Christensen wrote: > > Ok, thanks for testing anyway. > > I still think that this isn't really a driver bug though but > > you are hitting some hardware-related problem like f.e. a > > silicon bug and the question is how to work around it. > > There is a documented errata for the 5701 A3 where a 64bit DMA > read can be terminated early by the bridge and then completed > later as a 32bit access, causing corruption on the 5701. The > errata states this type of behavior is rare in bridges and that > the workaround is to force 32bit operation (set bit 15 of register > 0x6800). It's not clear whether this errata is occurring without > seeing a but trace but it certainly sounds right. The only > question would be knowing "when" to force 32bit operation. Should > it be done in all cases or only for this bridge? > David, could it be that bug doesn't only affect 5701 A3 but also B3 (i.e. chipid 0x01050000) as in this case or even all 5701 revisions? How does the problem you describe relate to the 5701 PCI-X issue, which we align the RX buffer differently for as a workaround, would that problem also be avoided by limiting 5701 to 32-bit operations? Or is the A3-errata you described an entirely different issue and limited to 5701 in a 64-bit non-PCI-X slot, or would 5701 in a PCI-X slot even require both workarounds? Marius From owner-freebsd-net@FreeBSD.ORG Sun Nov 23 17:25:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8EA1106564A for ; Sun, 23 Nov 2008 17:25:11 +0000 (UTC) (envelope-from eitans@mellanox.co.il) Received: from mellanox.co.il (mail.mellanox.co.il [194.90.237.43]) by mx1.freebsd.org (Postfix) with ESMTP id 8C6608FC0A for ; Sun, 23 Nov 2008 17:25:09 +0000 (UTC) (envelope-from eitans@mellanox.co.il) Received: from Internal Mail-Server by MTLPINE1 (envelope-from eitans@mellanox.co.il) with SMTP; 23 Nov 2008 19:25:06 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Sun, 23 Nov 2008 19:24:48 +0200 Message-ID: <5D49E7A8952DC44FB38C38FA0D758EAD0105450B@mtlexch01.mtl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IP fragmentation Thread-Index: AclNkGLMWsxOl8nETR6EdmKPzb9N6A== From: "Eitan Shefi" To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi Subject: IP fragmentation 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, 23 Nov 2008 17:25:12 -0000 Hi, =20 The IP fragmentation is not like in Linux, and is not clear to me. =20 I'm using 2 FreeBSD-6.3 hosts, connected directly. If I change the MTU of both hosts to 5000, and send "ping" with message size 4972 bytes ( 4972 =3D 5000 - 8(which is ICMP Header size) - 20 = (which is IP Header size) ) from one host to the other, the message is passed as one packet: packet size 5000 bytes. (as expected) But if I send "ping" with message size 4973 bytes, the IP fragmentation to 2 packets is not clear to me: The first packet is with size: 4116 bytes The second packet is with size: 905 bytes =20 I expected the first packet size to be: 4996 =3D 5000 - ((5000-20) Mod = 8) and the second packet size to be: 25 =3D 5021 - 4996 =20 What is the formula being used in FreeBSD to compute the IP fragments size? =20 =20 Thanks, Eitan =20 From owner-freebsd-net@FreeBSD.ORG Sun Nov 23 17:50:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A158E1065672 for ; Sun, 23 Nov 2008 17:50:13 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD618FC17 for ; Sun, 23 Nov 2008 17:50:13 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 320E341C705; Sun, 23 Nov 2008 18:50:11 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id Bg+UmxD6gXjJ; Sun, 23 Nov 2008 18:50:07 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id EEECF41C70C; Sun, 23 Nov 2008 18:50:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id A62AA444902; Sun, 23 Nov 2008 17:45:23 +0000 (UTC) Date: Sun, 23 Nov 2008 17:45:23 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Eitan Shefi In-Reply-To: <5D49E7A8952DC44FB38C38FA0D758EAD0105450B@mtlexch01.mtl.com> Message-ID: <20081123173627.V61259@maildrop.int.zabbadoz.net> References: <5D49E7A8952DC44FB38C38FA0D758EAD0105450B@mtlexch01.mtl.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: IP fragmentation 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, 23 Nov 2008 17:50:13 -0000 On Sun, 23 Nov 2008, Eitan Shefi wrote: > Hi, > > The IP fragmentation is not like in Linux, and is not clear to me. > > I'm using 2 FreeBSD-6.3 hosts, connected directly. > If I change the MTU of both hosts to 5000, and send "ping" with message > size 4972 bytes ( 4972 = 5000 - 8(which is ICMP Header size) - 20 (which > is IP Header size) ) > from one host to the other, the message is passed as one packet: packet > size 5000 bytes. (as expected) > But if I send "ping" with message size 4973 bytes, the IP fragmentation > to 2 packets is not clear to me: > The first packet is with size: 4116 bytes > The second packet is with size: 905 bytes 4116 = 4096 + 20 20 usually is the size of the IP header 4096 most likely is your PAGE_SIZE I expected the first packet size to be: 4996 = 5000 - ((5000-20) Mod 8) > and the second packet size to be: 25 = 5021 - 4996 > > What is the formula being used in FreeBSD to compute the IP fragments > size? Try this here: http://fxr.watson.org/fxr/source/netinet/ip_output.c#L617 and see how 'len' gets adjusted. /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 02:00:50 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AA32106564A for ; Mon, 24 Nov 2008 02:00:50 +0000 (UTC) (envelope-from andreas.carbin@run.se) Received: from mailgw.upg.se (h-89-233-252-20.wholesale.rp80.se [89.233.252.20]) by mx1.freebsd.org (Postfix) with ESMTP id D75FD8FC08 for ; Mon, 24 Nov 2008 02:00:49 +0000 (UTC) (envelope-from andreas.carbin@run.se) Received: from localhost (localhost [127.0.0.1]) by mailgw.upg.se (Postfix) with ESMTP id 78F583AF4E5; Mon, 24 Nov 2008 02:36:56 +0100 (CET) X-Virus-Scanned: amavisd-new at upg.se Received: from mailgw.upg.se ([127.0.0.1]) by localhost (mailgw.upg.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUxzEqavjikH; Mon, 24 Nov 2008 02:36:51 +0100 (CET) Received: from mail03.upg.se (mail03.upg.se [77.72.100.141]) by mailgw.upg.se (Postfix) with ESMTP; Mon, 24 Nov 2008 02:36:51 +0100 (CET) Received: from mail03.upg.se (mail03.upg.se [77.72.100.141]) by mail03.upg.se (Postfix) with ESMTP id ED4A224014B; Mon, 24 Nov 2008 02:36:22 +0100 (CET) Date: Mon, 24 Nov 2008 02:36:22 +0100 (CET) From: Andreas Carbin To: freebsd-net@freebsd.org Message-ID: <19347937.95871227490582742.JavaMail.root@mail03> In-Reply-To: <8072814.95851227489833192.JavaMail.root@mail03> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [213.115.92.164] X-Mailer: Zimbra 5.0.10_GA_2638.UBUNTU8 (ZimbraWebClient - FF3.0 (Win)/5.0.10_GA_2638.UBUNTU8) Cc: andreas Subject: FreeBSD 7.0 / Recv-Q full ? / win 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: Mon, 24 Nov 2008 02:00:50 -0000 Hello all, I have the following issue with my (quite newly installed) FreeBSD 7.0 machines: (I use "FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 07:51:58 UTC 2008" on Dell PowerEdge 2970.) When I copy large files with SCP from one host to another the destination host's recieve queue seems to fill up after a random number of seconds (10 - 300) with about 89.000 bytes, and the destination host sends Window Size = 0 to the sender. This means no data is transferred and the connection has "locked up" in some way (true?). This almost always happens when I copy a file from one host to another where there is a WAN connection between them. I have checked firewall rules - these are open to almost any traffic. (I have seen it happen between two locally connected machines also.) When copying with SCP starts, it runs perfectly at about 10 megabyte/s (100Mbit/s WAN network). A 3 GB file may succeed <5%. Error occurrs in about 10 to 300 seconds - then all payload data traffic stops. The TCP connection is still open. My guess was that maybe we get errors when copying this fast "close to thoeretical limit", so I used "scp -l " where I specified as 50 and 5 Mbit/s. This reduces speed perfectly, but gives me the same errors as in full speed. I have also tried (with no good results): * net.inet.tcp.rfc1323 (on and off) * net.inet.tcp.tso (on and off) * RCXSUM and TXCSUM on and off * change from on-board bce0 / Broadcom NetXtreme II BCM5708 1000Base-T to em0 / Intel(R) PRO/1000 Network Connection Version - 6.7.3 * setting net.inet.tcp.recvbuf_max: 16777216 * setting net.inet.tcp.sendbuf_max: 16777216 One really strange thing is that I can make the copy continue (!) with full data transfer if I truss the ssh process on the destination machine. So if I truss with output to /dev/null in the background all the copy completes (!!!!). This is a tcpdump on destination host of SCP's TCP connection when no data is transferred: 15:56:17.798079 IP sender_host.51296 > destination_host.ssh: . 8:9(1) ack 1 win 33304 15:56:17.897407 IP destination_host.ssh > sender_host.51296: . ack 9 win 0 15:56:22.797808 IP sender_host.51296 > destination_host.ssh: . 9:10(1) ack 1 win 33304 15:56:22.897457 IP destination_host.ssh > sender_host.51296: . ack 10 win 0 15:56:27.797913 IP sender_host.51296 > destination_host.ssh: . 10:11(1) ack 1 win 33304 15:56:27.897508 IP destination_host.ssh > sender_host.51296: . ack 11 win 0 15:56:32.798016 IP sender_host.51296 > destination_host.ssh: . 11:12(1) ack 1 win 33304 15:56:32.897559 IP destination_host.ssh > sender_host.51296: . ack 12 win 0 15:56:37.798119 IP sender_host.51296 > destination_host.ssh: . 12:13(1) ack 1 win 33304 15:56:37.897610 IP destination_host.ssh > sender_host.51296: . ack 13 win 0 Does enyone have an idea what this might be? The error occurs when the receiving host is a FreeBSD 7.0 host (the sender can be 7.0 or 6.2 accoriding to my tests). Thank you, //Andreas ------------------------------------------------------- Andreas Carbin RUN Communications AB http://www.run.se E-mail: andreas.carbin@run.se ------------------------------------------------------- From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 04:23:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2CD31065672 for ; Mon, 24 Nov 2008 04:23:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by mx1.freebsd.org (Postfix) with ESMTP id 5DE208FC0A for ; Mon, 24 Nov 2008 04:23:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so1033299tib.3 for ; Sun, 23 Nov 2008 20:23:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Q5Xohe4f27jCTFOZmYfrEM/EnWYqlo6iFD2vd7gyUHA=; b=P41sAGcIHQRWdhlIt44ug8tvgvRsXzD2Fxr3TotJOlSopiNk78ZuGPvgYarEe6fWHW bBTbtc6ALFSE0Z+EFGxPDCnHm8JYlnpKshRVvonK4wlkh3oOg90B038SRY4SoLVGFnN+ C9/yzJC9fy8S7nB84/1mZf24eeI5rkyc2Xa3o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=hqQwZ3I765y+gjCbNP4FckxsBXgbxBKrY4tESIQUJXtPPExZDJ3mRhkD5b1p2eL95k 5dd92v6wdVNn66f9+lnF/Xz2IIOhmFx+hUx4uroJosjjDLscgluG3+dkSsfQLxSzIcco ofqLgVbqee/8vuiJ2EwMtYuEYI6nYrzASCuYc= Received: by 10.110.20.15 with SMTP id 15mr4292749tit.28.1227500590111; Sun, 23 Nov 2008 20:23:10 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b4sm7021655tic.2.2008.11.23.20.23.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Nov 2008 20:23:08 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mAO4L32P079998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Nov 2008 13:21:03 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mAO4L1Y3079997; Mon, 24 Nov 2008 13:21:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 24 Nov 2008 13:21:01 +0900 From: Pyun YongHyeon To: Gabriel Lavoie Message-ID: <20081124042101.GK78954@cdnetworks.co.kr> References: <20081117003856.GB50872@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: Realtek 8139 with rl(4) driver -> Poor performance X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2008 04:23:11 -0000 On Tue, Nov 18, 2008 at 09:09:44PM -0500, Gabriel Lavoie wrote: > Hum when I do my Samba transfer, there is a lot of small files (> 50 000) > and it seems at some point Samba tops at 100% CPU usage on one core. Is it > possible the rl(4) driver could be influenced by high CPU load? With the Yes, it's possible. rl(4) hardwares are notorious for its poor performance and instability under heavy load. I'm not sure the poor performance you're suffering from comes from rl(4) hardware itself or driver bug though. Note, ale(4) is not best hardware too. ale(4) hardwares still requires copy operation as rl(4) due to hardware limitation and if you're looking for better performance, replace your hardware with better controller such as em(4)/bge(4) or jme(4) which would have good performance/price ratio. > ale(4) driver, there's no problem but the Samba transfer becomes really slow > because of the amount of files. > > Gabriel > > 2008/11/18 Gabriel Lavoie > > > By the way, I'm currently trying the ale(4) driver under FreeBSD 7.0 (my > > current installation). It seems to works flawlesly with excellent > > performances. I'm currently doing the 30 GB transfer I'm unable to do with > > the Realtek card. I'll see what happens. > > > > Gabriel > > > > 2008/11/16 Pyun YongHyeon > > > > On Sun, Nov 16, 2008 at 06:01:58PM -0500, Gabriel Lavoie wrote: > >> > Hello, > >> > I recently built a new system to use as a home server. This system > >> has > >> > an Intel Pentium Dual Core E5200, 4GB RAM and an Asus P5KPL-CM > >> motherboard > >> > which has an Atheros L1E network adapter, not yet supported on FreeBSD. > >> For > >> > >> ale(4) was committed to HEAD. If you're using lastest stable/7 > >> see the following URL. > >> http://people.freebsd.org/~yongari/ale/README > >> > >> > now, I use a Realtek 8139 PCI adapter that uses the rl(4) driver, but > >> the > >> > upload performances are really poor (under 1 MB/sec). Is there any way > >> to > >> > improve the performance with this driver? This adapter was in a Linux > >> system > >> > with a Pentium III processor before and I could upload/download at > >> around 10 > >> > MB/sec in my local network with no problem at all. > >> > > >> > >> There was a bus_dma(9) bug in rl(4) and it was fixed in HEAD. > >> How about rl(4) in HEAD? I guess it would build with minor > >> modification. > >> > >> -- > >> Regards, > >> Pyun YongHyeon > >> > > > > > > > > -- > > Gabriel Lavoie > > glavoie@gmail.com > > > > > > -- > Gabriel Lavoie > glavoie@gmail.com -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 04:44:53 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9CC61065670 for ; Mon, 24 Nov 2008 04:44:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.188]) by mx1.freebsd.org (Postfix) with ESMTP id 497248FC0C for ; Mon, 24 Nov 2008 04:44:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so1038900tib.3 for ; Sun, 23 Nov 2008 20:44:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=5OwqJDtvXDeI1QKLtlRI6N4ZmR0RQp2VWHeBcrh0KIU=; b=DfvXJCyUaV3zAidGVl7lUiybKJJQZwuVkeZk51NlB+PuYKmJjuOg4r4Im8KI9Rm6Cg F6vDL2erUe2nlCuFrzvAyJTYJf16o6iQr6uMklq75QsFRoHqmdENrT0msG5bOOUFud9C VS/h73oNgPWeCkjbC2rT3HbH/aX3sJNVlrfn8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Heo1qU68g9NdcOyHWnP/XIyJo8aj1FF0AM0psX35MW1oOG5uiFDxI1NQtGLnL22lh/ MnfkpNT+H8dW0Gg6JC66db0RtFfohxbn6PCO9fBZ1wOys9qkKsGKJZkcCgAl027r/0xa phTNv3JGiPEgEcdBLyRHCDRUMuaCkHygi7fGA= Received: by 10.110.105.5 with SMTP id d5mr4303901tic.38.1227501891903; Sun, 23 Nov 2008 20:44:51 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b4sm7083452tic.2.2008.11.23.20.44.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Nov 2008 20:44:50 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mAO4gimO080089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Nov 2008 13:42:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mAO4ghic080088; Mon, 24 Nov 2008 13:42:43 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 24 Nov 2008 13:42:42 +0900 From: Pyun YongHyeon To: Gabriel Lavoie Message-ID: <20081124044242.GL78954@cdnetworks.co.kr> References: <957411.42240.qm@web39101.mail.mud.yahoo.com> <20081117023024.GE50872@cdnetworks.co.kr> <20081117034428.GG50872@cdnetworks.co.kr> <20081118043731.GD55015@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: bf , freebsd-net@freebsd.org Subject: Re: Realtek 8139 with rl(4) driver -> Poor performance X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2008 04:44:54 -0000 On Tue, Nov 18, 2008 at 05:28:13PM -0500, Gabriel Lavoie wrote: > Requested commands: > > Before a problem happens: > > [root@headless ~]# sysctl hw.busdma > hw.busdma.total_bpages: 8260 > hw.busdma.zone0.total_bpages: 8196 > hw.busdma.zone0.free_bpages: 8196 > hw.busdma.zone0.reserved_bpages: 0 > hw.busdma.zone0.active_bpages: 0 > hw.busdma.zone0.total_bounced: 0 > hw.busdma.zone0.total_deferred: 0 > hw.busdma.zone0.lowaddr: 0xffffffff > hw.busdma.zone0.alignment: 1 > hw.busdma.zone0.boundary: 0 > hw.busdma.zone1.total_bpages: 64 > hw.busdma.zone1.free_bpages: 64 > hw.busdma.zone1.reserved_bpages: 0 > hw.busdma.zone1.active_bpages: 0 > hw.busdma.zone1.total_bounced: 8200 > hw.busdma.zone1.total_deferred: 0 > hw.busdma.zone1.lowaddr: 0xffffffff > hw.busdma.zone1.alignment: 2 > hw.busdma.zone1.boundary: 65536 > > [root@headless ~]# netstat -nd -I rl0 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Coll Drop > rl0 1500 00:50:fc:c6:c8:d2 64336 0 60706 > 0 0 0 > rl0 1500 192.168.69.0/ 192.168.69.87 63398 - 59820 > - - - > > > I got a Samba copy error at this point: > > [root@headless /home/wildchild]# sysctl hw.busdma > hw.busdma.total_bpages: 8260 > hw.busdma.zone0.total_bpages: 8196 > hw.busdma.zone0.free_bpages: 8196 > hw.busdma.zone0.reserved_bpages: 0 > hw.busdma.zone0.active_bpages: 0 > hw.busdma.zone0.total_bounced: 0 > hw.busdma.zone0.total_deferred: 0 > hw.busdma.zone0.lowaddr: 0xffffffff > hw.busdma.zone0.alignment: 1 > hw.busdma.zone0.boundary: 0 > hw.busdma.zone1.total_bpages: 64 > hw.busdma.zone1.free_bpages: 64 > hw.busdma.zone1.reserved_bpages: 0 > hw.busdma.zone1.active_bpages: 0 > hw.busdma.zone1.total_bounced: 144539 > hw.busdma.zone1.total_deferred: 0 > hw.busdma.zone1.lowaddr: 0xffffffff > hw.busdma.zone1.alignment: 2 > hw.busdma.zone1.boundary: 65536 > [root@headless /home/wildchild]# netstat -nd -I rl0 > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Coll Drop > rl0 1500 00:50:fc:c6:c8:d2 6718354 0 4023956 > 0 0 0 > rl0 1500 192.168.69.0/ 192.168.69.87 6717392 - 4023051 > - - - > > Now the networking is really erratic. I have a huge slowdown with SSH and > I'm unable to copy files on the computer anymore via Samba. I must reboot to > get back the full performance. > I don't see possible errors in code. Did rl(4) show some messages on your console? Since there are no errors in netstat output I have no clue yet. Does interface up/down fix the poor performance after you've seen Samba copy error? -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 11:07:18 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2A441065674 for ; Mon, 24 Nov 2008 11:07:18 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E187E8FC30 for ; Mon, 24 Nov 2008 11:07:18 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAOB7Iv8019980 for ; Mon, 24 Nov 2008 11:07:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAOB7HiQ019976 for freebsd-net@FreeBSD.org; Mon, 24 Nov 2008 11:07:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Nov 2008 11:07:17 GMT Message-Id: <200811241107.mAOB7HiQ019976@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org 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, 24 Nov 2008 11:07:19 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/129074 net [ppp] [panic] kernel panic with pppoe_server o kern/129022 net [ath] ath cannot connect using WEP o kern/128917 net [wpi] [panic] if_wpi and wpa+tkip causing kernel panic o kern/128884 net [msk] if_msk page fault while in kernel mode o kern/128840 net [igb] page fault under load with igb/LRO o kern/128833 net [bge] Network packets corrupted when bge card is in 64 o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128598 net [bluetooth] WARNING: attempt to net_add_domain(bluetoo o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o conf/128334 net [request] use wpa_cli in the "WPA DHCP" situation o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o kern/128247 net [ip6] [panic] Fatal Trap 12 in ip6_forward = o kern/128181 net [fxp] panic in fxp_add_rfabuf o conf/128030 net [request] Isn't it time to enable IPsec in GENERIC? o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127928 net [tcp] [patch] TCP bandwidth gets squeezed every time t o kern/127834 net [ixgbe] [patch] wrong error counting o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net arp: Segmentation fault (core dumped) s kern/127587 net [bge] [request] if_bge(4) doesn't support BCM576X fami f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127102 net [wpi] Intel 3945ABG low throughput o kern/127057 net [udp] Unable to send UDP packet via IPv6 socket to IPv o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126984 net [carp][patch] add carp userland notifications via devc o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126924 net [an] [patch] printf -> device_printf and simplify prob o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and f kern/126564 net [ath] doesn't work with my PCI-E X1 wireless network a o kern/126561 net [nlm] [patch] NLM (rpclockd) RPC UNLOCK failure (stall o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126469 net [fxp] [panic] fxp(4) related kernel panic o kern/126339 net [ipw] ipw driver drops the connection o kern/126214 net [ath] txpower problem with Atheros wifi card o kern/126075 net [in] Network: internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre f kern/125195 net [fxp] fxp(4) driver failed to initialize device Intel o kern/125079 net [ppp] host routes added by ppp with gateway flag (regr o kern/124904 net [fxp] EEPROM corruption with Compaq NC3163 NIC o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 net [ieee80211] net80211 discards power-save queue packets o kern/124609 net [ipsec] [panic] ipsec 'remainder too big' panic with p o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o kern/123892 net [tap] [patch] No buffer space available o kern/123881 net [tcp] Turning on TCP blackholing causes slow localhost o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123200 net [netgraph] Server failure due to netgraph mpd and dhcp f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/123066 net [ipsec] [panic] kernel trap with ipsec o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [multicast] FreeBSD 7 multicast routing problem p kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix o kern/122743 net [panic] vm_page_unwire: invalid wire count: 0 o kern/122697 net [ath] Atheros card is not well supported o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122427 net [apm] [panic] apm and mDNSResponder cause panic during o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122195 net [ed] Alignment problems in if_ed o kern/122068 net [ppp] ppp can not set the correct interface with pptpd o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/121983 net [fxp] fxp0 MBUF and PAE o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] LOR icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/120966 net [rum] kernel panic with if_rum and WPA encryption p docs/120945 net [PATCH] ip6(4) man page lacks documentation for TCLASS o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119361 net [bge] bge(4) transmit performance problem o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116328 net [bge]: Solid hang with bge interface o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/92090 net [bge] bge0: watchdog timeout -- resetting s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 s kern/60293 net FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [PATCH] for static ARP tables in rc.network 196 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 17:21:48 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EF601065674; Mon, 24 Nov 2008 17:21:48 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 592578FC1F; Mon, 24 Nov 2008 17:21:48 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAOHLmYb018750; Mon, 24 Nov 2008 17:21:48 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAOHLmYD018746; Mon, 24 Nov 2008 17:21:48 GMT (envelope-from remko) Date: Mon, 24 Nov 2008 17:21:48 GMT Message-Id: <200811241721.mAOHLmYD018746@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: i386/129135: vge driver on a VIA mini-ITX not 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: Mon, 24 Nov 2008 17:21:48 -0000 Synopsis: vge driver on a VIA mini-ITX not working Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Mon Nov 24 17:21:47 UTC 2008 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=129135 From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 19:50:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43E69106564A for ; Mon, 24 Nov 2008 19:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 35EDC8FC14 for ; Mon, 24 Nov 2008 19:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAOJo4kx024914 for ; Mon, 24 Nov 2008 19:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAOJo4hF024913; Mon, 24 Nov 2008 19:50:04 GMT (envelope-from gnats) Date: Mon, 24 Nov 2008 19:50:04 GMT Message-Id: <200811241950.mAOJo4hF024913@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "David Christensen" Cc: Subject: RE: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Christensen List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2008 19:50:04 -0000 The following reply was made to PR kern/128833; it has been noted by GNATS. From: "David Christensen" To: "Marius Strobl" Cc: "bug-followup@FreeBSD.org" Subject: RE: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot Date: Mon, 24 Nov 2008 11:28:10 -0800 > > There is a documented errata for the 5701 A3 where a 64bit DMA > > read can be terminated early by the bridge and then completed > > later as a 32bit access, causing corruption on the 5701. The > > errata states this type of behavior is rare in bridges and that > > the workaround is to force 32bit operation (set bit 15 of register > > 0x6800). It's not clear whether this errata is occurring without > > seeing a but trace but it certainly sounds right. The only > > question would be knowing "when" to force 32bit operation. Should > > it be done in all cases or only for this bridge? > > >=20 > David, >=20 > could it be that bug doesn't only affect 5701 A3 but also > B3 (i.e. chipid 0x01050000) as in this case or even all 5701 > revisions?=20 I checked the assembly instructions for the 5701 and even though the ASIC ID decodes as B5, the revision of the chip is actually A3. (You should be able to verify this as the silkscreen on the part should show "P13".) Unfortunately the "friendly" revision of the chip doesn't match the "ASIC" revision of the chip for the 5701 and the errata references the "friendly" name. The result is that the part you know as B5 is affected by this errata. Other versions of the chip (A2 which you know as B2 and A1 which you=20 know as B1) are not subject to this errata. > How does the problem you describe relate to the > 5701 PCI-X issue, which we align the RX buffer differently > for as a workaround, would that problem also be avoided > by limiting 5701 to 32-bit operations? Or is the A3-errata > you described an entirely different issue and limited to 5701 > in a 64-bit non-PCI-X slot, or would 5701 in a PCI-X slot > even require both workarounds? Which PCI-X issue are you referring to? Can you point me to the line number on http://fxr.watson.org/fxr/source/dev/bge/if_bge.c? Dave From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 21:46:15 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68AF41065674; Mon, 24 Nov 2008 21:46:15 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0F88FC1A; Mon, 24 Nov 2008 21:46:15 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.11.16.99] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 24 Nov 2008 13:31:59 -0800 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id DF5CC2B1; Mon, 24 Nov 2008 13:31:58 -0800 (PST) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.11.18.52]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id CB3402B0; Mon, 24 Nov 2008 13:31:58 -0800 (PST) Received: from mail-irva-13.broadcom.com (mail-irva-13.broadcom.com [10.11.16.103]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id HIC95391; Mon, 24 Nov 2008 13:31:57 -0800 (PST) Received: from IRVEXCHHUB01.corp.ad.broadcom.com (irvexchhub01 [10.9.200.131]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id AB9AD74CFE; Mon, 24 Nov 2008 13:31:57 -0800 (PST) Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Mon, 24 Nov 2008 13:31:57 -0800 From: "David Christensen" To: "freebsd-drivers@freebsd.org" , "freebsd-net@FreeBSD.org" Date: Mon, 24 Nov 2008 13:33:50 -0800 Thread-Topic: Gathering Hardware State During a Driver Initiated Kernel Panic Thread-Index: AclOfE8KvODwR+q4Q0S7pWqp+3T1AA== Message-ID: <5D267A3F22FD854F8F48B3D2B52381933940B2DEFE@IRVEXCHCCR01.corp.ad.broadcom.com> Accept-Language: en-US Content-Language: en-US acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 6535C2C537G20288383-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: Subject: Gathering Hardware State During a Driver Initiated Kernel Panic 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, 24 Nov 2008 21:46:15 -0000 Is there a method or callback in FreeBSD where a driver can=20 be notified that it has caused a kernel panic in order to=20 generate a dump of internal hardware state information? I've written a sysctl call for manual intervention and can handle some "expected" hardware events completely in the driver but I don't know of a way to get control again in cases where the=20 driver wasn't expecting a failure. Dave From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 21:50:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DE731065670 for ; Mon, 24 Nov 2008 21:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 304BC8FC08 for ; Mon, 24 Nov 2008 21:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAOLo4t8015021 for ; Mon, 24 Nov 2008 21:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAOLo4LZ015020; Mon, 24 Nov 2008 21:50:04 GMT (envelope-from gnats) Date: Mon, 24 Nov 2008 21:50:04 GMT Message-Id: <200811242150.mAOLo4LZ015020@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Marius Strobl Cc: Subject: Re: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2008 21:50:04 -0000 The following reply was made to PR kern/128833; it has been noted by GNATS. From: Marius Strobl To: David Christensen Cc: "bug-followup@FreeBSD.org" Subject: Re: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot Date: Mon, 24 Nov 2008 22:40:36 +0100 On Mon, Nov 24, 2008 at 11:28:10AM -0800, David Christensen wrote: > > > There is a documented errata for the 5701 A3 where a 64bit DMA > > > read can be terminated early by the bridge and then completed > > > later as a 32bit access, causing corruption on the 5701. The > > > errata states this type of behavior is rare in bridges and that > > > the workaround is to force 32bit operation (set bit 15 of register > > > 0x6800). It's not clear whether this errata is occurring without > > > seeing a but trace but it certainly sounds right. The only > > > question would be knowing "when" to force 32bit operation. Should > > > it be done in all cases or only for this bridge? > > > > > > > David, > > > > could it be that bug doesn't only affect 5701 A3 but also > > B3 (i.e. chipid 0x01050000) as in this case or even all 5701 > > revisions? > > I checked the assembly instructions for the 5701 and even though > the ASIC ID decodes as B5, the revision of the chip is actually > A3. (You should be able to verify this as the silkscreen on the > part should show "P13".) Unfortunately the "friendly" revision > of the chip doesn't match the "ASIC" revision of the chip for the > 5701 and the errata references the "friendly" name. The result > is that the part you know as B5 is affected by this errata. Other > versions of the chip (A2 which you know as B2 and A1 which you > know as B1) are not subject to this errata. Ah, this explains it. Thanks for looking it up! > > > How does the problem you describe relate to the > > 5701 PCI-X issue, which we align the RX buffer differently > > for as a workaround, would that problem also be avoided > > by limiting 5701 to 32-bit operations? Or is the A3-errata > > you described an entirely different issue and limited to 5701 > > in a 64-bit non-PCI-X slot, or would 5701 in a PCI-X slot > > even require both workarounds? > > Which PCI-X issue are you referring to? Can you point me to > the line number on http://fxr.watson.org/fxr/source/dev/bge/if_bge.c? > I was refering to BGE_FLAG_RX_ALIGNBUG, the lines dealing with it are 874-875, 933-934, 2698-2708 and 3112-3122. The Linux tg3 driver does pretty much the same via rx_offset. Marius From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 22:14:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 105E71065672 for ; Mon, 24 Nov 2008 22:14:18 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id D72798FC1B for ; Mon, 24 Nov 2008 22:14:17 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id mAOLuMgP049253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Nov 2008 13:56:22 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <492B2306.60404@freebsd.org> Date: Mon, 24 Nov 2008 13:56:22 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: David Christensen References: <5D267A3F22FD854F8F48B3D2B52381933940B2DEFE@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933940B2DEFE@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: "freebsd-net@FreeBSD.org" , "freebsd-drivers@freebsd.org" Subject: Re: Gathering Hardware State During a Driver Initiated Kernel Panic 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, 24 Nov 2008 22:14:18 -0000 David Christensen wrote: > Is there a method or callback in FreeBSD where a driver can > be notified that it has caused a kernel panic in order to > generate a dump of internal hardware state information? I've > written a sysctl call for manual intervention and can handle > some "expected" hardware events completely in the driver but > I don't know of a way to get control again in cases where the > driver wasn't expecting a failure. > Not sure how one can deduce a driver is at fault but you might define a ddb command for the driver and invoke that on panic using the ddb script mechanisms (see ddb(4)). Sam From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 22:40:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 400C31065670 for ; Mon, 24 Nov 2008 22:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 326868FC0A for ; Mon, 24 Nov 2008 22:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAOMe4F3052673 for ; Mon, 24 Nov 2008 22:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAOMe4kr052672; Mon, 24 Nov 2008 22:40:04 GMT (envelope-from gnats) Date: Mon, 24 Nov 2008 22:40:04 GMT Message-Id: <200811242240.mAOMe4kr052672@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "David Christensen" Cc: Subject: RE: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Christensen List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2008 22:40:04 -0000 The following reply was made to PR kern/128833; it has been noted by GNATS. From: "David Christensen" To: "Marius Strobl" Cc: "bug-followup@FreeBSD.org" Subject: RE: kern/128833: [bge] Network packets corrupted when bge card is in 64-bit PCI slot Date: Mon, 24 Nov 2008 14:38:35 -0800 > > > How does the problem you describe relate to the > > > 5701 PCI-X issue, which we align the RX buffer differently > > > for as a workaround, would that problem also be avoided > > > by limiting 5701 to 32-bit operations? Or is the A3-errata > > > you described an entirely different issue and limited to 5701 > > > in a 64-bit non-PCI-X slot, or would 5701 in a PCI-X slot > > > even require both workarounds? > > > > Which PCI-X issue are you referring to? Can you point me to > > the line number on http://fxr.watson.org/fxr/source/dev/bge/if_bge.c? > > >=20 > I was refering to BGE_FLAG_RX_ALIGNBUG, the lines dealing with it > are 874-875, 933-934, 2698-2708 and 3112-3122. The Linux tg3 > driver does pretty much the same via rx_offset. It's a different problem. The RX_ALIGNBUG is described in the errata as follows: "Description: In PCI-X mode, on rare instances, the DMA write engine=20 can incorrectly DMA duplicate data to the host if the first word of=20 the data being transferred is to a non-zero-offset address (offset=20 from the 8-byte boundary). Workaround: Align buffers to zero offset in the driver." I suppose you could force PCI mode for this problem too though at the expense of possible reduced performance. Dave From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 13:28:59 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 998871065675 for ; Tue, 25 Nov 2008 13:28:59 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id B51BF8FC18 for ; Tue, 25 Nov 2008 13:28:58 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 57119 invoked from network); 25 Nov 2008 13:02:38 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 25 Nov 2008 13:02:38 -0000 Received: (qmail 15696 invoked by uid 907); 25 Nov 2008 13:02:15 -0000 Received: from midgard.transactionware.com (HELO STUDYPC) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Wed, 26 Nov 2008 00:02:15 +1100 From: "Jan Mikkelsen" To: Date: Wed, 26 Nov 2008 00:02:15 +1100 Message-ID: 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.6838 Importance: Normal Thread-Index: AclO/goGdpiqsKM6SF+gYAp9rnGDxQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Subject: [em] 7.1-PRE, one em port works, one fails, no problem on 6.3-p1 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, 25 Nov 2008 13:28:59 -0000 Hi, On a machine with a Supermicro X7DB8 board I get this error on startup: em1: port 0x3020-0x303f mem = 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 em1: Using MSI interrupt em1: Hardware Initialization Failed em1: Unable to initialize the hardware device_attach: em1 attach returned 5 There is no management card in this particular machine, and em0 on the = same motherboard is fine. I can see a few similar problems in the archives, = but I don't see a definitive solution. The same machine runs fine with = 6.3-p1. Dmesg below. Any suggestions? Thanks, Jan Mikkelsen Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Tue Nov 25 10:07:25 EST 2008 =20 root@dm.transactionware.com:/home/janm/p4/freebsd-image-std-2008.2/work/b= ase -freebsd/home/janm/p4/freebsd-image-std-2008.2/FreeBSD/src/sys/TW-SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz (2333.35-MHz = K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x6f6 Stepping =3D 6 =20 Features=3D0xbfebfbff =20 Features2=3D0x4e3bd AMD Features=3D0x20100800 AMD Features2=3D0x1 Cores per package: 2 usable memory =3D 4280651776 (4082 MB) avail memory =3D 4117843968 (3927 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, = RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 ahd0: port 0x2400-0x24ff,0x2000-0x20ff mem 0xd8500000-0xd8501fff irq 16 at device = 2.0 on pci4 ahd0: [ITHREAD] aic7902: Ultra320 Wide Channel A, SCSI Id=3D7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0x2c00-0x2cff,0x2800-0x28ff mem 0xd8502000-0xd8503fff irq 17 at device = 2.1 on pci4 ahd1: [ITHREAD] aic7902: Ultra320 Wide Channel B, SCSI Id=3D7, PCI-X 67-100Mhz, 512 SCBs pcib5: at device 0.2 on pci3 pci5: on pcib5 bge0: mem 0xd8600000-0xd860ffff irq 16 at device 1.0 on pci5 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:40:f4:66:b1:56 bge0: [ITHREAD] pcib6: irq 18 at device 2.0 on pci2 pci6: on pcib6 em0: port 0x3000-0x301f mem 0xd8400000-0xd841ffff irq 18 at device 0.0 on pci6 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:30:48:31:67:86 em1: port 0x3020-0x303f mem 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 em1: Using MSI interrupt em1: Hardware Initialization Failed em1: Unable to initialize the hardware device_attach: em1 attach returned 5 pcib7: at device 0.3 on pci1 pci7: on pcib7 pcib8: at device 4.0 on pci0 pci8: on pcib8 pcib9: at device 6.0 on pci0 pci9: on pcib9 pcib10: at device 0.0 on pci9 pci10: on pcib10 arcmsr0: mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq 16 at device 14.0 = on pci10 ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07=20 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.42 2006-10-13=20 arcmsr0: [ITHREAD] pcib11: at device 0.2 on pci9 pci11: on pcib11 pcib12: irq 17 at device 28.0 on pci0 pci12: on pcib12 uhci0: port = 0x1800-0x181f irq 17 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port = 0x1820-0x183f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port = 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xd8c00000-0xd8c003ff irq = 17 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcib13: at device 30.0 on pci0 pci13: on pcib13 vgapci0: port 0x4000-0x40ff mem 0xd0000000-0xd7ffffff,0xd8800000-0xd880ffff irq 18 at device 1.0 on = pci13 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on = acpi0 fdc0: [FILTER] ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 728072806000728 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 728072806000728 device_attach: est1 attach returned 6 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 728072806000728 device_attach: est2 attach returned 6 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 728072806000728 device_attach: est3 attach returned 6 p4tcc3: on cpu3 orm0: at iomem 0xc0000-0xcafff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA66 Waiting 5 seconds for SCSI devices to settle (probe46:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step da0 at arcmsr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device=20 da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) da0: 77247MB (158201856 512 byte sectors: 255H 63S/T 9847C) da1 at arcmsr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-5 device=20 da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) da1: 953673MB (1953122304 512 byte sectors: 255H 63S/T 121576C) da2 at arcmsr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-5 device=20 da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) da2: 800131MB (1638669312 512 byte sectors: 255H 63S/T 102002C) sa0 at ahd1 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device=20 sa0: 10.000MB/s transfers (10.000MHz, offset 15) SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/da0s1a This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ WARNING: ZFS is considered to be an experimental feature in FreeBSD. ZFS filesystem version 6 ZFS storage pool version 6 em0: link state changed to UP bge0: link state changed to UP From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 13:42:42 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B3EC1065672 for ; Tue, 25 Nov 2008 13:42:42 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 90D2B8FC37 for ; Tue, 25 Nov 2008 13:42:41 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id mAPDgd2w018301; Tue, 25 Nov 2008 20:42:39 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id mAPDgdY1018299; Tue, 25 Nov 2008 20:42:39 +0700 (KRAT) (envelope-from eugen) Date: Tue, 25 Nov 2008 20:42:39 +0700 From: Eugene Grosbein To: net@freebsd.org Message-ID: <20081125134239.GA17138@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: ipfw@freebsd.org Subject: m_tag_find() overhead 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, 25 Nov 2008 13:42:42 -0000 Hi! I wonder if one more call to m_tag_find() for every outgoing packet would be expensive. For many years conventional way to implement PBR was: use 'ipfw fwd'. Currently 'ipfw add fwd ... in' marks a packet with PACKET_TAG_IPFORWARD. Such forwarding changes packet's outgoing interface generally but none in the kernel reflect this in packet's metadata and packets are passed by ip_output() to PFIL hooks with wrong outgoing interface name ( details and How-To-Repeat may be found here: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/129036 ) I've patched src/sys/netinet/ip_output.c to fix this problem by extra check for PACKET_TAG_IPFORWARD and update of route if necessary. This adds a call to m_tag_find() for every outgoing packet if packet filtering is enabled and kernel has options IPFIREWALL_FORWARD. Please review. It works for my test lab but I'm not sure if that's correct: should a call to rtalloc_ign() be accomplished with some resource freeing call? And what's the meaning of RTF_CLONING second argument of rtalloc_ign? --- ip_output.c.orig 2008-11-25 14:21:26.000000000 +0700 +++ ip_output.c 2008-11-25 18:29:32.000000000 +0700 @@ -195,6 +195,20 @@ ro->ro_rt = (struct rtentry *)0; } #ifdef IPFIREWALL_FORWARD + /* + * Check if packet has changed next-hop in ip_input() + * If so, update route so pfil hooks get it right + */ + if ((inet_pfil_hook.ph_busy_count != -1) && + (fwd_tag = m_tag_find(m, PACKET_TAG_IPFORWARD, NULL))) { + bzero(&iproute, sizeof(iproute)); + ro = &iproute; + bcopy((fwd_tag+1), &ro->ro_dst, sizeof(struct sockaddr_in)); + m_tag_delete(m, fwd_tag); + rtalloc_ign(ro, RTF_CLONING); + dst = (struct sockaddr_in *)&ro->ro_dst; + } + if (ro->ro_rt == NULL && fwd_tag == NULL) { #else if (ro->ro_rt == NULL) { Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 13:50:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E8431065672 for ; Tue, 25 Nov 2008 13:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 48DF28FC19 for ; Tue, 25 Nov 2008 13:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAPDo4P7073974 for ; Tue, 25 Nov 2008 13:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAPDo4Wq073967; Tue, 25 Nov 2008 13:50:04 GMT (envelope-from gnats) Date: Tue, 25 Nov 2008 13:50:04 GMT Message-Id: <200811251350.mAPDo4Wq073967@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Mam Ruoc Cc: Subject: Re: kern/129135: vge driver on a VIA mini-ITX not working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mam Ruoc List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2008 13:50:04 -0000 The following reply was made to PR kern/129135; it has been noted by GNATS. From: Mam Ruoc To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/129135: vge driver on a VIA mini-ITX not working Date: Tue, 25 Nov 2008 14:14:02 +0100 Seems like I'm not the only one that have this problem in 7.0: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/106851 From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 17:31:47 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC80D1065672 for ; Tue, 25 Nov 2008 17:31:46 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by mx1.freebsd.org (Postfix) with ESMTP id 175708FC23 for ; Tue, 25 Nov 2008 17:31:45 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so38422fkk.11 for ; Tue, 25 Nov 2008 09:31:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=AU44b414ih+ODKo2I5+RxhphniJsdMsGWoHaUdd/zW4=; b=l5VmN502sY8qzrS/SeuMUrhFEUtfBh20C6NV/OOXhyMgGzIXLMOpTZvRcxZZVaPa0m FJ9n3qu0l/vliDE+z2wU5aWJaGm7wsPPO63U9MfuVN+qDLgUU8Yv8nuCYPeuL66FXYmN 7omduz8Px7DoIJSNnm+0hBQLnVtGflUt6Nyjs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=NC0oaPy3R9L3pFD9ieCV/BO+4rJIXSXVc/6vTcHLp0hWoOu4GW9FomNa/eWJT43ogN 2iSFut6Wq+HOBRfoDY8WIqHO7F8Qt+MZrQihapP0JI6z1iXeaiUtcql+AaSlFN2FPPFp WBzkbFZYrGVttDWApdwDpN/ReWlHhF23gWbvg= Received: by 10.181.57.7 with SMTP id j7mr1198254bkk.115.1227634304716; Tue, 25 Nov 2008 09:31:44 -0800 (PST) Received: by 10.181.25.9 with HTTP; Tue, 25 Nov 2008 09:31:44 -0800 (PST) Message-ID: <2a41acea0811250931x53e545b8qd392c56c7705104d@mail.gmail.com> Date: Tue, 25 Nov 2008 09:31:44 -0800 From: "Jack Vogel" To: "Jan Mikkelsen" In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: [em] 7.1-PRE, one em port works, one fails, no problem on 6.3-p1 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, 25 Nov 2008 17:31:47 -0000 There is a fix for this, but have not been able to get it in yet :( Jack On Tue, Nov 25, 2008 at 5:02 AM, Jan Mikkelsen wrote: > Hi, > > On a machine with a Supermicro X7DB8 board I get this error on startup: > > em1: port 0x3020-0x303f mem > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > em1: Using MSI interrupt > em1: Hardware Initialization Failed > em1: Unable to initialize the hardware > device_attach: em1 attach returned 5 > > There is no management card in this particular machine, and em0 on the same > motherboard is fine. I can see a few similar problems in the archives, but > I don't see a definitive solution. The same machine runs fine with 6.3-p1. > > Dmesg below. > > Any suggestions? > > Thanks, > > Jan Mikkelsen > > Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-PRERELEASE #0: Tue Nov 25 10:07:25 EST 2008 > > root@dm.transactionware.com: > /home/janm/p4/freebsd-image-std-2008.2/work/base > -freebsd/home/janm/p4/freebsd-image-std-2008.2/FreeBSD/src/sys/TW-SMP > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz (2333.35-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > > Features=0xbfebfbff ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > Features2=0x4e3bd > > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 2 > usable memory = 4280651776 (4082 MB) > avail memory = 4117843968 (3927 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pcib2: irq 16 at device 0.0 on pci1 > pci2: on pcib2 > pcib3: irq 16 at device 0.0 on pci2 > pci3: on pcib3 > pcib4: at device 0.0 on pci3 > pci4: on pcib4 > ahd0: port > 0x2400-0x24ff,0x2000-0x20ff mem 0xd8500000-0xd8501fff irq 16 at device 2.0 > on pci4 > ahd0: [ITHREAD] > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > ahd1: port > 0x2c00-0x2cff,0x2800-0x28ff mem 0xd8502000-0xd8503fff irq 17 at device 2.1 > on pci4 > ahd1: [ITHREAD] > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > pcib5: at device 0.2 on pci3 > pci5: on pcib5 > bge0: mem > 0xd8600000-0xd860ffff irq 16 at device 1.0 on pci5 > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > bge0: Ethernet address: 00:40:f4:66:b1:56 > bge0: [ITHREAD] > pcib6: irq 18 at device 2.0 on pci2 > pci6: on pcib6 > em0: port 0x3000-0x301f mem > 0xd8400000-0xd841ffff irq 18 at device 0.0 on pci6 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:30:48:31:67:86 > em1: port 0x3020-0x303f mem > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > em1: Using MSI interrupt > em1: Hardware Initialization Failed > em1: Unable to initialize the hardware > device_attach: em1 attach returned 5 > pcib7: at device 0.3 on pci1 > pci7: on pcib7 > pcib8: at device 4.0 on pci0 > pci8: on pcib8 > pcib9: at device 6.0 on pci0 > pci9: on pcib9 > pcib10: at device 0.0 on pci9 > pci10: on pcib10 > arcmsr0: > mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq 16 at device 14.0 on > pci10 > ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 > ARECA RAID ADAPTER0: FIRMWARE VERSION V1.42 2006-10-13 > arcmsr0: [ITHREAD] > pcib11: at device 0.2 on pci9 > pci11: on pcib11 > pcib12: irq 17 at device 28.0 on pci0 > pci12: on pcib12 > uhci0: port 0x1800-0x181f > irq 17 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x1820-0x183f > irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x1840-0x185f > irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xd8c00000-0xd8c003ff irq 17 > at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pcib13: at device 30.0 on pci0 > pci13: on pcib13 > vgapci0: port 0x4000-0x40ff mem > 0xd0000000-0xd7ffffff,0xd8800000-0xd880ffff irq 18 at device 1.0 on pci13 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FILTER] > ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > cpu0: on acpi0 > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est0 attach returned 6 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est1 attach returned 6 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est2 attach returned 6 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est3 attach returned 6 > p4tcc3: on cpu3 > orm0: at iomem 0xc0000-0xcafff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: DVDR at ata0-master UDMA66 > Waiting 5 seconds for SCSI devices to settle > (probe46:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step > da0 at arcmsr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da0: 77247MB (158201856 512 byte sectors: 255H 63S/T 9847C) > da1 at arcmsr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-5 device > da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da1: 953673MB (1953122304 512 byte sectors: 255H 63S/T 121576C) > da2 at arcmsr0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-5 device > da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da2: 800131MB (1638669312 512 byte sectors: 255H 63S/T 102002C) > sa0 at ahd1 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 > device > sa0: 10.000MB/s transfers (10.000MHz, offset 15) > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > Trying to mount root from ufs:/dev/da0s1a > This module (opensolaris) contains code covered by the > Common Development and Distribution License (CDDL) > see http://opensolaris.org/os/licensing/opensolaris_license/ > WARNING: ZFS is considered to be an experimental feature in FreeBSD. > ZFS filesystem version 6 > ZFS storage pool version 6 > em0: link state changed to UP > bge0: link state changed to UP > > _______________________________________________ > 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 Tue Nov 25 19:50:54 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FDF1106567B for ; Tue, 25 Nov 2008 19:50:54 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 2CD8B8FC26 for ; Tue, 25 Nov 2008 19:50:52 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 76857 invoked from network); 25 Nov 2008 19:51:13 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 25 Nov 2008 19:51:13 -0000 Received: (qmail 38346 invoked by uid 907); 25 Nov 2008 19:50:51 -0000 Received: from midgard.transactionware.com (HELO STUDYPC) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Wed, 26 Nov 2008 06:50:51 +1100 From: "Jan Mikkelsen" To: "'Jack Vogel'" Date: Wed, 26 Nov 2008 06:50:47 +1100 Message-ID: <60C2C2D3A191401FAF7897C07C6C51E8@STUDYPC> 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.6838 In-Reply-To: <2a41acea0811250931x53e545b8qd392c56c7705104d@mail.gmail.com> Importance: Normal Thread-Index: AclPI72WNLS3KUYdRqyIhp3LLddnyAAExyAg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: freebsd-net@freebsd.org Subject: RE: [em] 7.1-PRE, one em port works, one fails, no problem on 6.3-p1 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, 25 Nov 2008 19:50:54 -0000 Hi Jack, Thanks for the reply. Is there a workaround, or something I can merge myself? If not, any = idea on when it might make it in? Thanks, Jan > -----Original Message----- > From: Jack Vogel [mailto:jfvogel@gmail.com]=20 > Sent: Wednesday, 26 November 2008 4:32 AM > To: Jan Mikkelsen > Cc: freebsd-net@freebsd.org > Subject: Re: [em] 7.1-PRE, one em port works, one fails, no=20 > problem on 6.3-p1 >=20 >=20 > There is a fix for this, but have not been able to get it in yet :( >=20 > Jack >=20 >=20 >=20 > On Tue, Nov 25, 2008 at 5:02 AM, Jan Mikkelsen=20 > wrote: >=20 >=20 > Hi, > =09 > On a machine with a Supermicro X7DB8 board I get this=20 > error on startup: > =09 > em1: port=20 > 0x3020-0x303f mem > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > em1: Using MSI interrupt > em1: Hardware Initialization Failed > em1: Unable to initialize the hardware > device_attach: em1 attach returned 5 > =09 > There is no management card in this particular machine,=20 > and em0 on the same > motherboard is fine. I can see a few similar problems=20 > in the archives, but > I don't see a definitive solution. The same machine=20 > runs fine with 6.3-p1. > =09 > Dmesg below. > =09 > Any suggestions? > =09 > Thanks, > =09 > Jan Mikkelsen > =09 > Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991,=20 > 1992, 1993, 1994 > The Regents of the University of California. All=20 > rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-PRERELEASE #0: Tue Nov 25 10:07:25 EST 2008 > =09 > =09 > root@dm.transactionware.com:/home/janm/p4/freebsd-image-std-20 > 08.2/work/base > =09 > -freebsd/home/janm/p4/freebsd-image-std-2008.2/FreeBSD/src/sys/TW-SMP > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz=20 > (2333.35-MHz K8-class > CPU) > Origin =3D "GenuineIntel" Id =3D 0x6f6 Stepping =3D 6 > =09 > =09 > Features=3D0xbfebfbff P,MTRR,PGE,MCA > =09 > ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > =09 > =09 > Features2=3D0x4e3bd ,xTPR,PDCM,DCA > > > AMD Features=3D0x20100800 > AMD Features2=3D0x1 > Cores per package: 2 > usable memory =3D 4280651776 (4082 MB) > avail memory =3D 4117843968 (3927 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111,=20 > RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port=20 > 0x1008-0x100b on acpi0 > acpi_hpet0: iomem=20 > 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pcib2: irq 16 at device 0.0 on pci1 > pci2: on pcib2 > pcib3: irq 16 at device 0.0 on pci2 > pci3: on pcib3 > pcib4: at device 0.0 on pci3 > pci4: on pcib4 > ahd0: port > 0x2400-0x24ff,0x2000-0x20ff mem 0xd8500000-0xd8501fff=20 > irq 16 at device 2.0 > on pci4 > ahd0: [ITHREAD] > aic7902: Ultra320 Wide Channel A, SCSI Id=3D7, PCI-X=20 > 67-100Mhz, 512 SCBs > ahd1: port > 0x2c00-0x2cff,0x2800-0x28ff mem 0xd8502000-0xd8503fff=20 > irq 17 at device 2.1 > on pci4 > ahd1: [ITHREAD] > aic7902: Ultra320 Wide Channel B, SCSI Id=3D7, PCI-X=20 > 67-100Mhz, 512 SCBs > pcib5: at device 0.2 on pci3 > pci5: on pcib5 > bge0: mem > 0xd8600000-0xd860ffff irq 16 at device 1.0 on pci5 > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX,=20 > 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > bge0: Ethernet address: 00:40:f4:66:b1:56 > bge0: [ITHREAD] > pcib6: irq 18 at device 2.0 on pci2 > pci6: on pcib6 > em0: port=20 > 0x3000-0x301f mem > 0xd8400000-0xd841ffff irq 18 at device 0.0 on pci6 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:30:48:31:67:86 > em1: port=20 > 0x3020-0x303f mem > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > em1: Using MSI interrupt > em1: Hardware Initialization Failed > em1: Unable to initialize the hardware > device_attach: em1 attach returned 5 > pcib7: at device 0.3 on pci1 > pci7: on pcib7 > pcib8: at device 4.0 on pci0 > pci8: on pcib8 > pcib9: at device 6.0 on pci0 > pci9: on pcib9 > pcib10: at device 0.0 on pci9 > pci10: on pcib10 > arcmsr0: (RAID6 capable) > > mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq=20 > 16 at device 14.0 on > pci10 > ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 > ARECA RAID ADAPTER0: FIRMWARE VERSION V1.42 2006-10-13 > arcmsr0: [ITHREAD] > pcib11: at device 0.2 on pci9 > pci11: on pcib11 > pcib12: irq 17 at device 28.0 on pci0 > pci12: on pcib12 > uhci0: USB-1> port 0x1800-0x181f > irq 17 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: addr 1> on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: USB-2> port 0x1820-0x183f > irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: addr 1> on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: USB-3> port 0x1840-0x185f > irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: addr 1> on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem=20 > 0xd8c00000-0xd8c003ff irq 17 > at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: addr 1> on usb3 > uhub3: 6 ports with 6 removable, self powered > pcib13: at device 30.0 on pci0 > pci13: on pcib13 > vgapci0: port 0x4000-0x40ff mem > 0xd0000000-0xd7ffffff,0xd8800000-0xd880ffff irq 18 at=20 > device 1.0 on pci13 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at=20 > device 31.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x60,0x64=20 > irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq=20 > 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq=20 > 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > fdc0: port 0x3f0-0x3f5,0x3f7=20 > irq 6 drq 2 on acpi0 > fdc0: [FILTER] > ppc0: port 0x378-0x37f,0x778-0x77f irq=20 > 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > cpu0: on acpi0 > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est0 attach returned 6 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est1 attach returned 6 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est2 attach returned 6 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 728072806000728 > device_attach: est3 attach returned 6 > p4tcc3: on cpu3 > orm0: at iomem 0xc0000-0xcafff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem=20 > 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: DVDR at ata0-master UDMA66 > Waiting 5 seconds for SCSI devices to settle > (probe46:arcmsr0:0:16:0): inquiry data fails comparison=20 > at DV1 step > da0 at arcmsr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access=20 > SCSI-5 device > da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da0: 77247MB (158201856 512 byte sectors: 255H 63S/T 9847C) > da1 at arcmsr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access=20 > SCSI-5 device > da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da1: 953673MB (1953122304 512 byte sectors: 255H 63S/T 121576C) > da2 at arcmsr0 bus 0 target 2 lun 0 > da2: Fixed Direct Access=20 > SCSI-5 device > da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da2: 800131MB (1638669312 512 byte sectors: 255H 63S/T 102002C) > sa0 at ahd1 bus 0 target 6 lun 0 > sa0: Removable=20 > Sequential Access SCSI-2 > device > sa0: 10.000MB/s transfers (10.000MHz, offset 15) > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > Trying to mount root from ufs:/dev/da0s1a > This module (opensolaris) contains code covered by the > Common Development and Distribution License (CDDL) > see http://opensolaris.org/os/licensing/opensolaris_license/ > WARNING: ZFS is considered to be an experimental=20 > feature in FreeBSD. > ZFS filesystem version 6 > ZFS storage pool version 6 > em0: link state changed to UP > bge0: link state changed to UP > =09 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to=20 > "freebsd-net-unsubscribe@freebsd.org" > =09 >=20 >=20 >=20 From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 23:41:30 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E4331065675 for ; Tue, 25 Nov 2008 23:41:30 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 358BF8FC1B for ; Tue, 25 Nov 2008 23:41:29 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so105022fgb.35 for ; Tue, 25 Nov 2008 15:41:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=1ne3+3ghrZpmVFSapNPB2zVfAp5pJRM9be+9PXrA8rs=; b=MKqiOg+Y468dtSwGKP49dNo/mbaVkw/ztCBbUTGDF70KbNiMREQV4mabTTZEKfaZv5 747ZE1jvQMaRsf0ddWooFtoZQB4yQaCDYc6wS0fm5nW11j7R3bShGo7kNt+uXKJk6rsQ Y8eXMmj8DRFnGLTfiJnZtldGpu5N+RShjVzD4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=wJ/7Ywp+FH6IF/Hz71jQcDK79xa/c/Qd8YV//cMRbI4Adf6QU/EHCwB6pTLB8Ameg+ PaGinCmwbzyW2qp8HYhvMt/OMkZFZsrmNCd/jNJjIBjOuGBHv+f+fnPu4t33+H/cca7E b0ha2GChp5+s3YagOsORQLqjmBsrUbBrlCQT4= Received: by 10.181.217.2 with SMTP id u2mr1709615bkq.153.1227656488203; Tue, 25 Nov 2008 15:41:28 -0800 (PST) Received: by 10.181.25.9 with HTTP; Tue, 25 Nov 2008 15:41:28 -0800 (PST) Message-ID: <2a41acea0811251541n53887005oabd7d2d96f346b6d@mail.gmail.com> Date: Tue, 25 Nov 2008 15:41:28 -0800 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: 7.1 RC E1000 fix testing 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, 25 Nov 2008 23:41:30 -0000 Anyone running 7.1 and using E1000 hardware that has the time, I would appreciate any testing you can do. This has an important fix for SuperMicro servers but any regression test of the code would be helpful. The email was getting rejected due to the tarball size, so contact me and I will send you the code directly. Jack From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 23:38:44 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DC70106564A for ; Tue, 25 Nov 2008 23:38:44 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 8382E8FC0A for ; Tue, 25 Nov 2008 23:38:42 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so104517fgb.35 for ; Tue, 25 Nov 2008 15:38:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=c1f3CMZoyROxjaWAvWd+6W3oiupdyUkZC+2juLHCoqA=; b=wlYPhkXHANK/db06/wgzACRpHTbTvoszMqXH6bcjeN1TVMXB6KIjosBpYIL0gn6yu7 6W9ixzgyDnvxB9hCrc/YQceF1WQFbBtU3lH0iG7sWvllmwTbs57X3CADDfaHjWt9fuyg 7atJAkhfWE4mJQuX9xuGswoACZiqTJZPb4+Bo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Ggkh/pfzuYGfi6ED8Tskqb+3Xl9s+4h68w+WJkSaX9aDc6CSsw0GZdNcH8bCPVEhjW bTK0RfuMKK0AbRHNIJtFQDHxkxwE2ESiGcJcvGKD3HEO5jzLu2HcRLkwCZC5+3dA7iBB 9+lWY7LldQ4LzJnWPe0sI8T042iVNx0aUopcg= Received: by 10.181.197.2 with SMTP id z2mr1717362bkp.100.1227656320654; Tue, 25 Nov 2008 15:38:40 -0800 (PST) Received: by 10.181.25.9 with HTTP; Tue, 25 Nov 2008 15:38:39 -0800 (PST) Message-ID: <2a41acea0811251538x6dbc8d5etcb114b99b784800a@mail.gmail.com> Date: Tue, 25 Nov 2008 15:38:39 -0800 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD stable" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_19936_21980209.1227656320636" X-Mailman-Approved-At: Wed, 26 Nov 2008 00:07:14 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: 7.1 RC E1000 fix 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, 25 Nov 2008 23:38:44 -0000 ------=_Part_19936_21980209.1227656320636 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Anyone running 7.1 and using E1000 hardware that has the time, I would appreciate any testing you can do. This has an important fix for SuperMicro servers but any regression test of the code would be helpful. Backup the contents of /usr/src/sys/dev/e1000 and then overwrite with this tarball. Send feedback to me, Jack ------=_Part_19936_21980209.1227656320636-- From owner-freebsd-net@FreeBSD.ORG Wed Nov 26 00:19:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD5B71065744; Wed, 26 Nov 2008 00:19:46 +0000 (UTC) (envelope-from prvs=121695da30=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 469958FC1E; Wed, 26 Nov 2008 00:19:46 +0000 (UTC) (envelope-from prvs=121695da30=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1227657779; x=1228262579; q=dns/txt; h=Received: Message-ID:From:To:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=rDAy2EIXEV+mYlt82OS/K hkK8ZDgh/IkqZwKRY9XhL4=; b=VkhUNN/hee6Lgqr0DQBWhSqsF4SlzVs6OPayK m/Le5F1huCE3wFr6y7/wnLd/nmYDXhc8E6LbmzpbTG6JgBrmJcv3kxhl0V9zmxOW LfIaidK5S3BzcKFtWzftnDUi2+PPDjYIvmwLAFH89TUHy3QFuTl03+62DyBhrYg1 NpXYeU= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50006592966.msg; Wed, 26 Nov 2008 00:02:57 +0000 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 213.123.247.160 X-Return-Path: prvs=121695da30=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <6D1A722EC3A74794A4DC82D8DC35F85B@multiplay.co.uk> From: "Steven Hartland" To: "Jack Vogel" , , "FreeBSD stable" References: <2a41acea0811251541n53887005oabd7d2d96f346b6d@mail.gmail.com> Date: Wed, 26 Nov 2008 00:02:51 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 26 Nov 2008 00:02:58 +0000 X-MDAV-Processed: mail1.multiplay.co.uk, Wed, 26 Nov 2008 00:02:59 +0000 Cc: Subject: Re: 7.1 RC E1000 fix testing 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, 26 Nov 2008 00:19:47 -0000 We run a large about of supermicro servers here and I've got two just about to be commissioned which I could use for testing. What sort of thing should we be looking for and what's the nature of the patch? Regards Steve ----- Original Message ----- From: "Jack Vogel" To: ; "FreeBSD stable" Sent: Tuesday, November 25, 2008 11:41 PM Subject: 7.1 RC E1000 fix testing > Anyone running 7.1 and using E1000 hardware that has the time, I would > appreciate > any testing you can do. This has an important fix for SuperMicro servers but > any > regression test of the code would be helpful. > > The email was getting rejected due to the tarball size, so contact me and I > will send > you the code directly. > > Jack > _______________________________________________ > 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" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Wed Nov 26 06:02:54 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1157106564A for ; Wed, 26 Nov 2008 06:02:54 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 8EC918FC08 for ; Wed, 26 Nov 2008 06:02:52 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 5026 invoked from network); 26 Nov 2008 06:03:12 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 26 Nov 2008 06:03:12 -0000 Received: (qmail 3258 invoked by uid 907); 26 Nov 2008 06:02:50 -0000 Received: from jmdesktop.transactionware.com (HELO [192.168.1.177]) (192.168.1.177) by midgard.transactionware.com (qpsmtpd/0.40) with ESMTP; Wed, 26 Nov 2008 17:02:50 +1100 Message-ID: <492CE68A.2070503@transactionware.com> Date: Wed, 26 Nov 2008 17:02:50 +1100 From: Jan Mikkelsen User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0811250931x53e545b8qd392c56c7705104d@mail.gmail.com> <60C2C2D3A191401FAF7897C07C6C51E8@STUDYPC> <2a41acea0811251429l1899a839p68abfaf02fb3f682@mail.gmail.com> In-Reply-To: <2a41acea0811251429l1899a839p68abfaf02fb3f682@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Paul Saab , "gnn@freebsd.org" Subject: Re: [em] 7.1-PRE, one em port works, one fails, no problem on 6.3-p1 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, 26 Nov 2008 06:02:54 -0000 Hi Jack, I've just run some simple tests with your second tar file, and seems to work fine. The error message on boot up is gone, and data can be transferred. I'll leave it running on this version and report any other issues I see. Thanks! Jan. Jack Vogel wrote: > I would appreciate any and all that can give this some quick test to do > so, this is what you > do: > 1) save the contents of /usr/src/sys/dev/e1000 > 2) then overwrite it with this tarball, due to the way the > drivers are > packaged this change effects igb and em > > I most need to know if it fixes your ESB2 problem, but sanity testing on > BOTH drivers > would be most appreciated. I would really like this checked into 7.1 ASAP. > > > On Tue, Nov 25, 2008 at 11:50 AM, Jan Mikkelsen > > wrote: > > Hi Jack, > > Thanks for the reply. > > Is there a workaround, or something I can merge myself? If not, any > idea on > when it might make it in? > > Thanks, > > Jan > > > -----Original Message----- > > From: Jack Vogel [mailto:jfvogel@gmail.com > ] > > Sent: Wednesday, 26 November 2008 4:32 AM > > To: Jan Mikkelsen > > Cc: freebsd-net@freebsd.org > > Subject: Re: [em] 7.1-PRE, one em port works, one fails, no > > problem on 6.3-p1 > > > > > > There is a fix for this, but have not been able to get it in yet :( > > > > Jack > > > > > > > > On Tue, Nov 25, 2008 at 5:02 AM, Jan Mikkelsen > > > wrote: > > > > > > Hi, > > > > On a machine with a Supermicro X7DB8 board I get this > > error on startup: > > > > em1: port > > 0x3020-0x303f mem > > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > > em1: Using MSI interrupt > > em1: Hardware Initialization Failed > > em1: Unable to initialize the hardware > > device_attach: em1 attach returned 5 > > > > There is no management card in this particular machine, > > and em0 on the same > > motherboard is fine. I can see a few similar problems > > in the archives, but > > I don't see a definitive solution. The same machine > > runs fine with 6.3-p1. > > > > Dmesg below. > > > > Any suggestions? > > > > Thanks, > > > > Jan Mikkelsen > > > > Copyright (c) 1992-2008 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, > > 1992, 1993, 1994 > > The Regents of the University of California. All > > rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 7.1-PRERELEASE #0: Tue Nov 25 10:07:25 EST 2008 > > > > > > root@dm.transactionware.com:/home/janm/p4/freebsd-image-std-20 > > 08.2/work/base > > > > -freebsd/home/janm/p4/freebsd-image-std-2008.2/FreeBSD/src/sys/TW-SMP > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz > > (2333.35-MHz K8-class > > CPU) > > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > > > > > Features=0xbfebfbff > P,MTRR,PGE,MCA > > > > ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > > > Features2=0x4e3bd > ,xTPR,PDCM,DCA > > > > > AMD Features=0x20100800 > > AMD Features2=0x1 > > Cores per package: 2 > > usable memory = 4280651776 (4082 MB) > > avail memory = 4117843968 (3927 MB) > > ACPI APIC Table: > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > cpu2 (AP): APIC ID: 6 > > cpu3 (AP): APIC ID: 7 > > ioapic0 irqs 0-23 on motherboard > > ioapic1 irqs 24-47 on motherboard > > kbd1 at kbdmux0 > > ath_hal: 0.9.20.3 (AR5210, AR5211, > AR5212, RF5111, > > RF5112, RF2413, RF5413) > > acpi0: on motherboard > > acpi0: [ITHREAD] > > acpi0: Power Button (fixed) > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > acpi_timer0: <24-bit timer at 3.579545MHz> port > > 0x1008-0x100b on acpi0 > > acpi_hpet0: iomem > > 0xfed00000-0xfed003ff on > > acpi0 > > Timecounter "HPET" frequency 14318180 Hz quality 900 > > pcib0: port 0xcf8-0xcff on acpi0 > > pci0: on pcib0 > > pcib1: at device 2.0 on pci0 > > pci1: on pcib1 > > pcib2: irq 16 at device 0.0 on pci1 > > pci2: on pcib2 > > pcib3: irq 16 at device 0.0 on pci2 > > pci3: on pcib3 > > pcib4: at device 0.0 on pci3 > > pci4: on pcib4 > > ahd0: port > > 0x2400-0x24ff,0x2000-0x20ff mem 0xd8500000-0xd8501fff > > irq 16 at device 2.0 > > on pci4 > > ahd0: [ITHREAD] > > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X > > 67-100Mhz, 512 SCBs > > ahd1: port > > 0x2c00-0x2cff,0x2800-0x28ff mem 0xd8502000-0xd8503fff > > irq 17 at device 2.1 > > on pci4 > > ahd1: [ITHREAD] > > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X > > 67-100Mhz, 512 SCBs > > pcib5: at device 0.2 on pci3 > > pci5: on pcib5 > > bge0: mem > > 0xd8600000-0xd860ffff irq 16 at device 1.0 on pci5 > > miibus0: on bge0 > > brgphy0: PHY 1 on miibus0 > > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, > > 100baseTX-FDX, 1000baseT, > > 1000baseT-FDX, auto > > bge0: Ethernet address: 00:40:f4:66:b1:56 > > bge0: [ITHREAD] > > pcib6: irq 18 at device 2.0 on pci2 > > pci6: on pcib6 > > em0: port > > 0x3000-0x301f mem > > 0xd8400000-0xd841ffff irq 18 at device 0.0 on pci6 > > em0: Using MSI interrupt > > em0: [FILTER] > > em0: Ethernet address: 00:30:48:31:67:86 > > em1: port > > 0x3020-0x303f mem > > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > > em1: Using MSI interrupt > > em1: Hardware Initialization Failed > > em1: Unable to initialize the hardware > > device_attach: em1 attach returned 5 > > pcib7: at device 0.3 on pci1 > > pci7: on pcib7 > > pcib8: at device 4.0 on pci0 > > pci8: on pcib8 > > pcib9: at device 6.0 on pci0 > > pci9: on pcib9 > > pcib10: at device 0.0 on pci9 > > pci10: on pcib10 > > arcmsr0: > (RAID6 capable) > > > mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq > > 16 at device 14.0 on > > pci10 > > ARECA RAID ADAPTER0: Driver Version 1.20.00.15 > 2007-10-07 > > ARECA RAID ADAPTER0: FIRMWARE VERSION V1.42 2006-10-13 > > arcmsr0: [ITHREAD] > > pcib11: at device 0.2 on pci9 > > pci11: on pcib11 > > pcib12: irq 17 at device 28.0 on pci0 > > pci12: on pcib12 > > uhci0: > USB-1> port 0x1800-0x181f > > irq 17 at device 29.0 on pci0 > > uhci0: [GIANT-LOCKED] > > uhci0: [ITHREAD] > > usb0: on > uhci0 > > usb0: USB revision 1.0 > > uhub0: > addr 1> on usb0 > > uhub0: 2 ports with 2 removable, self powered > > uhci1: > USB-2> port 0x1820-0x183f > > irq 19 at device 29.1 on pci0 > > uhci1: [GIANT-LOCKED] > > uhci1: [ITHREAD] > > usb1: on > uhci1 > > usb1: USB revision 1.0 > > uhub1: > addr 1> on usb1 > > uhub1: 2 ports with 2 removable, self powered > > uhci2: > USB-3> port 0x1840-0x185f > > irq 18 at device 29.2 on pci0 > > uhci2: [GIANT-LOCKED] > > uhci2: [ITHREAD] > > usb2: on > uhci2 > > usb2: USB revision 1.0 > > uhub2: > addr 1> on usb2 > > uhub2: 2 ports with 2 removable, self powered > > ehci0: mem > > 0xd8c00000-0xd8c003ff irq 17 > > at device 29.7 on pci0 > > ehci0: [GIANT-LOCKED] > > ehci0: [ITHREAD] > > usb3: EHCI version 1.0 > > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > > usb3: on ehci0 > > usb3: USB revision 2.0 > > uhub3: > addr 1> on usb3 > > uhub3: 6 ports with 6 removable, self powered > > pcib13: at device 30.0 on pci0 > > pci13: on pcib13 > > vgapci0: port 0x4000-0x40ff mem > > 0xd0000000-0xd7ffffff,0xd8800000-0xd880ffff irq 18 at > > device 1.0 on pci13 > > isab0: at device 31.0 on pci0 > > isa0: on isab0 > > atapci0: port > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at > > device 31.1 on pci0 > > ata0: on atapci0 > > ata0: [ITHREAD] > > pci0: at device 31.3 (no driver attached) > > acpi_button0: on acpi0 > > atkbdc0: port 0x60,0x64 > > irq 1 on acpi0 > > atkbd0: irq 1 on atkbdc0 > > kbd0 at atkbd0 > > atkbd0: [GIANT-LOCKED] > > atkbd0: [ITHREAD] > > psm0: irq 12 on atkbdc0 > > psm0: [GIANT-LOCKED] > > psm0: [ITHREAD] > > psm0: model Generic PS/2 mouse, device ID 0 > > sio0: configured irq 4 not in bitmap of probed irqs 0 > > sio0: port may not be enabled > > sio0: configured irq 4 not in bitmap of probed irqs 0 > > sio0: port may not be enabled > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq > > 4 flags 0x10 on > > acpi0 > > sio0: type 16550A > > sio0: [FILTER] > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > sio1: port may not be enabled > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > sio1: port may not be enabled > > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq > > 3 on acpi0 > > sio1: type 16550A > > sio1: [FILTER] > > fdc0: port 0x3f0-0x3f5,0x3f7 > > irq 6 drq 2 on acpi0 > > fdc0: [FILTER] > > ppc0: port 0x378-0x37f,0x778-0x77f irq > > 7 drq 3 on acpi0 > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > ppc0: FIFO with 16/16/9 bytes threshold > > ppbus0: on ppc0 > > ppbus0: [ITHREAD] > > plip0: on ppbus0 > > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > > lpt0: on ppbus0 > > lpt0: Interrupt-driven port > > ppi0: on ppbus0 > > ppc0: [GIANT-LOCKED] > > ppc0: [ITHREAD] > > cpu0: on acpi0 > > est0: on cpu0 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr 728072806000728 > > device_attach: est0 attach returned 6 > > p4tcc0: on cpu0 > > cpu1: on acpi0 > > est1: on cpu1 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr 728072806000728 > > device_attach: est1 attach returned 6 > > p4tcc1: on cpu1 > > cpu2: on acpi0 > > est2: on cpu2 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr 728072806000728 > > device_attach: est2 attach returned 6 > > p4tcc2: on cpu2 > > cpu3: on acpi0 > > est3: on cpu3 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr 728072806000728 > > device_attach: est3 attach returned 6 > > p4tcc3: on cpu3 > > orm0: at iomem 0xc0000-0xcafff on isa0 > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=0x300> > > vga0: at port 0x3c0-0x3df iomem > > 0xa0000-0xbffff on isa0 > > Timecounters tick every 1.000 msec > > acd0: DVDR at ata0-master UDMA66 > > Waiting 5 seconds for SCSI devices to settle > > (probe46:arcmsr0:0:16:0): inquiry data fails comparison > > at DV1 step > > da0 at arcmsr0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access > > SCSI-5 device > > da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > > da0: 77247MB (158201856 512 byte sectors: 255H 63S/T 9847C) > > da1 at arcmsr0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access > > SCSI-5 device > > da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > > da1: 953673MB (1953122304 512 byte sectors: 255H 63S/T 121576C) > > da2 at arcmsr0 bus 0 target 2 lun 0 > > da2: Fixed Direct Access > > SCSI-5 device > > da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > > da2: 800131MB (1638669312 512 byte sectors: 255H 63S/T 102002C) > > sa0 at ahd1 bus 0 target 6 lun 0 > > sa0: Removable > > Sequential Access SCSI-2 > > device > > sa0: 10.000MB/s transfers (10.000MHz, offset 15) > > SMP: AP CPU #1 Launched! > > SMP: AP CPU #2 Launched! > > SMP: AP CPU #3 Launched! > > Trying to mount root from ufs:/dev/da0s1a > > This module (opensolaris) contains code covered by the > > Common Development and Distribution License (CDDL) > > see http://opensolaris.org/os/licensing/opensolaris_license/ > > WARNING: ZFS is considered to be an experimental > > feature in FreeBSD. > > ZFS filesystem version 6 > > ZFS storage pool version 6 > > em0: link state changed to UP > > bge0: link state changed to UP > > > > _______________________________________________ > > 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 Nov 26 08:15:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27B641065670 for ; Wed, 26 Nov 2008 08:15:05 +0000 (UTC) (envelope-from cihangir@akademi.enderunix.org) Received: from istanbul.enderunix.org (freefall.marmara.edu.tr [193.140.143.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8CAC68FC21 for ; Wed, 26 Nov 2008 08:15:04 +0000 (UTC) (envelope-from cihangir@akademi.enderunix.org) Received: (qmail 74242 invoked by uid 89); 26 Nov 2008 07:48:19 -0000 Message-ID: <20081126074819.74241.qmail@istanbul.enderunix.org> From: "Cihangir Besiktas" To: freebsd-net@freebsd.org Date: Wed, 26 Nov 2008 09:48:19 +0200 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-9" Content-Transfer-Encoding: 8bit Subject: Measuring processes' bandwidth usage 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, 26 Nov 2008 08:15:05 -0000 Hi, I am planning to develop a project, and in this project, there must be a module that outputs all the processes' bandwidth usage. How can I handle a process' bandwidth usage? I am looking forward to your advices. Thanks. Cihangir Besiktas Эstanbul Technical University Computer Eng Student http://www.students.itu.edu.tr/~besiktas Enderunix SDT | Student Participant in Google Summer of Code 2008 http://www.enderunix.org | http://code.google.com/soc/2008/ From owner-freebsd-net@FreeBSD.ORG Wed Nov 26 13:41:10 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D1481065675 for ; Wed, 26 Nov 2008 13:41:10 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 0AA178FC1B for ; Wed, 26 Nov 2008 13:41:09 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so226080ywe.13 for ; Wed, 26 Nov 2008 05:41:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=kVqsja3uzsweZhZ2mScwiTxviPWBnMiJvwuXD+SfTns=; b=std3ggJpTQFbVe2K84m9NICoHVkv0MUi5oDWmESF/8GmEUafcn4S6lIJ1c1JHR45u+ UQAFTPb1LdBduxPhfSrnlKzErJ9Ld8SDoSr3yKtn7bx4Xj/T6Ow5LSMV8A5RuhlIx0Qe EkSgX5bwr4Rks3c9DblB7IigUdEaUz+7nLd4c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=v1dUWQHjWOmYrZCnmMos6mswzXg81jDLnQIBLPDQ0qprWMey/pgj0gRUlywIDPokY0 /8MxZptwsU5hjQ7rapgi5rFBkhDdSeOyS/ystgPvxM1MYDegiPrJO7Wc3p91OHNbyEr9 3uiBEpkdjIjsE1x1BI/25N+jtZ+B3w5CKuyeg= Received: by 10.150.97.19 with SMTP id u19mr8691ybb.174.1227706869673; Wed, 26 Nov 2008 05:41:09 -0800 (PST) Received: by 10.150.154.21 with HTTP; Wed, 26 Nov 2008 05:41:09 -0800 (PST) Message-ID: <20def4870811260541x2f9bb410o44152a406407686@mail.gmail.com> Date: Wed, 26 Nov 2008 15:41:09 +0200 From: "Yony Yossef" To: freebsd-net@freebsd.org In-Reply-To: <20def4870811260540x3d44a02bw43b6d18bc675de67@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20def4870811260540x3d44a02bw43b6d18bc675de67@mail.gmail.com> Subject: TSO on VLAN interface, FreeBSD 7 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, 26 Nov 2008 13:41:10 -0000 Hi All, When I create a VLAN interface it does not inherit the parent interface capabilities. Is there a way to enable TSO (as other capabilities) on VLAN interfaces? Thanks, Yony From owner-freebsd-net@FreeBSD.ORG Wed Nov 26 18:08:37 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59A3C1065673 for ; Wed, 26 Nov 2008 18:08:37 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.freebsd.org (Postfix) with ESMTP id E16D58FC12 for ; Wed, 26 Nov 2008 18:08:36 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mAQI8OMt021595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Nov 2008 05:08:25 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mAQI8Nad002766; Thu, 27 Nov 2008 05:08:23 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mAQI8NSm002765; Thu, 27 Nov 2008 05:08:23 +1100 (EST) (envelope-from peter) Date: Thu, 27 Nov 2008 05:08:23 +1100 From: Peter Jeremy To: Cihangir Besiktas Message-ID: <20081126180822.GF51761@server.vk2pj.dyndns.org> References: <20081126074819.74241.qmail@istanbul.enderunix.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vvRocJ6whMXXNc9q" Content-Disposition: inline In-Reply-To: <20081126074819.74241.qmail@istanbul.enderunix.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-net@freebsd.org Subject: Re: Measuring processes' bandwidth usage 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, 26 Nov 2008 18:08:37 -0000 --vvRocJ6whMXXNc9q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Cihangir, On 2008-Nov-26 09:48:19 +0200, Cihangir Besiktas wrote: >I am planning to develop a project, and in this project, there must be a= =20 >module that outputs all the processes' bandwidth usage. How can I handle a= =20 >process' bandwidth usage? I am looking forward to your advices.=20 Can you explain further what you mean by a "processes' bandwidth usage". The process-related information collected by the kernel is listed in getrusage(2). You might also like to look at ktrace(1,2). I suspect you may need to modify the kernel to capture the information you are looking for. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --vvRocJ6whMXXNc9q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkktkJYACgkQ/opHv/APuIc4ZACaA3o7aKjBIt4dGoxy1bCp4nfQ A04AnjA4jciWbrbuqN/UqUV7hMJ2Wsbq =7EEJ -----END PGP SIGNATURE----- --vvRocJ6whMXXNc9q-- From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 05:48:35 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 495191065686; Thu, 27 Nov 2008 05:48:35 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 30DF18FC08; Thu, 27 Nov 2008 05:48:35 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAR5mZ8w019563; Thu, 27 Nov 2008 05:48:35 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAR5mZhb019559; Thu, 27 Nov 2008 05:48:35 GMT (envelope-from linimon) Date: Thu, 27 Nov 2008 05:48:35 GMT Message-Id: <200811270548.mAR5mZhb019559@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/129219: [ppp] Kernel panic when using kernel mode ppp 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, 27 Nov 2008 05:48:35 -0000 Synopsis: [ppp] Kernel panic when using kernel mode ppp Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Nov 27 05:48:22 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=129219 From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 07:44:15 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86F68106564A; Thu, 27 Nov 2008 07:44:15 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5D75E8FC25; Thu, 27 Nov 2008 07:44:15 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAR7iFqW038590; Thu, 27 Nov 2008 07:44:15 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAR7iFpI038586; Thu, 27 Nov 2008 07:44:15 GMT (envelope-from remko) Date: Thu, 27 Nov 2008 07:44:15 GMT Message-Id: <200811270744.mAR7iFpI038586@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: bin/129218: [ipsec]: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac 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, 27 Nov 2008 07:44:15 -0000 Old Synopsis: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac New Synopsis: [ipsec]: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Thu Nov 27 07:43:48 UTC 2008 Responsible-Changed-Why: reassign to networking team http://www.freebsd.org/cgi/query-pr.cgi?pr=129218 From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 09:24:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D05B0106564A for ; Thu, 27 Nov 2008 09:24:05 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.freebsd.org (Postfix) with ESMTP id 91D918FC1F for ; Thu, 27 Nov 2008 09:24:05 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from [217.150.130.134] (helo=unknown) by marvin.harmless.hu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L5cqu-000LIG-CS; Thu, 27 Nov 2008 10:08:00 +0100 Date: Thu, 27 Nov 2008 10:07:58 +0100 From: Gergely CZUCZY To: "Yony Yossef" Message-ID: <20081127100758.0000577c@unknown> In-Reply-To: <20def4870811260541x2f9bb410o44152a406407686@mail.gmail.com> References: <20def4870811260540x3d44a02bw43b6d18bc675de67@mail.gmail.com> <20def4870811260541x2f9bb410o44152a406407686@mail.gmail.com> Organization: Harmless Digital Bt X-Mailer: Claws Mail 3.6.1cvs32 (GTK+ 2.10.13; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: TSO on VLAN interface, FreeBSD 7 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, 27 Nov 2008 09:24:05 -0000 Hello, I'd be also pretty interested in this one. And also, the question arises me for the very same issue, for LACP interfaces, and VLAN-over-LACP interfaces (lagg(4) as LACP). Having a gateway requires performances, and it often also means having VLANs, and LACP for failure tolerance. So I think this is a pretty important issue. On Wed, 26 Nov 2008 15:41:09 +0200 "Yony Yossef" wrote: > Hi All, > > When I create a VLAN interface it does not inherit the parent > interface capabilities. > Is there a way to enable TSO (as other capabilities) on VLAN > interfaces? > > Thanks, > Yony > _______________________________________________ > 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" -- Sincerely, Gergely CZUCZY Tel: +36-30-8414202 From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 09:30:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D6EB1065676 for ; Thu, 27 Nov 2008 09:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5E9D78FC16 for ; Thu, 27 Nov 2008 09:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAR9U3SV015972 for ; Thu, 27 Nov 2008 09:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAR9U3dr015969; Thu, 27 Nov 2008 09:30:03 GMT (envelope-from gnats) Date: Thu, 27 Nov 2008 09:30:03 GMT Message-Id: <200811270930.mAR9U3dr015969@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: wang_jiabo Cc: Subject: Re: i386/129218: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: wang_jiabo List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2008 09:30:04 -0000 The following reply was made to PR bin/129218; it has been noted by GNATS. From: wang_jiabo To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-i386@FreeBSD.org Cc: Subject: Re: i386/129218: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac Date: Thu, 27 Nov 2008 17:23:58 +0800 FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `i386/129218'. > The individual assigned to look at your > report is: freebsd-i386. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=129218 > > >> Category: i386 >> Responsible: freebsd-i386 >> Synopsis: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac >> Arrival-Date: Thu Nov 27 03:10:01 UTC 2008 >> How to close the bug, I found that freebsd 6.3 can reslove the problem. but i do not know why FreeBSD7.0 can not support ipsec aes-xcbc-mac and null AH Thanks From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 09:55:19 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53D1E1065675; Thu, 27 Nov 2008 09:55:19 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2DE8E8FC1A; Thu, 27 Nov 2008 09:55:19 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAR9tHqH038356; Thu, 27 Nov 2008 09:55:17 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAR9tHKT038352; Thu, 27 Nov 2008 09:55:17 GMT (envelope-from remko) Date: Thu, 27 Nov 2008 09:55:17 GMT Message-Id: <200811270955.mAR9tHKT038352@freefall.freebsd.org> To: jiabwang@redhat.com, remko@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: bin/129218: [ipsec]: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac 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, 27 Nov 2008 09:55:19 -0000 Synopsis: [ipsec]: freebsd6.2 kernel cannot support ipsec "-E null -A hmac-sha1", FreeBSD7.0 kernel cannot support -A aes-xcbc-mac State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Thu Nov 27 09:55:17 UTC 2008 State-Changed-Why: Close per request of the submitter. the other question you have should be asked on the net@ mailinglist I think since this might be an implementation decision but isn't a bug just yet. Thanks for reporting and taking the time to make freebsd better. http://www.freebsd.org/cgi/query-pr.cgi?pr=129218 From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 10:28:14 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 578881065674 for ; Thu, 27 Nov 2008 10:28:14 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0F0258FC0C for ; Thu, 27 Nov 2008 10:28:13 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L5e6U-0007Dy-69 for freebsd-net@freebsd.org; Thu, 27 Nov 2008 10:28:10 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 27 Nov 2008 10:28:10 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 27 Nov 2008 10:28:10 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Ivan Voras Date: Thu, 27 Nov 2008 11:28:05 +0100 Lines: 44 Message-ID: References: <20def4870811260540x3d44a02bw43b6d18bc675de67@mail.gmail.com> <20def4870811260541x2f9bb410o44152a406407686@mail.gmail.com> <20081127100758.0000577c@unknown> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC2EA1CFEB1E8377784559E84" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.18 (X11/20081125) In-Reply-To: <20081127100758.0000577c@unknown> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: TSO on VLAN interface, FreeBSD 7 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, 27 Nov 2008 10:28:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC2EA1CFEB1E8377784559E84 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Gergely CZUCZY wrote: > Hello, >=20 > I'd be also pretty interested in this one. And also, the question > arises me for the very same issue, for LACP interfaces, and > VLAN-over-LACP interfaces (lagg(4) as LACP). > Having a gateway requires performances, and it often also means having > VLANs, and LACP for failure tolerance. So I think this is a pretty > important issue. >=20 > On Wed, 26 Nov 2008 15:41:09 +0200 > "Yony Yossef" wrote: >=20 >> Hi All, >> >> When I create a VLAN interface it does not inherit the parent >> interface capabilities. >> Is there a way to enable TSO (as other capabilities) on VLAN >> interfaces? It will probably be implemented in the future: http://lists.freebsd.org/pipermail/freebsd-net/2008-October/019729.html --------------enigC2EA1CFEB1E8377784559E84 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJLnY1ldnAQVacBcgRAgrJAKCIJ8+hj4oMizflHAD5J3W22Spr6ACg0kCw MjE+lpNwwJC54g852p/r7Fc= =hclj -----END PGP SIGNATURE----- --------------enigC2EA1CFEB1E8377784559E84-- From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 12:03:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B3AE1065674 for ; Thu, 27 Nov 2008 12:03:13 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.freebsd.org (Postfix) with ESMTP id 564478FC17 for ; Thu, 27 Nov 2008 12:03:13 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from [217.150.130.134] (helo=unknown) by marvin.harmless.hu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L5faS-000PSD-7V; Thu, 27 Nov 2008 13:03:12 +0100 Date: Thu, 27 Nov 2008 13:03:10 +0100 From: Gergely CZUCZY To: Ivan Voras Message-ID: <20081127130310.00006eaf@unknown> In-Reply-To: References: <20def4870811260540x3d44a02bw43b6d18bc675de67@mail.gmail.com> <20def4870811260541x2f9bb410o44152a406407686@mail.gmail.com> <20081127100758.0000577c@unknown> Organization: Harmless Digital Bt X-Mailer: Claws Mail 3.6.1cvs32 (GTK+ 2.10.13; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: Czuczy Gergely Cc: freebsd-net@freebsd.org Subject: Re: TSO on VLAN interface, FreeBSD 7 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, 27 Nov 2008 12:03:13 -0000 And an other question. For now, if these options are manually set for the derived interfaces, will that work? On Thu, 27 Nov 2008 11:28:05 +0100 Ivan Voras wrote: > Gergely CZUCZY wrote: > > Hello, > > > > I'd be also pretty interested in this one. And also, the question > > arises me for the very same issue, for LACP interfaces, and > > VLAN-over-LACP interfaces (lagg(4) as LACP). > > Having a gateway requires performances, and it often also means > > having VLANs, and LACP for failure tolerance. So I think this is a > > pretty important issue. > > > > On Wed, 26 Nov 2008 15:41:09 +0200 > > "Yony Yossef" wrote: > > > >> Hi All, > >> > >> When I create a VLAN interface it does not inherit the parent > >> interface capabilities. > >> Is there a way to enable TSO (as other capabilities) on VLAN > >> interfaces? > > It will probably be implemented in the future: > http://lists.freebsd.org/pipermail/freebsd-net/2008-October/019729.html > > -- Sincerely, Gergely CZUCZY Tel: +36-30-8414202 From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 12:13:19 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFE0C1065674 for ; Thu, 27 Nov 2008 12:13:19 +0000 (UTC) (envelope-from dave.edwards@adelaide.on.net) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by mx1.freebsd.org (Postfix) with ESMTP id 803FC8FC16 for ; Thu, 27 Nov 2008 12:13:19 +0000 (UTC) (envelope-from dave.edwards@adelaide.on.net) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjEFAFMaLknLevBj/2dsb2JhbACBbdEggn0 X-IronPort-AV: E=Sophos;i="4.33,674,1220193000"; d="scan'208";a="239102179" Received: from ppp240-99.static.internode.on.net (HELO chunga.apana.org.au) ([203.122.240.99]) by ipmail01.adl6.internode.on.net with ESMTP; 27 Nov 2008 22:28:03 +1030 Received: from [10.0.0.58] (tonto.leabrook [10.0.0.58]) by chunga.apana.org.au (8.14.2/8.12.11) with ESMTP id mARBw30E021773 for ; Thu, 27 Nov 2008 22:28:03 +1030 (CST) Message-ID: <492E8B52.9010408@adelaide.on.net> Date: Thu, 27 Nov 2008 22:28:10 +1030 From: Dave Edwards User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (chunga.apana.org.au [10.0.0.1]); Thu, 27 Nov 2008 22:28:03 +1030 (CST) Subject: nmap on FreeBSD 7.0-RELEASE 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, 27 Nov 2008 12:13:20 -0000 Hi, I'm having some problems with nmap over the tun device. I connect to the net using ppp and pppoe (adsl) which creates the "tun0" device. My default route goes out that way. Using nmap to try to map an external host: ------------------------- # nmap -vvv -e tun0 -sS -p80,443 1.2.3.4 Starting Nmap 4.76 ( http://nmap.org ) at 2008-11-27 22:05 CST WARNING: Unable to find appropriate interface for system route to 1.2.3.4 nexthost: failed to determine route to 1.2.3.4 QUITTING! -------------------------- This only seems to occur when running nmap as root. As a normal user (using the "connect" scan option) it seems to work ok, but you can only run a SYN scan (or force a specific source port) as root. I think this means that the problem may be related to using a raw socket.. I have the same problem with nmapping over a VPN tunnel as well (another tun device) so I don't think it's the configuration of the ppp session. As root, nmap finds the following interface list (note the missing default route) -------------------------- $ nmap --iflist Starting Nmap 4.76 ( http://nmap.org ) at 2008-11-27 22:00 CST ************************INTERFACES************************ DEV (SHORT) IP/MASK TYPE UP MAC rl0 (rl0) x.x.x.x ethernet up 00:00:E8:7A:EE:1C re0 (re0) x.x.x.x ethernet up 00:E0:4C:50:19:8F lo0 (lo0) 127.0.0.1/8 loopback up tun0 (tun0) x.x.x.x/32 point2point up WARNING: Unable to find appropriate interface for system route to 203.16.215.186 **************************ROUTES************************** DST/MASK DEV GATEWAY 127.0.0.1/32 lo0 127.0.0.1 203.16.215.186/32 tun0 x.x.x.x -------------------------- I've tried creating a host route for the nmap target instead of relying on the default route and I've tried three other versions of nmap. As an aside (or maybe a hint) when compiling nmap from source, there are a number of warnings like: ------------------------ checking net/route.h presence... yes configure: WARNING: net/route.h: present but cannot be compiled configure: WARNING: net/route.h: check for missing prerequisite headers? configure: WARNING: net/route.h: see the Autoconf documentation configure: WARNING: net/route.h: section "Present But Cannot Be Compiled" configure: WARNING: net/route.h: proceeding with the preprocessor's result configure: WARNING: net/route.h: in the future, the compiler will take precedence checking for net/route.h... yes ------------------------- Google has let me down this time. There are a few comments about nmap and FreeBSD but nothing that seems helpful and they are mostly fairly old. Anyone got a clue for me? davo From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 12:41:38 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E8481065676 for ; Thu, 27 Nov 2008 12:41:38 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 597318FC17 for ; Thu, 27 Nov 2008 12:41:38 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so434220ywe.13 for ; Thu, 27 Nov 2008 04:41:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=1+He6tQBrN+zwH9jHhLYQ4jN+LombKEj7GRyDsK6wvk=; b=kUPjbNH0E+QE4EvwbJqEvhdqeBaA9A3iTIYP2HURzu7v2i7KYYY+NcaGa/ndVYMhuB WgRO5CCpAhZn/CdfBnXz0OGbj/fqq4hQl8pRurDI2wb53rPGQbiwDwvBxX70nEZErb+y Lx6XFtpV0cX2u/PmOuRbjqkD7VY1F/ymq6cwI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=rnWQ5ppFS9kXfaQQIuuI0XbgVS6cGZ5ekgI7VV8Sm+0smEsbQc+ZpjoWuSeUPqfmyU /jzlpXqQPfCh/akHi+b+KWNvZKY0/ZLyOkcE0NMxU1GrRAVlSPVYcogT/CxHv1CsgUUa E7bLnnHTQw89rKPt3RY4sg+vvenVPRaMWv9UU= Received: by 10.151.46.3 with SMTP id y3mr13354608ybj.199.1227789697927; Thu, 27 Nov 2008 04:41:37 -0800 (PST) Received: by 10.150.154.21 with HTTP; Thu, 27 Nov 2008 04:41:37 -0800 (PST) Message-ID: <20def4870811270441n6b201076k715e1c7e1adc8781@mail.gmail.com> Date: Thu, 27 Nov 2008 14:41:37 +0200 From: "Yony Yossef" To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: IFCAP_LRO on FreeBSD 7 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, 27 Nov 2008 12:41:38 -0000 Hi All, Is there a native interface for LRO in FreeBSD 7? I can't find any use for IFCAP_LRO but notifying the driver if to use or not to use this offload. If not, is it planned for FreeBSD 8? Thanks Yony From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 12:51:28 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEA77106564A; Thu, 27 Nov 2008 12:51:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B89D08FC12; Thu, 27 Nov 2008 12:51:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 47F8546B52; Thu, 27 Nov 2008 07:51:28 -0500 (EST) Date: Thu, 27 Nov 2008 12:51:28 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Yony Yossef In-Reply-To: <20def4870811270441n6b201076k715e1c7e1adc8781@mail.gmail.com> Message-ID: References: <20def4870811270441n6b201076k715e1c7e1adc8781@mail.gmail.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: jfv@FreeBSD.org, freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: IFCAP_LRO on FreeBSD 7 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, 27 Nov 2008 12:51:29 -0000 On Thu, 27 Nov 2008, Yony Yossef wrote: > Is there a native interface for LRO in FreeBSD 7? I can't find any use for > IFCAP_LRO but notifying the driver if to use or not to use this offload. > > If not, is it planned for FreeBSD 8? IFCAP_LRO is a capability/policy flag allowing drivers to declare support for LRO, and for administrators to enable/disable it if present. Drivers can either provide their own implementation (mxge, nxge) or use the system implementation (cxgb, igb). I'm slightly surprised to see that igb references tcp_lro_init() but not IFCAP_LRO -- perhaps lro isn't yet fully hooked up, or perhaps there's a bug? I believe all of the above applies to 7.1 but not 7.0, except possibly mxge supporting LRO in 7.0. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 12:54:03 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E7A31065673 for ; Thu, 27 Nov 2008 12:54:03 +0000 (UTC) (envelope-from chflags@gmail.com) Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com [209.85.221.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3F6688FC12 for ; Thu, 27 Nov 2008 12:54:03 +0000 (UTC) (envelope-from chflags@gmail.com) Received: by qyk11 with SMTP id 11so1229099qyk.19 for ; Thu, 27 Nov 2008 04:54:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=iRWjB4bKGOD7CRu2/XQvrPvW3Rcn63xZ2auY0oxWJwI=; b=hPV/IlrWGU3uBle0cGn0yVceKBbthegom9YF27J5dVvoB7/ZBRzYuQ5y8pKTRchpCi bQ4AYJqXXgTpvhlaNl9bCautJViSx+zh9YjOvBl1cZj+zYr2Lzrwkw7+sBgA5rvbrfaJ iCNflDOWagnCGo/HfRWqiDBdrrbo04BMtJ8kU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=uG8L4QGyHLs2fEJCRoutRW7efDe9EoYOTJxyXm6zWjBCdI4+11yhzR5XMjtkZ36Cmj +I5e1bpDO4ZrLf3mBhGAZ1N2CFrbpfwMp3CGt0yJBIes67RINynSlgjuNAs+EVrtpNA/ 1Z25wrfRx3dO0eMKe//rVgtkamhMqRZQq9Im8= Received: by 10.214.244.14 with SMTP id r14mr6719307qah.93.1227788815458; Thu, 27 Nov 2008 04:26:55 -0800 (PST) Received: by 10.214.147.11 with HTTP; Thu, 27 Nov 2008 04:26:55 -0800 (PST) Message-ID: <25cb30811270426i6b5cc4c2s49030f64d06b0ec8@mail.gmail.com> Date: Thu, 27 Nov 2008 20:26:55 +0800 From: "Kevin Foo" To: freebsd-pf@freebsd.org, freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: if_bridge + pf rdr (bridged inline proxy) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chflags@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2008 12:54:03 -0000 Hi list, I recently setup a bridge box with inline cache proxy. if_bridge with pf filtering was working perfectly. However, squid-cache listening on loopback device did not get any packets from pf rdr. I have seen successful setups with OpenBSD's bridge spamd which rather a similar setup. Is something broken on FreeBSD's if_bridge or am I missing some configuration here? pfctl -ss (on bridge box): ------------------ all tcp 127.0.0.1:3128 <- 71.14.235.147:80 <- 192.168.1.100:1041 CLOSED:SYN_SENT all tcp 192.168.1.100:1041 -> 127.0.0.1:3128 SYN_SENT:CLOSED Environment ------------------ FreeBSD bridge.mybox 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Tue Nov 25 22:56:22 MYT 2008 kev@bridge.mybox:/usr/obj/usr/src/sys/BRIDGE i386 Squid Cache: Version 2.7.STABLE5 with --enable-pf-transparent rc.conf: ------------------ cloned_interfaces="bridge0" ifconfig_bridge0="addm bge0 addm bge1 up" ifconfig_bge0="up" ifconfig_bge1="up" pf_enable="YES" squid_enabld="YES" pf.conf: ------------------ int_if="bge0" ext_if="bge1" rdr pass on $int_if inet proto tcp from any to any port 80 -> 127.0.0.1 port 3128 pass in all pass out all pass on $int_if route-to lo0 proto tcp from any to 127.0.0.1 port 3128 sysctl net.link.bridge : ------------------ net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 1 net.link.bridge.pfil_member: 1 net.link.bridge.pfil_bridge: 0 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 0 Hping Testing (from client 192.168.1.100): ------------------ hping -S -p 80 -c 10 www.google.com A quick search on freebsd-pf archive, I found a thread on similar setup in 2004. http://lists.freebsd.org/pipermail/freebsd-pf/2004-October/000522.html However, the bridge code of FreeBSD was blamed for poor performance and lack of functionalities. A more recent post on freebsd-net mailing list on similar issue. http://lists.freebsd.org/pipermail/freebsd-net/2008-September/019556.html Any ideas? TIA. P/S : please cc me as I'm not subscribed to freebsd-pf nor freebsd-net mailing list. Thanks. -- Regards Kevin Foo From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 13:57:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED5871065687 for ; Thu, 27 Nov 2008 13:57:05 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 57E778FC1B for ; Thu, 27 Nov 2008 13:57:04 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=S7XYJvXJwur6N6eg+AvCfrzEL1bb+YP4p742zh4rrSNFYOz/tZVnJKJIokULSQlSwdsa6ZlCv2XJEUnJ9LCLeO1DkXSXUIpOGBig9GanUDxk0kVrf5DcK79YlIHCHlkujWi4aXwrMRI+d0uO2p7SROXBCulqE47AADt2554VBM8=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1L5hMc-000NHC-Bn; Thu, 27 Nov 2008 16:57:02 +0300 Date: Thu, 27 Nov 2008 16:57:01 +0300 From: Eygene Ryabinkin To: Dave Edwards Message-ID: <4CREIW43kKwxaB43gZShXkxNn3U@2DcjJpvUBcA8GzIZe2t/Ulo9G+Y> References: <492E8B52.9010408@adelaide.on.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opg8F0UgoHELSI+9" Content-Disposition: inline In-Reply-To: <492E8B52.9010408@adelaide.on.net> Sender: rea-fbsd@codelabs.ru Cc: freebsd-net@freebsd.org Subject: Re: nmap on FreeBSD 7.0-RELEASE 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, 27 Nov 2008 13:57:06 -0000 --opg8F0UgoHELSI+9 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dave, good day. Thu, Nov 27, 2008 at 10:28:10PM +1030, Dave Edwards wrote: > I've tried creating a host route for the nmap target instead of relying > on the default route and I've tried three other versions of nmap. As an > aside (or maybe a hint) when compiling nmap from source, there are a > number of warnings like: > ------------------------ > checking net/route.h presence... yes > configure: WARNING: net/route.h: present but cannot be compiled > configure: WARNING: net/route.h: check for missing prerequisite heade= rs? > configure: WARNING: net/route.h: see the Autoconf documentation > configure: WARNING: net/route.h: section "Present But Cannot Be > Compiled" > configure: WARNING: net/route.h: proceeding with the preprocessor's result > configure: WARNING: net/route.h: in the future, the compiler will take > precedence > checking for net/route.h... yes > ------------------------- Could you, please, post the accompanying config.log that was produced by configure and the configure script itself? --=20 Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual =20 )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20 {_.-``-' {_/ # --opg8F0UgoHELSI+9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkupy0ACgkQthUKNsbL7YjajQCfU3WG1CYxPKCV+sgkZCEaeJew 38QAnj6TzAbN2wh3e0V6WS/3pa2zyDMj =ylCA -----END PGP SIGNATURE----- --opg8F0UgoHELSI+9-- From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 14:00:17 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B028C1065676 for ; Thu, 27 Nov 2008 14:00:17 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 609618FC12 for ; Thu, 27 Nov 2008 14:00:17 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=XNzavE+rEGrOliyiruUKB8sBcGdto5XmSHNxD45xBRszeFpDX0wWrcznU+OparoztklNCHR9QFjwtCD+K9iO2GU/+4LTf+dJDVFwTqEaw89sHARzc/LLiJ1Wd0Fx9ohpLg2Kn77qKZgMBVuVxr9KO/ijCvzcLR2fyDuWrxRXl80=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1L5hPk-000NUw-CC; Thu, 27 Nov 2008 17:00:16 +0300 Date: Thu, 27 Nov 2008 17:00:15 +0300 From: Eygene Ryabinkin To: Kevin Foo Message-ID: References: <25cb30811270426i6b5cc4c2s49030f64d06b0ec8@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0qVF/w3MHQqLSynd" Content-Disposition: inline In-Reply-To: <25cb30811270426i6b5cc4c2s49030f64d06b0ec8@mail.gmail.com> Sender: rea-fbsd@codelabs.ru Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: if_bridge + pf rdr (bridged inline proxy) 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, 27 Nov 2008 14:00:17 -0000 --0qVF/w3MHQqLSynd Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Kevin, good day. Thu, Nov 27, 2008 at 08:26:55PM +0800, Kevin Foo wrote: > I recently setup a bridge box with inline cache proxy. if_bridge with > pf filtering was working perfectly. However, squid-cache listening on > loopback device did not get any packets from pf rdr. I have seen > successful setups with OpenBSD's bridge spamd which rather a similar > setup. Is something broken on FreeBSD's if_bridge or am I missing some > configuration here? pf can 'rdr' only incoming packets (from 'man pf.conf'): ----- Evaluation order of the translation rules is dependent on the type of = the translation rules and of the direction of a packet. binat rules are always evaluated first. Then either the rdr rules are evaluated on an inbound packet or the nat rules on an outbound packet. Rules of the s= ame type are evaluated in the same order in which they appear in the rules= et. The first matching rule decides what action is taken. ----- So this can be just pf-related. And may be not, as usual... --=20 Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual =20 )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20 {_.-``-' {_/ # --0qVF/w3MHQqLSynd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkup+8ACgkQthUKNsbL7YjIJQCff20fjLaHQ7j5sscSdcUBElK+ trQAn3cHJZVTVJ1LcWbrjjH0fgWUQ7bU =rd2z -----END PGP SIGNATURE----- --0qVF/w3MHQqLSynd-- From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 14:03:26 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8B221065675 for ; Thu, 27 Nov 2008 14:03:26 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 377E88FC26 for ; Thu, 27 Nov 2008 14:03:26 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 27 Nov 2008 14:03:24 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by walton.maths.tcd.ie with SMTP id ; 27 Nov 2008 14:03:20 +0000 (GMT) To: freebsd-net@freebsd.org Date: Thu, 27 Nov 2008 14:03:20 +0000 From: David Malone Message-ID: <200811271403.aa55110@walton.maths.tcd.ie> Cc: Kevin Oberman Subject: FreeBSD Window updates 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, 27 Nov 2008 14:03:26 -0000 I was looking at some tcpdumps from a FreeBSD box receiving a TCP stream with someone yesterday and noticed that it seemed to be generating quite a lot of dupliacte acks. Looking more carefully, we noticed that the duplicates were actually window updates. The code for sending window updates can be found in: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c?annot ate=1.157 around lines 541-565. It seems that we generate a window update if the available buffer space changes by more than two packets, or if it changes by more than half the buffer size. This is probably a little aggressive, and in some cases seems to result in bursts of window updates that look like they should be batched. I wonder if it would make sense to not do a window update if a delayed ack is scheduled? It might even be possible to do them as a delayed ack without causing problems. I note that there is at least one PR mentioning we generate many window updates: http://www.freebsd.org/cgi/query-pr.cgi?pr=116335 I also wonder if it might cause non-FreeBSD senders to back off, we are careful not to retransmit if we get window updates (see http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_input.c?annota te=1.392 about line 1836, but other OSes might not be and that might degrade our performance when receiving from a non-FreeBSD sender. David. From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 14:25:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 009C21065674 for ; Thu, 27 Nov 2008 14:25:46 +0000 (UTC) (envelope-from frank@harz.behrens.de) Received: from post.behrens.de (post.behrens.de [IPv6:2a01:170:1023::1:2]) by mx1.freebsd.org (Postfix) with ESMTP id 517DD8FC0A for ; Thu, 27 Nov 2008 14:25:44 +0000 (UTC) (envelope-from frank@harz.behrens.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=behrens.de; h=from:to:date:mime-version:subject:in-reply-to:content-type:content-transfer-encoding:content-description; s=pinky1; t=1227795942; i=frank@harz.behrens.de; bh=mfyG6uw4eeTZnVDmGQfyFLiX5QZSSTmmUv3HQuV9mC0=; b=hcyQUOUEVNyUvKbI5EhymfyYDd2sR6h4lYt+M7opY4rEioloZWBevAOmvV+Y45uJRE4WfIi9WL8HdEWAkGEx8g== Received: from sun.behrens ([IPv6:2a01:170:1023:0:293a:5717:e088:4f7a]) by post.behrens.de (8.14.3/8.14.2) with ESMTP(MSA) id mAREPSwm004057 for ; Thu, 27 Nov 2008 15:25:28 +0100 (CET) (envelope-from frank@harz.behrens.de) Message-Id: <200811271425.mAREPSwm004057@post.behrens.de> From: "Frank Behrens" To: freebsd-net@freebsd.org Date: Thu, 27 Nov 2008 15:25:28 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <20081126234502.S61259@maildrop.int.zabbadoz.net> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Hashcash: 1:23:081127:freebsd-net@freebsd.org::rt8pKNc098YZtoqj:000000000012Tcn Subject: Problem with new source address selection (was Anyone interested in jail patches?) 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, 27 Nov 2008 14:25:46 -0000 Bjoern A. Zeeb wrote on 26 Nov 2008 23:56: > If you are interested in a new set of jail patches... anyone?;-) Yes, but about jail specific things I'll write later, in another mail and on another list. > 2b) for RELENG_7: > http://people.freebsd.org/~bz/bz_jail7-20081126-02-at153644.diff With this patch I received a new source selection implementation, I believe the same as announced for HEAD. Here I found a problem. One of my machines tunnels a private subnet via IPSEC (esp/tunnel). Lets assume my private subnet is 192.168.90.0/24 and the "foreign" subnet is 192.168.200.0/24. When I send packets via this tunnel I must ensure the right source address, because the machine has several interfaces. (BTW: this is so easy with openvpn and real routing, but sometimes other people decide..) An easy solution was for me ifconfig lo2 inet 192.168.90.254/32 route add -net 192.168.200.0/24 -iface lo2 The route is a "dummy" route only, because the IPSEC SPD determines the packet flow. This worked well in the past, but not with your patch. On connect(2) call for the tunneled subnet I receive always "Network unreachable". The following _wild hack_(tm) solves the problem _for me_, it is only to show the problem to you: --- sys/netinet/in_pcb.c.orig 2008-11-27 14:57:25.887082927 +0100 +++ sys/netinet/in_pcb.c 2008-11-27 14:29:28.918257601 +0100 @@ -697,6 +697,9 @@ in_pcbladdr(struct inpcb *inp, struct in ia = ifatoia(ifa_ifwithnet(sintosa(&sain))); if (cred == NULL || !jailed(cred)) { +// FB2008-11-27 + ia = (struct in_ifaddr *)sro.ro_rt->rt_ifa; +// FB if (ia == NULL) { error = ENETUNREACH; goto done; Can you provide a patch to solve the connect problem? Is there a better solution to setup source address selection for IPSEC tunnels? Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 14:55:07 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F09551065673 for ; Thu, 27 Nov 2008 14:55:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id AB1A28FC19 for ; Thu, 27 Nov 2008 14:55:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 25EB141C66F; Thu, 27 Nov 2008 15:55:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 08AOMH9QpJ7S; Thu, 27 Nov 2008 15:55:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id B6BC041C667; Thu, 27 Nov 2008 15:55:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 6CAAF4448D5; Thu, 27 Nov 2008 14:53:58 +0000 (UTC) Date: Thu, 27 Nov 2008 14:53:58 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Frank Behrens In-Reply-To: <200811271425.mAREPSwm004057@post.behrens.de> Message-ID: <20081127143300.M61259@maildrop.int.zabbadoz.net> References: <200811271425.mAREPSwm004057@post.behrens.de> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Problem with new source address selection (was Anyone interested in jail patches?) 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, 27 Nov 2008 14:55:08 -0000 On Thu, 27 Nov 2008, Frank Behrens wrote: >> 2b) for RELENG_7: >> http://people.freebsd.org/~bz/bz_jail7-20081126-02-at153644.diff > > With this patch I received a new source selection implementation, I > believe the same as announced for HEAD. Here I found a problem. HEAD has had it since beginning of October and older jail patches also had it for a while now. > One of my machines tunnels a private subnet via IPSEC (esp/tunnel). > Lets assume my private subnet is 192.168.90.0/24 and the "foreign" > subnet is 192.168.200.0/24. When I send packets via this tunnel I > must ensure the right source address, because the machine has several > interfaces. (BTW: this is so easy with openvpn and real routing, but > sometimes other people decide..) An easy solution was for me > ifconfig lo2 inet 192.168.90.254/32 > route add -net 192.168.200.0/24 -iface lo2 > The route is a "dummy" route only, because the IPSEC SPD determines > the packet flow. Yes I know that hack though I never actually used it with a loopback as the loopback case is *uhm* gross. You know you are telling the kernel to actually send the packets to yourself which so far has just worked more or less out of luck in my eyes. So is your 192.168.90.0/24 on any other interface but the lo2? Is it the only network on that interface or are there aliases? > This worked well in the past, but not with your patch. On connect(2) > call for the tunneled subnet I receive always "Network unreachable". > The following _wild hack_(tm) solves the problem _for me_, it is only > to show the problem to you: >From the code down I take it that the connect(2) call happens outside any jail and not within a jail, right? > --- sys/netinet/in_pcb.c.orig 2008-11-27 14:57:25.887082927 +0100 > +++ sys/netinet/in_pcb.c 2008-11-27 14:29:28.918257601 +0100 > @@ -697,6 +697,9 @@ in_pcbladdr(struct inpcb *inp, struct in > ia = ifatoia(ifa_ifwithnet(sintosa(&sain))); > > if (cred == NULL || !jailed(cred)) { > +// FB2008-11-27 > + ia = (struct in_ifaddr *)sro.ro_rt->rt_ifa; > +// FB > if (ia == NULL) { > error = ENETUNREACH; > goto done; > > Can you provide a patch to solve the connect problem? > Is there a better solution to setup source address selection for > IPSEC tunnels? Let me answer those later; in case you cannot reveal your network setup in public; contact me offlist. /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 15:42:48 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E2B9106564A for ; Thu, 27 Nov 2008 15:42:48 +0000 (UTC) (envelope-from frank@harz.behrens.de) Received: from post.behrens.de (post.behrens.de [IPv6:2a01:170:1023::1:2]) by mx1.freebsd.org (Postfix) with ESMTP id A2C708FC14 for ; Thu, 27 Nov 2008 15:42:47 +0000 (UTC) (envelope-from frank@harz.behrens.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=behrens.de; h=from:to:date:mime-version:subject:in-reply-to:references:content-type:content-transfer-encoding:content-description; s=pinky1; t=1227800565; i=frank@harz.behrens.de; bh=w3FzHEZ4GUUxq/gggK4LX5/NlABVayN4qp4rLWCUkto=; b=WfnjjLML2kFyrDn7QofXRZ/IeOWIdmFUd0+HjvrIyd+Ou6mv93juRSdJS/U03stUzcsiv8M1J8qWghRinMDPkw== Received: from sun.behrens ([IPv6:2a01:170:1023:0:293a:5717:e088:4f7a]) by post.behrens.de (8.14.3/8.14.2) with ESMTP(MSA) id mARFgglB004902 for ; Thu, 27 Nov 2008 16:42:42 +0100 (CET) (envelope-from frank@harz.behrens.de) Message-Id: <200811271542.mARFgglB004902@post.behrens.de> From: "Frank Behrens" To: freebsd-net@freebsd.org Date: Thu, 27 Nov 2008 16:42:42 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <20081127143300.M61259@maildrop.int.zabbadoz.net> References: <200811271425.mAREPSwm004057@post.behrens.de> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Hashcash: 1:23:081127:freebsd-net@freebsd.org::FibMkbSj/GT29NEa:0000000000LyO/ Subject: Re: Problem with new source address selection 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, 27 Nov 2008 15:42:48 -0000 Bjoern, thanks for your fast answer. Bjoern A. Zeeb wrote on 27 Nov 2008 14:53: > Yes I know that hack though I never actually used it with a loopback > as the loopback case is *uhm* gross. You know you are telling the > kernel to actually send the packets to yourself which so far has just > worked more or less out of luck in my eyes. IMHO here we see again the main problem of IPSEC. Suddenly packets disappear in kernel, are tunneled with ipsec and appear on other end. A gif-like device with routes instead of SPD entries would have some advantages. > So is your 192.168.90.0/24 on any other interface but the lo2? > Is it the only network on that interface or are there aliases? For this machine the simplified setup is: - an ethernet interface for private net with address 192.168.90.1/24 and additional aliases for external addresses - several tun devices with external and private addresses and routes - lo0 as real loopback device with 127.0.0.1/8 - lo1 with private jail addresses Now I want to tunnel between my 192.168.90.0/24 and a foreign 192.168.200.0/24. So I assigned 192.168.90.254/32 to lo2 and created a static route. > From the code down I take it that the connect(2) call happens outside > any jail and not within a jail, right? Yes, this is outside a jail. With jails I had no problems, every jail has currently one ipv4 and one ipv6 address. > Let me answer those later; in case you cannot reveal your network > setup in public; contact me offlist. If desired I could send you the complete interface and routing table. But I believe you should be able to see the problem with my example above. Thanks for sour support, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 16:50:07 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 327661065672 for ; Thu, 27 Nov 2008 16:50:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id E4E6F8FC20 for ; Thu, 27 Nov 2008 16:50:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 294AB41C69F; Thu, 27 Nov 2008 17:50:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 5-w+ZQeRN2KL; Thu, 27 Nov 2008 17:50:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id D27AE41C6A3; Thu, 27 Nov 2008 17:50:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id C5DE04448D5; Thu, 27 Nov 2008 16:47:52 +0000 (UTC) Date: Thu, 27 Nov 2008 16:47:52 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Frank Behrens In-Reply-To: <200811271542.mARFgglB004902@post.behrens.de> Message-ID: <20081127164201.M61259@maildrop.int.zabbadoz.net> References: <200811271425.mAREPSwm004057@post.behrens.de> <200811271542.mARFgglB004902@post.behrens.de> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Problem with new source address selection 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, 27 Nov 2008 16:50:07 -0000 On Thu, 27 Nov 2008, Frank Behrens wrote: Hi, I am running out the door but ... will check again tonight. > Bjoern A. Zeeb wrote on 27 Nov 2008 14:53: [gif-like ipsec and routes] routes are not alternatives for fixing applications;) Often it's easier to apply a hack instead of fix the application but that's a different story... >> So is your 192.168.90.0/24 on any other interface but the lo2? >> Is it the only network on that interface or are there aliases? > > For this machine the simplified setup is: > - an ethernet interface for private net with address 192.168.90.1/24 > and additional aliases for external addresses ... > Now I want to tunnel between my 192.168.90.0/24 and a foreign > 192.168.200.0/24. So I assigned 192.168.90.254/32 to lo2 and created > a static route. So if you don't mind to go out with a source address of 192.168.90.1 instead of .254, what about this hack. What happens if you change the route to route change -net 192.168.200.0/24 192.168.90.2 (assuming the .2 is not on your local machine). /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 17:09:14 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 961BD1065670 for ; Thu, 27 Nov 2008 17:09:14 +0000 (UTC) (envelope-from frank@harz.behrens.de) Received: from post.behrens.de (post.behrens.de [IPv6:2a01:170:1023::1:2]) by mx1.freebsd.org (Postfix) with ESMTP id F3C078FC0C for ; Thu, 27 Nov 2008 17:09:13 +0000 (UTC) (envelope-from frank@harz.behrens.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=behrens.de; h=from:to:date:mime-version:subject:in-reply-to:references:content-type:content-transfer-encoding:content-description; s=pinky1; t=1227805752; i=frank@harz.behrens.de; bh=MCyjdlXmaajZStxJEgk3LSM6+mDdiQ5fJUzzQHlRM14=; b=KZYYJJrbc+bBxSt0DPPF1aXUwF6l5cv1cN5L/gpkqxlYWfPj/dlJHed7NGG6+vt1ld56a9X26TmEIoyCaAYLYQ== Received: from sun.behrens ([IPv6:2a01:170:1023:0:293a:5717:e088:4f7a]) by post.behrens.de (8.14.3/8.14.2) with ESMTP(MSA) id mARH99HH009871 for ; Thu, 27 Nov 2008 18:09:09 +0100 (CET) (envelope-from frank@harz.behrens.de) Message-Id: <200811271709.mARH99HH009871@post.behrens.de> From: "Frank Behrens" To: freebsd-net@freebsd.org Date: Thu, 27 Nov 2008 18:09:09 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <20081127164201.M61259@maildrop.int.zabbadoz.net> References: <200811271542.mARFgglB004902@post.behrens.de> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Hashcash: 1:23:081127:freebsd-net@freebsd.org::YYAaCnDCBZfaglkb:0000000000GyG5 Subject: Re: Problem with new source address selection 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, 27 Nov 2008 17:09:14 -0000 Bjoern A. Zeeb wrote on 27 Nov 2008 16:47: > I am running out the door but ... will check again tonight. Thanks! > So if you don't mind to go out with a source address of 192.168.90.1 > instead of .254, what about this hack. What happens if you change the > route to > route change -net 192.168.200.0/24 192.168.90.2 > (assuming the .2 is not on your local machine). Hm, looks fine. I thought there must be another way for address selection. :-) Thanks for your idea, I'll test this and report. -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. From owner-freebsd-net@FreeBSD.ORG Thu Nov 27 19:43:33 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 040EB1065678 for ; Thu, 27 Nov 2008 19:43:33 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id CC72D8FC13 for ; Thu, 27 Nov 2008 19:43:32 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so520424wag.27 for ; Thu, 27 Nov 2008 11:43:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=wrsOd/+aYsVCKZMlSXn1TJiWJXvGhSQP00jthu3/tFo=; b=jPr3096JpAgIswuc3g8ldmlAU2fOc73bWdMrThmQoem4WSp/hSL2qOvk4LxuLJctYg yac8j/dVvx8jpCPmMtFp2KNP+Hs+4HRPo2Yh5dNG78/l5iVzFdhvFzpcI2tAXcfB/oIr 6jxfckWUoswBb6X/UD02m+dB8kSpAv5xRMm8A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=XT0bshxbrGiR1soS2huvKwSrPjIgtiuYoGW4o/c8UOCzRcqMdobribYTsKyFtX7kt9 nJ6QOD3Cbu4SJ/fedR5XB2R9li7iqafhgpmykJZKJo0sJT0BKgb4IifXZfZmL5jqXI99 HEzL3N0TApi61Nunhkaa5hKiQdgzbVs3HK168= Received: by 10.114.197.1 with SMTP id u1mr4143269waf.120.1227815012101; Thu, 27 Nov 2008 11:43:32 -0800 (PST) Received: by 10.114.235.17 with HTTP; Thu, 27 Nov 2008 11:43:32 -0800 (PST) Message-ID: <2a41acea0811271143q25f83e89i4df2791052a980ac@mail.gmail.com> Date: Thu, 27 Nov 2008 11:43:32 -0800 From: "Jack Vogel" To: "Robert Watson" In-Reply-To: MIME-Version: 1.0 References: <20def4870811270441n6b201076k715e1c7e1adc8781@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: jfv@freebsd.org, freebsd-hackers@freebsd.org, Yony Yossef , freebsd-net@freebsd.org Subject: Re: IFCAP_LRO on FreeBSD 7 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, 27 Nov 2008 19:43:33 -0000 On Thu, Nov 27, 2008 at 4:51 AM, Robert Watson wrote: > > On Thu, 27 Nov 2008, Yony Yossef wrote: > > Is there a native interface for LRO in FreeBSD 7? I can't find any use for >> IFCAP_LRO but notifying the driver if to use or not to use this offload. >> >> If not, is it planned for FreeBSD 8? >> > > IFCAP_LRO is a capability/policy flag allowing drivers to declare support > for LRO, and for administrators to enable/disable it if present. Drivers > can either provide their own implementation (mxge, nxge) or use the system > implementation (cxgb, igb). I'm slightly surprised to see that igb > references tcp_lro_init() but not IFCAP_LRO -- perhaps lro isn't yet fully > hooked up, or perhaps there's a bug? I believe all of the above applies to > 7.1 but not 7.0, except possibly mxge supporting LRO in 7.0. > Been so busy internally that I did not even realize that this capability had been created, I need to change both igb and ixgbe to use it. Thanks for pointing this out, Jack From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 05:29:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB8861065670 for ; Fri, 28 Nov 2008 05:29:36 +0000 (UTC) (envelope-from chflags@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1024A8FC13 for ; Fri, 28 Nov 2008 05:29:35 +0000 (UTC) (envelope-from chflags@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so305348qwb.7 for ; Thu, 27 Nov 2008 21:29:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=TQo1Dom25u2RFFFlCWQyXI/FXgo4eUHTEDN7CyVFfyY=; b=nPiNvlf1JjPVflEYo1RskES0LmAAI3HwV0PJaJ7RG9qTkyoDAL4RtFDok2GAeUOFY7 UkaW+tacaTDKE2PKyEzIfLeJQKGIchqnFOBlLcKz2iJ5OeQzpPWmfG4+JIArzLICgOQa FqcX2SAX2oPkW9vk6RLL2khuzj9JcnSkRK5cY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=QttUqXFh3A2q1IcfqH6OdSEzFgpICN4GEUnog3qEMRC2mVy2kbC3o2sX4aaKfe+Hwf WI+w9dW5Gw39z1jPFAh8mqjPkuaTKFZI999UpGprxnBwhkTdl+SpAUVbGbXDt4lr8npF O9fmirQ6UekdHOvFqXU0xUZgXxKmEB2X1uxj4= Received: by 10.215.67.5 with SMTP id u5mr7427146qak.12.1227850175373; Thu, 27 Nov 2008 21:29:35 -0800 (PST) Received: by 10.214.147.11 with HTTP; Thu, 27 Nov 2008 21:29:35 -0800 (PST) Message-ID: <25cb30811272129h68e50bf4u46b15823b101a3@mail.gmail.com> Date: Fri, 28 Nov 2008 13:29:35 +0800 From: "Kevin Foo" To: freebsd-pf@freebsd.org, freebsd-net@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <25cb30811270426i6b5cc4c2s49030f64d06b0ec8@mail.gmail.com> Cc: Subject: Re: if_bridge + pf rdr (bridged inline proxy) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chflags@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2008 05:29:36 -0000 Thank Eygene for the reply. It might be but I'm not sure. Anyone is having the same setting or any info on this? -- Regards Kevin Foo On Thu, Nov 27, 2008 at 10:00 PM, Eygene Ryabinkin wrote: > Kevin, good day. > > Thu, Nov 27, 2008 at 08:26:55PM +0800, Kevin Foo wrote: >> I recently setup a bridge box with inline cache proxy. if_bridge with >> pf filtering was working perfectly. However, squid-cache listening on >> loopback device did not get any packets from pf rdr. I have seen >> successful setups with OpenBSD's bridge spamd which rather a similar >> setup. Is something broken on FreeBSD's if_bridge or am I missing some >> configuration here? > > pf can 'rdr' only incoming packets (from 'man pf.conf'): > ----- > Evaluation order of the translation rules is dependent on the type of the > translation rules and of the direction of a packet. binat rules are > always evaluated first. Then either the rdr rules are evaluated on an > inbound packet or the nat rules on an outbound packet. Rules of the same > type are evaluated in the same order in which they appear in the ruleset. > The first matching rule decides what action is taken. > ----- > So this can be just pf-related. And may be not, as usual... > -- > Eygene > _ ___ _.--. # > \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard > / ' ` , __.--' # to read the on-line manual > )/' _/ \ `-_, / # while single-stepping the kernel. > `-'" `"\_ ,_.-;_.-\_ ', fsc/as # > _.-'_./ {_.' ; / # -- FreeBSD Developers handbook > {_.-``-' {_/ # > From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 06:53:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66C311065674 for ; Fri, 28 Nov 2008 06:53:11 +0000 (UTC) (envelope-from frank@harz.behrens.de) Received: from post.behrens.de (post.behrens.de [IPv6:2a01:170:1023::1:2]) by mx1.freebsd.org (Postfix) with ESMTP id 4F8A88FC26 for ; Fri, 28 Nov 2008 06:53:09 +0000 (UTC) (envelope-from frank@harz.behrens.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=behrens.de; h=from:to:date:mime-version:subject:cc:in-reply-to:references:content-type:content-transfer-encoding:content-description; s=pinky1; t=1227855188; i=frank@harz.behrens.de; bh=rMyU6uXbyNAqVK0p31OZz+YW+E0IXNVfswx3n2d1YDU=; b=AoSurEzvjaCCio8WrzJlyOHIxS4MdnplrSRJsCy/7xrWc5vCi9cCtqmzhNwjBhmQQ3qoGytxAwv181NWoT5wvg== Received: from sun.behrens ([IPv6:2a01:170:1023:0:c0d6:53ce:9573:dd8b]) by post.behrens.de (8.14.3/8.14.2) with ESMTP(MSA) id mAS6r1P3014050; Fri, 28 Nov 2008 07:53:01 +0100 (CET) (envelope-from frank@harz.behrens.de) Message-Id: <200811280653.mAS6r1P3014050@post.behrens.de> From: "Frank Behrens" To: "Bjoern A. Zeeb" Date: Fri, 28 Nov 2008 07:53:02 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <20081127164201.M61259@maildrop.int.zabbadoz.net> References: <200811271542.mARFgglB004902@post.behrens.de> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Hashcash: 1:23:081128:freebsd-net@freebsd.org::0+DtdclIdhiSGdRo:0000000000HBtx X-Hashcash: 1:23:081128:bzeeb-lists@lists.zabbadoz.net::7q2aWHNDOlM9kAqD:000RUmy Cc: freebsd-net@freebsd.org Subject: Re: Problem with new source address selection 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, 28 Nov 2008 06:53:11 -0000 Bjoern A. Zeeb wrote on 27 Nov 2008 16:47: > > Now I want to tunnel between my 192.168.90.0/24 and a foreign > > 192.168.200.0/24. So I assigned 192.168.90.254/32 to lo2 and created > > a static route. > > So if you don't mind to go out with a source address of 192.168.90.1 > instead of .254, what about this hack. What happens if you change the > route to > route change -net 192.168.200.0/24 192.168.90.2 > (assuming the .2 is not on your local machine). That works for the router, but for incoming packets on the internal interface (from -net 192.168.90.0/24) the machine will send an ICMP redirect to new router 192.168.90.2. Of course that is a black hole. When I use the route to own interface address (route change -net 192.168.200.0/24 192.168.90.1) it works, but also for every incoming packet an ICMP redirect is sent. So that solution is a workaround for short time only. Does anybody have a better solution for source address selection? Am I the only one with an IPSEC tunnel? -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 12:30:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7BFE1065670 for ; Fri, 28 Nov 2008 12:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D924B8FC08 for ; Fri, 28 Nov 2008 12:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mASCU4Qt058150 for ; Fri, 28 Nov 2008 12:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mASCU44Z058145; Fri, 28 Nov 2008 12:30:04 GMT (envelope-from gnats) Date: Fri, 28 Nov 2008 12:30:04 GMT Message-Id: <200811281230.mASCU44Z058145@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Alex Cc: Subject: Re: kern/129022: [ath] ath cannot connect using WEP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2008 12:30:05 -0000 The following reply was made to PR kern/129022; it has been noted by GNATS. From: Alex To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/129022: [ath] ath cannot connect using WEP Date: Fri, 28 Nov 2008 12:26:59 GMT >Submitter-Id: current-users >Originator: Alex >Organization: >Confidential: no >Synopsis: Re: kern/129022: [ath] ath cannot connect using WEP >Severity: serious >Priority: high >Category: kern >Class: sw-bug >Release: 8-CURRENT >Environment: FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #8 r185353M: Thu Nov 27 01:48:42 CET 2008 root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL i386 >Description: could somebody please have a look at this? just tell me if you need more debug output and i'll provide it. right now i have to connect to my router using no encryption at all which obviously is far from save. thanks in advance. >How-To-Repeat: >Fix: From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 15:36:51 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50EA4106564A for ; Fri, 28 Nov 2008 15:36:51 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id D543E8FC1D for ; Fri, 28 Nov 2008 15:36:50 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1942766ugs.39 for ; Fri, 28 Nov 2008 07:36:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer:sender; bh=OWI2qwD+iqinNRulKQqGa545UoPcbAwQy+xb9F4Vrvw=; b=QjwHd6/rrpBK96JOqiKQTQzAzgUH1RY/jvhUO22u/92b0IYWmh75Zg0PuBOwZ/jowN 9kjSlu5PZhei+VwjDvOwj4QJ6SlA9C7HHjno7fosI+l/dy4jhZ9ke5/Yb1WSrhzFltzA xjf1IKaDsR7qap9QZYzC6gzpBcLH2MvOY84Z0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer:sender; b=q798dDEm6Ac9L2Qdi44u3hxLR/fsCJ65iZoB56ZKnhaGWb7na63UwjvOXflFE4dcS4 4cd+32gV0eWGZgFKcBlTqemmQw29oReePri63p2uPlrfN8qMdftw3A/3lwlYUZt69v9W 26KwIs+TUGwpQm8KhwM7ubQXQ0OtslwK+FS0E= Received: by 10.103.248.17 with SMTP id a17mr3166552mus.97.1227886609457; Fri, 28 Nov 2008 07:36:49 -0800 (PST) Received: from ?172.17.0.182? ([193.136.24.184]) by mx.google.com with ESMTPS id e8sm2179640muf.53.2008.11.28.07.36.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 28 Nov 2008 07:36:48 -0800 (PST) Message-Id: <457EB70C-A3E6-4B3A-A707-CDE62FD2E8E0@fnop.net> From: Rui Paulo To: David Malone In-Reply-To: <200811271403.aa55110@walton.maths.tcd.ie> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Fri, 28 Nov 2008 15:36:45 +0000 References: <200811271403.aa55110@walton.maths.tcd.ie> X-Mailer: Apple Mail (2.929.2) Sender: Rui Paulo Cc: freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 28 Nov 2008 15:36:51 -0000 On 27 Nov 2008, at 14:03, David Malone wrote: > I was looking at some tcpdumps from a FreeBSD box receiving a TCP > stream with someone yesterday and noticed that it seemed to be > generating quite a lot of dupliacte acks. Looking more carefully, > we noticed that the duplicates were actually window updates. The > code for sending window updates can be found in: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c?annot > ate=1.157 > > around lines 541-565. It seems that we generate a window update if > the available buffer space changes by more than two packets, or if > it changes by more than half the buffer size. This is probably a > little aggressive, and in some cases seems to result in bursts of > window updates that look like they should be batched. I wonder if > it would make sense to not do a window update if a delayed ack is > scheduled? It might even be possible to do them as a delayed ack > without causing problems. Yes, this makes sense. Probably this is a bug since 4.4BSD-Lite. > I note that there is at least one PR mentioning we generate many > window updates: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=116335 > > I also wonder if it might cause non-FreeBSD senders to back off, > we are careful not to retransmit if we get window updates (see > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_input.c?annota > te=1.392 > > about line 1836, but other OSes might not be and that might degrade > our performance when receiving from a non-FreeBSD sender. So, from what I understand, we do back off and that implies we are losing performance in the FreeBSD to FreeBSD case, right? -- Rui Paulo From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 16:53:04 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C19F1065674 for ; Fri, 28 Nov 2008 16:53:04 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: from web58304.mail.re3.yahoo.com (web58304.mail.re3.yahoo.com [68.142.236.157]) by mx1.freebsd.org (Postfix) with SMTP id EA0F18FC08 for ; Fri, 28 Nov 2008 16:53:03 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: (qmail 57497 invoked by uid 60001); 28 Nov 2008 16:26:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=5Utts67klHw1RsQC2CV1OL6waGevB9v0KXY5+0lUue+NvzHe1i2rh2EgLiqSIhGybGKhVTqdjE+AfcioWBFph04R21yONgXSm+Q8ZoRGUDpgEAJP1aZ6gdPPenzTLDkfOs5IOwVpmPpvFPyjF0sxg+F+UbGa2FfUrif8AvgdJu8=; X-YMail-OSG: cbHm.ucVM1lWDw1bRM45cRKkecCvO9Wq.NxvMsOSHrqi6k14vqFFzTBnGPRAcfr3DuxVo2sXvf1VkGyWGI1juYvLWTz_HFyQW43VDAW_vv9FEXvdZCdwPal26YpROp9d4gcqNpR4OtP2mhZuTVgmmoiIfxZJ8GSHuozqBxdVofQkHgXKVn3Z6Z994gHG Received: from [70.112.131.248] by web58304.mail.re3.yahoo.com via HTTP; Fri, 28 Nov 2008 08:26:23 PST X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1 References: <200811271403.aa55110@walton.maths.tcd.ie> <457EB70C-A3E6-4B3A-A707-CDE62FD2E8E0@fnop.net> Date: Fri, 28 Nov 2008 08:26:23 -0800 (PST) From: Venkat Venkatsubra To: Rui Paulo , David Malone MIME-Version: 1.0 Message-ID: <725753.56771.qm@web58304.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 28 Nov 2008 16:53:04 -0000 By backoff if you are referring to sender side mistakenly counting the wind= ow updates=0Afor=A0a "fastretransmit" on a count of 3 dup acks, isn't the f= ollowing in tcp_input.c taking care of it ?=0A[Only when twin =3D=3D tp->sn= d_wnd it is counted as a dup ack.]=0A1836 if (SEQ_LEQ(th->th_ack, tp->snd_u= na)) {=0A1837 if (tlen =3D=3D 0 && tiwin =3D=3D tp->snd_wnd) {=0A1838 V_tcp= stat.tcps_rcvdupack++;=0A1839 /*=0A1840 * If we have outstanding data (othe= r than=0A1841 * a window probe), this is a completely=0A1842 * duplicate ac= k (ie, window info didn't=0A1843 * change), the ack is the biggest we've=0A= 1844 * seen and we've seen exactly our rexmt=0A1845 * threshhold of them, a= ssume a packet=0A1846 * has been dropped and retransmit it.=0A1847 * Kludge= snd_nxt & the congestion=0A1848 * window so we send only this one=0A1849 *= packet.=0A1850 *=0AHow many acks do you see for every 2 full-sized segment= s received ? 2 or 1 ?=0AAt least one ack needs to go out for every 2 incomi= ng segments as per the rfc.=0AAssociating window updates with delayed ack= =A0was not clear to me.=0AIf I see the tcpdump output I might understand be= tter.=0A=0AVenkat=0A=0A=0A________________________________=0AFrom: Rui Paul= o =0ATo: David Malone =0ACc: freebs= d-net@freebsd.org; Kevin Oberman =0ASent: Friday, November = 28, 2008 9:36:45 AM=0ASubject: Re: FreeBSD Window updates=0A=0A=0AOn 27 Nov= 2008, at 14:03, David Malone wrote:=0A=0A> I was looking at some tcpdumps = from a FreeBSD box receiving a TCP=0A> stream with someone yesterday and no= ticed that it seemed to be=0A> generating quite a lot of dupliacte acks. Lo= oking more carefully,=0A> we noticed that the duplicates were actually wind= ow updates. The=0A> code for sending window updates can be found in:=0A>=0A= > =A0=A0=A0 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_outpu= t.c?annot=0A> ate=3D1.157=0A>=0A> around lines 541-565. It seems that we ge= nerate a window update if=0A> the available buffer space changes by more th= an two packets, or if=0A> it changes by more than half the buffer size. Thi= s is probably a=0A> little aggressive, and in some cases seems to result in= bursts of=0A> window updates that look like they should be batched. I wond= er if=0A> it would make sense to not do a window update if a delayed ack is= =0A> scheduled? It might even be possible to do them as a delayed ack=0A> w= ithout causing problems.=0A=0AYes, this makes sense. Probably this is a bug= since 4.4BSD-Lite.=0A=0A> I note that there is at least one PR mentioning = we generate many=0A> window updates:=0A>=0A> =A0=A0=A0 http://www.freebsd.o= rg/cgi/query-pr.cgi?pr=3D116335=0A>=0A> I also wonder if it might cause non= -FreeBSD senders to back off,=0A> we are careful not to retransmit if we ge= t window updates (see=0A>=0A> =A0=A0=A0 http://www.freebsd.org/cgi/cvsweb.c= gi/src/sys/netinet/tcp_input.c?annota=0A> te=3D1.392=0A>=0A> about line 183= 6, but other OSes might not be and that might degrade=0A> our performance w= hen receiving from a non-FreeBSD sender.=0A=0A=0ASo, from what I understand= , we do back off and that implies we are=A0 =0Alosing performance in the Fr= eeBSD to FreeBSD case, right?=0A=0A--=0ARui Paulo=0A=0A____________________= ___________________________=0Afreebsd-net@freebsd.org mailing list=0Ahttp:/= /lists.freebsd.org/mailman/listinfo/freebsd-net=0ATo unsubscribe, send any = mail to "freebsd-net-unsubscribe@freebsd.org"=0A=0A=0A From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 18:14:15 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316631065675; Fri, 28 Nov 2008 18:14:15 +0000 (UTC) (envelope-from sam@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0B33F8FC0C; Fri, 28 Nov 2008 18:14:15 +0000 (UTC) (envelope-from sam@FreeBSD.org) Received: from freefall.freebsd.org (sam@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mASIEEEE022246; Fri, 28 Nov 2008 18:14:14 GMT (envelope-from sam@freefall.freebsd.org) Received: (from sam@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mASIEEli022242; Fri, 28 Nov 2008 18:14:14 GMT (envelope-from sam) Date: Fri, 28 Nov 2008 18:14:14 GMT Message-Id: <200811281814.mASIEEli022242@freefall.freebsd.org> To: sam@FreeBSD.org, freebsd-net@FreeBSD.org, sam@FreeBSD.org From: sam@FreeBSD.org Cc: Subject: Re: kern/129022: [ath] ath cannot connect using WEP 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, 28 Nov 2008 18:14:15 -0000 Synopsis: [ath] ath cannot connect using WEP Responsible-Changed-From-To: freebsd-net->sam Responsible-Changed-By: sam Responsible-Changed-When: Fri Nov 28 18:13:53 UTC 2008 Responsible-Changed-Why: didn't know this existed; will check http://www.freebsd.org/cgi/query-pr.cgi?pr=129022 From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 19:36:09 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB0361065676 for ; Fri, 28 Nov 2008 19:36:09 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 09AE78FC1D for ; Fri, 28 Nov 2008 19:36:08 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 28 Nov 2008 19:36:07 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by walton.maths.tcd.ie with SMTP id ; 28 Nov 2008 19:36:04 +0000 (GMT) To: Rui Paulo In-reply-to: Your message of "Fri, 28 Nov 2008 15:36:45 GMT." <457EB70C-A3E6-4B3A-A707-CDE62FD2E8E0@fnop.net> Date: Fri, 28 Nov 2008 19:36:04 +0000 From: David Malone Message-ID: <200811281936.aa78374@walton.maths.tcd.ie> Cc: freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 28 Nov 2008 19:36:09 -0000 > Yes, this makes sense. Probably this is a bug since 4.4BSD-Lite. I had a look to see what Linux does - it only generates pure window updates in the case that the advertised window would change by a factor of two. I guess this practically eliminates these updates. I would guess that changing the code to update on a change of a power of two would be OK. Another option would be to change the current limit of two MSSes to three, because this would eliminate window updates between regular delayed ACKs. > So, from what I understand, we do back off and that implies we are > losing performance in the FreeBSD to FreeBSD case, right? We do the right thing and ignore these pure window updates. I've checked, and Linux also ignores ACKs that just seem to update the window. David. From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 20:40:48 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE8AF1065674 for ; Fri, 28 Nov 2008 20:40:48 +0000 (UTC) (envelope-from mamruoc@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 3F4B28FC13 for ; Fri, 28 Nov 2008 20:40:48 +0000 (UTC) (envelope-from mamruoc@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1022936fgb.35 for ; Fri, 28 Nov 2008 12:40:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=FPsT/a0PfIAE2lyD5fDsACBIgHKJA9DZYrUcV+dNBOE=; b=rJkyjeYzlrkB+hZfBdZxNMkrlAuaMgSNGMfaZY3FFAw0hOnOFhGqmoBIiBnOiaLzgu s0Ved9ub/1zxz+JKj3U8ydY6kN/moaiDtU0ahruPrC3fxUwnToiz71k5vvo7mzVUGugo ff+CLnSzoB0JWEmQLBCtaIyueogTeh3jVd28Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=mY++k7wWS58BJswINjq49s2KiMoONbV+IhqxAqnUrDFjyGXaqDbWE1ciaQdfWqzFZp Zc4wJbTgA6rFpuKCl/VML6jWadnRbzwZA9rXT+q5e/G3CGnfp5iXhpDezU0hYcrIMyjV PxVPDxvTVfb2vhE8Luv9+ScfrWs9qLhVRqDhs= Received: by 10.181.239.8 with SMTP id q8mr2901227bkr.1.1227903635819; Fri, 28 Nov 2008 12:20:35 -0800 (PST) Received: by 10.181.221.2 with HTTP; Fri, 28 Nov 2008 12:20:35 -0800 (PST) Message-ID: <4d591a210811281220o7bdd420uafec124fc7e770a8@mail.gmail.com> Date: Fri, 28 Nov 2008 21:20:35 +0100 From: "Mam Ruoc" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: vge driver does not work on a VIA EPIA EN12000EG 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, 28 Nov 2008 20:40:48 -0000 Onboard LAN: VIA VT6122 GLAN Controller I have submitted a bug report, but has not heard anything, can anybody help me because this is a big showstopper! http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/129135 Mam Ruoc From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 02:00:07 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 991B81065673; Sat, 29 Nov 2008 02:00:06 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5D0DE8FC13; Sat, 29 Nov 2008 02:00:06 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mAT206oL016579; Sat, 29 Nov 2008 02:00:06 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mAT205Ou016575; Sat, 29 Nov 2008 02:00:05 GMT (envelope-from kris) Date: Sat, 29 Nov 2008 02:00:05 GMT Message-Id: <200811290200.mAT205Ou016575@freefall.freebsd.org> To: kes-kes@yandex.ru, kris@FreeBSD.org, freebsd-net@FreeBSD.org From: kris@FreeBSD.org Cc: Subject: Re: kern/129074: [ppp] [panic] kernel panic with pppoe_server 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, 29 Nov 2008 02:00:07 -0000 Synopsis: [ppp] [panic] kernel panic with pppoe_server State-Changed-From-To: open->feedback State-Changed-By: kris State-Changed-When: Sat Nov 29 01:59:30 UTC 2008 State-Changed-Why: Please provide some details so we can begin to investigate your problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=129074 From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 07:02:04 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28D27106564A for ; Sat, 29 Nov 2008 07:02:04 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by mx1.freebsd.org (Postfix) with ESMTP id A6D9D8FC08 for ; Sat, 29 Nov 2008 07:02:03 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so1112466tib.3 for ; Fri, 28 Nov 2008 23:02:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=KonvSd5hXyEOXSa14/fSembfzvDdP8KjqZBKRPP8qHk=; b=imkHDdxXGZH8lb0SrSusYLvyQ0ZrMD581P9zl5aE9MRgZ26z4H2QrsXmkqEKh/HJcZ f3wrh3DeIrzsZ92mlW2icLPQkm0G5t5VIPOV1MNSsaM6SqDd4zH/cc1c2bUg3iE76wVB qcogK1jGkG3dtISkfkGJcE1ZQFdpCvbpPqFDM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=GfZB6tRNcebFqr2Py49+K97E7Y25kngdQQxQL88jVW+i5n3UQpJInCxBEVRPT/3HR+ GzLL4Fz5WWF6q83zLCNzVJJbU7ZOmxES7KyE13T4YQQWLCZKzk82Nex3ESS3Tf7sRK7J mxjBWfV2QrMKngr34SEcCbPmWPdikhy0AjWeI= Received: by 10.110.49.2 with SMTP id w2mr13078520tiw.23.1227942122665; Fri, 28 Nov 2008 23:02:02 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b4sm3788852tic.2.2008.11.28.23.01.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 28 Nov 2008 23:01:55 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mAT6xpk5000630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Nov 2008 15:59:51 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mAT6xpsn000629; Sat, 29 Nov 2008 15:59:51 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 29 Nov 2008 15:59:50 +0900 From: Pyun YongHyeon To: Mam Ruoc Message-ID: <20081129065950.GG99324@cdnetworks.co.kr> References: <4d591a210811281220o7bdd420uafec124fc7e770a8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d591a210811281220o7bdd420uafec124fc7e770a8@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: vge driver does not work on a VIA EPIA EN12000EG X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2008 07:02:04 -0000 On Fri, Nov 28, 2008 at 09:20:35PM +0100, Mam Ruoc wrote: > Onboard LAN: VIA VT6122 GLAN Controller > > I have submitted a bug report, but has not heard anything, can anybody > help me because this is a big showstopper! > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/129135 > I think there was a similar report. Would you show me the output of "pciconf -lcv"? For a long time I wanted to clean up vge(4). Unfortunately the PCI NIC I have seem to broken so I guess it's hard to complete the cleanup. You can get a WIP(now stalled) in the following URL. Note, the driver may be chatty due to various debugging statements and it may not work at all for your controller. http://people.freebsd.org/~yongari/vge/if_vge.c http://people.freebsd.org/~yongari/vge/if_vgereg.h http://people.freebsd.org/~yongari/vge/if_vgevar.h -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 07:27:37 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3D60106564A for ; Sat, 29 Nov 2008 07:27:37 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 5B84D8FC21 for ; Sat, 29 Nov 2008 07:27:37 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id EFB7A1788B; Sat, 29 Nov 2008 18:27:34 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-10-138.lns10.syd7.internode.on.net [121.44.10.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 2D859171BF; Sat, 29 Nov 2008 18:27:27 +1100 (EST) Message-ID: <4930EE38.8010808@modulus.org> Date: Sat, 29 Nov 2008 18:24:40 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: pyunyh@gmail.com, FreeBSD Net , mamruoc@gmail.com References: <4d591a210811281220o7bdd420uafec124fc7e770a8@mail.gmail.com> <20081129065950.GG99324@cdnetworks.co.kr> In-Reply-To: <20081129065950.GG99324@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: vge driver does not work on a VIA EPIA EN12000EG 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, 29 Nov 2008 07:27:37 -0000 Yes it does! We have deployed many 7.0-STABLE routers based on the EPIA EN12000E motherboard, and found that vge works really well, never had any major problems with it - don't touch it! :-) I suspect the OP should try a newer version of FreeBSD than 7.0-RELEASE which was so long ago. vge0@pci0:0:14:0: class=0x020000 card=0x01101106 chip=0x31191106 rev=0x11 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6120/VT6121/VT6122 'Velocity' Gigabit Ethernet Controllers' class = network subclass = ethernet vge0: port 0xf800-0xf8ff mem 0xfdffe000-0xfdffe0ff irq 10 at device 14.0 on pci0 miibus0: on vge0 ciphy0: PHY 1 on miibus0 From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 08:14:58 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7A0E106564A; Sat, 29 Nov 2008 08:14:58 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forwards4.yandex.ru (forwards4.yandex.ru [77.88.32.20]) by mx1.freebsd.org (Postfix) with ESMTP id 1EF7A8FC08; Sat, 29 Nov 2008 08:14:57 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from smtp12.yandex.ru (smtp12.yandex.ru [77.88.32.82]) by forwards4.yandex.ru (Yandex) with ESMTP id CE3024C5F47; Sat, 29 Nov 2008 10:59:33 +0300 (MSK) Received: from 124-80-113-92.pool.ukrtel.net ([92.113.80.124]:46088 "EHLO kes" smtp-auth: "kes-kes" TLS-CIPHER: TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S5325777AbYK2H71 (ORCPT + 1 other); Sat, 29 Nov 2008 10:59:27 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp12 X-Yandex-TimeMark: 1227945567 X-BornDate: 1149541200 X-Yandex-Karma: 0 X-Yandex-KarmaStatus: 0 X-MsgDayCount: 5 X-Comment: RFC 2476 MSA function at smtp12.yandex.ru logged sender identity as: kes-kes Date: Sat, 29 Nov 2008 09:59:12 +0200 From: KES X-Mailer: The Bat! (v4.0.24) Professional Organization: SaftTen X-Priority: 3 (Normal) Message-ID: <788223423.20081129095912@yandex.ru> To: kris@FreeBSD.org In-Reply-To: <200811290200.mAT205Ou016575@freefall.freebsd.org> References: <200811290200.mAT205Ou016575@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org Subject: Re[2]: kern/129074: [ppp] [panic] kernel panic with pppoe_server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: KES List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2008 08:14:58 -0000 Здравствуйте, Kris. Вы писали 29 ноября 2008 г., 4:00:05: kFo> Synopsis: [ppp] [panic] kernel panic with pppoe_server kFo> State-Changed-From-To: open->feedback kFo> State-Changed-By: kris kFo> State-Changed-When: Sat Nov 29 01:59:30 UTC 2008 kFo> State-Changed-Why: kFo> Please provide some details so we can begin to investigate your problem. kFo> http://www.freebsd.org/cgi/query-pr.cgi?pr=129074 /etc/ppp/ppp.conf default: set log Phase Chat LCP IPCP CCP tun command adsl: set log Phase LCP tun command set device PPPoE:rl0:ukrtelecom # enable lqr # enable dns disable ipv6cp set cd 10 set dial # set login set redial 0 0 set reconnect random 999 set mtu 1492 set mru 1492 set authname name set authkey password # add! default HISADD Kernel panic and server reboot if my ISP response: ppp[348]: tun0: Phase: Pap Input: FAILURE (insufficient resources available to authenticate user) or ppp[348]: tun0: Phase: Pap Output: ******** last message repeated 2 times ppp[348]: tun0: Phase: Auth: No response from server -- С уважением, KES mailto:kes-kes@yandex.ru From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 13:43:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C497F106564A for ; Sat, 29 Nov 2008 13:43:05 +0000 (UTC) (envelope-from mamruoc@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.180]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD108FC14 for ; Sat, 29 Nov 2008 13:43:05 +0000 (UTC) (envelope-from mamruoc@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so1580850ika.3 for ; Sat, 29 Nov 2008 05:43:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Q/KIhob4E2l4UAyZpr5tRlafRDz4uUrTLg8AzyOt4Fw=; b=drzQDhi/z3j0zaGlkxGmnSI0kGEvu+IkgrP6re6D0uyvlMBOOmD7K9b5Z8aK3GlJYr pZm48qf+r3bYaGWbLDzIn9S+vI0n7CrKZQsBL4owKWV4oaVSTmgm58ifqVAZutKvo/KO pTcJREWo4iG4NUH65CJi7hxDGBXpLC+Yy8Ex8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=k+6e8kRvub5e8u+/6QS2FxaPGZwDuoz54wk/mxr6/d/tEkhMf7UcQwLwn3to1q5xEx AvFR6/oZ9M0rVxt8QSr0lk5AuvkctAa39Fg2jdEXsNrRoJ5U2a5g1/CORMNQ2lHU+xk1 Euip/hzi3Cm9wW1LtgMgZFtmSxKCZ9b4L2YTA= Received: by 10.210.25.19 with SMTP id 19mr7398492eby.114.1227966184171; Sat, 29 Nov 2008 05:43:04 -0800 (PST) Received: from ?192.168.1.136? (217-14-12-152-dhcp-osl.bbse.no [217.14.12.152]) by mx.google.com with ESMTPS id f6sm10253106nfh.12.2008.11.29.05.43.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 29 Nov 2008 05:43:03 -0800 (PST) Message-ID: <493146DD.20201@gmail.com> Date: Sat, 29 Nov 2008 14:42:53 +0100 From: Mam Ruoc User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Andrew Snow References: <4d591a210811281220o7bdd420uafec124fc7e770a8@mail.gmail.com> <20081129065950.GG99324@cdnetworks.co.kr> <4930EE38.8010808@modulus.org> In-Reply-To: <4930EE38.8010808@modulus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, FreeBSD Net Subject: Re: vge driver does not work on a VIA EPIA EN12000EG 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, 29 Nov 2008 13:43:05 -0000 Hi! Andrew Snow wrote: > We have deployed many 7.0-STABLE routers based on the EPIA EN12000E > motherboard, and found that vge works really well, never had any major > problems with it - don't touch it! :-) Unsure if it's the EPIA EN12000E (not EPIA EN12000EG) or you're using STABLE, but I will try stable. > I suspect the OP should try a newer version of FreeBSD than 7.0-RELEASE > which was so long ago. You know where I can get hold of a more recent bootonly-7.0-STABLE iso? I am reporting this bug because I use pfSense which has moved from FreeBSD 6.3 to 7.0 and that made my VIA useless. They said it was a FreeBSD problem and therefore I am here. Mam From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 14:10:17 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B4CF106564A for ; Sat, 29 Nov 2008 14:10:17 +0000 (UTC) (envelope-from mamruoc@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.180]) by mx1.freebsd.org (Postfix) with ESMTP id A720A8FC08 for ; Sat, 29 Nov 2008 14:10:16 +0000 (UTC) (envelope-from mamruoc@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so1588128ika.3 for ; Sat, 29 Nov 2008 06:10:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=CBmUZjXVZKjjEfBIxoalwbt26lWnSc/qDo7qEe88dhM=; b=bZ+Dx3w1xnOja0ajv3XwWbtCVWqGWMcYaLj2oHcFd7dg1tnMF9sWP9kgh+To/r7CDC TQLjgoAWWH7vJyIR/ZMXTE2Ss5um0IXUXC1pm0fQqq3vGYRV/cyT25hf4H2Oko9r0EaB IdiDo7nRxbSmXj95zG6miq78bliRYfIXMiepU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=CJsUvxopAhPUUkp2uCNZk6JISgHy4vucV3qBDxsBiepFZCxDxAxDE3mTiq1VsldT7z nDbzyxiasWARLGVMUWKdonjh1FatMneJFlGZyPbwxNEM1tsx7Ul3lQoCKjP/5KXSikch KkziP2Jihj55YDz6Ft5ZoU+/oU6UeI9nvMmQI= Received: by 10.210.22.8 with SMTP id 8mr10208582ebv.46.1227967815680; Sat, 29 Nov 2008 06:10:15 -0800 (PST) Received: from ?192.168.1.136? (217-14-12-152-dhcp-osl.bbse.no [217.14.12.152]) by mx.google.com with ESMTPS id 6sm10342818nfv.8.2008.11.29.06.10.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 29 Nov 2008 06:10:15 -0800 (PST) Message-ID: <49314D3C.4050108@gmail.com> Date: Sat, 29 Nov 2008 15:10:04 +0100 From: Mam Ruoc User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4d591a210811281220o7bdd420uafec124fc7e770a8@mail.gmail.com> <20081129065950.GG99324@cdnetworks.co.kr> In-Reply-To: <20081129065950.GG99324@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: vge driver does not work on a VIA EPIA EN12000EG 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, 29 Nov 2008 14:10:17 -0000 Pyun YongHyeon wrote: > I think there was a similar report. Would you show me the output of > "pciconf -lcv"? I'll try, unsure how to manage. Have tried to use Fixit in sysinstall to create a new shell, but Ghost-something did not have lspci, where can I find freebsd livecd? > For a long time I wanted to clean up vge(4). Unfortunately the PCI > NIC I have seem to broken so I guess it's hard to complete the > cleanup. You can get a WIP(now stalled) in the following URL. Note, > the driver may be chatty due to various debugging statements and it > may not work at all for your controller. > > http://people.freebsd.org/~yongari/vge/if_vge.c > http://people.freebsd.org/~yongari/vge/if_vgereg.h > http://people.freebsd.org/~yongari/vge/if_vgevar.h As I said in the other mail, unsure how to do this because I actually ned the fix because pfSense 1.2.1RC2 have this problem and made my VIA useless as a firewall. Mam From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 15:59:55 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22A0A1065675 for ; Sat, 29 Nov 2008 15:59:55 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: from web58307.mail.re3.yahoo.com (web58307.mail.re3.yahoo.com [68.142.236.160]) by mx1.freebsd.org (Postfix) with SMTP id C92038FC3C for ; Sat, 29 Nov 2008 15:59:54 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: (qmail 13927 invoked by uid 60001); 29 Nov 2008 15:59:54 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=NLcgzuN7/eS1hA3OBvWBG5nRY5LFL4iy7GoVKG6hxJVogDcyRHynvMPSqaJOY8gY4ZjMt7/z6Y903NAkjM7RclGQGW4wW6LwJ0BVdj00F74NjhzwTESHORr8lYlFjRASowIjzLobQfPhpwWGGCeyQUjl3nC2u1TUBUNb8sexOr4=; X-YMail-OSG: F.ax8ZIVM1kTlURDH1lk8Jl620Kg4kMVIdHIcq9FvcW0rR.wbQLtxxPhNg_bP_4jf0iMo._mSHgVsrijWCzYTf_KE0kRKGsYmkFarysSbM_CcGX7k.D6RLXzx1Qi7r0KaqsWx5KO6O.nUb2ge9X3oeCiwQd42kHfcKI4jAnTOVQbbV7Rj4ttvdLr88wN Received: from [70.112.131.248] by web58307.mail.re3.yahoo.com via HTTP; Sat, 29 Nov 2008 07:59:54 PST X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1 References: <200811281936.aa78374@walton.maths.tcd.ie> Date: Sat, 29 Nov 2008 07:59:54 -0800 (PST) From: Venkat Venkatsubra To: David Malone , Rui Paulo MIME-Version: 1.0 Message-ID: <88524.13498.qm@web58307.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 29 Nov 2008 15:59:55 -0000 Looking at some very old versions (4.3 BSD Reno for instance),=0Athe regula= r acks used to be=A0sent only through these=A0window updates.=0Ai.e. acks w= ere sent only when the apps read the data. Acks are piggybacked=0Awith wind= ow updates. Or, delayed till the delayed ack timer expires if the apps=0Ais= not reading. This would have had other issues with congestion control due = to generating=0Atoo few acks. When this was changed to send acks independen= t of apps reading the data,=0Awe=A0now have lot more acks due to these wind= ow updates in addition to the regular acks.=0A=0AVenkat=0A=0A=0A___________= _____________________=0AFrom: David Malone =0ATo: Ru= i Paulo =0ACc: freebsd-net@freebsd.org; Kevin Oberman =0ASent: Friday, November 28, 2008 1:36:04 PM=0ASubject: Re: Fr= eeBSD Window updates=0A=0A> Yes, this makes sense. Probably this is a bug s= ince 4.4BSD-Lite.=0A=0AI had a look to see what Linux does - it only genera= tes pure window=0Aupdates in the case that the advertised window would chan= ge by a=0Afactor of two. I guess this practically eliminates these updates.= =0A=0AI would guess that changing the code to update on a change of a=0Apow= er of two would be OK. Another option would be to change the=0Acurrent limi= t of two MSSes to three, because this would eliminate=0Awindow updates betw= een regular delayed ACKs.=0A=0A> So, from what I understand, we do back off= and that implies we are=A0 =0A> losing performance in the FreeBSD to FreeB= SD case, right?=0A=0AWe do the right thing and ignore these pure window upd= ates. I've=0Achecked, and Linux also ignores ACKs that just seem to update = the=0Awindow.=0A=0A=A0=A0=A0 David.=0A_____________________________________= __________=0Afreebsd-net@freebsd.org mailing list=0Ahttp://lists.freebsd.or= g/mailman/listinfo/freebsd-net=0ATo unsubscribe, send any mail to "freebsd-= net-unsubscribe@freebsd.org"=0A=0A=0A=0A From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 16:37:28 2008 Return-Path: Delivered-To: net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B0321065731 for ; Sat, 29 Nov 2008 16:37:28 +0000 (UTC) (envelope-from apache@vulcan.highspd.net) Received: from vulcan.highspd.net (vulcan.highspd.net [66.199.31.170]) by mx1.freebsd.org (Postfix) with ESMTP id EE3FA8FC08 for ; Sat, 29 Nov 2008 16:37:27 +0000 (UTC) (envelope-from apache@vulcan.highspd.net) Received: from vulcan.highspd.net (vulcan.highspd.net [127.0.0.1]) by vulcan.highspd.net (8.12.11/8.12.11) with ESMTP id mATG3bqC016643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 29 Nov 2008 10:03:37 -0600 Received: (from apache@localhost) by vulcan.highspd.net (8.12.11/8.12.11/Submit) id mATG3b3o016642; Sat, 29 Nov 2008 10:03:37 -0600 Date: Sat, 29 Nov 2008 10:03:37 -0600 Message-Id: <200811291603.mATG3b3o016642@vulcan.highspd.net> To: net@FreeBSD.ORG From: "Col. Salva Taha (Rtd)" MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Cc: Subject: PROPERTIES. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: salvataha1@live.co.za List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2008 16:37:28 -0000 Good Day, I wish to introduce myself to you.I am Col.Salva Taha a top Sudanese Goverment official who opposed the war in Dafur in my country Sudan.Due to my oppostion to the war,the goverment of my country has been persecuting me.Consequently my wife,children and I managed to enter a red cross air plane that was evacuating foreigners and we are presently in Cape Town,South Africa. We wish to invest in properties in your country with your assistance and cooperation.If you are in a good position to help my family, please send an email to the email address below indicating your desire to help my family invest the funds in your country and beyond. I urgently await your email. best regards. God bless, Col. Salva Taha (Rtd) Email:salvataha1@live.co.za From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 17:46:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9680B1065678 for ; Sat, 29 Nov 2008 17:46:36 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id C0D508FC1E for ; Sat, 29 Nov 2008 17:46:35 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 29 Nov 2008 17:46:34 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by walton.maths.tcd.ie with SMTP id ; 29 Nov 2008 17:46:31 +0000 (GMT) To: Venkat Venkatsubra In-reply-to: Your message of "Sat, 29 Nov 2008 07:59:54 PST." <88524.13498.qm@web58307.mail.re3.yahoo.com> Date: Sat, 29 Nov 2008 17:46:30 +0000 From: David Malone Message-ID: <200811291746.aa88825@walton.maths.tcd.ie> Cc: Rui Paulo , freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 29 Nov 2008 17:46:36 -0000 I've got an example extract tcpdump of this at the end of the mail - here 6 ACKs are sent, 5 of which are pure window updates and several are 2us apart! I think the easy option is to delete the code that generates explicit window updates if the window moves by 2*MSS. We then should be doing something similar to Linux. The other easy alternative would be to add a sysclt that lets us generate an window update every N*MSS and by default set it to something big, like 10 or 100. That should effectively eliminate the updates during bulk data transfer, but may still generate some window updates after a loss. Normal ACKing for driving congestion control shouldn't be impacted by either of these suggested changes. David. 1227622713.276609 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40798 (DF) 1227622713.276611 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40830 (DF) 1227622713.276613 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40862 (DF) 1227622713.276615 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40894 (DF) 1227622713.276852 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40926 (DF) 1227622713.276855 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40958 (DF) 1227622713.296585 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144100641 win 40956 (DF) From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 20:33:17 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67A961065675 for ; Sat, 29 Nov 2008 20:33:17 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from kennaway-macbookpro.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5AF8FC0C; Sat, 29 Nov 2008 20:33:17 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4931A70C.30708@FreeBSD.org> Date: Sat, 29 Nov 2008 12:33:16 -0800 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: KES References: <200811290200.mAT205Ou016575@freefall.freebsd.org> <788223423.20081129095912@yandex.ru> In-Reply-To: <788223423.20081129095912@yandex.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org Subject: Re: kern/129074: [ppp] [panic] kernel panic with pppoe_server 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, 29 Nov 2008 20:33:17 -0000 KES wrote: > Здравствуйте, Kris. > > Вы писали 29 ноября 2008 г., 4:00:05: > > kFo> Synopsis: [ppp] [panic] kernel panic with pppoe_server > > kFo> State-Changed-From-To: open->feedback > kFo> State-Changed-By: kris > kFo> State-Changed-When: Sat Nov 29 01:59:30 UTC 2008 > kFo> State-Changed-Why: > kFo> Please provide some details so we can begin to investigate your problem. > > kFo> http://www.freebsd.org/cgi/query-pr.cgi?pr=129074 > > /etc/ppp/ppp.conf > default: > set log Phase Chat LCP IPCP CCP tun command > > adsl: > set log Phase LCP tun command > set device PPPoE:rl0:ukrtelecom > # enable lqr > # enable dns > disable ipv6cp > set cd 10 > set dial > # set login > set redial 0 0 > set reconnect random 999 > set mtu 1492 > set mru 1492 > set authname name > set authkey password > # add! default HISADD > > Kernel panic and server reboot if my ISP response: > ppp[348]: tun0: Phase: Pap Input: FAILURE (insufficient resources available to authenticate user) > or > ppp[348]: tun0: Phase: Pap Output: ******** > last message repeated 2 times > ppp[348]: tun0: Phase: Auth: No response from server > > Please provide details of the panic too. See the developers handbook chapter on kernel debugging for full instructions. Kris From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 20:39:50 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6C6E1065670 for ; Sat, 29 Nov 2008 20:39:50 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: from web58304.mail.re3.yahoo.com (web58304.mail.re3.yahoo.com [68.142.236.157]) by mx1.freebsd.org (Postfix) with SMTP id 9B6CC8FC25 for ; Sat, 29 Nov 2008 20:39:50 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: (qmail 94704 invoked by uid 60001); 29 Nov 2008 20:39:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=oDUpg8LE1Ug6BD8friREb82glHc/QwnL4TPO6XttR4aUScKzatXzxqUhUmlt9HNoqITM4M0ZYGxnpBH4p9Jed1cGK0e+7/Ks5cc0kncCuhFCy3Q44/AzO6dJSs8GSx6SwAxhFK6UH/GmBv9CmflN8vpQhHz7DDyV+1uvBpQzPhU=; X-YMail-OSG: 4sC7_gYVM1mjIeF62ZOBBYYTXGZzpiGpGB7SK09HNYLUpYwkfOXwuh9J71Nbk1WiMWMylLPqDNM6krOu_JWUL1qacB3nvxyNRAhdIiCBPm9nXYdwWysPF0kkIZBDSI6AqNavIyqNY3cb0JwSOGmTruFZHCkgm.ZfvD1xcCvZeN1hF5n1wcV2d39kTlpD Received: from [70.112.131.248] by web58304.mail.re3.yahoo.com via HTTP; Sat, 29 Nov 2008 12:39:49 PST X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1 References: <200811291746.aa88825@walton.maths.tcd.ie> Date: Sat, 29 Nov 2008 12:39:49 -0800 (PST) From: Venkat Venkatsubra To: David Malone MIME-Version: 1.0 Message-ID: <10716.94191.qm@web58304.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Rui Paulo , freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 29 Nov 2008 20:39:51 -0000 Hi David,=0A=0AAssuming each of these 5 window updates are sent after the a= pps=0Acompleted the=A0read that it issued, what's the buffer size the apps = is passing=0Ato the read ? If it is small, could that be increased ?=0A=0AB= ut I agree with you that there is room for optimizing sending of these wind= ow updates.=0A=0A(Since I don't know the window scale factor for the connec= tion, I couldn't figure out=0Ahow much each of the window updates was openi= ng up the window.)=0A=0AVenkat=0A=0A=0A________________________________=0AF= rom: David Malone =0ATo: Venkat Venkatsubra =0ACc: Rui Paulo ; freebsd-net@freebs= d.org; Kevin Oberman =0ASent: Saturday, November 29, 2008 1= 1:46:30 AM=0ASubject: Re: FreeBSD Window updates=0A=0AI've got an example e= xtract tcpdump of this at the end of the mail=0A- here 6 ACKs are sent, 5 o= f which are pure window updates and=0Aseveral are 2us apart!=0A=0AI think t= he easy option is to delete the code that generates explicit=0Awindow updat= es if the window moves by 2*MSS. We then should be doing=0Asomething simila= r to Linux. The other easy alternative would be to=0Aadd a sysclt that lets= us generate an window update every N*MSS and=0Aby default set it to someth= ing big, like 10 or 100. That should=0Aeffectively eliminate the updates du= ring bulk data transfer, but=0Amay still generate some window updates after= a loss.=0A=0ANormal ACKing for driving congestion control shouldn't be imp= acted=0Aby either of these suggested changes.=0A=0A=A0=A0=A0 David.=0A=0A12= 27622713.276609 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40= 798 (DF)=0A1227622713.276611 172.16.2.2= .5002 > 172.16.1.51.39077: . ack 144097745 win 40830 (DF)=0A1227622713.276613 172.16.2.2.5002 > 172.16.1.51.39077:= . ack 144097745 win 40862 (DF)=0A12276= 22713.276615 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144097745 win 40894= (DF)=0A1227622713.276852 172.16.2.2.50= 02 > 172.16.1.51.39077: . ack 144097745 win 40926 (DF)=0A1227622713.276855 172.16.2.2.5002 > 172.16.1.51.39077: . = ack 144097745 win 40958 (DF)=0A12276227= 13.296585 172.16.2.2.5002 > 172.16.1.51.39077: . ack 144100641 win 40956 (DF)=0A__________________________________= _____________=0Afreebsd-net@freebsd.org mailing list=0Ahttp://lists.freebsd= .org/mailman/listinfo/freebsd-net=0ATo unsubscribe, send any mail to "freeb= sd-net-unsubscribe@freebsd.org"=0A=0A=0A=0A From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 20:47:00 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 734A7106564A for ; Sat, 29 Nov 2008 20:47:00 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id CE1D28FC1B for ; Sat, 29 Nov 2008 20:46:59 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 29 Nov 2008 20:46:56 +0000 (GMT) To: Venkat Venkatsubra In-reply-to: Your message of "Sat, 29 Nov 2008 12:39:49 PST." <10716.94191.qm@web58304.mail.re3.yahoo.com> X-Request-Do: Date: Sat, 29 Nov 2008 20:46:53 +0000 From: David Malone Message-ID: <200811292046.aa42834@salmon.maths.tcd.ie> Cc: Rui Paulo , freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 29 Nov 2008 20:47:00 -0000 > Each of these 5 window updates are sent after the apps completed the read > that it issued, what's the buffer size the apps is passing to the read? > If it is small, could that be increased? I'm not actually sure - the app is iperf. The window scaling factor is 8 here I think. > But I agree with you that there is room for optimizing sending of these > window updates. Any feeling for which would be the better fix? David. From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 20:55:25 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA0041065789 for ; Sat, 29 Nov 2008 20:55:25 +0000 (UTC) (envelope-from Mykel@mWare.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.freebsd.org (Postfix) with ESMTP id C84EF8FC18 for ; Sat, 29 Nov 2008 20:55:25 +0000 (UTC) (envelope-from Mykel@mWare.ca) Received: from fulgidous.condor.lan (radix.mWare.ca [72.0.75.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ox.eicat.ca (Postfix) with ESMTP id 9CE00B998 for ; Sat, 29 Nov 2008 15:27:35 -0500 (EST) Message-ID: <4931A5B6.1060000@mWare.ca> Date: Sat, 29 Nov 2008 15:27:34 -0500 From: Mykel User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Determining counts or size of routing table? (netstat performance?) 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, 29 Nov 2008 20:55:26 -0000 Got a few 6.x machines running OpenBGPd with a few BGP full-feeds and a handful of peers... I'd like to determine the size of the FIB/kernel routing table. OpenBGPd does not give me this data, and on my duallie-Xeon 2.8s, it takes quite a while to use netstat & wc to count. I'm not looking for exact numbers, just something I can poll via NetSNMP and plot in cacti... I looked though netstat, route, sysctl, vmstat, even pored over an snmpwalk... can't find anything. Been asking around, and the only suggestion I've received was to write a daemon that dumps the table and then monitors the changes, but I'm not a programmer, nor could I find any tool in ports that might assist in this. I'd be happy with almost any metric that gives me some absolute reference as to how big my routing table is so I can get some nice pretty graphs done up. Not pounding the system every 60-300 seconds would be very nice. Any suggestions? Or does everyone just pipe netstat? Is there a MIB for sysctl or NetSNMP I'm missing? Myke [root@jigsaw ~]# time route -vnd flush | wc -l 1121977 real 0m6.681s user 0m3.910s sys 0m2.351s [root@jigsaw ~]# time netstat -rnf inet | wc -l 280479 real 0m12.982s user 0m2.713s sys 0m9.609s [root@jigsaw ~]# From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 21:01:54 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F41310656A5 for ; Sat, 29 Nov 2008 21:01:54 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: from web58308.mail.re3.yahoo.com (web58308.mail.re3.yahoo.com [68.142.236.161]) by mx1.freebsd.org (Postfix) with SMTP id CFCB48FC18 for ; Sat, 29 Nov 2008 21:01:53 +0000 (UTC) (envelope-from venkatvenkatsubra@yahoo.com) Received: (qmail 29160 invoked by uid 60001); 29 Nov 2008 21:01:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=hhf5kPnpVM+kuH5XnFYoRhpKs/k4t9DYRfFmngZ+bbb8CYkXlve1jcGF2gcQFdhi5KmP6c5avYNvrOIt69dsPoMWbsQ0Qj0FZsDy9Ejpb/vtchXOmzwzVY0hO+B4F1tBisE6Mmq67tD53rvsQNPMQPthsXqlaOjMlnDb60UQtrc=; X-YMail-OSG: GhAGlVIVM1nO_Zy7IueRWP_JaSg3qBpquPWCkGeCiLzJ3egCZlHdrlx7L5CiLIMxNa37CPKuinb8K5NGtSeY8K8UYaksgcbcu.rfSkCvBMol8mWy10iKUbpDDKd6M8nX.2BOREdnmr4RgOWKTzg7ZYbQylWwbfgGfdqb2lTnB6V4T7EOhzqAI507euPT Received: from [70.112.131.248] by web58308.mail.re3.yahoo.com via HTTP; Sat, 29 Nov 2008 13:01:52 PST X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1 References: <200811292046.aa42834@salmon.maths.tcd.ie> Date: Sat, 29 Nov 2008 13:01:52 -0800 (PST) From: Venkat Venkatsubra To: David Malone MIME-Version: 1.0 Message-ID: <865234.28813.qm@web58308.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Rui Paulo , freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 29 Nov 2008 21:01:54 -0000 So the apps read buffer is possibly 32=A0times 2^8 =3D 8KB ?=0A(32 being th= e increment in each of those window updates.)=0A=0A=0A=0A=0A_______________= _________________=0AFrom: David Malone =0ATo: Venkat= Venkatsubra =0ACc: Rui Paulo ; freebsd-net@freebsd.org; Kevin Oberman =0ASent: Saturday= , November 29, 2008 2:46:53 PM=0ASubject: Re: FreeBSD Window updates=0A=0A>= Each of these 5 window updates are sent after the apps completed the read= =0A> that it issued, what's the buffer size the apps is passing to the read= ?=0A> If it is small, could that be increased?=0A=0AI'm not actually sure -= the app is iperf. The window scaling factor=0Ais 8 here I think.=0A=0A> Bu= t I agree with you that there is room for optimizing sending of these=0A> w= indow updates.=0A=0AAny feeling for which would be the better fix?=0A=0A=A0= =A0=A0 David.=0A=0A=0A=0A From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 21:08:43 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3924E1065670 for ; Sat, 29 Nov 2008 21:08:43 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id D5BE58FC1A for ; Sat, 29 Nov 2008 21:08:42 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from localhost ([127.0.0.1] helo=maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 29 Nov 2008 21:08:41 +0000 (GMT) To: Venkat Venkatsubra In-reply-to: Your message of "Sat, 29 Nov 2008 13:01:52 PST." <865234.28813.qm@web58308.mail.re3.yahoo.com> Date: Sat, 29 Nov 2008 21:08:38 +0000 From: David Malone Message-ID: <200811292108.aa49379@salmon.maths.tcd.ie> Cc: Rui Paulo , freebsd-net@freebsd.org, Kevin Oberman Subject: Re: FreeBSD Window updates 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, 29 Nov 2008 21:08:43 -0000 > So the apps read buffer is possibly 32 times 2^8 = 8KB ? (32 being the > increment in each of those window updates.) I don't have the source code to hand, but that certainly sounds plausable. It is a tcp traffic generation tool, so 8K sounds like the sort of size it is likely to read in. David.