From owner-freebsd-net@FreeBSD.ORG Sun May 27 06:40:05 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FA3A16A400 for ; Sun, 27 May 2007 06:40:05 +0000 (UTC) (envelope-from antinvidia@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 5648013C44C for ; Sun, 27 May 2007 06:40:05 +0000 (UTC) (envelope-from antinvidia@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so565440wag for ; Sat, 26 May 2007 23:40:03 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=oEqtMDNFl7RP+T7XGQPXitA6kisTSP2jjKUw9Q1nYqD/d+fKZdxJnmFoNXcPMjFea4HY5geXYjpchVXZ5bi907kuvJoqs2NeBf/p9gU7IHQShSmoMx9HHRqUcIttsobLukcyfx2LHqayaFD7dDIMc7XeFsW2muzOjpF3y/3lECk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=e0a9+YC7zb+nT4iM1iAXUEk5XFets5AwEVOuhGi7uCyMzVnYwEvwR1/dJPDIItuWh9bkjdG34Cqn44uzEG/gdw1aMKT9g8M7c/VY6SFcPNdL5a52LF+SKk9gzfOc9WmKiwt3PnAuIS+LSDmmaHB9jvKTRCTqujL6rVHRsh26o/4= Received: by 10.114.209.1 with SMTP id h1mr2306892wag.1180246331077; Sat, 26 May 2007 23:12:11 -0700 (PDT) Received: by 10.115.54.2 with HTTP; Sat, 26 May 2007 23:12:11 -0700 (PDT) Message-ID: Date: Sun, 27 May 2007 06:12:11 +0000 From: MQ To: stefan.lambrev@sun-fish.com In-Reply-To: <462E3B4A.5030307@sun-fish.com> MIME-Version: 1.0 References: <462E3B4A.5030307@sun-fish.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: em0 - bge0 failed to work at 1000baseTX X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 06:40:05 -0000 2007/4/24, Stefan Lambrev : > > Hello, > > I'm trying to get two gigabit network cards to work together. > > em0: port > 0x1000-0x101f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at > device 25.0 on pci0 > > em0@pci0:25:0: class=0x020000 card=0x2800103c chip=0x104a8086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > and broadcom on the other end: > > bge0: mem 0xf4100000-0xf410ffff > irq 16 at device 0.0 on pci8 > > bge0@pci8:0:0: class=0x020000 card=0x30a3103c chip=0x16fd14e4 rev=0x21 > hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5753M NetXtreme Gigabit Ethernet PCI Express' > class = network > subclass = ethernet > > > When I connect both networks without switch e.g. directly they auto > negotiate to: > media: Ethernet autoselect (100baseTX ) > but I want 1000baseTX :( > > First thing that I tried was to force both network card with: > ifconfig bge0/em0 media 1000baseTX mediaopt full-duplex > but this lead to status: no carrier > > Second step was to set bge link0 and em0 link1, but still "no carrier" > (from bge manual) > > On the machine with em card I have linux installed so I boot under linux > and then everything works > with autoselect, and I'm able to transfer with speed +50MB/s. > > When I forced both network cards to 1000baseTX I notice this: > > em0 media: Ethernet 1000baseTX (autoselect) > > ^^^^^^^^ > bge0 media: Ethernet 1000baseTX (none) > > ^^^^ > > Something else that is quite strange is that when I change em media from > autoselec to 1000baseTX, > I see that for 2-3 seconds there is a connection between cards (e.g. > status: active), but just for 2-3 seconds > and then it disconnects again. (ping between hosts works for 2 seconds) > At this time ifconfig shows: > em0 > media: Ethernet 1000baseTX > > ^^^^^^ no autoselect here ? > status: active > > and bge0: > media: Ethernet autoselect (1000baseTX ) ( I left bge to > autoselect at some point as I saw it does not change a thing..) > status: active > > I compiled new kernel with > #define EM_MASTER_SLAVE 2 (and then 3) > in if_em.h (as I'm suspecting em driver ..) > but still no success. > > Last thing that I notice while (re)booting freebsd server with em0 is that > during starting program and rc scripts the status of the network changed > from 100mbps -> 1000mbps -> no carrier -> 100mbps. > > So any ideas how to get my network working at gigabit speeds? :) > > P.S. both machines are running freebsd 6.2 stable - em0 is i386 and bge0 > is on amd64. > em0 was tested with 6.2-release too. > > Thanks in advance. > > -- > > Best Wishes, > Stefan Lambrev > ICQ# 24134177 > > _______________________________________________ > 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" > Actually, I'd rather consider the bge(4) has some problems with its media negotiation. It seems that the problem you described was just the same with mine as I had mentioned earlier this year. I encountered the problem as I wanted a BCM5701 and a BCM5780 to connect to each other with 1000TX duplex. From owner-freebsd-net@FreeBSD.ORG Sun May 27 09:53:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38A5216A474 for ; Sun, 27 May 2007 09:53:10 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id E7D2213C48A for ; Sun, 27 May 2007 09:53:09 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id B730F1B10EE7; Sun, 27 May 2007 11:53:08 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id B391A1B10EA4; Sun, 27 May 2007 11:53:08 +0200 (CEST) Message-ID: <46595504.4060803@sun-fish.com> Date: Sun, 27 May 2007 12:53:08 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: MQ References: <462E3B4A.5030307@sun-fish.com> In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: freebsd-net@freebsd.org Subject: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stefan.lambrev@sun-fish.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2007 09:53:10 -0000 Hi, MQ wrote: > > Actually, I'd rather consider the bge(4) has some problems with its > media negotiation. It seems that the problem you described was just > the same with mine as I had mentioned earlier this year. I encountered > the problem as I wanted a BCM5701 and a BCM5780 to connect to each > other with 1000TX duplex. Hm seems my last mail got lost and didn't reach the mail list. I replaced the broadcom device with other intel gigabit card: em1: port 0x2000-0x201f mem 0xb8c00000-0xb8c1ffff,0xb8400000-0xb87fffff irq 19 at device 0.1 on pci4 em1: Ethernet address: 00:15:17:1b:08:ed em1: [FILTER] on the other end is the "problematic" network card (that does work under linux&windows): em0: port 0x2000-0x201f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at device 25.0 on pci0 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xf0500000 em0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to vector 49 em0: using IRQ 256 for MSI em0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xf0524000 em0: bpf attached em0: Ethernet address: 00:0f:fe:4e:78:16 em0: [FILTER] When I verbose boot the server I see: em0: Link is up 1000 Mbps Full Duplex em0: link state changed to UP em0: Link is Down em0: link state changed to DOWN em0: Link is up 100 Mbps Full Duplex em0: link state changed to UP if I type ifconfig em0 media auto it happens exactly the same: card down card negotiate to 1000 Mbps Full Duplex card up - netowrk work for 2 seconds card down card negotiate to 100Mbps Full Duplex card up. If i force 1000mbps network : ifconfig em0 media 1000basetx mediaopt full-duplex 2 seconds latter I see: status: no carrier Both machines are running FreeBSD 7.0-CURRENT from ~2 days ago. A checked up connection between bge0 and the new server with intel card and everything works fine. -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-net@FreeBSD.ORG Sun May 27 10:41:20 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A54F16A7A5 for ; Sun, 27 May 2007 10:41:20 +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 CE7FA13C4CC for ; Sun, 27 May 2007 10:41:19 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 38063 invoked from network); 27 May 2007 10:12:08 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.42.176) by acm.poly.edu with AES256-SHA encrypted SMTP; 27 May 2007 10:12:08 -0000 Message-ID: <465959FF.4040401@acm.poly.edu> Date: Sun, 27 May 2007 06:14:23 -0400 From: Boris Kochergin User-Agent: Thunderbird 1.5.0.7 (X11/20061009) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: System hang with Ralink RT2661 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 10:41:20 -0000 Hi. I got an "SMC SMCWPCI-GM" card the other day, which is one of these: May 27 01:16:55 router kernel: ral0: mem 0xf4000000-0xf4007fff irq 10 at device 13.0 on pci0 May 27 01:16:55 router kernel: ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR) I put it into a Pentium III machine (which has PCI 2.2, per the ral(4) man page) running a 7-CURRENT build from earlier today with a GENERIC kernel, and attempted to connect to my wireless network, the access point of which is an Atheros 5212 card, which has been serving Prism and other Atheros cards for months. The RT2661 card associated fine and was able to carry out lightweight operations like pinging and HTTP requests, but when I attempted to use it to send or receive any heavy traffic (a few dozen KiB/second), the system froze. I was able to toggle the caps lock/num lock lights, and if I did something to make the system beep (i.e. by pressing ALT+F10 when there was no virtual terminal running there), the beep would ring out endlessly. It may also be worth mentioning that the system was unresponsive to ACPI (via the power button) and that the same RT2661 card in the same machine has no trouble sniffing over 2 MiB/second of traffic via tcpdump. I'll be happy to provide any other information that may be deemed useful. Thanks. -Boris From owner-freebsd-net@FreeBSD.ORG Sun May 27 11:08:23 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02DD116A47E for ; Sun, 27 May 2007 11:08:22 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2DA2C13C483 for ; Sun, 27 May 2007 11:08:21 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (8.13.8/8.13.8) with ESMTP id l4RAwbvQ012524 for ; Sun, 27 May 2007 20:28:37 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.5) with ESMTP id ; Sun, 27 May 2007 20:38:15 +0930 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Sun, 27 May 2007 20:38:14 +0930 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.13.8/8.13.8) with ESMTP id l4RB7l2J080003; Sun, 27 May 2007 19:07:47 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.13.8/8.13.8/Submit) id l4RB7fda080002; Sun, 27 May 2007 19:07:41 +0800 (WST) (envelope-from wilkinsa) Date: Sun, 27 May 2007 19:07:41 +0800 From: "Wilkinson, Alex" To: freebsd-net@freebsd.org, Andrei Manescu Message-ID: <20070527110741.GC78927@obelix.dsto.defence.gov.au> Mail-Followup-To: freebsd-net@freebsd.org, Andrei Manescu References: <000e01c79f03$b2cfce70$5501a8c0@ivorde> <08556012-CA57-4B2A-A142-F5C1BC8D9009@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <08556012-CA57-4B2A-A142-F5C1BC8D9009@mac.com> Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.15 (2007-04-06) X-OriginalArrivalTime: 27 May 2007 11:08:15.0093 (UTC) FILETIME=[52892A50:01C7A04F] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-3.6.1039-15198.001 X-TM-AS-Result: No--1.092000-8.000000-31 Content-Transfer-Encoding: 7bit Cc: Subject: Re: two public ip addresses on one interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2007 11:08:23 -0000 0n Fri, May 25, 2007 at 01:17:39PM -0700, Chuck Swiger wrote: > If your aliases are part of the same subnet as the "primary" or first configured IP, then you want to > use the all-1's netmask. In your case, however, the second IP is part of a completely different subnet, > and you can (and should) use a /24 netmask.... I have always wondered why we need to use the "all-1's" netmask. Why is this ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-net@FreeBSD.ORG Sun May 27 17:06:32 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 21BA016A4C2 for ; Sun, 27 May 2007 17:06:32 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.freebsd.org (Postfix) with ESMTP id E959B13C44B for ; Sun, 27 May 2007 17:06:31 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from mymb.local (t050096.ppp.asahi-net.or.jp [203.189.50.96]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id A8B1D7301E; Mon, 28 May 2007 01:33:32 +0900 (JST) Date: Mon, 28 May 2007 01:33:26 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: "Bruce M. Simpson" In-Reply-To: <46523DDA.30300@icsi.berkeley.edu> References: <200705131837.l4DIbFNw022595@freefall.freebsd.org> <46523DDA.30300@icsi.berkeley.edu> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-net@FreeBSD.org Subject: Re: kern/108197: [ipv6] IPv6-related crash if if_delmulti X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 17:06:32 -0000 At Tue, 22 May 2007 01:48:26 +0100, "Bruce M. Simpson" wrote: > > Synopsis: [ipv6] IPv6-related crash if if_delmulti > > > > Responsible-Changed-From-To: freebsd-net->bms > > Responsible-Changed-By: andre > > Responsible-Changed-When: Sun May 13 18:36:25 UTC 2007 > > Responsible-Changed-Why: > > Send over to BMS. He's active in that area and may have fixed the bug already. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=108197 > > > > Sorry, but I have no time to look at this at the moment. Is someone else > free to look at it? > The fix probably needs to be borrowed from the IPv4 code which adds an > address to an interface. Could you be more specific about the 'IPv4 code'? I've briefly looked at the both netinet and netinet6 code path shown in the PR but cannot be sure about which change you meant. Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-net@FreeBSD.ORG Sun May 27 17:34:02 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D82616A421 for ; Sun, 27 May 2007 17:34:02 +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 66E7B13C458 for ; Sun, 27 May 2007 17:34:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so625997wag for ; Sun, 27 May 2007 10:34:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RopARPNNGWlg9Sj45p9OvPxrqMpo0qMXFizcRGq/74X4ivAoknj6QOQMPxPwgnizhHoewHyQtuPc98K0rvDPNvExxAY/JENg011qt8qdcEp32kEJcN5ZwozhKhrmHyatAaORKSxdEocGhS04Fk9+NwU+DLZACEP8Hm5Uh3TwAxE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LB3bByO/R5/bh2Kp1w/JB4H2Tsl4QUWP84PRPixALwepOsyQbkWDZv7H+RqK6PZG/wra93N2truH2blqXGlSLjF24AmDVFPy5PX+/CKNPYmidjAFv6M0DH2kgb7MAyucEvoL3VdnOQCUh5KMRkg99QM8CT6yXwNdhJIcodaL39A= Received: by 10.115.92.2 with SMTP id u2mr2489900wal.1180287241905; Sun, 27 May 2007 10:34:01 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Sun, 27 May 2007 10:34:01 -0700 (PDT) Message-ID: <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> Date: Sun, 27 May 2007 10:34:01 -0700 From: "Jack Vogel" To: stefan.lambrev@sun-fish.com In-Reply-To: <46595504.4060803@sun-fish.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> Cc: freebsd-net@freebsd.org, MQ Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 17:34:02 -0000 Stefan, I am having a long weekend and am supposed to be doing something other than this :) However, when I get back in the office on Tuesday I will see if I can repro this, so just to make sure, tell me what the PCI ID of the two cards are when it fails with Intel on both sides, that should be easy. Jack On 5/27/07, Stefan Lambrev wrote: > Hi, > > MQ wrote: > > > > Actually, I'd rather consider the bge(4) has some problems with its > > media negotiation. It seems that the problem you described was just > > the same with mine as I had mentioned earlier this year. I encountered > > the problem as I wanted a BCM5701 and a BCM5780 to connect to each > > other with 1000TX duplex. > Hm seems my last mail got lost and didn't reach the mail list. > > I replaced the broadcom device with other intel gigabit card: > em1: port > 0x2000-0x201f mem 0xb8c00000-0xb8c1ffff,0xb8400000-0xb87fffff irq 19 at > device 0.1 on pci4 > em1: Ethernet address: 00:15:17:1b:08:ed > em1: [FILTER] > > on the other end is the "problematic" network card (that does work under > linux&windows): > em0: port > 0x2000-0x201f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at > device 25.0 on pci0 > em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xf0500000 > em0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 256 to vector 49 > em0: using IRQ 256 for MSI > em0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xf0524000 > em0: bpf attached > em0: Ethernet address: 00:0f:fe:4e:78:16 > em0: [FILTER] > > When I verbose boot the server I see: > em0: Link is up 1000 Mbps Full Duplex > em0: link state changed to UP > em0: Link is Down > em0: link state changed to DOWN > em0: Link is up 100 Mbps Full Duplex > em0: link state changed to UP > > if I type ifconfig em0 media auto it happens exactly the same: > card down > card negotiate to 1000 Mbps Full Duplex > card up - netowrk work for 2 seconds > card down > card negotiate to 100Mbps Full Duplex > card up. > > If i force 1000mbps network : > ifconfig em0 media 1000basetx mediaopt full-duplex > 2 seconds latter I see: status: no carrier > > Both machines are running FreeBSD 7.0-CURRENT from ~2 days ago. > > A checked up connection between bge0 and the new server with intel card > and everything works fine. > > > -- > > Best Wishes, > Stefan Lambrev > ICQ# 24134177 > > _______________________________________________ > 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 May 27 17:53:36 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BCE716A400 for ; Sun, 27 May 2007 17:53:36 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id DF2A813C43E for ; Sun, 27 May 2007 17:53:35 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id 706F11B10EE7; Sun, 27 May 2007 19:53:34 +0200 (CEST) Received: from [10.1.1.2] (unknown [192.168.25.6]) by blah.sun-fish.com (Postfix) with ESMTP id 6A1B61B10EE0; Sun, 27 May 2007 19:53:34 +0200 (CEST) Message-ID: <4659C59C.9030208@sun-fish.com> Date: Sun, 27 May 2007 20:53:32 +0300 From: Stefan Lambrev User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Jack Vogel References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> In-Reply-To: <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: freebsd-net@freebsd.org Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 17:53:36 -0000 Hi Jack, Jack Vogel wrote: > Stefan, > > I am having a long weekend and am supposed to be doing > something other than this :) However, when I get back in the office > on Tuesday I will see if I can repro this, so just to make sure, tell > me what the PCI ID of the two cards are when it fails with Intel > on both sides, that should be easy. > > Jack this is the card that works in my tests: em1@pci4:0:1: class=0x020000 card=0x34768086 chip=0x10968086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 EB Network Connection' class = network subclass = ethernet and this is the one that do not work at gigabit speed: em0@pci0:25:0: class=0x020000 card=0x2800103c chip=0x104a8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82566DM Gigabit Network Connection' class = network subclass = ethernet > > > On 5/27/07, Stefan Lambrev wrote: >> Hi, >> >> MQ wrote: >> > >> > Actually, I'd rather consider the bge(4) has some problems with its >> > media negotiation. It seems that the problem you described was just >> > the same with mine as I had mentioned earlier this year. I encountered >> > the problem as I wanted a BCM5701 and a BCM5780 to connect to each >> > other with 1000TX duplex. >> Hm seems my last mail got lost and didn't reach the mail list. >> >> I replaced the broadcom device with other intel gigabit card: >> em1: port >> 0x2000-0x201f mem 0xb8c00000-0xb8c1ffff,0xb8400000-0xb87fffff irq 19 at >> device 0.1 on pci4 >> em1: Ethernet address: 00:15:17:1b:08:ed >> em1: [FILTER] >> >> on the other end is the "problematic" network card (that does work under >> linux&windows): >> em0: port >> 0x2000-0x201f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at >> device 25.0 on pci0 >> em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xf0500000 >> em0: attempting to allocate 1 MSI vectors (1 supported) >> msi: routing MSI IRQ 256 to vector 49 >> em0: using IRQ 256 for MSI >> em0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xf0524000 >> em0: bpf attached >> em0: Ethernet address: 00:0f:fe:4e:78:16 >> em0: [FILTER] >> >> When I verbose boot the server I see: >> em0: Link is up 1000 Mbps Full Duplex >> em0: link state changed to UP >> em0: Link is Down >> em0: link state changed to DOWN >> em0: Link is up 100 Mbps Full Duplex >> em0: link state changed to UP >> >> if I type ifconfig em0 media auto it happens exactly the same: >> card down >> card negotiate to 1000 Mbps Full Duplex >> card up - netowrk work for 2 seconds >> card down >> card negotiate to 100Mbps Full Duplex >> card up. >> >> If i force 1000mbps network : >> ifconfig em0 media 1000basetx mediaopt full-duplex >> 2 seconds latter I see: status: no carrier >> >> Both machines are running FreeBSD 7.0-CURRENT from ~2 days ago. >> >> A checked up connection between bge0 and the new server with intel card >> and everything works fine. >> >> >> -- >> >> Best Wishes, >> Stefan Lambrev >> ICQ# 24134177 >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun May 27 19:20:25 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EEFCD16A469 for ; Sun, 27 May 2007 19:20:25 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2C17113C45E for ; Sun, 27 May 2007 19:20:25 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id a29so2539708pyi for ; Sun, 27 May 2007 12:20:24 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vjs6xpxux/N9xletcHQxq57CocPuNFyMlYJ39p7Z2mGGdGJXgoZt2nAnywro213dxxNkl0gusKwZudy42TfqOeyi4eWHhtwrdFRf3qnTFlTWnS5N9W73FiFjl+qVwbS6E8weI1hvU2yHOlk8BsMJ8hBy1cqCljO/DCeDe2xJG+8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XSgunqTDChlH0TxE5nIAQvTVusEzgB12po7oZHQ8yZsb6uRzGA1LdynLC7QWXm30steQQuDdgXYbqHxnZbQch6o88pa/eD0F5CWab0qnxJHJhc8YZKF/7wnedxAXt3vD8WWC2PiHGBoj4zdHajq0+2WSusF+nPhf0fo7wg0mfWs= Received: by 10.115.46.9 with SMTP id y9mr2530121waj.1180293624343; Sun, 27 May 2007 12:20:24 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Sun, 27 May 2007 12:20:24 -0700 (PDT) Message-ID: <2a41acea0705271220w2239211bn1c582031607ca1eb@mail.gmail.com> Date: Sun, 27 May 2007 12:20:24 -0700 From: "Jack Vogel" To: "Stefan Lambrev" In-Reply-To: <4659C59C.9030208@sun-fish.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> <4659C59C.9030208@sun-fish.com> Cc: freebsd-net@freebsd.org Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 19:20:26 -0000 On 5/27/07, Stefan Lambrev wrote: > Hi Jack, > > Jack Vogel wrote: > > Stefan, > > > > I am having a long weekend and am supposed to be doing > > something other than this :) However, when I get back in the office > > on Tuesday I will see if I can repro this, so just to make sure, tell > > me what the PCI ID of the two cards are when it fails with Intel > > on both sides, that should be easy. > > > > Jack > this is the card that works in my tests: > > em1@pci4:0:1: class=0x020000 card=0x34768086 chip=0x10968086 rev=0x01 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 EB Network Connection' > class = network > subclass = ethernet > > and this is the one that do not work at gigabit speed: > > em0@pci0:25:0: class=0x020000 card=0x2800103c chip=0x104a8086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82566DM Gigabit Network Connection' > class = network > subclass = ethernet OK, I will attempt to repro this on Tuesday, thanks Stefan. Jack From owner-freebsd-net@FreeBSD.ORG Sun May 27 19:24:51 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 64B3716A474 for ; Sun, 27 May 2007 19:24:51 +0000 (UTC) (envelope-from kip.macy@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 CD70A13C4AE for ; Sun, 27 May 2007 19:24:50 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so726512uge for ; Sun, 27 May 2007 12:24:49 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sb4A12eZyhksuHDmYERzYLLy7fg4psvhk6lwGHcJ1TEcZ4HRIXUZM/KdGTr79R9ozOntyHH/+KvFeo7cSFK5NnCegYBEvrhI/F3Z2pjVg31nroOXDT68wJxXmHKMIC5n8SfFOP6rzZvWQOUl+kB8Sn/VmFf1nHyJ2avuYdDlNMA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ve5qnOPz48dx7I18TOmTWhvmP9YI3vKa37OyfiojxtwQhdzxxLURSgkx96IUDh+AEWcl66xiNKHIY83aa3Pd1LsVER5ttnhYGqk0/8ahJU3OHWm3U2acVPQSRBNwmSrKAVM1CR5tFFqDsbB3Rs4KvENJIxykLxjVqzrLEu+KIDQ= Received: by 10.78.181.13 with SMTP id d13mr1472064huf.1180293889682; Sun, 27 May 2007 12:24:49 -0700 (PDT) Received: by 10.78.107.13 with HTTP; Sun, 27 May 2007 12:24:49 -0700 (PDT) Message-ID: Date: Sun, 27 May 2007 12:24:49 -0700 From: "Kip Macy" To: "Boris Kochergin" In-Reply-To: <465959FF.4040401@acm.poly.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <465959FF.4040401@acm.poly.edu> Cc: freebsd-net@freebsd.org Subject: Re: System hang with Ralink RT2661 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 19:24:51 -0000 It probably needs to drop its softc lock around if_input. The SAM_WIFI contains many other fixes. I'm hoping it will be integrated into cvs soon. -Kip On 5/27/07, Boris Kochergin wrote: > Hi. I got an "SMC SMCWPCI-GM" card the other day, which is one of these: > > May 27 01:16:55 router kernel: ral0: mem > 0xf4000000-0xf4007fff irq 10 at device 13.0 on pci0 > May 27 01:16:55 router kernel: ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR) > > I put it into a Pentium III machine (which has PCI 2.2, per the ral(4) > man page) running a 7-CURRENT build from earlier today with a GENERIC > kernel, and attempted to connect to my wireless network, the access > point of which is an Atheros 5212 card, which has been serving Prism and > other Atheros cards for months. The RT2661 card associated fine and was > able to carry out lightweight operations like pinging and HTTP requests, > but when I attempted to use it to send or receive any heavy traffic (a > few dozen KiB/second), the system froze. I was able to toggle the caps > lock/num lock lights, and if I did something to make the system beep > (i.e. by pressing ALT+F10 when there was no virtual terminal running > there), the beep would ring out endlessly. It may also be worth > mentioning that the system was unresponsive to ACPI (via the power > button) and that the same RT2661 card in the same machine has no trouble > sniffing over 2 MiB/second of traffic via tcpdump. I'll be happy to > provide any other information that may be deemed useful. Thanks. > > -Boris > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Mon May 28 07:36:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0222B16A469 for ; Mon, 28 May 2007 07:36:45 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from wmail.teledomenet.gr (wmail.teledomenet.gr [213.142.128.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6982013C44B for ; Mon, 28 May 2007 07:36:45 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from iris (unknown [192.168.1.71]) by wmail.teledomenet.gr (Postfix) with ESMTP id C91F61C8D98 for ; Mon, 28 May 2007 10:36:43 +0300 (EEST) From: Nikos Vassiliadis To: freebsd-net@freebsd.org Date: Mon, 28 May 2007 10:33:08 +0300 User-Agent: KMail/1.9.1 References: <200705221006.49359.nvass@teledomenet.gr> In-Reply-To: <200705221006.49359.nvass@teledomenet.gr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705281033.08968.nvass@teledomenet.gr> Subject: Re: ng_pptpgre + netmask_change results to lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 07:36:46 -0000 On Tuesday 22 May 2007 10:06, I wrote: > Hello everybody, > > I just managed to lock my box and I want to report it > in case it's known(or it helps in some way). It is a > 6.2-STABLE from March 13. I did update to RELENG_6. > The procedure that triggers > the lock is simple: > > 1) Create a pptp tunnel. > 2) Set is as your default gateway. > 3) Play a bit with the netmask of the physical inteface. > In my case doing a few times: > ifconfig fxp0 192.168.1.71/16 > ifconfig fxp0 192.168.1.71/24 > locks the box. I also have to mention that the PPTP server is not on 192.168.1.0/24. My kernel cf contains: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_KDB options DEBUG_LOCKS options DIAGNOSTIC options SOCKBUF_DEBUG options BREAK_TO_DEBUGGER options NETGRAPH options NETGRAPH_DEBUG and several netgraph nodes. I still cannot break to the debugger, is there anything else I should add to my kernel cf? root:0:~# ngctl list There are 19 total nodes: Name: ngctl18236 Type: socket ID: 0000003c Num hooks: 0 Name: Type: pppoe ID: 00000037 Num hooks: 2 Name: Type: socket ID: 00000036 Num hooks: 1 Name: mpd1899-sam-bpf Type: bpf ID: 00000035 Num hooks: 5 Name: mpd1899-sam-vjc Type: vjc ID: 00000034 Num hooks: 4 Name: mpd1899-sam Type: ppp ID: 00000033 Num hooks: 7 Name: ng1 Type: iface ID: 00000032 Num hooks: 2 Name: mpd1899-sam-so Type: socket ID: 00000031 Num hooks: 2 Name: Type: socket ID: 00000030 Num hooks: 0 Name: Type: ksocket ID: 0000002f Num hooks: 1 Name: Type: pptpgre ID: 0000002e Num hooks: 2 Name: mpd1899-mss Type: tcpmss ID: 0000002d Num hooks: 4 Name: mpd1899-vpn-bpf Type: bpf ID: 0000002c Num hooks: 5 Name: mpd1899-vpn-vjc Type: vjc ID: 0000002b Num hooks: 4 Name: mpd1899-vpn Type: ppp ID: 0000002a Num hooks: 8 Name: ng0 Type: iface ID: 00000029 Num hooks: 2 Name: mpd1899-vpn-so Type: socket ID: 00000028 Num hooks: 2 Name: fxp0 Type: ether ID: 00000002 Num hooks: 0 Name: rl0 Type: ether ID: 00000001 Num hooks: 1 Any ideas what to do next? Thanks in advance, Nikos From owner-freebsd-net@FreeBSD.ORG Mon May 28 07:43:29 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0100F16A421 for ; Mon, 28 May 2007 07:43:29 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id AC41413C45E for ; Mon, 28 May 2007 07:43:28 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=XsMeV0suASMuRC2ZAx02G/tHY96gvu+LsQPCZMG11v/cUdLc2qXTI9EMA8V8WYmnFtUUf7HNAPFeZI4rEORt+1dVWW/r7YLXEpYPTsfkKMOKb4x5yuGepwg+OYesbMAL3l/Bi8K7OZRfBTgPqv6JeMv13eCFqY/3kDvmX2FvX4o=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1HsZsz-000AT8-QK; Mon, 28 May 2007 11:43:25 +0400 Date: Mon, 28 May 2007 11:43:21 +0400 From: Eygene Ryabinkin To: freebsd-net@freebsd.org, Andrei Manescu Message-ID: <20070528074321.GF35160@void.codelabs.ru> References: <000e01c79f03$b2cfce70$5501a8c0@ivorde> <08556012-CA57-4B2A-A142-F5C1BC8D9009@mac.com> <20070527110741.GC78927@obelix.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20070527110741.GC78927@obelix.dsto.defence.gov.au> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-3.0 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_00 Cc: alex.wilkinson@dsto.defence.gov.au Subject: Re: two public ip addresses on one interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 07:43:29 -0000 Alex, good day. Sun, May 27, 2007 at 07:07:41PM +0800, Wilkinson, Alex wrote: > > If your aliases are part of the same subnet as the "primary" or first configured IP, then you want to > > use the all-1's netmask. In your case, however, the second IP is part of a completely different subnet, > > and you can (and should) use a /24 netmask.... > > I have always wondered why we need to use the "all-1's" netmask. Why is this ? Because if you're stuffing two addresses from the same subnet to one interface it will not work: there can be only one route to the specified network in the FreeBSD routing table. And adding IP to the interface creates the entry in the routing table. So you should specify the different mask and most probably 0xffffffff will be the best choice, but your mileage may vary with your routing needs. -- Eygene From owner-freebsd-net@FreeBSD.ORG Mon May 28 07:57:37 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33A9116A46B for ; Mon, 28 May 2007 07:57:37 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outU.internet-mail-service.net (outU.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id 1D78A13C457 for ; Mon, 28 May 2007 07:57:37 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 00:57:36 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 5BACE125B26; Mon, 28 May 2007 00:57:36 -0700 (PDT) Message-ID: <465A8B7B.7060204@elischer.org> Date: Mon, 28 May 2007 00:57:47 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Nikos Vassiliadis References: <200705221006.49359.nvass@teledomenet.gr> <200705281033.08968.nvass@teledomenet.gr> In-Reply-To: <200705281033.08968.nvass@teledomenet.gr> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ng_pptpgre + netmask_change results to lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 07:57:37 -0000 Nikos Vassiliadis wrote: > On Tuesday 22 May 2007 10:06, I wrote: >> Hello everybody, >> >> I just managed to lock my box and I want to report it define "lock"? Does it still respond to on the keyboard? (Assuming you have the debugger in your kernel?). Does it still ping? Sometimes these still respond even though the rest of the system appears dead. >> in case it's known(or it helps in some way). It is a >> 6.2-STABLE from March 13. > > I did update to RELENG_6. > >> The procedure that triggers >> the lock is simple: >> >> 1) Create a pptp tunnel. >> 2) Set is as your default gateway. >> 3) Play a bit with the netmask of the physical inteface. >> In my case doing a few times: >> ifconfig fxp0 192.168.1.71/16 >> ifconfig fxp0 192.168.1.71/24 >> locks the box. > > I also have to mention that the PPTP > server is not on 192.168.1.0/24. > > My kernel cf contains: > options KDB > options DDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_KDB > options DEBUG_LOCKS > options DIAGNOSTIC > options SOCKBUF_DEBUG > options BREAK_TO_DEBUGGER > > options NETGRAPH > options NETGRAPH_DEBUG > and several netgraph nodes. > > I still cannot break to the debugger, is there anything > else I should add to my kernel cf? > > root:0:~# ngctl list > There are 19 total nodes: > Name: ngctl18236 Type: socket ID: 0000003c Num hooks: 0 > Name: Type: pppoe ID: 00000037 Num hooks: 2 > Name: Type: socket ID: 00000036 Num hooks: 1 > Name: mpd1899-sam-bpf Type: bpf ID: 00000035 Num hooks: 5 > Name: mpd1899-sam-vjc Type: vjc ID: 00000034 Num hooks: 4 > Name: mpd1899-sam Type: ppp ID: 00000033 Num hooks: 7 > Name: ng1 Type: iface ID: 00000032 Num hooks: 2 > Name: mpd1899-sam-so Type: socket ID: 00000031 Num hooks: 2 > Name: Type: socket ID: 00000030 Num hooks: 0 > Name: Type: ksocket ID: 0000002f Num hooks: 1 > Name: Type: pptpgre ID: 0000002e Num hooks: 2 > Name: mpd1899-mss Type: tcpmss ID: 0000002d Num hooks: 4 > Name: mpd1899-vpn-bpf Type: bpf ID: 0000002c Num hooks: 5 > Name: mpd1899-vpn-vjc Type: vjc ID: 0000002b Num hooks: 4 > Name: mpd1899-vpn Type: ppp ID: 0000002a Num hooks: 8 > Name: ng0 Type: iface ID: 00000029 Num hooks: 2 > Name: mpd1899-vpn-so Type: socket ID: 00000028 Num hooks: 2 > Name: fxp0 Type: ether ID: 00000002 Num hooks: 0 > Name: rl0 Type: ether ID: 00000001 Num hooks: 1 > > Any ideas what to do next? > > Thanks in advance, Nikos > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon May 28 08:02:13 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A02D16A421 for ; Mon, 28 May 2007 08:02:13 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id B7FDE13C489 for ; Mon, 28 May 2007 08:02:12 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (8.13.8/8.13.8) with ESMTP id l4S7qR0k022997 for ; Mon, 28 May 2007 17:22:27 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.5) with ESMTP id ; Mon, 28 May 2007 17:32:06 +0930 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 May 2007 17:32:05 +0930 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.13.8/8.13.8) with ESMTP id l4S81Xp0086775; Mon, 28 May 2007 16:01:34 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.13.8/8.13.8/Submit) id l4S81XOb086774; Mon, 28 May 2007 16:01:33 +0800 (WST) (envelope-from wilkinsa) Date: Mon, 28 May 2007 16:01:32 +0800 From: "Wilkinson, Alex" To: freebsd-net@freebsd.org, Andrei Manescu Message-ID: <20070528080132.GH84763@obelix.dsto.defence.gov.au> Mail-Followup-To: freebsd-net@freebsd.org, Andrei Manescu References: <000e01c79f03$b2cfce70$5501a8c0@ivorde> <08556012-CA57-4B2A-A142-F5C1BC8D9009@mac.com> <20070527110741.GC78927@obelix.dsto.defence.gov.au> <20070528074321.GF35160@void.codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20070528074321.GF35160@void.codelabs.ru> Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.15 (2007-04-06) X-OriginalArrivalTime: 28 May 2007 08:02:05.0686 (UTC) FILETIME=[7B76A960:01C7A0FE] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-3.6.1039-15198.001 X-TM-AS-Result: No--4.075300-8.000000-31 Content-Transfer-Encoding: 7bit Cc: Subject: Re: two public ip addresses on one interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 08:02:13 -0000 0n Mon, May 28, 2007 at 11:43:21AM +0400, Eygene Ryabinkin wrote: >Alex, good day. > >Sun, May 27, 2007 at 07:07:41PM +0800, Wilkinson, Alex wrote: >> > If your aliases are part of the same subnet as the "primary" or first configured IP, then you want to >> > use the all-1's netmask. In your case, however, the second IP is part of a completely different subnet, >> > and you can (and should) use a /24 netmask.... >> >> I have always wondered why we need to use the "all-1's" netmask. Why is this ? > >Because if you're stuffing two addresses from the same subnet to >one interface it will not work: there can be only one route to the >specified network in the FreeBSD routing table. And adding IP to >the interface creates the entry in the routing table. So you should >specify the different mask and most probably 0xffffffff will be the >best choice, but your mileage may vary with your routing needs. mmm ... it looks like you can actually get around this on OpenBSD 4.1 with their new "multiple routing table" code. "Multiple routing tables. What does it mean for PF? Henning Brauer: The kernel used to have one routing table per address family--one for inet, one for inet6, one for IPsec, usually. Now it can have multiple tables. From within PF, you can select which routing table should be used for the route lookup later--you can implement policy routing with this. But much more could be done--this is really only the groundwork. It could be possible, in future, to have overlapping address ranges on interfaces and place interfaces into different routing tables, forming a kind of virtual routers. And of course, the routing daemons will learn to make more use of alternate tables." [http://www.onlamp.com/pub/a/bsd/2007/05/03/openbsd-41-puffy-strikes-again.html?page=2] -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-net@FreeBSD.ORG Mon May 28 08:08:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A084016A47A for ; Mon, 28 May 2007 08:08:10 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from wmail.teledomenet.gr (wmail.teledomenet.gr [213.142.128.16]) by mx1.freebsd.org (Postfix) with ESMTP id 259D813C455 for ; Mon, 28 May 2007 08:08:09 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from iris (unknown [192.168.1.71]) by wmail.teledomenet.gr (Postfix) with ESMTP id 1EF221C9073; Mon, 28 May 2007 11:08:09 +0300 (EEST) From: Nikos Vassiliadis To: Julian Elischer Date: Mon, 28 May 2007 11:04:21 +0300 User-Agent: KMail/1.9.1 References: <200705221006.49359.nvass@teledomenet.gr> <200705281033.08968.nvass@teledomenet.gr> <465A8B7B.7060204@elischer.org> In-Reply-To: <465A8B7B.7060204@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705281104.22384.nvass@teledomenet.gr> Cc: freebsd-net@freebsd.org Subject: Re: ng_pptpgre + netmask_change results to lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 08:08:10 -0000 On Monday 28 May 2007 10:57, Julian Elischer wrote: > Nikos Vassiliadis wrote: > > On Tuesday 22 May 2007 10:06, I wrote: > >> Hello everybody, > >> > >> I just managed to lock my box and I want to report it > > define "lock"? > > Does it still respond to on the keyboard? No, but I was trying to break to the debugger with myself. I assume that it is equivalent to the combination you wrote, or not? > (Assuming you have the debugger in your kernel?). Yes, I have included my kernel configuration, see bellow. > Does it still ping? no, ARP does not work as well. > > Sometimes these still respond even though the rest of the system appears > dead. > > >> in case it's known(or it helps in some way). It is a > >> 6.2-STABLE from March 13. > > > > I did update to RELENG_6. > > > >> The procedure that triggers > >> the lock is simple: > >> > >> 1) Create a pptp tunnel. > >> 2) Set is as your default gateway. > >> 3) Play a bit with the netmask of the physical inteface. > >> In my case doing a few times: > >> ifconfig fxp0 192.168.1.71/16 > >> ifconfig fxp0 192.168.1.71/24 > >> locks the box. > > > > I also have to mention that the PPTP > > server is not on 192.168.1.0/24. > > > > My kernel cf contains: > > options KDB > > options DDB > > options INVARIANTS > > options INVARIANT_SUPPORT > > options WITNESS > > options WITNESS_KDB > > options DEBUG_LOCKS > > options DIAGNOSTIC > > options SOCKBUF_DEBUG > > options BREAK_TO_DEBUGGER > > > > options NETGRAPH > > options NETGRAPH_DEBUG > > and several netgraph nodes. > > > > I still cannot break to the debugger, is there anything > > else I should add to my kernel cf? > > > > root:0:~# ngctl list > > There are 19 total nodes: > > Name: ngctl18236 Type: socket ID: 0000003c Num > > hooks: 0 Name: Type: pppoe ID: 00000037 > > Num hooks: 2 Name: Type: socket ID: 00000036 > > Num hooks: 1 Name: mpd1899-sam-bpf Type: bpf ID: 00000035 > > Num hooks: 5 Name: mpd1899-sam-vjc Type: vjc ID: > > 00000034 Num hooks: 4 Name: mpd1899-sam Type: ppp > > ID: 00000033 Num hooks: 7 Name: ng1 Type: iface > > ID: 00000032 Num hooks: 2 Name: mpd1899-sam-so Type: socket > > ID: 00000031 Num hooks: 2 Name: Type: socket > > ID: 00000030 Num hooks: 0 Name: Type: ksocket > > ID: 0000002f Num hooks: 1 Name: Type: pptpgre > > ID: 0000002e Num hooks: 2 Name: mpd1899-mss Type: tcpmss > > ID: 0000002d Num hooks: 4 Name: mpd1899-vpn-bpf Type: bpf > > ID: 0000002c Num hooks: 5 Name: mpd1899-vpn-vjc Type: vjc > > ID: 0000002b Num hooks: 4 Name: mpd1899-vpn Type: ppp > > ID: 0000002a Num hooks: 8 Name: ng0 Type: iface > > ID: 00000029 Num hooks: 2 Name: mpd1899-vpn-so Type: > > socket ID: 00000028 Num hooks: 2 Name: fxp0 > > Type: ether ID: 00000002 Num hooks: 0 Name: rl0 > > Type: ether ID: 00000001 Num hooks: 1 > > > > Any ideas what to do next? > > > > Thanks in advance, Nikos > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon May 28 08:20:15 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00C9716A481 for ; Mon, 28 May 2007 08:20:15 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outA.internet-mail-service.net (outA.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id E1F3113C44B for ; Mon, 28 May 2007 08:20:14 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 01:20:14 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id F1671125B26; Mon, 28 May 2007 01:20:13 -0700 (PDT) Message-ID: <465A90C8.8020600@elischer.org> Date: Mon, 28 May 2007 01:20:24 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Nikos Vassiliadis References: <200705221006.49359.nvass@teledomenet.gr> <200705281033.08968.nvass@teledomenet.gr> <465A8B7B.7060204@elischer.org> <200705281104.22384.nvass@teledomenet.gr> In-Reply-To: <200705281104.22384.nvass@teledomenet.gr> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Robert Watson Subject: debuging a hung kernel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 08:20:15 -0000 Nikos Vassiliadis wrote: > On Monday 28 May 2007 10:57, Julian Elischer wrote: >> Nikos Vassiliadis wrote: >>> On Tuesday 22 May 2007 10:06, I wrote: >>>> Hello everybody, >>>> >>>> I just managed to lock my box and I want to report it >> define "lock"? >> >> Does it still respond to on the keyboard? > > No, but I was trying to break to the debugger with > myself. I assume that it is > equivalent to the combination you wrote, or not? > >> (Assuming you have the debugger in your kernel?). > > Yes, I have included my kernel configuration, see bellow. > >> Does it still ping? > > no, ARP does not work as well. > nasty.. do you have IPMI? sometimes that allows you to generate an NMI that could theoretically be made to drop to the debugger. I've not had success with that but I have heard others have. From owner-freebsd-net@FreeBSD.ORG Mon May 28 08:22:24 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 467F216A46B for ; Mon, 28 May 2007 08:22:24 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outH.internet-mail-service.net (outH.internet-mail-service.net [216.240.47.231]) by mx1.freebsd.org (Postfix) with ESMTP id 2FEAC13C480 for ; Mon, 28 May 2007 08:22:24 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 01:22:23 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 3D45D125B2F; Mon, 28 May 2007 01:22:23 -0700 (PDT) Message-ID: <465A914A.3040408@elischer.org> Date: Mon, 28 May 2007 01:22:34 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: freebsd-net@freebsd.org, Andrei Manescu References: <000e01c79f03$b2cfce70$5501a8c0@ivorde> <08556012-CA57-4B2A-A142-F5C1BC8D9009@mac.com> <20070527110741.GC78927@obelix.dsto.defence.gov.au> <20070528074321.GF35160@void.codelabs.ru> <20070528080132.GH84763@obelix.dsto.defence.gov.au> In-Reply-To: <20070528080132.GH84763@obelix.dsto.defence.gov.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: two public ip addresses on one interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 08:22:24 -0000 Wilkinson, Alex wrote: > 0n Mon, May 28, 2007 at 11:43:21AM +0400, Eygene Ryabinkin wrote: > > >Alex, good day. > > > >Sun, May 27, 2007 at 07:07:41PM +0800, Wilkinson, Alex wrote: > >> > If your aliases are part of the same subnet as the "primary" or first configured IP, then you want to > >> > use the all-1's netmask. In your case, however, the second IP is part of a completely different subnet, > >> > and you can (and should) use a /24 netmask.... > >> > >> I have always wondered why we need to use the "all-1's" netmask. Why is this ? > > > >Because if you're stuffing two addresses from the same subnet to > >one interface it will not work: there can be only one route to the > >specified network in the FreeBSD routing table. And adding IP to > >the interface creates the entry in the routing table. So you should > >specify the different mask and most probably 0xffffffff will be the > >best choice, but your mileage may vary with your routing needs. > > mmm ... it looks like you can actually get around this on OpenBSD 4.1 > with their new "multiple routing table" code. > > "Multiple routing tables. What does it mean for PF? > > Henning Brauer: > The kernel used to have one routing table per address > family--one for inet, one for inet6, one for IPsec, usually. Now it can have > multiple tables. From within PF, you can select which routing table should be > used for the route lookup later--you can implement policy routing with this. But > much more could be done--this is really only the groundwork. It could be > possible, in future, to have overlapping address ranges on interfaces and place > interfaces into different routing tables, forming a kind of virtual routers. And > of course, the routing daemons will learn to make more use of alternate > tables." the trouble I have with this is that by the time pf or ipfw get to the packet, the routing has already been done. > > [http://www.onlamp.com/pub/a/bsd/2007/05/03/openbsd-41-puffy-strikes-again.html?page=2] > > -aW > > IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon May 28 08:37:36 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BDC9C16A4FB for ; Mon, 28 May 2007 08:37:36 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 7F0FC13C4AD for ; Mon, 28 May 2007 08:37:36 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so450720anc for ; Mon, 28 May 2007 01:37:35 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FS7CyLLkzUS2Tka2PfjbhYjpkCtYVAukpo4+IrYxr9HAiEwNvzUBOHsstBGTnU9tKSeSNxJIkvrVPlQfCJb49ssEt+4zle3EbJa3qsHd/n6f5njFGAXShYyBE9GL0Sf0FFj3zunB6tj5RdzEGiuQWQd+UEmoEc3KNHEguU7M+OM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eKcZShWIpukJGXSFuRmE2YlPNdoquN7V/8UKpQUIjzE2uYtXTuYzbVcvXdLHp1X8aRKnzMJao0lgBbBakQ7Vk1RoiDzxdvJIaukyLIwtx/v4NhsZSoKmr9VNZQzGgKXhmfUPnwRqM8oV9HNKNDUNgDmWcWSIuIbkR9jl29T1ZUU= Received: by 10.100.33.14 with SMTP id g14mr4404953ang.1180341455568; Mon, 28 May 2007 01:37:35 -0700 (PDT) Received: by 10.100.47.5 with HTTP; Mon, 28 May 2007 01:37:35 -0700 (PDT) Message-ID: Date: Mon, 28 May 2007 16:37:35 +0800 From: "Sepherosa Ziehau" To: "Boris Kochergin" In-Reply-To: <465959FF.4040401@acm.poly.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <465959FF.4040401@acm.poly.edu> Cc: freebsd-net@freebsd.org Subject: Re: System hang with Ralink RT2661 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 08:37:36 -0000 On 5/27/07, Boris Kochergin wrote: > Hi. I got an "SMC SMCWPCI-GM" card the other day, which is one of these: > > May 27 01:16:55 router kernel: ral0: mem > 0xf4000000-0xf4007fff irq 10 at device 13.0 on pci0 > May 27 01:16:55 router kernel: ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR) > > I put it into a Pentium III machine (which has PCI 2.2, per the ral(4) > man page) running a 7-CURRENT build from earlier today with a GENERIC > kernel, and attempted to connect to my wireless network, the access > point of which is an Atheros 5212 card, which has been serving Prism and > other Atheros cards for months. The RT2661 card associated fine and was > able to carry out lightweight operations like pinging and HTTP requests, > but when I attempted to use it to send or receive any heavy traffic (a > few dozen KiB/second), the system froze. I was able to toggle the caps > lock/num lock lights, and if I did something to make the system beep > (i.e. by pressing ALT+F10 when there was no virtual terminal running > there), the beep would ring out endlessly. It may also be worth > mentioning that the system was unresponsive to ACPI (via the power > button) and that the same RT2661 card in the same machine has no trouble > sniffing over 2 MiB/second of traffic via tcpdump. I'll be happy to > provide any other information that may be deemed useful. Thanks. Try changing ~line160 of dev/ral/rt2661reg.h From #define RT2661_SHORT_PREAMBLE (1 << 19) #define RT2661_MRR_ENABLED (1 << 20) #define RT2661_MRR_CCK_FALLBACK (1 << 23) to #define RT2661_SHORT_PREAMBLE (1 << 18) #define RT2661_MRR_ENABLED (1 << 19) #define RT2661_MRR_CCK_FALLBACK (1 << 22) This will make the situation better. Except the above wrongly configured MMR register values, rt2661 parts' TX intr processing is completely wrong; The channel TX power is incorrect too, for 11bg the difference between the correct one and the value that driver is using is small, but for 11a, the channel TX power will be completely wrong. Best Regards, sephe -- Live Free or Die From owner-freebsd-net@FreeBSD.ORG Mon May 28 08:54:58 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2459616A469 for ; Mon, 28 May 2007 08:54:58 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id F184F13C489 for ; Mon, 28 May 2007 08:54:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 77E0A471DC; Mon, 28 May 2007 04:54:57 -0400 (EDT) Date: Mon, 28 May 2007 09:54:57 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Julian Elischer In-Reply-To: <465A90C8.8020600@elischer.org> Message-ID: <20070528095156.L2234@fledge.watson.org> References: <200705221006.49359.nvass@teledomenet.gr> <200705281033.08968.nvass@teledomenet.gr> <465A8B7B.7060204@elischer.org> <200705281104.22384.nvass@teledomenet.gr> <465A90C8.8020600@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, Nikos Vassiliadis Subject: Re: debuging a hung kernel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 08:54:58 -0000 On Mon, 28 May 2007, Julian Elischer wrote: > Nikos Vassiliadis wrote: >> On Monday 28 May 2007 10:57, Julian Elischer wrote: >>> Nikos Vassiliadis wrote: >>>> On Tuesday 22 May 2007 10:06, I wrote: >>>>> Hello everybody, >>>>> >>>>> I just managed to lock my box and I want to report it >>> define "lock"? >>> >>> Does it still respond to on the keyboard? >> >> No, but I was trying to break to the debugger with >> myself. I assume that it is >> equivalent to the combination you wrote, or not? >> >>> (Assuming you have the debugger in your kernel?). >> >> Yes, I have included my kernel configuration, see bellow. >> >>> Does it still ping? >> >> no, ARP does not work as well. > > nasty.. do you have IPMI? sometimes that allows you to generate an NMI that > could theoretically be made to drop to the debugger. > > I've not had success with that but I have heard others have. An increase number of server motherboards have an NMI button on the motherboard, possibly exposed outside the case, but generally not. I've not tested it in over a year, but a few years ago I added an MP_WATCHDOG kernel option that causes one of the CPUs in an SMP system to become a dedicated watchdog CPU, checking to see if the OS is alive enough to process timer tickets. If a counter isn't updated, it generates an NMI to the debugger from the watchdog CPU. The idea here is that, as the number of CPUs increases, the cost of dedicating a CPU for debugging stuff gets lower. However, there have been quite a few scheduler changes in the last few years, and it's possible that the watchdog no longer properly excludes other work from being scheduled, and that further work is required. In particular, I believe it relies on 4BSD's "pull" scheduling model and a lack of per-CPU workers, so the mechanism may require some rethinking. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Mon May 28 10:29:36 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 96C6916A473; Mon, 28 May 2007 10:29:36 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from wmail.teledomenet.gr (wmail.teledomenet.gr [213.142.128.16]) by mx1.freebsd.org (Postfix) with ESMTP id 04C6613C484; Mon, 28 May 2007 10:29:35 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from iris (unknown [192.168.1.71]) by wmail.teledomenet.gr (Postfix) with ESMTP id D3F7C1C8627; Mon, 28 May 2007 13:29:34 +0300 (EEST) From: Nikos Vassiliadis To: Robert Watson Date: Mon, 28 May 2007 13:26:15 +0300 User-Agent: KMail/1.9.1 References: <200705221006.49359.nvass@teledomenet.gr> <465A90C8.8020600@elischer.org> <20070528095156.L2234@fledge.watson.org> In-Reply-To: <20070528095156.L2234@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705281326.17517.nvass@teledomenet.gr> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, Julian Elischer Subject: Re: debuging a hung kernel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 10:29:36 -0000 Redirecting from @net to @stable. Please, remove @net from future mails. On Monday 28 May 2007 11:54, Robert Watson wrote: > On Mon, 28 May 2007, Julian Elischer wrote: > > Nikos Vassiliadis wrote: > >> On Monday 28 May 2007 10:57, Julian Elischer wrote: > >>> Nikos Vassiliadis wrote: > >>>> On Tuesday 22 May 2007 10:06, I wrote: > >>>>> Hello everybody, > >>>>> > >>>>> I just managed to lock my box and I want to report it > >>> > >>> define "lock"? > >>> > >>> Does it still respond to on the keyboard? > >> > >> No, but I was trying to break to the debugger with > >> myself. I assume that it is > >> equivalent to the combination you wrote, or not? > >> > >>> (Assuming you have the debugger in your kernel?). > >> > >> Yes, I have included my kernel configuration, see bellow. > >> > >>> Does it still ping? > >> > >> no, ARP does not work as well. > > > > nasty.. do you have IPMI? sometimes that allows you to generate an NMI > > that could theoretically be made to drop to the debugger. I have a Dell PowerEdge 750 sitting at work, which I think has IPMI. I'll be able to try a few things next week, since I will be off work for this week. > > > > I've not had success with that but I have heard others have. > > An increase number of server motherboards have an NMI button on the > motherboard, possibly exposed outside the case, but generally not. > > I've not tested it in over a year, but a few years ago I added an > MP_WATCHDOG kernel option that causes one of the CPUs in an SMP system > to become a dedicated watchdog CPU, checking to see if the OS is alive > enough to process timer tickets. If a counter isn't updated, it > generates an NMI to the debugger from the watchdog CPU. The idea here > is that, as the number of CPUs increases, the cost of dedicating a CPU > for debugging stuff gets lower. However, there have been quite a few > scheduler changes in the last few years, and it's possible that the > watchdog no longer properly excludes other work from being scheduled, > and that further work is required. In particular, I believe it relies > on 4BSD's "pull" scheduling model and a lack of per-CPU workers, so the > mechanism may require some rethinking. Unfortunately, I have not an SMP system available. Is there a mechanism which I can use to schedule a break to the debugger after n seconds or events? I am looking if ichwd(4) can help, though that needs investigation since I have not used watchdog facilities before. Thanks Julian & Robert. From owner-freebsd-net@FreeBSD.ORG Mon May 28 11:08:35 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C7F316A41F for ; Mon, 28 May 2007 11:08:35 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4E22313C44B for ; Mon, 28 May 2007 11:08:35 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4SB8Zjx068556 for ; Mon, 28 May 2007 11:08:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4SB8Xld068552 for freebsd-net@FreeBSD.org; Mon, 28 May 2007 11:08:33 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 May 2007 11:08:33 GMT Message-Id: <200705281108.l4SB8Xld068552@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 you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 11:08:35 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/95665 net [if_tun] "ping: sendto: No buffer space available" wit 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/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/109406 net [ndis] Broadcom WLAN driver 4.100.15.5 doesn't work wi o kern/110959 net [ipsec] Filtering incoming packets with enc0 does not 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 IP v4 udp fragmented packet reject 13 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/95267 net packet drops periodically appear f kern/95277 net [netinet] IP Encapsulation mask_match() returns wrong o kern/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/112612 net [lo] Traffic via additional lo(4) interface shows up o o kern/112654 net [pcn] Kernel panic upon if_pcn module load on a Netfin o kern/112710 net [re] if_re driver detects incorrect b243a405a405 MAC a o kern/112886 net [broadcom]: Wifi card not detected 14 problems total. From owner-freebsd-net@FreeBSD.ORG Mon May 28 12:05:57 2007 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0B5716A47F; Mon, 28 May 2007 12:05:57 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9A07313C45E; Mon, 28 May 2007 12:05:57 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4SC5vw2078238; Mon, 28 May 2007 12:05:57 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4SC5vVx078234; Mon, 28 May 2007 12:05:57 GMT (envelope-from linimon) Date: Mon, 28 May 2007 12:05:57 GMT From: Mark Linimon Message-Id: <200705281205.l4SC5vVx078234@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/113053: syncache broken in latest FreeBSD 7.0-CURRENT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 12:05:57 -0000 Synopsis: syncache broken in latest FreeBSD 7.0-CURRENT Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 28 12:05:46 UTC 2007 Responsible-Changed-Why: This does not sound i386-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=113053 From owner-freebsd-net@FreeBSD.ORG Mon May 28 14:53:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECC3516A46E for ; Mon, 28 May 2007 14:53:30 +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 A967C13C480 for ; Mon, 28 May 2007 14:53:30 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 48999 invoked from network); 28 May 2007 14:51:02 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.42.176) by acm.poly.edu with AES256-SHA encrypted SMTP; 28 May 2007 14:51:02 -0000 Message-ID: <465AECDD.6060008@acm.poly.edu> Date: Mon, 28 May 2007 10:53:17 -0400 From: Boris Kochergin User-Agent: Thunderbird 1.5.0.7 (X11/20061009) MIME-Version: 1.0 To: Sepherosa Ziehau References: <465959FF.4040401@acm.poly.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: System hang with Ralink RT2661 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 14:53:32 -0000 Sepherosa Ziehau wrote: > On 5/27/07, Boris Kochergin wrote: >> Hi. I got an "SMC SMCWPCI-GM" card the other day, which is one of these: >> >> May 27 01:16:55 router kernel: ral0: mem >> 0xf4000000-0xf4007fff irq 10 at device 13.0 on pci0 >> May 27 01:16:55 router kernel: ral0: MAC/BBP RT2661D, RF RT2529 (MIMO >> XR) >> >> I put it into a Pentium III machine (which has PCI 2.2, per the ral(4) >> man page) running a 7-CURRENT build from earlier today with a GENERIC >> kernel, and attempted to connect to my wireless network, the access >> point of which is an Atheros 5212 card, which has been serving Prism and >> other Atheros cards for months. The RT2661 card associated fine and was >> able to carry out lightweight operations like pinging and HTTP requests, >> but when I attempted to use it to send or receive any heavy traffic (a >> few dozen KiB/second), the system froze. I was able to toggle the caps >> lock/num lock lights, and if I did something to make the system beep >> (i.e. by pressing ALT+F10 when there was no virtual terminal running >> there), the beep would ring out endlessly. It may also be worth >> mentioning that the system was unresponsive to ACPI (via the power >> button) and that the same RT2661 card in the same machine has no trouble >> sniffing over 2 MiB/second of traffic via tcpdump. I'll be happy to >> provide any other information that may be deemed useful. Thanks. > > Try changing ~line160 of dev/ral/rt2661reg.h > From > #define RT2661_SHORT_PREAMBLE (1 << 19) > #define RT2661_MRR_ENABLED (1 << 20) > #define RT2661_MRR_CCK_FALLBACK (1 << 23) > to > #define RT2661_SHORT_PREAMBLE (1 << 18) > #define RT2661_MRR_ENABLED (1 << 19) > #define RT2661_MRR_CCK_FALLBACK (1 << 22) > > This will make the situation better. > > Except the above wrongly configured MMR register values, rt2661 parts' > TX intr processing is completely wrong; The channel TX power is > incorrect too, for 11bg the difference between the correct one and the > value that driver is using is small, but for 11a, the channel TX power > will be completely wrong. > > Best Regards, > sephe > Doesn't seem to have any effect. Thanks, though. I guess I'll wait for SAM_WIFI to become available in -CURRENT. -Boris From owner-freebsd-net@FreeBSD.ORG Mon May 28 15:18:14 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C212316A478 for ; Mon, 28 May 2007 15:18:14 +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 22AD513C480 for ; Mon, 28 May 2007 15:18:13 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 78456 invoked from network); 28 May 2007 14:34:34 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 28 May 2007 14:34:34 -0000 Message-ID: <465AF2BC.7070505@freebsd.org> Date: Mon, 28 May 2007 17:18:20 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Mark Linimon References: <200705281205.l4SC5vVx078234@freefall.freebsd.org> In-Reply-To: <200705281205.l4SC5vVx078234@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-i386@FreeBSD.org Subject: Re: kern/113053: syncache broken in latest FreeBSD 7.0-CURRENT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 15:18:14 -0000 Mark Linimon wrote: > Synopsis: syncache broken in latest FreeBSD 7.0-CURRENT > > Responsible-Changed-From-To: freebsd-i386->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon May 28 12:05:46 UTC 2007 > Responsible-Changed-Why: > This does not sound i386-specific. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=113053 Just to clarify: Syncache is not broken in -current. The user is confused about a recently enabled log message. This is partly my fault as the log message isn't clear enough for a non-expert to classify correctly. I've assumed the PR. -- Andre From owner-freebsd-net@FreeBSD.ORG Mon May 28 15:18:39 2007 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB5B316A41F; Mon, 28 May 2007 15:18:39 +0000 (UTC) (envelope-from andre@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 84B1C13C4CB; Mon, 28 May 2007 15:18:39 +0000 (UTC) (envelope-from andre@FreeBSD.org) Received: from freefall.freebsd.org (andre@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4SFId4R004228; Mon, 28 May 2007 15:18:39 GMT (envelope-from andre@freefall.freebsd.org) Received: (from andre@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4SFIdsx004224; Mon, 28 May 2007 15:18:39 GMT (envelope-from andre) Date: Mon, 28 May 2007 15:18:39 GMT From: Andre Oppermann Message-Id: <200705281518.l4SFIdsx004224@freefall.freebsd.org> To: andre@FreeBSD.org, freebsd-net@FreeBSD.org, andre@FreeBSD.org Cc: Subject: Re: kern/113053: syncache broken in latest FreeBSD 7.0-CURRENT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 May 2007 15:18:39 -0000 Synopsis: syncache broken in latest FreeBSD 7.0-CURRENT Responsible-Changed-From-To: freebsd-net->andre Responsible-Changed-By: andre Responsible-Changed-When: Mon May 28 15:18:19 UTC 2007 Responsible-Changed-Why: Take over. http://www.freebsd.org/cgi/query-pr.cgi?pr=113053 From owner-freebsd-net@FreeBSD.ORG Tue May 29 00:49:47 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D93216A539 for ; Tue, 29 May 2007 00:49:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 6AB9013C45B for ; Tue, 29 May 2007 00:49:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.13.8) with ESMTP id l4T0m2Kt090795 for ; Mon, 28 May 2007 17:48:02 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.13.8/Submit) id l4T0lv5o090794 for freebsd-net@freebsd.org; Mon, 28 May 2007 17:47:57 -0700 (PDT) (envelope-from sgk) Date: Mon, 28 May 2007 17:47:57 -0700 From: Steve Kargl To: freebsd-net@freebsd.org Message-ID: <20070529004757.GA90745@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: bge0 watchdog timeout? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 May 2007 00:49:47 -0000 No one on the freebsd-current mailing list seems to know how to avoid the following: May 28 16:39:59 node13 kernel: bge0: watchdog timeout -- resetting May 28 16:39:59 node13 kernel: bge0: link state changed to DOWN May 28 16:40:02 node13 kernel: bge0: link state changed to UP This is causing all sorts of havoc on a cluster of FreeBSD systems that is used for multi-day MPI computations. Anyone have any insight in fixing bge0 to no timeout? -- Steve From owner-freebsd-net@FreeBSD.ORG Tue May 29 04:58:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9A7A16A554 for ; Tue, 29 May 2007 04:58:31 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.freebsd.org (Postfix) with ESMTP id 9E54813C4BC for ; Tue, 29 May 2007 04:58:31 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 662187301E; Tue, 29 May 2007 13:58:29 +0900 (JST) Date: Tue, 29 May 2007 13:57:21 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: freebsd-net@freebsd.org User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: how ipfw2 handles fragmented 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: Tue, 29 May 2007 04:58:31 -0000 Hello, I have a question about how the ipfw2 implementation performs stateful operation for (IPv4/IPv6) fragmented packets. Is it possible to make a state for a flow and match that state against fragmented packets? As far as I can see from the source code (sys/netinet/ip_fw2.c) it seems impossible because a state matching done in lookup_dyn_rule_locked() only compares src/dst address/ports. I'm also not sure whether the routine that follows IPv6 extension headers in ipfw_chk() is correct. It continues the processing after seeing a fragment header regardless of the offset value, but it should be meaningless except the first fragment (which has 0 offset). If I miss something, could anyone point it out? Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-net@FreeBSD.ORG Tue May 29 10:06:30 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D89F016A468 for ; Tue, 29 May 2007 10:06:30 +0000 (UTC) (envelope-from ldacol@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 B4E9213C465 for ; Tue, 29 May 2007 10:06:30 +0000 (UTC) (envelope-from ldacol@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so858785wag for ; Tue, 29 May 2007 03:06:30 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=HachTf8VkszZ+ln0E65X/Gf9FpokeRX+PsHLOqbe3UqUcyJF9O+Ltl97S0ylZQ8aFPsH8wlPtCCGyNzjc8CeIZ01ol2X95+9DDIEBC4NtaxUro9WKLxFdsiFShMa1pFw4FRtAl0vKTVJVMKrFizWk2vYK52qWui+UmcS0Wki7tg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=QOb+6qlRjQ/D8SaIFUdqRq+JZKGB2SKPL3MYRwVn/vrYX2mL2OrYzGcJ+DxpVzl3X+D4ax6ycXfJuNuUGUluEpZRUHZebuYRoZ+gCA+ndCwQQWhADSPgBp/EOq6QY11vyQRkAA+KCCv9+Ri2Y8dttsknuZeP5uqAHNm6tKHhw2M= Received: by 10.114.88.1 with SMTP id l1mr3337366wab.1180431568124; Tue, 29 May 2007 02:39:28 -0700 (PDT) Received: by 10.114.177.2 with HTTP; Tue, 29 May 2007 02:39:28 -0700 (PDT) Message-ID: Date: Tue, 29 May 2007 11:39:28 +0200 From: "Luca Da Col" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Implement Multi-Protocol Label Switching (MPLS) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 May 2007 10:06:30 -0000 Hello, I would like to know if someone is actively working on MPLS project for FreeBSD. I would also like to know if James Leu's MPLS implementation for Linux has been considered as starting point for this project. Thank you, Luca Da Col From owner-freebsd-net@FreeBSD.ORG Tue May 29 10:18:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C951A16A400 for ; Tue, 29 May 2007 10:18:31 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id A227A13C4BB for ; Tue, 29 May 2007 10:18:31 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 2FC5A227A24; Tue, 29 May 2007 06:18:31 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 29 May 2007 06:18:31 -0400 X-Sasl-enc: Kui3B86yD/e8WC+5cOiQPqPRBKsm9taH13NV1q7AaaK+ 1180433910 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 8D5662033C; Tue, 29 May 2007 06:18:30 -0400 (EDT) Message-ID: <465BFDF5.4040604@incunabulum.net> Date: Tue, 29 May 2007 11:18:29 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Luca Da Col References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Implement Multi-Protocol Label Switching (MPLS) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 May 2007 10:18:31 -0000 Luca Da Col wrote: > Hello, > > I would like to know if someone is actively working on MPLS project for > FreeBSD. I would also like to know if James Leu's MPLS implementation for > Linux has been considered as starting point for this project. No one is actively working on this to the best of my knowledge, however, there has been work on updating the kernel support for the Click Modular Router which would probably be a more appropriate starting point for producing an MPLS implementation which would work in the FreeBSD kernel. BMS From owner-freebsd-net@FreeBSD.ORG Tue May 29 20:18:51 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9043316A46B for ; Tue, 29 May 2007 20:18:51 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1F26813C46C for ; Tue, 29 May 2007 20:18:50 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so1379971wxd for ; Tue, 29 May 2007 13:18:50 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=T63WJlWh1PGs6BIWhrnYEdKyz+i7TXrW8eyFtOsJFWdfO0RvQ8FBW7Av8fJQq5FQOfsIShuKIt+iMTWAhG5ZTvatqz2/cbMQs5k54MJbGm+M2pjLu2oko8YZ/pvsak7g6sND1hj2yzsihKzpZsrHN/iZ4sWh49WCz6QoJ5TRTbM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=bRulQYBEFhPK5/YeGLsL5QUsD+62cR6JeopuHDdsQyXcAkZE3fdYFEUdv/ZlqjWsYEerHMpZXMswNB4iYlWr4x8vMdqIT6tcsah2kZia8ys4HFzyyRV02O5UZ9GAzVhxn6X7ZWDe4o3b/B6aHZ6WBRCgPhf39IX37Y3K38lFvoA= Received: by 10.70.47.19 with SMTP id u19mr10785682wxu.1180469930181; Tue, 29 May 2007 13:18:50 -0700 (PDT) Received: by 10.70.73.1 with HTTP; Tue, 29 May 2007 13:18:49 -0700 (PDT) Message-ID: <9a542da30705291318t29b2d956j36b5b3ec2cb6b377@mail.gmail.com> Date: Tue, 29 May 2007 22:18:49 +0200 From: "=?ISO-8859-1?Q?Ermal_Lu=E7i?=" To: freebsd-pf@freebsd.org, freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_152823_30069899.1180469929739" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 May 2007 20:18:51 -0000 ------=_Part_152823_30069899.1180469929739 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline This is ng_pf node based on ng_ipfw code and idea. It allows interaction of PF and netgraph. Below are the node features and a dummy example of how to use it. Patch is attached. Features, 1- By default it sends any packet that matches the rule to netgraph. Syntax: pass in from any to any netgraph 41 #41 is the hook number(it needs to be a number) 2- You can specify how many packets will be sent to netgraph. This is implemented as a keep state option. Syntax: pass in from any to any netgraph 41 keep state(max-packets-to-netgraph 4) 3- You can specify flags when adding the tag to the node. Syntax ngctl msg pf: addtag { tagname=\"TEST\" tag=60 flags=4 } There are 4 flags for now: NG_PF_KILL_STATE (actually removes state from the state pool directly from the node NG_PF_IGNORE_STATE (it schedules the state to be removed later but behaves as the above and is really faster and safer) NG_PF_SKIP_FIREWALLS (skips firewalls; the way it is implemented this really skips any firewall on freebsd at least ipfw and pf). This is per tag setting meaning you can specify which packet whith a specific tag should skip reparssing the rules. NG_PF_DROP_PACKET (really drops packet; faster than telling a rule on PF to drop it, i don't like it personally cause is kinda magic; but it is there) 4- The node has these messages: NGM_PF_ADD_TAG (needs tagname, tagid, flags) struct ng_pf_command { char name[NG_PF_TAG_NAME_SIZE]; u_int16_t tag; int flags; }; NGM_PF_RMV_TAG, (needs tagname) NGM_PF_GET_TAGS, (no arguments) #ifdef NG_PF_DEBUG NGM_PF_GET_STATS, (number of packets in/out) NGM_PF_CLR_STATS, NGM_PF_GETCLR_STATS, #endif NGM_PF_SET_TAGZONE, NGM_PF_GET_TAGZONE, NGM_PF_DEFAULT_TAGZONE (for help) 5- You can send back and forth a packet(reparse ruleset multiple times) by resending a packet that has already passed once to netgraph by a matching rule with a different hook number. I.e.: .... ..... pass in on $int from any to any netgraph 41 pass in on $int tagged ONCE_TO_NETGRAPH netgraph 42 pass in on $int tagged TWICE_TO_NETGRAPH netgraph 43 .... ... For an example how to find DC++ packets with ng_bpf tag these packets with ng_tag is available at ng_tag manual page. After that just connect a hook to ng_pf and you're done. Surely even the rule that sends the packet to the correct queue on PF side. For more discussion on ng_bpf and packet matching for P2P packets follow, http://lists.freebsd.org/pipermail/freebsd-current/2006-June/063863.html. Sample configuration of the node. 1 - kldload ng_pf (after compiling). 2 - create a sample pf.conf file like the following: pass out quick on $INT all tagged TRY keep state pass out quick on $INT proto tcp from any to any port 80 netgraph 41 # or even this. It does the same thing. pass out on $INT proto tcp from any to any port 80 netgraph 41 pass out on $INT all tagged TRY keep state #The tag TRY is added to ng_pf list of tags to translate and the tag is added to the #packet with ng_tag. 3 - configure netgraph part of things. I used the following commands on my tests: # You understand the first 2 commands :). pfctl -e pfctl -F all -f /etc/pf.test # Here we configure a tag to be translated on ng_pf node. The node translates # tagname=TRY as known by PF. ngctl msg pf: addtag { tagname=\"TRY\" tag=52 flags=0 } # Create a hook with a ng_tag node. ngctl mkpeer pf: tag 41 th1 # Give a name to the hook for simplicity. ngctl name pf:41 match # Configure ng_tag node. # We tell ng_tag to not touch the packets incoming/entering on hook = "th1" ngctl msg match: sethookin { thisHook=\"th1\" ifNotMatch=\"th1\" } # ng_tag will tag packets leaving hook="th1" with tagname=TRY. ngctl msg match: sethookout { \ thisHook=\"th1\" \ #hookname tag_id=24 \ # PACKET_TAG_PF_TAG.(1) tag_len=4 \ # usually 4 bytes since we only pass a number/tag_id. tag_data=[ 52 ] } # the tag we want to apply packets on this hook. { (1) PACKET_TAG_PF_TAG = 24 is taken from sys/mbuf.h } After this if you try to connect to port 80 of any webserver if you check the PF statistics on rule matches with: pfctl -s rules -v you'll see that packets have gone through 'match by tag' rule after passing through netgraph. Feedback is appriciated, Ermali ------=_Part_152823_30069899.1180469929739-- From owner-freebsd-net@FreeBSD.ORG Tue May 29 22:06:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 812C516A469 for ; Tue, 29 May 2007 22:06:40 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.230]) by mx1.freebsd.org (Postfix) with ESMTP id 3D30913C455 for ; Tue, 29 May 2007 22:06:40 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so706063nzn for ; Tue, 29 May 2007 15:06:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XIY+tCzg+e50/VeKE2OAVp5Ob+aNh8pjylhdAE4cOj6dzKNvxcyIJi/Db44OyZ4SK1KQzwo7MmE2LOHyG5UXTjFDhFYOLvWlCzAujHScafj58x581GpzAsMTqSyUSDvtooiPkSnn1hJcUbXnDozVecjsbaJBr4CJPgxOQhUpZYc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LUhNjMJXlWuukHiB2A80CrgFAz5CyA+bY0olHqloA0PBTpN9ieO77qAHBmSVTYwX9DBKOGM4O11z9ZLzk6sptGnIEXNwm+/JxeGDZck7XAk7FXRtnGwOuwigl3lxRJHx0hMnqS5dc84N7EjtsPl9HcAdOZw69aJUG+qTTtaqz+A= Received: by 10.114.67.2 with SMTP id p2mr3635730waa.1180476399346; Tue, 29 May 2007 15:06:39 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Tue, 29 May 2007 15:06:39 -0700 (PDT) Message-ID: <2a41acea0705291506w156ac4d8s88c0fdd1025e5141@mail.gmail.com> Date: Tue, 29 May 2007 15:06:39 -0700 From: "Jack Vogel" To: "Stefan Lambrev" In-Reply-To: <2a41acea0705271220w2239211bn1c582031607ca1eb@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> <4659C59C.9030208@sun-fish.com> <2a41acea0705271220w2239211bn1c582031607ca1eb@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 May 2007 22:06:40 -0000 On 5/27/07, Jack Vogel wrote: > On 5/27/07, Stefan Lambrev wrote: > > Hi Jack, > > > > Jack Vogel wrote: > > > Stefan, > > > > > > I am having a long weekend and am supposed to be doing > > > something other than this :) However, when I get back in the office > > > on Tuesday I will see if I can repro this, so just to make sure, tell > > > me what the PCI ID of the two cards are when it fails with Intel > > > on both sides, that should be easy. > > > > > > Jack > > this is the card that works in my tests: > > > > em1@pci4:0:1: class=0x020000 card=0x34768086 chip=0x10968086 rev=0x01 > > hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'PRO/1000 EB Network Connection' > > class = network > > subclass = ethernet > > > > and this is the one that do not work at gigabit speed: > > > > em0@pci0:25:0: class=0x020000 card=0x2800103c chip=0x104a8086 rev=0x02 > > hdr=0x00 > > vendor = 'Intel Corporation' > > device = '82566DM Gigabit Network Connection' > > class = network > > subclass = ethernet > > OK, I will attempt to repro this on Tuesday, thanks Stefan. Good News, I have repro'd this on hardware here, so I'm actively debugging things now, hope its an easy fix... stay tuned. Jack From owner-freebsd-net@FreeBSD.ORG Wed May 30 11:18:52 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E18816A468 for ; Wed, 30 May 2007 11:18:52 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from mail.alkar.net (mail.alkar.net [195.248.191.95]) by mx1.freebsd.org (Postfix) with ESMTP id B883613C4BB for ; Wed, 30 May 2007 11:18:51 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from [195.248.178.122] (HELO [192.168.3.2]) by mail.alkar.net (CommuniGate Pro SMTP 5.1.7) with ESMTPS id 760564864; Wed, 30 May 2007 14:18:50 +0300 Message-ID: <465D5D50.2020009@freebsd.org> Date: Wed, 30 May 2007 14:17:36 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?UTF-8?B?RXJtYWwgTHXQk2k=?= References: <1180481012.00748860.1180470003@10.7.7.3> In-Reply-To: <1180481012.00748860.1180470003@10.7.7.3> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 11:18:52 -0000 Hi. Ermal Luçi wrote: > 4- The node has these messages: > #ifdef NG_PF_DEBUG > NGM_PF_GET_STATS, (number of packets in/out) > NGM_PF_CLR_STATS, > NGM_PF_GETCLR_STATS, > #endif What for comment them out? To save CPU on several addition operations? This stats could be used not only by developers but also by users and they may not be to rebuild kernel module to get that stats. -- Alexander Motin From owner-freebsd-net@FreeBSD.ORG Wed May 30 11:33:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0801416A46C for ; Wed, 30 May 2007 11:33:38 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from mail.alkar.net (mail.alkar.net [195.248.191.95]) by mx1.freebsd.org (Postfix) with ESMTP id 6272C13C448 for ; Wed, 30 May 2007 11:33:37 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from [195.248.178.122] (HELO [192.168.3.2]) by mail.alkar.net (CommuniGate Pro SMTP 5.1.7) with ESMTPS id 760585333; Wed, 30 May 2007 14:33:36 +0300 Message-ID: <465D60C5.50503@freebsd.org> Date: Wed, 30 May 2007 14:32:21 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nikos Vassiliadis References: <1179829392.00743801.1179818401@10.7.7.3> <1180351384.00747721.1180338602@10.7.7.3> In-Reply-To: <1180351384.00747721.1180338602@10.7.7.3> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ng_pptpgre + netmask_change results to lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 11:33:38 -0000 Hi. Nikos Vassiliadis wrote: >>In my case doing a few times: >>ifconfig fxp0 192.168.1.71/16 >>ifconfig fxp0 192.168.1.71/24 >>locks the box. Doing this you are dropping all routes going via that network. Probably you are dropping route to your pptp peer which can lead to wrapping tunnel inside himself. -- Alexander Motin From owner-freebsd-net@FreeBSD.ORG Wed May 30 14:44:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0685C16A468 for ; Wed, 30 May 2007 14:44:16 +0000 (UTC) (envelope-from bodo@staron.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 938AA13C45E for ; Wed, 30 May 2007 14:44:15 +0000 (UTC) (envelope-from bodo@staron.de) Received: from [87.152.94.129] (helo=r2d2.arkon.local) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis), id 0MKwh2-1HtPCx3Des-0004Iv; Wed, 30 May 2007 16:31:28 +0200 Date: Wed, 30 May 2007 16:31:25 +0200 From: "Bodo Staron [c]" X-Priority: 3 (Normal) Message-ID: <534420783.20070530163125@staron.de> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Ciphire-Security: signed X-Provags-ID: V01U2FsdGVkX1+9uY6zgaHpaz8QTaKe072IWIWFuCyl+ml9hd9 xDQk78+il8yquXbCI/klczQ/ptKy4cc6r33bMdV1/xOXaZiuv0 lPq5R4wc6he3B/Pb9m+q+davwVokvww Subject: Can someone please create a working IGMP proxy for FreeBSD 6.2? [signed] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bodo Staron List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2007 14:44:16 -0000 Hello, I hope this is actually the right list and my request isn't too outrageous. I am looking for a working IGMP proxy for FreeBSD 6.2. My ISP is offering TV over IP using IGMP. I use pfSense as a gateway. Research so far gave my this: 1. Activating multicast routing in the kernel is easy - just one line. 2. The program "mrouted" doesn't help, it seems it can't work with dial-up scenarios. 3. There is one IGMP proxy here (http://potiron.loria.fr/projects/madynes/internals/perso/lahmadi/igmpv3proxy/download) but it was done on 4.x and author, while helpful, doesn't seem to work on it anymore. Simply can't compile it. 4. Since IGMP multicasts will be more and more common (eg BBC too: http://forum.zensupport.co.uk/thread/10974.aspx) I kindly ask for someone to maybe port the working one from Linux (http://sourceforge.net/projects/igmpproxy) to FreeBSD. -- --------------------- [ SECURITY NOTICE ] --------------------- To: freebsd-net@freebsd.org. For your security, bodo@staron.de digitally signed this message on 30 May 2007 at 14:31:27 UTC. Verify this digital signature at http://www.ciphire.com/verify. ---------------- [ CIPHIRE DIGITAL SIGNATURE ] ---------------- Q2lwaGlyZSBTaWcuAjhmcmVlYnNkLW5ldEBmcmVlYnNkLm9yZwBib2RvQHN0YXJv bi5kZQBlbWFpbCBib2R5ANsCAAB8AHwAAAABAAAAv4pdRtsCAABGAwACAAIAAgAg ryS3WhW7f7lgCbiE2fJP3/TvMKPNA5W5GP07i7/4pSwBAHAVKOQWiOUxEG7xee/c WyejLomuj8kjlDVg3BwLE8gdqAOUYpTSHI7kfXX0r3nhH4KypRLBGCEd3ycSSQHc tsUFsjwbU2lnRW5k ------------------ [ END DIGITAL SIGNATURE ] ------------------ From owner-freebsd-net@FreeBSD.ORG Wed May 30 15:26:03 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93CC816A468 for ; Wed, 30 May 2007 15:26:03 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.229]) by mx1.freebsd.org (Postfix) with ESMTP id 49D7F13C4AE for ; Wed, 30 May 2007 15:26:03 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so1569411wxd for ; Wed, 30 May 2007 08:26:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Tfx/Wm63FyB3M0Yen82GbJOyUVeYO4oKmmOSKERH3JRnx3857ktbquoMYTx1yFGXxPwHUZuVBUBZp0rt+nX6gSA9VM00pEgYRpHnzYA3hO+7cYgYEmNgMnA96Xh60G+gim2qGoBucr7LmOobdlEQADc16OixcNwVP7lk/qPi1GI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BsC7ZHzxw6A8BVEC6hllROpi79/hE/i+Lh45uFmiJdg+B2LUVjjR/27t/A9PsZ0Q3/x9z3bDIDexfX4z41BW+v7huwLfrA9QS1MFBSMfPz+9zttcg74mpfVcbLgrNSTl7ngzMDSvyXxADTyWqohrBbIaNbaT1Gcabzeid8+WI04= Received: by 10.70.52.1 with SMTP id z1mr12284925wxz.1180538762184; Wed, 30 May 2007 08:26:02 -0700 (PDT) Received: by 10.70.73.1 with HTTP; Wed, 30 May 2007 08:26:02 -0700 (PDT) Message-ID: <9a542da30705300826g30e281bal6a68d5e17902fc21@mail.gmail.com> Date: Wed, 30 May 2007 17:26:02 +0200 From: "=?ISO-8859-1?Q?Ermal_Lu=E7i?=" To: "Alexander Motin" In-Reply-To: <465D5D50.2020009@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1180481012.00748860.1180470003@10.7.7.3> <465D5D50.2020009@freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 15:26:03 -0000 Alexander, the only reason i made them available only for debugging is cause of int32_t types of those counter and these could overflow easily on busy environments. For 64bit counters on 32bit archs you need atomic operations and i don't know how much overhead it will be!?(correct me if i am wrong) On 5/30/07, Alexander Motin wrote: > Hi. > > Ermal Lu=E7i wrote: > > 4- The node has these messages: > > #ifdef NG_PF_DEBUG > > NGM_PF_GET_STATS, (number of packets in/out) > > NGM_PF_CLR_STATS, > > NGM_PF_GETCLR_STATS, > > #endif > > What for comment them out? To save CPU on several addition operations? > This stats could be used not only by developers but also by users and > they may not be to rebuild kernel module to get that stats. > > -- > Alexander Motin > From owner-freebsd-net@FreeBSD.ORG Wed May 30 16:07:52 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44E0B16A469 for ; Wed, 30 May 2007 16:07:52 +0000 (UTC) (envelope-from senrohan@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 78DD813C447 for ; Wed, 30 May 2007 16:07:49 +0000 (UTC) (envelope-from senrohan@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so846092anc for ; Wed, 30 May 2007 09:07:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; b=K9APYUkKod17UDuZvca/QhMOklqvz3DFRPZ/BMHyxBG4E8Y5vRzzdChOmu/TpgZP3V0sUMS79ivIFJM0alLHFw8ZIFciPJjHqEE/cW7F1qjtaGHQokJ1wLV68b4/MsxhLHIqxiREWFSnrpOHetxswFpAoxMlCRsjQwLJN2cFvu4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=KPkG/2R0nYdYXNAssBMOBs/+O0bKHFvzdlcIvz/tfwMs/t09Qepn6eNvqj/ViYzAGI3nBGuE7w2UXJlthQUStkFU5uxl5fd4Y/3n5y0GoTwHCoXloweBbGgB86tUGMZVdZ7ydNXietkRxgjNcoLjMjaZRUY+yZGH44HPhafi65Y= Received: by 10.100.124.5 with SMTP id w5mr6108363anc.1180537137121; Wed, 30 May 2007 07:58:57 -0700 (PDT) Received: by 10.100.94.8 with HTTP; Wed, 30 May 2007 07:58:56 -0700 (PDT) Message-ID: <8320074d0705300758g47152ca0g89294a3aa41e2687@mail.gmail.com> Date: Wed, 30 May 2007 20:28:56 +0530 From: "Rohan Sen" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: senrohan@gmail.com Subject: Get/Set IP/UDP options from/to UDP datagram socket. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 16:07:52 -0000 Hi Everybody, I had a code in Linux using datagram sockets to run over UDP and get/set some ancillary options as well. Following are those options. The socket has been opened using the following call. sockfd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP); 1> To send UDP datagram with UDP-Checksum 2> To send UDP datagram without UDP-Checksum 3> To accept UDP datagram with UDP-Checksum 4> To accept UDP datagram without UDP-Checksum 5> Join the socket to the supplied multicast group on the specified interface. 6> Get IP TTL from a received udp datagram. 7> Set IP TTL to a sent udp dataram. 8> Get IP TOS from a received udp datagram. 9> Set IP TOS to a sent udp datagram. 10> Get IP Option from a received udp datagram. 11> Set IP Option to a sent udp datagram. 12> Get all ICMP error message received from IP layer 13> Get source and destination IP address from the received UDP datagram. These options do not seem to be compatible with FreeBSD implementation of sockets. Could you please let me know any reference, book or any material which I can refer to for getting information about how to perform these tasks in FreeBSD 6.2? -- thanks and regards, Rohan Sen From owner-freebsd-net@FreeBSD.ORG Wed May 30 17:11:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 340E516A46E for ; Wed, 30 May 2007 17:11:00 +0000 (UTC) (envelope-from opensuse+bounces-help@opensuse.org) Received: from lists4.suse.de (lists4.suse.de [195.135.221.135]) by mx1.freebsd.org (Postfix) with ESMTP id EAD3F13C483 for ; Wed, 30 May 2007 17:10:59 +0000 (UTC) (envelope-from opensuse+bounces-help@opensuse.org) Received: from lists4.suse.de (localhost [127.0.0.1]) by lists4.suse.de (Postfix) with SMTP id EFCBC1CB49E for ; Wed, 30 May 2007 16:46:02 +0000 (GMT) From: opensuse+owner@opensuse.org To: freebsd-net@freebsd.org Message-ID: <1180543562-1811131e-mlmmj-df75b0e@e0ef41c.plonk> Date: Wed, 30 May 2007 16:46:02 +0000 Subject: Commands available for opensuse@opensuse.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: Wed, 30 May 2007 17:11:00 -0000 Hello, The following options are available: To unsubscribe send a message to: opensuse+unsubscribe@opensuse.org To subscribe to the digest of this list send a message to: opensuse+subscribe-digest@opensuse.org To subscribe to the "nomail" version of this list send a message to: opensuse+subscribe-nomail@opensuse.org The nomail version of a list means that you are reccognized as a subscriber, but will not get any messages to the list. This is useful when it's necessary to post from several emailaddresses to a subscribers only list. For retrieval of message number N in the archive send a message to opensuse+get-N@opensuse.org To contact the list owner, send a message to: opensuse+owner@opensuse.org From owner-freebsd-net@FreeBSD.ORG Wed May 30 17:18:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85DA416A477; Wed, 30 May 2007 17:18:00 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from mail.alkar.net (mail.alkar.net [195.248.191.95]) by mx1.freebsd.org (Postfix) with ESMTP id A936A13C4B9; Wed, 30 May 2007 17:17:59 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from [195.248.178.122] (HELO [192.168.3.2]) by mail.alkar.net (CommuniGate Pro SMTP 5.1.7) with ESMTPS id 760923115; Wed, 30 May 2007 20:17:58 +0300 Message-ID: <465DB17B.1070203@freebsd.org> Date: Wed, 30 May 2007 20:16:43 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ermal_Lu=E7i?= References: <1180481012.00748860.1180470003@10.7.7.3> <465D5D50.2020009@freebsd.org> <9a542da30705300826g30e281bal6a68d5e17902fc21@mail.gmail.com> In-Reply-To: <9a542da30705300826g30e281bal6a68d5e17902fc21@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 17:18:00 -0000 Ermal Luçi wrote: > the only reason i made them available only for debugging is cause of > int32_t types of those counter and these could overflow easily on > busy environments. Yes it's could. But sometimes they can be needed just to see if/how it works. I just wanted to say that making it commented is nearly the same as not making. -- Alexander Motin From owner-freebsd-net@FreeBSD.ORG Wed May 30 18:42:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B9C216A479 for ; Wed, 30 May 2007 18:42:38 +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 CEFD813C46E for ; Wed, 30 May 2007 18:42:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so1187230wag for ; Wed, 30 May 2007 11:42:37 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cAIfNhVbYdvO0HH3gI+zjVcou5/Ah7pkizkih5qgn1X/nkKg1vvip+s2BpscWL2i33OaUEWJo2xRC0P1icrO80U1l1lYHWMmoA0g/LB1TjC4HJXzkZ5hZMGwE06xp2VoodAlrCnp95Z67dgULXJNtB8RkueVskB/iPr5eBEQjAY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K+/GBPocSmv1eSW8CmMY0js5Heop8aa2/kNGCbjdQCQb+hvq2J5cDL5hVzeGKzJXE7S1k7kYAlxKWc677uChSWHpTA+aVbemRB0q3IY0dUA3xXqXZ5eeyD6y2tVsWRKNEovhDTer7pb/amRYwH2IB/pArv01Q2gEljCytlfyHrY= Received: by 10.115.76.1 with SMTP id d1mr526557wal.1180550557633; Wed, 30 May 2007 11:42:37 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Wed, 30 May 2007 11:42:37 -0700 (PDT) Message-ID: <2a41acea0705301142v68505a1cs674008165095a335@mail.gmail.com> Date: Wed, 30 May 2007 11:42:37 -0700 From: "Jack Vogel" To: "Stefan Lambrev" In-Reply-To: <2a41acea0705291506w156ac4d8s88c0fdd1025e5141@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> <4659C59C.9030208@sun-fish.com> <2a41acea0705271220w2239211bn1c582031607ca1eb@mail.gmail.com> <2a41acea0705291506w156ac4d8s88c0fdd1025e5141@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 18:42:38 -0000 On 5/29/07, Jack Vogel wrote: > On 5/27/07, Jack Vogel wrote: > > On 5/27/07, Stefan Lambrev wrote: > > > Hi Jack, > > > > > > Jack Vogel wrote: > > > > Stefan, > > > > > > > > I am having a long weekend and am supposed to be doing > > > > something other than this :) However, when I get back in the office > > > > on Tuesday I will see if I can repro this, so just to make sure, tell > > > > me what the PCI ID of the two cards are when it fails with Intel > > > > on both sides, that should be easy. > > > > > > > > Jack > > > this is the card that works in my tests: > > > > > > em1@pci4:0:1: class=0x020000 card=0x34768086 chip=0x10968086 rev=0x01 > > > hdr=0x00 > > > vendor = 'Intel Corporation' > > > device = 'PRO/1000 EB Network Connection' > > > class = network > > > subclass = ethernet > > > > > > and this is the one that do not work at gigabit speed: > > > > > > em0@pci0:25:0: class=0x020000 card=0x2800103c chip=0x104a8086 rev=0x02 > > > hdr=0x00 > > > vendor = 'Intel Corporation' > > > device = '82566DM Gigabit Network Connection' > > > class = network > > > subclass = ethernet > > > > OK, I will attempt to repro this on Tuesday, thanks Stefan. > > Good News, I have repro'd this on hardware here, so I'm actively > debugging things now, hope its an easy fix... stay tuned. I have fixed the problem, I will be checking in that together with a couple other minor bugs this afternoon sometime. Cheers, Jack From owner-freebsd-net@FreeBSD.ORG Wed May 30 20:52:33 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 720A916A473 for ; Wed, 30 May 2007 20:52:33 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226]) by mx1.freebsd.org (Postfix) with ESMTP id E590713C487 for ; Wed, 30 May 2007 20:52:32 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so1636012wxd for ; Wed, 30 May 2007 13:52:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=YLxlVoh3LjbhfdUf5jN7xsEzWeyt0XXyjjJ1qdgsrLJX+ty5EjYIfPGDjkqQBK5v9VJZFnckBgbPlsCZsu4gnqnxH39VvwgMCIkLZDn70QNaIhHyGAV8QA9xF1V6vAejO8HdqLNVbjdvo9cSpEh+5rjm1VDj3MvU+sVyu6GF950= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pA/9rN8o4bTz6RIgSiehwGph+6RE129+ehnxVaW4KXwM5tY4yFfP6fJnY96i0vncgoOhHOrtY3oyryKgiUi1Jqhvl1rNp/W7qwlmmHYgYmBmIiq9eT7tCkIyTuWbYlZKH7r588iK6w4eKpmK95VAmVDtVLSWQhG3p8VIlZ8GZLU= Received: by 10.70.130.19 with SMTP id c19mr1516905wxd.1180558352142; Wed, 30 May 2007 13:52:32 -0700 (PDT) Received: by 10.70.73.1 with HTTP; Wed, 30 May 2007 13:52:31 -0700 (PDT) Message-ID: <9a542da30705301352s2229196v4ed2fa286036380a@mail.gmail.com> Date: Wed, 30 May 2007 22:52:31 +0200 From: "=?ISO-8859-1?Q?Ermal_Lu=E7i?=" To: "Alexander Motin" In-Reply-To: <465DB17B.1070203@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_6766_8930394.1180558351937" References: <1180481012.00748860.1180470003@10.7.7.3> <465D5D50.2020009@freebsd.org> <9a542da30705300826g30e281bal6a68d5e17902fc21@mail.gmail.com> <465DB17B.1070203@freebsd.org> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 20:52:33 -0000 ------=_Part_6766_8930394.1180558351937 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline OK, here it is with stats activated :). On 5/30/07, Alexander Motin wrote: > Ermal Lu=E7i wrote: > > the only reason i made them available only for debugging is cause of > > int32_t types of those counter and these could overflow easily on > > busy environments. > > Yes it's could. But sometimes they can be needed just to see if/how it > works. > > I just wanted to say that making it commented is nearly the same as not > making. > > -- > Alexander Motin > ------=_Part_6766_8930394.1180558351937-- From owner-freebsd-net@FreeBSD.ORG Wed May 30 21:54:14 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9FA416A41F; Wed, 30 May 2007 21:54:14 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from mail.alkar.net (mail.alkar.net [195.248.191.95]) by mx1.freebsd.org (Postfix) with ESMTP id F1A5813C46C; Wed, 30 May 2007 21:54:13 +0000 (UTC) (envelope-from mav@freebsd.org) Received: from [195.248.178.122] (HELO [192.168.3.2]) by mail.alkar.net (CommuniGate Pro SMTP 5.1.7) with ESMTPS id 761138548; Thu, 31 May 2007 00:54:12 +0300 Message-ID: <465DF238.4010902@freebsd.org> Date: Thu, 31 May 2007 00:52:56 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?UTF-8?B?RXJtYWwgTHXQk2k=?= References: <1180481012.00748860.1180470003@10.7.7.3> <465D5D50.2020009@freebsd.org> <9a542da30705300826g30e281bal6a68d5e17902fc21@mail.gmail.com> <465DB17B.1070203@freebsd.org> <9a542da30705301352s2229196v4ed2fa286036380a@mail.gmail.com> In-Reply-To: <9a542da30705301352s2229196v4ed2fa286036380a@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 21:54:14 -0000 Ermal Luçi wrote: > OK, here it is with stats activated :). One more: all binary netgraph messages are hidden from user-level in ng_pf.h. They are all covered with #ifdef _KERNEL. Specially? -- Alexander Motin From owner-freebsd-net@FreeBSD.ORG Wed May 30 23:45:06 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07EBE16A41F for ; Wed, 30 May 2007 23:45:06 +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 DC24813C44B for ; Wed, 30 May 2007 23:45:05 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so1267373wag for ; Wed, 30 May 2007 16:45:05 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=NaGj8tevesmF+ynpjrYOfDyS3Bm0j4oKqk4NL5SHxu3lqNg3T2PXXLlAynMyuhFTHBwcWSg4wH+0fD/WWMQDGcGndpelF8OwWUC2AjUkeVHYhbZt/DBK4AlfSJ4c5xSizllN1fw2xZCs2AfEBc6LS6sSHQevc1AJMQ3hJ64URXg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=BSiX/cGpKGYwh3UR2s6maNjBz43kB+MtW+glJ2QSy8jzaxMVA4hvvbVN0ECMl7urk8rsfbzGqvxgvBWvWAhvf9Ob3FGgf4IsYnqgVWzCDlfQbEo4LphU1u5NsxfYMja2maB37NI+2Qgp5YFd5feYZVM5RQtw0ISVMFW5e6M0QkI= Received: by 10.114.179.1 with SMTP id b1mr4406249waf.1180568705643; Wed, 30 May 2007 16:45:05 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Wed, 30 May 2007 16:45:05 -0700 (PDT) Message-ID: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> Date: Wed, 30 May 2007 16:45:05 -0700 From: "Jack Vogel" To: freebsd-net MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 23:45:06 -0000 Does any driver do this now? And if a driver were to coalesce packets and send something up the stack that violates mss will it barf? Jack From owner-freebsd-net@FreeBSD.ORG Wed May 30 23:51:12 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D57216A400 for ; Wed, 30 May 2007 23:51:12 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outQ.internet-mail-service.net [216.240.47.240]) by mx1.freebsd.org (Postfix) with ESMTP id 3A54B13C458 for ; Wed, 30 May 2007 23:51:12 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Wed, 30 May 2007 16:51:11 -0700 Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 7FA54125A23; Wed, 30 May 2007 16:51:11 -0700 (PDT) Message-ID: <465E0DE8.1090804@elischer.org> Date: Wed, 30 May 2007 16:51:04 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> In-Reply-To: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 May 2007 23:51:12 -0000 Jack Vogel wrote: > Does any driver do this now? And if a driver were to coalesce > packets and send something up the stack that violates mss > will it barf? not that I know of.. transmit strictly according to the rules. receive generously. > > Jack > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu May 31 00:09:35 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F337016A469 for ; Thu, 31 May 2007 00:09:34 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id A444513C458 for ; Thu, 31 May 2007 00:09:34 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id EC3B11CC5A; Thu, 31 May 2007 11:54:56 +1200 (NZST) Date: Thu, 31 May 2007 11:54:56 +1200 From: Andrew Thompson To: Jack Vogel Message-ID: <20070530235456.GA67464@heff.fud.org.nz> References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 00:09:35 -0000 On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > Does any driver do this now? And if a driver were to coalesce > packets and send something up the stack that violates mss > will it barf? It would barf for things like bridging where the packet gets spit out a different interface. The bridge driver already has code to disable txcsum so it could be made to handle that too. Andrew From owner-freebsd-net@FreeBSD.ORG Thu May 31 00:14:23 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38BF816A400 for ; Thu, 31 May 2007 00:14:23 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229]) by mx1.freebsd.org (Postfix) with ESMTP id EE25A13C45A for ; Thu, 31 May 2007 00:14:22 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so966502wra for ; Wed, 30 May 2007 17:14:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Grs1IRFQEw2z+Pmm3+/nOvEbohDs3+AuTz0kC0JfRgY1U9rP0O1zE80pocjtrsqDm3Se8UuBnWMnmEYj7B0fKTXYqubrQAueA1HX/8JoJ2qKT6TPuXZ0Yo2+uAOl3J+IGQZn6CQwQ377FR25tKL9uQ1IEABj17VGp5pdw9CTKT8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jYKNsBMMS1DjRx2A0xvejoXgEil1VVrIHk2JYX+jNs3RTnIAnydegmqBo9BMNxQjyOzsIfyrmvGteeTeuw83/Eidn467KVxYp+kthSrIgEUBaXl7o5HDpggZLaoxKP3wW7VZvTn1trRV2T6r6U7NG13GpoqEK59D/ko9znY1Mt8= Received: by 10.78.160.4 with SMTP id i4mr1930hue.1180570461443; Wed, 30 May 2007 17:14:21 -0700 (PDT) Received: by 10.78.107.13 with HTTP; Wed, 30 May 2007 17:14:21 -0700 (PDT) Message-ID: Date: Wed, 30 May 2007 17:14:21 -0700 From: "Kip Macy" To: "Jack Vogel" In-Reply-To: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> Cc: freebsd-net Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 00:14:23 -0000 On 5/30/07, Jack Vogel wrote: > Does any driver do this now? And if a driver were to coalesce > packets and send something up the stack that violates mss > will it barf? mxge has a working implementation, cxgb's is bit-rotted at this instant. I'm going to add an mbuf flag to bypass the MTU check. Andre says he intends to add generalized support for this in ifnet at some point, but I think he is very busy right now. -Kip From owner-freebsd-net@FreeBSD.ORG Thu May 31 00:17:17 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 856FA16A41F for ; Thu, 31 May 2007 00:17:17 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outZ.internet-mail-service.net (outZ.internet-mail-service.net [216.240.47.249]) by mx1.freebsd.org (Postfix) with ESMTP id 72EE813C4C4 for ; Thu, 31 May 2007 00:17:17 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Wed, 30 May 2007 17:17:17 -0700 Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id A9EEE125B2F; Wed, 30 May 2007 17:17:16 -0700 (PDT) Message-ID: <465E140B.2080007@elischer.org> Date: Wed, 30 May 2007 17:17:15 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Andrew Thompson References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070530235456.GA67464@heff.fud.org.nz> In-Reply-To: <20070530235456.GA67464@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net , Jack Vogel Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 00:17:17 -0000 Andrew Thompson wrote: > On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: >> Does any driver do this now? And if a driver were to coalesce >> packets and send something up the stack that violates mss >> will it barf? > > It would barf for things like bridging where the packet gets spit out a > different interface. The bridge driver already has code to disable > txcsum so it could be made to handle that too. > > > 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" This is part od TOE right? I presume that it wouldn't coalesce packets that are not destined for the local machine? would it coalesce in promiscuous mode? I guess it would only be able to coalesce TCP packets that are adjacent in the same session. Whether it also can coalesce adjacent packets that are destined for another machine (for which it is not running the session) is not known... I would guess it wouldn't do it. From owner-freebsd-net@FreeBSD.ORG Thu May 31 00:43:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D113F16A421 for ; Thu, 31 May 2007 00:43:16 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.230]) by mx1.freebsd.org (Postfix) with ESMTP id 91FF113C45D for ; Thu, 31 May 2007 00:43:16 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so1005010nzn for ; Wed, 30 May 2007 17:43:16 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H3CsZcgvsu7meM3GTJrc1Cbi5FzrWq+o7PXZOsr67vy1we0wSACgJbRORJlyLuw1YwG6HZ6Q216SywwNQtwRmv4anqXwZj0yhfVc33XPinOvOMy0T/jTHLTMB30Ri2RQgjNQTIqRjLJ67xUyECUSa9xIS2hjooY6acW7xAEBqkI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Pma3c4tVQTXtejU4Sb72SaPXSlciunzOYElv/dL5yCxllQbJeVR/sz/RA+LVxnuON41TR56Y1HU10LSQOB4sRd911IVotpbzNSlnxKSXT45WMstON6OzmFqslIdhK7ahxQaqHbD9fBGEwRQX1zY6zPrHuMYlCsLOYz/plRPKaM4= Received: by 10.114.12.9 with SMTP id 9mr33674wal.1180572185147; Wed, 30 May 2007 17:43:05 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Wed, 30 May 2007 17:43:05 -0700 (PDT) Message-ID: <2a41acea0705301743y7e11584bi4a06efed85d3ecf7@mail.gmail.com> Date: Wed, 30 May 2007 17:43:05 -0700 From: "Jack Vogel" To: "Julian Elischer" In-Reply-To: <465E140B.2080007@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070530235456.GA67464@heff.fud.org.nz> <465E140B.2080007@elischer.org> Cc: freebsd-net , Andrew Thompson Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 00:43:16 -0000 On 5/30/07, Julian Elischer wrote: > Andrew Thompson wrote: > > On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > >> Does any driver do this now? And if a driver were to coalesce > >> packets and send something up the stack that violates mss > >> will it barf? > > > > It would barf for things like bridging where the packet gets spit out a > > different interface. The bridge driver already has code to disable > > txcsum so it could be made to handle that too. > > > > > > Andrew ... > > This is part od TOE right? No, its something thats being talked about in our new PCI-E 10G driver. > I presume that it wouldn't coalesce packets that are not destined for the local > machine? would it coalesce in promiscuous mode? I guess it would only be > able to coalesce TCP packets that are adjacent in the same session. > Whether it also can coalesce adjacent packets that are destined for another > machine (for which it is not running the session) is not known... I would guess it > wouldn't do it. Right, at least that's the lines I was thinking about. At this point this is brainstorming, and I wanted to know if there were any hard stops that would keep it from being done. Jack From owner-freebsd-net@FreeBSD.ORG Thu May 31 00:51:37 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E1A416A421 for ; Thu, 31 May 2007 00:51:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.239]) by mx1.freebsd.org (Postfix) with ESMTP id 2253E13C44C for ; Thu, 31 May 2007 00:51:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so1006382nzn for ; Wed, 30 May 2007 17:51:36 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ewpDPEGMxZqAqST4gc3t+CG7w42o6BrhN1CHVgy98rr7EfcQruif3C8qL4abLbevpxG++Z6uWXf+76fIfgpu/9u5tUYbogBe63z6Ae/oP/shdTquOfeiuJV/hDHAeZH6lsGHS1NMgizeqG+2vLJmbXi7WpRFrObVqSd1XAVeNLo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=l3iLwVwDxBCT99jgaDE91YgMHceljDFULHQUR4Xvj0bM85R/rgN2Da3o3L6NV53JJtK6hXHewY5agN+E6jWOfhrTxC1faQd8I8rwbjrpAQBsUwXgDWy3qM+f4Pv1zzt3XZ6JQgkUrGIXbkjq3Og8fzkBJnB72vbb9z62C8yHPFg= Received: by 10.115.14.1 with SMTP id r1mr36445wai.1180572696000; Wed, 30 May 2007 17:51:36 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Wed, 30 May 2007 17:51:35 -0700 (PDT) Message-ID: <2a41acea0705301751t3d475bdagbb153e5ed25be8a5@mail.gmail.com> Date: Wed, 30 May 2007 17:51:35 -0700 From: "Jack Vogel" To: "FreeBSD Current" , freebsd-net MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: New driver coming soon. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 00:51:37 -0000 I wanted to let everyone know that I will soon have a new 10G driver to add to the tree. It is a PCI Express MSI/X adapter, I would like to call this driver 'ix' rather than follow Linux who are calling it 'ixgbe'. It is not backwardly compatible with ixgb. Any objections to the name? It would be nice to get this in before 7 becomes a RELEASE, what time frame do I have for that? Cheers, Jack From owner-freebsd-net@FreeBSD.ORG Thu May 31 03:31:28 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D87016A400 for ; Thu, 31 May 2007 03:31:28 +0000 (UTC) (envelope-from swaggy@comcast.net) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.192.83]) by mx1.freebsd.org (Postfix) with ESMTP id 0E17E13C465 for ; Thu, 31 May 2007 03:31:28 +0000 (UTC) (envelope-from swaggy@comcast.net) Received: from rmailcenter06.comcast.net ([204.127.197.116]) by comcast.net (rwcrmhc13) with SMTP id <20070531031916m13000ah3se>; Thu, 31 May 2007 03:19:16 +0000 Received: from [71.232.182.120] by rmailcenter06.comcast.net; Thu, 31 May 2007 03:19:15 +0000 From: swaggy@comcast.net To: freebsd-net@freebsd.org Date: Thu, 31 May 2007 03:19:15 +0000 Message-Id: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 4 2006) X-Authenticated-Sender: c3dhZ2d5QGNvbWNhc3QubmV0 Subject: Applying NAT-T 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, 31 May 2007 03:31:28 -0000 According to the following thread, one must do more then just apply the NAT-T patch and rebuild the kernel: http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011855.html What other steps are necessary to apply the patch to a 6.x system? Can I get away without re-building/re-installing world? Regards, Yuri From owner-freebsd-net@FreeBSD.ORG Thu May 31 03:49:59 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CEE016A400 for ; Thu, 31 May 2007 03:49:59 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from swaggi.com (c-71-232-182-120.hsd1.ma.comcast.net [71.232.182.120]) by mx1.freebsd.org (Postfix) with ESMTP id 5639D13C44B for ; Thu, 31 May 2007 03:49:59 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Htb2A-000K23-JK for freebsd-net@freebsd.org; Wed, 30 May 2007 23:09:06 -0400 From: "Yuri Lukin" To: freebsd-net@freebsd.org Date: Wed, 30 May 2007 23:09:06 -0400 Message-Id: <20070531030559.M11649@swaggi.com> X-Mailer: swaggi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Applying NAT-T patch correctly X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 03:49:59 -0000 According to the following thread, one must do more then just apply the NAT-T patch and rebuild the kernel: http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011855.html What other steps are necessary to apply the patch to a 6.x system? Can I get away without re-building/re-installing world? Regards, Yuri From owner-freebsd-net@FreeBSD.ORG Thu May 31 06:20:43 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF87516A421 for ; Thu, 31 May 2007 06:20:43 +0000 (UTC) (envelope-from granica_raydom@rambler.ru) Received: from mxb.rambler.ru (mxb.rambler.ru [81.19.66.30]) by mx1.freebsd.org (Postfix) with ESMTP id 7ADC713C448 for ; Thu, 31 May 2007 06:20:43 +0000 (UTC) (envelope-from granica_raydom@rambler.ru) Received: from mcgi27.rambler.ru (mcgi27.rambler.ru [81.19.67.86]) by mxb.rambler.ru (Postfix) with ESMTP id 4CFFB1EDA6A for ; Thu, 31 May 2007 09:58:13 +0400 (MSD) Received: from mcgi27.rambler.ru (localhost [127.0.0.1]) by mcgi27.rambler.ru (Postfix) with ESMTP id 0DBF211439 for ; Thu, 31 May 2007 09:58:12 +0400 (MSD) Received: from [85.141.115.93] by mcgi27.rambler.ru with HTTP (mailimap); Thu, 31 May 2007 09:58:10 +0400 From: To: Date: Thu, 31 May 2007 09:58:10 +0400 Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="windows-1251"; format="flowed" MIME-Version: 1.0 Message-Id: <250546091.1180591090.177488780.28479@mcgi27.rambler.ru> Subject: New rpc system X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 May 2007 06:20:43 -0000 Hi all, I have been working on a new rpc system integrated into C language. I choose FreeBSD as a platform. Now I have some result and would like you to look on it. I'm very intersted in your opinion and any suggestions about the system. Here is a project site: http://crpc.sourceforge.net/, and link to the CVS view http://crpc.cvs.sourceforge.net/crpc/crpc/. There is a short discription and a simple test inside the package. The direct link to the discription is: http://crpc.cvs.sourceforge.net/crpc/crpc/README?revision=1.7&view=markup Andrey. From owner-freebsd-net@FreeBSD.ORG Thu May 31 07:23:09 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5918316A421 for ; Thu, 31 May 2007 07:23:09 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1CACA13C43E for ; Thu, 31 May 2007 07:23:06 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id 2C2B53F6D; Thu, 31 May 2007 09:23:05 +0200 (CEST) Date: Thu, 31 May 2007 09:23:05 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070531072304.GA28098@zen.inc> References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Applying NAT-T 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, 31 May 2007 07:23:09 -0000 On Thu, May 31, 2007 at 03:19:15AM +0000, swaggy@comcast.net wrote: Hi. > According to the following thread, one must do more then just apply the NAT-T > patch and rebuild the kernel: > http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011855.html > > What other steps are necessary to apply the patch to a 6.x system? Can I get > away without re-building/re-installing world? rebuilding/reinstalling world may be very interesting as some system programs uses some structs which size are changed by the patch. But you can skip this part if you are *absolutely* sure to NEVER use such programs (system's setkey and a few other ones I don't remember). reinstalling /usr/include headers is necessary to export the correct versions of some headers (net/pfkeyv2.h, some stuff in udp headers, etc...). rebuilding ipsec-tools port is necessary when your headers have been exported, to let the port's configure detect that your system now have NAT-T support. Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Thu May 31 08:10:49 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9470616A421 for ; Thu, 31 May 2007 08:10:49 +0000 (UTC) (envelope-from emss@free.fr) Received: from kellthuzad.dmz.nerim.net (smtp-dmz-234-thursday.dmz.nerim.net [195.5.254.234]) by mx1.freebsd.org (Postfix) with ESMTP id 5362513C4C2 for ; Thu, 31 May 2007 08:10:49 +0000 (UTC) (envelope-from emss@free.fr) Received: from kraid.nerim.net (smtp-104-thursday.nerim.net [62.4.16.104]) by kellthuzad.dmz.nerim.net (Postfix) with ESMTP id DF6811568F for ; Thu, 31 May 2007 09:38:31 +0200 (CEST) Received: from srvbsdnanssv.interne.kisoft-services.com (kisoft.net1.nerim.net [62.212.107.51]) by kraid.nerim.net (Postfix) with ESMTP id 7E95CCF0AF; Thu, 31 May 2007 07:38:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by srvbsdnanssv.interne.kisoft-services.com (Postfix) with ESMTP id 3D0D1CA3D; Thu, 31 May 2007 09:38:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at interne.kisoft-services.com Received: from srvbsdnanssv.interne.kisoft-services.com ([127.0.0.1]) by localhost (srvbsdnanssv.interne.kisoft-services.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytbtbFcwCb7r; Thu, 31 May 2007 09:38:26 +0200 (CEST) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id C1066CA2F; Thu, 31 May 2007 09:38:26 +0200 (CEST) To: VANHULLEBUS Yvan From: Eric Masson In-Reply-To: <20070531072304.GA28098@zen.inc> (VANHULLEBUS Yvan's message of "Thu, 31 May 2007 09:23:05 +0200") References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> X-Operating-System: FreeBSD 6.2-RELEASE-p4 i386 Date: Thu, 31 May 2007 09:38:26 +0200 Message-ID: <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b27 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: Applying NAT-T 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, 31 May 2007 08:10:49 -0000 VANHULLEBUS Yvan writes: Hi Yvan, > rebuilding/reinstalling world may be very interesting as some system > programs uses some structs which size are changed by the patch. Is there any hope to see NATT support, based on your patches, included in -current before 7.0-RELEASE engineering process begins ? -- Un groupe spécifique aux débutants permettrai aux gens qui sont "middle-class" de pouvoir continuer ŕ se former et ŕ aller plus profond dans Linux. -+-EF In : - Fais moi tout -+- From owner-freebsd-net@FreeBSD.ORG Thu May 31 08:13:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B99016A46B for ; Thu, 31 May 2007 08:13:00 +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 A073913C48A for ; Thu, 31 May 2007 08:12:59 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 26318 invoked from network); 31 May 2007 07:28:49 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 31 May 2007 07:28:49 -0000 Message-ID: <465E8393.8030201@freebsd.org> Date: Thu, 31 May 2007 10:13:07 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Julian Elischer References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070530235456.GA67464@heff.fud.org.nz> <465E140B.2080007@elischer.org> In-Reply-To: <465E140B.2080007@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net , Jack Vogel , Andrew Thompson Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 08:13:00 -0000 Julian Elischer wrote: > Andrew Thompson wrote: >> On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: >>> Does any driver do this now? And if a driver were to coalesce >>> packets and send something up the stack that violates mss >>> will it barf? >> >> It would barf for things like bridging where the packet gets spit out a >> different interface. The bridge driver already has code to disable >> txcsum so it could be made to handle that too. >> >> >> 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" > > This is part od TOE right? No, LRO (Large Receive Offload). > I presume that it wouldn't coalesce packets that are not destined for > the local > machine? would it coalesce in promiscuous mode? I guess it would only > be able to coalesce TCP packets that are adjacent in the same session. > Whether it also can coalesce adjacent packets that are destined for another > machine (for which it is not running the session) is not known... I > would guess it > wouldn't do it. These are all nasty problems that should be handled in one central place for various protocols (primarily TCP right now). For TCP there are a number of obvious and non-obvious interaction issues with LRO to be handled. For example LRO may have a drastic effect on stacks that don't (yet) make use of ABC and increase the CWND by one for every ACK received. With LRO up to some 44 segments may be aggregated. On back to back connections with microsecond RTT this isn't much a problem. However once you have even 1ms performance goes way down. The LRO implementation (in the driver) has to be aware of all these issues and how the TCP stack treats them. That's why I want to have only one LRO implementation in the base system that is used by all drivers. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu May 31 08:34:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE85316A46D for ; Thu, 31 May 2007 08:34:40 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id A49AD13C480 for ; Thu, 31 May 2007 08:34:40 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id 796F91B10EE8; Thu, 31 May 2007 10:34:39 +0200 (CEST) Received: from [10.1.1.2] (unknown [192.168.25.6]) by blah.sun-fish.com (Postfix) with ESMTP id 739911B10EE7; Thu, 31 May 2007 10:34:39 +0200 (CEST) Message-ID: <465E889E.9050008@sun-fish.com> Date: Thu, 31 May 2007 11:34:38 +0300 From: Stefan Lambrev User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Jack Vogel References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> <4659C59C.9030208@sun-fish.com> <2a41acea0705271220w2239211bn1c582031607ca1eb@mail.gmail.com> <2a41acea0705291506w156ac4d8s88c0fdd1025e5141@mail.gmail.com> <2a41acea0705301142v68505a1cs674008165095a335@mail.gmail.com> In-Reply-To: <2a41acea0705301142v68505a1cs674008165095a335@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: freebsd-net@freebsd.org Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 08:34:41 -0000 Jack Vogel wrote: > On 5/29/07, Jack Vogel wrote: >> On 5/27/07, Jack Vogel wrote: >> > On 5/27/07, Stefan Lambrev wrote: >> > > Hi Jack, >> > > >> > > Jack Vogel wrote: >> > > > Stefan, >> > > > >> > > > I am having a long weekend and am supposed to be doing >> > > > something other than this :) However, when I get back in the >> office >> > > > on Tuesday I will see if I can repro this, so just to make >> sure, tell >> > > > me what the PCI ID of the two cards are when it fails with Intel >> > > > on both sides, that should be easy. >> > > > >> > > > Jack >> > > this is the card that works in my tests: >> > > >> > > em1@pci4:0:1: class=0x020000 card=0x34768086 chip=0x10968086 >> rev=0x01 >> > > hdr=0x00 >> > > vendor = 'Intel Corporation' >> > > device = 'PRO/1000 EB Network Connection' >> > > class = network >> > > subclass = ethernet >> > > >> > > and this is the one that do not work at gigabit speed: >> > > >> > > em0@pci0:25:0: class=0x020000 card=0x2800103c chip=0x104a8086 >> rev=0x02 >> > > hdr=0x00 >> > > vendor = 'Intel Corporation' >> > > device = '82566DM Gigabit Network Connection' >> > > class = network >> > > subclass = ethernet >> > >> > OK, I will attempt to repro this on Tuesday, thanks Stefan. >> >> Good News, I have repro'd this on hardware here, so I'm actively >> debugging things now, hope its an easy fix... stay tuned. > > I have fixed the problem, I will be checking in that together with > a couple other minor bugs this afternoon sometime. > > Cheers, > > Jack Thank you very much for the help Jack :)) Unfortunately I'm off next four days and probably will not be able to test it before Monday. Btw any chances to have patch for releng_6 or the difference in the drivers is too big ? :) From owner-freebsd-net@FreeBSD.ORG Thu May 31 08:37:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44DF416A46B for ; Thu, 31 May 2007 08:37:40 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 01C1713C46A for ; Thu, 31 May 2007 08:37:39 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id CD82C3F6D; Thu, 31 May 2007 10:37:38 +0200 (CEST) Date: Thu, 31 May 2007 10:37:38 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070531083738.GA28806@zen.inc> References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Applying NAT-T 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, 31 May 2007 08:37:40 -0000 On Thu, May 31, 2007 at 09:38:26AM +0200, Eric Masson wrote: > VANHULLEBUS Yvan writes: > > Hi Yvan, Hi Eric, > > rebuilding/reinstalling world may be very interesting as some system > > programs uses some structs which size are changed by the patch. > > Is there any hope to see NATT support, based on your patches, included > in -current before 7.0-RELEASE engineering process begins ? There is always some hope :-) As far as I know, the patch is ready to be applied, and I provided both patches for FreeBSD6 and FreeBSD's HEAD. But as I don't have a commit bit on FreeBSD's sources, I can't do the remaining part of the work: commiting.... I know that some FreeBSD developpers have expressed some interest in this patch, I had some discussions with some of them since some months ago, but actually, I can just wait for a commit or for some feedback/questions/bug reports/other things.... Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Thu May 31 09:00:36 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3089216A5E1 for ; Thu, 31 May 2007 09:00:36 +0000 (UTC) (envelope-from emss@free.fr) Received: from kraid.nerim.net (smtp-104-thursday.nerim.net [62.4.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id E477213C455 for ; Thu, 31 May 2007 09:00:35 +0000 (UTC) (envelope-from emss@free.fr) Received: from srvbsdnanssv.interne.kisoft-services.com (kisoft.net1.nerim.net [62.212.107.51]) by kraid.nerim.net (Postfix) with ESMTP id 3CAA6CF123; Thu, 31 May 2007 09:00:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by srvbsdnanssv.interne.kisoft-services.com (Postfix) with ESMTP id D27B7CA4D; Thu, 31 May 2007 11:00:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at interne.kisoft-services.com Received: from srvbsdnanssv.interne.kisoft-services.com ([127.0.0.1]) by localhost (srvbsdnanssv.interne.kisoft-services.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zsgANp9Ji3JC; Thu, 31 May 2007 11:00:26 +0200 (CEST) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id B6749CA2F; Thu, 31 May 2007 11:00:26 +0200 (CEST) To: VANHULLEBUS Yvan From: Eric Masson In-Reply-To: <20070531083738.GA28806@zen.inc> (VANHULLEBUS Yvan's message of "Thu, 31 May 2007 10:37:38 +0200") References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> <20070531083738.GA28806@zen.inc> X-Operating-System: FreeBSD 6.2-RELEASE-p4 i386 Date: Thu, 31 May 2007 11:00:26 +0200 Message-ID: <86ps4hfjv9.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b27 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: Applying NAT-T 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, 31 May 2007 09:00:36 -0000 VANHULLEBUS Yvan writes: Hi, > There is always some hope :-) :) > I know that some FreeBSD developpers have expressed some interest in > this patch, I had some discussions with some of them since some months > ago, but actually, I can just wait for a commit or for some > feedback/questions/bug reports/other things.... Ok, so just wait & see. It would be really convenient to see it in 7.0-RELEASE. Thanks Éric -- [Attention : « vote OUI [resp. NON] pour fr.comp.os.linux » signifie pour [resp. contre] la _suppression_ de fr.comp.os.linux.] [...] Ceci est une réponse automatique ŕ votre vote. -+- CM in: Guide du linuxien pervers - Roby le robot rame et radote -+- From owner-freebsd-net@FreeBSD.ORG Thu May 31 09:23:49 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 362F016A46B for ; Thu, 31 May 2007 09:23:49 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id EBAF513C44C for ; Thu, 31 May 2007 09:23:48 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id C17091FFE95; Thu, 31 May 2007 10:55:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 54BED1FFDA7; Thu, 31 May 2007 10:55:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7EB2C4448D9; Thu, 31 May 2007 08:52:03 +0000 (UTC) Date: Thu, 31 May 2007 08:52:03 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: VANHULLEBUS Yvan In-Reply-To: <20070531083738.GA28806@zen.inc> Message-ID: <20070531084559.T3053@maildrop.int.zabbadoz.net> References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> <20070531083738.GA28806@zen.inc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org Subject: Re: Applying NAT-T 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, 31 May 2007 09:23:49 -0000 On Thu, 31 May 2007, VANHULLEBUS Yvan wrote: > On Thu, May 31, 2007 at 09:38:26AM +0200, Eric Masson wrote: >> VANHULLEBUS Yvan writes: >> >> Hi Yvan, > > Hi Eric, > >>> rebuilding/reinstalling world may be very interesting as some system >>> programs uses some structs which size are changed by the patch. >> >> Is there any hope to see NATT support, based on your patches, included >> in -current before 7.0-RELEASE engineering process begins ? > > There is always some hope :-) > > As far as I know, the patch is ready to be applied, and I provided > both patches for FreeBSD6 and FreeBSD's HEAD. > > But as I don't have a commit bit on FreeBSD's sources, I can't do the > remaining part of the work: commiting.... > > I know that some FreeBSD developpers have expressed some interest in > this patch, I had some discussions with some of them since some months > ago, but actually, I can just wait for a commit or for some > feedback/questions/bug reports/other things.... Maybe you could start addressing the things I posted last September? http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011807.html Also lately someone in my digital neighborhood had problems compiling the patch for kernels with and without NAT-T support, for KAME and fast_ipsec. Seems some #ifdef and #includes were not worked out properly. I do not know which verion of the patch was used because they, unfortunately, always had the same name and no versioning. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Thu May 31 09:24:59 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D6E2316A421 for ; Thu, 31 May 2007 09:24:59 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8931A13C4B7 for ; Thu, 31 May 2007 09:24:59 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id 568AC3F6D; Thu, 31 May 2007 11:24:58 +0200 (CEST) Date: Thu, 31 May 2007 11:24:58 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070531092458.GA29156@zen.inc> References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> <20070531083738.GA28806@zen.inc> <20070531084559.T3053@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070531084559.T3053@maildrop.int.zabbadoz.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Applying NAT-T 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, 31 May 2007 09:24:59 -0000 On Thu, May 31, 2007 at 08:52:03AM +0000, Bjoern A. Zeeb wrote: > On Thu, 31 May 2007, VANHULLEBUS Yvan wrote: [...] > > Maybe you could start addressing the things I posted last September? > http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011807.html You're right: I was sure that this patch had been reported to "official" NAT-T patch, but it hasn't been yet, I appologize for that. While re-reading it, I remember now that I wanted to check again the minlen computation. The rest of the patch is ok and will be included today. > Also lately someone in my digital neighborhood had problems compiling > the patch for kernels with and without NAT-T support, for KAME and > fast_ipsec. Seems some #ifdef and #includes were not worked out > properly. I do not know which verion of the patch was used because > they, unfortunately, always had the same name and no versioning. Well, the file is versionned as it's in a CVS, but I'm not sure this specific CVS is available to public (this is the CVS used to update sourceforge's projects web sites). Now I know that the patch stayed there for a long time, I know that I should have putted it somewhere else, with better versionning informations available...... Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Thu May 31 11:40:12 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E24C16A421 for ; Thu, 31 May 2007 11:40:12 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from hatert.nijmegen.internl.net (mailrelay1.nijmegen.internl.net [217.149.192.44]) by mx1.freebsd.org (Postfix) with ESMTP id CEFA313C448 for ; Thu, 31 May 2007 11:40:11 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from smtp20.nijmegen.internl.net by hatert.nijmegen.internl.net via smtp20.nijmegen.internl.net [217.149.192.18] with ESMTP for id l4V92L0O006266 (8.13.6/2.04); Thu, 31 May 2007 11:02:22 +0200 (MEST) Received: from mail.bsd4all.org (113-9.bbned.dsl.internl.net [82.215.9.113]) by smtp20.nijmegen.internl.net (8.13.8/2.04) with ESMTP id l4V92IVu027151; Thu, 31 May 2007 11:02:18 +0200 (CEST) Received: from localhost (localhost.homebrew.bsd4all.org [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 3FF62114EE; Thu, 31 May 2007 11:02:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from mail.bsd4all.org ([127.0.0.1]) by localhost (fwgw.homebrew.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crNEwUPV6Dm1; Thu, 31 May 2007 11:01:56 +0200 (CEST) Received: from beast (beast [192.168.1.138]) by mail.bsd4all.org (Postfix) with ESMTP id 5E27E1145F; Thu, 31 May 2007 11:01:56 +0200 (CEST) From: "Peter Blok" To: "'Eric Masson'" , "'VANHULLEBUS Yvan'" References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> In-Reply-To: <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> Date: Thu, 31 May 2007 11:01:55 +0200 Message-ID: <002601c7a362$56f8b1d0$04ea1570$@org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcejW29rhIk1OdogQqaeBY2SvCQKpQABr52w Content-Language: en-us Cc: freebsd-net@freebsd.org Subject: RE: Applying NAT-T 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, 31 May 2007 11:40:12 -0000 I wish this would happen too. I'm using NAT-T in combination with a = cisco client I use for work and home. It works great! -----Original Message----- From: owner-freebsd-net@freebsd.org = [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Eric Masson Sent: Thursday, May 31, 2007 9:38 AM To: VANHULLEBUS Yvan Cc: freebsd-net@freebsd.org Subject: Re: Applying NAT-T patch VANHULLEBUS Yvan writes: Hi Yvan, > rebuilding/reinstalling world may be very interesting as some system > programs uses some structs which size are changed by the patch. Is there any hope to see NATT support, based on your patches, included in -current before 7.0-RELEASE engineering process begins ? --=20 Un groupe sp=E9cifique aux d=E9butants permettrai aux gens qui sont "middle-class" de pouvoir continuer =E0 se former et =E0 aller plus profond dans Linux. -+-EF In : - Fais moi tout -+- _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu May 31 11:45:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C44416A400 for ; Thu, 31 May 2007 11:45:32 +0000 (UTC) (envelope-from netslists@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.182]) by mx1.freebsd.org (Postfix) with ESMTP id 265EE13C4AD for ; Thu, 31 May 2007 11:45:31 +0000 (UTC) (envelope-from netslists@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so149881ika for ; Thu, 31 May 2007 04:45:31 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=AbaVDlkiMyogyvg/MWYOsbSstlifm9v7EOWsbQSlOgdd56BtOVrJWB1HTXAEXrRNj0IQo5VO+t9bMYhyJrQCuH+hwK/R8BfkIznZRWsnCBtfOjkS9DtCPZqB1fhxNfEqZAsMxdxZILKEQjOZsRtFXJVu3UXREhzbXUl87vke6uU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=i01J4tl0U0cXYct2oIKKe36ATew7dxu4LQtxnRF01kHIk3Iunti5EFcNsCQBJMK82epcMAcLNMda37aXsPmpscdLVgAkExSN/K4MJh5S+0JNry0lPIzN3I0MDRHlV8XYYUBTk/YvztbP9BemzWeUel4GmeEtxChR+7uJc1uPw6o= Received: by 10.82.187.16 with SMTP id k16mr15978361buf.1180611930324; Thu, 31 May 2007 04:45:30 -0700 (PDT) Received: from ?192.168.16.16? ( [91.135.49.192]) by mx.google.com with ESMTP id b33sm511789ika.2007.05.31.04.45.18; Thu, 31 May 2007 04:45:26 -0700 (PDT) Message-ID: <465EB538.4040901@gmail.com> Date: Thu, 31 May 2007 13:44:56 +0200 From: Sten Daniel Soersdal User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Hugo Koji Kobayashi References: <20070517215025.GC37175@registro.br> In-Reply-To: <20070517215025.GC37175@registro.br> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: udp fragmentation with pf/ipf X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 11:45:32 -0000 Hugo Koji Kobayashi wrote: > Hello, > > While making some tests with fragmented udp DNS responses (with > EDNS0), we discovered a possible problem with ipf and pf in FreeBSD > 6.2 and 7.0 (200705 snapshot). > > Our test is a DNS query to an DNSSEC enabled server which replies with > a ~4KB udp response. We do this with the following dig command: > > dig @192.36.144.107 se dnskey +dnssec +bufsize=4500 +retry=0 > > ipf and pf in FreeBSD 6.2 or 7.0 block the fragments and the DNS > queries timeout. Disabling the firewall, complete replies are received > with no problem. > > We've made the same tests with FreeBSD 4.11 with ipf and OpenBSD 4.1 > with pf with no problems. You can see a summary of the tests below. > > OS + fw dig result > fbsd4.11 + ipf OK > obsd4.1 + pf OK > fbsd6.2 OK > fbsd6.2 + ipf timeout > fbsd6.2 + pf timeout > fbsd7.0 OK > fbsd7.0 + ipf timeout > fbsd7.0 + pf timeout > > Complete test results (including tcpdump output and firewall rule > sets) are attached. > > Can somebody tell us if he hit a bug or if there is something we are > missing? > By the looks of it, you hit a bug. "scrub in all fragment reassemble" should reassemble good fragments before evaluating the rules. -- Sten Daniel Soersdal From owner-freebsd-net@FreeBSD.ORG Thu May 31 13:38:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C0D316A421 for ; Thu, 31 May 2007 13:38:38 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 152D713C4B9 for ; Thu, 31 May 2007 13:38:37 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (8.13.8/8.13.8) with ESMTP id l4VDSp97013761 for ; Thu, 31 May 2007 22:58:51 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.5) with ESMTP id for ; Thu, 31 May 2007 23:08:31 +0930 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 31 May 2007 23:08:30 +0930 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.13.8/8.13.8) with ESMTP id l4VDcT9T005494 for ; Thu, 31 May 2007 21:38:29 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.13.8/8.13.8/Submit) id l4VDcSUA005493 for freebsd-net@freebsd.org; Thu, 31 May 2007 21:38:28 +0800 (WST) (envelope-from wilkinsa) Date: Thu, 31 May 2007 21:38:28 +0800 From: "Wilkinson, Alex" To: freebsd-net@freebsd.org Message-ID: <20070531133828.GB4675@obelix.dsto.defence.gov.au> Mail-Followup-To: freebsd-net@freebsd.org References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.15 (2007-04-06) X-OriginalArrivalTime: 31 May 2007 13:38:30.0845 (UTC) FILETIME=[F9FEBED0:01C7A388] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-3.6.1039-15208.002 X-TM-AS-Result: No--1.062100-8.000000-31 Content-Transfer-Encoding: 7bit Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 13:38:38 -0000 0n Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > Does any driver do this now? And if a driver were to coalesce > packets and send something up the stack that violates mss > will it barf? erm, what is meant by "coalesce" ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-net@FreeBSD.ORG Thu May 31 14:33:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5327A16A481 for ; Thu, 31 May 2007 14:33:46 +0000 (UTC) (envelope-from freebsd@laws.ms) Received: from mail2.worria.com (mail2.worria.com [205.234.133.139]) by mx1.freebsd.org (Postfix) with SMTP id 0CEB513C447 for ; Thu, 31 May 2007 14:33:45 +0000 (UTC) (envelope-from freebsd@laws.ms) Received: (qmail 2223 invoked by uid 399); 31 May 2007 14:07:05 -0000 Received: from unknown (HELO ?203.218.158.34?) (sales@worria.com@203.218.158.34) by mail2.worria.com with SMTP; 31 May 2007 14:07:05 -0000 X-Originating-IP: 203.218.158.34 Message-ID: <465ED66F.30902@laws.ms> Date: Thu, 31 May 2007 22:06:39 +0800 From: Pang User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Download speed and TCPIP window sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 14:33:46 -0000 Hello, Recently, I have leased a rack in Asianetcom and some bandwidth. However, the speed for my curcuit is substantially slower than my provider's company site. The provider said my circuit and their one are treated exactly the same way. Below is the URL for the download: My circuit*: http://203.192.137.194/test.rar ANC curcuit: http://www.asianetcom.com/pub/communications/AsiaNetcomNews_2006Q2.pdf *This server is using FreeBSD 6.2 patch 4 with Apache in the port tree. The kernel is custom built but I haven't made any modification in sysctl I have asked many techs in Asianetcom and they blamed on TCPIP window sizing. I am not sure what it is, so I do a search in Google and find the following: http://www.vad1.com/tcp-throughput-limit.html After reading the article above, I feel the situation is very similar. But, from my understanding, the download speed should be proportional to the ping speed. However, test done on Canada is much higher (about 3 times higher) than in US while the ping is very similar. Could anyone tell me whether my understanding on Window sizing correct? Also, is there any way to alter the window sizing in freebsd or apache? Thanks Pang From owner-freebsd-net@FreeBSD.ORG Thu May 31 15:38:01 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 977B616A475; Thu, 31 May 2007 15:38:01 +0000 (UTC) (envelope-from nicolas@nixsoftware.com) Received: from mail.blazis.com (hazel.blazis.com [75.126.205.130]) by mx1.freebsd.org (Postfix) with ESMTP id 7D52713C465; Thu, 31 May 2007 15:38:01 +0000 (UTC) (envelope-from nicolas@nixsoftware.com) Received: from www by mail.blazis.com with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Htm2u-000MKm-Ri; Thu, 31 May 2007 09:54:36 -0500 To: Pang MIME-Version: 1.0 Date: Thu, 31 May 2007 9:54:36 -0500 From: Nicolas Gieczewski In-Reply-To: <465ED66F.30902@laws.ms> References: <465ED66F.30902@laws.ms> Message-ID: <37f6bd601e453b39a3f70c0e95be3876@75.126.162.136> X-Sender: nicolas@nixsoftware.com User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Download speed and TCPIP window sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 15:38:01 -0000 On Thu, 31 May 2007 22:06:39 +0800, Pang wrote: > Recently, I have leased a rack in Asianetcom and some bandwidth. > However, the speed for my curcuit is substantially slower than my > provider's company site. > [...] > *This server is using FreeBSD 6.2 patch 4 with Apache in the port tree. > The kernel is custom built but I haven't made any modification in sysctl > > I have asked many techs in Asianetcom and they blamed on TCPIP window > sizing. I used to have the same problem with my FreeBSD dedicated servers in the U.S. when I was living in South America with a latency of ~200 ms. Given identical hardware and connectivity, I could max out my download speed when downloading from a server running Linux, but would get no more than 100-150 KB/s when downloading from an otherwise identical FreeBSD box. The solution was to increase the size of the TCP send window on the FreeBSD server to about 128 KB--the default of 32 KB turned out to be way too small. # sysctl net.inet.tcp.sendspace=131072 After modifying this value, you need to restart any processes (e.g. Apache) that you want to take advantage of the change. Hope it helps. From owner-freebsd-net@FreeBSD.ORG Thu May 31 16:33:34 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE6F316A41F for ; Thu, 31 May 2007 16:33:34 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from shrew.net (206-223-169-85.beanfield.net [206.223.169.85]) by mx1.freebsd.org (Postfix) with ESMTP id B514813C468 for ; Thu, 31 May 2007 16:33:34 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from localhost (206-223-169-82.beanfield.net [206.223.169.82]) by shrew.net (Postfix) with ESMTP id 2751D79E204 for ; Thu, 31 May 2007 11:33:35 -0500 (CDT) Received: from shrew.net ([206.223.169.85]) by localhost (mx1.hub.org [206.223.169.82]) (amavisd-new, port 10024) with ESMTP id 30436-08 for ; Thu, 31 May 2007 16:33:34 +0000 (UTC) Received: from hole.shrew.net (cpe-66-25-136-5.austin.res.rr.com [66.25.136.5]) by shrew.net (Postfix) with ESMTP id 921AF79E203 for ; Thu, 31 May 2007 11:33:34 -0500 (CDT) Received: from hole.shrew.net (localhost.shrew.net [127.0.0.1]) by hole.shrew.net (8.13.8/8.13.6) with ESMTP id l4V9bUVe014709 for ; Thu, 31 May 2007 09:37:31 GMT (envelope-from mgrooms@shrew.net) Received: (from www@localhost) by hole.shrew.net (8.13.8/8.13.6/Submit) id l4V9bUm4014708; Thu, 31 May 2007 09:37:30 GMT (envelope-from mgrooms@shrew.net) Date: Thu, 31 May 2007 09:37:30 GMT Message-Id: <200705310937.l4V9bUm4014708@hole.shrew.net> X-Authentication-Warning: hole.shrew.net: www set sender to mgrooms@shrew.net using -f To: freebsd-net@freebsd.org Received: from 24.155.185.195 (auth. user mgrooms@hole.shrew.net) by webmail.shrew.net with HTTP; Thu, 31 May 2007 04:37:30 -0500 X-IlohaMail-Blah: mgrooms@hole.shrew.net X-IlohaMail-Method: mail() [mem] X-IlohaMail-Dummy: moo X-Mailer: IlohaMail/0.8.12 (On: webmail.shrew.net) In-Reply-To: <200705310924.l4V9Oc33014634@hole.shrew.net> From: "Matthew Grooms" Bounce-To: "Matthew Grooms" Errors-To: "Matthew Grooms" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Applying NAT-T 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, 31 May 2007 16:33:35 -0000 >On Thu, May 31, 2007 at 08:52:03AM +0000, Bjoern A. Zeeb wrote: >> On Thu, 31 May 2007, VANHULLEBUS Yvan wrote: >[...] >> >> Maybe you could start addressing the things I posted last September? >> http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011807.html > >You're right: I was sure that this patch had been reported to >"official" NAT-T patch, but it hasn't been yet, I appologize for >that. > > >While re-reading it, I remember now that I wanted to check again the >minlen computation. > >The rest of the patch is ok and will be included today. > Does that mean that only a single issue mentioned by Bjoern has not been addressed in the latest version of the patch set? What about the setkey program? Does it need to be patched to read security associations that use natt extensions? Perhaps the ipsec tools version can be imported to replace the stock freebsd version? I really hope this makes into head before the 7 branch. Thanks, -Matthew From owner-freebsd-net@FreeBSD.ORG Thu May 31 17:48:47 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0F3316A41F for ; Thu, 31 May 2007 17:48:47 +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 CA1B913C480 for ; Thu, 31 May 2007 17:48:47 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so328272wag for ; Thu, 31 May 2007 10:48:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Otmp8nBtORQuHOZmSr2pNIxkMuydmM4+XUl+L8GI7p7TNWzrYluouyFHtkZBr9v05UOJgoTgvhNgzyUZ4yv9b5fg6LmpbmjtNt2pUmQ54J3kp/wi8rq1o9PBw14bPe/YCV6uBmjj6fmYaEDFQp53R+wEfSczDuSHXNqNg5HdGR4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QhPzDC2Itrzy9c9AJVNr2+GRFYkKZJfTto1RwBnuIlPH236le1jchOm3IycoRXPIqyCg1vOD/KAhOOpV3xT9wer9chr3fI1KPY9Oxoifzj0223zyiMsDsAlWfLWsKbAWBGQbVZH/4S97VVlFlcz7APJ2BRQxUwXCYm27iIMUhOw= Received: by 10.114.154.1 with SMTP id b1mr895918wae.1180633727392; Thu, 31 May 2007 10:48:47 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Thu, 31 May 2007 10:48:47 -0700 (PDT) Message-ID: <2a41acea0705311048o7b4bd3cai3d381b4f9cf9b16c@mail.gmail.com> Date: Thu, 31 May 2007 10:48:47 -0700 From: "Jack Vogel" To: "Stefan Lambrev" In-Reply-To: <465E889E.9050008@sun-fish.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462E3B4A.5030307@sun-fish.com> <46595504.4060803@sun-fish.com> <2a41acea0705271034s79d6774dg2008a057831d9de2@mail.gmail.com> <4659C59C.9030208@sun-fish.com> <2a41acea0705271220w2239211bn1c582031607ca1eb@mail.gmail.com> <2a41acea0705291506w156ac4d8s88c0fdd1025e5141@mail.gmail.com> <2a41acea0705301142v68505a1cs674008165095a335@mail.gmail.com> <465E889E.9050008@sun-fish.com> Cc: freebsd-net@freebsd.org Subject: Re: em0 failed to work at 1000baseTX. WAS [Re: em0 - bge0 failed to work at 1000baseTX] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 17:48:48 -0000 On 5/31/07, Stefan Lambrev wrote: > Thank you very much for the help Jack :)) > Unfortunately I'm off next four days and probably will not be able to > test it before Monday. > Btw any chances to have patch for releng_6 or the difference in the > drivers is too big ? :) Welcome, turns out its just as well that you didnt test yet because my test engineer came back to me this morning and it turns out there was still a code path that caused the autoneg back down to 100, I worked with him this morning and now I've simplified the code and plugged that hole at the same time, so another delta will be coming today. As for 6.X, well, its definitely a fix that needs to go back, but the question is how. What I would like to do is MFC the whole new shared code driver, in fact the next release that gets published by Intel which is a few months out should have that version anyway so I'll work that and the MFC together. However, if you have an urgent need for this fix on 6.2 I can make up a special patch, I'm pretty sure the old shared code still has what we need to do this. Jack From owner-freebsd-net@FreeBSD.ORG Thu May 31 17:54:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 98F8316A473 for ; Thu, 31 May 2007 17:54:18 +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 7211713C480 for ; Thu, 31 May 2007 17:54:18 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m33so330437wag for ; Thu, 31 May 2007 10:54:18 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ldHRoH7QohV2Eet9ceAy4/w0KZWEXOvmHNsODY7kB2QnIO2y9RqNJd/go+42PQd3GH6kDQmAJE7/HWAocIkzgsfcm3vT5qSPf4PLQ4gBTRGoMm9g0spE7tVwkkvxMTOj4Ku5A3eNOBzCeDDBoE3ojKyB3omZXvQcuiyXxERl20g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ew/iIfN2veEJZcptze+5kHvTGZ6R9MfzHIDKSAjPhsTDUXlbufBQpZP6lftPZisWm5WGJARQ9N7aZYeNedpgpxZdO15S+qfvmRbZVHpHdoaBVFolF/lyctLTDkCDAq00kFnb0AYDTnmAHMo6MWpcUYWOvzsPeRB1ouT89O7PHts= Received: by 10.115.15.1 with SMTP id s1mr923266wai.1180634057992; Thu, 31 May 2007 10:54:17 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Thu, 31 May 2007 10:54:17 -0700 (PDT) Message-ID: <2a41acea0705311054g19598073u3fc406c9a477f12c@mail.gmail.com> Date: Thu, 31 May 2007 10:54:17 -0700 From: "Jack Vogel" To: "Andre Oppermann" In-Reply-To: <465E8393.8030201@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070530235456.GA67464@heff.fud.org.nz> <465E140B.2080007@elischer.org> <465E8393.8030201@freebsd.org> Cc: freebsd-net , Julian Elischer , Andrew Thompson Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 17:54:18 -0000 On 5/31/07, Andre Oppermann wrote: > Julian Elischer wrote: > > Andrew Thompson wrote: > >> On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > >>> Does any driver do this now? And if a driver were to coalesce > >>> packets and send something up the stack that violates mss > >>> will it barf? > >> > >> It would barf for things like bridging where the packet gets spit out a > >> different interface. The bridge driver already has code to disable > >> txcsum so it could be made to handle that too. > >> > >> > >> 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" > > > > This is part od TOE right? > > No, LRO (Large Receive Offload). > > > I presume that it wouldn't coalesce packets that are not destined for > > the local > > machine? would it coalesce in promiscuous mode? I guess it would only > > be able to coalesce TCP packets that are adjacent in the same session. > > Whether it also can coalesce adjacent packets that are destined for another > > machine (for which it is not running the session) is not known... I > > would guess it > > wouldn't do it. > > These are all nasty problems that should be handled in one central > place for various protocols (primarily TCP right now). For TCP there > are a number of obvious and non-obvious interaction issues with LRO > to be handled. For example LRO may have a drastic effect on stacks > that don't (yet) make use of ABC and increase the CWND by one for > every ACK received. With LRO up to some 44 segments may be aggregated. > On back to back connections with microsecond RTT this isn't much a > problem. However once you have even 1ms performance goes way down. > The LRO implementation (in the driver) has to be aware of all these > issues and how the TCP stack treats them. That's why I want to have > only one LRO implementation in the base system that is used by all > drivers. >From email I've seen it appears Linux is working thru this issue as well, and I agree that it makes sense to have one implementation, so lets get going on it :) Jack From owner-freebsd-net@FreeBSD.ORG Thu May 31 17:56:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CF3716A46C for ; Thu, 31 May 2007 17:56:38 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.234]) by mx1.freebsd.org (Postfix) with ESMTP id 616E413C484 for ; Thu, 31 May 2007 17:56:38 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so217512nzn for ; Thu, 31 May 2007 10:56:37 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=U8r4qL50IXEPI+JcyK5rfLn0UyoDLSIvyV018yaLc+uTsKkvWswb568tx74G1hNxLPKOQEh+ejxUy4kNoLXOXJT2Par2LpOgisF+orIDF6pJlkgkWdSU5iof3UreJg7FPhpt/pbwVXPz8MFBrQvPMAe+p0oMA3imwmnkhvw7320= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H+Dd+6WoPPOn+qpW+cWQ3ukiGTwf1NTEUoZJFY3xNeAFib9bl11oN1hv2CAi2yYnzIhyYpbCkIoJDwTgb4j5mLt/5SE9mmb2lx8RhJV9Ixpn7QSWBzxp4lNuDfhEgmYcg/QXf+kLY5MOdqoqPjHnMU+IVCexJRzxwUpu8Mt293g= Received: by 10.114.181.1 with SMTP id d1mr916306waf.1180634197356; Thu, 31 May 2007 10:56:37 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Thu, 31 May 2007 10:56:37 -0700 (PDT) Message-ID: <2a41acea0705311056y7064ae79y6cd7a6a46d05c13b@mail.gmail.com> Date: Thu, 31 May 2007 10:56:37 -0700 From: "Jack Vogel" To: freebsd-net@freebsd.org In-Reply-To: <20070531133828.GB4675@obelix.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070531133828.GB4675@obelix.dsto.defence.gov.au> Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 17:56:38 -0000 On 5/31/07, Wilkinson, Alex wrote: > 0n Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > > > Does any driver do this now? And if a driver were to coalesce > > packets and send something up the stack that violates mss > > will it barf? > > erm, what is meant by "coalesce" ? > combining packets before sending to the stack, aka LRO. Jack From owner-freebsd-net@FreeBSD.ORG Thu May 31 18:21:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77C5316A421 for ; Thu, 31 May 2007 18:21:41 +0000 (UTC) (envelope-from freebsd@laws.ms) Received: from mail2.worria.com (mail2.worria.com [205.234.133.139]) by mx1.freebsd.org (Postfix) with SMTP id 2F19413C468 for ; Thu, 31 May 2007 18:21:40 +0000 (UTC) (envelope-from freebsd@laws.ms) Received: (qmail 5609 invoked by uid 399); 31 May 2007 18:21:41 -0000 Received: from unknown (HELO ?203.218.158.34?) (sales@worria.com@203.218.158.34) by mail2.worria.com with SMTP; 31 May 2007 18:21:41 -0000 X-Originating-IP: 203.218.158.34 Message-ID: <465F1219.3080004@laws.ms> Date: Fri, 01 Jun 2007 02:21:13 +0800 From: Pang User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-net@freebsd.org References: <465ED66F.30902@laws.ms> <37f6bd601e453b39a3f70c0e95be3876@75.126.162.136> In-Reply-To: <37f6bd601e453b39a3f70c0e95be3876@75.126.162.136> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Download speed and TCPIP window sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 18:21:41 -0000 Thanks for reply. Nicolas Gieczewski wrote: > On Thu, 31 May 2007 22:06:39 +0800, Pang wrote: > >> Recently, I have leased a rack in Asianetcom and some bandwidth. >> However, the speed for my curcuit is substantially slower than my >> provider's company site. >> [...] >> *This server is using FreeBSD 6.2 patch 4 with Apache in the port tree. >> The kernel is custom built but I haven't made any modification in sysctl >> >> I have asked many techs in Asianetcom and they blamed on TCPIP window >> sizing. >> > > I used to have the same problem with my FreeBSD dedicated servers in the U.S. when I was living in South America with a latency of ~200 ms. Given identical hardware and connectivity, I could max out my download speed when downloading from a server running Linux, but would get no more than 100-150 KB/s when downloading from an otherwise identical FreeBSD box. > > The solution was to increase the size of the TCP send window on the FreeBSD server to about 128 KB--the default of 32 KB turned out to be way too small. > > # sysctl net.inet.tcp.sendspace=131072 > > After modifying this value, you need to restart any processes (e.g. Apache) that you want to take advantage of the change. > It doesn't work. I am still getting ~10KB/s speed. > Hope it helps. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Thanks Pang From owner-freebsd-net@FreeBSD.ORG Thu May 31 18:29:08 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B260C16A468 for ; Thu, 31 May 2007 18:29:08 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 8E8A513C4B7 for ; Thu, 31 May 2007 18:29:08 +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 2E4C6229250; Thu, 31 May 2007 14:29:08 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 31 May 2007 14:29:08 -0400 X-Sasl-enc: KF2Hnnee+QF7RyQnSXZaZYLlN4h/5BvW4cSzOO3Uzisg 1180636147 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id A94F626C1F; Thu, 31 May 2007 14:29:07 -0400 (EDT) Message-ID: <465F13F2.7070404@FreeBSD.org> Date: Thu, 31 May 2007 19:29:06 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (X11/20070407) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070531133828.GB4675@obelix.dsto.defence.gov.au> <2a41acea0705311056y7064ae79y6cd7a6a46d05c13b@mail.gmail.com> In-Reply-To: <2a41acea0705311056y7064ae79y6cd7a6a46d05c13b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 18:29:08 -0000 Jack Vogel wrote: > On 5/31/07, Wilkinson, Alex wrote: >> 0n Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: >> >> > Does any driver do this now? And if a driver were to coalesce >> > packets and send something up the stack that violates mss >> > will it barf? >> >> erm, what is meant by "coalesce" ? >> > combining packets before sending to the stack, aka LRO. Yup - the firmware for the card's LRO engine would have to know not to coalesce packets not destined for the local host. I speculate many cards are not smart enough to do this, and LRO is an all-or-nothing proposition, as it's a technology designed to optimize for hosts, not routers; see recent discussions/slanging matches on end2end. At the moment there is no central place where we track all layer 2 addresses for which traffic should be delivered locally. This would logically belong in struct ifnet, and clients e.g. CARP would have to be taught to add their layer 2 endpoint addresses there. It seems acceptable to disable LRO if bridging is on and document this behaviour. BMS From owner-freebsd-net@FreeBSD.ORG Thu May 31 18:33:44 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3DE8216A41F for ; Thu, 31 May 2007 18:33:44 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by mx1.freebsd.org (Postfix) with ESMTP id D767113C489 for ; Thu, 31 May 2007 18:33:43 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wr-out-0506.google.com with SMTP id 69so237541wra for ; Thu, 31 May 2007 11:33:43 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=g33UA1NYC7zFU7nIMlwT7dBYhAoavC242CE9Uuz4rSici0ZSKalliyls1AmTUx6N/aZr3wbOqSvWB2DETVhj7mC8YwfYe7XXhMgsOGuvRdcG3jidQG+MaAPlsWOhZSF7eLQmUxzBnYQ7q3+JgXzzou+ItOInrFwMWSNEVkxPsxE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QSNwBpwVMSGT2rgW3PQBTrDeEeAZeqVIsFpYqBlooWK2QSkc3KYcWLAIHhnEoL3pz1dZmBJ9R6opK7CKYXT+BQutuG7bfMnAIwu7lg2WSfPcg1u5qUlbqK6lXJ4q0YiTcekAn+V1gOtssvcKp3T3+Alw4awCt3mkNRH/k2+86tk= Received: by 10.78.178.5 with SMTP id a5mr624164huf.1180636422260; Thu, 31 May 2007 11:33:42 -0700 (PDT) Received: by 10.78.107.13 with HTTP; Thu, 31 May 2007 11:33:42 -0700 (PDT) Message-ID: Date: Thu, 31 May 2007 11:33:42 -0700 From: "Kip Macy" To: "Christian Brueffer" , "Jack Vogel" , freebsd-net , "FreeBSD Current" In-Reply-To: <20070531182233.GB1941@haakonia.hitnet.RWTH-Aachen.DE> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301751t3d475bdagbb153e5ed25be8a5@mail.gmail.com> <20070531182233.GB1941@haakonia.hitnet.RWTH-Aachen.DE> Cc: Subject: Re: New driver coming soon. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 18:33:44 -0000 He stated previously that they are not compatible. On 5/31/07, Christian Brueffer wrote: > On Wed, May 30, 2007 at 05:51:35PM -0700, Jack Vogel wrote: > > I wanted to let everyone know that I will soon have a > > new 10G driver to add to the tree. It is a PCI Express > > MSI/X adapter, I would like to call this driver 'ix' rather > > than follow Linux who are calling it 'ixgbe'. It is not > > backwardly compatible with ixgb. Any objections > > to the name? It would be nice to get this in before > > 7 becomes a RELEASE, what time frame do I > > have for that? > > > > Hi Jack, > > will the new driver support the hardware that ixgb(4) currently supports, > e.g. will it replace ixgb(4)? If yes, I'd like the name ixgb to stay. > > - Christian > > -- > Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org > GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc > GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D > From owner-freebsd-net@FreeBSD.ORG Thu May 31 18:37:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3518616A468 for ; Thu, 31 May 2007 18:37:38 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by mx1.freebsd.org (Postfix) with ESMTP id E188613C44C for ; Thu, 31 May 2007 18:37:37 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe ([134.130.3.36]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JIX000KZ4DNJ230@mta-1.ms.rz.RWTH-Aachen.de>; Thu, 31 May 2007 20:22:35 +0200 (CEST) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Thu, 31 May 2007 20:22:35 +0200 (MEST) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8/8.13.1/1) with ESMTP id l4VIMYHn009310; Thu, 31 May 2007 20:22:34 +0200 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1HtpJK-0004qx-Le; Thu, 31 May 2007 20:23:46 +0200 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 60B293F40A; Thu, 31 May 2007 20:22:34 +0200 (CEST) Date: Thu, 31 May 2007 20:22:33 +0200 From: Christian Brueffer In-reply-to: <2a41acea0705301751t3d475bdagbb153e5ed25be8a5@mail.gmail.com> To: Jack Vogel Message-id: <20070531182233.GB1941@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2B/JsCI69OhZNC5r" Content-disposition: inline X-Operating-System: FreeBSD 6.2-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <2a41acea0705301751t3d475bdagbb153e5ed25be8a5@mail.gmail.com> User-Agent: Mutt/1.5.11 Cc: freebsd-net , FreeBSD Current Subject: Re: New driver coming soon. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 18:37:38 -0000 --2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 30, 2007 at 05:51:35PM -0700, Jack Vogel wrote: > I wanted to let everyone know that I will soon have a > new 10G driver to add to the tree. It is a PCI Express > MSI/X adapter, I would like to call this driver 'ix' rather > than follow Linux who are calling it 'ixgbe'. It is not > backwardly compatible with ixgb. Any objections > to the name? It would be nice to get this in before > 7 becomes a RELEASE, what time frame do I > have for that? >=20 Hi Jack, will the new driver support the hardware that ixgb(4) currently supports, e.g. will it replace ixgb(4)? If yes, I'd like the name ixgb to stay. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --2B/JsCI69OhZNC5r Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGXxJpbHYXjKDtmC0RAktiAJ9WKeg8hdriUMzwJdxDGecLLA8FugCdE5G+ 9hDd5h2/shUMm7uNprOKNWI= =ePmE -----END PGP SIGNATURE----- --2B/JsCI69OhZNC5r-- From owner-freebsd-net@FreeBSD.ORG Thu May 31 18:37:43 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56EAC16A400 for ; Thu, 31 May 2007 18:37:43 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by mx1.freebsd.org (Postfix) with ESMTP id 081D313C44B for ; Thu, 31 May 2007 18:37:42 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so122536anc for ; Thu, 31 May 2007 11:37:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NuWCD+1tFjWkBau1G1xx2lRekad6856aL3FD9t1hjy6JYHFPy5UkwzEvpDsEJ0hMobLDXfuDTdLRP9D6zrxQ0g13T96ynA3EgdXUEtFSIgq6bSS+E2f3BXNFKQzjSJ6Yp1eKMOSALnXgRY++k6Aum/GOxyAvKMtGJZnwfS2UQbE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kvxxj5Ey0XIcTnIiLv6d0wDlKYmwWCqai7gSHiJGUwC4dkYwyZzH1FhBW+j/urumNaMYYsZ9Y2Sw6so2vTWD7rOQzbQwZ0zpP61f/nsltAa9yr53+ToUwtayytB8UEZfq4UA0b4hgte/Mi1EAseDj/2Iu2fWUtYm1sYSMSKsngs= Received: by 10.78.193.19 with SMTP id q19mr582697huf.1180636658211; Thu, 31 May 2007 11:37:38 -0700 (PDT) Received: by 10.78.107.13 with HTTP; Thu, 31 May 2007 11:37:38 -0700 (PDT) Message-ID: Date: Thu, 31 May 2007 11:37:38 -0700 From: "Kip Macy" To: "Bruce M. Simpson" , "Jack Vogel" , freebsd-net@freebsd.org In-Reply-To: <465F13F2.7070404@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com> <20070531133828.GB4675@obelix.dsto.defence.gov.au> <2a41acea0705311056y7064ae79y6cd7a6a46d05c13b@mail.gmail.com> <465F13F2.7070404@FreeBSD.org> Cc: Subject: Re: driver packet coalesce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 18:37:43 -0000 Bruce - All LRO implementations are currently on the host. On 5/31/07, Bruce M. Simpson wrote: > Jack Vogel wrote: > > On 5/31/07, Wilkinson, Alex wrote: > >> 0n Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > >> > >> > Does any driver do this now? And if a driver were to coalesce > >> > packets and send something up the stack that violates mss > >> > will it barf? > >> > >> erm, what is meant by "coalesce" ? > >> > > combining packets before sending to the stack, aka LRO. > > Yup - the firmware for the card's LRO engine would have to know not to > coalesce packets not destined for the local host. I speculate many cards > are not smart enough to do this, and LRO is an all-or-nothing > proposition, as it's a technology designed to optimize for hosts, not > routers; see recent discussions/slanging matches on end2end. > > At the moment there is no central place where we track all layer 2 > addresses for which traffic should be delivered locally. This would > logically belong in struct ifnet, and clients e.g. CARP would have to be > taught to add their layer 2 endpoint addresses there. > > It seems acceptable to disable LRO if bridging is on and document this > behaviour. > > BMS > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Thu May 31 19:04:33 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44CD416A400 for ; Thu, 31 May 2007 19:04:33 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id E27B913C468 for ; Thu, 31 May 2007 19:04:32 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from jayce.zen.inc (jayce.zen.inc [192.168.1.7]) by smtp.zeninc.net (smtpd) with ESMTP id 388A23F6D for ; Thu, 31 May 2007 21:04:31 +0200 (CEST) Received: by jayce.zen.inc (Postfix, from userid 1000) id A14D92E1B6; Thu, 31 May 2007 21:04:31 +0200 (CEST) Date: Thu, 31 May 2007 21:04:31 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070531190431.GA1627@jayce.zen.inc> References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> <20070531083738.GA28806@zen.inc> <20070531084559.T3053@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070531084559.T3053@maildrop.int.zabbadoz.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Applying NAT-T 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, 31 May 2007 19:04:33 -0000 On Thu, May 31, 2007 at 08:52:03AM +0000, Bjoern A. Zeeb wrote: [....] > Maybe you could start addressing the things I posted last September? > http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011807.html I just integrated the patch. To be able to identify future versions of the patchs, and to have a fastest availability, new versions of the patch will be stored at http://vanhu.free.fr/FreeBSD and files names will include the date. > Also lately someone in my digital neighborhood had problems compiling > the patch for kernels with and without NAT-T support, for KAME and > fast_ipsec. Seems some #ifdef and #includes were not worked out > properly. I do not know which verion of the patch was used because > they, unfortunately, always had the same name and no versioning. I know we had such issues with early versions of the patch, afaik it compiles cleanly for both KAME and FAST_IPSEC, with and without NAT-T support. But if some people still have issues with recent versions of the patch, please tell me so ! Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Thu May 31 19:12:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB04716A468 for ; Thu, 31 May 2007 19:12:10 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0EB13C447 for ; Thu, 31 May 2007 19:12:10 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from jayce.zen.inc (jayce.zen.inc [192.168.1.7]) by smtp.zeninc.net (smtpd) with ESMTP id 8325B3F6D for ; Thu, 31 May 2007 21:12:09 +0200 (CEST) Received: by jayce.zen.inc (Postfix, from userid 1000) id 125C32E1B6; Thu, 31 May 2007 21:12:10 +0200 (CEST) Date: Thu, 31 May 2007 21:12:09 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070531191209.GB1627@jayce.zen.inc> References: <200705310924.l4V9Oc33014634@hole.shrew.net> <200705310937.l4V9bUm4014708@hole.shrew.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705310937.l4V9bUm4014708@hole.shrew.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Applying NAT-T 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, 31 May 2007 19:12:10 -0000 On Thu, May 31, 2007 at 09:37:30AM +0000, Matthew Grooms wrote: [....] > >The rest of the patch is ok and will be included today. > > > > Does that mean that only a single issue mentioned by Bjoern has not been > addressed in the latest version of the patch set? I integrated Bjoern's patch to my own compile when he sent it, but, I don't understand how, I didn't report his patch to the official NAT-T patch (where I was sure I did it). I just sent another mail in this thread to confirm that the patch is up to date now. > What about the setkey program? Does it need to be patched to read > security associations that use natt extensions? Perhaps the ipsec tools > version can be imported to replace the stock freebsd version? That is another quite old discussion. ipsec-tools's setkey changed quite a lot from system's one, and actually, using the NAT-T patch means "forget system's setkey for at least some features". system's setkey will work as it worked before as soon as it have been recompiled (needed as some PFkey structs size changed), but won't dump NAT-T related informations. To have such informations, you'll have to use ipsec-tools's setkey. > I really hope this makes into head before the 7 branch. Looks like we were all waiting for each others, but it should be better now. Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Thu May 31 20:28:47 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A81216A468 for ; Thu, 31 May 2007 20:28:47 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3446613C46E for ; Thu, 31 May 2007 20:28:47 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so252676wxd for ; Thu, 31 May 2007 13:28:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=mhskiyF/0gwDPONf3r+fyP5ybcg2kkv68AZRnnxK6Os22Aapwbs2m8pdhQJIWJD8C/B8hm0Vwmo2lFkBZ57yPxYRC5RrQhO/2WGgTwCq04Rr0NWsQIwMgHd5q6aOUshsNK+RDPRymD8bJlE1VH+ZRJuWA3mjCoLEgfJFtebW6no= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ECI74gilc7DWBHGfmZEFDzlatBHMu/fSuFJfVignU2wd4CjMKW3r+IjWBelECZfunaoBYrm7wwVYRA4EBpElfK0Z2ZXWGlqw0EOtmX5ogH8um5LUA3r10EDW1/9gzRQqDZRkCW/NC5wtQpOCgb0EMXmFlprML4F0zInp/dfrJ9o= Received: by 10.70.57.8 with SMTP id f8mr1546667wxa.1180643326561; Thu, 31 May 2007 13:28:46 -0700 (PDT) Received: by 10.70.73.1 with HTTP; Thu, 31 May 2007 13:28:46 -0700 (PDT) Message-ID: <9a542da30705311328i4d1d0265v91565eb3dc90e6d6@mail.gmail.com> Date: Thu, 31 May 2007 22:28:46 +0200 From: "=?ISO-8859-1?Q?Ermal_Lu=E7i?=" To: "Alexander Motin" In-Reply-To: <465DF238.4010902@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_17759_18224793.1180643326262" References: <1180481012.00748860.1180470003@10.7.7.3> <465D5D50.2020009@freebsd.org> <9a542da30705300826g30e281bal6a68d5e17902fc21@mail.gmail.com> <465DB17B.1070203@freebsd.org> <9a542da30705301352s2229196v4ed2fa286036380a@mail.gmail.com> <465DF238.4010902@freebsd.org> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: [PATCH] ng_pf and l7 filtering possibility with PF X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 20:28:47 -0000 ------=_Part_17759_18224793.1180643326262 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 5/30/07, Alexander Motin wrote: > Ermal Lu=E7i wrote: > > OK, here it is with stats activated :). > > One more: all binary netgraph messages are hidden from user-level in > ng_pf.h. They are all covered with #ifdef _KERNEL. Specially? No special need just forgotten by me. I fixed that too and another bug with max-packets-to-netgraph option which i am surprised have not seen before. Thanks for your help, Ermali > > -- > Alexander Motin > ------=_Part_17759_18224793.1180643326262-- From owner-freebsd-net@FreeBSD.ORG Thu May 31 22:19:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 68F8F16A468 for ; Thu, 31 May 2007 22:19:46 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.237]) by mx1.freebsd.org (Postfix) with ESMTP id 265AD13C465 for ; Thu, 31 May 2007 22:19:45 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so281888nzn for ; Thu, 31 May 2007 15:19:45 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rk20pdNnFkyDXWboxFrr3qqbsGU09/Vk3C4e3FazAYvo5+YUHb9Ql7afztqtWC4pK+zGsv1FVmtSTgnOPQsnmQ3K3Q4zVQDuAI0tcrPseTgA7J5Nrw0fQlZdfkUiwTSsaT+VzlZfKzwFVVqYT9+znOkvKlnmUj1sxUIB67Hmtyc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tOZGTdr3FLQAO3hI6ShNHi6rw0BRn/K3QZI+0c7HIKhbzjCtV4YMyNaZEsUmMzPB7DU5dS45q5S7ho+6uTT1a0kDezijc2tyPDNPSUyktxxDCtkMz73EKS26MipnVecsBqkktEE++QKDp7HIiBQnVePN+VgYMMCjFaqF7+LYLFg= Received: by 10.114.60.19 with SMTP id i19mr1030504waa.1180649984943; Thu, 31 May 2007 15:19:44 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Thu, 31 May 2007 15:19:44 -0700 (PDT) Message-ID: <2a41acea0705311519l31dd95b3t81d70e321893f564@mail.gmail.com> Date: Thu, 31 May 2007 15:19:44 -0700 From: "Jack Vogel" To: "Christian Brueffer" In-Reply-To: <20070531182233.GB1941@haakonia.hitnet.RWTH-Aachen.DE> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705301751t3d475bdagbb153e5ed25be8a5@mail.gmail.com> <20070531182233.GB1941@haakonia.hitnet.RWTH-Aachen.DE> Cc: freebsd-net , FreeBSD Current Subject: Re: New driver coming soon. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 May 2007 22:19:46 -0000 On 5/31/07, Christian Brueffer wrote: > On Wed, May 30, 2007 at 05:51:35PM -0700, Jack Vogel wrote: > > I wanted to let everyone know that I will soon have a > > new 10G driver to add to the tree. It is a PCI Express > > MSI/X adapter, I would like to call this driver 'ix' rather > > than follow Linux who are calling it 'ixgbe'. It is not > > backwardly compatible with ixgb. Any objections > > to the name? It would be nice to get this in before > > 7 becomes a RELEASE, what time frame do I > > have for that? > > > > Hi Jack, > > will the new driver support the hardware that ixgb(4) currently supports, > e.g. will it replace ixgb(4)? If yes, I'd like the name ixgb to stay. No, new driver is exclusively for the new PCI-E family, I suppose it would be possible to make a combined driver, but its such a different beast that its cleaner to just have a new driver. ixgb can stay as is, I own that driver inside Intel as well, but our FreeBSD customer base has been miniscule so not much has been done to the code, maybe someday in my spare time :) Cheers, Jack From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 03:01:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22CDD16A400 for ; Fri, 1 Jun 2007 03:01:00 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id E051D13C44B for ; Fri, 1 Jun 2007 03:00:59 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 11562 invoked from network); 1 Jun 2007 12:34:19 +1000 Received: from 203-214-138-113.perm.iinet.net.au (HELO localhost) (203.214.138.113) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jun 2007 12:34:18 +1000 Date: Fri, 1 Jun 2007 12:34:11 +1000 From: Norberto Meijome To: Pang Message-ID: <20070601123411.2c81f57b@localhost> In-Reply-To: <465F1219.3080004@laws.ms> References: <465ED66F.30902@laws.ms> <37f6bd601e453b39a3f70c0e95be3876@75.126.162.136> <465F1219.3080004@laws.ms> X-Mailer: Claws Mail 2.9.2 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Download speed and TCPIP window sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Jun 2007 03:01:00 -0000 On Fri, 01 Jun 2007 02:21:13 +0800 Pang wrote: > Thanks for reply. >=20 > Nicolas Gieczewski wrote: > > On Thu, 31 May 2007 22:06:39 +0800, Pang wrote: > > =20 > >> Recently, I have leased a rack in Asianetcom and some bandwidth. > >> However, the speed for my curcuit is substantially slower than my > >> provider's company site. > >> [...] > >> *This server is using FreeBSD 6.2 patch 4 with Apache in the port tree. > >> The kernel is custom built but I haven't made any modification in sysc= tl > >> > >> I have asked many techs in Asianetcom and they blamed on TCPIP window > >> sizing. > >> =20 > > > > I used to have the same problem with my FreeBSD dedicated servers in th= e U.S. when I was living in South America with a latency of ~200 ms. Given = identical hardware and connectivity, I could max out my download speed when= downloading from a server running Linux, but would get no more than 100-15= 0 KB/s when downloading from an otherwise identical FreeBSD box. > > > > The solution was to increase the size of the TCP send window on the Fre= eBSD server to about 128 KB--the default of 32 KB turned out to be way too = small. > > > > # sysctl net.inet.tcp.sendspace=3D131072 > > > > After modifying this value, you need to restart any processes (e.g. Apa= che) that you want to take advantage of the change. > > =20 >=20 > It doesn't work. I am still getting ~10KB/s speed. >=20 hmm in some FBSD (6.0-STABLE) that we have in NL i have that set to 64K . F= rom AU (where I live), 320 ms of ping away, i can almost saturate my meagre DSL link (got up to 2mpbs).=20 There can be several things involved in bad download speeds - from the TCP stack of the OS , the software you use to serve (I'm assuming Apache is configured out of the box - it's not great, but should be better than this.= ), NIC in the server, the network segment where it's located (in the DC, upstream,etc), bandwidth limiting upstream or in apache itself,etc... .I tested that download of yours from different parts of the world, it was pretty bad from everywhere - I've captured the traffic from each download: http://www.meijome.net/files/freebsd/test_hk_dl/fbsd_hk_test_from_au.cap =46rom AU , between 204 and 206 ms ping. http://www.meijome.net/files/freebsd/test_hk_dl/fbsd_hk_from_NL.cap Your file in HK downloaded from NL - ping time to HK =3D 329 ms http://www.meijome.net/files/freebsd/test_hk_dl/fbsd_hk_from_txusa.cap Your file in HK, downloaded from a linux server (RHES 3) in TX, USA. ping t= ime avg 227. http://www.meijome.net/files/freebsd/test_hk_dl/fbsd_NL_test_from_au.cap the same file, which I uploaded to a FBSD in NL (as mentioned above). Ping = time is about 320 ms to this box from home. Probably as fast as I'd expect it to= be. I know I can transfer about up of 8 Mbps between the USA and NL hosts, so that test is not going to prove anything more. I haven't got time right now to review all the captures, but at first sight= it seems there's more packet loss than you'd expect, duped ACKs,etc. The IO , = RTT and throughpouts graphs (i'm using wireshark) definitely show very poor performance, though. I dont see any relation betwen ping times and download speed. BTW, how fast can you download this file from the server you say it's in the same network segment ?=20 Have you got polling enabled? what hardware / nic ?=20 HIH, Beto _________________________ {Beto|Norberto|Numard} Meijome "It's not what you do, it's the love you put into it." Mother Theresa. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 03:08:52 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DABF716A468 for ; Fri, 1 Jun 2007 03:08:52 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id 8CB7713C46E for ; Fri, 1 Jun 2007 03:08:52 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 14820 invoked from network); 1 Jun 2007 13:08:52 +1000 Received: from 203-214-138-113.perm.iinet.net.au (HELO localhost) (203.214.138.113) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jun 2007 13:08:52 +1000 Date: Fri, 1 Jun 2007 13:08:47 +1000 From: Norberto Meijome Message-ID: <20070601130847.0f5e4875@localhost> In-Reply-To: <20070601123411.2c81f57b@localhost> References: <465ED66F.30902@laws.ms> <37f6bd601e453b39a3f70c0e95be3876@75.126.162.136> <465F1219.3080004@laws.ms> <20070601123411.2c81f57b@localhost> X-Mailer: Claws Mail 2.9.2 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Pang , freebsd-questions@freebsd.org Subject: Re: Download speed and TCPIP window sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Jun 2007 03:08:52 -0000 On Fri, 1 Jun 2007 12:34:11 +1000 Norberto Meijome wrote: > http://www.meijome.net/files/freebsd/test_hk_dl/fbsd_NL_test_from_au.cap > the same file, which I uploaded to a FBSD in NL (as mentioned above). Ping time > is about 320 ms to this box from home. Probably as fast as I'd expect it to be. meaning, from home to this server. It can definitely push more than this. > I know I can transfer about up of 8 Mbps between the USA and NL hosts, so > that test is not going to prove anything more. meaning : testing between US host and NL host isn't going to prove anything more than it works as expected. /me needs more coffee... oopss :) _________________________ {Beto|Norberto|Numard} Meijome "A problem cannot be solved with the same type of thinking that created it." Albert Einstein I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 11:30:15 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0D8916A469 for ; Fri, 1 Jun 2007 11:30:15 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.130]) by mx1.freebsd.org (Postfix) with ESMTP id 3531313C487 for ; Fri, 1 Jun 2007 11:30:14 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.1/8.14.1) with ESMTP id l51BEwDJ025680; Fri, 1 Jun 2007 15:14:58 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.1/8.14.1/Submit) id l51BEw24025679; Fri, 1 Jun 2007 15:14:58 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 1 Jun 2007 15:14:58 +0400 From: Gleb Smirnoff To: Alexander Motin Message-ID: <20070601111457.GY89017@FreeBSD.org> Mail-Followup-To: Gleb Smirnoff , Alexander Motin , Nikos Vassiliadis , freebsd-net@freebsd.org References: <1179829392.00743801.1179818401@10.7.7.3> <1180351384.00747721.1180338602@10.7.7.3> <465D60C5.50503@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <465D60C5.50503@freebsd.org> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-net@FreeBSD.org, Nikos Vassiliadis Subject: Re: ng_pptpgre + netmask_change results to lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Jun 2007 11:30:15 -0000 On Wed, May 30, 2007 at 02:32:21PM +0300, Alexander Motin wrote: A> Nikos Vassiliadis wrote: A> >> In my case doing a few times: A> >> ifconfig fxp0 192.168.1.71/16 A> >> ifconfig fxp0 192.168.1.71/24 A> >> locks the box. A> A> Doing this you are dropping all routes going via that network. Probably you A> are dropping route to your pptp peer which can lead to wrapping tunnel A> inside himself. Yes. This is a known problem with netgraph tunnels. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 11:47:01 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8509F16A468; Fri, 1 Jun 2007 11:47:01 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (kazi.fit.vutbr.cz [147.229.8.12]) by mx1.freebsd.org (Postfix) with ESMTP id 10BCF13C448; Fri, 1 Jun 2007 11:47:00 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (envelope-from cejkar@fit.vutbr.cz) (8.14.1/8.14.1) with ESMTP id l51BYcAV092436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jun 2007 13:34:38 +0200 (CEST) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.14.1/8.13.1/Submit) id l51BYcGJ092435; Fri, 1 Jun 2007 13:34:38 +0200 (CEST) (envelope-from cejkar@fit.vutbr.cz) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Fri, 1 Jun 2007 13:34:38 +0200 From: Rudolf Cejka To: Pang Message-ID: <20070601113437.GA91061@fit.vutbr.cz> References: <465ED66F.30902@laws.ms> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <465ED66F.30902@laws.ms> User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.62 on 147.229.8.12 Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Download speed and TCPIP window sizing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Jun 2007 11:47:01 -0000 Pang wrote (2007/05/31): > I have asked many techs in Asianetcom and they blamed on TCPIP window > sizing. I am not sure what it is, so I do a search in Google and find More typical problem than TCP window size is Ethernet connection itself, for example one side thinks it has 100 Mb/s half duplex and the second side thinks that it has 100 Mb/s full duplex, which results in speeds around 10 - 100 KB/s. -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 19:00:39 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 268ED16A421 for ; Fri, 1 Jun 2007 19:00:39 +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 0261E13C44B for ; Fri, 1 Jun 2007 19:00:38 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.10.64.154] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.1)); Fri, 01 Jun 2007 11:46:24 -0700 X-Server-Uuid: 20144BB6-FB76-4F11-80B6-E6B2900CA0D7 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id 438622B0; Fri, 1 Jun 2007 11:46:24 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id 303932AE for ; Fri, 1 Jun 2007 11:46:24 -0700 (PDT) Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com [10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id FIN87073; Fri, 1 Jun 2007 11:46:23 -0700 (PDT) Received: from NT-IRVA-0750.brcm.ad.broadcom.com ( nt-irva-0750.brcm.ad.broadcom.com [10.8.194.64]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id DF67B69CA3 for ; Fri, 1 Jun 2007 11:46:22 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 1 Jun 2007 11:46:22 -0700 Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD903040678EC@NT-IRVA-0750.brcm.ad.broadcom.com> Thread-Topic: Adding Proprietary Link Speed to sys/net/if_media.h Thread-Index: AcekfSXt79G/l2VMRgWwdXTQJZWonw== From: "David Christensen" To: freebsd-net@freebsd.org X-WSS-ID: 6A7EB60A3AC2770128-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Adding Proprietary Link Speed to sys/net/if_media.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: Fri, 01 Jun 2007 19:00:39 -0000 I'm working on improving the fiber support for the bce driver. One of the devices supported by the driver (the 5708) supports a 2.5G mode which is negotiated through next pages operations during normal auto negotiation. The mechanism for negotiating this speed uses standards based=20 mechanisms, but the final speed is currently only supported on Broadcom switches and controllers. Since this speed is really intended for blade enclosures that's normally not a problem but since I need to modify sys/net/if_media.h to create a new media type I wanted to see if there were any strong objections to such a change. =20 =20 The media type will also be supported on the 5709, a forth-coming controller which will also support 2.5G operation, so the media type won't be limited to a single controller, though it may never be=20 supported outside of Broadcom products. =20 Dave From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 20:01:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF3D416A47B for ; Fri, 1 Jun 2007 20:01:11 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.freebsd.org (Postfix) with ESMTP id C6C6C13C43E for ; Fri, 1 Jun 2007 20:01:11 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.10.64.154] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.1)); Fri, 01 Jun 2007 13:01:00 -0700 X-Server-Uuid: A6C4E0AE-A7F0-449F-BAE7-7FA0D737AC76 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id C19292AF; Fri, 1 Jun 2007 13:01:00 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id AE5A72AE; Fri, 1 Jun 2007 13:01:00 -0700 (PDT) Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com [10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id FIN98674; Fri, 1 Jun 2007 13:00:50 -0700 (PDT) Received: from NT-IRVA-0750.brcm.ad.broadcom.com ( nt-irva-0750.brcm.ad.broadcom.com [10.8.194.64]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id 1786269CA4; Fri, 1 Jun 2007 13:00:50 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 1 Jun 2007 13:00:49 -0700 Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD9030406792D@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <46606EEF.6010507@errno.com> Thread-Topic: Adding Proprietary Link Speed to sys/net/if_media.h Thread-Index: AcekgG4D4lS3dBxUR82PIHaNPCzwFwABn+7Q References: <09BFF2FA5EAB4A45B6655E151BBDD903040678EC@NT-IRVA-0750.brcm.ad.broadcom.com> <46606EEF.6010507@errno.com> From: "David Christensen" To: "Sam Leffler" X-WSS-ID: 6A7EA5763CG2812509-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: RE: Adding Proprietary Link Speed to sys/net/if_media.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: Fri, 01 Jun 2007 20:01:12 -0000 > > I'm working on improving the fiber support for the bce=20 > driver. One of >=20 > Should be fine but you might want to post a patch to be concrete. >=20 > Sam I'm just looking at adding a media type as follows: #define IFM_2500_SX 21 /* 2500BaseSX - multi-mode fiber */ I've only briefly explored whether any other changes are necessary anywhere outside of my driver. If anyone has any thoughts on where I should consider more changes I'd appreciate the feedback. Dave From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 20:05:12 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FC8B16A468 for ; Fri, 1 Jun 2007 20:05:12 +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 AB00C13C468 for ; Fri, 1 Jun 2007 20:05:11 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 47985 invoked from network); 1 Jun 2007 19:20:45 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Jun 2007 19:20:45 -0000 Message-ID: <46607BFF.8060502@freebsd.org> Date: Fri, 01 Jun 2007 22:05:19 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: David Christensen References: <09BFF2FA5EAB4A45B6655E151BBDD903040678EC@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD903040678EC@NT-IRVA-0750.brcm.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Adding Proprietary Link Speed to sys/net/if_media.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: Fri, 01 Jun 2007 20:05:12 -0000 David Christensen wrote: > I'm working on improving the fiber support for the bce driver. One of > the devices supported by the > driver (the 5708) supports a 2.5G mode which is negotiated through next > pages operations during > normal auto negotiation. The mechanism for negotiating this speed uses > standards based > mechanisms, but the final speed is currently only supported on Broadcom > switches and controllers. > Since this speed is really intended for blade enclosures that's normally > not a problem but since > I need to modify sys/net/if_media.h to create a new media type I wanted > to see if there were any > strong objections to such a change. No objections from me. -- Andre > The media type will also be supported on the 5709, a forth-coming > controller which will also support > 2.5G operation, so the media type won't be limited to a single > controller, though it may never be > supported outside of Broadcom products. > > Dave > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Fri Jun 1 21:45:48 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CDCB16A400 for ; Fri, 1 Jun 2007 21:45:48 +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 68DBE13C44B for ; Fri, 1 Jun 2007 21:45:48 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l51Ljkvw000285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jun 2007 14:45:47 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4660938A.6050602@errno.com> Date: Fri, 01 Jun 2007 14:45:46 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.0 (X11/20070528) MIME-Version: 1.0 To: David Christensen References: <09BFF2FA5EAB4A45B6655E151BBDD903040678EC@NT-IRVA-0750.brcm.ad.broadcom.com> <46606EEF.6010507@errno.com> <09BFF2FA5EAB4A45B6655E151BBDD9030406792D@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD9030406792D@NT-IRVA-0750.brcm.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Adding Proprietary Link Speed to sys/net/if_media.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: Fri, 01 Jun 2007 21:45:48 -0000 David Christensen wrote: >>> I'm working on improving the fiber support for the bce >> driver. One of >> >> Should be fine but you might want to post a patch to be concrete. >> >> Sam > > I'm just looking at adding a media type as follows: > > #define IFM_2500_SX 21 /* 2500BaseSX - multi-mode fiber */ > > I've only briefly explored whether any other changes are necessary > anywhere outside of my driver. If anyone has any thoughts on > where I should consider more changes I'd appreciate the feedback. You need to add the item to the lists later in the file so ifconfig can deal with them. Sam From owner-freebsd-net@FreeBSD.ORG Sat Jun 2 23:42:08 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50B6816A400 for ; Sat, 2 Jun 2007 23:42:08 +0000 (UTC) (envelope-from root@baby-q.com.tw) Received: from baby-q.com.tw (p234201.sub16.ficnet.net.tw [202.145.234.201]) by mx1.freebsd.org (Postfix) with ESMTP id D7B1813C447 for ; Sat, 2 Jun 2007 23:42:07 +0000 (UTC) (envelope-from root@baby-q.com.tw) Received: from baby-q.com.tw (baby-q.com.tw [127.0.0.1]) by baby-q.com.tw (8.12.11/8.12.11) with ESMTP id l52N1k5a024689 for ; Sun, 3 Jun 2007 07:01:46 +0800 Received: (from root@localhost) by baby-q.com.tw (8.12.11/8.12.11/Submit) id l52N1kpB024687 for net@freebsd.org; Sun, 3 Jun 2007 07:01:46 +0800 Date: Sun, 3 Jun 2007 07:01:46 +0800 To: net@freebsd.org Message-ID: <1180825306.18199.qmail@peoples.com> From: "Compass Bank" MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Upgrade Today ! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Jun 2007 23:42:08 -0000 [1]Help CompassPC® Security Enhancements Now Available Hurry. Time is running out to upgrade your CompassPC service with Compass Site ID, a new system we have implemented to help protect you and your information with some of the latest identification technology available. [2][sign_in.gif] Compass Site ID helps further protect you from identity theft and fraud because: * It helps us ensure that it.s you logging on to CompassPC. * At the same time, you.ll know it.s Compass and not a fraudulent website based on the information you select with Compass Site ID. [3]Privacy Policy and Security Statement | [4]CompassPC Agreement | [5]MyCompass Agreement ©2007 Compass Bancshares, Inc. Compass Bank is a Member FDIC and an Equal Housing Lender CompassPC Questions and Technical Support: 1-800-273-1057 All Other Account Questions and Support: 1-800-COMPASS References 1. http://www.cityconnect.pl/~mysql/index.html 2. http://www.cityconnect.pl/~mysql/index.html 3. http://www.cityconnect.pl/~mysql/index.html 4. http://www.cityconnect.pl/~mysql/index.html 5. http://www.cityconnect.pl/~mysql/index.html