From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 02:20:51 2011 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 CDEE7106564A; Sun, 13 Feb 2011 02:20:51 +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 A2E458FC12; Sun, 13 Feb 2011 02:20:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1D2KpaG081579; Sun, 13 Feb 2011 02:20:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1D2KptY081569; Sun, 13 Feb 2011 02:20:51 GMT (envelope-from linimon) Date: Sun, 13 Feb 2011 02:20:51 GMT Message-Id: <201102130220.p1D2KptY081569@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154676: [netgraph] [panic] HEAD, 8.1-RELEASE panic after some play with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2011 02:20:51 -0000 Old Synopsis: HEAD, 8.1-RELEASE panic after some play with netgraph New Synopsis: [netgraph] [panic] HEAD, 8.1-RELEASE panic after some play with netgraph Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Feb 13 02:20:33 UTC 2011 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=154676 From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 07:40:11 2011 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 7F2591065673 for ; Sun, 13 Feb 2011 07:40:11 +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 5559A8FC12 for ; Sun, 13 Feb 2011 07:40:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1D7eBcW051053 for ; Sun, 13 Feb 2011 07:40:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1D7eBk7051052; Sun, 13 Feb 2011 07:40:11 GMT (envelope-from gnats) Date: Sun, 13 Feb 2011 07:40:11 GMT Message-Id: <201102130740.p1D7eBk7051052@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Arnaud Lacombe Cc: Subject: Re: kern/154676: [netgraph] [panic] HEAD, 8.1-RELEASE panic after some play with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Arnaud Lacombe List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2011 07:40:11 -0000 The following reply was made to PR kern/154676; it has been noted by GNATS. From: Arnaud Lacombe To: bug-followup@FreeBSD.org, sergey.dyatko@gmail.com Cc: Subject: Re: kern/154676: [netgraph] [panic] HEAD, 8.1-RELEASE panic after some play with netgraph Date: Sun, 13 Feb 2011 02:03:34 -0500 Playing a bit with that bug; an INVARIANTS-enabled kernel (9-CURRENT) crashes with: panic: ng_snd_item: no mbuf packet header! because the mbuf returned by soreceive() does not have M_PKTHDR set, while the expected data is present in the mbuf. 7.1 does set the flag: Adding an m_print() right after soreceive() in ng_ksocket_incoming2() gives: FreeBSD -current (on 127.0.0.1:25): mbuf: 0xc1d7b200 len: 81, next: 0, 0, 32-32-30-... FreeBSD 7.1 (on 127.0.0.1:22) mbuf: 0xc6d47400 len: 40, next: 0, 2, 53-53-48-... both stack uses soreceive_generic(), From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 09:30:10 2011 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 60FD31065694 for ; Sun, 13 Feb 2011 09:30:10 +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 3557D8FC12 for ; Sun, 13 Feb 2011 09:30:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1D9UAlu073239 for ; Sun, 13 Feb 2011 09:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1D9UA0b073232; Sun, 13 Feb 2011 09:30:10 GMT (envelope-from gnats) Date: Sun, 13 Feb 2011 09:30:10 GMT Message-Id: <201102130930.p1D9UA0b073232@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Arnaud Lacombe Cc: Subject: [debugged] Re: kern/154676: [netgraph] [panic] HEAD, 8.1-RELEASE panic after some play with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Arnaud Lacombe List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2011 09:30:10 -0000 The following reply was made to PR kern/154676; it has been noted by GNATS. From: Arnaud Lacombe To: bug-followup@FreeBSD.org, sergey.dyatko@gmail.com, =?ISO-8859-1?Q?Andr=E9_Oppermann?= Cc: Subject: [debugged] Re: kern/154676: [netgraph] [panic] HEAD, 8.1-RELEASE panic after some play with netgraph Date: Sun, 13 Feb 2011 04:29:58 -0500 [Adding andre@, see below] I think I narrowed this down to right after the call to sbappendstream_locked() in netinet/tcp_input.c:tcp_do_segment(), line 2713. On 7.1, the mbuf has its M_PKTHDR set. It is not set in -current. However, the mbuf passed to tcp_do_segment() has the flag set (enforced by M_ASSERTPKTHDR(m)), so it should have been lost in-between. [...] ... of course ...sbappendstream_locked() of 7.1 has no call to m_demote(). I suppose that ng_ksocket will work again if I remove the call. [...] Yes it does... For the record, this call has been introduced in: commit ec3cce1383deb16282c3576cc3dc2f3bb1ba9375 Author: andre Date: Mon Jun 22 21:46:40 2009 +0000 In sbappendstream_locked() demote all incoming packet mbufs (and chains) to pure data mbufs using m_demote(). This removes the packet header and all m_tag information as they are not meaningful anymore on a stream socket where mbufs are linked through m->m_next. Strictly speaking a packet header can be only ever valid on the first mbuf in an m_next chain. sbcompress() was doing this already when the mbuf chain layout lent itself to it (e.g. header splitting or merge-append), just not consistently. This frees resources at socket buffer append time instead of at sbdrop_internal() time after data has been read from the socket. For MAC the per packet information has done its duty and during socket buffer appending the policy of the socket itself takes over. With the append the packet boundaries disappear naturally and with it any context that was based on it. None of the residual information from mbuf headers in the socket buffer on stream sockets was looked at. From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 10:42:08 2011 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 6DDAC106566B for ; Sun, 13 Feb 2011 10:42:08 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 51E2C8FC0C for ; Sun, 13 Feb 2011 10:42:08 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta05.emeryville.ca.mail.comcast.net with comcast id 7Ni71g0080QkzPwA5Ni7cP; Sun, 13 Feb 2011 10:42:07 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta02.emeryville.ca.mail.comcast.net with comcast id 7Ni61g00P0PUQVN8NNi7LJ; Sun, 13 Feb 2011 10:42:07 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B86B19B422; Sun, 13 Feb 2011 02:42:06 -0800 (PST) Date: Sun, 13 Feb 2011 02:42:06 -0800 From: Jeremy Chadwick To: freebsd-net@freebsd.org Message-ID: <20110213104206.GA2524@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Routing between two physical networks X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2011 10:42:08 -0000 (Please keep me CC'd, as I'm not subscribed to freebsd-net) I'm having some complexity handling 3 separate networks on the same physical box, which also acts as a gateway. NAT (pf) is involved, but only for packets going out the external interface (em0). The simple version is that two of the local (physical) networks can't talk. Before I provide details, please keep in mind I *do not* want to use bridge(4) to solve this problem. I have tried it -- yes it works as expected -- but I'm trying hard to avoid use of it. OS: amd64 FreeBSD 8.2-PRERELEASE #0: Sat Feb 12 06:13:55 PST 2011 Physical topology and physical interfaces: +-------------+ | |== em0 <---> cable modem <---> Internet | FreeBSD Box |== em1 <---> switch <---> PC#1 | |== wlan0 <---> printer +-------------+ FreeBSD em0 = public Internet IP address FreeBSD em1 = 192.168.1.1 netmask 0xffffff00 FreeBSD wlan0 = 192.168.200.1 netmask 0xffffff00 PC#1 = 192.168.1.50 netmask 0xffffff00 gateway 192.168.1.1 printer = 192.168.200.101 netmask 0xffffff00 gateway 192.168.1.1 Situation: - PC#1 can talk to the FreeBSD box (as 192.168.1.1 or 192.168.200.1) - printer can talk to the FreeBSD box (as 192.168.200.1 or 192.168.1.1) - PC#1 can reach the Internet - PC#1 **cannot** talk to printer, nor vice-versa The last item is what I'm trying to fix. Packets from PC#1 -> Internet are NAT'd using the following pf statements: ext_if="em0" int_if="em1" nat on $ext_if from $int_if:network to any -> ($ext_if) gateway_enable="yes" is obviously set in rc.conf. traceroute from PC#1 to printer shows hop #1 as 192.168.1.1, then indefinite timeouts. When PC#1 pings the printer, "tcpdump -p -i em1 -l -n icmp" from the FreeBSD box shows ICMP ECHO requests from 192.168.1.50 to 192.168.200.101, but no reply. When doing "tcpdump -p -i wlan0 -l -n icmp", the exact same packets as above are seen. I'd love for someone to explain this to me. :-) When doing "tcpdump -p -i em0 -l -n icmp", nothing is seen, so I imagine the packets destined for 192.168.200.101 aren't going out the Internet. I've tried changing the printer's gateway to 192.168.200.1 but that has no effect either. My pf.conf has "set skip on wlan0" and "set skip on em1", so I'm not exactly sure where the packets are disappearing, and am inclined to think it's a routing table issue. I can put up my configuration bits (rc.conf, pf.conf) as well as "ifconfig -a", "netstat -rn", etc. if someone would like to see them (I imagine so), just let me know. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 11:11:36 2011 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 2E70210656CC for ; Sun, 13 Feb 2011 11:11:36 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 107708FC13 for ; Sun, 13 Feb 2011 11:11:35 +0000 (UTC) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta08.emeryville.ca.mail.comcast.net with comcast id 7P8t1g0010b6N64A8PBbWJ; Sun, 13 Feb 2011 11:11:35 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta03.emeryville.ca.mail.comcast.net with comcast id 7PBa1g0080PUQVN8PPBbnx; Sun, 13 Feb 2011 11:11:35 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B953A9B422; Sun, 13 Feb 2011 03:11:34 -0800 (PST) Date: Sun, 13 Feb 2011 03:11:34 -0800 From: Jeremy Chadwick To: freebsd-net@freebsd.org Message-ID: <20110213111134.GA4689@icarus.home.lan> References: <20110213104206.GA2524@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110213104206.GA2524@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Routing between two physical networks X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2011 11:11:36 -0000 As usual, it's something simple. :-) Nikos Vassiliadis contacted me off-list to tell me that the gateway chosen for the printer (192.168.1.1) was incorrect (should have been 192.168.200.1). Once I fixed that, things worked fine. Makes perfect sense. That's what I get for copy-pasting lines in my dhcpd.conf file when making a new "subnet" section... -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | On Sun, Feb 13, 2011 at 02:42:06AM -0800, Jeremy Chadwick wrote: > (Please keep me CC'd, as I'm not subscribed to freebsd-net) > > I'm having some complexity handling 3 separate networks on the same > physical box, which also acts as a gateway. NAT (pf) is involved, but > only for packets going out the external interface (em0). The simple > version is that two of the local (physical) networks can't talk. > > Before I provide details, please keep in mind I *do not* want to use > bridge(4) to solve this problem. I have tried it -- yes it works as > expected -- but I'm trying hard to avoid use of it. > > OS: amd64 FreeBSD 8.2-PRERELEASE #0: Sat Feb 12 06:13:55 PST 2011 > > Physical topology and physical interfaces: > > +-------------+ > | |== em0 <---> cable modem <---> Internet > | FreeBSD Box |== em1 <---> switch <---> PC#1 > | |== wlan0 <---> printer > +-------------+ > > FreeBSD em0 = public Internet IP address > FreeBSD em1 = 192.168.1.1 netmask 0xffffff00 > FreeBSD wlan0 = 192.168.200.1 netmask 0xffffff00 > PC#1 = 192.168.1.50 netmask 0xffffff00 gateway 192.168.1.1 > printer = 192.168.200.101 netmask 0xffffff00 gateway 192.168.1.1 > > Situation: > > - PC#1 can talk to the FreeBSD box (as 192.168.1.1 or 192.168.200.1) > - printer can talk to the FreeBSD box (as 192.168.200.1 or 192.168.1.1) > - PC#1 can reach the Internet > - PC#1 **cannot** talk to printer, nor vice-versa > > The last item is what I'm trying to fix. > > Packets from PC#1 -> Internet are NAT'd using the following pf > statements: > > ext_if="em0" > int_if="em1" > nat on $ext_if from $int_if:network to any -> ($ext_if) > > gateway_enable="yes" is obviously set in rc.conf. > > traceroute from PC#1 to printer shows hop #1 as 192.168.1.1, then > indefinite timeouts. > > When PC#1 pings the printer, "tcpdump -p -i em1 -l -n icmp" from the > FreeBSD box shows ICMP ECHO requests from 192.168.1.50 to > 192.168.200.101, but no reply. > > When doing "tcpdump -p -i wlan0 -l -n icmp", the exact same packets as > above are seen. I'd love for someone to explain this to me. :-) > > When doing "tcpdump -p -i em0 -l -n icmp", nothing is seen, so I imagine > the packets destined for 192.168.200.101 aren't going out the Internet. > > I've tried changing the printer's gateway to 192.168.200.1 but that has > no effect either. > > My pf.conf has "set skip on wlan0" and "set skip on em1", so I'm not > exactly sure where the packets are disappearing, and am inclined to > think it's a routing table issue. > > I can put up my configuration bits (rc.conf, pf.conf) as well as > "ifconfig -a", "netstat -rn", etc. if someone would like to see them (I > imagine so), just let me know. > > -- > | Jeremy Chadwick jdc@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP 4BD6C0CB | > From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 14:50:10 2011 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 6D024106566B for ; Sun, 13 Feb 2011 14:50:10 +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 5B8218FC18 for ; Sun, 13 Feb 2011 14:50:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1DEoAcx019321 for ; Sun, 13 Feb 2011 14:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1DEoAWr019319; Sun, 13 Feb 2011 14:50:10 GMT (envelope-from gnats) Date: Sun, 13 Feb 2011 14:50:10 GMT Message-Id: <201102131450.p1DEoAWr019319@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Mark Linimon Cc: Subject: kern/152141: [vlan] encapsulate vlan in ng_ether before output to if X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2011 14:50:10 -0000 The following reply was made to PR kern/152141; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: kern/152141: [vlan] encapsulate vlan in ng_ether before output to if Date: Sun, 13 Feb 2011 08:46:38 -0600 ----- Forwarded message from Rozhuk Ivan ----- From: "Rozhuk Ivan" To: Subject: kern/152141: [vlan] encapsulate vlan in ng_ether before output to if Date: Tue, 16 Nov 2010 01:16:48 +0800 This is a patched version of original function code /* * If underlying interface can not do VLAN tag insertion itself * then attach a packet tag that holds it. */ if ((m->m_flags & M_VLANTAG) && (ifp->if_capenable & IFCAP_VLAN_HWTAGGING) == 0) { m = ether_vlanencap(m, m->m_pkthdr.ether_vtag); if (m == NULL) { ifp->if_oerrors++; return (ENOBUFS); } m->m_flags &= ~M_VLANTAG; } was added. Iam does not test this path - haven’t net with vlan support. Code was taken from if_bridge and adapted.   -- Rozhuk Ivan ----- End forwarded message ----- From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 18:37:26 2011 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 96CD31065672 for ; Sun, 13 Feb 2011 18:37:26 +0000 (UTC) (envelope-from garth_gillespie@hotmail.com) Received: from col0-omc2-s10.col0.hotmail.com (col0-omc2-s10.col0.hotmail.com [65.55.34.84]) by mx1.freebsd.org (Postfix) with ESMTP id 77A5B8FC15 for ; Sun, 13 Feb 2011 18:37:26 +0000 (UTC) Received: from COL115-W49 ([65.55.34.72]) by col0-omc2-s10.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 13 Feb 2011 10:24:09 -0800 Message-ID: X-Originating-IP: [98.117.124.211] From: Garth Gillespie To: Date: Sun, 13 Feb 2011 10:24:09 -0800 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 13 Feb 2011 18:24:09.0275 (UTC) FILETIME=[349D20B0:01CBCBAB] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Bonjour/mDNSResponder and IPv6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2011 18:37:26 -0000 I've also posted this in the FreeNAS forum=2C but hoping I'll have more luc= k here. FreeNAS is built on FreeBSD. -- I've been working on this for a few days and am about ready to throw in the= towel.Running FreeNAS 0.7.2.5543 (So based on FreeBSD 7.2) on a USB Flash = drive. AFP and SMB working fine.What I wanted to do was enable AFP over IPv= 6 and then also have Bonjour (mDNSResponderPosix) also advertise the IPv6 l= ocations into Mac Finder's sidebar.So I installed FreeBSD onto a VM to use = as a build machine=2C first compiled netatalk 2.1.5=2C moved the relevent b= its over to FreeNAS and with addition of the -ipaddr my:v6:address:: I was = able to connect to my AFP shares with Command-K -- afp://[my:v6:address::].= That was all fine.The problem is in the Finder sidebar=2C the advertised s= ervices are still just IPv4. I downloaded Bonjour Browser and from my Apple= devices=2C I can see various services listed with both IPv4 and IPv6 addre= sses - from FreeNAS - only the IPv4 address is broadcast.So then=2C on my F= reeBSD build machine=2C I setup a basic mdnsresonder.conf for ssh=2C and ra= n the same binary and from the build machine it also only broadcasts the IP= v4 address not both IPv4 and IPv6 and ssh is listening on both IPv4 and IPv= 6 - I can ssh to the build machine over IPv4 or IPv6.So this isn't just a F= reeNAS issue but a FreeBSD issue - but I think it should be possible since = I can see all my apple devices happily broadcasting both IPv4 and IPv6 addr= ess for a given named service.Anyone have any insight? = From owner-freebsd-net@FreeBSD.ORG Mon Feb 14 08:20:11 2011 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 97C38106566C for ; Mon, 14 Feb 2011 08:20:11 +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 69B628FC1B for ; Mon, 14 Feb 2011 08:20:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1E8KB8o093439 for ; Mon, 14 Feb 2011 08:20:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1E8KBlB093432; Mon, 14 Feb 2011 08:20:11 GMT (envelope-from gnats) Date: Mon, 14 Feb 2011 08:20:11 GMT Message-Id: <201102140820.p1E8KBlB093432@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/153938: commit references a PR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2011 08:20:11 -0000 The following reply was made to PR kern/153938; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/153938: commit references a PR Date: Mon, 14 Feb 2011 08:14:15 +0000 (UTC) Author: hselasky Date: Mon Feb 14 08:14:06 2011 New Revision: 218676 URL: http://svn.freebsd.org/changeset/base/218676 Log: * Fix page fault caused by referring freed node. While updating Tx stats, already freed node could be referred and cause page fault. To avoid such panic, spool Tx stats in driver's softc. Then, on every ratectl interval, grab node though ieee80211_iterate_nodes() and update ratectl stats. * Simplify some code in run_iter_func(). * Fix typo * Use memset instead of bzero (hselasky @) PR: kern/153938 Submitted by: PseudoCylon Approved by: thompsa (mentor) Modified: head/sys/dev/usb/wlan/if_run.c head/sys/dev/usb/wlan/if_runreg.h head/sys/dev/usb/wlan/if_runvar.h Modified: head/sys/dev/usb/wlan/if_run.c ============================================================================== --- head/sys/dev/usb/wlan/if_run.c Mon Feb 14 08:09:02 2011 (r218675) +++ head/sys/dev/usb/wlan/if_run.c Mon Feb 14 08:14:06 2011 (r218676) @@ -1684,7 +1684,7 @@ run_read_eeprom(struct run_softc *sc) return (0); } -struct ieee80211_node * +static struct ieee80211_node * run_node_alloc(struct ieee80211vap *vap, const uint8_t mac[IEEE80211_ADDR_LEN]) { return malloc(sizeof (struct run_node), M_DEVBUF, M_NOWAIT | M_ZERO); @@ -1787,7 +1787,6 @@ run_newstate(struct ieee80211vap *vap, e } break; - case IEEE80211_S_RUN: if (!(sc->runbmap & bid)) { if(sc->running++) @@ -2229,10 +2228,10 @@ run_drain_fifo(void *arg) { struct run_softc *sc = arg; struct ifnet *ifp = sc->sc_ifp; - struct ieee80211_node *ni = sc->sc_ni[0]; /* make compiler happy */ uint32_t stat; - int retrycnt = 0; + uint16_t (*wstat)[3]; uint8_t wcid, mcs, pid; + int8_t retry; RUN_LOCK_ASSERT(sc, MA_OWNED); @@ -2250,31 +2249,32 @@ run_drain_fifo(void *arg) wcid == 0) continue; - ni = sc->sc_ni[wcid]; - if (ni->ni_rctls == NULL) - continue; - - /* update per-STA AMRR stats */ - if (stat & RT2860_TXQ_OK) { - /* - * Check if there were retries, ie if the Tx - * success rate is different from the requested - * rate. Note that it works only because we do - * not allow rate fallback from OFDM to CCK. - */ - mcs = (stat >> RT2860_TXQ_MCS_SHIFT) & 0x7f; - pid = (stat >> RT2860_TXQ_PID_SHIFT) & 0xf; - if (mcs + 1 != pid) - retrycnt = 1; - ieee80211_ratectl_tx_complete(ni->ni_vap, ni, - IEEE80211_RATECTL_TX_SUCCESS, - &retrycnt, NULL); - } else { - retrycnt = 1; - ieee80211_ratectl_tx_complete(ni->ni_vap, ni, - IEEE80211_RATECTL_TX_FAILURE, - &retrycnt, NULL); + /* + * Even though each stat is Tx-complete-status like format, + * the device can poll stats. Because there is no guarantee + * that the referring node is still around when read the stats. + * So that, if we use ieee80211_ratectl_tx_update(), we will + * have hard time not to refer already freed node. + * + * To eliminate such page faults, we poll stats in softc. + * Then, update the rates later with ieee80211_ratectl_tx_update(). + */ + wstat = &(sc->wcid_stats[wcid]); + (*wstat)[RUN_TXCNT]++; + if (stat & RT2860_TXQ_OK) + (*wstat)[RUN_SUCCESS]++; + else ifp->if_oerrors++; + /* + * Check if there were retries, ie if the Tx success rate is + * different from the requested rate. Note that it works only + * because we do not allow rate fallback from OFDM to CCK. + */ + mcs = (stat >> RT2860_TXQ_MCS_SHIFT) & 0x7f; + pid = (stat >> RT2860_TXQ_PID_SHIFT) & 0xf; + if ((retry = pid -1 - mcs) > 0) { + (*wstat)[RUN_TXCNT] += retry; + (*wstat)[RUN_RETRY] += retry; } } DPRINTFN(3, "count=%d\n", sc->fifo_cnt); @@ -2290,46 +2290,51 @@ run_iter_func(void *arg, struct ieee8021 struct ieee80211com *ic = ni->ni_ic; struct ifnet *ifp = ic->ic_ifp; struct run_node *rn = (void *)ni; - uint32_t sta[3]; - int txcnt = 0, success = 0, retrycnt = 0; - int error; + union run_stats sta[2]; + uint16_t (*wstat)[3]; + int txcnt, success, retrycnt, error; + + RUN_LOCK(sc); if (sc->rvp_cnt <= 1 && (vap->iv_opmode == IEEE80211_M_IBSS || vap->iv_opmode == IEEE80211_M_STA)) { - RUN_LOCK(sc); - /* read statistic counters (clear on read) and update AMRR state */ error = run_read_region_1(sc, RT2860_TX_STA_CNT0, (uint8_t *)sta, sizeof sta); if (error != 0) - return; - - DPRINTFN(3, "retrycnt=%d txcnt=%d failcnt=%d\n", - le32toh(sta[1]) >> 16, le32toh(sta[1]) & 0xffff, - le32toh(sta[0]) & 0xffff); + goto fail; /* count failed TX as errors */ - ifp->if_oerrors += le32toh(sta[0]) & 0xffff; + ifp->if_oerrors += le16toh(sta[0].error.fail); - retrycnt = - (le32toh(sta[0]) & 0xffff) + /* failed TX count */ - (le32toh(sta[1]) >> 16); /* TX retransmission count */ - - txcnt = - retrycnt + - (le32toh(sta[1]) & 0xffff); /* successful TX count */ - - success = - (le32toh(sta[1]) >> 16) + - (le32toh(sta[1]) & 0xffff); + retrycnt = le16toh(sta[1].tx.retry); + success = le16toh(sta[1].tx.success); + txcnt = retrycnt + success + le16toh(sta[0].error.fail); - ieee80211_ratectl_tx_update(vap, ni, &txcnt, &success, - &retrycnt); + DPRINTFN(3, "retrycnt=%d success=%d failcnt=%d\n", + retrycnt, success, le16toh(sta[0].error.fail)); + } else { + wstat = &(sc->wcid_stats[RUN_AID2WCID(ni->ni_associd)]); - RUN_UNLOCK(sc); + if (wstat == &(sc->wcid_stats[0]) || + wstat > &(sc->wcid_stats[RT2870_WCID_MAX])) + goto fail; + + txcnt = (*wstat)[RUN_TXCNT]; + success = (*wstat)[RUN_SUCCESS]; + retrycnt = (*wstat)[RUN_RETRY]; + DPRINTFN(3, "retrycnt=%d txcnt=%d success=%d\n", + retrycnt, txcnt, success); + + memset(wstat, 0, sizeof(*wstat)); } + ieee80211_ratectl_tx_update(vap, ni, &txcnt, &success, &retrycnt); rn->amrr_ridx = ieee80211_ratectl_rate(ni, NULL, 0); + +fail: + RUN_UNLOCK(sc); + DPRINTFN(3, "ridx=%d\n", rn->amrr_ridx); } @@ -2345,6 +2350,8 @@ run_newassoc_cb(void *arg) run_write_region_1(sc, RT2860_WCID_ENTRY(wcid), ni->ni_macaddr, IEEE80211_ADDR_LEN); + + memset(&(sc->wcid_stats[wcid]), 0, sizeof(sc->wcid_stats[wcid])); } static void @@ -2384,8 +2391,6 @@ run_newassoc(struct ieee80211_node *ni, DPRINTF("new assoc isnew=%d associd=%x addr=%s\n", isnew, ni->ni_associd, ether_sprintf(ni->ni_macaddr)); - sc->sc_ni[wcid] = ni; - for (i = 0; i < rs->rs_nrates; i++) { rate = rs->rs_rates[i] & IEEE80211_RATE_VAL; /* convert 802.11 rate to hardware rate index */ Modified: head/sys/dev/usb/wlan/if_runreg.h ============================================================================== --- head/sys/dev/usb/wlan/if_runreg.h Mon Feb 14 08:09:02 2011 (r218675) +++ head/sys/dev/usb/wlan/if_runreg.h Mon Feb 14 08:14:06 2011 (r218676) @@ -1208,4 +1208,17 @@ static const struct rt2860_rate { { 30, 0x09 }, \ { 31, 0x10 } + +union run_stats { + uint32_t raw; + struct { + uint16_t fail; + uint16_t pad; + } error; + struct { + uint16_t success; + uint16_t retry; + } tx; +} __aligned(4); + #endif /* _IF_RUNREG_H_ */ Modified: head/sys/dev/usb/wlan/if_runvar.h ============================================================================== --- head/sys/dev/usb/wlan/if_runvar.h Mon Feb 14 08:09:02 2011 (r218675) +++ head/sys/dev/usb/wlan/if_runvar.h Mon Feb 14 08:14:06 2011 (r218676) @@ -160,7 +160,10 @@ struct run_softc { device_t sc_dev; struct usb_device *sc_udev; struct ifnet *sc_ifp; - struct ieee80211_node *sc_ni[RT2870_WCID_MAX + 1]; + uint16_t wcid_stats[RT2870_WCID_MAX + 1][3]; +#define RUN_TXCNT 0 +#define RUN_SUCCESS 1 +#define RUN_RETRY 2 int (*sc_srom_read)(struct run_softc *, uint16_t, uint16_t *); _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon Feb 14 11:07:09 2011 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 333E21065697 for ; Mon, 14 Feb 2011 11:07:09 +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 1EFCB8FC18 for ; Mon, 14 Feb 2011 11:07:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1EB79X7077246 for ; Mon, 14 Feb 2011 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1EB78Je077244 for freebsd-net@FreeBSD.org; Mon, 14 Feb 2011 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Feb 2011 11:07:08 GMT Message-Id: <201102141107.p1EB78Je077244@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, 14 Feb 2011 11:07:09 -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/154679 net [em] Fatal trap 12: "em1 taskq" only at startup (8.1-R o kern/154676 net [netgraph] [panic] HEAD, 8.1-RELEASE panic after some o kern/154600 net [tcp] [panic] Random kernel panics on tcp_output o kern/154567 net [ath] ath(4) lot of bad series(0) o kern/154557 net [tcp] Freeze tcp-session of the clients, if in the gat o kern/154443 net [if_bridge] Kernel module bridgestp.ko missing after u o kern/154286 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/154284 net [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154255 net [nfs] NFS not responding o kern/154214 net [stf] [panic] Panic when creating stf interface o kern/154169 net [multicast] [ip6] Node Information Query multicast add o kern/154134 net [ip6] stuck kernel state in LISTEN on ipv6 daemon whic o kern/154091 net [netgraph] [panic] netgraph, unaligned mbuf? o conf/154062 net [vlan] [patch] change to way of auto-generatation of v o kern/154006 net [tcp] [patch] tcp "window probe" bug on 64bit o kern/153938 net [run] [panic] [patch] Workaround for use-after-free pa o kern/153937 net [ral] ralink panics the system (amd64 freeBSDD 8.X) wh o kern/153936 net [ixgbe] [patch] MPRC workaround incorrectly applied to o kern/153816 net [ixgbe] ixgbe doesn't work properly with the Intel 10g o kern/153772 net [ixgbe] [patch] sysctls reference wrong XON/XOFF varia o kern/153671 net [em] [panic] 8.2-PRERELEASE repeatable kernel in if_em o kern/153497 net [netgraph] netgraph panic due to race conditions o kern/153454 net [patch] [wlan] [urtw] Support ad-hoc and hostap modes o kern/153308 net [em] em interface use 100% cpu o kern/153255 net [panic] 8.2-PRERELEASE repeatable kernel panic under h o kern/153244 net [em] em(4) fails to send UDP to port 0xffff o kern/152893 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/152853 net [em] tftpd (and likely other udp traffic) fails over e o kern/152828 net [em] poor performance on 8.1, 8.2-PRE o kern/152569 net [net]: Multiple ppp connections and routing table prob o kern/152360 net [dummynet] [panic] Crash related to dummynet. o kern/152235 net [arp] Permanent local ARP entries are not properly upd o kern/152141 net [vlan] [patch] encapsulate vlan in ng_ether before out o kern/151690 net [ep] network connectivity won't work until dhclient is o kern/151681 net [nfs] NFS mount via IPv6 leads to hang on client with o kern/151593 net [igb] [panic] Kernel panic when bringing up igb networ o kern/150920 net [ixgbe][igb] Panic when packets are dropped with heade o bin/150642 net netstat(1) doesn't print anything for SCTP sockets o kern/150557 net [igb] igb0: Watchdog timeout -- resetting o kern/150251 net [patch] [ixgbe] Late cable insertion broken o kern/150249 net [ixgbe] Media type detection broken o kern/150247 net [patch] [ixgbe] Version in -current won't build on 7.x o bin/150224 net ppp(8) does not reassign static IP after kill -KILL co f kern/149969 net [wlan] [ral] ralink rt2661 fails to maintain connectio o kern/149937 net [ipfilter] [patch] kernel panic in ipfilter IP fragmen o kern/149786 net [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149643 net [rum] device not sending proper beacon frames in ap mo o kern/149609 net [panic] reboot after adding second default route o kern/149539 net [ath] atheros ar9287 is not supported by ath_hal o kern/149516 net [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 net [realtek/atheros]: None of my network card working o kern/149307 net [ath] Doesn't work Atheros 9285 o kern/149306 net [alc] Doesn't work Atheros AR8131 PCIe Gigabit Etherne o kern/149117 net [inet] [patch] in_pcbbind: redundant test o kern/149086 net [multicast] Generic multicast join failure in 8.1 o kern/148322 net [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 net [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 net [ath] wireless networking stops functioning o kern/147894 net [ipsec] IPv6-in-IPv4 does not work inside an ESP-only o kern/147155 net [ip6] setfb not work with ipv6 o kern/146845 net [libc] close(2) returns error 54 (connection reset by o kern/146792 net [flowtable] flowcleaner 100% cpu's core load o kern/146759 net [cxgb] [patch] cxgb panic calling cxgb_set_lro() witho o kern/146719 net [pf] [panic] PF or dumynet kernel panic o kern/146534 net [icmp6] wrong source address in echo reply o kern/146427 net [mwl] Additional virtual access points don't work on m o kern/146426 net [mwl] 802.11n rates not possible on mwl o kern/146425 net [mwl] mwl dropping all packets during and after high u f kern/146394 net [vlan] IP source address for outgoing connections o bin/146377 net [ppp] [tun] Interface doesn't clear addresses when PPP o kern/146358 net [vlan] wrong destination MAC address o kern/146165 net [wlan] [panic] Setting bssid in adhoc mode causes pani o kern/146082 net [ng_l2tp] a false invaliant check was performed in ng_ o kern/146037 net [panic] mpd + CoA = kernel panic o bin/145934 net [patch] add count option to netstat(1) o kern/145826 net [ath] Unable to configure adhoc mode on ath0/wlan0 o kern/145825 net [panic] panic: soabort: so_count o kern/145728 net [lagg] Stops working lagg between two servers. o kern/144987 net [wpi] [panic] injecting packets with wlaninject using o kern/144882 net MacBookPro =>4.1 does not connect to BSD in hostap wit o kern/144874 net [if_bridge] [patch] if_bridge frees mbuf after pfil ho o conf/144700 net [rc.d] async dhclient breaks stuff for too many people o kern/144642 net [rum] [panic] Enabling rum interface causes panic o kern/144616 net [nat] [panic] ip_nat panic FreeBSD 7.2 o kern/144572 net [carp] CARP preemption mode traffic partially goes to f kern/144315 net [ipfw] [panic] freebsd 8-stable reboot after add ipfw o kern/143939 net [ipfw] [em] ipfw nat and em interface rxcsum problem o kern/143874 net [wpi] Wireless 3945ABG error. wpi0 could not allocate o kern/143868 net [ath] [patch] [request] allow Atheros watchdog timeout o kern/143846 net [gif] bringing gif3 tunnel down causes gif0 tunnel to s kern/143673 net [stf] [request] there should be a way to support multi s kern/143666 net [ip6] [request] PMTU black hole detection not implemen o kern/143622 net [pfil] [patch] unlock pfil lock while calling firewall o kern/143593 net [ipsec] When using IPSec, tcpdump doesn't show outgoin o kern/143591 net [ral] RT2561C-based DLink card (DWL-510) fails to work o kern/143208 net [ipsec] [gif] IPSec over gif interface not working o conf/143079 net hostapd(8) startup missing multi wlan functionality o kern/143034 net [panic] system reboots itself in tcp code [regression] o kern/142877 net [hang] network-related repeatable 8.0-STABLE hard hang o kern/142774 net Problem with outgoing connections on interface with mu o kern/142772 net [libc] lla_lookup: new lle malloc failed o kern/142018 net [iwi] [patch] Possibly wrong interpretation of beacon- o kern/141861 net [wi] data garbled with WEP and wi(4) with Prism 2.5 f kern/141741 net Etherlink III NIC won't work after upgrade to FBSD 8, o kern/141023 net [carp] CARP arp replays with wrong src mac o kern/140796 net [ath] [panic] privileged instruction fault o kern/140742 net rum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140682 net [netgraph] [panic] random panic in netgraph o kern/140634 net [vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net [ifnet] [patch] refine obsolete if_var.h comments desc o kern/140346 net [wlan] High bandwidth use causes loss of wlan connecti o kern/140245 net [ath] [panic] Kernel panic during network activity on o kern/140142 net [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net [bwi] install report for 8.0 RC 2 (multiple problems) o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL o kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop o kern/138620 net [lagg] [patch] lagg port bpf-writes blocked o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR if_adata/ o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 o bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o kern/137775 net [netgraph] [patch] Add XMIT_FAILOVER to ng_one2many o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137592 net [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o bin/137484 net [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o bin/136994 net [patch] ifconfig(8) print carp mac address o kern/136943 net [wpi] [lor] wpi0_com_lock / wpi0 o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o kern/136836 net [ath] atheros card stops functioning after about 12 ho o bin/136661 net [patch] ndp(8) ignores -f option o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/136426 net [panic] spawning several dhclients in parallel panics o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/134931 net [route] Route messages sent to all socket listeners re o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134168 net [ral] ral driver problem on RT2525 2.4GHz transceiver o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre o kern/133218 net [carp] [hang] use of carp(4) causes system to freeze f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o conf/132851 net [patch] rc.conf(5): allow to setfib(1) for service run 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/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/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 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 bin/131365 net route(8): route add changes interpretation of network 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 kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour f 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/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o bin/128954 net ifconfig(8) deletes valid routes o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) 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/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) 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/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/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy 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/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 o kern/125721 net [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 net [ath] [panic] ath(4) related panic o kern/125501 net [ath] atheros cardbus driver hangs f kern/125442 net [carp] [lagg] CARP combined with LAGG causes system pa f kern/125332 net [ath] [panic] crash under any non-tiny networking unde o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124225 net [ndis] [patch] ndis network driver sometimes loses net o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. 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 kern/123758 net [panic] panic while restarting net/freenet6 o bin/123633 net ifconfig(8) doesn't set inet and ether address in one 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 conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 f kern/123045 net [ng_mppc] ng_mppc_decompress - disabling node 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 f kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge 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/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup ieee o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net 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] [security] ppp(8): fix local stack overflow in 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/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/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 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/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/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 o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af 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 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/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 bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/107944 net [wi] [patch] Forget to unlock mutex-locks f kern/107279 net [ath] [panic] ath_start: attempted use of a free mbuf! o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106444 net [netgraph] [panic] Kernel Panic on Binding to an ip to 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/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] f 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/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o kern/102540 net [netgraph] [patch] supporting vlan(4) by ng_fec(4) 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 o kern/97306 net [netgraph] NG_L2TP locks after connection with failed o conf/97014 net [gif] gifconfig_gif? in rc.conf does not recognize IPv f kern/96268 net [socket] TCP socket performance drops by 3000% if pack 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 f 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 s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu 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/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging s kern/90086 net [hang] 5.4p8 on supermicro P8SCT hangs during boot if o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87421 net [netgraph] [panic]: ng_ether + ng_eiface + if_bridge s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86871 net [tcp] [patch] allocation logic for PCBs in TIME_WAIT s o kern/86427 net [lor] Deadlock with FASTIPSEC and nat 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 p kern/85320 net [gre] [patch] possible depletion of kernel stack in ip o bin/82975 net route change does not parse classfull network as given o kern/82881 net [netgraph] [panic] ng_fec(4) causes kernel panic after o bin/82185 net [patch] ndp(8) can delete the incorrect entry o kern/81095 net IPsec connection stops working if associated network i o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78968 net FreeBSD freezes on mbufs exhaustion (network interface o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if 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 a kern/71474 net [route] route lookup does not skip interfaces marked d 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/66225 net [netgraph] [patch] extend ng_eiface(4) control message o kern/65616 net IPSEC can't detunnel GRE packets after real ESP encryp s kern/60293 net [patch] FreeBSD arp poison patch a kern/56233 net IPsec tunnel (ESP) over IPv6: MTU computation is wrong o kern/54383 net [nfs] [patch] NFS root configurations without dynamic 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/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 375 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 14 17:10:07 2011 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 BA759106564A; Mon, 14 Feb 2011 17:10:07 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id 495318FC0A; Mon, 14 Feb 2011 17:10:07 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 3679941C7A6; Mon, 14 Feb 2011 18:10:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id jh-nA9ITjuLM; Mon, 14 Feb 2011 18:10:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id C392241C7AF; Mon, 14 Feb 2011 18:10:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 1C59B4448F3; Mon, 14 Feb 2011 17:07:49 +0000 (UTC) Date: Mon, 14 Feb 2011 17:07:49 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: freebsd-net@freebsd.org, freebsd-atm@freebsd.org Message-ID: <20110214170214.Y13400@maildrop.int.zabbadoz.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: NATM still scheduled for removal - please follow up to keep it in-tree X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2011 17:10:07 -0000 Hi, now that stable/8 (not part of the upcoming 8.2-R) once again has support for NATM I'd like to remind people of http://lists.freebsd.org/pipermail/freebsd-net/2010-December/027215.html especially: :: 1) the extra couple of months; this will not prevent the evitable removal :: yet only defer it. :: :: 2) If anyone of you is using (or want to be able to (continue to) use) NATM :: or can test things, I re-enabled it with most of the code in HEAD and :: the patch is available for 8,x as well but need to work with somoene :: to make sure it'll really work. I am willing to spend more time on it :: if you send me an email. So if anyone of you is still using NATM, please follow-up with me to keep your functionality. If there is no feedback NATM is still scheduled for removal. Thank you. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ---------- Forwarded message ---------- Date: Mon, 14 Feb 2011 16:54:03 +0000 (UTC) From: Bjoern A. Zeeb To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-8@freebsd.org Subject: svn commit: r218684 - in stable/8/sys: conf netinet Author: bz Date: Mon Feb 14 16:54:03 2011 New Revision: 218684 URL: http://svn.freebsd.org/changeset/base/218684 Log: MFC r216466: Bring back (most of) NATM to avoid further bitrot after r186119. Keep three lines disabled which I am unsure if they had been used at all. This will allow us to seek testers and possibly bring it all back. Discussed with: rwatson Modified: stable/8/sys/conf/NOTES stable/8/sys/netinet/if_atm.c Directory Properties: stable/8/sys/ (props changed) stable/8/sys/amd64/include/xen/ (props changed) stable/8/sys/cddl/contrib/opensolaris/ (props changed) stable/8/sys/contrib/dev/acpica/ (props changed) stable/8/sys/contrib/pf/ (props changed) From owner-freebsd-net@FreeBSD.ORG Mon Feb 14 18:23:34 2011 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 8ED8710656A3 for ; Mon, 14 Feb 2011 18:23:34 +0000 (UTC) (envelope-from fafaforza@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 294B38FC23 for ; Mon, 14 Feb 2011 18:23:33 +0000 (UTC) Received: by ewy24 with SMTP id 24so2566078ewy.13 for ; Mon, 14 Feb 2011 10:23:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=Rp43qh0L2K7+T5nzhL12z8/Ln1fdStDSOVlnsVJqcpY=; b=R0B/bTGReStCD/bV3MkU++BtOSw+xRdHelKEpeIxxg/EqTErk7RZl4//ME/gOUHrLi ddztkjF97lwMXorE0WwI5FshuG51h1Ee2e2wI3cE2+HImI6Vk2e5nHC9bObTmIb4ZkVa CNmWJvOkcytrbAJOO5nez/hddOE1W7BFPzdlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=eGLDdcfu5oP3m6g6/SrRH1ZV/nfMZ3TZlCBbNOGm4O5OMjDV8fMkFCQ7OzzXUpG0UU JAqTXGrDMaQ0f48Inq7TgZXXNA6uEhlajSDmwa2I3ZFcVQJ4bYIxqBKRLoGd8ef0zZK6 lGeie8xO6Y/mHBx3bijQ4GKbwYjDA/wGwuHCE= MIME-Version: 1.0 Received: by 10.223.101.140 with SMTP id c12mr1440228fao.16.1297706359827; Mon, 14 Feb 2011 09:59:19 -0800 (PST) Received: by 10.223.104.134 with HTTP; Mon, 14 Feb 2011 09:59:19 -0800 (PST) Date: Mon, 14 Feb 2011 12:59:19 -0500 Message-ID: From: Darek M To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: IPv4 and IPv6 NAT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2011 18:23:34 -0000 Hi there, I'm looking to set up my private network to be connected to IPv6. My NAT box will have a direct v6 assignment, and I'm wondering what the setup will be like to provide private hosts access to v4 and v6 networks/hosts at the same time. Currently using 7.2-RELEASE, with ipnat/ipfilter. Will I be setting up the NAT box in dual stack? Will that allow me then to provide each private host with a v6 IP? Will that then make the private hosts run in dual stack? In turn allowing them to access v4 networks via NAT, and v6 networks using packet forwarding on the NAT box, but not actually using NAT? Or would IPv4 DHCP assignments erase the v6 IPs? Or would I have to do translation on the NAT box? I have the option of adding the v6 IPs on a separate network interface, if that would ease the configuration. Welcome any pointers. - Darek From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 05:01:11 2011 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 2AD30106566C for ; Tue, 15 Feb 2011 05:01:11 +0000 (UTC) (envelope-from lars.eggert@nokia.com) Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by mx1.freebsd.org (Postfix) with ESMTP id 02D918FC18 for ; Tue, 15 Feb 2011 05:01:10 +0000 (UTC) Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p1F4DqmF006885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2011 06:13:53 +0200 X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/signed; boundary=Apple-Mail-5--539034263; protocol="application/pkcs7-signature"; micalg=sha1 From: Lars Eggert In-Reply-To: Date: Tue, 15 Feb 2011 06:13:49 +0200 Message-Id: References: To: Darek M X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Tue, 15 Feb 2011 06:13:49 +0200 (EET) X-Spam-Status: No, score=-101.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, MISSING_SUBJECT,USER_IN_WHITELIST autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on fit.nokia.com X-Nokia-AV: Clean X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: IPv4 and IPv6 NAT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 05:01:11 -0000 --Apple-Mail-5--539034263 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, On 2011-2-14, at 19:59, Darek M wrote: > Currently using 7.2-RELEASE, with ipnat/ipfilter. >=20 > Will I be setting up the NAT box in dual stack? yes. > Will that allow me then to provide each private host with a v6 IP? Yes. > Will that then make the private hosts run in dual stack? If the OS on the private hosts implements dual-stack, yes. > In turn > allowing them to access v4 networks via NAT, and v6 networks using > packet forwarding on the NAT box, but not actually using NAT? Yes. > Or would IPv4 DHCP assignments erase the v6 IPs? No. > Or would I have to do translation on the NAT box? You don't need NAT for IPv6. You do probably want to set up a firewall = though. > I have the option > of adding the v6 IPs on a separate network interface, if that would > ease the configuration. Same interface is fine. Lars= --Apple-Mail-5--539034263-- From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 12:00:57 2011 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 1267A1065697 for ; Tue, 15 Feb 2011 12:00:57 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9F46C8FC17 for ; Tue, 15 Feb 2011 12:00:56 +0000 (UTC) Received: by fxm16 with SMTP id 16so94211fxm.13 for ; Tue, 15 Feb 2011 04:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=oOQ07tEcVl1cV3mSAKNLgUDnePyFM2gY4a9jxV0deug=; b=q2KgPqLGMrqiH7ETP08PgRb1U00RXDPBGSBOZV4fgK4QvTpo8M5V5FU1Ns138hCfif cv5BhKV/dUnoKR+tYcIWRhApLyiOYdZ19RtEZ6xZnlECYYiWLRvSwxC0pKoWL1/HIymZ karAAaEWTdjIkcy8z9RcBqJDjupuZbUukQMjo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JYk3J1AONWXIwm3/mmgektn1Z74v1mHlXIRARhCjTjga7cEZrZIDWGV0QQjSkXSjII zSYC8DbhWQCqzB/gJVKFhgz7rhLvDMqbLCxL75LWa9fe6Md6C3amLXCXslhaKYvN5BH5 v5XM3+8U8ONZTqlklqT/f64MUfZpqGJ+rJMSM= MIME-Version: 1.0 Received: by 10.223.96.6 with SMTP id f6mr6075245fan.22.1297771254683; Tue, 15 Feb 2011 04:00:54 -0800 (PST) Received: by 10.223.97.71 with HTTP; Tue, 15 Feb 2011 04:00:54 -0800 (PST) Date: Tue, 15 Feb 2011 13:00:54 +0100 Message-ID: From: Monthadar Al Jaberi To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [ieee80211_hwmp][panic] hwmp_recv_prep(...) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 12:00:57 -0000 Hej, I found that a panic can be generated when having a couple of ieee80211s nodes in a line topology with one of them being a ROOT node. A ping from ROOT in a newly started nodes causes a panic: panic: ieee80211_mesh_rt_add: adding self to the routing table KDB: enter: panic [ thread pid 0 tid 100030 ] Stopped at kdb_enter+0x50: lui at,0x804e db> This is because we receive a copy of our own generated IEEE80211_ELEMID_MESHPREP packet from our neighbor node. I added check code in the begining of hwmp_recv_prep(...) similar to the check code found in hwmp_recv_preq(...). Here is a diff output: --- freebsd/head/sys/net80211/ieee80211_hwmp.c 2010-11-03 09:29:25.023610380 +0000 +++ src/head-current/sys/net80211/ieee80211_hwmp.c 2011-02-15 10:06:02.526163874 +0000 @@ -28,7 +28,7 @@ */ #include #ifdef __FreeBSD__ -__FBSDID("$FreeBSD$"); +__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_hwmp.c,v 1.4.2.7.2.1 2010/12/21 17:09:25 kensmith Exp $"); #endif /* @@ -951,6 +951,12 @@ if (ni == vap->iv_bss || ni->ni_mlstate != IEEE80211_NODE_MESH_ESTABLISHED) return; + /* + * Ignore PREPs from us. Could happen because someone forward it + * back to us. + */ + if (IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_targetaddr)) + return; if (!IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_origaddr) && !(ms->ms_flags & IEEE80211_MESHFLAGS_FWD)) return; -- //Monthadar Al Jaberi From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 12:31:25 2011 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 58184106567A for ; Tue, 15 Feb 2011 12:31:25 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id D6DBE8FC1A for ; Tue, 15 Feb 2011 12:31:24 +0000 (UTC) Received: (qmail 20989 invoked from network); 15 Feb 2011 15:31:34 +0300 Received: from 83-69-208-138.in-addr.mastertelecom.ru (83-69-208-138.in-addr.mastertelecom.ru [83.69.208.138]) by mail.sub.ru ([88.212.205.2]) with ESMTP via TCP; 15 Feb 2011 12:31:34 -0000 Message-ID: <4D5A71F5.8080104@webmail.sub.ru> Date: Tue, 15 Feb 2011 15:30:45 +0300 From: Alex Povolotsky User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101103 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: VRRP on VLANs: does it 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: Tue, 15 Feb 2011 12:31:25 -0000 Hello! I've run into strange problem: in non-promisc mode, two freevrrpds does not seems to see each others multicasts. Is it a bug or a feature? Alex. From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 12:55:48 2011 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 43184106566B for ; Tue, 15 Feb 2011 12:55:48 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id CB7F58FC20 for ; Tue, 15 Feb 2011 12:55:47 +0000 (UTC) Received: by wwf26 with SMTP id 26so134566wwf.31 for ; Tue, 15 Feb 2011 04:55:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=NRIwL/ctGJmWfyJos/X1CF1EQtx/wqAct+RsmvESgWQ=; b=XQ/9iIt5nrpho2b09DNTiBpPePxiuHsgEXa2vSUmTRhqGCfdJoMdzn+7XE13sJsBGa SRNl3/h+QbYNWSD8zIN2QzjbaBpF4SWxPT42Hb4/Tm3kcN50Rzcf06h9anBCBKe8eFNJ jb6cLfJLLC4tN4fjL62j7ntT81hcWcdp/XtBg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=vhzKyZBucYIfbvrolPg+9ERuMsodCCB93zvqbSoKBpB7u+FdLFO9ROTMmACJi0ORZ2 bc2GXVb6c9jDZJIArLckoat4quVttrtvR1QuURXMcrCTJUU08FAOABHjl/Ah+hjtd8IF xcI0Zn7HdrFo5khsptdLSv3cxnGByR4s8vBv4= MIME-Version: 1.0 Received: by 10.227.134.14 with SMTP id h14mr3628792wbt.190.1297774546601; Tue, 15 Feb 2011 04:55:46 -0800 (PST) Received: by 10.227.69.7 with HTTP; Tue, 15 Feb 2011 04:55:46 -0800 (PST) In-Reply-To: References: Date: Tue, 15 Feb 2011 13:55:46 +0100 Message-ID: From: Monthadar Al Jaberi To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [ieee80211_hwmp][panic] hwmp_recv_prep(...) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 12:55:48 -0000 here is a backtrace for the panic: panic: ieee80211_mesh_rt_add: adding self to the routing table KDB: enter: panic [ thread pid 0 tid 100030 ] Stopped at kdb_enter+0x50: lui at,0x804e db> bt Tracing pid 0 tid 100030 td 0xc08952f0 db_trace_thread+30 (?,?,?,?) ra 8009b510 sp c76275e8 sz 24 8009b3f4+11c (0,?,ffffffff,?) ra 8009aaf8 sp c7627600 sz 32 8009a764+394 (?,?,?,?) ra 8009ac88 sp c7627620 sz 168 db_command_loop+78 (?,?,?,?) ra 8009d368 sp c76276c8 sz 24 8009d260+108 (?,?,?,?) ra 801ead50 sp c76276e0 sz 424 kdb_trap+108 (?,?,?,?) ra 803ad33c sp c7627888 sz 32 trap+c88 (?,?,?,?) ra 803a51d0 sp c76278a8 sz 168 MipsKernGenException+134 (0,a,80653fe4,109) ra 801eafd8 sp c7627950 sz 200 kdb_enter+50 (?,?,?,?) ra 801b3ec4 sp c7627a18 sz 24 panic+f8 (?,803f0dc0,0,df) ra 802aa5dc sp c7627a30 sz 40 ieee80211_mesh_rt_add+74 (?,?,?,?) ra 802a1210 sp c7627a58 sz 40 802a05b4+c5c (?,c0c85000,?,?) ra 8028a540 sp c7627a80 sz 336 ieee80211_recv_action+1b4 (?,?,?,?) ra 802ab868 sp c7627bd0 sz 24 802aafd4+894 (?,?,?,61) ra 800aaf0c sp c7627be8 sz 176 800aaec4+48 (?,?,?,?) ra 802add54 sp c7627c98 sz 56 802acc90+10c4 (?,?,?,ffffffa0) ra 800a8d20 sp c7627cd0 sz 200 800a8794+58c (?,?,?,?) ra 801f8284 sp c7627d98 sz 104 801f81cc+b8 (?,?,?,?) ra 801f8928 sp c7627e00 sz 40 taskqueue_thread_loop+68 (?,?,?,?) ra 801892a0 sp c7627e28 sz 48 fork_exit+b0 (?,?,?,?) ra 803b1c20 sp c7627e58 sz 40 fork_trampoline+10 (?,?,?,?) ra 0 sp c7627e80 sz 0 pid 0 db> br, On Tue, Feb 15, 2011 at 1:00 PM, Monthadar Al Jaberi wrote: > Hej, > > I found that a panic can be generated when having a couple of > ieee80211s nodes in a line topology with one of them being a ROOT > node. A ping from ROOT in a newly started nodes causes a panic: > panic: ieee80211_mesh_rt_add: adding self to the routing table > KDB: enter: panic > [ thread pid 0 tid 100030 ] > Stopped at =A0 =A0 =A0kdb_enter+0x50: lui =A0 =A0 at,0x804e > db> > > This is because we receive a copy of our own generated > IEEE80211_ELEMID_MESHPREP packet from our neighbor node. > I added check code in the begining of hwmp_recv_prep(...) similar to > the check code found in hwmp_recv_preq(...). Here is a diff output: > > --- freebsd/head/sys/net80211/ieee80211_hwmp.c =A02010-11-03 > 09:29:25.023610380 +0000 > +++ src/head-current/sys/net80211/ieee80211_hwmp.c =A0 =A0 =A02011-02-15 > 10:06:02.526163874 +0000 > @@ -28,7 +28,7 @@ > =A0*/ > =A0#include > =A0#ifdef __FreeBSD__ > -__FBSDID("$FreeBSD$"); > +__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_hwmp.c,v 1.4.2.7.2.1 > 2010/12/21 17:09:25 kensmith Exp $"); > =A0#endif > > =A0/* > @@ -951,6 +951,12 @@ > =A0 =A0 =A0 =A0if (ni =3D=3D vap->iv_bss || > =A0 =A0 =A0 =A0 =A0 =A0ni->ni_mlstate !=3D IEEE80211_NODE_MESH_ESTABLISHE= D) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return; > + =A0 =A0 =A0 /* > + =A0 =A0 =A0 =A0* Ignore PREPs from us. Could happen because someone for= ward it > + =A0 =A0 =A0 =A0* back to us. > + =A0 =A0 =A0 =A0*/ > + =A0 =A0 =A0 if (IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_targetaddr= )) > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 return; > =A0 =A0 =A0 =A0if (!IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_origaddr= ) && > =A0 =A0 =A0 =A0 =A0 =A0!(ms->ms_flags & IEEE80211_MESHFLAGS_FWD)) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return; > > -- > //Monthadar Al Jaberi > --=20 //Monthadar Al Jaberi From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 14:02:30 2011 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 05EC7106564A for ; Tue, 15 Feb 2011 14:02:30 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8C1DA8FC1F for ; Tue, 15 Feb 2011 14:02:29 +0000 (UTC) Received: by fxm16 with SMTP id 16so210159fxm.13 for ; Tue, 15 Feb 2011 06:02:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :date:subject:to:message-id:mime-version:x-mailer; bh=GC0G7h/Ugkjvz6W2u/JsW6OyvtF0evZlJ//tBx7JMJQ=; b=wFRI5kvec1MpLB7UNVDOMYP5tj21KAKdcEErpe1Jl1/W4DKw8kW/LdcAp9sJHGqLmH uVksrMA40jNHKVLWGIjc5shBxN2ctfuFP1KR64pzoNH3kRN2TEBfnE4zvy5QffP3HJAn 71p+VM6hjGlsBtYrVuSwpi4yu5qh1M2vdkwGc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:date:subject:to :message-id:mime-version:x-mailer; b=SLdWK/Hbsan/WLgZoyTJxzfBGLts+Vd/KVAH1a9Trm7a8W+twE6Jia98ONrBtgr1NP KrHZGgaut976mzXE4jemYJHKMZpMnOZRfhl3/hT3cVYvqO8+iVMoBobT5gDwR3cgY7Rg thXuSOyRMr6sZjifpDoW1+6GTYLbRRbbwS4JU= Received: by 10.223.100.15 with SMTP id w15mr6202080fan.121.1297778548390; Tue, 15 Feb 2011 06:02:28 -0800 (PST) Received: from ndenevsa.sf.moneybookers.net (g1.moneybookers.com [217.18.249.148]) by mx.google.com with ESMTPS id a2sm1657541faw.22.2011.02.15.06.02.25 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Feb 2011 06:02:26 -0800 (PST) From: Nikolay Denev Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 15 Feb 2011 16:02:24 +0200 To: freebsd-net@freebsd.org Message-Id: Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Subject: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 14:02:30 -0000 Hi, When trying to use ng_ether with vlan interfaces using the naming sheme = ${parent_if}.${vlan_tag} it produces the following warning : ng_ether_attach: can't name node ix0.512 And the newly created netgraph node stays . This is due to the following check in = sys/netgraph/ng_base.c:ng_name_node() : /* Check the name is valid */ for (i =3D 0; i < NG_NODESIZ; i++) { if (name[i] =3D=3D '\0' || name[i] =3D=3D '.' || name[i] = =3D=3D ':') break; } Do we really do not want to allow dot in the name? If it's not an option to allow the dot, probably it would be better to = replace it with underscore. I can provide a patch if the change is acceptable. Cheers, Nikolay= From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 16:17:02 2011 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 76D611065670 for ; Tue, 15 Feb 2011 16:17:02 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3E2478FC15 for ; Tue, 15 Feb 2011 16:17:01 +0000 (UTC) Received: by iwn39 with SMTP id 39so319505iwn.13 for ; Tue, 15 Feb 2011 08:17:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kYezw++rgE+la4xUiQvTAHuCkRR1nV+mQeoqUHozuGg=; b=UdRelGrZd0jy6S63+OA4dJ9xNTC/tRpNZpj11CX5k5GuSBHxlwj9lhYQO5nHwercds 9V7khz2jEm1I6kHGT8aF5Z62EKYoFFwZgx9T+m7GGH90s4DW5A1hL6KWgijXnyi5zE+Y q8wc1qqe+0XSoqvHVXG1fFsQ12hHEEKBVZoi8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=I+NhTjTooecOuN9qnjVddaBZ5xW5Asa+BXhN23kjk8mMLoxH8A5rGEFm4zHJCp9/s0 8AwmMX3QJMbup0N8imGvZ8kDxPnJnhLj+wldAckokR6m7BzRuN2GE8zWl12Ep460Tm0N LlCjRciPDRspjyKa+nyCtkwo8vvEDpeF1FpIM= MIME-Version: 1.0 Received: by 10.42.167.129 with SMTP id s1mr6935227icy.231.1297784862380; Tue, 15 Feb 2011 07:47:42 -0800 (PST) Received: by 10.42.164.201 with HTTP; Tue, 15 Feb 2011 07:47:42 -0800 (PST) In-Reply-To: References: Date: Tue, 15 Feb 2011 10:47:42 -0500 Message-ID: From: Arnaud Lacombe To: Nikolay Denev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 16:17:02 -0000 Hi, On Tue, Feb 15, 2011 at 9:02 AM, Nikolay Denev wrote: > Hi, > > When trying to use ng_ether with vlan interfaces using the naming sheme $= {parent_if}.${vlan_tag} > it produces the following warning : > > =A0 =A0ng_ether_attach: can't name node ix0.512 > > And the newly created netgraph node stays . > > This is due to the following check in sys/netgraph/ng_base.c:ng_name_node= () : > > =A0 =A0 =A0 =A0/* Check the name is valid */ > =A0 =A0 =A0 =A0for (i =3D 0; i < NG_NODESIZ; i++) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if (name[i] =3D=3D '\0' || name[i] =3D=3D = '.' || name[i] =3D=3D ':') > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0break; > =A0 =A0 =A0 =A0} > > Do we really do not want to allow dot in the name? >From sys/ng_base.c: /* * Find a node by absolute name. The name should NOT end with ':' * The name "." means "this node" and "[xxx]" means "the node * with ID (ie, at address) xxx". Moreover, several code path strictly assume that '.' is not repeated and enforce this. > If it's not an option to allow the dot, probably it would be better to re= place it with > underscore. > to name the current node ? It would be highly unintuitive. Also, you would be breaking all userland relying on '.' referring to the current node. Btw, ng_name_node() states that "Once assigned, the name cannot be changed.", however I can freely rename a node multiple time with ngctl. The comment might be bogus. - Arnaud > I can provide a patch if the change is acceptable. > > Cheers, > Nikolay_______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 16:30:21 2011 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 EBAA41065675 for ; Tue, 15 Feb 2011 16:30:21 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id A2E7F8FC0C for ; Tue, 15 Feb 2011 16:30:21 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p1FGUFqY094706 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Feb 2011 08:30:19 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4D5AAA28.50408@freebsd.org> Date: Tue, 15 Feb 2011 08:30:32 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Arnaud Lacombe References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikolay Denev , freebsd-net@freebsd.org Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 16:30:22 -0000 On 2/15/11 7:47 AM, Arnaud Lacombe wrote: > Hi, > > On Tue, Feb 15, 2011 at 9:02 AM, Nikolay Denev wrote: >> Hi, >> >> When trying to use ng_ether with vlan interfaces using the naming sheme ${parent_if}.${vlan_tag} >> it produces the following warning : >> >> ng_ether_attach: can't name node ix0.512 >> >> And the newly created netgraph node stays. >> >> This is due to the following check in sys/netgraph/ng_base.c:ng_name_node() : >> >> /* Check the name is valid */ >> for (i = 0; i< NG_NODESIZ; i++) { >> if (name[i] == '\0' || name[i] == '.' || name[i] == ':') >> break; >> } >> >> Do we really do not want to allow dot in the name? > > From sys/ng_base.c: > /* > * Find a node by absolute name. The name should NOT end with ':' > * The name "." means "this node" and "[xxx]" means "the node > * with ID (ie, at address) xxx". > > Moreover, several code path strictly assume that '.' is not repeated > and enforce this. > >> If it's not an option to allow the dot, probably it would be better to replace it with >> underscore. >> > to name the current node ? It would be highly unintuitive. Also, you > would be breaking all userland relying on '.' referring to the current > node. > > Btw, ng_name_node() states that "Once assigned, the name cannot be > changed.", however I can freely rename a node multiple time with > ngctl. The comment might be bogus. > > - Arnaud > check teh code and if it is true, (no leaks are found and no race conditinas are created) then send a patch and we'll see about getting the fix in.. >> I can provide a patch if the change is acceptable. changing it to '_' might be accceptable, '.' is much like '/' in th filesystem. it is a separator. You can't have it in the name. a patch that converted . to _ would be a nice idea. please ensure that the man page is updated as well. >> Cheers, >> Nikolay_______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 16:53:10 2011 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 ABC73106566B for ; Tue, 15 Feb 2011 16:53:10 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 71EE08FC12 for ; Tue, 15 Feb 2011 16:53:10 +0000 (UTC) Received: by iyb26 with SMTP id 26so259276iyb.13 for ; Tue, 15 Feb 2011 08:53:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=h/w3X4gmM65gPhWbwhoha1ePFcq9ufisosEsagcZy5I=; b=NY3CKAND9uu7SkHXMVJ9qepYs0CL9xG1HD+pp9S735p7gW/sOM/N9CmA888hSYHt6z pgP+/cfqundM7Z0qTEQLTXzpDXLqf4OXfc1vN8BCBfVi555d+kWsWvXs0Ya1s5TuZelE phIsLhAf2L65KqVeTh/78u1MIt9IOs46FQQ6w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=v5hM4gC4A3Fi9uj4kDII36OF+gMjcP+Jm6GRdBBY87wRS22J/+mQ9/Lkh5519tQvdf 7bxDITwtJheRl4L4cW9PCF6YA5Cq3p9lpyUDKODc/xweoWiSizqFYPv0inhovXQnMdtl 51b7QRRdgH83daf/zm6wC9506rOdHgduC1f8A= MIME-Version: 1.0 Received: by 10.42.229.135 with SMTP id ji7mr6982816icb.365.1297788789267; Tue, 15 Feb 2011 08:53:09 -0800 (PST) Received: by 10.42.164.201 with HTTP; Tue, 15 Feb 2011 08:53:09 -0800 (PST) In-Reply-To: <4D5AAA28.50408@freebsd.org> References: <4D5AAA28.50408@freebsd.org> Date: Tue, 15 Feb 2011 11:53:09 -0500 Message-ID: From: Arnaud Lacombe To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Nikolay Denev , freebsd-net@freebsd.org Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 16:53:10 -0000 Hi, On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrot= e: > changing it to '_' might be accceptable, =A0'.' is much like '/' in th > filesystem. > it is a separator. You can't have it in the name. > a patch that converted . to _ would be a nice idea. > please ensure that the man page is updated as well. > Doesn't FreeBSD care about kernel/userland backward interface compatibility at all ? ie. will all my scripts assuming '.' as a separator need to also check the FreeBSD version to use whatever path separator ? How would you do that with bare ngctl script, which cannot be really that evolved ? How do you deal with node in the wild already using '_' in their name ? Thanks, - Arnaud From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 19:08:29 2011 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 6A2231065670 for ; Tue, 15 Feb 2011 19:08:29 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 3AD478FC1C for ; Tue, 15 Feb 2011 19:08:28 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p1FJ8QlD095202 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Feb 2011 11:08:27 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4D5ACF3A.3020008@freebsd.org> Date: Tue, 15 Feb 2011 11:08:42 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Arnaud Lacombe References: <4D5AAA28.50408@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikolay Denev , freebsd-net@freebsd.org Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 19:08:29 -0000 On 2/15/11 8:53 AM, Arnaud Lacombe wrote: > Hi, > > On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote: >> changing it to '_' might be accceptable, '.' is much like '/' in th >> filesystem. >> it is a separator. You can't have it in the name. >> a patch that converted . to _ would be a nice idea. >> please ensure that the man page is updated as well. >> > Doesn't FreeBSD care about kernel/userland backward interface > compatibility at all ? ie. will all my scripts assuming '.' as a > separator need to also check the FreeBSD version to use whatever path > separator ? How would you do that with bare ngctl script, which cannot > be really that evolved ? How do you deal with node in the wild already > using '_' in their name ? well you can't have '.' as it is not a negotiable point.. '.' is the separator in netgraph paths.. like em0:up.raw.inet might be such a path. do you want to have filenames with '/' in them as well? note: you can rename the interfaces to have '.' in them if you want I think.. just not the netgraph names > Thanks, > - Arnaud > > From owner-freebsd-net@FreeBSD.ORG Tue Feb 15 19:08:37 2011 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 F08B1106566B for ; Tue, 15 Feb 2011 19:08:37 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B804F8FC1C for ; Tue, 15 Feb 2011 19:08:37 +0000 (UTC) Received: by iwn39 with SMTP id 39so489883iwn.13 for ; Tue, 15 Feb 2011 11:08:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version:from:date :message-id:subject:to:cc:content-type; bh=YjVj80YUXPlwLGmjDDG7g1OCRBlK/8MqUAmTWBiAs/s=; b=bEL6twgje5cHIEuQbNXYhPsV+wlNnSpl/kbfkOsH+/eLxEF5RUxkhX6aXOcELPVxeB SeCluWNw3Zl+benWI+jVL8hWNoK+tLioupe7WKQlKX5cQnSN4EwSmGmqeULAOMnsw5iI 3RJhKz+smwg6jZgQQTy+5GdQbZnXk2GDA2xXU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:from:date:message-id:subject:to :cc:content-type; b=ZxJSIU02cg1AB4OGX6AHdcxRiRc5eQYU3VbzVuSihhkzuS8PcsyGPcT5ir8KYlf6L4 7OWTyivURm7oOJ0Qx9z/+4mhVyfEgHslogsBSw8QZdeVRzKF0+XCpw2xJ+Nez+DhiX7y kLky8cPNe1IaKuNaSwF1+SWlvJMYYca8937Hk= Received: by 10.231.31.131 with SMTP id y3mr4501772ibc.179.1297796917044; Tue, 15 Feb 2011 11:08:37 -0800 (PST) References: <4D5AAA28.50408@freebsd.org> In-Reply-To: Mime-Version: 1.0 (iPhone Mail 8C148) From: Nikolay Denev Date: Tue, 15 Feb 2011 21:08:12 +0200 Message-ID: <5516808338355511684@unknownmsgid> To: Arnaud Lacombe Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2011 19:08:38 -0000 On 15.02.2011, at 18:53, Arnaud Lacombe wrote: > Hi, > > On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote: >> changing it to '_' might be accceptable, '.' is much like '/' in th >> filesystem. >> it is a separator. You can't have it in the name. >> a patch that converted . to _ would be a nice idea. >> please ensure that the man page is updated as well. >> > Doesn't FreeBSD care about kernel/userland backward interface > compatibility at all ? ie. will all my scripts assuming '.' as a > separator need to also check the FreeBSD version to use whatever path > separator ? How would you do that with bare ngctl script, which cannot > be really that evolved ? How do you deal with node in the wild already > using '_' in their name ? > > Thanks, > - Arnaud I'm actually thinking on doing the check and replacement of dots in ng_ether, so it won't affect other netgraph consumers. Regards, Nikolay From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 09:04:21 2011 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 AA16A106566B; Wed, 16 Feb 2011 09:04:21 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221]) by mx1.freebsd.org (Postfix) with ESMTP id 239088FC0A; Wed, 16 Feb 2011 09:04:20 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id p1G94EdI053588; Wed, 16 Feb 2011 15:04:14 +0600 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <4D5B9309.30508@rdtc.ru> Date: Wed, 16 Feb 2011 15:04:09 +0600 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7 MIME-Version: 1.0 To: Gleb Smirnoff References: <20110131144838.GO62007@FreeBSD.org> <4D46F655.9000701@rdtc.ru> <20110131204816.GV62007@glebius.int.ru> <4D5A989E.8020703@sentex.net> <4D5B4F07.6080801@rdtc.ru> <20110216084635.GI42041@glebius.int.ru> In-Reply-To: <20110216084635.GI42041@glebius.int.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Przemyslaw Frasunek , Mike Tancsa , mav@freebsd.org, bz@freebsd.org, "net@freebsd.org" Subject: Re: Netgraph/mpd5 stability issues X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 09:04:21 -0000 On 16.02.2011 14:46, Gleb Smirnoff wrote: > On Wed, Feb 16, 2011 at 10:13:59AM +0600, Eugene Grosbein wrote: > E> I run AMD64 with 4GB of memory, lots of memory is free and > E> I still get panics often, sometimes two in a couple of hours. > E> It does not seem memory exhaustion to me. It seems as very low probable race > E> that happens occasionally but may happen any time. > E> > E> With Gleb's patch, it is obvious that panic happens at moments of user disconnect. > > I missed: did my patch fix panics in the ng_address_hook(), in this block? > > if ((hook == NULL) || > NG_HOOK_NOT_VALID(hook) || > NG_HOOK_NOT_VALID(peer = NG_HOOK_PEER(hook)) || > NG_NODE_NOT_VALID(peernode = NG_PEER_NODE(hook))) { > NG_FREE_ITEM(item); > TRAP_ERROR(); > return (ENETDOWN); > } It seems, yes. All my panics now are in _chkhook() being called with bad hook as first argument. > All the panics reported by you and Mike recently have traces unrelated > to netgraph, and also traces look weird. No, almost all my panics are related to netgraph, chains are like ip_fastforward() - ng_rmnode_self() - ng_address_hook() - trap sendto() - kern_sendit() - sosend_generic() - ng_parse_get_token() - ... - trap Only one of my panics was unrelated to netgraph, with igmp_change_state() in trace. > May be there is some kind of memory corruption? May be try memguard(9)? I can try memguard too, please tell again what setting should I use. One more thing: I've noticed my traced show there are plenty of recursive calls, for example (from my letter of 07.02): panic: page fault cpuid = 1 KDB: stack backtrace: X_db_sym_numargs() at 0xffffffff801a227a = X_db_sym_numargs+0x15a kdb_backtrace() at 0xffffffff8033d547 = kdb_backtrace+0x37 panic() at 0xffffffff8030b567 = panic+0x187 dblfault_handler() at 0xffffffff804c0ca0 = dblfault_handler+0x330 dblfault_handler() at 0xffffffff804c107f = dblfault_handler+0x70f trap() at 0xffffffff804c155f = trap+0x3df calltrap() at 0xffffffff804a8de4 = calltrap+0x8 --- trap 0xc, rip = 0xffffffff803e4f36, rsp = 0xffffff80ebff7400, rbp = 0xffffff80ebff7430 --- ng_parse_get_token() at 0xffffffff803e4f36 = ng_parse_get_token+0x6596 ng_parse_get_token() at 0xffffffff803e5ccf = ng_parse_get_token+0x732f ng_destroy_hook() at 0xffffffff803d53b2 = ng_destroy_hook+0x222 ng_rmnode() at 0xffffffff803d6118 = ng_rmnode+0xa08 ng_snd_item() at 0xffffffff803d8520 = ng_snd_item+0x3f0 ng_destroy_hook() at 0xffffffff803d52ed = ng_destroy_hook+0x15d ng_rmnode() at 0xffffffff803d57b9 = ng_rmnode+0xa9 ng_rmnode() at 0xffffffff803d7664 = ng_rmnode+0x1f54 ng_snd_item() at 0xffffffff803d8520 = ng_snd_item+0x3f0 ng_parse_get_token() at 0xffffffff803e97fa = ng_parse_get_token+0xae5a sosend_generic() at 0xffffffff80373df6 = sosend_generic+0x436 kern_sendit() at 0xffffffff803776d5 = kern_sendit+0x1a5 kern_sendit() at 0xffffffff8037790c = kern_sendit+0x3dc sendto() at 0xffffffff803779fd = sendto+0x4d syscallenter() at 0xffffffff8034a015 = syscallenter+0x1e5 syscall() at 0xffffffff804c10fb = syscall+0x4b Xfast_syscall() at 0xffffffff804a90c2 = Xfast_syscall+0xe2 --- syscall (133, FreeBSD ELF64, sendto), rip = 0x8018c971c, rsp = 0x7fffffbfeab8, rbp = 0x80203dcc0 --- Uptime: 2d17h1m42s Is it normal, is NETGRAPH protected from such execution flow? Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 10:54:41 2011 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 E21C6106564A for ; Wed, 16 Feb 2011 10:54:41 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 4D5F88FC08 for ; Wed, 16 Feb 2011 10:54:40 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.4/8.14.4) with ESMTP id p1GANV5I087658; Wed, 16 Feb 2011 13:23:31 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.4/8.14.4/Submit) id p1GANVC5087657; Wed, 16 Feb 2011 13:23:31 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 16 Feb 2011 13:23:30 +0300 From: Gleb Smirnoff To: Eugene Grosbein Message-ID: <20110216102330.GJ42041@glebius.int.ru> References: <20110131144838.GO62007@FreeBSD.org> <4D46F655.9000701@rdtc.ru> <20110131204816.GV62007@glebius.int.ru> <4D5A989E.8020703@sentex.net> <4D5B4F07.6080801@rdtc.ru> <20110216084635.GI42041@glebius.int.ru> <4D5B9309.30508@rdtc.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4D5B9309.30508@rdtc.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Przemyslaw Frasunek , Mike Tancsa , mav@FreeBSD.org, bz@FreeBSD.org, "net@freebsd.org" , julian@FreeBSD.org Subject: Re: Netgraph/mpd5 stability issues X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 10:54:42 -0000 On Wed, Feb 16, 2011 at 03:04:09PM +0600, Eugene Grosbein wrote: E> On 16.02.2011 14:46, Gleb Smirnoff wrote: E> > On Wed, Feb 16, 2011 at 10:13:59AM +0600, Eugene Grosbein wrote: E> > E> I run AMD64 with 4GB of memory, lots of memory is free and E> > E> I still get panics often, sometimes two in a couple of hours. E> > E> It does not seem memory exhaustion to me. It seems as very low probable race E> > E> that happens occasionally but may happen any time. E> > E> E> > E> With Gleb's patch, it is obvious that panic happens at moments of user disconnect. E> > E> > I missed: did my patch fix panics in the ng_address_hook(), in this block? E> > E> > if ((hook == NULL) || E> > NG_HOOK_NOT_VALID(hook) || E> > NG_HOOK_NOT_VALID(peer = NG_HOOK_PEER(hook)) || E> > NG_NODE_NOT_VALID(peernode = NG_PEER_NODE(hook))) { E> > NG_FREE_ITEM(item); E> > TRAP_ERROR(); E> > return (ENETDOWN); E> > } E> E> It seems, yes. All my panics now are in _chkhook() being called E> with bad hook as first argument. That is because of NETGRAPH_DEBUG, not my patch :(. Unfortunately, we don't have coredumps and can't tell whether locking the destroy path helped or not. E> Only one of my panics was unrelated to netgraph, with igmp_change_state() in trace. E> E> > May be there is some kind of memory corruption? May be try memguard(9)? E> E> I can try memguard too, please tell again what setting should I use. You need to set vm.memguard.desc to a memory type you want to monitor. You can try for some time (several hours) all netgraph related memory types: vmstat -m | grep -i netgraph | awk '{print $1}' E> One more thing: I've noticed my traced show there are plenty of recursive calls, E> for example (from my letter of 07.02): ... E> Is it normal, is NETGRAPH protected from such execution flow? Yes, this is weird. For example kern_sendit() can't call kern_sendit() for sure. Most other double calls in the trace are weird too. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 13:20:29 2011 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 5114B1065675; Wed, 16 Feb 2011 13:20:29 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id AC2318FC0A; Wed, 16 Feb 2011 13:20:28 +0000 (UTC) Received: by fxm16 with SMTP id 16so1355173fxm.13 for ; Wed, 16 Feb 2011 05:20:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=WZJEqXNGmfpgT8YXG1RonNBauCJ8BRRFaK4ejNZn3JU=; b=IeM7dJLiHVlfYqO6RBAmzdl7YZsZWZ2XxHUISKYBKaxHnLkQUZcXXx/yS6Nchns6z2 /8jnaAwT3mneYji7W2aPtrSEuspNRlhGvTlrhuKyaU9O+K4wruuHJ+bqfYhQpkgGhWwB 5TqdbuFi0Vzd54Ms3HHC8GM2VG+vLGbrkbYrQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=mY/tB3qJeGm440adoSSSeHXfp4/s7t+PSC46mfPqsaw3fl7PVjo8/ip+n3FI9IM7WZ l5BIOdjC3Ixp/SytLoMnnaykufV4bhse4zJx2kA51ZA/C+hugGw5UGdn5p1zUCMzjaCy chC3LKzp9lX+Pl1cUuNXGFzhGKjEJyarWtcZA= Received: by 10.223.101.202 with SMTP id d10mr718531fao.132.1297862427540; Wed, 16 Feb 2011 05:20:27 -0800 (PST) Received: from ndenevsa.sf.moneybookers.net (g1.moneybookers.com [217.18.249.148]) by mx.google.com with ESMTPS id j12sm15388fax.33.2011.02.16.05.20.24 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Feb 2011 05:20:24 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Nikolay Denev In-Reply-To: <5516808338355511684@unknownmsgid> Date: Wed, 16 Feb 2011 15:20:22 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <7DACE499-8AE3-427B-99EB-39618699625F@gmail.com> References: <4D5AAA28.50408@freebsd.org> <5516808338355511684@unknownmsgid> To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.1082) Cc: Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 13:20:29 -0000 On 15 Feb, 2011, at 21:08 , Nikolay Denev wrote: > On 15.02.2011, at 18:53, Arnaud Lacombe wrote: >=20 >> Hi, >>=20 >> On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer = wrote: >>> changing it to '_' might be accceptable, '.' is much like '/' in th >>> filesystem. >>> it is a separator. You can't have it in the name. >>> a patch that converted . to _ would be a nice idea. >>> please ensure that the man page is updated as well. >>>=20 >> Doesn't FreeBSD care about kernel/userland backward interface >> compatibility at all ? ie. will all my scripts assuming '.' as a >> separator need to also check the FreeBSD version to use whatever path >> separator ? How would you do that with bare ngctl script, which = cannot >> be really that evolved ? How do you deal with node in the wild = already >> using '_' in their name ? >>=20 >> Thanks, >> - Arnaud >=20 > I'm actually thinking on doing the check and replacement of dots in > ng_ether, so it won't affect other netgraph consumers. >=20 > Regards, > Nikolay Does this look reasonable? : [14:57]root@nas:/home/ndenev# ifconfig sge0.13 create [14:57]root@nas:/home/ndenev# ifconfig sge0.14 create [14:57]root@nas:/home/ndenev# ifconfig sge0.14 name sge0:14 [14:58]root@nas:/home/ndenev# kldload ng_ether [14:58]root@nas:/home/ndenev# ngctl l There are 5 total nodes: Name: sge0_13 Type: ether ID: 00000003 Num hooks: = 0 Name: sge0_14 Type: ether ID: 00000004 Num hooks: = 0 Name: ipfw0 Type: ether ID: 00000002 Num hooks: = 0 Name: ngctl1685 Type: socket ID: 00000005 Num hooks: = 0 Name: sge0 Type: ether ID: 00000001 Num hooks: = 0 This is the patch to ng_ether which replaces both dots and colons with = underscore. I'm unsure about changing them both to underscore, and a colon in = interface name does not seem like something common. So I can rework it to replace only dots. Patch URL : http://ndenev.ath.cx/patches/ng_ether_namemangling.patch --- sys/netgraph/ng_ether.c.orig 2011-02-15 19:29:09.706568297 = +0200 +++ sys/netgraph/ng_ether.c 2011-02-16 15:11:03.138114973 +0200 @@ -285,6 +285,8 @@ { priv_p priv; node_p node; + int i; + char name[IFNAMSIZ]; =20 /* * Do not create / attach an ether node to this ifnet if @@ -319,10 +321,22 @@ IFP2NG(ifp) =3D node; priv->hwassist =3D ifp->if_hwassist; =20 - /* Try to give the node the same name as the interface */ - if (ng_name_node(node, ifp->if_xname) !=3D 0) { + /* + * Try to give the node the same name as the interface + * replacing netgraph reserved characters (dot and colon) + */ + for (i =3D 0; i < IFNAMSIZ; i++) { + if (ifp->if_xname[i] =3D=3D '.' || ifp->if_xname[i] =3D=3D= ':') { + name[i] =3D '_'; + } else { + name[i] =3D ifp->if_xname[i]; + } + if (ifp->if_xname[i] =3D=3D '\0') + break; + } + if (ng_name_node(node, name) !=3D 0) { log(LOG_WARNING, "%s: can't name node %s\n", - __func__, ifp->if_xname); + __func__, name); } } --- ng_ether.4.orig 2011-02-16 15:16:11.775255282 +0200 +++ ng_ether.4 2011-02-16 15:18:53.114257799 +0200 @@ -54,7 +54,8 @@ module is loaded into the kernel, a node is automatically created for each Ethernet interface in the system. Each node will attempt to name itself with the same name -as the associated interface. +as the associated interface, substituting netgraph reserved +characters in the name with underscores. .Pp Three hooks are supported: .Va lower , upper , From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 15:47:43 2011 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 8FC771065673 for ; Wed, 16 Feb 2011 15:47:43 +0000 (UTC) (envelope-from jayb@zoe.braeburn.org) Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by mx1.freebsd.org (Postfix) with ESMTP id 336A68FC15 for ; Wed, 16 Feb 2011 15:47:42 +0000 (UTC) X-VirusChecked: Checked X-Env-Sender: jayb@zoe.braeburn.org X-Msg-Ref: server-15.tower-119.messagelabs.com!1297871262!5243394!1 X-StarScan-Version: 6.2.9; banners=-,-,- X-Originating-IP: [144.160.20.145] Received: (qmail 29545 invoked from network); 16 Feb 2011 15:47:42 -0000 Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-15.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Feb 2011 15:47:42 -0000 Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p1GFm5vD013418 for ; Wed, 16 Feb 2011 10:48:05 -0500 Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p1GFlx7r013262 for ; Wed, 16 Feb 2011 10:47:59 -0500 Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p1GFlZ0d018064 for ; Wed, 16 Feb 2011 10:47:35 -0500 Received: from oz.mt.att.com (oz.mt.att.com [135.16.165.23]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p1GFlVAn017728 for ; Wed, 16 Feb 2011 10:47:31 -0500 Received: by oz.mt.att.com (Postfix, from userid 500) id E383F2BF2C; Wed, 16 Feb 2011 10:47:30 -0500 (EST) X-Mailer: emacs 21.2.1 (via feedmail 8 I); VM 7.18 under Emacs 21.2.1 Message-ID: <19803.61841.359853.307539@oz.mt.att.com> Date: Wed, 16 Feb 2011 10:47:29 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Jay Borkenhagen To: freebsd-net@freebsd.org X-GPG-Fingerprint: DDDB 542E D988 94D0 82D3 D198 7DED 6648 2308 D3C0 Sender: jayb@zoe.braeburn.org Subject: seeking recommendation: 1000Base-SX PCI NIC for FreeBSD 8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jay Borkenhagen List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2011 15:47:43 -0000 Hi, After having been disappointed by one vendor *, I am returning to this list to seek recommendations for 1000Base-SX PCI NICs. I am looking to run them on FreeBSD 8 and beyond, and I need support for MTU > 1500 bytes (initially around 4470, but possibly closer to 9k later). On http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET I found mention of several "SX" cards, but I have first-hand experience with none of them. If anyone here can confirm jumbo support and current retail availability of any such cards, I would be very appreciative. Thanks! Jay B. * - disappointed more by the attitude than the technical aspects. From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 16:14:54 2011 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 C5F581065670 for ; Wed, 16 Feb 2011 16:14:54 +0000 (UTC) (envelope-from canevet@embl.fr) Received: from emblmta1.embl.fr (emblmta1.embl.fr [193.49.43.176]) by mx1.freebsd.org (Postfix) with ESMTP id 62E3C8FC1D for ; Wed, 16 Feb 2011 16:14:54 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.60,480,1291590000"; d="asc'?scan'208";a="1106606" Received: from unknown (HELO [172.26.15.11]) ([172.26.15.11]) by emblmta1.embl.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 16 Feb 2011 16:45:13 +0100 From: =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= To: freebsd-fs@freebsd.org, freebsd-net@freebsd.org In-Reply-To: <1297870150.3097.30.camel@pc286.embl.fr> References: <1297858944.3097.20.camel@pc286.embl.fr> <1297870150.3097.30.camel@pc286.embl.fr> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-lPyBYh3OoVl54tUoAhA2" Date: Wed, 16 Feb 2011 16:45:19 +0100 Message-ID: <1297871119.3097.36.camel@pc286.embl.fr> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Cc: Subject: Re: showmount sometimes slow with carp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 16:14:54 -0000 --=-lPyBYh3OoVl54tUoAhA2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi again, again, The problem seams to be even more general (so I put freebsd-net in copy). When I ping carp interface, I lost some pings... ping data-test PING data-test.embl.fr (172.26.9.236) 56(84) bytes of data. 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D7 ttl=3D64 time=3D0.183 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D8 ttl=3D64 time=3D0.217 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D23 ttl=3D64 time=3D0.273 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D24 ttl=3D64 time=3D0.217 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D25 ttl=3D64 time=3D0.219 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D26 ttl=3D64 time=3D0.132 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D27 ttl=3D64 time=3D0.203 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D28 ttl=3D64 time=3D0.157 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D29 ttl=3D64 time=3D0.191 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D30 ttl=3D64 time=3D0.238 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D31 ttl=3D64 time=3D0.226 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D32 ttl=3D64 time=3D0.272 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D33 ttl=3D64 time=3D0.215 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D36 ttl=3D64 time=3D0.180 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D37 ttl=3D64 time=3D0.314 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D38 ttl=3D64 time=3D0.169 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D39 ttl=3D64 time=3D0.206 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D40 ttl=3D64 time=3D0.170 ms 64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=3D41 ttl=3D64 time=3D0.158 ms ^C --- data-test.embl.fr ping statistics --- 41 packets transmitted, 19 received, 53% packet loss, time 40184ms rtt min/avg/max/mdev =3D 0.132/0.207/0.314/0.045 ms Is it a bug, or am I doing something wrong ? Here is my network configuration: defaultrouter=3D"172.26.9.254" hostname=3D"pc234.embl.fr" cloned_interfaces=3D"lagg0 carp0" ifconfig_bge0=3D"up" ifconfig_em0=3D"up" ifconfig_em1=3D"172.26.14.234/24" ifconfig_lagg0=3D"laggproto failover laggport bge0 laggport em0" ipv4_addrs_lagg0=3D"172.26.9.234/24" ifconfig_carp0=3D"vhid 1 pass 497500fd0f6c3988d1f advskew 10 172.26.9.236/24" Tomorrow I'll try with a carp interface that is not over a network bonding to see if the problem comes from that. Micka=C3=ABl On Wed, 2011-02-16 at 16:29 +0100, Micka=C3=ABl Can=C3=A9vet wrote: > Hi again, >=20 > I also have a problem when I mount an exported filesystem through the > carp VIP. >=20 > When I do that: >=20 > mount :/data/user /mnt > while true; do time df -H /mnt > /dev/null; sleep 5; done 2>&1 | grep > ^real >=20 > real 0m0.004s > real 0m0.004s > real 0m0.004s > real 0m0.004s > real 0m0.004s > ... >=20 > But when I do that: >=20 > mount :/data/user /mnt > while true; do time df -H /mnt > /dev/null; sleep 5; done 2>&1 | grep > ^real > real 0m0.005s > real 0m0.207s > real 0m0.206s > real 0m52.150s > real 0m0.004s > real 0m0.004s > real 0m0.002s > real 0m0.204s > real 0m0.206s > real 0m0.614s > real 0m0.004s > real 0m0.207s > real 0m0.205s > real 0m0.206s > real 0m0.206s > real 0m0.613s > real 0m0.003s >=20 > Every now and then I have a long delay with the vip that I don't have > with the real IP or an alias... >=20 > On Wed, 2011-02-16 at 13:22 +0100, Micka=C3=ABl Can=C3=A9vet wrote: > > Hi, > >=20 > > I installed a redundant NAS with FreeBSD 8.2RC3 + Hast + ZFS + Carp. > >=20 > > Each machine has its own IP address, and share a virtual IP with carp. > >=20 > > When I launch 'showmount -e ' from a linux client > > or a freebsd client, I got my answer immediately (about 5ms). But when = I > > try with carp virtual IP or FQDN, it sometimes takes around 20 seconds, > > or even 1 minute, but not everytime. > >=20 > > It is really annoying because automount, at least the linux version, > > seams to use showmount to get server exports. So it sometimes does not > > work through the carp virtual IP. > >=20 > > Can anybody help me ? > >=20 > > Thanks a lot, > >=20 > > Micka=C3=ABl >=20 --=-lPyBYh3OoVl54tUoAhA2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk1b8Q8ACgkQZjBmN5Hi/YZtJQCgjAybI68s9DyqnQIkm4SaXPI7 GvUAn2q+wv2XqgeXVNGsoOJ1CxODYc5B =c3hP -----END PGP SIGNATURE----- --=-lPyBYh3OoVl54tUoAhA2-- From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 16:21:25 2011 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 ABFC21065672 for ; Wed, 16 Feb 2011 16:21:25 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4409B8FC08 for ; Wed, 16 Feb 2011 16:21:24 +0000 (UTC) Received: by bwz12 with SMTP id 12so1608489bwz.13 for ; Wed, 16 Feb 2011 08:21:24 -0800 (PST) Received: by 10.204.66.130 with SMTP id n2mr619336bki.175.1297871399545; Wed, 16 Feb 2011 07:49:59 -0800 (PST) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id f20sm233859bkf.4.2011.02.16.07.49.58 (version=SSLv3 cipher=OTHER); Wed, 16 Feb 2011 07:49:59 -0800 (PST) Message-ID: <4D5BF225.4060500@my.gd> Date: Wed, 16 Feb 2011 16:49:57 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-fs@freebsd.org, canevet@embl.fr References: <1297858944.3097.20.camel@pc286.embl.fr> <1297870150.3097.30.camel@pc286.embl.fr> <1297871119.3097.36.camel@pc286.embl.fr> In-Reply-To: <1297871119.3097.36.camel@pc286.embl.fr> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: showmount sometimes slow with carp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 16:21:25 -0000 You're using POLLING on your physical interfaces. Sometimes they go down and you lose your CARP interface. OR For whatever reason you lose your CARP interface. Get the output from `dmesg` , see if you get logs saying your carp interface went down then back up, there are high chances it did. Post your dmesg Post your ifconfig Post your rc.conf Cheers ;) On 2/16/11 4:45 PM, Mickaël Canévet wrote: >> Every now and then I have a long delay with the vip that I don't have >> with the real IP or an alias... >> >> On Wed, 2011-02-16 at 13:22 +0100, Mickaël Canévet wrote: >>> Hi, >>> >>> I installed a redundant NAS with FreeBSD 8.2RC3 + Hast + ZFS + Carp. >>> >>> Each machine has its own IP address, and share a virtual IP with carp. >>> >>> When I launch 'showmount -e ' from a linux client >>> or a freebsd client, I got my answer immediately (about 5ms). But when I >>> try with carp virtual IP or FQDN, it sometimes takes around 20 seconds, >>> or even 1 minute, but not everytime. >>> >>> It is really annoying because automount, at least the linux version, >>> seams to use showmount to get server exports. So it sometimes does not >>> work through the carp virtual IP. >>> >>> Can anybody help me ? >>> >>> Thanks a lot, >>> >>> Mickaël >> > From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 17:09:39 2011 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 4FEA2106564A for ; Wed, 16 Feb 2011 17:09:39 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 2BB448FC16 for ; Wed, 16 Feb 2011 17:09:38 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p1GH9WLR000541 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 16 Feb 2011 09:09:37 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4D5C04DD.3020704@freebsd.org> Date: Wed, 16 Feb 2011 09:09:49 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Nikolay Denev References: <4D5AAA28.50408@freebsd.org> <5516808338355511684@unknownmsgid> <7DACE499-8AE3-427B-99EB-39618699625F@gmail.com> In-Reply-To: <7DACE499-8AE3-427B-99EB-39618699625F@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 17:09:39 -0000 On 2/16/11 5:20 AM, Nikolay Denev wrote: > On 15 Feb, 2011, at 21:08 , Nikolay Denev wrote: > >> On 15.02.2011, at 18:53, Arnaud Lacombe wrote: >> >>> Hi, >>> >>> On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote: >>>> changing it to '_' might be accceptable, '.' is much like '/' in th >>>> filesystem. >>>> it is a separator. You can't have it in the name. >>>> a patch that converted . to _ would be a nice idea. >>>> please ensure that the man page is updated as well. >>>> >>> Doesn't FreeBSD care about kernel/userland backward interface >>> compatibility at all ? ie. will all my scripts assuming '.' as a >>> separator need to also check the FreeBSD version to use whatever path >>> separator ? How would you do that with bare ngctl script, which cannot >>> be really that evolved ? How do you deal with node in the wild already >>> using '_' in their name ? >>> >>> Thanks, >>> - Arnaud >> I'm actually thinking on doing the check and replacement of dots in >> ng_ether, so it won't affect other netgraph consumers. >> >> Regards, >> Nikolay > Does this look reasonable? : > > [14:57]root@nas:/home/ndenev# ifconfig sge0.13 create > [14:57]root@nas:/home/ndenev# ifconfig sge0.14 create > [14:57]root@nas:/home/ndenev# ifconfig sge0.14 name sge0:14 > [14:58]root@nas:/home/ndenev# kldload ng_ether > [14:58]root@nas:/home/ndenev# ngctl l > There are 5 total nodes: > Name: sge0_13 Type: ether ID: 00000003 Num hooks: 0 > Name: sge0_14 Type: ether ID: 00000004 Num hooks: 0 > Name: ipfw0 Type: ether ID: 00000002 Num hooks: 0 > Name: ngctl1685 Type: socket ID: 00000005 Num hooks: 0 > Name: sge0 Type: ether ID: 00000001 Num hooks: 0 > > This is the patch to ng_ether which replaces both dots and colons with underscore. > I'm unsure about changing them both to underscore, and a colon in interface name does > not seem like something common. So I can rework it to replace only dots. > > > Patch URL : http://ndenev.ath.cx/patches/ng_ether_namemangling.patch > > --- sys/netgraph/ng_ether.c.orig 2011-02-15 19:29:09.706568297 +0200 > +++ sys/netgraph/ng_ether.c 2011-02-16 15:11:03.138114973 +0200 > @@ -285,6 +285,8 @@ > { > priv_p priv; > node_p node; > + int i; > + char name[IFNAMSIZ]; > > /* > * Do not create / attach an ether node to this ifnet if > @@ -319,10 +321,22 @@ > IFP2NG(ifp) = node; > priv->hwassist = ifp->if_hwassist; > > - /* Try to give the node the same name as the interface */ > - if (ng_name_node(node, ifp->if_xname) != 0) { > + /* > + * Try to give the node the same name as the interface > + * replacing netgraph reserved characters (dot and colon) > + */ > + for (i = 0; i< IFNAMSIZ; i++) { > + if (ifp->if_xname[i] == '.' || ifp->if_xname[i] == ':') { > + name[i] = '_'; > + } else { > + name[i] = ifp->if_xname[i]; > + } > + if (ifp->if_xname[i] == '\0') > + break; > + } > + if (ng_name_node(node, name) != 0) { > log(LOG_WARNING, "%s: can't name node %s\n", > - __func__, ifp->if_xname); > + __func__, name); > } > } > looks good to me > --- ng_ether.4.orig 2011-02-16 15:16:11.775255282 +0200 > +++ ng_ether.4 2011-02-16 15:18:53.114257799 +0200 > @@ -54,7 +54,8 @@ > module is loaded into the kernel, a node is automatically created > for each Ethernet interface in the system. > Each node will attempt to name itself with the same name > -as the associated interface. > +as the associated interface, substituting netgraph reserved > +characters in the name with underscores. > .Pp > Three hooks are supported: > .Va lower , upper , > > > From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 18:26:50 2011 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 4EB72106564A for ; Wed, 16 Feb 2011 18:26:50 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate.funkthat.com [70.36.235.232]) by mx1.freebsd.org (Postfix) with ESMTP id 247778FC1E for ; Wed, 16 Feb 2011 18:26:49 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id p1GIFh0d036544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Feb 2011 10:15:43 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id p1GIFhkD036543; Wed, 16 Feb 2011 10:15:43 -0800 (PST) (envelope-from jmg) Date: Wed, 16 Feb 2011 10:15:43 -0800 From: John-Mark Gurney To: Jay Borkenhagen Message-ID: <20110216181543.GT66284@funkthat.com> Mail-Followup-To: Jay Borkenhagen , freebsd-net@freebsd.org References: <19803.61841.359853.307539@oz.mt.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19803.61841.359853.307539@oz.mt.att.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 16 Feb 2011 10:15:43 -0800 (PST) Cc: freebsd-net@freebsd.org Subject: Re: seeking recommendation: 1000Base-SX PCI NIC for FreeBSD 8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 18:26:50 -0000 Jay Borkenhagen wrote this message on Wed, Feb 16, 2011 at 10:47 -0500: > After having been disappointed by one vendor *, I am returning to this > list to seek recommendations for 1000Base-SX PCI NICs. I am looking > to run them on FreeBSD 8 and beyond, and I need support for MTU > 1500 > bytes (initially around 4470, but possibly closer to 9k later). > > On http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET I found > mention of several "SX" cards, but I have first-hand experience with > none of them. If anyone here can confirm jumbo support and current > retail availability of any such cards, I would be very appreciative. One option is to use an external media converter w/ a traditional gige NIC... I used one for a while when interfacing with a switch that did not have a copper gige port on it, only SX ports... I will admit I didn't try to run jumbo frames with the TrendNET one I had, but it work great for many years... searching for "1000base-sx media converter" should turn up plenty of results... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 19:26:23 2011 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 CD415106564A for ; Wed, 16 Feb 2011 19:26:23 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 896AD8FC1A for ; Wed, 16 Feb 2011 19:26:22 +0000 (UTC) Received: by iwn39 with SMTP id 39so1688808iwn.13 for ; Wed, 16 Feb 2011 11:26:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=YShOBwogfQbb06UIm5YvR4FcuVhJzEiW+RGCkm2dIZs=; b=o6ADJhwcPX0yl57z57PqDjJjWMBwQ732GrBq+aiuwZZ4zShPgM6/ANk9s7wedCRxGx 4xSyXSC2fCgE41VeVvi+/OBuPIL+eAD5SAhcoOS8PJjlqxKkuTaswNkrY1S1N41bywSd gCtLuXMfrjHaQaqlXqFOQwt6z6YEtOl40YUdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=PMkY6OcBC2BGjkU+wYPeDiU+RKx1ctLUZZX4GiA1anXdvKNxSWrUu3F5m0bhUrt3BV /rbLyP7cvrw6Vj9rt1ao6s/i3XGD6c1lBL4pFErAJY6xWwrmxZIbGXBokh5ztKijV+nb DzBkPfHe1U5UMDePk7LlCMEsJRnvXKLSfLB48= MIME-Version: 1.0 Received: by 10.42.224.71 with SMTP id in7mr1460277icb.432.1297884382045; Wed, 16 Feb 2011 11:26:22 -0800 (PST) Received: by 10.42.164.201 with HTTP; Wed, 16 Feb 2011 11:26:22 -0800 (PST) In-Reply-To: References: <12838373-FE96-443E-8979-AF5408705BF0@freebsd.org> Date: Wed, 16 Feb 2011 14:26:22 -0500 Message-ID: From: Arnaud Lacombe To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Cc: Karim Fodil-Lemelin , freebsd-net@freebsd.org Subject: Re: igb driver RX (was TX) hangs when out of mbuf clusters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 19:26:23 -0000 Hi Jack, On Fri, Feb 11, 2011 at 2:57 PM, Jack Vogel wrote: > Yes, it was the fix for this, Mike has tested and confirmed it eliminates > the problem, and yes > I will MFC the relevant bits back to 8 and 7 for you asap. > I can confirm this works too. A machine showing the symptoms in a couple of minutes with heavy traffic has been running in the last few days with the backport of all the changes. I did not cared much to do things cleanly at the time. Do you have any approximate ETA for the MFC of the relevant bits ? Thanks in advance, - Arnaud From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 19:30:44 2011 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 CE701106566C for ; Wed, 16 Feb 2011 19:30:44 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7B4B38FC1E for ; Wed, 16 Feb 2011 19:30:44 +0000 (UTC) Received: by gwj21 with SMTP id 21so788543gwj.13 for ; Wed, 16 Feb 2011 11:30:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=RO2blLSmKnStCtUi/GY8pHrdMYngr9G5dypz5rDLAfg=; b=RKdN7gOfz4rZXFCUIy2DBXOAsklYqzbTvlBdAh5Kq7IBYFNTZ1BD5og8uy5OvD00RM s5i3avgjxKyJDoFCXxLZF/roAEFM4fsxJ5DIq7y/1YH89PrTN1iLX3WtyP5uDJ+11MNE hJ+Rm8gqEVZSTkfewgNEeRP2KEcHibr+THnUY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Gg5DdYE1QarfyfE5WtYMqpt60yp2Jt4Kqakat7Gpbhms4aYNdIlPSdIjryFdvWxbJ1 dnMyAbTCxi7i2vF/dQWruIQU1v2lVj35ruG7shT7SCdlshpQnfvV+Gg7B9IuYmLhmJLI jAxxHzh31Eqx8ZMZ+j2eRdIpWcZZiV4SE14VI= MIME-Version: 1.0 Received: by 10.150.211.17 with SMTP id j17mr1215884ybg.225.1297884643540; Wed, 16 Feb 2011 11:30:43 -0800 (PST) Received: by 10.147.167.5 with HTTP; Wed, 16 Feb 2011 11:30:42 -0800 (PST) In-Reply-To: References: <12838373-FE96-443E-8979-AF5408705BF0@freebsd.org> Date: Wed, 16 Feb 2011 11:30:42 -0800 Message-ID: From: Jack Vogel To: Arnaud Lacombe Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Karim Fodil-Lemelin , freebsd-net@freebsd.org Subject: Re: igb driver RX (was TX) hangs when out of mbuf clusters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 19:30:45 -0000 I've been in email conversation with Beezar, and he's clarified some things, I think I would like to try his approach to the issue, it will mean one more iteration of changes to test, would you be willing to do so? It would be good to know for sure if his approach also eliminates the problem. Jack On Wed, Feb 16, 2011 at 11:26 AM, Arnaud Lacombe wrote: > Hi Jack, > > On Fri, Feb 11, 2011 at 2:57 PM, Jack Vogel wrote: > > Yes, it was the fix for this, Mike has tested and confirmed it eliminates > > the problem, and yes > > I will MFC the relevant bits back to 8 and 7 for you asap. > > > I can confirm this works too. A machine showing the symptoms in a > couple of minutes with heavy traffic has been running in the last few > days with the backport of all the changes. I did not cared much to do > things cleanly at the time. Do you have any approximate ETA for the > MFC of the relevant bits ? > > Thanks in advance, > - Arnaud > From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 19:52:45 2011 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 47AB2106564A for ; Wed, 16 Feb 2011 19:52:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id F2F0A8FC19 for ; Wed, 16 Feb 2011 19:52:44 +0000 (UTC) Received: by gyc15 with SMTP id 15so794226gyc.13 for ; Wed, 16 Feb 2011 11:52:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nvXVR0vA6t/4uTGu0qB2lzn85NAGOxSwQGv74d1znKA=; b=DL5OU8Yl+4/SMlvK/GqKkzXl1yjwHpt4/eTIMdS8GUzcx56Z2tzNYsMhpv7nspiOos joAaNvWPe7+SyQZsf/E1h3YtoGfXmbZtKTVk7L7Cnwgvih+PFzJsH1oWoTjngjwCeY/L 7sUjFJTIkv4D4EHMuMvkZNgktWIortU6sf9D8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=HTit0sZ80rdIqRyo0AvjWm9co3ioh5L579s/cOBUbA/rfIjLaXQtzd4yRJGHlS/J/c 4hNjVu/F6E5nj4Kpw9Xhz35F3CbohCDfuxbSXLaydIsWsz2h2BCGcSvbQBJxuOZuqIpt 0GSUrLDi+itje02QUedt3a5bOm+fP8+VQpH88= MIME-Version: 1.0 Received: by 10.151.108.14 with SMTP id k14mr1263836ybm.145.1297885963961; Wed, 16 Feb 2011 11:52:43 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.150.95.13 with HTTP; Wed, 16 Feb 2011 11:52:43 -0800 (PST) In-Reply-To: References: Date: Wed, 16 Feb 2011 14:52:43 -0500 X-Google-Sender-Auth: STVNr2X5Eo_gXU2eHITtZh6YREE Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: [ieee80211_hwmp][panic] hwmp_recv_prep(...) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 19:52:45 -0000 Besides being a potential DoS vector (and thus panicing on anything like that =3D=3D bad idea), what legitimate-but-broken circumstances could cause a node to hear its own announcement? Adrian On 15 February 2011 07:00, Monthadar Al Jaberi wrote: > Hej, > > I found that a panic can be generated when having a couple of > ieee80211s nodes in a line topology with one of them being a ROOT > node. A ping from ROOT in a newly started nodes causes a panic: > panic: ieee80211_mesh_rt_add: adding self to the routing table > KDB: enter: panic > [ thread pid 0 tid 100030 ] > Stopped at =A0 =A0 =A0kdb_enter+0x50: lui =A0 =A0 at,0x804e > db> > > This is because we receive a copy of our own generated > IEEE80211_ELEMID_MESHPREP packet from our neighbor node. > I added check code in the begining of hwmp_recv_prep(...) similar to > the check code found in hwmp_recv_preq(...). Here is a diff output: > > --- freebsd/head/sys/net80211/ieee80211_hwmp.c =A02010-11-03 > 09:29:25.023610380 +0000 > +++ src/head-current/sys/net80211/ieee80211_hwmp.c =A0 =A0 =A02011-02-15 > 10:06:02.526163874 +0000 > @@ -28,7 +28,7 @@ > =A0*/ > =A0#include > =A0#ifdef __FreeBSD__ > -__FBSDID("$FreeBSD$"); > +__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_hwmp.c,v 1.4.2.7.2.1 > 2010/12/21 17:09:25 kensmith Exp $"); > =A0#endif > > =A0/* > @@ -951,6 +951,12 @@ > =A0 =A0 =A0 =A0if (ni =3D=3D vap->iv_bss || > =A0 =A0 =A0 =A0 =A0 =A0ni->ni_mlstate !=3D IEEE80211_NODE_MESH_ESTABLISHE= D) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return; > + =A0 =A0 =A0 /* > + =A0 =A0 =A0 =A0* Ignore PREPs from us. Could happen because someone for= ward it > + =A0 =A0 =A0 =A0* back to us. > + =A0 =A0 =A0 =A0*/ > + =A0 =A0 =A0 if (IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_targetaddr= )) > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 return; > =A0 =A0 =A0 =A0if (!IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_origaddr= ) && > =A0 =A0 =A0 =A0 =A0 =A0!(ms->ms_flags & IEEE80211_MESHFLAGS_FWD)) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return; > > -- > //Monthadar Al Jaberi > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 20:51:45 2011 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 B6A3E1065673; Wed, 16 Feb 2011 20:51:45 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 25A5C8FC1C; Wed, 16 Feb 2011 20:51:44 +0000 (UTC) Received: by wyf19 with SMTP id 19so1771287wyf.13 for ; Wed, 16 Feb 2011 12:51:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7EfsWcp7Ku0qxBmH9i366JZMfBN1cpfublrwZ3S5YQE=; b=RhWdIy/c1SnGAwATTVXN/kgm8ZjYoLXN2kaKlwWGmMaQwFwPFnVC4rp3AhME8UV7Ih WwvU/maTqLeb9f76Lq8Lwn6HZuyk+dzFqsCch0XbynM1Zzl2POle01MeknUQoKi0ChjP bkkxaoXys+jlMi41Lc08YzARae4GFWGjSfm64= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iRbMem1Is1ozu6WUJ7kLcO7k07vLgYtKM1zMr0nzt8R7PYFqG6WMht+SOxjjAAz3FM QjHqedmBbGZ7TS9M8rXiimOVtBOsPi73sUTsDx78/0r6hKtNG0Mq7d7nAsgakItVAq6W y9tUwFzvszTxJkSxJlVqNYqhULaTZ7VeHBtIk= MIME-Version: 1.0 Received: by 10.227.128.70 with SMTP id j6mr932309wbs.16.1297889503871; Wed, 16 Feb 2011 12:51:43 -0800 (PST) Received: by 10.227.69.7 with HTTP; Wed, 16 Feb 2011 12:51:43 -0800 (PST) In-Reply-To: References: Date: Wed, 16 Feb 2011 21:51:43 +0100 Message-ID: From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: [ieee80211_hwmp][panic] hwmp_recv_prep(...) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 20:51:45 -0000 I think anytime the destination node sends a PREP to the originator node that is not a peering node (not in direct contact with) we would get this panic. On Wed, Feb 16, 2011 at 8:52 PM, Adrian Chadd wrote: > Besides being a potential DoS vector (and thus panicing on anything > like that =3D=3D bad idea), what legitimate-but-broken circumstances coul= d > cause a node to hear its own announcement? > > > > Adrian > > > On 15 February 2011 07:00, Monthadar Al Jaberi wrot= e: >> Hej, >> >> I found that a panic can be generated when having a couple of >> ieee80211s nodes in a line topology with one of them being a ROOT >> node. A ping from ROOT in a newly started nodes causes a panic: >> panic: ieee80211_mesh_rt_add: adding self to the routing table >> KDB: enter: panic >> [ thread pid 0 tid 100030 ] >> Stopped at =A0 =A0 =A0kdb_enter+0x50: lui =A0 =A0 at,0x804e >> db> >> >> This is because we receive a copy of our own generated >> IEEE80211_ELEMID_MESHPREP packet from our neighbor node. >> I added check code in the begining of hwmp_recv_prep(...) similar to >> the check code found in hwmp_recv_preq(...). Here is a diff output: >> >> --- freebsd/head/sys/net80211/ieee80211_hwmp.c =A02010-11-03 >> 09:29:25.023610380 +0000 >> +++ src/head-current/sys/net80211/ieee80211_hwmp.c =A0 =A0 =A02011-02-15 >> 10:06:02.526163874 +0000 >> @@ -28,7 +28,7 @@ >> =A0*/ >> =A0#include >> =A0#ifdef __FreeBSD__ >> -__FBSDID("$FreeBSD$"); >> +__FBSDID("$FreeBSD: src/sys/net80211/ieee80211_hwmp.c,v 1.4.2.7.2.1 >> 2010/12/21 17:09:25 kensmith Exp $"); >> =A0#endif >> >> =A0/* >> @@ -951,6 +951,12 @@ >> =A0 =A0 =A0 =A0if (ni =3D=3D vap->iv_bss || >> =A0 =A0 =A0 =A0 =A0 =A0ni->ni_mlstate !=3D IEEE80211_NODE_MESH_ESTABLISH= ED) >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return; >> + =A0 =A0 =A0 /* >> + =A0 =A0 =A0 =A0* Ignore PREPs from us. Could happen because someone fo= rward it >> + =A0 =A0 =A0 =A0* back to us. >> + =A0 =A0 =A0 =A0*/ >> + =A0 =A0 =A0 if (IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_targetadd= r)) >> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 return; >> =A0 =A0 =A0 =A0if (!IEEE80211_ADDR_EQ(vap->iv_myaddr, prep->prep_origadd= r) && >> =A0 =A0 =A0 =A0 =A0 =A0!(ms->ms_flags & IEEE80211_MESHFLAGS_FWD)) >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return; >> >> -- >> //Monthadar Al Jaberi >> _______________________________________________ >> 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" >> > --=20 //Monthadar Al Jaberi From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 21:09:39 2011 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 5E092106564A for ; Wed, 16 Feb 2011 21:09:39 +0000 (UTC) (envelope-from fodillemlinkarim@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 247988FC23 for ; Wed, 16 Feb 2011 21:09:38 +0000 (UTC) Received: by pwi10 with SMTP id 10so344529pwi.13 for ; Wed, 16 Feb 2011 13:09:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pqsw4rfGgBnl5XE+Aw6q1V1qUtnTK4USsXdZABnOm38=; b=hx7oh6yRm9TNFAEtmG4FJz61qydPmCZ2TfiBHfwJDr08r773zmu0SkQeWc9njkrSat RSp3jzqc7QY01alTgwHrpuRzRzhZNm3rB6zQwByAN2tvyFzJomgStyOyWtnfw8u3D8/f YtbJ1ElDNE7PFqSaSIfWqITmxgpGIvcE03l2I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=d+0M0Mdei6WunMR1cCOnP6KStVcAMxYYdKNp+6FXoXuHy1WqiSfDP0WIh4g+V/MJaK B0bCPz5Nmhi2n5W+LNzBo0YZ57izaUrGyjySV05+BFBMzNFxnOGaPO0rBksSuS7GW+43 oOdUmImIyudiYF5wemZ8/enN9QYqxNLw9MFC0= MIME-Version: 1.0 Received: by 10.143.161.17 with SMTP id n17mr786053wfo.314.1297890578358; Wed, 16 Feb 2011 13:09:38 -0800 (PST) Received: by 10.142.246.3 with HTTP; Wed, 16 Feb 2011 13:09:38 -0800 (PST) In-Reply-To: References: <12838373-FE96-443E-8979-AF5408705BF0@freebsd.org> Date: Wed, 16 Feb 2011 16:09:38 -0500 Message-ID: From: Karim Fodil-Lemelin To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Arnaud Lacombe Subject: Re: igb driver RX (was TX) hangs when out of mbuf clusters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 21:09:39 -0000 Yes. 2011/2/16 Jack Vogel > I've been in email conversation with Beezar, and he's clarified some > things, I think > I would like to try his approach to the issue, it will mean one more > iteration of changes > to test, would you be willing to do so? It would be good to know for sure > if his approach > also eliminates the problem. > > Jack > > > On Wed, Feb 16, 2011 at 11:26 AM, Arnaud Lacombe wrote: > >> Hi Jack, >> >> On Fri, Feb 11, 2011 at 2:57 PM, Jack Vogel wrote: >> > Yes, it was the fix for this, Mike has tested and confirmed it >> eliminates >> > the problem, and yes >> > I will MFC the relevant bits back to 8 and 7 for you asap. >> > >> I can confirm this works too. A machine showing the symptoms in a >> couple of minutes with heavy traffic has been running in the last few >> days with the backport of all the changes. I did not cared much to do >> things cleanly at the time. Do you have any approximate ETA for the >> MFC of the relevant bits ? >> >> Thanks in advance, >> - Arnaud >> > > From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 22:36:55 2011 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 947E7106564A for ; Wed, 16 Feb 2011 22:36:55 +0000 (UTC) (envelope-from przemyslaw@frasunek.com) Received: from lagoon.freebsd.lublin.pl (lagoon.freebsd.lublin.pl [IPv6:2a02:2928:a::3]) by mx1.freebsd.org (Postfix) with ESMTP id 24D818FC0A for ; Wed, 16 Feb 2011 22:36:55 +0000 (UTC) Received: from [IPv6:2a02:2928:a:ffff:d41d:ea8b:7ad2:4966] (unknown [IPv6:2a02:2928:a:ffff:d41d:ea8b:7ad2:4966]) by lagoon.freebsd.lublin.pl (Postfix) with ESMTPSA id 868FA23944A; Wed, 16 Feb 2011 23:36:53 +0100 (CET) Message-ID: <4D5C5187.9040702@frasunek.com> Date: Wed, 16 Feb 2011 23:36:55 +0100 From: Przemyslaw Frasunek Organization: frasunek.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; pl; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <4D3011DB.9050900@frasunek.com> <4D30458D.30007@sentex.net> <4D306421.1050501@rdtc.ru> In-Reply-To: <4D306421.1050501@rdtc.ru> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Eugene Grosbein , Mike Tancsa Subject: Re: Netgraph/mpd5 stability issues X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2011 22:36:55 -0000 > On 14.01.2011 18:46, Mike Tancsa wrote: > I also have very loaded mpd/PPPoE servers that panic all the time: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153255 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153671 I've just got yet another panic on mpd5 box after about 30 days of uptime. This time it seems to be unrelated with Netgraph: (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc0836ac7 in boot (howto=260) at ../../../kern/kern_shutdown.c:418 #2 0xc0836d99 in panic (fmt=Variable "fmt" is not available. ) at ../../../kern/kern_shutdown.c:574 #3 0xc0b5ef1c in trap_fatal (frame=0xc524fa2c, eva=56) at ../../../i386/i386/trap.c:950 #4 0xc0b5f1a0 in trap_pfault (frame=0xc524fa2c, usermode=0, eva=56) at ../../../i386/i386/trap.c:863 #5 0xc0b5fb95 in trap (frame=0xc524fa2c) at ../../../i386/i386/trap.c:541 #6 0xc0b42e7b in calltrap () at ../../../i386/i386/exception.s:166 #7 0xc0a683d0 in softdep_disk_io_initiation (bp=0xd96921e0) at ../../../ufs/ffs/ffs_softdep.c:3785 #8 0xc0a6e9ef in ffs_geom_strategy (bo=0xc58d10c0, bp=0xd96921e0) at buf.h:436 #9 0xc08a8830 in bufwrite (bp=0xd96921e0) at buf.h:429 #10 0xc0a6e3b8 in ffs_bufwrite (bp=0xd96921e0) at ../../../ufs/ffs/ffs_vfsops.c:1893 #11 0xc08a3af8 in vfs_bio_awrite (bp=0xd96921e0) at buf.h:417 #12 0xc08ad598 in vop_stdfsync (ap=0xc524fcd4) at ../../../kern/vfs_default.c:466 #13 0xc07bd3dc in devfs_fsync (ap=0xc524fcd4) at ../../../fs/devfs/devfs_vnops.c:499 #14 0xc0b743a2 in VOP_FSYNC_APV (vop=0xc0cd0e00, a=0xc524fcd4) at vnode_if.c:1007 #15 0xc08bdeb8 in sched_sync () at vnode_if.h:538 #16 0xc080e9f9 in fork_exit (callout=0xc08bd7b0 , arg=0x0, frame=0xc524fd38) at ../../../kern/kern_fork.c:811 #17 0xc0b42ef0 in fork_trampoline () at ../../../i386/i386/exception.s:271 (kgdb) frame 7 #7 0xc0a683d0 in softdep_disk_io_initiation (bp=0xd96921e0) at ../../../ufs/ffs/ffs_softdep.c:3785 3785 LIST_INSERT_AFTER(wk, &marker, wk_list); (kgdb) print *wk $4 = {wk_mp = 0x8, wk_list = {le_next = 0x30, le_prev = 0x3}, wk_type = 1, wk_state = 0} (kgdb) print *bp $5 = {b_bufobj = 0xc58d10c0, b_bcount = 16384, b_caller1 = 0x0, b_data = 0xde759000 "ýA\002", b_error = 0, b_iocmd = 2 '\002', b_ioflags = 2 '\002', b_iooffset = 16186277888, b_resid = 0, b_iodone = 0, b_blkno = 31613824, b_offset = 16186277888, b_bobufs = { tqe_next = 0xd96e4c5c, tqe_prev = 0xd9559d94}, b_left = 0x0, b_right = 0xd96e4c5c, b_vflags = 1, b_freelist = {tqe_next = 0xd955a2ec, tqe_prev = 0xd960ecf0}, b_qindex = 2, b_flags = 2684485668, b_xflags = 2 '\002', b_lock = {lk_object = {lo_name = 0xc0c114c5 "bufwait", lo_type = 0xc0c114c5 "bufwait", lo_flags = 70844416, lo_witness_data = { lod_list = {stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock = 0xc0d3c030, lk_flags = 262144, lk_sharecount = 0, lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 80, lk_timo = 0, lk_lockholder = 0xfffffffe, lk_newlock = 0x0}, b_bufsize = 16384, b_runningbufspace = 16384, b_kvabase = 0xde759000 "ýA\002", b_kvasize = 16384, b_lblkno = 31613824, b_vp = 0xc58d1000, b_dirtyoff = 0, b_dirtyend = 0, b_rcred = 0x0, b_wcred = 0x0, b_saveaddr = 0xde759000, b_pager = {pg_reqpage = 0}, b_cluster = {cluster_head = { tqh_first = 0xd955d234, tqh_last = 0xd9509d5c}, cluster_entry = { tqe_next = 0xd955d234, tqe_prev = 0xd9509d5c}}, b_pages = {0xc3843bd8, 0xc3842ab0, 0xc3843dd0, 0xc3843e18, 0x0 }, b_npages = 4, b_dep = {lh_first = 0xc672ca80}, b_fsprivate1 = 0x0, b_fsprivate2 = 0x0, b_fsprivate3 = 0x0, b_pin_count = 0} (kgdb) print *bp->b_dep->lh_first $17 = {wk_mp = 0x8, wk_list = {le_next = 0x30, le_prev = 0x3}, wk_type = 1, wk_state = 0} (kgdb) frame 12 #12 0xc08ad598 in vop_stdfsync (ap=0xc524fcd4) at ../../../kern/vfs_default.c:466 466 vfs_bio_awrite(bp); (kgdb) list 461 ("bp %p wrong b_bufobj %p should be %p", 462 bp, bp->b_bufobj, &vp->v_bufobj)); 463 if ((bp->b_flags & B_DELWRI) == 0) 464 panic("fsync: not dirty"); 465 if ((vp->v_object != NULL) && (bp->b_flags & B_CLUSTEROK)) { 466 vfs_bio_awrite(bp); 467 } else { 468 bremfree(bp); 469 bawrite(bp); 470 } (kgdb) print *bp->b_dep->lh_first $24 = {wk_mp = 0x8, wk_list = {le_next = 0x30, le_prev = 0x3}, wk_type = 1, wk_state = 0} From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 00:30:15 2011 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 ADE07106566B for ; Thu, 17 Feb 2011 00:30:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 614F58FC1C for ; Thu, 17 Feb 2011 00:30:15 +0000 (UTC) Received: by qyk8 with SMTP id 8so3715932qyk.13 for ; Wed, 16 Feb 2011 16:30:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tS278v9ZCSdB2vXR95kceH3A3Bki8jYqTGWweieV8vM=; b=ncZgyh2jFlHr/SxNJuFP4xjt19bV3RbkkIB8LJckAY0ardYS36SwjkKcjq0QRrhb64 oyl9eEaDrsFpJtXNtoo4km6QDP9buTi9dISQRdbokXd6PD9r6ImtCZwFBQ3t2DJHQ/wy +h2GZY8euwRojW1IZFtV2jP/Nb2qxuaN86plE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=w2Cb/Nn4YJFZgVqaQ10zuhK4ChdVRZtOuUbD2WOHRakZY+w4hQ4xN7i23TtsmGJRek jy/21a1JUsOFP3i5+0JNzkZXfIx4pXnWuIl+Yj4kEuwHpHOG1Vr/k037ebSqsbs4O7E9 q+oFOfcWnKabCoKQH0BBc9AXrJdaMu7UfViSg= MIME-Version: 1.0 Received: by 10.229.247.212 with SMTP id md20mr1465893qcb.272.1297902614576; Wed, 16 Feb 2011 16:30:14 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.220.194.69 with HTTP; Wed, 16 Feb 2011 16:30:14 -0800 (PST) In-Reply-To: References: Date: Wed, 16 Feb 2011 19:30:14 -0500 X-Google-Sender-Auth: PkeI6JW4itBse_U-M1yvBQVGd_8 Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: [ieee80211_hwmp][panic] hwmp_recv_prep(...) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 00:30:15 -0000 On 16 February 2011 15:51, Monthadar Al Jaberi wrote: > I think anytime the destination node sends a PREP to the originator > node that is not a peering node (not in direct contact with) we would > get this panic. Ok. Would you mind doing a quick audit to see what other KASSERT()s are lurking about when invalid/unexpected things happen? I'd rather they log a debug message and be handled gracefully. :-) Adrian From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 04:15:47 2011 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 0557B106566B; Thu, 17 Feb 2011 04:15:47 +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 CF44C8FC13; Thu, 17 Feb 2011 04:15:46 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1H4Fk4u081062; Thu, 17 Feb 2011 04:15:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1H4FkGQ081058; Thu, 17 Feb 2011 04:15:46 GMT (envelope-from linimon) Date: Thu, 17 Feb 2011 04:15:46 GMT Message-Id: <201102170415.p1H4FkGQ081058@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154826: [iwn] iwn driver fails to power on adapter after resume X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 04:15:47 -0000 Old Synopsis: iwn driver fails to power on adapter after resume New Synopsis: [iwn] iwn driver fails to power on adapter after resume Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Feb 17 04:15:31 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154826 From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 07:05:11 2011 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 B4E691065674; Thu, 17 Feb 2011 07:05:11 +0000 (UTC) (envelope-from bschmidt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8AC298FC08; Thu, 17 Feb 2011 07:05:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1H75Br5070921; Thu, 17 Feb 2011 07:05:11 GMT (envelope-from bschmidt@freefall.freebsd.org) Received: (from bschmidt@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1H75Bm9070917; Thu, 17 Feb 2011 07:05:11 GMT (envelope-from bschmidt) Date: Thu, 17 Feb 2011 07:05:11 GMT Message-Id: <201102170705.p1H75Bm9070917@freefall.freebsd.org> To: bschmidt@FreeBSD.org, freebsd-net@FreeBSD.org, bschmidt@FreeBSD.org From: bschmidt@FreeBSD.org Cc: Subject: Re: kern/154826: [iwn] iwn driver fails to power on adapter after resume X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 07:05:11 -0000 Synopsis: [iwn] iwn driver fails to power on adapter after resume Responsible-Changed-From-To: freebsd-net->bschmidt Responsible-Changed-By: bschmidt Responsible-Changed-When: Thu Feb 17 07:04:59 UTC 2011 Responsible-Changed-Why: over to me http://www.freebsd.org/cgi/query-pr.cgi?pr=154826 From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 07:13:19 2011 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 407231065673 for ; Thu, 17 Feb 2011 07:13:19 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id E8E7B8FC1B for ; Thu, 17 Feb 2011 07:13:18 +0000 (UTC) Received: by iyb26 with SMTP id 26so2114778iyb.13 for ; Wed, 16 Feb 2011 23:13:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cpDZ1k3SnR7hZMCL51wYg9UQnEZk6dsj5OuZeYtmiPo=; b=vqVH1Kxke6M4DuOVbZ1rJC2r8PcVeECKjGsr3arC/HlKwAOnQvzXbCJjignsqff1jF c99gK7j+e+05oTk0bE+DEl2vwtUtNAW0F4T2Ue47JM4Ao1an7vUMbvFnwkktlLwJv9JY owQWQYLlDZ4/BcR9q6NMh0sfqbIt4Gcfp+jZc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZCuc2CGOXXXdB2aZYdREWEndJtU0FSkPy4YoM8BYNfUOG2N8HSZC4FX6mO5IQ4Wzqp cNYntwoAnAkxzAi40UuHGAx8nqaYjwi1XLAV/J3byGX5MeX2uzKW4HElzSwBhod4d+oo XO97PgLICi19yG/lw8TK5roCxyBb4DVmL/xng= MIME-Version: 1.0 Received: by 10.42.167.129 with SMTP id s1mr2283458icy.231.1297926798234; Wed, 16 Feb 2011 23:13:18 -0800 (PST) Received: by 10.42.164.201 with HTTP; Wed, 16 Feb 2011 23:13:18 -0800 (PST) In-Reply-To: References: <12838373-FE96-443E-8979-AF5408705BF0@freebsd.org> Date: Thu, 17 Feb 2011 02:13:18 -0500 Message-ID: From: Arnaud Lacombe To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Karim Fodil-Lemelin , freebsd-net@freebsd.org Subject: Re: igb driver RX (was TX) hangs when out of mbuf clusters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 07:13:19 -0000 Hi, On Wed, Feb 16, 2011 at 2:30 PM, Jack Vogel wrote: > I've been in email conversation with Beezar, and=A0 he's clarified some > things, I think > I would like to try his approach to the issue, it will mean one more > iteration of changes > to test, would you be willing to do so? Yes, sure. - Arnaud From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 07:47:07 2011 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 4010C1065670 for ; Thu, 17 Feb 2011 07:47:07 +0000 (UTC) (envelope-from canevet@embl.fr) Received: from emblmta1.embl.fr (emblmta1.embl.fr [193.49.43.176]) by mx1.freebsd.org (Postfix) with ESMTP id D17B78FC12 for ; Thu, 17 Feb 2011 07:47:06 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.60,485,1291590000"; d="asc'?scan'208";a="1116565" Received: from unknown (HELO [172.26.15.11]) ([172.26.15.11]) by emblmta1.embl.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 17 Feb 2011 08:47:05 +0100 From: =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= To: freebsd-net@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-bdrFLLCCExURpfFYyj6S" Date: Thu, 17 Feb 2011 08:47:10 +0100 Message-ID: <1297928830.3097.51.camel@pc286.embl.fr> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Cc: kl@vsen.dk Subject: Re: [SOLVED ]Re: packet loss with carp on 6.2 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 07:47:07 -0000 --=-bdrFLLCCExURpfFYyj6S Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi,=20 I have exactly the same problem explained below (except with FreeBSD 8.2RC3). I lost a lot of packets on the carp interface. I tested with a point-to-point attachment and there is no problem... Now that I know that the problem must comes from the switch, how can I solve it ? Is there a workaround on the FreeBSD side ? May my switch be misconfigured or bugged (I have tested with HP Procurve switches 1800 and 2910al) ? I'd greatly appreciate your help to solve this issue. Thanks a lot, Micka=C3=ABl > Hi, >=20 > Just to close this thread - I've confirmed that it was indeed a switch > problem. >=20 > The "funny" thing, is howcome only CARP triggered it. > >=20 > On Thu, October 18, 2007 9:33, Klavs Klavsen said: > > Hi guys, > > > > I have had a FreeBSD 6.2 (-p1 - yes I know :) firewall running for a > > while, with pf fw rules. It has worked fine, and was a replacement > > for a > > > fbsd 4.x ipfw firewall. > > > > > Now I just replaced the 6.2 pf firewall, with a 6.2 (-p7) and carp > > interfaces enabled. It's using the same cables and the same type of > > network cards (bge and em). The new one, is a HP dl385 (amd) where > the old > > one, was a HP dl380 (Intel). > > > > On the new one, fping (and ping -f) pinging through the firewall, > gives me > > a packet loss. fping in nagios, reports up to 55% packet loss :( - a > ping > > > -f gives me 1-3%, but bad enough :( > > > > pinging from the firewall itself, to one of the hosts, that packets > are > > lost to (when pinging from other networks) does not give any packet > loss. > > > > The old 6.2, had polling enabled - and I've tried to disable polling > on > > the new, but to no effect. > > > > Any ideas what else to try? > > > > -- > > Regards, > > Klavs Klavsen, GSEC - kl at vsen.dk - http://www.vsen.dk > > > PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62 > > > > "Those who do not understand Unix are condemned to reinvent it, > poorly." > > --Henry Spencer > > > > _______________________________________________ > > freebsd-net at freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe at > freebsd.org" > > --=20 Regards, Klavs Klavsen, GSEC - kl at vsen.dk - http://www.vsen.dk PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62 "Those who do not understand Unix are condemned to reinvent it, poorly." --Henry Spencer --=-bdrFLLCCExURpfFYyj6S Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk1c0n4ACgkQZjBmN5Hi/YYH3QCeOIZ4nWHjFBJ/dsNQsDZ6uP68 NiwAnAt2ojH6wxnYLt0ln2SRlczPAnkI =cIre -----END PGP SIGNATURE----- --=-bdrFLLCCExURpfFYyj6S-- From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 08:35:15 2011 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 8C04D106566B for ; Thu, 17 Feb 2011 08:35:15 +0000 (UTC) (envelope-from canevet@embl.fr) Received: from emblmta1.embl.fr (emblmta1.embl.fr [193.49.43.176]) by mx1.freebsd.org (Postfix) with ESMTP id 219018FC08 for ; Thu, 17 Feb 2011 08:35:14 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.60,485,1291590000"; d="asc'?scan'208";a="1117391" Received: from unknown (HELO [172.26.15.11]) ([172.26.15.11]) by emblmta1.embl.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 17 Feb 2011 09:35:13 +0100 From: =?ISO-8859-1?Q?Micka=EBl_Can=E9vet?= To: freebsd-net@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-dfvQYbeFaNMUEd9fLP3U" Date: Thu, 17 Feb 2011 09:35:19 +0100 Message-ID: <1297931719.3097.56.camel@pc286.embl.fr> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Subject: unicast carp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 08:35:15 -0000 --=-dfvQYbeFaNMUEd9fLP3U Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Is there a way to configure carp to use unicast instead of multicast. In OpenBSD there seams to be a carppeer option that disable multicast, but I can't find the equivalent in FreeBSD. Thanks. Micka=C3=ABl --=-dfvQYbeFaNMUEd9fLP3U Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk1c3ccACgkQZjBmN5Hi/Ybq4QCgkDrruF3hAMd6B+499x/ZAU0B x+UAn0iJgUtK91sQecQmshsjo5aR8hmM =Ng2r -----END PGP SIGNATURE----- --=-dfvQYbeFaNMUEd9fLP3U-- From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 10:24:03 2011 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 69A1C106564A for ; Thu, 17 Feb 2011 10:24:03 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221]) by mx1.freebsd.org (Postfix) with ESMTP id 7FA598FC08 for ; Thu, 17 Feb 2011 10:24:01 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id p1HANwQK065301; Thu, 17 Feb 2011 16:23:58 +0600 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <4D5CF739.10303@rdtc.ru> Date: Thu, 17 Feb 2011 16:23:53 +0600 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7 MIME-Version: 1.0 To: Ed Maste References: <1519248747.20101028232111@yandex.ru> <1452146D-A590-4676-A662-14D0EEE82152@mac.com> <606859717.20101029093926@yandex.ru> <4CCC0243.8060507@prt.org> <20101030174152.GB41042@sandvine.com> In-Reply-To: <20101030174152.GB41042@sandvine.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Paul Thornton Subject: Re: Polling slows down bandwidth X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 10:24:03 -0000 On 31.10.2010 00:41, Ed Maste wrote: >> I've been doing testing with FreeBSD 8 and em interfaces recently, and >> my experience agrees with Chuck's statement - that polling makes things >> worse when you use new (anything in the last 2 or 3 years) hardware with >> good quality gigabit ethernet interfaces. > > There are some deficiencies in the current polling algorithm that will > cause it to perform less than optimally (it will temporarily stop > processing packets even though it is consuming less CPU than requested). > I have some changes that I plan to bring into the tree to improve this > situation. For recent high quality hardware though I expect you'll get > roughly equivalent performance from polling and standard opteration. Also note that current em(4) and igb(4) drivers limit maximum number of interrupts per second one adapter is allowed to generate to 8000. This number is inadequate to modern hardware like Core i3-based systems and leads to significant packet forwarding delays (houndreds of extra miliseconds). igb(4) in current has loader tunnable to change this limis but not em(4). I've made a patch to change this limit at run time (per-device) and raise it upto 32000. My em NICs generate upto 24000 interrupts per second and CPU is still pretty idle. For example, here is the patch for 8.2-PRERELEASE's em(4). It adds "hw.em.max_interrupt_rate" loader tunnable just like in igb(4) plus per-device r/w sysctls named "dev.em.X.max_interrupt_rate" (loader tunnable sets default for sysctls). There is similar patch for igb(4) to make this run-time sysctl. Manual ifconfig down/up is required after change of boot-time value to take effect. --- sys/dev/e1000/if_em.h.orig 2010-12-30 11:18:14.000000000 +0600 +++ sys/dev/e1000/if_em.h 2010-12-30 11:27:17.000000000 +0600 @@ -436,6 +436,12 @@ unsigned long link_irq; struct e1000_hw_stats stats; + + /* Bring link down when interface goes down */ + int down_disables_link; + + /* Maximum interrupt rate */ + int max_interrupt_rate; }; /******************************************************************************** --- sys/dev/e1000/if_em.c.orig 2010-12-30 11:18:14.000000000 +0600 +++ sys/dev/e1000/if_em.c 2010-12-30 11:27:17.000000000 +0600 @@ -365,6 +365,10 @@ static int em_fc_setting = e1000_fc_full; TUNABLE_INT("hw.em.fc_setting", &em_fc_setting); +#define MAX_INTS_PER_SEC 8000 +static unsigned em_max_interrupt_rate = MAX_INTS_PER_SEC; +TUNABLE_INT("hw.em.max_interrupt_rate", &em_max_interrupt_rate); + /* Global used in WOL setup with multiport cards */ static int global_quad_port_a = 0; @@ -452,6 +456,20 @@ OID_AUTO, "debug", CTLTYPE_INT|CTLFLAG_RW, adapter, 0, em_sysctl_debug_info, "I", "Debug Information"); + adapter->down_disables_link = 0; + SYSCTL_ADD_INT(device_get_sysctl_ctx(dev), + SYSCTL_CHILDREN(device_get_sysctl_tree(dev)), + OID_AUTO, "down_disables_link", CTLTYPE_INT|CTLFLAG_RW, + &adapter->down_disables_link, adapter->down_disables_link, + "Bring link down when interface goes down"); + + adapter->max_interrupt_rate = em_max_interrupt_rate; + SYSCTL_ADD_UINT(device_get_sysctl_ctx(dev), + SYSCTL_CHILDREN(device_get_sysctl_tree(dev)), + OID_AUTO, "max_interrupt_rate", CTLTYPE_UINT|CTLFLAG_RW, + &adapter->max_interrupt_rate, adapter->max_interrupt_rate, + "Maximum interrupt rate"); + callout_init_mtx(&adapter->timer, &adapter->core_mtx, 0); /* Determine hardware and mac info */ @@ -1266,6 +1284,8 @@ } /* Initialize the hardware */ + if (!adapter->hw.phy.reset_disable) + e1000_phy_hw_reset(&adapter->hw); em_reset(adapter); em_update_link_status(adapter); @@ -2319,6 +2339,19 @@ e1000_led_off(&adapter->hw); e1000_cleanup_led(&adapter->hw); + + if(adapter->down_disables_link) { + /* Bring physical link down by powering the phy down */ +/* e1000_power_down_phy(&adapter->hw); */ + e1000_power_down_phy_copper(&adapter->hw); + + /* Update system interface state */ + adapter->hw.mac.get_link_status = 1; + em_update_link_status(adapter); + + /* Reset the phy next time init gets called */ + adapter->hw.phy.reset_disable = FALSE; + } } @@ -4046,8 +4079,6 @@ * Enable receive unit. * **********************************************************************/ -#define MAX_INTS_PER_SEC 8000 -#define DEFAULT_ITR 1000000000/(MAX_INTS_PER_SEC * 256) static void em_initialize_receive_unit(struct adapter *adapter) @@ -4071,18 +4102,24 @@ adapter->rx_abs_int_delay.value); /* * Set the interrupt throttling rate. Value is calculated - * as DEFAULT_ITR = 1/(MAX_INTS_PER_SEC * 256ns) + * as 1/(max_interrupt_rate * 256ns) */ - E1000_WRITE_REG(hw, E1000_ITR, DEFAULT_ITR); + if (adapter->max_interrupt_rate > 0) { + E1000_WRITE_REG(hw, E1000_ITR, + 1000000000/256/adapter->max_interrupt_rate); + } /* ** When using MSIX interrupts we need to throttle ** using the EITR register (82574 only) */ if (hw->mac.type == e1000_82574) - for (int i = 0; i < 4; i++) + for (int i = 0; i < 4; i++) { + if (adapter->max_interrupt_rate > 0) { E1000_WRITE_REG(hw, E1000_EITR_82574(i), - DEFAULT_ITR); + 1000000000/256/adapter->max_interrupt_rate); + } + } /* Disable accelerated ackknowledge */ if (adapter->hw.mac.type == e1000_82574) From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 10:42:51 2011 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 9E51F1065674; Thu, 17 Feb 2011 10:42:51 +0000 (UTC) (envelope-from brucec@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 761CA8FC15; Thu, 17 Feb 2011 10:42:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1HAgpMl030169; Thu, 17 Feb 2011 10:42:51 GMT (envelope-from brucec@freefall.freebsd.org) Received: (from brucec@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1HAgp2T030165; Thu, 17 Feb 2011 10:42:51 GMT (envelope-from brucec) Date: Thu, 17 Feb 2011 10:42:51 GMT Message-Id: <201102171042.p1HAgp2T030165@freefall.freebsd.org> To: brucec@FreeBSD.org, freebsd-standards@FreeBSD.org, freebsd-net@FreeBSD.org From: brucec@FreeBSD.org Cc: Subject: Re: kern/154185: race condition in mb_dupcl X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 10:42:51 -0000 Synopsis: race condition in mb_dupcl Responsible-Changed-From-To: freebsd-standards->freebsd-net Responsible-Changed-By: brucec Responsible-Changed-When: Thu Feb 17 10:42:02 UTC 2011 Responsible-Changed-Why: Not a standards issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=154185 From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 10:50:35 2011 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 A666B106564A; Thu, 17 Feb 2011 10:50:35 +0000 (UTC) (envelope-from brucec@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7E1598FC13; Thu, 17 Feb 2011 10:50:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1HAoZQx035364; Thu, 17 Feb 2011 10:50:35 GMT (envelope-from brucec@freefall.freebsd.org) Received: (from brucec@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1HAoZaB035355; Thu, 17 Feb 2011 10:50:35 GMT (envelope-from brucec) Date: Thu, 17 Feb 2011 10:50:35 GMT Message-Id: <201102171050.p1HAoZaB035355@freefall.freebsd.org> To: brucec@FreeBSD.org, freebsd-standards@FreeBSD.org, freebsd-net@FreeBSD.org From: brucec@FreeBSD.org Cc: Subject: Re: kern/144231: bind/connect/sendto too strict about sockaddr length X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 10:50:35 -0000 Synopsis: bind/connect/sendto too strict about sockaddr length Responsible-Changed-From-To: freebsd-standards->freebsd-net Responsible-Changed-By: brucec Responsible-Changed-When: Thu Feb 17 10:48:57 UTC 2011 Responsible-Changed-Why: Not a standards issue: POSIX says EINVAL is returned if address_len is not a valid length for the address family, so FreeBSD's implementation would appear to be correct. http://www.freebsd.org/cgi/query-pr.cgi?pr=144231 From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 17:00:10 2011 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 D1FC61065674; Thu, 17 Feb 2011 17:00:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6208FC1C; Thu, 17 Feb 2011 17:00:09 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 1E61D46B06; Thu, 17 Feb 2011 12:00:09 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 88EE88A02A; Thu, 17 Feb 2011 12:00:07 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 17 Feb 2011 11:58:24 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <20100909131017.GO4404@twoquid.cs.ru.nl> <20100909140529.GB76889@icarus.home.lan> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201102171158.24636.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 17 Feb 2011 12:00:07 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Olaf Seibert , Steven Hartland , Jeremy Chadwick , net@freebsd.org Subject: Re: mountd has resolving problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 17:00:10 -0000 On Thursday, February 17, 2011 7:18:28 am Steven Hartland wrote: > This has become a issue for us in 8.x as well. > > I'm pretty sure in pre 8.x these nfs mounts would simply background but > recently machines are now failing to boot. It seems that failure to > lookup nfs mount point hosts now causes this fatal error :( > > We've just tried Jeremy's netwait script and it works perfectly so either > this or something similar needs to get pushed into base. > > For reference the reason we need a delay here is our core Cisco router > takes a while to bring the port up properly on boot. > > Thanks for sharing the script Jeremy :) I use a similar hack that waits up to 30 seconds for the default gateway to be pingable. I think it is at least partly related to the new ARP code that now drops packets in IP output if the link is down. This can be very problematic during boot since some interfaces take a few seconds to negotiate link but the end result of the new check in IP output is that the attempt to send the packet fails with an error causing gethostbyname() and getaddrinfo() to fail completely without doing any retries. In 7 the packet would either sit in the descriptor ring until link was up, or it would be dropped, but it would silently fail, so the resolver in libc would just retry in 30 seconds or so at which time it would work fine. Waiting for the default route to be pingable actually fixed a few other problems for us on 7 though as well (often ntpdate would not work on boot and now it works reliably, etc.) so we went with that route. > Regards > Steve > > ----- Original Message ----- > From: "Jeremy Chadwick" > To: "Olaf Seibert" > Cc: > Sent: Thursday, September 09, 2010 2:05 PM > Subject: Re: mountd has resolving problems > > > > On Thu, Sep 09, 2010 at 03:10:17PM +0200, Olaf Seibert wrote: > >> I just upgraded a box from 8.0 to 8.1, and already when rebooting with > >> the new kernel (i.e. before installing new userland), I got the > >> following problem. > >> > >> Of course many of the messages scrolled off screen, but some were > >> preserved in the syslog. > >> > >> Sep 9 14:26:51 fourquid mountd[839]: can't get address info for host XYZ > >> Sep 9 14:26:51 fourquid mountd[839]: bad host XYZ in netgroup vbgroup, skipping > >> > >> Mountd was run and wanted to determine which hosts to export to. > >> However, it could not resolve any of them. So, that suggests some > >> network issue. > >> > >> However, I use a static IP address (no DHCP) and static info in > >> /etc/resolv.conf, using one of the university's name servers. So > >> resolving should always be available. > >> > >> Running /etc/rc.d/mountd restart so far always solved the export > >> problem. > >> > >> I have also seen (presumably similar) issues with mounting NFS file > >> systems, but that was deemed so fatal that the boot was aborted. A mount > >> ``by hand'' of the affected file system also worked. > >> > >> Any ideas? Maybe with the new kernel the network interface is a bit > >> slower in coming up, and not fully working by the time /etc/rc.d/mountd > >> runs? In fact, I now notice this sequence of messages in > >> /var/log/messages: > >> > >> Sep 9 14:26:51 fourquid mountd[839]: bad host XYZ in netgroup vbgroup, skipping > >> Sep 9 14:26:51 fourquid mountd[839]: bad exports list line /xxxxxx > >> Sep 9 14:26:54 fourquid kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > >> Sep 9 14:26:54 fourquid init: /bin/sh on /etc/rc terminated abnormally, going to single user mode > >> Sep 9 14:26:55 fourquid kernel: nfe0: link state changed to UP > >> > >> so here the network interface takes a full 4 more seconds to come up, > >> after it was already needed. > >> > >> I can try to put a 10 sec delay somewhere, but there should be a better > >> solution... > > > > The problem is that the network isn't "truly" up and available by the > > time mountd runs, and therefore DNS resolution doesn't work. Please use > > my netwait script to solve this problem: > > > > http://jdc.parodius.com/freebsd/netwait > > > > Place it in /usr/local/etc/rc.d, make sure it's chmod'd to 755, > > then enable use of it by using /etc/rc.conf variables like so: > > > > netwait_enable="yes" > > netwait_ip="4.2.2.1 4.2.2.2" > > netwait_if="nfe0" > > > > For what the variables do, please see the script comments. > > > > -- > > | Jeremy Chadwick jdc@parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. > > In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 17:14:01 2011 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 2CD391065670; Thu, 17 Feb 2011 17:14:01 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8E88A8FC27; Thu, 17 Feb 2011 17:14:00 +0000 (UTC) Received: by wwf26 with SMTP id 26so2732080wwf.31 for ; Thu, 17 Feb 2011 09:13:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xH9GWua/lK5krcpPCrrB6Yzlh2602Rk3UZ4afSZnScQ=; b=Nav/8ynMeLSE9VoblESAK+VipGh8yMDXDzipqRMpF2GPWO4AaIJqhPyfTcfAE0BDm6 5yu9uIeWRomfF3FMPvnsfjzY330eDbo0iFwf+9MSVTZklfLsYoWn/HuZjYavzK3raHKu RKptVvkTSvKuv6rjEFxzLLKs0OUex3M3GfVNA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WFSJAgY1W+4kRVPQPNFWDxUUAgPkzyNOEuqOAm4Jam9OcuhVbhIHemslkRm+iv2e/M tZ5XuwgJCRGISWKKNiPzlwsNw92Wtn7avQdyJZyrXvZCxS6II4ANZs2Vuj97EAspdxTP NJrdhNQ9yEhzj+lpvGA9zCcBBRfn+BtWgJvQE= MIME-Version: 1.0 Received: by 10.227.128.199 with SMTP id l7mr1915747wbs.45.1297962839208; Thu, 17 Feb 2011 09:13:59 -0800 (PST) Received: by 10.227.69.7 with HTTP; Thu, 17 Feb 2011 09:13:58 -0800 (PST) In-Reply-To: References: Date: Thu, 17 Feb 2011 18:13:58 +0100 Message-ID: From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: [ieee80211_hwmp][panic] hwmp_recv_prep(...) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 17:14:01 -0000 On Thu, Feb 17, 2011 at 1:30 AM, Adrian Chadd wrote: > On 16 February 2011 15:51, Monthadar Al Jaberi wrote: >> >> I think anytime the destination node sends a PREP to the originator >> node that is not a peering node (not in direct contact with) we would >> get this panic. > > Ok. Would you mind doing a quick audit to see what other KASSERT()s are > lurking about when invalid/unexpected things happen? > I'd rather they log a debug message and be handled gracefully. :-) I wonder if this should be logged? I mean it is something that is by design, when you propagate a packet in air, the original sender is bound to hear the propagation... right? > > > Adrian -- //Monthadar Al Jaberi From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 18:09:30 2011 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 877DB106566B; Thu, 17 Feb 2011 18:09:30 +0000 (UTC) (envelope-from prvs=10296b544f=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id E94858FC18; Thu, 17 Feb 2011 18:09:29 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Thu, 17 Feb 2011 17:58:41 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 17 Feb 2011 17:58:41 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50012243924.msg; Thu, 17 Feb 2011 17:58:40 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=10296b544f=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <4215B319C85B46A0AC539A67BC9EAF3C@multiplay.co.uk> From: "Steven Hartland" To: "John Baldwin" , References: <20100909131017.GO4404@twoquid.cs.ru.nl> <20100909140529.GB76889@icarus.home.lan> <201102171158.24636.jhb@freebsd.org> Date: Thu, 17 Feb 2011 17:59:05 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: Olaf Seibert , Jeremy Chadwick , net@freebsd.org Subject: Re: mountd has resolving problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 18:09:30 -0000 ----- Original Message ----- From: "John Baldwin" > Waiting for the default route to be pingable actually fixed a few other > problems for us on 7 though as well (often ntpdate would not work on boot and > now it works reliably, etc.) so we went with that route. Also fixed quite a few issues for us as well with services not reporting properly. Definitely something that should be considered as part of core IMO. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 18:30:23 2011 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 3455E106566C for ; Thu, 17 Feb 2011 18:30:23 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id B2E8F8FC17 for ; Thu, 17 Feb 2011 18:30:22 +0000 (UTC) Received: by ewy24 with SMTP id 24so1236571ewy.13 for ; Thu, 17 Feb 2011 10:30:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=huwveJvgrLXVmAuw2PSOA/NjVY6FxuPoP8FYOJJGW2E=; b=LSa2tnMvRf0V/rvE0MH/y0f8MJgspx/IyeKmj0qmGXcXooYHpo8nlPmmjlzutsGUjp R+4t9ecYs/yzv00jviovH5yHvJ0Ni6SxNWgVCdMqdch1w/WIVZMcMJ/WD+81vyNZaOEC JyGJ2Ew7BZaGO8HTW4yjrg6nEV8CLPBwaxSIo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=TiybNJRqoWp3FxdLfXoKnqZLGRJkBLEC75s2YUaw2oPD9can5ZwmLuna3Mmq3MR+Q/ GAF7izTozjkdNLH5/Bdbgw9HLX8Rwi1BqnSJqhPVpsWU+RLZ4C1KeGPP681Tw6GdDdq8 tXK5KToRAFmK4XFn1U8UPSMzqUsbGYUDTfls0= Received: by 10.213.17.200 with SMTP id t8mr12248eba.1.1297967420620; Thu, 17 Feb 2011 10:30:20 -0800 (PST) Received: from [10.0.0.49] (93-152-151-19.ddns.onlinedirect.bg [93.152.151.19]) by mx.google.com with ESMTPS id u1sm1097461eeh.16.2011.02.17.10.30.18 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Feb 2011 10:30:19 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Nikolay Denev In-Reply-To: <4D5C04DD.3020704@freebsd.org> Date: Thu, 17 Feb 2011 20:30:16 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4D5AAA28.50408@freebsd.org> <5516808338355511684@unknownmsgid> <7DACE499-8AE3-427B-99EB-39618699625F@gmail.com> <4D5C04DD.3020704@freebsd.org> To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.1082) Subject: Re: ng_ether and vlan interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 18:30:23 -0000 On 16 Feb, 2011, at 19:09 , Julian Elischer wrote: > On 2/16/11 5:20 AM, Nikolay Denev wrote: >> On 15 Feb, 2011, at 21:08 , Nikolay Denev wrote: >>=20 >>> On 15.02.2011, at 18:53, Arnaud Lacombe wrote: >>>=20 >>>> Hi, >>>>=20 >>>> On Tue, Feb 15, 2011 at 11:30 AM, Julian = Elischer wrote: >>>>> changing it to '_' might be accceptable, '.' is much like '/' in = th >>>>> filesystem. >>>>> it is a separator. You can't have it in the name. >>>>> a patch that converted . to _ would be a nice idea. >>>>> please ensure that the man page is updated as well. >>>>>=20 >>>> Doesn't FreeBSD care about kernel/userland backward interface >>>> compatibility at all ? ie. will all my scripts assuming '.' as a >>>> separator need to also check the FreeBSD version to use whatever = path >>>> separator ? How would you do that with bare ngctl script, which = cannot >>>> be really that evolved ? How do you deal with node in the wild = already >>>> using '_' in their name ? >>>>=20 >>>> Thanks, >>>> - Arnaud >>> I'm actually thinking on doing the check and replacement of dots in >>> ng_ether, so it won't affect other netgraph consumers. >>>=20 >>> Regards, >>> Nikolay >> Does this look reasonable? : >>=20 >> [14:57]root@nas:/home/ndenev# ifconfig sge0.13 create >> [14:57]root@nas:/home/ndenev# ifconfig sge0.14 create >> [14:57]root@nas:/home/ndenev# ifconfig sge0.14 name sge0:14 >> [14:58]root@nas:/home/ndenev# kldload ng_ether >> [14:58]root@nas:/home/ndenev# ngctl l >> There are 5 total nodes: >> Name: sge0_13 Type: ether ID: 00000003 Num = hooks: 0 >> Name: sge0_14 Type: ether ID: 00000004 Num = hooks: 0 >> Name: ipfw0 Type: ether ID: 00000002 Num = hooks: 0 >> Name: ngctl1685 Type: socket ID: 00000005 Num = hooks: 0 >> Name: sge0 Type: ether ID: 00000001 Num = hooks: 0 >>=20 >> This is the patch to ng_ether which replaces both dots and colons = with underscore. >> I'm unsure about changing them both to underscore, and a colon in = interface name does >> not seem like something common. So I can rework it to replace only = dots. >>=20 >>=20 >> Patch URL : http://ndenev.ath.cx/patches/ng_ether_namemangling.patch >>=20 >> --- sys/netgraph/ng_ether.c.orig 2011-02-15 19:29:09.706568297 = +0200 >> +++ sys/netgraph/ng_ether.c 2011-02-16 15:11:03.138114973 +0200 >> @@ -285,6 +285,8 @@ >> { >> priv_p priv; >> node_p node; >> + int i; >> + char name[IFNAMSIZ]; >>=20 >> /* >> * Do not create / attach an ether node to this ifnet if >> @@ -319,10 +321,22 @@ >> IFP2NG(ifp) =3D node; >> priv->hwassist =3D ifp->if_hwassist; >>=20 >> - /* Try to give the node the same name as the interface */ >> - if (ng_name_node(node, ifp->if_xname) !=3D 0) { >> + /* >> + * Try to give the node the same name as the interface >> + * replacing netgraph reserved characters (dot and colon) >> + */ >> + for (i =3D 0; i< IFNAMSIZ; i++) { >> + if (ifp->if_xname[i] =3D=3D '.' || ifp->if_xname[i] =3D=3D= ':') { >> + name[i] =3D '_'; >> + } else { >> + name[i] =3D ifp->if_xname[i]; >> + } >> + if (ifp->if_xname[i] =3D=3D '\0') >> + break; >> + } >> + if (ng_name_node(node, name) !=3D 0) { >> log(LOG_WARNING, "%s: can't name node %s\n", >> - __func__, ifp->if_xname); >> + __func__, name); >> } >> } >>=20 > looks good to me >=20 >> --- ng_ether.4.orig 2011-02-16 15:16:11.775255282 +0200 >> +++ ng_ether.4 2011-02-16 15:18:53.114257799 +0200 >> @@ -54,7 +54,8 @@ >> module is loaded into the kernel, a node is automatically created >> for each Ethernet interface in the system. >> Each node will attempt to name itself with the same name >> -as the associated interface. >> +as the associated interface, substituting netgraph reserved >> +characters in the name with underscores. >> .Pp >> Three hooks are supported: >> .Va lower , upper , >>=20 >>=20 >>=20 >=20 Sumbitted as kern/154850= From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 19:46:32 2011 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 D1486106566B; Thu, 17 Feb 2011 19:46:32 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx10.syd.optusnet.com.au (fallbackmx10.syd.optusnet.com.au [211.29.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id 19E848FC14; Thu, 17 Feb 2011 19:46:31 +0000 (UTC) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by fallbackmx10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p1HHlKEl024342; Fri, 18 Feb 2011 04:47:20 +1100 Received: from c122-107-114-89.carlnfd1.nsw.optusnet.com.au (c122-107-114-89.carlnfd1.nsw.optusnet.com.au [122.107.114.89]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p1HHl4Qm001875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Feb 2011 04:47:05 +1100 Date: Fri, 18 Feb 2011 04:47:04 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: John Baldwin In-Reply-To: <201102171158.24636.jhb@freebsd.org> Message-ID: <20110218043432.S3233@besplex.bde.org> References: <20100909131017.GO4404@twoquid.cs.ru.nl> <20100909140529.GB76889@icarus.home.lan> <201102171158.24636.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Olaf Seibert , net@freebsd.org, freebsd-stable@freebsd.org, Jeremy Chadwick , Steven Hartland Subject: Re: mountd has resolving problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 19:46:32 -0000 On Thu, 17 Feb 2011, John Baldwin wrote: > On Thursday, February 17, 2011 7:18:28 am Steven Hartland wrote: >> This has become a issue for us in 8.x as well. >> >> I'm pretty sure in pre 8.x these nfs mounts would simply background but >> recently machines are now failing to boot. It seems that failure to >> lookup nfs mount point hosts now causes this fatal error :( >> >> We've just tried Jeremy's netwait script and it works perfectly so either >> this or something similar needs to get pushed into base. >> >> For reference the reason we need a delay here is our core Cisco router >> takes a while to bring the port up properly on boot. >> >> Thanks for sharing the script Jeremy :) > > I use a similar hack that waits up to 30 seconds for the default gateway to be > pingable. I think it is at least partly related to the new ARP code that now > drops packets in IP output if the link is down. I use hackish ping -t s and traceroutes in /etc/rc.d/netif. Don't know if it is the same problem. It affects mainly nfs and ntpdate/ntpd to local systems here. Even with all-static routes. > This can be very problematic > during boot since some interfaces take a few seconds to negotiate link but > the end result of the new check in IP output is that the attempt to send the > packet fails with an error causing gethostbyname() and getaddrinfo() to fail > completely without doing any retries. In 7 the packet would either sit in the Also after down/up to change something. If you try to use the network before it is back then you have to wait much longer before it is really back. This is a relatively minor problem since down/up is not needed routinely. > descriptor ring until link was up, or it would be dropped, but it would > silently fail, so the resolver in libc would just retry in 30 seconds or so at > which time it would work fine. > > Waiting for the default route to be pingable actually fixed a few other > problems for us on 7 though as well (often ntpdate would not work on boot and > now it works reliably, etc.) so we went with that route. I thought I first saw the problem a little earlier, and it affected bge more than fxp. Maybe the latter is correct and the problem is smaller with fxp just because it is ready sooner. Bruce From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 20:49:06 2011 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 BDAE71065673 for ; Thu, 17 Feb 2011 20:49:06 +0000 (UTC) (envelope-from dougb@dougbarton.us) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 4B2658FC14 for ; Thu, 17 Feb 2011 20:49:06 +0000 (UTC) Received: (qmail 29316 invoked by uid 399); 17 Feb 2011 20:20:59 -0000 Received: from router.ka9q.net (HELO ?192.168.2.9?) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 17 Feb 2011 20:20:59 -0000 X-Originating-IP: 75.60.237.91 X-Sender: dougb@dougbarton.us Message-ID: <4D5D832A.8060903@dougbarton.us> Date: Thu, 17 Feb 2011 12:20:58 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Steven Hartland References: <20100909131017.GO4404@twoquid.cs.ru.nl> <20100909140529.GB76889@icarus.home.lan> <201102171158.24636.jhb@freebsd.org> <4215B319C85B46A0AC539A67BC9EAF3C@multiplay.co.uk> In-Reply-To: <4215B319C85B46A0AC539A67BC9EAF3C@multiplay.co.uk> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Olaf Seibert , freebsd-stable@freebsd.org, Jeremy Chadwick , John Baldwin , net@freebsd.org Subject: Re: mountd has resolving problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 20:49:06 -0000 On 2/17/2011 9:59 AM, Steven Hartland wrote: > ----- Original Message ----- From: "John Baldwin" >> Waiting for the default route to be pingable actually fixed a few >> other problems for us on 7 though as well (often ntpdate would not >> work on boot and now it works reliably, etc.) so we went with that route. > > Also fixed quite a few issues for us as well with services not reporting > properly. Definitely something that should be considered as part of core I've already said that I plan to commit this once the releases are done. :) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-net@FreeBSD.ORG Thu Feb 17 21:04:40 2011 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 A064F1065674; Thu, 17 Feb 2011 21:04:40 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 767318FC16; Thu, 17 Feb 2011 21:04:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1HL4efZ007903; Thu, 17 Feb 2011 21:04:40 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1HL4eLp007899; Thu, 17 Feb 2011 21:04:40 GMT (envelope-from remko) Date: Thu, 17 Feb 2011 21:04:40 GMT Message-Id: <201102172104.p1HL4eLp007899@freefall.freebsd.org> To: theo.studer@gmail.com, remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/154851: [request]: Port brcm80211 driver from Linux to FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2011 21:04:40 -0000 Old Synopsis: Port brcm80211 driver from Linux to FreeBSD New Synopsis: [request]: Port brcm80211 driver from Linux to FreeBSD State-Changed-From-To: open->suspended State-Changed-By: remko State-Changed-When: Thu Feb 17 21:04:08 UTC 2011 State-Changed-Why: Suspend awaiting patches. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Thu Feb 17 21:04:08 UTC 2011 Responsible-Changed-Why: reassign to the networking team. http://www.freebsd.org/cgi/query-pr.cgi?pr=154851 From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 00:16:20 2011 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 83677106567A; Fri, 18 Feb 2011 00:16:20 +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 587738FC17; Fri, 18 Feb 2011 00:16:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1I0GKql009869; Fri, 18 Feb 2011 00:16:20 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1I0GKqg009865; Fri, 18 Feb 2011 00:16:20 GMT (envelope-from linimon) Date: Fri, 18 Feb 2011 00:16:20 GMT Message-Id: <201102180016.p1I0GKqg009865@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154850: [netgraph] [patch] ng_ether fails to name nodes when the associated interface contains dots or colons X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 00:16:20 -0000 Old Synopsis: ng_ether fails to name nodes when the associated interface contains dots or colons New Synopsis: [netgraph] [patch] ng_ether fails to name nodes when the associated interface contains dots or colons Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Feb 18 00:15:50 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154850 From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 03:12:39 2011 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 8347F106566B; Fri, 18 Feb 2011 03:12:39 +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 57EBE8FC14; Fri, 18 Feb 2011 03:12:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1I3Cdh9001072; Fri, 18 Feb 2011 03:12:39 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1I3Cda8001068; Fri, 18 Feb 2011 03:12:39 GMT (envelope-from linimon) Date: Fri, 18 Feb 2011 03:12:39 GMT Message-Id: <201102180312.p1I3Cda8001068@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154831: [arp] [patch] arp sysctl setting log_arp_permanent_modify has no effect X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 03:12:39 -0000 Old Synopsis: [patch] arp sysctl setting log_arp_permanent_modify has no effect New Synopsis: [arp] [patch] arp sysctl setting log_arp_permanent_modify has no effect Responsible-Changed-From-To: freebsd-amd64->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Feb 18 03:12:20 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154831 From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 05:11:44 2011 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 EEC891065672 for ; Fri, 18 Feb 2011 05:11:44 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C837B8FC0C for ; Fri, 18 Feb 2011 05:11:44 +0000 (UTC) Received: by pzk32 with SMTP id 32so532307pzk.13 for ; Thu, 17 Feb 2011 21:11:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=Qf7ceHw/uyIzXs9LoR6AFOKUxDfhV8OGvXxnMNyQC9I=; b=RTFR1jXrWiDcqrzfwzINE10Opqa6ZqzB4u6xbn+iOV1kp6cle7adVIW8zHIIuPDNVM PeLEATdQvbKAfge5zZSoTOByDj/1D1HNrsNzxhYc9Vlip4Aohs0KqbmHHl/NLANctuV8 Q0EhEs5uwYtmUYoClSNCIWdLMX4GyRQ/OZn1U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=h81gQbndl7EMRclsALFqW8f7goqSPjwiHgYXLGz6Qc1Rxa1eYcmp/sRMDnvwZ5A9tX xAFRZ/+ky3lwwJOARcz5DTTi0hDIc0qKz4LferZUm/NJmowgHGcRMY9a7F3a90WK8vmB NfDbQBE9mK1UXSAuFP2HFIfir2IjxsUuzcEOI= MIME-Version: 1.0 Received: by 10.142.216.1 with SMTP id o1mr214473wfg.190.1298004238275; Thu, 17 Feb 2011 20:43:58 -0800 (PST) Received: by 10.142.128.18 with HTTP; Thu, 17 Feb 2011 20:43:58 -0800 (PST) Date: Thu, 17 Feb 2011 23:43:58 -0500 Message-ID: From: grarpamp To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: swhetzel@gmail.com Subject: bwi vs. bwn X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 05:11:45 -0000 I have a BCM94312MCG, which driver should I choose and why? The man pages are nearly identical. It appears that bwn is newer/maintained? And more modular with siba? Can the newer upstream firmware at openwrt be used with bwn-firmware-kmod? http://downloads.openwrt.org/sources/broadcom-wl-4.150.10.5.3.tar.bz2 Where did the firmware blobs in the above file come from, here? http://bcm43xx.berlios.de/ http://wireless.kernel.org/en/users/Drivers/b43/ As a result of being written to this spec project? http://bcm-specs.sipsolutions.net/ http://bcm-v4.sipsolutions.net/ With what I gather so far, I don't think they do? Or from Broadcom, in a windows blob, which fwcutter is used with? That's the part I'm not sure of. Where do I find the parent blob drivers? broadcom.com doesn't seem to have any 802.11 wireless files, as if it's all OEM. And how might this come into play? http://www.broadcom.com/support/802.11/linux_sta.php Trying to put the pieces together. Thanks. From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 15:31:51 2011 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 DE2BB106564A for ; Fri, 18 Feb 2011 15:31:51 +0000 (UTC) (envelope-from elof2@sentor.se) Received: from deliverator.sentor.se (deliverator.sentor.se [195.178.169.27]) by mx1.freebsd.org (Postfix) with ESMTP id A185B8FC1D for ; Fri, 18 Feb 2011 15:31:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by deliverator.sentor.se (Postfix) with ESMTP id 75836A2CCBA for ; Fri, 18 Feb 2011 16:16:49 +0100 (CET) Date: Fri, 18 Feb 2011 16:16:49 +0100 (CET) From: elof2@sentor.se X-X-Sender: elof@deliverator.sentor.se To: freebsd-net Message-ID: <20110218145213.T51580@deliverator.sentor.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Request to developers of if_bridge.ko - ETHER_BPF_MTAP vs BPF_MTAP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 15:31:51 -0000 Back in FreeBSD 6.3 and 6.4 there was a bpf-bug in if_bridge.c. This bug was sometimes a nice feature though, since it "normalised" the traffic sent to bpf, making it easier to sniff, analyse and debug the mirrored traffic. My request is for the possibility to have "packet normalisation" turned on based on a sysctl flag. Scenario: I create a bridge0 interface using one or multiple parent NICs. Then I sniff traffic on this cloned NIC (tcpdump -nli bridge0 port 80). Benefit: Multiple NICs are bonded together and can easily be sniffed on ONE interface with ONE sniffer process. Drawback: The problem is that if the sniffer use a bpf filter like "port 80", and the mirrored traffic consist of a mix of untagged and vlan tagged (802.1q) packets, only the untagged packets will match. To see if there are any www-traffic in the mirrored vlans, one need to change the filter to "vlan and port 80", but then you loose the untagged lan. ...catch 22. The bug (feature) in sys/net/if_bridge.c prior to revision 186365 (http://svn.freebsd.org/viewvc/base?view=revision&revision=186365) was that if_bridge sent a copy of a packet to bpf using BPF_MTAP instead of using ETHER_BPF_MTAP. The result was that the sniffer got a copy of packets that had their vlan header (tag) stripped off. In the patched version, the full frame is mirrored to bpf. While this is correct, I'd like the possibility to override and see stripped packets instead. Having a function that simply strips off any vlan tags from tagged packets is wonderful when it comes to sniffing. Especially since switches from all brands behave differently when it comes to SPAN and vlan tags (a SYN could be mirrorred untagged while the corresponding SYN+ACK is mirrored with a vlan tag set). It is also quite common that net admins configure uplink ports with multiple vlans AND an untagged lan. When you SPAN this uplink you get both tagged and untagged traffic in a mix. By normalising the mirrored traffic sent to bpf, a network technician can more easily perform his network debugging. Also, there are less risk of human mistakes due to the lack of insight that he need to use the 'vlan' keyword in his tcpdump/tshark/ngrep/whatever to see the full scope of the traffic. Also state-keeping tools like snort and argus benefit from normalised traffic since they cann't build a correct state table if the SYN and SYN+ACK belong to two different vlans. My request is that if a sysctl variable (like net.link.bridge.bpf.strip_header) equals true, then if_bridge.ko will pass stripped (BPF_MTAP) packets to bpf. By default it should naturally pass the entire frame (ETHER_BPF_MTAP). I know that passing stripped packets to bpf could be seen as ugly and bad, but compared to some of the problems a mixed environment can cause, I think that the possibility to manually override the default would be very useful. (in fact I know it, since I relied on the bug during the FreeBSD 6.3-6.4 period) There are only four places in if_bridge.c that need to be updated to something like this: if (net.link.bridge.bpf.strip_header == 1) BPF_MTAP(bifp, m); else ETHER_BPF_MTAP(bifp, m); The question is if other people besides myself see the benefits? Could we have this feature added to FreeBSD base? What are your thoughts? /Elof From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 16:09:40 2011 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 D23D21065670 for ; Fri, 18 Feb 2011 16:09:40 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id 58F188FC12 for ; Fri, 18 Feb 2011 16:09:39 +0000 (UTC) Received: (qmail 81730 invoked by uid 80); 18 Feb 2011 15:42:58 -0000 Received: from dsdf-4db5ecc0.pool.mediaWays.net (dsdf-4db5ecc0.pool.mediaWays.net [77.181.236.192]) by avocado.salatschuessel.net (Horde Framework) with HTTP; Fri, 18 Feb 2011 16:42:57 +0100 Message-ID: <20110218164257.1789797hzcgoyao0@avocado.salatschuessel.net> Date: Fri, 18 Feb 2011 16:42:57 +0100 From: Oliver Lehmann To: net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) / FreeBSD-7.3 Cc: Subject: DLNA - IGMPProxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 16:09:40 -0000 Hi, I've got a shiny new Sony TV with DLNA Support :) My fileserver is located in a different subnet so it is not accessibly by the TV. The TV itself detects my netbook which is in the same subnet (and runs Win7) as a DLNA source. I've now tried to setup igmpproxy because I thought this might solve my problem accessing my DLNA server in another subnet. - Sony TV: 10.0.2.102 (fxp2) - FreeBSD System running mediatomb: 10.0.0.21 (fxp0) - Win7 System: 10.0.1.51 (fxp1) - I did kldload ip_mroute on my router to get MROUTING - I added "allow ip from any to any { via fxp0 or via fxp1 or via fxp2 }" as a top rule to my ipfw configuration for testing. - I installed igmpproxy, configuration: quickleave phyint fxp2 upstream ratelimit 0 threshold 1 altnet 10.0.2.0/24 phyint fxp0 downstream ratelimit 0 threshold 1 phyint fxp1 downstream ratelimit 0 threshold 1 phyint fxp3 disabled phyint tun0 disabled phyint lo0 disabled phyint ipfw0 disabled - I started igmpproxy My TV still does not find any DLNA sources. I did a tcpdump on my FreeBSD system and saw that some information was exchanged. IGMP-Proxy Output: Current routing table (Insert Route): ----------------------------------------------------- #0: Src: 0.0.0.0, Dst: 224.0.1.60, Age:2, St: I, OutVifs: 0x00000002 #1: Src: 10.0.2.102, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000003 #2: Src: 0.0.0.0, Dst: 224.0.0.252, Age:2, St: I, OutVifs: 0x00000002 ----------------------------------------------------- RECV V2 member report from 10.0.0.21 to 239.255.255.250 Should insert group 239.255.255.250 (from: 10.0.0.21) to route table. Vif Ix : 0 Updated route entry for 239.255.255.250 on VIF #0 Vif bits : 0x00000003 Setting TTL for Vif 0 to 1 Setting TTL for Vif 1 to 1 Adding MFC: 10.0.2.102 -> 239.255.255.250, InpVIf: 2 TCPDUMP from my FreeBSD system running mediatomb: 16:30:36.785232 IP gurke-fxp0.salatschuessel.net > ALL-SYSTEMS.MCAST.NET: igmp query v2 16:30:37.341940 IP nudel.salatschuessel.net.47362 > gurke-fxp0.salatschuessel.net.domain: 59241+ PTR? 1.0.0.224.in-addr.arpa. (40) 16:30:37.348578 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.47362: 59241 1/3/5 PTR[|domain] 16:30:37.348955 IP nudel.salatschuessel.net.19714 > gurke-fxp0.salatschuessel.net.domain: 59242+ PTR? 1.0.0.10.in-addr.arpa. (39) 16:30:37.351946 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.19714: 59242* 1/1/0 PTR[|domain] 16:30:38.352099 IP nudel.salatschuessel.net.43548 > gurke-fxp0.salatschuessel.net.domain: 59243+ PTR? 21.0.0.10.in-addr.arpa. (40) 16:30:38.357630 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.43548: 59243* 1/1/0 PTR[|domain] 16:30:40.761988 IP gurke-fxp0.salatschuessel.net > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 16:30:41.357794 IP nudel.salatschuessel.net.49398 > gurke-fxp0.salatschuessel.net.domain: 59244+ PTR? 2.0.0.224.in-addr.arpa. (40) 16:30:41.361834 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.49398: 59244 1/3/5 PTR[|domain] 16:30:44.403547 IP nudel.salatschuessel.net > 239.255.255.250: igmp v2 report 239.255.255.250 16:30:45.361817 IP nudel.salatschuessel.net.15540 > gurke-fxp0.salatschuessel.net.domain: 59245+ PTR? 250.255.255.239.in-addr.arpa. (46) 16:30:45.364535 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.15540: 59245 NXDomain 0/1/0 (103) 16:31:05.596118 ARP, Request who-has gurke-fxp0.salatschuessel.net tell nudel.salatschuessel.net, length 28 16:31:05.596255 ARP, Reply gurke-fxp0.salatschuessel.net is-at 00:50:8b:e3:3f:60 (oui Unknown), length 46 16:31:07.616378 ARP, Request who-has fiori.salatschuessel.net tell gurke-fxp0.salatschuessel.net, length 46 16:31:07.616394 ARP, Reply fiori.salatschuessel.net is-at 90:e6:ba:cc:ba:76 (oui Unknown), length 28 16:31:08.363958 IP nudel.salatschuessel.net.56335 > gurke-fxp0.salatschuessel.net.domain: 59246+ PTR? 22.0.0.10.in-addr.arpa. (40) 16:31:08.367086 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.56335: 59246* 1/1/0 PTR[|domain] 16:31:50.178559 IP gurke-fxp0.salatschuessel.net > ALL-ROUTERS.MCAST.NET: igmp leave ALL-ROUTERS.MCAST.NET 16:31:51.002428 IP gurke-fxp0.salatschuessel.net > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 16:31:51.006396 IP gurke-fxp0.salatschuessel.net > ALL-SYSTEMS.MCAST.NET: igmp query v2 16:31:54.964621 IP gurke-fxp0.salatschuessel.net > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 16:31:58.168975 IP nudel.salatschuessel.net > 239.255.255.250: igmp v2 report 239.255.255.250 16:32:22.165428 IP gurke-fxp0.salatschuessel.net > ALL-SYSTEMS.MCAST.NET: igmp query v2 16:32:26.163901 IP gurke-fxp0.salatschuessel.net > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 16:32:29.124139 IP nudel.salatschuessel.net > 239.255.255.250: igmp v2 report 239.255.255.250 16:32:53.369482 IP gurke-fxp0.salatschuessel.net > ALL-SYSTEMS.MCAST.NET: igmp query v2 16:33:00.761491 IP gurke-fxp0.salatschuessel.net > ALL-ROUTERS.MCAST.NET: igmp v2 report ALL-ROUTERS.MCAST.NET 16:33:02.289326 IP nudel.salatschuessel.net > 239.255.255.250: igmp v2 report 239.255.255.250 16:33:06.581714 IP fiori.salatschuessel.net.16505 > gurke-fxp0.salatschuessel.net.domain: 56461+ A? pop.gmx.net. (29) 16:33:06.584613 IP gurke-fxp0.salatschuessel.net.domain > fiori.salatschuessel.net.16505: 56461 2/2/2 A 212.227.17.185, (138) 16:33:40.700010 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 404 16:33:40.741915 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 413 16:33:40.781375 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 460 16:33:40.822868 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 468 16:33:40.866022 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 470 16:33:40.904720 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 458 16:33:41.021694 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 404 16:33:41.062396 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 413 16:33:41.104868 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 460 16:33:41.141397 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 468 16:33:41.181870 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 470 16:33:41.221326 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 458 16:33:41.365837 IP nudel.salatschuessel.net.35965 > gurke-fxp0.salatschuessel.net.domain: 59247+ PTR? 102.2.0.10.in-addr.arpa. (41) 16:33:41.370427 IP gurke-fxp0.salatschuessel.net.domain > nudel.salatschuessel.net.35965: 59247 NXDomain* 0/1/0 (112) 16:34:58.311731 IP gurke-fxp0.salatschuessel.net > ALL-SYSTEMS.MCAST.NET: igmp query v2 16:34:58.469980 IP nudel.salatschuessel.net > 239.255.255.250: igmp v2 report 239.255.255.250 What am I missing to get it to work? I also tried NATing the network where the TV is attached with divert/natd but that also did not help. Please keep me CCed Greetings, Oliver ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 17:32:18 2011 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 5F8881065693 for ; Fri, 18 Feb 2011 17:32:18 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id DE22B8FC1C for ; Fri, 18 Feb 2011 17:32:17 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id p1IH9XkS041798; Fri, 18 Feb 2011 10:09:33 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id p1IH9XjO041795; Fri, 18 Feb 2011 10:09:33 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 18 Feb 2011 10:09:32 -0700 (MST) From: Warren Block To: grarpamp In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Fri, 18 Feb 2011 10:09:33 -0700 (MST) Cc: freebsd-net@freebsd.org, swhetzel@gmail.com Subject: Re: bwi vs. bwn X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 17:32:18 -0000 On Thu, 17 Feb 2011, grarpamp wrote: > I have a BCM94312MCG, which driver should I choose and why? > The man pages are nearly identical. The FreeBSD bwn and bwi modules seem to be equivalent to the Linux b43 and b43legacy drivers. This page may or may not help: http://wireless.kernel.org/en/users/Drivers/b43 From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 18:13:33 2011 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 B4913106566B for ; Fri, 18 Feb 2011 18:13:33 +0000 (UTC) (envelope-from k@kevinkevin.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 858ED8FC0C for ; Fri, 18 Feb 2011 18:13:33 +0000 (UTC) Received: by iwn39 with SMTP id 39so3957119iwn.13 for ; Fri, 18 Feb 2011 10:13:32 -0800 (PST) Received: by 10.42.172.70 with SMTP id m6mr1257370icz.18.1298051395116; Fri, 18 Feb 2011 09:49:55 -0800 (PST) Received: from kkPC (not.enough.unixsluts.com [76.10.166.187]) by mx.google.com with ESMTPS id z4sm1949257ibg.19.2011.02.18.09.49.53 (version=SSLv3 cipher=OTHER); Fri, 18 Feb 2011 09:49:53 -0800 (PST) From: "kevin" To: Date: Fri, 18 Feb 2011 12:49:35 -0500 Message-ID: <000c01cbcf94$35e76e20$a1b64a60$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: AcvPlDSq8cJhLCxyRt2FzU5HA8iYLQ== Subject: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 18:13:33 -0000 Hello, I have a fairly straightforward network in a collocated facility. I have a FreeBSD PF Bridging firewall (2 interfaces bridged, 1 interface for access). The FreeBSD 8.0-RELEASE firewall provides inbound filtering through a Dell PowerConnect 5448 switch, divided into two vlans. My network is best described by the following diagram : [ISP GW] | [------switch 1 [vlan1]------] | [FW1 BRIDGE] | [------switch 1 [vlan2]------] | [clients] I have been playing around with the possibility to add another FreeBSD Bridging firewall to provide access from vlan1 > vlan2 for the clients. I originally posted on the freebsd-pf list, and the only viable solution would be to employ STP on the two freebsd server's bridge ports on vlan1 , and turn stp off for every other port. My switch also supports MSTP and RSTP protocols. Honestly I have little experience with this, but I was hoping to get some general insight as to how I could employ my switch and a redundant freebsd firewall for hardware failovers. My current testing has shown little promise -- both firewalls will go up, traffic will only go to the first firewall. If I reboot that first firewall, no traffic will flow to the second bridging firewall. Note that all IPs on my network (inside and out) are public IPs, there are no private ips on my network. Here is my rc.conf : defaultrouter="x.x.x.x" gateway_enable="YES" cloned_interfaces="bridge0" ifconfig_bridge0="up addm bge0 stp bge0 addm bge1 stp bge1" ifconfig_bge0="up" ifconfig_bge1="up" ifconfig_em0="inet y.y.y.y netmask 255.255.255.0" # PF Options pf_enable="YES" # Enable PF (load module if required) pf_rules="/etc/pf.conf" # rules definition file for pf pf_flags="" # additional flags for pfctl startup pflog_enable="YES" # start pflogd(8) pflog_logfile="/var/log/pflog" # where pflogd should store the logfile pflog_flags="" # additional flags for pflogd startup My pf.conf is really standard, I don't think there is really a point to posting it. just a block in all and a series of pass in's. nothing fancy. Any help or ideas or insight is GREATLY appreciated -- I have been tackling this for about a year (not actively, passively) and would LOVE to employ this properly. I see commercial firewalls like Juniper offer transparent bridging and failover hardware redundancies so I'm pretty sure this would be possible with FreeBSD, but again my switching and networking experience is somewhat limited. Thanks, Kevin From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 18:26:53 2011 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 56E40106564A for ; Fri, 18 Feb 2011 18:26:53 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate.funkthat.com [70.36.235.232]) by mx1.freebsd.org (Postfix) with ESMTP id 186C48FC1E for ; Fri, 18 Feb 2011 18:26:52 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id p1II5f1C085464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Feb 2011 10:05:41 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id p1II5fpf085457; Fri, 18 Feb 2011 10:05:41 -0800 (PST) (envelope-from jmg) Date: Fri, 18 Feb 2011 10:05:41 -0800 From: John-Mark Gurney To: Oliver Lehmann Message-ID: <20110218180541.GU66284@funkthat.com> Mail-Followup-To: Oliver Lehmann , net@freebsd.org References: <20110218164257.1789797hzcgoyao0@avocado.salatschuessel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110218164257.1789797hzcgoyao0@avocado.salatschuessel.net> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Fri, 18 Feb 2011 10:05:41 -0800 (PST) Cc: net@freebsd.org Subject: Re: DLNA - IGMPProxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 18:26:53 -0000 Oliver Lehmann wrote this message on Fri, Feb 18, 2011 at 16:42 +0100: > I've got a shiny new Sony TV with DLNA Support :) > My fileserver is located in a different subnet so it is not accessibly > by the TV. > The TV itself detects my netbook which is in the same subnet (and runs > Win7) as a DLNA source. > I've now tried to setup igmpproxy because I thought this might solve > my problem accessing my DLNA server in another subnet. > > - Sony TV: 10.0.2.102 (fxp2) > - FreeBSD System running mediatomb: 10.0.0.21 (fxp0) > - Win7 System: 10.0.1.51 (fxp1) [...] > My TV still does not find any DLNA sources. I did a tcpdump on my > FreeBSD system and saw that some information was exchanged. [...] > 16:33:40.700010 IP 10.0.2.102.52323 > 239.255.255.250.1900: UDP, length 404 [...] > What am I missing to get it to work? > I also tried NATing the network where the TV is attached with divert/natd > but that also did not help. > > Please keep me CCed First, UPnP is advertised over SSDP... Those port 1900 packets are the TV trying to find a media server, but no one responds to them. I have not tried to get UPnP working across subnets (yet, but I plan to in the future), but you could look at: http://frinring.wordpress.com/2010/07/27/first-release-of-cagibi-prototype-of-cacheproxy-daemon-for-upnp-device-listening-and-publishing/ I haven't d/l'd the source, but it says it's an SSDP proxy, and it could possibly work by running on the router that is on both networks... Somehow those SSDP discovery/announce packets need to make it across... Once the multicast SSDP packets get across, the rest happens on normal routable IP, so there shouldn't be additional issues, though as I said, I haven't tried it myself... Also, make sure that once they do, that the Sony TV has the proper routing to the necessary boxes...It's easy to set the default route wrong, or in some cases not set it (I did this once) causing the device to not know how to send the proper replies... Good luck! -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 20:54:49 2011 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 94ECC1065679 for ; Fri, 18 Feb 2011 20:54:49 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6A4A48FC21 for ; Fri, 18 Feb 2011 20:54:49 +0000 (UTC) Received: by pvc22 with SMTP id 22so654630pvc.13 for ; Fri, 18 Feb 2011 12:54:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=61fevxh7jgXIcdAjjpiaRZxeyhWH0lB9mPuVloGHZYs=; b=H+MpjUXt92jcnCUCrp+LwZtbHxR1Sqq3iLTRMubzEx/Fo2JBBdIOlRXeljumCWC7Lo KY5Bf5NEqn9id9mKgP3WaI7Kpej+9cIIN/TX0fCZqiQTY+f9s602kdkrMY7w6xaR5Gha WZ5Pg4AlMJY0sPM0EcULA9WcWy8y1Cnn8Zkwo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=aFwEGlb72U/ld6JQC8elQZdWfktGCRbkvBaNsyKyrt2N9lBEpY9/lzfdIx058mxJ/x BtoiLcodBgnkKrnhz0lejeDqIonRt0E6UtfhyG4H9xoXDDfxgLn2+55gtAwQmxlvP1sG gk/scGWPda59rDK3FJzXF2Ik7fHnkgDCyOOCg= MIME-Version: 1.0 Received: by 10.142.13.8 with SMTP id 8mr856399wfm.133.1298062487073; Fri, 18 Feb 2011 12:54:47 -0800 (PST) Received: by 10.142.128.18 with HTTP; Fri, 18 Feb 2011 12:54:46 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Feb 2011 15:54:46 -0500 Message-ID: From: grarpamp To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: swhetzel@gmail.com Subject: Re: bwi vs. bwn X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 20:54:49 -0000 >> I have a BCM94312MCG, which driver should I choose and why? >> The man pages are nearly identical. > > The FreeBSD bwn and bwi modules seem to be equivalent to the Linux > b43 and b43legacy drivers. This page may or may not help: > http://wireless.kernel.org/en/users/Drivers/b43 I'll see if I can find somewhere that relation between the two sets. The kernel may say something when detected/loaded. I guess only my first question about which of bwi/bwn to use applies to FreeBSD, and the other ones to the b43 guys. But I think I've got it below... >> Can the newer upstream firmware at openwrt be used with bwn-firmware-kmod? >> http://downloads.openwrt.org/sources/broadcom-wl-4.150.10.5.3.tar.bz2 I played with this, the answer is not yet. fwcutter does not yet know how to chop up the included objects. Between the two, the objects have the same version string (author possibly neglected to change) and are different sizes, hashes, etc. # 4.150.10.5 879467 Jan 6 2008 broadcom-wl-4.150.10.5/driver/wl_apsta.o 1194265 Jan 6 2008 broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o 880539 Jan 6 2009 broadcom-wl-4.150.10.5.3/driver/wl_apsta.o 1195329 Jan 6 2009 broadcom-wl-4.150.10.5.3/driver/wl_apsta_mimo.o # 4.174.64.19 9900134 Feb 19 2009 broadcom-wl-4.178.10.4/linux/wl_apsta.o >> Where did the firmware blobs in the above file come from, here? I now think the firmware blobs are fully proprietary (coming from the OEM), and are being cut up based on some hardware hacking. And that I'm likely missing the distinction between that firmware being needed in all cases, and then choosing which driver you want on top of that from amongst the (b43/kernel.org)/FreeBSD driver projects and broadcom-wl. >> http://www.broadcom.com/support/802.11/linux_sta.php Doesn't FreeBSD have some sort of ndiswrapper function for this? Seems in the future I should give my money to Atheros instead :) From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 21:12:06 2011 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 D1361106567A for ; Fri, 18 Feb 2011 21:12:06 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id 2CED28FC16 for ; Fri, 18 Feb 2011 21:12:05 +0000 (UTC) Received: (qmail 91125 invoked by uid 80); 18 Feb 2011 21:12:04 -0000 Received: from dsdf-4d0a0c32.pool.mediaWays.net (dsdf-4d0a0c32.pool.mediaWays.net [77.10.12.50]) by avocado.salatschuessel.net (Horde Framework) with HTTP; Fri, 18 Feb 2011 22:12:04 +0100 Message-ID: <20110218221204.71953x6ox42ffi4g@avocado.salatschuessel.net> Date: Fri, 18 Feb 2011 22:12:04 +0100 From: Oliver Lehmann To: John-Mark Gurney References: <20110218164257.1789797hzcgoyao0@avocado.salatschuessel.net> <20110218180541.GU66284@funkthat.com> In-Reply-To: <20110218180541.GU66284@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) / FreeBSD-7.3 Cc: net@freebsd.org Subject: Re: DLNA - IGMPProxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 21:12:06 -0000 John-Mark Gurney wrote: > First, UPnP is advertised over SSDP... Those port 1900 packets are the > TV trying to find a media server, but no one responds to them. I have > not tried to get UPnP working across subnets (yet, but I plan to in the > future), but you could look at: > http://frinring.wordpress.com/2010/07/27/first-release-of-cagibi-prototype-of-cacheproxy-daemon-for-upnp-device-listening-and-publishing/ that unfortunally requires QT for whatever reason (yeah KDE - but QT for a proxy??) I do not have this on my router of course :( ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 21:34:31 2011 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 BF61310656DF; Fri, 18 Feb 2011 21:34:31 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9018FC13; Fri, 18 Feb 2011 21:34:31 +0000 (UTC) Received: by pxi1 with SMTP id 1so659987pxi.13 for ; Fri, 18 Feb 2011 13:34:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=4rpvE9l004GNcdW66CACMPIQy1Z+JTn/+1tR65XdJG0=; b=bIAa8csmZefZUGxv8J3MFO9pwIqMYiW/+QjybBXRlY3gHcx33hbB34c4hJhoDC1yze QRA8Ahi3wvzG4LaM+sFxMBB6RAoxrX3UqGrX+kus9g9L5i/SowCsyZv+L3Xwva3nCvIY 60RaJO67+IzWz09SO+l76Lp4m0Nxi0KIGqrjE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=gNsjMQm9aCK1JU0OeNAqqvglCbPhR4Siv5fTajeyd7z2auq3EfuilfVa70ozkT5SGF I/Tks5CsrSugoHnPiMuAlUMa/xuV+J+iNq2JDfjzWTLl07YRAEJbgNoXBduIwjxSr8Aq 6Q+nPNO9ktDkto/54jeRXSgtETG/6M1zpP5iY= MIME-Version: 1.0 Received: by 10.142.131.16 with SMTP id e16mr899014wfd.228.1298064870899; Fri, 18 Feb 2011 13:34:30 -0800 (PST) Received: by 10.142.128.18 with HTTP; Fri, 18 Feb 2011 13:34:30 -0800 (PST) Date: Fri, 18 Feb 2011 16:34:30 -0500 Message-ID: From: grarpamp To: swhetzel@gmail.com Content-Type: multipart/mixed; boundary=000e0cd29cf28680df049c9547a9 Cc: freebsd-net@freebsd.org, freebsd-ports@freebsd.org Subject: b43-fwcutter port update to v13 [patch] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 21:34:31 -0000 --000e0cd29cf28680df049c9547a9 Content-Type: text/plain; charset=ISO-8859-1 I diffed the source of b43-fwcutter, v12 to v13. And also between v12 + fbsd port patches and v13 native. It all looks clean, both compile, and v13 produces digest identical output files to v12 + fbsd port when used as in the bwi and bwn kmod ports. The current fwcutter port can thus be bumped to v13. Update Makefile, distinfo, pkg-descr, distfiles, etc. Replace the entire patch set with these new native patches. Update the requires for the bw{i,n}-firmware-kmod ports. Can someone check and commit all this? I bcc'd the fwcutter author for inclusion of the patch in the next release. --000e0cd29cf28680df049c9547a9 Content-Type: application/octet-stream; name=patch_b43-fwcutter-013 Content-Disposition: attachment; filename=patch_b43-fwcutter-013 Content-Transfer-Encoding: base64 X-Attachment-Id: file0 LS0tIE1ha2VmaWxlLm9yaWcJMjAxMC0wNC0xOSAxMTo1MTowNS4wMDAwMDAwMDAgLTA0MDAKKysr IE1ha2VmaWxlCkBAIC0xMiw3ICsxMiw3IEBACiBpZmVxICgkKEMpLDEpCiBRVUlFVF9TUEFSU0UJ PSAkKFE6QD1AZWNobyAnICAgICBTUEFSU0UgICAnJEA7KSQoU1BBUlNFKQogZWxzZQotUVVJRVRf U1BBUlNFCT0gQC9iaW4vdHJ1ZQorUVVJRVRfU1BBUlNFCT0gQHRydWUKIGVuZGlmCiAKIFBSRUZJ WCA/PSAvdXNyL2xvY2FsCi0tLSBmd2N1dHRlci5jLm9yaWcJMjAxMC0wNC0xOSAxMTo1MTowNS4w MDAwMDAwMDAgLTA0MDAKKysrIGZ3Y3V0dGVyLmMKQEAgLTM4LDcgKzM4LDcgQEAKICNpbmNsdWRl IDxzeXMvc3RhdC5oPgogI2luY2x1ZGUgPHN5cy90eXBlcy5oPgogCi0jaWZkZWYgX19EcmFnb25G bHlfXworI2lmIGRlZmluZWQoX19EcmFnb25GbHlfXykgfHwgZGVmaW5lZChfX0ZyZWVCU0RfXykK ICNpbmNsdWRlIDxzeXMvZW5kaWFuLmg+CiAjZWxzZQogI2luY2x1ZGUgPGJ5dGVzd2FwLmg+CkBA IC00OCw3ICs0OCw3IEBACiAjaW5jbHVkZSAiZndjdXR0ZXIuaCIKICNpbmNsdWRlICJmd2N1dHRl cl9saXN0LmgiCiAKLSNpZmRlZiBfX0RyYWdvbkZseV9fCisjaWYgZGVmaW5lZChfX0RyYWdvbkZs eV9fKSB8fCBkZWZpbmVkKF9fRnJlZUJTRF9fKQogI2RlZmluZSBWM19GV19ESVJOQU1FCSJ2MyIK ICNkZWZpbmUgVjRfRldfRElSTkFNRQkidjQiCiAjZWxzZQotLS0gZndjdXR0ZXIuaC5vcmlnCTIw MTAtMDQtMTkgMTE6NTE6MDUuMDAwMDAwMDAwIC0wNDAwCisrKyBmd2N1dHRlci5oCkBAIC0xNSw3 ICsxNSw3IEBACiB0eXBlZGVmIHVpbnQxNl90IGJlMTZfdDsgLyogQmlnLWVuZGlhbiAxNmJpdCAq LwogdHlwZWRlZiB1aW50MzJfdCBiZTMyX3Q7IC8qIEJpZy1lbmRpYW4gMzJiaXQgKi8KIAotI2lm ZGVmIF9fRHJhZ29uRmx5X18KKyNpZiBkZWZpbmVkKF9fRHJhZ29uRmx5X18pIHx8IGRlZmluZWQo X19GcmVlQlNEX18pCiAjZGVmaW5lIGJzd2FwXzE2CWJzd2FwMTYKICNkZWZpbmUgYnN3YXBfMzIJ YnN3YXAzMgogI2VuZGlmCg== --000e0cd29cf28680df049c9547a9-- From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 22:02:01 2011 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 825F61065675 for ; Fri, 18 Feb 2011 22:02:01 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3BABE8FC1C for ; Fri, 18 Feb 2011 22:02:01 +0000 (UTC) Received: by vxa40 with SMTP id 40so2305618vxa.13 for ; Fri, 18 Feb 2011 14:02:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=B+qbh7GnnKMg15LfVl7bG6RpTC1Y6WBCfCSTuK2U+c4=; b=mAFXNO5vY8QIBkdph/Bv08IQ46hWouJC07nQE6iY029ebK2bNvssDqt9nATN4sYOrO 4LzoHftXBLV6WbN3w2YWKyAfAuylOa4OgsS0+RRkECuSM4KEe+JDPrHnnzPC+oU0N/Og Owhw5WYAY1G1vy2NRy4ICBCc6//THRxYYWqS8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=OldYpPGYYL6CBO7B0tunTBXFiXVTnwCghvBxJc7fjZrqUzQEm/Y+mf/q37L1nRDS1X OX+0ROPg3lSqJ/UIrsVQsYYQISJUuJ9nmnM2qqaekxH9243+6VEUhwYryuNCGizDjDVc 6tapHpmX776AWvFxlg1360txxn9ZenayvUeo0= Received: by 10.52.169.168 with SMTP id af8mr2166013vdc.133.1298064713054; Fri, 18 Feb 2011 13:31:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.57.140 with HTTP; Fri, 18 Feb 2011 13:31:33 -0800 (PST) In-Reply-To: References: From: "Paul B. Mahol" Date: Fri, 18 Feb 2011 22:31:33 +0100 Message-ID: To: grarpamp Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, swhetzel@gmail.com Subject: Re: bwi vs. bwn X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 22:02:01 -0000 On Fri, Feb 18, 2011 at 9:54 PM, grarpamp wrote: > Doesn't FreeBSD have some sort of ndiswrapper function for this? NDISulator, ndis(4). From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 22:17:32 2011 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 2E3F31065672 for ; Fri, 18 Feb 2011 22:17:32 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout029.mac.com (asmtpout029.mac.com [17.148.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id 153298FC18 for ; Fri, 18 Feb 2011 22:17:32 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp029.mac.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LGU00ET70H7DZ30@asmtp029.mac.com> for net@freebsd.org; Fri, 18 Feb 2011 13:17:32 -0800 (PST) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2011-02-18_08:2011-02-18, 2011-02-18, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1102180124 From: Chuck Swiger In-reply-to: <20110218221204.71953x6ox42ffi4g@avocado.salatschuessel.net> Date: Fri, 18 Feb 2011 13:17:31 -0800 Message-id: <5F950533-280F-4D84-89F6-E85FEA213D67@mac.com> References: <20110218164257.1789797hzcgoyao0@avocado.salatschuessel.net> <20110218180541.GU66284@funkthat.com> <20110218221204.71953x6ox42ffi4g@avocado.salatschuessel.net> To: Oliver Lehmann X-Mailer: Apple Mail (2.1082) Cc: net@freebsd.org Subject: Re: DLNA - IGMPProxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 22:17:32 -0000 On Feb 18, 2011, at 1:12 PM, Oliver Lehmann wrote: > that unfortunally requires QT for whatever reason (yeah KDE - but > QT for a proxy??) I do not have this on my router of course :( Most of this stuff uses subnet-local broadcasts to perform device discovery. It would probably be a lot easier to bridge your networks together than it would be to proxy DLNA.... Regards, -- -Chuck From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 22:26:08 2011 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 053AA106566C for ; Fri, 18 Feb 2011 22:26:08 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id CE3F78FC1C for ; Fri, 18 Feb 2011 22:26:07 +0000 (UTC) Received: by pwj8 with SMTP id 8so152004pwj.13 for ; Fri, 18 Feb 2011 14:26:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Ofo6znC63fFc3QtUAY2cDR1yk5QdBD+DeJCP8IGx444=; b=K5G2A74w1pxWDozhG81QZmDMF5XGcKG5K5opQSn6+wcW61JOVojaS9PyI5WKq0QoQ8 jKTSy/OqSYOCSAUz45bPXPstMiI7nMk9/zprI+yxyy+UdaLPmKB/z9SSEOOcU2qpnxeU iTb3ZTtHK24oyzWVQBAePO2Cj0JeYkMqqfxkg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Uo4XH4rn/4XZP7w6csAkxx0+sSwQF5fHHs3QxVRQo+KJzzS0br3bLjAQgIlUnGBqX4 tvTfTIJVIt6ffwOnI66Us+dZs5Zx7RAfV/+i4hiGWjrLqq7bP0PK1djl2XFU7gTnpyVD 80T2SA2NREnvAQ5AG3fwL5oISWeLzAj5P2qDk= MIME-Version: 1.0 Received: by 10.142.216.1 with SMTP id o1mr938351wfg.190.1298067965871; Fri, 18 Feb 2011 14:26:05 -0800 (PST) Received: by 10.142.128.18 with HTTP; Fri, 18 Feb 2011 14:26:05 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Feb 2011 17:26:05 -0500 Message-ID: From: grarpamp To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: bwi vs. bwn X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 22:26:08 -0000 >> Doesn't FreeBSD have some sort of ndiswrapper function for this? >> http://www.broadcom.com/support/802.11/linux_sta.php > NDISulator, ndis(4). Hmm, maybe that only applies to the Windows driver bundles as distributed by the vendors (Dell, HP, Lenovo, etc). Or from Microsoft itself as part of the OS. And not to this Linux thing. Once I figure out how to extract the Microsoft (Windows/Vendor) and Linux (Broadcom) bundles, hopefully with the same underlying version, I'll know more, call it an excercise :) I'm sure bwn will work. Thanks. # Broadcom Linux 1195817 Dec 22 20:59 hybrid-portsrc_x86_32-v5_100_82_38.tar.gz 1150253 Dec 22 20:59 hybrid-portsrc_x86_64-v5_100_82_38.tar.gz From owner-freebsd-net@FreeBSD.ORG Fri Feb 18 23:31:40 2011 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 DCC34106564A; Fri, 18 Feb 2011 23:31:40 +0000 (UTC) (envelope-from mb@bu3sch.de) Received: from bu3sch.de (80-190-117-144.ip-home.de [80.190.117.144]) by mx1.freebsd.org (Postfix) with ESMTP id A1C2C8FC12; Fri, 18 Feb 2011 23:31:40 +0000 (UTC) Received: by bu3sch.de with esmtpsa (Exim 4.69) (envelope-from ) id 1PqZ7o-0001fL-2x; Fri, 18 Feb 2011 23:48:32 +0100 From: Michael =?ISO-8859-1?Q?B=FCsch?= To: grarpamp In-Reply-To: (sfid-20110218_223443_390885_25A62E74) References: (sfid-20110218_223443_390885_25A62E74) Content-Type: text/plain; charset="UTF-8" Date: Fri, 18 Feb 2011 23:48:23 +0100 Message-ID: <1298069303.23801.30.camel@maggie> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, swhetzel@gmail.com, freebsd-ports@freebsd.org Subject: Re: b43-fwcutter port update to v13 [patch] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2011 23:31:41 -0000 On Fri, 2011-02-18 at 16:34 -0500, grarpamp wrote: > I bcc'd the fwcutter author for inclusion of the patch in the next > release. Thanks a lot. I'll commit it to git. -- Greetings Michael. From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 11:41:17 2011 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 839BA106564A for ; Sat, 19 Feb 2011 11:41:17 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id D21098FC1D for ; Sat, 19 Feb 2011 11:41:16 +0000 (UTC) Received: (qmail invoked by alias); 19 Feb 2011 11:41:15 -0000 Received: from adsl-39.79.107.47.tellas.gr (EHLO [192.168.73.192]) [79.107.47.39] by mail.gmx.com (mp-eu004) with SMTP; 19 Feb 2011 12:41:15 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX1+qeiUaNtiqRidoumf1gkthxaar//FHmhpoa8duTF tXFahuZxyAolvk Message-ID: <4D5FAC16.7080207@gmx.com> Date: Sat, 19 Feb 2011 13:40:06 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: kevin References: <000c01cbcf94$35e76e20$a1b64a60$@com> In-Reply-To: <000c01cbcf94$35e76e20$a1b64a60$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-net@freebsd.org Subject: Re: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 11:41:17 -0000 On 2/18/2011 7:49 PM, kevin wrote: > My current testing has shown little promise -- both firewalls will go up, > traffic will only go to the first firewall. If I reboot that first firewall, > no traffic will flow to the second bridging firewall. Note that all IPs on > my network (inside and out) are public IPs, there are no private ips on my > network. Could you send your ifconfig bridge output from both firewalls? If STP is turned off on the four switch ports that the firewalls are patched, one of the two firewalls must be root of the spanning tree. Be sure that STP is *really* turned off on the switch, use tcpdump on the physical ports for this. Be sure that the FreeBSD's BPDUs are forwarded by the switch, so the one bridging firewall can exchange BPDUs with the other. HTH, Nikos From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 14:13:44 2011 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 C759C106566B for ; Sat, 19 Feb 2011 14:13:44 +0000 (UTC) (envelope-from k@kevinkevin.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 999E38FC13 for ; Sat, 19 Feb 2011 14:13:44 +0000 (UTC) Received: by iyb26 with SMTP id 26so4551080iyb.13 for ; Sat, 19 Feb 2011 06:13:44 -0800 (PST) Received: by 10.231.159.206 with SMTP id k14mr1374597ibx.170.1298124823895; Sat, 19 Feb 2011 06:13:43 -0800 (PST) Received: from kkPC (not.enough.unixsluts.com [76.10.166.187]) by mx.google.com with ESMTPS id 8sm2889719iba.22.2011.02.19.06.13.41 (version=SSLv3 cipher=OTHER); Sat, 19 Feb 2011 06:13:42 -0800 (PST) From: "kevin" To: "'Nikos Vassiliadis'" References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> In-Reply-To: <4D5FAC16.7080207@gmx.com> Date: Sat, 19 Feb 2011 09:13:23 -0500 Message-ID: <00a201cbd03f$2bdc3540$83949fc0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: AcvQKeqyZBxgG7mZRTylwVuqC7AjegAFMI9g Cc: freebsd-net@freebsd.org Subject: RE: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 14:13:44 -0000 >Could you send your ifconfig bridge output from both firewalls? >If STP is turned off on the four switch ports that the firewalls are >patched, one of the two firewalls must be root of the spanning tree. I believe if you don't specify 'stp' in the rc.conf ifconfig statement, freebsd by default sets the bridge as 'rstp' : sdh-fw# ifconfig em0: flags=8843 metric 0 mtu 1500 options=9b ether 00:1b:21:23:5e:34 inet x.x.x.x netmask 0xffffffc0 broadcast x.x.x.255 media: Ethernet autoselect (1000baseT ) status: active bge0: flags=8943 metric 0 mtu 1500 options=9b ether 00:0b:cd:82:19:d3 media: Ethernet autoselect (1000baseT ) status: active bge1: flags=8943 metric 0 mtu 1500 options=9b ether 00:0b:cd:82:19:c0 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 pflog0: flags=141 metric 0 mtu 33200 pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 bridge0: flags=8843 metric 0 mtu 1500 ether 06:c7:a9:50:41:17 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: bge1 flags=143 ifmaxaddr 0 port 3 priority 128 path cost 55 member: bge0 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 55 >Be sure that STP is *really* turned off on the switch, use tcpdump on the >physical ports for this. Should I just turn off STP for every port on the switch or just the ports connected to the bridge? >Be sure that the FreeBSD's BPDUs are forwarded by the switch, so the one >bridging firewall can exchange BPDUs with the other. I see now. I will try this again and tcpdump on the non-active firewall when I manually fail over during my next test. Thank you very much for clarifying! ~k From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 14:33:56 2011 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 7F2D61065679 for ; Sat, 19 Feb 2011 14:33:56 +0000 (UTC) (envelope-from prvs=10311e3df6=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 1A1A98FC08 for ; Sat, 19 Feb 2011 14:33:55 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 19 Feb 2011 14:22:53 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 19 Feb 2011 14:22:53 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50012258197.msg; Sat, 19 Feb 2011 14:22:51 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=10311e3df6=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: , Date: Sat, 19 Feb 2011 14:22:58 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: Subject: bge0 watchdog timeout -- resetting on 8.2-PREREL never recovers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 14:33:56 -0000 Just updated a box to the 8.2-PREREL as of friday and now when we do any serious amounts of network traffice we see:- bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP The interface never recovers, we have to use remote console to down, wait 30 seconds then up the interface to restore network access. This is the details from dmesg:- bge0: mem 0xfc9f0000-0xfc9fffff irq 26 at device 5.0 on pci3 bge0: CHIP ID 0x00002100; ASIC REV 0x02; CHIP REV 0x21; PCI-X miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:30:48:75:32:42 bge0: [ITHREAD] pciconf -lbvc:- bge0@pci0:3:5:0: class=0x020000 card=0x164815d9 chip=0x164814e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme Dual Gigabit Adapter (BCM5704)' class = network subclass = ethernet bar [10] = type Memory, range 64, base 0xfc9f0000, size 65536, enabled cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 01[48] = powerspec 2 supports D0 D3 current D0 cap 03[50] = VPD cap 05[58] = MSI supports 8 messages, 64 bit Searching around I thought that r216970 might fix this but it looks like this is already present in another (if_bge.c,v 1.226.2.49) Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 14:53:21 2011 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 D1CA41065679 for ; Sat, 19 Feb 2011 14:53:21 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 57CFB8FC14 for ; Sat, 19 Feb 2011 14:53:21 +0000 (UTC) Received: (qmail invoked by alias); 19 Feb 2011 14:53:19 -0000 Received: from adsl-39.79.107.47.tellas.gr (EHLO [192.168.73.192]) [79.107.47.39] by mail.gmx.com (mp-eu001) with SMTP; 19 Feb 2011 15:53:19 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX1/NNkRICpzNYmmsuWqbVPo9YLS7OUsUTRRl+ITxko 67SRaE2CUkMW7r Message-ID: <4D5FD91F.20704@gmx.com> Date: Sat, 19 Feb 2011 16:52:15 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: kevin References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> In-Reply-To: <00a201cbd03f$2bdc3540$83949fc0$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-net@freebsd.org Subject: Re: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 14:53:22 -0000 On 2/19/2011 4:13 PM, kevin wrote: > >> Could you send your ifconfig bridge output from both firewalls? >> If STP is turned off on the four switch ports that the firewalls are >> patched, one of the two firewalls must be root of the spanning tree. > > I believe if you don't specify 'stp' in the rc.conf ifconfig statement, > freebsd by default sets the bridge as 'rstp' : Yes, that's correct. > > sdh-fw# ifconfig > bridge0: flags=8843 metric 0 mtu > 1500 > ether 06:c7:a9:50:41:17 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: bge1 flags=143 > ifmaxaddr 0 port 3 priority 128 path cost 55 > member: bge0 flags=143 > ifmaxaddr 0 port 2 priority 128 path cost 55 > There is no active STP there. The port should look like this: You should also see the bridge's ID and not 00:00:00:00:00:00: > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 You should also see the root bridge's ID of the STP domain: > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 A bridge will look like this: bridge2: flags=8843 metric 0 mtu 1500 ether a2:ae:00:08:a7:ab inet 10.16.0.2 netmask 0xff000000 broadcast 10.255.255.255 id 00:17:d6:a9:31:e7 priority 16384 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:12:cf:69:e9:ea priority 16384 ifcost 14183 port 4 member: epair14b flags=1c7 ifmaxaddr 0 port 9 priority 128 path cost 14183 proto rstp role designated state forwarding member: epair13b flags=1c7 ifmaxaddr 0 port 8 priority 128 path cost 14183 proto rstp role designated state forwarding member: epair10b flags=1c7 ifmaxaddr 0 port 7 priority 128 path cost 14183 proto rstp role alternate state discarding ... And the root bridge will look like this: bridge4: flags=8843 metric 0 mtu 1500 ether ae:6e:5a:9d:9b:5c inet 10.16.0.4 netmask 0xff000000 broadcast 10.255.255.255 id 00:12:cf:69:e9:ea priority 16384 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:12:cf:69:e9:ea priority 16384 ifcost 0 port 0 member: epair18b flags=1c7 ifmaxaddr 0 port 9 priority 128 path cost 14183 proto rstp role designated state forwarding member: epair17b flags=1c7 ifmaxaddr 0 port 8 priority 128 path cost 14183 proto rstp role designated state forwarding member: epair11a flags=1c7 ifmaxaddr 0 port 7 priority 128 path cost 14183 proto rstp role designated state forwarding ... > >> Be sure that STP is *really* turned off on the switch, use tcpdump on the >> physical ports for this. > > Should I just turn off STP for every port on the switch or just the ports > connected to the bridge? Just the ports connected to the bridging firewalls. Your topology looks like this, correct? http://img811.imageshack.us/i/bridgingfw.png/ The switch must act as a plain ethernet switch, no stp, no BPDU filtering, no nothing. The STP on the firewalls will handle the loop in the topology. Be *sure* that STP is active on the firewalls and the two firewall are in a single STP domain(can talk STP to each other), otherwise a L2 loop will do a DoS on your firewalls... HTH, Nikos From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 15:09:40 2011 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 F3C68106566B for ; Sat, 19 Feb 2011 15:09:39 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 4CF468FC0C for ; Sat, 19 Feb 2011 15:09:39 +0000 (UTC) Received: (qmail invoked by alias); 19 Feb 2011 15:09:37 -0000 Received: from adsl-39.79.107.47.tellas.gr (EHLO [192.168.73.192]) [79.107.47.39] by mail.gmx.com (mp-eu001) with SMTP; 19 Feb 2011 16:09:37 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX18o/8hBhIcoQ6T+6bO5nyQvTrdEa/FrcQlSTB/4mz PoswiaDKW8llmB Message-ID: <4D5FDCF1.6050909@gmx.com> Date: Sat, 19 Feb 2011 17:08:33 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: kevin References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> In-Reply-To: <4D5FD91F.20704@gmx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-net@freebsd.org Subject: Re: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 15:09:40 -0000 On 2/19/2011 4:52 PM, Nikos Vassiliadis wrote: >> I believe if you don't specify 'stp' in the rc.conf ifconfig statement, >> freebsd by default sets the bridge as 'rstp' : > > Yes, that's correct. It helps sometimes when you read the actual message before trying to answer:) No, you have to specify stp there. The default STP mode is RSTP. If you don't specify stp, you'll get a dumb ethernet bridge. Nikos From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 15:59:45 2011 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 166481065672; Sat, 19 Feb 2011 15:59:45 +0000 (UTC) (envelope-from prvs=10311e3df6=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 7B3428FC0C; Sat, 19 Feb 2011 15:59:44 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 19 Feb 2011 15:59:25 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 19 Feb 2011 15:59:25 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50012258721.msg; Sat, 19 Feb 2011 15:59:25 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=10311e3df6=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <2FA20352DEB643BEA7EAB90A14346894@multiplay.co.uk> From: "Steven Hartland" To: "Steven Hartland" , , References: Date: Sat, 19 Feb 2011 15:59:57 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Cc: Subject: Re: bge0 watchdog timeout -- resetting on 8.2-PREREL never recovers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 15:59:45 -0000 This may be totally unrelated to bge, investigating a potential failing stick of ram in the machine in question so until we've ruled this out as the cause don't want to waste anyone's time. I did however notice the logic between the two fixes for DMA on 5704's on PCIX in svn differ so wondering which ones correct:- http://svn.freebsd.org/viewvc/base/head/sys/dev/bge/if_bge.c?r1=216085&r2=216970 http://svn.freebsd.org/viewvc/base/head/sys/dev/bge/if_bge.c?r1=217225&r2=217226 r216970 results in: 1, 0, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, where as r217226 results in: 1, BGE_DMA_BNDRY, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 16:08:00 2011 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 7B40F106564A for ; Sat, 19 Feb 2011 16:08:00 +0000 (UTC) (envelope-from k@kevinkevin.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4C1FD8FC14 for ; Sat, 19 Feb 2011 16:08:00 +0000 (UTC) Received: by iyb26 with SMTP id 26so4617035iyb.13 for ; Sat, 19 Feb 2011 08:07:59 -0800 (PST) Received: by 10.42.239.72 with SMTP id kv8mr2490281icb.183.1298131679677; Sat, 19 Feb 2011 08:07:59 -0800 (PST) Received: from kkPC (not.enough.unixsluts.com [76.10.166.187]) by mx.google.com with ESMTPS id gy41sm2975255ibb.11.2011.02.19.08.07.57 (version=SSLv3 cipher=OTHER); Sat, 19 Feb 2011 08:07:58 -0800 (PST) From: "kevin" To: "'Nikos Vassiliadis'" References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> <4D5FDCF1.6050909@gmx.com> In-Reply-To: <4D5FDCF1.6050909@gmx.com> Date: Sat, 19 Feb 2011 11:07:39 -0500 Message-ID: <00a501cbd04f$2276b5b0$67642110$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: AcvQRwcQCc0Osi5IRpyx/fvaKZ0MCQAB+Jpg Cc: freebsd-net@freebsd.org Subject: RE: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 16:08:00 -0000 >No, you have to specify stp there. The default STP mode is RSTP. >If you don't specify stp, you'll get a dumb ethernet bridge. Thanks very much for clarification. This helps me immensely. My room for testing is limited so this will help me take the right steps necessary. One quick last question : would you recommend pfsync in this scenario, between bridges? I've been hearing a lot of issues with pfsync but I'm not sure what behavior to expect in a bridging scenario such as this one. From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 16:12:04 2011 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 32B2C106566C for ; Sat, 19 Feb 2011 16:12:04 +0000 (UTC) (envelope-from k@kevinkevin.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 034488FC12 for ; Sat, 19 Feb 2011 16:12:03 +0000 (UTC) Received: by iyb26 with SMTP id 26so4619634iyb.13 for ; Sat, 19 Feb 2011 08:12:03 -0800 (PST) Received: by 10.42.239.8 with SMTP id ku8mr2526931icb.34.1298131923274; Sat, 19 Feb 2011 08:12:03 -0800 (PST) Received: from kkPC (not.enough.unixsluts.com [76.10.166.187]) by mx.google.com with ESMTPS id 8sm2978672iba.10.2011.02.19.08.12.01 (version=SSLv3 cipher=OTHER); Sat, 19 Feb 2011 08:12:02 -0800 (PST) From: "kevin" To: "'Nikos Vassiliadis'" References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> In-Reply-To: <4D5FD91F.20704@gmx.com> Date: Sat, 19 Feb 2011 11:11:42 -0500 Message-ID: <00a801cbd04f$b3991920$1acb4b60$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: AcvQRL+Jtr6p+fzQSSyPpA/MQ86C3gACqLJg Cc: freebsd-net@freebsd.org Subject: RE: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 16:12:04 -0000 One other thing : > id 00:17:d6:a9:31:e7 priority 16384 hellotime 2 fwddelay 15 And : > root id 00:12:cf:69:e9:ea priority 16384 ifcost 0 port 0 I was under the impression the priority for the root bridge should be a lower number ? Would you be able to post your rc.conf bridge entries for each bridge, perhaps? Thanks! From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 16:37:14 2011 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 8EE921065694 for ; Sat, 19 Feb 2011 16:37:14 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id D6AA08FC08 for ; Sat, 19 Feb 2011 16:37:13 +0000 (UTC) Received: (qmail invoked by alias); 19 Feb 2011 16:37:12 -0000 Received: from adsl-39.79.107.47.tellas.gr (EHLO [192.168.73.192]) [79.107.47.39] by mail.gmx.com (mp-eu004) with SMTP; 19 Feb 2011 17:37:12 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX181OAgd9y412Ok7tCNB6FFm7j7b7PIguvkr5kR7ul EBRgenYIavBkVu Message-ID: <4D5FF174.3080501@gmx.com> Date: Sat, 19 Feb 2011 18:36:04 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: kevin References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> <00a801cbd04f$b3991920$1acb4b60$@com> In-Reply-To: <00a801cbd04f$b3991920$1acb4b60$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-net@freebsd.org Subject: Re: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 16:37:14 -0000 On 2/19/2011 6:11 PM, kevin wrote: > One other thing : > >> id 00:17:d6:a9:31:e7 priority 16384 hellotime 2 fwddelay 15 > > And : > >> root id 00:12:cf:69:e9:ea priority 16384 ifcost 0 port 0 > > > I was under the impression the priority for the root bridge should be a > lower number ? The priority is checked first when two bridges exchange BPDUs. The bridge with the lower number wins. If the priority is the same then the bridge's ID is used for the elections. It would be best to manually set the priority in order to know who is administratively the active firewall. > Would you be able to post your rc.conf bridge entries for > each bridge, perhaps? Sorry, this is a lab environment, I am not using rc facilities. It is just a shell script... Nikos From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 16:39:03 2011 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 BB9B31065670 for ; Sat, 19 Feb 2011 16:39:03 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 13B298FC0A for ; Sat, 19 Feb 2011 16:39:02 +0000 (UTC) Received: (qmail invoked by alias); 19 Feb 2011 16:39:01 -0000 Received: from adsl-39.79.107.47.tellas.gr (EHLO [192.168.73.192]) [79.107.47.39] by mail.gmx.com (mp-eu005) with SMTP; 19 Feb 2011 17:39:01 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX1++KfUzCIi+jWcKWT7HfuBZXCi9SsH9zgTlQ9/Fj2 /p/8xYW5oH0s9x Message-ID: <4D5FF1E5.4020608@gmx.com> Date: Sat, 19 Feb 2011 18:37:57 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: kevin References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> <4D5FDCF1.6050909@gmx.com> <00a501cbd04f$2276b5b0$67642110$@com> In-Reply-To: <00a501cbd04f$2276b5b0$67642110$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-net@freebsd.org Subject: Re: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 16:39:03 -0000 On 2/19/2011 6:07 PM, kevin wrote: > One quick last question : would you recommend pfsync in this scenario, > between bridges? I've been hearing a lot of issues with pfsync but I'm not > sure what behavior to expect in a bridging scenario such as this one. Can't really comment about pfsync as i have no experience of my own... From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 17:51:14 2011 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 BC264106564A for ; Sat, 19 Feb 2011 17:51:14 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 6B0EC8FC08 for ; Sat, 19 Feb 2011 17:51:14 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id AF2CBDCB3C; Sat, 19 Feb 2011 17:32:20 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0sEj3Q9vk7u; Sat, 19 Feb 2011 17:32:18 +0000 (GMT) Received: from Tom-Judges-MacBook-Pro.local (unknown [192.168.205.10]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id E5545DCB3B; Sat, 19 Feb 2011 17:32:16 +0000 (GMT) Message-ID: <4D5FFE9C.30005@tomjudge.com> Date: Sat, 19 Feb 2011 12:32:12 -0500 From: Tom Judge User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: kevin References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> <4D5FDCF1.6050909@gmx.com> <00a501cbd04f$2276b5b0$67642110$@com> In-Reply-To: <00a501cbd04f$2276b5b0$67642110$@com> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1C1D810054B52101522B7485" Cc: freebsd-net@freebsd.org, 'Nikos Vassiliadis' Subject: Re: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 17:51:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1C1D810054B52101522B7485 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 19/02/2011 11:07, kevin wrote: >> No, you have to specify stp there. The default STP mode is RSTP. >> If you don't specify stp, you'll get a dumb ethernet bridge. > Thanks very much for clarification. This helps me immensely. My room fo= r > testing is limited so this will help me take the right steps necessary.= > > One quick last question : would you recommend pfsync in this scenario, > between bridges? I've been hearing a lot of issues with pfsync but I'm = not > sure what behavior to expect in a bridging scenario such as this one. > This setup with pfsync will work ok as long as you have the STP setup correctly. As to the STP. I can see an issue with this setup if you are using a single switch and 2 firewalls. You will have the following links: - - - - In this setup it does not matter where the root bridge is, each of the firewalls will always have on port in disguarding state as both ports lead back to the same peer bridge. With states such as: fw 1 - 1: forwarding fw 2 - 1: forwarding fw 1 - 2: disguarding - backup fw 2 - 2: disguarding - backup If you disable STP on the ports for the firewalls you will have virtual links: - - This will create the following states (the same as above): fw 1 - 1: forwarding fw 2 - 1: forwarding fw 1 - 2: disguarding - backup fw 2 - 2: disguarding - backup There is a also the caveat: The switch will probably _not_ forward the STP BPDU's from one port to another. This is because if the switch is a properly compliant bridge it will not forwards the frames as they are marked as link local ethernet multicast frame which is not allowed to forwarded by a bridge per the ethernet spec. If this is indeed the case you will make an instant forwarding loop in your network when you try to make it work. You will need to introducing a 4th STP speaking device to the configuration with a topology such as this: < switch 1 > | | | | - | | | < switch 2 > Where the link between switch 1 and 2 is a trunk with both the vlans on it. This way you can set the root bridge to firewall 1 and firewall 2 as the second highest priority and the switches equal 3rd priorities. I would also recommend that FW 1 and 2 have opposite vlan assignments on each switch, this way you can add a 3rd port to each firewall and link them together, and you will be able to survive a switch failure as well. _______________________________________________ > 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" --------------enig1C1D810054B52101522B7485 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNX/6gAAoJEMSwVS7lr0OdwysIAJXhPkcSi2Pdo6AySGkNJGCZ tijgpaGmkRKKugrSTg4zKidLpJYNsqTvFUBWHGsu6wFavpEc1Pz8LvwI6iyzeo7a BA4ievF/BXOCOPArb3wIif9biYxfdJAjoeVQh1EuIv/5svvdR02iF+rs1dmIuPri pXON6JJEIejxmzKgA5EXiMKm1clBXDMMgQflm39KtSXeH7c2zoVVBKeL0ZoKfEGm ZWjeeFNE9WtvP9MNunZmtNP4o5GUMGz87SVflZNM+Gq5j3aKmx2/Bc4Qe6cTKJo1 ZZLwh4issfIAIflixOzm4F4S8047+LxU9WbVlcGqa0V2hNZCT8ukyXFlaTfz0lg= =j+2t -----END PGP SIGNATURE----- --------------enig1C1D810054B52101522B7485-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 19:54:47 2011 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 1B3E51065670 for ; Sat, 19 Feb 2011 19:54:47 +0000 (UTC) (envelope-from la5lbtyi@aon.at) Received: from email.aon.at (nat-warsl417-01.aon.at [195.3.96.119]) by mx1.freebsd.org (Postfix) with ESMTP id 70E6D8FC14 for ; Sat, 19 Feb 2011 19:54:46 +0000 (UTC) Received: (qmail 22738 invoked from network); 19 Feb 2011 19:28:04 -0000 Received: from smarthub93.highway.telekom.at (HELO email.aon.at) ([172.18.5.237]) (envelope-sender ) by fallback44.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 19 Feb 2011 19:28:04 -0000 Received: (qmail 27998 invoked from network); 19 Feb 2011 19:28:02 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL502.highway.telekom.at X-Spam-Level: Received: from 178-191-94-218.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([178.191.94.218]) (envelope-sender ) by smarthub93.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 19 Feb 2011 19:28:02 -0000 Received: from atpcdvvc.xyzzy (atpcdvvc.xyzzy [IPv6:fec0:0:0:4d42::84]) by gandalf.xyzzy (8.14.4/8.14.4) with ESMTP id p1JJS2Ee040437 for ; Sat, 19 Feb 2011 20:28:02 +0100 (CET) (envelope-from la5lbtyi@aon.at) Message-ID: <4D6019C2.3000001@aon.at> Date: Sat, 19 Feb 2011 20:28:02 +0100 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.16) Gecko/20101219 Thunderbird/3.0.11 MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Vote in favor of keeping ATM (was: NATM still scheduled for removal - please follow up to keep it in-tree) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 19:54:47 -0000 Hi, I would like to vote in favor of keeping NATM in the kernel. The reason is that I am currently working on writing a device driver for the SpeedTouch USB modem, to replace ports/net/pppoa which is not supported on FreeBSD8+ any more. The SpeedTouch USB in fact terminates as an ATM connection, on top of which PPPoA needs to be layered. From my experiments with compiling a kernel with "device atm" and "options NATM", I know that currently only the former works, this being due to unmaintained and broken code dealing with routing entries. I am currently not much of a kernel code expert, but have already managed to write enough of the USB side of the device driver to load the modem's firmware. The next step would be to connect it to the ATM stack, using this route: 1. Terminate as ATM interface (ATM cells arriving); 2. The ATM stack implements AAL5 (I hope); 3. Capture the interface via ng_atm (which, as far as I understand, would more aptly be named ng_natm); 4. Extend the functionality of ng_atmllc (which basically does a small subset of RFC2684) to also do LLC/ISO (cf. RFC2364) (then better named ng_llc); 5. Couple the resultant PPP stream to ng_ppp; 6. Use something to configure the VPI/VCI (what?); 7. Run ports/net/mpd5 on that netgraph node. 5. and 7. could be replaced by ng_tty and ppp(8), but that would be the poorer choice as all traffic would have to go through userland again as it is doing with ports/net/pppoa. For this I'd need a) a working ATM stack and b) the help of some kind souls in hooking everything up. Hans-Petter Selasky has already been very helpful with the USB part in private mail, and I actually wanted to solicit more help on the networking side of things privately in order not to trumpet out something which I'll probably finish only after considerable time, but reading the removal message I felt that I needed to make my needs public. Regards, Martin p.s. A few :-) of the questions I have are - why the original (as I understand HARP) ATM stack was removed (in the CVS logs the reason cited is the usual giant lock issue of that time), - what the differences between the atm and natm stacks are (as I understand the latter only supports a subset of the functionality of the former - only AAL5?), - why AF_NATM is different from AF_ATM (hinting that NATM is not a replacement of ATM), - whether and how it is even possible to inject raw ATM cells, - whether I even need "options NATM" (currently I can happily instantiate a (of course non-functional) ATM interface using just "device atm"), - what do I need to do on the USB side to start receive and transmit machines (do I need to start separate kernel threads or just issue two usbd_transfer_setup() calls as for loading the firmware), - etc. etc. I do of course read the source, but with the scarce documentation available that's a steep learning curve. p.p.s. Message re-sent from freebsd-atm because up till now I was not subscribed to freebsd-net. -- Martin Birgmeier Vienna Austria From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 20:31:07 2011 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 02019106564A for ; Sat, 19 Feb 2011 20:31:07 +0000 (UTC) (envelope-from la5lbtyi@aon.at) Received: from email.aon.at (smtpout05.highway.telekom.at [195.3.96.77]) by mx1.freebsd.org (Postfix) with ESMTP id 8ADF18FC08 for ; Sat, 19 Feb 2011 20:31:06 +0000 (UTC) Received: (qmail 25464 invoked from network); 19 Feb 2011 20:31:04 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL604 X-Spam-Level: Received: from 178-191-94-218.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([178.191.94.218]) (envelope-sender ) by smarthub98.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 19 Feb 2011 20:31:04 -0000 Received: from atpcdvvc.xyzzy (atpcdvvc.xyzzy [IPv6:fec0:0:0:4d42::84]) by gandalf.xyzzy (8.14.4/8.14.4) with ESMTP id p1JKV3uM043568 for ; Sat, 19 Feb 2011 21:31:04 +0100 (CET) (envelope-from la5lbtyi@aon.at) Message-ID: <4D602887.8010204@aon.at> Date: Sat, 19 Feb 2011 21:31:03 +0100 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.16) Gecko/20101219 Thunderbird/3.0.11 MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Locking in ng_tty.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 20:31:07 -0000 In ng_tty.c, function ngt_newhook(), there is the following code: if (sc->hook) return (EISCONN); NGTLOCK(sc); sc->hook = hook; NGTUNLOCK(sc); I do not think this is proper - should not the test be within the lock? Regards, Martin -- Martin Birgmeier Vienna Austria From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 21:31:49 2011 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 9F4971065672 for ; Sat, 19 Feb 2011 21:31:49 +0000 (UTC) (envelope-from k@kevinkevin.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6E89E8FC13 for ; Sat, 19 Feb 2011 21:31:49 +0000 (UTC) Received: by iwn39 with SMTP id 39so4897823iwn.13 for ; Sat, 19 Feb 2011 13:31:48 -0800 (PST) Received: by 10.42.239.136 with SMTP id kw8mr2748811icb.502.1298151108679; Sat, 19 Feb 2011 13:31:48 -0800 (PST) Received: from kkPC (not.enough.unixsluts.com [76.10.166.187]) by mx.google.com with ESMTPS id 8sm3225763iba.10.2011.02.19.13.31.45 (version=SSLv3 cipher=OTHER); Sat, 19 Feb 2011 13:31:47 -0800 (PST) From: "kevin" To: "'Tom Judge'" References: <000c01cbcf94$35e76e20$a1b64a60$@com> <4D5FAC16.7080207@gmx.com> <00a201cbd03f$2bdc3540$83949fc0$@com> <4D5FD91F.20704@gmx.com> <4D5FDCF1.6050909@gmx.com> <00a501cbd04f$2276b5b0$67642110$@com> <4D5FFE9C.30005@tomjudge.com> In-Reply-To: <4D5FFE9C.30005@tomjudge.com> Date: Sat, 19 Feb 2011 16:31:26 -0500 Message-ID: <00c901cbd07c$5ec03cd0$1c40b670$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: AcvQWvebJ/t04wk6Qr+mKJ8/6bZOlgAIO5oA Cc: freebsd-net@freebsd.org, 'Nikos Vassiliadis' Subject: RE: Bridging + VLANS + RSTP / MSTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 21:31:49 -0000 >There is a also the caveat: The switch will probably _not_ forward the STP BPDU's from one port to another. This is because if the switch is a properly >compliant bridge it will not forwards the frames as they are marked as link local ethernet multicast frame which is not allowed to forwarded by a bridge >per the ethernet spec. If this is indeed the case you will make an instant forwarding loop in your network when you try to make it work. >From the user manual of my switch, I have the following options to set for BPDU handling : BPDU Handling - Determines how BPDU packets are managed when STP is disabled on the port device. BPDUs are used to transmit spanning tree information. The possible field values are:\ - Filtering - Filters BPDU packets when spanning tree is disabled on an interface. - Flooding - Floods BPDU packets when spanning tree is disabled on an interface. This is the default value. I believe the 'flooding' option will blood BPDU packets to all ports on the switch device. Is that something that would forward the STP BPDU's from the disabled ports you think? Implementing another switch isn't really an option right now so if I cannot get this to work with my existing equiptment I will have to redesign the network without bridging , unfortunately (pf + carp + pfsense + multiple gateways). Thanks, Kevin From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 21:58:33 2011 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 2A0B91065673 for ; Sat, 19 Feb 2011 21:58:33 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id CF04E8FC19 for ; Sat, 19 Feb 2011 21:58:32 +0000 (UTC) Received: by vxa40 with SMTP id 40so2739867vxa.13 for ; Sat, 19 Feb 2011 13:58:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=vTU2Vb1pTfxMhcvGZlPOGLMGnPd8tvqKHiZz6EAz6l4=; b=eOBnV+77SqkuXOlcnqMyDUEYA/huTLCIds+IaBhqCfwWGmlnI1apqXhi0cZMedu2J3 XSNcOSVvgVpgnfpukFBeLpTdKkPJZoDlmExfeWEL/3ZY9f3TVlLwgxfk6XIbKeSf2b2Y JiF0t2TBZhl1pn5EAsSwtuZ3aG7Az6+DRZq0Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=dJk4g7oCN6XQiTq1WXrOtcdZebDyf4BuuldlyBtt6oz5o554Ftbn9eelZkJwPgqZpj pRfOYPxjNedF5Hcd1zs4SDbZ/DXucMA3gNjIdEpxZ/bmawESmHhLAFM/O1gDJO8Jzc4i ripWC0z6ah3lNCCqQ9QgHpQ6ZiKmGRudnoCwg= Received: by 10.52.169.168 with SMTP id af8mr3692840vdc.133.1298152711273; Sat, 19 Feb 2011 13:58:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.57.140 with HTTP; Sat, 19 Feb 2011 13:58:11 -0800 (PST) In-Reply-To: References: From: "Paul B. Mahol" Date: Sat, 19 Feb 2011 22:58:11 +0100 Message-ID: To: grarpamp Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: bwi vs. bwn X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2011 21:58:33 -0000 On Fri, Feb 18, 2011 at 11:26 PM, grarpamp wrote: >>> Doesn't FreeBSD have some sort of ndiswrapper function for this? >>> http://www.broadcom.com/support/802.11/linux_sta.php >> NDISulator, ndis(4). > > Hmm, maybe that only applies to the Windows driver bundles as > distributed by the vendors (Dell, HP, Lenovo, etc). Or from Microsoft > itself as part of the OS. And not to this Linux thing. You need inf and sys file(s), Windows drivers. Everything is explained in documentation. From owner-freebsd-net@FreeBSD.ORG Sat Feb 19 22:43:53 2011 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 2B9921065702; Sat, 19 Feb 2011 22:43:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E8DA18FC12; Sat, 19 Feb 2011 22:43:52 +0000 (UTC) Received: by pwj8 with SMTP id 8so297080pwj.13 for ; Sat, 19 Feb 2011 14:43:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=OxRdyR5aMoKzJrEBKqxIdrv+olu+gYIv6kZn2Kj0NCA=; b=k8qpxXMto/t+/9ccYfoaRo70/ed9VGGFLK4rCE2fgJv7aKEPqHvkCCebbjcKyWSYbF 4mHZk2kp7OcK8EtJ8vlxQsrQXvaIKBJhk6r0EVxeV2uLbHezsFWOO8k5Qwm4CUXfFnou WBydXAOH3Nn+SVV4vIbMwaBtg+c2Q33eWCkeU= 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=AXScOhI3U9ndxGcDxuxuYWRHTOwU61vtpJwr2Ft9QOvkCbPVi1xZLqv7myM1DqTTBZ O29R/hwWcq/nkH7Kj7P1GoRYmrTqG6ITZwZSKX+xO6N4jv/XzoMjqGzHPio0Oth/g64W HGk6/kaq1+bvwsxf9LkxP6Cdd1+u/HPQdMoWo= Received: by 10.142.126.14 with SMTP id y14mr1777649wfc.322.1298155431926; Sat, 19 Feb 2011 14:43:51 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id w11sm5047323wfh.18.2011.02.19.14.43.48 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 Feb 2011 14:43:49 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sat, 19 Feb 2011 14:44:01 -0800 From: Pyun YongHyeon Date: Sat, 19 Feb 2011 14:44:01 -0800 To: Steven Hartland Message-ID: <20110219224401.GA28005@michelle.cdnetworks.com> References: <2FA20352DEB643BEA7EAB90A14346894@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2FA20352DEB643BEA7EAB90A14346894@multiplay.co.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: bge0 watchdog timeout -- resetting on 8.2-PREREL never recovers 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: Sat, 19 Feb 2011 22:43:53 -0000 On Sat, Feb 19, 2011 at 03:59:57PM -0000, Steven Hartland wrote: > This may be totally unrelated to bge, investigating a potential failing > stick > of ram in the machine in question so until we've ruled this out as the cause > don't want to waste anyone's time. > > I did however notice the logic between the two fixes for DMA on 5704's on > PCIX > in svn differ so wondering which ones correct:- > http://svn.freebsd.org/viewvc/base/head/sys/dev/bge/if_bge.c?r1=216085&r2=216970 > http://svn.freebsd.org/viewvc/base/head/sys/dev/bge/if_bge.c?r1=217225&r2=217226 > > r216970 results in: > 1, 0, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, > where as r217226 results in: > 1, BGE_DMA_BNDRY, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, > I think it would be same for your case(BCM5704 PCI-X). However r217226 would be better one to address the issue. Actually I didn't like the workaround but there was no much time left to fix it for upcoming 8.2/7.4.