From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 05:01:09 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2836710656CA for ; Sun, 8 Jun 2008 05:01:09 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id 14E4A8FC1C for ; Sun, 8 Jun 2008 05:01:09 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-179-28.hsd1.fl.comcast.net ([76.108.179.28] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1K5D08-0001cs-Sv for freebsd-net@freebsd.org; Sun, 08 Jun 2008 00:59:32 -0400 Message-ID: <484B6807.1000007@gtcomm.net> Date: Sun, 08 Jun 2008 01:03:03 -0400 From: Paul User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: using ipfw forward with gre tunnel crashes machine (BUG) 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, 08 Jun 2008 05:01:09 -0000 Hoping maybe one of you can test this as I didn't have time to look into it, but I tried twice. Setting up gre interface and then using IPFW Gre interface 1.1.1.1 -- 1.1.1.2 ipfw fwd 1.1.1.2 ip from any to any recv lagg2 Command works no problem. The instant any traffic at all is sent incoming on lagg2 machine crashes (reboots), nothing in log. Thanks :) From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 05:02:30 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E19CC1065672 for ; Sun, 8 Jun 2008 05:02:30 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id CCDA88FC12 for ; Sun, 8 Jun 2008 05:02:30 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-179-28.hsd1.fl.comcast.net ([76.108.179.28] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1K5D1S-0001ml-VB for freebsd-net@freebsd.org; Sun, 08 Jun 2008 01:00:55 -0400 Message-ID: <484B6859.6070500@gtcomm.net> Date: Sun, 08 Jun 2008 01:04:25 -0400 From: Paul User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: FreeBSD Net References: <484B6807.1000007@gtcomm.net> In-Reply-To: <484B6807.1000007@gtcomm.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: using ipfw forward with gre tunnel crashes machine (BUG) 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, 08 Jun 2008 05:02:31 -0000 Grr.. forgot.. 7.0-STABLE FreeBSD 7.0-STABLE #5: Sun May 11 19:00:57 EDT 2008 amd64 Paul wrote: > Hoping maybe one of you can test this as I didn't have time to look > into it, but I tried twice. > > Setting up gre interface and then using IPFW > > Gre interface 1.1.1.1 -- 1.1.1.2 > ipfw fwd 1.1.1.2 ip from any to any recv lagg2 > > Command works no problem. The instant any traffic at all is sent > incoming on lagg2 machine crashes (reboots), nothing in log. > > > Thanks :) > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 06:42:39 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E2561065672 for ; Sun, 8 Jun 2008 06:42:39 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4ADCC8FC1C for ; Sun, 8 Jun 2008 06:42:38 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1232471wah.3 for ; Sat, 07 Jun 2008 23:42:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tXn+ntzlG9Yrzl6sNTiHzmab0YgSyHoTH//skBEXqwM=; b=SgLdRtpq5pHDlWQxP6to+n0phudwo1iPG6qjj3dYlclBVaD2ftipDYbt4pS/PATiRi qv2u6fWk/J/7ZNz5Acd+8JY/bChbhAFrOorv9Z7lPTi5SkdpqocbS6IwHEBv7Z+4XDip RDR6wnm/J8iqAc8sblVF+WHsZoKjM13YaNUG0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=kYOLFLl2Wgz+y/7a5Im6RDhp0NniwA5H8yTUi94iUxkkb/4P0qSHrtB8pDKXJJNUml DH8946g996z/1pYpIqWb48kVeN+WD6O9OS1L8i4DfctmVvYVzDteFDyhshJikzK8tEVH rZmzV5iCi6EycPUxYaPyNRx3Wv+EMxJcStRrk= Received: by 10.114.89.1 with SMTP id m1mr1992095wab.146.1212907358380; Sat, 07 Jun 2008 23:42:38 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Sat, 7 Jun 2008 23:42:38 -0700 (PDT) Message-ID: <2a41acea0806072342q518ac2afo663c91e730c16db@mail.gmail.com> Date: Sat, 7 Jun 2008 23:42:38 -0700 From: "Jack Vogel" To: "Daniel Ponticello" In-Reply-To: <484AFEF1.4040500@skytek.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484AFEF1.4040500@skytek.it> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 06:42:39 -0000 On Sat, Jun 7, 2008 at 2:34 PM, Daniel Ponticello wrote: > Hello, > i'm experiencing periodic kernel panics on a server with FreeBSD 7.0-STABLE > #0: Tue May 20 19:09:43 CEST 2008. > My big problem is that the system is not performing memory dumping and/or > automatic reoboot, > it just stays there. > > Here' console output: > > em0: watchdog timeout -- resetting > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic_id = 00 > fault virtual address = 0x14 > fault code = supervisor read, page not present > intruction pointerr = 0x20:0xc056e2ce > stack pointer = 0x28:0xe537fc08 > frame pointer = 0x28:0xe537fc28 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 29 (em0 taskq) > trap number = 12 > panic: page fault > cpuid = 0 > > > It just stays there, unresponsive (no automatic reboot). > > > > Any ideas? There was a problem in the watchdog path, I don't recall if it was checked in to STABLE, I will check after the weekend. But, there is also the question of why you are in the watchdog path in the first place. Jack From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 09:06:00 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9C931065672; Sun, 8 Jun 2008 09:06:00 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id D5A7F8FC18; Sun, 8 Jun 2008 09:05:59 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OPN14158; Sun, 08 Jun 2008 11:05:58 +0200 Message-ID: <484BA0FD.40706@skytek.it> Date: Sun, 08 Jun 2008 11:06:05 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jack Vogel References: <484AFEF1.4040500@skytek.it> <2a41acea0806072342q518ac2afo663c91e730c16db@mail.gmail.com> In-Reply-To: <2a41acea0806072342q518ac2afo663c91e730c16db@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 09:06:00 -0000 Hello Jack! > > There was a problem in the watchdog path, I don't recall if > it was checked in to STABLE, I will check after the weekend. > > But, there is also the question of why you are in the watchdog > path in the first place. > I tried to apply the latest patch 1.184.2.3 2008/05/21 21:34:05 which includes the watchdog fix you mentioned. Let's see if it helps! No idea of why i'm in the watchdog path, but I forgot to add that this is virtualized VM on VmWare ESX (it emulates em interface)... so i guess it might the cause of why i am in the watchdog path. Do you have any ideas of why i wasn't able to collect dump and the system did not reboot automatically? Thanks, Daniel -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 12:08:52 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD1A61065675; Sun, 8 Jun 2008 12:08:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id B266B8FC0C; Sun, 8 Jun 2008 12:08:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C3AF41CC031; Sun, 8 Jun 2008 05:08:52 -0700 (PDT) Date: Sun, 8 Jun 2008 05:08:52 -0700 From: Jeremy Chadwick To: Daniel Ponticello Message-ID: <20080608120852.GB50122@eos.sc1.parodius.com> References: <484AFEF1.4040500@skytek.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484AFEF1.4040500@skytek.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 12:08:53 -0000 On Sat, Jun 07, 2008 at 11:34:41PM +0200, Daniel Ponticello wrote: > Hello, > i'm experiencing periodic kernel panics on a server with FreeBSD > 7.0-STABLE #0: Tue May 20 19:09:43 CEST 2008. > My big problem is that the system is not performing memory dumping and/or > automatic reoboot, > it just stays there. Try adjusting some of these sysctl values: hw.acpi.disable_on_reboot hw.acpi.handle_reboot You're using VMware, which may or may not behave properly anyways. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 12:58:55 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F3AF1065671; Sun, 8 Jun 2008 12:58:55 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 371F48FC15; Sun, 8 Jun 2008 12:58:54 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OSO96953; Sun, 08 Jun 2008 14:58:53 +0200 Message-ID: <484BD795.80502@skytek.it> Date: Sun, 08 Jun 2008 14:59:01 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> In-Reply-To: <20080608120852.GB50122@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 12:58:55 -0000 Hello, disabling acpi is not an option, since i'm running SMP. I have several other systems running 7.0 Release without problems, so it might be something on 7-Stable. Thanks, Daniel Jeremy Chadwick ha scritto: > On Sat, Jun 07, 2008 at 11:34:41PM +0200, Daniel Ponticello wrote: > >> Hello, >> i'm experiencing periodic kernel panics on a server with FreeBSD >> 7.0-STABLE #0: Tue May 20 19:09:43 CEST 2008. >> My big problem is that the system is not performing memory dumping and/or >> automatic reoboot, >> it just stays there. >> > > Try adjusting some of these sysctl values: > > hw.acpi.disable_on_reboot > hw.acpi.handle_reboot > > You're using VMware, which may or may not behave properly anyways. > > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 13:07:03 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01069106567C; Sun, 8 Jun 2008 13:07:03 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id EB6358FC17; Sun, 8 Jun 2008 13:07:01 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OTP60901; Sun, 08 Jun 2008 15:07:01 +0200 Message-ID: <484BD97C.5000009@skytek.it> Date: Sun, 08 Jun 2008 15:07:08 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> <484BD795.80502@skytek.it> In-Reply-To: <484BD795.80502@skytek.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 13:07:03 -0000 Sorry, I did not read well you suggestion ;) Anyway, the system reboots correctly if I issue the reboot command from command line. Should i adjust those values anyway? Thanks, Daniel Daniel Ponticello ha scritto: > Hello, > disabling acpi is not an option, since i'm running SMP. > I have several other systems running 7.0 Release without problems, > so it might be something on 7-Stable. > > > Thanks, > > Daniel > > > Jeremy Chadwick ha scritto: >> On Sat, Jun 07, 2008 at 11:34:41PM +0200, Daniel Ponticello wrote: >> >>> Hello, >>> i'm experiencing periodic kernel panics on a server with FreeBSD >>> 7.0-STABLE #0: Tue May 20 19:09:43 CEST 2008. >>> My big problem is that the system is not performing memory dumping >>> and/or automatic reoboot, >>> it just stays there. >>> >> >> Try adjusting some of these sysctl values: >> >> hw.acpi.disable_on_reboot >> hw.acpi.handle_reboot >> >> You're using VMware, which may or may not behave properly anyways. >> >> > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 13:31:14 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1B361065673; Sun, 8 Jun 2008 13:31:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7348FC0C; Sun, 8 Jun 2008 13:31:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 470131CC031; Sun, 8 Jun 2008 06:31:14 -0700 (PDT) Date: Sun, 8 Jun 2008 06:31:14 -0700 From: Jeremy Chadwick To: Daniel Ponticello Message-ID: <20080608133114.GA61781@eos.sc1.parodius.com> References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> <484BD795.80502@skytek.it> <484BD97C.5000009@skytek.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484BD97C.5000009@skytek.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 13:31:14 -0000 On Sun, Jun 08, 2008 at 03:07:08PM +0200, Daniel Ponticello wrote: > Sorry, I did not read well you suggestion ;) > > Anyway, the system reboots correctly if I issue the reboot command from > command line. > Should i adjust those values anyway? I'd recommend adjusting them and see if the bug (not automatically rebooting on panic) changes. I'm guessing it won't (especially if reboot(8) works fine), but it's worth trying. You're the 2nd person I've seen who has reported this problem (re: FreeBSD not properly rebooting on panic). The other person: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042250.html I'll add this to my Commonly reported issues Wiki. As for the problem itself, sorry, I have no idea what's causing it. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-net@FreeBSD.ORG Sun Jun 8 18:28:45 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 365B71065670; Sun, 8 Jun 2008 18:28:45 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 178FD8FC1F; Sun, 8 Jun 2008 18:28:43 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OYK23444; Sun, 08 Jun 2008 20:28:44 +0200 Message-ID: <484C24E4.5040108@skytek.it> Date: Sun, 08 Jun 2008 20:28:52 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> <484BD795.80502@skytek.it> <484BD97C.5000009@skytek.it> <20080608133114.GA61781@eos.sc1.parodius.com> In-Reply-To: <20080608133114.GA61781@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 18:28:45 -0000 I just checked the link you have reported. It looks like the problem is present only on SMP machines with both ULE and 4BSD scheduler. I can confirm that the problem is also present on 6.3-Stable. Basically, it freezes before collecting dump and before being able to reboot. I wish i could have more informations to open a PR. Thanks, Daniel Jeremy Chadwick ha scritto: > On Sun, Jun 08, 2008 at 03:07:08PM +0200, Daniel Ponticello wrote: > >> Sorry, I did not read well you suggestion ;) >> >> Anyway, the system reboots correctly if I issue the reboot command from >> command line. >> Should i adjust those values anyway? >> > > I'd recommend adjusting them and see if the bug (not automatically > rebooting on panic) changes. I'm guessing it won't (especially if > reboot(8) works fine), but it's worth trying. > > You're the 2nd person I've seen who has reported this problem (re: > FreeBSD not properly rebooting on panic). The other person: > > http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042250.html > > I'll add this to my Commonly reported issues Wiki. As for the problem > itself, sorry, I have no idea what's causing it. > > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 03:14:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 107911065672 for ; Mon, 9 Jun 2008 03:14:36 +0000 (UTC) (envelope-from kernel.panic007@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 B89038FC15 for ; Mon, 9 Jun 2008 03:14:35 +0000 (UTC) (envelope-from kernel.panic007@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so473935ana.13 for ; Sun, 08 Jun 2008 20:14:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:to:content-type :content-transfer-encoding:mime-version:subject:date:x-mailer:from; bh=/wz7F7IxS3pF7HDO1qkTgUOm0PD59j0S9Qvk7tIsjB0=; b=vwiZfq71XD/1DB9Fm1Y6V9hwal/BFdO2lf6/IFwYyYI6qzBg/Fd7EHiZ2QwbDTsZFk 0hiPn/mOCER7jLGbEvynvi+Ogn2HUHeQ5gXBhlobRsomeMDIc9CprwOoty29CgfZ9VjK coRksxrv7UgG6eUa9zNMo7p3fVKeyU1IkpVBg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:to:content-type:content-transfer-encoding:mime-version :subject:date:x-mailer:from; b=VSMAvWxS0IKXK0o+JEyMp0ehq/aD6w6H2JyEOJnBGcblrQF0OUEOQQgaI2/KCSXmIX VunDCZthBgRbClgsSs2NOBK3/qdYiSq+khbBHQodRfcXAFdh5ir1h186qtpL8w4V+oCh QWQ/QGrZMXZwuIlzPlK1HK5WXra9ZBtFv/CEI= Received: by 10.100.110.15 with SMTP id i15mr2786393anc.130.1212979822172; Sun, 08 Jun 2008 19:50:22 -0700 (PDT) Received: from ?192.168.1.100? ( [209.240.126.70]) by mx.google.com with ESMTPS id c37sm18685966ana.11.2008.06.08.19.50.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 08 Jun 2008 19:50:21 -0700 (PDT) Message-Id: <45BD6738-5D37-4B22-91B6-3CB60B9BEA24@gmail.com> To: freebsd-net@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Sun, 8 Jun 2008 22:50:18 -0400 X-Mailer: Apple Mail (2.924) From: Segnale007 Subject: I need some information about how to build my first voip . 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, 09 Jun 2008 03:14:36 -0000 Hello, I am getting an soekris net5501-70 where I will install freebsd, and I will build my voip. I don't know how to build a voip because I never did one, and I am wondering which program should I use to set it up, I did a lot of googling and I found many programs, such as Asterisk or SER, but I still don't know the difference between either of them, and I am trying to understand how I am supposed to start to build it. I am still wondering which kind of phone I should use. For example, can I use a standard landline phone or do I have to use something else? Thank you, Sincerely Pietro From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 08:13:49 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 927EE106567B for ; Mon, 9 Jun 2008 08:13:49 +0000 (UTC) (envelope-from marc.loerner@hob.de) Received: from mailgate.hob.de (mailgate.hob.de [212.185.199.3]) by mx1.freebsd.org (Postfix) with ESMTP id 50BC88FC24 for ; Mon, 9 Jun 2008 08:13:49 +0000 (UTC) (envelope-from marc.loerner@hob.de) Received: from imap.hob.de (mail2.hob.de [172.25.1.102]) by mailgate.hob.de (Postfix) with ESMTP id 539F6520075; Mon, 9 Jun 2008 10:13:48 +0200 (CEST) Received: from [172.22.0.190] (linux03.hob.de [172.22.0.190]) by imap.hob.de (Postfix on SuSE eMail Server 2.0) with ESMTP id 9032AFD413; Mon, 9 Jun 2008 10:13:47 +0200 (CEST) From: Marc =?iso-8859-1?q?L=F6rner?= Organization: hob To: Bruce Evans Date: Mon, 9 Jun 2008 10:13:27 +0200 User-Agent: KMail/1.6.2 References: <200806051712.47048.marc.loerner@hob.de> <200806061025.37856.marc.loerner@hob.de> <20080606221917.A16250@delplex.bde.org> In-Reply-To: <20080606221917.A16250@delplex.bde.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200806091013.27813.marc.loerner@hob.de> Cc: Peter Jeremy , freebsd-net@freebsd.org Subject: Re: Probable Bug in tcp.h X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 08:13:49 -0000 On Friday 06 June 2008 14:25, Bruce Evans wrote: > On Fri, 6 Jun 2008, Marc [iso-8859-1] Lörner wrote: > > On Friday 06 June 2008 09:52, Peter Jeremy wrote: > >> I gather from this comment that you have some code using struct tcphdr > >> that is getting alignment errors. struct tcphdr is extensively used > >> in the TCP stack within the kernel so it's likely that any layout or > >> alignment problem with it would show up there. I suspect you are > >> dereferencing a mis-aligned struct tcphdr. > > > > The funny thing is that the dereferencing occurs in > > "/usr/src/sys/netinet/tcp_input.c" in function tcp_input in line 550: > > > > /* > > * Check that TCP offset makes sense, > > * pull out TCP options and adjust length. XXX > > */ > > off = th->th_off << 2; <----- here > > if (off < sizeof (struct tcphdr) || off > tlen) { > > tcpstat.tcps_rcvbadoff++; > > goto drop; > > } > > > > So the misalignment may probably lie in TCP stack? > > Quite likely. th is normally at offset off0 in ip, where ip is required > to be 32-bit aligned (see my previous reply). You can see off0 in a > stack trace. > off0 is 0x14 => no problem with that but address of ip is 0xe000000021c8706e => not correct aligned to 32-bits Can anyone tell me, where ip is allocated, so I can do a little bit more research? Marc From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 10:16:31 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8E19106567C for ; Mon, 9 Jun 2008 10:16:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 754708FC1E for ; Mon, 9 Jun 2008 10:16:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id E80CE11381A; Mon, 9 Jun 2008 06:16:30 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 09 Jun 2008 06:16:31 -0400 X-Sasl-enc: jMr+L8R/Avn7Q960D6FFF4/xDNStjTwEIyPgBjDGhMPV 1213006590 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 20E1911328; Mon, 9 Jun 2008 06:16:30 -0400 (EDT) Message-ID: <484D02FC.9090407@FreeBSD.org> Date: Mon, 09 Jun 2008 11:16:28 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Marc_L=F6rner?= References: <200806051712.47048.marc.loerner@hob.de> <200806061025.37856.marc.loerner@hob.de> <20080606221917.A16250@delplex.bde.org> <200806091013.27813.marc.loerner@hob.de> In-Reply-To: <200806091013.27813.marc.loerner@hob.de> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Peter Jeremy , freebsd-net@freebsd.org Subject: Re: Probable Bug in tcp.h X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 10:16:31 -0000 Marc L=F6rner wrote: > off0 is 0x14 =3D> no problem with that > but address of ip is 0xe000000021c8706e =3D> not correct aligned to 32-= bits > > Can anyone tell me, where ip is allocated, so I can do a little bit mor= e=20 > research? > =20 It really depends on the context! That's a very wide ranging question. It depends upon whether mbuf chains are flowing up or down the stack,=20 whether or not the network driver supports checksum or header/segment=20 offload, and whether or not it is using zero-copy. Zero copy transmit normally only has mmu cost if the mbuf (from=20 userland) can be mapped to a location where headers are easily=20 prepended. Zero copy receive is more expensive and complex as it=20 requires that the DMA engine on the network interface card supports=20 header splitting. The FreeBSD stack is known to have some issues with mbuf alignment and=20 architectures other than those in its Tier 1. From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 11:07:03 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ABBE10656C7 for ; Mon, 9 Jun 2008 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 50B5E8FC28 for ; Mon, 9 Jun 2008 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m59B73dg070819 for ; Mon, 9 Jun 2008 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m59B72qd070815 for freebsd-net@FreeBSD.org; Mon, 9 Jun 2008 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Jun 2008 11:07:02 GMT Message-Id: <200806091107.m59B72qd070815@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 11:07:03 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/92090 net [bge] bge0: watchdog timeout -- resetting f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau f kern/102344 net [ipf] Some packets do not pass through network interfa o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] s kern/105943 net Network stack may modify read-only mbuf chain copies o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109733 net [bge] bge link state issues [regression] o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116328 net [bge]: Solid hang with bge interface o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117423 net [vlan] Duplicate IP on different interfaces o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119361 net [bge] bge(4) transmit performance problem o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 o kern/121983 net [fxp] fxp0 MBUF and PAE o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122082 net [in_pcb] NULL pointer dereference in in_pcbdrop o kern/122195 net [ed] Alignment problems in if_ed f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122427 net [apm] [panic] apm and mDNSResponder cause panic during o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122743 net [panic] vm_page_unwire: invalid wire count: 0 o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix f kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar f conf/122858 net [nsswitch.conf] nsswitch in 7.0 is f*cked up o kern/122875 net [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stabl o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/123066 net [ipsec] [panic] kernel trap with ipsec o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 f kern/123172 net [bce] Watchdog timeout problems with if_bce o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o bin/123465 net [ip6] route(1): route add -inet6 -interfac o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123617 net [tcp] breaking connection when client downloading file o bin/123633 net ifconfig(8) doesn't set inet and ether address in one p kern/123741 net [netgraph] [panic] kernel panic due to netgraph mpd o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o kern/123881 net [tcp] Turning on TCP blackholing causes slow localhost o kern/123950 net [tcp] TH_RST packet sended if received out-of-order da o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov 91 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/23063 net [PATCH] for static ARP tables in rc.network o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". 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/64556 net [sis] if_sis short cable fix problems with NetGear FA3 o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 o kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/95267 net packet drops periodically appear o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/100519 net [netisr] suggestion to fix suboptimal network polling 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 o conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/112179 net [sis] [patch] sis driver for natsemi DP83815D autonego o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o bin/117339 net [patch] route(8): loading routing management commands o kern/118727 net [netgraph] [patch] [request] add new ng_pf module a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/119432 net [arp] route add -host -iface causes arp e f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/121242 net [ate] [patch] Promiscuous mode of if_ate (arm) doesn't o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121443 net [gif] LOR icmp6_input/nd6_lookup o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122068 net [ppp] ppp can not set the correct interface with pptpd o kern/122145 net error while compiling with device ath_rate_amrr o kern/122295 net [bge] bge Ierr rate increase (since 6.0R) [regression] o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122697 net [ath] Atheros card is not well supported o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge f kern/122839 net [multicast] FreeBSD 7 multicast routing problem o kern/122928 net [em] interface watchdog timeouts and stops receiving p o kern/123892 net [tap] [patch] No buffer space available o kern/123961 net [vr] [patch] Allow vr interface to handle vlans o bin/124004 net ifconfig(8): Cannot assign both an IP and a MAC addres o kern/124225 net [ndis] [patch] ndis network driver sometimes loses net o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses 53 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 19:47:12 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6A8E106567F for ; Mon, 9 Jun 2008 19:47:12 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outT.internet-mail-service.net (outt.internet-mail-service.net [216.240.47.243]) by mx1.freebsd.org (Postfix) with ESMTP id 93FAD8FC21 for ; Mon, 9 Jun 2008 19:47:12 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 863422425; Mon, 9 Jun 2008 12:47:12 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 918FC2D623F; Mon, 9 Jun 2008 12:46:58 -0700 (PDT) Message-ID: <484D88AC.2000402@elischer.org> Date: Mon, 09 Jun 2008 12:46:52 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: FreeBSD Net , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: vimage include files 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, 09 Jun 2008 19:47:12 -0000 The current vimage code adds a handful of new include files.. e.g. vnet.h for vimage related defines that are related to general networking stuff vinet for vimage related defines that are related to inet. however eventually these defines would move to other files. For example I think every single file that includes vinet.h already includes netinet/in.h so these definitions move into that file. My question however comes with vnet.h 95% of the files that use it also include so possibly they could go there, but a few of them don't. they are: uipc_socket.c (sets a reference counter in the vnet structure) raw_cb.c accesses V_rawcb_list raw_usrreq.c accesses V_rawcb_list tcp_output.c lots of stuff of course but doesn't use if.h tcp_timer.c ditto vnet appears to be needed jsut for the SYSCTL_V_ stuff. (marko?) netipsec/keysock.c no need for if.h so there is no one place where all of the vnet structure is in scope but if.h is the closest. so should we: keep vnet.h? split it up a bit to make it more in scope? Find/make an include file for "networking in general?" is there such a file? As I said if.h seems the closest. From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 22:35:25 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07A65106566B for ; Mon, 9 Jun 2008 22:35:25 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id DF02C8FC16 for ; Mon, 9 Jun 2008 22:35:24 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail0.meer.net [209.157.152.14]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m59MYtRH059952 for ; Mon, 9 Jun 2008 15:35:20 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m59MYeMM050307 for ; Mon, 9 Jun 2008 15:34:40 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (hudson-trading.com [66.150.84.160] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m59MYeld055149 for ; Mon, 9 Jun 2008 15:34:40 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Mon, 09 Jun 2008 18:34:39 -0400 Message-ID: From: gnn@freebsd.org To: net@freebsd.org User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 620112 - 4434d8370520 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: Subject: Anyone seen this error on em ? 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, 09 Jun 2008 22:35:25 -0000 Jun 9 18:23:59 ... kernel: em0: port 0x2000-0x201f mem 0xd8020000-0xd803ffff,0xd800 0000-0xd801ffff irq 18 at device 0.0 on pci4 Jun 9 18:23:59 ... kernel: em0: Using MSI interrupt Jun 9 18:23:59 ... kernel: em0: Setup of Shared code failed Jun 9 18:23:59 ... kernel: device_attach: em0 attach returned 6 I've never seen the "returned 6" thing. Plugging a cable into the other em device on the motherboard, a super micro, currently works, but it looks like bad hardware to me. Thoughts? Later, George From owner-freebsd-net@FreeBSD.ORG Mon Jun 9 23:57:09 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEBF81065673 for ; Mon, 9 Jun 2008 23:57:09 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 8FA748FC0A for ; Mon, 9 Jun 2008 23:57:09 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2801459rvf.43 for ; Mon, 09 Jun 2008 16:57:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ANqZC/7SzeUZBkZmoa40mE8mIfbMA4y/dPCZbiz6SIQ=; b=igWIubv+X4OdJidCJGg+ThKsIZkMksTKpAFm94+WfU+kkOX+uLLU750rp0QQsZ0BOL pzA0OZNWmS7ByzMOXXKOdgUzrgcMJUTFwpMDkYmI64/4KxB5dOgOqBYF2Q3XxYA1clPQ lIk+XrLTuvCYt8sbGQFNoH1HljpVbIQY3pBeM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=f0jwi+BfjvOYwYMMZd/nqi7Hi1eOyM3iE4iU6VUETAbBzPD6Py2DCSn155KggQbhMd 3YZGir3/vXZp0Rr6+LYu2eiTLXl1C0rvWzrMFQi0WXVQqw6tnzcSA2jXNsPj9+Cjhl3C ggpKGlJUoFA34DSWkhWAfWUmAjP7hyXRSa97A= Received: by 10.114.166.1 with SMTP id o1mr4158670wae.119.1213054103012; Mon, 09 Jun 2008 16:28:23 -0700 (PDT) Received: by 10.114.59.4 with HTTP; Mon, 9 Jun 2008 16:28:22 -0700 (PDT) Message-ID: Date: Mon, 9 Jun 2008 16:28:22 -0700 From: "Kip Macy" To: gnn@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: net@freebsd.org Subject: Re: Anyone seen this error on em ? 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, 09 Jun 2008 23:57:09 -0000 Paul Saab has seen the same. What hardware are you using? -Kip On Mon, Jun 9, 2008 at 3:34 PM, wrote: > > > > Jun 9 18:23:59 ... kernel: em0: Version - 6.7.3> port 0x2000-0x201f mem 0xd8020000-0xd803ffff,0xd800 > 0000-0xd801ffff irq 18 at device 0.0 on pci4 > Jun 9 18:23:59 ... kernel: em0: Using MSI interrupt > Jun 9 18:23:59 ... kernel: em0: Setup of Shared code failed > Jun 9 18:23:59 ... kernel: device_attach: em0 attach returned 6 > > I've never seen the "returned 6" thing. Plugging a cable into the > other em device on the motherboard, a super micro, currently works, > but it looks like bad hardware to me. Thoughts? > > Later, > George > _______________________________________________ > 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 Jun 10 00:20:29 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC5121065670 for ; Tue, 10 Jun 2008 00:20:29 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 4049A8FC2D for ; Tue, 10 Jun 2008 00:20:29 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 39132 invoked from network); 9 Jun 2008 23:53:47 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.45.64) by acm.poly.edu with AES256-SHA encrypted SMTP; 9 Jun 2008 23:53:47 -0000 Message-ID: <484DC272.6020002@acm.poly.edu> Date: Mon, 09 Jun 2008 19:53:22 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: gnn@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: Anyone seen this error on em ? 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, 10 Jun 2008 00:20:29 -0000 gnn@freebsd.org wrote: > > Jun 9 18:23:59 ... kernel: em0: Version - 6.7.3> port 0x2000-0x201f mem 0xd8020000-0xd803ffff,0xd800 > 0000-0xd801ffff irq 18 at device 0.0 on pci4 > Jun 9 18:23:59 ... kernel: em0: Using MSI interrupt > Jun 9 18:23:59 ... kernel: em0: Setup of Shared code failed > Jun 9 18:23:59 ... kernel: device_attach: em0 attach returned 6 > > I've never seen the "returned 6" thing. Plugging a cable into the > other em device on the motherboard, a super micro, currently works, > but it looks like bad hardware to me. Thoughts? > > Later, > George > _______________________________________________ > 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" > Just a "me, too." Also on a Supermicro board, and it happens on some boots, but not all. -Boris From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 00:51:47 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71A451065670 for ; Tue, 10 Jun 2008 00:51:47 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 2E6098FC1B for ; Tue, 10 Jun 2008 00:51:47 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 7BDAC17D83; Tue, 10 Jun 2008 10:51:45 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (142.19.96.58.exetel.com.au [58.96.19.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 6A05A17D03; Tue, 10 Jun 2008 10:51:41 +1000 (EST) Message-ID: <484DD008.6090009@modulus.org> Date: Tue, 10 Jun 2008 10:51:20 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Boris Kochergin References: <484DC272.6020002@acm.poly.edu> In-Reply-To: <484DC272.6020002@acm.poly.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Anyone seen this error on em ? 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, 10 Jun 2008 00:51:47 -0000 > Just a "me, too." Also on a Supermicro board, and it happens on some > boots, but not all. I used to have this problem, but it went away after upgrading FreeBSD version (7-stable) - Andrew From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 01:11:49 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FB8D1065672 for ; Tue, 10 Jun 2008 01:11:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 5DAEE8FC1C for ; Tue, 10 Jun 2008 01:11:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1806402wah.3 for ; Mon, 09 Jun 2008 18:11:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8H/ZnCoDGZseK7ZsyNqRxg3aCbhfdGUU27yfzfzppdU=; b=Dq4NZyT+2Zbe46kBARgdeTarEQZ/a3XMwdGaFn7IHLwwEX29tDlL0jZ33ZvYapsOLW MnE39Eh/h3LRmU+20dwaa+OqKzowWQeIgc0ZS1QgBH2KIPNY+2r8b0VTGpnd8M2J4kCe LacaaEnpUZ9oZaWtmWKUK4soKyp8V3vTSklpI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=M2xjLtIkOZ+6gOaV6t98twBnqfHRUbGvdo9yOA7YihJheyCvJLLoA82jF8jM9pKy9O qrq7GV12hZdz6EmfhUGp6ZN1/iPKY1D2oU1aJSJDsQIiDAgzoNqfpTEAj/Qzdw4mdv1t O35sBLboPgRF1hryt9xFvGtdqR49mRcUli44I= Received: by 10.114.122.2 with SMTP id u2mr4261704wac.1.1213060309064; Mon, 09 Jun 2008 18:11:49 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Mon, 9 Jun 2008 18:11:49 -0700 (PDT) Message-ID: <2a41acea0806091811t2d085d64ra9e9e24029e91d73@mail.gmail.com> Date: Mon, 9 Jun 2008 18:11:49 -0700 From: "Jack Vogel" To: "Andrew Snow" In-Reply-To: <484DD008.6090009@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484DC272.6020002@acm.poly.edu> <484DD008.6090009@modulus.org> Cc: freebsd-net@freebsd.org, Boris Kochergin Subject: Re: Anyone seen this error on em ? 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, 10 Jun 2008 01:11:49 -0000 There is more than one problem that results in the same error in the core driver, the more common one is actually fixed, as Andrew notes, in the shared code in the latest driver. However, this is a more obscure bug that occurs on some hardware, and it seems to require that you have a management BMC, this is what Paul Saab is seeing, there is not a final fix for this issue yet. Note that both these problems only occur with the esb2lan type NIC. Jack On Mon, Jun 9, 2008 at 5:51 PM, Andrew Snow wrote: >> Just a "me, too." Also on a Supermicro board, and it happens on some >> boots, but not all. > > > I used to have this problem, but it went away after upgrading FreeBSD > version (7-stable) > > - Andrew > _______________________________________________ > 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 Jun 10 02:04:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C45EE1065677 for ; Tue, 10 Jun 2008 02:04:22 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 8BE0E8FC12 for ; Tue, 10 Jun 2008 02:04:22 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2856182rvf.43 for ; Mon, 09 Jun 2008 19:04:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=grH2Zim8jBD2E8roHTkvGA/C2jvcVPxRhAhZM9sLD+Q=; b=JUXz25q5H3rdh5MOm21vvFu8ojUppZUWndA1jnlae6buECg5ZsNptPJMnSVUPVIxan JHzVtZFDNyOKc5gBdb4djoT5+kta/SjWQQxjRxkeOTlQotkdjqJm3GkTqtn+DjtuWThS aT/0vFbKkwr9XySR/7N7VNw3hCz972PVhn8/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=DuCAtYDIffHch0vLaO7V7Ft9XLySN3pQtAXhTQTmMSkFFZZJmLJ/O3hJAvY/Myswa9 vSq3cd2fZ7tgahQEUVKLz4KZnIwiFoYQdCpPnpgF2ItLkD17X5fOAkjid4z0Bs+neMdr ubym600Dl/RelhEEbsr+wH0cC3HR9sXhxfJIk= Received: by 10.115.77.1 with SMTP id e1mr4253672wal.58.1213061737582; Mon, 09 Jun 2008 18:35:37 -0700 (PDT) Received: by 10.114.108.20 with HTTP; Mon, 9 Jun 2008 18:35:37 -0700 (PDT) Message-ID: <5c0ff6a70806091835p2c206fe2p203b37433b87e073@mail.gmail.com> Date: Mon, 9 Jun 2008 18:35:37 -0700 From: "Paul Saab" Sender: paul.m.saab@gmail.com To: freebsd-net@freebsd.org In-Reply-To: <2a41acea0806091811t2d085d64ra9e9e24029e91d73@mail.gmail.com> MIME-Version: 1.0 References: <484DC272.6020002@acm.poly.edu> <484DD008.6090009@modulus.org> <2a41acea0806091811t2d085d64ra9e9e24029e91d73@mail.gmail.com> X-Google-Sender-Auth: 2ea79bf5a59a4fc1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Anyone seen this error on em ? 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, 10 Jun 2008 02:04:23 -0000 http://yogurt.org/FreeBSD/em.diff On Mon, Jun 9, 2008 at 6:11 PM, Jack Vogel wrote: > There is more than one problem that results in the same error in the > core driver, the more common one is actually fixed, as Andrew notes, > in the shared code in the latest driver. However, this is a more obscure > bug that occurs on some hardware, and it seems to require that you have > a management BMC, this is what Paul Saab is seeing, there is not a final > fix for this issue yet. > > Note that both these problems only occur with the esb2lan type NIC. > > Jack > > > On Mon, Jun 9, 2008 at 5:51 PM, Andrew Snow wrote: > >> Just a "me, too." Also on a Supermicro board, and it happens on some > >> boots, but not all. > > > > > > I used to have this problem, but it went away after upgrading FreeBSD > > version (7-stable) > > > > - Andrew > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 03:51:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A7771065687 for ; Tue, 10 Jun 2008 03:51:13 +0000 (UTC) (envelope-from agaviola@infoweapons.com) Received: from infoweapons.com (mail0.infoweapons.org [204.2.248.50]) by mx1.freebsd.org (Postfix) with ESMTP id BCCE58FC2F for ; Tue, 10 Jun 2008 03:51:12 +0000 (UTC) (envelope-from agaviola@infoweapons.com) Received: from ([58.71.34.137]) by mail0.infoweapons.com with ESMTP with TLS id 4321444.303102; Mon, 09 Jun 2008 23:35:44 -0400 Message-ID: <484DF690.6010101@infoweapons.com> Date: Tue, 10 Jun 2008 11:35:44 +0800 From: "Archimedes S. Gaviola" User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "Bruce M. Simpson" , "Andrey V. Elsukov" References: <4849C87F.9030804@infoweapons.com> <484A49D6.1000808@FreeBSD.org> In-Reply-To: <484A49D6.1000808@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [Removal of mrouted in FreeBSD-7.0] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 03:51:13 -0000 Bruce M. Simpson wrote: > Archimedes S. Gaviola wrote: >> Hi! I have just read from the FreeBSD-7.0 release notes >> http://www.freebsd.org/releases/7.0R/relnotes.html that the mrouted >> multicast routing protocol (DVMRP implementation) has been removed >> from the base system. I want to know what multicast routing protocol >> will served as replacement to this? The KAME snap kit have PIM-SM and >> PIM-DM implementations but are specific only to IPv6. > > DVMRP is something of a legacy protocol now, most deployments use PIM-SM. > > mrouted is still available in ports as other folk have pointed out > > If you want a freely available router with full multicast capability, > please give XORP a try. > Thanks Bruce and Andrey to your reply! Yes DVMRP is a legacy protocol which I've known many users used it on the IP multicast backbone (MBONE) deployment. Yes XORP, which I'm familiar with and have used it but if ever there's a way to implement IP multicasting with PIM-SM and or PIM-DM in the FreeBSD base system, how big is the work would be? What are the things that needs to be considered if we are going to implement PIM-SM and or PIM-DM to the current FreeBSD network subsystem? The goal is to be able FreeBSD to provide native IP multicast using PIM just like the way DVMRP protocol is implemented before as part of the base system. Thanks, Archimedes From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 03:58:31 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8DBF1065676 for ; Tue, 10 Jun 2008 03:58:31 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id B1BC48FC0A for ; Tue, 10 Jun 2008 03:58:31 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1845874wah.3 for ; Mon, 09 Jun 2008 20:58:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ASGHIexsrG8bvCG1NCb4wJUvU0EyEy5j21UhgHbDRy0=; b=Jr8UsRw2B/JNEaK0XQM7n/ENyd/5iEOzkBcBeSqyH8yz+CAsWn00sZ6/aue0UvNk7U 7OYe/0B0S59zHaf8uqsRU+lVz+QRuvDJILmr4Ty0qHh9EcENOxL5/GGPvhNw/OjUt5sV tQP6Wphuse3flXdJ2sKfuWFV++DYsX/xtM45I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=a/Z/nS1z/nw/DYvvOqk+/dSlgZ8H/Pd8/nChjj7xoOcqD9GmB/g2xdEde1OUe/YRYK nqkdXFSZXx8ymC0PNdoscQ0ZE7p7fCSDT4/823obAa+AAl9hin/VfR5fkg2b23TQtnor 3ZMMX0Jo2obBRuMledHj5MpuEjD3jb5bbPsQY= Received: by 10.114.52.1 with SMTP id z1mr4345093waz.42.1213070310775; Mon, 09 Jun 2008 20:58:30 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Mon, 9 Jun 2008 20:58:30 -0700 (PDT) Message-ID: <2a41acea0806092058o5d559329pd6138d90fe67a484@mail.gmail.com> Date: Mon, 9 Jun 2008 20:58:30 -0700 From: "Jack Vogel" To: "Paul Saab" In-Reply-To: <5c0ff6a70806091835p2c206fe2p203b37433b87e073@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484DC272.6020002@acm.poly.edu> <484DD008.6090009@modulus.org> <2a41acea0806091811t2d085d64ra9e9e24029e91d73@mail.gmail.com> <5c0ff6a70806091835p2c206fe2p203b37433b87e073@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Anyone seen this error on em ? 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, 10 Jun 2008 03:58:32 -0000 Just so people understand, you can try this change and if it eliminates the init failure then use it temporarily. What the code is, is a way that the driver and BMC have agreed to use to keep out of eachother's way, but at the moment the code is flawed, its being actively worked and I expect new shared code soon. If you disable the BMC, by the way, you should not see this error or need this change. Jack On Mon, Jun 9, 2008 at 6:35 PM, Paul Saab wrote: > http://yogurt.org/FreeBSD/em.diff > > On Mon, Jun 9, 2008 at 6:11 PM, Jack Vogel wrote: > >> There is more than one problem that results in the same error in the >> core driver, the more common one is actually fixed, as Andrew notes, >> in the shared code in the latest driver. However, this is a more obscure >> bug that occurs on some hardware, and it seems to require that you have >> a management BMC, this is what Paul Saab is seeing, there is not a final >> fix for this issue yet. >> >> Note that both these problems only occur with the esb2lan type NIC. >> >> Jack >> >> >> On Mon, Jun 9, 2008 at 5:51 PM, Andrew Snow wrote: >> >> Just a "me, too." Also on a Supermicro board, and it happens on some >> >> boots, but not all. >> > >> > >> > I used to have this problem, but it went away after upgrading FreeBSD >> > version (7-stable) >> > >> > - Andrew >> > _______________________________________________ >> > freebsd-net@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >> > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >> > _______________________________________________ > 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 Jun 10 05:07:24 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9858D1065681 for ; Tue, 10 Jun 2008 05:07:24 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 3A8228FC1E for ; Tue, 10 Jun 2008 05:07:24 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 29872 invoked by uid 399); 10 Jun 2008 05:07:22 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 10 Jun 2008 05:07:22 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <484E0C08.1060800@FreeBSD.org> Date: Mon, 09 Jun 2008 22:07:20 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: freebsd-net@freebsd.org, so@freebsd.org X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Proposal: Enable IPv6 Privacy Extensions (RFCs 3041/4941) by default 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, 10 Jun 2008 05:07:24 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 By default, IPv6 stateless autoconfiguration creates a 64 bit hostid for each interface based on the mac address (for ethernet, but for us that's the common case). This is convenient since if you're using RA neither the user nor the admin has to do anything to get the node on line, it "just works." There is a privacy issue with this however, because this identifier is created in such a way as to make it globally unique, the machine (and therefore in almost all cases the user) can be tracked by third parties such as web sites, even if they move from one network prefix to another, such as with a laptop. To address those privacy concerns RFC 3041 was written, and eventually obsoleted by RFC 4941. ftp://ftp.rfc-editor.org/in-notes/rfc4941.txt Our IPv6 implementation comes with the code to enable this feature, but by default it is turned off. My proposal is to enable it by default, and give the user a knob in rc.conf to turn it off. I'm interested in any arguments y'all might have for or against. To test this is pretty simple, add the following to /etc/sysctl.conf: net.inet6.ip6.use_tempaddr=1 net.inet6.ip6.prefer_tempaddr=1 The "normal" EUI-64-based address will still be configured, but there will also be a random identifier added to the interface as an alias, and outgoing traffic will go out from that address. In way of comparison, windows starting with XP enables this feature by default for clients, and has a knob to enable it for servers. I'd be interested to hear what other systems do. Thoughts? Doug - -- ~ This .signature sanitized for your protection -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREDAAYFAkhODAcACgkQyIakK9Wy8PumNgCg8Gi+sa0OYanbVcY1IgGu0S3i 64sAn2edBnEh1YkEeqvKPHrAZnOQAbsr =PNXz -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 07:45:31 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B21C106567F; Tue, 10 Jun 2008 07:45:31 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id 1C8BC8FC12; Tue, 10 Jun 2008 07:45:31 +0000 (UTC) (envelope-from randy@psg.com) Received: from [202.214.86.146] (helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K5yXq-000Ei3-Le; Tue, 10 Jun 2008 07:45:30 +0000 Message-ID: <484E3119.4060102@psg.com> Date: Tue, 10 Jun 2008 16:45:29 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Doug Barton References: <484E0C08.1060800@FreeBSD.org> In-Reply-To: <484E0C08.1060800@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, so@freebsd.org Subject: Re: Proposal: Enable IPv6 Privacy Extensions (RFCs 3041/4941) by default 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, 10 Jun 2008 07:45:31 -0000 > To address those privacy concerns RFC 3041 was written, and eventually > obsoleted by RFC 4941. ftp://ftp.rfc-editor.org/in-notes/rfc4941.txt > Our IPv6 implementation comes with the code to enable this feature, > but by default it is turned off. My proposal is to enable it by > default, and give the user a knob in rc.conf to turn it off. the only drawback is that forward and reverse dns would not be easily filled. but anyone who relies on a mac address for dns hacking is asking for trouble; use dhcpv6 or hard code the host's ip address in /etc/rc.conf. so i have no problem with the change. thanks for asking. randy From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 08:03:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FF4F1065684 for ; Tue, 10 Jun 2008 08:03:22 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 07A468FC0A for ; Tue, 10 Jun 2008 08:03:21 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1257102ywe.13 for ; Tue, 10 Jun 2008 01:03:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=F8HGDH6JBKLrLI39KzbZK2QfpkC07jsZBFv93Jo93GM=; b=fmGP91e1ldtfoOOHFYpjUu/hocgqAjdhQxP/dAmtUyq5b0oVIkBR75zwcvBupN/ICW NA5WRGkN1R1aGu7uyQ4Rfz3Z8tRbkNHniGAlg8K8HJBc3INox1HhKsxBNSG4iFUzt5VK jqR7dpWnQHoET+5cT22fpiLzRDfYRsYhRwv+Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=RsxxqmAR3yJ+b+E8zkTw9/vVN+osA2n5gxfVvCl3LRMqnPvfPqPuE4MXF+5jTD1NPE AinFla+OpXJ5AtJYGoXZwpPgvdnAB5KT02tgb7hxHLpkhdfhc0gm59q6RUm7uihEqAAO tUj5p96H0NfzqvEf3imzgN1KDCRWJn1+hmDJ4= Received: by 10.151.153.14 with SMTP id f14mr7976229ybo.73.1213084999040; Tue, 10 Jun 2008 01:03:19 -0700 (PDT) Received: by 10.151.84.2 with HTTP; Tue, 10 Jun 2008 01:03:19 -0700 (PDT) Message-ID: <20def4870806100103o6fcc70e3t78adf8f94d0b3b47@mail.gmail.com> Date: Tue, 10 Jun 2008 11:03:19 +0300 From: "Yony Yossef" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: TCP messages go OUT OF ORDER on FreeBSD 7 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 08:03:22 -0000 Hi All. I'm working on a 10GigE driver for FreeBSD 7, supporting both LRO and TSO (LSO). I get a stable connection enabling LRO alone and TSO alone, but when I enable both offloads I get OUT OF ORDER packets on the sender side. Meaning the sending OS sends the same packet several times without getting any ACKs in between. The wireshark timestamps show that the sender did not even wait too long in order to retransmit the packets, there is only a 10-20 microsecs gap between the first and second sends of the same packet. I'm a TCP/IP newbee, can anybody explain to me how can this happen? Yony From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 08:25:42 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A68C5106567D for ; Tue, 10 Jun 2008 08:25:42 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 643D68FC12 for ; Tue, 10 Jun 2008 08:25:42 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1259384ywe.13 for ; Tue, 10 Jun 2008 01:25:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=xj0exH8xC8wMn6t4c1nsq8Ik7J2Q5kUcsICoqyu84XQ=; b=rXLbcE5CFKCqATQJmbL/9dqKTMWoJ0msVzfscxLkVgTmjc3gAYBnvcm+et87KH2slh CRImytHzJzNtK+9aQWwJDVfoo9bUZNF2L454tEfG5itxW3QW1sh7pLlpd69ZpCmUWzM+ off4qwlBt+XciRCG8eaHPrnbjvqrTb9FMNyDo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=pE5w4wADtLm7Nvccrl5Z2pwRUNW2562C15d075pVjgMox+038uLK8oovHEHkTItSnA U+YlNfGswHGJWtHeVf/REkH4SyWX7CBQ/CnWnBw2pfeweWXi2F3xHpk9iz6QtYdF1KFc Ks2rrD/DLREXuHwfQXNNYFD+TnPHbhx2nmANM= Received: by 10.151.84.12 with SMTP id m12mr8031981ybl.2.1213086339574; Tue, 10 Jun 2008 01:25:39 -0700 (PDT) Received: by 10.151.84.2 with HTTP; Tue, 10 Jun 2008 01:25:39 -0700 (PDT) Message-ID: <20def4870806100125l7b5b1e6fhd295d46d1106abb5@mail.gmail.com> Date: Tue, 10 Jun 2008 11:25:39 +0300 From: "Yony Yossef" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: tso_segsz and mss above jumbo MTU in FreeBSD 7 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 08:25:42 -0000 Hi All. I'm working on a 10GigE driver for FreeBSD 7. Looking at other GigE and 10GigE drivers I've seen that mbuf->m_pkthdr.tso_segsz is assigned to MSS (Max Segment Size) on the Tx routines. If I understand correctly the tso_segsz is supposed to inform the driver with the MTU set by the OS, therefore it should change upon ifconfig mtu commands. When I set my MTU to 9600 I still recieve tso_segsz=1500 in the Tx mbufs from the OS. Where's my mistake here? Yony From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 12:42:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EA711065671 for ; Tue, 10 Jun 2008 12:42:05 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id BF49A8FC1C for ; Tue, 10 Jun 2008 12:42:04 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 30535 invoked by uid 89); 10 Jun 2008 12:42:34 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 10 Jun 2008 12:42:34 -0000 Message-ID: <484E7718.9050607@ibctech.ca> Date: Tue, 10 Jun 2008 08:44:08 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Randy Bush References: <484E0C08.1060800@FreeBSD.org> <484E3119.4060102@psg.com> In-Reply-To: <484E3119.4060102@psg.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Doug Barton , so@freebsd.org Subject: Re: Proposal: Enable IPv6 Privacy Extensions (RFCs 3041/4941) by default 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, 10 Jun 2008 12:42:05 -0000 Randy Bush wrote: >> To address those privacy concerns RFC 3041 was written, and eventually >> obsoleted by RFC 4941. ftp://ftp.rfc-editor.org/in-notes/rfc4941.txt >> Our IPv6 implementation comes with the code to enable this feature, >> but by default it is turned off. My proposal is to enable it by >> default, and give the user a knob in rc.conf to turn it off. > > the only drawback is that forward and reverse dns would not be easily > filled. but anyone who relies on a mac address for dns hacking is > asking for trouble; use dhcpv6 or hard code the host's ip address in > /etc/rc.conf. DNS in this context is really of least concern, and there are simple ways around that as Randy states. I would think that enabling IPv6 Privacy Extensions by default would have no worse effect on a host in regards to DNS than a similar situation with IPv4 Auto Configuration. > so i have no problem with the change. thanks for asking. I also support following the specification by default. Steve From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 12:47:41 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D87AF1065679 for ; Tue, 10 Jun 2008 12:47:41 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id B39C18FC1C for ; Tue, 10 Jun 2008 12:47:41 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 27856112CA0; Tue, 10 Jun 2008 08:47:41 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 10 Jun 2008 08:47:41 -0400 X-Sasl-enc: OCiRjfY+LrlJENEcvOBp4V7gJg8Qb6U1x/py+E/+USjC 1213102060 Received: from empiric.lon.incunabulum.net (unknown [81.168.51.182]) by mail.messagingengine.com (Postfix) with ESMTPSA id 6F70036C5B; Tue, 10 Jun 2008 08:47:40 -0400 (EDT) Message-ID: <484E77E9.5030101@FreeBSD.org> Date: Tue, 10 Jun 2008 13:47:37 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: "Archimedes S. Gaviola" References: <4849C87F.9030804@infoweapons.com> <484A49D6.1000808@FreeBSD.org> <484DF690.6010101@infoweapons.com> In-Reply-To: <484DF690.6010101@infoweapons.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "Andrey V. Elsukov" Subject: Re: [Removal of mrouted in FreeBSD-7.0] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 12:47:41 -0000 Archimedes S. Gaviola wrote: > ...if ever there's a way to implement IP multicasting with PIM-SM and > or PIM-DM in the FreeBSD base system, how big is the work would be? > What are the things that needs to be considered if we are going to > implement PIM-SM and or PIM-DM to the current FreeBSD network > subsystem? The goal is to be able FreeBSD to provide native IP > multicast using PIM just like the way DVMRP protocol is implemented > before as part of the base system. I really think the remit of multicast routing is too wide to be addressed in the base system, which is why projects like XORP and pimdd exist -- it doesn't strike me as a good fit for the FreeBSD base system. Separate projects already exist for this. If someone is willing to commit to all the man-hours involved in the reimplementation and ongoing support of such a thing, blimey... they must have a lot of free time! cheers BMS From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 12:54:33 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CA911065670 for ; Tue, 10 Jun 2008 12:54:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id CB5AE8FC13 for ; Tue, 10 Jun 2008 12:54:32 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-055-146.pools.arcor-ip.net [88.66.55.146]) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis) id 0MKwtQ-1K63Mt2Mcf-0004CT; Tue, 10 Jun 2008 14:54:31 +0200 Received: (qmail 46219 invoked by uid 80); 10 Jun 2008 12:52:29 -0000 Received: from 141.3.70.194 (SquirrelMail authenticated user mlaier) by mlaier.homeunix.org with HTTP; Tue, 10 Jun 2008 14:52:29 +0200 (CEST) Message-ID: In-Reply-To: <484E0C08.1060800@FreeBSD.org> References: <484E0C08.1060800@FreeBSD.org> Date: Tue, 10 Jun 2008 14:52:29 +0200 (CEST) From: "Max Laier" To: "Doug Barton" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Provags-ID: V01U2FsdGVkX18Lyo6xh1A3IzVDt/36kvT3nFqSARnO9clFHSg BUpSu+UYq4QoIYZxOufVf6NbSOlMbpZ8J9n6CnTH8qBCjHYQJx cHdvvPJhXaJNVWyJyckEQ== Cc: freebsd-net@freebsd.org, so@freebsd.org Subject: Re: Proposal: Enable IPv6 Privacy Extensions (RFCs 3041/4941) by default 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, 10 Jun 2008 12:54:33 -0000 Am Di, 10.06.2008, 07:07, schrieb Doug Barton: > By default, IPv6 stateless autoconfiguration creates a 64 bit hostid > for each interface based on the mac address (for ethernet, but for us > that's the common case). This is convenient since if you're using RA > neither the user nor the admin has to do anything to get the node on > line, it "just works." There is a privacy issue with this however, > because this identifier is created in such a way as to make it > globally unique, the machine (and therefore in almost all cases the > user) can be tracked by third parties such as web sites, even if they > move from one network prefix to another, such as with a laptop. > > To address those privacy concerns RFC 3041 was written, and eventually > obsoleted by RFC 4941. ftp://ftp.rfc-editor.org/in-notes/rfc4941.txt > Our IPv6 implementation comes with the code to enable this feature, > but by default it is turned off. My proposal is to enable it by > default, and give the user a knob in rc.conf to turn it off. I'm > interested in any arguments y'all might have for or against. To test > this is pretty simple, add the following to /etc/sysctl.conf: > net.inet6.ip6.use_tempaddr=1 > net.inet6.ip6.prefer_tempaddr=1 > > The "normal" EUI-64-based address will still be configured, but there > will also be a random identifier added to the interface as an alias, > and outgoing traffic will go out from that address. > > In way of comparison, windows starting with XP enables this feature by > default for clients, and has a knob to enable it for servers. I'd be > interested to hear what other systems do. > > > Thoughts? All for it. Are you, however, sure that we implement RFC 4941 fully? I think there are some configuration parameters missing. Also, I seem to recall that our DAD wasn't quite state-of-the-art, yet. Finally, any chance I can get you to implement the socket options in RFC 5014, so that programs have can force a temp/static address if they so choose - independent of the global setting. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 15:52:07 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96BF5106566B for ; Tue, 10 Jun 2008 15:52:07 +0000 (UTC) (envelope-from rjohanne@wnk.hamline.edu) Received: from wnk.hamline.edu (wnk.hamline.edu [138.192.24.100]) by mx1.freebsd.org (Postfix) with ESMTP id 5DF798FC22 for ; Tue, 10 Jun 2008 15:52:07 +0000 (UTC) (envelope-from rjohanne@wnk.hamline.edu) Received: from wnk.hamline.edu (wnk.hamline.edu [138.192.24.100]) by wnk.hamline.edu (8.13.8/8.13.8) with ESMTP id m5AEkNDY025192 for ; Tue, 10 Jun 2008 09:46:23 -0500 Date: Tue, 10 Jun 2008 09:46:23 -0500 (CDT) From: R J X-X-Sender: rjohanne@wnk.hamline.edu To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: tcpdump/snort to capture chat sessions 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, 10 Jun 2008 15:52:07 -0000 I am trying to use tcpdump (or snort, but they are both behaving the same in this case) to capture all the lines or contents of an msn chat session, the actual conversation. I am getting partial output; i.e, I'll only get half of a sentence, and I don't see the rest of the lines. And ofcourse, alot of it seems to be hex or obfuscated html? What switches do I need to capture the entire lines of text? I am using these options with snort: snort -i hme1 -v -K None -X That's sending output to stdout, which is fine with me. Thanks for any pointers/suggestions/recommendations. Robert From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 16:01:52 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DD55106567D for ; Tue, 10 Jun 2008 16:01:52 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 058668FC21 for ; Tue, 10 Jun 2008 16:01:51 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so113169uge.37 for ; Tue, 10 Jun 2008 09:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent:sender; bh=A3Yzrodolg2I5mwPaXj3c/gFZKBFRFvJ1QG50ldVbZc=; b=RpriBMWJ0cKZyfckGklud5su1Fe+JOBlOUTNuX+3IquUMMzNIzfbhXY15cQHS6Wakw Crx+ZwtA/6cWMGewNkIGfNYhYNfqZYItSsljlhaAHKNyMhzF12EQ11aWLBSaa12YWwj6 YgtHXKmbL/bDQEbrn8a0NcQhe2u4s9qmrb/Ig= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent:sender; b=kutW9TwEGa7qPTbMPLtYkbRKCfxnJ/5qPWzEataia/iQtsVXUL6RLbsXUsOjEsndb0 73Hf8j2+NxX9djC0SjdcmYqm/lFoHRTykcsaqH/sYTIWks8Hn0HWniOswRSmB3adcQsO hl7XkCU047e0zjI05KfDz1bgc+xH0qfJB2JVE= Received: by 10.67.15.2 with SMTP id s2mr490201ugi.87.1213113710518; Tue, 10 Jun 2008 09:01:50 -0700 (PDT) Received: from epsilon.local ( [89.214.193.209]) by mx.google.com with ESMTPS id 5sm419883ugc.87.2008.06.10.09.01.46 (version=SSLv3 cipher=RC4-MD5); Tue, 10 Jun 2008 09:01:49 -0700 (PDT) Date: Tue, 10 Jun 2008 17:01:40 +0100 From: Rui Paulo To: Doug Barton Message-ID: <20080610160140.GB33773@epsilon.local> References: <484E0C08.1060800@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484E0C08.1060800@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: Rui Paulo Cc: freebsd-net@freebsd.org, so@freebsd.org Subject: Re: Proposal: Enable IPv6 Privacy Extensions (RFCs 3041/4941) by default 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, 10 Jun 2008 16:01:52 -0000 On Mon, Jun 09, 2008 at 10:07:20PM -0700, Doug Barton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > By default, IPv6 stateless autoconfiguration creates a 64 bit hostid > for each interface based on the mac address (for ethernet, but for us > that's the common case). This is convenient since if you're using RA > neither the user nor the admin has to do anything to get the node on > line, it "just works." There is a privacy issue with this however, > because this identifier is created in such a way as to make it > globally unique, the machine (and therefore in almost all cases the > user) can be tracked by third parties such as web sites, even if they > move from one network prefix to another, such as with a laptop. > > To address those privacy concerns RFC 3041 was written, and eventually > obsoleted by RFC 4941. ftp://ftp.rfc-editor.org/in-notes/rfc4941.txt > Our IPv6 implementation comes with the code to enable this feature, > but by default it is turned off. My proposal is to enable it by > default, and give the user a knob in rc.conf to turn it off. I'm > interested in any arguments y'all might have for or against. To test > this is pretty simple, add the following to /etc/sysctl.conf: > net.inet6.ip6.use_tempaddr=1 > net.inet6.ip6.prefer_tempaddr=1 > > The "normal" EUI-64-based address will still be configured, but there > will also be a random identifier added to the interface as an alias, > and outgoing traffic will go out from that address. > > In way of comparison, windows starting with XP enables this feature by > default for clients, and has a knob to enable it for servers. I'd be > interested to hear what other systems do. > > > Thoughts? +1. I'm okay with it. Regards, -- Rui Paulo From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 16:03:21 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A22F106568D for ; Tue, 10 Jun 2008 16:03:21 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id F2F628FC33 for ; Tue, 10 Jun 2008 16:03:20 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (vanquish.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.162]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Tue, 10 Jun 2008 12:03:19 -0400 id 0005641D.484EA5C8.00013EBA Date: Tue, 10 Jun 2008 12:02:22 -0400 From: Bill Moran To: R J Message-Id: <20080610120222.9e2760fe.wmoran@collaborativefusion.com> In-Reply-To: References: Organization: Collaborative Fusion X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: tcpdump/snort to capture chat sessions 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, 10 Jun 2008 16:03:21 -0000 In response to R J : > I am trying to use tcpdump (or snort, but they are both behaving the same > in this case) to capture all the lines or contents of an msn > chat session, the actual conversation. I am getting partial output; i.e, > I'll only get half of a sentence, and I don't see the rest of the lines. > And ofcourse, alot of it seems to be hex or obfuscated html? > > What switches do I need to capture the entire lines of text? Don't know about snort, but with tcpdump use -s0 -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023 From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 16:29:00 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FB27106567F for ; Tue, 10 Jun 2008 16:29:00 +0000 (UTC) (envelope-from rahman.sazzadur@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id D9F9D8FC0A for ; Tue, 10 Jun 2008 16:28:59 +0000 (UTC) (envelope-from rahman.sazzadur@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1343604ywe.13 for ; Tue, 10 Jun 2008 09:28:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type; bh=GqG4/cZe828cqfhHD0zC8UNgN7nfnJL4Dq12UjNQpHU=; b=PcEe81ctzdaZ0NFHY3RynTkUjOqEcW+SiNc5dhP8C/ZE8nhAC94a4ArBH5skmQD7sZ BQVJXMX2vtEv54julE50cUCO0wu67uUzmShVigyZ7SSY19jbMtte64l8o5Be0o6alJJl 99ulpNGcXBOnq6T9nwPmY4qX3/BiI3tdK1Jq8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=GmOMY0tA5kQysGOwjYGMU4+1Mtr8RcAsvFqczlzAwdfVjLFKQcxVOLw80X9ZZMMWfY 9LCW+yW3u0yHHq6QWOiBNz3eCmyi8PDxh+DXIC5hoBfcYaSGcQ/KZ0rwdMwNpl4Z4SBx zq+5i/qcEIMwDTB0yYtOA9N2WGRRfigmZvtjU= Received: by 10.142.211.10 with SMTP id j10mr2138124wfg.197.1213115331938; Tue, 10 Jun 2008 09:28:51 -0700 (PDT) Received: by 10.143.195.10 with HTTP; Tue, 10 Jun 2008 09:28:51 -0700 (PDT) Message-ID: <82bdb5ec0806100928q15e25480k24f88798e12bffc4@mail.gmail.com> Date: Tue, 10 Jun 2008 11:28:51 -0500 From: "sazzadur rahman" To: rrs@cisco.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Could not enable SCTP trace: "Sysctl: unknown OID: net.inet.sctp.sctp_logging" 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, 10 Jun 2008 16:29:00 -0000 Hi, Thanks for the suggestion. I am trying to get real time cwnd data via SCTP logging function (SCTP_LOCAL_TRACE_BUF). I could compile the utilities dump_apple_log and prtcwdlog successfully. But I failed to enable logging trace. Below are the steps I have proceeded: 1. Installed FreeBSD 7.0 2. Build a custom kernel cd /usr/src/sys/i386/conf cp GENERIC /root/CUSTOM_KERNEL_9_6 ln -s /root/CUSTOM_KERNEL_9_6 cd /usr/src make buildkernel KERNCONF=CUSTOM_KERNEL_9_6 3. I found opt_sctp.h in /usr/obj/usr/src/sys/CUSTOM_KERNEL_9_6 along with all sctp binaries here. 4. To see SCTP_LOCAL_TRACE_BUF is already defined or not, I executed the following command: Cd /usr/obj/usr/src/sys/CUSTOM_KERNEL_9_6 nm sctputil.o | grep sctp_log_trace And it didn't show me any symbol. That means SCTP_LOCAL_TRACE_BUF is not defined so far. 5. Added the following line in opt_sctp.h #define SCTP_LOCAL_TRACE_BUF 1 6. Run 'make' to compile sctp with SCTP_LOCAL_TRACE_BUF 7. To see SCTP_LOCAL_TRACE_BUF is compiled or not, again, I executed the following command: nm sctputil.o | grep sctp_log_trace 00000130 T sctp_log_trace Hence, I assumed that sctp is built with SCTP_LOCAL_TRACE_BUF. 8. I installed this custom kernel : Make installkernel KERNCONF=CUSTOM_KERNEL_9_6 9. Reboot and load the new kernel. 10. Tried to enable trace point by: Sysctl -w "net.inet.sctp.sctp_logging=0x00000004" But got:( Sysctl: unknown OID: net.inet.sctp.sctp_logging At this point, I guess that SCTP was not successfully built with SCTP_LOCAL_TRACE_BUF and that's why sysctl is unable to find the OID. Do you have any suggestions how can I build SCTP with SCTP_LOCAL_TRACE_BUF successfully? I would appreciate any help in this regard. Best Regards, Md Sazzadur Rahman Graduate Student, School of Computer Science, University of Oklahoma, Norman, Oklahoma, USA -----Original Message----- From: Randall Stewart [mailto:rrs@cisco.com] Sent: Wednesday, April 16, 2008 9:04 AM To: Rahman, Md Sazzadur Cc: freebsd-net@freebsd.org Subject: Re: A query regarding SCTP congestion control Rahman, Md Sazzadur wrote: > Hi, I would like to get the values of SCTP congestion control > algorithm variables (cwnd, ssthresh, flightsize and pba) from any > SCTP based application in runtime for research purpose. Does any API > exist in SCTP for that? Do I need to dig the SCTP code in kernel to > get the values? There is a socket option to get the cwnd. However, I think what you really want is some of the researchish tracing stuff that SCTP provides. You can actually get a real time trace of the cwnd/flight etc via the various logging functions. You basically must compile this as an option.. have to go look at the options.. And then you can either use ktrace (which I don't recommend since it turns on to much overhead in the kernel) or you can use SCTP_LOCAL_TRACE_BUF This will put it into a piece of memory only for SCTP and not turn on all the other ktrace points. After you enable the logging in your compile you must turn on the logging level.. SCTP_CWND_LOGGING_ENABLE woudl be my recommendation. It gives you a real time up/down growth of the cwnd/flight/rwnd I think I wrote a "how to" somewhere.. let me go look.. R > > I will appreciate any help in this regard. > > Best Regards, Md Sazzadur Rahman Graduate Student, School of Computer > Science, University of Oklahoma, Norman, Oklahoma, USA > > _______________________________________________ > 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" > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 16:51:53 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AE371065673 for ; Tue, 10 Jun 2008 16:51:53 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 67BAA8FC1B for ; Tue, 10 Jun 2008 16:51:53 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2025359wah.3 for ; Tue, 10 Jun 2008 09:51:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=mLVLbQP6D6fy4mLaKkct/rs4Y/3KA2takR6zpJO4U/Y=; b=BpPzdv3n6kFRkPmljXGKmoJ/XnlAtgF/kXKhutu9UOeZ5+p+Tmlt1VpgmMX8MM19aP 8cgmVD1xoHgaJOUzTqO0HA1dzBeUvWzuABcXDgZfFbwfn+m1CKV0VHvtR1v+CMrx7G+w tS0OqkPoS0tSm72KRZnbKLdy1fdoqtgCkD24w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=AqW9yynGCP05ps9t2XQKLoxDCRmsFLIiH++tM6sBxyBaRzdHQ6MgsRyFuVBTUq8BN2 B1AYIHDoM2hSTaXaY1oD6oIfQfaSpa7l4qn/q9Q9BUaZW83Na2idldpL/4H46OZNUgB9 7gYCOFbJFDDg8fqVFqTDnk7UhuIveHsDEYoAw= Received: by 10.115.47.1 with SMTP id z1mr5211645waj.129.1213116713062; Tue, 10 Jun 2008 09:51:53 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Tue, 10 Jun 2008 09:51:53 -0700 (PDT) Message-ID: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> Date: Tue, 10 Jun 2008 09:51:53 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Current" , "FreeBSD Stable List" , "Sam Leffler" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Vlan EVENT patch 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, 10 Jun 2008 16:51:53 -0000 This is a small patch that Sam came up with for me, it will allow drivers to know when a vlan attaches. It is transparent to any code that doesn't want to change, but this will allow my drivers to finally utilize the vlan hardware filter (something Linux has had for ever but we lacked). My test group has done some basic testing of this and it is working great. But we wanted to give any vlan users a chance to see, ask questions, or whatever before its committed. Jack From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 17:30:37 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05D5E1065687 for ; Tue, 10 Jun 2008 17:30:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.freebsd.org (Postfix) with ESMTP id B44428FC25 for ; Tue, 10 Jun 2008 17:30:36 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1279936pyb.10 for ; Tue, 10 Jun 2008 10:30:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=41PC+Mdi7jkKb4JeclWr1DnNU6tg5wr5HbAVnyv4AZc=; b=DGX7P4oSZr9QXUdLcn9R8G5sWF8xLvGmqvVeq6tkCQ58JBVGZHhk/A8UpatIh+mFDm N835sWG6fJdixr9Uytxz4SqZapnDAeJzf9YVv0eGVzTdezzvn/FPFMR5d+QkKNgXkhXB uWspvVn54C+BhmM7E6kzjjT5hztgwU/K/kb0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=q+GY2PopnJORYeqzEq0ZJKcOxWGo8d7L9zVc8R9Q/Tl7xOvHYB3acO9XZsemJMjN3F rZBCKxRkivgYuOZohq9wtjzhxMXNQQQYVmE58UUiLy3H/p7cakehOOL0ZNdtA+fKa2FA LsPEcku5nOXiNA2BJVi4zeM96dQAlLEzWQXiQ= Received: by 10.114.92.2 with SMTP id p2mr5244201wab.223.1213119035228; Tue, 10 Jun 2008 10:30:35 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Tue, 10 Jun 2008 10:30:35 -0700 (PDT) Message-ID: <2a41acea0806101030xa9f0689k663709a4595b1771@mail.gmail.com> Date: Tue, 10 Jun 2008 10:30:35 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Current" , "FreeBSD Stable List" , "Sam Leffler" In-Reply-To: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_32711_23637119.1213119035234" References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> Cc: Subject: Re: Vlan EVENT patch 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, 10 Jun 2008 17:30:37 -0000 ------=_Part_32711_23637119.1213119035234 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/10/08, Jack Vogel wrote: > This is a small patch that Sam came up with for me, it will allow > drivers to know > when a vlan attaches. > > It is transparent to any code that doesn't want to change, but this > will allow my > drivers to finally utilize the vlan hardware filter (something Linux has had > for > ever but we lacked). > > My test group has done some basic testing of this and it is working great. > But we wanted to give any vlan users a chance to see, ask questions, or > whatever before its committed. > > Jack > Sigh, sorry, here's the actual patch :) Jack ------=_Part_32711_23637119.1213119035234 Content-Type: text/x-patch; name=vlan.patch Content-Transfer-Encoding: base64 X-Attachment-Id: file0 Content-Disposition: attachment; filename=vlan.patch LS0tIGlmX3ZsYW4uZGlzdC5jCTIwMDgtMDYtMDQgMDk6MzU6MDUuMDAwMDAwMDAwIC0wNzAwCisr KyBpZl92bGFuLmMJMjAwOC0wNi0wNSAxNDo0ODowNC4wMDAwMDAwMDAgLTA3MDAKQEAgLTEwNjIs NiArMTA2Miw4IEBACiAJaWZwLT5pZl9kcnZfZmxhZ3MgfD0gSUZGX0RSVl9SVU5OSU5HOwogZG9u ZToKIAlUUlVOS19VTkxPQ0sodHJ1bmspOworCWlmIChlcnJvciA9PSAwKQorCQlFVkVOVEhBTkRM RVJfSU5WT0tFKHZsYW5fY29uZmlnLCBwLCBpZnYtPmlmdl90YWcpOwogCVZMQU5fVU5MT0NLKCk7 CiAKIAlyZXR1cm4gKGVycm9yKTsKQEAgLTEwODQsMTIgKzEwODYsMTQgQEAKIAlzdHJ1Y3QgaWZ2 bGFudHJ1bmsgKnRydW5rOwogCXN0cnVjdCB2bGFuX21jX2VudHJ5ICptYzsKIAlzdHJ1Y3QgaWZ2 bGFuICppZnY7CisJc3RydWN0IGlmbmV0ICAqcGFyZW50OwogCWludCBlcnJvcjsKIAogCVZMQU5f TE9DS19BU1NFUlQoKTsKIAogCWlmdiA9IGlmcC0+aWZfc29mdGM7CiAJdHJ1bmsgPSBpZnYtPmlm dl90cnVuazsKKwlwYXJlbnQgPSBQQVJFTlQoaWZ2KTsKIAogCWlmICh0cnVuaykgewogCQlzdHJ1 Y3Qgc29ja2FkZHJfZGwgc2RsOwpAQCAtMTE1Myw2ICsxMTU3LDggQEAKIAlpZnAtPmlmX2xpbmtf c3RhdGUgPSBMSU5LX1NUQVRFX1VOS05PV047CiAJaWZwLT5pZl9kcnZfZmxhZ3MgJj0gfklGRl9E UlZfUlVOTklORzsKIAorCUVWRU5USEFORExFUl9JTlZPS0Uodmxhbl91bmNvbmZpZywgcGFyZW50 LCBpZnYtPmlmdl90YWcpOworCiAJcmV0dXJuICgwKTsKIH0KIAotLS0gZXZlbnRoYW5kbGVyLmRp c3QuaAkyMDA4LTA2LTA1IDA5OjI0OjE2LjAwMDAwMDAwMCAtMDcwMAorKysgZXZlbnRoYW5kbGVy LmgJMjAwOC0wNi0wNSAwOToyNzozNi4wMDAwMDAwMDAgLTA3MDAKQEAgLTE3NSw2ICsxNzUsMTMg QEAKIHR5cGVkZWYgdm9pZCAoKm1vdW50cm9vdF9oYW5kbGVyX3QpKHZvaWQgKik7CiBFVkVOVEhB TkRMRVJfREVDTEFSRShtb3VudHJvb3QsIG1vdW50cm9vdF9oYW5kbGVyX3QpOwogCisvKiBWTEFO IHN0YXRlIGNoYW5nZSBldmVudHMgKi8KK3N0cnVjdCBpZm5ldDsKK3R5cGVkZWYgdm9pZCAoKnZs YW5fY29uZmlnX2ZuKSh2b2lkICosIHN0cnVjdCBpZm5ldCAqLCB1aW50MTZfdCk7Cit0eXBlZGVm IHZvaWQgKCp2bGFuX3VuY29uZmlnX2ZuKSh2b2lkICosIHN0cnVjdCBpZm5ldCAqLCB1aW50MTZf dCk7CitFVkVOVEhBTkRMRVJfREVDTEFSRSh2bGFuX2NvbmZpZywgdmxhbl9jb25maWdfZm4pOwor RVZFTlRIQU5ETEVSX0RFQ0xBUkUodmxhbl91bmNvbmZpZywgdmxhbl91bmNvbmZpZ19mbik7CisK IC8qCiAgKiBQcm9jZXNzIGV2ZW50cwogICogcHJvY2Vzc19mb3JrIGFuZCBleGl0IGhhbmRsZXJz IGFyZSBjYWxsZWQgd2l0aG91dCBHaWFudC4K ------=_Part_32711_23637119.1213119035234-- From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 18:48:36 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64C531065677; Tue, 10 Jun 2008 18:48:36 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3BC438FC0C; Tue, 10 Jun 2008 18:48:36 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (jhb@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5AImang089387; Tue, 10 Jun 2008 18:48:36 GMT (envelope-from jhb@freefall.freebsd.org) Received: (from jhb@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5AImZ9I089383; Tue, 10 Jun 2008 18:48:35 GMT (envelope-from jhb) Date: Tue, 10 Jun 2008 18:48:35 GMT Message-Id: <200806101848.m5AImZ9I089383@freefall.freebsd.org> To: hostmaster@gts.infra-service.ca, jhb@FreeBSD.org, freebsd-net@FreeBSD.org, jhb@FreeBSD.org From: jhb@FreeBSD.org Cc: Subject: Re: kern/122875: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] 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, 10 Jun 2008 18:48:36 -0000 Synopsis: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] State-Changed-From-To: open->patched State-Changed-By: jhb State-Changed-When: Tue Jun 10 18:47:56 UTC 2008 State-Changed-Why: Fix committed to HEAD. Responsible-Changed-From-To: freebsd-net->jhb Responsible-Changed-By: jhb Responsible-Changed-When: Tue Jun 10 18:47:56 UTC 2008 Responsible-Changed-Why: Fix committed to HEAD. http://www.freebsd.org/cgi/query-pr.cgi?pr=122875 From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 19:15:37 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0A14106566B; Tue, 10 Jun 2008 19:15:37 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-service.CA) Received: from fukspam.GTS.NET (fukspam.gts.t-fcn.net [204.138.66.129]) by mx1.freebsd.org (Postfix) with ESMTP id 64CDE8FC12; Tue, 10 Jun 2008 19:15:37 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-service.CA) Received: (using Smail-3.2.0.122-Pre 2005-Nov-17 #1 built 2006-Mar-11) from gts.net ([204.138.66.129:3109]) by fukspam.GTS.NET ([204.138.66.129:25]) via TCP with esmtp (/origin:L/R:inet_hosts/T:inet_zone_smtp/dest:R) id (sender ) (ident using UNIX) for (body size 711, total 1515 bytes); Tue, 10 Jun 2008 15:01:36 -0400 (EDT) Date: Tue, 10 Jun 2008 15:01:34 -0400 (EDT) From: hotlips Internet admin Sender: hostmaster@hotlips.gts.net To: jhb@FreeBSD.org In-Reply-To: <200806101848.m5AImZ9I089383@freefall.freebsd.org> Message-ID: References: <200806101848.m5AImZ9I089383@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@FreeBSD.org Subject: Re: kern/122875: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] 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, 10 Jun 2008 19:15:37 -0000 On Tue, 10 Jun 2008 jhb@FreeBSD.org wrote: |Synopsis: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] | |State-Changed-From-To: open->patched |State-Changed-By: jhb |State-Changed-When: Tue Jun 10 18:47:56 UTC 2008 |State-Changed-Why: |Fix committed to HEAD. | | |Responsible-Changed-From-To: freebsd-net->jhb |Responsible-Changed-By: jhb |Responsible-Changed-When: Tue Jun 10 18:47:56 UTC 2008 |Responsible-Changed-Why: |Fix committed to HEAD. | |http://www.freebsd.org/cgi/query-pr.cgi?pr=122875 will this get propagated to 6.3 & 7.0 ? Thanks, Bruce Becker +1 416 410 0879 GTS Network Administration Toronto, Ont. Email: hostmaster@GTS.Infra-service.CA From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 19:25:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D2EA1065881 for ; Tue, 10 Jun 2008 19:25:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id CD43A8FC14 for ; Tue, 10 Jun 2008 19:25:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m5AJOqZ0064458; Tue, 10 Jun 2008 15:25:11 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: hotlips Internet admin Date: Tue, 10 Jun 2008 15:24:14 -0400 User-Agent: KMail/1.9.7 References: <200806101848.m5AImZ9I089383@freefall.freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806101524.15124.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Tue, 10 Jun 2008 15:25:11 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/7425/Tue Jun 10 13:42:21 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-net@freebsd.org Subject: Re: kern/122875: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] 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, 10 Jun 2008 19:25:18 -0000 On Tuesday 10 June 2008 03:01:34 pm hotlips Internet admin wrote: > On Tue, 10 Jun 2008 jhb@FreeBSD.org wrote: > > |Synopsis: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] > | > |State-Changed-From-To: open->patched > |State-Changed-By: jhb > |State-Changed-When: Tue Jun 10 18:47:56 UTC 2008 > |State-Changed-Why: > |Fix committed to HEAD. > | > | > |Responsible-Changed-From-To: freebsd-net->jhb > |Responsible-Changed-By: jhb > |Responsible-Changed-When: Tue Jun 10 18:47:56 UTC 2008 > |Responsible-Changed-Why: > |Fix committed to HEAD. > | > |http://www.freebsd.org/cgi/query-pr.cgi?pr=122875 > > > will this get propagated to 6.3 & 7.0 ? It will go to RELENG_6 and RELENG_7. The cp_time changes were never made in RELENG_6_3 and RELENG_7_0 so they should not need this change. -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Tue Jun 10 19:45:50 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 738CC1065678; Tue, 10 Jun 2008 19:45:50 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-service.CA) Received: from fukspam.GTS.NET (gts.net [204.138.66.129]) by mx1.freebsd.org (Postfix) with ESMTP id BDC938FC25; Tue, 10 Jun 2008 19:45:49 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-service.CA) Received: (using Smail-3.2.0.122-Pre 2005-Nov-17 #1 built 2006-Mar-11) from gts.net ([204.138.66.129:3164]) by fukspam.GTS.NET ([204.138.66.129:25]) via TCP with esmtp (/origin:L/R:inet_hosts/T:inet_zone_smtp/dest:R) id (sender ) (ident using UNIX) for (body size 1098, total 1992 bytes); Tue, 10 Jun 2008 15:45:47 -0400 (EDT) Date: Tue, 10 Jun 2008 15:45:45 -0400 (EDT) From: hotlips Internet admin Sender: hostmaster@hotlips.gts.net To: John Baldwin In-Reply-To: <200806101524.15124.jhb@freebsd.org> Message-ID: References: <200806101848.m5AImZ9I089383@freefall.freebsd.org> <200806101524.15124.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: kern/122875: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] 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, 10 Jun 2008 19:45:50 -0000 On Tue, 10 Jun 2008, John Baldwin wrote: |On Tuesday 10 June 2008 03:01:34 pm hotlips Internet admin wrote: |> On Tue, 10 Jun 2008 jhb@FreeBSD.org wrote: |> |> |Synopsis: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok |in 7.0-release) [regression] |> | |> |State-Changed-From-To: open->patched |> |State-Changed-By: jhb |> |State-Changed-When: Tue Jun 10 18:47:56 UTC 2008 |> |State-Changed-Why: |> |Fix committed to HEAD. |> | |> | |> |Responsible-Changed-From-To: freebsd-net->jhb |> |Responsible-Changed-By: jhb |> |Responsible-Changed-When: Tue Jun 10 18:47:56 UTC 2008 |> |Responsible-Changed-Why: |> |Fix committed to HEAD. |> | |> |http://www.freebsd.org/cgi/query-pr.cgi?pr=122875 |> |> will this get propagated to 6.3 & 7.0 ? | |It will go to RELENG_6 and RELENG_7. The cp_time changes were never made in |RELENG_6_3 and RELENG_7_0 so they should not need this change. perfect - this will make my life a bit easier when it's in place :) Thanks, Bruce Becker +1 416 410 0879 GTS Network Administration Toronto, Ont. Email: hostmaster@GTS.Infra-service.CA From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 02:51:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DD1B106567B for ; Wed, 11 Jun 2008 02:51:11 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 0267F8FC17 for ; Wed, 11 Jun 2008 02:51:10 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 6789 invoked by uid 89); 11 Jun 2008 02:51:44 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 11 Jun 2008 02:51:44 -0000 Message-ID: <484F3E1B.9050104@ibctech.ca> Date: Tue, 10 Jun 2008 22:53:15 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Throughput rate testing configurations 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, 11 Jun 2008 02:51:11 -0000 Hi everyone, I see what I believe to be less-than-adequate communication performance between many devices in parts of our network. Can someone recommend software (and config recommendations if possible) that I can implement to test both throughput and pps reliably, initially/primarily in a simple host-sw-host configuration? Perhaps I'm asking too much, but I'd like to have something that can push the link to it's absolute maximum capacity (for now, up to 1Gbps) for a long sustained time, that I can just walk away from and let it do it's work, and review the reports later where it had to scale down due to errors. What I'm really trying to achieve is: - test the link between hosts alone - throw in a switch - test the link while r/w to disk - test the link while r/w to GELI disk - test the link with oddball MTU sizes ...and see what impact occurs in each scenario, to be able to tell where things can be improved. All machines that will be part of this test will be either 6.3 or 7. Steve From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 07:06:56 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F7F910656A9 for ; Wed, 11 Jun 2008 07:06:56 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id 4F42B8FC0A for ; Wed, 11 Jun 2008 07:06:54 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 39503 invoked by uid 0); 11 Jun 2008 10:40:17 +0400 Received: from 89.222.147.9 ([89.222.147.9]) by techno.sub.ru ([88.212.205.2]) with ESMTP via TCP; 11 Jun 2008 06:40:17 -0000 Message-ID: <484F7339.7040400@webmail.sub.ru> Date: Wed, 11 Jun 2008 10:39:53 +0400 From: Alex Povolotsky User-Agent: Thunderbird 2.0.0.4 (X11/20070709) MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: mpd, nat, netflow: does not work for me 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, 11 Jun 2008 07:06:56 -0000 Hello! I'm trying to use mpd 5.1, on FreeBSD 6.2, and got some really strange problems. 1. NAT. [10:37] services-new:/<2>etc/mpd5 # grep nat /usr/local/etc/mpd5/mpd.conf set nat address 81.195.122.86 set iface enable nat in web interface, option for interface includes "nat enable" NO address translation at all. 2. Netflow set iface enable netflow-out set netflow peer PEER-IP-ADDR 8787 netflow-out, of course, is labeled as "enable" MPD even sends some netflow data (1464 bytes packet every 15-20 minutes, it is definitely insufficient to send required data), collector receives it and stores nothing. Maybe someone could help? Alex. From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 07:35:25 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A1E4106566B for ; Wed, 11 Jun 2008 07:35:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4C9808FC1A for ; Wed, 11 Jun 2008 07:35:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3591145rvf.43 for ; Wed, 11 Jun 2008 00:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=j5iGNU9J2VOCURcUab29KfFq5Rv7H7zjHUGxb8kl2KM=; b=pRL/88RrzejejCmgzNKxteM3u7pqbxdcreYYo2kYTG/AbwNxc0OH6zYgZwvYHhPFHb XGJutPS+uF7RQ3h6U1dpHEZ9/dk67eVzGo1pCNOfvsKeOZTH7PM0eL0efSyVjpaT5tWg zqOni0TmAb19hAq2nmsTxWo7YpzGnxS6WW3Wg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ixJljoerE+Ocmxj5tJqY+we08zaiJSLe/67Hd1zsR6ASIRI+ZM8pfxaUd8Wg7wcERr quzuzfQ7jE1F+HNJQS6w6njbAhss3FOrXTSdB+Q8LO9tVXGS+9BbuuTrmJoUcon8PpvA PGxV4dfX5O7umivw4VW2K8zc+RFX9Kl2Mz5vY= Received: by 10.140.144.1 with SMTP id r1mr3631680rvd.199.1213169725142; Wed, 11 Jun 2008 00:35:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm18085938rvf.9.2008.06.11.00.35.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 00:35:24 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m5B7XFqJ004608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 16:33:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5B7XEGi004607; Wed, 11 Jun 2008 16:33:14 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 11 Jun 2008 16:33:14 +0900 From: Pyun YongHyeon To: Jack Vogel Message-ID: <20080611073313.GF3529@cdnetworks.co.kr> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Vlan EVENT patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 07:35:25 -0000 On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > This is a small patch that Sam came up with for me, it will allow > drivers to know > when a vlan attaches. > > It is transparent to any code that doesn't want to change, but this > will allow my > drivers to finally utilize the vlan hardware filter (something Linux has had for > ever but we lacked). > Just curious, is there any rule how to use that new capability? Because drivers will receive events whenever VLAN tags are added/removed they would know how to act for these events. If promiscuous mode is on for interface, driver should not filter any VLAN tagged frames, right? If users want to disable VLAN hardware filtering feature what is best way to perform this? Introducing a new flag like IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? I guess VIA Rhine III also have VLAN hardware filtering capability so it would be even better if we have a way to share common part. > My test group has done some basic testing of this and it is working great. > But we wanted to give any vlan users a chance to see, ask questions, or > whatever before its committed. > > Jack -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 13:01:35 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75A68106567A; Wed, 11 Jun 2008 13:01:35 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 49D6D8FC1F; Wed, 11 Jun 2008 13:01:35 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5BD1ZHw037574; Wed, 11 Jun 2008 13:01:35 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5BD1ZuU037570; Wed, 11 Jun 2008 13:01:35 GMT (envelope-from gavin) Date: Wed, 11 Jun 2008 13:01:35 GMT Message-Id: <200806111301.m5BD1ZuU037570@freefall.freebsd.org> To: takeda@takeda.tk, gavin@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/122145: error while compiling with device ath_rate_amrr 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, 11 Jun 2008 13:01:35 -0000 Synopsis: error while compiling with device ath_rate_amrr State-Changed-From-To: open->patched State-Changed-By: gavin State-Changed-When: Wed Jun 11 12:59:14 UTC 2008 State-Changed-Why: Mark as patched, this is fixed in HEAD and RELENG_7 http://www.freebsd.org/cgi/query-pr.cgi?pr=122145 From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 16:52:24 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E768C1065670 for ; Wed, 11 Jun 2008 16:52:24 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id B19A98FC0C for ; Wed, 11 Jun 2008 16:52:24 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2361191wah.3 for ; Wed, 11 Jun 2008 09:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=4CZz+RjpATxrplvNyIDq0c/BsrSqyJxtDzH1/elFkcE=; b=j/BdZ0aTo09vrD2INYsCBuVOxdHZfRSiBgzzc7jtPM5njjZj2QfJlu0Kq9Yyjdugk2 F1IwMEM1ht3Tl7Kcjb1qDp+xGYqYMSV39E+Qzc61q2uCFaku9P30dtKotxSikb5PLCcF PS4WLIQoPCZbNsK/Loq6n+PWsZxy3DQyF8k9M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=hWXuYB8G5lFCkHy9KJj+ECuRWL3C/6m2+qPolU8nAbvPNctvTlQIOyBR47fj2zUmFL SIeBub6K/xWO96NrvnOUFQ8ZhAlBIkSbKjBdP8AIeDlT2L0G7/lfejg3wuw3uPl5iGNA tErC8neptakdX2lYccZgeVdEUUMp1x4xk+8x4= Received: by 10.114.132.5 with SMTP id f5mr16189wad.201.1213203144069; Wed, 11 Jun 2008 09:52:24 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Wed, 11 Jun 2008 09:52:23 -0700 (PDT) Message-ID: <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> Date: Wed, 11 Jun 2008 09:52:23 -0700 From: "Jack Vogel" To: pyunyh@gmail.com In-Reply-To: <20080611073313.GF3529@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Vlan EVENT patch 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, 11 Jun 2008 16:52:25 -0000 On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon wrote: > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > > This is a small patch that Sam came up with for me, it will allow > > drivers to know > > when a vlan attaches. > > > > It is transparent to any code that doesn't want to change, but this > > will allow my > > drivers to finally utilize the vlan hardware filter (something Linux has had for > > ever but we lacked). > > > > Just curious, is there any rule how to use that new capability? > Because drivers will receive events whenever VLAN tags are > added/removed they would know how to act for these events. If > promiscuous mode is on for interface, driver should not filter any > VLAN tagged frames, right? > If users want to disable VLAN hardware filtering feature what is > best way to perform this? Introducing a new flag like > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? > I guess VIA Rhine III also have VLAN hardware filtering capability > so it would be even better if we have a way to share common part. All the patch does is have the vlan driver generate events when it attaches or detaches from a NIC, there are no rules, however I can tell you what I'm coding into this in the Intel drivers. The way it works is the driver registers a callback for each event, I will call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. Right now, the drivers just generically enable VLAN capability because there is never a trigger to know IF and WHEN you need to do so, but with this change the VLAN capability will only get turned on by the registration routine. Most significantly, now when the pseudo device it gives the driver the VLAN tag, this will mean the driver will be able from the start to use the VFTA, the hardware filter, for each vlan attach the driver will add the ID into this table. The unregister event will turn the table entry off, and if this is the last VLAN being detached it will then disable the features. Oh yes, these routines will also take care of the size change of the frame due to the tag. I already have the changes in place in the igb drive, and they are working great. I do not understand why you think you need a flag to disable this, yes it could be done, but why? If you need to do some sort of debugging won't a system not using vlans and in promiscuous mode do just fine? It just seems to violate the whole reason for doing vlans in the first place, however perhaps I am missing something? I do not believe the Linux driver has some way to disable use of the table but I'll double check on that. Remember, this change requires NO driver changes unless they wish to take advantage of the ability. Cheers, Jack From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 17:18:14 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 636971065673 for ; Wed, 11 Jun 2008 17:18:14 +0000 (UTC) (envelope-from security@jim-liesl.org) Received: from smtp2.mc.surewest.net (qsmtp.mc.surewest.net [66.60.130.145]) by mx1.freebsd.org (Postfix) with SMTP id 3ADE78FC2A for ; Wed, 11 Jun 2008 17:18:14 +0000 (UTC) (envelope-from security@jim-liesl.org) Received: (qmail 1293 invoked from network); 11 Jun 2008 09:51:32 -0700 Received: by simscan 1.1.0 ppid: 1289, pid: 1290, t: 0.1989s scanners: regex: 1.1.0 attach: 1.1.0 spam: 3.1.7-deb X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on smtp2.surewest.net. X-Spam-Level: X-Spam-Status: No, score=0.0 required=10.0 tests=none autolearn=disabled version=3.1.7-deb X-Spam-CMAE-Analysis: v=1.0 c=1 a=_gmmSJ4pHMQAR5b-KBAA:9 a=EAXpBrJZP6GKjT1duwRDP9IX7b8A:4 a=ufO146cb3fEA:10 Received: from unknown (HELO smtp.jim-liesl.org) (66.60.173.44) by smtp2 with SMTP; 11 Jun 2008 09:51:32 -0700 Received: from smtp.jim-liesl.org (localhost.static.surewest.net [127.0.0.1]) by smtp.jim-liesl.org (Postfix) with ESMTP id A56D05C6E; Wed, 11 Jun 2008 09:51:31 -0700 (PDT) Received: from [IPv6:::1] (daemon.static.surewest.net [192.168.1.15]) by smtp.jim-liesl.org (Postfix) with ESMTP id 490575C5A; Wed, 11 Jun 2008 09:51:27 -0700 (PDT) Message-ID: <4850028F.6090103@jim-liesl.org> Date: Wed, 11 Jun 2008 09:51:27 -0700 From: security User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Steve Bertrand References: <484F3E1B.9050104@ibctech.ca> In-Reply-To: <484F3E1B.9050104@ibctech.ca> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-net@freebsd.org Subject: Re: Throughput rate testing configurations 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, 11 Jun 2008 17:18:14 -0000 Steve Bertrand wrote: > Hi everyone, > > I see what I believe to be less-than-adequate communication > performance between many devices in parts of our network. > > Can someone recommend software (and config recommendations if > possible) that I can implement to test both throughput and pps > reliably, initially/primarily in a simple host-sw-host configuration? > > Perhaps I'm asking too much, but I'd like to have something that can > push the link to it's absolute maximum capacity (for now, up to 1Gbps) > for a long sustained time, that I can just walk away from and let it > do it's work, and review the reports later where it had to scale down > due to errors. > > What I'm really trying to achieve is: > > - test the link between hosts alone > - throw in a switch > - test the link while r/w to disk > - test the link while r/w to GELI disk > - test the link with oddball MTU sizes > Iperf or netperf are probably what you're looking for. Both try real had NOT to tweak other subsystems while they run, so if you want to throw disk activity in, you'll need to run another tool or roll your own to create disk activity. You probably don't want to run them for extended periods in a production network. Depending on the adapters at each end, you may or may not be able to drive the link to saturation or alter frame size. The Intel adapters I've seen allow jumbo frames, and generally good performance (as opposed to say the realtek). It's also useful to have a managed switch in between so you can look at the counters on it. jim From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 20:20:43 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D42B41065680 for ; Wed, 11 Jun 2008 20:20:43 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog13.obsmtp.com (s200aog13.obsmtp.com [207.126.144.127]) by mx1.freebsd.org (Postfix) with SMTP id EBE918FC19 for ; Wed, 11 Jun 2008 20:20:42 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([63.174.175.251]) by eu1sys200aob013.postini.com ([207.126.147.11]) with SMTP; Wed, 11 Jun 2008 20:20:41 UTC Received: from [172.17.3.47] (unknown [172.17.3.47]) by bbbx3.usdmm.com (Postfix) with ESMTP id 71251FD02E; Wed, 11 Jun 2008 20:01:46 +0000 (UTC) Message-ID: <48502F2C.7090505@tomjudge.com> Date: Wed, 11 Jun 2008 15:01:48 -0500 From: Tom Judge User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Bill Moran References: <20080610120222.9e2760fe.wmoran@collaborativefusion.com> In-Reply-To: <20080610120222.9e2760fe.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: R J , freebsd-net@freebsd.org Subject: Re: tcpdump/snort to capture chat sessions 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, 11 Jun 2008 20:20:43 -0000 Bill Moran wrote: > In response to R J : > >> I am trying to use tcpdump (or snort, but they are both behaving the same >> in this case) to capture all the lines or contents of an msn >> chat session, the actual conversation. I am getting partial output; i.e, >> I'll only get half of a sentence, and I don't see the rest of the lines. >> And ofcourse, alot of it seems to be hex or obfuscated html? >> >> What switches do I need to capture the entire lines of text? > > Don't know about snort, but with tcpdump use -s0 > This is a good start however you are not guaranteed to see the whole chat message in a single TCP packet. If you are looking for something more advanced you will have to write a program around pcap/bpf or similar to read the TCP stream. Tom J From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 20:41:35 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3A9D10656BE; Wed, 11 Jun 2008 20:41:35 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-service.CA) Received: from fukspam.GTS.NET (hotlips.gts.net [204.138.66.129]) by mx1.freebsd.org (Postfix) with ESMTP id 3225C8FC12; Wed, 11 Jun 2008 20:41:34 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-service.CA) Received: (using Smail-3.2.0.122-Pre 2005-Nov-17 #1 built 2006-Mar-11) from gts.net ([204.138.66.129:4135]) by fukspam.GTS.NET ([204.138.66.129:25]) via TCP with esmtp (/origin:L/R:inet_hosts/T:inet_zone_smtp/dest:R) id (sender ) (ident using UNIX) for (body size 1531, total 2479 bytes); Wed, 11 Jun 2008 16:41:32 -0400 (EDT) Date: Wed, 11 Jun 2008 16:41:30 -0400 (EDT) From: hotlips Internet admin Sender: hostmaster@hotlips.gts.net To: John Baldwin In-Reply-To: <200806101524.15124.jhb@freebsd.org> Message-ID: References: <200806101848.m5AImZ9I089383@freefall.freebsd.org> <200806101524.15124.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/122875: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] 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, 11 Jun 2008 20:41:35 -0000 On Tue, 10 Jun 2008, John Baldwin wrote: |On Tuesday 10 June 2008 03:01:34 pm hotlips Internet admin wrote: |> On Tue, 10 Jun 2008 jhb@FreeBSD.org wrote: |> |> |Synopsis: [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stable (works ok in 7.0-release) [regression] |> | |> |State-Changed-From-To: open->patched |> |State-Changed-By: jhb |> |State-Changed-When: Tue Jun 10 18:47:56 UTC 2008 |> |State-Changed-Why: |> |Fix committed to HEAD. |> | |> |Responsible-Changed-From-To: freebsd-net->jhb |> |Responsible-Changed-By: jhb |> |Responsible-Changed-When: Tue Jun 10 18:47:56 UTC 2008 |> |Responsible-Changed-Why: |> |Fix committed to HEAD. |> | |> |http://www.freebsd.org/cgi/query-pr.cgi?pr=122875 |> |> will this get propagated to 6.3 & 7.0 ? | |It will go to RELENG_6 and RELENG_7. The cp_time changes were never made in |RELENG_6_3 and RELENG_7_0 so they should not need this change. ok, I'm somewhat confused. It seems the patch is to rpc.rstatd, and not to src/sys/kern/kern_clock.c please note that a patch to kern_clock.c for RELENG_6 seems to have been committed on June 3 (but not for RELENG_7 ??!) also please note that the patch shown below has been in the queue for quite a while now without any action, so further patches to rpc.rstatd should take its fixes into account (since it's rather broken in general without them): http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92412 Bruce Becker +1 416 410 0879 GTS Network Administration Toronto, Ont. Email: hostmaster@GTS.Infra-service.CA From owner-freebsd-net@FreeBSD.ORG Wed Jun 11 20:42:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFC96106564A for ; Wed, 11 Jun 2008 20:42:22 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 947818FC23 for ; Wed, 11 Jun 2008 20:42:22 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (vanquish.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.162]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Wed, 11 Jun 2008 16:42:21 -0400 id 00056428.485038AD.0001210C Date: Wed, 11 Jun 2008 16:41:25 -0400 From: Bill Moran To: Tom Judge Message-Id: <20080611164125.ac5b7312.wmoran@collaborativefusion.com> In-Reply-To: <48502F2C.7090505@tomjudge.com> References: <20080610120222.9e2760fe.wmoran@collaborativefusion.com> <48502F2C.7090505@tomjudge.com> Organization: Collaborative Fusion X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: R J , freebsd-net@freebsd.org Subject: Re: tcpdump/snort to capture chat sessions 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, 11 Jun 2008 20:42:23 -0000 In response to Tom Judge : > Bill Moran wrote: > > In response to R J : > > > >> I am trying to use tcpdump (or snort, but they are both behaving the same > >> in this case) to capture all the lines or contents of an msn > >> chat session, the actual conversation. I am getting partial output; i.e, > >> I'll only get half of a sentence, and I don't see the rest of the lines. > >> And ofcourse, alot of it seems to be hex or obfuscated html? > >> > >> What switches do I need to capture the entire lines of text? > > > > Don't know about snort, but with tcpdump use -s0 > > > This is a good start however you are not guaranteed to see the whole > chat message in a single TCP packet. If you are looking for something > more advanced you will have to write a program around pcap/bpf or > similar to read the TCP stream. He could use wireshark. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023 From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 00:11:54 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3F56106567B for ; Thu, 12 Jun 2008 00:11:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id 652348FC23 for ; Thu, 12 Jun 2008 00:11:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4045366rvf.43 for ; Wed, 11 Jun 2008 17:11:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+liliLsBgAr2ccjerdXDwDsBUZbdULe8sqQjoUiiA9w=; b=oYxeOVt9Y0FeHwoQ0O7jn+scK0RJOzxJmYwnlneDaV8J9qSf3j1+u1YXaGjk3aLOVj FmQzHYRHP8N7zVhZgA4CqYvsAverCng1KVD8Svwh0XP9lpVbxjlWhEp0ON4ZcAa5HY1O 9aaUnjrmgm09QlEWOcLwHyxZP6CjewgFGDaHQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=kgvGrmg9IWd3yOAv80ytbPBk/mKmaaGu4NMueQLuaUtTXLBeVK6O7kAaKFTyuhohQB 0bZ2CuM2qaI90f5BrQrTrXeRiWoe/lPbwOpVp2gJRTOZGOH/bMkJ6SxvXp/OV3Ebp2A7 pBGpGhD3zEkU2V62vDnZpUtaW8aXhbj9nhzrM= Received: by 10.141.71.14 with SMTP id y14mr468893rvk.24.1213229513601; Wed, 11 Jun 2008 17:11:53 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm686167rvf.9.2008.06.11.17.11.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 17:11:52 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m5C09iEU007424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Jun 2008 09:09:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5C09h3E007423; Thu, 12 Jun 2008 09:09:43 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 12 Jun 2008 09:09:43 +0900 From: Pyun YongHyeon To: Jack Vogel Message-ID: <20080612000943.GA7250@cdnetworks.co.kr> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Vlan EVENT patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 00:11:54 -0000 On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon wrote: > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > > > This is a small patch that Sam came up with for me, it will allow > > > drivers to know > > > when a vlan attaches. > > > > > > It is transparent to any code that doesn't want to change, but this > > > will allow my > > > drivers to finally utilize the vlan hardware filter (something Linux has had for > > > ever but we lacked). > > > > > > > Just curious, is there any rule how to use that new capability? > > Because drivers will receive events whenever VLAN tags are > > added/removed they would know how to act for these events. If > > promiscuous mode is on for interface, driver should not filter any > > VLAN tagged frames, right? > > If users want to disable VLAN hardware filtering feature what is > > best way to perform this? Introducing a new flag like > > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? > > I guess VIA Rhine III also have VLAN hardware filtering capability > > so it would be even better if we have a way to share common part. > > All the patch does is have the vlan driver generate events when it attaches > or detaches from a NIC, there are no rules, however I can tell you what > I'm coding into this in the Intel drivers. > > The way it works is the driver registers a callback for each event, I will > call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. > > Right now, the drivers just generically enable VLAN capability because > there is never a trigger to know IF and WHEN you need to do so, but > with this change the VLAN capability will only get turned on by the > registration routine. > > Most significantly, now when the pseudo device it gives the driver > the VLAN tag, this will mean the driver will be able from the start > to use the VFTA, the hardware filter, for each vlan attach the driver > will add the ID into this table. > > The unregister event will turn the table entry off, and if this is the > last VLAN being detached it will then disable the features. > > Oh yes, these routines will also take care of the size change of > the frame due to the tag. I already have the changes in place in > the igb drive, and they are working great. > > I do not understand why you think you need a flag to disable this, > yes it could be done, but why? If you need to do some sort of > debugging won't a system not using vlans and in promiscuous > mode do just fine? > I guess this would be the same reason why FreeBSD have a way to disable checksum offload for buggy hardware. Diabling all hardware VLAN assistance due to broken VLAN filtering doesn't look right. > It just seems to violate the whole reason for doing vlans in the > first place, however perhaps I am missing something? I do not > believe the Linux driver has some way to disable use of the table > but I'll double check on that. > > Remember, this change requires NO driver changes unless they > wish to take advantage of the ability. Yes. > > Cheers, > > Jack Thanks. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 02:41:40 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73BB0106566B for ; Thu, 12 Jun 2008 02:41:40 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1FEA38FC2B for ; Thu, 12 Jun 2008 02:41:39 +0000 (UTC) (envelope-from sam@errno.com) Received: from Macintosh-4.local ([10.0.0.194]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m5C2GeWC004505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 19:16:40 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <48508708.50903@errno.com> Date: Wed, 11 Jun 2008 19:16:40 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: pyunyh@gmail.com References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> <20080612000943.GA7250@cdnetworks.co.kr> In-Reply-To: <20080612000943.GA7250@cdnetworks.co.kr> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: "freebsd-net@freebsd.org" , Jack Vogel Subject: Re: Vlan EVENT patch 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, 12 Jun 2008 02:41:40 -0000 [trimming cc list to reduce spamage] Pyun YongHyeon wrote: > On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: > > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon wrote: > > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > > > > This is a small patch that Sam came up with for me, it will allow > > > > drivers to know > > > > when a vlan attaches. > > > > > > > > It is transparent to any code that doesn't want to change, but this > > > > will allow my > > > > drivers to finally utilize the vlan hardware filter (something Linux has had for > > > > ever but we lacked). > > > > > > > > > > Just curious, is there any rule how to use that new capability? > > > Because drivers will receive events whenever VLAN tags are > > > added/removed they would know how to act for these events. If > > > promiscuous mode is on for interface, driver should not filter any > > > VLAN tagged frames, right? > > > If users want to disable VLAN hardware filtering feature what is > > > best way to perform this? Introducing a new flag like > > > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? > > > I guess VIA Rhine III also have VLAN hardware filtering capability > > > so it would be even better if we have a way to share common part. > > > > All the patch does is have the vlan driver generate events when it attaches > > or detaches from a NIC, there are no rules, however I can tell you what > > I'm coding into this in the Intel drivers. > > > > The way it works is the driver registers a callback for each event, I will > > call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. > > > > Right now, the drivers just generically enable VLAN capability because > > there is never a trigger to know IF and WHEN you need to do so, but > > with this change the VLAN capability will only get turned on by the > > registration routine. > > > > Most significantly, now when the pseudo device it gives the driver > > the VLAN tag, this will mean the driver will be able from the start > > to use the VFTA, the hardware filter, for each vlan attach the driver > > will add the ID into this table. > > > > The unregister event will turn the table entry off, and if this is the > > last VLAN being detached it will then disable the features. > > > > Oh yes, these routines will also take care of the size change of > > the frame due to the tag. I already have the changes in place in > > the igb drive, and they are working great. > > > > I do not understand why you think you need a flag to disable this, > > yes it could be done, but why? If you need to do some sort of > > debugging won't a system not using vlans and in promiscuous > > mode do just fine? > > > > I guess this would be the same reason why FreeBSD have a way to > disable checksum offload for buggy hardware. Diabling all hardware > VLAN assistance due to broken VLAN filtering doesn't look right. > > > It just seems to violate the whole reason for doing vlans in the > > first place, however perhaps I am missing something? I do not > > believe the Linux driver has some way to disable use of the table > > but I'll double check on that. > > > > Remember, this change requires NO driver changes unless they > > wish to take advantage of the ability. > > Yes. > > > > > Cheers, > > > > Jack > > Thanks. Sounds like there needs to be a h/w vlan assist capability bit that controls this in the driver. Then you'd have a way to disable via ifconfig w/ a trivial mod. Sam From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 03:49:04 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68FC71065685 for ; Thu, 12 Jun 2008 03:49:04 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 3363C8FC0C for ; Thu, 12 Jun 2008 03:48:58 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2512351wah.3 for ; Wed, 11 Jun 2008 20:48:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=F5PU0IctPAOEDX72iZWs+L0cpMVYx8DKhM+q9qkbiiY=; b=JLl8KQZPJk8/koU0YeXu3GJtxbO8pTONMwmHm4tAG4ZWeO4HPigr3gpUo79dBA1txJ iVF8lFzBe1hjX4u1dFAD8c+gIjD6YQ+kOErTiiyRXFY3Gin4pC5Bh2Y9qnoy3Dw50nRG psVweYNeNUA8cUsKl5MbdoOvqKbrOxp/T//xg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XV15aKzuOr/cNkZx+f2fCfoBfvZsy5AV7OMRFPaSl8w1l3uXGOSZ80fDop91p+sNHX Mmot0KLpWxMHZUc3Cc3ruiRe5rYMZ8Iq5LXiQJhCFmkJK3G138uNPP3QO4JJUa4NZl88 a9i1o56AQukibUKXnGUVBjbzhwCvqlYUV12jY= Received: by 10.114.181.1 with SMTP id d1mr904516waf.3.1213242538475; Wed, 11 Jun 2008 20:48:58 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Wed, 11 Jun 2008 20:48:58 -0700 (PDT) Message-ID: <2a41acea0806112048g60084f72o4391701ba242442@mail.gmail.com> Date: Wed, 11 Jun 2008 20:48:58 -0700 From: "Jack Vogel" To: "Sam Leffler" In-Reply-To: <48508708.50903@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> <20080612000943.GA7250@cdnetworks.co.kr> <48508708.50903@errno.com> Cc: pyunyh@gmail.com, "freebsd-net@freebsd.org" Subject: Re: Vlan EVENT patch 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, 12 Jun 2008 03:49:04 -0000 On Wed, Jun 11, 2008 at 7:16 PM, Sam Leffler wrote: > [trimming cc list to reduce spamage] > > Pyun YongHyeon wrote: >> >> On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: >> > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon >> wrote: >> > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: >> > > > This is a small patch that Sam came up with for me, it will allow >> > > > drivers to know >> > > > when a vlan attaches. >> > > > >> > > > It is transparent to any code that doesn't want to change, but >> this >> > > > will allow my >> > > > drivers to finally utilize the vlan hardware filter (something >> Linux has had for >> > > > ever but we lacked). >> > > > >> > > >> > > Just curious, is there any rule how to use that new capability? >> > > Because drivers will receive events whenever VLAN tags are >> > > added/removed they would know how to act for these events. If >> > > promiscuous mode is on for interface, driver should not filter any >> > > VLAN tagged frames, right? >> > > If users want to disable VLAN hardware filtering feature what is >> > > best way to perform this? Introducing a new flag like >> > > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? >> > > I guess VIA Rhine III also have VLAN hardware filtering capability >> > > so it would be even better if we have a way to share common part. >> > > All the patch does is have the vlan driver generate events when it >> attaches >> > or detaches from a NIC, there are no rules, however I can tell you what >> > I'm coding into this in the Intel drivers. >> > > The way it works is the driver registers a callback for each event, >> I will >> > call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. >> > > Right now, the drivers just generically enable VLAN capability >> because >> > there is never a trigger to know IF and WHEN you need to do so, but >> > with this change the VLAN capability will only get turned on by the >> > registration routine. >> > > Most significantly, now when the pseudo device it gives the driver >> > the VLAN tag, this will mean the driver will be able from the start >> > to use the VFTA, the hardware filter, for each vlan attach the driver >> > will add the ID into this table. >> > > The unregister event will turn the table entry off, and if this is >> the >> > last VLAN being detached it will then disable the features. >> > > Oh yes, these routines will also take care of the size change of >> > the frame due to the tag. I already have the changes in place in >> > the igb drive, and they are working great. >> > > I do not understand why you think you need a flag to disable this, >> > yes it could be done, but why? If you need to do some sort of >> > debugging won't a system not using vlans and in promiscuous >> > mode do just fine? >> > >> I guess this would be the same reason why FreeBSD have a way to >> disable checksum offload for buggy hardware. Diabling all hardware >> VLAN assistance due to broken VLAN filtering doesn't look right. >> >> > It just seems to violate the whole reason for doing vlans in the >> > first place, however perhaps I am missing something? I do not >> > believe the Linux driver has some way to disable use of the table >> > but I'll double check on that. >> > > Remember, this change requires NO driver changes unless they >> > wish to take advantage of the ability. >> >> Yes. >> >> > > Cheers, >> > > Jack >> >> Thanks. > > Sounds like there needs to be a h/w vlan assist capability bit that controls > this in the driver. Then you'd have a way to disable via ifconfig w/ a > trivial mod. I don't want to create stuff in ifconfig when I'm not convinced of the need. If there were, as he says, 'buggy hardware', specifically buggy Intel hardware, then either our drivers would have had special errata or workarounds in it for that, but none of the OS drivers have any special code for issues involving VFTA (the filter) or other VLAN controlling components that I am aware of. If there are other network drivers that are buggy in this regard then why encumber the generic interface due to that, let the drivers deal with it, via sysctl or something of the sort. There are enough real cases of hardware problems we need to address in code that I don't just want to modify code on the mere theoretical possibility of such. How bout this, we put the change into HEAD, I add support as I've planned into the em and igb drivers, and then we let them get tested, if a real problem comes up, THEN we worry about adding special case code, how's that? Regards, Jack From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 04:07:04 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC97A1065679 for ; Thu, 12 Jun 2008 04:07:03 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id AB3408FC14 for ; Thu, 12 Jun 2008 04:07:03 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4128133rvf.43 for ; Wed, 11 Jun 2008 21:07:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=wgoEYaIuQaaDQbmcAoKUJALlBolXjKOV3XN43o6oTrY=; b=QKcp6BuumVMni+cYU75Ga5BoPFMyFEwuvuKdv5TUzP1hVOVKWXq0F5gxPX0ua/1ueQ k2ZCaqxjuVu9C6Bw/Amn6A8lDgN7jYam8/OA1AVAIpBqibWIrm8ikiNP7QZe19uH5uBI nc2AukQjc/KCCIQbdIOVdCGbiNsKD3/u53Wl0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=kMsguQmUAQP2BHTtVcHvzXme/FoQyTrULrtnmPqe03hPiwdAwUQ1aXTeTLO9X91TLS sDEqUUNsV8Pzfg02hTJvYJdi7xaMWylZ1kft/Y1nG9ajzC8staYy4MhVEUyYOtANKudA esfPKHH54K9irQsbhfrby1YuHG7pEDyVU3Yb8= Received: by 10.140.131.11 with SMTP id e11mr506011rvd.234.1213243623109; Wed, 11 Jun 2008 21:07:03 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id f21sm984146rvb.0.2008.06.11.21.07.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 21:07:02 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m5C44rFZ008103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Jun 2008 13:04:53 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5C44q48008102; Thu, 12 Jun 2008 13:04:52 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 12 Jun 2008 13:04:52 +0900 From: Pyun YongHyeon To: Jack Vogel Message-ID: <20080612040452.GE7250@cdnetworks.co.kr> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> <20080612000943.GA7250@cdnetworks.co.kr> <48508708.50903@errno.com> <2a41acea0806112048g60084f72o4391701ba242442@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0806112048g60084f72o4391701ba242442@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: "freebsd-net@freebsd.org" Subject: Re: Vlan EVENT patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 04:07:04 -0000 On Wed, Jun 11, 2008 at 08:48:58PM -0700, Jack Vogel wrote: > On Wed, Jun 11, 2008 at 7:16 PM, Sam Leffler wrote: > > [trimming cc list to reduce spamage] > > > > Pyun YongHyeon wrote: > >> > >> On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: > >> > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon > >> wrote: > >> > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > >> > > > This is a small patch that Sam came up with for me, it will allow > >> > > > drivers to know > >> > > > when a vlan attaches. > >> > > > > >> > > > It is transparent to any code that doesn't want to change, but > >> this > >> > > > will allow my > >> > > > drivers to finally utilize the vlan hardware filter (something > >> Linux has had for > >> > > > ever but we lacked). > >> > > > > >> > > > >> > > Just curious, is there any rule how to use that new capability? > >> > > Because drivers will receive events whenever VLAN tags are > >> > > added/removed they would know how to act for these events. If > >> > > promiscuous mode is on for interface, driver should not filter any > >> > > VLAN tagged frames, right? > >> > > If users want to disable VLAN hardware filtering feature what is > >> > > best way to perform this? Introducing a new flag like > >> > > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? > >> > > I guess VIA Rhine III also have VLAN hardware filtering capability > >> > > so it would be even better if we have a way to share common part. > >> > > All the patch does is have the vlan driver generate events when it > >> attaches > >> > or detaches from a NIC, there are no rules, however I can tell you what > >> > I'm coding into this in the Intel drivers. > >> > > The way it works is the driver registers a callback for each event, > >> I will > >> > call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. > >> > > Right now, the drivers just generically enable VLAN capability > >> because > >> > there is never a trigger to know IF and WHEN you need to do so, but > >> > with this change the VLAN capability will only get turned on by the > >> > registration routine. > >> > > Most significantly, now when the pseudo device it gives the driver > >> > the VLAN tag, this will mean the driver will be able from the start > >> > to use the VFTA, the hardware filter, for each vlan attach the driver > >> > will add the ID into this table. > >> > > The unregister event will turn the table entry off, and if this is > >> the > >> > last VLAN being detached it will then disable the features. > >> > > Oh yes, these routines will also take care of the size change of > >> > the frame due to the tag. I already have the changes in place in > >> > the igb drive, and they are working great. > >> > > I do not understand why you think you need a flag to disable this, > >> > yes it could be done, but why? If you need to do some sort of > >> > debugging won't a system not using vlans and in promiscuous > >> > mode do just fine? > >> > > >> I guess this would be the same reason why FreeBSD have a way to > >> disable checksum offload for buggy hardware. Diabling all hardware > >> VLAN assistance due to broken VLAN filtering doesn't look right. > >> > >> > It just seems to violate the whole reason for doing vlans in the > >> > first place, however perhaps I am missing something? I do not > >> > believe the Linux driver has some way to disable use of the table > >> > but I'll double check on that. > >> > > Remember, this change requires NO driver changes unless they > >> > wish to take advantage of the ability. > >> > >> Yes. > >> > >> > > Cheers, > >> > > Jack > >> > >> Thanks. > > > > Sounds like there needs to be a h/w vlan assist capability bit that controls > > this in the driver. Then you'd have a way to disable via ifconfig w/ a > > trivial mod. > > I don't want to create stuff in ifconfig when I'm not convinced > of the need. If there were, as he says, 'buggy hardware', specifically > buggy Intel hardware, then either our drivers would have had special > errata or workarounds in it for that, but none of the OS drivers have > any special code for issues involving VFTA (the filter) or other VLAN > controlling components that I am aware of. > > If there are other network drivers that are buggy in this regard then why > encumber the generic interface due to that, let the drivers deal with it, > via sysctl or something of the sort. > > There are enough real cases of hardware problems we need to address in > code that I don't just want to modify code on the mere theoretical possibility > of such. > > How bout this, we put the change into HEAD, I add support as I've planned into > the em and igb drivers, and then we let them get tested, if a real problem comes > up, THEN we worry about adding special case code, how's that? > Please go ahead. I don't have any objections on it. I just thought it would be better to show a flag to indicate hardware VLAN filtering is active in ifconfig(8) and have user disable this feature in some rare cases. > Regards, > > Jack -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 07:43:21 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 944101065673 for ; Thu, 12 Jun 2008 07:43:21 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.freebsd.org (Postfix) with ESMTP id 176008FC23 for ; Thu, 12 Jun 2008 07:43:20 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from fw.publishing.hu ([82.131.181.62] helo=twoflower.in.publishing.hu) by marvin.harmless.hu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K6hCX-000Mw0-8h; Thu, 12 Jun 2008 09:26:29 +0200 Date: Thu, 12 Jun 2008 09:26:21 +0200 From: CZUCZY Gergely To: pyunyh@gmail.com Message-ID: <20080612092621.61b44529@twoflower.in.publishing.hu> In-Reply-To: <20080612040452.GE7250@cdnetworks.co.kr> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> <20080612000943.GA7250@cdnetworks.co.kr> <48508708.50903@errno.com> <2a41acea0806112048g60084f72o4391701ba242442@mail.gmail.com> <20080612040452.GE7250@cdnetworks.co.kr> Organization: Harmless Digital X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/il4TY5XZLaETCJstBMO17Lx"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: "freebsd-net@freebsd.org" , Jack Vogel Subject: Re: Vlan EVENT patch 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, 12 Jun 2008 07:43:21 -0000 --Sig_/il4TY5XZLaETCJstBMO17Lx Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 12 Jun 2008 13:04:52 +0900 Pyun YongHyeon wrote: > On Wed, Jun 11, 2008 at 08:48:58PM -0700, Jack Vogel wrote: > > On Wed, Jun 11, 2008 at 7:16 PM, Sam Leffler wrote: > > > [trimming cc list to reduce spamage] > > > > > > Pyun YongHyeon wrote: > > >> > > >> On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: > > >> > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon > > >> wrote: > > >> > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > > >> > > > This is a small patch that Sam came up with for me, it will > > >> > > > allow drivers to know > > >> > > > when a vlan attaches. > > >> > > > > > >> > > > It is transparent to any code that doesn't want to change, = but > > >> this > > >> > > > will allow my > > >> > > > drivers to finally utilize the vlan hardware filter (someth= ing > > >> Linux has had for > > >> > > > ever but we lacked). > > >> > > > > > >> > > > > >> > > Just curious, is there any rule how to use that new capability? > > >> > > Because drivers will receive events whenever VLAN tags are > > >> > > added/removed they would know how to act for these events. If > > >> > > promiscuous mode is on for interface, driver should not filter= any > > >> > > VLAN tagged frames, right? > > >> > > If users want to disable VLAN hardware filtering feature what = is > > >> > > best way to perform this? Introducing a new flag like > > >> > > IFCAP_VLAN_HWFILT or add a new sysctl that control this featur= e? > > >> > > I guess VIA Rhine III also have VLAN hardware filtering capabi= lity > > >> > > so it would be even better if we have a way to share common pa= rt. > > >> > > All the patch does is have the vlan driver generate events wh= en it > > >> attaches > > >> > or detaches from a NIC, there are no rules, however I can tell y= ou > > >> > what I'm coding into this in the Intel drivers. > > >> > > The way it works is the driver registers a callback for each > > >> > > event, > > >> I will > > >> > call that [igb,em,ixgbe]_register_vlan(), and unregister obvious= ly. > > >> > > Right now, the drivers just generically enable VLAN capability > > >> because > > >> > there is never a trigger to know IF and WHEN you need to do so, = but > > >> > with this change the VLAN capability will only get turned on by = the > > >> > registration routine. > > >> > > Most significantly, now when the pseudo device it gives the d= river > > >> > the VLAN tag, this will mean the driver will be able from the st= art > > >> > to use the VFTA, the hardware filter, for each vlan attach the d= river > > >> > will add the ID into this table. > > >> > > The unregister event will turn the table entry off, and if th= is is > > >> the > > >> > last VLAN being detached it will then disable the features. > > >> > > Oh yes, these routines will also take care of the size change= of > > >> > the frame due to the tag. I already have the changes in place in > > >> > the igb drive, and they are working great. > > >> > > I do not understand why you think you need a flag to disable = this, > > >> > yes it could be done, but why? If you need to do some sort of > > >> > debugging won't a system not using vlans and in promiscuous > > >> > mode do just fine? > > >> > > > >> I guess this would be the same reason why FreeBSD have a way to > > >> disable checksum offload for buggy hardware. Diabling all hardware > > >> VLAN assistance due to broken VLAN filtering doesn't look right. > > >> > > >> > It just seems to violate the whole reason for doing vlans in the > > >> > first place, however perhaps I am missing something? I do not > > >> > believe the Linux driver has some way to disable use of the table > > >> > but I'll double check on that. > > >> > > Remember, this change requires NO driver changes unless they > > >> > wish to take advantage of the ability. > > >> > > >> Yes. > > >> > > >> > > Cheers, > > >> > > Jack > > >> > > >> Thanks. > > > > > > Sounds like there needs to be a h/w vlan assist capability bit that > > > controls this in the driver. Then you'd have a way to disable via > > > ifconfig w/ a trivial mod. > >=20 > > I don't want to create stuff in ifconfig when I'm not convinced > > of the need. If there were, as he says, 'buggy hardware', specifically > > buggy Intel hardware, then either our drivers would have had special > > errata or workarounds in it for that, but none of the OS drivers have > > any special code for issues involving VFTA (the filter) or other VLAN > > controlling components that I am aware of. > >=20 > > If there are other network drivers that are buggy in this regard then = why > > encumber the generic interface due to that, let the drivers deal with = it, > > via sysctl or something of the sort. > >=20 > > There are enough real cases of hardware problems we need to address in > > code that I don't just want to modify code on the mere theoretical > > possibility of such. > >=20 > > How bout this, we put the change into HEAD, I add support as I've plan= ned > > into the em and igb drivers, and then we let them get tested, if a real > > problem comes up, THEN we worry about adding special case code, how's = that? > >=20 >=20 > Please go ahead. I don't have any objections on it. > I just thought it would be better to show a flag to indicate > hardware VLAN filtering is active in ifconfig(8) and have user > disable this feature in some rare cases. >=20 > > Regards, > >=20 > > Jack I don't know whether it's a policy or not in FreeBSD, but I also agree with= the opinion, that a flag should show up in the ifconfig output indicating that hardware filtering is being done on that interface. It helps the administra= tor to clarify how the hardware is working, which features of the hardware are = in use, and also, they can be disabled. Disabling features is important. Sometimes the code is messed up, the hardw= are is messed up, or neither are messed up, but they are unable to work togethe= r. In these cases the feature could be disabled without hacking the source, wh= ich is a clean solution. FreeBSD has design, and prefers clean solutions as I s= ee. I understand, that you _currently_ have no troubles and problems with your = code and hardware, but there are unforseen cases out there, lots of other hardw= are then intel's, and to quote Douglas N. Adams, "expect the unexpected". So, it won't hurt if it shows up in ifconfig, and it can be controlled, but definitely helps our job, the administrators'. --=20 =C3=9Cdv=C3=B6lettel, Czuczy Gergely Harmless Digital Bt mailto: gergely.czuczy@harmless.hu Tel: +36-30-9702963 --Sig_/il4TY5XZLaETCJstBMO17Lx Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFIUM+jzrC0WyuMkpsRAi3iAJ9TXAXn/R3Y+Z5EA1ZvF6A7WhKI3ACginxd Tw0W1Ep5UMUN8sNGFanlAR0= =yfIO -----END PGP SIGNATURE----- --Sig_/il4TY5XZLaETCJstBMO17Lx-- From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 14:47:25 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 053D41065683 for ; Thu, 12 Jun 2008 14:47:25 +0000 (UTC) (envelope-from bilouro@bilouro.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.245]) by mx1.freebsd.org (Postfix) with ESMTP id C8DBD8FC1B for ; Thu, 12 Jun 2008 14:47:24 +0000 (UTC) (envelope-from bilouro@bilouro.com) Received: by an-out-0708.google.com with SMTP id b33so909544ana.13 for ; Thu, 12 Jun 2008 07:47:24 -0700 (PDT) Received: by 10.100.247.14 with SMTP id u14mr2113174anh.104.1213280475351; Thu, 12 Jun 2008 07:21:15 -0700 (PDT) Received: by 10.100.216.6 with HTTP; Thu, 12 Jun 2008 07:21:15 -0700 (PDT) Message-ID: Date: Thu, 12 Jun 2008 11:21:15 -0300 From: "Victor Hugo Bilouro" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [GSoC - tcptest] Weekly Status Report #02 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, 12 Jun 2008 14:47:25 -0000 Hi, I posted the tcptest** weekly status report at freebsd wiki. Links: http://wiki.freebsd.org/VictorBilouro/TCP-IP_regression_test_suite http://wiki.freebsd.org/VictorBilouro/Following_tcptest http://wiki.freebsd.org/VictorBilouro/Release_0.1_Iteration_2 http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/bilouro%5ftcptest&HIDEDEL=NO Thank you! cheers -- Victor Hugo Bilouro FreeBSD! **tcptest** --> tcptest is a GSoC (Google Summer of Code) project, it's a TCP/IP Regression Test Suite implementation. As a testing tool, it can perform regression, protocol conformance, and fuzz tests. The tool may also be employed as an aid to protocol developers and both testing and debugging of firewalls/routers. It's was built on top of pcs.sf.net of gnn at freebsd. ps: I will keep the nomenclature used at subject. From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 15:03:42 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15C37106568D for ; Thu, 12 Jun 2008 15:03:42 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id EE0288FC1C for ; Thu, 12 Jun 2008 15:03:41 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail0.meer.net [209.157.152.14]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m5CF3bXU061009; Thu, 12 Jun 2008 08:03:41 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m5CF3ZC2083731; Thu, 12 Jun 2008 08:03:35 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from dhcp-75.hudson-trading.com.neville-neil.com (hudson-trading.com [66.150.84.160] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m5CF3YER018654; Thu, 12 Jun 2008 08:03:34 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Thu, 12 Jun 2008 11:03:34 -0400 Message-ID: From: "George V. Neville-Neil" To: security In-Reply-To: <4850028F.6090103@jim-liesl.org> References: <484F3E1B.9050104@ibctech.ca> <4850028F.6090103@jim-liesl.org> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.00 () [Tag at 5.00] X-CanItPRO-Stream: default X-Canit-Stats-ID: 646738 - fa1aa35888d2 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: freebsd-net@freebsd.org, Steve Bertrand Subject: Re: Throughput rate testing configurations 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, 12 Jun 2008 15:03:42 -0000 At Wed, 11 Jun 2008 09:51:27 -0700, security wrote: > > Steve Bertrand wrote: > > Hi everyone, > > > > I see what I believe to be less-than-adequate communication > > performance between many devices in parts of our network. > > > > Can someone recommend software (and config recommendations if > > possible) that I can implement to test both throughput and pps > > reliably, initially/primarily in a simple host-sw-host configuration? > > > > Perhaps I'm asking too much, but I'd like to have something that can > > push the link to it's absolute maximum capacity (for now, up to 1Gbps) > > for a long sustained time, that I can just walk away from and let it > > do it's work, and review the reports later where it had to scale down > > due to errors. > > > > What I'm really trying to achieve is: > > > > - test the link between hosts alone > > - throw in a switch > > - test the link while r/w to disk > > - test the link while r/w to GELI disk > > - test the link with oddball MTU sizes > > > Iperf or netperf are probably what you're looking for. Both try real > had NOT to tweak other subsystems while they run, so if you want to > throw disk activity in, you'll need to run another tool or roll your own > to create disk activity. You probably don't want to run them for > extended periods in a production network. Depending on the adapters at > each end, you may or may not be able to drive the link to saturation or > alter frame size. The Intel adapters I've seen allow jumbo frames, and > generally good performance (as opposed to say the realtek). It's also > useful to have a managed switch in between so you can look at the > counters on it. > I personally prefer netpipe because it tries odd sized (non power of 2) messages and tends to help edge cases come to light. /usr/ports/benchmarks/netpipe Later, George From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 15:17:21 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FE1C106566C for ; Thu, 12 Jun 2008 15:17:21 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 022418FC1B for ; Thu, 12 Jun 2008 15:17:20 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by yx-out-2324.google.com with SMTP id 31so383234yxl.13 for ; Thu, 12 Jun 2008 08:17:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type; bh=EqhrSHoRvznXaILaP7FKlQBpIMR/lI4OMCfptZQOYIE=; b=fupx5qpq6x94fbfkPVX6HQkKxD38eB6jIwrHpCujOypQeXQShhm1E/f+3hD4rTRoDn 3GdoaR1EhG+DXMg1HOf4H2Ra2W6qWAox6FlsSgxO4Bt0OlMU/5A87zFPsdm6tx4MUlx5 67Me2scXHf8JdLxykyzK0AvuaGO7bbaYpgoKQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=d0kOdxUbHTPyec6KkR7HggRBIR1p4F0lAx2RjNLQ6pgI6TgFbq+i1RXcDhGWlflLIo 6/kREzRHvtJNlS8oD8EEpcMmp6amDIubR+uTYCa+CdkTjJbCtMC65U+ma77kwCFXeNnm 1KOAKHpsUgZ+EwMkds0/v5m5AMdzWyPE6xwvM= Received: by 10.151.45.6 with SMTP id x6mr2547489ybj.6.1213283840347; Thu, 12 Jun 2008 08:17:20 -0700 (PDT) Received: by 10.151.84.2 with HTTP; Thu, 12 Jun 2008 08:17:20 -0700 (PDT) Message-ID: <20def4870806120817q5b755805hfafa0d0d1523f2ad@mail.gmail.com> Date: Thu, 12 Jun 2008 18:17:20 +0300 From: "Yony Yossef" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: liranl@mellanox.co.il Subject: TSO bug in FreeBSD 7.0 ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 15:17:21 -0000 Hi freebsd-net, I'm seeing mbuf chains larger than 64K being sent down by FreeBSD 7 when TSO is enabled. Then my driver crashes in bus_dmamap_load_mbuf_sg (error=EINVAL). I'm printing the mbuf m_pkthdr.len size right after the DEQUEUE from the stack: IFQ_DRV_DEQUEUE(&dev->if_snd, m_head); if (m_head == NULL) break; if (m_head->m_pkthdr.len > 65000) { printf("TSO packet mbuf len:%d\n", m_head->m_pkthdr.len); } and the output is: .... TSO packet mbuf len:65387 TSO packet mbuf len:65417 TSO packet mbuf len:65447 TSO packet mbuf len:65477 TSO packet mbuf len:65507 TSO packet mbuf len:65537 mtnic0: bus_dmamap_load_mbuf_sg error: 22 xmit_failure:12 ... Note the 65537, I've also seen TSO packets sized 65542. There's this old thread talking about it: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2007-02/msg00312.html but I've seen no solution for this bug. Is there a fix for that? Thanks, Yony From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 15:26:28 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 910B61065670 for ; Thu, 12 Jun 2008 15:26:28 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7968FC14 for ; Thu, 12 Jun 2008 15:26:27 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m5CFQPb7021115; Thu, 12 Jun 2008 17:26:26 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m5CFQPAI021114; Thu, 12 Jun 2008 17:26:25 +0200 (CEST) (envelope-from olli) Date: Thu, 12 Jun 2008 17:26:25 +0200 (CEST) Message-Id: <200806121526.m5CFQPAI021114@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG X-Newsgroups: list.freebsd-net User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 12 Jun 2008 17:26:26 +0200 (CEST) Cc: Subject: CARP + multiple 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: Thu, 12 Jun 2008 15:26:28 -0000 Hi, I'm building a fail-over setup with two database servers, so when the first one fails, the second takes over. The data is replicated. So far it seems to work fine with CARP, but now it turned out that I need another address from a different subnet which also needs to access the database. What's the best way to do that? Add a second IP address to the existing carp interface, or create a new carp interface? Are there any pros and cons? I.e. currently it looks like this: Database server A: bge0: physical interface vlan101: 10.1.101.41/24 on bge0 vlan202: 10.1.202.41/24 on bge0 carp0: 10.1.101.40/32 vhid 1 Database server B: bge0: physical interface vlan101: 10.1.101.42/24 on bge0 vlan202: 10.1.202.42/24 on bge0 carp0: 10.1.101.40/32 vhid 1 And now I need to add an IP address from vlan202 which also needs to access the same database. I'm inclined to add 10.1.202.40/32 vhid 1 to the existing carp0 on both servers. I assume that the CARP interface goes to BACKUP when *any* of its IP addresses fail, right? Can anybody confirm this, please? So, would that work, or is there a better way? Any hints are appreciated! Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "In My Egoistical Opinion, most people's C programs should be indented six feet downward and covered with dirt." -- Blair P. Houghton From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 16:38:01 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57BB61065672 for ; Thu, 12 Jun 2008 16:38:01 +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 C1DD38FC17 for ; Thu, 12 Jun 2008 16:38:00 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 88804 invoked from network); 12 Jun 2008 15:33:05 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Jun 2008 15:33:05 -0000 Message-ID: <485150E8.7050903@freebsd.org> Date: Thu, 12 Jun 2008 18:38:00 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Yony Yossef References: <20def4870806120817q5b755805hfafa0d0d1523f2ad@mail.gmail.com> In-Reply-To: <20def4870806120817q5b755805hfafa0d0d1523f2ad@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, liranl@mellanox.co.il Subject: Re: TSO bug in FreeBSD 7.0 ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 16:38:01 -0000 Yony Yossef wrote: > Hi freebsd-net, > > I'm seeing mbuf chains larger than 64K being sent down by FreeBSD 7 when TSO > is enabled. > Then my driver crashes in bus_dmamap_load_mbuf_sg (error=EINVAL). > I'm printing the mbuf m_pkthdr.len size right after the DEQUEUE from the > stack: > > IFQ_DRV_DEQUEUE(&dev->if_snd, m_head); > if (m_head == NULL) > break; > if (m_head->m_pkthdr.len > 65000) { > printf("TSO packet mbuf len:%d\n", m_head->m_pkthdr.len); > } > and the output is: > > .... > TSO packet mbuf len:65387 > TSO packet mbuf len:65417 > TSO packet mbuf len:65447 > TSO packet mbuf len:65477 > TSO packet mbuf len:65507 > TSO packet mbuf len:65537 > mtnic0: bus_dmamap_load_mbuf_sg error: 22 > xmit_failure:12 > ... > > Note the 65537, I've also seen TSO packets sized 65542. > > There's this old thread talking about it: > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2007-02/msg00312.html > but I've seen no solution for this bug. > > Is there a fix for that? This bug is supposed to be fixed and the fix should also be included in 7.0. The other users of TSO reported no more overflows. I'll have another look whether later changes may have had an effect. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 17:06:06 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF752106566C for ; Thu, 12 Jun 2008 17:06:06 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id 77E698FC1E for ; Thu, 12 Jun 2008 17:06:06 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1695336pyb.10 for ; Thu, 12 Jun 2008 10:06:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=kN0U087lEn0seXfrcbeBA51tWxsbNtrWqyHu8d3xMOw=; b=X960JcUg+x5d0xLk/aG6m1H9xmCSR2ikJRTLCyyCnPSvaW36tq69iV/B1QCwCHD/3d if4BeyFm96ibo3SZbcqql002XW555kbDBTdD5nQOB42lK4xBhab1u3x1RvY+fEfLxGnN axPqQrb25atbdlPT6OOhd1ML8Wg+JjDb7Wpbc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=APlAfPf7yRQDqGfBTiqPvhhz1fOjYAvo/hj+OOe7VdiYm/5q4X5eJvTAkcpU05vLJW BXpVxVifp4LyY2qk7votk2zFaI7Ct5jb21EWq8AFcC90QVIsrRt/qhRbheaXg8huti9B RFmUPMPybjyZQHdBQYQ0cjxbMfajvJYePyjl4= Received: by 10.114.155.1 with SMTP id c1mr1880015wae.24.1213290365211; Thu, 12 Jun 2008 10:06:05 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Thu, 12 Jun 2008 10:06:05 -0700 (PDT) Message-ID: <2a41acea0806121006r23936007x5acf1fa9e302a94d@mail.gmail.com> Date: Thu, 12 Jun 2008 10:06:05 -0700 From: "Jack Vogel" To: "CZUCZY Gergely" In-Reply-To: <20080612092621.61b44529@twoflower.in.publishing.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> <20080612000943.GA7250@cdnetworks.co.kr> <48508708.50903@errno.com> <2a41acea0806112048g60084f72o4391701ba242442@mail.gmail.com> <20080612040452.GE7250@cdnetworks.co.kr> <20080612092621.61b44529@twoflower.in.publishing.hu> Cc: pyunyh@gmail.com, "freebsd-net@freebsd.org" Subject: Re: Vlan EVENT patch 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, 12 Jun 2008 17:06:06 -0000 On Thu, Jun 12, 2008 at 12:26 AM, CZUCZY Gergely wrote: > On Thu, 12 Jun 2008 13:04:52 +0900 > Pyun YongHyeon wrote: > >> On Wed, Jun 11, 2008 at 08:48:58PM -0700, Jack Vogel wrote: >> > On Wed, Jun 11, 2008 at 7:16 PM, Sam Leffler wrote: >> > > [trimming cc list to reduce spamage] >> > > >> > > Pyun YongHyeon wrote: >> > >> >> > >> On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: >> > >> > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon >> > >> wrote: >> > >> > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: >> > >> > > > This is a small patch that Sam came up with for me, it will >> > >> > > > allow drivers to know >> > >> > > > when a vlan attaches. >> > >> > > > >> > >> > > > It is transparent to any code that doesn't want to change, but >> > >> this >> > >> > > > will allow my >> > >> > > > drivers to finally utilize the vlan hardware filter (something >> > >> Linux has had for >> > >> > > > ever but we lacked). >> > >> > > > >> > >> > > >> > >> > > Just curious, is there any rule how to use that new capability? >> > >> > > Because drivers will receive events whenever VLAN tags are >> > >> > > added/removed they would know how to act for these events. If >> > >> > > promiscuous mode is on for interface, driver should not filter any >> > >> > > VLAN tagged frames, right? >> > >> > > If users want to disable VLAN hardware filtering feature what is >> > >> > > best way to perform this? Introducing a new flag like >> > >> > > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? >> > >> > > I guess VIA Rhine III also have VLAN hardware filtering capability >> > >> > > so it would be even better if we have a way to share common part. >> > >> > > All the patch does is have the vlan driver generate events when it >> > >> attaches >> > >> > or detaches from a NIC, there are no rules, however I can tell you >> > >> > what I'm coding into this in the Intel drivers. >> > >> > > The way it works is the driver registers a callback for each >> > >> > > event, >> > >> I will >> > >> > call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. >> > >> > > Right now, the drivers just generically enable VLAN capability >> > >> because >> > >> > there is never a trigger to know IF and WHEN you need to do so, but >> > >> > with this change the VLAN capability will only get turned on by the >> > >> > registration routine. >> > >> > > Most significantly, now when the pseudo device it gives the driver >> > >> > the VLAN tag, this will mean the driver will be able from the start >> > >> > to use the VFTA, the hardware filter, for each vlan attach the driver >> > >> > will add the ID into this table. >> > >> > > The unregister event will turn the table entry off, and if this is >> > >> the >> > >> > last VLAN being detached it will then disable the features. >> > >> > > Oh yes, these routines will also take care of the size change of >> > >> > the frame due to the tag. I already have the changes in place in >> > >> > the igb drive, and they are working great. >> > >> > > I do not understand why you think you need a flag to disable this, >> > >> > yes it could be done, but why? If you need to do some sort of >> > >> > debugging won't a system not using vlans and in promiscuous >> > >> > mode do just fine? >> > >> > >> > >> I guess this would be the same reason why FreeBSD have a way to >> > >> disable checksum offload for buggy hardware. Diabling all hardware >> > >> VLAN assistance due to broken VLAN filtering doesn't look right. >> > >> >> > >> > It just seems to violate the whole reason for doing vlans in the >> > >> > first place, however perhaps I am missing something? I do not >> > >> > believe the Linux driver has some way to disable use of the table >> > >> > but I'll double check on that. >> > >> > > Remember, this change requires NO driver changes unless they >> > >> > wish to take advantage of the ability. >> > >> >> > >> Yes. >> > >> >> > >> > > Cheers, >> > >> > > Jack >> > >> >> > >> Thanks. >> > > >> > > Sounds like there needs to be a h/w vlan assist capability bit that >> > > controls this in the driver. Then you'd have a way to disable via >> > > ifconfig w/ a trivial mod. >> > >> > I don't want to create stuff in ifconfig when I'm not convinced >> > of the need. If there were, as he says, 'buggy hardware', specifically >> > buggy Intel hardware, then either our drivers would have had special >> > errata or workarounds in it for that, but none of the OS drivers have >> > any special code for issues involving VFTA (the filter) or other VLAN >> > controlling components that I am aware of. >> > >> > If there are other network drivers that are buggy in this regard then why >> > encumber the generic interface due to that, let the drivers deal with it, >> > via sysctl or something of the sort. >> > >> > There are enough real cases of hardware problems we need to address in >> > code that I don't just want to modify code on the mere theoretical >> > possibility of such. >> > >> > How bout this, we put the change into HEAD, I add support as I've planned >> > into the em and igb drivers, and then we let them get tested, if a real >> > problem comes up, THEN we worry about adding special case code, how's that? >> > >> >> Please go ahead. I don't have any objections on it. >> I just thought it would be better to show a flag to indicate >> hardware VLAN filtering is active in ifconfig(8) and have user >> disable this feature in some rare cases. >> >> > Regards, >> > >> > Jack > > I don't know whether it's a policy or not in FreeBSD, but I also agree with the > opinion, that a flag should show up in the ifconfig output indicating that > hardware filtering is being done on that interface. It helps the administrator > to clarify how the hardware is working, which features of the hardware are in > use, and also, they can be disabled. > Disabling features is important. Sometimes the code is messed up, the hardware > is messed up, or neither are messed up, but they are unable to work together. > In these cases the feature could be disabled without hacking the source, which > is a clean solution. FreeBSD has design, and prefers clean solutions as I see. > I understand, that you _currently_ have no troubles and problems with your code > and hardware, but there are unforseen cases out there, lots of other hardware > then intel's, and to quote Douglas N. Adams, "expect the unexpected". > > So, it won't hurt if it shows up in ifconfig, and it can be controlled, but > definitely helps our job, the administrators'. OK, if people feel strongly about this, and someone wants to implement the code in ifconfig I'll go along with it. Jack From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 18:52:53 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C1F81065676; Thu, 12 Jun 2008 18:52:53 +0000 (UTC) (envelope-from ups@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 060BE8FC12; Thu, 12 Jun 2008 18:52:53 +0000 (UTC) (envelope-from ups@FreeBSD.org) Received: from freefall.freebsd.org (ups@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5CIqqWc088617; Thu, 12 Jun 2008 18:52:52 GMT (envelope-from ups@freefall.freebsd.org) Received: (from ups@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5CIqqj9088608; Thu, 12 Jun 2008 18:52:52 GMT (envelope-from ups) Date: Thu, 12 Jun 2008 18:52:52 GMT Message-Id: <200806121852.m5CIqqj9088608@freefall.freebsd.org> To: ups@FreeBSD.org, freebsd-net@FreeBSD.org, ups@FreeBSD.org From: ups@FreeBSD.org Cc: Subject: Re: kern/123950: [tcp] TH_RST packet sended if received out-of-order data (ACK) in SYN_RECEIVED state 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, 12 Jun 2008 18:52:53 -0000 Synopsis: [tcp] TH_RST packet sended if received out-of-order data (ACK) in SYN_RECEIVED state Responsible-Changed-From-To: freebsd-net->ups Responsible-Changed-By: ups Responsible-Changed-When: Thu Jun 12 18:47:47 UTC 2008 Responsible-Changed-Why: Currently working on the syn cache and have encountered the same problem. Fix should be checked in in a few days. http://www.freebsd.org/cgi/query-pr.cgi?pr=123950 From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 19:19:09 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FE55106564A for ; Thu, 12 Jun 2008 19:19:09 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.freebsd.org (Postfix) with ESMTP id DA5648FC18 for ; Thu, 12 Jun 2008 19:19:08 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail12.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5CJJ5Zp014584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jun 2008 05:19:06 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m5CJJ5Tt014147; Fri, 13 Jun 2008 05:19:05 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m5CJJ5pg014146; Fri, 13 Jun 2008 05:19:05 +1000 (EST) (envelope-from peter) Date: Fri, 13 Jun 2008 05:19:05 +1000 From: Peter Jeremy To: Oliver Fromme Message-ID: <20080612191905.GK84454@server.vk2pj.dyndns.org> References: <200806121526.m5CFQPAI021114@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tEFtbjk+mNEviIIX" Content-Disposition: inline In-Reply-To: <200806121526.m5CFQPAI021114@lurza.secnetix.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org Subject: Re: CARP + multiple 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: Thu, 12 Jun 2008 19:19:09 -0000 --tEFtbjk+mNEviIIX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-12 17:26:25 +0200, Oliver Fromme wrote: >So far it seems to work fine with CARP, but now it turned >out that I need another address from a different subnet >which also needs to access the database. What's the best >way to do that? Add a second IP address to the existing >carp interface, or create a new carp interface? Are there >any pros and cons? I'm currently working towards something like this and intending to have one CARP interface for each VLAN. >And now I need to add an IP address from vlan202 which >also needs to access the same database. I'm inclined to >add 10.1.202.40/32 vhid 1 to the existing carp0 on both >servers. I assume that the CARP interface goes to BACKUP >when *any* of its IP addresses fail, right? Can anybody >confirm this, please? My reading of the various documentation says that you are on the right track but, by default, each CARP interface will fail over independently. If you want them all to fail over together then you should set net.inet.carp.preempt (see carp(4) and its first example) --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --tEFtbjk+mNEviIIX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhRdqgACgkQ/opHv/APuIcscgCdGWkBfbAqY+Ch8wy8YMw8Arsn zm4AoKUEPdIbKfRipIlYTI7S95r9Uykb =62fj -----END PGP SIGNATURE----- --tEFtbjk+mNEviIIX-- From owner-freebsd-net@FreeBSD.ORG Thu Jun 12 21:12:58 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 565AF10657CD for ; Thu, 12 Jun 2008 21:12:58 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6878FC1B for ; Thu, 12 Jun 2008 21:12:58 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.11.16.99] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 12 Jun 2008 13:58:28 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id 956A22B1; Thu, 12 Jun 2008 13:58:28 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.11.18.52]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id 7D17D2B0; Thu, 12 Jun 2008 13:58:28 -0700 (PDT) Received: from mail-irva-13.broadcom.com (mail-irva-13.broadcom.com [10.11.16.103]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id GYB48750; Thu, 12 Jun 2008 13:58:19 -0700 (PDT) Received: from NT-IRVA-0752.brcm.ad.broadcom.com (nt-irva-0752 [10.8.194.67]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id AE4E874D00; Thu, 12 Jun 2008 13:58:19 -0700 (PDT) Received: from IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) by NT-IRVA-0752.brcm.ad.broadcom.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Jun 2008 13:58:19 -0700 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.9.200.129]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Thu, 12 Jun 2008 13:59:02 -0700 From: "David Christensen" To: "Jack Vogel" , "CZUCZY Gergely" Date: Thu, 12 Jun 2008 13:58:53 -0700 Thread-Topic: Vlan EVENT patch Thread-Index: AcjMrqbpMDYx72efRGqdh5LUyPIdYAAIBpOA Message-ID: <5D267A3F22FD854F8F48B3D2B523819324F0D70877@IRVEXCHCCR01.corp.ad.broadcom.com> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> <20080612000943.GA7250@cdnetworks.co.kr> <48508708.50903@errno.com> <2a41acea0806112048g60084f72o4391701ba242442@mail.gmail.com> <20080612040452.GE7250@cdnetworks.co.kr> <20080612092621.61b44529@twoflower.in.publishing.hu> <2a41acea0806121006r23936007x5acf1fa9e302a94d@mail.gmail.com> In-Reply-To: <2a41acea0806121006r23936007x5acf1fa9e302a94d@mail.gmail.com> Accept-Language: en-US Content-Language: en-US acceptlanguage: en-US MIME-Version: 1.0 X-OriginalArrivalTime: 12 Jun 2008 20:58:19.0591 (UTC) FILETIME=[0B0F5570:01C8CCCF] X-WSS-ID: 644F527E63S62855494-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "pyunyh@gmail.com" , "freebsd-net@freebsd.org" Subject: RE: Vlan EVENT patch 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, 12 Jun 2008 21:12:58 -0000 > > So, it won't hurt if it shows up in ifconfig, and it can be > controlled, but > > definitely helps our job, the administrators'. > > OK, if people feel strongly about this, and someone wants to implement > the > code in ifconfig I'll go along with it. I believe there are some valid reasons when you consider virtualization with Xen where you need to pass VLAN tags to the hypervisor. Not sure if Xen is running on FreeBSD yet but I can definitely see the need. dave From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 00:29:29 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9741065679 for ; Fri, 13 Jun 2008 00:29:29 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id C2FF68FC15 for ; Fri, 13 Jun 2008 00:29:28 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 94116 invoked by uid 89); 13 Jun 2008 00:30:14 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 13 Jun 2008 00:30:14 -0000 Message-ID: <4851BFE9.5070905@ibctech.ca> Date: Thu, 12 Jun 2008 20:31:37 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "George V. Neville-Neil" References: <484F3E1B.9050104@ibctech.ca> <4850028F.6090103@jim-liesl.org> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, security Subject: Re: Throughput rate testing configurations 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, 13 Jun 2008 00:29:29 -0000 George V. Neville-Neil wrote: > At Wed, 11 Jun 2008 09:51:27 -0700, > security wrote: >> Iperf or netperf are probably what you're looking for. > I personally prefer netpipe because it tries odd sized (non power of > 2) messages and tends to help edge cases come to light. > > /usr/ports/benchmarks/netpipe Thank you for the recommendations. I will try out all three of them. I'm certain I'll get the results I am after. Cheers, Steve From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 01:25:42 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F04B51065670 for ; Fri, 13 Jun 2008 01:25:42 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id D62A08FC0A for ; Fri, 13 Jun 2008 01:25:42 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K6y2w-0002Ri-Jl for freebsd-net@freebsd.org; Fri, 13 Jun 2008 01:25:42 +0000 Message-ID: <4851CC95.8070902@psg.com> Date: Fri, 13 Jun 2008 10:25:41 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: FreeBSD Net X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ssh window 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, 13 Jun 2008 01:25:43 -0000 this has been a cause of great pain for a loooong time. http://www.psc.edu/networking/projects/hpn-ssh/ as openssh seems not to be fixing it (and i do not consider a 2mb fixed buffer to be fixed, especially not from a 100mb link here in tokyo and servers in the states, europe, and africa), perhaps i could convince freebsd net folk to do so? randy From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 01:30:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 018B21065677 for ; Fri, 13 Jun 2008 01:30:13 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by mx1.freebsd.org (Postfix) with ESMTP id D0EEE8FC1D for ; Fri, 13 Jun 2008 01:30:12 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTPS id 3781A11402C for ; Fri, 13 Jun 2008 01:30:11 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from manx.isc.org (manx.isc.org [IPv6:2001:4f8:3:bb::37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id E86CCE601A for ; Fri, 13 Jun 2008 01:30:10 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Message-ID: <4851CD9D.3010801@isc.org> Date: Thu, 12 Jun 2008 18:30:05 -0700 From: Peter Losher Organization: ISC User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <4851CC95.8070902@psg.com> In-Reply-To: <4851CC95.8070902@psg.com> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF4225F96DB094E289D0D27C0" X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mx.isc.org Subject: Re: ssh window 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, 13 Jun 2008 01:30:13 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF4225F96DB094E289D0D27C0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Randy Bush wrote: > this has been a cause of great pain for a loooong time. >=20 > http://www.psc.edu/networking/projects/hpn-ssh/ >=20 > as openssh seems not to be fixing it (and i do not consider a 2mb fixed= > buffer to be fixed, especially not from a 100mb link here in tokyo and > servers in the states, europe, and africa), perhaps i could convince > freebsd net folk to do so? FYI - HPN is already a build option in the openssh-portable port. -Peter --=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --------------enigF4225F96DB094E289D0D27C0 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.7 (Darwin) iD8DBQFIUc2iPtVx9OgEjQgRAiG/AJ9sNtzsuluIxCnmYG1r3jZwKCVzVgCeOzEF MqFjeaqhl/3gaS23bf0rHms= =hf4D -----END PGP SIGNATURE----- --------------enigF4225F96DB094E289D0D27C0-- From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 02:51:28 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 935861065672 for ; Fri, 13 Jun 2008 02:51:28 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1962F8FC12 for ; Fri, 13 Jun 2008 02:51:27 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.2/8.14.2) with ESMTP id m5D2pvVH091425; Thu, 12 Jun 2008 21:51:57 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m5D2pvHM091424; Thu, 12 Jun 2008 21:51:57 -0500 (CDT) (envelope-from brooks) Date: Thu, 12 Jun 2008 21:51:57 -0500 From: Brooks Davis To: Peter Losher Message-ID: <20080613025157.GA90190@lor.one-eyed-alien.net> References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <4851CD9D.3010801@isc.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Thu, 12 Jun 2008 21:51:58 -0500 (CDT) Cc: freebsd-net@freebsd.org Subject: Re: ssh window 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, 13 Jun 2008 02:51:28 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: > Randy Bush wrote: >> this has been a cause of great pain for a loooong time. >>=20 >> http://www.psc.edu/networking/projects/hpn-ssh/ >>=20 >> as openssh seems not to be fixing it (and i do not consider a 2mb fixed >> buffer to be fixed, especially not from a 100mb link here in tokyo and >> servers in the states, europe, and africa), perhaps i could convince >> freebsd net folk to do so? >=20 > FYI - HPN is already a build option in the openssh-portable port. I do think we should strongly consider adding the rest of it to the base. -- Brooks --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIUeDMXY6L6fI4GtQRAroiAJ4yaKy99N1UcvokZhlNMhoOD63PlwCfUpVh POIoXyt/CANbUTHHhsu5Lyc= =8aaa -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 03:26:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83EB01065670 for ; Fri, 13 Jun 2008 03:26:36 +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 917A48FC19 for ; Fri, 13 Jun 2008 03:26:34 +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 NAA07307; Fri, 13 Jun 2008 13:26:31 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 13 Jun 2008 13:26:29 +1000 (EST) From: Ian Smith To: Brooks Davis In-Reply-To: <20080613025157.GA90190@lor.one-eyed-alien.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org, Peter Losher Subject: Re: ssh window 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, 13 Jun 2008 03:26:36 -0000 On Thu, 12 Jun 2008, Brooks Davis wrote: > On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: > > Randy Bush wrote: > >> this has been a cause of great pain for a loooong time. > >> > >> http://www.psc.edu/networking/projects/hpn-ssh/ > >> > >> as openssh seems not to be fixing it (and i do not consider a 2mb fixed > >> buffer to be fixed, especially not from a 100mb link here in tokyo and > >> servers in the states, europe, and africa), perhaps i could convince > >> freebsd net folk to do so? > > > > FYI - HPN is already a build option in the openssh-portable port. > > I do think we should strongly consider adding the rest of it to the base. Presumably with suitable caveats re NONE CYPHER, NoneEnabled=no default? cheers, Ian From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 03:29:52 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67F6D1065679; Fri, 13 Jun 2008 03:29:52 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id 1800F8FC19; Fri, 13 Jun 2008 03:29:52 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K6zz3-0002wd-BU; Fri, 13 Jun 2008 03:29:49 +0000 Message-ID: <4851E9A9.90809@psg.com> Date: Fri, 13 Jun 2008 12:29:45 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Ian Smith References: In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Brooks Davis , Peter Losher Subject: Re: ssh window 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, 13 Jun 2008 03:29:52 -0000 Ian Smith wrote: > On Thu, 12 Jun 2008, Brooks Davis wrote: > > On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: > > > Randy Bush wrote: > > >> this has been a cause of great pain for a loooong time. > > >> > > >> http://www.psc.edu/networking/projects/hpn-ssh/ > > >> > > >> as openssh seems not to be fixing it (and i do not consider a 2mb fixed > > >> buffer to be fixed, especially not from a 100mb link here in tokyo and > > >> servers in the states, europe, and africa), perhaps i could convince > > >> freebsd net folk to do so? > > > > > > FYI - HPN is already a build option in the openssh-portable port. > > > > I do think we should strongly consider adding the rest of it to the base. > > Presumably with suitable caveats re NONE CYPHER, NoneEnabled=no default? for sure! randy From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 03:36:47 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65B6C106566C; Fri, 13 Jun 2008 03:36:47 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id C7BD08FC0C; Fri, 13 Jun 2008 03:36:46 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id TJX09545; Thu, 12 Jun 2008 20:36:45 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9A5C345048; Thu, 12 Jun 2008 20:36:41 -0700 (PDT) To: Randy Bush In-Reply-To: Your message of "Fri, 13 Jun 2008 12:29:45 +0900." <4851E9A9.90809@psg.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1213328201_9366P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 12 Jun 2008 20:36:41 -0700 From: "Kevin Oberman" Message-Id: <20080613033641.9A5C345048@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; ; X-Sender: X-To_Name: Randy Bush X-To_Domain: psg.com X-To: Randy Bush X-To_Email: randy@psg.com X-To_Alias: randy Cc: freebsd-net@freebsd.org, Brooks Davis , Ian Smith , Peter Losher Subject: Re: ssh window 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, 13 Jun 2008 03:36:47 -0000 --==_Exmh_1213328201_9366P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Fri, 13 Jun 2008 12:29:45 +0900 > From: Randy Bush > Sender: owner-freebsd-net@freebsd.org > > Ian Smith wrote: > > On Thu, 12 Jun 2008, Brooks Davis wrote: > > > On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: > > > > Randy Bush wrote: > > > >> this has been a cause of great pain for a loooong time. > > > >> > > > >> http://www.psc.edu/networking/projects/hpn-ssh/ > > > >> > > > >> as openssh seems not to be fixing it (and i do not consider a 2mb fixed > > > >> buffer to be fixed, especially not from a 100mb link here in tokyo and > > > >> servers in the states, europe, and africa), perhaps i could convince > > > >> freebsd net folk to do so? > > > > > > > > FYI - HPN is already a build option in the openssh-portable port. > > > > > > I do think we should strongly consider adding the rest of it to the base. > > > > Presumably with suitable caveats re NONE CYPHER, NoneEnabled=no default? > > for sure! Agreed. PSC had valid reasons to allow NONE. They just don't apply to most cases and are a a very bad idea for a default install. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1213328201_9366P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIUetJkn3rs5h7N1ERAgMGAJ9FvgFhCfR5GOFL1V7vbWr3uLXyagCgk/vl vBlWK//v2PGP0x737ZnHVx4= =W+6t -----END PGP SIGNATURE----- --==_Exmh_1213328201_9366P-- From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 03:49:43 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B87C21065679; Fri, 13 Jun 2008 03:49:43 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 678168FC16; Fri, 13 Jun 2008 03:49:42 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.13.8/8.13.8) with ESMTP id m5D3BDg5063746; Thu, 12 Jun 2008 23:11:13 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.13.8/8.13.8/Submit) id m5D3BD5m063745; Thu, 12 Jun 2008 23:11:13 -0400 (EDT) (envelope-from wollman) Date: Thu, 12 Jun 2008 23:11:13 -0400 (EDT) From: Garrett Wollman Message-Id: <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> To: brooks@freebsd.org In-Reply-To: <20080613025157.GA90190@lor.one-eyed-alien.net> References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Thu, 12 Jun 2008 23:11:13 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on hergotha.csail.mit.edu Cc: net@freebsd.org Subject: Re: ssh window 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, 13 Jun 2008 03:49:43 -0000 In article <20080613025157.GA90190@lor.one-eyed-alien.net>, Brooks Davis writes: >On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: >> FYI - HPN is already a build option in the openssh-portable port. > >I do think we should strongly consider adding the rest of it to the base. Am I the only one who would be happier if openssh were not in the base system at all? I always have to install the port anyway; having it in the base just gives me more files I need to delete after an install. (Heimdal is the other big culprit.) -GAWollman From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 11:02:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5C481065673; Fri, 13 Jun 2008 11:02:13 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 297298FC13; Fri, 13 Jun 2008 11:02:09 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <485253AF.4000000@FreeBSD.org> Date: Fri, 13 Jun 2008 13:02:07 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Brooks Davis References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> <20080613025157.GA90190@lor.one-eyed-alien.net> In-Reply-To: <20080613025157.GA90190@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Peter Losher Subject: Re: ssh window 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, 13 Jun 2008 11:02:13 -0000 Brooks Davis wrote: > On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: >> Randy Bush wrote: >>> this has been a cause of great pain for a loooong time. >>> >>> http://www.psc.edu/networking/projects/hpn-ssh/ >>> >>> as openssh seems not to be fixing it (and i do not consider a 2mb fixed >>> buffer to be fixed, especially not from a 100mb link here in tokyo and >>> servers in the states, europe, and africa), perhaps i could convince >>> freebsd net folk to do so? >> FYI - HPN is already a build option in the openssh-portable port. > > I do think we should strongly consider adding the rest of it to the base. > > -- Brooks There seem to be a couple of issues: 1) Connection aborts during interactive use. I started using this patch only yesterday but already a couple of times my interactive session to a machine has aborted from typing one character to the next. It doesnt seem to be affecting non-interactive use. I have not investigated this yet. 2) -c none handling is a bit weird. There is no way to shut up the warnings on non-interactive connections ("WARNING: ENABLED NONE CIPHER"; yes, I know, because I WROTE THAT SCRIPT :). Also it doesn't fall back gracefully if the other side doesn't support -c none; it just aborts the collection. This means you can't automatically interoperate with a non-HPN server if you want to use 'none' encryption. This is not related to the buffer handling but it is part of the same patch set. I really like the idea of -c none, but I think they have gone overboard with the paranoia. Kris From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 11:04:14 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AFF81065676; Fri, 13 Jun 2008 11:04:14 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F1A1D8FC1A; Fri, 13 Jun 2008 11:04:09 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48525428.9000703@FreeBSD.org> Date: Fri, 13 Jun 2008 13:04:08 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Garrett Wollman References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> In-Reply-To: <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: brooks@freebsd.org, net@freebsd.org Subject: Re: ssh window 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, 13 Jun 2008 11:04:14 -0000 Garrett Wollman wrote: > In article <20080613025157.GA90190@lor.one-eyed-alien.net>, Brooks > Davis writes: > >> On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: >>> FYI - HPN is already a build option in the openssh-portable port. >> I do think we should strongly consider adding the rest of it to the base. > > Am I the only one who would be happier if openssh were not in the base > system at all? Quite possibly :) I don't think it's at all viable to ship FreeBSD without an ssh client in this day and age. Kris From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 11:31:51 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A07F11065680 for ; Fri, 13 Jun 2008 11:31:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0CC8FC25 for ; Fri, 13 Jun 2008 11:31:51 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 23F8C2049; Fri, 13 Jun 2008 13:12:08 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Garrett Wollman References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> Date: Fri, 13 Jun 2008 13:12:07 +0200 In-Reply-To: <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> (Garrett Wollman's message of "Thu\, 12 Jun 2008 23\:11\:13 -0400 \(EDT\)") Message-ID: <861w31oago.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: brooks@freebsd.org, net@freebsd.org Subject: Re: ssh window 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, 13 Jun 2008 11:31:51 -0000 Garrett Wollman writes: > Am I the only one who would be happier if openssh were not in the base > system at all? I always have to install the port anyway; having it in > the base just gives me more files I need to delete after an install. Well, it's not going to get any better if you don't talk to me about it. I don't read minds. As for the OP: Randy Bush writes: > this has been a cause of great pain for a loooong time. > > http://www.psc.edu/networking/projects/hpn-ssh/ > > as openssh seems not to be fixing it (and i do not consider a 2mb fixed > buffer to be fixed, especially not from a 100mb link here in tokyo and > servers in the states, europe, and africa), perhaps i could convince > freebsd net folk to do so? OpenSSH is not within the purview of the "freebsd net folk". If you have an issue with OpenSSH, you need to talk to me. The last time I was asked to apply the HPN patches to base, IIRC, they had not yet been submitted to (and rejected by) the upstream vendor, so I decided to wait and see. The NoneCipher issue comes up regularly, and is on my todo list for the 5.0p1 upgrade (along with several other things, such as changing the default key type back to RSA). I hope to import 5.0p1 as soon as we have a vendor import policy in place for Subversion. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 14:28:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C3331065679 for ; Fri, 13 Jun 2008 14:28:13 +0000 (UTC) (envelope-from brennanma@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.236]) by mx1.freebsd.org (Postfix) with ESMTP id D43E18FC26 for ; Fri, 13 Jun 2008 14:28:12 +0000 (UTC) (envelope-from brennanma@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so623098wra.27 for ; Fri, 13 Jun 2008 07:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=8y/8jZtmb2ncmB3VNKsoAjOH7XDr9SunjNXJ11z3VVg=; b=Snw9Hg4CsrjlwnqKOuifNkm2r3pBCou0+7WfdeN+BawIZgjCDPEGr2c+MZqaNjlH3n WUBUiTHl1Htgp7urOf7uXixaPh9vx7/9UL62/XSMgehpp1HLBBd51KnkpfXo4/Gp/6cZ E+uMTUmzVau3VMyK1AInWtcL4RGE/ht0E308I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=ot8hshbUS7E7PMlNXIso94AlH4miwlmLvXf8PdA8Stb8FwReKzWHATF7vATISM0byz nVpXbmTaN7LAIsvAE2J9w0YCzl3ikKMFTcKD3dwE6NUbu8VqqwB11vocckjvD2bHx+TG ZkJ6+mk0hGxmond6RD7q4bugJdbTwsiyPZXhY= Received: by 10.100.94.14 with SMTP id r14mr2802761anb.152.1213365590983; Fri, 13 Jun 2008 06:59:50 -0700 (PDT) Received: by 10.100.142.17 with HTTP; Fri, 13 Jun 2008 06:59:50 -0700 (PDT) Message-ID: <1c01b5070806130659ufaa761ax18de48287c7064d1@mail.gmail.com> Date: Fri, 13 Jun 2008 09:59:50 -0400 From: "Matt Brennan" To: "FreeBSD Networking" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Static NAT and PAT on 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: Fri, 13 Jun 2008 14:28:13 -0000 Hi All, I am running FreeBSD 6.2-release. I have been running PAT via natd and ipfw for some time now and it runs great. However, I continue to try and employ static NAT on this router, and as soon as I do so all other clients lose routing. My natd.conf is as below: unregistered_only use_sockets log_ipfw_denied redirect_address 10.100.1.2 66.92.79.20 alias_address 66.92.79.89 Whenever I run with this configuration all clients except the static'ed one lose routing out of the building. I have tried switching the order of the alias_address and redirect_address. Any help is appreciated. -Matt From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 14:39:19 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D4111065675; Fri, 13 Jun 2008 14:39:19 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5B1908FC23; Fri, 13 Jun 2008 14:39:19 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5DEdJrm079658; Fri, 13 Jun 2008 14:39:19 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5DEdJb0079654; Fri, 13 Jun 2008 14:39:19 GMT (envelope-from remko) Date: Fri, 13 Jun 2008 14:39:19 GMT Message-Id: <200806131439.m5DEdJb0079654@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/124540: RTM_MISS with the transit packets 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, 13 Jun 2008 14:39:19 -0000 Synopsis: RTM_MISS with the transit packets Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Fri Jun 13 14:39:07 UTC 2008 Responsible-Changed-Why: This looks like networking code :) http://www.freebsd.org/cgi/query-pr.cgi?pr=124540 From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 15:52:36 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F4C6106567D for ; Fri, 13 Jun 2008 15:52:36 +0000 (UTC) (envelope-from piso@southcross.wired.org) Received: from mail.oltrelinux.com (krisma.oltrelinux.com [194.242.226.43]) by mx1.freebsd.org (Postfix) with ESMTP id B72988FC0C for ; Fri, 13 Jun 2008 15:52:35 +0000 (UTC) (envelope-from piso@southcross.wired.org) Received: from southcross.wired.org (host-84-221-233-142.cust-adsl.tiscali.it [84.221.233.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.oltrelinux.com (Postfix) with ESMTP id EAD9A11AE49 for ; Fri, 13 Jun 2008 17:28:05 +0200 (CEST) Received: (from piso@localhost) by southcross.wired.org (8.14.2/8.14.2/Submit) id m5DFSZvQ097949 for freebsd-net@FreeBSD.org; Fri, 13 Jun 2008 17:28:35 +0200 (CEST) (envelope-from piso) Date: Fri, 13 Jun 2008 17:28:35 +0200 From: Paolo Pisati To: freebsd-net@FreeBSD.org Message-ID: <20080613152835.GA97758@tin.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at krisma.oltrelinux.com Cc: Subject: [OT] Supported wifi express card 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, 13 Jun 2008 15:52:36 -0000 Hi, as the subjects says i'm looking for a freebsd-supported wifi express card. I know i should look for an atheros-based card, but it's really difficult to find which chip a card is using without trying it out first. Googling around, it seems the belkin n express card is what i'm looking for, but i'm open to suggestions. -- bye, P. From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 15:54:06 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 836D91065672; Fri, 13 Jun 2008 15:54:06 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 003AA8FC1E; Fri, 13 Jun 2008 15:54:05 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.2/8.14.2) with ESMTP id m5DFsZ1Z099309; Fri, 13 Jun 2008 10:54:35 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m5DFsZ98099308; Fri, 13 Jun 2008 10:54:35 -0500 (CDT) (envelope-from brooks) Date: Fri, 13 Jun 2008 10:54:35 -0500 From: Brooks Davis To: Kris Kennaway Message-ID: <20080613155435.GB90190@lor.one-eyed-alien.net> References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> <20080613025157.GA90190@lor.one-eyed-alien.net> <485253AF.4000000@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline In-Reply-To: <485253AF.4000000@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Fri, 13 Jun 2008 10:54:35 -0500 (CDT) Cc: freebsd-net@FreeBSD.org, Peter Losher Subject: Re: ssh window 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, 13 Jun 2008 15:54:06 -0000 --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 13, 2008 at 01:02:07PM +0200, Kris Kennaway wrote: > Brooks Davis wrote: >> On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: >>> Randy Bush wrote: >>>> this has been a cause of great pain for a loooong time. >>>>=20 >>>> http://www.psc.edu/networking/projects/hpn-ssh/ >>>>=20 >>>> as openssh seems not to be fixing it (and i do not consider a 2mb fixed >>>> buffer to be fixed, especially not from a 100mb link here in tokyo and >>>> servers in the states, europe, and africa), perhaps i could convince >>>> freebsd net folk to do so? >>> FYI - HPN is already a build option in the openssh-portable port. >>=20 >> I do think we should strongly consider adding the rest of it to the base. >>=20 >> -- Brooks >=20 > There seem to be a couple of issues: >=20 > 1) Connection aborts during interactive use. I started using this patch= =20 > only yesterday but already a couple of times my interactive session to a= =20 > machine has aborted from typing one character to the next. It doesnt see= m=20 > to be affecting non-interactive use. I have not investigated this yet. >=20 > 2) -c none handling is a bit weird. There is no way to shut up the=20 > warnings on non-interactive connections ("WARNING: ENABLED NONE CIPHER";= =20 > yes, I know, because I WROTE THAT SCRIPT :). Also it doesn't fall back= =20 > gracefully if the other side doesn't support -c none; it just aborts the= =20 > collection. This means you can't automatically interoperate with a non-H= PN=20 > server if you want to use 'none' encryption. This is not related to the= =20 > buffer handling but it is part of the same patch set. I really like the= =20 > idea of -c none, but I think they have gone overboard with the paranoia. It is worth noting that over most people's WAN's the none cipher is pretty pointless since you can do nearly 200Mbps with arcfour and a decent = CPU (IIRC the graphs are several years old). -- Brooks --ftEhullJWpWg/VHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIUpg6XY6L6fI4GtQRAg4cAKDRUHUH7319fZTB6pNLGmo7q8NuxQCffvFq LmwjEZqXl1m+TtlHheO6zhQ= =ePEq -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq-- From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 17:29:50 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F9B21065671; Fri, 13 Jun 2008 17:29:50 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id 8D31B8FC20; Fri, 13 Jun 2008 17:29:49 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id TXQ30648; Fri, 13 Jun 2008 10:29:48 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 2ED344500E; Fri, 13 Jun 2008 10:29:47 -0700 (PDT) To: Garrett Wollman In-Reply-To: Your message of "Thu, 12 Jun 2008 23:11:13 EDT." <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1213378187_53832P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 13 Jun 2008 10:29:47 -0700 From: "Kevin Oberman" Message-Id: <20080613172947.2ED344500E@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; X-Sender: X-To_Name: Garrett Wollman X-To_Domain: hergotha.csail.mit.edu X-To: Garrett Wollman X-To_Email: wollman@hergotha.csail.mit.edu X-To_Alias: wollman Cc: brooks@freebsd.org, net@freebsd.org Subject: Re: ssh window 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, 13 Jun 2008 17:29:50 -0000 --==_Exmh_1213378187_53832P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 12 Jun 2008 23:11:13 -0400 (EDT) > From: Garrett Wollman > Sender: owner-freebsd-net@freebsd.org > > In article <20080613025157.GA90190@lor.one-eyed-alien.net>, Brooks > Davis writes: > > >On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote: > >> FYI - HPN is already a build option in the openssh-portable port. > > > >I do think we should strongly consider adding the rest of it to the base. > > Am I the only one who would be happier if openssh were not in the base > system at all? I always have to install the port anyway; having it in > the base just gives me more files I need to delete after an install. > (Heimdal is the other big culprit.) Build it with OVERRIDE_BASE and make the required entry in /etc/make.conf (pre-V7) or /etc/sys.conf (V7) so that rebuilding the system does not over-write them. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1213378187_53832P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIUq6Lkn3rs5h7N1ERAtYlAJ9XLNRrOQWeripuqmbbnh+xRmxBhwCfUP5v aUKazCU1frhdhNMJfWBH1Ic= =UCoM -----END PGP SIGNATURE----- --==_Exmh_1213378187_53832P-- From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 17:37:14 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BD70106566C for ; Fri, 13 Jun 2008 17:37:14 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id C17DD8FC1A for ; Fri, 13 Jun 2008 17:37:13 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 13259 invoked from network); 13 Jun 2008 17:10:30 -0000 Received: from unknown (HELO ?10.0.0.128?) (spawk@128.238.64.31) by acm.poly.edu with AES256-SHA encrypted SMTP; 13 Jun 2008 17:10:30 -0000 Message-ID: <4852A9F3.4000107@acm.poly.edu> Date: Fri, 13 Jun 2008 13:10:11 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: Paolo Pisati References: <20080613152835.GA97758@tin.it> In-Reply-To: <20080613152835.GA97758@tin.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: [OT] Supported wifi express card 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, 13 Jun 2008 17:37:14 -0000 Someone I know got a http://www.buy.com/prod/thinkpad-11a-b-g-wireless-lan-mini-pci-express-adapter-network-adapter/q/loc/101/201992199.html and it works well. -Boris Paolo Pisati wrote: > Hi, > > as the subjects says i'm looking for a freebsd-supported wifi express card. > I know i should look for an atheros-based card, but it's really difficult to find > which chip a card is using without trying it out first. > > Googling around, it seems the belkin n express card is what i'm > looking for, but i'm open to suggestions. > From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 18:43:41 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3B74106566C for ; Fri, 13 Jun 2008 18:43:41 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 6ECF58FC17 for ; Fri, 13 Jun 2008 18:43:40 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.13.8/8.13.8) with ESMTP id m5DIhdK6078365; Fri, 13 Jun 2008 14:43:39 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.13.8/8.13.8/Submit) id m5DIhdtS078362; Fri, 13 Jun 2008 14:43:39 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18514.49115.708560.587859@hergotha.csail.mit.edu> Date: Fri, 13 Jun 2008 14:43:39 -0400 From: Garrett Wollman To: Kris Kennaway In-Reply-To: <48525428.9000703@FreeBSD.org> References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> <200806130311.m5D3BD5m063745@hergotha.csail.mit.edu> <48525428.9000703@FreeBSD.org> X-Mailer: VM 7.17 under 21.4 (patch 21) "Educational Television" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Fri, 13 Jun 2008 14:43:39 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on hergotha.csail.mit.edu Cc: net@FreeBSD.org Subject: Re: ssh window 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, 13 Jun 2008 18:43:41 -0000 < said: > Garrett Wollman wrote: >> Am I the only one who would be happier if openssh were not in the base >> system at all? > Quite possibly :) > I don't think it's at all viable to ship FreeBSD without an ssh client > in this day and age. If that were what I had suggested, you might have a point. I'm want FreeBSD to ship with an ssh client, too. I just want it shipped as a package, so that it's easier to delete when I'm ready to replace it with one that meets my requirements (about an hour after install). Having it be easier to update when there's a security issue would be an added bonus. -GAWollman From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 19:02:58 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3F921065672 for ; Fri, 13 Jun 2008 19:02:58 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id 55A278FC21 for ; Fri, 13 Jun 2008 19:02:58 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id TZP15857; Fri, 13 Jun 2008 12:02:57 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0B4AE4500E; Fri, 13 Jun 2008 12:02:56 -0700 (PDT) To: Garrett Wollman In-Reply-To: Your message of "Fri, 13 Jun 2008 14:43:39 EDT." <18514.49115.708560.587859@hergotha.csail.mit.edu> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1213383776_53832P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 13 Jun 2008 12:02:56 -0700 From: "Kevin Oberman" Message-Id: <20080613190256.0B4AE4500E@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;;; X-Sender: X-To_Name: Garrett Wollman X-To_Domain: bimajority.org X-To: Garrett Wollman X-To_Email: wollman@bimajority.org X-To_Alias: wollman Cc: Kris Kennaway , net@FreeBSD.org Subject: Re: ssh window 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, 13 Jun 2008 19:02:58 -0000 --==_Exmh_1213383776_53832P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Fri, 13 Jun 2008 14:43:39 -0400 > From: Garrett Wollman > Sender: owner-freebsd-net@freebsd.org > > < said: > > > Garrett Wollman wrote: > >> Am I the only one who would be happier if openssh were not in the base > >> system at all? > > > Quite possibly :) > > > I don't think it's at all viable to ship FreeBSD without an ssh client > > in this day and age. > > If that were what I had suggested, you might have a point. I'm want > FreeBSD to ship with an ssh client, too. I just want it shipped as a > package, so that it's easier to delete when I'm ready to replace it > with one that meets my requirements (about an hour after install). > Having it be easier to update when there's a security issue would be > an added bonus. Replacing the base ssh with the port is utterly trivial. You already are setting configuration options, so OVERWRITE_BASE is no more than a few key presses and a one-liner in make.conf or src.conf is pretty trivial. V7---Add "WITHOUT_OPENSSH=" to /etc/src.conf Pre-V7--=-Add "NO_OPENSSH=" to /etc/make.conf That is all it takes. We use SmartCards for authentication, so I already have a bunch of systems that are configured this way. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1213383776_53832P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIUsRgkn3rs5h7N1ERAmpZAKCdvYUce/MRDxu2kIFkrKsjfQfk+wCeNUtf JqOQJLDn0IwMhZE6yJDdsj8= =ctW2 -----END PGP SIGNATURE----- --==_Exmh_1213383776_53832P-- From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 21:08:26 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61389106566B for ; Fri, 13 Jun 2008 21:08:26 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id 2CFB78FC14 for ; Fri, 13 Jun 2008 21:08:26 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-179-28.hsd1.fl.comcast.net ([76.108.179.28] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1K7GTW-0003yb-8p for freebsd-net@freebsd.org; Fri, 13 Jun 2008 17:06:22 -0400 Message-ID: <4852E23E.2040505@gtcomm.net> Date: Fri, 13 Jun 2008 17:10:22 -0400 From: Paul User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Route messages 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, 13 Jun 2008 21:08:26 -0000 Get these with GRE tunnel on FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Sun May 11 19:00:57 EDT 2008 :/usr/obj/usr/src/sys/ROUTER amd64 But do not get them with 7.0-RELEASE Any ideas what changed? :) Wish there was some sort of changelog.. # of messages per second seems consistent with packets per second on GRE interface.. No impact in routing, but definitely impact in cpu usage for all processes monitoring the route messages. got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 16:58:37 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default got message of size 160 on Fri Jun 13 17:08:16 2008 RTM_MISS: Lookup failed on this address: len 160, pid: 0, seq 0, errno 0, flags: locks: inits: sockaddrs: default From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 23:03:28 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35106106566B; Fri, 13 Jun 2008 23:03:28 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2038FC14; Fri, 13 Jun 2008 23:03:25 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4852FCBD.6060702@FreeBSD.org> Date: Sat, 14 Jun 2008 01:03:25 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Brooks Davis References: <4851CC95.8070902@psg.com> <4851CD9D.3010801@isc.org> <20080613025157.GA90190@lor.one-eyed-alien.net> <485253AF.4000000@FreeBSD.org> <20080613155435.GB90190@lor.one-eyed-alien.net> In-Reply-To: <20080613155435.GB90190@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, Peter Losher Subject: Re: ssh window 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, 13 Jun 2008 23:03:28 -0000 Brooks Davis wrote: > It is worth noting that over most people's WAN's the none cipher is > pretty pointless since you can do nearly 200Mbps with arcfour and a decent CPU > (IIRC the graphs are several years old). In my case I'm CPU bound from other processes, so reducing SSH overhead will have a net benefit. Kris From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 23:40:16 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFA33106564A for ; Fri, 13 Jun 2008 23:40:16 +0000 (UTC) (envelope-from crapsh@MonkeyBrains.NET) Received: from ape.monkeybrains.net (ape.monkeybrains.net [208.69.40.11]) by mx1.freebsd.org (Postfix) with ESMTP id B25628FC12 for ; Fri, 13 Jun 2008 23:40:16 +0000 (UTC) (envelope-from crapsh@MonkeyBrains.NET) Received: from Penelope-Thomas-Computer.local (adsl-75-63-19-43.dsl.pltn13.sbcglobal.net [75.63.19.43]) (authenticated bits=0) by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id m5DNe8AN094902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Jun 2008 16:40:09 -0700 (PDT) (envelope-from crapsh@MonkeyBrains.NET) Message-ID: <4853055C.2030303@MonkeyBrains.NET> Date: Fri, 13 Jun 2008 16:40:12 -0700 From: Rudy User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> In-Reply-To: <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on pita.monkeybrains.net X-Virus-Status: Clean Subject: Re: em0: watchdog timeout -- resetting 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, 13 Jun 2008 23:40:16 -0000 Jack Vogel wrote: > Did you ever install the fix to the 82573 NIC eeprom? Just saw the "watchdog" error using an Intel Pro Quad PT card... it has the '82571EB' chip on it. -- Do those cards need the eeprom 'fix'? -- or is related to kern/122928 -- how does one go about disabling the watchdog? (turning off acpi?) Thanks, Rudy SYSTEM INFO: # grep Exp /usr/src/sys/dev/em/if_em.c /*$FreeBSD: src/sys/dev/em/if_em.c,v 1.184.2.3 2008/05/21 21:34:05 jfv Exp $*/ # pciconf -lv | grep -A 4 em2 em2@pci0:6:0:0: class=0x020000 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB Gigabit Ethernet Controller' class = network subclass = ethernet # sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 6.9.5 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x10a4 subvendor=0x8086 subdevice=0x10a4 class=0x020000 dev.em.2.%parent: pci6 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 # ifconfig em2 em2: flags=8843 metric 0 mtu 1500 options=1db ether 00:15:17:78:99:72 inet 10.10.30.154 netmask 0xfffffffc broadcast 10.10.30.155 media: Ethernet autoselect (1000baseTX ) status: active # uname -a FreeBSD example.monkeybrains.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Jun 3 16:43:19 PDT 2008 root@buildbox.monkeybrains.net:/usr/obj/usr/src/sys/ROUTER i386 # grep em2 /var/log/messages Jun 11 23:08:34 example kernel: em2: port 0x3000-0x301f mem 0xd8120000-0xd813ffff,0xd8100000-0xd811ffff irq 17 at device 0.0 on pci6 Jun 11 23:08:34 example kernel: em2: Using MSI interrupt Jun 11 23:08:34 example kernel: em2: [FILTER] Jun 11 23:08:34 example kernel: em2: Ethernet address: 00:15:17:78:99:72 Jun 11 23:18:08 example kernel: em2: link state changed to UP Jun 13 00:27:22 example kernel: em2: watchdog timeout -- resetting Jun 13 00:27:22 example kernel: em2: link state changed to DOWN Jun 13 00:27:25 example kernel: em2: link state changed to UP Jun 13 03:37:52 example kernel: em2: watchdog timeout -- resetting Jun 13 03:37:52 example kernel: em2: link state changed to DOWN Jun 13 03:37:55 example kernel: em2: link state changed to UP Jun 13 05:17:18 example kernel: em2: watchdog timeout -- resetting Jun 13 05:17:18 example kernel: em2: link state changed to DOWN Jun 13 05:17:22 example kernel: em2: link state changed to UP Jun 13 05:17:23 example kernel: em2: link state changed to DOWN Jun 13 05:17:25 example kernel: em2: link state changed to UP Jun 13 06:54:47 example kernel: em2: watchdog timeout -- resetting Jun 13 06:54:47 example kernel: em2: link state changed to DOWN Jun 13 06:54:51 example kernel: em2: link state changed to UP Jun 13 06:59:22 example kernel: em2: watchdog timeout -- resetting Jun 13 06:59:22 example kernel: em2: link state changed to DOWN Jun 13 06:59:25 example kernel: em2: link state changed to UP From owner-freebsd-net@FreeBSD.ORG Fri Jun 13 23:49:35 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95384106567E for ; Fri, 13 Jun 2008 23:49:35 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id E83968FC2C for ; Fri, 13 Jun 2008 23:49:34 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (jqkh1yj7aic21f0s@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id m5DNEgdd014681; Fri, 13 Jun 2008 16:14:42 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id m5DNEe88014680; Fri, 13 Jun 2008 16:14:40 -0700 (PDT) (envelope-from jmg) Date: Fri, 13 Jun 2008 16:14:40 -0700 From: John-Mark Gurney To: Tom Judge Message-ID: <20080613231440.GH3767@funkthat.com> Mail-Followup-To: Tom Judge , Bill Moran , R J , freebsd-net@freebsd.org References: <20080610120222.9e2760fe.wmoran@collaborativefusion.com> <48502F2C.7090505@tomjudge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48502F2C.7090505@tomjudge.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hydrogen.funkthat.com [127.0.0.1]); Fri, 13 Jun 2008 16:14:43 -0700 (PDT) Cc: R J , Bill Moran , freebsd-net@freebsd.org Subject: Re: tcpdump/snort to capture chat sessions 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, 13 Jun 2008 23:49:35 -0000 Tom Judge wrote this message on Wed, Jun 11, 2008 at 15:01 -0500: > Bill Moran wrote: > >In response to R J : > > > >>I am trying to use tcpdump (or snort, but they are both behaving the same > >>in this case) to capture all the lines or contents of an msn > >>chat session, the actual conversation. I am getting partial output; i.e, > >>I'll only get half of a sentence, and I don't see the rest of the lines. > >>And ofcourse, alot of it seems to be hex or obfuscated html? > >> > >>What switches do I need to capture the entire lines of text? > > > >Don't know about snort, but with tcpdump use -s0 > > > This is a good start however you are not guaranteed to see the whole > chat message in a single TCP packet. If you are looking for something > more advanced you will have to write a program around pcap/bpf or > similar to read the TCP stream. such as tcpflow which read tcpdump streams and outputs each TCP byte stream... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@FreeBSD.ORG Sat Jun 14 02:51:14 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93EA1106567D; Sat, 14 Jun 2008 02:51:14 +0000 (UTC) (envelope-from prvs=105103e53c=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id F3A978FC12; Sat, 14 Jun 2008 02:51:13 +0000 (UTC) (envelope-from prvs=105103e53c=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1213410760; x=1214015560; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=t6yV8cNO+1Q0vS8ciKLD9 EUKlStdZO2aWThOhHK/PdI=; b=FTpxfknV8gIGKi8SvtZ0Cyar1DzmgY8BJ5kyF nyHRd4LTN4F+aAGGbIuzVJfHhRTqimkvZ4OZlPjo2pzRkAdOf1eF86uoBCHopIO5 3AtUfNh81eVxKNj1m7hwWv0oQ2Ph9JgnXo/jUmJTdTLphuQTp+6880/bQS4eHZ4R DXAnls= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50005758406.msg; Sat, 14 Jun 2008 03:32:39 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=105103e53c=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <224D75AFD2724FC1A3E6E1004AB87F07@multiplay.co.uk> From: "Steven Hartland" To: "Garrett Wollman" , "Kevin Oberman" References: <20080613172947.2ED344500E@ptavv.es.net> Date: Sat, 14 Jun 2008 03:32:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 14 Jun 2008 03:32:40 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 14 Jun 2008 03:32:40 +0100 Cc: brooks@freebsd.org, net@freebsd.org Subject: Re: ssh window 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, 14 Jun 2008 02:51:14 -0000 >> Date: Thu, 12 Jun 2008 23:11:13 -0400 (EDT) >> In article <20080613025157.GA90190@lor.one-eyed-alien.net>, Brooks >> Am I the only one who would be happier if openssh were not in the base >> system at all? I always have to install the port anyway; having it in >> the base just gives me more files I need to delete after an install. >> (Heimdal is the other big culprit.) > > Build it with OVERRIDE_BASE and make the required entry in >/etc/make.conf (pre-V7) or /etc/sys.conf (V7) so that rebuilding the >system does not over-write them. Unfortunately this doesnt stop sysinstall breaking rc.conf by adding back in sshd_enable="YES" every time its used :( Regards 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 Sat Jun 14 04:09:00 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE35E1065688; Sat, 14 Jun 2008 04:09:00 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id BE2FA8FC1C; Sat, 14 Jun 2008 04:09:00 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id UJU01409; Fri, 13 Jun 2008 20:58:09 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id E118D45047; Fri, 13 Jun 2008 20:58:06 -0700 (PDT) To: "Steven Hartland" In-Reply-To: Your message of "Sat, 14 Jun 2008 03:32:39 BST." <224D75AFD2724FC1A3E6E1004AB87F07@multiplay.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1213415886_83238P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 13 Jun 2008 20:58:06 -0700 From: "Kevin Oberman" Message-Id: <20080614035806.E118D45047@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; X-Sender: X-To_Name: Steven Hartland X-To_Domain: multiplay.co.uk X-To: "Steven Hartland" X-To_Email: killing@multiplay.co.uk X-To_Alias: killing Cc: brooks@freebsd.org, Garrett Wollman , net@freebsd.org Subject: Re: ssh window 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, 14 Jun 2008 04:09:01 -0000 --==_Exmh_1213415886_83238P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: "Steven Hartland" > Date: Sat, 14 Jun 2008 03:32:39 +0100 > > >> Date: Thu, 12 Jun 2008 23:11:13 -0400 (EDT) > >> In article <20080613025157.GA90190@lor.one-eyed-alien.net>, Brooks > >> Am I the only one who would be happier if openssh were not in the base > >> system at all? I always have to install the port anyway; having it in > >> the base just gives me more files I need to delete after an install. > >> (Heimdal is the other big culprit.) > > > > Build it with OVERRIDE_BASE and make the required entry in > >/etc/make.conf (pre-V7) or /etc/sys.conf (V7) so that rebuilding the > >system does not over-write them. > > Unfortunately this doesnt stop sysinstall breaking rc.conf by > adding back in sshd_enable="YES" every time its used :( If you OVERWRITE_BASE, sshd is written into /usr/sbin, so the stock /etc/rc.d/ntpd works just fine. I don't see the need to change to the one in the port when the port replaces the system version. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1213415886_83238P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIU0HOkn3rs5h7N1ERArCGAKCXuphrH1w8mfg7m6GLh329aO7V2ACfb1/J iDpy1ePxLU8mlHVcbjX4zGA= =Yr9a -----END PGP SIGNATURE----- --==_Exmh_1213415886_83238P-- From owner-freebsd-net@FreeBSD.ORG Sat Jun 14 05:41:42 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6D8F10656A8 for ; Sat, 14 Jun 2008 05:41:42 +0000 (UTC) (envelope-from crapsh@monkeybrains.net) Received: from ape.monkeybrains.net (ape.monkeybrains.net [208.69.40.11]) by mx1.freebsd.org (Postfix) with ESMTP id D1C9B8FC24 for ; Sat, 14 Jun 2008 05:41:42 +0000 (UTC) (envelope-from crapsh@monkeybrains.net) Received: from monchichi.monkeybrains.net (adsl-75-63-19-43.dsl.pltn13.sbcglobal.net [75.63.19.43]) (authenticated bits=0) by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id m5E5fgGF062762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Jun 2008 22:41:42 -0700 (PDT) (envelope-from crapsh@monkeybrains.net) Message-ID: <48535A11.4020003@monkeybrains.net> Date: Fri, 13 Jun 2008 22:41:37 -0700 From: Rudy User-Agent: Thunderbird 2.0.0.12 (X11/20080310) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> <4853055C.2030303@MonkeyBrains.NET> In-Reply-To: <4853055C.2030303@MonkeyBrains.NET> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on pita.monkeybrains.net X-Virus-Status: Clean Subject: Re: em0: watchdog timeout -- resetting 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, 14 Jun 2008 05:41:43 -0000 > Just saw the "watchdog" error using an Intel Pro Quad PT card... more info: doing about 100Mbps plugged into a Cisco 2960: Gi0/23 mango-em2 connected a-full a-1000 10/100/1000BaseTX Would setting the duplex and speed manually (instead of using auto-negotionation) help prevent the watchdog timer? What is the watchdog timeout for? Does the driver catch stalled interface conditions? Rudy