From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 00:38:15 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C54416A400; Sun, 11 Feb 2007 00:38:15 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 6BE7313C48D; Sun, 11 Feb 2007 00:38:15 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout3.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l1B0c3M4041937; Sat, 10 Feb 2007 16:38:03 -0800 (PST) Date: Sat, 10 Feb 2007 16:37:54 -0800 Message-ID: From: gnn@freebsd.org To: Christian Brueffer In-Reply-To: <20070209110745.GB1686@haakonia.hitnet.RWTH-Aachen.DE> References: <20070209110745.GB1686@haakonia.hitnet.RWTH-Aachen.DE> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.92 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: net@freebsd.org Subject: Re: Networking FreeBSD Wiki X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 00:38:15 -0000 At Fri, 09 Feb 2007 12:07:45 +0100, Christian Brueffer wrote: > > [1 ] > On Thu, Feb 08, 2007 at 05:07:31PM -0800, gnn@freebsd.org wrote: > > Hi, > > > > I've started a Wiki page in the FreeBSD Wiki in an attempt to > > coordinate some of the clean up work and networking projects that > > aren't already covered. Please see: > > > > http://wiki.freebsd.org/Networking > > > > and update (if you're a committer) or email me corrections etc. > > > > Some of the stuff seems to come from > http://www.freebsd.org/projects/dingo/ . > > Should we move all the entries to the wiki and simply nuke the dingo > page? Yes. Later, George From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 00:54:26 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E5CE316A403 for ; Sun, 11 Feb 2007 00:54:26 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id BF91713C428 for ; Sun, 11 Feb 2007 00:54:26 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 00FF228596; Sat, 10 Feb 2007 18:34:28 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 186CB61C3A; Sat, 10 Feb 2007 18:34:28 -0600 (CST) Date: Sat, 10 Feb 2007 18:34:27 -0600 From: "Matthew D. Fuller" To: Bruce M Simpson Message-ID: <20070211003427.GA59292@over-yonder.net> References: <45CE4DC9.4050605@incunabulum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45CE4DC9.4050605@incunabulum.net> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: net@FreeBSD.org Subject: Re: [PATCH] netstat(1) should print CIDR prefixes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 00:54:27 -0000 On Sat, Feb 10, 2007 at 10:57:13PM +0000 I heard the voice of Bruce M Simpson, and lo! it spake thus: > > This is a POLA violating 'let's move with the times' patch that gets > rid of the special treatment of classful IPv4 network prefixes in > 'netstat -rn' output. Comments please! Please! 1.2.3/24 is *wrong* when you're referring to 1.2.3.0/24 and not 1.2.0.3/24. Talking netstat out of giving me that wrong information is a Good Thing(tm). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 03:46:48 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6C73C16A406 for ; Sun, 11 Feb 2007 03:46:48 +0000 (UTC) (envelope-from gcorcoran@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2918E13C4A3 for ; Sun, 11 Feb 2007 03:46:47 +0000 (UTC) (envelope-from gcorcoran@rcn.com) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 10 Feb 2007 22:18:32 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id MXB25393; Sat, 10 Feb 2007 22:18:30 -0500 (EST) Received: from 207-172-55-230.c3-0.tlg-ubr5.atw-tlg.pa.cable.rcn.com (HELO [10.56.78.161]) ([207.172.55.230]) by smtp01.lnh.mail.rcn.net with ESMTP; 10 Feb 2007 22:18:28 -0500 Message-ID: <45CE8B96.3050008@rcn.com> Date: Sat, 10 Feb 2007 22:20:54 -0500 From: Gary Corcoran User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Bruce M Simpson References: <45CE4DC9.4050605@incunabulum.net> In-Reply-To: <45CE4DC9.4050605@incunabulum.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Status: score=10/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090206.45CE8B06.00A8,ss=1,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.125/2006-10-10 Cc: net@FreeBSD.org Subject: Re: [PATCH] netstat(1) should print CIDR prefixes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 03:46:48 -0000 Bruce M Simpson wrote: > Hi, > > This is a POLA violating 'let's move with the times' patch that gets rid > of the special treatment of classful IPv4 network prefixes in 'netstat > -rn' output. Comments please! Since those 'classes' haven't meant anything for many years, and interpreting them as 'special' is just plain wrong in almost all cases these days, I think the change is the right thing to do. Just my $0.02 worth... Gary From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 06:21:50 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C23C16A401; Sun, 11 Feb 2007 06:21:50 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 19C5313C47E; Sun, 11 Feb 2007 06:21:50 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id A2E061CC51; Sun, 11 Feb 2007 19:21:48 +1300 (NZDT) Date: Sun, 11 Feb 2007 19:21:48 +1300 From: Andrew Thompson To: "Bruce M. Simpson" Message-ID: <20070211062148.GA33021@heff.fud.org.nz> References: <45CDFA18.3030102@incunabulum.net> <45CE0ED9.1010905@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45CE0ED9.1010905@FreeBSD.org> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Part 2 of low level 802.1p priority support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 06:21:50 -0000 On Sat, Feb 10, 2007 at 06:28:41PM +0000, Bruce M. Simpson wrote: > This updated patch moves VLAN tag decapsulation into if_ethersubr.c and > always uses M_VLANTAG, which is also passed to the upper layer. > > Tests with ping: > fxp (no VLAN_HWTAGGING support) OK > msk (VLAN_HWTAGGING enabled) OK > msk (VLAN_HWTAGGING disanabled) FAIL > > I am concerned that this may need review and testing to support > situations where we do nested VLANs or with bridge(4) before it can be > committed. This is great for the bridge, it has needed to take the vlan tag into account when deciding to forward or not. Having m_pkthdr.ether_vtag always set makes this much easier to implement. > Index: if_vlan.c > =================================================================== > RCS file: /home/ncvs/src/sys/net/if_vlan.c,v > > - if (m->m_flags & M_VLANTAG) { > - /* > - * Packet is tagged, but m contains a normal > - * Ethernet frame; the tag is stored out-of-band. > - */ > - tag = EVL_VLANOFTAG(m->m_pkthdr.ether_vtag); > - m->m_flags &= ~M_VLANTAG; ^^^^^^^^^^^^^^^^^^^^^^^^ > - } else { ... > + tag = EVL_VLANOFTAG(m->m_pkthdr.ether_vtag); In the deleted code M_VLANTAG is cleared but is not done anymore, is this right? Andrew From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 07:31:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1116B16A400 for ; Sun, 11 Feb 2007 07:31:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id BE3EC13C442 for ; Sun, 11 Feb 2007 07:31:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id f47so651730pye for ; Sat, 10 Feb 2007 23:31:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=HU7U0XEpd0rCzOnQZBPpJ/MSbS048nFk+MpZLCgx02cc7Vi2cVYnWZZLYBFm7fsYIUSYHVr4O2Aw6jUybAASQmQ1QvCCTl/ClUolCyL5EU0lYUhP5mv86yWcvNCjZH48/azPlknz82vHOzNjaPiAS5guOdZHMbti/F4XV4EAdQg= Received: by 10.35.128.17 with SMTP id f17mr26995301pyn.1171179116157; Sat, 10 Feb 2007 23:31:56 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 37sm7663738nzf.2007.02.10.23.31.54; Sat, 10 Feb 2007 23:31:55 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l1B7XSII055792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Feb 2007 16:33:28 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l1B7XSVx055791; Sun, 11 Feb 2007 16:33:28 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sun, 11 Feb 2007 16:33:28 +0900 From: Pyun YongHyeon To: "Bruce M. Simpson" Message-ID: <20070211073328.GB55314@cdnetworks.co.kr> References: <45CDFA18.3030102@incunabulum.net> <45CE0ED9.1010905@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <45CE0ED9.1010905@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@FreeBSD.org Subject: Re: [PATCH] Part 2 of low level 802.1p priority support 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: Sun, 11 Feb 2007 07:31:57 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Feb 10, 2007 at 06:28:41PM +0000, Bruce M. Simpson wrote: > This updated patch moves VLAN tag decapsulation into if_ethersubr.c and > always uses M_VLANTAG, which is also passed to the upper layer. > > Tests with ping: > fxp (no VLAN_HWTAGGING support) OK > msk (VLAN_HWTAGGING enabled) OK > msk (VLAN_HWTAGGING disanabled) FAIL > > I am concerned that this may need review and testing to support > situations where we do nested VLANs or with bridge(4) before it can be > committed. > > Further testing with drivers is needed (I can't be 100% sure it fails > with msk(4) because something strange is happening when vlan tagging is > turned off). Perhaps Pyun knows? > I guess I've not merged local changes before committing to HEAD. How about attached one? > Regards, > BMS > > -- Regards, Pyun YongHyeon --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_msk.vlan.patch" Index: if_msk.c =================================================================== RCS file: /home/ncvs/src/sys/dev/msk/if_msk.c,v retrieving revision 1.8 diff -u -r1.8 if_msk.c --- if_msk.c 9 Jan 2007 01:31:22 -0000 1.8 +++ if_msk.c 11 Feb 2007 07:26:08 -0000 @@ -3029,7 +3029,8 @@ cons = sc_if->msk_cdata.msk_rx_cons; do { rxlen = status >> 16; - if ((status & GMR_FS_VLAN) != 0) + if ((status & GMR_FS_VLAN) != 0 && + (ifp->if_capenable & IFCAP_VLAN_HWTAGGING) != 0) rxlen -= ETHER_VLAN_ENCAP_LEN; if (len > sc_if->msk_framesize || ((status & GMR_FS_ANY_ERR) != 0) || --2oS5YaxWCcQjTEyO-- From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 13:56:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F2B216A401; Sun, 11 Feb 2007 13:56:10 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 30EB713C474; Sun, 11 Feb 2007 13:56:10 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 0EF0E1AA29B; Sun, 11 Feb 2007 08:56:08 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Sun, 11 Feb 2007 08:56:08 -0500 X-Sasl-enc: I3KE1qwZsxpTxlLur0gCD0fgKAVWjGpxXJda9ldv+w2h 1171202167 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 861169409; Sun, 11 Feb 2007 08:56:07 -0500 (EST) Message-ID: <45CF2077.1060106@FreeBSD.org> Date: Sun, 11 Feb 2007 13:56:07 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Andrew Thompson References: <45CDFA18.3030102@incunabulum.net> <45CE0ED9.1010905@FreeBSD.org> <20070211062148.GA33021@heff.fud.org.nz> In-Reply-To: <20070211062148.GA33021@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Part 2 of low level 802.1p priority support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 13:56:10 -0000 Andrew Thompson wrote: > This is great for the bridge, it has needed to take the vlan tag into > account when deciding to forward or not. Having m_pkthdr.ether_vtag > always set makes this much easier to implement. > > In the deleted code M_VLANTAG is cleared but is not done anymore, is > this right? > Correct. The vlan(4) code as it currently stands consumes M_VLANTAG (though as its allocation has been moved into the mbuf header itself, there is no additional free needed -- it's not a deep allocation). The patch moves the M_VLANTAG handling into ether_demux() (it should probably move further down to ether_input()) and always sets M_VLANTAG if we got raw 802.1q frames from the NIC (!(ifcap & VLAN_HWTAG) situation), so that we can deal with VLAN 0 in a clean way in ether_demux(). This may be a slight pessimization, but we always knew that cards which don't deal with 802.1q in hardware cause a performance hit anyway -- this just means that they will at least be able to process packet priorities! M_VLANTAG then may be passed to upper layers, providing they either ignore its presence or do something useful with it. In the case of ALTQ we'd examine the priority field in the 802.1q tag to map Layer 2 Quality of Service to ALTQ rules. These changes really need to be considered together with M_PROMISC. NetBSD did this presumably to stop the madness we have in ether_demux() to deal with the situation of stacked software Ethernet devices (vlan, bridge, agr, etc); M_PROMISC gets set for frames coming in off the card which we wouldn't have received had we not been in IFF_PROMISC. 'I am a hub, not a switch'. It's not smart enough to drop M_MCASTs we didn't ask for, it will blindly tag those also. Both of these changes use mbuf flags, not tags, because tags have a higher cost. M_PROMISC is also used in NetBSD to stop the IP forwarding paths seeing promiscuous traffic. Throw a wi(4) PRISM2 card into a laptop and set up OSPF+DVMRP on the same FreeBSD kernel and you'll see what I mean. We have checks in our code which only deal with that if there's a vlan(4) configured on top of your NIC... BMS From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 16:25:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF6D616A406; Sun, 11 Feb 2007 16:24:59 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.freebsd.org (Postfix) with ESMTP id B01B913C4A7; Sun, 11 Feb 2007 16:24:59 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (t050096.ppp.asahi-net.or.jp [203.189.50.96]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4F3597301D; Mon, 12 Feb 2007 01:25:04 +0900 (JST) Date: Mon, 12 Feb 2007 01:24:49 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Dimitry Andric In-Reply-To: <45CCF3ED.1090704@andric.com> References: <20070120162936.GA18104@tomcat.kitchenlab.org> <20070121.020741.59649277.hrs@allbsd.org> <45B251A5.4000209@freebsd.org> <45B3CA56.4040106@andric.com> <45B421D4.2050008@freebsd.org> <45B48F0C.9090809@andric.com> <45B63C3E.9010808@freebsd.org> <45B676A2.5090009@andric.com> <45CBD32E.40005@freebsd.org> <45CCF3ED.1090704@andric.com> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: "Bruce A. Mah" , freebsd-stable@freebsd.org, jhay@freebsd.org, freebsd-net@freebsd.org Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 16:25:00 -0000 >>>>> On Fri, 09 Feb 2007 23:21:33 +0100, >>>>> Dimitry Andric said: > Bruce A. Mah wrote: >> I've convinced myself that this problem needs to be tested in isolation >> (i.e. you have complete control over both ends of the tunnel) because >> incoming packets over the tunnel cause the host route to get added >> automatically if it wasn't there already. >> >> After reading the code and discussing this with a couple folks, I've >> managed to convince myself that 1.48.2.14 and 1.48.2.15 (and their >> analogues on HEAD) need to go away. I've committed diffs that back >> these out, and they solve the problem for me in my testing (which I've >> done with two VMs in isolation). The applicable revisions for nd6.c are >> 1.74 (HEAD) and 1.48.2.18 (RELENG_6). Updating up to (or beyond) these >> revisions should clear up the problem. > Confirmed. I've updated the machine on which I originally had this > problem to -STABLE as of today, and the problem has disappeared. I thought it was also planned to be incorporated to RELENG_6_2, right? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 17:56:59 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CA1516A400 for ; Sun, 11 Feb 2007 17:56:59 +0000 (UTC) (envelope-from slawek.zak@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id C188913C471 for ; Sun, 11 Feb 2007 17:56:58 +0000 (UTC) (envelope-from slawek.zak@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so301744ugh for ; Sun, 11 Feb 2007 09:56:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=fzNz4H8PYLTJ1MaBCk+/beM7H22tu4TRlQ5u/vmSDSYlsVSMF13AM/ak9dlQYy2a4+rOWS5E2NL3fm+Wc+tvmOyX0zNYeIZwPTQWZPGHy3uyQoyw77x4bF3PzC85zARDGCuZn2gGdyg/pjVewFfgYaqMJS0tWOZ35a5ztUEMx3E= Received: by 10.114.194.1 with SMTP id r1mr5515505waf.1171216615952; Sun, 11 Feb 2007 09:56:55 -0800 (PST) Received: by 10.114.15.16 with HTTP; Sun, 11 Feb 2007 09:56:55 -0800 (PST) Message-ID: <787bbe1c0702110956j5c247638v711b45d87040b48b@mail.gmail.com> Date: Sun, 11 Feb 2007 18:56:55 +0100 From: "Slawek Zak" To: freebsd-net@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <787bbe1c0701310827o9b84b33q1322007bf68f4f8a@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_29668_8561517.1171216615743" References: <787bbe1c0701310827o9b84b33q1322007bf68f4f8a@mail.gmail.com> Cc: Subject: Re: Forcing 1000FD for bce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 17:56:59 -0000 ------=_Part_29668_8561517.1171216615743 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline T24gMS8zMS8wNywgU2xhd2VrIFphayA8c2xhd2VrLnpha0BnbWFpbC5jb20+IHdyb3RlOgo+IEkg aGF2ZSBhIHF1ZXN0aW9uIGZvciBzb21lb25lIGZhbWlsaWFyIHdpdGggdGhpcyBkcml2ZXIuIEkg bXVzdAo+IGVuZm9yY2UgR2IvRnVsbC1kdXBsZXggYmVmb3JlIHRoZSBlbmQgb2YgYm9vdC4gSSBo YXZlIElCTSBCbGFkZUNlbnRlcgo+IGNoYXNzaXMgd2hpY2ggaW50ZXJuYWxseSB1c2VzIE5vcnRl bCAyLTMgc3dpdGNoZXMgd2hpY2ggaW4gdHVybiBkbyBub3QKPiBhbGxvdyBmb3IgYXV0b25lZ290 aWF0aW9uIG9mIGludGVybmFsIGludGVyZmFjZXMuCj4KPiBJIHdhbnQgdG8gcnVuIGEgZGlza2xl c3MgY29uZmlndXJhdGlvbiBzbyBjaGFuZ2luZyB0aGUgYml0cyB3aXRoCj4gaWZjb25maWcgaXMg bm90IGFuIG9wdGlvbi4gVHdlYWtpbmcgc2V0dGluZ3MgaW4gUFhFIGJvb3QgYWdlbnQgZG9lc24n dAo+IGhlbHAgLSB0aGUgbGluayBwcmVmZXJlbmNlIGlzIG5vdCBwcmVzZXJ2ZWQgYWZ0ZXIga2Vy bmVsIHN0YXJ0cwo+IGJvb3RpbmcuCgpJJ3ZlIGltcGxlbWVudGVkIGEgaGFsZi1iYWtlZCBzb2x1 dGlvbiBqdXN0IHRvIG1ha2UgdGhlIGRhcm4gdGhpbmcKd29yay4gQXNzdW1pbmcgeW91IGhhdmUg Z2VudGJpIFBIWSAoY2hlY2sgdGhlIGRtZXNnKSwgdGhlIGZvbGxvd2luZwpwYXRjaCByZW1vdmVz IGF1dG8gbmVnb3RpYXRpb24gYW5kIGhhbGYtZHVwbGV4IGhhbmRsaW5nIGZvciBTWAppbnRlcmZh Y2UsIHRodXMgbGVhdmluZyAxMDAwRkQgb25seS4gVGVzdGVkIG9uIElCTSBMUzIxIGJsYWRlcy4g RW5qb3kuCgovUwotLSAKU7Nhd2VrIK9hayAvIFVOSVggU3lzdGVtcyBBZG1pbmlzdHJhdG9yCg== ------=_Part_29668_8561517.1171216615743 Content-Type: application/octet-stream; name="gentbi.c.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gentbi.c.diff" X-Attachment-Id: f_ey1s4beo KioqIHN5cy9kZXYvbWlpL2dlbnRiaS5jLm9yaWcgICBGcmkgSmFuIDI2IDE4OjA2OjAyIDIwMDcN Ci0tLSBzeXMvZGV2L21paS9nZW50YmkuYyAgICAgICAgU3VuIEZlYiAxMSAxODo1MToyOSAyMDA3 DQoqKioqKioqKioqKioqKioNCioqKiAxOTMsMjAxICoqKioNCiAgICAgICAgICogaW4gImF1dG8i Lg0KICAgICAgICAgKi8NCiAgICAgICAgc2MtPm1paV9jYXBhYmlsaXRpZXMgPQ0KISAgICAgICAg ICAgUEhZX1JFQUQoc2MsIE1JSV9CTVNSKSAmIG1hLT5taWlfY2FwbWFzayAmIH5CTVNSX01FRElB TUFTSzsNCiAgICAgICAgaWYgKHNjLT5taWlfY2FwYWJpbGl0aWVzICYgQk1TUl9FWFRTVEFUKQ0K ISAgICAgICAgICAgICAgIHNjLT5taWlfZXh0Y2FwYWJpbGl0aWVzID0gUEhZX1JFQUQoc2MsIE1J SV9FWFRTUik7DQoNCiAgICAgICAgZGV2aWNlX3ByaW50ZihkZXYsICIgIik7DQogICAgICAgIG1p aV9waHlfYWRkX21lZGlhKHNjKTsNCi0tLSAxOTMsMjAxIC0tLS0NCiAgICAgICAgICogaW4gImF1 dG8iLg0KICAgICAgICAgKi8NCiAgICAgICAgc2MtPm1paV9jYXBhYmlsaXRpZXMgPQ0KISAgICAg ICAgICAgUEhZX1JFQUQoc2MsIE1JSV9CTVNSKSAmIG1hLT5taWlfY2FwbWFzayAmIH5CTVNSX01F RElBTUFTSyAmIH5CTVNSX0FORUc7DQogICAgICAgIGlmIChzYy0+bWlpX2NhcGFiaWxpdGllcyAm IEJNU1JfRVhUU1RBVCkNCiEgICAgICAgICAgICAgICBzYy0+bWlpX2V4dGNhcGFiaWxpdGllcyA9 IEVYVFNSXzEwMDBYRkRYOw0KDQogICAgICAgIGRldmljZV9wcmludGYoZGV2LCAiICIpOw0KICAg ICAgICBtaWlfcGh5X2FkZF9tZWRpYShzYyk7DQoNCg== ------=_Part_29668_8561517.1171216615743-- From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 18:29:30 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DDC4516A400; Sun, 11 Feb 2007 18:29:30 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (tensor.andric.com [213.154.244.69]) by mx1.freebsd.org (Postfix) with ESMTP id 9887513C481; Sun, 11 Feb 2007 18:29:30 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [192.168.0.3] (kilgore.lan.dim [192.168.0.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTP id 3165CB80E; Sun, 11 Feb 2007 19:29:27 +0100 (CET) Message-ID: <45CF6089.3040700@andric.com> Date: Sun, 11 Feb 2007 19:29:29 +0100 From: Dimitry Andric User-Agent: Thunderbird 2.0pre (Windows/20070210) MIME-Version: 1.0 To: =?UTF-8?B?SklOTUVJIFRhdHV5YSAvIOelnuaYjumBlOWTiQ==?= References: <20070120162936.GA18104@tomcat.kitchenlab.org> <20070121.020741.59649277.hrs@allbsd.org> <45B251A5.4000209@freebsd.org> <45B3CA56.4040106@andric.com> <45B421D4.2050008@freebsd.org> <45B48F0C.9090809@andric.com> <45B63C3E.9010808@freebsd.org> <45B676A2.5090009@andric.com> <45CBD32E.40005@freebsd.org> <45CCF3ED.1090704@andric.com> In-Reply-To: X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "Bruce A. Mah" , freebsd-stable@freebsd.org, jhay@freebsd.org, freebsd-net@freebsd.org Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 18:29:31 -0000 JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote: >> Confirmed. I've updated the machine on which I originally had this >> problem to -STABLE as of today, and the problem has disappeared. >=20 > I thought it was also planned to be incorporated to RELENG_6_2, right? I'm not sure if non-security related fixes are considered for release branches. Also, there's a workaround mentioned on the 6.2 errata page, under "Known Issues": http://www.freebsd.org/releases/6.2R/errata.html Then again, it's really up to the release engineering team whether they deem this critical enough. :) From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 20:25:09 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5117E16A402; Sun, 11 Feb 2007 20:25:09 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.freebsd.org (Postfix) with ESMTP id 321CE13C471; Sun, 11 Feb 2007 20:25:09 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from [192.168.2.119] (hornet.kitchenlab.org [64.142.31.105]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id l1BKP5jx011847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Feb 2007 12:25:05 -0800 Message-ID: <45CF7B91.7040700@freebsd.org> Date: Sun, 11 Feb 2007 12:24:49 -0800 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Dimitry Andric References: <20070120162936.GA18104@tomcat.kitchenlab.org> <20070121.020741.59649277.hrs@allbsd.org> <45B251A5.4000209@freebsd.org> <45B3CA56.4040106@andric.com> <45B421D4.2050008@freebsd.org> <45B48F0C.9090809@andric.com> <45B63C3E.9010808@freebsd.org> <45B676A2.5090009@andric.com> <45CBD32E.40005@freebsd.org> <45CCF3ED.1090704@andric.com> <45CF6089.3040700@andric.com> In-Reply-To: <45CF6089.3040700@andric.com> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA56D3B9F9968A334C512B1C6" Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, jhay@freebsd.org, =?UTF-8?B?SklOTUVJIFRhdHV5YSAvIOelnuaYjumBlOWTiQ==?= Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Feb 2007 20:25:09 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA56D3B9F9968A334C512B1C6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable If memory serves me right, Dimitry Andric wrote: > JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote: >>> Confirmed. I've updated the machine on which I originally had this >>> problem to -STABLE as of today, and the problem has disappeared. >> I thought it was also planned to be incorporated to RELENG_6_2, right?= >=20 > I'm not sure if non-security related fixes are considered for release > branches. Also, there's a workaround mentioned on the 6.2 errata page,= > under "Known Issues": Yes, we do this (most releases nowadays have at least a couple of errata notices / patches). > http://www.freebsd.org/releases/6.2R/errata.html >=20 > Then again, it's really up to the release engineering team whether they= > deem this critical enough. :) Its a joint decision between re@ and so@. I *am* on re@, and I'd planned on getting this change into RELENG_6_2, but I'm seriously ENOTIME (now trying to type one-handed with my sleeping two-week-old son in the other hand). I'll send a copy of this to re@, hopefully one of us will do this. Cheers, Bruce. --------------enigA56D3B9F9968A334C512B1C6 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.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFz3uY2MoxcVugUsMRAj/GAJ9RHeu9C40zdGoiyXRlG0d3C8H7NQCgzH01 Pj9z8P0M4P6HOTz+QQ3dDug= =Ut+q -----END PGP SIGNATURE----- --------------enigA56D3B9F9968A334C512B1C6-- From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 09:30:22 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6737316A4E1 for ; Mon, 12 Feb 2007 09:30:22 +0000 (UTC) (envelope-from sebosik@demax.sk) Received: from mail.demax.sk (mail.demax.sk [213.215.102.234]) by mx1.freebsd.org (Postfix) with ESMTP id 25D2613C48D for ; Mon, 12 Feb 2007 09:30:22 +0000 (UTC) (envelope-from sebosik@demax.sk) Received: from mail.demax.sk (localhost [127.0.0.1]) by nod32.demax.sk (Postfix) with ESMTP id 877DC42ACB for ; Mon, 12 Feb 2007 10:30:20 +0100 (CET) X-Virus-Scanner: This message was checked by NOD32 Antivirus system NOD32 for Linux Mail Server. For more information on NOD32 Antivirus System, please, visit our website: http://www.nod32.com/. Received: from sql.demax.sk (sql.demax.sk [213.215.102.236]) by mail.demax.sk (Postfix) with ESMTP id 636D142AC7 for ; Mon, 12 Feb 2007 10:30:20 +0100 (CET) Received: from 158.193.139.178 (SquirrelMail authenticated user sebosik) by webmail.demax.sk with HTTP; Mon, 12 Feb 2007 10:30:20 +0100 (CET) Message-ID: <1433.158.193.139.178.1171272620.squirrel@webmail.demax.sk> Date: Mon, 12 Feb 2007 10:30:20 +0100 (CET) From: sebosik@demax.sk To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Priority: 1 (Highest) Importance: High Subject: Configuring rendevous point X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 09:30:22 -0000 Hi all situation: got freebsd box working as NAT for my local network. In kernel config there is an option PIM. I want my hosts behind NAT to receive multicast streams. I`ve seen in Debian in pimdd.conf undocumented option rp_address, which stands for rendevous point IP address (http://ftp.debian.org/debian/pool/main/p/pimd/pimd_2.1.0-alpha29.17-6.diff.gz). Is there any way to specify rendevous point in freebsd via pimd.conf or mrouted ? Best regards --- Jan Sebosik sebosik@demax.sk From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 11:04:06 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50A0416A408 for ; Mon, 12 Feb 2007 11:04:06 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id D201513C48E for ; Mon, 12 Feb 2007 11:04:05 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20728444; Mon, 12 Feb 2007 13:04:04 +0200 Message-ID: <45D049A3.2030907@alkar.net> Date: Mon, 12 Feb 2007 13:04:03 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: mpd-users@lists.sourceforge.net, FreeBSD Net Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 11:04:06 -0000 I am glad to present you the first stable release of mpd4.x branch - the mpd4.1! It has almost a two years passed since last stable release of mpd3.18 and I must say that this time wasn't spent useless. Comparing to the 3.18, release 4.1 presents: - performance multithreading auth backend, - IPv6 support, - L2TP link type, - working TCP and UDP link types, - NetFlow, - NAT, - new Telnet console, - WEB interface, - Deflate and Predictor-1 traffic compression, - DESE-bis traffic encryption, - _HUGE_ amount of bug fixes, refactoring cases and performance optimizations. Considering above, the mpd3.x branch is announced as legacy and will not be anymore supported and updated. All mpd users are strongly recommended to upgrade to the latest 4.x release. Complete change log of MPD4 branch you can find here: http://mpd.sourceforge.net/doc/mpd5.html You can download mpd in source form here: http://sourceforge.net/project/showfiles.php?group_id=14145 , or install it via FreeBSD ports system. -- Alexander Motin mav@alkar.net From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 11:10:39 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C96DE16A4A7 for ; Mon, 12 Feb 2007 11:10:39 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B83FF13C4A8 for ; Mon, 12 Feb 2007 11:10:39 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1CBAdhP098690 for ; Mon, 12 Feb 2007 11:10:39 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1CBAb3Z098686 for freebsd-net@FreeBSD.org; Mon, 12 Feb 2007 11:10:37 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Feb 2007 11:10:37 GMT Message-Id: <200702121110.l1CBAb3Z098686@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2007 11:10:39 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue o kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/95665 net [if_tun] "ping: sendto: No buffer space available" wit o kern/106722 net [net] [patch] ifconfig may not connect an interface to o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL 6 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19875 net A new protocol family, PF_IPOPTION, to handle IP optio o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/95267 net packet drops periodically appear f kern/95277 net [netinet] IP Encapsulation mask_match() returns wrong o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n 9 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 11:57:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9688B16A407 for ; Mon, 12 Feb 2007 11:57:32 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.234]) by mx1.freebsd.org (Postfix) with ESMTP id 2B03C13C4A6 for ; Mon, 12 Feb 2007 11:57:31 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by hu-out-0506.google.com with SMTP id 38so2110927huc for ; Mon, 12 Feb 2007 03:57:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=NBzdin1LmLEYImQWU4NbRi2JZhYASURmSx5YPAchZKrkGYvrDSNACvT12WYflAbgubF7ZLD09VkCBflkwualIuajDdusUu9yhO3PHxI3T76Dk7RgSWg92r1PwwwqxaXdEFENnov2HZ4UBUQm7sXLQmpRWV11N3Q5kfix9+FjlWc= Received: by 10.78.158.11 with SMTP id g11mr301584hue.1171279836454; Mon, 12 Feb 2007 03:30:36 -0800 (PST) Received: by 10.78.164.20 with HTTP; Mon, 12 Feb 2007 03:30:36 -0800 (PST) Message-ID: Date: Mon, 12 Feb 2007 14:30:36 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Alexander Motin" In-Reply-To: <45D049A3.2030907@alkar.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45D049A3.2030907@alkar.net> X-Google-Sender-Auth: 9e2e62de33af166f Cc: FreeBSD Net , mpd-users@lists.sourceforge.net Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 11:57:32 -0000 On 2/12/07, Alexander Motin wrote: > I am glad to present you the first stable release of mpd4.x > branch - the mpd4.1! You can't imagine how much your effort is appreciated! We'll be looking at mpd4.1 this or next week during the FreeBSD course at specialist.ru. It really seems you've done a lot to shorten the learning curve while giving a boost to functionality. Thanks! From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 10:17:02 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9548A16A47F for ; Mon, 12 Feb 2007 10:17:02 +0000 (UTC) (envelope-from korkodinov@ertelecom.ru) Received: from smtp.ertelecom.ru (smtp.ertelecom.ru [212.33.232.210]) by mx1.freebsd.org (Postfix) with ESMTP id 96FE213C4EF for ; Mon, 12 Feb 2007 10:17:01 +0000 (UTC) (envelope-from korkodinov@ertelecom.ru) Received: from office.ertelecom.ru ([212.33.232.253]:64053 helo=mx1.ertelecom.ru) by smtp.ertelecom.ru with esmtp (Exim) id 1HGXnv-000PG0-3k for ; Mon, 12 Feb 2007 14:48:59 +0500 MIME-Version: 1.0 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Mon, 12 Feb 2007 14:48:23 +0500 Message-ID: <838DB0534DD36F4EAF4793C7EC83DDFF21EC94@er-mail.hq> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: i386/108963: kernel panic on swi:net Thread-Index: AcdMODa1z//0V+teScyT+vGVmpJLVACUJ/EQ From: =?koi8-r?B?68/Sy8/Eyc7P1yD3zMHEyc3J0iD3zMHEydPMwdfP18ne?= To: X-Mailman-Approved-At: Mon, 12 Feb 2007 12:37:35 +0000 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FW: i386/108963: kernel panic on swi:net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 10:17:02 -0000 Dear mailinglist members, =20 Maybe somebody can look at this PR? http://www.freebsd.org/cgi/query-pr.cgi?pr=3D108963&cat=3D As I see we have NULL pointer in m_copydata. Why it happened? =20 Are there any suggestions that could assist in solving this problem? =20 P.S. I have similar problem when using ipnat with ftp_proxy on 6.1R and = 6.2R Thanks, Vladimir =9A =20 -----Original Message----- From: owner-freebsd-i386@freebsd.org = [mailto:owner-freebsd-i386@freebsd.org] On Behalf Of Denis Sent: Friday, February 09, 2007 3:47 PM To: freebsd-gnats-submit@FreeBSD.org Subject: i386/108963: kernel panic on swi:net =20 =20 >Number:=9A=9A=9A=9A=9A=9A=9A=9A 108963 >Category:=9A=9A=9A=9A=9A=9A i386 >Synopsis:=9A=9A=9A=9A=9A=9A kernel panic on swi:net >Confidential:=9A=9A no >Severity:=9A=9A=9A=9A=9A=9A serious >Priority:=9A=9A=9A=9A=9A=9A high >Responsible:=9A=9A=9A freebsd-i386 >State:=9A=9A=9A=9A=9A=9A=9A=9A=9A open >Quarter:=9A=9A=9A=9A=9A=9A=9A=20 >Keywords:=9A=9A=9A=9A=9A=9A=20 >Date-Required: >Class:=9A=9A=9A=9A=9A=9A=9A=9A=9A sw-bug >Submitter-Id:=9A=9A current-users >Arrival-Date:=9A=9A Fri Feb 09 10:50:10 GMT 2007 >Closed-Date: >Last-Modified: >Originator:=9A=9A=9A=9A Denis >Release:=9A=9A=9A=9A=9A=9A=9A 6.2-PRERELEASE CVSUpped from 6.1 RELEASE = on Feb 6 >Organization: ISP MainStream >Environment: FreeBSD main.nikopol.net 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #29: Wed = Feb=9A 7 10:55:22 EET 2007=9A=9A=9A=9A = den@main.nikopol.net:/usr/src/sys/i386/compile/MS=9A i386 >Description: Server is using MPD authorization, ipnat address translation; serves = proxy, sendmail, popa3d, BIND and MySQL daemons. Problem begin to appear in 6.1-RELEASE with same error and after CVSup = to 6.2-PRERELEASE on Feb, 6 problem doesn't solved. =20 Server is running on single core AMD Athlon 3500+, have two Intel = Gigabit NIC's (em) and one Intel 100Mbit NIC (fxp). =20 =20 Below I paste core debug information. =20 =20 Fatal trap 12: page fault while in kernel mode fault virtual address=9A=9A =3D 0xc fault code=9A=9A=9A=9A=9A=9A=9A=9A =9A=9A=9A=9A=9A=3D supervisor read, = page not present instruction pointer=9A=9A=9A=9A =3D 0x20:0xc055b4cc stack pointer=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A =3D 0x28:0xe4faaa20 frame pointer=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A =3D 0x28:0xe4faaa2c code segment=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A =3D base 0x0, limit = 0xfffff, type 0x1b =9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A = =3D DPL 0, pres 1, def32 1, gran 1 processor eflags=9A=9A=9A=9A=9A=9A=9A =3D interrupt enabled, resume, = IOPL =3D 0 current process=9A=9A=9A=9A=9A=9A=9A=9A =3D 13 (swi1: net) trap number=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A =3D 12 panic: page fault Uptime: 9h24m41s Dumping 2046 MB (2 chunks) =9A chunk 0: 1MB (159 pages) ... ok =9A chunk 1: 2046MB (523760 pages) 2030 2014 1998 1982 1966 1950 1934 = 1918 1902 1886 1870 1854 1838 1822 1 806 1790 1774 1758 1742 1726 1710 1694 1678 1662 1646 1630 1614 1598 = 1582 1566 1550 1534 1518 1502 1486 1470 1454 1438 1422 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262 = 1246 1230 1214 1198 1182 1166 1150 =9A1134 1118 1102 1086 1070 1054 1038 1022 1006 990 974 958 942 926 910 = 894 878 862 846 830 814 798 782 76 6 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 = 478 462 446 430 414 398 382 366 35 0 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 = 46 30 14 =20 #0=9A doadump () at pcpu.h:165 165=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A __asm __volatile("movl = %%fs:0,%0" : "=3Dr" (td)); (kgdb) list *0xc055b4cc 0xc055b4cc is in m_copydata (libkern.h:56). 51=9A=9A=9A=9A=9A static __inline int imax(int a, int b) { return (a > b = ? a : b); } 52=9A=9A=9A=9A=9A static __inline int imin(int a, int b) { return (a < b = ? a : b); } 53=9A=9A=9A=9A=9A static __inline long lmax(long a, long b) { return (a = > b ? a : b); } 54=9A=9A=9A=9A=9A static __inline long lmin(long a, long b) { return (a = < b ? a : b); } 55=9A=9A=9A=9A=9A static __inline u_int max(u_int a, u_int b) { return = (a > b ? a : b); } 56=9A=9A=9A=9A=9A static __inline u_int min(u_int a, u_int b) { return = (a < b ? a : b); } 57=9A=9A=9A=9A=9A static __inline quad_t qmax(quad_t a, quad_t b) { = return (a > b ? a : b); } 58=9A=9A=9A=9A=9A static __inline quad_t qmin(quad_t a, quad_t b) { = return (a < b ? a : b); } 59=9A=9A=9A=9A=9A static __inline u_long ulmax(u_long a, u_long b) { = return (a > b ? a : b); } 60=9A=9A=9A=9A=9A static __inline u_long ulmin(u_long a, u_long b) { = return (a < b ? a : b); } (kgdb) bt #0=9A doadump () at pcpu.h:165 #1=9A 0xc0529c56 in boot (howto=3D260) at = ../../../kern/kern_shutdown.c:409 #2=9A 0xc0529f1c in panic (fmt=3D0xc06824a6 "%s") at = ../../../kern/kern_shutdown.c:565 #3=9A 0xc065bd26 in trap_fatal (frame=3D0xe4faa9e0, eva=3D12) at = ../../../i386/i386/trap.c:837 #4=9A 0xc065ba57 in trap_pfault (frame=3D0xe4faa9e0, usermode=3D0, = eva=3D12) at ../../../i386/i386/trap.c:745 #5=9A 0xc065b671 in trap (frame=3D =9A=9A=9A=9A=9A {tf_fs =3D 8, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D 1, = tf_esi =3D 0, tf_ebp =3D -453334484, tf_isp =3D -4533345 16, tf_ebx =3D -891044160, tf_edx =3D 0, tf_ecx =3D -891044192, tf_eax = =3D 120, tf_trapno =3D 12, tf_err =3D 0, tf_e ip =3D -1068124980, tf_cs =3D 32, tf_eflags =3D 590338, tf_esp =3D = -891044160, tf_ss =3D -891044147}) =9A=9A=9A at ../../../i386/i386/trap.c:435 #6=9A 0xc064a5ea in calltrap () at ../../../i386/i386/exception.s:139 #7=9A 0xc055b4cc in m_copydata (m=3D0x0, off=3D0, len=3D1, =9A=9A=9A cp=3D0xcae3becd "complete.\r\n227 Entering Passive Mode = (212,119,184,110,138,178).\r\n200 PORT command =9Asuccessful\r\n221 Goodbye.\rЗ\003") at = ../../../kern/uipc_mbuf.c:543 #8=9A 0xc044cd32 in ippr_ftp_process (fin=3D0xe4faab6c, = nat=3D0xc744ac00, ftp=3D0xcae3be00, rv=3D1) =9A=9A=9A at ip_ftp_pxy.c:1192 #9=9A 0xc044d076 in ippr_ftp_in (fin=3D0xe4faab6c, aps=3D0x78, = nat=3D0xc744ac00) at ip_ftp_pxy.c:1358 #10 0xc045180d in appr_check (fin=3D0xe4faab6c, nat=3D0xc744ac00) =9A=9A=9A at ../../../contrib/ipfilter/netinet/ip_proxy.c:540 #11 0xc044a559 in fr_natin (fin=3D0xe4faab6c, nat=3D0xc744ac00, = natadd=3D1, nflags=3D1) =9A=9A=9A at ../../../contrib/ipfilter/netinet/ip_nat.c:4105 #12 0xc044a42e in fr_checknatin (fin=3D0xe4faab6c, passp=3D0xe4faab68) =9A=9A=9A at ../../../contrib/ipfilter/netinet/ip_nat.c:4040 #13 0xc043e705 in fr_check (ip=3D0xc7300030, hlen=3D20, ifp=3D0x78, = out=3D0, mp=3D0xe4faac54) =9A=9A=9A at ../../../contrib/ipfilter/netinet/fil.c:2466 #14 0xc0442af2 in fr_check_wrapper (arg=3D0x0, mp=3D0x0, = ifp=3D0xc64a9800, dir=3D1) =9A=9A=9A at ../../../contrib/ipfilter/netinet/ip_fil_freebsd.c:171 #15 0xc059b4b3 in pfil_run_hooks (ph=3D0xc07003e0, mp=3D0xe4faaca8, = ifp=3D0xc64a9800, dir=3D1, inp=3D0x0) =9A=9A=9A at ../../../net/pfil.c:139 #16 0xc05c4bdf in ip_input (m=3D0xc95a7300) at = ../../../netinet/ip_input.c:468 #17 0xc059a053 in netisr_processqueue (ni=3D0xc06ff398) at = ../../../net/netisr.c:236 #18 0xc059a24e in swi_net (dummy=3D0x0) at ../../../net/netisr.c:349 #19 0xc0515c05 in ithread_execute_handlers (p=3D0xc6384648, = ie=3D0xc63ea100) =9A=9A=9A at ../../../kern/kern_intr.c:682 #20 0xc0515d10 in ithread_loop (arg=3D0xc636e6f0) at = ../../../kern/kern_intr.c:765 #21 0xc0514bb4 in fork_exit (callout=3D0xc0515cbc , = arg=3D0xc636e6f0, frame=3D0xe4faad38) =9A=9A=9A at ../../../kern/kern_fork.c:821 #22 0xc064a64c in fork_trampoline () at = ../../../i386/i386/exception.s:208 >How-To-Repeat: Problem appear in random, so I have no clue what exactly results panic. >Fix: =20 >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ freebsd-i386@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-i386 To unsubscribe, send any mail to "freebsd-i386-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 13:15:20 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BA4616A407 for ; Mon, 12 Feb 2007 13:15:20 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 637AF13C4AC for ; Mon, 12 Feb 2007 13:15:20 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 3FEE51ABDF0; Mon, 12 Feb 2007 08:15:18 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Mon, 12 Feb 2007 08:15:18 -0500 X-Sasl-enc: U7asvandqHwqHx1bzYLf41cf3GQVhsAZaGpIYL2YF5Gt 1171286117 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id BFBE92A840; Mon, 12 Feb 2007 08:15:17 -0500 (EST) Message-ID: <45D06866.4020009@FreeBSD.org> Date: Mon, 12 Feb 2007 13:15:18 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: sebosik@demax.sk References: <1433.158.193.139.178.1171272620.squirrel@webmail.demax.sk> In-Reply-To: <1433.158.193.139.178.1171272620.squirrel@webmail.demax.sk> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Configuring rendevous point X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 13:15:20 -0000 sebosik@demax.sk wrote: > Hi all > > situation: got freebsd box working as NAT for my local network. In kernel > config there is an option PIM. > FYI, PIM is now the default in -CURRENT; the option has been removed. You should be able to load multicast routing with PIM as a loadable kernel module in -CURRENT. > I want my hosts behind NAT to receive multicast streams. I`ve seen in > Debian in pimdd.conf undocumented option rp_address, which stands for > rendevous point IP address > (http://ftp.debian.org/debian/pool/main/p/pimd/pimd_2.1.0-alpha29.17-6.diff.gz). > PIM-DM (Dense mode) does not use the Rendezvous Point. > Is there any way to specify rendevous point in freebsd via pimd.conf or > mrouted ? Try XORP, in ports/net/xorp; it supports PIM-SM (Sparse mode) which is probably what you want for this kind of network configuration. Normally the RP for a given group or set of groups is discovered using the Auto-RP feature of PIM-SM however, they may be statically configured; see the 'static-rps {}' configuration block in XORP's PIM-SM. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 13:27:27 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60A2B16A401 for ; Mon, 12 Feb 2007 13:27:27 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 38A2513C428 for ; Mon, 12 Feb 2007 13:27:27 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 1D5401ABE9E for ; Mon, 12 Feb 2007 08:27:25 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Mon, 12 Feb 2007 08:27:25 -0500 X-Sasl-enc: DQpjODtdf54zG5ARs3I792LcitTK3QHfNLPGybe4H5OB 1171286844 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id B49D811363 for ; Mon, 12 Feb 2007 08:27:24 -0500 (EST) Message-ID: <45D06B3D.8010807@incunabulum.net> Date: Mon, 12 Feb 2007 13:27:25 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org References: <45CE4DC9.4050605@incunabulum.net> <45CE8B96.3050008@rcn.com> In-Reply-To: <45CE8B96.3050008@rcn.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: [PATCH] netstat(1) should print CIDR prefixes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 13:27:27 -0000 Gary Corcoran wrote: > > Since those 'classes' haven't meant anything for many years, and > interpreting > them as 'special' is just plain wrong in almost all cases these days, > I think > the change is the right thing to do. I've had +3. Any objections? If I hear none I will make this change in -CURRENT; with a note in UPDATING. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 15:37:15 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F9C816A409 for ; Mon, 12 Feb 2007 15:37:15 +0000 (UTC) (envelope-from fernando@gont.com.ar) Received: from smtp1.xmundo.net (smtp1.xmundo.net [201.216.232.80]) by mx1.freebsd.org (Postfix) with ESMTP id D28A913C481 for ; Mon, 12 Feb 2007 15:37:14 +0000 (UTC) (envelope-from fernando@gont.com.ar) Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56]) by smtp1.xmundo.net (Postfix) with ESMTP id 727A6F0C45D for ; Mon, 12 Feb 2007 12:16:19 -0300 (ART) Received: from fgont.gont.com.ar (3-176-231-201.fibertel.com.ar [201.231.176.3]) (authenticated bits=0) by venus.xmundo.net (8.12.11.20060308/8.12.11) with ESMTP id l1CFGHMX002994 for ; Mon, 12 Feb 2007 12:16:18 -0300 Message-Id: <200702121516.l1CFGHMX002994@venus.xmundo.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 12 Feb 2007 12:16:12 -0300 To: freebsd-net@freebsd.org From: Fernando Gont Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (venus.xmundo.net [201.216.232.56]); Mon, 12 Feb 2007 12:16:18 -0300 (ART) Subject: Ephemeral port selection X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 15:37:15 -0000 Folks, Looking at FreeBSD's TCP implementation, I see that by default, ephemeral ports are selected from the range 49152-65535. This means that only 15K ports out of the available 65K port range are used for ephemeral port selection. This has at least two implications: * Ephemeral ports are easier to predict (as you are picking them from a smaller range) * There is a higher chance of facing the interoperability problems described in Mike Silbersack's presentation at EuroBSDCon 2005 (http://www.silby.com/eurobsdcon05/eurobsdcon_silbersack.pdf). A first and small proposal would be to change the range of ephemeral port numbers to use the range 1024-65535. An array of bits could be maintained in memory to avoid the selection of ports that are used for services (e.g., X). We have also been working on an alternative port randomization scheme, that would help to avoid the problems described in Mike's presentation. Our work on the subject is available at: http://www.gont.com.ar/drafts/port-randomization/draft-larsen-tsvwg-port-randomization-01.txt We would be willing to provide patches for these things if there is interest in implementing the proposed changes (extending the port range and possibly implementing the RFC1948-like scheme for ephemeral port selection). Any comments will be more than welcome. Thanks, -- Fernando Gont e-mail: fernando@gont.com.ar || fgont@acm.org PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 18:42:05 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E27116A469 for ; Mon, 12 Feb 2007 18:42:05 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5EC13C4B6 for ; Mon, 12 Feb 2007 18:42:05 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay5.apple.com (a17-128-113-35.apple.com [17.128.113.35]) by mail-out3.apple.com (8.13.8/8.13.8) with ESMTP id l1CIg5Tw001356; Mon, 12 Feb 2007 10:42:05 -0800 (PST) Received: from relay5.apple.com (unknown [127.0.0.1]) by relay5.apple.com (Symantec Mail Security) with ESMTP id 5A18929C004; Mon, 12 Feb 2007 10:42:05 -0800 (PST) X-AuditID: 11807123-9fbb8bb000000a1d-64-45d0b4fd2d06 In-Reply-To: <200702121516.l1CFGHMX002994@venus.xmundo.net> References: <200702121516.l1CFGHMX002994@venus.xmundo.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1A3700B3-A649-419C-A5A4-FE181DE2D682@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Mon, 12 Feb 2007 10:42:00 -0800 To: Fernando Gont X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-net@freebsd.org Subject: Re: Ephemeral port selection X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Feb 2007 18:42:05 -0000 On Feb 12, 2007, at 7:16 AM, Fernando Gont wrote: > Looking at FreeBSD's TCP implementation, I see that by default, > ephemeral ports are selected from the range 49152-65535. This means > that only 15K ports out of the available 65K port range are used > for ephemeral port selection. You can change the following sysctl's: net.inet.ip.portrange.first: 49152 net.inet.ip.portrange.last: 65535 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 ...to adjust the range of ephemeral port #'s. I assume you're familiar with the IANA document on port # ranges here: http://www.iana.org/assignments/port-numbers It's likely to be the case that you could use a larger range (starting from 32K or even 10K) without bothering anything significant, but it's not really apparent to me that doubling or tripling the range of the available ephemeral ports is going to help significantly except for unusual cases. How many machines really need to have more than 15K open connections outstanding and where the other parts of the connection tuple (srcIP, srcPort, dstIP, dstPort) do not vary? > We have also been working on an alternative port randomization > scheme, that would help to avoid the problems described in Mike's > presentation. A better mechanism for allocating random ephemeral ports would certainly be valuable. -- -Chuck From owner-freebsd-net@FreeBSD.ORG Mon Feb 12 21:25:21 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5B8D16A4CC for ; Mon, 12 Feb 2007 21:25:21 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.223.87]) by mx1.freebsd.org (Postfix) with ESMTP id DAF9B13C491 for ; Mon, 12 Feb 2007 21:25:20 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from 156-102-124-91.pool.ukrtel.net ([91.124.102.156]:6663 "EHLO 156-102-124-91.pool.ukrtel.net" smtp-auth: "kes-kes" TLS-CIPHER: TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S2078336AbXBLVCb (ORCPT ); Tue, 13 Feb 2007 00:02:31 +0300 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: kes-kes Date: Mon, 12 Feb 2007 23:02:23 +0200 From: KES X-Mailer: The Bat! (v3.62.12) Professional Organization: SaftTen X-Priority: 3 (Normal) Message-ID: <1033847930.20070212230223@yandex.ru> To: freebsd-net@freebsd.org In-Reply-To: <200702121516.l1CFGHMX002994@venus.xmundo.net> References: <200702121516.l1CFGHMX002994@venus.xmundo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: ng_dummy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: KES List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2007 21:25:21 -0000 Hello, all Where I can get last version of ng_dummy? ___________ Konkov E.S. From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 07:15:59 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 382AB16A4A0; Tue, 13 Feb 2007 07:15:59 +0000 (UTC) (envelope-from t-momose@kame.net) Received: from doller.momose.org (203.141.155.85.static.zoot.jp [203.141.155.85]) by mx1.freebsd.org (Postfix) with ESMTP id C493613C442; Tue, 13 Feb 2007 07:15:58 +0000 (UTC) (envelope-from t-momose@kame.net) Received: from [192.168.1.129] (p1180-ipv6dual01hon.tokyo.ocn.ne.jp [221.113.184.180]) (authenticated bits=0) by doller.momose.org (8.13.8/8.13.8) with ESMTP id l1D75PBc024842; Tue, 13 Feb 2007 16:05:25 +0900 (JST) (envelope-from t-momose@kame.net) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-2022-JP; delsp=yes; format=flowed Message-Id: <9ABB7D86-5E75-46A2-AF8A-B834A1EC0DD2@kame.net> Content-Transfer-Encoding: 7bit From: Tsuyoshi MOMOSE Date: Tue, 13 Feb 2007 16:05:15 +0900 To: "George Neville-Neil V." , net@freebsd.org X-Mailer: Apple Mail (2.752.3) Cc: Momose Tsuyoshi Subject: Re: Networking FreeBSD Wiki X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 07:15:59 -0000 George, On 2007/02/09, at 10:07, gnn@freebsd.org wrote: > Hi, > > I've started a Wiki page in the FreeBSD Wiki in an attempt to > coordinate some of the clean up work and networking projects that > aren't already covered. Please see: > > http://wiki.freebsd.org/Networking > > and update (if you're a committer) or email me corrections etc. We, SHISA development team who is a part of KAME project and develops RFC3775/3963 compliant Mobile IPv6/NEMO stack for BSDs, are going to start to port to freebsd-current our code. Current SHISA works on FreeBSD 5.4 in kame snap. More information about SHISA is available on http://www.mobileip.jp/ We hope it to merge the FreeBSD. Is it possible to put our project to the wiki ? ---------------------------- Tsuyoshi MOMOSE / $B$b$b$;$D$h$7(B momose@momose.org http://www.momose.org/ (Underconstruction) From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 09:03:13 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A95116A400 for ; Tue, 13 Feb 2007 09:03:13 +0000 (UTC) (envelope-from andriko.b@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.228]) by mx1.freebsd.org (Postfix) with ESMTP id 2DF2A13C494 for ; Tue, 13 Feb 2007 09:03:13 +0000 (UTC) (envelope-from andriko.b@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so2009893nzh for ; Tue, 13 Feb 2007 01:03:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=pAO2Z/vWIiRW+dwRhhEL2vKKKF56SCRlAPNVfLr8l4dVoz+k9/WCm1o1kEhfEq4p8lzIXH3GiJGcyQGKnOnadrOGSojqlMsMklZg73FRQCvYRWoQCnRRbHGYQr9HGltRcnoEw7XghOR8YFqhzn4Px4iSqoNIahV6K7TVJ54yaA0= Received: by 10.115.54.1 with SMTP id g1mr7450043wak.1171355731433; Tue, 13 Feb 2007 00:35:31 -0800 (PST) Received: by 10.114.130.8 with HTTP; Tue, 13 Feb 2007 00:35:31 -0800 (PST) Message-ID: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> Date: Tue, 13 Feb 2007 10:35:31 +0200 From: "Andrew Bliznak" To: mav@alkar.net MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-net@freebsd.org Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 09:03:13 -0000 Hi, > I am glad to present you the first stable release of mpd4.x branch - the > mpd4.1! Thank you very much, great software! I testing it now and have some bug reports... I have set netflow node option in mpd.conf to attach to existing ng_netflow node --- default: load psrv1 load psrv3 ... pppoe: ... set netflow node netflow set netflow export 172.16.2.35 9996 ... psrv1: new -n -i ng1 pppoe1 pppoe1 load pppoe psrv3: new -n -i ng2 pppoe2 pppoe2 load pppoe ... --- After loading I got: ngctl list There are 115 total nodes: ... Name: mpd45965-pppoe3-bpf Type: bpf ID: 000017ce Num hooks: 5 Name: mpd45965-pppoe3-vjc Type: vjc ID: 000017cd Num hooks: 4 Name: mpd45965-pppoe3 Type: ppp ID: 000017cc Num hooks: 7 Name: ng3 Type: iface ID: 000017cb Num hooks: 2 Name: mpd45965-pppoe3-so Type: socket ID: 000017ca Num hooks: 2 Name: Type: socket ID: 000017c9 Num hooks: 1 Name: mpd45965-mss Type: tcpmss ID: 000017c8 Num hooks: 40 Name: mpd45965-nfso Type: ksocket ID: 000017c7 Num hooks: 1 Name: mpd45965-nf Type: netflow ID: 000017c6 Num hooks: 3 Name: mpd45965-pppoe1-bpf Type: bpf ID: 000017c5 Num hooks: 5 Name: mpd45965-pppoe1-vjc Type: vjc ID: 000017c4 Num hooks: 4 Name: mpd45965-pppoe1 Type: ppp ID: 000017c3 Num hooks: 8 Name: ng1 Type: iface ID: 000017c2 Num hooks: 2 Name: mpd45965-pppoe1-so Type: socket ID: 000017c1 Num hooks: 2 Name: mpd43388-nfso Type: ksocket ID: 00001759 Num hooks: 1 Name: mpd43388-nf Type: netflow ID: 00001758 Num hooks: 1 Name: Type: ksocket ID: 000016e5 Num hooks: 1 Name: netflow Type: netflow ID: 000016e4 Num hooks: 5 Name: Type: pppoe ID: 00001691 Num hooks: 3 Name: ng0 Type: iface ID: 00001630 Num hooks: 0 Name: ng2 Type: iface ID: 00000013 Num hooks: 0 Name: vlan4 Type: ether ID: 0000000b Num hooks: 1 Name: rl0 Type: ether ID: 0000000a Num hooks: 2 First created bundle stay something special, it don't see gNetflowNodeName, but rest connected correctly. Later, variable gNetflowNodeName for first bundle is set and on shutdown mpd not cleaning corresponding nodes. You can see two nodes from pid 43388... From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 10:37:34 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F8D016A402 for ; Tue, 13 Feb 2007 10:37:34 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id C168613C471 for ; Tue, 13 Feb 2007 10:37:33 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20770100; Tue, 13 Feb 2007 12:37:32 +0200 Message-ID: <45D194EB.10008@alkar.net> Date: Tue, 13 Feb 2007 12:37:31 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: Andrew Bliznak References: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> In-Reply-To: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 10:37:34 -0000 Hi. Andrew Bliznak wrote: > I have set netflow node option in mpd.conf to attach to > existing ng_netflow node > --- > default: > load psrv1 > load psrv3 > ... > pppoe: > ... > set netflow node netflow > set netflow export 172.16.2.35 9996 > ... > psrv1: > new -n -i ng1 pppoe1 pppoe1 > load pppoe 'set netflow ...' options should be specified _before_ creation of any bundle which require it. Move 'set netflow ...' commands to the startup section. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 11:21:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E14116A407 for ; Tue, 13 Feb 2007 11:21:41 +0000 (UTC) (envelope-from andriko.b@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.234]) by mx1.freebsd.org (Postfix) with ESMTP id 2FB3013C49D for ; Tue, 13 Feb 2007 11:21:41 +0000 (UTC) (envelope-from andriko.b@gmail.com) Received: by wr-out-0506.google.com with SMTP id 69so2293964wra for ; Tue, 13 Feb 2007 03:21:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z+Dlf/4vryls43scYTEQ/T1ZoeJ6HGzwHNUbv6LowQhC6e9nUWEErdJ+9CarKREhI1MjChK10OaE3CJ+kSBleBmGv1AwnXRYCQaYEcNNzv+2kP599vXgS15HYoEct+H3d7onTZhxJj8m7eVtJgBqO/XtoBPoNhZu9f/euKZqfV8= Received: by 10.114.73.1 with SMTP id v1mr7482441waa.1171365700254; Tue, 13 Feb 2007 03:21:40 -0800 (PST) Received: by 10.114.130.8 with HTTP; Tue, 13 Feb 2007 03:21:40 -0800 (PST) Message-ID: <21be38170702130321t23345ce0pe298733be438d6b0@mail.gmail.com> Date: Tue, 13 Feb 2007 13:21:40 +0200 From: "Andrew Bliznak" To: "Alexander Motin" In-Reply-To: <45D194EB.10008@alkar.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> <45D194EB.10008@alkar.net> Cc: freebsd-net@freebsd.org Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 11:21:41 -0000 2007/2/13, Alexander Motin : > Hi. > > Andrew Bliznak wrote: > > I have set netflow node option in mpd.conf to attach to > > existing ng_netflow node > > --- > > default: > > load psrv1 > > load psrv3 > > ... > > pppoe: > > ... > > set netflow node netflow > > set netflow export 172.16.2.35 9996 > > ... > > psrv1: > > new -n -i ng1 pppoe1 pppoe1 > > load pppoe > > 'set netflow ...' options should be specified _before_ creation of any > bundle which require it. Move 'set netflow ...' commands to the startup > section. OK. This works. Thanks... One more questions. a) Device type l2tp (copy pppoe config with changed device type) produce INVARIANTS KASSERT in sys/netgraph/ng_l2tp.c on first packet from nearest cisco :( b) Now on exit not cleaned only three nodes: ... Name: Type: pppoe ID: 00001843 Num hooks: 1 Name: ng0 Type: iface ID: 00001630 Num hooks: 0 Name: ng2 Type: iface ID: 00000013 Num hooks: 0 ... pyvo# ngctl show \[00001843\]: Name: Type: pppoe ID: 00001843 Num hooks: 1 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- ethernet vlan4 ether 0000000b orphans > > -- > Alexander Motin mav@alkar.net > Optima Telecom > From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 11:25:04 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01A8D16A408; Tue, 13 Feb 2007 11:25:04 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id 8574A13C481; Tue, 13 Feb 2007 11:25:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.66.18.21] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1HGvmI3Goy-0004EA; Tue, 13 Feb 2007 12:24:57 +0100 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Tue, 13 Feb 2007 12:24:42 +0100 User-Agent: KMail/1.9.5 References: <9ABB7D86-5E75-46A2-AF8A-B834A1EC0DD2@kame.net> In-Reply-To: <9ABB7D86-5E75-46A2-AF8A-B834A1EC0DD2@kame.net> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3179845.c9KxFfVChf"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200702131224.50520.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 X-Provags-ID2: V01U2FsdGVkX1+OKGsPj+kkg6PqPz4lSCF3fb7Bf4cg/A1Q4iHjkRrDPbT9IMHrh15iel/zJPhJTa9V4Q9yp3xw5WJgnRYHzmUdec89CYtTDCRvSaqtqpbLPA== Cc: "George Neville-Neil V." , Tsuyoshi MOMOSE Subject: Re: Networking FreeBSD Wiki X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 11:25:04 -0000 --nextPart3179845.c9KxFfVChf Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 13 February 2007 08:05, Tsuyoshi MOMOSE wrote: > George, > > On 2007/02/09, at 10:07, gnn@freebsd.org wrote: > > Hi, > > > > I've started a Wiki page in the FreeBSD Wiki in an attempt to > > coordinate some of the clean up work and networking projects that > > aren't already covered. Please see: > > > > http://wiki.freebsd.org/Networking > > > > and update (if you're a committer) or email me corrections etc. > > We, SHISA development team who is a part of KAME project and develops > RFC3775/3963 compliant Mobile IPv6/NEMO stack for BSDs, are going to > start to port to freebsd-current our code. > Current SHISA works on FreeBSD 5.4 in kame snap. > More information about SHISA is available on http://www.mobileip.jp/ > > We hope it to merge the FreeBSD. > > Is it possible to put our project to the wiki ? Done. Added under "Long term projects". =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3179845.c9KxFfVChf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBF0aACXyyEoT62BG0RApQrAJ9EyfksVWSka5EdN7jyncaBoeymHwCeOnl4 nHyq2+oZj/gx0eZBx1AnnN8= =xkiL -----END PGP SIGNATURE----- --nextPart3179845.c9KxFfVChf-- From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 11:53:57 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C5B4916A400; Tue, 13 Feb 2007 11:53:57 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 180EF13C46B; Tue, 13 Feb 2007 11:53:56 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20772402; Tue, 13 Feb 2007 13:53:56 +0200 Message-ID: <45D1A6D3.8060301@alkar.net> Date: Tue, 13 Feb 2007 13:53:55 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: Andrew Bliznak References: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> <45D194EB.10008@alkar.net> <21be38170702130321t23345ce0pe298733be438d6b0@mail.gmail.com> In-Reply-To: <21be38170702130321t23345ce0pe298733be438d6b0@mail.gmail.com> Content-Type: multipart/mixed; boundary="------------050303050907060207080901" Cc: freebsd-net@freebsd.org Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 11:53:57 -0000 This is a multi-part message in MIME format. --------------050303050907060207080901 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Andrew Bliznak wrote: > One more questions. > a) Device type l2tp (copy pppoe config with changed device type) > produce INVARIANTS KASSERT in sys/netgraph/ng_l2tp.c on first packet > from nearest cisco :( I know about one KASSERT problem in ng_l2tp. I have already sent patches to the commiter and waiting for his reply. You can try patch from attachment. > b) Now on exit not cleaned only three nodes: > ... > Name: Type: pppoe ID: 00001843 Num hooks: 1 This is current normal behavior. It doesn't usually make any problems. > Name: ng0 Type: iface ID: 00001630 Num hooks: 0 > Name: ng2 Type: iface ID: 00000013 Num hooks: 0 This is strange. I think it can be result of using -i parameter at bundle creation. Try to not use it. -- Alexander Motin mav@alkar.net Optima Telecom --------------050303050907060207080901 Content-Type: text/plain; name="ng_l2tp.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ng_l2tp.c.patch" --- ng_l2tp.c.orig Sat Feb 10 06:58:03 2007 +++ ng_l2tp.c Sat Feb 10 06:58:00 2007 @@ -1121,6 +1121,10 @@ hpriv->stats.xmitPackets++; hpriv->stats.xmitOctets += m->m_pkthdr.len; + /* And the global one. */ + priv->stats.xmitPackets++; + priv->stats.xmitOctets += m->m_pkthdr.len; + /* Send packet */ NG_FWD_NEW_DATA(error, item, priv->lower, m); return (error); @@ -1398,12 +1402,13 @@ const priv_p priv = NG_NODE_PRIVATE(node); struct l2tp_seq *const seq = &priv->seq; - /* Sanity check */ - L2TP_SEQ_CHECK(seq); - /* If ack is still outstanding, send a ZLB */ - if (seq->xack != seq->nr) + if (seq->xack != seq->nr) { ng_l2tp_xmit_ctrl(priv, NULL, seq->ns); + /* If there was memory error, ignore it. + We must keep state consistent here. */ + seq->xack = seq->nr; + } /* Done */ L2TP_SEQ_CHECK(seq); @@ -1420,9 +1425,6 @@ struct l2tp_seq *const seq = &priv->seq; struct mbuf *m; u_int delay; - - /* Sanity check */ - L2TP_SEQ_CHECK(seq); /* Make sure peer's ack is still outstanding before doing anything */ if (seq->rack == seq->ns) --------------050303050907060207080901-- From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 12:59:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 142C816A401 for ; Tue, 13 Feb 2007 12:59:32 +0000 (UTC) (envelope-from andriko.b@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by mx1.freebsd.org (Postfix) with ESMTP id CBE5E13C4A6 for ; Tue, 13 Feb 2007 12:59:31 +0000 (UTC) (envelope-from andriko.b@gmail.com) Received: by wr-out-0506.google.com with SMTP id 69so2332083wra for ; Tue, 13 Feb 2007 04:59:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q4O0T6mlve/euXS4lsG6il5UZjZWevD/VD5+EPXrz4N59fYtHbQiCMUKY3GyBIl+wL43urzhOvRw5wyWxXyKtQMkXUpJ01GWjOVDmdbapjPo+1sErpNUfr0lRGVFXXJ0I+rrO61u0GQxaqW+eWd5ThXEpTJPdKb0AXohB0gBjpg= Received: by 10.114.192.1 with SMTP id p1mr6827538waf.1171371570762; Tue, 13 Feb 2007 04:59:30 -0800 (PST) Received: by 10.114.130.8 with HTTP; Tue, 13 Feb 2007 04:59:30 -0800 (PST) Message-ID: <21be38170702130459icefa374hcf813518b8ed6ed6@mail.gmail.com> Date: Tue, 13 Feb 2007 14:59:30 +0200 From: "Andrew Bliznak" To: "Alexander Motin" In-Reply-To: <45D1A6D3.8060301@alkar.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> <45D194EB.10008@alkar.net> <21be38170702130321t23345ce0pe298733be438d6b0@mail.gmail.com> <45D1A6D3.8060301@alkar.net> Cc: freebsd-net@freebsd.org Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 12:59:32 -0000 2007/2/13, Alexander Motin : > Andrew Bliznak wrote: > > One more questions. > > a) Device type l2tp (copy pppoe config with changed device type) > > produce INVARIANTS KASSERT in sys/netgraph/ng_l2tp.c on first packet > > from nearest cisco :( > > I know about one KASSERT problem in ng_l2tp. I have already sent patches > to the commiter and waiting for his reply. You can try patch from > attachment. Patch works, I now can connect cisco router without KASSERTs > > > b) Now on exit not cleaned only three nodes: > > ... > > Name: Type: pppoe ID: 00001843 Num hooks: 1 > > This is current normal behavior. It doesn't usually make any problems. OK > > > Name: ng0 Type: iface ID: 00001630 Num hooks: 0 > > Name: ng2 Type: iface ID: 00000013 Num hooks: 0 > > This is strange. I think it can be result of using -i parameter at > bundle creation. Try to not use it. This clear all issues for now. Thank you!!! > -- > Alexander Motin mav@alkar.net > Optima Telecom > From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 13:40:19 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CEF716A41F for ; Tue, 13 Feb 2007 13:40:19 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4D74213C474 for ; Tue, 13 Feb 2007 13:40:19 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 3BB151FFE82; Tue, 13 Feb 2007 14:40:17 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id DD3421FFE79; Tue, 13 Feb 2007 14:40:06 +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 11F0C444AFE; Tue, 13 Feb 2007 13:37:34 +0000 (UTC) Date: Tue, 13 Feb 2007 13:37:34 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Alexander Motin In-Reply-To: <45D1A6D3.8060301@alkar.net> Message-ID: <20070213133017.A47107@maildrop.int.zabbadoz.net> References: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> <45D194EB.10008@alkar.net> <21be38170702130321t23345ce0pe298733be438d6b0@mail.gmail.com> <45D1A6D3.8060301@alkar.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org, Andrew Bliznak Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 13:40:19 -0000 On Tue, 13 Feb 2007, Alexander Motin wrote: Hi, --- ng_l2tp.c.orig Sat Feb 10 06:58:03 2007 +++ ng_l2tp.c Sat Feb 10 06:58:00 2007 @@ -1121,6 +1121,10 @@ /* If ack is still outstanding, send a ZLB */ - if (seq->xack != seq->nr) + if (seq->xack != seq->nr) { ng_l2tp_xmit_ctrl(priv, NULL, seq->ns); + /* If there was memory error, ignore it. + We must keep state consistent here. */ + seq->xack = seq->nr; + } This change is not needed. ng_l2tp_xmit_ctrl() does this already. It's not a good idea to remove the L2TP_SEQ_CHECK()s. Been there years ago but seems I missed to get this fixed in the FreeBSD repo. The problem is in ng_l2tp_seq_check(). Fix it there. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 14:42:58 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E1D416A402 for ; Tue, 13 Feb 2007 14:42:58 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 8F44E13C471 for ; Tue, 13 Feb 2007 14:42:56 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20779764; Tue, 13 Feb 2007 16:42:55 +0200 Message-ID: <45D1CE6F.1050505@alkar.net> Date: Tue, 13 Feb 2007 16:42:55 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <21be38170702130035n4ee69773mddc07a2b674fb81a@mail.gmail.com> <45D194EB.10008@alkar.net> <21be38170702130321t23345ce0pe298733be438d6b0@mail.gmail.com> <45D1A6D3.8060301@alkar.net> <20070213133017.A47107@maildrop.int.zabbadoz.net> In-Reply-To: <20070213133017.A47107@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Andrew Bliznak Subject: Re: Mpd-4.1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 14:42:58 -0000 Bjoern A. Zeeb wrote: > --- ng_l2tp.c.orig Sat Feb 10 06:58:03 2007 > +++ ng_l2tp.c Sat Feb 10 06:58:00 2007 > @@ -1121,6 +1121,10 @@ > > /* If ack is still outstanding, send a ZLB */ > - if (seq->xack != seq->nr) > + if (seq->xack != seq->nr) { > ng_l2tp_xmit_ctrl(priv, NULL, seq->ns); > + /* If there was memory error, ignore it. > + We must keep state consistent here. */ > + seq->xack = seq->nr; > + } > > This change is not needed. ng_l2tp_xmit_ctrl() does this already. It does this usually. But in case of no free mbufs it does not. Usually it's ok. But in this case it will lead to assertion in next check. The other way is to schedule next timeout, but in lack of system resources it can be better to just skip this packet. > It's not a good idea to remove the L2TP_SEQ_CHECK()s. It is _incorrect_ to call it there. When ng_l2tp_seq_xack_timeout() called callout_pending() function will already return FALSE because of timeout already ended. But at this moment action is not actually done and seq->xack != seq->nr. This leads to KASSERT without any reason. > Been there years ago but seems I missed to get this fixed > in the FreeBSD repo. > The problem is in ng_l2tp_seq_check(). Fix it there. Problem is not there! ng_l2tp_seq_check() works correctly from it's point of view. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 16:43:12 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E9F716A400 for ; Tue, 13 Feb 2007 16:43:12 +0000 (UTC) (envelope-from katherrafi@hcl.in) Received: from gws04.hcl.in (gws04.mail.hcl.in [203.105.186.20]) by mx1.freebsd.org (Postfix) with ESMTP id B5E4E13C4A6 for ; Tue, 13 Feb 2007 16:43:06 +0000 (UTC) (envelope-from katherrafi@hcl.in) Received: from gws04.hcl.in (gws04 [10.249.64.135]) by localhost.hcl.in (Postfix) with ESMTP id A6838360013 for ; Tue, 13 Feb 2007 22:01:51 +0530 (IST) Received: from chn-egw02-out.corp.hcl.in (unknown [10.249.64.38])by gws04.hcl.in (Postfix) with ESMTP id 83C3A36000Ffor ; Tue, 13 Feb 2007 22:01:51 +0530 (IST) Received: from CHN-HCLT-EVS01.HCLT.CORP.HCL.IN ([10.101.26.14]) by chn-egw02-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Feb 2007 22:01:51 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 13 Feb 2007 22:01:33 +0530 Message-ID: <6B2C2CD6EB6A2743950CB51B60DEB946278EDA@CHN-HCLT-EVS01.HCLT.CORP.HCL.IN> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: "route add" how it behaves Thread-Index: AcdPjGyOIVR4SiyNQjqANbOXsWXtMg== From: "Kather Rafi -TLS,Chennai" To: X-OriginalArrivalTime: 13 Feb 2007 16:31:51.0226 (UTC) FILETIME=[76E7B1A0:01C74F8C] X-imss-version: 2.046 X-imss-result: Passed X-imss-scanInfo: M:T L:E SM:1 X-imss-tmaseResult: TT:1 TS:-10.4586 TC:1F TRN:57 TV:3.6.1039(14996.003) X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0 X-imss-settings: Baseline:2 C:2 M:2 S:2 R:2 (0.0000 0.0000) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: "route add" how it behaves X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 16:43:12 -0000 Hi all, I am new to FreeBSD. I want to know how the "route add " is working for the network routes and host routes in the case of with out specifying the gateway. In linux we can add like "route add -host 10.0.12.24 eth0" but in FreeBSD it should be like "route add -host 10.0.12.24 -iface fxp0" I want to know 1. how the flag -iface provides gateway to the route inside the kernel.? 2. If it does not provide the gateway address how it identifies the ifaddr inside the kernel (ie interface address for the particular interface)? =20 Thanks and Regards , Kather Rafi Ibrahim =20 =20 DISCLAIMER: ---------------------------------------------------------------------------= -------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and= intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its= affiliates. Any views or opinions presented in=20 this email are solely those of the author and may not necessarily reflect= the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,= distribution and / or publication of=20 this message without the prior written consent of the author of this e-mail= is strictly prohibited. If you have=20 received this email in error please delete it and notify the sender= immediately. Before opening any mail and=20 attachments please check them for viruses and defect. ---------------------------------------------------------------------------= -------------------------------------------- From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 16:51:55 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 742A616A406 for ; Tue, 13 Feb 2007 16:51:55 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout10-04.prod.mesa1.secureserver.net (smtpout10-04.prod.mesa1.secureserver.net [64.202.165.238]) by mx1.freebsd.org (Postfix) with SMTP id 44E5713C4B7 for ; Tue, 13 Feb 2007 16:51:55 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 7597 invoked from network); 13 Feb 2007 16:25:14 -0000 Received: from unknown (24.144.77.243) by smtpout10-04.prod.mesa1.secureserver.net (64.202.165.238) with ESMTP; 13 Feb 2007 16:25:14 -0000 Message-ID: <45D1E669.30402@seclark.us> Date: Tue, 13 Feb 2007 11:25:13 -0500 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 16:51:55 -0000 Hello List, We have a setup that looks like the following. pc <-ethernet-> freebsd 4.9 <-pppoe-> internet <-ethernet-> freebsd 6.1 on the freebsd box we have a gre tunnel with a mtu of 1420 feeding into a gif vpn tunnel with a mtu of 1280 ( I know this dumb but it the default value when you create a gif ) feeding into a tun0 with a mtu of 1492. What we see is the packet never makes it to the freebsd 6.1 system. if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the freebsd 4.9 system send back an icmp dest unreachable - fragmentation needed and DF bit set? $ sysctl -a | grep mtu net.inet.tcp.path_mtu_discovery: 1 Now if I change the mtu of the gre to 1412 everything works. Any insight would be appreciated. Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 17:27:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD35416A402 for ; Tue, 13 Feb 2007 17:27:11 +0000 (UTC) (envelope-from SRS0=fb6b8d794e804d17f72c3de114c3a2d5b0710768=245=es.net=dart@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id AF4A013C441 for ; Tue, 13 Feb 2007 17:27:11 +0000 (UTC) (envelope-from SRS0=fb6b8d794e804d17f72c3de114c3a2d5b0710768=245=es.net=dart@es.net) Received: from [198.128.1.31] (usul.es.net [198.128.1.31]) by postal1.es.net (Postal Node 1) with ASMTP (SSL) id STC57302; Tue, 13 Feb 2007 09:15:02 -0800 Message-ID: <45D1F216.1090708@es.net> Date: Tue, 13 Feb 2007 09:15:02 -0800 From: Eli Dart Organization: Energy Sciences Network User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <45D1E669.30402@seclark.us> In-Reply-To: <45D1E669.30402@seclark.us> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dart@es.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 17:27:11 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephen Clark wrote: > if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the > freebsd 4.9 system > send back an icmp dest unreachable - fragmentation needed and DF bit set? Are you blocking icmp with a firewall filter? --eli > $ sysctl -a | grep mtu > net.inet.tcp.path_mtu_discovery: 1 > > Now if I change the mtu of the gre to 1412 everything works. > > Any insight would be appreciated. > > Thanks, > Steve - -- Eli Dart Office: (510) 486-5629 ESnet Network Engineering Group Fax: (510) 486-6712 Lawrence Berkeley National Laboratory PGP Key fingerprint = C970 F8D3 CFDD 8FFF 5486 343A 2D31 4478 5F82 B2B3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD4DBQFF0fIWLTFEeF+CsrMRAig5AKDLp0PzYvaH93VZSfkiTMWorKCkBwCY6a78 qWtMMH4GdqHFac6frQjb7w== =06S0 -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 17:56:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 80C8816A400 for ; Tue, 13 Feb 2007 17:56:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF8313C478 for ; Tue, 13 Feb 2007 17:56:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id F05191AF33F; Tue, 13 Feb 2007 12:56:50 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Tue, 13 Feb 2007 12:56:50 -0500 X-Sasl-enc: CML+PEmeZ6wt/jqT4AXR2m/KmBcR4TN08r2ioFLxTiE1 1171389410 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 56D1B14AC7; Tue, 13 Feb 2007 12:56:49 -0500 (EST) Message-ID: <45D1FBE2.2050308@FreeBSD.org> Date: Tue, 13 Feb 2007 17:56:50 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: "Kather Rafi -TLS,Chennai" References: <6B2C2CD6EB6A2743950CB51B60DEB946278EDA@CHN-HCLT-EVS01.HCLT.CORP.HCL.IN> In-Reply-To: <6B2C2CD6EB6A2743950CB51B60DEB946278EDA@CHN-HCLT-EVS01.HCLT.CORP.HCL.IN> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: "route add" how it behaves X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Feb 2007 17:56:53 -0000 Kather Rafi -TLS,Chennai wrote: > Hi all, > > I am new to FreeBSD. > > I want to know how the "route add " is working for the network routes > and host routes in the case of with out specifying the gateway. > > In linux we can add like "route add -host 10.0.12.24 eth0" but in > FreeBSD it should be like "route add -host 10.0.12.24 -iface fxp0" > > I want to know > > 1. how the flag -iface provides gateway to the route inside > the kernel.? > > Watch the output of 'route -nv monitor' running in the background when you do it. > 2. If it does not provide the gateway address how it > identifies the ifaddr inside the kernel (ie interface address for the > particular interface)? > If you specify an interface as the next-hop, what you are doing is asking the link layer to resolve the next-hop. In the case of a PPP interface, it should just send the packet to the next hop (example: someone running PPP over RFCOMM with Bluetooth with Proxy-ARP to bridge the Bluetooth endpoint device onto a LAN). In the case of Ethernet (a CSMA/CD broadcast LAN which uses BSD's route-cloning facility), it should ARP for the address. The 'route' command actually manages the Forwarding Information Base (FIB) or 'forwarding table'. We just call it the 'routing table' though that is a misnomer. The Layer 2 entries ('ARP table') are also contained within the FreeBSD FIB. FreeBSD usually relies on an interface having an IPv4 number.The results for an unnumbered PPP interface, which is not bridging in the example above, may be undefined. In the case of Ethernet, it's quite possible that an entity on the directly attached LAN knows how to resolve the next-hop by doing Proxy ARP on its behalf. Hope this clarifies matters. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 18:19:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D715016A402 for ; Tue, 13 Feb 2007 18:19:00 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout05-04.prod.mesa1.secureserver.net (smtpout05-04.prod.mesa1.secureserver.net [64.202.165.221]) by mx1.freebsd.org (Postfix) with SMTP id BFB6E13C442 for ; Tue, 13 Feb 2007 18:19:00 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 9275 invoked from network); 13 Feb 2007 18:19:00 -0000 Received: from unknown (24.144.77.243) by smtpout05-04.prod.mesa1.secureserver.net (64.202.165.221) with ESMTP; 13 Feb 2007 18:19:00 -0000 Message-ID: <45D20113.1060403@seclark.us> Date: Tue, 13 Feb 2007 13:18:59 -0500 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dart@es.net References: <45D1E669.30402@seclark.us> <45D1F216.1090708@es.net> In-Reply-To: <45D1F216.1090708@es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 18:19:00 -0000 Eli Dart wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > > > >Stephen Clark wrote: > > > >>if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the >>freebsd 4.9 system >>send back an icmp dest unreachable - fragmentation needed and DF bit set? >> >> > >Are you blocking icmp with a firewall filter? > > --eli > > > Good question - but the answer is no. The other interesting fact is when I drop the mtu on the gre to 1412 I do see the icmp messages. >>$ sysctl -a | grep mtu >>net.inet.tcp.path_mtu_discovery: 1 >> >>Now if I change the mtu of the gre to 1412 everything works. >> >>Any insight would be appreciated. >> >>Thanks, >>Steve >> >> > >- -- >Eli Dart Office: (510) 486-5629 >ESnet Network Engineering Group Fax: (510) 486-6712 >Lawrence Berkeley National Laboratory >PGP Key fingerprint = C970 F8D3 CFDD 8FFF 5486 343A 2D31 4478 5F82 B2B3 >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.6 (FreeBSD) > >iD4DBQFF0fIWLTFEeF+CsrMRAig5AKDLp0PzYvaH93VZSfkiTMWorKCkBwCY6a78 >qWtMMH4GdqHFac6frQjb7w== >=06S0 >-----END PGP SIGNATURE----- >_______________________________________________ >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" > > > -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-net@FreeBSD.ORG Tue Feb 13 22:52:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B12316A46D for ; Tue, 13 Feb 2007 22:52:00 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 0780813C4A7 for ; Tue, 13 Feb 2007 22:51:59 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [195.248.178.122] (account mav@alkar.net HELO [192.168.3.2]) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20792488; Wed, 14 Feb 2007 00:51:58 +0200 Message-ID: <45D2410D.70509@alkar.net> Date: Wed, 14 Feb 2007 00:51:57 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <1171398196.00688135.1171386001@10.7.7.3> <1171398210.00688151.1171387801@10.7.7.3> <1171401795.00688172.1171391400@10.7.7.3> In-Reply-To: <1171401795.00688172.1171391400@10.7.7.3> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 22:52:00 -0000 Stephen Clark wrote: >>> if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the >>> freebsd 4.9 system >>> send back an icmp dest unreachable - fragmentation needed and DF bit >>> set? >> >> Are you blocking icmp with a firewall filter? >> > Good question - but the answer is no. The other interesting fact is > when I drop the mtu on > the gre to 1412 I do see the icmp messages. Are you using any dummynet shapes? There is ancient bug in dummynet, which leads to not sending of ICMPs when shape used on outgoing interface. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 07:55:14 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B59A216A400 for ; Wed, 14 Feb 2007 07:55:14 +0000 (UTC) (envelope-from tomas@tutus.se) Received: from fw-y.tutus.se (static-213-115-50-13.sme.bredbandsbolaget.se [213.115.50.13]) by mx1.freebsd.org (Postfix) with ESMTP id 4D40513C48E for ; Wed, 14 Feb 2007 07:55:13 +0000 (UTC) (envelope-from tomas@tutus.se) Received: from munin.tutus.se (munin.tutus.se [193.181.0.67]) by fw-y.tutus.se (omb_smtp 1.7) with ESMTP; (cipher=AES256-SHA from= verify=NO) Wed, 14 Feb 2007 08:55:45 +0100 (CET) Received: from [193.181.0.105] ([193.181.0.105]) by munin.tutus.se (8.13.6.20060614/8.13.6) with ESMTP id l1E7t8df090367 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 14 Feb 2007 08:55:09 +0100 (CET) Message-ID: <45D2C05D.7000707@tutus.se> Date: Wed, 14 Feb 2007 08:55:09 +0100 From: Tomas Svensson User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Julian Elischer References: <45CC686F.1050409@tutus.se> <45CCDF66.90505@elischer.org> In-Reply-To: <45CCDF66.90505@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: problem with ng_device as tun replacement X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2007 07:55:14 -0000 Julian Elischer wrote: > Tomas Svensson wrote: >> Hi, >> >> I am trying to replace the tun interface using netgraph by linking >> ng_device and ng_iface: >> >> ngctl mkpeer iface dummy inet >> ngctl mkpeer ng0: device inet inet >> >> then I try to use it as a drop-in replacement for tun, but it doesn't >> really work: >> >> 1. If I send an IP packet through /dev/ngd0 (after doing a normal >> open()), the packet doesn't get sent until I write a second packet to >> the device. > > Do you know it the ng-device device is hanging onto it, or the > ng_iface device is getting it but not passing it on? > > If you don't know, you can put a 'tee' node between them > and use nghook(8) to see when the packet is passed between the nodes. > Thanks, I checked with tee and nghook(8) and found the follwing two cases: 1. Packets are arriving from the ng_iface (ng0) via the hook to ng_device (dev/ngd0), but the packets are just queuing up and the descriptor that opened /dev/ngd0 is not marked as readable until there is a number of packets queued. 2. A packet first arrives on /dev/ngd0 and is sent via the hook to ng0. A response packet is later arriving on the interface and is sent back to the device via the hook. Now the packet is stuck. Yet another packet arrives on /dev/ngd0 which makes it let go of the first packet (the first packet is sent out /dev/ngd0 and the new packet is sent via the hook to ng0). I send normal ICMP echo packets and the code works fine with tun(4). -Tomas From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 08:55:34 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F32D16A408 for ; Wed, 14 Feb 2007 08:55:34 +0000 (UTC) (envelope-from Susan.Lan@zyxel.com.tw) Received: from zyadd226.zyxel.com.tw (59-124-182-147.HINET-IP.hinet.net [59.124.182.147]) by mx1.freebsd.org (Postfix) with ESMTP id 0422E13C481 for ; Wed, 14 Feb 2007 08:55:33 +0000 (UTC) (envelope-from Susan.Lan@zyxel.com.tw) Received: from zytwfe02.ZyXEL.com ([172.23.5.50]) by smtp.zyxel.com.tw with InterScan Messaging Security Suite; Wed, 14 Feb 2007 16:41:00 +0800 Received: from zytwbe01.zyxel.com ([172.23.5.10]) by zytwfe02.ZyXEL.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Feb 2007 16:40:26 +0800 Received: from zytwfe01.ZyXEL.com ([172.23.5.5]) by zytwbe01.zyxel.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Feb 2007 16:40:25 +0800 Received: from [172.23.17.92] ([172.23.17.92]) by zytwfe01.ZyXEL.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Feb 2007 16:40:25 +0800 Message-ID: <45D2CAFE.8000806@zyxel.com.tw> Date: Wed, 14 Feb 2007 16:40:30 +0800 From: Blue User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Feb 2007 08:40:25.0563 (UTC) FILETIME=[C5BFCAB0:01C75013] Subject: [FreeBSD-6.1 6.2] Race condition could happen while two thread close socket? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 08:55:34 -0000 Dear all: When looking into the soclose() in uipc_socket.c, I thought of one possible situation. If thread A called soclose() first, and then execute sorele() then sofree(). However, in sofree() (defined in uipc_socket.c), the socket mutex and accept mutex is unlocked first before releasing socket send buffer. While thread A is dealing with the send buffer releasing, another thread, thread B, jumped in. It also calls soclose(), and then sorele(). Following will be a catastrophe: sorele() will examine the socket's reference count ((so)->so_count), then panic occurs since the count value equals zero! Is there any reasonable explanation? Thanks. BR, Yi-Wen From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 10:45:44 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F075316A402 for ; Wed, 14 Feb 2007 10:45:44 +0000 (UTC) (envelope-from ea@sellinet.net) Received: from sellinet.net (galileo.sellinet.net [82.199.192.2]) by mx1.freebsd.org (Postfix) with SMTP id 3BEAC13C478 for ; Wed, 14 Feb 2007 10:45:44 +0000 (UTC) (envelope-from ea@sellinet.net) Received: (qmail 31673 invoked by uid 1009); 14 Feb 2007 12:19:02 +0200 Received: from ea@sellinet.net by galileo by uid 1002 with qmail-scanner-1.22 (spamassassin: 3.0.3. Clear:RC:1(127.0.0.1):. Processed in 0.088185 secs); 14 Feb 2007 10:19:02 -0000 Received: from unknown (HELO z.sellinet.net) (127.0.0.1) by localhost with SMTP; 14 Feb 2007 12:19:01 +0200 Received: from 82.199.192.218 (SquirrelMail authenticated user ea@sellinet.net); by z.sellinet.net with HTTP; Wed, 14 Feb 2007 12:19:01 +0200 (EET) Message-ID: <51675.82.199.192.218.1171448341.squirrel@82.199.192.218> Date: Wed, 14 Feb 2007 12:19:01 +0200 (EET) From: ea@sellinet.net To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.2 X-Mailer: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=windows-1251 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Strange behavior with arp permanent entries X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2007 10:45:45 -0000 Hello, Guys! I'm trying to restrict some LAN access by arp permanent entries. But it didn't work or it didn't work as I realize it. For example I have the following perm entries: user1: (82.199.215.195) at 00:0f:ea:a4:60:c5 on vlan804 permanent [vlan] user2: (82.199.215.196) at 00:13:8f:b1:68:4b on vlan804 permanent [vlan] And from what I realize if the user1 attempts to use user2's IP address. The Router should block all packets which coming from wrong physical address. But actually that didn't happen and user1 can use user2's IP address without any problems. Maybe someone of you will advice me to use ipfw arp rules but when I turn net.link.ether.ipfw ON I'm getting very low performance from the router. We talking about 800mbps and 600k packets per second, and many users which means many ipfw arp rules. System1 info: FreeBSD 6.2-RELEASE Intel(R) Xeon(R) CPU 5130 @ 2.00GHz 1G ram System2 info: FreeBSD 6.1-RELEASE ntel(R) Xeon(R) CPU 5130 @ 2.00GHz 1G ram Also I have a few other systems and it seems that it works on them (Working)System3 info: 6.0-RELEASE Dual Core AMD Opteron(tm) Processor 275 @ 2193.76-MHz 1G ram (Working)System4 info: 6.2-PRERELEASE Intel(R) Xeon(R) CPU 5130 @ 2.00GHz 1G ram Thank you guys. Any suggestions will be appreciated. Regards, E.A. -------------------------------------------------------------- SELLINET Internet Services Provider - http://www.sellinet.net/ From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 11:07:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF92216A420 for ; Wed, 14 Feb 2007 11:07:16 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog12.obsmtp.com (s200aog12.obsmtp.com [207.126.144.126]) by mx1.freebsd.org (Postfix) with SMTP id 3D48E13C4B6 for ; Wed, 14 Feb 2007 11:07:16 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([217.206.187.80]) by eu1sys200aob012.postini.com ([207.126.147.11]) with SMTP; Wed, 14 Feb 2007 11:07:15 UTC Received: from [10.0.0.79] (bwb.mintel.co.uk [10.0.0.79]) by rodney.mintel.co.uk (Postfix) with ESMTP id C5432181429; Wed, 14 Feb 2007 10:48:59 +0000 (GMT) Message-ID: <45D2E894.4090404@tomjudge.com> Date: Wed, 14 Feb 2007 10:46:44 +0000 From: Tom Judge User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <45D1E669.30402@seclark.us> In-Reply-To: <45D1E669.30402@seclark.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 11:07:17 -0000 Stephen Clark wrote: > Hello List, > > We have a setup that looks like the following. > > pc <-ethernet-> freebsd 4.9 <-pppoe-> internet <-ethernet-> freebsd 6.1 > on the freebsd box we have a gre tunnel with a mtu of 1420 feeding into a > gif vpn tunnel with a mtu of 1280 ( I know this dumb but it the default > value when you create a gif ) > feeding into a tun0 with a mtu of 1492. > > What we see is the packet never makes it to the freebsd 6.1 system. > > if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the > freebsd 4.9 system > send back an icmp dest unreachable - fragmentation needed and DF bit set? > $ sysctl -a | grep mtu > net.inet.tcp.path_mtu_discovery: 1 > > Now if I change the mtu of the gre to 1412 everything works. > > Any insight would be appreciated. > > Thanks, > Steve Are you using IPSEC on your gif interface? If so there is a bug in 6.1 where the IPSEC code that is responsible for populating the ICMP packet fields (Fragmentation needed and the MTU hint) fails to set the MTU hint in the icmp packet. The problem is fixed in 6.2 and it is a very simple patch for 6.1. Please see the link for the discussion on this problem back in november. http://groups.google.ms/group/muc.lists.freebsd.hackers/browse_thread/thread/bff95bd13d700fde/51a27f0d0c42ee92 Regards Tom J From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 15:22:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FA1516A409 for ; Wed, 14 Feb 2007 15:22:54 +0000 (UTC) (envelope-from msgs_for_me@mail.ru) Received: from mx28.mail.ru (mx28.mail.ru [194.67.23.67]) by mx1.freebsd.org (Postfix) with ESMTP id AC22F13C46B for ; Wed, 14 Feb 2007 15:22:53 +0000 (UTC) (envelope-from msgs_for_me@mail.ru) Received: from mx7.mail.ru (mx7.mail.ru [194.67.23.27]) by mx28.mail.ru (mPOP.Fallback_MX) with ESMTP id 16A886FAA70 for ; Wed, 14 Feb 2007 14:19:27 +0300 (MSK) Received: from [80.244.229.35] (port=35670 helo=VLADIMIR) by mx7.mail.ru with asmtp id 1HHIAV-0001Od-00 for freebsd-net@freebsd.org; Wed, 14 Feb 2007 14:19:23 +0300 X-Nat-Received: from [192.168.1.110]:2971 [ident-empty] by smtp-proxy.vltele.com with TPROXY id 1171451789.25854 Date: Wed, 14 Feb 2007 14:19:25 +0300 From: Vladimir Kapustin X-Mailer: The Bat! (v3.85.03) Professional Organization: vltele.com X-Priority: 3 (Normal) Message-ID: <319763897.20070214141925@mail.ru> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Strange behavior with arp permanent entries X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Kapustin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 15:22:54 -0000 >Hello, Guys! > >I'm trying to restrict some LAN access by arp permanent entries. But it >didn't work or it didn't work as I realize it. For example I have the >following perm entries: > > >user1: (82.199.215.195) at 00:0f:ea:a4:60:c5 on vlan804 permanent [vlan] >user2: (82.199.215.196) at 00:13:8f:b1:68:4b on vlan804 permanent [vlan] > > >And from what I realize if the user1 attempts to use user2's IP address. >The Router should block all packets which coming from wrong physical >address. But actually that didn't happen and user1 can use user2's IP >address without any problems. > > >Maybe someone of you will advice me to use ipfw arp rules but when I turn >net.link.ether.ipfw ON I'm getting very low performance from the router. >We talking about 800mbps and 600k packets per second, and many users which >means many ipfw arp rules. > > >System1 info: >FreeBSD 6.2-RELEASE >Intel(R) Xeon(R) CPU 5130 @ 2.00GHz >1G ram > >System2 info: > >...................................... man arp : ................... -s hostname ether_addr Create an ARP entry for the host called hostname with the Ether- net address ether_addr. The Ethernet address is given as six hex bytes separated by colons. The entry will be permanent unless the word temp is given in the command. If the word pub is given, the entry will be ``published''; i.e., this system will act as an ARP server, responding to requests for hostname even though the host address is not its own. In this case the ether_addr can be given as auto in which case the interfaces on this host will be examined, and if one of them is found to occupy the same subnet, its Ethernet address will be used. If the only keyword is also specified, this will create a ``published (proxy only)'' entry. This type of entry is created automatically if arp detects that a routing table entry for hostname already exists. -S hostname ether_addr Is just like -s except any existing ARP entry for this host will be deleted first. ....................... I have: root@router1# arp -a | wc -l 927 root@router1# arp -a | less ? (10.3.13.5) at 00:e0:4d:01:cb:09 on vlan313 permanent published [vlan] ? (10.3.13.7) at 00:0d:61:1c:b0:b6 on vlan313 permanent published [vlan] ? (10.3.13.14) at 00:11:d8:e8:db:0a on vlan313 permanent published [vlan] ......................... with the rules: arp -S IP mac pub From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 15:36:29 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7D7F16A408; Wed, 14 Feb 2007 15:36:29 +0000 (UTC) (envelope-from msgs_for_me@mail.ru) Received: from mx33.mail.ru (mx33.mail.ru [194.67.23.194]) by mx1.freebsd.org (Postfix) with ESMTP id 71D9013C48D; Wed, 14 Feb 2007 15:36:29 +0000 (UTC) (envelope-from msgs_for_me@mail.ru) Received: from [80.244.229.35] (port=7229 helo=VLADIMIR) by mx33.mail.ru with asmtp id 1HHMBG-000DLd-00; Wed, 14 Feb 2007 18:36:27 +0300 X-Nat-Received: from [192.168.1.110]:3843 [ident-empty] by smtp-proxy.vltele.com with TPROXY id 1171467214.12688 Date: Wed, 14 Feb 2007 18:36:25 +0300 From: Vladimir Kapustin X-Mailer: The Bat! (v3.85.03) Professional Organization: vltele.com X-Priority: 3 (Normal) Message-ID: <1024498861.20070214183625@mail.ru> To: freebsd-pf@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-isp@FreeBSD.ORG, freebsd-net@freebsd.org, freebsd-performance@FreeBSD.ORG Subject: How to optimize ruleset for gateway? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Kapustin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 15:36:29 -0000 Hi, all! I have such a problem when configuring the gateway for my LAN: I want to minimize the number of rules, and for this purpose I chose PF, but, as I wrote earlyer: http://lists.freebsd.org/pipermail/freebsd-pf/2007-January/002958.html and found some mails of other people: http://lists.freebsd.org/pipermail/freebsd-pf/2006-October/002681.html if I want to configure connection speed for each user on PF, I must configure the number of queues equal to the number of users, i.e. if I configure one queue and allow the table of users go to the Internet through this queue, I see, that all of them share the bandwidth of this queue. I don't think this is a good idea, and now I choosing some other variants of optimization, such as: 1. Configure PF for major rules and SPAM filtering and IPFW+DUMMYNET for queueing. I've read somewhere, that IPFW-shaper supports tables the way I need. I'm afraid that two firewalls should significantly decrease perfomance. 2. Configure only IPFW. But this means that I have to read full documentation about it, and find the way to protect the Internet from SPAM going from my local NET. The ruleset looks like: 0. Binat for real IP. 1. Block NetBIOS 2. Pass all from table-1 3. Pass all from table-128kbps queue 1(128kbps) 4. ..................... 5. Pass all from table-1024kbps queue 4(1024kbps) 6. Some spam-protection tool (like spamd) 7. Block all Could somebody give me some advice what way to go? P.S. Now my gateway works on 2-processor Xeon router with Redhat and iptables. It has 100 Mbps Internet channel, and in the time of maximum charge it processes 10-20 kpps. From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 16:18:55 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84FFB16A409 for ; Wed, 14 Feb 2007 16:18:55 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 1413F13C494 for ; Wed, 14 Feb 2007 16:18:54 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-235-229.51-151.net24.it [151.51.229.235]) (authenticated bits=128) by parrot.aev.net (8.13.8/8.13.8) with ESMTP id l1EGPBGP027601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 14 Feb 2007 17:25:17 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.13.8/8.13.8) with ESMTP id l1EGImVL080498 for ; Wed, 14 Feb 2007 17:18:49 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45D33663.9040902@netfence.it> Date: Wed, 14 Feb 2007 17:18:43 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 212.31.247.179 Subject: Gateway slowed down to barely usable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 16:18:55 -0000 Hello. A 6.1p13/i386 firewall of mine, although a bit rusty wrt hardware, is working wonderfully and is allowing us to fully exploit our Internet connections (1Mb/s). Today it suddenly dropped to a bare few b/s. I checked the ISP line by attaching another machine in place of this and it could do full 1Mb/s, so this box was the problem. After a simple reboot it started working as good as always. Now the question is: in case this happens again, how do I find out what's wrong? CPU usage was under 2% and so was swap usage... what else could I check? What tools should I use? bye & Thanks av. From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 18:17:13 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B413216A402 for ; Wed, 14 Feb 2007 18:17:13 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout05-04.prod.mesa1.secureserver.net (smtpout05-04.prod.mesa1.secureserver.net [64.202.165.221]) by mx1.freebsd.org (Postfix) with SMTP id 7A85B13C442 for ; Wed, 14 Feb 2007 18:17:11 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 9487 invoked from network); 14 Feb 2007 18:17:11 -0000 Received: from unknown (24.144.77.243) by smtpout05-04.prod.mesa1.secureserver.net (64.202.165.221) with ESMTP; 14 Feb 2007 18:17:10 -0000 Message-ID: <45D35225.2080103@seclark.us> Date: Wed, 14 Feb 2007 13:17:09 -0500 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Motin References: <1171398196.00688135.1171386001@10.7.7.3> <1171398210.00688151.1171387801@10.7.7.3> <1171401795.00688172.1171391400@10.7.7.3> <45D2410D.70509@alkar.net> In-Reply-To: <45D2410D.70509@alkar.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 18:17:13 -0000 Alexander Motin wrote: >Stephen Clark wrote: > > >>>>if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the >>>>freebsd 4.9 system >>>>send back an icmp dest unreachable - fragmentation needed and DF bit >>>>set? >>>> >>>> >>>Are you blocking icmp with a firewall filter? >>> >>> >>> >>Good question - but the answer is no. The other interesting fact is >>when I drop the mtu on >>the gre to 1412 I do see the icmp messages. >> >> > >Are you using any dummynet shapes? There is ancient bug in dummynet, >which leads to not sending of ICMPs when shape used on outgoing interface. > > > Hi Alexander, I had run into that problem before, in this case I am seing a icmp for 1420 mtu for the gre on the 4.9 side but the tun0 interface that pppoe is 1492 to allow for the ppp wrapper and I just read that the gif when using ipv4 doesn't handle pmtud - that I think is my real problem. Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 18:27:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2193916A402 for ; Wed, 14 Feb 2007 18:27:11 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpauth03.prod.mesa1.secureserver.net (smtpauth03.prod.mesa1.secureserver.net [64.202.165.183]) by mx1.freebsd.org (Postfix) with SMTP id 88E2613C461 for ; Wed, 14 Feb 2007 18:27:08 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 18986 invoked from network); 14 Feb 2007 18:27:06 -0000 Received: from unknown (24.144.77.243) by smtpauth03-04.prod.mesa1.secureserver.net (64.202.165.183) with ESMTP; 14 Feb 2007 18:27:05 -0000 Message-ID: <45D35479.8010100@seclark.us> Date: Wed, 14 Feb 2007 13:27:05 -0500 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Judge References: <45D1E669.30402@seclark.us> <45D2E894.4090404@tomjudge.com> In-Reply-To: <45D2E894.4090404@tomjudge.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: pmtud problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 18:27:11 -0000 Tom Judge wrote: >Stephen Clark wrote: > > >>Hello List, >> >>We have a setup that looks like the following. >> >>pc <-ethernet-> freebsd 4.9 <-pppoe-> internet <-ethernet-> freebsd 6.1 >>on the freebsd box we have a gre tunnel with a mtu of 1420 feeding into a >>gif vpn tunnel with a mtu of 1280 ( I know this dumb but it the default >>value when you create a gif ) >>feeding into a tun0 with a mtu of 1492. >> >>What we see is the packet never makes it to the freebsd 6.1 system. >> >>if the pc sends a packet of 1460 bytes with the DF bit set shouldn't the >>freebsd 4.9 system >>send back an icmp dest unreachable - fragmentation needed and DF bit set? >>$ sysctl -a | grep mtu >>net.inet.tcp.path_mtu_discovery: 1 >> >>Now if I change the mtu of the gre to 1412 everything works. >> >>Any insight would be appreciated. >> >>Thanks, >>Steve >> >> > >Are you using IPSEC on your gif interface? If so there is a bug in 6.1 >where the IPSEC code that is responsible for populating the ICMP packet >fields (Fragmentation needed and the MTU hint) fails to set the MTU hint >in the icmp packet. The problem is fixed in 6.2 and it is a very simple >patch for 6.1. > >Please see the link for the discussion on this problem back in november. > >http://groups.google.ms/group/muc.lists.freebsd.hackers/browse_thread/thread/bff95bd13d700fde/51a27f0d0c42ee92 > >Regards > >Tom J > > > Hi Tom, Thanks I saw that when I was sending from the 6.1 side and was sort of supprised there was no mtu hint size. I'll get the patch and apply it. The real place I am seeing the problem is on the other side. Regards, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 19:38:24 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B283216A400 for ; Wed, 14 Feb 2007 19:38:24 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0A213C4A8 for ; Wed, 14 Feb 2007 19:38:24 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 1D5C41AF1A2; Wed, 14 Feb 2007 14:38:22 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 14 Feb 2007 14:38:22 -0500 X-Sasl-enc: TL/WSwblwTXKGr76kaXlmddqdbI/TU3tgdxZ/V5zNn3w 1171481901 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 0DB3B234F1; Wed, 14 Feb 2007 14:38:20 -0500 (EST) Message-ID: <45D3652D.4020201@FreeBSD.org> Date: Wed, 14 Feb 2007 19:38:21 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: pyunyh@gmail.com References: <45CDFA18.3030102@incunabulum.net> <45CE0ED9.1010905@FreeBSD.org> <20070211073328.GB55314@cdnetworks.co.kr> In-Reply-To: <20070211073328.GB55314@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: [PATCH] Part 2 of low level 802.1p priority support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2007 19:38:24 -0000 Pyun YongHyeon wrote: > > Further testing with drivers is needed (I can't be 100% sure it fails > > with msk(4) because something strange is happening when vlan tagging is > > turned off). Perhaps Pyun knows? > > > > I guess I've not merged local changes before committing to HEAD. > How about attached one? > I can confirm that the merged VLAN tag code works OK with msk and VLAN_HWTAGGING disabled when using this patch. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 22:18:52 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 57F0D16A406 for ; Wed, 14 Feb 2007 22:18:52 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 31EBE13C48D for ; Wed, 14 Feb 2007 22:18:52 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id C80221AE8B0 for ; Wed, 14 Feb 2007 17:18:49 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 14 Feb 2007 17:18:49 -0500 X-Sasl-enc: cmlPXq8fW1HO4Le3yUFViKvynBKfcI5o7CKucKQtSsvf 1171491529 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 31852181C for ; Wed, 14 Feb 2007 17:18:48 -0500 (EST) Message-ID: <45D38AC9.50107@incunabulum.net> Date: Wed, 14 Feb 2007 22:18:49 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [PATCH] Updated 802.1p/q patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 22:18:52 -0000 Hi, I have tested my 802.1p input patch with vlans configured. So far so good. It is now available from: http://people.FreeBSD.org/~bms/dump/latest-8021p.diff This updated patch moves the 802.1q encapsulation into if_ethersubr.c, allowing M_VLANTAG to be passed up and down the stack for 802.1p priority. I would greatly appreciate wider testing before it is committed. I've noticed that vlan(4) will not put a parent interface into PROMISC if the vlanhwtag capability exists but is disabled. If the main non-vlan input path receives datagrams destined for a layer 3 address configured on a vlan interface, the netinet stack will quite reasonably try to reply on the vlan interface unless net.inet.ip.check_interface is set to 1; something to be aware of. If vlan(4) gets an mbuf which has already been tagged with M_VLANTAG from higher up in the stack, it *should* ignore the vlan id by overwriting it, and using the priority field already assigned to it, so that ALTQ or PF can do its magic. This new patch should do this. The Ethernet code will not use 802.1p by default unless it came from higher up (by way of M_VLANTAG passed to a driver); we should insert the 802.1p tag in the situation where we got an M_VLANTAG from further up without a vlan(4) instance being involved. The new patch should do this. We should also make sure the CFI bit is always cleared in bridging situations as it has special meaning for token ring and FDDI. What has not been tested or considered is the situation where we have nested VLANs. At least one individual has asked about this feature. At the moment, I'd suggest that only Netgraph potentially deals with this rather than the main network stack. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Wed Feb 14 23:29:54 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A945C16A401 for ; Wed, 14 Feb 2007 23:29:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 71AA113C428 for ; Wed, 14 Feb 2007 23:29:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l1EN5PsI089277 for ; Wed, 14 Feb 2007 18:05:25 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-net@FreeBSD.org Date: Wed, 14 Feb 2007 18:05:15 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200702141805.20228.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2568/Wed Feb 14 10:42:10 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: [PATCH] BPF to support directions and more X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Feb 2007 23:29:54 -0000 I was playing with some BPF ideas for few days and I added two new features. SEESENT flag is extended to see only outgoing packets, which is analogous to libpcap's PCAP_D_OUT direction. Thus SEESENT is now called DIRECTION. Second feature is feedback mode (sort of simulated hardware loopback), i.e., when packets are injected, you can feed them back as if they are coming from the wire. You can debug link layer protocols easily with this without second machine, network controller, or loopback plug. It's only tested with Ethernet, though. All necessary patches (including libpcap modification) are here: http://people.freebsd.org/~jkim/bpf_feedback.diff Don't forget to turn off all hardware assisted features (e.g., RX/TX checksum offloading) to test feedback mode. Otherwise, packets will be dropped. Jung-uk Kim Note: Actually I started this for QEMU networking, so that's another example. See: http://docs.freebsd.org/cgi/mid.cgi?200702092002.31220.jkim From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 01:02:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AF9916A407 for ; Thu, 15 Feb 2007 01:02:54 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id E75FC13C46B for ; Thu, 15 Feb 2007 01:02:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 262C91AF0E3 for ; Wed, 14 Feb 2007 20:02:51 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 14 Feb 2007 20:02:51 -0500 X-Sasl-enc: xnyCYk6tOIbP+J7OY6oSjcMKa8OpGiem4Nl7MWn7A0nj 1171501370 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 687F02364C for ; Wed, 14 Feb 2007 20:02:50 -0500 (EST) Message-ID: <45D3B13A.5080700@FreeBSD.org> Date: Thu, 15 Feb 2007 01:02:50 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <45D33663.9040902@netfence.it> In-Reply-To: <45D33663.9040902@netfence.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Gateway slowed down to barely usable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 01:02:54 -0000 Andrea Venturoli wrote: > > Today it suddenly dropped to a bare few b/s. I checked the ISP line by > attaching another machine in place of this and it could do full 1Mb/s, > so this box was the problem. > > After a simple reboot it started working as good as always. > > Now the question is: in case this happens again, how do I find out > what's wrong? > CPU usage was under 2% and so was swap usage... what else could I check? > What tools should I use? Points for further investigation: How long was the machine up for? Exactly which network components in FreeBSD are you using? Do you have any figures on what kind of network load the machine was dealing with? Can you rule out problems with an intermediate switch? Based on what you've said I can only speculate that the possible causes are either mbuf memory fragmentation or a driver problem; both are a total stab in the dark. Regards, BMS > > bye & Thanks > av. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 06:22:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 03A8E16A420 for ; Thu, 15 Feb 2007 06:22:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by mx1.freebsd.org (Postfix) with ESMTP id B607913C471 for ; Thu, 15 Feb 2007 06:22:31 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so487503nzh for ; Wed, 14 Feb 2007 22:22:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=NSAUt8z+K5itFAknKtDffiXdp/Vf4q3iUxkHCbSuqJuqkz3CVYcL3rwvKdpQCZW8zffBfQNZtpDCtfoPJU1QAVXPmGVTb7ym7TFO3MjfEAojUTc8CPqqTL2hwVxUd77K4NL5H3CVJzvQobXgZ05h2nsahqvVIKR2pJRCA1yvRdg= Received: by 10.65.154.2 with SMTP id g2mr2087434qbo.1171520550909; Wed, 14 Feb 2007 22:22:30 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 18sm7785430nzo.2007.02.14.22.22.28; Wed, 14 Feb 2007 22:22:30 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l1F6KVXa005545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Feb 2007 15:20:31 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l1F6KVuo005544; Thu, 15 Feb 2007 15:20:31 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 15 Feb 2007 15:20:31 +0900 From: Pyun YongHyeon To: "Bruce M. Simpson" Message-ID: <20070215062030.GB4319@cdnetworks.co.kr> References: <45CDFA18.3030102@incunabulum.net> <45CE0ED9.1010905@FreeBSD.org> <20070211073328.GB55314@cdnetworks.co.kr> <45D3652D.4020201@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45D3652D.4020201@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@FreeBSD.org Subject: Re: [PATCH] Part 2 of low level 802.1p priority support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 06:22:32 -0000 On Wed, Feb 14, 2007 at 07:38:21PM +0000, Bruce M. Simpson wrote: > Pyun YongHyeon wrote: > > > Further testing with drivers is needed (I can't be 100% sure it fails > > > with msk(4) because something strange is happening when vlan tagging is > > > turned off). Perhaps Pyun knows? > > > > > > >I guess I've not merged local changes before committing to HEAD. > >How about attached one? > > > I can confirm that the merged VLAN tag code works OK with msk and > VLAN_HWTAGGING disabled when using this patch. > Thank you. Patch committed(if_msk.c, rev 1.9). > Regards, > BMS -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 09:13:24 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4038916A400 for ; Thu, 15 Feb 2007 09:13:24 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 969A013C428 for ; Thu, 15 Feb 2007 09:13:17 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id l1F9DAgP025868; Thu, 15 Feb 2007 12:13:10 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id l1F9D9HY025867; Thu, 15 Feb 2007 12:13:09 +0300 (MSK) (envelope-from yar) Date: Thu, 15 Feb 2007 12:13:09 +0300 From: Yar Tikhiy To: Bruce M Simpson Message-ID: <20070215091309.GC20957@comp.chem.msu.su> References: <45D38AC9.50107@incunabulum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45D38AC9.50107@incunabulum.net> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Updated 802.1p/q patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 09:13:24 -0000 On Wed, Feb 14, 2007 at 10:18:49PM +0000, Bruce M Simpson wrote: > > What has not been tested or considered is the situation where we have > nested VLANs. At least one individual has asked about this feature. At > the moment, I'd suggest that only Netgraph potentially deals with this > rather than the main network stack. Do you have any architectural reservations about nested VLANs in the main network stack? Presently, a one-line patch can allow a vlan(4) to attach to another vlan(4), but I haven't heard about the behaviour of the resulting setup yet. Thanks! -- Yar From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 09:17:13 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1806E16A4C5 for ; Thu, 15 Feb 2007 09:17:13 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 7780413C441 for ; Thu, 15 Feb 2007 09:17:10 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id l1F9H5Wb025971; Thu, 15 Feb 2007 12:17:05 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id l1F9H3no025966; Thu, 15 Feb 2007 12:17:03 +0300 (MSK) (envelope-from yar) Date: Thu, 15 Feb 2007 12:17:03 +0300 From: Yar Tikhiy To: Jung-uk Kim Message-ID: <20070215091702.GD20957@comp.chem.msu.su> References: <200702141805.20228.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200702141805.20228.jkim@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] BPF to support directions and more X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 09:17:13 -0000 On Wed, Feb 14, 2007 at 06:05:15PM -0500, Jung-uk Kim wrote: > I was playing with some BPF ideas for few days and I added two new > features. SEESENT flag is extended to see only outgoing packets, > which is analogous to libpcap's PCAP_D_OUT direction. Thus SEESENT > is now called DIRECTION. Any plans to teach BPF to report the direction a packet goes in? In some cases it can be unobvious whether it's incoming or outgoing. -- Yar From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 09:55:45 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3E0616A402 for ; Thu, 15 Feb 2007 09:55:45 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 15D0213C4BB for ; Thu, 15 Feb 2007 09:55:44 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id BFD141CC52; Thu, 15 Feb 2007 22:55:42 +1300 (NZDT) Date: Thu, 15 Feb 2007 22:55:42 +1300 From: Andrew Thompson To: Bruce M Simpson Message-ID: <20070215095542.GA58929@heff.fud.org.nz> References: <45D38AC9.50107@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45D38AC9.50107@incunabulum.net> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Updated 802.1p/q patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 09:55:46 -0000 On Wed, Feb 14, 2007 at 10:18:49PM +0000, Bruce M Simpson wrote: > Hi, > > I have tested my 802.1p input patch with vlans configured. So far so good. > > It is now available from: > http://people.FreeBSD.org/~bms/dump/latest-8021p.diff > /* * If the device did not perform decapsulation of the 802.1q * VLAN header itself, do this now... */ if ((ether_type == ETHERTYPE_VLAN) && !(m->m_flags & M_VLANTAG)) { ... } Is it possible to move this block into ether_input() above the bridge hook? it would be nice if ether_vtag was set consistently early on in the game. cheers, Andrew From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 18:03:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A01116A400 for ; Thu, 15 Feb 2007 18:03:10 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outV.internet-mail-service.net (outV.internet-mail-service.net [216.240.47.245]) by mx1.freebsd.org (Postfix) with ESMTP id 376CD13C4BB for ; Thu, 15 Feb 2007 18:03:10 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Thu, 15 Feb 2007 09:39:37 -0800 Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id A1EBA125B39; Thu, 15 Feb 2007 10:03:07 -0800 (PST) Message-ID: <45D4A05B.4090509@elischer.org> Date: Thu, 15 Feb 2007 10:03:07 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Andrew Thompson References: <45D38AC9.50107@incunabulum.net> <20070215095542.GA58929@heff.fud.org.nz> In-Reply-To: <20070215095542.GA58929@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Bruce M Simpson Subject: Re: [PATCH] Updated 802.1p/q patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 18:03:10 -0000 Andrew Thompson wrote: > On Wed, Feb 14, 2007 at 10:18:49PM +0000, Bruce M Simpson wrote: >> Hi, >> >> I have tested my 802.1p input patch with vlans configured. So far so good. >> >> It is now available from: >> http://people.FreeBSD.org/~bms/dump/latest-8021p.diff >> > > /* > * If the device did not perform decapsulation of the 802.1q > * VLAN header itself, do this now... > */ > if ((ether_type == ETHERTYPE_VLAN) && !(m->m_flags & M_VLANTAG)) { > ... > } > > Is it possible to move this block into ether_input() above the bridge > hook? it would be nice if ether_vtag was set consistently early on in > the game. > yes, I would like the tagging to be done before the bridging so that all packets being filtered by the bridge are the same. > > cheers, > Andrew > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 20:50:26 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D6D416A407 for ; Thu, 15 Feb 2007 20:50:26 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from rock.polstra.com (rock.polstra.com [64.119.0.113]) by mx1.freebsd.org (Postfix) with ESMTP id 2E05813C4B5 for ; Thu, 15 Feb 2007 20:50:26 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) (authenticated bits=0) by rock.polstra.com (8.13.8/8.13.8) with ESMTP id l1FKZpRR060908 for ; Thu, 15 Feb 2007 12:35:51 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 15 Feb 2007 12:35:42 -0800 (PST) From: John Polstra To: freebsd-net@freebsd.org X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (rock.polstra.com [64.119.0.113]); Thu, 15 Feb 2007 12:35:51 -0800 (PST) Subject: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 20:50:26 -0000 I have a Dell SC1435 server running an i386 -current system from around the end of December, with a few selected updates applied. It had been running reliably until early this morning, when the following sequence of events happened. First, this message was logged: Feb 15 07:14:29 rock kernel: bge0: discard frame w/o packet header About 2 minutes later, at 07:16:30, the last /var/log/maillog entry was logged. (This machine is under constant assault from spambots trying dictionary attacks. It is rare for more than 15 seconds to pass without something being logged in the maillog file.) 30 seconds after that came another bge message: Feb 15 07:17:00 rock kernel: bge0: discard frame w/o packet header At that point, all network connectivity was gone. The machine didn't respond to pings. Worse, its remote management controller, which uses ASF and shares the same network interface, was also unresponsive to pings. To get the machine back, I had to ask somebody working at the colocation facility to power-cycle it. The "discard frame w/o packet header" message comes from ether_input() if it gets an mbuf that doesn't have the M_PKTHDR flag set. That can't happen unless something is very wrong with the system. I'd like to make it a panic. At least then the machine would reboot instead of just becoming unreachable. Any objections? Some other nearby warnings should also be panics, in my opinion: discard frame w/o leading ethernet header ... discard frame w/o interface pointer ... and, maybe: discard oversize frame ... Opinions? John PS - dmesg output for bge0: bge0: mem 0xefef0000-0xefefffff irq 33 at device 0.0 on pci1 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:18:8b:78:b7:b1 I'm running the following revisions of the driver sources: if_bge.c 1.172 if_bgereg.h 1.65 brgphy.c 1.52 These aren't completely up-to-date, but I don't see any recent changes that would have anything to do with the messages that were logged. From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:11:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EAA1D16A401 for ; Thu, 15 Feb 2007 21:11:41 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7E74413C4A5 for ; Thu, 15 Feb 2007 21:11:41 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1277990nfc for ; Thu, 15 Feb 2007 13:11:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XUT+ZCx12VY+xZrZ9jO0L5lPJM+wsBLcz18g1+5Mg/7ZlZrHAIZv7vzjreeMe8yp+kYBWzVaQoiNPynAIujB5lZrJ4llToLcdNegk5EcoRgWM/s/ggagBd6Oov6K3rS1hn+rXX99xoqXG7lriEDhH4CqYIK1Vo50NbkwnXvgcaI= Received: by 10.82.160.2 with SMTP id i2mr3606225bue.1171573118942; Thu, 15 Feb 2007 12:58:38 -0800 (PST) Received: by 10.82.151.15 with HTTP; Thu, 15 Feb 2007 12:58:38 -0800 (PST) Message-ID: Date: Thu, 15 Feb 2007 12:58:38 -0800 From: "Kip Macy" To: "John Polstra" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:11:42 -0000 > > The "discard frame w/o packet header" message comes from ether_input() > if it gets an mbuf that doesn't have the M_PKTHDR flag set. That > can't happen unless something is very wrong with the system. I'd like > to make it a panic. At least then the machine would reboot instead of > just becoming unreachable. Any objections? Please don't make it the default. Odds are ifconfig down, ifconfig up would fix it for those of us with console access. Either way it sounds like someone has discovered a DOS in bge. -Kip From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:18:07 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3798B16A408 for ; Thu, 15 Feb 2007 21:18:07 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.238]) by mx1.freebsd.org (Postfix) with ESMTP id 02FAB13C442 for ; Thu, 15 Feb 2007 21:18:06 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by nz-out-0506.google.com with SMTP id i11so743196nzh for ; Thu, 15 Feb 2007 13:18:06 -0800 (PST) Received: by 10.64.241.3 with SMTP id o3mr3711132qbh.1171574286084; Thu, 15 Feb 2007 13:18:06 -0800 (PST) Received: by 10.64.220.15 with HTTP; Thu, 15 Feb 2007 13:18:06 -0800 (PST) Message-ID: Date: Thu, 15 Feb 2007 23:18:06 +0200 From: "Vlad GALU" To: freebsd-net@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:18:07 -0000 On 2/15/07, Kip Macy wrote: > > > > The "discard frame w/o packet header" message comes from ether_input() > > if it gets an mbuf that doesn't have the M_PKTHDR flag set. That > > can't happen unless something is very wrong with the system. I'd like > > to make it a panic. At least then the machine would reboot instead of > > just becoming unreachable. Any objections? > > Please don't make it the default. Odds are ifconfig down, ifconfig up > would fix it for those of us with console access. Either way it sounds > like someone has discovered a DOS in bge. It's present in at least sk(4) as well. I saw it recently. > -Kip > _______________________________________________ > 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" > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:32:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD3A616A400 for ; Thu, 15 Feb 2007 21:32:30 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6988313C481 for ; Thu, 15 Feb 2007 21:32:30 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l1FLWT5b013536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Feb 2007 13:32:30 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45D4D16D.2000205@errno.com> Date: Thu, 15 Feb 2007 13:32:29 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.9 (X11/20070208) MIME-Version: 1.0 To: John Polstra References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:32:31 -0000 John Polstra wrote: > I have a Dell SC1435 server running an i386 -current system from > around the end of December, with a few selected updates applied. It > had been running reliably until early this morning, when the > following sequence of events happened. First, this message was > logged: > > Feb 15 07:14:29 rock kernel: bge0: discard frame w/o packet header > > About 2 minutes later, at 07:16:30, the last /var/log/maillog entry > was logged. (This machine is under constant assault from spambots > trying dictionary attacks. It is rare for more than 15 seconds to > pass without something being logged in the maillog file.) > > 30 seconds after that came another bge message: > > Feb 15 07:17:00 rock kernel: bge0: discard frame w/o packet header > > At that point, all network connectivity was gone. The machine didn't > respond to pings. Worse, its remote management controller, which uses > ASF and shares the same network interface, was also unresponsive to > pings. To get the machine back, I had to ask somebody working at the > colocation facility to power-cycle it. > > The "discard frame w/o packet header" message comes from ether_input() > if it gets an mbuf that doesn't have the M_PKTHDR flag set. That > can't happen unless something is very wrong with the system. I'd like > to make it a panic. At least then the machine would reboot instead of > just becoming unreachable. Any objections? > > Some other nearby warnings should also be panics, in my opinion: > > discard frame w/o leading ethernet header ... > > discard frame w/o interface pointer ... > > and, maybe: > > discard oversize frame ... > > Opinions? There are several diagnostics in ether_input I added mostly because drivers "shouldn't do that"; this is one of them. However some are questionable. I'm not sure about the panic but at the least we should rate limit the messages so they can't be used as a DOS mechanism. Replacing them with counters and sticking the printf's under IFF_DEBUG is another option. Sam From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:47:26 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7198C16A408 for ; Thu, 15 Feb 2007 21:47:26 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from rock.polstra.com (rock.polstra.com [64.119.0.113]) by mx1.freebsd.org (Postfix) with ESMTP id 531BB13C4BD for ; Thu, 15 Feb 2007 21:47:26 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) (authenticated bits=0) by rock.polstra.com (8.13.8/8.13.8) with ESMTP id l1FLlONp003668; Thu, 15 Feb 2007 13:47:25 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Feb 2007 13:47:24 -0800 (PST) From: John Polstra To: Kip Macy X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (rock.polstra.com [64.119.0.113]); Thu, 15 Feb 2007 13:47:25 -0800 (PST) Cc: freebsd-net@freebsd.org Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:47:26 -0000 On 15-Feb-2007 Kip Macy wrote: >> >> The "discard frame w/o packet header" message comes from ether_input() >> if it gets an mbuf that doesn't have the M_PKTHDR flag set. That >> can't happen unless something is very wrong with the system. I'd like >> to make it a panic. At least then the machine would reboot instead of >> just becoming unreachable. Any objections? > > Please don't make it the default. Odds are ifconfig down, ifconfig up > would fix it for those of us with console access. That may be the case, but you might not notice it for many hours. I'd think most folks would want the system to recover on its own, by rebooting. > Either way it sounds like someone has discovered a DOS in bge. No, it just about has to be a bug -- either in the mbuf allocator, the driver, or the NIC hardware. M_PKTHDR is a flag in the mbuf header, an area that isn't touched by packet data. The driver allocates all of its receive mbufs with the M_PKTHDR flag set. There's no legitimate way for the flag to get cleared, and nothing coming in on the wire should be able to cause it to be cleared. John From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:50:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB83016A400 for ; Thu, 15 Feb 2007 21:50:18 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 613ED13C461 for ; Thu, 15 Feb 2007 21:50:18 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1289675nfc for ; Thu, 15 Feb 2007 13:50:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qbUcJP/Bad+qGEnQX4tGxon6A5AAX0TaMQ9UGNqAeFSdLgsB5tF98ffaTO4/lJfPIoVaAHMWkm3739eGFzMe6WF+WGLBIYwLk1pg3Ki9PD9CnJDILCNJldEvTQJ4CGwaOt3zxA2IcHv89cigaBIIn2jrU8F9Al48E1CqdiST3dk= Received: by 10.82.154.2 with SMTP id b2mr3687308bue.1171576216774; Thu, 15 Feb 2007 13:50:16 -0800 (PST) Received: by 10.82.151.15 with HTTP; Thu, 15 Feb 2007 13:50:16 -0800 (PST) Message-ID: Date: Thu, 15 Feb 2007 13:50:16 -0800 From: "Kip Macy" To: "John Polstra" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:50:18 -0000 > > Either way it sounds like someone has discovered a DOS in bge. > > No, it just about has to be a bug -- either in the mbuf allocator, the > driver, or the NIC hardware. M_PKTHDR is a flag in the mbuf header, > an area that isn't touched by packet data. The driver allocates > all of its receive mbufs with the M_PKTHDR flag set. There's no > legitimate way for the flag to get cleared, and nothing coming in on > the wire should be able to cause it to be cleared. I mean a bug in if_bge.c - there are a lot of ways that this could happen - not calling M_GETHDR, mis-calling m_pullup etc. -Kip From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:51:48 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E84F16A420 for ; Thu, 15 Feb 2007 21:51:48 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 36EE813C4A6 for ; Thu, 15 Feb 2007 21:51:48 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l1FLpcfN051211; Thu, 15 Feb 2007 16:51:38 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-net@FreeBSD.org Date: Thu, 15 Feb 2007 16:51:27 -0500 User-Agent: KMail/1.6.2 References: <200702141805.20228.jkim@FreeBSD.org> <20070215091702.GD20957@comp.chem.msu.su> In-Reply-To: <20070215091702.GD20957@comp.chem.msu.su> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200702151651.35631.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2576/Thu Feb 15 12:05:25 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Yar Tikhiy Subject: Re: [PATCH] BPF to support directions and more X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:51:48 -0000 On Thursday 15 February 2007 04:17 am, Yar Tikhiy wrote: > On Wed, Feb 14, 2007 at 06:05:15PM -0500, Jung-uk Kim wrote: > > I was playing with some BPF ideas for few days and I added two > > new features. SEESENT flag is extended to see only outgoing > > packets, which is analogous to libpcap's PCAP_D_OUT direction. > > Thus SEESENT is now called DIRECTION. > > Any plans to teach BPF to report the direction a packet goes in? > In some cases it can be unobvious whether it's incoming or > outgoing. No, not at the moment. You can work around it by using the patch though. Capture incoming packets with BPF_D_IN and outgoing packets with BPF_D_OUT. If you want to merge them back, you can use mergecap utility from Wireshark. Jung-uk Kim From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:55:59 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AEE1616A400 for ; Thu, 15 Feb 2007 21:55:59 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 761EC13C46B for ; Thu, 15 Feb 2007 21:55:57 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l1FLttXR051516 for ; Thu, 15 Feb 2007 16:55:55 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-net@FreeBSD.org Date: Thu, 15 Feb 2007 16:55:51 -0500 User-Agent: KMail/1.6.2 References: <200702141805.20228.jkim@FreeBSD.org> In-Reply-To: <200702141805.20228.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200702151655.53581.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2576/Thu Feb 15 12:05:25 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: [PATCH] BPF to support directions and more X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 21:55:59 -0000 On Wednesday 14 February 2007 06:05 pm, Jung-uk Kim wrote: > I was playing with some BPF ideas for few days and I added two new > features. SEESENT flag is extended to see only outgoing packets, > which is analogous to libpcap's PCAP_D_OUT direction. Thus SEESENT > is now called DIRECTION. Second feature is feedback mode (sort of > simulated hardware loopback), i.e., when packets are injected, you > can feed them back as if they are coming from the wire. You can > debug link layer protocols easily with this without second machine, > network controller, or loopback plug. It's only tested with > Ethernet, though. All necessary patches (including libpcap > modification) are here: > > http://people.freebsd.org/~jkim/bpf_feedback.diff I have received some positive feedbacks and comments. So, I made some adjustments/corrections to reflect them: http://people.freebsd.org/~jkim/bpf_feedback-20070215.diff Thanks, Jung-uk Kim From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 22:28:59 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E19E316A402 for ; Thu, 15 Feb 2007 22:28:59 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx4.mail.ru (fallback.mail.ru [194.67.57.14]) by mx1.freebsd.org (Postfix) with ESMTP id A59B413C4A8 for ; Thu, 15 Feb 2007 22:28:59 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx2.mail.ru (mx2-2.mail.ru [194.67.23.122]) by mx4.mail.ru (mPOP.Fallback_MX) with ESMTP id 677DD5EF507 for ; Fri, 16 Feb 2007 00:34:51 +0300 (MSK) Received: from [85.156.232.99] (port=61118 helo=localhost) by mx2.mail.ru with asmtp id 1HHoFd-000CGp-00 for freebsd-net@freebsd.org; Fri, 16 Feb 2007 00:34:49 +0300 Date: Thu, 15 Feb 2007 23:34:48 +0200 To: freebsd-net@freebsd.org From: "V.Chukharev" Content-Type: text/plain; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Message-ID: User-Agent: Opera Mail/9.10 (FreeBSD) Subject: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 22:29:00 -0000 Hi, It seems that iwi driver cannot survive more than just a few cycles of switching down/up. In a place with a bad wireless connection I needed to do that quite a number of times (that was the simplest way to restore connectivity I knew), and after 5-10 cycles I needed to reboot my notebook totally. Can anybody with iwi () confirm (or better unconfirm) that doing for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig iwi0 up; done always results in the following messages (and lost connectivity): Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN Feb 15 09:44:18 chu kernel: iwi0: device timeout Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory A fix for this would be even better ;)) Thanks, -- V. Chukharev From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 22:35:52 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8E0716A409 for ; Thu, 15 Feb 2007 22:35:52 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 7502113C4A7 for ; Thu, 15 Feb 2007 22:35:52 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l1FMZp1k095317; Thu, 15 Feb 2007 14:35:51 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l1FMZpvK095316; Thu, 15 Feb 2007 14:35:51 -0800 (PST) (envelope-from rizzo) Date: Thu, 15 Feb 2007 14:35:51 -0800 From: Luigi Rizzo To: "V.Chukharev" Message-ID: <20070215143551.A94883@xorpc.icir.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from chukharev@mail.ru on Thu, Feb 15, 2007 at 11:34:48PM +0200 Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 22:35:52 -0000 will have a look at this. Which version of if_iwi.c are you using ? cheers luigi On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote: > Hi, > > It seems that iwi driver cannot survive more than just a few cycles of switching down/up. > In a place with a bad wireless connection I needed to do that quite a number of times > (that was the simplest way to restore connectivity I knew), and after 5-10 cycles I needed > to reboot my notebook totally. > > Can anybody with iwi () confirm (or better unconfirm) > that doing > > for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig iwi0 up; done > > always results in the following messages (and lost connectivity): > > Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP > Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:18 chu kernel: iwi0: device timeout > Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory > > A fix for this would be even better ;)) > > Thanks, > -- > V. Chukharev > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 22:40:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 82A2B16A401 for ; Thu, 15 Feb 2007 22:40:41 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from rock.polstra.com (rock.polstra.com [64.119.0.113]) by mx1.freebsd.org (Postfix) with ESMTP id 647A713C441 for ; Thu, 15 Feb 2007 22:40:41 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) (authenticated bits=0) by rock.polstra.com (8.13.8/8.13.8) with ESMTP id l1FMee8k004405; Thu, 15 Feb 2007 14:40:40 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Feb 2007 14:40:40 -0800 (PST) From: John Polstra To: Kip Macy X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (rock.polstra.com [64.119.0.113]); Thu, 15 Feb 2007 14:40:41 -0800 (PST) Cc: freebsd-net@freebsd.org Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 22:40:41 -0000 On 15-Feb-2007 Kip Macy wrote: > I mean a bug in if_bge.c - there are a lot of ways that this could > happen - not calling M_GETHDR, mis-calling m_pullup etc. There's no obvious bug in that part of the driver, but I'm going to instrument it on the offending system to try to find out just what's going on. When a packet is received, the driver allocates an mbuf to replace the one that the received packet occupied. It does that in one of two ways. The normal case is to call m_getcl(M_DONTWAIT, MT_DATA, M_PKTHDR). For that to return an mbuf without M_PKTHDR set would require a pretty serious bug in the mbuf or UMA code. The less common case is that the driver discards the just-received packet and reuses the mbuf it occupied. It does that if the m_getcl call failed (i.e., we are out of mbufs) or if the flags in the descriptor show that the just-received packet had errors. If there's a driver bug it's probably in this code path, but I don't see it yet. Hopefully, the diagnostics I've added will point to the problem. John From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 23:22:30 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F75E16A401 for ; Thu, 15 Feb 2007 23:22:30 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id 3338013C48E for ; Thu, 15 Feb 2007 23:22:30 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.2.163]) by mailout1.pacific.net.au (Postfix) with ESMTP id EA2195A7D22; Fri, 16 Feb 2007 10:22:28 +1100 (EST) Received: from besplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (Postfix) with ESMTP id 7E9C12740D; Fri, 16 Feb 2007 10:22:27 +1100 (EST) Date: Fri, 16 Feb 2007 10:22:26 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Sam Leffler In-Reply-To: <45D4D16D.2000205@errno.com> Message-ID: <20070216092306.A2150@besplex.bde.org> References: <45D4D16D.2000205@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@FreeBSD.org, John Polstra Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 23:22:30 -0000 On Thu, 15 Feb 2007, Sam Leffler wrote: > John Polstra wrote: >> I have a Dell SC1435 server running an i386 -current system from >> around the end of December, with a few selected updates applied. It >> had been running reliably until early this morning, when the >> following sequence of events happened. First, this message was >> logged: >> >> Feb 15 07:14:29 rock kernel: bge0: discard frame w/o packet header >> >> About 2 minutes later, at 07:16:30, the last /var/log/maillog entry >> was logged. (This machine is under constant assault from spambots >> trying dictionary attacks. It is rare for more than 15 seconds to >> pass without something being logged in the maillog file.) >> >> 30 seconds after that came another bge message: >> >> Feb 15 07:17:00 rock kernel: bge0: discard frame w/o packet header >> >> At that point, all network connectivity was gone. The machine didn't >> respond to pings. Worse, its remote management controller, which uses >> ASF and shares the same network interface, was also unresponsive to >> pings. To get the machine back, I had to ask somebody working at the >> colocation facility to power-cycle it. >> >> The "discard frame w/o packet header" message comes from ether_input() >> if it gets an mbuf that doesn't have the M_PKTHDR flag set. That >> can't happen unless something is very wrong with the system. I'd like >> to make it a panic. At least then the machine would reboot instead of >> just becoming unreachable. Any objections? >> >> Some other nearby warnings should also be panics, in my opinion: >> >> discard frame w/o leading ethernet header ... >> >> discard frame w/o interface pointer ... >> >> and, maybe: >> >> discard oversize frame ... Old versions of sk with a Yukon Lite NIC spew the first and third of these messages when blasted with tiny packets. ISTR seeing just a few of "discard frame w/o packet header" in combination with this. It was a driver bug. I haven't seen any 1 Gbps NICs/buses that are UnLite enough to actually keep up with 1 Gbps for small packets, and the Yukon Lite is one of the Lite-ests. With old versions of sk, when blasted at 640 kpps, it claims to to receive 270k good pps and drop a few thousand bad pps, with most of the few thousand reported in the above messages, at least when I hide the messages under bootverbose so that the system doesn't spend most of its time spewing the messages (then it only reports the errors by incrementing if_ierrors). In newer versions of sk, it checks the correct hardware error bit and also checks packet lengths, and finds errors in 112k of the packets previously reported as good. It still doesn't report errors for 640-270k packets dropped before reaching the interrupt handler. >> Opinions? > > There are several diagnostics in ether_input I added mostly because > drivers "shouldn't do that"; this is one of them. However some are > questionable. I'm not sure about the panic but at the least we should > rate limit the messages so they can't be used as a DOS mechanism. > Replacing them with counters and sticking the printf's under IFF_DEBUG > is another option. sk would have been fixed sooner if the printfs were panics, but what I wanted was just rate limiting, with some messages to remind me of the problem since being silent about it except for incrementing if_ierrors makes it far too easy to ignore. Accumulating and printing counters for new and old types of errors is another problem. Handling the errors at low levels (preferably entirely in hardware) is good for efficiency, but gives the problem of mapping hardware error counters for each type of error to error counters designed for software. The fixed sk driver doesn't do this at all -- it just increments the generic if_ierrors for all types of errors; it doesn't know how to read hardware error counts or even if they exist, so it doesn't even get if_ierrors correct (multiple dropped packets are counted as 1 error). The bge driver knows how to do this, but can't do it well since there are dozens of hardware error counters and only a few software error counters, and statistics programs can barely display the old ones. Bruce From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 23:29:42 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 356FF16A401 for ; Thu, 15 Feb 2007 23:29:42 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 28C0013C46B for ; Thu, 15 Feb 2007 23:29:42 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l1FMxnpX095593; Thu, 15 Feb 2007 14:59:49 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l1FMxn9U095592; Thu, 15 Feb 2007 14:59:49 -0800 (PST) (envelope-from rizzo) Date: Thu, 15 Feb 2007 14:59:49 -0800 From: Luigi Rizzo To: net@freebsd.org Message-ID: <20070215145948.B94883@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Cc: Subject: iwi freezing (RELENG_6) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Feb 2007 23:29:42 -0000 [This is a summary of something i have already discussed with other people with no solution so far. I have some more data points if that may help/ring any bell] Since an upgrade of if_iwi.c to 1.8.2.10 (before i have been running a prerelease of 1.8.2.7 which worked pretty reliably) I have been experiencing the problems described below with if_iwi on my Dell Latitude X1 laptop. I am trying to fix them, so i'd like to know if if others are seeing similar problems, and if so if they could contact me. The problems are mainly two: 1. Machine freezing. Very very frequently (7 out of 10 or more) the machine freezes solid (not even going to the debugger with ctrl-alt-esc) as soon as /etc/rc.d/netif starts and tries to setup the interface. For this i have a simple cure: adding this IWI_LOCK_DECL; + printf("%s: start\n", __func__); IWI_LOCK(sc); near the beginning of iwi_ioctl() (and maybe iwi_scanstart() ) has not caused a crash in the >20 reboots (warm&cold) done so far. Patching iwi_scanstart() alone is not enough. 2. Problem associating, reporting endlessly a BEACON MISS This happens with a particular AP which used to work fine until i did the upgrade. For this i don't have a cure yet, also because the AP is not in a convenient location. Anyone else experiencing similar problems ? More details below cheers luigi ---- DETAILED DESCRIPTION ---- 1. machine freezing. As said above, the machine freezes solid soon after netif starts. It really seems a race condition related to starting the card, as instrumenting the code with prinf, or setting debug.iwi to a high values changes things. Setting the radio off does not help. Some experiments show this to happen after iwi_scanstart() has been called 3 times. If i instrument more, the problem disappears so i cannot tell exactly where it happens, however it is before the 4th iwi_scanstart call, but no idea how it is positioned with respect to the iwi_ioctl(). One sequence i saw is this iwi_ioctl(SIOCSIFFLAGS) iwi_scanstart iwi_ioctl(SIOCS80211) iwi_scanstart iwi_ioctl(SIOCS80211) iwi_scanstart <--- freeze here iwi_ioctl(SIOCS80211) <--- freeze here <--- freeze here iwi_scanstart ... but the iwi_scanstart calls seem to be asynchronous and their position/number seem to be dependent on the presence of other access points in the area. When there are no printf and i am lucky (no hang) i see this iwi_cmd: cmd 6 not sent, busy device configuration failed and then dhcp manages to get an address. Note that the printf() in iwi_ioctl makes me never see the 'cmd 6 not sent' message. 2. Problem associating, reporting endlessly a BEACON MISS I have not investigated this in detail, but noticed that the card could not associate to a particular AP i was using just before rebooting after installing the new kernel, and constantly reporting beacin miss. Diffing the two version of the driver, my attention was caught by these threw chunks - could they have something to do with the problem ? @@ -433,6 +438,7 @@ } ieee80211_ifattach(ic); + ic->ic_bmissthreshold = 10; /* override default */ /* override default methods */ ic->ic_node_alloc = iwi_node_alloc; sc->sc_node_free = ic->ic_node_free; @@ -979,13 +972,19 @@ ieee80211_state_name[ic->ic_state], ieee80211_state_name[nstate], sc->flags)); + /* XXX state change race with taskqueue */ switch (nstate) { case IEEE80211_S_SCAN: if (ic->ic_state == IEEE80211_S_RUN) { /* * Beacon miss, send disassoc and wait for a reply - * from the card; we'll start a scan then. - */ + * from the card; we'll start a scan then. Note + * this only happens with auto roaming; otherwise + * just notify users and wait to be directed. + */ + /* notify directly as we bypass net80211 */ + ieee80211_sta_leave(ic, ic->ic_bss); + if (ic->ic_roaming == IEEE80211_ROAMING_AUTO) taskqueue_enqueue(sc->sc_tq, &sc->sc_downtask); break; } @@ -2455,6 +2585,7 @@ memset(&config, 0, sizeof config); config.bluetooth_coexistence = sc->bluetooth; + config.silence_threshold = 0x1e; config.antenna = sc->antenna; config.multicast_enabled = 1; config.answer_pbreq = (ic->ic_opmode == IEEE80211_M_IBSS) ? 1 : 0; --------------------------------------------------------------------------- From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 23:30:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6674416A400 for ; Thu, 15 Feb 2007 23:30:18 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 4208313C49D for ; Thu, 15 Feb 2007 23:30:18 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 4C34C1AFD17; Thu, 15 Feb 2007 18:30:24 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Thu, 15 Feb 2007 18:30:24 -0500 X-Sasl-enc: 8hliqX7+EGdN5+60MX7Cn2p2rG7iFq26EsRKWIsj/p2B 1171582223 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 3B75724599; Thu, 15 Feb 2007 18:30:22 -0500 (EST) Message-ID: <45D4ED06.40709@incunabulum.net> Date: Thu, 15 Feb 2007 23:30:14 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Yar Tikhiy References: <45D38AC9.50107@incunabulum.net> <20070215091309.GC20957@comp.chem.msu.su> In-Reply-To: <20070215091309.GC20957@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] Updated 802.1p/q patch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 23:30:18 -0000 Yar Tikhiy wrote: > Do you have any architectural reservations about nested VLANs in > the main network stack? Presently, a one-line patch can allow a > vlan(4) to attach to another vlan(4), but I haven't heard about the > behaviour of the resulting setup yet. > After looking around it seems there is definite scope and demand for such a feature in scenarios such as ISP Metro Ethernet setups. However, we can't rely on M_VLANTAG alone to implement it. To do it we need to be sure of the following: 1. Output path in vlan(4) changes not to call ether_output_frame() directly if nested. 2. Output path in vlan(4) detects when it's going to re-enter the parent vlan(4), and makes sure the inner 802.1q header is expanded and inserted from M_VLANTAG before passing it down the stack. 3. That the drivers and cards out there can deal with Q-in-Q. 4. That the input path only extracts and applies M_VLANTAG for the outer 802.1q header. 4. That the input path is able to reenter vlan(4) correctly on the way back up the stack; The code which produces/consumes M_VLANTAG from the 802.1q header might need to be made common. The priority field them becomes problematic. As a compromise I'd suggest the priority field in the VLAN tag is derived from the innermost 802.1q header, which will be the first M_VLANTAG which the Ethernet part of the stack sees. This gives ALTQ/RSVP/PF a chance to do its thing without complicated workarounds. BMS From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 00:49:39 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BB9C916A400 for ; Fri, 16 Feb 2007 00:49:39 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id AC5D813C481 for ; Fri, 16 Feb 2007 00:49:39 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l1G0nOb8076232; Thu, 15 Feb 2007 16:49:24 -0800 (PST) Date: Thu, 15 Feb 2007 16:49:08 -0800 Message-ID: From: gnn@freebsd.org To: Jung-uk Kim In-Reply-To: <200702151655.53581.jkim@FreeBSD.org> References: <200702141805.20228.jkim@FreeBSD.org> <200702151655.53581.jkim@FreeBSD.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.92 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: [PATCH] BPF to support directions and more X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 00:49:39 -0000 At Thu, 15 Feb 2007 16:55:51 -0500, Jung-uk Kim wrote: > > On Wednesday 14 February 2007 06:05 pm, Jung-uk Kim wrote: > > I was playing with some BPF ideas for few days and I added two new > > features. SEESENT flag is extended to see only outgoing packets, > > which is analogous to libpcap's PCAP_D_OUT direction. Thus SEESENT > > is now called DIRECTION. Second feature is feedback mode (sort of > > simulated hardware loopback), i.e., when packets are injected, you > > can feed them back as if they are coming from the wire. You can > > debug link layer protocols easily with this without second machine, > > network controller, or loopback plug. It's only tested with > > Ethernet, though. All necessary patches (including libpcap > > modification) are here: > > > > http://people.freebsd.org/~jkim/bpf_feedback.diff > > I have received some positive feedbacks and comments. So, I made some > adjustments/corrections to reflect them: > > http://people.freebsd.org/~jkim/bpf_feedback-20070215.diff Hmmm. Those would be interesting things to have working with pypcap and PCS. I will try to take a look, but I like the ideas. Best, George From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 06:41:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 76A4316A406 for ; Fri, 16 Feb 2007 06:41:16 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx2.mail.ru (mx2-2.mail.ru [194.67.23.122]) by mx1.freebsd.org (Postfix) with ESMTP id 32E7E13C4BE for ; Fri, 16 Feb 2007 06:41:15 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from [85.156.232.99] (port=61508 helo=localhost) by mx2.mail.ru with asmtp id 1HHwmM-000FAM-00; Fri, 16 Feb 2007 09:41:11 +0300 Date: Fri, 16 Feb 2007 08:41:09 +0200 To: "Luigi Rizzo" From: "V.Chukharev" Content-Type: text/plain; charset=utf-8 MIME-Version: 1.0 References: <20070215143551.A94883@xorpc.icir.org> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <20070215143551.A94883@xorpc.icir.org> User-Agent: Opera Mail/9.10 (FreeBSD) Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 06:41:16 -0000 On Fri, 16 Feb 2007 00:35:51 +0200, Luigi Rizzo wrote: > will have a look at this. > Which version of if_iwi.c are you using ? Thanks. $ grep -i __FBSDID /usr/src/sys/dev/iwi/if_iwi.c __FBSDID("$FreeBSD: src/sys/dev/iwi/if_iwi.c,v 1.8.2.12 2007/01/23 22:17:48 jhb Exp $"); It's STABLE, updated couple of days ago. > cheers > luigi > > On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote: >> Hi, >> >> It seems that iwi driver cannot survive more than just a few cycles of switching down/up. >> In a place with a bad wireless connection I needed to do that quite a number of times >> (that was the simplest way to restore connectivity I knew), and after 5-10 cycles I needed >> to reboot my notebook totally. >> >> Can anybody with iwi () confirm (or better unconfirm) >> that doing >> >> for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig iwi0 up; done >> >> always results in the following messages (and lost connectivity): >> >> Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN >> Feb 15 09:44:18 chu kernel: iwi0: device timeout >> Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory >> >> A fix for this would be even better ;)) >> >> Thanks, >> -- >> V. Chukharev >> _______________________________________________ >> 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" > -- V. Chukharev From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 10:36:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C47816A400 for ; Fri, 16 Feb 2007 10:36:32 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8E13B13C46B for ; Fri, 16 Feb 2007 10:36:31 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-235-229.51-151.net24.it [151.51.229.235]) (authenticated bits=128) by parrot.aev.net (8.13.8/8.13.8) with ESMTP id l1GAgwPT066816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Feb 2007 11:43:04 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.13.8/8.13.8) with ESMTP id l1GAabAr067339; Fri, 16 Feb 2007 11:36:37 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45D58923.1000803@netfence.it> Date: Fri, 16 Feb 2007 11:36:19 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <45D33663.9040902@netfence.it> <45D3B13A.5080700@FreeBSD.org> In-Reply-To: <45D3B13A.5080700@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 212.31.247.179 Cc: freebsd-net@freebsd.org Subject: Re: Gateway slowed down to barely usable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2007 10:36:32 -0000 Bruce M. Simpson wrote: >> Now the question is: in case this happens again, how do I find out >> what's wrong? >> CPU usage was under 2% and so was swap usage... what else could I check? >> What tools should I use? > Points for further investigation: > How long was the machine up for? A couple of days. > Exactly which network components in FreeBSD are you using? Here's my ifconfig's output: rl0: flags=8943 mtu 1500 options=8 inet 192.168.99.1 netmask 0xffffff00 broadcast 192.168.99.255 ether 00:00:e8:63:d1:25 media: Ethernet autoselect (100baseTX) status: active rl1: flags=8943 mtu 1500 options=8 inet xxx.xxx.xxx.xxx netmask 0xfffffff8 broadcast 212.31.247.183 ether 00:00:e8:63:d1:10 media: Ethernet autoselect (100baseTX ) status: active fxp0: flags=8943 mtu 1500 options=8 inet 192.168.100.201 netmask 0xffffff00 broadcast 192.168.100.255 ether 00:a0:c9:d5:33:5d media: Ethernet autoselect (100baseTX ) status: active xl0: flags=8943 mtu 1500 options=9 ether 00:50:04:0c:60:03 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 rl1 is connected to an HDSL router with a public IP; xl0 is bridged to rl1; fxp0 and rl0 are private nets which require NAT. It's working as a firewall with ipfw/natd/inetd and snort. This box is also running squid, named and DHCP server for the internal nets. > Do you have any figures on what kind of network load the machine was > dealing with? Yes, I use cacti to graph that, so what I can say is: _ most traffic goes from fxp0 through squid or natd to internet; _ the HDSL is 1Mb/s and it is frequently saturated; _ the other day, we had virtually constant 1Mb/s for about 6 hours, then the sudden performance drop. > Can you rule out problems with an intermediate switch? I don't understand; what do you mean? > Based on what you've said I can only speculate that the possible causes > are either mbuf memory fragmentation or a driver problem; both are a > total stab in the dark. WRT driver, xl0 was added at the beginning of this week, so it could be that. Is that driver known to be problematic? I've always used it on several other boxes without any problem. As for mbuf, how do I check this? (BTW I only have a rough idea of what mbufs are. Any good doc pointer?) bye av. From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 11:15:20 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9EB0E16A400 for ; Fri, 16 Feb 2007 11:15:20 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6FE3813C491 for ; Fri, 16 Feb 2007 11:15:20 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l1GBFJK3004132; Fri, 16 Feb 2007 03:15:19 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l1GBFIkc004131; Fri, 16 Feb 2007 03:15:18 -0800 (PST) (envelope-from rizzo) Date: Fri, 16 Feb 2007 03:15:18 -0800 From: Luigi Rizzo To: "V.Chukharev" Message-ID: <20070216031518.A4090@xorpc.icir.org> References: <20070215143551.A94883@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from chukharev@mail.ru on Fri, Feb 16, 2007 at 08:41:09AM +0200 Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 11:15:20 -0000 On Fri, Feb 16, 2007 at 08:41:09AM +0200, V.Chukharev wrote: > On Fri, 16 Feb 2007 00:35:51 +0200, Luigi Rizzo wrote: > > > will have a look at this. > > Which version of if_iwi.c are you using ? > > Thanks. > $ grep -i __FBSDID /usr/src/sys/dev/iwi/if_iwi.c > __FBSDID("$FreeBSD: src/sys/dev/iwi/if_iwi.c,v 1.8.2.12 2007/01/23 22:17:48 jhb Exp $"); > > It's STABLE, updated couple of days ago. ok i tried your script to do ifconfig up and down and it does not give me the problem you see (at least not until 100). Do you see the error always at the same point ? Any other things e.g. how is the iwi_bss loaded (manually, from /boot/loader or automatically) ? cheers luigi > > cheers > > luigi > > > > On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote: > >> Hi, > >> > >> It seems that iwi driver cannot survive more than just a few cycles of switching down/up. > >> In a place with a bad wireless connection I needed to do that quite a number of times > >> (that was the simplest way to restore connectivity I knew), and after 5-10 cycles I needed > >> to reboot my notebook totally. > >> > >> Can anybody with iwi () confirm (or better unconfirm) > >> that doing > >> > >> for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig iwi0 up; done > >> > >> always results in the following messages (and lost connectivity): > >> > >> Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN > >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP > >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN > >> Feb 15 09:44:18 chu kernel: iwi0: device timeout > >> Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory > >> > >> A fix for this would be even better ;)) > >> > >> Thanks, > >> -- > >> V. Chukharev > >> _______________________________________________ > >> 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" > > > > > -- > V. Chukharev From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 13:32:48 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5953416A400 for ; Fri, 16 Feb 2007 13:32:48 +0000 (UTC) (envelope-from yb@bashibuzuk.net) Received: from a.6f2.net (a.6f2.net [213.189.5.89]) by mx1.freebsd.org (Postfix) with ESMTP id 21D4F13C467 for ; Fri, 16 Feb 2007 13:32:47 +0000 (UTC) (envelope-from yb@bashibuzuk.net) Received: by a.6f2.net (Postfix, from userid 66) id EF5CDBF929E; Fri, 16 Feb 2007 14:10:40 +0100 (CET) Received: by cc.bashibuzuk.net (Postfix, from userid 1001) id C1FACBCAF; Fri, 16 Feb 2007 08:10:30 -0500 (EST) Date: Fri, 16 Feb 2007 08:10:30 -0500 From: Yann Berthier To: "V.Chukharev" Message-ID: <20070216131030.GO1255@bashibuzuk.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 13:32:48 -0000 On Thu, 15 Feb 2007, at 23:34, V.Chukharev wrote: > Hi, > > It seems that iwi driver cannot survive more than just a few cycles of switching down/up. > In a place with a bad wireless connection I needed to do that quite a number of times > (that was the simplest way to restore connectivity I knew), and after 5-10 cycles I needed > to reboot my notebook totally. > > Can anybody with iwi () confirm (or better unconfirm) > that doing > > for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig iwi0 up; done > > always results in the following messages (and lost connectivity): > > Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP > Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:18 chu kernel: iwi0: device timeout > Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory +1 - link goes down whatever the AP is after some time. ifconfig down & up works until the point i get the DMA error. While insisting i can sometimes get back connectivity (while ifconfig iwi0 | grep "no carrier"; do ifconfig iwi0 up; sleep 10; done) but after a few steps of that dance i'm left with rebooting or finding a plug. this on a T42, tracking more or less regularly -current. As far as i remember, i've "always" had this problem with this laptop / intel chip (2200BG) From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 13:35:17 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA78F16A468 for ; Fri, 16 Feb 2007 13:35:17 +0000 (UTC) (envelope-from ilja@lynx.ee) Received: from mail.lynx.ee (mail.lynx.ee [212.7.7.23]) by mx1.freebsd.org (Postfix) with ESMTP id 6387313C47E for ; Fri, 16 Feb 2007 13:35:17 +0000 (UTC) (envelope-from ilja@lynx.ee) Received: from localhost (unknown [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 641ECB90C; Fri, 16 Feb 2007 15:13:47 +0200 (EET) X-Virus-Scanned: amavisd-new at lynx.ee Received: from mail.lynx.ee ([127.0.0.1]) by localhost (pinkfloyd.lynx.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0WldJ8xCenI; Fri, 16 Feb 2007 15:13:40 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 93061B907; Fri, 16 Feb 2007 15:13:40 +0200 (EET) Received: from 84-50-157-3-dsl.est.estpak.ee (84-50-157-3-dsl.est.estpak.ee [84.50.157.3]) by secure.lynx.ee (Horde MIME library) with HTTP; Fri, 16 Feb 2007 15:13:40 +0200 Message-ID: <20070216151340.sihitp1o8wwc8404@secure.lynx.ee> Date: Fri, 16 Feb 2007 15:13:40 +0200 From: Ilja Morozov To: Luigi Rizzo References: <20070215143551.A94883@xorpc.icir.org> In-Reply-To: <20070215143551.A94883@xorpc.icir.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 13:35:17 -0000 Hi guys, today I had the same problems. src/sys/dev/iwi/if_iwi.c,v 1.8.2.12 2007/01/23 22:17:48 Quoting Luigi Rizzo : > will have a look at this. > Which version of if_iwi.c are you using ? > > =09cheers > =09luigi > > On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote: >> Hi, >> >> It seems that iwi driver cannot survive more than just a few cycles =20 >> of switching down/up. >> In a place with a bad wireless connection I needed to do that quite =20 >> a number of times >> (that was the simplest way to restore connectivity I knew), and =20 >> after 5-10 cycles I needed >> to reboot my notebook totally. >> >> Can anybody with iwi () confirm (or =20 >> better unconfirm) >> that doing >> >> for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo =20 >> ifconfig iwi0 up; done >> >> always results in the following messages (and lost connectivity): >> >> Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN >> Feb 15 09:44:18 chu kernel: iwi0: device timeout >> Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory >> >> A fix for this would be even better ;)) >> >> Thanks, >> -- >> V. Chukharev >> _______________________________________________ >> 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" > --=20 Best regards, Ilja Morozov mailto:ilja@lynx.ee Lynx Computers O"U + 372 6313 000 From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 13:35:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FA8516A46B for ; Fri, 16 Feb 2007 13:35:18 +0000 (UTC) (envelope-from ilja@lynx.ee) Received: from mail.lynx.ee (mail.lynx.ee [212.7.7.23]) by mx1.freebsd.org (Postfix) with ESMTP id D974313C4AA for ; Fri, 16 Feb 2007 13:35:17 +0000 (UTC) (envelope-from ilja@lynx.ee) Received: from localhost (unknown [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 7324DB940; Fri, 16 Feb 2007 15:33:14 +0200 (EET) X-Virus-Scanned: amavisd-new at lynx.ee Received: from mail.lynx.ee ([127.0.0.1]) by localhost (pinkfloyd.lynx.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhYXWhzxLmyv; Fri, 16 Feb 2007 15:33:05 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 9F887B92B; Fri, 16 Feb 2007 15:33:05 +0200 (EET) Received: from 84-50-157-3-dsl.est.estpak.ee (84-50-157-3-dsl.est.estpak.ee [84.50.157.3]) by secure.lynx.ee (Horde MIME library) with HTTP; Fri, 16 Feb 2007 15:33:05 +0200 Message-ID: <20070216153305.xhr6va74g8gkogsw@secure.lynx.ee> Date: Fri, 16 Feb 2007 15:33:05 +0200 From: Ilja Morozov To: Luigi Rizzo References: <20070215143551.A94883@xorpc.icir.org> <20070216031518.A4090@xorpc.icir.org> In-Reply-To: <20070216031518.A4090@xorpc.icir.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 13:35:18 -0000 as I mentioned before - I had the same problem in place with very poor =20 wifi signal. and I did also some apm suspends using "zzz" . Can =20 suspend affect it ? unfortunately I didn't make any statistics dumps or similar, because =20 was very busy and just restarted box. IBM T42 FreeBSD wind.kalakala 6.2-STABLE FreeBSD 6.2-STABLE #33: Sat Feb 10 =20 17:38:43 EET 2007 logs related to the problem: Feb 16 11:55:22 wind kernel: iwi0: link state changed to UP Feb 16 11:55:30 wind dhclient: New IP Address (iwi0): 192.168.1.101 Feb 16 11:55:30 wind dhclient: New Subnet Mask (iwi0): 255.255.255.0 Feb 16 11:55:30 wind dhclient: New Broadcast Address (iwi0): 192.168.1.255 Feb 16 11:55:30 wind dhclient: New Routers (iwi0): 192.168.1.1 Feb 16 12:01:50 wind kernel: iwi0: link state changed to DOWN Feb 16 12:01:52 wind kernel: iwi0: link state changed to UP Feb 16 12:01:52 wind dhclient: New IP Address (iwi0): 192.168.1.101 Feb 16 12:01:52 wind dhclient: New Subnet Mask (iwi0): 255.255.255.0 Feb 16 12:01:52 wind dhclient: New Broadcast Address (iwi0): 192.168.1.255 Feb 16 12:01:52 wind dhclient: New Routers (iwi0): 192.168.1.1 Feb 16 12:06:11 wind kernel: iwi0: link state changed to DOWN Feb 16 12:06:16 wind kernel: iwi0: device timeout Feb 16 12:06:16 wind kernel: iwi0: could not allocate firmware DMA memory Feb 16 12:18:39 wind su: ilja to root on /dev/ttyp1 Feb 16 12:18:56 wind kernel: iwi0: could not allocate firmware DMA memory Feb 16 12:19:27 wind last message repeated 2 times Feb 16 12:19:27 wind kernel: firmware_get: failed to load firmware =20 image iwi_bss Feb 16 12:19:27 wind kernel: iwi0: could not load firmware Feb 16 12:19:27 wind dhclient[37467]: iwi0: not found Feb 16 12:19:27 wind dhclient[37467]: exiting. Feb 16 12:19:27 wind dhclient[37468]: connection closed Feb 16 12:19:27 wind dhclient[37468]: exiting. Quoting Luigi Rizzo : > On Fri, Feb 16, 2007 at 08:41:09AM +0200, V.Chukharev wrote: >> On Fri, 16 Feb 2007 00:35:51 +0200, Luigi Rizzo wrote: >> >> > will have a look at this. >> > Which version of if_iwi.c are you using ? >> >> Thanks. >> $ grep -i __FBSDID /usr/src/sys/dev/iwi/if_iwi.c >> __FBSDID("$FreeBSD: src/sys/dev/iwi/if_iwi.c,v 1.8.2.12 2007/01/23 =20 >> 22:17:48 jhb Exp $"); >> >> It's STABLE, updated couple of days ago. > > ok i tried your script to do ifconfig up and down > and it does not give me the problem you see (at least not until 100). > Do you see the error always at the same point ? Any other things > e.g. how is the iwi_bss loaded (manually, from /boot/loader or > automatically) ? > > =09cheers > =09luigi > >> > =09cheers >> > =09luigi >> > >> > On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote: >> >> Hi, >> >> >> >> It seems that iwi driver cannot survive more than just a few =20 >> cycles of switching down/up. >> >> In a place with a bad wireless connection I needed to do that =20 >> quite a number of times >> >> (that was the simplest way to restore connectivity I knew), and =20 >> after 5-10 cycles I needed >> >> to reboot my notebook totally. >> >> >> >> Can anybody with iwi () confirm =20 >> (or better unconfirm) >> >> that doing >> >> >> >> for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; =20 >> sudo ifconfig iwi0 up; done >> >> >> >> always results in the following messages (and lost connectivity): >> >> >> >> Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN >> >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP >> >> Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN >> >> Feb 15 09:44:18 chu kernel: iwi0: device timeout >> >> Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memo= ry >> >> >> >> A fix for this would be even better ;)) >> >> >> >> Thanks, >> >> -- >> >> V. Chukharev >> >> _______________________________________________ >> >> 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 Best regards, Ilja Morozov From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 16:06:45 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF1ED16A401 for ; Fri, 16 Feb 2007 16:06:45 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx2.mail.ru (mx2-2.mail.ru [194.67.23.122]) by mx1.freebsd.org (Postfix) with ESMTP id 7B32513C48E for ; Fri, 16 Feb 2007 16:06:43 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from [130.230.40.65] (port=49482 helo=localhost) by mx2.mail.ru with asmtp id 1HI5bd-0003FX-00; Fri, 16 Feb 2007 19:06:41 +0300 Date: Fri, 16 Feb 2007 18:06:40 +0200 To: "Luigi Rizzo" From: "V.Chukharev" Content-Type: text/plain; charset=utf-8 MIME-Version: 1.0 References: <20070215143551.A94883@xorpc.icir.org> <20070216031518.A4090@xorpc.icir.org> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <20070216031518.A4090@xorpc.icir.org> User-Agent: Opera Mail/9.10 (FreeBSD) Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 16:06:45 -0000 On Fri, 16 Feb 2007 13:15:18 +0200, Luigi Rizzo wrote: > ok i tried your script to do ifconfig up and down > and it does not give me the problem you see (at least not until 100). > Do you see the error always at the same point ? Any other things > e.g. how is the iwi_bss loaded (manually, from /boot/loader or > automatically) ? I have the following two lines in /etc/rc.conf. ifconfig_iwi0=3Ddhcp iwi_enable=3D"YES" My /boot/loader.conf is #agp_load=3D"YES" acpi_video_load=3D"YES" atapicam_load=3D"YES" cpufreq_load=3D"YES" if_iwi_load=3D"YES" wlan_load=3D"YES" firmware_load=3D"YES" snd_ich_load=3D"YES" sound_load=3D"YES" kern.maxfiles=3D"25000" I cannot find anything else about iwi... > cheers > luigi > -- = V. Chukharev From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 16:17:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1718C16A402 for ; Fri, 16 Feb 2007 16:17:38 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id F35D513C474 for ; Fri, 16 Feb 2007 16:17:37 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l1GGHbRa007843; Fri, 16 Feb 2007 08:17:37 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l1GGHbkO007842; Fri, 16 Feb 2007 08:17:37 -0800 (PST) (envelope-from rizzo) Date: Fri, 16 Feb 2007 08:17:37 -0800 From: Luigi Rizzo To: "V.Chukharev" Message-ID: <20070216081737.A7793@xorpc.icir.org> References: <20070215143551.A94883@xorpc.icir.org> <20070216031518.A4090@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from chukharev@mail.ru on Fri, Feb 16, 2007 at 06:06:40PM +0200 Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 16:17:38 -0000 On Fri, Feb 16, 2007 at 06:06:40PM +0200, V.Chukharev wrote: > On Fri, 16 Feb 2007 13:15:18 +0200, Luigi Rizzo wrote: > > > ok i tried your script to do ifconfig up and down > > and it does not give me the problem you see (at least not until 100). > > Do you see the error always at the same point ? Any other things > > e.g. how is the iwi_bss loaded (manually, from /boot/loader or > > automatically) ? > > I have the following two lines in /etc/rc.conf. > ifconfig_iwi0=dhcp > iwi_enable="YES" > > My /boot/loader.conf is > #agp_load="YES" > acpi_video_load="YES" > atapicam_load="YES" > cpufreq_load="YES" > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > snd_ich_load="YES" > sound_load="YES" > kern.maxfiles="25000" > > I cannot find anything else about iwi... ok doesn't seem to have anything strange, nor there seem to be any memory leak in iwi_init_locked... will keep the problem in mind, but right now i have no ideas on what could happen. cheers luigi From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 16:32:12 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A50116A401 for ; Fri, 16 Feb 2007 16:32:12 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 70E7913C441 for ; Fri, 16 Feb 2007 16:32:12 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 4E80C1AFEB8 for ; Fri, 16 Feb 2007 11:32:27 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Fri, 16 Feb 2007 11:32:27 -0500 X-Sasl-enc: l4WTougkaA4W59LV6lVv8jVBzeN8nCAQ6duQwvlXNThA 1171643546 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id DBF06BA62 for ; Fri, 16 Feb 2007 11:32:26 -0500 (EST) Message-ID: <45D5DC8A.8080300@incunabulum.net> Date: Fri, 16 Feb 2007 16:32:10 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Recommendations for OSPF v3 book? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 16:32:12 -0000 Does anyone have any good suggestions for a book which discusses OSPF v3 architecture? I have read the original John Moy book 'OSPF: Anatomy of an Internet routing protocol' but would very much like to know of there is a good text out there which discusses OSPF in the wider context of IPv6 and the improvements made in version 3 of the protocol. I should be most grateful for your suggestions. Kind regards, BMS From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 16:38:46 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F6A916A401 for ; Fri, 16 Feb 2007 16:38:46 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by mx1.freebsd.org (Postfix) with ESMTP id 32E0B13C4AA for ; Fri, 16 Feb 2007 16:38:46 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.66.10.54] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1HI66W1vsO-0003DA; Fri, 16 Feb 2007 17:38:37 +0100 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Fri, 16 Feb 2007 17:38:28 +0100 User-Agent: KMail/1.9.5 References: <20070216081737.A7793@xorpc.icir.org> In-Reply-To: <20070216081737.A7793@xorpc.icir.org> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1553602.urpBlFFFDJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200702161738.35142.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 X-Provags-ID2: V01U2FsdGVkX19uxmb5k7Fobao5sPDURlrfN+ZkofkG1kI4D/v6Ibage4HFAAIFAoibb+AUEAnUIEA7Ce9hhL/0C4aym9ZgC4ytZFPPaAq/B6JUdn3CmU5lAQ== Cc: Luigi Rizzo , "V.Chukharev" Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 16:38:46 -0000 --nextPart1553602.urpBlFFFDJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 16 February 2007 17:17, Luigi Rizzo wrote: > On Fri, Feb 16, 2007 at 06:06:40PM +0200, V.Chukharev wrote: > > On Fri, 16 Feb 2007 13:15:18 +0200, Luigi Rizzo =20 wrote: > > > ok i tried your script to do ifconfig up and down > > > and it does not give me the problem you see (at least not until > > > 100). Do you see the error always at the same point ? Any other > > > things e.g. how is the iwi_bss loaded (manually, from /boot/loader > > > or automatically) ? > > > > I have the following two lines in /etc/rc.conf. > > ifconfig_iwi0=3Ddhcp > > iwi_enable=3D"YES" > > > > My /boot/loader.conf is > > #agp_load=3D"YES" > > acpi_video_load=3D"YES" > > atapicam_load=3D"YES" > > cpufreq_load=3D"YES" > > if_iwi_load=3D"YES" > > wlan_load=3D"YES" > > firmware_load=3D"YES" > > snd_ich_load=3D"YES" > > sound_load=3D"YES" > > kern.maxfiles=3D"25000" > > > > I cannot find anything else about iwi... > > ok doesn't seem to have anything strange, nor there > seem to be any memory leak in iwi_init_locked... > > will keep the problem in mind, but right now i have no > ideas on what could happen. I'm under the impression that this is more a problem of increasing=20 fragmentation until we can't get a big enough unfragmented chunk. I=20 don't have any proof of this assumption yet. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1553602.urpBlFFFDJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBF1d4LXyyEoT62BG0RAm+/AJ9OV+bVW4gtDjs67yq4lzaJs/dkuwCePAsg KODe82cB+VLjQQi1JKlKkfU= =Bgd/ -----END PGP SIGNATURE----- --nextPart1553602.urpBlFFFDJ-- From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 16:51:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD13C16A401 for ; Fri, 16 Feb 2007 16:51:32 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 93FDD13C467 for ; Fri, 16 Feb 2007 16:51:32 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l1GGpWC8008205; Fri, 16 Feb 2007 08:51:32 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l1GGpW6k008204; Fri, 16 Feb 2007 08:51:32 -0800 (PST) (envelope-from rizzo) Date: Fri, 16 Feb 2007 08:51:32 -0800 From: Luigi Rizzo To: Max Laier Message-ID: <20070216085132.A7944@xorpc.icir.org> References: <20070216081737.A7793@xorpc.icir.org> <200702161738.35142.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200702161738.35142.max@love2party.net>; from max@love2party.net on Fri, Feb 16, 2007 at 05:38:28PM +0100 Cc: freebsd-net@freebsd.org, "V.Chukharev" Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 16:51:32 -0000 On Fri, Feb 16, 2007 at 05:38:28PM +0100, Max Laier wrote: ... > I'm under the impression that this is more a problem of increasing > fragmentation until we can't get a big enough unfragmented chunk. I > don't have any proof of this assumption yet. makes sense. As a matter of fact i wonder whether it wouldn't be smarter to allocate the dma-ble memory on the first request and keep it around until the driver is unloaded. If i read the code in iwi_load_firmware() correctly, the contiguous chunks cannot be longer than 8191 bytes, so a single contiguous buffer is not mandatory. I just don't know if we can write the firmware to the adapter with multiple operations (lists of command blocks) or it needs to be just a single list ? cheers luigi From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 17:12:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F124616A406 for ; Fri, 16 Feb 2007 17:12:18 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id D7B3D13C441 for ; Fri, 16 Feb 2007 17:12:18 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id C95C85B52; Fri, 16 Feb 2007 08:46:32 -0800 (PST) To: Luigi Rizzo In-reply-to: Your message of "Fri, 16 Feb 2007 08:17:37 PST." <20070216081737.A7793@xorpc.icir.org> Date: Fri, 16 Feb 2007 08:46:32 -0800 From: Bakul Shah Message-Id: <20070216164632.C95C85B52@mail.bitblocks.com> Cc: freebsd-net@freebsd.org, "V.Chukharev" Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 17:12:19 -0000 > ok doesn't seem to have anything strange, nor there > seem to be any memory leak in iwi_init_locked... > > will keep the problem in mind, but right now i have no > ideas on what could happen. One data point: when I see a iwi0: could not allocate firmware DMA memory I close memory hog programs one by one and ultimately iwi manages to find memory. My guess is it needs contiguous physical memory and normally memory gets very fragmented and may be by killing enough programs somehow enough physmem is found to be free? No idea if firmware loading can be made smarter. From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 17:19:38 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A649E16A401 for ; Fri, 16 Feb 2007 17:19:38 +0000 (UTC) (envelope-from cjeker@diehard.n-r-g.com) Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) by mx1.freebsd.org (Postfix) with ESMTP id 4353B13C428 for ; Fri, 16 Feb 2007 17:19:38 +0000 (UTC) (envelope-from cjeker@diehard.n-r-g.com) Received: (qmail 25040 invoked by uid 1001); 16 Feb 2007 16:52:56 -0000 Date: Fri, 16 Feb 2007 17:52:56 +0100 From: Claudio Jeker To: freebsd-net@freebsd.org Message-ID: <20070216165256.GD14190@diehard.n-r-g.com> Mail-Followup-To: Claudio Jeker , freebsd-net@freebsd.org References: <45D5DC8A.8080300@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45D5DC8A.8080300@incunabulum.net> User-Agent: Mutt/1.5.12-2006-07-14 Subject: Re: Recommendations for OSPF v3 book? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 17:19:38 -0000 On Fri, Feb 16, 2007 at 04:32:10PM +0000, Bruce M Simpson wrote: > Does anyone have any good suggestions for a book which discusses OSPF v3 > architecture? > > I have read the original John Moy book 'OSPF: Anatomy of an Internet > routing protocol' but would very much like to know of there is a good > text out there which discusses OSPF in the wider context of IPv6 and the > improvements made in version 3 of the protocol. > > I should be most grateful for your suggestions. > I documented OpenOSPFD for EuroBSDCon 05 -- paper on http://www.networx.ch/ but honestly I have not seen a good OSPFv3 book. -- :wq Claudio From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 18:12:04 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4AFBD16A402 for ; Fri, 16 Feb 2007 18:12:04 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id D6D7F13C4A7 for ; Fri, 16 Feb 2007 18:12:03 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65]) by postfix2-g20.free.fr (Postfix) with ESMTP id E9FBDB0E0F3 for ; Fri, 16 Feb 2007 17:42:29 +0100 (CET) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp8-g19.free.fr (Postfix) with ESMTP id 9FE125613; Fri, 16 Feb 2007 18:42:18 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id F0F699D41F; Fri, 16 Feb 2007 17:43:17 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id DEA6C405D; Fri, 16 Feb 2007 18:43:17 +0100 (CET) Date: Fri, 16 Feb 2007 18:43:17 +0100 From: Jeremie Le Hen To: "V.Chukharev" Message-ID: <20070216174317.GZ64768@obiwan.tataz.chchile.org> References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="vni90+aGYgRvsTuO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org, cognet@FreeBSD.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 18:12:04 -0000 --vni90+aGYgRvsTuO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, On Thu, Feb 15, 2007 at 11:34:48PM +0200, V.Chukharev wrote: > Hi, > > It seems that iwi driver cannot survive more than just a few cycles > of switching down/up. > In a place with a bad wireless connection I needed to do that quite > a number of times > (that was the simplest way to restore connectivity I knew), and after > 5-10 cycles I needed > to reboot my notebook totally. > > Can anybody with iwi () confirm (or > better unconfirm) > that doing > > for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig iwi0 up; done > > always results in the following messages (and lost connectivity): > > Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP > Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:18 chu kernel: iwi0: device timeout > Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory > > A fix for this would be even better ;)) cognet@ has once provided me a tiny hack to the iwi(4) driver and I never get such errors. Maybe I'm not suffering enough UP/DOWN cycles to trigger it, but it might be worth trying it. Note that he has insisted that this is a *hack*. The patch is attached. Please let us know if it makes things better. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > --vni90+aGYgRvsTuO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_iwi.c.patch" Index: if_iwi.c =================================================================== RCS file: /home/ncvs/src/sys/dev/iwi/if_iwi.c,v retrieving revision 1.45 diff -u -p -r1.45 if_iwi.c --- if_iwi.c 2 Feb 2007 05:17:18 -0000 1.45 +++ if_iwi.c 16 Feb 2007 17:40:33 -0000 @@ -512,6 +512,12 @@ iwi_detach(device_t dev) if (sc->mem != NULL) bus_release_resource(dev, SYS_RES_MEMORY, sc->mem_rid, sc->mem); + if (sc->fw_map) + bus_dmamap_unload(sc->fw_dmat, sc->fw_map); + if (sc->fw_virtaddr != 0) + bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); + if (sc->fw_dmat) + bus_dma_tag_destroy(sc->fw_dmat); if (ifp != NULL) if_free(ifp); @@ -3085,6 +3091,7 @@ iwi_init_locked(void *priv, int force) struct ifnet *ifp = ic->ic_ifp; struct iwi_rx_data *data; int i; + int must_realloc = 0; IWI_LOCK_DECL; if (sc->flags & IWI_FLAG_FW_LOADING) @@ -3106,14 +3113,27 @@ iwi_init_locked(void *priv, int force) } /* allocate DMA memory for mapping firmware image */ - if (sc->fw_boot.size > sc->fw_dma_size) + if (sc->fw_boot.size > sc->fw_dma_size) { + must_realloc = 1; sc->fw_dma_size = sc->fw_boot.size; - if (sc->fw_fw.size > sc->fw_dma_size) + } + if (sc->fw_fw.size > sc->fw_dma_size) { + must_realloc = 1; sc->fw_dma_size = sc->fw_fw.size; - if (sc->fw_uc.size > sc->fw_dma_size) + } + if (sc->fw_uc.size > sc->fw_dma_size) { sc->fw_dma_size = sc->fw_uc.size; + must_realloc = 1; + } + if (must_realloc && sc->fw_virtaddr != 0) { + bus_dmamap_sync(sc->fw_dmat, sc->fw_map, BUS_DMASYNC_POSTWRITE); + bus_dmamap_unload(sc->fw_dmat, sc->fw_map); + bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); + bus_dma_tag_destroy(sc->fw_dmat); + } - if (bus_dma_tag_create(bus_get_dma_tag(sc->sc_dev), 4, 0, + if (must_realloc && + bus_dma_tag_create(bus_get_dma_tag(sc->sc_dev), 4, 0, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, NULL, sc->fw_dma_size, 1, sc->fw_dma_size, 0, NULL, NULL, &sc->fw_dmat) != 0) { @@ -3122,14 +3142,16 @@ iwi_init_locked(void *priv, int force) IWI_LOCK(sc); goto fail; } - if (bus_dmamem_alloc(sc->fw_dmat, &sc->fw_virtaddr, 0, + if (must_realloc && + bus_dmamem_alloc(sc->fw_dmat, &sc->fw_virtaddr, 0, &sc->fw_map) != 0) { device_printf(sc->sc_dev, "could not allocate firmware DMA memory\n"); IWI_LOCK(sc); goto fail2; } - if (bus_dmamap_load(sc->fw_dmat, sc->fw_map, sc->fw_virtaddr, + if (must_realloc && + bus_dmamap_load(sc->fw_dmat, sc->fw_map, sc->fw_virtaddr, sc->fw_dma_size, iwi_dma_map_addr, &sc->fw_physaddr, 0) != 0) { device_printf(sc->sc_dev, "could not load firmware DMA map\n"); IWI_LOCK(sc); @@ -3185,11 +3207,6 @@ iwi_init_locked(void *priv, int force) } sc->flags |= IWI_FLAG_FW_INITED; - bus_dmamap_sync(sc->fw_dmat, sc->fw_map, BUS_DMASYNC_POSTWRITE); - bus_dmamap_unload(sc->fw_dmat, sc->fw_map); - bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); - bus_dma_tag_destroy(sc->fw_dmat); - if (iwi_config(sc) != 0) { device_printf(sc->sc_dev, "device configuration failed\n"); goto fail; @@ -3218,6 +3235,7 @@ fail4: bus_dmamap_sync(sc->fw_dmat, sc-> fail3: bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); fail2: bus_dma_tag_destroy(sc->fw_dmat); fail: ifp->if_flags &= ~IFF_UP; + sc->fw_virtaddr = 0; sc->flags &= ~IWI_FLAG_FW_LOADING; iwi_stop(sc); iwi_put_firmware(sc); --vni90+aGYgRvsTuO-- From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 21:10:27 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D124616A407; Fri, 16 Feb 2007 21:10:27 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx2.mail.ru (mx2-2.mail.ru [194.67.23.122]) by mx1.freebsd.org (Postfix) with ESMTP id 8BD8813C461; Fri, 16 Feb 2007 21:10:27 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from [85.156.232.99] (port=61667 helo=localhost) by mx2.mail.ru with asmtp id 1HIALa-0003wT-00; Sat, 17 Feb 2007 00:10:26 +0300 Date: Fri, 16 Feb 2007 23:10:24 +0200 To: "Jeremie Le Hen" From: "V.Chukharev" Content-Type: text/plain; charset=utf-8 MIME-Version: 1.0 References: <20070216174317.GZ64768@obiwan.tataz.chchile.org> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <20070216174317.GZ64768@obiwan.tataz.chchile.org> User-Agent: Opera Mail/9.10 (FreeBSD) Cc: freebsd-net@freebsd.org, cognet@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 21:10:27 -0000 On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen wrote: > Hi, > > cognet@ has once provided me a tiny hack to the iwi(4) driver and > I never get such errors. Maybe I'm not suffering enough UP/DOWN > cycles to trigger it, but it might be worth trying it. > > Note that he has insisted that this is a *hack*. > > The patch is attached. Please let us know if it makes things > better. I cannot apply the patch ;-( It seems it's for CURRENT, and I run STABLE. > Regards, All the best, -- V. Chukharev From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 23:41:39 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 885EC16A400 for ; Fri, 16 Feb 2007 23:41:39 +0000 (UTC) (envelope-from doginou@dong.ci0.org) Received: from dong.ci0.org (cognet.ci0.org [80.65.224.102]) by mx1.freebsd.org (Postfix) with ESMTP id 47A4913C441 for ; Fri, 16 Feb 2007 23:41:38 +0000 (UTC) (envelope-from doginou@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.7/8.13.4) with ESMTP id l1GNNuSw083575; Sat, 17 Feb 2007 00:23:56 +0100 (CET) (envelope-from doginou@dong.ci0.org) Received: (from doginou@localhost) by dong.ci0.org (8.13.8/8.13.8/Submit) id l1GNNtZ8083574; Sat, 17 Feb 2007 00:23:55 +0100 (CET) (envelope-from doginou) Date: Sat, 17 Feb 2007 00:23:55 +0100 From: Olivier Houchard To: "V.Chukharev" Message-ID: <20070216232355.GA83548@ci0.org> References: <20070216174317.GZ64768@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Cc: freebsd-net@freebsd.org, Jeremie Le Hen Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2007 23:41:39 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Feb 16, 2007 at 11:10:24PM +0200, V.Chukharev wrote: > On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen wrote: > > > Hi, > > > > cognet@ has once provided me a tiny hack to the iwi(4) driver and > > I never get such errors. Maybe I'm not suffering enough UP/DOWN > > cycles to trigger it, but it might be worth trying it. > > > > Note that he has insisted that this is a *hack*. > > > > The patch is attached. Please let us know if it makes things > > better. > > I cannot apply the patch ;-( > It seems it's for CURRENT, and I run STABLE. > Hi, I regenerated the patch against STABLE. Beware however, I didn't test it, only compile-test it, as I have no such hardware. Cheers, Olivier --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_iwi.stable.diff" Index: dev/iwi/if_iwi.c =================================================================== RCS file: /cognet/ncvs/src/sys/dev/iwi/if_iwi.c,v retrieving revision 1.8.2.12 diff -u -p -r1.8.2.12 if_iwi.c --- dev/iwi/if_iwi.c 23 Jan 2007 22:17:48 -0000 1.8.2.12 +++ dev/iwi/if_iwi.c 16 Feb 2007 22:53:39 -0000 @@ -511,6 +511,12 @@ iwi_detach(device_t dev) if (sc->mem != NULL) bus_release_resource(dev, SYS_RES_MEMORY, sc->mem_rid, sc->mem); + if (sc->fw_map) + bus_dmamap_unload(sc->fw_dmat, sc->fw_map); + if (sc->fw_virtaddr != 0) + bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); + if (sc->fw_dmat) + bus_dma_tag_destroy(sc->fw_dmat); if (ifp != NULL) if_free(ifp); @@ -3079,6 +3085,7 @@ iwi_init_locked(void *priv, int force) struct ifnet *ifp = ic->ic_ifp; struct iwi_rx_data *data; int i; + int must_realloc = 0; IWI_LOCK_DECL; if (sc->flags & IWI_FLAG_FW_LOADING) @@ -3100,14 +3107,26 @@ iwi_init_locked(void *priv, int force) } /* allocate DMA memory for mapping firmware image */ - if (sc->fw_boot.size > sc->fw_dma_size) + if (sc->fw_boot.size > sc->fw_dma_size) { + must_realloc = 1; sc->fw_dma_size = sc->fw_boot.size; - if (sc->fw_fw.size > sc->fw_dma_size) + } + if (sc->fw_fw.size > sc->fw_dma_size) { + must_realloc = 1; sc->fw_dma_size = sc->fw_fw.size; - if (sc->fw_uc.size > sc->fw_dma_size) + } + if (sc->fw_uc.size > sc->fw_dma_size) { + must_realloc = 1; sc->fw_dma_size = sc->fw_uc.size; - - if (bus_dma_tag_create(NULL, 4, 0, BUS_SPACE_MAXADDR_32BIT, + } + if (must_realloc && sc->fw_virtaddr != 0) { + bus_dmamap_sync(sc->fw_dmat, sc->fw_map, BUS_DMASYNC_POSTWRITE); + bus_dmamap_unload(sc->fw_dmat, sc->fw_map); + bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); + bus_dma_tag_destroy(sc->fw_dmat); + } + if (must_realloc && + bus_dma_tag_create(NULL, 4, 0, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, NULL, sc->fw_dma_size, 1, sc->fw_dma_size, 0, NULL, NULL, &sc->fw_dmat) != 0) { device_printf(sc->sc_dev, @@ -3115,14 +3134,16 @@ iwi_init_locked(void *priv, int force) IWI_LOCK(sc); goto fail; } - if (bus_dmamem_alloc(sc->fw_dmat, &sc->fw_virtaddr, 0, + if (must_realloc && + bus_dmamem_alloc(sc->fw_dmat, &sc->fw_virtaddr, 0, &sc->fw_map) != 0) { device_printf(sc->sc_dev, "could not allocate firmware DMA memory\n"); IWI_LOCK(sc); goto fail2; } - if (bus_dmamap_load(sc->fw_dmat, sc->fw_map, sc->fw_virtaddr, + if (must_realloc && + bus_dmamap_load(sc->fw_dmat, sc->fw_map, sc->fw_virtaddr, sc->fw_dma_size, iwi_dma_map_addr, &sc->fw_physaddr, 0) != 0) { device_printf(sc->sc_dev, "could not load firmware DMA map\n"); IWI_LOCK(sc); @@ -3178,11 +3199,6 @@ iwi_init_locked(void *priv, int force) } sc->flags |= IWI_FLAG_FW_INITED; - bus_dmamap_sync(sc->fw_dmat, sc->fw_map, BUS_DMASYNC_POSTWRITE); - bus_dmamap_unload(sc->fw_dmat, sc->fw_map); - bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); - bus_dma_tag_destroy(sc->fw_dmat); - if (iwi_config(sc) != 0) { device_printf(sc->sc_dev, "device configuration failed\n"); goto fail; @@ -3211,6 +3227,7 @@ fail4: bus_dmamap_sync(sc->fw_dmat, sc-> fail3: bus_dmamem_free(sc->fw_dmat, sc->fw_virtaddr, sc->fw_map); fail2: bus_dma_tag_destroy(sc->fw_dmat); fail: ifp->if_flags &= ~IFF_UP; + sc->fw_virtaddr = 0; sc->flags &= ~IWI_FLAG_FW_LOADING; iwi_stop(sc); iwi_put_firmware(sc); --r5Pyd7+fXNt84Ff3-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 13:29:19 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 937C916A400; Sat, 17 Feb 2007 13:29:19 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx2.mail.ru (mx2-2.mail.ru [194.67.23.122]) by mx1.freebsd.org (Postfix) with ESMTP id 49F6A13C441; Sat, 17 Feb 2007 13:29:18 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from [85.156.232.99] (port=63353 helo=localhost) by mx2.mail.ru with asmtp id 1HIPbe-0001m7-00; Sat, 17 Feb 2007 16:28:02 +0300 Date: Sat, 17 Feb 2007 15:27:37 +0200 To: "Jeremie Le Hen" From: "V.Chukharev" Content-Type: text/plain; charset=utf-8 MIME-Version: 1.0 References: <20070216174317.GZ64768@obiwan.tataz.chchile.org> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: User-Agent: Opera Mail/9.10 (FreeBSD) Cc: freebsd-net@freebsd.org, cognet@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 13:29:19 -0000 On Fri, 16 Feb 2007 23:10:24 +0200, V.Chukharev wrote: > On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen wrote: > >> Hi, >> >> cognet@ has once provided me a tiny hack to the iwi(4) driver and >> I never get such errors. Maybe I'm not suffering enough UP/DOWN >> cycles to trigger it, but it might be worth trying it. >> >> Note that he has insisted that this is a *hack*. >> >> The patch is attached. Please let us know if it makes things >> better. > > I cannot apply the patch ;-( > It seems it's for CURRENT, and I run STABLE. I applyed the patch regenerated by Oliver against STABLE (I did not recieve the message, found it on the list archive, that's the reason for replying to myself). Yes, the patch helps. The driver did not complain after 100 down/up cycles. Before the patch, it started to complain usually after 6..8 cycles. >> Regards, > > All the best, Thanks! -- V. Chukharev From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 13:46:48 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E0C916A401 for ; Sat, 17 Feb 2007 13:46:48 +0000 (UTC) (envelope-from j.witteveen@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by mx1.freebsd.org (Postfix) with ESMTP id 195F913C481 for ; Sat, 17 Feb 2007 13:46:47 +0000 (UTC) (envelope-from j.witteveen@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so1343159nzh for ; Sat, 17 Feb 2007 05:46:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lnAtan8SOOlt0wZy5FINmbmxRrUrHgvP0kOevrIZ0NgnEfDvIpKdEbNG+KFlPbC/1A6bv4K+NDltxx0yCODKOs0DDfTb7Yl1QavvVobuSrSs1u+UTrWR87TdtzZeSgg0uZu8BSix778PKXHaiENIkZwsVu7NZrqf4m3zRAZvHQU= Received: by 10.114.95.1 with SMTP id s1mr2343040wab.1171720007140; Sat, 17 Feb 2007 05:46:47 -0800 (PST) Received: by 10.114.12.1 with HTTP; Sat, 17 Feb 2007 05:46:47 -0800 (PST) Message-ID: <3993a4980702170546t7f9384eaq358986a4cc734582@mail.gmail.com> Date: Sat, 17 Feb 2007 14:46:47 +0100 From: "Jouke Witteveen" To: "Bruce M. Simpson" In-Reply-To: <45C7A1F9.20306@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3993a4980702051233u10c30575kd1f6d27fcd600110@mail.gmail.com> <45C7A1F9.20306@FreeBSD.org> Cc: freebsd-net@freebsd.org Subject: Re: ioctl: SIOCADDMULTI (howto?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 13:46:48 -0000 On 2/5/07, Bruce M. Simpson wrote: > Jouke Witteveen wrote: > > Hello all, > > > > I'm in need of some information on how to utilize SIOCADDMULTI. It is > > supposed to be demonstrated by the mtest [1] program, but that doesn't > > do anything (on an SIOCDELMULTI rn it appears nothing was added: > > ENOENT), At least not for the values I tested, 1.80.c2.0.0.1 in > > particular. I presume it doesn't work because the program has not been > > revised in 3 years and revision 1.4 notes that it might not work. > > If this ioctl is depricated then please tell me what is the best way > > to receive multicast messages from the 01.80.c2.00.00.0x (802.1) > > range? It is ofcourse possible to go into ALLMULTI-mode and check on > > all datagrams, but the NIC's I use are suited with a very nice > > hardware filter (21143 chip) that should be able to do this more > > effectively. Anyway, I believe Linux still programs the hardware > > filter through SIOCADDMULTI so is a bit easier on this. > > I tracked down the source from the ioctl call to the network driver > > for some time now and could find no obvious fault, except for quite > > much casting, and inconsistent use of types (checks happen on all > > sorts of casts: socket, sokcet_dl, multiaddr, ...). > It's quite possible that path is broken, as hardly anyone else out there > needs to directly join a link-layer multicast group, and there is no > regression test for it. > > The IP paths are known to work A-OK. If you didn't have code hooked up > to ether_demux() to see this traffic, you'd never see it in userland anyway. > > As such, it's not a priority for me to fix , but will try to help anyway. > > Are there specific performance constraints for your app? If not you > should just be able to use pcap (or bpf) to get the traffic. Admittedly > this is a performance hit, but with the optimization work on bpf and > ever more powerful CPUs, this shouldn't be a big issue. > > You can write a regression test for this though with getifmaddrs(). > > anglepoise:~/head/src/sys/net % s mtest > Password: > multicast membership test program; enter ? for list of commands > a fxp0 01.80.c2.00.00.02 > ether address added > > should yield route -nv monitor output > > got message of size 128 on Mon Feb 5 21:23:57 2007 > RTM_NEWMADDR: new multicast group membership on iface: len 128, > sockaddrs: > fxp0:0.90.27.59.40.2c 1.80.c2.0.0.2 > > Of course, netstat -g won't show you this, because it's concerned with > IP/IPv6 only. > netstat -ian should however tell you which link-layer multicast > addresses are configured. > > When I add an ethernet multicast address manually with mtest, I see > vmstat -m | grep ether_multi increment as I'd expect. > > It looks like there may be a missing piece somewhere. The code which I > see is OK but the results aren't as I'd expect. I am quite tired at the > moment so I may be way off. > > Regards, > BMS > Further investigation showed that the address gets to the driver just fine. I also saw with tcpdump that it actualy works: with `tcpdump -i dc0 -p multicast` I could see traffic that I didn't see when I hadn't added the multicast address. So my apologies for suggesting it doesn't work at all; it seems that the application I'm trying to get to work (wpa_supplicant for wired interfaces) just doesn't _send_ its packets the right way. Things aren't perfect though. In if.c the if_findmulti function is broken (always returns NULL). I presume just comparing the *LLADDR((sockaddr *)sa) data on both sockets is a better check, though my knowledge on these things is limited. As for netstat, I do not really know what is keeping it from showing the Multicast addresses. Again: my knowledge on this matter is limited. All I can think of is that getifmaddrs is forgetting something (perhaps the lack of a group membership). Maybe you can take a look at it (I believe you wrote it). As I am still learning how best to contribute to a project as big as FreeBSD and I do not think I am skilled enough yet in C I refrain from writing a patch. I am eager to see one though, be it only out of curiosity to know what would be considered a proper fix. I hope someone can find a spare minute to look at if_findmulti. It would help me quite much. Kind regards, - Jouke From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 13:55:01 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3058616A400; Sat, 17 Feb 2007 13:55:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by mx1.freebsd.org (Postfix) with ESMTP id A75BF13C428; Sat, 17 Feb 2007 13:55:00 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.66.18.208] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis), id 0ML29c-1HIQ1i1BLg-0000og; Sat, 17 Feb 2007 14:54:59 +0100 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Sat, 17 Feb 2007 14:54:49 +0100 User-Agent: KMail/1.9.5 References: In-Reply-To: X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1253199.JX7CTxXP58"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200702171454.57301.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 X-Provags-ID2: V01U2FsdGVkX19+EaM7usMvsfwMyhQ6/ts5jD5SLaqdHPsgHJfS4lJlP5pOwV0+YVh+xGUM3Omqgiqawy+qGYvGTn0Dh6sBmzwddtGE5icbnaNQOP87CFA6eg== Cc: Jeremie Le Hen , "V.Chukharev" , cognet@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 13:55:01 -0000 --nextPart1253199.JX7CTxXP58 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 17 February 2007 14:27, V.Chukharev wrote: > On Fri, 16 Feb 2007 23:10:24 +0200, V.Chukharev =20 wrote: > > On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen=20 wrote: > >> Hi, > >> > >> cognet@ has once provided me a tiny hack to the iwi(4) driver and > >> I never get such errors. Maybe I'm not suffering enough UP/DOWN > >> cycles to trigger it, but it might be worth trying it. > >> > >> Note that he has insisted that this is a *hack*. > >> > >> The patch is attached. Please let us know if it makes things > >> better. > > > > I cannot apply the patch ;-( > > It seems it's for CURRENT, and I run STABLE. > > I applyed the patch regenerated by Oliver against STABLE (I did not > recieve the message, found it on the list archive, that's the reason > for replying to myself). > > Yes, the patch helps. The driver did not complain after 100 down/up > cycles. Before the patch, it started to complain usually after 6..8 > cycles. Okay ... this confirms that this is a problem with memory fragmentation. =20 It seems that keeping the DMA'able memory around is indeed the best thing=20 we can do. As long as the firmware is as (un)reliable as it is now there=20 is no way around the casual reset. For normal operation it seems best to=20 store the bss firmware in the DMA'able memory and keep it there. That=20 lets us firmware_put() the image itself. I will have a patch later=20 today, unless somebody disagrees and/or has a better idea. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1253199.JX7CTxXP58 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBF1wkxXyyEoT62BG0RAh6SAJ9gdR9Q94z5AgFfeVdaXr7mljR1YQCeJpAX 5jmQdiUpGWv5ukNgC7eZXtA= =tCrH -----END PGP SIGNATURE----- --nextPart1253199.JX7CTxXP58-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 18:26:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6319616A401 for ; Sat, 17 Feb 2007 18:26:16 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 21E5D13C441 for ; Sat, 17 Feb 2007 18:26:16 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 13ACD1AFFAD; Sat, 17 Feb 2007 13:26:44 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Sat, 17 Feb 2007 13:26:44 -0500 X-Sasl-enc: vVKd532SPQGnNyPaxFqLUeVhxAq5DE/0ngYcHKm93QYX 1171736803 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 486432AD17; Sat, 17 Feb 2007 13:26:43 -0500 (EST) Message-ID: <45D748C5.6040904@FreeBSD.org> Date: Sat, 17 Feb 2007 18:26:13 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Jouke Witteveen References: <3993a4980702051233u10c30575kd1f6d27fcd600110@mail.gmail.com> <45C7A1F9.20306@FreeBSD.org> <3993a4980702170546t7f9384eaq358986a4cc734582@mail.gmail.com> In-Reply-To: <3993a4980702170546t7f9384eaq358986a4cc734582@mail.gmail.com> Content-Type: multipart/mixed; boundary="------------020907090605090509040208" Cc: freebsd-net@freebsd.org Subject: [PATCH] Re: ioctl: SIOCADDMULTI (howto?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 18:26:16 -0000 This is a multi-part message in MIME format. --------------020907090605090509040208 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Jouke Witteveen wrote: > > So my apologies for suggesting it doesn't work at all; it seems that > the application I'm trying to get to work (wpa_supplicant for wired > interfaces) just doesn't _send_ its packets the right way. That's a big relief! I added an item to the Wiki for someone to write a regression test. > > Things aren't perfect though. In if.c the if_findmulti function is > broken (always returns NULL). I presume just comparing the > *LLADDR((sockaddr *)sa) data on both sockets is a better check, though > my knowledge on these things is limited. I think I see a possible problem, though the code looks as though it is behaving as expected. I am looking at RELENG_6 if.c. I think sa_equal() may be to blame. sa_equal() performs a binary comparison on all of sa_data up to sa_len. Looking at struct sockaddr_dl, this might not be the right thing at all in that situation... though I need another pair of eyes to look. Can anyone shed light on this? An AF_INET and AF_INET6 address can be completely specified and compared with sa_equal(). An AF_LINK address looks as though sa_equal() may return irrational results. > > As for netstat, I do not really know what is keeping it from showing > the Multicast addresses. Again: my knowledge on this matter is > limited. All I can think of is that getifmaddrs is forgetting > something (perhaps the lack of a group membership). Maybe you can take > a look at it (I believe you wrote it). I wrote the libc getifmaddrs() function and integrated it into netstat -g; Harti Brandt wrote the NET_RT_IFMALIST support. getifmaddrs() *should* return sockaddr_dl as well as sockaddr_in and all the others. netstat skips over AF_LINK addresses. Try this patch to reveal them. It doesn't seem to show the IPv4 link layer memberships underneath, which is interesting... > > As I am still learning how best to contribute to a project as big as > FreeBSD and I do not think I am skilled enough yet in C I refrain from > writing a patch. I am eager to see one though, be it only out of > curiosity to know what would be considered a proper fix. Give it a try anyway! I like to think we have strong healthy egos round here. Regards, BMS --------------020907090605090509040208 Content-Type: text/x-patch; name="llmcast.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="llmcast.diff" --- mcast.c.orig Sat Feb 17 18:12:28 2007 +++ mcast.c Sat Feb 17 18:14:15 2007 @@ -84,7 +84,7 @@ if (getifmaddrs(&ifmap)) err(EX_OSERR, "getifmaddrs"); - fputs("IPv4/IPv6 Multicast Group Memberships\n", stdout); + fputs("IPv4/IPv6/Layer 2 Multicast Group Memberships\n", stdout); fprintf(stdout, "%-20s\t%-16s\t%s\n", "Group", "Gateway", "Netif"); for (ifma = ifmap; ifma; ifma = ifma->ifma_next) { @@ -103,6 +103,15 @@ inet_ntop(psa->sa.sa_family, addr, addrbuf, sizeof(addrbuf)); pgroup = addrbuf; + break; + case AF_LINK: + if (psa->sdl.sdl_type == IFT_ETHER) { + plladdr = ether_ntoa((struct ether_addr *) + &psa->sdl.sdl_data); + } else { + plladdr = link_ntoa(&psa->sdl); + } + strlcpy(addrbuf, plladdr, sizeof(addrbuf)); break; default: continue; /* XXX */ --------------020907090605090509040208-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 18:52:08 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ACE7F16A401 for ; Sat, 17 Feb 2007 18:52:08 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.freebsd.org (Postfix) with ESMTP id 6DD1013C47E for ; Sat, 17 Feb 2007 18:52:08 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp2-g19.free.fr (Postfix) with ESMTP id 59F057D67 for ; Sat, 17 Feb 2007 19:52:07 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id D74DB9D41F for ; Sat, 17 Feb 2007 18:53:05 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id B76E2405D; Sat, 17 Feb 2007 19:53:05 +0100 (CET) Date: Sat, 17 Feb 2007 19:53:05 +0100 From: Jeremie Le Hen To: freebsd-net@FreeBSD.org Message-ID: <20070217185305.GA22946@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: Firewalling DNS jails X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 18:52:08 -0000 Hi there, I have two jails with named(8) running on my server. - The first one (dns_int) is used as a resolver for my local network, and also serve the zone adressing it. - The second one (dns_ext) is used to serve my zones on the Internet side. I want to know if the following rules are secure enough and if there can be tightened regarding the DNS protocol and the policy I've set up. === 8< === 8< === 8< === pass in inet proto { tcp, udp } from $local_net to $dns_int domain keep state pass out inet proto { tcp, udp } from $dns_int to any domain keep state pass in inet proto { tcp, udp } from any to $dns_ext domain keep state pass out inet proto { tcp, udp } from $dns_int to !$local_net domain keep state === 8< === 8< === 8< === Thank you. PS: If you know about problems using the same nameserver for resolving and serving my internal zone, please let me know as well. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 19:19:42 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16E2E16A401 for ; Sat, 17 Feb 2007 19:19:42 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id D248413C461 for ; Sat, 17 Feb 2007 19:19:41 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l1HJJfGk028401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 17 Feb 2007 11:19:41 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45D7554D.3000709@errno.com> Date: Sat, 17 Feb 2007 11:19:41 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.9 (X11/20070208) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [PATH] make ifconfig use getifaddrs X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 19:19:42 -0000 ifconfig has a hand-rolled version of the code in getifaddrs. The patch here: http://people.freebsd.org/~sam/ifconfig.patch (against HEAD) converts it to use getifaddrs. I'm especially interested in whether this properly handles ipv6, atalk, ipx, and p2p configurations. There should no visible changes in output; if you see anything please provide the output of ifconfig before+after. Sam From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 19:40:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2A5216A402; Sat, 17 Feb 2007 19:40:40 +0000 (UTC) (envelope-from chrishome@austin.rr.com) Received: from ms-smtp-01.texas.rr.com (ms-smtp-01.texas.rr.com [24.93.47.40]) by mx1.freebsd.org (Postfix) with ESMTP id 42FFA13C49D; Sat, 17 Feb 2007 19:40:39 +0000 (UTC) (envelope-from chrishome@austin.rr.com) Received: from ms-mss-01 (ms-mss-01-smtp.texas.rr.com [10.93.38.14]) by ms-smtp-01.texas.rr.com (8.13.6/8.13.6) with ESMTP id l1HJ1I5Q012501; Sat, 17 Feb 2007 13:01:18 -0600 (CST) Received: from texas.rr.com (localhost [127.0.0.1]) by ms-mss-01.texas.rr.com (iPlanet Messaging Server 5.2 HotFix 2.10 (built Dec 26 2005)) with ESMTP id <0JDM0085PFI612@ms-mss-01.texas.rr.com>; Sat, 17 Feb 2007 13:01:18 -0600 (CST) Received: from [10.93.36.25] (Forwarded-For: [24.28.0.133]) by ms-mss-01.texas.rr.com (mshttpd); Sat, 17 Feb 2007 13:01:18 -0600 Date: Sat, 17 Feb 2007 13:01:18 -0600 From: chrishome@austin.rr.com In-reply-to: <45C99336.3010508@demax.sk> To: Jan Sebosik Message-id: MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.10 (built Dec 26 2005) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal References: <45C99336.3010508@demax.sk> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Packet rate limiter X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 19:40:40 -0000 > Hi > > is there any way how to limit packet per second [PPS] rate to > specified > IP (group of IP) ? Linux can achieve this via IPtables. > I`ve searched a lot of web, but nothing interesting found (for PF, > IPFilter, and IPFW). > I agree this would be a very nice addition to IPFW as a basic feature, or maybe a more advanced version via Dummynet. It's much to easy for a trojan / virus or intentionally malicious user to flood a FreeBSD box setup as a router with loads of tiny UDP packets on port 80. In fact, just a few days ago we had 2 users behind one of our FreeBSD gateways sending huge loads of traffic to a webhosting site.. This packet count shown below was all within a 12 hour period ;) 00010 990465375 39618916491 deny ip from 172.17.106.114 to any 00010 20010976 800449444 deny ip from 172.17.105.114 to any Being able to put limits per protocol would be a wonderful addition. For now what we do is setup a count rule by MAC address for every user, we check the count rules every 60 seconds, if we begin to see packets per second for a certain host climb above for example 4000PPS, we simply automatically add a deny rule. These are generally users set for 1 or 2 Mbps each, so 4000PPS is pretty extreme for that kind of bandwidth unless your doing something you shouldn't. I've been talking to a few friends about possibly adding this to ipfw or dummynet, and if I ever get around to a completed working version, I would be more than happy to share, but for now, there are ways to still fix the problem, just not as elegant as if it where actually a firewall rule ;) Chris Bowman From owner-freebsd-net@FreeBSD.ORG Sat Feb 17 20:30:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23FC516A402 for ; Sat, 17 Feb 2007 20:30:10 +0000 (UTC) (envelope-from admin@azuni.net) Received: from mail.azuni.net (ns0.azuni.net [217.25.25.3]) by mx1.freebsd.org (Postfix) with ESMTP id 237C813C491 for ; Sat, 17 Feb 2007 20:30:08 +0000 (UTC) (envelope-from admin@azuni.net) Received: (qmail 11283 invoked by uid 1004); 17 Feb 2007 20:03:26 -0000 Received: from admin@azuni.net by mail.azuni.net by uid 89 with qmail-scanner-1.20 (clamscan: 0.65. spamassassin: 2.63. Clear:RC:1(217.25.23.9):. Processed in 0.019759 secs); 17 Feb 2007 20:03:26 -0000 Received: from unknown (HELO ?217.25.23.9?) (217.25.23.9) by ns0.azuni.net with AES256-SHA encrypted SMTP; 17 Feb 2007 20:03:26 -0000 Message-ID: <45D75F87.6050908@azuni.net> Date: Sun, 18 Feb 2007 00:03:19 +0400 From: admin Organization: UniNet User-Agent: Debian Thunderbird 1.0.2 (X11/20070113) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: ipfw limit src-addr woes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2007 20:30:10 -0000 Hi, I'm trying to use ipfw's limit clause to limit the number of connections a single IP can have at the same time in a transparent web-proxy environment: 00350 skipto 401 tcp from x.x.x.x/x,y.y.y.y/y,z.z.z.z/z to any dst-port 80 in via if0 setup limit src-addr 10 00401 fwd local.ip.ad.dr,8080 tcp from x.x.x.x/x to any dst-port 80 ... the rest fwd... the problem is that the src-addr limit is not enforced for some nasty clients that open a huge number (3-5 times the prescribed value) of www-connections to some single address Out There, forcing you to bump up certain sysctl variables (such as kern.ipc.nmbclusters, kern.ipc.maxsockets, etc.) to mitigate the DOS effects. What might be going on? Is ipfw broken, or am I misusing it? OS: FreeBSD 6.2