From owner-freebsd-net@FreeBSD.ORG Sun Mar 29 11:44:53 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5DCD106566C; Sun, 29 Mar 2009 11:44:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5768FC08; Sun, 29 Mar 2009 11:44:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2TBirdr031036; Sun, 29 Mar 2009 11:44:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2TBir2E031032; Sun, 29 Mar 2009 11:44:53 GMT (envelope-from linimon) Date: Sun, 29 Mar 2009 11:44:53 GMT Message-Id: <200903291144.n2TBir2E031032@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/133178: [lagg] [wlan] lagg with wlan laggpport does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2009 11:44:54 -0000 Old Synopsis: lagg with wlan laggpport does not work New Synopsis: [lagg] [wlan] lagg with wlan laggpport does not work Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 29 11:44:29 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=133178 From owner-freebsd-net@FreeBSD.ORG Sun Mar 29 12:09:13 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7030106564A for ; Sun, 29 Mar 2009 12:09:13 +0000 (UTC) (envelope-from c.r.n.a@wanadoo.fr) Received: from smtp2c.orange.fr (smtp2c.orange.fr [80.12.242.154]) by mx1.freebsd.org (Postfix) with ESMTP id A83FC8FC0A for ; Sun, 29 Mar 2009 12:09:13 +0000 (UTC) (envelope-from c.r.n.a@wanadoo.fr) Received: from smtp20.orange.fr (mwinf2027 [172.22.130.127]) by mwinf2c15.orange.fr (SMTP Server) with ESMTP id 0720A1C02479 for ; Sun, 29 Mar 2009 12:06:36 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2027.orange.fr (SMTP Server) with ESMTP id 717A32000041 for ; Sun, 29 Mar 2009 12:06:34 +0200 (CEST) Received: from [192.168.1.96] (ABordeaux-157-1-61-228.w90-30.abo.wanadoo.fr [90.30.228.228]) by mwinf2027.orange.fr (SMTP Server) with ESMTP id 371B42000040 for ; Sun, 29 Mar 2009 12:06:34 +0200 (CEST) X-ME-UUID: 20090329100634225.371B42000040@mwinf2027.orange.fr Message-ID: <49CF47BE.6030505@wanadoo.fr> Date: Sun, 29 Mar 2009 12:04:46 +0200 From: Nicolas User-Agent: Thunderbird 2.0.0.19 (X11/20090311) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: 49CE52AA.6060500@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: iwn(4): Porting Intel 5100/5300 support from OpenBSD? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Mar 2009 12:09:14 -0000 Hi, I'm also interested. If you have a patch, I can test it, I have a 5100 card. Thanks in advance, Niko. From owner-freebsd-net@FreeBSD.ORG Sun Mar 29 13:21:57 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FEAE106564A for ; Sun, 29 Mar 2009 13:21:57 +0000 (UTC) (envelope-from fjo-lists@ogris.de) Received: from ns1.ogris.net (ns1.ogris.net [212.62.68.23]) by mx1.freebsd.org (Postfix) with ESMTP id 2461A8FC0C for ; Sun, 29 Mar 2009 13:21:57 +0000 (UTC) (envelope-from fjo-lists@ogris.de) Received: from [192.168.0.10] (p5487543E.dip.t-dialin.net [84.135.84.62]) by ns1.ogris.net (Postfix) with ESMTPA id D0F211209FA for ; Sun, 29 Mar 2009 15:21:55 +0200 (CEST) Message-ID: <49CF75F3.6010808@ogris.de> Date: Sun, 29 Mar 2009 15:21:55 +0200 From: "Felix J. Ogris" User-Agent: Thunderbird 2.0.0.21 (X11/20090329) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <278464.35012.qm@web63907.mail.re1.yahoo.com> In-Reply-To: <278464.35012.qm@web63907.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: CARP IP level load balancing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Mar 2009 13:21:57 -0000 Barney Cordoba wrote: > > > --- On Sun, 3/8/09, Felix J. Ogris wrote: > > >> From: Felix J. Ogris >> Subject: Re: CARP IP level load balancing >> To: freebsd-net@freebsd.org >> Date: Sunday, March 8, 2009, 4:24 AM >> On 1/20/09 3:30 PM, "Alexey Ivanov" >> wrote: >> >> >>> Is there any plans to port IP level LB from OpenBSD, >>> >> and, if yes, will it be >> >>> ported to 7x and 6x? >>> >> Feel free to port http://ogris.de/carp/carp_aa.patch to >> 7.x. >> >> Felix >> >> > > Is there some difference from LAGG? > > Barney > > > > Yes. It is similar to netfilter's clusterip target. Felix From owner-freebsd-net@FreeBSD.ORG Sun Mar 29 17:20:22 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 250C41065670; Sun, 29 Mar 2009 17:20:22 +0000 (UTC) (envelope-from sam@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EF5818FC14; Sun, 29 Mar 2009 17:20:21 +0000 (UTC) (envelope-from sam@FreeBSD.org) Received: from freefall.freebsd.org (sam@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2THKLIc076697; Sun, 29 Mar 2009 17:20:21 GMT (envelope-from sam@freefall.freebsd.org) Received: (from sam@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2THKLhb076687; Sun, 29 Mar 2009 17:20:21 GMT (envelope-from sam) Date: Sun, 29 Mar 2009 17:20:21 GMT Message-Id: <200903291720.n2THKLhb076687@freefall.freebsd.org> To: sam@FreeBSD.org, freebsd-net@FreeBSD.org, sam@FreeBSD.org From: sam@FreeBSD.org Cc: Subject: Re: kern/133178: [lagg] [wlan] lagg with wlan laggpport does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2009 17:20:22 -0000 Synopsis: [lagg] [wlan] lagg with wlan laggpport does not work Responsible-Changed-From-To: freebsd-net->sam Responsible-Changed-By: sam Responsible-Changed-When: Sun Mar 29 17:19:47 UTC 2009 Responsible-Changed-Why: take responsibility http://www.freebsd.org/cgi/query-pr.cgi?pr=133178 From owner-freebsd-net@FreeBSD.ORG Sun Mar 29 21:43:07 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BB811065693 for ; Sun, 29 Mar 2009 21:43:07 +0000 (UTC) (envelope-from ghe@slsware.com) Received: from a218.slsware.com (a218.slsware.com [209.97.231.218]) by mx1.freebsd.org (Postfix) with ESMTP id 07F178FC0A for ; Sun, 29 Mar 2009 21:43:06 +0000 (UTC) (envelope-from ghe@slsware.com) Received: from air.slsware.wif (a226.slsware.dmz [192.168.2.226]) (Authenticated sender: ghe) by a218.slsware.com (a218.slsware.com) with ESMTPA id 469B940049C for ; Sun, 29 Mar 2009 15:23:16 -0600 (MDT) Message-ID: <49CFE6C4.1080809@slsware.com> Date: Sun, 29 Mar 2009 15:23:16 -0600 From: ghe User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: 7.1 network problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Mar 2009 21:43:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This morning I put 7.1 on a Via box with RealTek 8139C+/8169/8169S/8110S Ethernet card (from sysinstall). I'm new to FreeBSD, but I've been playing with this box to learn a little about the BSD side. The network seems not to work unless the interface (re0) is in promiscuous mode. I don't understand this. arp -a looks reasonable, and it doesn't change when promisc is turned off. ping works to localhost and to re0, but if I start a ping to outside the machine, nothing happens until I enable promisc by starting tcpdump or by issuing a command to ifconfig. Then the echoes start. And disabling stops them again. I don't think it's hardware because this box ran Debian Linux for several months with no problems -- unless maybe the Debian driver kept it in promisc all the time; I didn't look... rc.conf: > # -- sysinstall generated deltas -- # Sun Mar 29 09:52:35 2009 > # Created: Sun Mar 29 09:52:35 2009 > # Enable network daemons for user convenience. > # Please make all changes to this file, not to /etc/defaults/rc.conf. > # This file now contains just the overrides from /etc/defaults/rc.conf. > hostname="otto.slsware.lan" > ifconfig_re0="inet 192.168.3.177 netmask 255.255.255.0" > defaultrouter="192.168.3.1" > font8x14="NO" > font8x16="swiss-8x16" > font8x8="swiss-8x8" > ### linux_enable="YES" > ### nfs_client_enable="YES" > ### saver="daemon" > webmin_enable="YES" > # -- sysinstall generated deltas -- # Sun Mar 29 12:45:49 2009 > gateway_enable="NO" > router_enable="YES" > ftpd_enable="YES" > inetd_enable="YES" > named_enable="YES" > ntpd_enable="YES" > postfix_enable="YES" > routed_enable="YES" > rsyncd_enable="YES" > sshd_enable="YES" ifconfig -a: > re0: flags=8943 metric 0 mtu 1500 > options=389b > ether 00:30:18:a0:29:dc > inet 192.168.3.177 netmask 0xffffff00 broadcast 192.168.3.255 > media: Ethernet autoselect (100baseTX ) > status: active > re1: flags=8802 metric 0 mtu 1500 > options=389b > ether 00:30:18:a0:29:dd > media: Ethernet autoselect (10baseT/UTP ) > status: no carrier > plip0: flags=108810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 This is with promisc on. The output is identical with it off, except the PROMISC flag is off. - -- Glenn English ghe@slsware.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknP5sMACgkQ04yQfZbbTLa5TQCeKToOFTJKy9B7xkZ1TTV3q2tG yBsAnRzLRjJJlnE1y8ZZFc/L9V1OUtzz =K+D6 -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Mon Mar 30 01:55:58 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 340E21065670 for ; Mon, 30 Mar 2009 01:55:58 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id 032B48FC08 for ; Mon, 30 Mar 2009 01:55:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so2498097rvb.43 for ; Sun, 29 Mar 2009 18:55:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=X8Bswn9rym/hZbxRw28R2MJV0xytHx8vhEHhNj2kiQU=; b=oLKpkC7vFHXtyRYyn2JQvjmcxD80Fm2+tcmOhRHvCBORRYLXP4xO0JNbCaSzYI8f39 KM2RKg9qaJPeGX2DjfvYkl7rDMR1IkcQ+5M0f33AO2q2IaiT7OvrFB+TzgzeNWqLqdJp IgN/1O/Cpp565MKMHH9VPCJylDcSOvf3cTNbI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=cKhDTh2VwgctNCz2swCfEhHM+Yok2W8s30o9S6cTBb7GCXEx/Z/KIFT0sFNJuHSu5B 9X8oHuUdDk/KIL0OV+JvKNTP3+bjvtXPgH8DTzPuKBmyIrQ65wZgCT1b9nhH031PC5ho xtnnD8givuaLRAEGvZhxUqKCo3wXqJWgPUjPk= Received: by 10.142.222.19 with SMTP id u19mr1896086wfg.243.1238378157322; Sun, 29 Mar 2009 18:55:57 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id b39sm11311118rvf.6.2009.03.29.18.55.54 (version=SSLv3 cipher=RC4-MD5); Sun, 29 Mar 2009 18:55:56 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Mon, 30 Mar 2009 10:54:53 +0900 From: Pyun YongHyeon Date: Mon, 30 Mar 2009 10:54:53 +0900 To: ghe Message-ID: <20090330015453.GA7076@michelle.cdnetworks.co.kr> References: <49CFE6C4.1080809@slsware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49CFE6C4.1080809@slsware.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: 7.1 network problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2009 01:55:58 -0000 On Sun, Mar 29, 2009 at 03:23:16PM -0600, ghe wrote: [...] > This morning I put 7.1 on a Via box with RealTek 8139C+/8169/8169S/8110S > Ethernet card (from sysinstall). I'm new to FreeBSD, but I've been > playing with this box to learn a little about the BSD side. > > The network seems not to work unless the interface (re0) is in > promiscuous mode. > > I don't understand this. arp -a looks reasonable, and it doesn't change > when promisc is turned off. ping works to localhost and to re0, but if I > start a ping to outside the machine, nothing happens until I enable > promisc by starting tcpdump or by issuing a command to ifconfig. Then > the echoes start. And disabling stops them again. > Would you show me dmesg output(re(4) related part only)? From owner-freebsd-net@FreeBSD.ORG Mon Mar 30 09:46:43 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E72A1065672; Mon, 30 Mar 2009 09:46:43 +0000 (UTC) (envelope-from ume@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 43F188FC1A; Mon, 30 Mar 2009 09:46:43 +0000 (UTC) (envelope-from ume@FreeBSD.org) Received: from freefall.freebsd.org (ume@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2U9kgwj044292; Mon, 30 Mar 2009 09:46:42 GMT (envelope-from ume@freefall.freebsd.org) Received: (from ume@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2U9kfZv044288; Mon, 30 Mar 2009 09:46:41 GMT (envelope-from ume) Date: Mon, 30 Mar 2009 09:46:41 GMT Message-Id: <200903300946.n2U9kfZv044288@freefall.freebsd.org> To: wb@arb-phys.uni-dortmund.de, ume@FreeBSD.org, freebsd-net@FreeBSD.org, ume@FreeBSD.org From: ume@FreeBSD.org Cc: Subject: Re: bin/92370: [pppd] ppp server not accessible to IPV4 unless built with NO_INET6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Mar 2009 09:46:43 -0000 Synopsis: [pppd] ppp server not accessible to IPV4 unless built with NO_INET6 State-Changed-From-To: open->feedback State-Changed-By: ume State-Changed-When: Mon Mar 30 09:43:57 UTC 2009 State-Changed-Why: Responsible-Changed-From-To: freebsd-net->ume Responsible-Changed-By: ume Responsible-Changed-When: Mon Mar 30 09:43:57 UTC 2009 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=92370 From owner-freebsd-net@FreeBSD.ORG Mon Mar 30 11:06:57 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44641106564A for ; Mon, 30 Mar 2009 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 309A38FC0A for ; Mon, 30 Mar 2009 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2UB6vkF054824 for ; Mon, 30 Mar 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2UB6uRt054820 for freebsd-net@FreeBSD.org; Mon, 30 Mar 2009 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Mar 2009 11:06:56 GMT Message-Id: <200903301106.n2UB6uRt054820@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2009 11:06:57 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132991 net [bge] if_bge low performance problem o kern/132984 net [netgraph] swi1: net 100% cpu usage f bin/132911 net ip6fw(8): argument type of fill_icmptypes is wrong and o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o kern/132885 net [wlan] 802.1x broken after SVN rev 189592 o conf/132851 net [fib] [patch] allow to setup fib for service running f o bin/132798 net [patch] ggatec(8): ggated/ggatec connection slowdown p o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132722 net [ath] Wifi ath0 associates fine with AP, but DHCP or I o kern/132715 net [lagg] [panic] Panic when creating vlan's on lagg inte o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132669 net [xl] 3c905-TX send DUP! in reply on ping (sometime) o kern/132625 net [iwn] iwn drivers don't support setting country o kern/132554 net [ipl] There is no ippool start script/ipfilter magic t o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132285 net [carp] alias gives incorrect hash in dmesg o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o conf/132179 net [patch] /etc/network.subr: ipv6 rtsol on incorrect wla o kern/132107 net [carp] carp(4) advskew setting ignored when carp IP us o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o bin/131567 net [socket] [patch] Update for regression/sockets/unix_cm o kern/131549 net ifconfig(8) can't clear 'monitor' mode on the wireless o kern/131536 net [netinet] [patch] kernel does allow manipulation of su o bin/131365 net route(8): route add changes interpretation of network o kern/131310 net [netgraph] [panic] 7.1 panics with mpd netgraph interf o kern/131162 net [ath] Atheros driver bugginess and kernel crashes o kern/131153 net [iwi] iwi doesn't see a wireless network f kern/131087 net [ipw] [panic] ipw / iwi - no sent/received packets; iw f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o bin/130159 net [patch] ppp(8) fails to correctly set routes o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour o kern/129750 net [ath] Atheros AR5006 exits on "cannot map register spa f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129580 net [ndis] Netgear WG311v3 (ndis) causes kenel trap at boo o kern/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129352 net [xl] [patch] xl0 watchdog timeout o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o kern/129135 net [vge] vge driver on a VIA mini-ITX not working o bin/128954 net ifconfig(8) deletes valid routes o kern/128917 net [wpi] [panic] if_wpi and wpa+tkip causing kernel panic o kern/128884 net [msk] if_msk page fault while in kernel mode o kern/128840 net [igb] page fault under load with igb/LRO o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128598 net [bluetooth] WARNING: attempt to net_add_domain(bluetoo o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o conf/128334 net [request] use wpa_cli in the "WPA DHCP" situation o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127928 net [tcp] [patch] TCP bandwidth gets squeezed every time t o kern/127834 net [ixgbe] [patch] wrong error counting o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) s kern/127587 net [bge] [request] if_bge(4) doesn't support BCM576X fami f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127102 net [wpi] Intel 3945ABG low throughput o kern/127057 net [udp] Unable to send UDP packet via IPv6 socket to IPv o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126924 net [an] [patch] printf -> device_printf and simplify prob o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126339 net [ipw] ipw driver drops the connection o kern/126214 net [ath] txpower problem with Atheros wifi card o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre f kern/125195 net [fxp] fxp(4) driver failed to initialize device Intel o kern/124904 net [fxp] EEPROM corruption with Compaq NC3163 NIC o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 net [ieee80211] net80211 discards power-save queue packets o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one f kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [multicast] FreeBSD 7 multicast routing problem p kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix o kern/122743 net [mbuf] [panic] vm_page_unwire: invalid wire count: 0 o kern/122697 net [ath] Atheros card is not well supported o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122195 net [ed] Alignment problems in if_ed o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/121983 net [fxp] fxp0 MBUF and PAE o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] ppp(8): fix local stack overflow in ppp o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/120966 net [rum] kernel panic with if_rum and WPA encryption p docs/120945 net [patch] ip6(4) man page lacks documentation for TCLASS o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr a bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o sparc/118932 net [panic] 7.0-BETA4/sparc-64 kernel panic in rip_output a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118727 net [netgraph] [patch] [request] add new ng_pf module s kern/117717 net [panic] Kernel panic with Bittorrent client. o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116328 net [bge]: Solid hang with bge interface o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f f kern/114899 net [bge] bge0: watchdog timeout -- resetting o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/113895 net [xl] xl0 fails on 6.2-RELEASE but worked fine on 5.5-R o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112570 net [bge] packet loss with bge driver on BCM5704 chipset o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111457 net [ral] ral(4) freeze o kern/110140 net [ipw] ipw fails under load o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109251 net [re] [patch] if_re cardbus card won't attach o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce] Huge network latencies with 6.2-RELEASE / STABLE o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o kern/107850 net [bce] bce driver link negotiation is faulty o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/106243 net [nve] double fault panic in if_nve.c on high loads o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/105348 net [ath] ath device stopps TX o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/104485 net [bge] Broadcom BCM5704C: Intermittent on newer chip ve o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working f bin/97392 net ppp(8) hangs instead terminating o kern/97306 net [netgraph] NG_L2TP locks after connection with failed f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/96030 net [bfe] [patch] Install hangs with Broadcomm 440x NIC in o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear s kern/94863 net [bge] [patch] hack to get bge(4) working on IBM e326m o kern/94162 net [bge] 6.x kenel stale with bge(4) o kern/93886 net [ath] Atheros/D-Link DWL-G650 long delay to associate f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi f kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/92090 net [bge] bge0: watchdog timeout -- resetting o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/90890 net [vr] Problems with network: vr0: tx shutdown timeout s kern/90086 net [hang] 5.4p8 on supermicro P8SCT hangs during boot if f kern/88082 net [ath] [panic] cts protection for ath0 causes panic o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87506 net [vr] [patch] Fix alias support on vr interfaces o kern/87194 net [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ o kern/85266 net [xe] [patch] xe(4) driver does not recognise Xircom XE o kern/84202 net [ed] [patch] Holtek HT80232 PCI NIC recognition on Fre o bin/82975 net route change does not parse classfull network as given o kern/82497 net [vge] vge(4) on AMD64 only works when loaded late, not f kern/81644 net [vge] vge(4) does not work properly when loaded as a K s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/80853 net [ed] [patch] add support for Compex RL2000/ISA in PnP o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph f kern/79262 net [dc] Adaptec ANA-6922 not fully supported o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77341 net [ip6] problems with IPV6 implementation o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time f kern/73538 net [bge] problem with the Broadcom BCM5788 Gigabit Ethern o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 s kern/60293 net [patch] FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic f i386/45773 net [bge] Softboot causes autoconf failure on Broadcom 570 s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [arp] [patch] for static ARP tables in rc.network 285 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Mar 30 22:53:11 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9C47106566B for ; Mon, 30 Mar 2009 22:53:11 +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 A52A68FC21 for ; Mon, 30 Mar 2009 22:53:11 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 30 Mar 2009 15:38:40 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Mon, 30 Mar 2009 15:38:40 -0700 From: "David Christensen" To: "freebsd-net@freebsd.org" Date: Mon, 30 Mar 2009 15:38:39 -0700 Thread-Topic: Availability of Programmer's Guide for Broadcom 57XX LAN Controllers Thread-Index: AcmxiEV2UW0eU6qvSmGydf4F5EFU+Q== Message-ID: <5D267A3F22FD854F8F48B3D2B5238193397DC21622@IRVEXCHCCR01.corp.ad.broadcom.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 65CF967A5Y812614970-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Availability of Programmer's Guide for Broadcom 57XX LAN Controllers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Mar 2009 22:53:12 -0000 For those who are interested in working on the bge(4) driver, Broadcom has = now posted its Programmer's Guide at http://www.broadcom.com/collateral/pg/= 57XX-PG105-R.pdf. This document covers most of the older chips including 5= 700, 5701, 5703, 5704, 5714, and 5721, though since much of the architectur= e is shared with newer chips such as 5754 and 5761, it is still a useful re= ference. We're working on releasing the PG's for other members of the bge(= 4) family and also the PG for the bce(4) family soon. Dave From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 05:50:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3773A106566B; Tue, 31 Mar 2009 05:50:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0BEB98FC08; Tue, 31 Mar 2009 05:50:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2V5o2eN075733; Tue, 31 Mar 2009 05:50:02 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2V5o22X075727; Tue, 31 Mar 2009 05:50:02 GMT (envelope-from linimon) Date: Tue, 31 Mar 2009 05:50:02 GMT Message-Id: <200903310550.n2V5o22X075727@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/133235: [netinet] [patch] Process SIOCDLIFADDR command incorrectly in in_control() X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Mar 2009 05:50:04 -0000 Old Synopsis: Process SIOCDLIFADDR command incorrectly in in_control() New Synopsis: [netinet] [patch] Process SIOCDLIFADDR command incorrectly in in_control() Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Mar 31 05:49:29 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=133235 From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 06:38:59 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C75591065688 for ; Tue, 31 Mar 2009 06:38:59 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-qy0-f134.google.com (mail-qy0-f134.google.com [209.85.221.134]) by mx1.freebsd.org (Postfix) with ESMTP id 85AEA8FC25 for ; Tue, 31 Mar 2009 06:38:59 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by qyk40 with SMTP id 40so4578072qyk.3 for ; Mon, 30 Mar 2009 23:38:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=tpsys4wObwpp1GllxZCjZiA2vzdsRplxA/2CTSfyrLA=; b=jsOTEg9XcVQHB+LdsY3dNl/w3JWyv5UfvKUeOiU3R70U+sib5BHKl0SCFhCJhFVjnH 8XxrTZ16yT/rq6M/0yyUstPHo187geGUjQYw7vGgJ8IFpZI0PUUjlJeOOkKofWmTvPzY Dyv09GYMCWmcSS/nLjDHJDYwHnmvC9dLYzNKI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=HH+iMBYIxJH36lLa7Xri8A9LN4htdsausJO75IDnuwOeTcVena9M+Wt0AmZ/4rfgww BnmReACOdJuX70ZmQVzblWWifukWU2XFZAWUq79+ePNh+Qpc72+Sid9rqfwcRU95+DlR mHlVj2T1oKi0kU5BjymY0/ybTRzzjhVSTknqo= MIME-Version: 1.0 Received: by 10.229.94.148 with SMTP id z20mr2185655qcm.106.1238480114964; Mon, 30 Mar 2009 23:15:14 -0700 (PDT) Date: Tue, 31 Mar 2009 01:15:14 -0500 Message-ID: <11167f520903302315u28f2dffdqe79f493a49b96863@mail.gmail.com> From: "Sam Fourman Jr." To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: 802.11 QinQ in need of some help X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Mar 2009 06:39:00 -0000 Hello List, I have searched hi and low, and I have not found the answer to my question, So I am seeking help. We have a small dedicated server webhosting company, and we need support for QinQ vlan tags actually I need the following Customers Vlan tag our Vlan tag aka service provider Would someone have the spare time, to provide me with a working sample on how to use ng_vlan on a bridge between Customer and core service network to apply at least Double stacked VLAN tags, I am confused on how to Double tag specific Ethernet frames with a specific "Service Provider tag" based on destination ip address. and then how to "unstack the frame on the other end" Thank you very much for your time Sam Fourman Jr. From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 07:00:09 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF6C4106566C for ; Tue, 31 Mar 2009 07:00:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A383D8FC16 for ; Tue, 31 Mar 2009 07:00:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2V709ir072930 for ; Tue, 31 Mar 2009 07:00:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2V709k6072929; Tue, 31 Mar 2009 07:00:09 GMT (envelope-from gnats) Date: Tue, 31 Mar 2009 07:00:09 GMT Message-Id: <200903310700.n2V709k6072929@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Vany Serezhkin Cc: Subject: Re: kern/132885: [wlan] 802.1x broken after SVN rev 189592 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vany Serezhkin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 07:00:10 -0000 The following reply was made to PR kern/132885; it has been noted by GNATS. From: Vany Serezhkin To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/132885: [wlan] 802.1x broken after SVN rev 189592 Date: Tue, 31 Mar 2009 10:35:57 +0400 Hello again. In last weekend i update system and this bug is 'magically' disappeared. All works now. -- Vany Serezhkin. Yandex. http://yandex.ru/ From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 08:25:28 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8B91106566B for ; Tue, 31 Mar 2009 08:25:28 +0000 (UTC) (envelope-from sergey@vavilov.org) Received: from mx2.sms-hit.ru (mx2.sms-hit.ru [195.137.200.46]) by mx1.freebsd.org (Postfix) with ESMTP id E02E98FC08 for ; Tue, 31 Mar 2009 08:25:27 +0000 (UTC) (envelope-from sergey@vavilov.org) Received: from [10.100.10.3] (smsone.sms-hit.ru [10.100.10.3]) by mx2.sms-hit.ru (8.14.2/8.14.2) with ESMTP id n2V8B5cX008890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Mar 2009 14:11:06 +0600 (YEKST) (envelope-from sergey@vavilov.org) Message-ID: <49D1D019.6090906@vavilov.org> Date: Tue, 31 Mar 2009 14:11:05 +0600 From: Sergey Vavilov User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: David Christensen , freebsd-net@freebsd.org References: <5D267A3F22FD854F8F48B3D2B5238193397DC21622@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B5238193397DC21622@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mx2.sms-hit.ru [10.100.10.2]); Tue, 31 Mar 2009 14:11:06 +0600 (YEKST) Cc: Subject: Re: Availability of Programmer's Guide for Broadcom 57XX LAN Controllers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Mar 2009 08:25:29 -0000 Hello! BCM5721 now supported in 7.1-RELEASE ? Thank you! David Christensen wrote: > For those who are interested in working on the bge(4) driver, Broadcom has now posted its Programmer's Guide at http://www.broadcom.com/collateral/pg/57XX-PG105-R.pdf. This document covers most of the older chips including 5700, 5701, 5703, 5704, 5714, and 5721, though since much of the architecture is shared with newer chips such as 5754 and 5761, it is still a useful reference. We're working on releasing the PG's for other members of the bge(4) family and also the PG for the bce(4) family soon. > > 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" > -- Sergey Vavilov, Perm, Russia From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 10:40:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FB6E106566B for ; Tue, 31 Mar 2009 10:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 538678FC12 for ; Tue, 31 Mar 2009 10:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2VAe30i002562 for ; Tue, 31 Mar 2009 10:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2VAe314002561; Tue, 31 Mar 2009 10:40:03 GMT (envelope-from gnats) Date: Tue, 31 Mar 2009 10:40:03 GMT Message-Id: <200903311040.n2VAe314002561@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: LiangZhenyu Cc: Subject: Re: kern/133235: [netinet] [patch] Process SIOCDLIFADDR command incorrectly in in_control() X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: LiangZhenyu List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 10:40:03 -0000 The following reply was made to PR kern/133235; it has been noted by GNATS. From: LiangZhenyu To: bug-followup@FreeBSD.org, soflare@gmail.com Cc: Subject: Re: kern/133235: [netinet] [patch] Process SIOCDLIFADDR command incorrectly in in_control() Date: Tue, 31 Mar 2009 18:02:50 +0800 The long expression: candidate.s_addr = ((struct sockaddr_in *)&ifa->ifa_addr)->sin_addr.s_addr; will cause a compilation problem in my machine. The target can be generated but was wrong. So I split it to 2 short expressions. From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 12:40:02 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90E49106566C for ; Tue, 31 Mar 2009 12:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4D58FC1A for ; Tue, 31 Mar 2009 12:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2VCe2pI068733 for ; Tue, 31 Mar 2009 12:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2VCe2qR068732; Tue, 31 Mar 2009 12:40:02 GMT (envelope-from gnats) Date: Tue, 31 Mar 2009 12:40:02 GMT Message-Id: <200903311240.n2VCe2qR068732@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Sergey Pronin Cc: Subject: Re: kern/132984: [netgraph] swi1: net 100% cpu usage X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sergey Pronin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 12:40:02 -0000 The following reply was made to PR kern/132984; it has been noted by GNATS. From: Sergey Pronin To: bug-followup@FreeBSD.org, vlad@prokk.net Cc: Subject: Re: kern/132984: [netgraph] swi1: net 100% cpu usage Date: Tue, 31 Mar 2009 15:01:39 +0300 --001636c5a72e353f32046668f6ec Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit This bug is also related to: http://lists.freebsd.org/pipermail/freebsd-net/2009-March/021345.html http://lists.freebsd.org/pipermail/freebsd-net/2009-March/021518.html I've experienced the same problem with: FreeBSD 7.1-RELEASE-p1 and p2 FreeBSD 7.0-RELEASE-p9 and p10 FreeBSD 6.4-RELEASE-p3 --001636c5a72e353f32046668f6ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This bug is also related to:
http://lists.freebsd.org/pipermail/f= reebsd-net/2009-March/021345.html
http://lists.freebsd.org/pi= permail/freebsd-net/2009-March/021518.html

I've experienced=
  the same problem with:
FreeBSD 7.1-RELEASE-p1 and p2
FreeBSD 7.0-REL=
 EASE-p9 and p10
FreeBSD 6.4-RELEASE-p3

--001636c5a72e353f32046668f6ec-- From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 07:34:36 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 815031065670 for ; Wed, 1 Apr 2009 07:34:36 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 44CE18FC1A for ; Wed, 1 Apr 2009 07:34:36 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n317W5lE085839 for ; Wed, 1 Apr 2009 01:32:05 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 01 Apr 2009 01:32:46 -0600 (MDT) Message-Id: <20090401.013246.-1253043078.imp@bsdimp.com> To: net@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Small change to ukphy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Apr 2009 07:34:36 -0000 I've encountered a number of PHY chips that need auto negotiation kicked off to come out of ISO state. This makes sense, because the ukphy driver never seems to take the PHY out of isolation state otherwise. Index: ukphy.c =================================================================== --- ukphy.c (revision 190463) +++ ukphy.c (working copy) @@ -146,6 +146,7 @@ sc->mii_phy = ma->mii_phyno; sc->mii_service = ukphy_service; sc->mii_pdata = mii; + sc->mii_flags |= MIIF_FORCEANEG; mii->mii_instance++; This forces auto negotiation. The reason for this is that it takes it out of ISO state (Isolate). Once out of that state, things work well. The question I have is will we properly go back into ISO state for PHYs that should be isolated. NetBSD has many of its NIC drivers setting this flag. Their APIs allow them to set this directly at mii attach time. Ours don't, so none of our drivers set this flag. The other fix for this might be: Index: mii_physubr.c =================================================================== --- mii_physubr.c (revision 190463) +++ mii_physubr.c (working copy) @@ -113,7 +113,9 @@ int bmcr, anar, gtcr; if (IFM_SUBTYPE(ife->ifm_media) == IFM_AUTO) { - if ((PHY_READ(sc, MII_BMCR) & BMCR_AUTOEN) == 0 || + bmcr = PHY_READ(sc, MII_BMCR); + if ((bmcr & BMCR_AUTOEN) == 0 || + (bmcr & BMCR_ISO) || (sc->mii_flags & MIIF_FORCEANEG)) (void) mii_phy_auto(sc); return; Which says that if auto negotiation is enabled, and ISO is set to go ahead and kick off an auto negotiation. I'm less sure of this path, but it is an alternative. Otherwise, we never write to the BMCR to take the device out of isolation. If there's a better place to do this, then I'm all ears. Either one of these hacks make several PC Cards that I have start to work... In fact, I'm starting to approach 100% (up from 50%) of my ed-based PC Cards working with this simple change (and others to the ed driver). I know that these cards are a little behind the leading edge, but I'd like to get them working since I've put a few hours into investigating things here. Comments? Warner From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 10:36:32 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E360B10656DB for ; Wed, 1 Apr 2009 10:36:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id B21228FC1C for ; Wed, 1 Apr 2009 10:36:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so3803417rvb.43 for ; Wed, 01 Apr 2009 03:36:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=b8rWJgwky+sggFvSRYa9r8LZAT0GWBSTWHCA1iQNNRI=; b=d/6fWXliieEQJaV4+v1nWbUX9YGbRgpWKIdP95TRbGlp0am4pGIgtA11Cd4tz+TDsr KT42RmssNLz7hMBmXK3gAlULn4tpyF2rFLpNMZL1cYXMRaLjdlaeffK+ArmkDwNc5eTS AI/8E3k/Pl7sPDt8/Dr5u+ZJkdzgENEFJURLk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=n9JcepkSpEoCLUlTgPqdnrcrIRuYdpecPhHjx5p15EqF23o3v981UqQ+bJhfZvau5U OOudtw4MrS2861SOdWiolfpy/ziTxsssvzQL6XS+eTcmK7Puy77Q/gN7MQeAbj8qvRO2 DjEDFVAb+0Rd+ntSd9ndy+KMyh5T14zBd2kfs= Received: by 10.141.33.19 with SMTP id l19mr3956888rvj.209.1238580613270; Wed, 01 Apr 2009 03:10:13 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id f21sm19656270rvb.5.2009.04.01.03.10.11 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Apr 2009 03:10:12 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Wed, 1 Apr 2009 19:09:39 +0900 From: Pyun YongHyeon Date: Wed, 1 Apr 2009 19:09:39 +0900 To: "M. Warner Losh" Message-ID: <20090401100939.GB12246@michelle.cdnetworks.co.kr> References: <20090401.013246.-1253043078.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090401.013246.-1253043078.imp@bsdimp.com> User-Agent: Mutt/1.4.2.3i Cc: net@freebsd.org Subject: Re: Small change to ukphy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2009 10:36:33 -0000 On Wed, Apr 01, 2009 at 01:32:46AM -0600, M. Warner Losh wrote: > I've encountered a number of PHY chips that need auto negotiation > kicked off to come out of ISO state. This makes sense, because the > ukphy driver never seems to take the PHY out of isolation state > otherwise. > > Index: ukphy.c > =================================================================== > --- ukphy.c (revision 190463) > +++ ukphy.c (working copy) > @@ -146,6 +146,7 @@ > sc->mii_phy = ma->mii_phyno; > sc->mii_service = ukphy_service; > sc->mii_pdata = mii; > + sc->mii_flags |= MIIF_FORCEANEG; > > mii->mii_instance++; > > > This forces auto negotiation. The reason for this is that it takes it > out of ISO state (Isolate). Once out of that state, things work If the purpose is to take PHY out of isolated state couldn't this be handled in ifm_change_cb_t handler of parent interface? I guess the callback can reset the PHY and subsequent mii_mediachg() call may start auto-negotiation. > well. The question I have is will we properly go back into ISO state > for PHYs that should be isolated. > If the PHY requires special handing for ISO state in reset it may need separated PHY driver as ukphy(4) does not set MIIF_NOISOLATE. As you said it would be really great if we have a generic way to pass various MII flags or driver specific information to mii(4). > NetBSD has many of its NIC drivers setting this flag. Their APIs > allow them to set this directly at mii attach time. Ours don't, so > none of our drivers set this flag. > > The other fix for this might be: > Index: mii_physubr.c > =================================================================== > --- mii_physubr.c (revision 190463) > +++ mii_physubr.c (working copy) > @@ -113,7 +113,9 @@ > int bmcr, anar, gtcr; > > if (IFM_SUBTYPE(ife->ifm_media) == IFM_AUTO) { > - if ((PHY_READ(sc, MII_BMCR) & BMCR_AUTOEN) == 0 || > + bmcr = PHY_READ(sc, MII_BMCR); > + if ((bmcr & BMCR_AUTOEN) == 0 || > + (bmcr & BMCR_ISO) || > (sc->mii_flags & MIIF_FORCEANEG)) > (void) mii_phy_auto(sc); > return; > > Which says that if auto negotiation is enabled, and ISO is set to go > ahead and kick off an auto negotiation. I'm less sure of this path, > but it is an alternative. Otherwise, we never write to the BMCR to > take the device out of isolation. If there's a better place to do > this, then I'm all ears. > > Either one of these hacks make several PC Cards that I have start to > work... In fact, I'm starting to approach 100% (up from 50%) of my > ed-based PC Cards working with this simple change (and others to the > ed driver). I know that these cards are a little behind the leading > edge, but I'd like to get them working since I've put a few hours into > investigating things here. > > Comments? > > Warner From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 15:37:55 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BFF5106566B for ; Wed, 1 Apr 2009 15:37:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4B6F58FC19 for ; Wed, 1 Apr 2009 15:37:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n31Faw5s099101; Wed, 1 Apr 2009 09:36:58 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 01 Apr 2009 09:37:40 -0600 (MDT) Message-Id: <20090401.093740.669301742.imp@bsdimp.com> To: pyunyh@gmail.com From: "M. Warner Losh" In-Reply-To: <20090401100939.GB12246@michelle.cdnetworks.co.kr> References: <20090401.013246.-1253043078.imp@bsdimp.com> <20090401100939.GB12246@michelle.cdnetworks.co.kr> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: Small change to ukphy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Apr 2009 15:37:55 -0000 In message: <20090401100939.GB12246@michelle.cdnetworks.co.kr> Pyun YongHyeon writes: : On Wed, Apr 01, 2009 at 01:32:46AM -0600, M. Warner Losh wrote: : > I've encountered a number of PHY chips that need auto negotiation : > kicked off to come out of ISO state. This makes sense, because the : > ukphy driver never seems to take the PHY out of isolation state : > otherwise. : > : > Index: ukphy.c : > =================================================================== : > --- ukphy.c (revision 190463) : > +++ ukphy.c (working copy) : > @@ -146,6 +146,7 @@ : > sc->mii_phy = ma->mii_phyno; : > sc->mii_service = ukphy_service; : > sc->mii_pdata = mii; : > + sc->mii_flags |= MIIF_FORCEANEG; : > : > mii->mii_instance++; : > : > : > This forces auto negotiation. The reason for this is that it takes it : > out of ISO state (Isolate). Once out of that state, things work : : If the purpose is to take PHY out of isolated state couldn't this : be handled in ifm_change_cb_t handler of parent interface? I guess : the callback can reset the PHY and subsequent mii_mediachg() call : may start auto-negotiation. This callback isn't called. The problem is that the PHY is in ISO state. Since it is in ISO state with auto negotiation enabled, we never kick off an explicit auto negotiation, so the state never changes so we never get this callback... : > well. The question I have is will we properly go back into ISO state : > for PHYs that should be isolated. : > : : If the PHY requires special handing for ISO state in reset it may : need separated PHY driver as ukphy(4) does not set MIIF_NOISOLATE. : As you said it would be really great if we have a generic way to : pass various MII flags or driver specific information to mii(4). This seems to be a common quirk. I'd hate to have a driver that's just ukphy but with the one line added above and play what-a-mole with all the odd-balls that are out there. Doesn't seem like a strategy that will win the day. I think we have a way to do this... I could do the following in my attach routine: mii = device_get_softc(sc->miibus); LIST_FOREACH(miisc, &mii->mii_phys, mii_list) { miisc->mii_flags |= MIIF_FORCEANEG; mii_phy_reset(miisc); } mii_mediachg(mii); which is similar to what fxp does in its change routine (it is what I put in my status change routine). Also MIIF_NOISOLATE works as well. Is the above too insane? Warner : > NetBSD has many of its NIC drivers setting this flag. Their APIs : > allow them to set this directly at mii attach time. Ours don't, so : > none of our drivers set this flag. : > : > The other fix for this might be: : > Index: mii_physubr.c : > =================================================================== : > --- mii_physubr.c (revision 190463) : > +++ mii_physubr.c (working copy) : > @@ -113,7 +113,9 @@ : > int bmcr, anar, gtcr; : > : > if (IFM_SUBTYPE(ife->ifm_media) == IFM_AUTO) { : > - if ((PHY_READ(sc, MII_BMCR) & BMCR_AUTOEN) == 0 || : > + bmcr = PHY_READ(sc, MII_BMCR); : > + if ((bmcr & BMCR_AUTOEN) == 0 || : > + (bmcr & BMCR_ISO) || : > (sc->mii_flags & MIIF_FORCEANEG)) : > (void) mii_phy_auto(sc); : > return; : > : > Which says that if auto negotiation is enabled, and ISO is set to go : > ahead and kick off an auto negotiation. I'm less sure of this path, : > but it is an alternative. Otherwise, we never write to the BMCR to : > take the device out of isolation. If there's a better place to do : > this, then I'm all ears. : > : > Either one of these hacks make several PC Cards that I have start to : > work... In fact, I'm starting to approach 100% (up from 50%) of my : > ed-based PC Cards working with this simple change (and others to the : > ed driver). I know that these cards are a little behind the leading : > edge, but I'd like to get them working since I've put a few hours into : > investigating things here. : > : > Comments? : > : > Warner : From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 17:27:56 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0199F106566B for ; Wed, 1 Apr 2009 17:27:56 +0000 (UTC) (envelope-from craft@alacritech.com) Received: from smtp171.sat.emailsrvr.com (smtp171.sat.emailsrvr.com [66.216.121.171]) by mx1.freebsd.org (Postfix) with ESMTP id D351D8FC1D for ; Wed, 1 Apr 2009 17:27:55 +0000 (UTC) (envelope-from craft@alacritech.com) Received: from relay17.relay.sat.mlsrvr.com (localhost [127.0.0.1]) by relay17.relay.sat.mlsrvr.com (SMTP Server) with ESMTP id A82331B4201; Wed, 1 Apr 2009 13:14:08 -0400 (EDT) Received: by relay17.relay.sat.mlsrvr.com (Authenticated sender: craft-AT-alacritech.com) with ESMTPSA id 6DCA01B4200 for ; Wed, 1 Apr 2009 13:14:08 -0400 (EDT) Message-ID: <2ed801c9b2ed$44c6c3c0$510a010a@alacritech.com> From: "Peter Craft" To: Date: Wed, 1 Apr 2009 10:14:07 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: pNFS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Apr 2009 17:27:56 -0000 Are there any efforts underway to implement parallel NFS in FreeBSD? From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 21:26:22 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49331106564A for ; Wed, 1 Apr 2009 21:26:22 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id A66598FC18 for ; Wed, 1 Apr 2009 21:26:21 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n31LCsHE083842; Wed, 1 Apr 2009 23:12:55 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n31LCsvh083841; Wed, 1 Apr 2009 23:12:54 +0200 (CEST) (envelope-from marius) Date: Wed, 1 Apr 2009 23:12:54 +0200 From: Marius Strobl To: Pyun YongHyeon Message-ID: <20090401211254.GA83780@alchemy.franken.de> References: <20090401.013246.-1253043078.imp@bsdimp.com> <20090401100939.GB12246@michelle.cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090401100939.GB12246@michelle.cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: "M. Warner Losh" , net@freebsd.org Subject: Re: Small change to ukphy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Apr 2009 21:26:22 -0000 On Wed, Apr 01, 2009 at 07:09:39PM +0900, Pyun YongHyeon wrote: > On Wed, Apr 01, 2009 at 01:32:46AM -0600, M. Warner Losh wrote: > > I've encountered a number of PHY chips that need auto negotiation > > kicked off to come out of ISO state. This makes sense, because the > > ukphy driver never seems to take the PHY out of isolation state > > otherwise. > > > > Index: ukphy.c > > =================================================================== > > --- ukphy.c (revision 190463) > > +++ ukphy.c (working copy) > > @@ -146,6 +146,7 @@ > > sc->mii_phy = ma->mii_phyno; > > sc->mii_service = ukphy_service; > > sc->mii_pdata = mii; > > + sc->mii_flags |= MIIF_FORCEANEG; > > > > mii->mii_instance++; > > > > > > This forces auto negotiation. The reason for this is that it takes it > > out of ISO state (Isolate). Once out of that state, things work > > If the purpose is to take PHY out of isolated state couldn't this > be handled in ifm_change_cb_t handler of parent interface? I guess > the callback can reset the PHY and subsequent mii_mediachg() call > may start auto-negotiation. > > > well. The question I have is will we properly go back into ISO state > > for PHYs that should be isolated. > > > > If the PHY requires special handing for ISO state in reset it may > need separated PHY driver as ukphy(4) does not set MIIF_NOISOLATE. > As you said it would be really great if we have a generic way to > pass various MII flags or driver specific information to mii(4). > > > NetBSD has many of its NIC drivers setting this flag. Their APIs > > allow them to set this directly at mii attach time. Ours don't, so > > none of our drivers set this flag. > > > > The other fix for this might be: > > Index: mii_physubr.c > > =================================================================== > > --- mii_physubr.c (revision 190463) > > +++ mii_physubr.c (working copy) > > @@ -113,7 +113,9 @@ > > int bmcr, anar, gtcr; > > > > if (IFM_SUBTYPE(ife->ifm_media) == IFM_AUTO) { > > - if ((PHY_READ(sc, MII_BMCR) & BMCR_AUTOEN) == 0 || > > + bmcr = PHY_READ(sc, MII_BMCR); > > + if ((bmcr & BMCR_AUTOEN) == 0 || > > + (bmcr & BMCR_ISO) || > > (sc->mii_flags & MIIF_FORCEANEG)) > > (void) mii_phy_auto(sc); > > return; > > > > Which says that if auto negotiation is enabled, and ISO is set to go > > ahead and kick off an auto negotiation. I'm less sure of this path, > > but it is an alternative. Otherwise, we never write to the BMCR to > > take the device out of isolation. If there's a better place to do > > this, then I'm all ears. > > > > Either one of these hacks make several PC Cards that I have start to > > work... In fact, I'm starting to approach 100% (up from 50%) of my > > ed-based PC Cards working with this simple change (and others to the > > ed driver). I know that these cards are a little behind the leading > > edge, but I'd like to get them working since I've put a few hours into > > investigating things here. > > > > Comments? > > FYI, the idea I had for passing MIIF_DOPAUSE from the NIC drivers to the PHY drivers as required by the flow-control support without breaking the ABI was to use device flags. A proof-of-concept patch with an example application of that approach is: http://people.freebsd.org/~marius/mii_flags.diff One could even or the flags together in miibus_attach(), allowing MIIF_FORCEANEG etc to be additionally set via hints. Marius From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 00:19:32 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86D8F1065672 for ; Thu, 2 Apr 2009 00:19:32 +0000 (UTC) (envelope-from brunner@nic-naa.net) Received: from abenaki.wabanaki.net (abenaki.wabanaki.net [65.99.1.130]) by mx1.freebsd.org (Postfix) with ESMTP id 2F0518FC1B for ; Thu, 2 Apr 2009 00:19:32 +0000 (UTC) (envelope-from brunner@nic-naa.net) Received: from clam.local (host671420093250.direcway.com [67.142.250.93] (may be forged)) by abenaki.wabanaki.net (8.14.2/8.14.2) with ESMTP id n31NGUdf087348; Wed, 1 Apr 2009 18:16:33 -0500 (EST) (envelope-from brunner@nic-naa.net) Message-ID: <49D3FE6C.5050505@nic-naa.net> Date: Wed, 01 Apr 2009 19:53:16 -0400 From: Eric Brunner-Williams User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Peter Craft References: <2ed801c9b2ed$44c6c3c0$510a010a@alacritech.com> In-Reply-To: <2ed801c9b2ed$44c6c3c0$510a010a@alacritech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pNFS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2009 00:19:32 -0000 Peter Craft wrote: > Are there any efforts underway to implement parallel NFS in FreeBSD? > _______________________________________________ > 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" > > > i've not implemented a line of pnfs, and i've not looked much at the pnfs list since leaving panasas, however ... i thought the question was interesting at the time and i'm responding to your query. From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 00:53:33 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D3CF1065675 for ; Thu, 2 Apr 2009 00:53:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 0AEAB8FC16 for ; Thu, 2 Apr 2009 00:53:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so288501rvb.43 for ; Wed, 01 Apr 2009 17:53:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=7+CuscxNlgV4iID8bcsqjhay2D8SzUQhVjH7wqA8B5k=; b=INaTQSQpdWrjYnyiqlzR3fHYvIGbL3UNBhPAnP0y94bssOGa8jRno5r87DdgOjZgOk KABj7GS1d9ggfKRyG6/uH0drR2/SFa+8qTneMWtOTzz0b1tx6SVaExKgo5OLiu6gvLUf vY5G3UUAlE14vzPvy52l15aJore1E0eHva2Lw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=HhoH2Pvdf6d/Ol8bnofYZSn9Yaaz5+5jdGttoRaED8OfuhtYkP3uuY9TZns1wLF+ke GpsW74G4/RrACcBcK0nEhBYVq2h9BuaQyl37cBKrjiCnlWTpXJazuZIG9jpOb2c0KmX2 Yebc46CYubeDC0vowCq+4FUVDfiYONcH5dUV8= Received: by 10.141.107.13 with SMTP id j13mr4255460rvm.251.1238633612769; Wed, 01 Apr 2009 17:53:32 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id f21sm1370608rvb.25.2009.04.01.17.53.31 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Apr 2009 17:53:32 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Thu, 2 Apr 2009 09:53:08 +0900 From: Pyun YongHyeon Date: Thu, 2 Apr 2009 09:53:08 +0900 To: "M. Warner Losh" Message-ID: <20090402005308.GA19091@michelle.cdnetworks.co.kr> References: <20090401.013246.-1253043078.imp@bsdimp.com> <20090401100939.GB12246@michelle.cdnetworks.co.kr> <20090401.093740.669301742.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090401.093740.669301742.imp@bsdimp.com> User-Agent: Mutt/1.4.2.3i Cc: net@freebsd.org Subject: Re: Small change to ukphy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 00:53:33 -0000 On Wed, Apr 01, 2009 at 09:37:40AM -0600, M. Warner Losh wrote: > In message: <20090401100939.GB12246@michelle.cdnetworks.co.kr> > Pyun YongHyeon writes: > : On Wed, Apr 01, 2009 at 01:32:46AM -0600, M. Warner Losh wrote: > : > I've encountered a number of PHY chips that need auto negotiation > : > kicked off to come out of ISO state. This makes sense, because the > : > ukphy driver never seems to take the PHY out of isolation state > : > otherwise. > : > > : > Index: ukphy.c > : > =================================================================== > : > --- ukphy.c (revision 190463) > : > +++ ukphy.c (working copy) > : > @@ -146,6 +146,7 @@ > : > sc->mii_phy = ma->mii_phyno; > : > sc->mii_service = ukphy_service; > : > sc->mii_pdata = mii; > : > + sc->mii_flags |= MIIF_FORCEANEG; > : > > : > mii->mii_instance++; > : > > : > > : > This forces auto negotiation. The reason for this is that it takes it > : > out of ISO state (Isolate). Once out of that state, things work > : > : If the purpose is to take PHY out of isolated state couldn't this > : be handled in ifm_change_cb_t handler of parent interface? I guess > : the callback can reset the PHY and subsequent mii_mediachg() call > : may start auto-negotiation. > > This callback isn't called. The problem is that the PHY is in ISO Oops, you're right. > state. Since it is in ISO state with auto negotiation enabled, we > never kick off an explicit auto negotiation, so the state never > changes so we never get this callback... > > : > well. The question I have is will we properly go back into ISO state > : > for PHYs that should be isolated. > : > > : > : If the PHY requires special handing for ISO state in reset it may > : need separated PHY driver as ukphy(4) does not set MIIF_NOISOLATE. > : As you said it would be really great if we have a generic way to > : pass various MII flags or driver specific information to mii(4). > > This seems to be a common quirk. I'd hate to have a driver that's > just ukphy but with the one line added above and play what-a-mole with > all the odd-balls that are out there. Doesn't seem like a strategy > that will win the day. > > I think we have a way to do this... I could do the following in my > attach routine: > > mii = device_get_softc(sc->miibus); > LIST_FOREACH(miisc, &mii->mii_phys, mii_list) { > miisc->mii_flags |= MIIF_FORCEANEG; > mii_phy_reset(miisc); > } > mii_mediachg(mii); > > which is similar to what fxp does in its change routine (it is what I > put in my status change routine). Also MIIF_NOISOLATE works as well. > > Is the above too insane? > That looks ok to me but marius's patch would be the right direction. From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 00:55:28 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5DDA106566B for ; Thu, 2 Apr 2009 00:55:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id B2BF58FC1C for ; Thu, 2 Apr 2009 00:55:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so289199rvb.43 for ; Wed, 01 Apr 2009 17:55:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=lvoZFgYUU1onmG8qO5p10AAA+fT6J35BeB0mASayiHY=; b=pApo3uRbpn8nBhz2/2q/hsGxXjLXvkweOHLCHY9mm8yshq+SUbdb7WOkcPTr/B1ClB SN05C/Kvua4/8ED75Or1hPVoYR8pT7xbYFS8g/zX16dTjnUXKXdu1rzC0IJLJ2zx9VqJ pnj4oC05wLnikOJ3EdTHWO+Y7BT+NBLhMG5jQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=S6gnO6rlB9SR0qwcuiLjp613Z0hJ2wkNDPF4zX/QBbihyH5rEXqY7QXaQYO4/8hU6W RNLxC4E89LDoCwFAzEgorf5QIq+/qRobiLBAx93jYYs02xkeLzO35iStRBedr995Ush0 zAuIxe+YX1v0vCqiSjXqw4W+vnEQSHPRYQINk= Received: by 10.141.10.1 with SMTP id n1mr3857417rvi.76.1238633728350; Wed, 01 Apr 2009 17:55:28 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id k37sm1359269rvb.28.2009.04.01.17.55.26 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Apr 2009 17:55:27 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Thu, 2 Apr 2009 09:55:03 +0900 From: Pyun YongHyeon Date: Thu, 2 Apr 2009 09:55:03 +0900 To: Marius Strobl Message-ID: <20090402005503.GB19091@michelle.cdnetworks.co.kr> References: <20090401.013246.-1253043078.imp@bsdimp.com> <20090401100939.GB12246@michelle.cdnetworks.co.kr> <20090401211254.GA83780@alchemy.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090401211254.GA83780@alchemy.franken.de> User-Agent: Mutt/1.4.2.3i Cc: "M. Warner Losh" , net@freebsd.org Subject: Re: Small change to ukphy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 00:55:29 -0000 On Wed, Apr 01, 2009 at 11:12:54PM +0200, Marius Strobl wrote: > On Wed, Apr 01, 2009 at 07:09:39PM +0900, Pyun YongHyeon wrote: > > On Wed, Apr 01, 2009 at 01:32:46AM -0600, M. Warner Losh wrote: > > > I've encountered a number of PHY chips that need auto negotiation > > > kicked off to come out of ISO state. This makes sense, because the > > > ukphy driver never seems to take the PHY out of isolation state > > > otherwise. > > > > > > Index: ukphy.c > > > =================================================================== > > > --- ukphy.c (revision 190463) > > > +++ ukphy.c (working copy) > > > @@ -146,6 +146,7 @@ > > > sc->mii_phy = ma->mii_phyno; > > > sc->mii_service = ukphy_service; > > > sc->mii_pdata = mii; > > > + sc->mii_flags |= MIIF_FORCEANEG; > > > > > > mii->mii_instance++; > > > > > > > > > This forces auto negotiation. The reason for this is that it takes it > > > out of ISO state (Isolate). Once out of that state, things work > > > > If the purpose is to take PHY out of isolated state couldn't this > > be handled in ifm_change_cb_t handler of parent interface? I guess > > the callback can reset the PHY and subsequent mii_mediachg() call > > may start auto-negotiation. > > > > > well. The question I have is will we properly go back into ISO state > > > for PHYs that should be isolated. > > > > > > > If the PHY requires special handing for ISO state in reset it may > > need separated PHY driver as ukphy(4) does not set MIIF_NOISOLATE. > > As you said it would be really great if we have a generic way to > > pass various MII flags or driver specific information to mii(4). > > > > > NetBSD has many of its NIC drivers setting this flag. Their APIs > > > allow them to set this directly at mii attach time. Ours don't, so > > > none of our drivers set this flag. > > > > > > The other fix for this might be: > > > Index: mii_physubr.c > > > =================================================================== > > > --- mii_physubr.c (revision 190463) > > > +++ mii_physubr.c (working copy) > > > @@ -113,7 +113,9 @@ > > > int bmcr, anar, gtcr; > > > > > > if (IFM_SUBTYPE(ife->ifm_media) == IFM_AUTO) { > > > - if ((PHY_READ(sc, MII_BMCR) & BMCR_AUTOEN) == 0 || > > > + bmcr = PHY_READ(sc, MII_BMCR); > > > + if ((bmcr & BMCR_AUTOEN) == 0 || > > > + (bmcr & BMCR_ISO) || > > > (sc->mii_flags & MIIF_FORCEANEG)) > > > (void) mii_phy_auto(sc); > > > return; > > > > > > Which says that if auto negotiation is enabled, and ISO is set to go > > > ahead and kick off an auto negotiation. I'm less sure of this path, > > > but it is an alternative. Otherwise, we never write to the BMCR to > > > take the device out of isolation. If there's a better place to do > > > this, then I'm all ears. > > > > > > Either one of these hacks make several PC Cards that I have start to > > > work... In fact, I'm starting to approach 100% (up from 50%) of my > > > ed-based PC Cards working with this simple change (and others to the > > > ed driver). I know that these cards are a little behind the leading > > > edge, but I'd like to get them working since I've put a few hours into > > > investigating things here. > > > > > > Comments? > > > > > FYI, the idea I had for passing MIIF_DOPAUSE from the NIC > drivers to the PHY drivers as required by the flow-control > support without breaking the ABI was to use device flags. > A proof-of-concept patch with an example application of > that approach is: > http://people.freebsd.org/~marius/mii_flags.diff > One could even or the flags together in miibus_attach(), > allowing MIIF_FORCEANEG etc to be additionally set via > hints. > This looks good. As you know some PHY drivers(e.g. brgphy(4), e1000phy(4)) have to know more information than mii flags. How about passing one more pointer argument to mii_probe()? The pointer would be used to point to a driver specific data. From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 08:04:16 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C4041065674 for ; Thu, 2 Apr 2009 08:04:16 +0000 (UTC) (envelope-from upakul@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 47D058FC1B for ; Thu, 2 Apr 2009 08:04:16 +0000 (UTC) (envelope-from upakul@gmail.com) Received: by an-out-0708.google.com with SMTP id d11so286680and.13 for ; Thu, 02 Apr 2009 01:04:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=ejzr7tuP6k+kKqS1yYBNDIEXJzKguh+6FxGwMywEBSM=; b=JRQ2+X6x/DuKg9Sri4zuOCM1ubIVN2+EnR6GsLtV0wOvyiu7LByqyw16wkA9jGBsr8 NcdIKlV/YtOrig8B9rmj9A0eaMe8XSTvZcO7g7EJco4mULMAvSh3zUFzDJZTaW5pVlqL INbNz2nN2KJlUOQazWpstdU/2Bv15sXjVJ2QM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RY3i8LMlYi9x9mU3UxwJ4WuXHJnTYYsoQOElPOTQLzl/jG75SBuKdbrwBTehyYwvAh QjTPSXIoRSzc+Q4PqjnB58w7H44HxgTYz4SJlygXvglBC3Pl8XgxHumlw+DvJLEhnGEZ SkIGkoFaGNgDcpnq6w/0bA6JPrqWzB7wZKkH8= MIME-Version: 1.0 Received: by 10.100.8.4 with SMTP id 4mr8415514anh.81.1238658201371; Thu, 02 Apr 2009 00:43:21 -0700 (PDT) Date: Thu, 2 Apr 2009 13:13:21 +0530 Message-ID: From: Upakul Barkakaty To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Multicast routing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2009 08:04:16 -0000 Hi all, I was trying to setup a multicast tunneling setup with freebsd, with the mrouted utility. However, my multicast router doesnt seem to be forwarding those multicast packets. It would really be helpful if someone could help me with the setup or the mrouted.conf file contents. Thanks in anticipation. -- Regards, Upakul Barkakaty From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 09:38:58 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36EF01065678 for ; Thu, 2 Apr 2009 09:38:58 +0000 (UTC) (envelope-from uebershark@googlemail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id BB4D98FC21 for ; Thu, 2 Apr 2009 09:38:57 +0000 (UTC) (envelope-from uebershark@googlemail.com) Received: by fg-out-1718.google.com with SMTP id 19so698962fgg.12 for ; Thu, 02 Apr 2009 02:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:x-mailer:mime-version:content-type :content-transfer-encoding; bh=rjgleBhBtpcjya8ZqCatpw4DEXF7LMQXIAGA90N7LYc=; b=nDGxIHNNkhxpFE2BOFC7yYD0LMpvmvDxzVgRmnVGrTnBTwKujAH2Qb4/N6lzAv9J7I bQzg8pFADyZ6V7j/bv4J6rbdHwdzmVZ4NcTfSqh0tLc+uMEcvmJHJ9d15uwTcbrnQCYk sboiWGZn8wFXS8jLq+OZ8vXt5bERUSW+hXv6c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type :content-transfer-encoding; b=fTL8TQG58hIBsePAXVVK/JeGBTnpfBjOMCk0lmTZ7FHBi+dKsyxh8DiJLbnh9xMnU9 WOPlF9WrVR8uv2PYghd7KUTGDoIO9wy3ts7qoPYdE3aGfuB0fZF7LBADLHiowjm012TW Dcv4PTZP2bguBV7gU6X5YJKZyjEKFkITAteec= Received: by 10.86.76.16 with SMTP id y16mr4141915fga.35.1238663451909; Thu, 02 Apr 2009 02:10:51 -0700 (PDT) Received: from ViciousVincent ([78.52.201.8]) by mx.google.com with ESMTPS id 25sm603599fxm.24.2009.04.02.02.10.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Apr 2009 02:10:51 -0700 (PDT) Date: Thu, 2 Apr 2009 11:10:50 +0200 From: Tom To: freebsd-net@freebsd.org Message-ID: <20090402111050.625a5d35@ViciousVincent> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.14.7; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FreeBSD and ULI M526x NI X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2009 09:38:59 -0000 Hi, Is the ULI M526x NIC somehow supported in Free-or any other BSD? If so, how do I go about installing support for it, without a working internet connection? The m526x belongs to the 'tulip'-family with the linux-kernel. Thanks for any pointers! Tom From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 22:46:40 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 729A4106564A for ; Thu, 2 Apr 2009 22:46:40 +0000 (UTC) (envelope-from erich@fuujingroup.com) Received: from fluorine.fuujinnetworks.com (fluorine.fuujinnetworks.com [64.90.67.234]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE218FC1A for ; Thu, 2 Apr 2009 22:46:40 +0000 (UTC) (envelope-from erich@fuujingroup.com) Received: from [10.168.1.8] (copper.fuujinnetworks.com [64.90.67.254]) by fluorine.fuujinnetworks.com (Postfix) with ESMTPA id 99BFC43B26C for ; Thu, 2 Apr 2009 17:30:08 -0500 (CDT) Message-ID: <49D54989.3010905@fuujingroup.com> Date: Thu, 02 Apr 2009 17:26:01 -0600 From: Erich Jenkins User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: IPF, IPNAT and Kernel Panic?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 22:46:40 -0000 I've a FreeBSD 7.0 box in a production environment, now doing spurious things. I've tried this on two servers with the same config (thinking there was a possible hardware issue). As it turns out, I see the same kernel panic and reboot no matter what I run this on. Every so often (perhaps once or twice daily) this box will panic, reboot and cause many people to call me at once to threaten my man bits... Currently: FreeBSD 7.0 Stable i386 kernel The firewall kernel modules are loaded on boot and are not compiled in. IPFilter is doing the firewall work on the public interfaces. IPNAT is doing NAT for the subnets behind this box on and port mapping. This machine is a 2GHz AMD-64bit box (being used as a 32bit) with a gig of ram and some Intel 10/100 NICs. I see the same thing on Intel x86 hardware, so I don't know this to be platform dependent. Here's some KGDB BT info: [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc387f94b stack pointer = 0x28:0xdceb59c8 frame pointer = 0x28:0xdceb5a44 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 26 (irq23: vr0) trap number = 12 panic: page fault cpuid = 0 Uptime: 18h43m50s Physical memory: 742 MB Dumping 113 MB: 98 82 66 50 34 18 2 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc05ba397 in boot (howto=260) at ../../../kern/kern_shutdown.c:409 #2 0xc05ba659 in panic (fmt=Variable "fmt" is not available. ) at ../../../kern/kern_shutdown.c:563 #3 0xc080307c in trap_fatal (frame=0xdceb5988, eva=4) at ../../../i386/i386/trap.c:899 #4 0xc08032e0 in trap_pfault (frame=0xdceb5988, usermode=0, eva=4) at ../../../i386/i386/trap.c:812 #5 0xc0803c62 in trap (frame=0xdceb5988) at ../../../i386/i386/trap.c:490 #6 0xc07ea5eb in calltrap () at ../../../i386/i386/exception.s:139 #7 0xc387f94b in ?? () Previous frame inner to this frame (corrupt stack?) Here's the kernel info: cpu I686_CPU ident KNL0329 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing # To make an SMP kernel, the next two lines are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC # CPU frequency control device cpufreq # Bus support. device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device le # AMD Am7900 LANCE and Am79C9xx PCnet device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device lge # Level 1 LXT1001 gigabit Ethernet device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet device nfe # nVidia nForce MCP on-board Ethernet device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet Networking device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device stge # Sundance/Tamarack TC9021 gigabit Ethernet device ti # Alteon Networks Tigon I/II gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit Ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) device firmware # firmware assist module device bpf # Berkeley packet filter Any help or thoughts would be greatly appreciated! Erich From owner-freebsd-net@FreeBSD.ORG Thu Apr 2 22:57:32 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DC05106564A for ; Thu, 2 Apr 2009 22:57:32 +0000 (UTC) (envelope-from kfl@xiplink.com) Received: from smtp181.iad.emailsrvr.com (smtp181.iad.emailsrvr.com [207.97.245.181]) by mx1.freebsd.org (Postfix) with ESMTP id 376C78FC12 for ; Thu, 2 Apr 2009 22:57:32 +0000 (UTC) (envelope-from kfl@xiplink.com) Received: from relay18.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay18.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id 541141B4044 for ; Thu, 2 Apr 2009 18:47:25 -0400 (EDT) Received: by relay18.relay.iad.mlsrvr.com (Authenticated sender: kfodil-lemelin-AT-xiplink.com) with ESMTPSA id 3F4091B402C for ; Thu, 2 Apr 2009 18:47:25 -0400 (EDT) Message-ID: <49D54083.5060504@xiplink.com> Date: Thu, 02 Apr 2009 18:47:31 -0400 From: Karim Fodil-Lemelin User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 7.1 Crash dump with WITNESS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Apr 2009 22:57:32 -0000 Hi, I got this crash while running tcpdump and saving to a file. I can't reproduce it consistently but perhaps someone can give me some pointers on how to fix this. It looks like the witness code is in some infinite loop and that get stopped by an MPASS check. (kgdb) bt #0 kdb_enter_why (why=0xc092cefd "panic", msg=0xc092cefd "panic") at ../../../kern/subr_kdb.c:316 #1 0xc06a69c6 in panic (fmt=0xc091345b "Assertion %s failed at %s:%d") at ../../../kern/kern_shutdown.c:557 #2 0xc06e1e22 in isitmydescendant (parent=0xc0a2a208, child=0xc0a2c468) at ../../../kern/subr_witness.c:1634 #3 0xc06e1e33 in isitmydescendant (parent=0xc0a2ac80, child=0xc0a2c468) at ../../../kern/subr_witness.c:1636 #4 0xc06e1e33 in isitmydescendant (parent=0xc0a2abe0, child=0xc0a2c468) at ../../../kern/subr_witness.c:1636 #5 0xc06e1e33 in isitmydescendant (parent=0xc0a2ac08, child=0xc0a2c468) at ../../../kern/subr_witness.c:1636 #6 0xc06e3f82 in witness_checkorder (lock=0xca37c2d0, flags=Variable "flags" is not available. ) at ../../../kern/subr_witness.c:1019 #7 0xc0698705 in _mtx_lock_flags (m=0xca37c2d0, opts=0, file=0xc091253f "../../../dev/e1000/if_em.c", line=1136) at ../../../kern/kern_mutex.c:183 #8 0xc0527f18 in em_ioctl (ifp=0xca394c00, command=2149607696, data=0xf572fa04 ",\226\2235\226\2230rU:n\003\210@") at ../../../dev/e1000/if_em.c:1136 #9 0xc073eb91 in if_setflag (ifp=0xca394c00, flag=256, pflag=131072, refcount=0xca394c44, onswitch=0) at ../../../net/if.c:2098 #10 0xc073ec6a in ifpromisc (ifp=0xca394c00, pswitch=0) at ../../../net/if.c:2125 #11 0xc0738083 in bpf_detachd (d=0xcb262f00) at ../../../net/bpf.c:379 #12 0xc0739664 in bpfclose (dev=0xcb0ddd00, flags=3, fmt=8192, td=0xcb087230) at ../../../net/bpf.c:452 #13 0xc0633845 in devfs_close (ap=0xf572fb30) at ../../../fs/devfs/devfs_vnops.c:460 #14 0xc08d0306 in VOP_CLOSE_APV (vop=0xc09c52c0, a=0xf572fb30) at vnode_if.c:415 #15 0xc073427b in vn_close (vp=0xcb27f420, flags=3, file_cred=0xcb279300, td=0xcb087230) at vnode_if.h:228 #16 0xc0734389 in vn_closefile (fp=0xcaae44c0, td=0xcb087230) at ../../../kern/vfs_vnops.c:867 #17 0xc0630b9c in devfs_close_f (fp=0xcaae44c0, td=0xcb087230) at ../../../fs/devfs/devfs_vnops.c:479 #18 0xc0675a79 in fdrop (fp=0xcaae44c0, td=0xcb087230) at file.h:299 #19 0xc06777b9 in closef (fp=0xcaae44c0, td=0xcb087230) at ../../../kern/kern_descrip.c:2033 #20 0xc0677b67 in kern_close (td=0xcb087230, fd=3) ---Type to continue, or q to quit--- at ../../../kern/kern_descrip.c:1125 #21 0xc0677bff in close (td=0xcb087230, uap=0xf572fcfc) at ../../../kern/kern_descrip.c:1077 #22 0xc08c3cdf in syscall (frame=0xf572fd38) at ../../../i386/i386/trap.c:1076 #23 0xc08aa9fa in Xlcall_syscall () at ../../../i386/i386/exception.s:229 #24 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) up #1 0xc06a69c6 in panic (fmt=0xc091345b "Assertion %s failed at %s:%d") at ../../../kern/kern_shutdown.c:557 557 kdb_enter_why(KDB_WHY_PANIC, "panic"); (kgdb) #2 0xc06e1e22 in isitmydescendant (parent=0xc0a2a208, child=0xc0a2c468) at ../../../kern/subr_witness.c:1634 1634 MPASS(j < 1000); (kgdb) p j $1 = 1000 (kgdb) (kgdb) p *child $2 = {w_name = 0xc0932551 "bpf global lock", w_class = 0xc09ceb04, w_list = { stqe_next = 0xc0a2c490}, w_typelist = {stqe_next = 0xc0a2c490}, w_children = 0xc0a4c640, w_file = 0xc0939635 "net/bpf.c", w_line = 452, w_level = 0, w_refcount = 2, w_Giant_squawked = 0 '\0', w_other_squawked = 0 '\0', w_same_squawked = 0 '\0', w_displayed = 0 '\0'} Anyone that can shed some light on this? Btw I've never witnessed that crash without WITNESS on ;). Thanks! Karim. From owner-freebsd-net@FreeBSD.ORG Sat Apr 4 13:50:55 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58206106566C; Sat, 4 Apr 2009 13:50:55 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id DA5EE8FC08; Sat, 4 Apr 2009 13:50:54 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: by yw-out-2324.google.com with SMTP id 5so937881ywh.13 for ; Sat, 04 Apr 2009 06:50:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:cc :references:subject:date:mime-version:content-type:x-priority :x-msmail-priority:x-mailer:x-mimeole; bh=FCy2s6oTYy9DURkn7q+ZS9ok1C30yvlc/2JJq4e5bWM=; b=fEzBULV1XX6jpT11bhevfEVXW1Q5+0LrT11bk1H3T+z1OKgxf8DgvteaMsvYVxQTY7 Vso7+pdEIOOyJz07LMj8LAc6ukLuvPH6ump1jFLK/fQiWDIn4OWzJSuSXMui9eXoMGhp t/Bab1fCT9ROr+6jc2eCgzLESYYjeGiqezing= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:subject:date:mime-version :content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=RwTH1JH94qblV1hNaa8JEK2ZzFNc/HOXwC6WPJvI8ONzFp709KqlzNNXWRUQUVbg67 4qlJN/xAL2Ry+ryvO7dUySbh/J3/WUWeHiLyG3V6KB2e4BpLxeawv488Ihb9NRlik6Eq k5+1ZXmvFYIY5ut+R7qxgM5VyNbLqddPA/yzI= Received: by 10.90.118.19 with SMTP id q19mr1452569agc.93.1238851327358; Sat, 04 Apr 2009 06:22:07 -0700 (PDT) Received: from adnote989 (201-42-151-145.dsl.telesp.net.br [201.42.151.145]) by mx.google.com with ESMTPS id 30sm4117257agc.49.2009.04.04.06.22.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Apr 2009 06:22:06 -0700 (PDT) Message-ID: <3F89BC6021844DC58B956E5433650445@adnote989> From: "Luiz Otavio O Souza" To: "Julian Elischer" References: <3FD46C21A487490FB15B89E890790121@adnote989> <49d5c0de.E5bkeKr+p+fg4K00%perryh@pluto.rain.com> <64D5D9E633734200A603D067ED5A81E9@adnote989> <49D63315.6050108@elischer.org> Date: Sat, 4 Apr 2009 10:21:38 -0300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01BF_01C9B50F.239BA6B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Mailman-Approved-At: Sat, 04 Apr 2009 15:55:17 +0000 Cc: Lawrence Stewart , freebsd-net@freebsd.org Subject: Re: Setting the mss for 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: Sat, 04 Apr 2009 13:50:55 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_01BF_01C9B50F.239BA6B0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit > Luiz Otavio O Souza wrote: >>>> Is there a way to set the mss for a socket ? Like you can do >>>> in linux with setsockopt(TCP_MAXSEG) ? >>>> >>>> So i can set the maximum size of packets (or sort of) from a >>>> simple userland program. >>> >>> Depending on exactly what you need to accomplish, you may >>> find something useful in this thread from last August in >>> freebsd-questions@ >>> >>> setting the other end's TCP segment size >> >> Very informative thread, thanks. >> >> This thread show me that TCP_MAXSEG is implemented in freebsd but don't >> work. You can set the setsockopt(IPPROTO_TCP, TCP_MAXSEG), wich will set >> the >> tp->t_maxseg, but this value is recalculated at tcp_input, so in short, >> you >> cannot set the max segment size for a socket. >> >> I've posted a completly wrong patch (from style point-of-view - and using >> SOL_SOCKET instead of IPPROTO_TCP), but with that patch i'm able to set >> the >> mss in iperf. > > this thread shoud be in FreeBSD-net@ so tha the right people see it > many developers do not read hackers every day as it tends to overload > them. The above patch is a better fix for this, it fix the setsockopt(IPPROTO_TCP, TCP_MAXSEG), so iperf (and other userland programs) works by default. It's clear on code that tp->t_maxseg should not be changed, at least in this situation (it keeps the maximum mss for connection and it is used to calculate the tcp window scaling). tp->t_maxseg is also reseted to maxmtu (or rmx_mtu) at tcp_mss_update(). So here is the patch: http://loos.no-ip.org/downloads/mss-patch Thanks Luiz ------=_NextPart_000_01BF_01C9B50F.239BA6B0 Content-Type: text/plain; format=flowed; name="mss-patch.txt"; reply-type=response Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="mss-patch.txt" --- netinet/socketvar.h.orig 2009-04-03 22:29:34.000000000 -0300=0A= +++ netinet/socketvar.h 2009-04-03 22:29:44.000000000 -0300=0A= @@ -115,6 +115,7 @@=0A= char *so_accept_filter_str; /* saved user args */=0A= } *so_accf;=0A= int so_fibnum; /* routing domain for this socket */=0A= + int so_maxseg; /* maxseg this socket */=0A= };=0A= =0A= /*=0A= --- netinet/tcp_usrreq.c.orig 2009-04-03 22:24:53.000000000 -0300=0A= +++ netinet/tcp_usrreq.c 2009-04-03 23:26:35.000000000 -0300=0A= @@ -1352,9 +1352,8 @@=0A= return (error);=0A= =0A= INP_WLOCK_RECHECK(inp);=0A= - if (optval > 0 && optval <=3D tp->t_maxseg &&=0A= - optval + 40 >=3D V_tcp_minmss)=0A= - tp->t_maxseg =3D optval;=0A= + if (optval >=3D 40 && optval <=3D tp->t_maxseg)=0A= + so->so_maxseg =3D optval;=0A= else=0A= error =3D EINVAL;=0A= INP_WUNLOCK(inp);=0A= @@ -1389,7 +1388,10 @@=0A= error =3D sooptcopyout(sopt, &optval, sizeof optval);=0A= break;=0A= case TCP_MAXSEG:=0A= - optval =3D tp->t_maxseg;=0A= + if (so->so_maxseg)=0A= + optval =3D so->so_maxseg;=0A= + else=0A= + optval =3D tp->t_maxseg;=0A= INP_WUNLOCK(inp);=0A= error =3D sooptcopyout(sopt, &optval, sizeof optval);=0A= break;=0A= --- netinet/tcp_output.c.orig 2009-04-02 22:48:04.000000000 -0300=0A= +++ netinet/tcp_output.c 2009-04-03 23:28:07.000000000 -0300=0A= @@ -493,6 +493,11 @@=0A= }=0A= }=0A= =0A= + if (so->so_maxseg && len > so->so_maxseg) {=0A= + len =3D so->so_maxseg;=0A= + sendalot =3D 1;=0A= + }=0A= +=0A= if (sack_rxmit) {=0A= if (SEQ_LT(p->rxmit + len, tp->snd_una + so->so_snd.sb_cc))=0A= flags &=3D ~TH_FIN;=0A= @@ -518,6 +523,8 @@=0A= if (len) {=0A= if (len >=3D tp->t_maxseg)=0A= goto send;=0A= + if (so->so_maxseg && len >=3D so->so_maxseg)=0A= + goto send;=0A= /*=0A= * NOTE! on localhost connections an 'ack' from the remote=0A= * end may occur synchronously with the output and cause=0A= ------=_NextPart_000_01BF_01C9B50F.239BA6B0--