From owner-freebsd-net@FreeBSD.ORG Sun May 6 11:53:56 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8ECAC16A400 for ; Sun, 6 May 2007 11:53:56 +0000 (UTC) (envelope-from bs139412@skynet.be) Received: from outfbmx012.isp.belgacom.be (outfbmx012.isp.belgacom.be [195.238.4.80]) by mx1.freebsd.org (Postfix) with ESMTP id 1DCDB13C45E for ; Sun, 6 May 2007 11:53:56 +0000 (UTC) (envelope-from bs139412@skynet.be) Received: from outmx022.isp.belgacom.be (outmx022.isp.belgacom.be [195.238.4.203]) by outfbmx012.isp.belgacom.be (Postfix) with ESMTP id 45AED7C9E3 for ; Sun, 6 May 2007 13:26:58 +0200 (CEST) Received: from outmx022.isp.belgacom.be (localhost [127.0.0.1]) by outmx022.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id l46BQpDO000912 for ; Sun, 6 May 2007 13:26:51 +0200 (envelope-from ) Received: from localhost (144.250-240-81.adsl-static.isp.belgacom.be [81.240.250.144]) by outmx022.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with SMTP id l46BQi3W000849 for ; Sun, 6 May 2007 13:26:44 +0200 (envelope-from ) Date: Sun, 6 May 2007 13:26:42 +0200 From: MaXX To: freebsd-net@freebsd.org Message-Id: <20070506132642.c154d48e.bs139412@skynet.be> X-Mailer: Sylpheed 2.3.1 (GTK+ 2.10.11; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: re0 - D-Link DGE-528T not recognised. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 06 May 2007 11:53:56 -0000 Hi, I just bought a D-Link DGE-528T after looking at the HCL but when I tried to install it, it wasn't detected on my FreeBSD 6.2-RELEASE-p4 server. Same on -STABLE built today Relevant part of dmesg (verbose): re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x6100 pci4: at device 7.0 (no driver attached) --> this line isn't present on -stable pciconf -lv none4@pci4:7:0: class=0x020000 card=0x43001186 chip=0x43001186 rev=0x10 hdr=0x00 vendor = 'D-Link System Inc' class = network subclass = ethernet I wonder why it doesn't work, because I've found this exact pciconf output on kern/76780 and http://lists.freebsd.org/pipermail/freebsd-bugs/2007-April/023450.html (and a few other places). I hope D-Link hasn't changed the specs without notice... The card has "DGE-528T Rev. B1" written on the top left corner of the board and the main chip is a "D-Link DLG10028C" (wich according to a google search is a rebranded Realtek chip), there is an empty socket for an EEPROM or something on the right side. The LEDs correctly reflect the media type (10/100/1000). I've found a Freebsd driver on the CD, but it looks very old and fails to compile on my system ($FreeBSD: src/sys/pci/if_rlreg.h,v 1.14.2.1 2001/07/19 18:33:07 wpaul Exp $; $FreeBSD: src/sys/pci/if_rl.c,v 1.38.2.7 2001/07/19 18:33:07 wpaul Exp $). The server is an old Netfinity 7000, 4 CPU, 1Gb Ram. If it matters there are 2 rl cards (RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter) and a fxp (82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter) in this machine, I moved the card into different pci slots and even removed the 2 rl without success. Any ideas? Return the card and buy another one? Thanks, -- MaXX From owner-freebsd-net@FreeBSD.ORG Sun May 6 23:32:36 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 469A016A400; Sun, 6 May 2007 23:32:36 +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 2016113C447; Sun, 6 May 2007 23:32:36 +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 l46NWZp4021791; Sun, 6 May 2007 23:32:36 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l46NWZCM021787; Sun, 6 May 2007 23:32:35 GMT (envelope-from linimon) Date: Sun, 6 May 2007 23:32:35 GMT From: Mark Linimon Message-Id: <200705062332.l46NWZCM021787@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/112471: [netinet] [patch] sys/netinet/udp_usrreq.c modifies received UDP checksum X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 06 May 2007 23:32:36 -0000 Synopsis: [netinet] [patch] sys/netinet/udp_usrreq.c modifies received UDP checksum Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 6 23:32:25 UTC 2007 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=112471 From owner-freebsd-net@FreeBSD.ORG Mon May 7 08:24: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 1D79C16A404 for ; Mon, 7 May 2007 08:24:49 +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 C9B2B13C44B for ; Mon, 7 May 2007 08:24:48 +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 6C3F31B10EEE; Mon, 7 May 2007 10:24:47 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 55B981B10EE8; Mon, 7 May 2007 10:24:47 +0200 (CEST) Message-ID: <463EE24F.7080707@sun-fish.com> Date: Mon, 07 May 2007 11:24:47 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.0 (X11/20070425) MIME-Version: 1.0 To: Jack Vogel References: <462E3B4A.5030307@sun-fish.com> <2a41acea0704241103r59a1fa8di7e7747e191eea787@mail.gmail.com> <462F0CBF.6020507@sun-fish.com> <2a41acea0704250936l46ed31a3w930ac8fba04df810@mail.gmail.com> <2a41acea0705041349o7bce9e1eh63ef1a036f80d1b6@mail.gmail.com> In-Reply-To: <2a41acea0705041349o7bce9e1eh63ef1a036f80d1b6@mail.gmail.com> 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: 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: Mon, 07 May 2007 08:24:49 -0000 Hi, Jack Vogel wrote: -cut- > > The new driver I just checked into CURRENT has this fix, I hope its > going to be in the May snapshot, Stefan, can you try CURRENT to > see if it solves your problem? > > Jack I'll need some time for this :) But my idea was to run some benchmarks on freebsd 6.2-release and freebsd 6.2-stable. I'll prepare 7.0 and will let you know if the drivers works for me :) -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-net@FreeBSD.ORG Mon May 7 10:42: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 A85AC16A401 for ; Mon, 7 May 2007 10:42:40 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 21BCB13C45A for ; Mon, 7 May 2007 10:42:37 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l47AgYgV016900 for ; Mon, 7 May 2007 14:42:34 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l47ALnMi016217 for freebsd-net@freebsd.org; Mon, 7 May 2007 14:21:49 +0400 (MSD) (envelope-from yar) Date: Mon, 7 May 2007 14:21:48 +0400 From: Yar Tikhiy To: freebsd-net@freebsd.org Message-ID: <20070507102147.GD13200@comp.chem.msu.su> References: <20070502115118.GG51428@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070502115118.GG51428@comp.chem.msu.su> User-Agent: Mutt/1.5.9i Subject: Re: Anybody running VLANs over tl(4) or nve(4)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2007 10:42:40 -0000 On Wed, May 02, 2007 at 03:51:18PM +0400, Yar Tikhiy wrote: > Hi folks, > > There two network interface drivers that have uncertain VLAN_MTU > support status, namely nve(4) and tl(4). The nve(4) driver has a > sign of unfinished VLAN_MTU support in it as it forgets to set the > respective bit in if_capenable; and tl(4) was told to support long > frames, but its driver doesn't indicate that capability at all. > > Therefore I'd appreciate reports of successfully running VLANs over > nve(4) or tl(4) with an MTU of 1500 bytes on the vlan(4) interfaces. > > Attached are trivial patches that add correct and complete indication > of VLAN_MTU support to the two drivers. [...] Status report: nve(4) can handle long frames (thanks to Pyun YongHyeon for testing it), so now the driver sets the respective bit in if_capenable. tl(4) remains a grey area. If somebody needs to run VLANs over tl(4) and makes sure it can handle long frames in default mode (at least rumours say so), I'll be glad to reflect that capability in the driver. -- Yar From owner-freebsd-net@FreeBSD.ORG Mon May 7 11:08: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 1669716A47E for ; Mon, 7 May 2007 11:08:39 +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 E1B3C13C459 for ; Mon, 7 May 2007 11:08:38 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l47B8bAa078722 for ; Mon, 7 May 2007 11:08:37 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l47B8aH7078718 for freebsd-net@FreeBSD.org; Mon, 7 May 2007 11:08:36 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 May 2007 11:08:36 GMT Message-Id: <200705071108.l47B8aH7078718@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2007 11:08:39 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue o kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/95665 net [if_tun] "ping: sendto: No buffer space available" wit 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/108197 net [ipv6] IPv6-related crash if if_delmulti o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/108670 net [tcp] TCP connection ETIMEDOUT 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 11 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/110720 net [net] [patch] support for interface descriptions o kern/112471 net [netinet] [patch] sys/netinet/udp_usrreq.c modifies re 12 problems total. From owner-freebsd-net@FreeBSD.ORG Mon May 7 13:01: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 B1A7016A402 for ; Mon, 7 May 2007 13:01:14 +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 6AFC313C46E for ; Mon, 7 May 2007 13:01:14 +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 01AB71B10EE9; Mon, 7 May 2007 15:01:13 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id F1DBB1B10EE7; Mon, 7 May 2007 15:01:12 +0200 (CEST) Message-ID: <463F2318.4070702@sun-fish.com> Date: Mon, 07 May 2007 16:01:12 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.0 (X11/20070425) MIME-Version: 1.0 To: Jack Vogel References: <462E3B4A.5030307@sun-fish.com> <2a41acea0704241103r59a1fa8di7e7747e191eea787@mail.gmail.com> <462F0CBF.6020507@sun-fish.com> <2a41acea0704250936l46ed31a3w930ac8fba04df810@mail.gmail.com> <2a41acea0705041349o7bce9e1eh63ef1a036f80d1b6@mail.gmail.com> In-Reply-To: <2a41acea0705041349o7bce9e1eh63ef1a036f80d1b6@mail.gmail.com> 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: 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: Mon, 07 May 2007 13:01:14 -0000 Hi again, Jack Vogel wrote: > > The new driver I just checked into CURRENT has this fix, I hope its > going to be in the May snapshot, Stefan, can you try CURRENT to > see if it solves your problem? > > Jack I have problems with loading if_em as module on 7.0-current from today: link_elf: symbol e1000_init_function_pointers_82575 undefined so I compiled in the kernel, and it works, but nothing changed about my problem - it still refuses to stay on 1000baseTX for more then 2 seconds and auto-negotiate to 100baseTX. em0: port 0x2000-0x201f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at device 25.0 on pci0 em0: Ethernet address: 00:0f:fe:4e:78:16 em0: [FILTER] I'm ready to test any new patches :) -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-net@FreeBSD.ORG Mon May 7 15:04:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA04016A406 for ; Mon, 7 May 2007 15:04:53 +0000 (UTC) (envelope-from mehul_freebsd@yahoo.com) Received: from n7.bullet.re3.yahoo.com (n7.bullet.re3.yahoo.com [68.142.237.92]) by mx1.freebsd.org (Postfix) with SMTP id 87C3D13C487 for ; Mon, 7 May 2007 15:04:53 +0000 (UTC) (envelope-from mehul_freebsd@yahoo.com) Received: from [68.142.237.88] by n7.bullet.re3.yahoo.com with NNFMP; 07 May 2007 14:52:33 -0000 Received: from [66.196.101.131] by t4.bullet.re3.yahoo.com with NNFMP; 07 May 2007 14:52:33 -0000 Received: from [127.0.0.1] by rrr2.mail.re1.yahoo.com with NNFMP; 07 May 2007 14:52:33 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 200085.86722.bm@rrr2.mail.re1.yahoo.com Received: (qmail 30298 invoked by uid 60001); 7 May 2007 14:52:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=3oGJqhPQpygiDaMYjH+NlEe9SuF1iG81dma1xNI0e5h+cb6/crUig5+7Mt7cQUC6Ql7nU7MveyKFHA/VIqP2kSSpzpNUQeCi+Khk7ZFCK/4dVmMXwD232J2jWASc3UMetKVlep3R03ZlVexiks9lJVLlqMnKVs2CrcJByymeXaQ=; X-YMail-OSG: SoyYWiIVM1nZrtAhX12uKdZfIjVhytV53RgZzXISIip.XAt11ZKQXI2lTnBJeHJnjzq8cmbrIa.FFcKFtXIpRN0vI7yBbvqLAHFPKT86Xp_5Ly7aQlUVbC6mdV.gFUHS Received: from [203.92.57.132] by web63604.mail.re1.yahoo.com via HTTP; Mon, 07 May 2007 07:52:32 PDT Date: Mon, 7 May 2007 07:52:32 -0700 (PDT) From: Mehul Vora To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-15606975-1178549552=:30264" Content-Transfer-Encoding: 8bit Message-ID: <93263.30264.qm@web63604.mail.re1.yahoo.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with "rt_check" routine. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 May 2007 15:04:53 -0000 --0-15606975-1178549552=:30264 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, Current implementation (Version 6.2) of rt_check() routine defined in route.c is not completely MPSAFE. I found an issue when i started routing with "directisr" enabled. For the first rcvd packet this function initializes rt_gateway of the passed rt_entry. This is done by calling "rtalloc1" routine. But "rt_check" function doesnt hold any lock while calling this function. So incase if we have multiple instances of "ip_input - netisr" running than more than one thread can call this routine which may lead to some corruption, in my case it leads to a dead lock. Problem doesn't happen if before sending heavy traffic a single packet of same kind is sent. But if initially itself heavy traffic is sent than this happens immediately. I have fixed this and it works well after it. Workaround patch for this issue is attached here with. Probably we need to define a macro in route.h for the hardcoded values in the patch. Can any one confirm this ? Thanks, Mehul. --------------------------------- Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. --0-15606975-1178549552=:30264 Content-Type: text/plain; name="rt_check.patch.txt" Content-Description: 206142780-rt_check.patch.txt Content-Disposition: inline; filename="rt_check.patch.txt" 1260a1261 > try_again: 1280a1282,1289 > > if(rt0->rt_flags & 0x80000000U){ > /*This rt is under process...*/ > RT_UNLOCK(rt); > RT_UNLOCK(rt0); > goto try_again; > } > 1281a1291 > rt0->rt_flags |= 0x80000000U; 1288a1299 > rt0->rt_flags &= (~0x80000000U); --0-15606975-1178549552=:30264-- From owner-freebsd-net@FreeBSD.ORG Tue May 8 09:47:26 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16F6716A412 for ; Tue, 8 May 2007 09:47:26 +0000 (UTC) (envelope-from suvashrestha@wlink.com.np) Received: from smtp5.wlink.com.np (smtp5.wlink.com.np [202.79.32.52]) by mx1.freebsd.org (Postfix) with SMTP id 220F013C44C for ; Tue, 8 May 2007 09:47:14 +0000 (UTC) (envelope-from suvashrestha@wlink.com.np) Received: (qmail 92724 invoked from network); 8 May 2007 09:20:29 -0000 Received: from unknown (HELO smtp1.wlink.com.np) (202.79.32.76) by 0 with SMTP; 8 May 2007 09:20:29 -0000 Received: (qmail 90213 invoked by uid 98); 8 May 2007 09:20:29 -0000 Received: from 202.79.32.67 by smtp1.wlink.com.np (envelope-from , uid 1009) with qmail-scanner-1.25 (clamdscan: 0.88.4/2205. Clear:RC:1(202.79.32.67):. Processed in 0.037815 secs); 08 May 2007 09:20:29 -0000 X-Qmail-Scanner-Mail-From: suvashrestha@wlink.com.np via smtp1.wlink.com.np X-Qmail-Scanner: 1.25 (Clear:RC:1(202.79.32.67):. Processed in 0.037815 secs) Received: from [202.79.32.67] (HELO webmail.wlink.com.np) by smtp1.wlink.com.np (qmail-smtpd) with SMTP; 08 May 2007 09:20:29 -0000 (Tue, 08 May 2007 15:05:29 +0545) Received: from 202.79.36.118 (auth. user suvashrestha@pop3.wlink.com.np) by webmail.wlink.com.np with HTTP; Tue, 08 May 2007 14:20:27 +0500 To: freebsd-net@freebsd.org Date: Tue, 08 May 2007 14:20:27 +0500 X-Mailer: IlohaMail/0.8.14 (On: webmail.wlink.com.np) Message-ID: In-Reply-To: From: Bounce-To: Errors-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Check-By: smtp1.wlink.com.np Spam: No ; -0.8 / 7.0 X-Spam-Status-WL: No, hits=-0.8 required=7.0 Subject: bridge query X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 May 2007 09:47:26 -0000 hello... i am using freebox 5.4 as a bridge using dummynet. My NIC can support traffic upto 10Mbit/s (10,000 Kbit/s); and it does support such traffic when no delay and plr ( packet loss ratio) are enabled. When I add delay of 250ms and plr of 0.05 (5%), the packet transfer falls to 80Kbit/s. Is this expected behaviour or is there a bug?? Thanks suva From owner-freebsd-net@FreeBSD.ORG Tue May 8 11:22: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 CDE1816A400 for ; Tue, 8 May 2007 11:22:17 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 52F8013C45B for ; Tue, 8 May 2007 11:22:17 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l48BMF6G001425; Tue, 8 May 2007 21:22:15 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l48BMFGr001424; Tue, 8 May 2007 21:22:15 +1000 (EST) (envelope-from peter) Date: Tue, 8 May 2007 21:22:15 +1000 From: Peter Jeremy To: suvashrestha@wlink.com.np Message-ID: <20070508112215.GF838@turion.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y5rl02BVI9TCfPar" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-net@freebsd.org Subject: Re: bridge query X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 May 2007 11:22:17 -0000 --Y5rl02BVI9TCfPar Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-May-08 14:20:27 +0500, suvashrestha@wlink.com.np wrote: >i am using freebox 5.4 as a bridge using dummynet. =2E.. >When I add delay of 250ms and plr of 0.05 (5%), the packet transfer falls >to 80Kbit/s. How are you measuring packet transfer (single TCP socket, multiple TCP sockets or UDP) and what were you expecting? For a TCP connection, the window size needs to be able to handle at least 1 RTT (0.5 second in this case) of data. This translates to a total of 5Mb (~640KB) outstanding data to get 10Mbps throughput. With only a single cnnection, you would need a 640KB window size - which is far larger (an order of magnitude or so) than typical. TCP is also designed to work on a mostly lossless link. I am not sure how much a 5% packet loss will affect it but I would expect it to be significant. I'm not sure how to optimise throughput in this situation. --=20 Peter Jeremy --Y5rl02BVI9TCfPar Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGQF1n/opHv/APuIcRAvewAJsHDb324nYSB4HNqgpPJ8t2lk2YRwCglPhf gMDoyTTeHt6/jPeHtDb7CSs= =Zmpu -----END PGP SIGNATURE----- --Y5rl02BVI9TCfPar-- From owner-freebsd-net@FreeBSD.ORG Tue May 8 22:31:46 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 5FBEE16A408; Tue, 8 May 2007 22:31:46 +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 5106F13C480; Tue, 8 May 2007 22:31:46 +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 l48MVkmN021512; Tue, 8 May 2007 22:31:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l48MVkpC021508; Tue, 8 May 2007 22:31:46 GMT (envelope-from linimon) Date: Tue, 8 May 2007 22:31:46 GMT From: Mark Linimon Message-Id: <200705082231.l48MVkpC021508@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/81147: [net] [patch] em0 reinitialization while adding aliases to interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2007 22:31:46 -0000 Old Synopsis: [em] [patch] em0 reinitialization while adding aliases to interface New Synopsis: [net] [patch] em0 reinitialization while adding aliases to interface Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue May 8 22:30:12 UTC 2007 Responsible-Changed-Why: I'm going to reclassify this one. The original submitter did indeed submit a patch, which was kind of hacky; I got not response when asking for feedback. However, a later correspondant noted that this was more of a general problem, and submitted a patch against sys/net/if_ethersubr.c. Since that patch may need to be evaluated, I'll reassign this to -net. http://www.freebsd.org/cgi/query-pr.cgi?pr=81147 From owner-freebsd-net@FreeBSD.ORG Thu May 10 18:15: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 B0AC616A403 for ; Thu, 10 May 2007 18:15:11 +0000 (UTC) (envelope-from cjharrer@comcast.net) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.77.83]) by mx1.freebsd.org (Postfix) with ESMTP id 7478713C448 for ; Thu, 10 May 2007 18:15:11 +0000 (UTC) (envelope-from cjharrer@comcast.net) Received: from record (h-68-164-177-211.phlapafg.covad.net[68.164.177.211]) by comcast.net (sccrmhc13) with SMTP id <20070510180231013009hehre>; Thu, 10 May 2007 18:02:31 +0000 From: "Chris Harrer" To: Date: Thu, 10 May 2007 14:02:33 -0400 Message-ID: <001001c7932d$6311f0c0$ac01020a@record> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceTLWJH8/C6OVoWQ4ShHkXil40HBA== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RELENG 6.2 Slow Start Question X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 10 May 2007 18:15:11 -0000 Hello All, This is my first time posting a message to this list, so please excuse me if this is not an appropriate message for this list (if it is inappropriate, could you please direct me to a more appropriate place?). I've been looking at some slow start code in the FreeBSD 6.2 RELENG, in particular the following block that increments the CWND in Ack processing: 2128 /* 2129 * When new data is acked, open the congestion window. 2130 * If the window gives us less than ssthresh packets 2131 * in flight, open exponentially (maxseg per packet). 2132 * Otherwise open linearly: maxseg per window 2133 * (maxseg^2 / cwnd per packet). 2134 */ 2135 if ((!tcp_do_newreno && !tp ->sack_enable) || 2136 !IN_FASTRECOVERY (tp )) { 2137 register u_int cw = tp ->snd_cwnd; 2138 register u_int incr = tp ->t_maxseg; 2139 if (cw > tp ->snd_ssthresh) 2140 incr = incr * incr / cw; 2141 tp ->snd_cwnd = min (cw+incr, TCP_MAXWIN < ->snd_scale); 2142 } Assume this connection is just opened, CWND has an initial value of 2920 and snd_ssthresh is sufficiently big (for this example, use 17500). A write is given to TCP of length 8760 bytes. Tcp_output determines it can send the first 2920 bytes of that write based on snd_cwnd and does so. A single ACK is received that ACK's all 2920 bytes of data, in looking at the code above, tp->snd_cwnd would get set to 4380 (assuming a t_maxseg of 1460). This is in contrast to the description in Steven's Volume 1 regarding slow start increasing the window exponentially, as well as the description in RFC 2581 whereby I would expect tp->snd_cwnd to be set to 5840. After processing the ACK, tcp_output would send 3 new full segments as opposed to 4 (i.e., all of the remaining data) which I would expect. This seems obviously wrong to me, but it's code that always been there. I'd like to understand where my analysis goes wrong or why it's acceptable for the call to tcp_output (after the acking of the first 2920 bytes of data) to only send 3 packets as opposed to completing the transmission of the write in two calls to tcp_output. Thanks very much. Chris From owner-freebsd-net@FreeBSD.ORG Thu May 10 23:35: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 DDE1C16A400; Thu, 10 May 2007 23:35:46 +0000 (UTC) (envelope-from bushman@freebsd.org) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.freebsd.org (Postfix) with ESMTP id CF20A13C45A; Thu, 10 May 2007 23:35:45 +0000 (UTC) (envelope-from bushman@freebsd.org) Received: from [83.188.106.197] (m83-188-106-197.cust.tele2.ru [83.188.106.197]) (authenticated bits=0) by mail.r61.net (8.14.1/8.14.1) with ESMTP id l4AN3mv7031228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 11 May 2007 03:03:55 +0400 (MSD) (envelope-from bushman@freebsd.org) Message-ID: <4643A4CB.4070801@freebsd.org> Date: Fri, 11 May 2007 03:03:39 +0400 From: Michael Bushkov User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: Brooks Davis , freebsd-arch@freebsd.org Subject: [PATCH] getipnodebyXXX() via gethostbyXXX() 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, 10 May 2007 23:35:47 -0000 Hi, During my Summer Of Code 2006 work I've done a lot of refactoring in libc's nsswitch, which was basically needed to separate libc and nsswitch modules. One part of that refactoring was reimplementation of getipnodebyXXX() family of functions through gethostbyXXX() family of functions. Actually both of these groups of functions had a lot of duplicated (or very similar) code, so such reimplementation seems to be quite logic to me. The patch is here: http://rsu.ru/~bushman/name6.patch It would be great to have it tested (maybe with nsswitch regression tests - /tools/regresion/lib/libc/nss) and to hear comments about it. -- With best regards, Michael Bushkov Southern Federal University From owner-freebsd-net@FreeBSD.ORG Fri May 11 05:23: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 5D6A116A400 for ; Fri, 11 May 2007 05:23:03 +0000 (UTC) (envelope-from suvashrestha@wlink.com.np) Received: from smtp5.wlink.com.np (smtp5.wlink.com.np [202.79.32.52]) by mx1.freebsd.org (Postfix) with SMTP id 44DD213C44B for ; Fri, 11 May 2007 05:23:00 +0000 (UTC) (envelope-from suvashrestha@wlink.com.np) Received: (qmail 98986 invoked from network); 11 May 2007 05:22:47 -0000 Received: from unknown (HELO smtp1.wlink.com.np) (202.79.32.76) by 0 with SMTP; 11 May 2007 05:22:47 -0000 Received: (qmail 81206 invoked by uid 98); 11 May 2007 05:22:47 -0000 Received: from 202.79.32.67 by smtp1.wlink.com.np (envelope-from , uid 1009) with qmail-scanner-1.25 (clamdscan: 0.88.4/2205. Clear:RC:1(202.79.32.67):. Processed in 0.58594 secs); 11 May 2007 05:22:47 -0000 X-Qmail-Scanner-Mail-From: suvashrestha@wlink.com.np via smtp1.wlink.com.np X-Qmail-Scanner: 1.25 (Clear:RC:1(202.79.32.67):. Processed in 0.58594 secs) Received: from [202.79.32.67] (HELO webmail.wlink.com.np) by smtp1.wlink.com.np (qmail-smtpd) with SMTP; 11 May 2007 05:22:45 -0000 (Fri, 11 May 2007 11:07:45 +0545) Received: from 202.79.36.118 (auth. user suvashrestha@pop3.wlink.com.np) by webmail.wlink.com.np with HTTP; Fri, 11 May 2007 10:22:43 +0500 To: freebsd-net@freebsd.org Date: Fri, 11 May 2007 10:22:43 +0500 X-Mailer: IlohaMail/0.8.14 (On: webmail.wlink.com.np) Message-ID: In-Reply-To: From: Bounce-To: Errors-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Check-By: smtp1.wlink.com.np Spam: No ; -0.8 / 7.0 X-Spam-Status-WL: No, hits=-0.8 required=7.0 Subject: bridge query X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 May 2007 05:23:03 -0000 Hello.... I am using TCP sockets to measure packet transfer. And I am also not looking to optimise the link. I just want to know if this is the usual behaviour of the freeBSD TCP or bridge when we apply delay and packet loss. The throughtput falls from around 8 Mbps (8000 Kbps) to just 80 Kbps. This is very significant. Thanks suva How are you measuring packet transfer (single TCP socket, multiple TCP sockets or UDP) and what were you expecting? For a TCP connection, the window size needs to be able to handle at least 1 RTT (0.5 second in this case) of data. This translates to a total of 5Mb (~640KB) outstanding data to get 10Mbps throughput. With only a single cnnection, you would need a 640KB window size - which is far larger (an order of magnitude or so) than typical. TCP is also designed to work on a mostly lossless link. I am not sure how much a 5% packet loss will affect it but I would expect it to be significant. I'm not sure how to optimise throughput in this situation. Peter Jeremy From owner-freebsd-net@FreeBSD.ORG Fri May 11 09:39: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 8528416A404 for ; Fri, 11 May 2007 09:39:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 13C5B13C4C3 for ; Fri, 11 May 2007 09:39:11 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l4B9dAUH001645; Fri, 11 May 2007 19:39:10 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l4B9dA6B001644; Fri, 11 May 2007 19:39:10 +1000 (EST) (envelope-from peter) Date: Fri, 11 May 2007 19:39:10 +1000 From: Peter Jeremy To: suvashrestha@wlink.com.np Message-ID: <20070511093910.GG826@turion.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+nBD6E3TurpgldQp" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-net@freebsd.org Subject: Re: bridge query X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 May 2007 09:39:12 -0000 --+nBD6E3TurpgldQp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-May-11 10:22:43 +0500, suvashrestha@wlink.com.np wrote: >I am using TCP sockets to measure packet transfer. And I am also not >looking to optimise the link. I just want to know if this is the usual >behaviour of the freeBSD TCP or bridge when we apply delay and packet >loss. This is nothing to do with FreeBSD and is expected behaviour for TCP. The TCP sender has to buffer data until the receiver acknowledges it. The default buffer is 64KB. With a 250msec delay in each direction, this gives you a theoretical maximum thruput of 128KBps. >The throughtput falls from around 8 Mbps (8000 Kbps) to just 80 Kbps. >This is very significant. Increasing PLR above 0 will reduce the theoretical throughput: A lost ACK will block the sender until the next ACK is received. A lost data packet means the receiver won't ACK it. SACK makes things slightly better because only the lost packet will be re-transmitted but the very long RTT will still have a major impact on throughput. --=20 Peter Jeremy --+nBD6E3TurpgldQp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGRDm+/opHv/APuIcRAlAHAKCPG+LksfR2KDcTz2sANd+lu6wHXgCfQc9L copgOlHUOOTFE0bKTq/ucT4= =lUa5 -----END PGP SIGNATURE----- --+nBD6E3TurpgldQp-- From owner-freebsd-net@FreeBSD.ORG Fri May 11 15:07:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6872D16A404 for ; Fri, 11 May 2007 15:07:53 +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 DD3DE13C483 for ; Fri, 11 May 2007 15:07:52 +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 94F8C79E211 for ; Fri, 11 May 2007 10:07:52 -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 33385-02 for ; Fri, 11 May 2007 15:07:52 +0000 (UTC) Received: from hole.shrew.net (66-90-185-31.dyn.grandenetworks.net [66.90.185.31]) by shrew.net (Postfix) with ESMTP id 101F779E204 for ; Fri, 11 May 2007 10:07:51 -0500 (CDT) Received: from hole.shrew.net (localhost.shrew.net [127.0.0.1]) by hole.shrew.net (8.13.6/8.13.6) with ESMTP id l4B8BTjY031339 for ; Fri, 11 May 2007 08:11:29 GMT (envelope-from mgrooms@shrew.net) Received: (from www@localhost) by hole.shrew.net (8.13.6/8.13.6/Submit) id l4B8BTL6031338; Fri, 11 May 2007 08:11:29 GMT (envelope-from mgrooms@shrew.net) Date: Fri, 11 May 2007 08:11:29 GMT Message-Id: <200705110811.l4B8BTL6031338@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; Fri, 11 May 2007 03:11:29 -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) 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: NAT Traversal Patches ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 15:07:53 -0000 All, I understand that FreeBSD is a volunteer project, but does anyone have any information regarding the status of the IPsec NAT Traversal patches and their inclusion with FeeBSD? I have seen them floating around this list for a few years now. At one point, there was an objection that concerned a possible legal issue related to patents. This can't be too much of a road block as Linux, OpenBSD and NetBSD all include support for NATT in official stable kernel sources. Fedora Core 6 even has the feature enabled by default in the generic kernel. Another objection I have seen was related to the patch only offering support for the KAME stack. But the most recent patch set also offers support for the Fast IPsec stack as well. Is the patch lacking sponsorship by a FreeBSD developer sponsor since the author does not have commit access? Maybe a developer looking at the patch is just short on time at the moment? If so, is there another developer that could maybe help out? Is there a technical reason why the patches have not been committed? If so, I don't think the author is aware so a little communication is required? Lastly, is there anything the community can do to help out? Maybe donating to a FreeBSD Foundation project that sponsors IPsec related work? Thanks, -Matthew From owner-freebsd-net@FreeBSD.ORG Fri May 11 22:02: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 B328816A4CC for ; Fri, 11 May 2007 22:02:00 +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 5D54113C459 for ; Fri, 11 May 2007 22:02:00 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id s1so1183952nze for ; Fri, 11 May 2007 15:01:59 -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=pHJEqZlLc2dvxxiR48UKR4UG5lMokpKaUCgKpccFTm4Lh42XI3PboiW0Qwcbhpf+WxsATCcYKJEb4Qh2lrbxg1P9IAPPR28X87fiIVLRTlme7buJzkwZMJPOAUY+RxtZ3+555OLZOpZmVbAOOOypNUd8OuPynv/NpJhEc1z3inE= 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=qPd7lKPeV52ta9M596qUIIWWfOm64yXVeC3lzEoLTtvRtY3W/7/Fn8whjicQPmcKVRnA19tywf2ZoclVCxC5QJg6aCg3ly0jI/HmDE+pma8KigKUJxr2ajXV/5nUjjKyZIGyMbz381oYO4Al9hUaoonT2b4DCUQ1P3xKE6xUFhI= Received: by 10.114.205.1 with SMTP id c1mr19462wag.1178920918930; Fri, 11 May 2007 15:01:58 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Fri, 11 May 2007 15:01:58 -0700 (PDT) Message-ID: <2a41acea0705111501h41170824qddbf8fee9d9dacc7@mail.gmail.com> Date: Fri, 11 May 2007 15:01:58 -0700 From: "Jack Vogel" To: stefan.lambrev@sun-fish.com In-Reply-To: <463F2318.4070702@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> <2a41acea0704241103r59a1fa8di7e7747e191eea787@mail.gmail.com> <462F0CBF.6020507@sun-fish.com> <2a41acea0704250936l46ed31a3w930ac8fba04df810@mail.gmail.com> <2a41acea0705041349o7bce9e1eh63ef1a036f80d1b6@mail.gmail.com> <463F2318.4070702@sun-fish.com> 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: Fri, 11 May 2007 22:02:00 -0000 On 5/7/07, Stefan Lambrev wrote: > Hi again, > > Jack Vogel wrote: > > > > > The new driver I just checked into CURRENT has this fix, I hope its > > going to be in the May snapshot, Stefan, can you try CURRENT to > > see if it solves your problem? > > > > Jack > I have problems with loading if_em as module on 7.0-current from today: > > link_elf: symbol e1000_init_function_pointers_82575 undefined > > so I compiled in the kernel, and it works, but nothing changed about my > problem - it still refuses to stay on 1000baseTX for more then 2 seconds > and auto-negotiate to 100baseTX. > > em0: port > 0x2000-0x201f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at > device 25.0 on pci0 > em0: Ethernet address: 00:0f:fe:4e:78:16 > em0: [FILTER] > > I'm ready to test any new patches :) My patch made assumptions about what is causing your problem, and that may be incorrect. Our test group does not have that Broadcom adapter but they are going to get one. They had a suggestion that you can try, go into your BIOS, and then the Advanced Menu, I believe under that you will find settings for the NorthBridge, in that submenu there is settings for HECI, disable that, it is the interface to the management processor. Then boot up and test again, if it now autonegs correctly then it is the management getting in your way, on the other hand if you still see it happen then we're back to square one :) Good luck, Jack From owner-freebsd-net@FreeBSD.ORG Fri May 11 23:46: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 9AD6316A402 for ; Fri, 11 May 2007 23:46:02 +0000 (UTC) (envelope-from cjharrer@comcast.net) Received: from alnrmhc12.comcast.net (alnrmhc12.comcast.net [204.127.225.92]) by mx1.freebsd.org (Postfix) with ESMTP id 7810013C44C for ; Fri, 11 May 2007 23:46:02 +0000 (UTC) (envelope-from cjharrer@comcast.net) Received: from record (c-71-230-132-214.hsd1.pa.comcast.net[71.230.132.214]) by comcast.net (alnrmhc12) with SMTP id <20070511234601b1200f7nvje>; Fri, 11 May 2007 23:46:01 +0000 From: "Chris Harrer" To: References: <001001c7932d$6311f0c0$ac01020a@record> Date: Fri, 11 May 2007 19:46:03 -0400 Message-ID: <000001c79426$8aa95610$6602a8c0@record> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: <001001c7932d$6311f0c0$ac01020a@record> Thread-Index: AceTLWJH8/C6OVoWQ4ShHkXil40HBAA+NWog Subject: RE: RELENG 6.2 Slow Start Question X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 May 2007 23:46:02 -0000 I apologize, I didn't realize that my original message inserted the embedded links in the snippet of code I posted. Just wondering if anyone had any thoughts on my questions below, here's a cleaner listing of the code: 2128 /* 2129 * When new data is acked, open the congestion window. 2130 * If the window gives us less than ssthresh packets 2131 * in flight, open exponentially (maxseg per packet). 2132 * Otherwise open linearly: maxseg per window 2133 * (maxseg^2 / cwnd per packet). 2134 */ 2135 if ((!tcp_do_newreno && !tp->sack_enable) || 2136 !IN_FASTRECOVERY(tp)) { 2137 register u_int cw = tp->snd_cwnd; 2138 register u_int incr = tp->t_maxseg; 2139 if (cw > tp->snd_ssthresh) 2140 incr = incr * incr / cw; 2141 tp->snd_cwnd = min(cw+incr, TCP_MAXWIN<snd_scale); 2142 } Thanks in advance. Chris -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Chris Harrer Sent: Thursday, May 10, 2007 2:03 PM To: freebsd-net@freebsd.org Subject: RELENG 6.2 Slow Start Question Hello All, This is my first time posting a message to this list, so please excuse me if this is not an appropriate message for this list (if it is inappropriate, could you please direct me to a more appropriate place?). I've been looking at some slow start code in the FreeBSD 6.2 RELENG, in particular the following block that increments the CWND in Ack processing: 2128 /* 2129 * When new data is acked, open the congestion window. 2130 * If the window gives us less than ssthresh packets 2131 * in flight, open exponentially (maxseg per packet). 2132 * Otherwise open linearly: maxseg per window 2133 * (maxseg^2 / cwnd per packet). 2134 */ 2135 if ((!tcp_do_newreno && !tp ->sack_enable) || 2136 !IN_FASTRECOVERY (tp )) { 2137 register u_int cw = tp ->snd_cwnd; 2138 register u_int incr = tp ->t_maxseg; 2139 if (cw > tp ->snd_ssthresh) 2140 incr = incr * incr / cw; 2141 tp ->snd_cwnd = min (cw+incr, TCP_MAXWIN < ->snd_scale); 2142 } Assume this connection is just opened, CWND has an initial value of 2920 and snd_ssthresh is sufficiently big (for this example, use 17500). A write is given to TCP of length 8760 bytes. Tcp_output determines it can send the first 2920 bytes of that write based on snd_cwnd and does so. A single ACK is received that ACK's all 2920 bytes of data, in looking at the code above, tp->snd_cwnd would get set to 4380 (assuming a t_maxseg of 1460). This is in contrast to the description in Steven's Volume 1 regarding slow start increasing the window exponentially, as well as the description in RFC 2581 whereby I would expect tp->snd_cwnd to be set to 5840. After processing the ACK, tcp_output would send 3 new full segments as opposed to 4 (i.e., all of the remaining data) which I would expect. This seems obviously wrong to me, but it's code that always been there. I'd like to understand where my analysis goes wrong or why it's acceptable for the call to tcp_output (after the acking of the first 2920 bytes of data) to only send 3 packets as opposed to completing the transmission of the write in two calls to tcp_output. Thanks very much. Chris _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sat May 12 05:12:22 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5875F16A400 for ; Sat, 12 May 2007 05:12:22 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9FE13C468 for ; Sat, 12 May 2007 05:12:22 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 28A4D1A3C1A; Fri, 11 May 2007 21:54:41 -0700 (PDT) Date: Fri, 11 May 2007 21:54:41 -0700 From: Alfred Perlstein To: Matthew Grooms Message-ID: <20070512045441.GI21795@elvis.mu.org> References: <200705110811.l4B8BTL6031338@hole.shrew.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705110811.l4B8BTL6031338@hole.shrew.net> User-Agent: Mutt/1.4.2.2i Cc: freebsd-net@freebsd.org Subject: Re: NAT Traversal Patches ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 05:12:22 -0000 Matthew, can you provide links to the patches and surrounding discussion. It may just be a matter of integration manpower... * Matthew Grooms [070511 08:08] wrote: > > All, > > I understand that FreeBSD is a volunteer project, but does anyone > have any information regarding the status of the IPsec NAT Traversal > patches and their inclusion with FeeBSD? I have seen them floating > around this list for a few years now. At one point, there was an > objection that concerned a possible legal issue related to patents. This > can't be too much of a road block as Linux, OpenBSD and NetBSD all > include support for NATT in official stable kernel sources. Fedora Core > 6 even has the feature enabled by default in the generic kernel. Another > objection I have seen was related to the patch only offering support for > the KAME stack. But the most recent patch set also offers support for > the Fast IPsec stack as well. > > Is the patch lacking sponsorship by a FreeBSD developer sponsor > since the author does not have commit access? Maybe a developer looking > at the patch is just short on time at the moment? If so, is there > another developer that could maybe help out? Is there a technical reason > why the patches have not been committed? If so, I don't think the > author is aware so a little communication is required? > > Lastly, is there anything the community can do to help out? Maybe > donating to a FreeBSD Foundation project that sponsors IPsec related > work? > > Thanks, > > -Matthew > _______________________________________________ > 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" -- - Alfred Perlstein From owner-freebsd-net@FreeBSD.ORG Sat May 12 06:11: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 0942F16A400; Sat, 12 May 2007 06:11:29 +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 C75E413C45B; Sat, 12 May 2007 06:11:28 +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 4648779E20E; Sat, 12 May 2007 01:11:28 -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 29468-04; Sat, 12 May 2007 06:11:27 +0000 (UTC) Received: from hole.shrew.net (66-90-185-31.dyn.grandenetworks.net [66.90.185.31]) by shrew.net (Postfix) with ESMTP id 31FDD79E203; Sat, 12 May 2007 01:11:26 -0500 (CDT) Received: from [10.22.200.21] ([10.22.200.21]) by hole.shrew.net (8.13.6/8.13.6) with ESMTP id l4BNF4hw034158; Fri, 11 May 2007 23:15:04 GMT (envelope-from mgrooms@shrew.net) Message-ID: <46455B30.5030100@shrew.net> Date: Sat, 12 May 2007 01:14:08 -0500 From: Matthew Grooms User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Alfred Perlstein References: <200705110811.l4B8BTL6031338@hole.shrew.net> <20070512045441.GI21795@elvis.mu.org> In-Reply-To: <20070512045441.GI21795@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, vanhu@free.fr Subject: Re: NAT Traversal Patches ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 06:11:29 -0000 Alfred Perlstein wrote: > Matthew, can you provide links to the patches and surrounding > discussion. It may just be a matter of integration manpower... > Here is a link to the 6.x patch set. I'm not sure where the most recent patches are for head. Yvan will probably be willing to point us in the right direction. http://ipsec-tools.sf.net/freebsd6-natt.diff As for the surrounding discussion, I haven't seen anything recently about why the changes haven't been integrated. I was hoping my post would seed a new discussion regarding this. Here is a link to a few older threads regarding patents and fast-ipsec support. http://lists.freebsd.org/mailman/htdig/freebsd-net/2005-August/007986.html http://lists.freebsd.org/mailman/htdig/freebsd-net/2006-March/010164.html > * Matthew Grooms [070511 08:08] wrote: >> All, >> >> I understand that FreeBSD is a volunteer project, but does anyone >> have any information regarding the status of the IPsec NAT Traversal >> patches and their inclusion with FeeBSD? I have seen them floating >> around this list for a few years now. At one point, there was an >> objection that concerned a possible legal issue related to patents. This >> can't be too much of a road block as Linux, OpenBSD and NetBSD all >> include support for NATT in official stable kernel sources. Fedora Core >> 6 even has the feature enabled by default in the generic kernel. Another >> objection I have seen was related to the patch only offering support for >> the KAME stack. But the most recent patch set also offers support for >> the Fast IPsec stack as well. >> >> Is the patch lacking sponsorship by a FreeBSD developer sponsor >> since the author does not have commit access? Maybe a developer looking >> at the patch is just short on time at the moment? If so, is there >> another developer that could maybe help out? Is there a technical reason >> why the patches have not been committed? If so, I don't think the >> author is aware so a little communication is required? >> >> Lastly, is there anything the community can do to help out? Maybe >> donating to a FreeBSD Foundation project that sponsors IPsec related >> work? >> >> Thanks, >> >> -Matthew >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sat May 12 16:57:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BEDF916A400 for ; Sat, 12 May 2007 16:57:53 +0000 (UTC) (envelope-from fli@FreeBSD.org) Received: from mx1.h3q.net (mx1.h3q.net [212.37.5.30]) by mx1.freebsd.org (Postfix) with ESMTP id 83F4B13C447 for ; Sat, 12 May 2007 16:57:53 +0000 (UTC) (envelope-from fli@FreeBSD.org) Received: from [192.168.1.100] (81-232-22-115-no50.tbcn.telia.com [81.232.22.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fli@shapeshifter.se) by mx1.h3q.net (Postfix) with ESMTP id 273BB78C5F; Sat, 12 May 2007 18:30:02 +0200 (CEST) Message-ID: <4645EB89.6030208@FreeBSD.org> Date: Sat, 12 May 2007 18:30:01 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: multipart/mixed; boundary="------------020804090506080608050002" Cc: jfvogel@gmail.com Subject: em_ioctl and SIOCGIFADDR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 May 2007 16:57:53 -0000 This is a multi-part message in MIME format. --------------020804090506080608050002 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi I'm getting panics when doing a SIOCGIFADDR ioctl to a em device, verified with todays current. FreeBSD 7.0-CURRENT #16: Sat May 12 15:44:05 CEST 2007 The interface only had a auto configured ipv6 address and no ipv4 address at all. Both SIOCGIFADDR and SIOCSIFADDR take a struct ifreq as an argument, so one should dereference a struct ifreq in em_ioctl and not a struct ifaddr. At least this takes care of the panic. Fredrik Lindberg --------------020804090506080608050002 Content-Type: text/plain; name="if_em.c-20070512" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_em.c-20070512" Index: if_em.c =================================================================== RCS file: /home/ncvs/src/sys/dev/em/if_em.c,v retrieving revision 1.175 diff -u -u -r1.175 if_em.c --- if_em.c 11 May 2007 21:36:08 -0000 1.175 +++ if_em.c 12 May 2007 16:19:14 -0000 @@ -974,7 +974,7 @@ switch (command) { case SIOCSIFADDR: case SIOCGIFADDR: - if (ifa->ifa_addr->sa_family == AF_INET) { + if (ifr->ifr_addr.sa_family == AF_INET) { /* * XXX * Since resetting hardware takes a very long time --------------020804090506080608050002-- From owner-freebsd-net@FreeBSD.ORG Sat May 12 19:48:14 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 7B37E16A403; Sat, 12 May 2007 19:48:14 +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 55A1013C45A; Sat, 12 May 2007 19:48:14 +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 l4CJmDUw069802; Sat, 12 May 2007 19:48:14 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4CJmDH7069798; Sat, 12 May 2007 19:48:13 GMT (envelope-from linimon) Date: Sat, 12 May 2007 19:48:13 GMT From: Mark Linimon Message-Id: <200705121948.l4CJmDH7069798@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/112612: Traffic via additional lo(4) interface shows up on lo0 in bpf(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 19:48:14 -0000 Synopsis: Traffic via additional lo(4) interface shows up on lo0 in bpf(4) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 12 19:48:01 UTC 2007 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=112612 From owner-freebsd-net@FreeBSD.ORG Sat May 12 19:55:50 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B12C16A403 for ; Sat, 12 May 2007 19:55:50 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id 5BE3213C487 for ; Sat, 12 May 2007 19:55:49 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 98562 invoked from network); 13 May 2007 00:01:47 +0400 Received: from unknown (HELO localhost) (88.212.205.2) by mail.sub.ru with SMTP; 13 May 2007 00:01:47 +0400 X-Virus-Scanned: by amavisd-new at mail.sub.ru Received: from unknown ([88.212.205.2]) by localhost (mail-new.sub.ru [88.212.205.2]) (amavisd-new, port 10024) with SMTP id TQ0-7iJAwf+k; Sun, 13 May 2007 00:01:44 +0400 (MSD) Received: from unknown (HELO ?89.222.147.9?) (tarkhil%sub.ru@89.222.147.9) by techno.sub.ru with SMTP; 12 May 2007 20:01:43 -0000 Message-ID: <46461BB6.7050101@webmail.sub.ru> Date: Sat, 12 May 2007 23:55:34 +0400 From: Alex Povolotsky User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: freebsd-net@FreeBSD.org, freebsd-mobile@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Asus WL-167g not working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 19:55:50 -0000 Hello! I'm trying to use ASUS WL-167g, with ural driver compiled into kernel, but system does not recognize it. from /var/log/messages May 12 23:47:15 tarkhil kernel: ugen1: Ralink 802.11 bg WLAN, rev 2.00/0.01, addr 2 from usbdevs -v port 5 addr 2: high speed, power 300 mA, config 1, 802.11 bg WLAN(0x1723), Ralink(0x0b05), rev 0.01 System is FreeBSD 6.2-RELEASEp3. Any help is appreciated. Alex. From owner-freebsd-net@FreeBSD.ORG Sat May 12 21:28:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A13CF16A408 for ; Sat, 12 May 2007 21:28:57 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 66A7D13C458 for ; Sat, 12 May 2007 21:28:57 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7cf3.q.ppp-pool.de [89.53.124.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 08943128847; Sat, 12 May 2007 23:00:03 +0200 (CEST) Received: from cesar.sz.vwsoft.com (unknown [192.168.18.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 5BB713F9E3; Sat, 12 May 2007 22:59:37 +0200 (CEST) Message-ID: <46462AB8.3070500@vwsoft.com> Date: Sat, 12 May 2007 22:59:36 +0200 From: Volker User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Alex Povolotsky References: <46461BB6.7050101@webmail.sub.ru> In-Reply-To: <46461BB6.7050101@webmail.sub.ru> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-net@FreeBSD.org, freebsd-mobile@freebsd.org Subject: Re: Asus WL-167g not working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 21:28:57 -0000 On 05/12/07 21:55, Alex Povolotsky wrote: > Hello! > > I'm trying to use ASUS WL-167g, with ural driver compiled into kernel, > but system does not recognize it. > > from /var/log/messages > > May 12 23:47:15 tarkhil kernel: ugen1: Ralink 802.11 bg WLAN, rev > 2.00/0.01, addr 2 > > from usbdevs -v > > port 5 addr 2: high speed, power 300 mA, config 1, 802.11 bg > WLAN(0x1723), Ralink(0x0b05), rev 0.01 if_ural.c does not know about a usb ID 1723 (only Asus IDs 1706 and 1705 are known). You need to patch it. HTH Volker From owner-freebsd-net@FreeBSD.ORG Sat May 12 21:41: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 E3FFE16A400 for ; Sat, 12 May 2007 21:41:35 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id 39CDE13C448 for ; Sat, 12 May 2007 21:41:34 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 43554 invoked from network); 13 May 2007 01:47:33 +0400 Received: from unknown (HELO localhost) (88.212.205.2) by mail.sub.ru with SMTP; 13 May 2007 01:47:33 +0400 X-Virus-Scanned: by amavisd-new at mail.sub.ru Received: from unknown ([88.212.205.2]) by localhost (mail-new.sub.ru [88.212.205.2]) (amavisd-new, port 10024) with SMTP id 9FlQUw-n9eq4; Sun, 13 May 2007 01:47:29 +0400 (MSD) Received: from unknown (HELO ?89.222.147.9?) (tarkhil%sub.ru@89.222.147.9) by techno.sub.ru with SMTP; 12 May 2007 21:47:29 -0000 Message-ID: <46463480.6000109@webmail.sub.ru> Date: Sun, 13 May 2007 01:41:20 +0400 From: Alex Povolotsky User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: Volker References: <46461BB6.7050101@webmail.sub.ru> <46462AB8.3070500@vwsoft.com> In-Reply-To: <46462AB8.3070500@vwsoft.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-mobile@freebsd.org Subject: Re: Asus WL-167g not working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 21:41:36 -0000 Volker wrote: > On 05/12/07 21:55, Alex Povolotsky wrote: > >> Hello! >> >> I'm trying to use ASUS WL-167g, with ural driver compiled into kernel, >> but system does not recognize it. >> >> from /var/log/messages >> >> May 12 23:47:15 tarkhil kernel: ugen1: Ralink 802.11 bg WLAN, rev >> 2.00/0.01, addr 2 >> >> from usbdevs -v >> >> port 5 addr 2: high speed, power 300 mA, config 1, 802.11 bg >> WLAN(0x1723), Ralink(0x0b05), rev 0.01 >> > > if_ural.c does not know about a usb ID 1723 (only Asus IDs 1706 and > 1705 are known). You need to patch it. > Partially helped. Now it can be detected, but cannot scan. May 13 01:37:03 tarkhil kernel: ural0: Ralink 802.11 bg WLAN, rev 2.00/0.01, addr 2 May 13 01:37:04 tarkhil kernel: ural0: MAC/BBP RT2570 (rev 0x00), RF unknown May 13 01:37:04 tarkhil kernel: ural0: Ethernet address: 00:18:f3:e5:b8:dd May 13 01:37:04 tarkhil kernel: ural0: if_start running deferred for Giant Here I do ifconfig ural0 up scan May 13 01:37:08 tarkhil kernel: ural0: timeout waiting for BBP/RF to wakeup And no scan result. Alex. > HTH > > Volker > > _______________________________________________ > 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" > >