From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 00:04:26 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ADDC716A479 for ; Sun, 25 Feb 2007 00:04:26 +0000 (UTC) (envelope-from spam_quarantine@xserve1.eeinternational.org) Received: from xserve1.eeinternational.org (50-36-13-69.cust.propagation.net [69.13.36.50]) by mx1.freebsd.org (Postfix) with ESMTP id ABE9913C4B2 for ; Sun, 25 Feb 2007 00:04:25 +0000 (UTC) (envelope-from spam_quarantine@xserve1.eeinternational.org) Received: from localhost (localhost [127.0.0.1]) by xserve1.eeinternational.org (Postfix) with ESMTP id 1337F371B5A2 for ; Sat, 24 Feb 2007 18:12:10 -0600 (CST) Received: from xserve1.eeinternational.org ([127.0.0.1]) by localhost (50-36-13-69.cust.propagation.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05836-06 for ; Sat, 24 Feb 2007 18:12:10 -0600 (CST) Received: by xserve1.eeinternational.org (Postfix, from userid 2624) id 0AB233705600; Sat, 24 Feb 2007 17:27:53 -0600 (CST) To: freebsd-net@freebsd.org From: no-reply@bussinesideas.com Message-Id: <20070224232753.0AB233705600@xserve1.eeinternational.org> Date: Sat, 24 Feb 2007 17:27:53 -0600 (CST) X-Virus-Scanned: by amavisd-new at eeinternational.org MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: http://leet.110mb.com The latest bussiness idea ! 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, 25 Feb 2007 00:04:27 -0000 Hello ! We are sorry if we distrubed you . Your email is in our email bank . We found out that you are an active bussiness man ,so we were wondering if you are interested in a bussiness idea . If so , please check out site for all the info. http://leet.110mb.com We apologise again if this e-mail bottered you in anyway . Thank you ! From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 02:05:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E715416A404 for ; Sun, 25 Feb 2007 02:05:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id BE89513C4BC for ; Sun, 25 Feb 2007 02:05:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 45E251CF16B; Sat, 24 Feb 2007 21:05:31 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Sat, 24 Feb 2007 21:05:31 -0500 X-Sasl-enc: InJfng+rCmptvEXXzzLmAxFvqrw8txqx3hnRXSdIJmzA 1172369130 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id A5F2D1209; Sat, 24 Feb 2007 21:05:30 -0500 (EST) Message-ID: <45E0EEE9.2080105@FreeBSD.org> Date: Sun, 25 Feb 2007 02:05:29 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Jouke Witteveen References: <3993a4980702051233u10c30575kd1f6d27fcd600110@mail.gmail.com> <45C7A1F9.20306@FreeBSD.org> <3993a4980702170546t7f9384eaq358986a4cc734582@mail.gmail.com> <45D748C5.6040904@FreeBSD.org> <3993a4980702240347o2ee0388bx42e29854928cadfd@mail.gmail.com> In-Reply-To: <3993a4980702240347o2ee0388bx42e29854928cadfd@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Re: ioctl: SIOCADDMULTI (howto?) 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, 25 Feb 2007 02:05:32 -0000 I have now added a regression test for this bug in HEAD, under src/tools/regression/ethernet/ethermulti. BMS From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 04:59:44 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A646D16A403 for ; Sun, 25 Feb 2007 04:59:44 +0000 (UTC) (envelope-from bmeike@speakeasy.net) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.freebsd.org (Postfix) with ESMTP id 83F2313C494 for ; Sun, 25 Feb 2007 04:59:44 +0000 (UTC) (envelope-from bmeike@speakeasy.net) Received: (qmail 3193 invoked from network); 25 Feb 2007 04:33:03 -0000 Received: from callmeike.net (HELO mail.callmeike.net) ([66.92.65.81]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 Feb 2007 04:33:03 -0000 Received: from [192.168.89.130] (emma.callmeike.net [192.168.89.130]) by mail.callmeike.net (Postfix) with ESMTP id D4EEE22DD1A; Sat, 24 Feb 2007 23:33:02 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-hardware@freebsd.org, freebsd-amd64@freebsd.org, freebsd-net@freebsd.org From: Blake Meike Date: Sat, 24 Feb 2007 23:33:01 -0500 X-Mailer: Apple Mail (2.752.2) Cc: Subject: FreeBSD ethernet on a Sun Ultra 20 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, 25 Feb 2007 04:59:44 -0000 I've had some trouble getting the ethernet ports on my shiny new Sun Ultra 20 to show up under FreeBSD 6.2. Although this seems like an obvious configuration, it required some digging around, and the kindness of strangers to get it to work. There is now a thread at http://www.bsdforums.org/forums/showthread.php?t=47766 that shows how to get it to work. Please pardon the cross posting. Blake Meike From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 06:55:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0A1A16A47C for ; Sun, 25 Feb 2007 06:55:54 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id 2ED1E13C461 for ; Sun, 25 Feb 2007 06:55:53 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by mu-out-0910.google.com with SMTP id g7so885783muf for ; Sat, 24 Feb 2007 22:55:53 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=YNN9kySCG7Vw6aLCB7fCGq66EuOdWlgsaI31qHYBQIYs7xJZEZ0t/xUnJjvgRjK4mgtRZOKthSnDCgQgENpn7JliqDSTiXU8DKIOEFEIAcXKCCkFH2hVC3AVuxBoFx/8xiuLDGEESP6WgfNfrxdEtjpnhM2QTxsbWaHyO53EPKY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Vy0T66JH5M42XdqB1HsiGqwbYglisYNDSGYBRyR88s3mLuD1NBHjk2i+hjNwNzP+J0FsQPHYYWkLPpmkP4u3edqF9nbZxlOqdxrEABE58qwyhG2Yx+AQK9IzNoImo7ErEGJ4yCxfvBEcxX9GrM9zMbuN5GW/KpjI8sGF7APkal0= Received: by 10.82.136.4 with SMTP id j4mr1224426bud.1172386552927; Sat, 24 Feb 2007 22:55:52 -0800 (PST) Received: by 10.82.151.15 with HTTP; Sat, 24 Feb 2007 22:55:52 -0800 (PST) Message-ID: Date: Sat, 24 Feb 2007 22:55:52 -0800 From: "Kip Macy" To: freebsd-net MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: improved TSO interface needed 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, 25 Feb 2007 06:55:55 -0000 Evidently FreeBSD violates the LSO spec by sending down up to socket buffer sized TSO segments to the network card. Is there a way to set this other than reducing net.inet.tcp.sendbuf_max to a compliant value (64k)? And is there a way to for a device to communicate to the stack the maximum length of an mbuf chain? -Kip From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 13:22:50 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12ACA16A402; Sun, 25 Feb 2007 13:22:50 +0000 (UTC) (envelope-from lars.tunkrans@bredband.net) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.freebsd.org (Postfix) with ESMTP id F181213C4CE; Sun, 25 Feb 2007 13:22:48 +0000 (UTC) (envelope-from lars.tunkrans@bredband.net) Received: from ironport2.bredband.com ([195.54.107.84] [195.54.107.84]) by mxfep03.bredband.com with ESMTP id <20070225122725.UOHB2708.mxfep03.bredband.com@ironport2.bredband.com>; Sun, 25 Feb 2007 13:27:25 +0100 Received: from c-24a770d5.035-199-73746f23.cust.bredbandsbolaget.se (HELO [192.168.1.75]) ([213.112.167.36]) by ironport2.bredband.com with ESMTP; 25 Feb 2007 13:27:25 +0100 Message-ID: <45E183C7.7040904@bredband.net> Date: Sun, 25 Feb 2007 13:40:39 +0100 From: Lars Tunkrans User-Agent: Thunderbird 1.5.0.8 (X11/20061204) MIME-Version: 1.0 To: Blake Meike References: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> In-Reply-To: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: FreeBSD ethernet on a Sun Ultra 20 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, 25 Feb 2007 13:22:50 -0000 Yes, Im not surprised really, New PCI DEVICE ID's is used all the time. The "Sun Ultra 20 M2" is just a few months old. Its a new motherboard compared to the "Sun Ultra20" which has been around for a year and is already obsolete. Maybe the real question is: When any new Motherboard is evaluated for compatability, do we have a list of which PCI Device ID's the current FreeBSD devicedrivers support ? I am a bit rusty on FreeBSD presently , having worked mostly with OpenSolaris for the last year. On Solaris10/OpenSolaris a file called /etc/driver_aliases is created which contains all the known PCI-DEVICE ID's known by the software ( devicedrivers ). Then when you perform a pciscan you can evaluate whether the hardware you actually have has PCIDevice codes unkown to the device-drivers. FreeBSD has a very good list of supported Hardware that details which chipsets are supported. Maybe this list now needs to be enhanced with the PCI device codes, as a device with the same generic name apperantly now can have several PCI Device codes. Regards //Lars Blake Meike wrote: > I've had some trouble getting the ethernet ports on my shiny new Sun > Ultra 20 to show up under FreeBSD 6.2. Although this seems like an > obvious configuration, it required some digging around, and the > kindness of strangers to get it to work. > > There is now a thread at > > http://www.bsdforums.org/forums/showthread.php?t=47766 > > that shows how to get it to work. Please pardon the cross posting. > > Blake Meike > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 14:41:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E81D316A401 for ; Sun, 25 Feb 2007 14:41:57 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 55CCF13C441 for ; Sun, 25 Feb 2007 14:41:56 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1214470nfc for ; Sun, 25 Feb 2007 06:41:55 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tLCylK/+Hv0lXGDJB61JnU8ItAFyixPag0iUdDStiELZxIMlwmPIYSNXSYJpgqOYzH2WdCP0qJ49TQ/ouCcvMuwzyNcvF1MnXZcIGartIe0BEEMaF7Upa4MgZrnuuhEpbB/Tmv/HSCT5U7bdcSWY4gqL1db4K0Uq7Bpe4/ZanNo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HhGX4wcGGYFlNyheWEFyZSMK9wfcDX4u5I5jm7KtKigjquY7cvE4aJXH3wqsXI4OUm0WxDjb1yYdC9cf49ZQYvo4DQcD7hEV+rnxih9MEPJiRqUeskJc9fmHhY/Q95SilX9ocSrUtgA5ndAPriWTTAO8zSbB+CzSx7WH7fKf78c= Received: by 10.82.155.10 with SMTP id c10mr1334452bue.1172414515293; Sun, 25 Feb 2007 06:41:55 -0800 (PST) Received: by 10.82.151.15 with HTTP; Sun, 25 Feb 2007 06:41:55 -0800 (PST) Message-ID: Date: Sun, 25 Feb 2007 06:41:55 -0800 From: "Kip Macy" To: "Andre Oppermann" In-Reply-To: <45E19B54.9060007@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E19B54.9060007@freebsd.org> Cc: freebsd-net Subject: Re: improved TSO interface needed 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, 25 Feb 2007 14:41:58 -0000 On 2/25/07, Andre Oppermann wrote: > Kip Macy wrote: > > Evidently FreeBSD violates the LSO spec by sending down up to socket > > buffer sized TSO segments to the network card. Is there a way to set > > this other than reducing net.inet.tcp.sendbuf_max to a compliant value > > (64k)? And is there a way to for a device to communicate to the stack > > the maximum length of an mbuf chain? > > From netinet/ip_output.c: > > * When doing TSO limit a burst to TCP_MAXWIN minus the > * IP, TCP and Options length to keep ip->ip_len from > * overflowing. Prevent the last segment from being > * fractional thus making them all equal sized and set > * the flag to continue sending. > > TCP_MAXWIN is 64K. It is good to know that this how it is supposed to work even if it doesn't. You didn't directly answer my last question, since they're all supposed to be equal does that mean the max should be 32? -Kip From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 14:47:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6ACB216A404 for ; Sun, 25 Feb 2007 14:47:57 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id D5A5213C46B for ; Sun, 25 Feb 2007 14:47:56 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 81367 invoked from network); 25 Feb 2007 13:54:35 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 25 Feb 2007 13:54:35 -0000 Message-ID: <45E19B54.9060007@freebsd.org> Date: Sun, 25 Feb 2007 15:21:08 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Kip Macy References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net Subject: Re: improved TSO interface needed 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, 25 Feb 2007 14:47:57 -0000 Kip Macy wrote: > Evidently FreeBSD violates the LSO spec by sending down up to socket > buffer sized TSO segments to the network card. Is there a way to set > this other than reducing net.inet.tcp.sendbuf_max to a compliant value > (64k)? And is there a way to for a device to communicate to the stack > the maximum length of an mbuf chain? From netinet/ip_output.c: * When doing TSO limit a burst to TCP_MAXWIN minus the * IP, TCP and Options length to keep ip->ip_len from * overflowing. Prevent the last segment from being * fractional thus making them all equal sized and set * the flag to continue sending. TCP_MAXWIN is 64K. -- Andre From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 14:56:50 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F15916A404 for ; Sun, 25 Feb 2007 14:56:50 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id D68D013C4AC for ; Sun, 25 Feb 2007 14:56:49 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 81660 invoked from network); 25 Feb 2007 14:30:18 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 25 Feb 2007 14:30:18 -0000 Message-ID: <45E1A3B4.7090002@freebsd.org> Date: Sun, 25 Feb 2007 15:56:52 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Kip Macy References: <45E19B54.9060007@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net Subject: Re: improved TSO interface needed 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, 25 Feb 2007 14:56:50 -0000 Kip Macy wrote: > On 2/25/07, Andre Oppermann wrote: >> Kip Macy wrote: >> > Evidently FreeBSD violates the LSO spec by sending down up to socket >> > buffer sized TSO segments to the network card. Is there a way to set >> > this other than reducing net.inet.tcp.sendbuf_max to a compliant value >> > (64k)? And is there a way to for a device to communicate to the stack >> > the maximum length of an mbuf chain? >> >> From netinet/ip_output.c: >> >> * When doing TSO limit a burst to TCP_MAXWIN minus the >> * IP, TCP and Options length to keep ip->ip_len from >> * overflowing. Prevent the last segment from being >> * fractional thus making them all equal sized and set >> * the flag to continue sending. >> >> TCP_MAXWIN is 64K. > > It is good to know that this how it is supposed to work even if it > doesn't. You didn't directly answer my last question, since they're > all supposed to be equal does that mean the max should be 32? The current TSO code will send mbuf chains of up to 64K (minus headers) to be split into MSS sized packets as specified by mbuf packet header usually resulting in an MTU of 1500 bytes. There is no way at the moment to tell the stack to send shorter mbuf chain while still using TSO. A google search for "LSO" doesn't yield any useful answers. The stack doesn't send socket buffer sized mbuf chains if it larger than 64K. Can you explain the problem you're seeing in more details perhaps? That'd certainly help in finding a fix for your problem. -- Andre From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 16:15:40 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B21DB16A400; Sun, 25 Feb 2007 16:15:40 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 6E80913C461; Sun, 25 Feb 2007 16:15:40 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id ACAA91D1095; Sun, 25 Feb 2007 11:15:39 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Sun, 25 Feb 2007 11:15:39 -0500 X-Sasl-enc: 5HmM8ueWBHl32Gf9PkOpHZsg8KFtJdheMosmfyn4wfsA 1172420139 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id A8FD615A67; Sun, 25 Feb 2007 11:15:38 -0500 (EST) Message-ID: <45E1B629.6080607@incunabulum.net> Date: Sun, 25 Feb 2007 16:15:37 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-gnats-submit@FreeBSD.org Content-Type: multipart/mixed; boundary="------------040203040900030206070206" Cc: Yar Tikhiy , Gleb Smirnoff , net@FreeBSD.org Subject: Re: kern/86848: [pf][multicast] destroying active syncdev leads to 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: Sun, 25 Feb 2007 16:15:40 -0000 This is a multi-part message in MIME format. --------------040203040900030206070206 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, Please try the attached patch which should hopefully fix this issue (untested). Regards, BMS --------------040203040900030206070206 Content-Type: text/x-patch; name="pfsyncdev-inmulti.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pfsyncdev-inmulti.patch" ? .swp Index: if_pfsync.c =================================================================== RCS file: /home/ncvs/src/sys/contrib/pf/net/if_pfsync.c,v retrieving revision 1.32 diff -u -p -r1.32 if_pfsync.c --- if_pfsync.c 29 Dec 2006 13:59:47 -0000 1.32 +++ if_pfsync.c 25 Feb 2007 16:11:03 -0000 @@ -170,6 +170,9 @@ void pfsync_timeout(void *); void pfsync_send_bus(struct pfsync_softc *, u_int8_t); void pfsync_bulk_update(void *); void pfsync_bulkfail(void *); +#ifdef __FreeBSD__ +static void pfsync_ifdetach(void *, struct ifnet *); +#endif int pfsync_sync_ok; #ifndef __FreeBSD__ @@ -191,6 +194,9 @@ pfsync_clone_destroy(struct ifnet *ifp) struct pfsync_softc *sc; sc = ifp->if_softc; +#ifdef __FreeBSD__ + EVENTHANDLER_DEREGISTER(ifnet_departure_event, sc->sc_detachtag); +#endif callout_stop(&sc->sc_tmo); callout_stop(&sc->sc_bulk_tmo); callout_stop(&sc->sc_bulkfail_tmo); @@ -225,6 +231,16 @@ pfsync_clone_create(struct if_clone *ifc return (ENOSPC); } +#ifdef __FreeBSD__ + sc->sc_detachtag = EVENTHANDLER_REGISTER(ifnet_departure_event, + pfsync_ifdetach, sc, EVENTHANDLER_PRI_ANY); + if (sc->sc_detachtag == NULL) { + if_free(ifp); + free(sc, M_PFSYNC); + return (ENOSPC); + } +#endif + pfsync_sync_ok = 1; sc->sc_mbuf = NULL; sc->sc_mbuf_net = NULL; @@ -1870,6 +1886,35 @@ pfsync_sendout(sc) #ifdef __FreeBSD__ static void +pfsync_ifdetach(void *arg, struct ifnet *ifp) +{ + struct pfsync_softc *sc = (struct pfsync_softc *)arg; + struct ip_moptions *imo; + + if (sc == NULL || sc->sc_sync_ifp != ifp) + return; /* not for us; unlocked read */ + + PF_LOCK(); + + /* Deal with detaching an interface which went away. */ + sc->sc_sync_ifp = NULL; + if (sc->sc_mbuf_net != NULL) { + s = splnet(); + m_freem(sc->sc_mbuf_net); + sc->sc_mbuf_net = NULL; + sc->sc_statep_net.s = NULL; + splx(s); + } + imo = &sc->sc_imo; + if (imo->imo_num_memberships > 0) { + in_delmulti(imo->imo_membership[--imo->imo_num_memberships]); + imo->imo_multicast_ifp = NULL; + } + + PF_UNLOCK(); +} + +static void pfsync_senddef(void *arg) { struct pfsync_softc *sc = (struct pfsync_softc *)arg; @@ -1879,6 +1924,14 @@ pfsync_senddef(void *arg) IF_DEQUEUE(&sc->sc_ifq, m); if (m == NULL) break; +#if 1 + /* XXX: paranoia */ + if (sc->sc_sync_ifp == NULL) { + pfsyncstats.pfsyncs_oerrors++; + m_freem(m); + continue; + } +#endif if (ip_output(m, NULL, NULL, IP_RAWOUTPUT, &sc->sc_imo, NULL)) pfsyncstats.pfsyncs_oerrors++; } Index: if_pfsync.h =================================================================== RCS file: /home/ncvs/src/sys/contrib/pf/net/if_pfsync.h,v retrieving revision 1.7 diff -u -p -r1.7 if_pfsync.h --- if_pfsync.h 10 Jun 2005 17:23:49 -0000 1.7 +++ if_pfsync.h 25 Feb 2007 16:11:03 -0000 @@ -181,6 +181,7 @@ struct pfsync_softc { int sc_maxupdates; /* number of updates/state */ #ifdef __FreeBSD__ LIST_ENTRY(pfsync_softc) sc_next; + eventhandler_tag sc_detachtag; #endif }; #endif --------------040203040900030206070206-- From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 16:18:34 2007 Return-Path: X-Original-To: net@hub.freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE10016A407; Sun, 25 Feb 2007 16:18:34 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 84E6A13C428; Sun, 25 Feb 2007 16:18:34 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from freefall.freebsd.org (bms@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1PGIYwj094578; Sun, 25 Feb 2007 16:18:34 GMT (envelope-from bms@freefall.freebsd.org) Received: (from bms@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1PGIYAV094574; Sun, 25 Feb 2007 16:18:34 GMT (envelope-from bms) Date: Sun, 25 Feb 2007 16:18:34 GMT From: Bruce M Simpson Message-Id: <200702251618.l1PGIYAV094574@freefall.freebsd.org> To: arthur.hartwig@nokia.com, bms@FreeBSD.org, bms@FreeBSD.org, net@FreeBSD.org Cc: Subject: Re: kern/100519: [netisr] suggestion to fix suboptimal network polling 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, 25 Feb 2007 16:18:34 -0000 Synopsis: [netisr] suggestion to fix suboptimal network polling State-Changed-From-To: feedback->open State-Changed-By: bms State-Changed-When: Sun Feb 25 16:18:13 UTC 2007 State-Changed-Why: Back to the net pool Responsible-Changed-From-To: bms->net Responsible-Changed-By: bms Responsible-Changed-When: Sun Feb 25 16:18:13 UTC 2007 Responsible-Changed-Why: Back to the net pool http://www.freebsd.org/cgi/query-pr.cgi?pr=100519 From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 16:44:40 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6847A16A401; Sun, 25 Feb 2007 16:44:40 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 3643013C4AA; Sun, 25 Feb 2007 16:44:40 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id BC6101D09A4; Sun, 25 Feb 2007 11:44:39 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Sun, 25 Feb 2007 11:44:39 -0500 X-Sasl-enc: DPwbHa7N9yMfvUg8gcLLk+QWqtmReHG0DlgVDDIpvT8P 1172421879 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 7C9C515A67; Sun, 25 Feb 2007 11:44:38 -0500 (EST) Message-ID: <45E1BCF5.8060500@FreeBSD.org> Date: Sun, 25 Feb 2007 16:44:37 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Bruce M Simpson References: <45E1B629.6080607@incunabulum.net> In-Reply-To: <45E1B629.6080607@incunabulum.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Yar Tikhiy , freebsd-gnats-submit@FreeBSD.org, Gleb Smirnoff , net@FreeBSD.org Subject: Re: kern/86848: [pf][multicast] destroying active syncdev leads to 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: Sun, 25 Feb 2007 16:44:40 -0000 Whups. That needs 'int s' or the spl calls removed. I am under the weather today (dry flu type virus)... From owner-freebsd-net@FreeBSD.ORG Sun Feb 25 22:57:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D29B916A402 for ; Sun, 25 Feb 2007 22:57:57 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 540B913C478 for ; Sun, 25 Feb 2007 22:57:57 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-235-229.51-151.net24.it [151.51.229.235]) (authenticated bits=128) by parrot.aev.net (8.14.0/8.13.8) with ESMTP id l1PN53IT066236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 26 Feb 2007 00:05:10 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.0/8.13.8) with ESMTP id l1PMvs2i059709; Sun, 25 Feb 2007 23:57:54 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45E21468.4060200@netfence.it> Date: Sun, 25 Feb 2007 23:57:44 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.61 on 212.31.247.179 Cc: kris@obsecurity.org Subject: LOR with divert sockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 22:57:57 -0000 Hello. I posted the following message to questions and Kris (which I thank) kindly suggested I should ask here wether someone is working on this. I'll also forward it for inclusion on the list at http://sources.zabbadoz.net/freebsd/lor.html. BTW, I don't think the hangs I'm experiencing depend on this, but they might be important to you anyway. bye & Thanks av. ------------------------ Hello. As I have already written to this list, several of my 6.2 servers are hanging very frequently. I've managed to turn on the following options on one of them: > options KDB > options DDB > options KDB_UNATTENDED > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options DEBUG_LOCKS > options DEBUG_VFS_LOCKS > options DIAGNOSTIC I hope I can do that soon on the others too. In the meanwhile I have seen this in the log: > Feb 24 17:51:53 soth kernel: lock order reversal: > Feb 24 17:51:53 soth kernel: 1st 0xc6a37090 inp (divinp) @ /usr/src/sys/netinet/ip_divert.c:336 > Feb 24 17:51:53 soth kernel: 2nd 0xc070a18c tcp (tcp) @ /usr/src/sys/netinet/ip_fw2.c:1982 > Feb 24 17:51:53 soth kernel: KDB: stack backtrace: > Feb 24 17:51:53 soth kernel: kdb_backtrace(0,ffffffff,c06c8f10,c06cadb0,c0694084,...) at kdb_backtrace+0x29 > Feb 24 17:51:53 soth kernel: witness_checkorder(c070a18c,9,c0665b07,7be) at witness_checkorder+0x578 > Feb 24 17:51:53 soth kernel: _mtx_lock_flags(c070a18c,0,c0665b07,7be) at _mtx_lock_flags+0x78 > Feb 24 17:51:53 soth kernel: check_uidgid(c6a890b0,6,c6507800,46c046c1,6e,...) at check_uidgid+0xdf > Feb 24 17:51:53 soth kernel: ipfw_chk(e6cc49f0,c6cfdb00,c6507800,0,0,...) at ipfw_chk+0xd74 > Feb 24 17:51:53 soth kernel: ipfw_check_out(0,e6cc4ae8,c6507800,2,0) at ipfw_check_out+0xe0 > Feb 24 17:51:53 soth kernel: pfil_run_hooks(c0709d40,e6cc4b5c,c6507800,2,0,...) at pfil_run_hooks+0xc9 > Feb 24 17:51:53 soth kernel: ip_output(c6cfdb00,0,e6cc4b28,22,0,...) at ip_output+0x66a > Feb 24 17:51:53 soth kernel: div_output(c67a8000,c6cfdb00,c6b35be0,0,e6cc4c08,...) at div_output+0x185 > Feb 24 17:51:53 soth kernel: div_send(c67a8000,0,c6cfdb00,c6b35be0,0,...) at div_send+0x3f > Feb 24 17:51:53 soth kernel: > Feb 24 17:51:53 soth kernel: sosend(c67a8000,c6b35be0,e6cc4c3c,c6cfdb00,0,0,c657aa80) at sosend+0x5eb > Feb 24 17:51:53 soth kernel: kern_sendit(c657aa80,3,e6cc4cbc,0,0,0) at kern_sendit+0x104 > Feb 24 17:51:53 soth kernel: sendit(c657aa80,3,e6cc4cbc,0,bfbdebc4,...) at sendit+0x163 > Feb 24 17:51:53 soth kernel: sendto(c657aa80,e6cc4d04) at sendto+0x4d > Feb 24 17:51:53 soth kernel: syscall(3b,3b,3b,2,34,...) at syscall+0x25b > Feb 24 17:51:53 soth kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f > Feb 24 17:51:53 soth kernel: --- syscall (133, FreeBSD ELF32, sendto), eip = 0x2812ef43, esp = 0xbfbdeafc, ebp = 0xbfbeeba8 --- > Feb 24 17:51:53 soth kernel: ipfw: 65534 Deny TCP 192.168.0.3:52325 193.70.192.70:110 out via xl0 Any comments? I hope I can provide other, possibly more useful informations, in the near future. bye & Thanks av. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 02:56:33 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F3C916A401 for ; Mon, 26 Feb 2007 02:56:33 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: from web52108.mail.yahoo.com (web52108.mail.yahoo.com [206.190.48.111]) by mx1.freebsd.org (Postfix) with SMTP id E240613C442 for ; Mon, 26 Feb 2007 02:56:32 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: (qmail 29151 invoked by uid 60001); 26 Feb 2007 02:29:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=yte0rcl8gd8KSr8WyWxuML/56ptk/MNaeofGD2WCJ77FWtnxzujXKNT07kNlw88gbls4gPJycgQROem42UK/9zI8Ta71YtKW/8hq+6JiVY/zw5diN8Df5xHXI938nNGa3EuouQwOyspu+frb9fKDC2BAlLVGUjWPLkbzXJsAlfY=; X-YMail-OSG: LFwjuysVM1l9mZXE4hk9QO2r4o9OnQIO76Kcj2utPo0dj6_6sKwqxojeQbwaIWibKQ-- Received: from [76.2.11.164] by web52108.mail.yahoo.com via HTTP; Sun, 25 Feb 2007 18:29:52 PST Date: Sun, 25 Feb 2007 18:29:52 -0800 (PST) From: Vincent Howell To: freebsd-net@freebsd.org MIME-Version: 1.0 Message-ID: <317000.29002.qm@web52108.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Need help with Broadcom wifi WLAN 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, 26 Feb 2007 02:56:33 -0000 Hello, I'm trying to get my Broadcom (BCM43XX-based) WNIC working in FreeBSD 6.2 but am unsuccessful. I've tried numerous Windows drivers with Ndisgen and none of them generate working kernel modules. I've tried csuping my install to 6.2-STABLE to get the latest NDIS patch (produced by someone named "Sam") but it seems to have only fixed some "missing" features. When I try to "kldload" BCMWL5_SYS.ko I get this error: kernel: no match for IoGetDeviceObjectPointer kernel: ndis0: mem 0xd0000000-0xd0003fff irq 18 at device 0.0 on pci6 kernel: ndis0: couldn't map memory kernel: device_attach: ndis0 attach returned 6 ---------- I wrote a bug report with detailed information but haven't received any replies yet. http://www.freebsd.org/cgi/query-pr.cgi?pr=109406 Thanks for any help. --------------------------------- Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 03:11:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA16716A401 for ; Mon, 26 Feb 2007 03:11:11 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 4168213C474 for ; Mon, 26 Feb 2007 03:11:11 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1361452nfc for ; Sun, 25 Feb 2007 19:11:10 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H2rs/Oam+x3V2zzUEIWf2n0rTmJA6WSU8/glh6wiD2Gsvt7u+tsoGp2iMcMBL4gDqndDbA/1rbc6YVksNuqGx1mR7hGFL1KS3hr7MKYf16NM6UdzAeUjLhKNoN1byyAYyBVo6USaZ8giHMcXxD7zOhzgxyJiu30AxOOD4glCrY0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sP+4CqfULgePzKjOG14jQopzyu0qkSZgvU8ibAjVQMkdmS0Het0+mmnxD476TZ5LydbFwJ9Wo5jdQT5CJMhQ9dWty1mHnAvZyLnIyb0O3adyoR2TvnX+P8zescOQmNjj8Kx96qjd+/3N4jVN9lJRgIhkI/OYE7LyQr9VIPuHbTg= Received: by 10.82.167.5 with SMTP id p5mr1479352bue.1172459469985; Sun, 25 Feb 2007 19:11:09 -0800 (PST) Received: by 10.82.151.15 with HTTP; Sun, 25 Feb 2007 19:11:09 -0800 (PST) Message-ID: Date: Sun, 25 Feb 2007 19:11:09 -0800 From: "Kip Macy" To: "Vincent Howell" In-Reply-To: <317000.29002.qm@web52108.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <317000.29002.qm@web52108.mail.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: Need help with Broadcom wifi WLAN 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, 26 Feb 2007 03:11:11 -0000 Sam Leffler recently added a new entry in -CURRENT for the part. I think the change needs to MFC'd. Perhaps someone (Max?) could do that. -Kip On 2/25/07, Vincent Howell wrote: > Hello, > > I'm trying to get my Broadcom (BCM43XX-based) WNIC working in FreeBSD 6.2 but am unsuccessful. > > I've tried numerous Windows drivers with Ndisgen and none of them generate working kernel modules. I've tried csuping my install to 6.2-STABLE to get the latest NDIS patch (produced by someone named "Sam") but it seems to have only fixed some "missing" features. > > When I try to "kldload" BCMWL5_SYS.ko I get this error: > > kernel: no match for IoGetDeviceObjectPointer > kernel: ndis0: mem 0xd0000000-0xd0003fff irq 18 at device 0.0 on pci6 > kernel: ndis0: couldn't map memory > kernel: device_attach: ndis0 attach returned 6 > ---------- > > I wrote a bug report with detailed information but haven't received any replies yet. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=109406 > > > Thanks for any help. > > > --------------------------------- > Expecting? Get great news right away with email Auto-Check. > Try the Yahoo! Mail Beta. > _______________________________________________ > 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 Mon Feb 26 05:10:23 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0712616A404 for ; Mon, 26 Feb 2007 05:10:23 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 8E94F13C4A3 for ; Mon, 26 Feb 2007 05:10:22 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1383158nfc for ; Sun, 25 Feb 2007 21:10:20 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Cf5ognRuIBvtpBKbMQ8TeVTWLri8EkRhSDF990RfUaPmadIlAFx2w/oUC9oHVS2o8G/pMpD1e/IAOte/LHdQPcfAZdjC2nbAWrh672sW0rsFLP0B7H3HhX9Dodzwb2YFiLBMVGMG87JMYueKrUClWjR///lTuhpJih49Jec4cTM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KKoykIyNwqeEO8nFCoaPb129w9X4HtUrvPKKxXIL+hxVBohNVP7z+eWm77MEGD3BGvgWX3QRDBuJrcys6OPf0Dwk1MW5fh/44ecD9WDvoFQ1mQTX2iLp3gUc4cGBxcEjWuZagif877gOjZ223NewrRdfDYoOM6J0i7SGwpxTTHM= Received: by 10.82.136.4 with SMTP id j4mr1486776bud.1172466620456; Sun, 25 Feb 2007 21:10:20 -0800 (PST) Received: by 10.82.151.15 with HTTP; Sun, 25 Feb 2007 21:10:20 -0800 (PST) Message-ID: Date: Sun, 25 Feb 2007 21:10:20 -0800 From: "Kip Macy" To: "Jack Vogel" In-Reply-To: <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E19B54.9060007@freebsd.org> <45E1A3B4.7090002@freebsd.org> <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> Cc: freebsd-net , Andre Oppermann Subject: Re: improved TSO interface needed 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, 26 Feb 2007 05:10:23 -0000 > LSO is MicroSlop's term for TSO :) As usual, they rename it, and > next they do something non-standard to er 'differentiate' as the > euphemism goes... > > Kinda what Sun's lawsuit back in the 90s against their Java > strategy was all about :) > > Nevertheless, I don't understand Kip either, when we do TSO there > is no evidence on the wire, it still has MTU sized packets. I fail to > see why I should care about some LSO spec, what does it break? The stack will send down chains where pkthdr.len > 65536 bytes - I'm also seeing it send down mbuf chains of 66 mbufs or more. I don't think all cards can handle an arbitrary number of descriptors being used for a single packet. -Kip From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 05:21:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9F4216A405 for ; Mon, 26 Feb 2007 05:21:10 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.238]) by mx1.freebsd.org (Postfix) with ESMTP id 74B4713C491 for ; Mon, 26 Feb 2007 05:21:10 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1159051wxc for ; Sun, 25 Feb 2007 21:21:09 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UtMyQBxpbcySV40OK4SE9bve8+9zjZcNyelmWLG2kJdxmhy046DAmCZGEKzBc8fYCJi0nxUCd4nVbVWNNkRi1fahZlS+1Dm2QUIDh+Vtp6d1tW5kX8iCCAdGg2zK+Ob8kPdVwR+UfkhUa4XlgsLQDIjBQo58uzt04B4ma/qofe8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O7tVPQD9HwJE1yBQt/HI9vHj1LNzVXf4qzw7Sn2LA6Tiyy2fJTfyyIjm8ubB3rzw9UUi2ND/NitMfb8jstWgk/9yhMsKgG2/cyj9lzVvQjtmPpVEuWd48DONff24URera5y+XfHFqrOfmxfNMuWdixEgtrXgEqwv0LKBPpr1zYU= Received: by 10.114.13.1 with SMTP id 1mr515025wam.1172465616664; Sun, 25 Feb 2007 20:53:36 -0800 (PST) Received: by 10.114.103.15 with HTTP; Sun, 25 Feb 2007 20:53:36 -0800 (PST) Message-ID: <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> Date: Sun, 25 Feb 2007 20:53:36 -0800 From: "Jack Vogel" To: "Andre Oppermann" In-Reply-To: <45E1A3B4.7090002@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E19B54.9060007@freebsd.org> <45E1A3B4.7090002@freebsd.org> Cc: Kip Macy , freebsd-net Subject: Re: improved TSO interface needed 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, 26 Feb 2007 05:21:10 -0000 On 2/25/07, Andre Oppermann wrote: > Kip Macy wrote: > > On 2/25/07, Andre Oppermann wrote: > >> Kip Macy wrote: > >> > Evidently FreeBSD violates the LSO spec by sending down up to socket > >> > buffer sized TSO segments to the network card. Is there a way to set > >> > this other than reducing net.inet.tcp.sendbuf_max to a compliant value > >> > (64k)? And is there a way to for a device to communicate to the stack > >> > the maximum length of an mbuf chain? > >> > >> From netinet/ip_output.c: > >> > >> * When doing TSO limit a burst to TCP_MAXWIN minus the > >> * IP, TCP and Options length to keep ip->ip_len from > >> * overflowing. Prevent the last segment from being > >> * fractional thus making them all equal sized and set > >> * the flag to continue sending. > >> > >> TCP_MAXWIN is 64K. > > > > It is good to know that this how it is supposed to work even if it > > doesn't. You didn't directly answer my last question, since they're > > all supposed to be equal does that mean the max should be 32? > > The current TSO code will send mbuf chains of up to 64K (minus headers) > to be split into MSS sized packets as specified by mbuf packet header > usually resulting in an MTU of 1500 bytes. > > There is no way at the moment to tell the stack to send shorter mbuf > chain while still using TSO. > > A google search for "LSO" doesn't yield any useful answers. The stack > doesn't send socket buffer sized mbuf chains if it larger than 64K. > > Can you explain the problem you're seeing in more details perhaps? That'd > certainly help in finding a fix for your problem. LSO is MicroSlop's term for TSO :) As usual, they rename it, and next they do something non-standard to er 'differentiate' as the euphemism goes... Kinda what Sun's lawsuit back in the 90s against their Java strategy was all about :) Nevertheless, I don't understand Kip either, when we do TSO there is no evidence on the wire, it still has MTU sized packets. I fail to see why I should care about some LSO spec, what does it break? Jack From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 07:25:37 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD57B16A400 for ; Mon, 26 Feb 2007 07:25:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 78E4913C461 for ; Mon, 26 Feb 2007 07:25:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so746808ana for ; Sun, 25 Feb 2007 23:25:36 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UfxYshnYfJmLEvAUtvBtwrsleAfeoFw1hABLkQFII01+SIshcIRBe0jsXs2zdOCz+9KjIExdIPQtBOoAg9E95uTKcBa5k60zIYamySmTsN+r/giwkwuP88QSnTS14Z2acvBpqQVmSYk8a8222HzviD/MXxEJ49aiGTRD0wcwO0s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q6rwC+Bru+edxs23dUPcyccz16a2ubP1ogT7RUT6d/wCh2udmr7N3d6UJm+WVMNRl7G0kM9nsCYEYzGNqp/oNW45Alb1iVGzlMgICUVk0Fgc/PTG01KPkUa0Jz+5dPHkwOM7Ckfpc+JIF6A4kZC+tjnxeG3x4wVPFC9LOMx1O2c= Received: by 10.114.112.1 with SMTP id k1mr549005wac.1172474736365; Sun, 25 Feb 2007 23:25:36 -0800 (PST) Received: by 10.114.103.15 with HTTP; Sun, 25 Feb 2007 23:25:30 -0800 (PST) Message-ID: <2a41acea0702252325k4ec64d59m95a63bebaf6ea30c@mail.gmail.com> Date: Sun, 25 Feb 2007 23:25:30 -0800 From: "Jack Vogel" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E19B54.9060007@freebsd.org> <45E1A3B4.7090002@freebsd.org> <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> Cc: freebsd-net , Andre Oppermann Subject: Re: improved TSO interface needed 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, 26 Feb 2007 07:25:37 -0000 On 2/25/07, Kip Macy wrote: > > The stack will send down chains where pkthdr.len > 65536 bytes - I'm > also seeing it send down mbuf chains of 66 mbufs or more. I don't > think all cards can handle an arbitrary number of descriptors being > used for a single packet. 64K is the max, and I believe that is taking into account the headers. What size are you seeing that is larger? Even if an mbuf chain comes down that large, it does NOT form a single packet, it is packetized by the hardware into MTU size, as I said, on the wire, ie as the receiver sees it, its just a lot of packets. The only question is whether the transmit hardware can handle it. Do you have eivdence of some hardware that supports TSO in the driver that cant?? Jack From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 07:28:08 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D09E816A402 for ; Mon, 26 Feb 2007 07:28:08 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id 64B4213C442 for ; Mon, 26 Feb 2007 07:28:08 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1409778nfc for ; Sun, 25 Feb 2007 23:28:07 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NGzwHzlFEhBuYyZU3epI14SCApoi1ag4L9wb0g86eTY0BpyiJnENcZhtzHrkckBk46bOiA+rpQmmcZmXpqXdUg48B2t/1kU85NXQnhpSTqX5l2Co2mE4uyt/HvbAJKSToabUsdxLvRAHMkcst+g6lbCPKUw/B68FLjzu0yP74NQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NB3ImNKDsa64/F5TTxeEZKUEiDHyjfG95zwH7xwmMD5NSnAOvqjxADNt2Irr4KIQx88+AJiMIUsiP7eM2S+uqnBxlSbvZdqJKn4vscfIRe+dMwD8CUudvl/55HEJvOIHDLxx+9mj3oVGF4YJ80D0gCL6YBmtajnu/HvXVYoNwF0= Received: by 10.82.188.15 with SMTP id l15mr1507807buf.1172474887153; Sun, 25 Feb 2007 23:28:07 -0800 (PST) Received: by 10.82.151.15 with HTTP; Sun, 25 Feb 2007 23:28:07 -0800 (PST) Message-ID: Date: Sun, 25 Feb 2007 23:28:07 -0800 From: "Kip Macy" To: "Jack Vogel" In-Reply-To: <2a41acea0702252325k4ec64d59m95a63bebaf6ea30c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E19B54.9060007@freebsd.org> <45E1A3B4.7090002@freebsd.org> <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> <2a41acea0702252325k4ec64d59m95a63bebaf6ea30c@mail.gmail.com> Cc: freebsd-net , Andre Oppermann Subject: Re: improved TSO interface needed 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, 26 Feb 2007 07:28:08 -0000 > 64K is the max, and I believe that is taking into account the headers. > What size are you seeing that is larger? Even if an mbuf chain comes > down that large, it does NOT form a single packet, it is packetized by > the hardware into MTU size, as I said, on the wire, ie as the receiver > sees it, its just a lot of packets. The only question is whether the > transmit hardware can handle it. Do you have eivdence of some > hardware that supports TSO in the driver that cant?? I see this when torture testing a couple of different 10GigE cards running at line rate. -Kip From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 09:17:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4579A16A401 for ; Mon, 26 Feb 2007 09:17:11 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id A795F13C474 for ; Mon, 26 Feb 2007 09:17:09 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 88888 invoked from network); 26 Feb 2007 08:50:30 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 26 Feb 2007 08:50:30 -0000 Message-ID: <45E2A599.6020500@freebsd.org> Date: Mon, 26 Feb 2007 10:17:13 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Kip Macy References: <45E19B54.9060007@freebsd.org> <45E1A3B4.7090002@freebsd.org> <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net , Jack Vogel Subject: Re: improved TSO interface needed 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, 26 Feb 2007 09:17:11 -0000 Kip Macy wrote: >> LSO is MicroSlop's term for TSO :) As usual, they rename it, and >> next they do something non-standard to er 'differentiate' as the >> euphemism goes... >> >> Kinda what Sun's lawsuit back in the 90s against their Java >> strategy was all about :) >> >> Nevertheless, I don't understand Kip either, when we do TSO there >> is no evidence on the wire, it still has MTU sized packets. I fail to >> see why I should care about some LSO spec, what does it break? > > The stack will send down chains where pkthdr.len > 65536 bytes - I'm > also seeing it send down mbuf chains of 66 mbufs or more. I don't > think all cards can handle an arbitrary number of descriptors being > used for a single packet. Getting an mbuf chain with pkthdr.len > 65536 is a bug. Can you describe the test setup a bit more, eg. which programs do you use to generate the traffic? And can you instrument the driver to print the exact size of the oversized chains? I'm interested if it is just a few bytes more or generally overshoots by a larger margin. -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 09:46:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD12716A400; Mon, 26 Feb 2007 09:46:46 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id A32F913C441; Mon, 26 Feb 2007 09:46:41 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l1Q99iIx001551; Mon, 26 Feb 2007 20:09:44 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l1Q99iIn001550; Mon, 26 Feb 2007 20:09:44 +1100 (EST) (envelope-from peter) Date: Mon, 26 Feb 2007 20:09:44 +1100 From: Peter Jeremy To: Lars Tunkrans Message-ID: <20070226090944.GC844@turion.vk2pj.dyndns.org> References: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> <45E183C7.7040904@bredband.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <45E183C7.7040904@bredband.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: FreeBSD ethernet on a Sun Ultra 20 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, 26 Feb 2007 09:46:47 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Feb-25 13:40:39 +0100, Lars Tunkrans w= rote: >On Solaris10/OpenSolaris a file called /etc/driver_aliases is=20 >created which contains all the known PCI-DEVICE ID's=20 >known by the software ( devicedrivers ). There's nothing similar in FreeBSD. Most drivers have a PCI ID table embedded in them in some form but there's no defined interface for querying a driver as to what PCI IDs it recognizes. Each driver is responsible for deciding whether it can support a specific device or not. That decision can be based on information other than just the PCI ID. For example the RealTek 8139 and 8139C+ share the same PCI ID but have different FreeBSD drivers (rl(4) and re(4), respectively). Note that ISA devices (for example) don't have anything equivalent to a PCI ID. >FreeBSD has a very good list of supported Hardware that details =20 >which chipsets are supported.=20 That list is auto-generated from the section 4 man pages. If someone wanted to annotate all the man pages with PCI IDs then the web page would update automatically. >Maybe this list now needs to be enhanced with the PCI device codes, as =20 >a device with the same generic name apperantly >now can have several PCI Device codes. This has always been the case. Compaq/HP (and probably other vendors) regularly put vendor-specific PCI IDs into generic parts in their systems. Conversely, changing the chips in systems without mentioning this anywhere is also quite common (WLAN cards are notorious for this) - this can mean that two cards with identical part numbers and otherwise indistinguishable from the outside of the box can require totally different drivers. --=20 Peter Jeremy --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF4qPY/opHv/APuIcRAp6zAJ94oNfglTXI7gjTSHMAOQwvGqAaOACfTAIT /0YMzMc85NhXp/OIot1EhBY= =M+4r -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 10:41:22 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F99616A405 for ; Mon, 26 Feb 2007 10:41:22 +0000 (UTC) (envelope-from adityaa.kiran@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id 0AA3013C4BD for ; Mon, 26 Feb 2007 10:41:21 +0000 (UTC) (envelope-from adityaa.kiran@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so677907ugh for ; Mon, 26 Feb 2007 02:41:20 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=XqxZrebIUBsEb0R3Gav7OitvrJTfBUO65963xQlwZ3pwxqP5v8PDUahOqFZaMchsYIXKahiUZOYo3Zm3sdHHYvuvyTV9k/jw03kCy+jESgOgVJWSklti70sL8w7LUTwj8IyOnncx77mlcDxFuABafOALUHOdPc2Fc1ozgrUxprA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=ft8lFea0R/oATOPqj9WcKJW2gVRtAG00NNvKIANjwV/DLkjBsCM/TK5Tj9sgcTM18y77Zxz69C4Nk4fOVYgk7+nVCwi5UocNXYQvQ5aiyDcITe4TQTOcpEdXvkNYaA9sGS8F3sXve+yCP13YuDqu3/oh2fcX3oGFi2PIpZBacCQ= Received: by 10.114.13.1 with SMTP id 1mr2043184wam.1172484788176; Mon, 26 Feb 2007 02:13:08 -0800 (PST) Received: by 10.114.145.9 with HTTP; Mon, 26 Feb 2007 02:13:08 -0800 (PST) Message-ID: <994cd1cf0702260213k7a57b3e5h1c957bbfc8a01be2@mail.gmail.com> Date: Mon, 26 Feb 2007 15:43:08 +0530 From: "aditya kiran" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: PMTU Discovery - How to enable 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, 26 Feb 2007 10:41:22 -0000 Hi, I would like to know how to enable Path MTU Discovery in Free BSD 6.0. Do I need to apply some patch to get it work? Thanks, Adityaa From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 10:48:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1BBB616A403 for ; Mon, 26 Feb 2007 10:48:53 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id AD71813C4A3 for ; Mon, 26 Feb 2007 10:48:52 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 89392 invoked from network); 26 Feb 2007 10:22:12 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 26 Feb 2007 10:22:12 -0000 Message-ID: <45E2BB17.40701@freebsd.org> Date: Mon, 26 Feb 2007 11:48:55 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: aditya kiran References: <994cd1cf0702260213k7a57b3e5h1c957bbfc8a01be2@mail.gmail.com> In-Reply-To: <994cd1cf0702260213k7a57b3e5h1c957bbfc8a01be2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: PMTU Discovery - How to enable 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, 26 Feb 2007 10:48:53 -0000 aditya kiran wrote: > Hi, > I would like to know how to enable Path MTU Discovery in Free BSD 6.0. > Do I need to apply some patch to get it work? No patch is needed. PMTU discovery should be enabled by default on all FreeBSD machines. You can check with "sysctl net.inet.tcp.path_mtu_discovery". -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 11:15:33 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C768816A406 for ; Mon, 26 Feb 2007 11:15:33 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B36EC13C4B8 for ; Mon, 26 Feb 2007 11:15:33 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1QBFX6A005491 for ; Mon, 26 Feb 2007 11:15:33 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1QBFTRX005488 for freebsd-net@FreeBSD.org; Mon, 26 Feb 2007 11:15:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Feb 2007 11:15:29 GMT Message-Id: <200702261115.l1QBFTRX005488@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2007 11:15:33 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue o kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/95665 net [if_tun] "ping: sendto: No buffer space available" wit o kern/106722 net [net] [patch] ifconfig may not connect an interface to o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/109406 net [ndis] Broadcom WLAN driver 4.100.15.5 doesn't work wi 7 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19875 net A new protocol family, PF_IPOPTION, to handle IP optio o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/95267 net packet drops periodically appear f kern/95277 net [netinet] IP Encapsulation mask_match() returns wrong o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n 9 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 11:25:03 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A61DE16A407 for ; Mon, 26 Feb 2007 11:25:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 69F9813C4B9 for ; Mon, 26 Feb 2007 11:25:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1QBP2Np007518 for ; Mon, 26 Feb 2007 11:25:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1QBOsoI007459 for net@FreeBSD.org; Mon, 26 Feb 2007 11:24:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Feb 2007 11:24:56 GMT Message-Id: <200702261124.l1QBOsoI007459@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2007 11:25:03 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/100519 net [netisr] suggestion to fix suboptimal network polling 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 11:50:05 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1569616A401 for ; Mon, 26 Feb 2007 11:50:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id B057E13C4B5 for ; Mon, 26 Feb 2007 11:50:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id EE0654781F for ; Mon, 26 Feb 2007 06:49:57 -0500 (EST) Date: Mon, 26 Feb 2007 11:49:57 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: net@FreeBSD.org Message-ID: <20070226114451.O48828@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Looking for users of IPX over IP tunneling 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, 26 Feb 2007 11:50:05 -0000 Dear all, Over the next couple of weeks, I will be reviewing the set of non-MPSAFE network stack components in preparation for a status update to the arch@ mailing list. One of the remaining components that requires Giant is the IPX over IP tunneling facility (ipx_ip). I'd like to solicit users of this facility, if any, to work with me in testing locking patches I'm currently developing against FreeBSD 7.x. I'm actually not entirely convinced this feature works, so would also like to hear from users of IPX over IP tunneling for this reason. I've found a couple of bugs that would result in improper error messages being returned, etc. There's also a comment in the NOTES file that this feature is "not available". Thanks, Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 11:56:22 2007 Return-Path: X-Original-To: net@hub.freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A7E316A406; Mon, 26 Feb 2007 11:56:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0372A13C4B2; Mon, 26 Feb 2007 11:56:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (rwatson@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1QBuLaE011734; Mon, 26 Feb 2007 11:56:21 GMT (envelope-from rwatson@freefall.freebsd.org) Received: (from rwatson@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1QBuLNL011730; Mon, 26 Feb 2007 11:56:21 GMT (envelope-from rwatson) Date: Mon, 26 Feb 2007 11:56:21 GMT From: Robert Watson Message-Id: <200702261156.l1QBuLNL011730@freefall.freebsd.org> To: rwatson@FreeBSD.org, net@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/100519: [netisr] suggestion to fix suboptimal network polling 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, 26 Feb 2007 11:56:22 -0000 Synopsis: [netisr] suggestion to fix suboptimal network polling Responsible-Changed-From-To: net->freebsd-net Responsible-Changed-By: rwatson Responsible-Changed-When: Mon Feb 26 11:55:47 UTC 2007 Responsible-Changed-Why: Assign to freebsd-net instead of net, since that's the more usual name for net@ assignments. http://www.freebsd.org/cgi/query-pr.cgi?pr=100519 From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 11:56:22 2007 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A7E316A406; Mon, 26 Feb 2007 11:56:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0372A13C4B2; Mon, 26 Feb 2007 11:56:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (rwatson@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1QBuLaE011734; Mon, 26 Feb 2007 11:56:21 GMT (envelope-from rwatson@freefall.freebsd.org) Received: (from rwatson@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1QBuLNL011730; Mon, 26 Feb 2007 11:56:21 GMT (envelope-from rwatson) Date: Mon, 26 Feb 2007 11:56:21 GMT From: Robert Watson Message-Id: <200702261156.l1QBuLNL011730@freefall.freebsd.org> To: rwatson@FreeBSD.org, net@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/100519: [netisr] suggestion to fix suboptimal network polling 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, 26 Feb 2007 11:56:22 -0000 Synopsis: [netisr] suggestion to fix suboptimal network polling Responsible-Changed-From-To: net->freebsd-net Responsible-Changed-By: rwatson Responsible-Changed-When: Mon Feb 26 11:55:47 UTC 2007 Responsible-Changed-Why: Assign to freebsd-net instead of net, since that's the more usual name for net@ assignments. http://www.freebsd.org/cgi/query-pr.cgi?pr=100519 From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 13:55:21 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8ED7D16A403 for ; Mon, 26 Feb 2007 13:55:21 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id F3EB013C478 for ; Mon, 26 Feb 2007 13:55:20 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 90832 invoked from network); 26 Feb 2007 13:28:39 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 26 Feb 2007 13:28:39 -0000 Message-ID: <45E2E6CB.8030707@freebsd.org> Date: Mon, 26 Feb 2007 14:55:23 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Kip Macy References: <45E19B54.9060007@freebsd.org> <45E1A3B4.7090002@freebsd.org> <2a41acea0702252053v2357b5f5tefbcf58375be1a2f@mail.gmail.com> <2a41acea0702252325k4ec64d59m95a63bebaf6ea30c@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net , Jack Vogel Subject: Re: improved TSO interface needed 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, 26 Feb 2007 13:55:21 -0000 Kip Macy wrote: >> 64K is the max, and I believe that is taking into account the headers. >> What size are you seeing that is larger? Even if an mbuf chain comes >> down that large, it does NOT form a single packet, it is packetized by >> the hardware into MTU size, as I said, on the wire, ie as the receiver >> sees it, its just a lot of packets. The only question is whether the >> transmit hardware can handle it. Do you have eivdence of some >> hardware that supports TSO in the driver that cant?? > > I see this when torture testing a couple of different 10GigE cards > running at line rate. Your reported overshooting of 10 bytes is due to a buglet that didn't appear until now. Please try this fix: http://people.freebsd.org/~andre/tso_fix-20070226.diff -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 22:20:24 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0C8816A405 for ; Mon, 26 Feb 2007 22:20:24 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 96A0A13C4A3 for ; Mon, 26 Feb 2007 22:20:24 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l1QMKOib076449 for ; Mon, 26 Feb 2007 14:20:24 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l1QMKOUn076448 for net@freebsd.org; Mon, 26 Feb 2007 14:20:24 -0800 (PST) (envelope-from rizzo) Date: Mon, 26 Feb 2007 14:20:24 -0800 From: Luigi Rizzo To: net@freebsd.org Message-ID: <20070226142024.A76380@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Cc: Subject: making a dumb switch into a smart one 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, 26 Feb 2007 22:20:24 -0000 partly off topic, but maybe someone migth find this interesting given that the device can do vlan tag insertion/removal, so it can be used to provide additional fan-in/fan-out to freebsd-based routers in not too high-speed networks. http://info.iet.unipi.it/~luigi/FreeBSD/edimax/ cheers luigi From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 23:43:28 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC0A916A5FC for ; Mon, 26 Feb 2007 23:43:28 +0000 (UTC) (envelope-from x_element108@btinternet.com) Received: from smtp808.mail.ukl.yahoo.com (smtp808.mail.ukl.yahoo.com [217.12.12.198]) by mx1.freebsd.org (Postfix) with SMTP id 1476013C428 for ; Mon, 26 Feb 2007 23:43:27 +0000 (UTC) (envelope-from x_element108@btinternet.com) Received: (qmail 79467 invoked from network); 26 Feb 2007 23:43:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding; b=0CZ66xPZVLEtaajyQPt71wL1eZHg35HophFkGR92E0rkGu4UKvTuJxNNql6J7l382ftkliWIzdqab+J/q52rwQ2MZ/UrotjdMSzzz1nw89ZKWMkbdLlhplaO12nFZjsGB1mbFykB6XvGc7q2ocunkPkS1jcy0YQZcpi9pwk2Ckc= ; Received: from unknown (HELO ?192.168.1.67?) (x_element108@btinternet.com@86.133.112.228 with plain) by smtp808.mail.ukl.yahoo.com with SMTP; 26 Feb 2007 23:43:26 -0000 X-YMail-OSG: jyOWWGwVM1nFccloW3nmTiqbMez7.KVJT2vv5LhYb3IFPXbFbrnZD0kLlLyVAn_jfdLNWJtYgL8Fhh3VzFFq9Rn.ElBxu.asqyGxAc5mvMPHnKZ2Rq1scYUOhR6_I3L__6P5SFIVp3I- Message-ID: <45E3706C.9020105@btinternet.com> Date: Mon, 26 Feb 2007 23:42:36 +0000 From: "Rajen Jani (BT Yahoo! Broadband)" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: OpenSSH cannot login - PAM Authentication Failure 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, 26 Feb 2007 23:43:28 -0000 Hi everybody, I cannot login to SSH. I use TTSSH as a client on windows. Everytime I type in my host (ritm) password (***) Freebsd comes up with the error "PAM Authentication Failure". I disable PAM from sshd_config but I still get this problem. Any help on this would be much appreciated. Rajen From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 23:45:02 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1F7A16A402 for ; Mon, 26 Feb 2007 23:45:02 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 7750D13C442 for ; Mon, 26 Feb 2007 23:44:58 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from wlan-a-207-213.corp.yahoo.com.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l1QNiXAu037262; Mon, 26 Feb 2007 15:44:33 -0800 (PST) Date: Mon, 26 Feb 2007 15:44:25 -0800 Message-ID: From: gnn@FreeBSD.org To: Anders Nordby In-Reply-To: <20070223121703.GA86159@fupp.net> References: <20070223121703.GA86159@fupp.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.92 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: net@FreeBSD.org Subject: Re: Networking FreeBSD Wiki 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, 26 Feb 2007 23:45:02 -0000 At Fri, 23 Feb 2007 13:17:03 +0100, Anders Nordby wrote: > > Hi, > > George, maybe there should be a separate category in GNATS also, for > network issues? > Instead of being in kern you mean? I have thought that before but I don't control GNATS and we'd have to review a lot of bugs. You could ask Linimon though. Best, George From owner-freebsd-net@FreeBSD.ORG Mon Feb 26 23:55:21 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8780F16A404 for ; Mon, 26 Feb 2007 23:55:21 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 61BB713C4A5 for ; Mon, 26 Feb 2007 23:55:21 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id D965E1E115B; Mon, 26 Feb 2007 18:55:20 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Mon, 26 Feb 2007 18:55:20 -0500 X-Sasl-enc: 165MVt+sHSTcVdKmVKw3zkC3y3aWgXph2xE42OdwmuSn 1172534120 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 492E8CC4C; Mon, 26 Feb 2007 18:55:19 -0500 (EST) Message-ID: <45E37366.4080203@FreeBSD.org> Date: Mon, 26 Feb 2007 23:55:18 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Luigi Rizzo References: <20070226142024.A76380@xorpc.icir.org> In-Reply-To: <20070226142024.A76380@xorpc.icir.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: making a dumb switch into a smart one 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, 26 Feb 2007 23:55:21 -0000 Luigi Rizzo wrote: > partly off topic, but maybe someone migth find this interesting > given that the device can do vlan tag insertion/removal, > so it can be used to provide additional fan-in/fan-out > to freebsd-based routers in not too high-speed networks. > Were you trying to perform the same evil experiment on the Asound 4-port Ethernet 'switch' PCI card which I found in my/your old office at ICSI? ;-) I think it was Juli Mallett who said she had code to deal with the Asound. This is cool. BMS From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 00:10:57 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D43DB16A407; Tue, 27 Feb 2007 00:10:57 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id A643113C474; Tue, 27 Feb 2007 00:10:57 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id E9C081E119F; Mon, 26 Feb 2007 19:10:56 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Mon, 26 Feb 2007 19:10:56 -0500 X-Sasl-enc: nq/VSu6l91fD6tNoS1qJvaGeQeq62nyyCQjNOfd4ehBH 1172535056 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 532E41A1C7; Mon, 26 Feb 2007 19:10:56 -0500 (EST) Message-ID: <45E3770F.1030109@FreeBSD.org> Date: Tue, 27 Feb 2007 00:10:55 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: gnn@FreeBSD.org References: <20070223121703.GA86159@fupp.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anders Nordby , net@FreeBSD.org Subject: Re: Networking FreeBSD Wiki 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, 27 Feb 2007 00:10:57 -0000 gnn@FreeBSD.org wrote: >> >> George, maybe there should be a separate category in GNATS also, for >> network issues? >> > > Instead of being in kern you mean? I have thought that before but I > don't control GNATS and we'd have to review a lot of bugs. > I have noticed there has been a gradual effort over time by the Bugmeisters to classify bugs by putting [netinet] or other strings in the one-line bug synopsis. Whilst this is a great help, it still doesn't address many of the issues we have with GNATS, upon which consensus has not yet been reached as to how to go forward. Personally, I'd like to blow GNATS up and replace it with Bugzilla. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 00:33:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D5B416A404 for ; Tue, 27 Feb 2007 00:33:32 +0000 (UTC) (envelope-from gregm@econet.com) Received: from hubble.sl.econet.com (hubble.sl.econet.com [65.170.12.18]) by mx1.freebsd.org (Postfix) with ESMTP id 808A613C4A6 for ; Tue, 27 Feb 2007 00:33:32 +0000 (UTC) (envelope-from gregm@econet.com) Received: from exchdal02.ecolan.econet.com (exchdal02.ecolan.econet.com [192.168.32.15]) by hubble.sl.econet.com (Postfix) with ESMTP id D3F978FC20 for ; Mon, 26 Feb 2007 18:00:27 -0600 (CST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Date: Mon, 26 Feb 2007 18:00:26 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: OpenSSH cannot login - PAM Authentication Failure Thread-Index: AcdaAVDJSaUcIiXnT96fu+vdAmCJ3wAALLH9 From: "Greg C. Martin" To: "Rajen Jani (BT Yahoo! Broadband)" , X-Virus-Scanned: amavisd-new at econet.com Cc: Subject: RE: OpenSSH cannot login - PAM Authentication Failure 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, 27 Feb 2007 00:33:32 -0000 That usually indicates that you typed a bad password. Also FreeBSD by = default does not allow root logins, try logging in as a standard user = and add them to the wheel group. Or you can add the following to your sshd_config file. PermitRootLogin yes Good luck, Greg -----Original Message----- From: Rajen Jani (BT Yahoo! Broadband) = [mailto:x_element108@btinternet.com] Sent: Mon 2/26/2007 5:42 PM To: freebsd-net@freebsd.org Cc:=09 Subject: OpenSSH cannot login - PAM Authentication Failure Hi everybody, I cannot login to SSH. I use TTSSH as a client on windows. Everytime I type in my host (ritm) password (***) Freebsd comes up with the error "PAM Authentication Failure". I disable PAM from sshd_config but I still get this problem. Any help on this would be much appreciated. Rajen _______________________________________________ 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 Feb 27 00:46:56 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 82C4416A405 for ; Tue, 27 Feb 2007 00:46:56 +0000 (UTC) (envelope-from stom@free.fr) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3E62013C4A5 for ; Tue, 27 Feb 2007 00:46:56 +0000 (UTC) (envelope-from stom@free.fr) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by postfix1-g20.free.fr (Postfix) with ESMTP id B248EAA4A66 for ; Tue, 27 Feb 2007 01:18:01 +0100 (CET) Received: from btn.mine.nu (tok69-1-82-67-36-224.fbx.proxad.net [82.67.36.224]) by smtp2-g19.free.fr (Postfix) with ESMTP id 303018A159; Tue, 27 Feb 2007 01:18:00 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by btn.mine.nu (Postfix) with ESMTP id 80B5C47EE6; Tue, 27 Feb 2007 01:17:41 +0100 (CET) Received: from btn.mine.nu ([127.0.0.1]) by localhost (btn.mine.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22673-01; Tue, 27 Feb 2007 01:17:41 +0100 (CET) Received: from [127.0.0.1] (windows.donblas.lan [192.168.1.200]) by btn.mine.nu (Postfix) with ESMTP id 1DBA947EE5; Tue, 27 Feb 2007 01:17:41 +0100 (CET) Message-ID: <45E3792B.3060108@free.fr> Date: Tue, 27 Feb 2007 01:19:55 +0100 From: Philippe Laquet User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Rajen Jani (BT Yahoo! Broadband)" References: <45E3706C.9020105@btinternet.com> In-Reply-To: <45E3706C.9020105@btinternet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 000717-1, 26/02/2007), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at btn.mine.nu Cc: freebsd-net@freebsd.org Subject: Re: OpenSSH cannot login - PAM Authentication Failure 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, 27 Feb 2007 00:46:56 -0000 Hi Rajen, Can you send your sshd_config and your PAM file for SSH? Is your account a typical Unix account or do you use an alternate authentication method (LDAP/OPIE/*SQL...) Your rc.conf options, especially "sshd_*" sections may also be useful Kind Regards, Philippe Laquet. Rajen Jani (BT Yahoo! Broadband) a écrit : > Hi everybody, > > I cannot login to SSH. I use TTSSH as a client on windows. > Everytime I type in my host (ritm) password (***) Freebsd > comes up with the error "PAM Authentication Failure". I disable PAM from > sshd_config but I still get this problem. Any help on this would be > much appreciated. > > > Rajen > _______________________________________________ > 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 Feb 27 08:22:33 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CCFE16A407 for ; Tue, 27 Feb 2007 08:22:33 +0000 (UTC) (envelope-from tanniru.sankar@wipro.com) Received: from wip-ectls-mx3.wipro.com (wip-ectls-mx3.wipro.com [203.91.193.23]) by mx1.freebsd.org (Postfix) with ESMTP id 758F113C4A3 for ; Tue, 27 Feb 2007 08:22:32 +0000 (UTC) (envelope-from tanniru.sankar@wipro.com) Received: from wip-ectls-mx3.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id D8B5B224351 for ; Tue, 27 Feb 2007 13:26:07 +0530 (IST) Received: from blr-ec-bh01.wipro.com (blr-ec-bh01.wipro.com [10.201.50.91]) by wip-ectls-mx3.wipro.com (Postfix) with ESMTP id CE488224109 for ; Tue, 27 Feb 2007 13:26:07 +0530 (IST) Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-ec-bh01.wipro.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Feb 2007 13:26:07 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 27 Feb 2007 13:29:42 +0530 Message-ID: <8B9F8433B684734581EB519F1A3E5AF47B1D48@blr-m3-msg.wipro.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to enable VLAN interface on normal interface Thread-Index: AcdaRTzMJ66FrOF5T9y2zxFRLENeEQ== From: To: X-OriginalArrivalTime: 27 Feb 2007 07:56:07.0674 (UTC) FILETIME=[BCE4DDA0:01C75A44] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How to enable VLAN interface on normal interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 08:22:33 -0000 Hi, =20 I need some help on enabling VLAN interface on an ethernet interface. Please provide me the steps to configure and enable VLAN interface on FreeBSD 6.0 OS. =20 Thanks The information contained in this electronic message and any attachments to= this message are intended for the exclusive use of the addressee(s) and= may contain proprietary, confidential or privileged information. If you= are not the intended recipient, you should not disseminate, distribute or= copy this e-mail. Please notify the sender immediately and destroy all= copies of this message and any attachments.=20 WARNING: Computer viruses can be transmitted via email. The recipient= should check this email and any attachments for the presence of viruses.= The company accepts no liability for any damage caused by any virus= transmitted by this email. =20 www.wipro.com From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 09:01:16 2007 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33EEA16A405; Tue, 27 Feb 2007 09:01:16 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 05C3513C4B3; Tue, 27 Feb 2007 09:01:15 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from freefall.freebsd.org (thompsa@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1R91FbR094726; Tue, 27 Feb 2007 09:01:15 GMT (envelope-from thompsa@freefall.freebsd.org) Received: (from thompsa@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1R91F9x094722; Tue, 27 Feb 2007 09:01:15 GMT (envelope-from thompsa) Date: Tue, 27 Feb 2007 09:01:15 GMT From: Andrew Thompson Message-Id: <200702270901.l1R91F9x094722@freefall.freebsd.org> To: thompsa@FreeBSD.org, freebsd-rc@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: conf/107035: bridge interface given in rc.conf not taking an (static) IP address 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, 27 Feb 2007 09:01:16 -0000 Synopsis: bridge interface given in rc.conf not taking an (static) IP address Responsible-Changed-From-To: freebsd-rc->freebsd-net Responsible-Changed-By: thompsa Responsible-Changed-When: Tue Feb 27 08:58:47 UTC 2007 Responsible-Changed-Why: This is a limitation of ifconfig rather than rc. The ip address needs to be the first argument, why is this so? http://www.freebsd.org/cgi/query-pr.cgi?pr=107035 From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 09:18:37 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6D6A16A404 for ; Tue, 27 Feb 2007 09:18:37 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id A3F4E13C471 for ; Tue, 27 Feb 2007 09:18:37 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1HLy6n-000CjR-Lk; Tue, 27 Feb 2007 11:54:53 +0300 Date: Tue, 27 Feb 2007 11:54:48 +0300 From: Eygene Ryabinkin To: tanniru.sankar@wipro.com Message-ID: <20070227085447.GR1084@codelabs.ru> References: <8B9F8433B684734581EB519F1A3E5AF47B1D48@blr-m3-msg.wipro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <8B9F8433B684734581EB519F1A3E5AF47B1D48@blr-m3-msg.wipro.com> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.1 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: freebsd-net@freebsd.org Subject: Re: How to enable VLAN interface on normal interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 09:18:38 -0000 > I need some help on enabling VLAN interface on an ethernet interface. > Please provide me the steps to configure and enable VLAN interface on > FreeBSD 6.0 OS. Is your Google worse than mine? See http://people.freebsd.org/~arved/vlan/vlan_en.html, the third link in Google on the request 'freebsd vlan'. -- Eygene From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 09:58:27 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6371F16A404 for ; Tue, 27 Feb 2007 09:58:27 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (www.unsane.co.uk [85.233.185.162]) by mx1.freebsd.org (Postfix) with ESMTP id EA38513C4AC for ; Tue, 27 Feb 2007 09:58:26 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from [10.0.0.178] ([10.0.0.178]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.13.8) with ESMTP id l1R9xFIB025072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Feb 2007 09:59:17 GMT (envelope-from jhary@unsane.co.uk) Message-ID: <45E400B2.7090101@unsane.co.uk> Date: Tue, 27 Feb 2007 09:58:10 +0000 From: Vince User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: Eygene Ryabinkin References: <8B9F8433B684734581EB519F1A3E5AF47B1D48@blr-m3-msg.wipro.com> <20070227085447.GR1084@codelabs.ru> In-Reply-To: <20070227085447.GR1084@codelabs.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: tanniru.sankar@wipro.com, freebsd-net@freebsd.org Subject: Re: How to enable VLAN interface on normal interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 09:58:27 -0000 Eygene Ryabinkin wrote: >> I need some help on enabling VLAN interface on an ethernet interface. >> Please provide me the steps to configure and enable VLAN interface on >> FreeBSD 6.0 OS. >> > > Is your Google worse than mine? > See http://people.freebsd.org/~arved/vlan/vlan_en.html, the third > link in Google on the request 'freebsd vlan'. > Its actually even easier than that these days. using an0 as its the only interface on this laptop. kldload if_vlan ifconfig an0.1 create ifconfig an0.1 an0.1: flags=8842 mtu 1496 ether 00:40:96:43:24:09 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated vlan: 1 parent interface: an0 Vince From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 10:55:49 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C21116A402; Tue, 27 Feb 2007 10:55:49 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8809813C47E; Tue, 27 Feb 2007 10:55:48 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-235-229.51-151.net24.it [151.51.229.235]) (authenticated bits=128) by parrot.aev.net (8.14.0/8.13.8) with ESMTP id l1RB34mT055412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 27 Feb 2007 12:03:10 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.0/8.13.8) with ESMTP id l1RAtvrZ062325; Tue, 27 Feb 2007 11:55:57 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45E40E28.3080700@netfence.it> Date: Tue, 27 Feb 2007 11:55:36 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: "Bruce A. Mah" References: <45DDABA6.60407@netfence.it> <45DDC9CD.1020207@freebsd.org> In-Reply-To: <45DDC9CD.1020207@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.61 on 212.31.247.179 Cc: freebsd-net@freebsd.org Subject: SOLVED: Bridge and NAT problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 10:55:49 -0000 Bruce A. Mah wrote: > If you can, try switching to using if_bridge(4). You (probably) want to > assign the public NAT address to the bridge0 interface, and leave the > physical interfaces making up the bridges (xl0 and rl1 in your case) > unnumbered. I've had good experiences with this type of configuration. I did what you suggested: I don't think anything ever went as smooth as this. So far it's working perfectly. Thanks. bye av. From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 17:38:28 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5602916A400; Tue, 27 Feb 2007 17:38:28 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 3F36513C461; Tue, 27 Feb 2007 17:38:28 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from 20.33.61.10.in-addr.arpa.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l1RHbFZN066353; Tue, 27 Feb 2007 09:37:17 -0800 (PST) Date: Tue, 27 Feb 2007 08:25:08 -0800 Message-ID: From: gnn@FreeBSD.org To: "Bruce M. Simpson" In-Reply-To: <45E3770F.1030109@FreeBSD.org> References: <20070223121703.GA86159@fupp.net> <45E3770F.1030109@FreeBSD.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.92 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Anders Nordby , net@FreeBSD.org Subject: Re: Networking FreeBSD Wiki 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, 27 Feb 2007 17:38:28 -0000 At Tue, 27 Feb 2007 00:10:55 +0000, Bruce M. Simpson wrote: > I have noticed there has been a gradual effort over time by the > Bugmeisters to classify bugs by putting [netinet] or other strings in > the one-line bug synopsis. > > Whilst this is a great help, it still doesn't address many of the issues > we have with GNATS, upon which consensus has not yet been reached as to > how to go forward. > > Personally, I'd like to blow GNATS up and replace it with Bugzilla. We're not going there on this list ;-) Later, George From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 19:35:15 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 19F4216A409 for ; Tue, 27 Feb 2007 19:35:15 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id CF88B13C4A8 for ; Tue, 27 Feb 2007 19:35:14 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 165151FFE7E; Tue, 27 Feb 2007 20:35:11 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 72DF51FFE77; Tue, 27 Feb 2007 20:35: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 14978444885; Tue, 27 Feb 2007 19:33:47 +0000 (UTC) Date: Tue, 27 Feb 2007 19:33:47 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: freebsd-net@freebsd.org In-Reply-To: <45E21468.4060200@netfence.it> Message-ID: <20070227193245.R6506@maildrop.int.zabbadoz.net> References: <45E21468.4060200@netfence.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Andrea Venturoli Subject: Re: LOR with divert sockets 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, 27 Feb 2007 19:35:15 -0000 On Sun, 25 Feb 2007, Andrea Venturoli wrote: > I'll also forward it for inclusion on the list at > http://sources.zabbadoz.net/freebsd/lor.html. # lock order reversal: # 1st 0xc6a37090 inp (divinp) @ sys/netinet/ip_divert.c:336 # 2nd 0xc070a18c tcp (tcp) @ sys/netinet/ip_fw2.c:1982 And I added it with LOR ID #203: http://sources.zabbadoz.net/freebsd/lor.html#203 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 21:00:58 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4CC016A402 for ; Tue, 27 Feb 2007 21:00:58 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: from web52107.mail.yahoo.com (web52107.mail.yahoo.com [206.190.48.110]) by mx1.freebsd.org (Postfix) with SMTP id 52F8F13C4B9 for ; Tue, 27 Feb 2007 21:00:57 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: (qmail 16243 invoked by uid 60001); 27 Feb 2007 21:00:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=MWS8/IlgUHjT1b0eCqZ5hWoSIVD75ZHw86GToWZlKNYmnFu5/raYnHK8jhzO+pzODUwwMFJGRu6QBIoPcXRpvkmB20sv69MbM1kv1SmQZVBILZyuXsOk9dU+FNkiLigE16sgmqXU5I14NVfiS53V12p7QxJN/LoKajBnFPYQAAk=; X-YMail-OSG: 0vNVzyQVM1k7wyqUrbf2vrio85Jh_qK1pnIPp2Nu2qac4jsD71LgZefD4oDfvaTXtDEC.gCyd8LkAn_4cIQ1tazqVXY7buKAmZBeqyYpCu6QM_Xjshv70VNd1Dogr9GTmKEZUfx9OzO3LT0- Received: from [76.2.11.164] by web52107.mail.yahoo.com via HTTP; Tue, 27 Feb 2007 13:00:53 PST Date: Tue, 27 Feb 2007 13:00:53 -0800 (PST) From: Vincent Howell To: freebsd-net@freebsd.org In-Reply-To: MIME-Version: 1.0 Message-ID: <317652.6238.qm@web52107.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Need help with Broadcom wifi WLAN 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, 27 Feb 2007 21:00:58 -0000 I'm using MFC'd one for RELENG_6: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/compat/ndis/subr_ntoskrnl.c?rev=1.71.2.6&content-type=text/x-cvsweb-markup&sortby=date I was getting more "missing feature" errors before trying the patch and upgrading to 6.2-STABLE. I've tried a half a dozen different drivers and none of them worked. But even if they did, I would only want to use driver version 4.100.15.5 or newer because it contains a fix for a nasty security hole on Windows that could indirectly affect BSD via NDISwrapper. Maybe I should try contacting Sam Leffler by email to see if he could modify his patch to fix my problem? All the hardware on my laptop seems to be working. Even ACPI is working (or at least partially, battery reading works, Suspend to RAM almost works (little tweaking?), etc. I would hate to give up simply because a patch needs modifying inorder for my WNIC to operate. Kip Macy wrote: Sam Leffler recently added a new entry in -CURRENT for the part. I think the change needs to MFC'd. Perhaps someone (Max?) could do that. -Kip --------------------------------- We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 21:16:36 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5DCC416A402 for ; Tue, 27 Feb 2007 21:16:36 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: from web52102.mail.yahoo.com (web52102.mail.yahoo.com [206.190.48.105]) by mx1.freebsd.org (Postfix) with SMTP id 0E67913C4A3 for ; Tue, 27 Feb 2007 21:16:35 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: (qmail 78172 invoked by uid 60001); 27 Feb 2007 21:16:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=d1eqiY4SKjiOpZWcTD8vOuxJoEXPBQ/KXcmhTbY0rKI7M9Qcy00VSsWqXaf6jck2oCmjVYtlEy8/BrNuBKIvRHWRM8HxMrl5+oluRdC4ssTX4tO4lFytA9XxFFiqYzp5yGiqtpdSRoSmP7bEwXXsjDLpYVjV9+dWGEcuQ3QlhLc=; X-YMail-OSG: l.CiZBIVM1nrLCSYjGz4dHLT14usroGmk0JAB7lNAap6KD1pT6C.uiBIeCAzpGoy2jXBa8Un2IbpyHs.npLDwDI1X9P6qz6ekscaHiw3d18GuD.Csz_JrotJ_LGggdjlGPh03__w1DaOeOM- Received: from [76.2.11.164] by web52102.mail.yahoo.com via HTTP; Tue, 27 Feb 2007 13:16:35 PST Date: Tue, 27 Feb 2007 13:16:35 -0800 (PST) From: Vincent Howell To: freebsd-net@freebsd.org In-Reply-To: MIME-Version: 1.0 Message-ID: <136799.75448.qm@web52102.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: [Reply] Need help with Broadcom (BCM43XX) WLAN 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, 27 Feb 2007 21:16:36 -0000 Re-sent to bring message upfront. I'm using MFC'd one for RELENG_6: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/compat/ndis/subr_ntoskrnl.c?rev=1.71.2.6&content-type=text/x-cvsweb-markup&sortby=date I was getting more "missing feature" errors before trying the patch and upgrading to 6.2-STABLE.I've tried a half a dozen different drivers and none of them worked. But even if they did, I would only want to use driver version 4.100.15.5 or newer because it contains a fix for a nasty security hole on Windows that could indirectly affect BSD via NDISwrapper. Maybe I should try contacting Sam Leffler by email to see if he could modify his patch to fix my problem? All the hardware on my laptop seems to be working. Even ACPI is working (or at least partially, battery reading works, Suspend to RAM almost works (little tweaking?), etc. I would hate to give up simply because a patch needs modifying inorder for my WNIC to operate. Kip Macy wrote: Sam Leffler recently added a new entry in -CURRENT for the part. I think the change needs to MFC'd. Perhaps someone (Max?) could do that. -Kip --------------------------------- Any questions? Get answers on any topic at Yahoo! Answers. Try it now. From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 21:20:27 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00E9F16A402 for ; Tue, 27 Feb 2007 21:20:27 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187]) by mx1.freebsd.org (Postfix) with ESMTP id 822F213C48D for ; Tue, 27 Feb 2007 21:20:26 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by mu-out-0910.google.com with SMTP id g7so1674679muf for ; Tue, 27 Feb 2007 13:20:25 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nFIpr1pJvfnxnBeNdINBGoKWlk5t+ab2bc0Rze5wu9y+j0gOkVUbul0uwfT9IfzmH5VKOSDHvYY31vFqZvmMMuVLKnsJLNurvzIPsJUvNCuqY3UFtEHsF7Ggv/Zdlx759Y5ASzrpQCHNXg/q8ukBE/lpsrpLEQiwuGMQc12z0J0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X+0M83jmPf7jtODW59YGFIPckmqwAQHgP9q9z200cm+jr4cUb663G7qV/q5fS+lUDa326phI82j2qh6ErXLZ935EGZZyRfm4b6D3EG+u5mPebOkjrWbThHcaVV81jDuCO1cnvPb3GLWPWj6aTClhZGAZrCmse4XQvRzcPJSKHSE= Received: by 10.82.107.15 with SMTP id f15mr2305972buc.1172611224434; Tue, 27 Feb 2007 13:20:24 -0800 (PST) Received: by 10.82.151.15 with HTTP; Tue, 27 Feb 2007 13:20:24 -0800 (PST) Message-ID: Date: Tue, 27 Feb 2007 13:20:24 -0800 From: "Kip Macy" To: "Vincent Howell" In-Reply-To: <317652.6238.qm@web52107.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <317652.6238.qm@web52107.mail.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: Need help with Broadcom wifi WLAN 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, 27 Feb 2007 21:20:27 -0000 On 2/27/07, Vincent Howell wrote: > I'm using MFC'd one for RELENG_6: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/compat/ndis/subr_ntoskrnl.c?rev=1.71.2.6&content-type=text/x-cvsweb-markup&sortby=date > > I was getting more "missing feature" errors before trying the patch and upgrading to 6.2-STABLE. > > I've tried a half a dozen different drivers and none of them worked. But even if they did, I would only want to use driver version 4.100.15.5 or newer because it contains a fix for a nasty security hole on Windows that could indirectly affect BSD via NDISwrapper. > > Maybe I should try contacting Sam Leffler by email to see if he could modify his patch to fix my problem? Sam is really busy right now (I am too :-( ). If someone hasn't gotten to it in a week ping me again and I will try to fix it. I need to set up a RELENG_6 install this weekend anyway. -Kip From owner-freebsd-net@FreeBSD.ORG Tue Feb 27 22:24:29 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0962C16A400 for ; Tue, 27 Feb 2007 22:24:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id AE43013C428 for ; Tue, 27 Feb 2007 22:24:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 161F04A185; Tue, 27 Feb 2007 17:24:28 -0500 (EST) Date: Tue, 27 Feb 2007 22:24:27 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: freebsd-net@freebsd.org In-Reply-To: <45E21468.4060200@netfence.it> Message-ID: <20070227222316.R60173@fledge.watson.org> References: <45E21468.4060200@netfence.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: kris@obsecurity.org Subject: Re: LOR with divert sockets 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, 27 Feb 2007 22:24:29 -0000 On Sun, 25 Feb 2007, Andrea Venturoli wrote: > I posted the following message to questions and Kris (which I thank) kindly > suggested I should ask here wether someone is working on this. I'll also > forward it for inclusion on the list at > http://sources.zabbadoz.net/freebsd/lor.html. > > BTW, I don't think the hangs I'm experiencing depend on this, but they might > be important to you anyway. What versions of ip_fw2.c and ip_divert.c were in use? The line numbers aren't as useful without matching revision number information. I'm pretty sure I've fixed this, but it suddenly occurs to me that I may not have committed the fix. Also, could you let me know if you use any uid/gid rules in your IPFW rule set? Thanks, Robert N M Watson Computer Laboratory University of Cambridge > > bye & Thanks > av. > > > ------------------------ > Hello. > As I have already written to this list, several of my 6.2 servers are > hanging very frequently. > I've managed to turn on the following options on one of them: > >> options KDB >> options DDB >> options KDB_UNATTENDED >> options INVARIANTS >> options INVARIANT_SUPPORT >> options WITNESS >> options DEBUG_LOCKS >> options DEBUG_VFS_LOCKS >> options DIAGNOSTIC > > I hope I can do that soon on the others too. > In the meanwhile I have seen this in the log: > >> Feb 24 17:51:53 soth kernel: lock order reversal: >> Feb 24 17:51:53 soth kernel: 1st 0xc6a37090 inp (divinp) @ >> /usr/src/sys/netinet/ip_divert.c:336 >> Feb 24 17:51:53 soth kernel: 2nd 0xc070a18c tcp (tcp) @ >> /usr/src/sys/netinet/ip_fw2.c:1982 >> Feb 24 17:51:53 soth kernel: KDB: stack backtrace: >> Feb 24 17:51:53 soth kernel: >> kdb_backtrace(0,ffffffff,c06c8f10,c06cadb0,c0694084,...) at >> kdb_backtrace+0x29 >> Feb 24 17:51:53 soth kernel: witness_checkorder(c070a18c,9,c0665b07,7be) at >> witness_checkorder+0x578 >> Feb 24 17:51:53 soth kernel: _mtx_lock_flags(c070a18c,0,c0665b07,7be) at >> _mtx_lock_flags+0x78 >> Feb 24 17:51:53 soth kernel: >> check_uidgid(c6a890b0,6,c6507800,46c046c1,6e,...) at check_uidgid+0xdf >> Feb 24 17:51:53 soth kernel: ipfw_chk(e6cc49f0,c6cfdb00,c6507800,0,0,...) >> at ipfw_chk+0xd74 >> Feb 24 17:51:53 soth kernel: ipfw_check_out(0,e6cc4ae8,c6507800,2,0) at >> ipfw_check_out+0xe0 >> Feb 24 17:51:53 soth kernel: >> pfil_run_hooks(c0709d40,e6cc4b5c,c6507800,2,0,...) at pfil_run_hooks+0xc9 >> Feb 24 17:51:53 soth kernel: ip_output(c6cfdb00,0,e6cc4b28,22,0,...) at >> ip_output+0x66a >> Feb 24 17:51:53 soth kernel: >> div_output(c67a8000,c6cfdb00,c6b35be0,0,e6cc4c08,...) at div_output+0x185 >> Feb 24 17:51:53 soth kernel: div_send(c67a8000,0,c6cfdb00,c6b35be0,0,...) >> at div_send+0x3f >> Feb 24 17:51:53 soth kernel: >> Feb 24 17:51:53 soth kernel: >> sosend(c67a8000,c6b35be0,e6cc4c3c,c6cfdb00,0,0,c657aa80) at sosend+0x5eb >> Feb 24 17:51:53 soth kernel: kern_sendit(c657aa80,3,e6cc4cbc,0,0,0) at >> kern_sendit+0x104 >> Feb 24 17:51:53 soth kernel: sendit(c657aa80,3,e6cc4cbc,0,bfbdebc4,...) at >> sendit+0x163 >> Feb 24 17:51:53 soth kernel: sendto(c657aa80,e6cc4d04) at sendto+0x4d >> Feb 24 17:51:53 soth kernel: syscall(3b,3b,3b,2,34,...) at syscall+0x25b >> Feb 24 17:51:53 soth kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f >> Feb 24 17:51:53 soth kernel: --- syscall (133, FreeBSD ELF32, sendto), eip >> = 0x2812ef43, esp = 0xbfbdeafc, ebp = 0xbfbeeba8 --- >> Feb 24 17:51:53 soth kernel: ipfw: 65534 Deny TCP 192.168.0.3:52325 >> 193.70.192.70:110 out via xl0 > > > Any comments? > > I hope I can provide other, possibly more useful informations, in the > near future. > > bye & Thanks > av. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > 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 Feb 27 23:46:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C1F0916AFB6 for ; Tue, 27 Feb 2007 23:46:53 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: from web52110.mail.yahoo.com (web52110.mail.yahoo.com [206.190.48.113]) by mx1.freebsd.org (Postfix) with SMTP id 741A113C428 for ; Tue, 27 Feb 2007 23:46:51 +0000 (UTC) (envelope-from darkvincentdude@yahoo.com) Received: (qmail 56632 invoked by uid 60001); 27 Feb 2007 23:46:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=PlQUd9vJ6pWh14ADNExfhxvAf3y9obGPQf8iyIBHd/8UDHtn+CCmnu+EVkpnynV6qfp8XYtWFb8z3dPskhhIAZ0BH3WIWedhRIEdLK0SZJqV5OXXk3YrwGO9jITcb/Hy9VGK8xNZwz4VcnIqZx5EwPCtydZbWwbW2Qqn2R8mNOM=; X-YMail-OSG: E6ro7_YVM1mEkvcfj2G_zsVkaDIQGYGT7fPOdJZk8ucVQmFcU_aNK9BXf8g5JFV.a73mVL69FvlKUw159W4.qK3YmpYkCFSfpAVeAnoQZzlj4ctKJj.n Received: from [76.2.11.164] by web52110.mail.yahoo.com via HTTP; Tue, 27 Feb 2007 15:46:47 PST Date: Tue, 27 Feb 2007 15:46:47 -0800 (PST) From: Vincent Howell To: freebsd-net@freebsd.org In-Reply-To: MIME-Version: 1.0 Message-ID: <66342.55652.qm@web52110.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Need help with Broadcom wifi WLAN 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, 27 Feb 2007 23:46:53 -0000 OK I'll do that. Thanks, I appreciate the very generous offer. :-) Cheers Kip Macy wrote: Sam is really busy right now (I am too :-( ). If someone hasn't gotten to it in a week ping me again and I will try to fix it. I need to set up a RELENG_6 install this weekend anyway. -Kip --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 08:38:33 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15C2D16A400 for ; Wed, 28 Feb 2007 08:38:33 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 9473013C4B4 for ; Wed, 28 Feb 2007 08:38:32 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-42-242.51-151.net24.it [151.51.242.42]) (authenticated bits=128) by parrot.aev.net (8.14.0/8.13.8) with ESMTP id l1S8jrxQ024495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 28 Feb 2007 09:46:00 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.0/8.13.8) with ESMTP id l1S8cmgE021824; Wed, 28 Feb 2007 09:38:48 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45E53F7D.4030703@netfence.it> Date: Wed, 28 Feb 2007 09:38:21 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: Robert Watson References: <45E21468.4060200@netfence.it> <20070227222316.R60173@fledge.watson.org> In-Reply-To: <20070227222316.R60173@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.61 on 212.31.247.179 Cc: freebsd-net@freebsd.org Subject: Re: LOR with divert sockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 08:38:33 -0000 Robert Watson wrote: > What versions of ip_fw2.c and ip_divert.c were in use? From i386/6.2-RELEASE-p1, i.e.: src/sys/netinet/ip_fw2.c,v 1.106.2.21 2006/10/10 18:39:38 bz src/sys/netinet/ip_divert.c,v 1.113.2.2 2006/05/16 07:27:48 ps > Also, could you let me know if you use any > uid/gid rules in your IPFW rule set? Yep. 04000 allow tcp from me to any uid squid out via xl0 setup keep-state I use this to allow squid to retrieve everything according to its own security settings. > Thanks, Thanks to you. bye av. From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 08:48:01 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D22316A402 for ; Wed, 28 Feb 2007 08:48:01 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by mx1.freebsd.org (Postfix) with ESMTP id 6A5B613C48D for ; Wed, 28 Feb 2007 08:48:01 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 28 Feb 2007 00:48:01 -0800 X-IronPort-AV: i="4.14,228,1170662400"; d="scan'208"; a="394643287:sNHT53914828" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l1S8m1td019304 for ; Wed, 28 Feb 2007 00:48:01 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l1S8m1Gk025856 for ; Wed, 28 Feb 2007 00:48:01 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 00:48:00 -0800 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 00:48:00 -0800 Message-ID: <45E541A2.4020005@cisco.com> Date: Wed, 28 Feb 2007 03:47:30 -0500 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6 MIME-Version: 1.0 To: freebsd-net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Feb 2007 08:48:00.0679 (UTC) FILETIME=[26CD7B70:01C75B15] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1392; t=1172652481; x=1173516481; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Thinking=20about=20IPv6=20and=20DEPRECATED=20addresses |Sender:=20; bh=ag6hOXEs0k7x5ORvHTMKevVsGZOsVy27HK1BLV5qI9U=; b=MeuD4vQ+T+c/lAclfI4/7PvqQ7CcFhCf13WnlQVu5hOdiLYhuJR7k2PlF3v4ledYC6KHnwbh yYIw+CFC78IuIc7dtPZAbQuwRHvlW3GNVrKuRx5bXvT/L7117i4VmEMn; Authentication-Results: sj-dkim-2; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim2002 verified; ); Subject: Thinking about IPv6 and DEPRECATED addresses 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, 28 Feb 2007 08:48:01 -0000 All: I have been deep in the middle of breaking SCTP's dependencies on looking at ifa structures... One of the problems I have run in to is that V6 has this additional set of flags: ifa6->ia6_flags And it can have things like: IN6_IFF_DEPRECATED IN6_IFF_DETACHED IN6_IFF_ANYCAST IN6_IFF_NOTREADY Now obviously if you have a deprecated or detached address you probably do not want to use them.. nor do you want to use a "NOTREADY" since I think that means that DAD has not finished... So, I am contemplating adding to rtsock.c the ability to send these types of events up. I am thinking on adding this there for two reasons.. a) SCTP already hooks into the routing socket to get interface changes. and b) It may well be a relevant fact that if an address becomes DETACHED or non-DETACHED (etc) for a routing process to want to know about.. What do others think? If I am off in the weeds somewhere and this does not concern the routing socket I could use other methods .. including isolating the "look at the state" flags into a special place so that proper locking could be added when we actually do locking for the ifa's... of course I would prefer just not to have to look at it :-D Opinions if this is a good idea or not?? Thanks R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 08:50:55 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F85516A403 for ; Wed, 28 Feb 2007 08:50:55 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 1512613C494 for ; Wed, 28 Feb 2007 08:50:55 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 5CEC21FFD8E; Wed, 28 Feb 2007 09:50:53 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id E25621FFEB2; Wed, 28 Feb 2007 09:50:47 +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 36ECF444885; Wed, 28 Feb 2007 08:50:41 +0000 (UTC) Date: Wed, 28 Feb 2007 08:50:40 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: freebsd-net@freebsd.org In-Reply-To: <45E53F7D.4030703@netfence.it> Message-ID: <20070228084928.Y64827@maildrop.int.zabbadoz.net> References: <45E21468.4060200@netfence.it> <20070227222316.R60173@fledge.watson.org> <45E53F7D.4030703@netfence.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Robert Watson Subject: Re: LOR with divert sockets 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, 28 Feb 2007 08:50:55 -0000 On Wed, 28 Feb 2007, Andrea Venturoli wrote: > Robert Watson wrote: > >> What versions of ip_fw2.c and ip_divert.c were in use? > > From i386/6.2-RELEASE-p1, i.e.: > src/sys/netinet/ip_fw2.c,v 1.106.2.21 2006/10/10 18:39:38 bz > src/sys/netinet/ip_divert.c,v 1.113.2.2 2006/05/16 07:27:48 ps > > > >> Also, could you let me know if you use any uid/gid rules in your IPFW rule >> set? > > Yep. > > 04000 allow tcp from me to any uid squid out via xl0 setup keep-state > > I use this to allow squid to retrieve everything according to its own > security settings. I am unsure but this should still be true for at least RELENG_6. I can only remember that there was work in progress but cannot remmember things were patched and where or not... %man ipfw | col -b | grep -5 'Rules which use uid' | tail -7 | head -5 Rules which use uid, gid or jail based matching should be used only if debug.mpsafenet=0 to avoid possible deadlocks due to layering violations in its implementation. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 09:45:42 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18D3516A400; Wed, 28 Feb 2007 09:45:42 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 7B68813C442; Wed, 28 Feb 2007 09:45:41 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-42-242.51-151.net24.it [151.51.242.42]) (authenticated bits=128) by parrot.aev.net (8.14.0/8.13.8) with ESMTP id l1S9r3Nu033611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 28 Feb 2007 10:53:09 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.0/8.13.8) with ESMTP id l1S9juVW034308; Wed, 28 Feb 2007 10:45:57 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45E54F39.4050204@netfence.it> Date: Wed, 28 Feb 2007 10:45:29 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <45E21468.4060200@netfence.it> <20070227222316.R60173@fledge.watson.org> <45E53F7D.4030703@netfence.it> <20070228084928.Y64827@maildrop.int.zabbadoz.net> In-Reply-To: <20070228084928.Y64827@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.61 on 212.31.247.179 Cc: freebsd-net@freebsd.org, Robert Watson Subject: Re: LOR with divert sockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 09:45:42 -0000 Bjoern A. Zeeb wrote: > I am unsure but this should still be true for at least RELENG_6. I > can only remember that there was work in progress but cannot remmember > things were patched and where or not... > > %man ipfw | col -b | grep -5 'Rules which use uid' | tail -7 | head -5 > > Rules which use uid, gid or jail based matching should be used only if > debug.mpsafenet=0 to avoid possible deadlocks due to layering > violations > in its implementation. > > Thanks, this is very interesting. I see this paragraph was added in 6.x, and I admit I never saw it. In fact I had been using uid rules in 5.x without any trouble. Shouldn't this be mentioned in the ERRATA document? I guess no one really reads *all* the man pages again, after an upgrade. First off, I searched for what debug.mpsafe does and came up with some vague description. Are there any reason not to disable this? Second. I grasped the idea that this is important in SMP boxes, but I'm not sure. Does it affect UP boxes too? I'm currently having: _ 1 SMP box *with* one uid rule which occasionally hangs (running INVARIANTS&Co and from which my report was taken); _ 1 SMP box *without* uid rules which occasionally hangs (running INVARIANTS&Co); _ 1 UP box *with* one uid rule which frequently hangs (I'm turning INVARIANTS&Co on this afternoon on this one); _ 1 UP box *with* one uid rule which frequently hangs (I'm turning SMP and INVARIANTS&Co on this afternoon on this one); _ 2 UP boxes *with* one uid rule which never ever hanged. IMHO the uid rule problems could explain half of the data above, but then again, I guess it can also depend on network load, hardware type or other combinations of things. If there are no bigger drawbacks (I don't care for speed as much as I do for stability), I might disable debug.mpsafenet today. Comments? bye & Thanks av. From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 10:14:08 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B225216A40D for ; Wed, 28 Feb 2007 10:14:08 +0000 (UTC) (envelope-from j.witteveen@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 4C94813C48D for ; Wed, 28 Feb 2007 10:14:08 +0000 (UTC) (envelope-from j.witteveen@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so72185ugh for ; Wed, 28 Feb 2007 02:14:07 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=VHJHVF1nZv8EvJTSYrdFddBe5Yo+xedIw0oVKVnq7O+ZHbvDMDRl4PUpItot7OIq6uqJA62lNQYoDu9s0R4Vz/MUU/er1E0RD2bCAAtqCdbiYBeCJODaLOZyLwGIR2fERPbkXBoOce0g9LCPgZBh8zLQSGzx1ufu/bCM8hMMd6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=BH7ldayMuw+BaeCYRPUOrJaRoz2T53flihRDsULFkasWQT44t5pMTfI8+6cSYvaTxyvnrCV1XdKtZ6Bxnw8vW8uXjrZ05CV9BLVhWwOooIX0QSMmoNx6Ilil7feKiASHmgTk4TEBvDT09HmNmm8OXenuwwN/Wv4GtfSPA2csxcs= Received: by 10.114.78.1 with SMTP id a1mr92914wab.1172657645638; Wed, 28 Feb 2007 02:14:05 -0800 (PST) Received: by 10.114.182.9 with HTTP; Wed, 28 Feb 2007 02:14:05 -0800 (PST) Message-ID: <3993a4980702280214uf7deddfr4660b0cbdff4d3d1@mail.gmail.com> Date: Wed, 28 Feb 2007 11:14:05 +0100 From: "Jouke Witteveen" To: sam@errno.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-net@freebsd.org, hostap@shmoo.com Subject: FreeBSD version of wired wpa_supplicant driver 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, 28 Feb 2007 10:14:08 -0000 Dear mister Leffler, Hello all, Lately I have been trying to make wpa_supplicant work for wired interfaces on FreeBSD. The driver_wired.c code of the supplicant has been corrected to ask for multicast membership the right way, and if.c has been updated to handle multicast requests properly (special thanks to Bruce Simpson). Some testing with wpa_supplicant 0.5.7 show that a little more work needs to be done. Monitoring traffic with tcpdump (*not* going promiscious) I can see how, on FreeBSD, wpa authentication is started properly, but a response to the server's 'Request Identity' is not sent. In Linux this response is sent immediately. I suspect l2_packet_freebsd.c to not properly receive the packages (ie l2_packet_receive fails to work) because the initial frame is sent out correctly. As I can think of now there are two possible solutions. One being a revision of the existing l2-freebsd code, the other a override on receiving frames for the wired driver. As I'm not a fast programmer on these matters I send out this e-mail as a request for help and an assurance for me that I am not duplicating someone else's efforts. Regards, - Jouke From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 11:33:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 57D3916A401 for ; Wed, 28 Feb 2007 11:33:54 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by mx1.freebsd.org (Postfix) with ESMTP id DDBA913C47E for ; Wed, 28 Feb 2007 11:33:53 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.66.35.158] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1HMN4B19bK-0002qi; Wed, 28 Feb 2007 12:33:52 +0100 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Wed, 28 Feb 2007 12:33:42 +0100 User-Agent: KMail/1.9.5 References: <45E541A2.4020005@cisco.com> In-Reply-To: <45E541A2.4020005@cisco.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7924588.U0Mz05VLzK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200702281233.50145.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 X-Provags-ID2: V01U2FsdGVkX1+j+d614w0gE9hAq/23lNj+4myxY12i/Pf/eZ5 pFTu3uO6uHNd7RGQrJYFbAeBj4TMTxk2m6mLI/4vre1lXxrSbK Tx+LGL/q4FFHVRHN9OwrQ== Cc: Tsuyoshi MOMOSE , Randall Stewart Subject: Re: Thinking about IPv6 and DEPRECATED addresses 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, 28 Feb 2007 11:33:54 -0000 --nextPart7924588.U0Mz05VLzK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 28 February 2007 09:47, Randall Stewart wrote: > All: > > I have been deep in the middle of breaking SCTP's dependencies on > looking at ifa structures... > > One of the problems I have run in to is that V6 has this > additional set of flags: > ifa6->ia6_flags > > And it can have things like: > IN6_IFF_DEPRECATED > IN6_IFF_DETACHED > IN6_IFF_ANYCAST > IN6_IFF_NOTREADY > > Now obviously if you have a deprecated or detached address > you probably do not want to use them.. nor do you want to > use a "NOTREADY" since I think that means that DAD has not > finished... > > So, I am contemplating adding to rtsock.c the ability to > send these types of events up. I am thinking on adding > this there for two reasons.. > > a) SCTP already hooks into the routing socket to get > interface changes. > and > > b) It may well be a relevant fact that if an address becomes > DETACHED or non-DETACHED (etc) for a routing process > to want to know about.. > > > What do others think? If I am off in the weeds somewhere and > this does not concern the routing socket I could use other > methods .. including isolating the "look at the state" flags > into a special place so that proper locking could be added > when we actually do locking for the ifa's... of course I would > prefer just not to have to look at it :-D > > Opinions if this is a good idea or not?? Great idea. I'm also CC-ing Tsuyoshi MOMOSE who is working on importing=20 MIP6 which will likely be interested in this information (in userland) as=20 well. AFAIK, the mnd already listens on the rtsock to pick up new=20 addresses as soon as possible, but not sooner (for which it has to go=20 through great lengths). =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart7924588.U0Mz05VLzK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBF5WieXyyEoT62BG0RAvDxAJ917kfUN6J3U6qh2AXsneBzVCkpTQCfWSdZ YgE0oy1EdmEYmJX3Koy+/NY= =IXVq -----END PGP SIGNATURE----- --nextPart7924588.U0Mz05VLzK-- From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 11:55:24 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F238E16A403 for ; Wed, 28 Feb 2007 11:55:24 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from mx28.mail.ru (mx28.mail.ru [194.67.23.67]) by mx1.freebsd.org (Postfix) with ESMTP id A931413C471 for ; Wed, 28 Feb 2007 11:55:24 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f62.mail.ru (f62.mail.ru [194.67.57.96]) by mx28.mail.ru (mPOP.Fallback_MX) with ESMTP id 5899476D2E6 for ; Wed, 28 Feb 2007 14:28:22 +0300 (MSK) Received: from mail by f62.mail.ru with local id 1HMMyj-000IC7-00 for freebsd-net@freebsd.org; Wed, 28 Feb 2007 14:28:13 +0300 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Wed, 28 Feb 2007 14:28:13 +0300 From: dima <_pppp@mail.ru> To: freebsd-net@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Wed, 28 Feb 2007 14:28:13 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Subject: is CARP still impossible on SMP in 6.2? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 11:55:25 -0000 Hello, all. I'm trying to make CARP working on a 2-Xeon hardware. It worked OK on 5.5, but not on 6.2. The result of compiling both options SMP device carp into the kernel makes it crash in 'swi1: net' kernel thread on a random (usually first) use of the CARP facility. Regards, Dmitriy. From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 12:25:06 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 48D1616A402 for ; Wed, 28 Feb 2007 12:25:06 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.freebsd.org (Postfix) with ESMTP id C3FAE13C4A5 for ; Wed, 28 Feb 2007 12:25:05 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id l1SCOx4u097219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Feb 2007 15:25:00 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id l1SCOxAH097218; Wed, 28 Feb 2007 15:24:59 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 28 Feb 2007 15:24:59 +0300 From: Gleb Smirnoff To: dima <_pppp@mail.ru> Message-ID: <20070228122459.GK1621@FreeBSD.org> Mail-Followup-To: Gleb Smirnoff , dima <_pppp@mail.ru>, freebsd-net@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: is CARP still impossible on SMP in 6.2? 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, 28 Feb 2007 12:25:06 -0000 On Wed, Feb 28, 2007 at 02:28:13PM +0300, dima wrote: d> I'm trying to make CARP working on a 2-Xeon hardware. It worked OK on 5.5, but not on 6.2. d> The result of compiling both d> options SMP d> device carp d> into the kernel makes it crash in 'swi1: net' kernel thread on a random (usually first) use of the CARP facility. Can you please provide a backtrace? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 15:08:26 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56BEC16A400 for ; Wed, 28 Feb 2007 15:08:26 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f21.mail.ru (f21.mail.ru [194.67.57.54]) by mx1.freebsd.org (Postfix) with ESMTP id 120F113C4CC for ; Wed, 28 Feb 2007 15:08:26 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from mail by f21.mail.ru with local id 1HMQPl-0005hz-00; Wed, 28 Feb 2007 18:08:21 +0300 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Wed, 28 Feb 2007 18:08:21 +0300 From: dima <_pppp@mail.ru> To: Gleb Smirnoff Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Wed, 28 Feb 2007 18:08:21 +0300 In-Reply-To: <20070228122459.GK1621@FreeBSD.org> References: <20070228122459.GK1621@FreeBSD.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Cc: freebsd-net@FreeBSD.org Subject: Re[2]: is CARP still impossible on SMP in 6.2? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 15:08:26 -0000 > On Wed, Feb 28, 2007 at 02:28:13PM +0300, dima wrote: > d> I'm trying to make CARP working on a 2-Xeon hardware. It worked OK on 5.5, but not on 6.2. > d> The result of compiling both > d> options SMP > d> device carp > d> into the kernel makes it crash in 'swi1: net' kernel thread on a random (usually first) use of the CARP facility. > > Can you please provide a backtrace? It's not that easy. The server becomes extremely unstable under these conditions. I tried to build the kernel with '-g' option and included 'dumpdev' in /etc/rc.conf. The server can't even make a memory dump: it either gets one more page fault or just stops responding to anything but Reset key in the beginning of the dump. It's strange since it rebooted well while the kernel was built without debugging symbols and a dumpdev. Any ideas how I can make a memory dump? From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 16:45:01 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CDA2516A404 for ; Wed, 28 Feb 2007 16:45:01 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 17A2E13C491 for ; Wed, 28 Feb 2007 16:44:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 13B7AEB70F6; Thu, 1 Mar 2007 00:44:58 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id 0A56Bgs5fBXk; Thu, 1 Mar 2007 00:44:47 +0800 (CST) Received: from [192.168.1.32] (unknown [221.219.159.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id BC54FEB3534; Thu, 1 Mar 2007 00:44:46 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to:cc: subject:references:in-reply-to:x-enigmail-version:content-type; b=E61vSF1s6DpLUzqOWuAoq4Ng2roSPDfK4DekUCWll6fU95ZEl/BcMro9hHR+GgcnT k/K69dwhVa4djMgIbLTKQ== Message-ID: <45E5B176.1010303@delphij.net> Date: Thu, 01 Mar 2007 00:44:38 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: LI Xin References: <45D85A88.4040402@delphij.net> In-Reply-To: <45D85A88.4040402@delphij.net> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig9FF510FAE24CDAF5DB54513C" Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Feature request: exit netstat(1) after user specified outputs 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, 28 Feb 2007 16:45:01 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9FF510FAE24CDAF5DB54513C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, If no one objects this change, I will commit it? LI Xin wrote: > Hi, >=20 > This is a patch that I have backported to -CURRENT, which is originally= > made against RELENG_6_2. >=20 > I have received several feature requests from our local community which= > they wanted to have a top(1)'s '-d' alike feature for netstat, so they > will be able to use netstat(1) as a handy brick when building monitorin= g > scripts. >=20 > So here is the patchset that adds a '-q' option, which accepts a > numerical argument meaning how many outputs are going out before we exi= t. >=20 > Comments? (I think 'q' is arguable, but netstat(1) has too many option= s :-) >=20 > Cheers, >=20 >=20 > -----------------------------------------------------------------------= - >=20 > Index: if.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/usr.bin/netstat/if.c,v > retrieving revision 1.66 > diff -u -p -r1.66 if.c > --- if.c 8 Nov 2006 15:15:05 -0000 1.66 > +++ if.c 18 Feb 2007 13:37:32 -0000 > @@ -676,6 +676,8 @@ loop: > (void)alarm(interval1); > line++; > first =3D 0; > + if (qflag && (qval-- =3D=3D 0)) > + exit(0); > if (line =3D=3D 21) > goto banner; > else > Index: main.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/usr.bin/netstat/main.c,v > retrieving revision 1.83 > diff -u -p -r1.83 main.c > --- main.c 28 Jul 2006 16:16:40 -0000 1.83 > +++ main.c 18 Feb 2007 13:29:11 -0000 > @@ -295,6 +295,8 @@ int mflag; /* show memory stats */ > int numeric_addr; /* show addresses numerically */ > int numeric_port; /* show ports numerically */ > static int pflag; /* show given protocol */ > +int qflag; /* whether to quit after specified outputs */ > +int qval; /* how much outputs before we exit */ > int rflag; /* show routing tables (or routing stats) */ > int sflag; /* show protocol statistics */ > int tflag; /* show i/f watchdog timers */ > @@ -316,7 +318,7 @@ main(int argc, char *argv[]) > =20 > af =3D AF_UNSPEC; > =20 > - while ((ch =3D getopt(argc, argv, "AaBbdf:ghI:iLlM:mN:np:rSstuWw:z"))= !=3D -1) > + while ((ch =3D getopt(argc, argv, "AaBbdf:ghI:iLlM:mN:np:q:rSstuWw:z"= )) !=3D -1) > switch(ch) { > case 'A': > Aflag =3D 1; > @@ -400,6 +402,10 @@ main(int argc, char *argv[]) > } > pflag =3D 1; > break; > + case 'q': > + qval =3D atoi(optarg); > + qflag =3D 1; > + break; > case 'r': > rflag =3D 1; > break; > Index: netstat.1 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/usr.bin/netstat/netstat.1,v > retrieving revision 1.57 > diff -u -p -r1.57 netstat.1 > --- netstat.1 29 Sep 2006 15:20:46 -0000 1.57 > +++ netstat.1 18 Feb 2007 13:40:17 -0000 > @@ -130,6 +130,7 @@ is also present, print interface names u > .Nm > .Fl w Ar wait > .Op Fl I Ar interface > +.Op Fl q Ar howmany > .Op Fl d > .Op Fl M Ar core > .Op Fl N Ar system > @@ -143,6 +144,11 @@ traffic on all configured network interf > or a single > .Ar interface . > If > +.Fl q > +is also present, exit after > +.Ar howmany > +outputs. > +If > .Fl d > is also present, show the number of dropped packets. > .It Xo > Index: netstat.h > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/usr.bin/netstat/netstat.h,v > retrieving revision 1.48 > diff -u -p -r1.48 netstat.h > --- netstat.h 28 Jul 2006 16:09:18 -0000 1.48 > +++ netstat.h 18 Feb 2007 13:19:41 -0000 > @@ -47,6 +47,8 @@ extern int Lflag; /* show size of listen > extern int mflag; /* show memory stats */ > extern int numeric_addr; /* show addresses numerically */ > extern int numeric_port; /* show ports numerically */ > +extern int qflag; /* whether to quit after specified outputs */ > +extern int qval; /* how much outputs before we exit */ > extern int rflag; /* show routing tables (or routing stats) */ > extern int sflag; /* show protocol statistics */ > extern int tflag; /* show i/f watchdog timers */ Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig9FF510FAE24CDAF5DB54513C 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.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5bF2OfuToMruuMARCnxeAJ9o/+p1LfdVwNhVfLzzzk8dl86ChgCeOLd9 dYK8PsvqREy3xq/ttMCM94s= =FSzP -----END PGP SIGNATURE----- --------------enig9FF510FAE24CDAF5DB54513C-- From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 19:12:27 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01C1B16A406 for ; Wed, 28 Feb 2007 19:12:27 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id C6FA613C47E for ; Wed, 28 Feb 2007 19:12:26 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 5088E1F4428; Wed, 28 Feb 2007 14:12:26 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 28 Feb 2007 14:12:26 -0500 X-Sasl-enc: ccLA08QXGK2l5U5/KLVvL4bpp+NhZ9StJJL7eu4qv9dS 1172689946 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id B1BEA105A3; Wed, 28 Feb 2007 14:12:25 -0500 (EST) Message-ID: <45E5D417.9000403@FreeBSD.org> Date: Wed, 28 Feb 2007 19:12:23 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: LI Xin References: <45D85A88.4040402@delphij.net> <45E5B176.1010303@delphij.net> In-Reply-To: <45E5B176.1010303@delphij.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Feature request: exit netstat(1) after user specified outputs 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, 28 Feb 2007 19:12:27 -0000 LI Xin wrote: > Hi, > > If no one objects this change, I will commit it? > > No objection here. BMS From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 20:01:03 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6895516A400 for ; Wed, 28 Feb 2007 20:01:03 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id E34A413C478 for ; Wed, 28 Feb 2007 20:01:02 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-42-242.51-151.net24.it [151.51.242.42]) (authenticated bits=128) by parrot.aev.net (8.14.0/8.13.8) with ESMTP id l1SK8Mwr015774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 28 Feb 2007 21:08:28 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.0/8.13.8) with ESMTP id l1SK1GfB048617 for ; Wed, 28 Feb 2007 21:01:17 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45E5DF6D.3000004@netfence.it> Date: Wed, 28 Feb 2007 21:00:45 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <45E21468.4060200@netfence.it> <20070227222316.R60173@fledge.watson.org> <45E53F7D.4030703@netfence.it> <20070228084928.Y64827@maildrop.int.zabbadoz.net> <45E54F39.4050204@netfence.it> In-Reply-To: <45E54F39.4050204@netfence.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.61 on 212.31.247.179 Subject: Update: LOR with divert sockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 20:01:03 -0000 Andrea Venturoli wrote: > I'm currently having: > _ 1 SMP box *with* one uid rule which occasionally hangs (running > INVARIANTS&Co and from which my report was taken); > _ 1 SMP box *without* uid rules which occasionally hangs (running > INVARIANTS&Co); > _ 1 UP box *with* one uid rule which frequently hangs (I'm turning > INVARIANTS&Co on this afternoon on this one); > _ 1 UP box *with* one uid rule which frequently hangs (I'm turning SMP > and INVARIANTS&Co on this afternoon on this one); > _ 2 UP boxes *with* one uid rule which never ever hanged. I did what I told I was about to do, i.e. I enabled all the mentioned debugging options on two servers which are configured almost alike and are working in pair (i.e. running carp to backup each other): one is an i386/UP, the other an amd64/SMP. Both are 6.2p1 running ipfw with the uid rule I reported in one of my previous messages. As soon as I rebooted I got a LOR on both of them: this seems like #202 on the list at http://sources.zabbadoz.net/freebsd/lor.html, except first line number is 336. I then disabled debug.mpsafenet and had to reboot for this to apply. Again I immediately had two LORs, but this time the one on the i386/UP box was different: in fact it was #203, which is what I reported from another server of mine (which by the way is an i386/SMP). On that same box I later got #193, within two hours of enabling debugging messages. Time will tell wether disabling mpsafenet will solve stability problems on these two boxes. Hope this helps. bye & Thanks av. From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 21:53:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E20816A400 for ; Wed, 28 Feb 2007 21:53:16 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id E3FBB13C474 for ; Wed, 28 Feb 2007 21:53:15 +0000 (UTC) (envelope-from killing@multiplay.co.uk) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on core6.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-22.4 required=6.0 tests=BAYES_05, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.5 Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.5.4) with ESMTP id md50003572737.msg; Wed, 28 Feb 2007 21:37:44 +0000 Message-ID: <003501c75b80$a8eacc50$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: , Date: Wed, 28 Feb 2007 21:37:27 -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.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-Spam-Processed: multiplay.co.uk, Wed, 28 Feb 2007 21:37:45 +0000 X-MDAV-Processed: multiplay.co.uk, Wed, 28 Feb 2007 21:37:45 +0000 Cc: Subject: dump -> restore to nfs volume hangs NFS server ( 6.2-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: Wed, 28 Feb 2007 21:53:16 -0000 I've just performed the following from one machine to another. dump -a0uL -C 32 -f - /usr | ( cd /mnt && restore rf - ) Both boxes running 6.2-RELEASE src box on em0 dest on bge0. shortly after starting the above I tried to do an ls -l in an ssh session I had open on the destination box. This hung and never returned so I tried to open a new session again shortly before gaining a command prompt. I left this and waited for the backup to finish, which it did, hoping the machine would spark back into life once the backup completed. Unfortunately not although still responding to ping and being able to ls via other nfs mounts the machine was otherwise dead. Even a console login via kvm proved fruitless as did CTRL+ALT+DEL. The machine seems to be still stuck in this state of trying to reboot due to the CTRL+ALT+DEL but not getting very far very quick, ssh is now off and syslogd has quit but nothing else so far on the console. So has anyone else experienced this before? Should I try this again once I get the affected machine back online? If so what steps should I do to debug this so we can find a fix? Steve ================================================ 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 Feb 28 22:20:52 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A69F16A403 for ; Wed, 28 Feb 2007 22:20:52 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 56C3913C48D for ; Wed, 28 Feb 2007 22:20:52 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 4B9021F463B for ; Wed, 28 Feb 2007 17:20:52 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 28 Feb 2007 17:20:52 -0500 X-Sasl-enc: Q47ZMR718n97xORVbifzwSgmgsTJ75vEjMQRXxMqjFFG 1172701251 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id C86F32118 for ; Wed, 28 Feb 2007 17:20:51 -0500 (EST) Message-ID: <45E60041.1090607@incunabulum.net> Date: Wed, 28 Feb 2007 22:20:49 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Proposal: Add M_HASCL(). 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, 28 Feb 2007 22:20:52 -0000 Much network code needs to know if the mbuf it is looking at is using a cluster. I propose putting M_HASCL() in sys/mbuf.h. I realise this is a style change, however, it seems to be a very common idiom. Places this macro is currently defined and used directly: netinet/ip_mroute.c netinet6/ip6_mroute.c nfsclient/nfsm_subs.h nfsserver/nfsm_subs.h Places which use this idiom by another name: if_ppp.c ppp_tty.c Places which use this idiom indirectly by its expansion: sys/mbuf.h sys/socketvar.h netinet/ip6.h dev/pdq Many device drivers and third party code. Head on over to http://fxr.watson.org/fxr/ident?i=M_HASCL and have a look. Feel free to not bikeshed about this. It became apparent that this is a common idiom (needing to know if an mbuf is using external storage for whatever reason). Thoughts? BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 00:25:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0882916A402 for ; Thu, 1 Mar 2007 00:25:54 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.233]) by mx1.freebsd.org (Postfix) with ESMTP id BB97713C48E for ; Thu, 1 Mar 2007 00:25:53 +0000 (UTC) (envelope-from artemb@gmail.com) Received: by nz-out-0506.google.com with SMTP id r28so324647nza for ; Wed, 28 Feb 2007 16:25:41 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=QEwPWuR498lFUJkyGJ+AVixNcCvsI2mvUU6J9Xnpg7seL/tHqQFmikzSDzcEV9zrBj730JSIWfYBd9BL4pM1PsvByaWC3oCi4NN94VKsHPnM94hNII8eUm1ZGN2qpODjvGx/6osxFf6rI8+fqD/z0GPH4xgun/kCtuhgBrVNbAk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Thiq8QPZ/SwewC5qd32IGpndqtEsj0RrMqa3YDJ4psJsk3/hTi7k527+m6O34Ls/kfhssVathT6CZtYKvtCILxXoxZqq83HbaY2L0uIPG4k3Z+cybBiuau1ulyN0Morm4a3BSz/Jsz/zFLPd6CKa1z3KUsuvBNvuzuSo86Nxc4g= Received: by 10.115.47.1 with SMTP id z1mr104486waj.1172693531475; Wed, 28 Feb 2007 12:12:11 -0800 (PST) Received: by 10.115.22.18 with HTTP; Wed, 28 Feb 2007 12:12:11 -0800 (PST) Message-ID: Date: Wed, 28 Feb 2007 12:12:11 -0800 From: "Artem Belevich" Sender: artemb@gmail.com To: "LI Xin" In-Reply-To: <45E5D417.9000403@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45D85A88.4040402@delphij.net> <45E5B176.1010303@delphij.net> <45E5D417.9000403@FreeBSD.org> X-Google-Sender-Auth: 5ec7a8d1b3ee582c Cc: freebsd-net@freebsd.org, "Bruce M. Simpson" Subject: Re: [PATCH] Feature request: exit netstat(1) after user specified outputs 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, 01 Mar 2007 00:25:54 -0000 This looks suspiciously like a mild case of creeping featurism. http://en.wikipedia.org/wiki/Creeping_featurism Can't one pipe netstat output through 'head' command to achieve desired effect? Thanks, --Artem On 2/28/07, Bruce M. Simpson wrote: > LI Xin wrote: > > Hi, > > > > If no one objects this change, I will commit it? > > > > > No objection here. > > BMS > _______________________________________________ > 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" > -- --Artem From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 10:24:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD22916A401 for ; Thu, 1 Mar 2007 10:24:11 +0000 (UTC) (envelope-from antonio.tommasi@unile.it) Received: from cabis.unile.it (cabis.unile.it [212.189.128.35]) by mx1.freebsd.org (Postfix) with ESMTP id 8068D13C474 for ; Thu, 1 Mar 2007 10:24:11 +0000 (UTC) (envelope-from antonio.tommasi@unile.it) Received: from localhost (cabis [127.0.0.1]) by cabis.unile.it (Postfix) with ESMTP id 5B56422AED1 for ; Thu, 1 Mar 2007 11:24:10 +0100 (CET) X-Virus-Scanned: virus/spam checker at unile.it Received: from cabis.unile.it ([127.0.0.1]) by localhost (cabis.unile.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6WKaWyqYPz9O for ; Thu, 1 Mar 2007 11:24:09 +0100 (CET) Received: from [212.189.128.38] (titto.unile.it [212.189.128.38]) by cabis.unile.it (Postfix) with ESMTP id 5C97922AEE6 for ; Thu, 1 Mar 2007 11:24:09 +0100 (CET) Mime-Version: 1.0 Message-Id: Date: Thu, 1 Mar 2007 11:24:07 +0100 To: freebsd-net@freebsd.org From: Antonio Tommasi Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: ipfw 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, 01 Mar 2007 10:24:11 -0000 Hi to all, i want to know if it is possibile in my firewall.conf refer to an external file where for example i indicate my source ip or/and my destination ip of my rules. Thanks in advance Antonio From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 11:01:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DD6AE16A400 for ; Thu, 1 Mar 2007 11:01:32 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id B5F4513C491 for ; Thu, 1 Mar 2007 11:01:32 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l21B1WBY044112; Thu, 1 Mar 2007 03:01:32 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l21B1WjJ044111; Thu, 1 Mar 2007 03:01:32 -0800 (PST) (envelope-from rizzo) Date: Thu, 1 Mar 2007 03:01:32 -0800 From: Luigi Rizzo To: Antonio Tommasi Message-ID: <20070301030132.A43934@xorpc.icir.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from antonio.tommasi@unile.it on Thu, Mar 01, 2007 at 11:24:07AM +0100 Cc: freebsd-net@freebsd.org Subject: Re: ipfw 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, 01 Mar 2007 11:01:32 -0000 On Thu, Mar 01, 2007 at 11:24:07AM +0100, Antonio Tommasi wrote: > Hi to all, > i want to know if it is possibile in my firewall.conf refer to an > external file where for example i indicate my source ip or/and my > destination ip of my rules. this is not supported directly in /sbin/ipfw, because there is no reason to replicate a scripting language within /sbin/ipfw. Rather, you should create your configuration using a scripting language of your choice (e.g. /bin/sh) and produce a suitable output to feed /sbin/ipfw cheers luigi From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 11:05:30 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF14316A403 for ; Thu, 1 Mar 2007 11:05:30 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id BC38913C461 for ; Thu, 1 Mar 2007 11:05:30 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 9586A1F3E00 for ; Thu, 1 Mar 2007 06:05:30 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Thu, 01 Mar 2007 06:05:30 -0500 X-Sasl-enc: TJToq+iZKcLGPW9b9IkIpv2VdM1ksC5ZxeUHwJRxaC0Z 1172747130 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id D055521E6C; Thu, 1 Mar 2007 06:05:29 -0500 (EST) Message-ID: <45E6B378.1020703@FreeBSD.org> Date: Thu, 01 Mar 2007 11:05:28 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Bruce M Simpson References: <45E60041.1090607@incunabulum.net> In-Reply-To: <45E60041.1090607@incunabulum.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@FreeBSD.org Subject: Re: Proposal: Add M_HASCL(). 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, 01 Mar 2007 11:05:31 -0000 Bruce M Simpson wrote: > Much network code needs to know if the mbuf it is looking at is using > a cluster. I propose putting M_HASCL() in sys/mbuf.h. I realise this > is a style change, however, it seems to be a very common idiom. I sent this, then I looked at NetBSD, having caught a glimpse of their MBUFTRACE code when skimming lots of diffs. That is also a good idea, and might help us catch problems before they go prime-time; I've added it to the wiki. Point there is, M_HASCL() seems to be a hangover from the 4.4BSD era. NetBSD seems to treat clusters and external storage as separate entities. So I'm reconsidering this in the light of this new evidence. As far as I understand it, the presence of M_EXT in an mbuf chain's header in FreeBSD always indicate that we are using external storage (not necessarily, but possibly, a cluster). Can someone confirm this? Regards, BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 11:35:21 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5859F16A49A for ; Thu, 1 Mar 2007 11:35:21 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id 705BA13C4AC for ; Thu, 1 Mar 2007 11:35:18 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by mu-out-0910.google.com with SMTP id g7so408173muf for ; Thu, 01 Mar 2007 03:35:17 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gWzsSLE2KN8WfMo/wB8vyHQEbznWxmLHa454yJvJJJ1AJFaMT/BY4FuO/LSzt35BCRHY0uBTT5FbAAcBnbX8Z/RrqgFUHjWGNLtMz2HanNBekPXoCfoZVUAxA+k+fE2MUiXHG3edI5Zqoxdjwad4LK3EYBjL+kiGqzEm3ilSwRQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aMFMbGt3tn0pwNT8wKnf0jAdegWNNplx1hJZCQgODYKyhp9Vzz/Y9UgRd6lu50Mut2n8CGvy9kJjWGVfqsK7mTPEDiqGuFax+CKJ9Nk3c2nkiI6q8WJc/6hXcTZUU11ZjyQXbzo+7ZyBQ/KJv3j8sc0iBiC7L55X5+IYX25jud4= Received: by 10.82.172.15 with SMTP id u15mr525190bue.1172747307438; Thu, 01 Mar 2007 03:08:27 -0800 (PST) Received: by 10.82.135.17 with HTTP; Thu, 1 Mar 2007 03:08:27 -0800 (PST) Message-ID: <3aaaa3a0703010308t1fad983em2707001dc5ec3593@mail.gmail.com> Date: Thu, 1 Mar 2007 11:08:27 +0000 From: Chris To: "chrishome@austin.rr.com" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45C99336.3010508@demax.sk> Cc: freebsd-net@freebsd.org, Jan Sebosik , freebsd-questions@freebsd.org Subject: Re: Packet rate limiter 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, 01 Mar 2007 11:35:21 -0000 On 17/02/07, chrishome@austin.rr.com wrote: > > Hi > > > > is there any way how to limit packet per second [PPS] rate to > > specified > > IP (group of IP) ? Linux can achieve this via IPtables. > > I`ve searched a lot of web, but nothing interesting found (for PF, > > IPFilter, and IPFW). > > > > I agree this would be a very nice addition to IPFW as a basic feature, > or maybe a more advanced version via Dummynet. It's much to easy for a > trojan / virus or intentionally malicious user to flood a FreeBSD box > setup as a router with loads of tiny UDP packets on port 80. In fact, > just a few days ago we had 2 users behind one of our FreeBSD gateways > sending huge loads of traffic to a webhosting site.. This packet count > shown below was all within a 12 hour period ;) > > 00010 990465375 39618916491 deny ip from 172.17.106.114 to any > 00010 20010976 800449444 deny ip from 172.17.105.114 to any > > > Being able to put limits per protocol would be a wonderful addition. > For now what we do is setup a count rule by MAC address for every user, > we check the count rules every 60 seconds, if we begin to see packets > per second for a certain host climb above for example 4000PPS, we simply > automatically add a deny rule. These are generally users set for 1 or 2 > Mbps each, so 4000PPS is pretty extreme for that kind of bandwidth > unless your doing something you shouldn't. > > I've been talking to a few friends about possibly adding this to ipfw or > dummynet, and if I ever get around to a completed working version, I > would be more than happy to share, but for now, there are ways to still > fix the problem, just not as elegant as if it where actually a firewall > rule ;) > > Chris Bowman > > _______________________________________________ > 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" > Whats the rule that counts per src address? thanks Chris From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 11:38:02 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D298B16A403 for ; Thu, 1 Mar 2007 11:38:02 +0000 (UTC) (envelope-from lecocq@lipn.univ-paris13.fr) Received: from obelix.math.univ-paris13.fr (obelix.math.univ-paris13.fr [194.254.165.6]) by mx1.freebsd.org (Postfix) with ESMTP id 91FF113C442 for ; Thu, 1 Mar 2007 11:38:02 +0000 (UTC) (envelope-from lecocq@lipn.univ-paris13.fr) Received: from [192.168.70.222] (addoo.math.univ-paris13.fr [194.254.165.54]) by obelix.math.univ-paris13.fr (Postfix) with ESMTP id 5BB69E1D19 for ; Thu, 1 Mar 2007 12:16:09 +0100 (CET) Message-ID: <45E6B5F9.7050702@lipn.univ-paris13.fr> Date: Thu, 01 Mar 2007 12:16:09 +0100 From: Le Cocq Michel User-Agent: IceDove 1.5.0.7 (X11/20061014) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: python 2.4.4, 1 vs 2.4.3, 1 - zope trouble - python version downgrade 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, 01 Mar 2007 11:38:03 -0000 Yesterday I try to install a python module after a 'portsnap fetch update', during the install python upgrade from version 2.4.3,1 to 2.4.4,1. python-2.4.3,1 The "meta-port" for the stable version of Python interprete vs python-2.4.4,1 [...] since these upgrade my zope (zope29-2.9.6) won't start anymore ! How can I come back to version python-2.4.3,1 ? Michel From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 11:54:10 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E447C16A405 for ; Thu, 1 Mar 2007 11:54:10 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id AACA013C4BF for ; Thu, 1 Mar 2007 11:54:10 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id A63C01F4088 for ; Thu, 1 Mar 2007 06:54:10 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Thu, 01 Mar 2007 06:54:10 -0500 X-Sasl-enc: ZIVJM6QygzDQ4qZMvzTr3xV406BleRGeSW/wdf3J8ijR 1172750050 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 438B521049 for ; Thu, 1 Mar 2007 06:54:09 -0500 (EST) Message-ID: <45E6BEE0.2050307@FreeBSD.org> Date: Thu, 01 Mar 2007 11:54:08 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org References: <45C0CA5D.5090903@incunabulum.net> In-Reply-To: <45C0CA5D.5090903@incunabulum.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: nconsistencies with IP_ONESBCAST and/or IP_SENDSRCADDR 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, 01 Mar 2007 11:54:11 -0000 Bruce M Simpson wrote: > Hello, > > In preparation for tightening up our handling of INADDR_BROADCAST > sends, I ran some brief tests today on the network stack with the > attached test code. > > I found some inconsistencies when run against 6.2-RELEASE; > > 1. IP_ONESBCAST breaks if SO_DONTROUTE is specified. > > One thing appears to be consistent about the failure mode: bad UDP > checksums. > dc(4) is being used on the destination end of the test network, so > checksum offloading should not be an issue. > I am also seeing the wrong destination address being used in most > cases. This is intermittent regardless of whether the socket is bound > or unbound. This is consistent with ip_output() treating its internal flag IP_SENDONES as separate from IP_ROUTETOIF. I was skimming an old patch of mine which attempts to implement part of SO_BINDTODEVICE which contains a fix related to this condition. The fix isn't the right fix so I will revisit this now and hopefully commit a fix shortly. > > 2. IP_SENDSRCADDR has some other inconsistencies. > a. The option is always rejected if the socket is not bound. > I find this behaviour suspect; the whole point of the option is to > specify, for SOCK_DGRAM and SOCK_RAW, the source address of a packet. > b. 0.0.0.0 is always accepted. > A regular interface lookup is used based on destination if this is > specified. This appears suspect to me because such an option is > redundant. This is of course a separate issue. Because it's more involved (it concerns the general concept of 'ip unnumbered' in the stack) it needs further consideration before any fix is attempted. udp_output() will only call in_pcbbind_setup() if a non-INADDR_ANY source address was specified; this is usually obtained from the socket being bound previously. This explains why the IP_SENDSRCADDR option is rejected in udp_output() for an unbound socket. It *will* be accepted if the option contains INADDR_ANY. In this case, normal source address selection takes place. This is a good use case demonstrating the need for source address selection logic such as is now found in NetBSD. There is no sanity checking on the IP_SENDSRCADDR option data containing INADDR_ANY; such an option is redundant and is nonsensical for an unbound socket. We should reject the option if it contains INADDR_ANY if and only if the socket is not bound. Implementing such a check is fairly easy and makes sense for this use case. Returning EINVAL in this case seems acceptable according to ip(4). The option *should* be accepted if the application has bound the socket to a device somehow (oh dear, SO_BINDTODEVICE rears its head again) as DHCP for example needs to override any IPv4 address which may be assigned on an ifnet with 0.0.0.0. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 12:29:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B82016A401 for ; Thu, 1 Mar 2007 12:29:11 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.freebsd.org (Postfix) with ESMTP id D5EF213C467 for ; Thu, 1 Mar 2007 12:29:10 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from citrin (unknown [81.19.65.100]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: citrin.citrin.ru) by mail.classis.ru (Postfix) with ESMTP id A335012279AE for ; Thu, 1 Mar 2007 15:18:24 +0300 (MSK) Date: Thu, 1 Mar 2007 15:17:29 +0300 From: Anton Yuzhaninov X-Mailer: The Bat! (v3.62.14) Professional Organization: Rambler X-Priority: 3 (Normal) Message-ID: <2110071423.20070301151729@citrin.ru> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------EA1EE1A83EA702A6" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 12:29:11 -0000 This is a cryptographically signed message in MIME format. ------------EA1EE1A83EA702A6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hello. Is SO_NOSIGPIPE work? It try to set on socket option SO_NOSIGPIPE but anyway process received sigpipe. Test case: #include #include #include #include #define SERVER_PORT 8000 void sigpipe(int signo __unused) { printf("SIGPIPE recivied\n"); } int main(int argc, char *argv[]) { int s , c; int on =3D 1; socklen_t slen, c_len; struct sockaddr_in serv_addr, client_addr; if ((s =3D socket(PF_INET, SOCK_STREAM, 0)) < 0) err(1, "socket() failed"); bzero(&serv_addr, sizeof(serv_addr)); serv_addr.sin_family =3D AF_INET; serv_addr.sin_addr.s_addr =3D htonl(INADDR_LOOPBACK); serv_addr.sin_port =3D htons(SERVER_PORT); if (bind(s, (struct sockaddr *)&serv_addr, sizeof(serv_addr)) < 0) err(1, "bind() failed"); if (listen(s, -1) < 0) err(1, "listen() failed"); (void)signal(SIGPIPE, sigpipe); for (;;) { if ((c =3D accept(s, (struct sockaddr *)&client_addr, &c_len)) < 0)= { warn("accept() failed"); continue; } if (setsockopt(c, SOL_SOCKET, SO_NOSIGPIPE, (void *)&on, sizeof(on)= ) < 0) err(1, "setsockopt(SOL_SOCKET, SO_NOSIGPIPE) failed"); sleep(2); if (write(c, "abc", strlen("abc")) < 0) warn("first write() failed"); if (write(c, "\r\n", strlen("\r\n")) < 0) warn("second write() failed"); close(c); } } Client connect, than disconnect. server print: SIGPIPE recivied a.out: second write() failed: Broken pipe Is SO_NOSIGPIPE broken, or something wrong in my code? system: 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Feb 19 17:07:12 MSK 2007 --=20 WBR, Anton Yuzhaninov ------------EA1EE1A83EA702A6-- From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 12:33:43 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1400316A402 for ; Thu, 1 Mar 2007 12:33:43 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8622F13C442 for ; Thu, 1 Mar 2007 12:33:42 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 30744 invoked from network); 1 Mar 2007 11:39:46 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Mar 2007 11:39:46 -0000 Message-ID: <45E6C1EA.8030109@freebsd.org> Date: Thu, 01 Mar 2007 13:07:06 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <45E60041.1090607@incunabulum.net> <45E6B378.1020703@FreeBSD.org> In-Reply-To: <45E6B378.1020703@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Bruce M Simpson , net@FreeBSD.org Subject: Re: Proposal: Add M_HASCL(). 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, 01 Mar 2007 12:33:43 -0000 Bruce M. Simpson wrote: > Bruce M Simpson wrote: >> Much network code needs to know if the mbuf it is looking at is using >> a cluster. I propose putting M_HASCL() in sys/mbuf.h. I realise this >> is a style change, however, it seems to be a very common idiom. > I sent this, then I looked at NetBSD, having caught a glimpse of their > MBUFTRACE code when skimming lots of diffs. That is also a good idea, > and might help us catch problems before they go prime-time; I've added > it to the wiki. > > Point there is, M_HASCL() seems to be a hangover from the 4.4BSD era. > NetBSD seems to treat clusters and external storage as separate > entities. So I'm reconsidering this in the light of this new evidence. > > As far as I understand it, the presence of M_EXT in an mbuf chain's > header in FreeBSD always indicate that we are using external storage > (not necessarily, but possibly, a cluster). > > Can someone confirm this? This is correct. M_EXT is set whenever external storage is attached to an mbuf. We have many different classes of external storage with traditional 2k clusters being one of them. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 12:34:49 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CF96F16A402 for ; Thu, 1 Mar 2007 12:34:49 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 45C9A13C491 for ; Thu, 1 Mar 2007 12:34:49 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 30761 invoked from network); 1 Mar 2007 11:40:53 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Mar 2007 11:40:53 -0000 Message-ID: <45E6C22D.7060200@freebsd.org> Date: Thu, 01 Mar 2007 13:08:13 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <45C0CA5D.5090903@incunabulum.net> <45E6BEE0.2050307@FreeBSD.org> In-Reply-To: <45E6BEE0.2050307@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@FreeBSD.org Subject: Re: nconsistencies with IP_ONESBCAST and/or IP_SENDSRCADDR 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, 01 Mar 2007 12:34:49 -0000 Bruce M. Simpson wrote: > Bruce M Simpson wrote: >> Hello, >> >> In preparation for tightening up our handling of INADDR_BROADCAST >> sends, I ran some brief tests today on the network stack with the >> attached test code. >> >> I found some inconsistencies when run against 6.2-RELEASE; >> >> 1. IP_ONESBCAST breaks if SO_DONTROUTE is specified. >> >> One thing appears to be consistent about the failure mode: bad UDP >> checksums. >> dc(4) is being used on the destination end of the test network, so >> checksum offloading should not be an issue. >> I am also seeing the wrong destination address being used in most >> cases. This is intermittent regardless of whether the socket is bound >> or unbound. > This is consistent with ip_output() treating its internal flag > IP_SENDONES as separate from IP_ROUTETOIF. I was skimming an old patch > of mine which attempts to implement part of SO_BINDTODEVICE which > contains a fix related to this condition. > > The fix isn't the right fix so I will revisit this now and hopefully > commit a fix shortly. >> >> 2. IP_SENDSRCADDR has some other inconsistencies. >> a. The option is always rejected if the socket is not bound. >> I find this behaviour suspect; the whole point of the option is to >> specify, for SOCK_DGRAM and SOCK_RAW, the source address of a packet. >> b. 0.0.0.0 is always accepted. >> A regular interface lookup is used based on destination if this is >> specified. This appears suspect to me because such an option is >> redundant. > This is of course a separate issue. Because it's more involved (it > concerns the general concept of 'ip unnumbered' in the stack) it needs > further consideration before any fix is attempted. > > udp_output() will only call in_pcbbind_setup() if a non-INADDR_ANY > source address was specified; this is usually obtained from the socket > being bound previously. This explains why the IP_SENDSRCADDR option is > rejected in udp_output() for an unbound socket. It *will* be accepted if > the option contains INADDR_ANY. In this case, normal source address > selection takes place. > > This is a good use case demonstrating the need for source address > selection logic such as is now found in NetBSD. > > There is no sanity checking on the IP_SENDSRCADDR option data containing > INADDR_ANY; such an option is redundant and is nonsensical for an > unbound socket. We should reject the option if it contains INADDR_ANY if > and only if the socket is not bound. Implementing such a check is fairly > easy and makes sense for this use case. Returning EINVAL in this case > seems acceptable according to ip(4). > > The option *should* be accepted if the application has bound the socket > to a device somehow (oh dear, SO_BINDTODEVICE rears its head again) as > DHCP for example needs to override any IPv4 address which may be > assigned on an ifnet with 0.0.0.0. I have some WIP here too. I'll send it to you later this afternoon. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 13:37:18 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D8B716A400; Thu, 1 Mar 2007 13:37:18 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 6A37E13C474; Thu, 1 Mar 2007 13:37:18 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 543031F1ED3; Thu, 1 Mar 2007 08:37:18 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Thu, 01 Mar 2007 08:37:18 -0500 X-Sasl-enc: WcZhPIxIDHwY6mJgxhvncQo+CcV5fTlqlab8oyIgneQK 1172756238 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id D31791EC5; Thu, 1 Mar 2007 08:37:17 -0500 (EST) Message-ID: <45E6D70C.10104@FreeBSD.org> Date: Thu, 01 Mar 2007 13:37:16 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Andre Oppermann References: <45C0CA5D.5090903@incunabulum.net> <45E6BEE0.2050307@FreeBSD.org> <45E6C22D.7060200@freebsd.org> In-Reply-To: <45E6C22D.7060200@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@FreeBSD.org Subject: Re: Inconsistencies with IP_ONESBCAST and/or IP_SENDSRCADDR 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, 01 Mar 2007 13:37:18 -0000 Andre Oppermann wrote: > > I have some WIP here too. I'll send it to you later this afternoon. > Thanks, I look forward to seeing it, re Issue #2 IP_SENDSRCADDR. Dealing with dhclient is a separate issue -- here, something like IP_SENDIF needs to be introduced, as we are truly in an 'ip unnumbered' situation -- ie the ifnet MAY not yet have been assigned an IPv4 address at all, and IP_SENDSRCADDR implies that you are source routing in the local stack by passing the address of a numbered interface I have however dealt with Issue #1 by committing a fix to ip_output() for the IP_ONESBCAST && SO_DONTROUTE case. This together with the fix you committed for ethernet next-hop resolution (thanks!) should mean that projects like OLSRD can stop using libnet and other hacks for sending 255.255.255.255 on FreeBSD. The original broadtest tool has now been cleaned up and put into the tree under src/tools/regression/netinet/ipbroadcast. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 14:27:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD23B16A404 for ; Thu, 1 Mar 2007 14:27:54 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 3BD1113C494 for ; Thu, 1 Mar 2007 14:27:54 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 32239 invoked from network); 1 Mar 2007 14:00:38 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Mar 2007 14:00:38 -0000 Message-ID: <45E6E2E8.5060408@freebsd.org> Date: Thu, 01 Mar 2007 15:27:52 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gallatin@freebsd.org, rwatson@freebsd.org, kmacy@freebsd.org Subject: Large TCP send socket buffer optimizations 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, 01 Mar 2007 14:27:54 -0000 With the TCP socket buffer autosizing and generally larger socket buffers for high bandwidth and high delay connections tcp_output() has become increasingly inefficient for sending segments. For every segment sent it is traversing the entire socket buffer mbuf chain until it finds the offset to continue from. Usually this is close to the end of the chain. Once it got past a few dozen mbufs it starts to bust the CPU caches and performance starts to fall off. This patch solves the problem by maintaining an offset pointer in the socket buffer to give tcp_output() the closest mbuf right away avoiding the traversal from the beginning. With this patch we should be able to compete nicely for the Internet land speed record again. The patch is here: http://people.freebsd.org/~andre/sockbuf_sndptr-20070301.diff Any testing, especially on 10Gig cards, and feedback appreciated. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 14:45:50 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77DCC16A406; Thu, 1 Mar 2007 14:45:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3B85113C4B4; Thu, 1 Mar 2007 14:45:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id ACD0646F3F; Thu, 1 Mar 2007 09:45:49 -0500 (EST) Date: Thu, 1 Mar 2007 14:45:49 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andre Oppermann In-Reply-To: <45E6E2E8.5060408@freebsd.org> Message-ID: <20070301144321.O98688@fledge.watson.org> References: <45E6E2E8.5060408@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, gallatin@freebsd.org, freebsd-current@freebsd.org, kmacy@freebsd.org Subject: Re: Large TCP send socket buffer optimizations 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, 01 Mar 2007 14:45:50 -0000 On Thu, 1 Mar 2007, Andre Oppermann wrote: > With the TCP socket buffer autosizing and generally larger socket buffers > for high bandwidth and high delay connections tcp_output() has become > increasingly inefficient for sending segments. For every segment sent it is > traversing the entire socket buffer mbuf chain until it finds the offset to > continue from. Usually this is close to the end of the chain. Once it got > past a few dozen mbufs it starts to bust the CPU caches and performance > starts to fall off. > > This patch solves the problem by maintaining an offset pointer in the socket > buffer to give tcp_output() the closest mbuf right away avoiding the > traversal from the beginning. > > With this patch we should be able to compete nicely for the Internet land > speed record again. > > The patch is here: > > http://people.freebsd.org/~andre/sockbuf_sndptr-20070301.diff > > Any testing, especially on 10Gig cards, and feedback appreciated. I'm going to be on- and off-line from now through about the last week of March on travel to LinuxForum.dk, AsiaBSDCon, and UKUUG. However, once I get back online from that in late March through the end of April, I will be spending quite a bit of time looking at high performance packet capture issues, so can certainly spend some time looking at this. Per our earlier discussions and my previous exploration of this issue, I see precisely this sort of problem with TCP as socket buffer size grows, so should be set up to fairly easily test for an improvement once I have my feet on the ground. If I'm lucky I may get a breather for a few days from about 15 March - 18 March and could take an early look at it then. Thanks, Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 14:52:39 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8086916A403 for ; Thu, 1 Mar 2007 14:52:39 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.freebsd.org (Postfix) with ESMTP id 0948313C4A3 for ; Thu, 1 Mar 2007 14:52:38 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id l21EqYFm007289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Mar 2007 17:52:34 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id l21EqY3o007288; Thu, 1 Mar 2007 17:52:34 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 1 Mar 2007 17:52:33 +0300 From: Gleb Smirnoff To: dima <_pppp@mail.ru> Message-ID: <20070301145233.GR1621@FreeBSD.org> Mail-Followup-To: Gleb Smirnoff , dima <_pppp@mail.ru>, freebsd-net@freebsd.org References: <20070228122459.GK1621@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org Subject: Re: is CARP still impossible on SMP in 6.2? 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, 01 Mar 2007 14:52:39 -0000 On Wed, Feb 28, 2007 at 06:08:21PM +0300, dima wrote: d> > On Wed, Feb 28, 2007 at 02:28:13PM +0300, dima wrote: d> > d> I'm trying to make CARP working on a 2-Xeon hardware. It worked OK on 5.5, but not on 6.2. d> > d> The result of compiling both d> > d> options SMP d> > d> device carp d> > d> into the kernel makes it crash in 'swi1: net' kernel thread on a random (usually first) use of the CARP facility. d> > d> > Can you please provide a backtrace? d> d> It's not that easy. The server becomes extremely unstable under these conditions. d> I tried to build the kernel with '-g' option and included 'dumpdev' in /etc/rc.conf. The server can't even make a memory dump: it either gets one more page fault or just stops responding to anything but Reset key in the beginning of the dump. d> It's strange since it rebooted well while the kernel was built without debugging symbols and a dumpdev. Any ideas how I can make a memory dump? Why do you think the CARP is guilty in this unstableness? Are you triggering MASTER<->BACKUP events and this causes instability? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 15:25:09 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DAB8716A405; Thu, 1 Mar 2007 15:25:09 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id 0559213C4A8; Thu, 1 Mar 2007 15:25:08 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.14.0/8.14.0) with ESMTP id l21FM7HX017318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Mar 2007 10:22:07 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id l21FM1Mt042892; Thu, 1 Mar 2007 10:22:01 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17894.61337.772803.325091@grasshopper.cs.duke.edu> Date: Thu, 1 Mar 2007 10:22:01 -0500 (EST) To: Andre Oppermann In-Reply-To: <45E6E2E8.5060408@freebsd.org> References: <45E6E2E8.5060408@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, rwatson@freebsd.org, kmacy@freebsd.org Subject: Re: Large TCP send socket buffer optimizations 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, 01 Mar 2007 15:25:10 -0000 Andre Oppermann writes: > This patch solves the problem by maintaining an offset pointer in the socket > buffer to give tcp_output() the closest mbuf right away avoiding the traversal > from the beginning. > > With this patch we should be able to compete nicely for the Internet land > speed record again. Great news. I will test soon. Have you found the bug which makes a freebsd sender spew duplicate acks? This will have a negative affect on any benchmarks.. Drew From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 15:57:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0D0616A405 for ; Thu, 1 Mar 2007 15:57:10 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 8E1FA13C441 for ; Thu, 1 Mar 2007 15:57:10 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 212AA5F6E; Thu, 1 Mar 2007 18:32:13 +0300 (MSK) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id F25315DDF; Thu, 1 Mar 2007 18:32:12 +0300 (MSK) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id l21FTg2O027477; Thu, 1 Mar 2007 18:29:42 +0300 (MSK) (envelope-from ru) Date: Thu, 1 Mar 2007 18:29:42 +0300 From: Ruslan Ermilov To: Anton Yuzhaninov Message-ID: <20070301152942.GA27336@rambler-co.ru> References: <2110071423.20070301151729@citrin.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <2110071423.20070301151729@citrin.ru> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-net@freebsd.org Subject: Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 15:57:10 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Anton, On Thu, Mar 01, 2007 at 03:17:29PM +0300, Anton Yuzhaninov wrote: > Hello. >=20 > Is SO_NOSIGPIPE work? >=20 > It try to set on socket option SO_NOSIGPIPE but anyway process > received sigpipe. >=20 It works, but only if you use send() instead of write(). Alternatively, you can control the behavior on a per message basis, by passing the MSG_NOSIGNAL in the "flags" argument to the send() call (without having to set a socket option). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.2 (FreeBSD) iD8DBQFF5vFmqRfpzJluFF4RAqvzAJ4wrnjeCo1hcSgl4iQA95sMa1aSYwCeJndi JbDSkxbHqzViAfULxJFzzP0= =nPbM -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 16:14:40 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22CAF16A40D; Thu, 1 Mar 2007 16:14:40 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f42.mail.ru (f42.mail.ru [194.67.57.80]) by mx1.freebsd.org (Postfix) with ESMTP id 595D013C4A6; Thu, 1 Mar 2007 16:14:38 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from mail by f42.mail.ru with local id 1HMnvQ-000EHa-00; Thu, 01 Mar 2007 19:14:36 +0300 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Thu, 01 Mar 2007 19:14:36 +0300 From: dima <_pppp@mail.ru> To: Gleb Smirnoff Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Thu, 01 Mar 2007 19:14:36 +0300 In-Reply-To: <20070301145233.GR1621@FreeBSD.org> References: <20070301145233.GR1621@FreeBSD.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Cc: freebsd-net@FreeBSD.org Subject: Re[2]: is CARP still impossible on SMP in 6.2? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 16:14:40 -0000 > On Wed, Feb 28, 2007 at 06:08:21PM +0300, dima wrote: > d> > On Wed, Feb 28, 2007 at 02:28:13PM +0300, dima wrote: > d> > d> I'm trying to make CARP working on a 2-Xeon hardware. It worked OK on 5.5, but not on 6.2. > d> > d> The result of compiling both > d> > d> options SMP > d> > d> device carp > d> > d> into the kernel makes it crash in 'swi1: net' kernel thread on a random (usually first) use of the CARP facility. > d> > > d> > Can you please provide a backtrace? > d> > d> It's not that easy. The server becomes extremely unstable under these conditions. > d> I tried to build the kernel with '-g' option and included 'dumpdev' in /etc/rc.conf. The server can't even make a memory dump: it either gets one more page fault or just stops responding to anything but Reset key in the beginning of the dump. > d> It's strange since it rebooted well while the kernel was built without debugging symbols and a dumpdev. Any ideas how I can make a memory dump? > > Why do you think the CARP is guilty in this unstableness? Are you triggering > MASTER<->BACKUP events and this causes instability? CARP was my only 3rd subject for investigation. The previous two were polling (which is why I want to upgrade from 5.x to 6.x) and ACPI. I tried to build different kernels but as I included CARP even in GENERIC+SMP I saw the same effect. The server can sometimes hang on 'ifconfig' commands using CARP, but the easier way to reproduce the bug is to connect() to a socket on a CARP address. bind() can have the same effect -- I haven't tested that, but bind to INADDR_ANY works ok. From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 16:40:47 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFF9016A407 for ; Thu, 1 Mar 2007 16:40:47 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1C96513C461 for ; Thu, 1 Mar 2007 16:40:46 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 33480 invoked from network); 1 Mar 2007 16:13:30 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Mar 2007 16:13:30 -0000 Message-ID: <45E7020D.2000605@freebsd.org> Date: Thu, 01 Mar 2007 17:40:45 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Andrew Gallatin References: <45E6E2E8.5060408@freebsd.org> <17894.61337.772803.325091@grasshopper.cs.duke.edu> In-Reply-To: <17894.61337.772803.325091@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, rwatson@freebsd.org, kmacy@freebsd.org Subject: Re: Large TCP send socket buffer optimizations 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, 01 Mar 2007 16:40:47 -0000 Andrew Gallatin wrote: > Andre Oppermann writes: > > This patch solves the problem by maintaining an offset pointer in the socket > > buffer to give tcp_output() the closest mbuf right away avoiding the traversal > > from the beginning. > > > > With this patch we should be able to compete nicely for the Internet land > > speed record again. > > Great news. I will test soon. > > Have you found the bug which makes a freebsd sender spew > duplicate acks? This will have a negative affect on > any benchmarks.. No, not yet. And my current test environment doesn't lend itself to reproduce the bug easily. I'm very likely to need further input from you and will send you some patches for instrumentation in the near future. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 16:47:43 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4440D16A402 for ; Thu, 1 Mar 2007 16:47:43 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.freebsd.org (Postfix) with ESMTP id B41B113C4A8 for ; Thu, 1 Mar 2007 16:47:42 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from citrin (unknown [81.19.65.100]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: citrin.citrin.ru) by mail.classis.ru (Postfix) with ESMTP id 233FA12279A4; Thu, 1 Mar 2007 19:47:41 +0300 (MSK) Date: Thu, 1 Mar 2007 19:46:53 +0300 From: Anton Yuzhaninov X-Mailer: The Bat! (v3.62.14) Professional Organization: Rambler X-Priority: 3 (Normal) Message-ID: <1047693239.20070301194653@citrin.ru> To: Ruslan Ermilov In-Reply-To: <20070301152942.GA27336@rambler-co.ru> References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------D414CF8269B3701" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re[2]: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 16:47:43 -0000 This is a cryptographically signed message in MIME format. ------------D414CF8269B3701 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Thursday, March 1, 2007, 6:29:42 PM, Ruslan Ermilov wrote: RE> On Thu, Mar 01, 2007 at 03:17:29PM +0300, Anton Yuzhaninov wrote: >> Is SO_NOSIGPIPE work? >>=20 >> It try to set on socket option SO_NOSIGPIPE but anyway process >> received sigpipe. >>=20 RE> It works, but only if you use send() instead of write(). RE> Alternatively, you can control the behavior on a per RE> message basis, by passing the MSG_NOSIGNAL in the "flags" RE> argument to the send() call (without having to set a RE> socket option). Thanks, with send() it works fine. I think it should be documented in setsockopt(2). --=20 WBR, Anton Yuzhaninov ------------D414CF8269B3701-- From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 17:24:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34F4F16A400; Thu, 1 Mar 2007 17:24:40 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 0877E13C4A7; Thu, 1 Mar 2007 17:24:39 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id EF9521F4588; Thu, 1 Mar 2007 12:24:39 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Thu, 01 Mar 2007 12:24:39 -0500 X-Sasl-enc: z9G1jKwwxF3bJGgdtBa1GdsOCMTEM1wC+em2lZVszuKj 1172769879 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id D100324498; Thu, 1 Mar 2007 12:24:36 -0500 (EST) Message-ID: <45E70C52.2080500@FreeBSD.org> Date: Thu, 01 Mar 2007 17:24:34 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Anton Yuzhaninov References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> <1047693239.20070301194653@citrin.ru> In-Reply-To: <1047693239.20070301194653@citrin.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 17:24:40 -0000 Anton Yuzhaninov wrote: > RE> It works, but only if you use send() instead of write(). > RE> Alternatively, you can control the behavior on a per > RE> message basis, by passing the MSG_NOSIGNAL in the "flags" > RE> argument to the send() call (without having to set a > RE> socket option). > > Thanks, with send() it works fine. > I think it should be documented in setsockopt(2). > AFAIK this is not a POSIX sockopt. I can only trace it back to MacOS X as the origin. Most applications I know of set the handler for SIGPIPE to SIG_IGN in such situations. Call graph: write() -> dofilewrite() -> soo_write() -> pru_send() Looking at the code for the generic write() path it looks like we would never squelch this kind of SIGPIPE intentionally. In soo_write() we check the SO_NOSIGPIPE option to tell if we should call psignal(). However, as soon as we return from soo_write(), the EPIPE is mapped to psignal() by the generic code in dofilewrite() which generates the SIGPIPE you are seeing. I think this may be a bug but in the absence of precise written requirements I can't be sure. :-) BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 17:34:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D45BB16A401; Thu, 1 Mar 2007 17:34:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id A5EC113C49D; Thu, 1 Mar 2007 17:34:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 9E4321F2A85; Thu, 1 Mar 2007 12:34:53 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Thu, 01 Mar 2007 12:34:53 -0500 X-Sasl-enc: j08B2DY91JEJMzBhi1x5anZwIW73K8be8etfoKyu/TjZ 1172770493 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id B0ECD111DC; Thu, 1 Mar 2007 12:34:52 -0500 (EST) Message-ID: <45E70EBA.3030808@FreeBSD.org> Date: Thu, 01 Mar 2007 17:34:50 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Anton Yuzhaninov References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> <1047693239.20070301194653@citrin.ru> In-Reply-To: <1047693239.20070301194653@citrin.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: [PATCH] Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 17:34:53 -0000 Anton Yuzhaninov wrote: > > Thanks, with send() it works fine. > I think it should be documented in setsockopt(2). Try this patch. The comment doesn't reflect what the code does. SIGPIPE may actually be getting queued twice in your case. It is most likely that the process's main thread wasn't preempted before return from the syscall. Perhaps someone more familiar with the signal code than I can chime in. --- sys_generic.c 14 Oct 2006 19:01:55 -0000 1.151 +++ sys_generic.c 1 Mar 2007 17:30:39 -0000 @@ -489,7 +489,7 @@ dofilewrite(td, fd, fp, auio, offset, fl error == EINTR || error == EWOULDBLOCK)) error = 0; /* Socket layer is responsible for issuing SIGPIPE. */ - if (error == EPIPE) { + if (fp->f_type != DTYPE_SOCKET && error == EPIPE) { PROC_LOCK(td->td_proc); psignal(td->td_proc, SIGPIPE); PROC_UNLOCK(td->td_proc); From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 18:22:15 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D8F0516A401 for ; Thu, 1 Mar 2007 18:22:15 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.freebsd.org (Postfix) with ESMTP id 8C72B13C491 for ; Thu, 1 Mar 2007 18:22:15 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from citrin (unknown [81.19.65.100]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: citrin.citrin.ru) by mail.classis.ru (Postfix) with ESMTP id 330781227A01; Thu, 1 Mar 2007 21:22:14 +0300 (MSK) Date: Thu, 1 Mar 2007 21:21:26 +0300 From: Anton Yuzhaninov X-Mailer: The Bat! (v3.62.14) Professional Organization: Rambler X-Priority: 3 (Normal) Message-ID: <11810015988.20070301212126@citrin.ru> To: "Bruce M. Simpson" In-Reply-To: <45E70EBA.3030808@FreeBSD.org> References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> <1047693239.20070301194653@citrin.ru> <45E70EBA.3030808@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 18:22:15 -0000 Thursday, March 1, 2007, 8:34:50 PM, Bruce M. Simpson wrote: BMS> Anton Yuzhaninov wrote: >> >> Thanks, with send() it works fine. >> I think it should be documented in setsockopt(2). BMS> Try this patch. The comment doesn't reflect what the code does. SIGPIPE BMS> may actually be getting queued twice in your case. It is most likely BMS> that the process's main thread wasn't preempted before return from the BMS> syscall. Works for me. src/tools/regression/sockets/sigpipe also pass now (without this patch it failed) BMS> Perhaps someone more familiar with the signal code than I can chime in. BMS> --- sys_generic.c 14 Oct 2006 19:01:55 -0000 1.151 BMS> +++ sys_generic.c 1 Mar 2007 17:30:39 -0000 BMS> @@ -489,7 +489,7 @@ dofilewrite(td, fd, fp, auio, offset, fl BMS> error == EINTR || error == EWOULDBLOCK)) BMS> error = 0; BMS> /* Socket layer is responsible for issuing SIGPIPE. */ BMS> - if (error == EPIPE) { + if (fp->>f_type != DTYPE_SOCKET && error == EPIPE) { BMS> PROC_LOCK(td->td_proc); BMS> psignal(td->td_proc, SIGPIPE); BMS> PROC_UNLOCK(td->td_proc); -- WBR, Anton Yuzhaninov From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 20:09:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6895316A406 for ; Thu, 1 Mar 2007 20:09:38 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 3628F13C481 for ; Thu, 1 Mar 2007 20:09:38 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 32C6B1F24B2; Thu, 1 Mar 2007 15:09:38 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Thu, 01 Mar 2007 15:09:38 -0500 X-Sasl-enc: d+FYfXQfyvd7bxQEfnl8lQfNJs2oB5C/6iglcAUAukq9 1172779777 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 81D66BABE; Thu, 1 Mar 2007 15:09:37 -0500 (EST) Message-ID: <45E732FF.40800@FreeBSD.org> Date: Thu, 01 Mar 2007 20:09:35 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Anton Yuzhaninov References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> <1047693239.20070301194653@citrin.ru> <45E70EBA.3030808@FreeBSD.org> <11810015988.20070301212126@citrin.ru> In-Reply-To: <11810015988.20070301212126@citrin.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 20:09:38 -0000 Anton Yuzhaninov wrote: > Works for me. > Committed, thanks for finding this bug. BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 20:33:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4CAE916A400 for ; Thu, 1 Mar 2007 20:33:46 +0000 (UTC) (envelope-from njm@njm.f2s.com) Received: from outmail1.freedom2surf.net (outmail1.freedom2surf.net [194.106.33.237]) by mx1.freebsd.org (Postfix) with ESMTP id 07B8313C471 for ; Thu, 1 Mar 2007 20:33:46 +0000 (UTC) (envelope-from njm@njm.f2s.com) Received: from ariel.njm.f2s.com (i-195-137-21-170.freedom2surf.net [195.137.21.170]) by outmail1.freedom2surf.net (Postfix) with ESMTP id C5A1656CD3 for ; Thu, 1 Mar 2007 20:00:36 +0000 (GMT) Received: from ariel.njm.f2s.com (localhost.njm.f2s.com [127.0.0.1]) by ariel.njm.f2s.com (8.13.8/8.13.8) with ESMTP id l21K0Z9l011061 for ; Thu, 1 Mar 2007 20:00:35 GMT (envelope-from njm@ariel.njm.f2s.com) Received: (from njm@localhost) by ariel.njm.f2s.com (8.13.8/8.13.8/Submit) id l21K0ZbL011060 for freebsd-net@freebsd.org; Thu, 1 Mar 2007 20:00:35 GMT (envelope-from njm) Date: Thu, 1 Mar 2007 20:00:35 +0000 From: "N.J. Mann" To: freebsd-net@freebsd.org Message-ID: <20070301200035.GA9041@ariel.njm.f2s.com> Mail-Followup-To: freebsd-net@freebsd.org References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> <1047693239.20070301194653@citrin.ru> <45E70EBA.3030808@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E70EBA.3030808@FreeBSD.org> X-Operating-System: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: [PATCH] Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 20:33:46 -0000 On Thursday, 1 March, 2007 at 17:34:50 +0000, Bruce M. Simpson wrote: > Anton Yuzhaninov wrote: > > > >Thanks, with send() it works fine. > >I think it should be documented in setsockopt(2). > Try this patch. The comment doesn't reflect what the code does. SIGPIPE > may actually be getting queued twice in your case. It is most likely > that the process's main thread wasn't preempted before return from the > syscall. > > Perhaps someone more familiar with the signal code than I can chime in. > > --- sys_generic.c 14 Oct 2006 19:01:55 -0000 1.151 > +++ sys_generic.c 1 Mar 2007 17:30:39 -0000 > @@ -489,7 +489,7 @@ dofilewrite(td, fd, fp, auio, offset, fl > error == EINTR || error == EWOULDBLOCK)) > error = 0; > /* Socket layer is responsible for issuing SIGPIPE. */ > - if (error == EPIPE) { > + if (fp->f_type != DTYPE_SOCKET && error == EPIPE) { > PROC_LOCK(td->td_proc); > psignal(td->td_proc, SIGPIPE); > PROC_UNLOCK(td->td_proc); Could this be why mail from cron doesn't work for me in 6.2? I got as far as finding that cron receives a SIGPIPE while sending the mail message to sendmail, but never worked out why. I ended up hacking cron to ignore SIGPIPE and then ENOTIME to investigate further. Cheers, Nick. -- Please do not CC me on replies, I read the list and don't need the dupes. From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 20:40:13 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53B8616A400 for ; Thu, 1 Mar 2007 20:40:13 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 1F70113C48E for ; Thu, 1 Mar 2007 20:40:13 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 11FD41F473D for ; Thu, 1 Mar 2007 15:40:13 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Thu, 01 Mar 2007 15:40:13 -0500 X-Sasl-enc: CH4LYbGs18FwQAeQwTp4qNq7e9er88L9wRC30PvHju7F 1172781612 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id B44E4329A3 for ; Thu, 1 Mar 2007 15:40:12 -0500 (EST) Message-ID: <45E73A2A.3000805@FreeBSD.org> Date: Thu, 01 Mar 2007 20:40:10 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <2110071423.20070301151729@citrin.ru> <20070301152942.GA27336@rambler-co.ru> <1047693239.20070301194653@citrin.ru> <45E70EBA.3030808@FreeBSD.org> <20070301200035.GA9041@ariel.njm.f2s.com> In-Reply-To: <20070301200035.GA9041@ariel.njm.f2s.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] Re: is setsockopt SO_NOSIGPIPE work? 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, 01 Mar 2007 20:40:13 -0000 N.J. Mann wrote: > > Could this be why mail from cron doesn't work for me in 6.2? I got as > far as finding that cron receives a SIGPIPE while sending the mail > message to sendmail, but never worked out why. I ended up hacking cron > to ignore SIGPIPE and then ENOTIME to investigate further. Unlikely, unless cron were directly hooked up to a TCP socket. BMS From owner-freebsd-net@FreeBSD.ORG Thu Mar 1 21:06:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D95E916A401; Thu, 1 Mar 2007 21:06:46 +0000 (UTC) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6DB7F13C471; Thu, 1 Mar 2007 21:06:46 +0000 (UTC) (envelope-from andy@siliconlandmark.com) Received: from [10.7.6.254] ([63.76.235.163]) by lexi.siliconlandmark.com (8.13.8/8.13.3) with ESMTP id l21KrI5S049905; Thu, 1 Mar 2007 15:53:18 -0500 (EST) (envelope-from andy@siliconlandmark.com) In-Reply-To: <45E7020D.2000605@freebsd.org> References: <45E6E2E8.5060408@freebsd.org> <17894.61337.772803.325091@grasshopper.cs.duke.edu> <45E7020D.2000605@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andre Guibert de Bruet Date: Thu, 1 Mar 2007 15:53:13 -0500 To: Andre Oppermann X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: ClamAV 0.88.7/2690/Thu Mar 1 06:11:27 2007 on lexi.siliconlandmark.com X-Virus-Status: Clean X-Information: Please contact the ISP for more information X-SL-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-SL-SpamCheck: not spam, SpamAssassin (not cached, score=-2.008, required 6, autolearn=not spam, AWL 0.59, BAYES_00 -2.60, SPF_PASS -0.00) X-MailScanner-From: andy@siliconlandmark.com Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, rwatson@freebsd.org, Andrew Gallatin , kmacy@freebsd.org Subject: Re: Large TCP send socket buffer optimizations 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, 01 Mar 2007 21:06:46 -0000 On Mar 1, 2007, at 11:40 AM, Andre Oppermann wrote: > Andrew Gallatin wrote: >> Andre Oppermann writes: >> > This patch solves the problem by maintaining an offset pointer >> in the socket >> > buffer to give tcp_output() the closest mbuf right away >> avoiding the traversal >> > from the beginning. >> > > With this patch we should be able to compete nicely for the >> Internet land >> > speed record again. >> Great news. I will test soon. >> Have you found the bug which makes a freebsd sender spew >> duplicate acks? This will have a negative affect on >> any benchmarks.. > > No, not yet. And my current test environment doesn't lend itself > to reproduce > the bug easily. I'm very likely to need further input from you and > will send > you some patches for instrumentation in the near future. Please CC me on the patches. Did you get a chance to check out the pcap that I linked to? Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 00:03:26 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C94316A409 for ; Fri, 2 Mar 2007 00:03:26 +0000 (UTC) (envelope-from tsuyoshi.momose@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id B8F3013C474 for ; Fri, 2 Mar 2007 00:02:41 +0000 (UTC) (envelope-from tsuyoshi.momose@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so510891ana for ; Thu, 01 Mar 2007 16:02:40 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=KUT73VLg3c47yMbMuCcAyHf16CcBDhmpxrOPpvYGWFIKWYoCkYnXgMFKOFpQV7i0LjV98ZQytGV+THyos6KhhYelXdQnSRtVhupi5Y4N3+ERY9dS2sVf/FDY4Dn70N0zmEDwHTKMOEy+6yKlZP9BxbWqllN/uY4BvzY9pUB81i0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=QaqeGNjBqRgJe1C2yI1Ec1tsxqMe5uwHpVVYkgnh2gRSZw/sHO5x/eNgOQLHZ0SQsgl28a4md7gAQFeufj8xhI0cgI0f2FR4x9lz7Jc03r16t4Alwf/n59jKjatmJEyBhnkS3fjYj61SopydnUJxzxDS+A45mZ8dFxThZvZ5pm4= Received: by 10.115.89.1 with SMTP id r1mr29356wal.1172790274708; Thu, 01 Mar 2007 15:04:34 -0800 (PST) Received: from ?10.0.0.81? ( [203.141.155.85]) by mx.google.com with ESMTP id a8sm5631691poa.2007.03.01.15.04.32; Thu, 01 Mar 2007 15:04:32 -0800 (PST) In-Reply-To: <200702281233.50145.max@love2party.net> References: <45E541A2.4020005@cisco.com> <200702281233.50145.max@love2party.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-2022-JP; delsp=yes; format=flowed Message-Id: <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net> Content-Transfer-Encoding: 7bit From: Tsuyoshi MOMOSE Date: Fri, 2 Mar 2007 08:04:25 +0900 To: Max Laier , Randall Stewart X-Mailer: Apple Mail (2.752.3) Sender: Tsuyoshi MOMOSE Cc: freebsd-net@freebsd.org Subject: Re: Thinking about IPv6 and DEPRECATED addresses 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, 02 Mar 2007 00:03:26 -0000 On 2007/02/28, at 20:33, Max Laier wrote: >> So, I am contemplating adding to rtsock.c the ability to >> send these types of events up. I am thinking on adding >> this there for two reasons.. >> >> a) SCTP already hooks into the routing socket to get >> interface changes. >> and >> >> b) It may well be a relevant fact that if an address becomes >> DETACHED or non-DETACHED (etc) for a routing process >> to want to know about.. >> >> >> What do others think? If I am off in the weeds somewhere and >> this does not concern the routing socket I could use other >> methods .. including isolating the "look at the state" flags >> into a special place so that proper locking could be added >> when we actually do locking for the ifa's... of course I would >> prefer just not to have to look at it :-D >> >> Opinions if this is a good idea or not?? > > Great idea. I'm also CC-ing Tsuyoshi MOMOSE who is working on > importing > MIP6 which will likely be interested in this information (in > userland) as > well. AFAIK, the mnd already listens on the rtsock to pick up new > addresses as soon as possible, but not sooner (for which it has to go > through great lengths). Thanks for CCed to me. As Max said, our Mobile IPv6 stack uses rtsock to detect changing address address such as added, deleted. (but actually, the program which listens the rtsock is not mnd but mdd (babymdd). The aim of mdd is just detcting the movement of the node and notifies to mnd its movement information) To do that, SHISA introduces a new routing socket message RTM_ADDRINFO which is sent from kernel when a new address is attached, detached, and DAD was done. So, you can get an address information soon as possible. I guess the message meets Randall's requirement for the SCTP. I don't start the SHISA porting to the head yet, but I can begin the port first from the RTM_ADDRINFO part if you hope. ---------------------------- Tsuyoshi MOMOSE / $B$b$b$;$D$h$7(B momose@momose.org http://www.momose.org/ (Underconstruction) From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 10:22:42 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C00C16A404; Fri, 2 Mar 2007 10:22:42 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id A9B2E13C491; Fri, 2 Mar 2007 10:22:41 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l228lmKq009762; Fri, 2 Mar 2007 09:47:49 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id 755811550CC; Fri, 2 Mar 2007 09:47:47 +0100 (CET) Date: Fri, 2 Mar 2007 09:47:47 +0100 From: Alessandro de Manzano To: freebsd-net@freebsd.org Message-ID: <20070302084747.GA80114@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-amd64@freebsd.org Subject: two problems with broadcom NICs 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, 02 Mar 2007 10:22:42 -0000 Hello, I've got a bunch of new Dell PowerEdge SC440 machines, but I've some problems running FreeBSD on them. OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried also GENERIC monoprocessor), both i386 and amd64, always same results. Situation: Two Broadcom NICs, one on the motherboard and one on PCI-express bus, here is a snippet of pciconf -lv (as you can see I had to add a 3COM PCI card in order to have connectivity) bge0@pci3:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' class = network subclass = ethernet none1@pci4:0:0: class=0x020000 card=0x01df1028 chip=0x167a14e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class = network subclass = ethernet xl0@pci5:2:0: class=0x020000 card=0x100010b7 chip=0x920010b7 rev=0x74 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet The first one (bge0) is the motherboard integrated, the second one (none1) is on PCI-express Problems: First NIC: recognized, but it never see the carrier. ifconfig gives always this result: bge0: flags=8802 mtu 1500 options=1b ether 00:10:18:27:f3:4c media: Ethernet autoselect (none) status: no carrier No matter of what I do (change cable, change remote switch) it always gives "status: no carrier". Leds on the RJ-45 female connector are on (orange one for link) and off (activity). On the switch(es) link leds are always correctly on, so physic carrier should be present. What could be ? What could I try ? Ideas ? Second NIC: is not recognized at all. Maybe it's a matter of missing PCI IDs ? I don't know exactly which model is supposed to be, searching for those IDs gives inconsitances results.. This is a not-yet-in-production machine, so I can do any experiment necessary to solve these problems Hoping in your help ;) below is my full verbose dmesg Many thanks anyway! -- bye! Ale Copyright (c) 1992-2007 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 6.2-STABLE #0: Thu Mar 1 12:21:39 CET 2007 root@power64.playstos.ldr:/usr/obj/usr/src/sys/POWER64 Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80a9b000. Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0xffffffff80a9b1f8. INTR: Adding local APIC 0 as a target ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193207 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1862010668 Hz CPU: Intel(R) Xeon(R) CPU 3040 @ 1.86GHz (1862.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd,CX16,XTPR,> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 real memory = 1072152576 (1022 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000b98000 - 0x000000003e03efff, 1028288512 bytes (251047 pages) avail memory = 1022246912 (974 MB) INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 2 MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 8 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic: Routing NMI -> LINT1 lapic: LINT1 trigger: level lapic: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ath_rate: version 1.2 wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: io: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (Mar 1 2007 12:21:26) acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80000098 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=27788086) acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: Power Button (fixed) ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 11 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 10 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 3 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 3 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 9 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 5 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 9 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 5 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 10 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 cpu0: on acpi0 cpu0: switching to generic Cx mode acpi_perf0: on cpu0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x2778, revid=0x00 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2779, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27d0, revid=0x01 bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27e0, revid=0x01 bus=0, slot=28, func=4 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27e2, revid=0x01 bus=0, slot=28, func=5 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTB pcib0: slot 28 INTB hardwired to IRQ 17 found-> vendor=0x8086, dev=0x27c8, revid=0x01 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 map[20]: type 4, range 32, base 0000ff80, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 21 found-> vendor=0x8086, dev=0x27c9, revid=0x01 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[20]: type 4, range 32, base 0000ff60, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 22 found-> vendor=0x8086, dev=0x27ca, revid=0x01 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=3 map[20]: type 4, range 32, base 0000ff40, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 18 found-> vendor=0x8086, dev=0x27cb, revid=0x01 bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=10 map[20]: type 4, range 32, base 0000ff20, size 5, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 23 found-> vendor=0x8086, dev=0x27cc, revid=0x01 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base ff980800, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 21 found-> vendor=0x8086, dev=0x244e, revid=0xe1 bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27b8, revid=0x01 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0107, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27df, revid=0x01 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0288, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled pcib0: matched entry for 0.31.INTA pcib0: slot 31 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27c0, revid=0x01 bus=0, slot=31, func=2 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000fe00, size 3, enabled map[14]: type 4, range 32, base 0000fe10, size 2, enabled map[18]: type 4, range 32, base 0000fe20, size 3, enabled map[1c]: type 4, range 32, base 0000fe30, size 2, enabled map[20]: type 4, range 32, base 0000fec0, size 4, enabled map[24]: type 1, range 32, base effffc00, size 10, enabled pcib0: matched entry for 0.31.INTC pcib0: slot 31 INTC hardwired to IRQ 20 found-> vendor=0x8086, dev=0x27da, revid=0x01 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 map[20]: type 4, range 32, base 0000ece0, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 17 pcib1: irq 16 at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xefe00000-0xefefffff pcib1: prefetched decode 0xfff00000-0xfffff pci1: on pcib1 pci1: physical bus=1 pcib2: irq 16 at device 28.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xefd00000-0xefdfffff pcib2: prefetched decode 0xfff00000-0xfffff pci2: on pcib2 pci2: physical bus=2 pcib3: irq 16 at device 28.4 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xf000-0xfff pcib3: memory decode 0xefc00000-0xefcfffff pcib3: prefetched decode 0xfff00000-0xfffff pci3: on pcib3 pci3: physical bus=3 found-> vendor=0x14e4, dev=0x1659, revid=0x21 bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base efcf0000, size 16, enabled pcib3: requested memory range 0xefcf0000-0xefcfffff: good pcib3: matched entry for 3.0.INTA pcib3: slot 0 INTA hardwired to IRQ 16 bge0: mem 0xefcf0000-0xefcfffff irq 16 at device 0.0 on pci3 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xefcf0000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:10:18:27:f3:4c ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49 bge0: [MPSAFE] pcib4: irq 17 at device 28.5 on pci0 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0xf000-0xfff pcib4: memory decode 0xefb00000-0xefbfffff pcib4: prefetched decode 0xfff00000-0xfffff pci4: on pcib4 pci4: physical bus=4 found-> vendor=0x14e4, dev=0x167a, revid=0x02 bus=4, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 64, base efbf0000, size 16, enabled pcib4: requested memory range 0xefbf0000-0xefbfffff: good pcib4: matched entry for 4.0.INTA pcib4: slot 0 INTA hardwired to IRQ 17 pci4: at device 0.0 (no driver attached) uhci0: port 0xff80-0xff9f irq 21 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff80 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 50 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 22 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff60 ioapic0: routing intpin 22 (PCI IRQ 22) to vector 51 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff40 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 52 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xff20-0xff3f irq 23 at device 29.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff20 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 53 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xff980800-0xff980bff irq 21 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xff980800 ehci0: [GIANT-LOCKED] usb4: waiting for BIOS to give up control usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib5: at device 30.0 on pci0 pcib5: secondary bus 5 pcib5: subordinate bus 5 pcib5: I/O decode 0xd000-0xdfff pcib5: memory decode 0xef900000-0xefafffff pcib5: prefetched decode 0xe0000000-0xe7ffffff pcib5: Subtractively decoded bridge. pci5: on pcib5 pci5: physical bus=5 found-> vendor=0x10b7, dev=0x9200, revid=0x74 bus=5, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=3 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000d880, size 7, enabled pcib5: requested I/O range 0xd880-0xd8ff: in range map[14]: type 1, range 32, base ef9eff80, size 7, enabled pcib5: requested memory range 0xef9eff80-0xef9effff: good pcib5: matched entry for 5.2.INTA pcib5: slot 2 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x515e, revid=0x02 bus=5, slot=7, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0183, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base e0000000, size 27, enabled pcib5: requested memory range 0xe0000000-0xe7ffffff: good map[14]: type 4, range 32, base 0000dc00, size 8, enabled pcib5: requested I/O range 0xdc00-0xdcff: in range map[18]: type 1, range 32, base ef9f0000, size 16, enabled pcib5: requested memory range 0xef9f0000-0xef9fffff: good pcib5: matched entry for 5.7.INTA pcib5: slot 7 INTA hardwired to IRQ 19 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd880-0xd8ff mem 0xef9eff80-0xef9effff irq 18 at device 2.0 on pci5 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xef9eff80 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus1: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:04:76:24:2c:e6 xl0: [MPSAFE] pci5: at device 7.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=01 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x01 err=0x04 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=01 devices=0x4 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55 ata1: [MPSAFE] atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf mem 0xeffffc00-0xefffffff irq 20 at device 31.2 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfec0 ioapic0: routing intpin 20 (PCI IRQ 20) to vector 56 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xfe00 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xfe10 ata2: reset tp1 mask=03 ostat0=80 ostat1=80 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=50 devices=0x3 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xfe20 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xfe30 ata3: reset tp1 mask=00 ostat0=ff ostat1=ff ata3: [MPSAFE] pci0: at device 31.3 (no driver attached) fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 ioapic0: routing intpin 6 (ISA IRQ 6) to vector 57 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x4c29 0x4c39 0x4c29 0x4c29 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ioapic0: routing intpin 4 (ISA IRQ 4) to vector 58 ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed ex_isa_identify() fdc: fdc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xc97ff,0xc9800-0xcb7ff,0xcb800-0xcbfff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0xffffffff (1) atkbd: failed to reset the keyboard. kbd0 at atkbd0 kbd0: atkbd0, AT 84 (1), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 59 atkbd0: [GIANT-LOCKED] psm0: current command byte:0045 psm0: failed to reset the aux device. ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x4c29 0x4c29 0x4c29 0x4c29 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices ums0: Dell Dell USB Mouse, rev 1.10/29.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhub5: vendor 0x0451 product 0x1446, class 9/0, rev 1.10/1.10, addr 2 uhub5: 4 ports with 4 removable, self powered ukbd0: vendor 0x045e Microsoft Internet Keyboard Pro, rev 1.10/1.11, addr 3, iclass 3/1 kbd2 at ukbd0 kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000 uhid0: vendor 0x045e Microsoft Internet Keyboard Pro, rev 1.10/1.11, addr 3, iclass 3/1 Device configuration finished. linprocfs registered procfs registered lapic: Divisor 2, Frequency 133000422 hz Timecounter "TSC" frequency 1862010668 Hz quality -100 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached rr232x: no controller detected. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on ICH7 chip acd0: setting UDMA33 on ICH7 chip acd0: DVDROM drive at ata0 as master acd0: read 8268KB/s (8268KB/s), 256KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata2-slave: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 76293MB at ata2-master SATA150 ad4: 156250000 sectors [155009C/16H/63S] 16 sectors/interrupt 1 depth queue ad4: Intel check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ad5: 76293MB at ata2-slave SATA150 ad5: 156250000 sectors [155009C/16H/63S] 16 sectors/interrupt 1 depth queue ad5: Intel check1 failed ad5: Adaptec check1 failed ad5: LSI (v3) check1 failed ad5: LSI (v2) check1 failed ad5: FreeBSD check1 failed ATA PseudoRAID loaded lapic1: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 4 to local APIC 1 ioapic0: Assigning ISA IRQ 6 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 1 ioapic0: Assigning ISA IRQ 14 to local APIC 0 ioapic0: Assigning ISA IRQ 15 to local APIC 1 ioapic0: Assigning PCI IRQ 16 to local APIC 0 ioapic0: Assigning PCI IRQ 18 to local APIC 1 ioapic0: Assigning PCI IRQ 20 to local APIC 0 ioapic0: Assigning PCI IRQ 21 to local APIC 1 ioapic0: Assigning PCI IRQ 22 to local APIC 0 ioapic0: Assigning PCI IRQ 23 to local APIC 1 GEOM: new disk ad4 GEOM: new disk ad5 GEOM_MIRROR: Device gm0 created (id=3212637885). GEOM_MIRROR: Device gm0: provider ad4 detected. GEOM_MIRROR: Device gm0: provider ad5 detected. GEOM_MIRROR: Device gm0: provider ad5 activated. GEOM_MIRROR: Device gm0: provider ad4 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. Trying to mount root from ufs:/dev/mirror/gm0s1a start_init: trying /sbin/init From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 11:45:35 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 954DF16A402; Fri, 2 Mar 2007 11:45:35 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id E7CD413C442; Fri, 2 Mar 2007 11:45:34 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l22BaHOB002797; Fri, 2 Mar 2007 11:36:19 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l22BaHtS002796; Fri, 2 Mar 2007 11:36:17 GMT (envelope-from dunstan) Date: Fri, 2 Mar 2007 11:36:15 +0000 From: "Wojciech A. Koszek" To: Alessandro de Manzano Message-ID: <20070302113615.GA2766@FreeBSD.czest.pl> References: <20070302084747.GA80114@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Fri, 02 Mar 2007 11:36:19 +0000 (UTC) Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs 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, 02 Mar 2007 11:45:35 -0000 On Fri, Mar 02, 2007 at 09:47:47AM +0100, Alessandro de Manzano wrote: > Hello, > > > What could be ? What could I try ? Ideas ? You can check if changing the interface "UP" flag makes in any better: ifconfig up -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 12:51:35 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF6BA16A401; Fri, 2 Mar 2007 12:51:35 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi2.ngi.it (smtpi2.ngi.it [88.149.128.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6381613C461; Fri, 2 Mar 2007 12:51:35 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi2.ngi.it (8.13.8/8.13.8) with ESMTP id l22CpXi7031136; Fri, 2 Mar 2007 13:51:33 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id 6A18C1550CC; Fri, 2 Mar 2007 13:51:32 +0100 (CET) Date: Fri, 2 Mar 2007 13:51:32 +0100 From: Alessandro de Manzano To: freebsd-net@freebsd.org Message-ID: <20070302125132.GA80931@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs 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, 02 Mar 2007 12:51:36 -0000 On Fri, Mar 02, 2007 at 09:47:47AM +0100, Alessandro de Manzano wrote: > The first one (bge0) is the motherboard integrated, the second one > (none1) is on PCI-express ERRATA: sorry, I swapped them, bge0 is the PCI-express one, none1 is the motherboard integrated one! -- bye! Ale From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 12:59:44 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D115616A5A5 for ; Fri, 2 Mar 2007 12:59:44 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70]) by mx1.freebsd.org (Postfix) with ESMTP id AA27313C4A7 for ; Fri, 2 Mar 2007 12:59:44 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-1.cisco.com with ESMTP; 02 Mar 2007 04:59:44 -0800 X-IronPort-AV: i="4.14,241,1170662400"; d="scan'208"; a="765209744:sNHT47377676" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l22Cxi9A017122; Fri, 2 Mar 2007 04:59:44 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l22Cxbho024863; Fri, 2 Mar 2007 04:59:41 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 04:59:37 -0800 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 04:59:35 -0800 Message-ID: <45E81F98.8040205@cisco.com> Date: Fri, 02 Mar 2007 07:59:04 -0500 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6 MIME-Version: 1.0 To: Tsuyoshi MOMOSE References: <45E541A2.4020005@cisco.com> <200702281233.50145.max@love2party.net> <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net> In-Reply-To: <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Mar 2007 12:59:35.0987 (UTC) FILETIME=[A1223030:01C75CCA] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2782; t=1172840384; x=1173704384; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Re=3A=20Thinking=20about=20IPv6=20and=20DEPRECATED=20addresse s |Sender:=20; bh=1yEQLPT59vFS5uUA5SX/xbN5Vp8/Lnjwmn1q4r1jrA0=; b=FiVOsqKjlZUo9QvCZ7Dj3uF+VDyvjHkrNjyOEHYGb6ahImxan2L0Byy5AXaufLOKGqt1wZUk oSXm1jvNyTycsDXn4S/a4nSvEzO3MP++YbLvwegLaQGDihs3fhcl2elC; Authentication-Results: sj-dkim-6; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim6002 verified; ); Cc: Max Laier , freebsd-net@freebsd.org Subject: Re: Thinking about IPv6 and DEPRECATED addresses 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, 02 Mar 2007 12:59:44 -0000 Tsuyoshi MOMOSE wrote: > > On 2007/02/28, at 20:33, Max Laier wrote: > >>> So, I am contemplating adding to rtsock.c the ability to >>> send these types of events up. I am thinking on adding >>> this there for two reasons.. >>> >>> a) SCTP already hooks into the routing socket to get >>> interface changes. >>> and >>> >>> b) It may well be a relevant fact that if an address becomes >>> DETACHED or non-DETACHED (etc) for a routing process >>> to want to know about.. >>> >>> >>> What do others think? If I am off in the weeds somewhere and >>> this does not concern the routing socket I could use other >>> methods .. including isolating the "look at the state" flags >>> into a special place so that proper locking could be added >>> when we actually do locking for the ifa's... of course I would >>> prefer just not to have to look at it :-D >>> >>> Opinions if this is a good idea or not?? >> >> Great idea. I'm also CC-ing Tsuyoshi MOMOSE who is working on importing >> MIP6 which will likely be interested in this information (in userland) as >> well. AFAIK, the mnd already listens on the rtsock to pick up new >> addresses as soon as possible, but not sooner (for which it has to go >> through great lengths). > > Thanks for CCed to me. > > As Max said, our Mobile IPv6 stack uses rtsock to detect changing > address address such as added, deleted. > (but actually, the program which listens the rtsock is not mnd but > mdd(babymdd). The aim of mdd is just detcting the movement of the node > and notifies to mnd its movement information) > > To do that, SHISA introduces a new routing socket message RTM_ADDRINFO > which is sent from kernel when a new address is attached, detached, and > DAD was done. So, you can get an address information soon as possible. > I guess the message meets Randall's requirement for the SCTP. > > I don't start the SHISA porting to the head yet, but I can begin the > port first from the RTM_ADDRINFO part if you hope. Well it might meet some of them.. I need to know when DAD is done, but also if a interface detaches.. aka stops hearing the RT adverts.. and then later starts hearing them again.. I was thinking of all the various states V6 addresses go through.. Now, I would love to look at your "patch" if you could send it to me.. and see if it can be the basis for what I want. Will you be at the WIDE meeting next week? Or maybe BSD Asia. If so maybe we could meet up to discuss this :-) R > > > > ---------------------------- > Tsuyoshi MOMOSE / $B$b$b$;$D$h$7(B > momose@momose.org > http://www.momose.org/ (Underconstruction) > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 13:32:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3729E16A404 for ; Fri, 2 Mar 2007 13:32:31 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8654713C4B8 for ; Fri, 2 Mar 2007 13:32:30 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 43444 invoked from network); 2 Mar 2007 13:05:04 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2007 13:05:04 -0000 Message-ID: <45E8276D.60105@freebsd.org> Date: Fri, 02 Mar 2007 14:32:29 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gallatin@freebsd.org, rwatson@freebsd.org, kmacy@freebsd.org Subject: New optimized soreceive_stream() for TCP sockets, proof of concept 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, 02 Mar 2007 13:32:31 -0000 Currently we are using the generic soreceive_generic() function to pull and copy data from the socket buffer to userland. It is a huge function that can deal with all eventualities and types of data that may happen on socket buffers. From a performance point of view most importantly it does a unlock- lock cycle per mbuf data segment that is copied out. This is neccessary to avoid deadlocks. On high speed TCP connections this leads to high locking overhead and contention on the receive socket buffer lock as both the upper and the lower half have to compete. The lower half wants to add newly received data while the upper half wants to move it to userland and the application. This patch takes a different approach by adding a specific soreceive_stream() function that is highly optimized for stream type sockets as TCP uses. On the send side we've done this differentiation in a different way a long time ago. Instead of the unlock-lock dance soreceive_stream() pulls a properly sized (relative to the receive system call buffer space) from the socket buffer drops the lock and gives copyout as much time as it needs. In the mean time the lower half can happily add as many new packets as it wants without having to wait for a lock. It also allows the upper and lower halfs to run on different CPUs without much interference. There is a unsolved nasty race condition in the patch though. When the socket closes and we still have data around or the copyout failed it tries to put the data back into the socket buffer which is gone already by then leading to a panic. Work is underway to find a realiable fix for this. I wanted to get this out to the community nonetheless to give it some more exposure. The patch is here: http://people.freebsd.org/~andre/soreceive_stream-20070302.diff Any testing, especially on 10Gig cards, and feedback appreciated. -- Andre From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 16:14:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A310116A404; Fri, 2 Mar 2007 16:14:57 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id 64D2113C467; Fri, 2 Mar 2007 16:14:57 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.14.0/8.14.0) with ESMTP id l22GEu7E028871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Mar 2007 11:14:56 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id l22GEput046769; Fri, 2 Mar 2007 11:14:51 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17896.19835.258246.284397@grasshopper.cs.duke.edu> Date: Fri, 2 Mar 2007 11:14:51 -0500 (EST) To: Andre Oppermann In-Reply-To: <45E8276D.60105@freebsd.org> References: <45E8276D.60105@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, rwatson@freebsd.org, kmacy@freebsd.org Subject: Re: New optimized soreceive_stream() for TCP sockets, proof of concept 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, 02 Mar 2007 16:14:57 -0000 Andre Oppermann writes: > Instead of the unlock-lock dance soreceive_stream() pulls a properly sized > (relative to the receive system call buffer space) from the socket buffer drops > the lock and gives copyout as much time as it needs. In the mean time the lower > half can happily add as many new packets as it wants without having to wait for > a lock. It also allows the upper and lower halfs to run on different CPUs without > much interference. There is a unsolved nasty race condition in the patch though. Excellent. This sounds very exciting! > Any testing, especially on 10Gig cards, and feedback appreciated. I'll try to test sometime soon, but possibly not until next week.. Is there any particular config you're interested in? If not, I'll just compare the pre/post-patch performance of a fast (linux) sender to an SMP (FreeBSD) receiver, using the default "out of the box" settings for a jumbo and standard MTU. Drew From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 20:57:35 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1040116A402 for ; Fri, 2 Mar 2007 20:57:35 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 7E8F713C4A3 for ; Fri, 2 Mar 2007 20:57:34 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 47406 invoked from network); 2 Mar 2007 20:30:04 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2007 20:30:04 -0000 Message-ID: <45E88FBD.4060407@freebsd.org> Date: Fri, 02 Mar 2007 21:57:33 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qingli@freebsd.org, silby@freebsd.org, bms@freebsd.org, mohans@freebsd.org Subject: Unification and simplification of outbound TCP options handling 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, 02 Mar 2007 20:57:35 -0000 In tcp_syncache and tcp_output we have two entirely separate code paths dealing with outbound TCP options. Each of them has a significant size and many quirks. This patch is a proper rewrite of both of them and introduces a new generic function tcp_addoptions() to tcp_output.c. The new function is then used in both the syncache and the normal tcp_output path instead of their previous versions. It it alignment agnostic and can be used to write directly into mbufs with any alignment. The patch is here: http://people.freebsd.org/~andre/tcp_options-20070302.diff Any testing and reviews appreciated. -- Andre From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 21:11:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89FF116A402; Fri, 2 Mar 2007 21:11:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp2.utdallas.edu (smtp2.utdallas.edu [129.110.10.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF5B13C461; Fri, 2 Mar 2007 21:11:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp2.utdallas.edu (Postfix) with ESMTP id 1D96A5C2EF; Fri, 2 Mar 2007 14:37:50 -0600 (CST) Date: Fri, 02 Mar 2007 14:37:50 -0600 From: Paul Schmehl To: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Message-ID: <0596BF936C9E2F724954C223@utd59514.utdallas.edu> In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========9CE1C0190F08AECC356A==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: two problems with broadcom NICs 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, 02 Mar 2007 21:11:00 -0000 --==========9CE1C0190F08AECC356A========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Friday, March 02, 2007 09:47:47 +0100 Alessandro de Manzano=20 wrote: > Hello, > > I've got a bunch of new Dell PowerEdge SC440 machines, but I've some > problems running FreeBSD on them. > > OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried > also GENERIC monoprocessor), both i386 and amd64, always same results. > > Situation: Two Broadcom NICs, one on the motherboard and one on > PCI-express bus, here is a snippet of pciconf -lv (as you can see I had > to add a 3COM PCI card in order to have connectivity) > > > bge0@pci3:0:0: class=3D0x020000 card=3D0x165914e4 chip=3D0x165914e4 = rev=3D0x21 > hdr=3D0x00 vendor =3D 'Broadcom Corporation' > device =3D 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > class =3D network > subclass =3D ethernet > none1@pci4:0:0: class=3D0x020000 card=3D0x01df1028 chip=3D0x167a14e4 = rev=3D0x02 > hdr=3D0x00 vendor =3D 'Broadcom Corporation' > class =3D network > subclass =3D ethernet > xl0@pci5:2:0: class=3D0x020000 card=3D0x100010b7 chip=3D0x920010b7 = rev=3D0x74 > hdr=3D0x00 vendor =3D '3COM Corp, Networking Division' > device =3D '3C905C-TX Fast EtherLink for PC Management NIC' > class =3D network > subclass =3D ethernet > Shouldn't you be using the bce driver? This is an i386 machine, but amd64=20 should work the same (you're using the same chipset): bce0@pci9:0:0: class=3D0x020000 card=3D0x01b31028 chip=3D0x164c14e4 = rev=3D0x11=20 hdr=3D0x00 vendor =3D 'Broadcom Corporation' class =3D network subclass =3D ethernet bce1@pci5:0:0: class=3D0x020000 card=3D0x01b31028 chip=3D0x164c14e4 = rev=3D0x11=20 hdr=3D0x00 vendor =3D 'Broadcom Corporation' class =3D network subclass =3D ethernet This is a Dell 1950, from dmesg.boot: bce0: mem=20 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz bce1: mem=20 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========9CE1C0190F08AECC356A==========-- From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 22:55:41 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E581E16A400; Fri, 2 Mar 2007 22:55:41 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 9C50D13C442; Fri, 2 Mar 2007 22:55:41 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l22Mtehf064319; Fri, 2 Mar 2007 17:55:40 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-net@FreeBSD.org Date: Fri, 2 Mar 2007 17:55:35 -0500 User-Agent: KMail/1.6.2 References: <20070302084747.GA80114@libero.sunshine.ale> In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200703021755.36600.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2702/Fri Mar 2 10:04:51 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Alessandro de Manzano , freebsd-amd64@FreeBSD.org Subject: Re: two problems with broadcom NICs 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, 02 Mar 2007 22:55:42 -0000 On Friday 02 March 2007 03:47 am, Alessandro de Manzano wrote: > Hello, > > I've got a bunch of new Dell PowerEdge SC440 machines, but I've > some problems running FreeBSD on them. > > OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but > tried also GENERIC monoprocessor), both i386 and amd64, always same > results. > > Situation: Two Broadcom NICs, one on the motherboard and one on > PCI-express bus, here is a snippet of pciconf -lv (as you can see I > had to add a 3COM PCI card in order to have connectivity) > > > bge0@pci3:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 > rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' > device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > class = network > subclass = ethernet I am not sure about this controller (BTW, you had to include dmesg output) but you may want to try -CURRENT. > none1@pci4:0:0: class=0x020000 card=0x01df1028 chip=0x167a14e4 > rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' > class = network > subclass = ethernet This controller is not supported in 6.2-RELEASE. It should be supported in -CURRENT. Jung-uk Kim From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 23:42:43 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4883916A402 for ; Fri, 2 Mar 2007 23:42:43 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id A7CC013C46B for ; Fri, 2 Mar 2007 23:42:42 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l22NgfSQ009900 for ; Sat, 3 Mar 2007 10:42:41 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l22NgfSb009899 for freebsd-net@freebsd.org; Sat, 3 Mar 2007 10:42:41 +1100 (EST) (envelope-from peter) Date: Sat, 3 Mar 2007 10:42:40 +1100 From: Peter Jeremy To: freebsd-net@freebsd.org Message-ID: <20070302234240.GA9421@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Subject: TCP source port reuse problems 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, 02 Mar 2007 23:42:43 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, After upgrading my firewall to FreeBSD 6.2-RELEASE (with IPfilter), I noticed that TCP connections between my firewall and internal hosts (all FreeBSD and mostly 6.2) were randomly dropping out. I've found a variety of anomolies in both FreeBSD and IPfilter and will post about them separately. In the following, the internal host is 192.168.234.64 and it is running 6.2-STABLE/amd64 from late January. First problem: FreeBSD appears to be re-using source ports too rapidly. My understanding is that a TCP socket ({src IP, src port, dst IP, dst port} tuple) should not be re-used for 120 seconds after teardown. Sample tcpdumps and IPfilter whinges below show reuse after 66 and 83 seconds. Disabling net.inet.ip.portrange.randomized appears to work around this but is undesirable for other reasons. 08:00:31.668618 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1301449385:13= 01449385(0) win 65535 08:00:31.669181 IP 192.168.234.1.22 > 192.168.234.64.63872: S 2272001345:22= 72001345(0) ack 1301449386 win 65535 08:00:31.672974 IP 192.168.234.64.63872 > 192.168.234.1.22: . ack 227200134= 6 win 33304 =2E.. 08:00:32.786175 IP 192.168.234.1.22 > 192.168.234.64.63872: P 2272031433:22= 72031561(128) ack 1301451929 win 33304 08:00:32.786631 IP 192.168.234.64.63872 > 192.168.234.1.22: P 1301451929:13= 01451961(32) ack 2272031561 win 33304 08:00:32.786690 IP 192.168.234.64.63872 > 192.168.234.1.22: F 1301451961:13= 01451961(0) ack 2272031561 win 33304 08:00:32.787159 IP 192.168.234.1.22 > 192.168.234.64.63872: . ack 130145196= 2 win 33288 08:00:32.796379 IP 192.168.234.1.22 > 192.168.234.64.63872: F 2272031561:22= 72031561(0) ack 1301451962 win 33288 08:00:32.796621 IP 192.168.234.64.63872 > 192.168.234.1.22: . ack 227203156= 2 win 33303 08:01:38.540025 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:01:41.536233 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:01:44.736148 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:01:47.936094 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:01:51.136055 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:01:54.336026 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:02:00.535977 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:02:12.735809 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 08:02:36.935520 IP 192.168.234.64.63872 > 192.168.234.1.22: S 1371565575:13= 71565575(0) win 65535 Mar 3 08:01:39 fwall ipmon[575]: 08:01:38.540233 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 64 -S IN OOW Mar 3 08:01:42 fwall ipmon[575]: 08:01:41.536388 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 64 -S IN OOW Mar 3 08:01:45 fwall ipmon[575]: 08:01:44.736309 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 64 -S IN OOW Mar 3 08:01:48 fwall ipmon[575]: 08:01:47.936239 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:01:51 fwall ipmon[575]: 08:01:51.136205 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:01:54 fwall ipmon[575]: 08:01:54.336173 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:02:01 fwall ipmon[575]: 08:02:00.536124 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:02:13 fwall ipmon[575]: 08:02:12.735960 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:02:37 fwall ipmon[575]: 08:02:36.935674 fxp1 @10:4 b 192.168.234.= 64,63872 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW 08:03:06.348372 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3089625906:30= 89625906(0) win 65535 08:03:06.348987 IP 192.168.234.1.22 > 192.168.234.64.60014: S 1659245487:16= 59245487(0) ack 3089625907 win 65535 08:03:06.349213 IP 192.168.234.64.60014 > 192.168.234.1.22: . ack 165924548= 8 win 33304 =2E.. 08:03:07.472719 IP 192.168.234.1.22 > 192.168.234.64.60014: P 1659276391:16= 59276519(128) ack 3089628450 win 33304 08:03:07.473177 IP 192.168.234.64.60014 > 192.168.234.1.22: P 3089628450:30= 89628482(32) ack 1659276519 win 33304 08:03:07.473234 IP 192.168.234.64.60014 > 192.168.234.1.22: F 3089628482:30= 89628482(0) ack 1659276519 win 33304 08:03:07.473722 IP 192.168.234.1.22 > 192.168.234.64.60014: . ack 308962848= 3 win 33288 08:03:07.482770 IP 192.168.234.1.22 > 192.168.234.64.60014: F 1659276519:16= 59276519(0) ack 3089628483 win 33288 08:03:07.483011 IP 192.168.234.64.60014 > 192.168.234.1.22: . ack 165927652= 0 win 33303 08:04:30.990192 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:04:33.989120 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:04:37.189082 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:04:40.389049 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:04:43.589015 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:04:46.788957 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:04:52.988886 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:05:05.188740 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 08:05:29.388457 IP 192.168.234.64.60014 > 192.168.234.1.22: S 3178380813:31= 78380813(0) win 65535 Mar 3 08:04:31 fwall ipmon[575]: 08:04:30.990391 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 64 -S IN OOW Mar 3 08:04:34 fwall ipmon[575]: 08:04:33.989273 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 64 -S IN OOW Mar 3 08:04:37 fwall ipmon[575]: 08:04:37.189232 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 64 -S IN OOW Mar 3 08:04:40 fwall ipmon[575]: 08:04:40.389201 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:04:44 fwall ipmon[575]: 08:04:43.589164 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:04:47 fwall ipmon[575]: 08:04:46.789101 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:04:53 fwall ipmon[575]: 08:04:52.989035 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:05:05 fwall ipmon[575]: 08:05:05.188887 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW Mar 3 08:05:29 fwall ipmon[575]: 08:05:29.388632 fxp1 @10:4 b 192.168.234.= 64,60014 -> 192.168.234.1,22 PR tcp len 20 48 -S IN OOW --=20 Peter Jeremy --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF6LZw/opHv/APuIcRAqiNAJ4ytizhvInH0Def0kjl6d6Tdc6sxQCaA8VP 8Ny/6E1GpCakBYE4O+3L0Nc= =idLX -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 23:55:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B16A016A400 for ; Fri, 2 Mar 2007 23:55:18 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 8C3DE13C49D for ; Fri, 2 Mar 2007 23:55:18 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 777A41F43AA for ; Fri, 2 Mar 2007 18:55:18 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Fri, 02 Mar 2007 18:55:18 -0500 X-Sasl-enc: pmhqGYKPfADfn9N1pfH1Rng3xQh3zztIoskw0GqclzDY 1172879718 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 34DFD14055 for ; Fri, 2 Mar 2007 18:55:18 -0500 (EST) Message-ID: <45E8B964.2090200@incunabulum.net> Date: Fri, 02 Mar 2007 23:55:16 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [PATCH] Ethernet cleanup; 802.1p input and M_PROMISC 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, 02 Mar 2007 23:55:18 -0000 Hello all, I would like to announce an updated version of the 802.1p input patch, available at: http://people.freebsd.org/~bms/dump/latest-8021p.diff I have cut down the original scope of the patch. I previously ran into problems when I tried to move VLAN tag input and output processing into if_ethersubr.c. FreeBSD should now accept VLAN 0 traffic on input with this patch. In addition to this, the M_PROMISC flag is now used, which considerably simplifies the Ethernet input path in general. I have performed some light testing on a 1Gbps COTS switch with 802.1q encapsulation and without, with carp and vlan, with and without hardware VLAN tagging, and all looks OK. I would greatly appreciate further testing, particularly with if_bridge and ng_ether which I have not tried. If all goes to plan, I would hope to commit this code to -CURRENT within the next 10 days. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 00:03:07 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 676FF16A400 for ; Sat, 3 Mar 2007 00:03:07 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 42BB113C442 for ; Sat, 3 Mar 2007 00:03:07 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 1F8341F500C for ; Fri, 2 Mar 2007 19:03:07 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Fri, 02 Mar 2007 19:03:07 -0500 X-Sasl-enc: pR6mWSE8kA/0limXhcNKVcxt1ot9PeM7KsRLouBZ3ME0 1172880187 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id E7800BABF for ; Fri, 2 Mar 2007 19:03:06 -0500 (EST) Message-ID: <45E8BB39.9030602@incunabulum.net> Date: Sat, 03 Mar 2007 00:03:05 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: CARP behaviour 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, 03 Mar 2007 00:03:07 -0000 During testing of M_PROMISC I noticed a couple of issues with our CARP. 1. carp doesn't seem to maintain input/output statistics on its ifnet. 2. carp doesn't seem to detect that the underlying route to the subnet its address is exposed on changed to another interface. Are these conditions normal / expected? Regards, BMS From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 16:53:23 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E39016A405 for ; Sat, 3 Mar 2007 16:53:23 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id E551713C4A5 for ; Sat, 3 Mar 2007 16:53:19 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id DAA18352 for ; Sun, 4 Mar 2007 03:53:16 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 4 Mar 2007 03:53:15 +1100 (EST) From: Ian Smith To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: mpd 4.1 on 5.5-STABLE 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, 03 Mar 2007 16:53:23 -0000 I'm having trouble getting mpd 4.1 going, and am a netgraph noobie. FreeBSD paqi.nimnet.asn.au 5.5-STABLE FreeBSD 5.5-STABLE #0: Sat Mar 3 03:14:13 EST 2007 root@paqi.nimnet.asn.au:/usr/obj/usr/src/sys/PAQI5S_3 i386 paqi# mpd4 -v Version 4.1 (root@paqi.nimnet.asn.au 20:51 3-Mar-2007) /etc/rc.conf (updated since rebooting after installworld) has: mpd_enable="YES" mpd_flags="-b" When started the first time, before there's any ng0 interface, mpd logs the following two lines then immediately exits without further ado: paqi# /usr/local/etc/rc.d/mpd4.sh start Starting mpd4. /var/log/mpd.log: [.. previous attempts with mpd4.1-rc2 on a 5.5-STABLE from December, with exactly the same set of symptoms as now ..] Mar 3 23:25:18 paqi mpd: process 36762 started, version 4.1 (root@paqi.nimnet.asn.au 20:51 3-Mar-2007) Mar 3 23:25:18 paqi mpd: CONSOLE: listening on 127.0.0.1 5005 paqi# ps aux | grep "[m]pd" paqi# sockstat | grep mpd Having been exactly here before with rc2, I see ng0 has been created: paqi# ifconfig plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 dc0: flags=108843 mtu 1500 options=8 inet 192.168.7.1 netmask 0xffffff00 broadcast 192.168.7.255 ether 00:14:6c:8e:ef:37 media: Ethernet 100baseTX status: active xe0: flags=108843 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:80:c7:ea:cb:c5 media: Ethernet 10baseT/UTP status: active ng0: flags=8890 mtu 1500 and know that it'll refer to the now-dead PID 36762 from above: paqi# ngctl list There are 5 total nodes: Name: ngctl36785 Type: socket ID: 00000006 Num hooks: 0 Name: mpd36762-PPPoE-bpf Type: bpf ID: 00000005 Num hooks: 2 Name: mpd36762-PPPoE-vjc Type: vjc ID: 00000004 Num hooks: 4 Name: mpd36762-PPPoE Type: ppp ID: 00000003 Num hooks: 6 Name: ng0 Type: iface ID: 00000002 Num hooks: 2 paqi# ngctl list -l There are 5 total nodes: Name: ngctl36786 Type: socket ID: 00000007 Num hooks: 0 Name: mpd36762-PPPoE-bpf Type: bpf ID: 00000005 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- iface ng0 iface 00000002 inet ppp mpd36762-PPPoE ppp 00000003 inet Name: mpd36762-PPPoE-vjc Type: vjc ID: 00000004 Num hooks: 4 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- vjip mpd36762-PPPoE ppp 00000003 vjc_vjip vjuncomp mpd36762-PPPoE ppp 00000003 vjc_vjuncomp vjcomp mpd36762-PPPoE ppp 00000003 vjc_vjcomp ip mpd36762-PPPoE ppp 00000003 vjc_ip Name: mpd36762-PPPoE Type: ppp ID: 00000003 Num hooks: 6 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- ipv6 ng0 iface 00000002 inet6 inet mpd36762-PPPoE-bpf bpf 00000005 ppp vjc_vjip mpd36762-PPPoE-vjc vjc 00000004 vjip vjc_vjuncomp mpd36762-PPPoE-vjc vjc 00000004 vjuncomp vjc_vjcomp mpd36762-PPPoE-vjc vjc 00000004 vjcomp vjc_ip mpd36762-PPPoE-vjc vjc 00000004 ip Name: ng0 Type: iface ID: 00000002 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- inet6 mpd36762-PPPoE ppp 00000003 ipv6 inet mpd36762-PPPoE-bpf bpf 00000005 iface 'ifconfig ng0 destroy' won't. So then, now mpd will start, uselessly: paqi# /usr/local/etc/rc.d/mpd4.sh start Starting mpd4. paqi# ps auxww | grep "[m]pd" root 36794 0.0 1.5 4040 2268 ?? Is 11:31PM 0:00.02 /usr/local/sbin/mpd4 -p /var/run/mpd4.pid -b paqi# cat /var/run/mpd4.pid 36794 paqi# sockstat | grep mpd root mpd4 36794 3 dgram -> /var/run/logpriv root mpd4 36794 10 tcp4 127.0.0.1:5005 *:* Now I can telnet in ok, but it's 'no bundles defined' all the way. I can exit, or quit which stops mpd ok (but leaves ng0 as is), but this time my poking around also found that 'show iface' murdered it: Mar 3 23:31:44 paqi mpd: process 36794 started, version 4.1 (root@paqi.nimnet.asn.au 20:51 3-Mar-2007) Mar 3 23:31:44 paqi mpd: CONSOLE: listening on 127.0.0.1 5005 Mar 3 23:31:44 paqi mpd: [PPPoE] can't connect "bypass.inet"->"iface" and "ng0:"->"inet": File exists Mar 3 23:31:44 paqi mpd: [PPPoE] netgraph initialization failed Mar 3 23:31:44 paqi mpd: no bundles defined [obviously the problem, but why?] Mar 4 01:34:22 paqi mpd: last message repeated 14 times (14 more conf lines) Mar 4 01:34:22 paqi mpd: CONSOLE: Connect Mar 4 01:34:22 paqi mpd: CONSOLE: Allocated new console session 0x80d501c from 127.0.0.1 Mar 4 01:34:33 paqi mpd: [(null)] CONSOLE: smithi: log Mar 4 01:35:40 paqi mpd: [(null)] CONSOLE: smithi: log -ipv6cp Mar 4 01:35:45 paqi mpd: [(null)] CONSOLE: smithi: log Mar 4 01:35:54 paqi mpd: [(null)] CONSOLE: smithi: load PPPoE Mar 4 01:35:54 paqi mpd: [PPPoE] can't connect "bypass.inet"->"iface" and "ng0:"->"inet": File exists Mar 4 01:35:54 paqi mpd: [PPPoE] netgraph initialization failed Mar 4 01:35:54 paqi mpd: no bundles defined Mar 4 01:36:24 paqi mpd: last message repeated 14 times Mar 4 01:36:24 paqi mpd: [(null)] CONSOLE: smithi: sho Mar 4 01:36:40 paqi mpd: [(null)] CONSOLE: smithi: sho ipv6cp Mar 4 01:36:40 paqi mpd: no bundles defined Mar 4 01:36:49 paqi mpd: [(null)] CONSOLE: smithi: sho auth Mar 4 01:36:49 paqi mpd: no bundles defined Mar 4 01:36:57 paqi mpd: [(null)] CONSOLE: smithi: sho types Mar 4 01:37:18 paqi mpd: [(null)] CONSOLE: smithi: sho iface Mar 4 01:37:19 paqi mpd: caught fatal signal segv Mar 4 01:37:19 paqi mpd: fatal error, exiting Mar 4 01:37:19 paqi mpd: process 36794 terminated (no core) paqi# ngctl list There are 5 total nodes: Name: ngctl37232 Type: socket ID: 00000012 Num hooks: 0 Name: mpd36762-PPPoE-bpf Type: bpf ID: 00000005 Num hooks: 2 Name: mpd36762-PPPoE-vjc Type: vjc ID: 00000004 Num hooks: 4 Name: mpd36762-PPPoE Type: ppp ID: 00000003 Num hooks: 6 Name: ng0 Type: iface ID: 00000002 Num hooks: 2 mpd.conf less comments (yes, with no empty lines between) startup: set console port 5005 set console ip 127.0.0.1 set console user smithi xxxxx set console user root xxxxxxx set console open default: load PPPoE PPPoE: new -i ng0 PPPoE PPPoE set iface addrs 1.1.1.1 2.2.2.2 set iface route default set iface disable on-demand set iface idle 0 set bundle disable multilink set auth authname "number@provider" set auth password "yeahsure" set link no acfcomp protocomp set link disable pap chap set link accept chap set link mtu 1492 set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges w.x.y.z/0 w.x.0.0/16 open mpd.links likewise: PPPoE: set link type pppoe set pppoe iface xe0 set pppoe service "" set pppoe disable incoming set pppoe enable originate NETGRAPH is in kernel, modules are loaded: paqi# kldstat -v | egrep "net|ng_" 161 netgraph 163 dummynet 4 1 0xc227a000 4000 ng_socket.ko 239 ng_socket 5 1 0xc227e000 3000 ng_iface.ko 240 ng_iface 6 1 0xc2281000 6000 ng_ppp.ko 241 ng_ppp 7 1 0xc2287000 4000 ng_vjc.ko 242 ng_vjc 8 1 0xc2296000 4000 ng_bpf.ko 243 ng_bpf Hmmm, I'm sure I saw ng_pppoe.ko was there too on my attempts with rc2 before, though they had also all come up with exactly the same error: mpd: [PPPoE] can't connect "bypass.inet"->"iface" and "ng0:"->"inet": File exists mpd: [PPPoE] netgraph initialization failed One thing makes me a bit nervous: those ipv6 and inet6 hooks. kernel is compiled without INET6, new kernel/world built with make.conf having: NOINET6=true # do not build IPv6 related programs and libraries WITHOUT_IPV6=true Hope that's enough but not too much info. Cheers, Ian From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 17:53:21 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C754C16A400; Sat, 3 Mar 2007 17:53:21 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id 0557A13C48D; Sat, 3 Mar 2007 17:53:20 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l23HrIeU002210; Sat, 3 Mar 2007 18:53:19 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id ED6391550DA; Sat, 3 Mar 2007 18:53:17 +0100 (CET) Date: Sat, 3 Mar 2007 18:53:17 +0100 From: Alessandro de Manzano To: Paul Schmehl Message-ID: <20070303175317.GA89496@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> <0596BF936C9E2F724954C223@utd59514.utdallas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0596BF936C9E2F724954C223@utd59514.utdallas.edu> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs 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, 03 Mar 2007 17:53:21 -0000 On Fri, Mar 02, 2007 at 02:37:50PM -0600, Paul Schmehl wrote: > Shouldn't you be using the bce driver? This is an i386 machine, but amd64 > should work the same (you're using the same chipset): well, actually I have that driver in my kernel but it does not get attached (tried both i386 and x64 kernel) Looking for that card id it seems indeed a bge-supported card in -CURRENT (browswed the cvs commit archive for poweredge SC440), problem is if/when it will be supported in RELENG_6... Many thanks for your answer! -- bye! Ale ale@unixmania.net From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 17:59:12 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D017516A403; Sat, 3 Mar 2007 17:59:12 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id 55F2113C478; Sat, 3 Mar 2007 17:59:12 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l23HxBNt002661; Sat, 3 Mar 2007 18:59:11 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id A96341550CC; Sat, 3 Mar 2007 18:59:10 +0100 (CET) Date: Sat, 3 Mar 2007 18:59:10 +0100 From: Alessandro de Manzano To: Jung-uk Kim Message-ID: <20070303175910.GA89601@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> <200703021755.36600.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200703021755.36600.jkim@FreeBSD.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-net@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: two problems with broadcom NICs 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, 03 Mar 2007 17:59:12 -0000 On Fri, Mar 02, 2007 at 05:55:35PM -0500, Jung-uk Kim wrote: > > bge0@pci3:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 > > rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' > > device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > > class = network > > subclass = ethernet > > I am not sure about this controller (BTW, you had to include dmesg > output) but you may want to try -CURRENT. My verbose dmesg was in my original mail (not attached, just after my signature), I hope it is not been removed from some MUA :-) Unfortunately I need this machines in production and I must stay with 6.2(-stable if needed) I saw your commit on -CURRENT for BCM7574 on Dell SC440 (did you received my mail ? :) ) > > > none1@pci4:0:0: class=0x020000 card=0x01df1028 chip=0x167a14e4 > > rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' > > class = network > > subclass = ethernet > > This controller is not supported in 6.2-RELEASE. It should be > supported in -CURRENT. Do you plan/know if/when it will be backported to RELENG_6 ? (maybe for 6.3 ?) Thanks a lot! -- bye! Ale ale@unixmania.net From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 18:01:03 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9E8216A400; Sat, 3 Mar 2007 18:01:03 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id 29A6A13C481; Sat, 3 Mar 2007 18:01:02 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l23I12eI002857; Sat, 3 Mar 2007 19:01:02 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id E333B1550CC; Sat, 3 Mar 2007 19:01:00 +0100 (CET) Date: Sat, 3 Mar 2007 19:01:00 +0100 From: Alessandro de Manzano To: "Wojciech A. Koszek" Message-ID: <20070303180100.GB89601@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> <20070302113615.GA2766@FreeBSD.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070302113615.GA2766@FreeBSD.czest.pl> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs 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, 03 Mar 2007 18:01:03 -0000 On Fri, Mar 02, 2007 at 11:36:15AM +0000, Wojciech A. Koszek wrote: > > What could be ? What could I try ? Ideas ? > > You can check if changing the interface "UP" flag makes in any better: > > ifconfig up yep, this worked for use with my 2 switches. I today also tried with another switch and the NIC worked also without forcing it up.. :-| Maybe some weird in my previous cheap switches ? ;) Thanks! -- bye! Ale ale@unixmania.net From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 19:46:03 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C2FC16A402 for ; Sat, 3 Mar 2007 19:46:03 +0000 (UTC) (envelope-from wwdevil@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.freebsd.org (Postfix) with ESMTP id 2BF3113C441 for ; Sat, 3 Mar 2007 19:46:02 +0000 (UTC) (envelope-from wwdevil@gmail.com) Received: by wr-out-0506.google.com with SMTP id 55so1685738wri for ; Sat, 03 Mar 2007 11:46:02 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=fxHJR2ybZHXst4zqUOxNl637JcDxTNQNuj0pIk3THvok3iY93DuwZsmVmhtOGch1pBmFDUVd6ZICaTcNeFIX0cftd69rapkhMjA90YUm7UK5r7+ry4USFEBkavY8n0X9gEFyDtc6rk2RNXxXVwBiWePXJ34XPzZOdAuBeXkC5O8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=avMYLnkbrqiKfp31ANEMRBah3Xk72LMT49NxKW9uqHW7nauZ5TuJxaV1erEDnHzoHd4mS5UqKZ1VDtPIACNxYKYRLon9T+lnm68c3aK8pcKjuRlZYQTLEY7M3N7I2qobNRQ1TA6X1KXZ5mTmfHGDVYqqNTTD/ipanNEtpi0xksI= Received: by 10.115.33.1 with SMTP id l1mr718866waj.1172949582601; Sat, 03 Mar 2007 11:19:42 -0800 (PST) Received: by 10.114.53.14 with HTTP; Sat, 3 Mar 2007 11:19:42 -0800 (PST) Message-ID: <31ee4d090703031119i76bff153ke6ff8762945949ec@mail.gmail.com> Date: Sun, 4 Mar 2007 04:19:42 +0900 From: "wDevil wDevil" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: iwi, FreeBSD 6.1 Release on Acer Aspire 1640z. 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, 03 Mar 2007 19:46:03 -0000 Kernel device wlan device iwi device wlan_tkip device wlan_acl device wlan_ccmp device wlan_wep kldstat [root@]# kldstat Id Refs Address Size Name 1 15 0xc0400000 3c5288 kernel 2 1 0xc07c6000 7160 if_rl.ko 3 1 0xc07ce000 246c8 sound.ko 4 1 0xc07f8000 60f94 acpi.ko 5 1 0xc34d6000 2000 msdosfs_iconv.ko 6 1 0xc34d8000 3000 libiconv.ko 7 1 0xc3509000 e000 msdosfs.ko 8 1 0xc35f7000 18000 linux.ko /usr/ports/net/iwi-firmware (2.4_2) installed. [root@]# pkg_info -L iwi* Information for iwi-firmware-2.4_2: Files: /usr/share/man/man8/iwicontrol.8.gz //usr/sbin/iwicontrol /boot/firmware/LICENSE.iwi /boot/firmware/iwi-boot.fw /boot/firmware/iwi-bss.fw /boot/firmware/iwi-ucode-bss.fw /boot/firmware/iwi-ibss.fw /boot/firmware/iwi-ucode-ibss.fw /boot/firmware/iwi-sniffer.fw /boot/firmware/iwi-ucode-sniffer.fw //etc/rc.d/iwi rc.conf iwi_enable="YES" ifconfig_iwi0="WPA DHCP" /etc/wpa_supplicant.conf ctrl_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 network={ ssid="wDevil" key_mgmt=WPA-PSK proto=WPA pairwise=TKIP group=TKIP psk="zzzzz" } dmesg wlan: mac acl policy registered iwi0: mem 0xb0101000-0xb0101fff irq 17 at device 4.0 on pci6 iwi0: Ethernet address: 00:13:ce:e6:c2:d7 wpa_supplicant already running? (pid=211). DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 13 send_packet: Network is down DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 9 send_packet: Network is down iwi0: flags=8802 mtu 1500 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 ether 00:13:ce:e6:c2:d7 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 10 authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpowmax 100 protmode CTS roaming MANUAL iwicontrol iwi0 -r Radio is OFF sysctl -a |grep iwi net.wlan.0.%parent: iwi0 dev.iwi.0.%desc: Intel(R) PRO/Wireless 2200BG dev.iwi.0.%driver: iwi dev.iwi.0.%location: slot=4 function=0 dev.iwi.0.%pnpinfo: vendor=0x8086 device=0x4220 subvendor=0x8086 subdevice=0x2701 class=0x028000 dev.iwi.0.%parent: pci6 dev.iwi.0.radio: 0 dev.iwi.0.dwell: 100 dev.iwi.0.bluetooth: 1 dev.iwi.0.antenna: 0 The led on the computer is not on. [root@]# sysctl dev.iwi.0.radio=1 sysctl: oid 'dev.iwi.0.radio' is read only In http://damien.bergamini.free.fr/ipw/iwi-freebsd.html i found: "If your adapter radio transmitter is off (=0), use your laptop switch to turn it on and re-run the above command to see if it has some effect. If your radio transmitter is still off, it is likely that your laptop uses a software switch that requires additionnal drivers to work. Unfortunately, not all those laptops are supported at this time. " Don't work. [root@]# sysctl net.wlan.debug=-1 [root@]# sysctl net.wlan.0.debug=-1 [root@]# /etc/rc.d/wpa_supplicant stop iwi0 Stopping wpa_supplicant. Waiting for PIDS: 211^[[A. [root@]# /etc/rc.d/wpa_supplicant start iwi0 Starting wpa_supplicant. /var/log/messages kernel: iwi0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 last message repeated 3 times kernel: iwi0: ieee80211_node_table_reset scan table kernel: iwi0: ieee80211_free_allnodes_locked: free all nodes in scan table [root@]# wpa_supplicant -i iwi0 -c/etc/wpa_supplicant.conf -d Initializing interface 'iwi0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 Priority group 0 id=0 ssid='wDevil' Initializing interface (2) 'iwi0' EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Own MAC address: 00:13:ce:e6:c2:d7 wpa_driver_bsd_set_wpa: enabled=1 wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_set_countermeasures: enabled=0 wpa_driver_bsd_set_drop_unencrypted: enabled=1 Setting scan request: 0 sec 100000 usec Added interface iwi0 State: DISCONNECTED -> SCANNING Starting AP scan (broadcast SSID) ^CCTRL-EVENT-TERMINATING - signal 2 received Removing interface iwi0 State: SCANNING -> DISCONNECTED No keys have been configured - skip key clearing EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 wpa_driver_bsd_set_wpa: enabled=0 wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 wpa_driver_bsd_set_drop_unencrypted: enabled=0 wpa_driver_bsd_set_countermeasures: enabled=0 No keys have been configured - skip key clearing wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 Cancelling scan request After "Starting AP scan (broadcast SSID)" nothing... ctrl+c. Ideas? From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 19:56:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E96516A400; Sat, 3 Mar 2007 19:56:53 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id 88AC513C461; Sat, 3 Mar 2007 19:56:52 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l23KQX2P014165; Sat, 3 Mar 2007 20:26:34 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l23KQWLY014164; Sat, 3 Mar 2007 20:26:32 GMT (envelope-from dunstan) Date: Sat, 3 Mar 2007 20:26:30 +0000 From: "Wojciech A. Koszek" To: Alessandro de Manzano Message-ID: <20070303202630.GA14147@FreeBSD.czest.pl> References: <20070302084747.GA80114@libero.sunshine.ale> <0596BF936C9E2F724954C223@utd59514.utdallas.edu> <20070303175317.GA89496@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070303175317.GA89496@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Sat, 03 Mar 2007 20:26:34 +0000 (UTC) Cc: Paul Schmehl , freebsd-amd64@freebsd.org, freebsd-net@freebsd.org Subject: Re: two problems with broadcom NICs 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, 03 Mar 2007 19:56:53 -0000 On Sat, Mar 03, 2007 at 06:53:17PM +0100, Alessandro de Manzano wrote: > On Fri, Mar 02, 2007 at 02:37:50PM -0600, Paul Schmehl wrote: > > > Shouldn't you be using the bce driver? This is an i386 machine, but amd64 > > should work the same (you're using the same chipset): > > well, actually I have that driver in my kernel but it does not get > attached (tried both i386 and x64 kernel) > > Looking for that card id it seems indeed a bge-supported card in > -CURRENT (browswed the cvs commit archive for poweredge SC440), problem > is if/when it will be supported in RELENG_6... > > Many thanks for your answer! You might want to generate a patch for RELENG_6 for yourself, if it's a matter of quirk with proper ID. This should only apply if probe method doesn't return true in your case, and none other changes were made to support your specific device. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 20:06:48 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF00516A402; Sat, 3 Mar 2007 20:06:48 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6888013C48E; Sat, 3 Mar 2007 20:06:48 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l23KaXfw014203; Sat, 3 Mar 2007 20:36:33 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l23KaWKe014202; Sat, 3 Mar 2007 20:36:32 GMT (envelope-from dunstan) Date: Sat, 3 Mar 2007 20:36:32 +0000 From: "Wojciech A. Koszek" To: Alessandro de Manzano Message-ID: <20070303203631.GB14147@FreeBSD.czest.pl> References: <20070302084747.GA80114@libero.sunshine.ale> <20070302113615.GA2766@FreeBSD.czest.pl> <20070303180100.GB89601@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070303180100.GB89601@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Sat, 03 Mar 2007 20:36:33 +0000 (UTC) Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs 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, 03 Mar 2007 20:06:49 -0000 On Sat, Mar 03, 2007 at 07:01:00PM +0100, Alessandro de Manzano wrote: > On Fri, Mar 02, 2007 at 11:36:15AM +0000, Wojciech A. Koszek wrote: > > > > What could be ? What could I try ? Ideas ? > > > > You can check if changing the interface "UP" flag makes in any better: > > > > ifconfig up > > yep, this worked for use with my 2 switches. > I today also tried with another switch and the NIC worked also without > forcing it up.. :-| > Maybe some weird in my previous cheap switches ? ;) Unfortunately for FreeBSD, it's not a problem with your switches -- it's rather driver's fault, since I've seen such issue before. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 21:12:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 589A816A400 for ; Sat, 3 Mar 2007 21:12:38 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id D73AA13C4A7 for ; Sat, 3 Mar 2007 21:12:37 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [195.248.178.122] (account mav@alkar.net HELO [192.168.3.2]) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 21372512; Sat, 03 Mar 2007 23:12:33 +0200 Message-ID: <45E9E4BF.4040403@alkar.net> Date: Sat, 03 Mar 2007 23:12:31 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Smith References: <1172953385.00698247.1172941201@10.7.7.3> In-Reply-To: <1172953385.00698247.1172941201@10.7.7.3> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: mpd 4.1 on 5.5-STABLE 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, 03 Mar 2007 21:12:38 -0000 Hi. Ian Smith wrote: > When started the first time, before there's any ng0 interface, mpd logs > the following two lines then immediately exits without further ado: > > paqi# /usr/local/etc/rc.d/mpd4.sh start Try to run mpd from console just by typing "mpd4" to get all logs to console. To get more logs you can add to the begining of mpd.conf command "log +all". > 'ifconfig ng0 destroy' won't. So then, now mpd will start, uselessly: ngX interfaces can be shutted down only from inside of netgraph by "ngctl shutdown ngX:" command. > new -i ng0 PPPoE PPPoE -i parameter is not recommended for use. If you remove it, mpd will just use first free ngX interface. > One thing makes me a bit nervous: those ipv6 and inet6 hooks. kernel is > compiled without INET6, new kernel/world built with make.conf having: > NOINET6=true # do not build IPv6 related programs and libraries > WITHOUT_IPV6=true I don't think that this should be a problem. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 21:34:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 42A4916A502 for ; Sat, 3 Mar 2007 21:34:11 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 83FE813C442 for ; Sat, 3 Mar 2007 21:34:10 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l23LY7Dc043293; Sun, 4 Mar 2007 00:34:07 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l23LY6nP043292; Sun, 4 Mar 2007 00:34:06 +0300 (MSK) (envelope-from yar) Date: Sun, 4 Mar 2007 00:34:06 +0300 From: Yar Tikhiy To: Bruce M Simpson Message-ID: <20070303213406.GA40430@comp.chem.msu.su> References: <45E8BB39.9030602@incunabulum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E8BB39.9030602@incunabulum.net> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org Subject: Re: CARP behaviour 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, 03 Mar 2007 21:34:11 -0000 On Sat, Mar 03, 2007 at 12:03:05AM +0000, Bruce M Simpson wrote: > During testing of M_PROMISC I noticed a couple of issues with our CARP. > > 1. carp doesn't seem to maintain input/output statistics on its ifnet. This should be OK. A carp(4) interface is just a place for CARP settings to live. No real traffic passes through it. > 2. carp doesn't seem to detect that the underlying route to the subnet > its address is exposed on changed to another interface. I seem to recollect that I ran into this issue, too. Of course, it's a bug. CARP apparently caches the old route forever. It should track such a change if it doesn't yet. We have a sort of notification for the event, don't we? The userland has the routing socket for that, but I don't remember about the kernel. Thank you for paying attention to that! -- Yar From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 21:54:02 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A6E116A407 for ; Sat, 3 Mar 2007 21:54:02 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 03C3313C442 for ; Sat, 3 Mar 2007 21:54:01 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l23Ls0Im043452; Sun, 4 Mar 2007 00:54:00 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l23Lrx9r043451; Sun, 4 Mar 2007 00:54:00 +0300 (MSK) (envelope-from yar) Date: Sun, 4 Mar 2007 00:53:59 +0300 From: Yar Tikhiy To: Bruce M Simpson Message-ID: <20070303215359.GB40430@comp.chem.msu.su> References: <45E8B964.2090200@incunabulum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E8B964.2090200@incunabulum.net> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Ethernet cleanup; 802.1p input and M_PROMISC 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, 03 Mar 2007 21:54:02 -0000 On Fri, Mar 02, 2007 at 11:55:16PM +0000, Bruce M Simpson wrote: > Hello all, > > I would like to announce an updated version of the 802.1p input patch, > available at: > http://people.freebsd.org/~bms/dump/latest-8021p.diff > > I have cut down the original scope of the patch. I previously ran into > problems when I tried to move VLAN tag input and output processing into > if_ethersubr.c. > > FreeBSD should now accept VLAN 0 traffic on input with this patch. In > addition to this, the M_PROMISC flag is now used, which considerably > simplifies the Ethernet input path in general. [...] Sorry, I don't have an opportunity to test your patch, but it looks good to me. It seems to remove some cruft from the code, which is a good sign! I've got only one question about this piece: @@ -504,6 +507,10 @@ struct ether_header *eh; u_short etype; + if ((ifp->if_flags & IFF_UP) == 0) { + m_freem(m); + return; + } In fact, there two independent flags indicating interface's readiness: IFF_UP and IFF_DRV_RUNNING. The former is controlled by the admin and the latter, by the driver. E.g., an interface can be UP but not really ready to operate due to h/w reasons, or vice versa. Perhaps we should check both flags to see if the interface is, so to say, up and running. if_vlan.c has an obvious macro for that, and it can go to if_var.h to avoid code duplication if we decide it's the right way to take. -- Yar From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 22:30:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A4E816A401; Sat, 3 Mar 2007 22:30:53 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4A44613C478; Sat, 3 Mar 2007 22:30:53 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 9EAAA46CE9; Sat, 3 Mar 2007 17:30:52 -0500 (EST) Date: Sat, 3 Mar 2007 22:30:52 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andre Oppermann In-Reply-To: <45E8276D.60105@freebsd.org> Message-ID: <20070303222356.S60688@fledge.watson.org> References: <45E8276D.60105@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, gallatin@freebsd.org, freebsd-current@freebsd.org, kmacy@freebsd.org Subject: Re: New optimized soreceive_stream() for TCP sockets, proof of concept 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, 03 Mar 2007 22:30:53 -0000 On Fri, 2 Mar 2007, Andre Oppermann wrote: > Instead of the unlock-lock dance soreceive_stream() pulls a properly sized > (relative to the receive system call buffer space) from the socket buffer > drops the lock and gives copyout as much time as it needs. In the mean time > the lower half can happily add as many new packets as it wants without > having to wait for a lock. It also allows the upper and lower halfs to run > on different CPUs without much interference. There is a unsolved nasty race > condition in the patch though. When the socket closes and we still have data > around or the copyout failed it tries to put the data back into the socket > buffer which is gone already by then leading to a panic. Work is underway > to find a realiable fix for this. I wanted to get this out to the community > nonetheless to give it some more exposure. I'll try to take a look at this in the next few days. However, I find the description above of soreceive() a bit odd -- I'm pretty sure it doesn't do some of the things you're describing. For example, soreceive() does release the locks acquired by the network input processing path while copying to user space: there should be no contention during the copyout(), only while processing the socket buffer between copyout() calls. This is possible because the socket receive sleep lock (not the mutex) holds sb_mb constant if it is non-NULL, making copyout() of sb_mb->m_data safe while not holding the socket buffer mutex in the current implementation. In my experience, soreceive() is an incredibly complicated function, and could stand significant simplification. However, it has to be done very carefully for exactly this reason :-). There are some existing bugs in soreceive(), one involving incorrect handling of interlaced I/O due to a label being in the wrong place, that we should resolve. BTW, the point of not pulling the data out of the socket buffer until copyout() is complete is not error handling reversion so much as not changing the advertised window size until the copy is done, since the data isn't delivered to user space. Copyout() can take a very long time to run, due to page faults, for example, and the socket buffer represents a maximum bound on in-flight traffic as specified by the application. Whether this is a property we want to keep is another question, but I believe that's the rationale. Robert N M Watson Computer Laboratory University of Cambridge > > The patch is here: > > http://people.freebsd.org/~andre/soreceive_stream-20070302.diff > > Any testing, especially on 10Gig cards, and feedback appreciated. > > -- > Andre > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 22:44:06 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BDC2D16A401 for ; Sat, 3 Mar 2007 22:44:06 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 3622113C491 for ; Sat, 3 Mar 2007 22:44:06 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 2593 invoked from network); 3 Mar 2007 22:16:24 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 3 Mar 2007 22:16:24 -0000 Message-ID: <45E9FA3C.5030404@freebsd.org> Date: Sat, 03 Mar 2007 23:44:12 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Yar Tikhiy References: <45E8BB39.9030602@incunabulum.net> <20070303213406.GA40430@comp.chem.msu.su> In-Reply-To: <20070303213406.GA40430@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Bruce M Simpson Subject: Re: CARP behaviour 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, 03 Mar 2007 22:44:06 -0000 Yar Tikhiy wrote: > On Sat, Mar 03, 2007 at 12:03:05AM +0000, Bruce M Simpson wrote: >> During testing of M_PROMISC I noticed a couple of issues with our CARP. >> >> 1. carp doesn't seem to maintain input/output statistics on its ifnet. > > This should be OK. A carp(4) interface is just a place for CARP > settings to live. No real traffic passes through it. > >> 2. carp doesn't seem to detect that the underlying route to the subnet >> its address is exposed on changed to another interface. > > I seem to recollect that I ran into this issue, too. Of course, > it's a bug. CARP apparently caches the old route forever. It > should track such a change if it doesn't yet. We have a sort of > notification for the event, don't we? The userland has the routing > socket for that, but I don't remember about the kernel. We shouldn't cache route pointers anywhere anymore. It has been completely removed from the PCBs and things like gif and others. > Thank you for paying attention to that! -- Andre From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 22:55:50 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F41016A400 for ; Sat, 3 Mar 2007 22:55:50 +0000 (UTC) (envelope-from kimimeister@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id D41C913C4A5 for ; Sat, 3 Mar 2007 22:55:49 +0000 (UTC) (envelope-from kimimeister@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1068124wxc for ; Sat, 03 Mar 2007 14:55:49 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=KInfDP9jk/6VYUSefO3wcHqn81cWpBMXQRfc9dv6VE8PP3wCLXClj8R+hHEvfxzu7kPaShuXdWp88QA1DlYFWrvOTLAfuhDis99ecx3DEf0XIilho98keotB6Qx2CaNP4m6+gFXGMYVzLINwZ5cN99hnOQ8D2YtmUu84K9yf8lo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=en1sChZoCSkPNX3Bq+6vOfB/b2JVpIakkTPvwofOTuw0OGxltVA6c1kpsZ8ka2RoV6XRT2KQ9+YYS1CmrKAV5di28gVBZuR70npRfyT5ui/zEuWU2sujNIfct0CDuinbSVNRPu6Bl2f2ITbiVdkXt5qpVCi/JIXANomU8jI5G7o= Received: by 10.115.108.1 with SMTP id k1mr750561wam.1172960801226; Sat, 03 Mar 2007 14:26:41 -0800 (PST) Received: by 10.114.195.9 with HTTP; Sat, 3 Mar 2007 14:26:41 -0800 (PST) Message-ID: <42b497160703031426y259f0c4bl8620c804c1c84c05@mail.gmail.com> Date: Sat, 3 Mar 2007 22:26:41 +0000 From: "Kimi Ostro" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: kimimeister@gmail.com Subject: wifi locking up system 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, 03 Mar 2007 22:55:50 -0000 Hi list, I have been using a FreeBSD based wifi network for about 5 months now, reading the handbook made this a breeze. Introducing wifi to one of my boxes that would have uptimes of months now causes lock-ups of some sort, the machine just completely dies atleast to any networking access and I haven't seen any panicks yet which doesn't really help, power-cycling is the only resolution. Diagram: [freebsd] | [if_fxp]--[if_bridge]--[if_ral] if_ral is in HostAp mode. I also get the same kind of symptomns on my laptop, also with an if_ral, both are manufactured by MSI: MSI CB54G2 and MSI PC54G2. Heavy networking like file transfering, lots of SSH sessions (5/6) and general web browsing cause this to happen a lot, yet if I just do web browsing there will be no lock-up for weeks on end, yet as soon as I start doing heavy networking again it will lock up all with in 10 minutes. I've even tried using just 11b or 54g modes. Please CC me. -- Kimi From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 22:59:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4FA0316A401 for ; Sat, 3 Mar 2007 22:59:18 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.234]) by mx1.freebsd.org (Postfix) with ESMTP id F0E7D13C481 for ; Sat, 3 Mar 2007 22:59:17 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1068734wxc for ; Sat, 03 Mar 2007 14:59:17 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sMHbLLCzlhEyTu2vfoCumZCWyJOXiDPbhAtl4qCn4w/J3ubD3v9kNxBp/ekkqQF5EYetazmQbXKLhww6JJn2ITtSS09RGtifK8sXwkqohqh1rOovM236yexDpozsTnvGl58A90RZm+1VEFA8Ctkl9j2w+ZTdigjGd2vPdED7AxQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AyHEp9e+XIS/BHYf+WoW7uA2jJLiQfo5FnjiUNMWEFVKdDt3PmCqFdnkGSVjr1WSaqoWMc8tYrAfFZKa/J5YHlcKFwZXRAh6wlc2DcwX21Lc3qbXcPbTE6LxbMMmtlR8rcQP7cSyr9jTUobuU69czzyuWuixH8I2z423HLq4+0A= Received: by 10.90.69.8 with SMTP id r8mr3888974aga.1172962757483; Sat, 03 Mar 2007 14:59:17 -0800 (PST) Received: by 10.90.25.1 with HTTP; Sat, 3 Mar 2007 14:59:17 -0800 (PST) Message-ID: Date: Sat, 3 Mar 2007 14:59:17 -0800 From: "Kip Macy" To: "Kimi Ostro" In-Reply-To: <42b497160703031426y259f0c4bl8620c804c1c84c05@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <42b497160703031426y259f0c4bl8620c804c1c84c05@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: wifi locking up system 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, 03 Mar 2007 22:59:18 -0000 ral has locking bugs on 6.x. I was under the impression that it is barely used from how quickly I hit them. -Kip On 3/3/07, Kimi Ostro wrote: > Hi list, > > I have been using a FreeBSD based wifi network for about 5 months now, > reading the handbook made this a breeze. > > Introducing wifi to one of my boxes that would have uptimes of months > now causes lock-ups of some sort, the machine just completely dies > atleast to any networking access and I haven't seen any panicks yet > which doesn't really help, power-cycling is the only resolution. > > Diagram: > > [freebsd] > | > [if_fxp]--[if_bridge]--[if_ral] > > if_ral is in HostAp mode. > > I also get the same kind of symptomns on my laptop, also with an > if_ral, both are manufactured by MSI: MSI CB54G2 and MSI PC54G2. > > Heavy networking like file transfering, lots of SSH sessions (5/6) and > general web browsing cause this to happen a lot, yet if I just do web > browsing there will be no lock-up for weeks on end, yet as soon as I > start doing heavy networking again it will lock up all with in 10 > minutes. > > I've even tried using just 11b or 54g modes. > > Please CC me. > > -- > Kimi > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 23:06:28 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C2FD16A404 for ; Sat, 3 Mar 2007 23:06:28 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id 5BB2113C4A7 for ; Sat, 3 Mar 2007 23:06:28 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1069911wxc for ; Sat, 03 Mar 2007 15:06:27 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ieSQwP5Dz89p22rS9GxoQXVdUzmApD+X42fPqm0eKvPY8gMEI8CKmNFDamcy2CzEecRA3sg4z+8XnoKVJr6FvCSI46wME1+buV79vRBqxtuzwjBVKYlus7fUZeRxzPpT0H3NbcilHlHP8Z/S1aNzgrhQe2rN2yrngCETV2lu/D4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ORb4wcGqwZbNdH9Nu8Oz2xAKKCZMkcJo2n4MpJpTGYKgSAucRpq/YKykLVg1ehKReP2StPn6BlEc5uvc9wusUFqjs85kmJHPpvO4SgfeCLNVmao58VKWBZ9TjoLpa3S6LtATAQIRZLSJfJjesiUFQkRwY4d+eRwf8xNB4tiLrvY= Received: by 10.90.81.14 with SMTP id e14mr3877864agb.1172963187675; Sat, 03 Mar 2007 15:06:27 -0800 (PST) Received: by 10.90.25.1 with HTTP; Sat, 3 Mar 2007 15:06:27 -0800 (PST) Message-ID: Date: Sat, 3 Mar 2007 15:06:27 -0800 From: "Kip Macy" To: "Kimi Ostro" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <42b497160703031426y259f0c4bl8620c804c1c84c05@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: wifi locking up system 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, 03 Mar 2007 23:06:28 -0000 On 3/3/07, Kip Macy wrote: > ral has locking bugs on 6.x. I was under the impression that it is > barely used from how quickly I hit them. On a sidenote - my laptop runing 6.1 has a tendency to overheat. I'm installing RELENG_6 on a desktop for different reasons. Can someone point me to something to hook up a cardbus card to a PC? (I might be able to check in a fix if I can test it). -Kip From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 23:13:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F54D16A404 for ; Sat, 3 Mar 2007 23:13:00 +0000 (UTC) (envelope-from kimimeister@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id C123013C474 for ; Sat, 3 Mar 2007 23:12:59 +0000 (UTC) (envelope-from kimimeister@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1071045wxc for ; Sat, 03 Mar 2007 15:12:59 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BhUuqxXXfaqXQOmCT6VSxHvdvSAiHId1qkOfHCBGshTiTxbFdf1/kEejO4YpQZ64P0MTrVRySt47JJN99m/ELO7dzxiF7aD1BQ+aqEjbqVs9yqnyUquQAMqgZJjznGcLdrqQL8p3soC2IK/3VhsUBZf7Eun46xz6cFSZGjxKSeI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hM1HGJLnliAg2YCrl/q5pfqZ3b22ngw+kgBdNij+gSQM9YnS+e+uLR8PNvFjCkwNsWtgDYj/0GXKhP4XScNUay7So4pXM/Ow9oKhJpLCF0vKc6j1yoxfs/uzrrvQNLEyJEJKhs/ih2T1iiKSVoPAqZpi01ehDndk5bRFHWUNGHY= Received: by 10.115.111.1 with SMTP id o1mr751511wam.1172963578217; Sat, 03 Mar 2007 15:12:58 -0800 (PST) Received: by 10.114.195.9 with HTTP; Sat, 3 Mar 2007 15:12:58 -0800 (PST) Message-ID: <42b497160703031512n6e94e5far9ab139de4ca04df5@mail.gmail.com> Date: Sat, 3 Mar 2007 23:12:58 +0000 From: "Kimi Ostro" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <42b497160703031426y259f0c4bl8620c804c1c84c05@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: wifi locking up system 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, 03 Mar 2007 23:13:00 -0000 On 03/03/07, Kip Macy wrote: > ral has locking bugs on 6.x. I was under the impression that it is > barely used from how quickly I hit them. > > -Kip > is this just a case of "grin & bare it"? unless there is something I can do, testing wise which I am more then happy to do? the system's are both UP, if that helps. thanks for the fast reply. -- Kimi From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 23:20:04 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C14916A407 for ; Sat, 3 Mar 2007 23:20:04 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id B946013C4B7 for ; Sat, 3 Mar 2007 23:20:03 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 2824 invoked from network); 3 Mar 2007 22:52:21 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 3 Mar 2007 22:52:21 -0000 Message-ID: <45EA02AA.8030800@freebsd.org> Date: Sun, 04 Mar 2007 00:20:10 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Watson References: <45E8276D.60105@freebsd.org> <20070303222356.S60688@fledge.watson.org> In-Reply-To: <20070303222356.S60688@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, gallatin@freebsd.org, freebsd-current@freebsd.org, kmacy@freebsd.org Subject: Re: New optimized soreceive_stream() for TCP sockets, proof of concept 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, 03 Mar 2007 23:20:04 -0000 Robert Watson wrote: > > On Fri, 2 Mar 2007, Andre Oppermann wrote: > >> Instead of the unlock-lock dance soreceive_stream() pulls a properly >> sized (relative to the receive system call buffer space) from the >> socket buffer drops the lock and gives copyout as much time as it >> needs. In the mean time the lower half can happily add as many new >> packets as it wants without having to wait for a lock. It also allows >> the upper and lower halfs to run on different CPUs without much >> interference. There is a unsolved nasty race condition in the patch >> though. When the socket closes and we still have data around or the >> copyout failed it tries to put the data back into the socket buffer >> which is gone already by then leading to a panic. Work is underway to >> find a realiable fix for this. I wanted to get this out to the >> community nonetheless to give it some more exposure. > > I'll try to take a look at this in the next few days. > > However, I find the description above of soreceive() a bit odd -- I'm > pretty sure it doesn't do some of the things you're describing. For > example, soreceive() does release the locks acquired by the network > input processing path while copying to user space: there should be no > contention during the copyout(), only while processing the socket buffer > between copyout() calls. This is possible because the socket receive > sleep lock (not the mutex) holds sb_mb constant if it is non-NULL, > making copyout() of sb_mb->m_data safe while not holding the socket > buffer mutex in the current implementation. The copyout is done without holding the lock. However for every mbuf in the socket buffer it unlocks, does the copyout and then locks it again for the next. I was referring to that unlock-lock pair for every mbuf. > In my experience, soreceive() is an incredibly complicated function, and > could stand significant simplification. However, it has to be done very > carefully for exactly this reason :-). There are some existing bugs in > soreceive(), one involving incorrect handling of interlaced I/O due to a > label being in the wrong place, that we should resolve. It's damn complex. That's one of the reasons I started the soreceive_stream() function and related stuff. To try to understand it and to document all the evil edge cases right. I'm pretty sure I've not accounted for some yet. > BTW, the point of not pulling the data out of the socket buffer until > copyout() is complete is not error handling reversion so much as not > changing the advertised window size until the copy is done, since the > data isn't delivered to user space. Copyout() can take a very long time > to run, due to page faults, for example, and the socket buffer > represents a maximum bound on in-flight traffic as specified by the > application. Whether this is a property we want to keep is another > question, but I believe that's the rationale. Haven't thought of that rationale yet. So far it appeared to me that it was done for sanity reasons and there wasn't really a need in the spl() days to do it otherwise. I'll think some more about it and whether it is good, bad or doesn't matter. Mind you this patch is just a pretty advanced proof of concept thing. Certainly not something to kick into the tree by tomorrow or the day after. -- Andre From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 23:22:09 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8538616A404 for ; Sat, 3 Mar 2007 23:22:09 +0000 (UTC) (envelope-from kimimeister@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228]) by mx1.freebsd.org (Postfix) with ESMTP id 4395A13C46B for ; Sat, 3 Mar 2007 23:22:09 +0000 (UTC) (envelope-from kimimeister@gmail.com) Received: by wr-out-0506.google.com with SMTP id 55so1736724wri for ; Sat, 03 Mar 2007 15:22:08 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bQTouz3V05IHwHCg1BqNkH4g/3Qes4lL/7V2/l2SDxDw8jm08BW85G+rRqI5NaRN1HID8cVbCzC25rakQDbd7XOcFYAzXPE7X0Ga42ufKTSKNfGBlpL3tTsLe90HUUx3hu/1/LcExp5rOXRHI4d+0I0xqAZSyLW8n436nTtmQTA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QlQydAOjJ+p4045iPQSK7XIDGZXte/ia0ja8Iy5Z2YUznZ3NaFMnPZNhFi2x/USiAzNczeCsSCn0QwYoHjzzFPVv8gQ7KmEyCiIpPpcUM+KdHQJbr3t63vY2fZNejMur6zaK6dF7pdR8gxjMyja3pMP11hh0LFGwkxvHMw72Lwk= Received: by 10.114.157.1 with SMTP id f1mr785586wae.1172964128269; Sat, 03 Mar 2007 15:22:08 -0800 (PST) Received: by 10.114.195.9 with HTTP; Sat, 3 Mar 2007 15:22:08 -0800 (PST) Message-ID: <42b497160703031522t1015a3ccheea65dd801ab54c3@mail.gmail.com> Date: Sat, 3 Mar 2007 23:22:08 +0000 From: "Kimi Ostro" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <42b497160703031426y259f0c4bl8620c804c1c84c05@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: wifi locking up system 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, 03 Mar 2007 23:22:09 -0000 On 03/03/07, Kip Macy wrote: > > On a sidenote - my laptop runing 6.1 has a tendency to overheat. I'm > installing RELENG_6 on a desktop for different reasons. Can someone > point me to something to hook up a cardbus card to a PC? (I might be > able to check in a fix if I can test it). > > -Kip > http://www.amazon.com/StarTech-com-CardBus-PCMCIA-Adapter-Card/dp/B00068YUPM -- Kimi From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 23:40:09 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81C6016A403 for ; Sat, 3 Mar 2007 23:40:09 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 5AA7413C471 for ; Sat, 3 Mar 2007 23:40:09 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 2D95F1F4246; Sat, 3 Mar 2007 18:40:09 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Sat, 03 Mar 2007 18:40:09 -0500 X-Sasl-enc: 960qFYlYnpOtgTHW4x87idybWh7Kn2IAFqS442MV9f6F 1172965209 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 7DAD82AE19; Sat, 3 Mar 2007 18:40:08 -0500 (EST) Message-ID: <45EA0756.2000107@incunabulum.net> Date: Sat, 03 Mar 2007 23:40:06 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Yar Tikhiy References: <45E8B964.2090200@incunabulum.net> <20070303215359.GB40430@comp.chem.msu.su> In-Reply-To: <20070303215359.GB40430@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Ethernet cleanup; 802.1p input and M_PROMISC 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, 03 Mar 2007 23:40:09 -0000 Yar Tikhiy wrote: > > In fact, there two independent flags indicating interface's readiness: > IFF_UP and IFF_DRV_RUNNING. The former is controlled by the admin > and the latter, by the driver. E.g., an interface can be UP but > not really ready to operate due to h/w reasons, or vice versa. > Perhaps we should check both flags to see if the interface is, so > to say, up and running. if_vlan.c has an obvious macro for that, > and it can go to if_var.h to avoid code duplication if we decide it's > the right way to take. > Thanks for looking at this. The purpose of the IFF_UP check is to immediately drop frames destined for an interface which is administratively configured down. Surely if ether_input() is called from the driver, there should be no need to check IFF_DRV_RUNNING? Indeed if the hardware flips to a state where it is not running but its internal queues or descriptor rings are draining, this might cause frames to be lost? Regards, BMS