From owner-freebsd-net@FreeBSD.ORG Sun May 18 07:19:37 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC18E1065671; Sun, 18 May 2008 07:19:37 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (gate6.infracaninophile.co.uk [IPv6:2001:8b0:151:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 219028FC1F; Sun, 18 May 2008 07:19:36 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost [IPv6:::1]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.2/8.14.2) with ESMTP id m4I7JPia047593; Sun, 18 May 2008 08:19:31 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.5.5 smtp.infracaninophile.co.uk m4I7JPia047593 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=infracaninophile.co.uk; s=200708; t=1211095171; bh=iWyqktAVywGpDc U0NcrxG8hB86FP9xRqEpWwTqbmoGA=; h=Message-ID:Date:From:MIME-Version: To:CC:Subject:References:In-Reply-To:Content-Type:Cc:Content-Type: Date:From:In-Reply-To:Message-ID:Mime-Version:References:To; z=Mes sage-ID:=20<482FD877.6050707@infracaninophile.co.uk>|Date:=20Sun,=2 018=20May=202008=2008:19:19=20+0100|From:=20Matthew=20Seaman=20|Organization:=20Infracaninophile|User -Agent:=20Thunderbird=202.0.0.14=20(X11/20080503)|MIME-Version:=201 .0|To:=20=3D?ISO-8859-1?Q?Johan_Str=3DF6m?=3D=20 |CC:=20Alex=20Trull=20,=20freebsd-net@freebsd.org,= 20=0D=0A=20freebsd-stable=20,=0D=0A=20f reebsd-pf@freebsd.org|Subject:=20Re:=20connect():=20Operation=20not =20permitted|References:=20<678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@st romnet.se>=09<1211037564.6326.27.camel@porksoda>=20<679DB462-75D6-4 5CC-949C-1BE8E12C22CD@stromnet.se>|In-Reply-To:=20<679DB462-75D6-45 CC-949C-1BE8E12C22CD@stromnet.se>|X-Enigmail-Version:=200.95.6|Cont ent-Type:=20multipart/signed=3B=20micalg=3Dpgp-sha256=3B=0D=0A=20pr otocol=3D"application/pgp-signature"=3B=0D=0A=20boundary=3D"------- -----enig220B22B21812B7D67D58F6E8"; b=w7qPpxsaWqz6TEKv4DfNfAWG1f4BY NvqZJ+Qxop7l87WoCeipBz42/rDtdapiWN0z7aEv8sZGHWTSfDPSjHJXbCHbR/LLxwL 2fdEMrNW6bWWbmhZmRMKM5FWEMzXypFj9Fksze1EcodyIrj1CcNKRlUZNCBksI/4QyB egiOx4kE= Message-ID: <482FD877.6050707@infracaninophile.co.uk> Date: Sun, 18 May 2008 08:19:19 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Johan_Str=F6m?= References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> <1211037564.6326.27.camel@porksoda> <679DB462-75D6-45CC-949C-1BE8E12C22CD@stromnet.se> In-Reply-To: <679DB462-75D6-45CC-949C-1BE8E12C22CD@stromnet.se> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig220B22B21812B7D67D58F6E8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (smtp.infracaninophile.co.uk [IPv6:::1]); Sun, 18 May 2008 08:19:31 +0100 (BST) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on happy-idiot-talk.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VERIFIED,NO_RELAYS autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on happy-idiot-talk.infracaninophile.co.uk Cc: Alex Trull , freebsd-pf@freebsd.org, freebsd-stable , freebsd-net@freebsd.org Subject: Re: connect(): Operation not permitted X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 May 2008 07:19:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig220B22B21812B7D67D58F6E8 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Johan Str=F6m wrote: > drop all traffic)? A check with pfctl -vsr reveals that the actual rule= =20 > inserted is "pass on lo0 inet from 123.123.123.123 to 123.123.123.123=20 > flags S/SA keep state". Where did that "keep state" come from? 'flags S/SA keep state' is the default now for tcp filter rules -- that was new in 7.0 reflecting the upstream changes made between the 4.0 and 4= =2E1 releases of OpenBSD. If you want a stateless rule, append 'no state'. http://www.openbsd.org/faq/pf/filter.html#state Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enig220B22B21812B7D67D58F6E8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkgv2HwACgkQ8Mjk52CukIwjCwCfa/ntbIVtKQwooaR/j8aLxKPF ukEAni24eJYNJRCwOLZUQFCd2A1kf+tO =2vt+ -----END PGP SIGNATURE----- --------------enig220B22B21812B7D67D58F6E8-- From owner-freebsd-net@FreeBSD.ORG Sun May 18 10:33:58 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27502106564A; Sun, 18 May 2008 10:33:58 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from core.stromnet.se (core.stromnet.se [83.218.84.131]) by mx1.freebsd.org (Postfix) with ESMTP id CF7038FC1E; Sun, 18 May 2008 10:33:57 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from localhost (core.stromnet.se [83.218.84.131]) by core.stromnet.se (Postfix) with ESMTP id CA17FF5B078; Sun, 18 May 2008 12:33:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se X-Spam-Flag: NO X-Spam-Score: 0.176 X-Spam-Level: X-Spam-Status: No, score=0.176 tagged_above=0 required=6.2 tests=[AWL=1.982, BAYES_00=-2.599, RDNS_DYNAMIC=0.1, SPF_FAIL=0.693] Received: from core.stromnet.se ([83.218.84.131]) by localhost (core.stromnet.se [83.218.84.131]) (amavisd-new, port 10024) with ESMTP id lvorf6evv2oD; Sun, 18 May 2008 12:33:52 +0200 (CEST) Received: from johan-mp.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by core.stromnet.se (Postfix) with ESMTP id 48A7AF5AFF5; Sun, 18 May 2008 12:33:52 +0200 (CEST) Message-Id: From: =?ISO-8859-1?Q?Johan_Str=F6m?= To: Matthew Seaman In-Reply-To: <482FD877.6050707@infracaninophile.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sun, 18 May 2008 12:33:51 +0200 References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> <1211037564.6326.27.camel@porksoda> <679DB462-75D6-45CC-949C-1BE8E12C22CD@stromnet.se> <482FD877.6050707@infracaninophile.co.uk> X-Mailer: Apple Mail (2.919.2) Cc: Alex Trull , freebsd-pf@freebsd.org, freebsd-stable , freebsd-net@freebsd.org Subject: Re: connect(): Operation not permitted X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 May 2008 10:33:58 -0000 On May 18, 2008, at 9:19 AM, Matthew Seaman wrote: > Johan Str=F6m wrote: > >> drop all traffic)? A check with pfctl -vsr reveals that the actual =20= >> rule inserted is "pass on lo0 inet from 123.123.123.123 to =20 >> 123.123.123.123 flags S/SA keep state". Where did that "keep state" =20= >> come from? > > 'flags S/SA keep state' is the default now for tcp filter rules -- =20 > that > was new in 7.0 reflecting the upstream changes made between the 4.0 =20= > and 4.1 > releases of OpenBSD. If you want a stateless rule, append 'no state'. > > http://www.openbsd.org/faq/pf/filter.html#state Thanks! I was actually looking around in the pf.conf manpage but =20 failed to find it yesterday, but looking closer today I now saw it. Applied the no state (and quick) to the rule, and now no state is =20 created. And the problem I had in the first place seems to have been resolved =20 too now, even though it didn't look like a state problem.. (started to =20= deny new connections much earlier than the states was full, altough =20 maybee i wasnt looking for updates fast enough or something). Anyways, thanks to all helping me out, and of course thanks to =20 everybody involved in FreeBSD/pf and all for great products! Cannot be =20= said enough times ;)= From owner-freebsd-net@FreeBSD.ORG Sun May 18 16:59:45 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C07C106566B; Sun, 18 May 2008 16:59:45 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D8E898FC0C; Sun, 18 May 2008 16:59:44 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4IGxiMi085250; Sun, 18 May 2008 16:59:44 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4IGxisL085246; Sun, 18 May 2008 16:59:44 GMT (envelope-from vwe) Date: Sun, 18 May 2008 16:59:44 GMT Message-Id: <200805181659.m4IGxisL085246@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-pf@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/123726: [panic] [altq] page fault after ppp restart and pf resync X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 May 2008 16:59:45 -0000 Old Synopsis: page fault after ppp restart and pf resync New Synopsis: [panic] [altq] page fault after ppp restart and pf resync Responsible-Changed-From-To: freebsd-net->freebsd-pf Responsible-Changed-By: vwe Responsible-Changed-When: Sun May 18 16:57:03 UTC 2008 Responsible-Changed-Why: altq is Max' territory - reassign also please note, this PR is a slightly different DUP to similar PRs (problem is caused by altq when interfaces disappear) http://www.freebsd.org/cgi/query-pr.cgi?pr=123726 From owner-freebsd-net@FreeBSD.ORG Sun May 18 17:54:57 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 101531065675 for ; Sun, 18 May 2008 17:54:57 +0000 (UTC) (envelope-from kian.mohageri@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.177]) by mx1.freebsd.org (Postfix) with ESMTP id 934968FC1A for ; Sun, 18 May 2008 17:54:56 +0000 (UTC) (envelope-from kian.mohageri@gmail.com) Received: by ik-out-1112.google.com with SMTP id c30so412706ika.3 for ; Sun, 18 May 2008 10:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=QTfaQKgKefpYojHrfCXWQp6lMgu7zDIPVcdEzI/F3Zg=; b=M2jj2TJBbCz5/zup3RaSgyxVIBVrWEYBdVOBV6RKQYUkCArXwArrOX/7WuQLFRkebs6KWZeWcG6b0JBWW5xmU4piqJvbDb23OnC6mmzT2Pj9/nK1S4WgeorNDFbkX4uDa1KebSuFaHBBn8SZi9YPflcb7Q+HxJDd1pWvaVGx2Zw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EMBSg6Sc2718xODEfKjHL11TMJZphNZ4gqQofrS1BAY4OIKdTbDiKMswQzZS60x1WCTqbvMOA3Eh/ebsUZmiVXi1mKFLwfoeEyVd1Q72HuRXTt/tRpfAU4CwEspXSXKY2spZx0mHhAik7cqFBghSjMIADYdAXEf+mZE0bVYDAkY= Received: by 10.142.86.7 with SMTP id j7mr2465478wfb.78.1211131759597; Sun, 18 May 2008 10:29:19 -0700 (PDT) Received: by 10.143.195.9 with HTTP; Sun, 18 May 2008 10:29:19 -0700 (PDT) Message-ID: Date: Sun, 18 May 2008 10:29:19 -0700 From: "Kian Mohageri" To: "=?UTF-8?Q?Johan_Str=C3=B6m?=" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> <1211037564.6326.27.camel@porksoda> <679DB462-75D6-45CC-949C-1BE8E12C22CD@stromnet.se> <482FD877.6050707@infracaninophile.co.uk> Cc: Alex Trull , freebsd-net@freebsd.org, Matthew Seaman , freebsd-stable , freebsd-pf@freebsd.org Subject: Re: connect(): Operation not permitted X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 May 2008 17:54:57 -0000 T24gU3VuLCBNYXkgMTgsIDIwMDggYXQgMzozMyBBTSwgSm9oYW4gU3Ryw7ZtIDxqb2hhbkBzdHJv bW5ldC5zZT4gd3JvdGU6Cj4gT24gTWF5IDE4LCAyMDA4LCBhdCA5OjE5IEFNLCBNYXR0aGV3IFNl YW1hbiB3cm90ZToKPgo+PiBKb2hhbiBTdHLDtm0gd3JvdGU6Cj4+Cj4+PiBkcm9wIGFsbCB0cmFm ZmljKT8gQSBjaGVjayB3aXRoIHBmY3RsIC12c3IgcmV2ZWFscyB0aGF0IHRoZSBhY3R1YWwgcnVs ZQo+Pj4gaW5zZXJ0ZWQgaXMgInBhc3Mgb24gbG8wIGluZXQgZnJvbSAxMjMuMTIzLjEyMy4xMjMg dG8gMTIzLjEyMy4xMjMuMTIzIGZsYWdzCj4+PiBTL1NBIGtlZXAgc3RhdGUiLiBXaGVyZSBkaWQg dGhhdCAia2VlcCBzdGF0ZSIgY29tZSBmcm9tPwo+Pgo+PiAnZmxhZ3MgUy9TQSBrZWVwIHN0YXRl JyBpcyB0aGUgZGVmYXVsdCBub3cgZm9yIHRjcCBmaWx0ZXIgcnVsZXMgLS0gdGhhdAo+PiB3YXMg bmV3IGluIDcuMCByZWZsZWN0aW5nIHRoZSB1cHN0cmVhbSBjaGFuZ2VzIG1hZGUgYmV0d2VlbiB0 aGUgNC4wIGFuZAo+PiA0LjEKPj4gcmVsZWFzZXMgb2YgT3BlbkJTRC4gIElmIHlvdSB3YW50IGEg c3RhdGVsZXNzIHJ1bGUsIGFwcGVuZCAnbm8gc3RhdGUnLgo+Pgo+PiBodHRwOi8vd3d3Lm9wZW5i c2Qub3JnL2ZhcS9wZi9maWx0ZXIuaHRtbCNzdGF0ZQo+Cj4gVGhhbmtzISBJIHdhcyBhY3R1YWxs eSBsb29raW5nIGFyb3VuZCBpbiB0aGUgcGYuY29uZiBtYW5wYWdlIGJ1dCBmYWlsZWQgdG8KPiBm aW5kIGl0IHllc3RlcmRheSwgYnV0IGxvb2tpbmcgY2xvc2VyIHRvZGF5IEkgbm93IHNhdyBpdC4K PiBBcHBsaWVkIHRoZSBubyBzdGF0ZSAoYW5kIHF1aWNrKSB0byB0aGUgcnVsZSwgYW5kIG5vdyBu byBzdGF0ZSBpcyBjcmVhdGVkLgo+IEFuZCB0aGUgcHJvYmxlbSBJIGhhZCBpbiB0aGUgZmlyc3Qg cGxhY2Ugc2VlbXMgdG8gaGF2ZSBiZWVuIHJlc29sdmVkIHRvbwo+IG5vdywgZXZlbiB0aG91Z2gg aXQgZGlkbid0IGxvb2sgbGlrZSBhIHN0YXRlIHByb2JsZW0uLiAoc3RhcnRlZCB0byBkZW55IG5l dwo+IGNvbm5lY3Rpb25zIG11Y2ggZWFybGllciB0aGFuIHRoZSBzdGF0ZXMgd2FzIGZ1bGwsIGFs dG91Z2ggbWF5YmVlIGkgd2FzbnQKPiBsb29raW5nIGZvciB1cGRhdGVzIGZhc3QgZW5vdWdoIG9y IHNvbWV0aGluZykuCj4KCkknZCBiZSB3aWxsaW5nIHRvIGJldCBpdCdzIGJlY2F1c2UgeW91J3Jl IHJldXNpbmcgdGhlIHNvdXJjZSBwb3J0IG9uIGEKbmV3IGNvbm5lY3Rpb24gYmVmb3JlIHRoZSBv bGQgc3RhdGUgZXhwaXJlcy4KCllvdSdsbCBrbm93IGlmIHlvdSBjaGVjayB0aGUgc3RhdGUtbWlz bWF0Y2ggY291bnRlci4KCkFueXdheSwgZ2xhZCB5b3UgZm91bmQgYSByZXNvbHV0aW9uLgoKLUtp YW4K From owner-freebsd-net@FreeBSD.ORG Sun May 18 20:27:23 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11E551065672 for ; Sun, 18 May 2008 20:27:23 +0000 (UTC) (envelope-from jay@jcornwall.me.uk) Received: from vps1.jcornwall.me.uk (vps1.jcornwall.me.uk [193.227.111.74]) by mx1.freebsd.org (Postfix) with ESMTP id AAB948FC1B for ; Sun, 18 May 2008 20:27:22 +0000 (UTC) (envelope-from jay@jcornwall.me.uk) Received: from [82.70.152.17] (cobra.home.jcornwall.me.uk [82.70.152.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vps1.jcornwall.me.uk (Postfix) with ESMTP id 098785201C2; Sun, 18 May 2008 21:29:32 +0100 (BST) Message-ID: <48309128.1020101@jcornwall.me.uk> Date: Sun, 18 May 2008 21:27:20 +0100 From: "Jay L. T. Cornwall" User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: "H.fazaeli" References: <4825EF8D.1050304@jcornwall.me.uk> <4826EB42.104@sepehrs.com> <48274E6D.9060704@jcornwall.me.uk> <48286052.6000507@sepehrs.com> In-Reply-To: <48286052.6000507@sepehrs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: if_bridge with two subnets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 May 2008 20:27:23 -0000 H.fazaeli wrote: > It does work. However, if I understand your setup correctly, the freebsd > box > has been setup to act as a bridge, not as a router (routing is enabled with > sysctl net.inet.ip.forwarding=1). Bridging works when the forwarding is > between the same subnets. > > For freebsd box to route between subnets: > - enable routing: sysctl net.inet.ip.forwarding=1 > - clients must use the freebsd box as gateway. > - IP addresses must be removed from the bridge and assigned to > the member interfaces. (the bridge is no longer needed). > > You may have bridging & routing on the same box at the same time but > note that a single packet coming into the system either goes through > bridging _or_ routing code, but not both. The former case happens > if packet's destination MAC address is not that of box. The > latter case happens when destination MAC address is that of receiving > interface. Thank you very much for your explanation. I had misunderstood precisely how routing and bridging are done in FreeBSD but it now makes sense. > If you provide a network diagram along with your requirements, > we can better discuss the matter. I now have a working network configuration. For completeness I will explain how it's set up. I have a small, publicly routable netblock to serve a larger LAN of machines. Thus some of the machines draw IPs from a non-routable private pool and are NAT'd to a one of the public IPs. It looks like this: [Gateway] XX.XX.XXX.22 | [FreeBSD] XX.XX.XXX.20-21 | [L2 Switch] | PCs XX.XX.XXX.17-19 192.168.1.0/24 The gateway must have one of the public IPs to communicate with its upstream correctly. On the other side of the FreeBSD server the rest of those IPs are used. So a traditional gateway setup would not work here: it would imply that the FreeBSD server has two interfaces from two different subnets, rather than one split subnet. Perhaps a static route for the gateway would work, but it would be messy. So I bridge the two interfaces to join the public subnet. Following your advice I have set the FreeBSD server to the network gateway - previously it was the .22 gateway - and now all of the LAN PCs can communicate without additional routing information. Inter-subnet packets will bounce off the FreeBSD server, rather than staying inside the L2 switch, but that's OK. -- Jay L. T. Cornwall http://www.jcornwall.me.uk/ From owner-freebsd-net@FreeBSD.ORG Sun May 18 22:47:35 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A1AC106567D; Sun, 18 May 2008 22:47:35 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E6B518FC15; Sun, 18 May 2008 22:47:34 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4IMlYxM015763; Sun, 18 May 2008 22:47:34 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4IMlYqq015759; Sun, 18 May 2008 22:47:34 GMT (envelope-from linimon) Date: Sun, 18 May 2008 22:47:34 GMT Message-Id: <200805182247.m4IMlYqq015759@freefall.freebsd.org> To: linimon@FreeBSD.org, gnats-admin@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/123796: FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2008 22:47:35 -0000 Old Synopsis: Port mapping does not work New Synopsis: FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not work Responsible-Changed-From-To: gnats-admin->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 18 22:45:21 UTC 2008 Responsible-Changed-Why: Rescue this PR from the 'pending' category. http://www.freebsd.org/cgi/query-pr.cgi?pr=123796 From owner-freebsd-net@FreeBSD.ORG Mon May 19 08:17:41 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00CDF106567B for ; Mon, 19 May 2008 08:17:41 +0000 (UTC) (envelope-from mjl@luckie.org.nz) Received: from mailfilter14.ihug.co.nz (mailfilter14.ihug.co.nz [203.109.136.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8DDF88FC14 for ; Mon, 19 May 2008 08:17:40 +0000 (UTC) (envelope-from mjl@luckie.org.nz) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AswEABHOMEh2XXmb/2dsb2JhbACBVao5 X-IronPort-AV: E=Sophos;i="4.27,508,1204455600"; d="scan'208";a="13143221" Received: from 118-93-121-155.dsl.dyn.ihug.co.nz (HELO spandex.luckie.org.nz) ([118.93.121.155]) by smtp.mailfilter6.ihug.co.nz with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 May 2008 19:48:53 +1200 Received: from mjl by spandex.luckie.org.nz with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jy072-000GDB-Nd for freebsd-net@freebsd.org; Mon, 19 May 2008 19:48:52 +1200 Date: Mon, 19 May 2008 19:48:52 +1200 From: Matthew Luckie To: freebsd-net@freebsd.org Message-ID: <20080519074852.GA62290@spandex.luckie.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: rtadvd/rrenum.c:179 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 08:17:41 -0000 When rtadvd is compiled on 7.0, the following warning is emitted: /usr/src/usr.sbin/rtadvd/rrenum.c:179: warning: overflow in implicit constant conversion I have not determined if the code works correct or not, but I wonder if it does. the line in question is this: struct irr_raflagmask { u_char onlink : 1; u_char autonomous : 1; u_char reserved : 6; } irr_raflagmask; irr->irr_raf_mask_onlink = (rpu->rpu_ramask & ICMP6_RR_PCOUSE_RAFLAGS_ONLINK); rpu_ramask is unsigned char, the constant is 0x80, and irr_raf_mask_onlink is a single bit value. This troubles me, and the compiler. I'm only raising this for consideration; if it can be determined that the code works correctly, maybe a commit can be made to silence the warnings. --- rrenum.c.orig 2004-03-10 21:46:39.000000000 +1300 +++ rrenum.c 2008-05-19 19:39:52.000000000 +1200 @@ -176,9 +176,9 @@ do_use_prefix(int len, struct rr_pco_mat irr->irr_u_uselen = rpu->rpu_uselen; irr->irr_u_keeplen = rpu->rpu_keeplen; irr->irr_raf_mask_onlink = - (rpu->rpu_ramask & ICMP6_RR_PCOUSE_RAFLAGS_ONLINK); + (rpu->rpu_ramask & ICMP6_RR_PCOUSE_RAFLAGS_ONLINK) == 0 ? 0 : 1; irr->irr_raf_mask_auto = - (rpu->rpu_ramask & ICMP6_RR_PCOUSE_RAFLAGS_AUTO); + (rpu->rpu_ramask & ICMP6_RR_PCOUSE_RAFLAGS_AUTO) == 0 ? 0 : 1; irr->irr_vltime = ntohl(rpu->rpu_vltime); irr->irr_pltime = ntohl(rpu->rpu_pltime); irr->irr_raf_onlink = From owner-freebsd-net@FreeBSD.ORG Mon May 19 09:14:33 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC88B106566C; Mon, 19 May 2008 09:14:33 +0000 (UTC) (envelope-from mlaier@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9C6458FC12; Mon, 19 May 2008 09:14:33 +0000 (UTC) (envelope-from mlaier@FreeBSD.org) Received: from freefall.freebsd.org (mlaier@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4J9EX8O000508; Mon, 19 May 2008 09:14:33 GMT (envelope-from mlaier@freefall.freebsd.org) Received: (from mlaier@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4J9EXq8000504; Mon, 19 May 2008 09:14:33 GMT (envelope-from mlaier) Date: Mon, 19 May 2008 09:14:33 GMT Message-Id: <200805190914.m4J9EXq8000504@freefall.freebsd.org> To: mlaier@FreeBSD.org, freebsd-pf@FreeBSD.org, freebsd-net@FreeBSD.org From: mlaier@FreeBSD.org Cc: Subject: Re: kern/78090: [ipf] ipf filtering on bridged packets doesn't work if ipfw is loaded X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 09:14:33 -0000 Synopsis: [ipf] ipf filtering on bridged packets doesn't work if ipfw is loaded Responsible-Changed-From-To: freebsd-pf->freebsd-net Responsible-Changed-By: mlaier Responsible-Changed-When: Mon May 19 09:12:31 UTC 2008 Responsible-Changed-Why: This is not a pf problem. Also note that the old bridge implementation, to which this PR relates to, is obsolete by if_bridge(4) and likely no longer maintained. Over to freebsd-net in case somebody is still interested. http://www.freebsd.org/cgi/query-pr.cgi?pr=78090 From owner-freebsd-net@FreeBSD.ORG Mon May 19 09:17:10 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E26291065671; Mon, 19 May 2008 09:17:10 +0000 (UTC) (envelope-from mlaier@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B29958FC29; Mon, 19 May 2008 09:17:10 +0000 (UTC) (envelope-from mlaier@FreeBSD.org) Received: from freefall.freebsd.org (mlaier@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4J9HAhW000567; Mon, 19 May 2008 09:17:10 GMT (envelope-from mlaier@freefall.freebsd.org) Received: (from mlaier@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4J9HAMx000563; Mon, 19 May 2008 09:17:10 GMT (envelope-from mlaier) Date: Mon, 19 May 2008 09:17:10 GMT Message-Id: <200805190917.m4J9HAMx000563@freefall.freebsd.org> To: read@midland.com.ua, mlaier@FreeBSD.org, freebsd-pf@FreeBSD.org, freebsd-net@FreeBSD.org From: mlaier@FreeBSD.org Cc: Subject: Re: kern/102344: [ipf] Some packets do not pass through network interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 09:17:11 -0000 Synopsis: [ipf] Some packets do not pass through network interface State-Changed-From-To: open->feedback State-Changed-By: mlaier State-Changed-When: Mon May 19 09:15:26 UTC 2008 State-Changed-Why: The submitter has been asked for configuration details over a year ago. Responsible-Changed-From-To: freebsd-pf->freebsd-net Responsible-Changed-By: mlaier Responsible-Changed-When: Mon May 19 09:15:26 UTC 2008 Responsible-Changed-Why: Not a pf problem. Reassign to freebsd-net. http://www.freebsd.org/cgi/query-pr.cgi?pr=102344 From owner-freebsd-net@FreeBSD.ORG Mon May 19 11:06:57 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D85C1065676 for ; Mon, 19 May 2008 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0B1448FC1B for ; Mon, 19 May 2008 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4JB6uAf011660 for ; Mon, 19 May 2008 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4JB6uxc011656 for freebsd-net@FreeBSD.org; Mon, 19 May 2008 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 May 2008 11:06:56 GMT Message-Id: <200805191106.m4JB6uxc011656@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 11:06:57 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue s kern/81147 net [net] [patch] em0 reinitialization while adding aliase s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/92090 net [bge] bge0: watchdog timeout -- resetting f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr f kern/102344 net [ipf] Some packets do not pass through network interfa o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] s kern/105943 net Network stack may modify read-only mbuf chain copies o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109733 net [bge] bge link state issues [regression] o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116328 net [bge]: Solid hang with bge interface o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117423 net [vlan] Duplicate IP on different interfaces o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119361 net [bge] bge(4) transmit performance problem o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o kern/121555 net Fatal trap 12: current process = 12 (swi1: net) o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 o kern/121983 net [fxp] fxp0 MBUF and PAE o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122082 net [in_pcb] NULL pointer dereference in in_pcbdrop o kern/122195 net [ed] Alignment problems in if_ed f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122427 net [apm] [panic] apm and mDNSResponder cause panic during o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122743 net [panic] vm_page_unwire: invalid wire count: 0 o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix f kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar f kern/122858 net [nsswitch] nsswitch in 7.0 is f*cked up o kern/122875 net [nfs] "rstatd: Can't get namelist. 1" - fbsd 7.0-stabl o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/123066 net [ipsec] [panic] kernel trap with ipsec o kern/123123 net [re][patch] Realtek RTL8111C detection and failure o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123330 net [nsswitch] Enabling samba wins in nsswitch.conf causes o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o bin/123465 net [ip6] route(1): route add -inet6 -interfac o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123617 net [tcp] breaking connection when client downloading file o bin/123633 net ifconfig(8) doesn't set inet and ether address in one p kern/123741 net [netgraph] [panic] kernel panic due to netgraph mpd o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not 79 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 o kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o bin/79228 net [patch] extend /sbin/arp to be able to create blackhol o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/95267 net packet drops periodically appear o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/112179 net [sis] [patch] sis driver for natsemi DP83815D autonego o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o bin/117339 net [patch] route(8): loading routing management commands o kern/118727 net [netgraph] [patch] [request] add new ng_pf module a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/119432 net [arp] route add -host -iface causes arp e f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/121242 net [ate] [patch] Promiscuous mode of if_ate (arm) doesn't o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121443 net [gif] LOR icmp6_input/nd6_lookup o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122068 net [ppp] ppp can not set the correct interface with pptpd o kern/122145 net error while compiling with device ath_rate_amrr o kern/122295 net [bge] bge Ierr rate increase (since 6.0R) [regression] o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122697 net [ath] Atheros card is not well supported o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge f kern/122839 net [multicast] FreeBSD 7 multicast routing problem f kern/122928 net [em] interface watchdog timeouts and stops receiving p o kern/123053 net [re][patch] re(4) unsupported hardware revision (8168/ 45 problems total. From owner-freebsd-net@FreeBSD.ORG Mon May 19 12:10:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22F561065675 for ; Mon, 19 May 2008 12:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0B6BC8FC1E for ; Mon, 19 May 2008 12:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4JCA3xN019960 for ; Mon, 19 May 2008 12:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4JCA3D4019959; Mon, 19 May 2008 12:10:03 GMT (envelope-from gnats) Date: Mon, 19 May 2008 12:10:03 GMT Message-Id: <200805191210.m4JCA3D4019959@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Marc Olzheim Cc: Subject: Re: kern/116185: [iwi] if_iwi driver leads system to reboot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marc Olzheim List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 12:10:04 -0000 The following reply was made to PR kern/116185; it has been noted by GNATS. From: Marc Olzheim To: matteo@FreeBSD.org, bug-followup@FreeBSD.org Cc: ggg_mail@inbox.ru, freebsd-net@FreeBSD.org, Marc Olzheim Subject: Re: kern/116185: [iwi] if_iwi driver leads system to reboot Date: Mon, 19 May 2008 14:00:45 +0200 > Can you still experience this problem on newer FreeBSD releases? Something similar, probably related happens on my laptop (HP pavillion dv6570ed) with a 3945abg chipset. wpa_supplicant can negotiate fine, but as soon as dhclient runs, the box panics. I haven't had time to set up proper dumping yet, so alas, I have no detailed information at this point. Marc From owner-freebsd-net@FreeBSD.ORG Mon May 19 12:17:12 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2FEF1065689; Mon, 19 May 2008 12:17:12 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by mx1.freebsd.org (Postfix) with ESMTP id A9E638FC1D; Mon, 19 May 2008 12:17:12 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Jolp9bRriViFbmzPgs2pVOLyuj5u8GQoc7BrXDp90aW0603/8O7KGAMJrdG9GyF8; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [24.144.77.185] (helo=joker.seclark.com) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1Jy41R-0006pq-Qw; Mon, 19 May 2008 07:59:21 -0400 Message-ID: <48316B98.5010503@earthlink.net> Date: Mon, 19 May 2008 07:59:20 -0400 From: Stephen Clark User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: linimon@freebsd.org References: <200805182247.m4IMlYqq015759@freefall.freebsd.org> In-Reply-To: <200805182247.m4IMlYqq015759@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec7998a3fb009baedc987b502ad52f3effa0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 24.144.77.185 Cc: freebsd-net@freebsd.org, gnats-admin@freebsd.org Subject: Re: kern/123796: FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 12:17:13 -0000 linimon@freebsd.org wrote: > Old Synopsis: Port mapping does not work > New Synopsis: FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not work > > Responsible-Changed-From-To: gnats-admin->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: Sun May 18 22:45:21 UTC 2008 > Responsible-Changed-Why: > Rescue this PR from the 'pending' category. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=123796 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > I had a similar problem until I turned on "options IPSEC_FILTERGIF" in my kernel config. Otherwise stuff coming out of the vpn tunnel doesn't go thru ipf. 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 Mon May 19 12:20:39 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99DC31065672 for ; Mon, 19 May 2008 12:20:39 +0000 (UTC) (envelope-from proks@logos.sky.od.ua) Received: from logos.sky.od.ua (logos.sky.od.ua [81.25.224.11]) by mx1.freebsd.org (Postfix) with ESMTP id 4FE138FC1B for ; Mon, 19 May 2008 12:20:39 +0000 (UTC) (envelope-from proks@logos.sky.od.ua) Received: from localhost (localhost [127.0.0.1]) by logos.sky.od.ua (Postfix) with ESMTP id 99FEB102CD4; Mon, 19 May 2008 15:20:36 +0300 (EEST) Date: Mon, 19 May 2008 15:20:36 +0300 (EEST) From: "Prokofiev S.P." To: Jack Vogel In-Reply-To: <2a41acea0805161151l5b51d2edl84d0ac30fa77cad5@mail.gmail.com> Message-ID: <20080519150851.W43593@logos.sky.od.ua> References: <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> <20080516210223.A19166@logos.sky.od.ua> <2a41acea0805161151l5b51d2edl84d0ac30fa77cad5@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 12:20:39 -0000 I understand it, but where is the patch ? I found the mailist http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-10/msg00754.html and that http://blog.pfsense.org/?m=200711 but link http://www.higherorder.com.au/2007/6/25/intel_82573_patch is broked... On Fri, 16 May 2008, Jack Vogel wrote: > On Fri, May 16, 2008 at 11:09 AM, Prokofiev S.P. wrote: >> >> >> How install the fix to the 82573 NIC eeprom? >> Please help... > > Once you locate the fix its a zip file as I recall, when unzipped it is > a DOS executable, you can make a driver diskette and then put > the patcher on that (or a USB drive if you have one that is bootable) > then run the patcher from DOS. > > I am not sure this is the source of your problem, but absolutely any > SuperMicro system that has an 82573 should have this fix applied. > > Regards, > > Jack > >> On Fri, 16 May 2008, Jack Vogel wrote: >> >>> Did you ever install the fix to the 82573 NIC eeprom? If not >>> search mail archive for 82573, it's a DOS binary that will >>> patch your prom. Also check for BIOS update from SM. >>> >>> Jack >>> >> > From owner-freebsd-net@FreeBSD.ORG Mon May 19 12:32:15 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D5891065670; Mon, 19 May 2008 12:32:15 +0000 (UTC) (envelope-from z@zlo.nu) Received: from mzh.zlo.nu (ns0.zlo.nu [85.17.141.90]) by mx1.freebsd.org (Postfix) with ESMTP id E32EC8FC1B; Mon, 19 May 2008 12:32:14 +0000 (UTC) (envelope-from z@zlo.nu) Received: by mzh.zlo.nu (Postfix, from userid 1000) id 4F64A1421B; Mon, 19 May 2008 14:00:45 +0200 (CEST) Date: Mon, 19 May 2008 14:00:45 +0200 From: Marc Olzheim To: matteo@FreeBSD.org, bug-followup@FreeBSD.org Message-ID: <20080519120045.GA22238@zlo.nu> References: <200805171052.m4HAqrto091588@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200805171052.m4HAqrto091588@freefall.freebsd.org> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Marc Olzheim , freebsd-net@FreeBSD.org, ggg_mail@inbox.ru Subject: Re: kern/116185: [iwi] if_iwi driver leads system to reboot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 12:32:15 -0000 > Can you still experience this problem on newer FreeBSD releases? Something similar, probably related happens on my laptop (HP pavillion dv6570ed) with a 3945abg chipset. wpa_supplicant can negotiate fine, but as soon as dhclient runs, the box panics. I haven't had time to set up proper dumping yet, so alas, I have no detailed information at this point. Marc From owner-freebsd-net@FreeBSD.ORG Mon May 19 12:50:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5A1C1065679 for ; Mon, 19 May 2008 12:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A4ADE8FC16 for ; Mon, 19 May 2008 12:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4JCo4Mm024652 for ; Mon, 19 May 2008 12:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4JCo44W024651; Mon, 19 May 2008 12:50:04 GMT (envelope-from gnats) Date: Mon, 19 May 2008 12:50:04 GMT Message-Id: <200805191250.m4JCo44W024651@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Manuel Kasper Cc: Subject: Re: kern/78090: [ipf] ipf filtering on bridged packets doesn't work if ipfw is loaded X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Manuel Kasper List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 12:50:04 -0000 The following reply was made to PR kern/78090; it has been noted by GNATS. From: Manuel Kasper To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/78090: [ipf] ipf filtering on bridged packets doesn't work if ipfw is loaded Date: Mon, 19 May 2008 14:13:43 +0200 This PR can be closed as far as I'm concerned. It's been more than three years anyway :) m0n0wall has a workaround/fix for this now (see http://svn.m0n0.ch/wall/branches/freebsd6/build/patches/kernel/kernel-6.patch) , and as mlaier pointed out, BRIDGE is deprecated anyway and we should switch to if_bridge. - Manuel From owner-freebsd-net@FreeBSD.ORG Mon May 19 13:07:27 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46D591065671 for ; Mon, 19 May 2008 13:07:27 +0000 (UTC) (envelope-from john@roof1.dnepro.net) Received: from roof1.dnepro.net (a66.dnepro.net [212.3.111.66]) by mx1.freebsd.org (Postfix) with ESMTP id ADB1A8FC19 for ; Mon, 19 May 2008 13:07:25 +0000 (UTC) (envelope-from john@roof1.dnepro.net) Received: from roof1.dnepro.net (localhost [127.0.0.1]) by roof1.dnepro.net (8.14.1/8.14.1) with ESMTP id m4JD7MJ1045251 for ; Mon, 19 May 2008 16:07:23 +0300 (EEST) (envelope-from john@roof1.dnepro.net) Received: (from john@localhost) by roof1.dnepro.net (8.14.1/8.14.1/Submit) id m4JD7McV045250 for freebsd-net@freebsd.org; Mon, 19 May 2008 16:07:22 +0300 (EEST) (envelope-from john) Date: Mon, 19 May 2008 16:07:22 +0300 From: Eugene Perevyazko To: freebsd-net@freebsd.org Message-ID: <20080519130722.GA40822@roof1.dnepro.net> Mail-Followup-To: freebsd-net@freebsd.org References: <20080515152607.GA36663@roof1.dnepro.net> <482C6303.9000904@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482C6303.9000904@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on roof1.dnepro.net X-Virus-Status: Clean Subject: Re: How to inject fullsize 802.1q-tagged frame through BPF? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 13:07:27 -0000 On Thu, May 15, 2008 at 12:21:23PM -0400, Sam Leffler wrote: > Eugene Perevyazko wrote: > > Is there a way to inject full-mtu vlan-tagged frame through BPF on parent > >device? > > I'd like not to open several tenths of BPFs for each vlanN if it's > > possible. > > bpf write code in the kernel calculates header size when packets are > injected. This is likely based on the frames being stock 802.3 so would > require mods to the bpf code to handle the additional space for the tag. I've made a simple patch that works for me on FreeBSD 6.2-RELEASE #1. Not sure if this is the way to do it, but it "just works". May be someone else will need such feature too. Eugene Perevyazko --- bpf.c.old Mon May 19 10:47:55 2008 +++ bpf.c Mon May 19 10:57:44 2008 @@ -64,6 +64,7 @@ #include #include +#include #include #include @@ -617,7 +618,9 @@ return (0); bzero(&dst, sizeof(dst)); - error = bpf_movein(uio, (int)d->bd_bif->bif_dlt, ifp->if_mtu, + /* Use VLAN_MTU capability, if supported */ + error = bpf_movein(uio, (int)d->bd_bif->bif_dlt, + ifp->if_mtu + ( (ifp->if_capenable & IFCAP_VLAN_MTU) ? ETHER_VLAN_ENCAP_LEN : 0 ), &m, &dst, d->bd_wfilter); if (error) return (error); From owner-freebsd-net@FreeBSD.ORG Mon May 19 15:10:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 109131065686 for ; Mon, 19 May 2008 15:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ED01C8FC14 for ; Mon, 19 May 2008 15:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4JFA2Z5035588 for ; Mon, 19 May 2008 15:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4JFA2vP035587; Mon, 19 May 2008 15:10:02 GMT (envelope-from gnats) Date: Mon, 19 May 2008 15:10:02 GMT Message-Id: <200805191510.m4JFA2vP035587@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 15:10:03 -0000 The following reply was made to PR kern/123603; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: John , freebsd-gnats-submit@freebsd.org, andre@FreeBSD.org Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN Date: Mon, 19 May 2008 10:06:40 -0400 On Monday 12 May 2008 03:45:16 am John wrote: > >Number: 123603 > >Category: amd64 > >Synopsis: tcp_do_segment and Received duplicate SYN > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon May 12 07:50:01 UTC 2008 > >Closed-Date: > >Last-Modified: > >Originator: John > >Release: FB7.0 (x64) > >Organization: > > NULL > > >Environment: > > FreeBSD mail.mydomain.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu Mar 6 > 12:04:57 HKT 2008 root@mydomain.com:/usr/src/sys/amd64/compile/FB7NEW > amd64 > > >Description: > > A FreeBSD 7.0 (x64) Lighttpd Web Server with most-updated ports and patchs. > when a client connect and view a static HTML file, At the first time > (before web server idle time), it needs to wait a long time to establish a > connection, OR when this server try to download file from Internet, there > are lots of logs messages just like below: > > May 12 11:57:54 mail kernel: TCP: [55.66.77.88]:41792 to [11.22.33.44]:80 > tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer > and retransmitting SYN|ACK > May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:45979 to > [11.22.33.44]:63372 tcpflags 0x10; tcp_do_segment: FIN_WAIT_1: > Received 1448 bytes of data after socket was closed, sending RST and > removing tcpcb May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:21 to > [11.22.33.44]:55007 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: > Received 13 bytes of data after socket was closed, sending RST and removing > tcpcb > > >How-To-Repeat: > > any type of connection will generate above log messages. You can either comment out all the log(LOG_DEBUG, ...) calls in /sys/netinet/tcp*.c or change your /etc/syslog.conf to not send kern.debug messages to the console. I think these messages should probably be conditional on a kernel option FWIW. -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Mon May 19 15:55:32 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 518CC106567A for ; Mon, 19 May 2008 15:55:32 +0000 (UTC) (envelope-from proks@logos.sky.od.ua) Received: from logos.sky.od.ua (logos.sky.od.ua [81.25.224.11]) by mx1.freebsd.org (Postfix) with ESMTP id 07F248FC1E for ; Mon, 19 May 2008 15:55:31 +0000 (UTC) (envelope-from proks@logos.sky.od.ua) Received: from localhost (localhost [127.0.0.1]) by logos.sky.od.ua (Postfix) with ESMTP id 46169102CDB; Mon, 19 May 2008 18:55:30 +0300 (EEST) Date: Mon, 19 May 2008 18:55:30 +0300 (EEST) From: "Prokofiev S.P." To: Jack Vogel In-Reply-To: <2a41acea0805161151l5b51d2edl84d0ac30fa77cad5@mail.gmail.com> Message-ID: <20080519185013.O80128@logos.sky.od.ua> References: <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> <20080516210223.A19166@logos.sky.od.ua> <2a41acea0805161151l5b51d2edl84d0ac30fa77cad5@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 15:55:32 -0000 I found the fix utility on link http://www.mullet.se/support/dcgdis.zip and run under DOS, but it answer - " Update not needed" ! Sergey From owner-freebsd-net@FreeBSD.ORG Mon May 19 16:46:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85DAE106578D for ; Mon, 19 May 2008 16:46:46 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id 09D748FC0A for ; Mon, 19 May 2008 16:46:45 +0000 (UTC) (envelope-from mwm@mired.org) Received: (qmail 3290 invoked from network); 19 May 2008 12:20:28 -0400 Received: from unknown (HELO mbook.local) (192.168.195.193) by 0 with SMTP; 19 May 2008 12:20:28 -0400 Date: Mon, 19 May 2008 12:20:00 -0400 From: Mike Meyer To: Jeremy Chadwick Message-ID: <20080519122000.526b2964@mbook.local> In-Reply-To: <20080519063133.GA54791@eos.sc1.parodius.com> References: <130587.38887.qm@web46316.mail.sp1.yahoo.com> <20080519063133.GA54791@eos.sc1.parodius.com> Organization: Meyer Consulting X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.2.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, John Timony Subject: Re: Net Mask Prob! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 16:46:46 -0000 On Sun, 18 May 2008 23:31:33 -0700 Jeremy Chadwick wro= te: > On Sun, May 18, 2008 at 09:40:37PM -0700, John Timony wrote: > > Hi,all > > =C2=A0 > > I have installed Freebsd 7.0 on my Acer TravelMate 220,my router ip is = 192.168.0.1,the ip of my Freebsd is 192.168.1.4,Net Mask is 255.255.0.0,Why= my system can not connect wiht the router? > > =C2=A0 > > any idea? >=20 > Chances are your router uses 255.255.255.0 as a default netmask; most > residential routers do. FreeBSD doesn't have any issues/bugs relating > to netmasks which would cause what you're seeing. Freebsd should be using 255.255.255.0 as a default netmask for the 192.168 block as well. That's what it's defined to be. Changing that means fixing it everywhere. Also, as you get further from common setups, residential and soho routers tend to get flakier. Given that most users of such don't have hundreds of hosts and don't need two internal networks, a /23 in 192.168.0.0 qualifies as uncommon; it certainly gave me fits. I found that splitting the /24 into a pair of /25s worked better. > Additionally, your request probably should have gone to -net, not > -hackers. Yup. Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E1A6106568E for ; Mon, 19 May 2008 17:31:27 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from server13.yawl.com.br (server13.yawl.com.br [200.175.230.13]) by mx1.freebsd.org (Postfix) with ESMTP id D94568FC14 for ; Mon, 19 May 2008 17:31:25 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from [200.175.230.21] ([200.175.230.21]) by server13.yawl.com.br (IceWarp 9.2.1) with ASMTP id ZWL54608 for ; Mon, 19 May 2008 14:18:08 -0300 Message-ID: <4831B670.7060502@yawl.com.br> Date: Mon, 19 May 2008 14:18:40 -0300 From: Einstein Oliveira User-Agent: Thunderbird 1.5.0.12 (X11/20080430) MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 17:31:27 -0000 Hi all, In an attempt to change from pppoed + ppp to mpd I'm having some strange behaviour with the later on the same host that usually handles 100+ clients with the former. Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. Users can connect without any problem. After a few minutes a SECOND mpd process is initiated and this one consumes all idle processing of the host. Whoever is connected before that still remains connected but no new user can get in anymore. Also logging stops being generated. The only solution is a killall -KILL on mpd. On another host I have the same configuration working as expected but with less than 50 clients. Both configurations are the same from mpd.conf.sample. So I'm looking for any suggestions that somebody has been using to handle that many pppoe connections (100+) with mpd. Thanks, -- Einstein Oliveira einstein@yawl.com.br ___________________________________________________ Yawl Internet Ltda. http://www.yawl.com.br/ From owner-freebsd-net@FreeBSD.ORG Mon May 19 17:55:59 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79B67106566B for ; Mon, 19 May 2008 17:55:59 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outo.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 5DF798FC2D for ; Mon, 19 May 2008 17:55:59 +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.40) with ESMTP; Tue, 20 May 2008 06:01:59 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 536A02D6004; Mon, 19 May 2008 10:55:57 -0700 (PDT) Message-ID: <4831BF2D.3040802@elischer.org> Date: Mon, 19 May 2008 10:55:57 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Einstein Oliveira References: <4831B670.7060502@yawl.com.br> In-Reply-To: <4831B670.7060502@yawl.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 17:55:59 -0000 Einstein Oliveira wrote: > Hi all, > > In an attempt to change from pppoed + ppp to mpd I'm having some strange > behaviour with the later on the same host that usually handles 100+ > clients with the former. > > Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. > Users can connect without any problem. > > After a few minutes a SECOND mpd process is initiated and this one > consumes all idle processing of the host. > > Whoever is connected before that still remains connected but no new user > can get in anymore. Also logging stops being generated. > > The only solution is a killall -KILL on mpd. > > On another host I have the same configuration working as expected but > with less than 50 clients. > > Both configurations are the same from mpd.conf.sample. > > So I'm looking for any suggestions that somebody has been using to > handle that many pppoe connections (100+) with mpd. > > > > Thanks, > people have handled many more than 100 I think.. however there is no reason that a 2nd should start up. what is teh PPID of the 2nd? are you sure that it isn't being started up by whatever starts up the first? From owner-freebsd-net@FreeBSD.ORG Mon May 19 18:22:05 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B8941065743 for ; Mon, 19 May 2008 18:22:05 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from server13.yawl.com.br (server13.yawl.com.br [200.175.230.13]) by mx1.freebsd.org (Postfix) with ESMTP id B20CE8FC17 for ; Mon, 19 May 2008 18:22:03 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from [200.175.230.21] ([200.175.230.21]) by server13.yawl.com.br (IceWarp 9.2.1) with ASMTP id ZXP01500 for ; Mon, 19 May 2008 15:22:00 -0300 Message-ID: <4831C56C.8090708@yawl.com.br> Date: Mon, 19 May 2008 15:22:36 -0300 From: Einstein Oliveira User-Agent: Thunderbird 1.5.0.12 (X11/20080430) MIME-Version: 1.0 To: FreeBSD Net References: <4831B670.7060502@yawl.com.br> <4831BF2D.3040802@elischer.org> In-Reply-To: <4831BF2D.3040802@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 18:22:05 -0000 Julian Elischer wrote: > Einstein Oliveira wrote: >> Hi all, >> >> In an attempt to change from pppoed + ppp to mpd I'm having some >> strange behaviour with the later on the same host that usually handles >> 100+ clients with the former. >> >> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. >> Users can connect without any problem. >> >> After a few minutes a SECOND mpd process is initiated and this one >> consumes all idle processing of the host. >> >> Whoever is connected before that still remains connected but no new >> user can get in anymore. Also logging stops being generated. >> >> The only solution is a killall -KILL on mpd. >> >> On another host I have the same configuration working as expected but >> with less than 50 clients. >> >> Both configurations are the same from mpd.conf.sample. >> >> So I'm looking for any suggestions that somebody has been using to >> handle that many pppoe connections (100+) with mpd. >> >> >> >> Thanks, >> > > > people have handled many more than 100 I think.. > however there is no reason that a 2nd should start up. > what is teh PPID of the 2nd? > > are you sure that it isn't being started up by whatever starts up the > first? > > The second process has a bigger PID than the first and I'm using the default /usr/local/etc/rc.d/mpd5 as startup script with mpd_enable="YES" on /etc/rc.conf. -- Einstein Oliveira einstein@yawl.com.br ___________________________________________________ Yawl Internet Ltda. http://www.yawl.com.br/ From owner-freebsd-net@FreeBSD.ORG Mon May 19 18:27:58 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F5EC1065670 for ; Mon, 19 May 2008 18:27:58 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from server13.yawl.com.br (server13.yawl.com.br [200.175.230.13]) by mx1.freebsd.org (Postfix) with ESMTP id E6AEA8FC0A for ; Mon, 19 May 2008 18:27:56 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from [200.175.230.21] ([200.175.230.21]) by server13.yawl.com.br (IceWarp 9.2.1) with ASMTP id ZXU09353 for ; Mon, 19 May 2008 15:27:53 -0300 Message-ID: <4831C6CD.3070701@yawl.com.br> Date: Mon, 19 May 2008 15:28:29 -0300 From: Einstein Oliveira User-Agent: Thunderbird 1.5.0.12 (X11/20080430) MIME-Version: 1.0 To: FreeBSD Net References: <4831B670.7060502@yawl.com.br> <4831BF2D.3040802@elischer.org> In-Reply-To: <4831BF2D.3040802@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 18:27:58 -0000 Julian Elischer wrote: > Einstein Oliveira wrote: >> Hi all, >> >> In an attempt to change from pppoed + ppp to mpd I'm having some >> strange behaviour with the later on the same host that usually handles >> 100+ clients with the former. >> >> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. >> Users can connect without any problem. >> >> After a few minutes a SECOND mpd process is initiated and this one >> consumes all idle processing of the host. >> >> Whoever is connected before that still remains connected but no new >> user can get in anymore. Also logging stops being generated. >> >> The only solution is a killall -KILL on mpd. >> >> On another host I have the same configuration working as expected but >> with less than 50 clients. >> >> Both configurations are the same from mpd.conf.sample. >> >> So I'm looking for any suggestions that somebody has been using to >> handle that many pppoe connections (100+) with mpd. >> >> >> >> Thanks, >> > > > people have handled many more than 100 I think.. > however there is no reason that a 2nd should start up. > what is teh PPID of the 2nd? Right now I can't try to run mpd to verify this information but as soon as I can I'll send this to the list. > > are you sure that it isn't being started up by whatever starts up the > first? > > -- Einstein Oliveira einstein@yawl.com.br ___________________________________________________ Yawl Internet Ltda. http://www.yawl.com.br/ From owner-freebsd-net@FreeBSD.ORG Mon May 19 18:36:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A809106567D for ; Mon, 19 May 2008 18:36:22 +0000 (UTC) (envelope-from rahman.sazzadur@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 521B98FC18 for ; Mon, 19 May 2008 18:36:21 +0000 (UTC) (envelope-from rahman.sazzadur@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1122201ywe.13 for ; Mon, 19 May 2008 11:36:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; bh=YnGMFhMEn2yU/VyBa3gA95olxEPMCjJXvI7cfYfbrl4=; b=XqzQZKkc9CRjKBkpZ80/zfHMrz9jbDzZItSGPL0nN7AY3VLR5tAcBL66W0Ij8y7SyNMQ8swpeXjzsZJ/srHD8zClKwrECVsVZsuhLhATf0wXIAPmYgZcj3YhDeb+j4yzP9TzFy8x3iG0/IBInnPPmMdkik/41tqew8EzrNfOZXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=aPGxlII1XKJ/GSt3G0DbL5c84jHyDo6xJSBlVACsBybMROwg6OkyAP+44jd2e8/pSIt4U4ezEx1gdQroJT+F75t8wYXqOVo86/ZEZV7lk+rAKTNSOOzsS65fohWKi/x+cksvHHkMJscT04vp7p75Tf7tOeyEuOAD3f6wOY/h+NU= Received: by 10.150.148.19 with SMTP id v19mr6605963ybd.240.1211220687107; Mon, 19 May 2008 11:11:27 -0700 (PDT) Received: by 10.150.138.5 with HTTP; Mon, 19 May 2008 11:11:26 -0700 (PDT) Message-ID: <82bdb5ec0805191111h17fa4391uf2021104adbf606f@mail.gmail.com> Date: Mon, 19 May 2008 13:11:26 -0500 From: "sazzadur rahman" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: techerst@wanadoo.fr, atiq@ou.edu, olivier.civel@gmail.com Subject: A query regarding interop between BSD SCTP and lksctp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 18:36:22 -0000 Hello, We are using SCTP client on Linux (Fedora 5) and SCTP server on FreeBSD 7.0. Client-Server communication works fine. However, when we send ASCONF (ADD_IP) from Client to the server, it seems that FreeBSD does not respond with ASCONF_ACK to the Client. Is there any interop issue between BSD SCTP and lksctp? Please let us know if you have any questions. Best Regards, Md Sazzadur Rahman Graduate Student, School of Computer Science, University of Oklahoma, Norman, Oklahoma, USA From owner-freebsd-net@FreeBSD.ORG Mon May 19 18:58:59 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DBDC106566C for ; Mon, 19 May 2008 18:58:59 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outC.internet-mail-service.net (outc.internet-mail-service.net [216.240.47.226]) by mx1.freebsd.org (Postfix) with ESMTP id 548178FC12 for ; Mon, 19 May 2008 18:58:54 +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.40) with ESMTP; Tue, 20 May 2008 07:05:34 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 978C02D6023; Mon, 19 May 2008 11:58:53 -0700 (PDT) Message-ID: <4831CDEE.8060106@elischer.org> Date: Mon, 19 May 2008 11:58:54 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Einstein Oliveira References: <4831B670.7060502@yawl.com.br> <4831BF2D.3040802@elischer.org> <4831C56C.8090708@yawl.com.br> In-Reply-To: <4831C56C.8090708@yawl.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 18:58:59 -0000 Einstein Oliveira wrote: > Julian Elischer wrote: >> Einstein Oliveira wrote: >>> Hi all, >>> >>> In an attempt to change from pppoed + ppp to mpd I'm having some >>> strange behaviour with the later on the same host that usually >>> handles 100+ clients with the former. >>> >>> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. >>> Users can connect without any problem. >>> >>> After a few minutes a SECOND mpd process is initiated and this one >>> consumes all idle processing of the host. >>> >>> Whoever is connected before that still remains connected but no new >>> user can get in anymore. Also logging stops being generated. >>> >>> The only solution is a killall -KILL on mpd. >>> >>> On another host I have the same configuration working as expected but >>> with less than 50 clients. >>> >>> Both configurations are the same from mpd.conf.sample. >>> >>> So I'm looking for any suggestions that somebody has been using to >>> handle that many pppoe connections (100+) with mpd. >>> >>> >>> >>> Thanks, >>> >> >> >> people have handled many more than 100 I think.. >> however there is no reason that a 2nd should start up. >> what is teh PPID of the 2nd? >> >> are you sure that it isn't being started up by whatever starts up the >> first? >> >> > > The second process has a bigger PID than the first and I'm using the > default /usr/local/etc/rc.d/mpd5 as startup script with mpd_enable="YES" > on /etc/rc.conf. what about the PPID? (Parent PID) ps alx shows this. > From owner-freebsd-net@FreeBSD.ORG Mon May 19 19:00:53 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A655106566B for ; Mon, 19 May 2008 19:00:53 +0000 (UTC) (envelope-from peter.lei@ieee.org) Received: from QMTA03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 4AFBA8FC0A for ; Mon, 19 May 2008 19:00:53 +0000 (UTC) (envelope-from peter.lei@ieee.org) Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA03.emeryville.ca.mail.comcast.net with comcast id TWKq1Z01H16AWCUA300p00; Mon, 19 May 2008 18:44:53 +0000 Received: from macbookpro.local ([67.167.15.209]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id TWkl1Z0034WeFZP8S00000; Mon, 19 May 2008 18:44:52 +0000 X-Authority-Analysis: v=1.0 c=1 a=K-Bm9VoBQhoA:10 a=DkW5kUONJxUA:10 a=6I5d2MoRAAAA:8 a=vY8dNVhbuptUNI-sSVIA:9 a=B8q0cFn1BvveVj3arLwA:7 a=TZ9d5xe7rnfH1-CGmG_nuxUXNOkA:4 a=SV7veod9ZcQA:10 a=8b0TY1xhFYQA:10 Message-ID: <4831CA98.7050807@ieee.org> Date: Mon, 19 May 2008 13:44:40 -0500 From: Peter Lei User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: sazzadur rahman References: <82bdb5ec0805191111h17fa4391uf2021104adbf606f@mail.gmail.com> In-Reply-To: <82bdb5ec0805191111h17fa4391uf2021104adbf606f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: techerst@wanadoo.fr, freebsd-net@freebsd.org, atiq@ou.edu, olivier.civel@gmail.com Subject: Re: A query regarding interop between BSD SCTP and lksctp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 19:00:53 -0000 Can you verify that the version of the stack in Fedora 5 implements the SCTP AUTH chunk? The FreeBSD stack will silently discard the ADD-IP chunk if it's not wrapped with an AUTH chunk as per the RFC. --peter sazzadur rahman wrote: > Hello, > We are using SCTP client on Linux (Fedora 5) and SCTP server on FreeBSD 7.0. > Client-Server communication works fine. However, when we send ASCONF > (ADD_IP) from Client to the server, it seems that FreeBSD does not respond > with ASCONF_ACK to the Client. Is there any interop issue between BSD SCTP > and lksctp? > > Please let us know if you have any questions. > > > Best Regards, > Md Sazzadur Rahman > Graduate Student, > School of Computer Science, > University of Oklahoma, > Norman, Oklahoma, USA > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Mon May 19 22:08:45 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C2CE106568C for ; Mon, 19 May 2008 22:08:45 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from server13.yawl.com.br (server13.yawl.com.br [200.175.230.13]) by mx1.freebsd.org (Postfix) with ESMTP id 8E4E78FC1C for ; Mon, 19 May 2008 22:08:44 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from [127.0.0.1] ([200.175.230.100]) by server13.yawl.com.br (IceWarp 9.2.1) with ASMTP id ZBB64041; Mon, 19 May 2008 19:08:41 -0300 Message-ID: <4831FA6A.1080906@yawl.com.br> Date: Mon, 19 May 2008 19:08:42 -0300 From: Einstein Oliveira User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Julian Elischer , FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080519-0, 19/05/2008), Outbound message X-Antivirus-Status: Clean Cc: Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 22:08:45 -0000 > Einstein Oliveira wrote: >> Julian Elischer wrote: >>> Einstein Oliveira wrote: >>>> Hi all, >>>> >>>> In an attempt to change from pppoed + ppp to mpd I'm having some >>>> strange behaviour with the later on the same host that usually >>>> handles 100+ clients with the former. >>>> >>>> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. >>>> Users can connect without any problem. >>>> >>>> After a few minutes a SECOND mpd process is initiated and this one >>>> consumes all idle processing of the host. >>>> >>>> Whoever is connected before that still remains connected but no new >>>> user can get in anymore. Also logging stops being generated. >>>> >>>> The only solution is a killall -KILL on mpd. >>>> >>>> On another host I have the same configuration working as expected but >>>> with less than 50 clients. >>>> >>>> Both configurations are the same from mpd.conf.sample. >>>> >>>> So I'm looking for any suggestions that somebody has been using to >>>> handle that many pppoe connections (100+) with mpd. >>>> >>>> >>>> >>>> Thanks, >>>> >>> >>> >>> people have handled many more than 100 I think.. >>> however there is no reason that a 2nd should start up. >>> what is teh PPID of the 2nd? >>> >>> are you sure that it isn't being started up by whatever starts up the >>> first? >>> >>> >> >> The second process has a bigger PID than the first and I'm using the >> default /usr/local/etc/rc.d/mpd5 as startup script with mpd_enable="YES" >> on /etc/rc.conf. > > what about the PPID? (Parent PID) ps alx shows this. > >> here is the output of ps -alx: 0 12573 1 0 20 0 5424 3468 kserel Ss ?? 0:00.15 /usr/local/sbin/mpd5 -p /va 0 12629 12573 283 131 0 5424 3452 - R ?? 0:36.94 /usr/local/sbin/mpd5 -p /va 0 12707 11713 0 96 0 1528 868 - R+ p0 0:00.00 grep mpd5 -- Einstein Oliveira einstein@yawl.com.br ___________________________________________________ Yawl Internet Ltda. http://www.yawl.com.br/ From owner-freebsd-net@FreeBSD.ORG Mon May 19 22:25:14 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84C99106564A for ; Mon, 19 May 2008 22:25:14 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outX.internet-mail-service.net (outx.internet-mail-service.net [216.240.47.247]) by mx1.freebsd.org (Postfix) with ESMTP id 7567E8FC15 for ; Mon, 19 May 2008 22:25:14 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Tue, 20 May 2008 10:31:55 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id B73852D6011; Mon, 19 May 2008 15:25:13 -0700 (PDT) Message-ID: <4831FE4A.8010002@elischer.org> Date: Mon, 19 May 2008 15:25:14 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Einstein Oliveira References: <4831FA6A.1080906@yawl.com.br> In-Reply-To: <4831FA6A.1080906@yawl.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 22:25:14 -0000 Einstein Oliveira wrote: >> Einstein Oliveira wrote: >>> Julian Elischer wrote: >>>> Einstein Oliveira wrote: >>>>> Hi all, >>>>> >>>>> In an attempt to change from pppoed + ppp to mpd I'm having some >>>>> strange behaviour with the later on the same host that usually >>>>> handles 100+ clients with the former. >>>>> >>>>> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. >>>>> Users can connect without any problem. >>>>> >>>>> After a few minutes a SECOND mpd process is initiated and this one >>>>> consumes all idle processing of the host. >>>>> >>>>> Whoever is connected before that still remains connected but no new >>>>> user can get in anymore. Also logging stops being generated. >>>>> >>>>> The only solution is a killall -KILL on mpd. >>>>> >>>>> On another host I have the same configuration working as expected >>>>> but with less than 50 clients. >>>>> >>>>> Both configurations are the same from mpd.conf.sample. >>>>> >>>>> So I'm looking for any suggestions that somebody has been using to >>>>> handle that many pppoe connections (100+) with mpd. >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> >>>> >>>> >>>> people have handled many more than 100 I think.. >>>> however there is no reason that a 2nd should start up. >>>> what is teh PPID of the 2nd? >>>> >>>> are you sure that it isn't being started up by whatever starts up >>>> the first? >>>> >>>> >>> >>> The second process has a bigger PID than the first and I'm using the >>> default /usr/local/etc/rc.d/mpd5 as startup script with >>> mpd_enable="YES" on /etc/rc.conf. >> >> what about the PPID? (Parent PID) ps alx shows this. >> >>> > > here is the output of ps -alx: > > 0 12573 1 0 20 0 5424 3468 kserel Ss ?? 0:00.15 > /usr/local/sbin/mpd5 -p /va > 0 12629 12573 283 131 0 5424 3452 - R ?? 0:36.94 > /usr/local/sbin/mpd5 -p /va > 0 12707 11713 0 96 0 1528 868 - R+ p0 0:00.00 > grep mpd5 > > sorry I repeated myself.. hmmm kserel... it's threaded? I didn't know that.. does top -H show a bunch of threads? So the first copy of mpd has spawned another while threaded. have you applied the patch for 6.3 in the 6.3 errata notifications? http://security.freebsd.org/advisories/FreeBSD-EN-08:01.libpthread.asc From owner-freebsd-net@FreeBSD.ORG Mon May 19 22:38:53 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D17751065674 for ; Mon, 19 May 2008 22:38:53 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from server13.yawl.com.br (server13.yawl.com.br [200.175.230.13]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9B88FC0A for ; Mon, 19 May 2008 22:38:52 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from [127.0.0.1] ([200.175.230.100]) by server13.yawl.com.br (IceWarp 9.2.1) with ASMTP id ZBF14050; Mon, 19 May 2008 19:38:50 -0300 Message-ID: <4832017B.30003@yawl.com.br> Date: Mon, 19 May 2008 19:38:51 -0300 From: Einstein Oliveira User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Julian Elischer References: <4831FA6A.1080906@yawl.com.br> <4831FE4A.8010002@elischer.org> In-Reply-To: <4831FE4A.8010002@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080519-0, 19/05/2008), Outbound message X-Antivirus-Status: Clean Cc: FreeBSD Net Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 22:38:53 -0000 Julian Elischer wrote: > Einstein Oliveira wrote: >>> Einstein Oliveira wrote: >>>> Julian Elischer wrote: >>>>> Einstein Oliveira wrote: >>>>>> Hi all, >>>>>> >>>>>> In an attempt to change from pppoed + ppp to mpd I'm having some >>>>>> strange behaviour with the later on the same host that usually >>>>>> handles 100+ clients with the former. >>>>>> >>>>>> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB >>>>>> Ram. Users can connect without any problem. >>>>>> >>>>>> After a few minutes a SECOND mpd process is initiated and this one >>>>>> consumes all idle processing of the host. >>>>>> >>>>>> Whoever is connected before that still remains connected but no >>>>>> new user can get in anymore. Also logging stops being generated. >>>>>> >>>>>> The only solution is a killall -KILL on mpd. >>>>>> >>>>>> On another host I have the same configuration working as expected >>>>>> but with less than 50 clients. >>>>>> >>>>>> Both configurations are the same from mpd.conf.sample. >>>>>> >>>>>> So I'm looking for any suggestions that somebody has been using to >>>>>> handle that many pppoe connections (100+) with mpd. >>>>>> >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>> >>>>> >>>>> people have handled many more than 100 I think.. >>>>> however there is no reason that a 2nd should start up. >>>>> what is teh PPID of the 2nd? >>>>> >>>>> are you sure that it isn't being started up by whatever starts up >>>>> the first? >>>>> >>>>> >>>> >>>> The second process has a bigger PID than the first and I'm using the >>>> default /usr/local/etc/rc.d/mpd5 as startup script with >>>> mpd_enable="YES" on /etc/rc.conf. >>> >>> what about the PPID? (Parent PID) ps alx shows this. >>> >>>> >> >> here is the output of ps -alx: >> >> 0 12573 1 0 20 0 5424 3468 kserel Ss ?? 0:00.15 >> /usr/local/sbin/mpd5 -p /va >> 0 12629 12573 283 131 0 5424 3452 - R ?? 0:36.94 >> /usr/local/sbin/mpd5 -p /va >> 0 12707 11713 0 96 0 1528 868 - R+ p0 0:00.00 >> grep mpd5 >> >> > sorry I repeated myself.. > hmmm kserel... it's threaded? I didn't know that.. > does top -H show a bunch of threads? 12720 root 96 0 8252K 5656K select 0:26 0.00% mpd5 12720 root 20 0 8252K 5656K kserel 0:26 0.00% mpd5 12720 root 20 0 8252K 5656K ksesig 0:26 0.00% mpd5 > > So the first copy of mpd has spawned another while threaded. > have you applied the patch for 6.3 in the 6.3 errata notifications? > > http://security.freebsd.org/advisories/FreeBSD-EN-08:01.libpthread.asc > > Not yet. This host is using the RELENG_6_3 tag but I can do that if you think it can help. -- Einstein Oliveira einstein@yawl.com.br ___________________________________________________ Yawl Internet Ltda. http://www.yawl.com.br/ From owner-freebsd-net@FreeBSD.ORG Mon May 19 22:41:35 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A30C5106567D for ; Mon, 19 May 2008 22:41:35 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outB.internet-mail-service.net (outb.internet-mail-service.net [216.240.47.225]) by mx1.freebsd.org (Postfix) with ESMTP id 5DC9E8FC15 for ; Mon, 19 May 2008 22:41:35 +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.40) with ESMTP; Tue, 20 May 2008 10:48:17 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 86EEE2D6010; Mon, 19 May 2008 15:41:34 -0700 (PDT) Message-ID: <4832021F.7070007@elischer.org> Date: Mon, 19 May 2008 15:41:35 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Einstein Oliveira References: <4831FA6A.1080906@yawl.com.br> <4831FE4A.8010002@elischer.org> <4832017B.30003@yawl.com.br> In-Reply-To: <4832017B.30003@yawl.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 22:41:35 -0000 Einstein Oliveira wrote: > Julian Elischer wrote: >> Einstein Oliveira wrote: >>>> Einstein Oliveira wrote: >>>>> Julian Elischer wrote: >>>>>> Einstein Oliveira wrote: >>>>>>> Hi all, >>>>>>> >>>>>>> In an attempt to change from pppoed + ppp to mpd I'm having some >>>>>>> strange behaviour with the later on the same host that usually >>>>>>> handles 100+ clients with the former. >>>>>>> >>>>>>> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB >>>>>>> Ram. Users can connect without any problem. >>>>>>> >>>>>>> After a few minutes a SECOND mpd process is initiated and this >>>>>>> one consumes all idle processing of the host. >>>>>>> >>>>>>> Whoever is connected before that still remains connected but no >>>>>>> new user can get in anymore. Also logging stops being generated. >>>>>>> >>>>>>> The only solution is a killall -KILL on mpd. >>>>>>> >>>>>>> On another host I have the same configuration working as expected >>>>>>> but with less than 50 clients. >>>>>>> >>>>>>> Both configurations are the same from mpd.conf.sample. >>>>>>> >>>>>>> So I'm looking for any suggestions that somebody has been using >>>>>>> to handle that many pppoe connections (100+) with mpd. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>> >>>>>> >>>>>> people have handled many more than 100 I think.. >>>>>> however there is no reason that a 2nd should start up. >>>>>> what is teh PPID of the 2nd? >>>>>> >>>>>> are you sure that it isn't being started up by whatever starts up >>>>>> the first? >>>>>> >>>>>> >>>>> >>>>> The second process has a bigger PID than the first and I'm using >>>>> the default /usr/local/etc/rc.d/mpd5 as startup script with >>>>> mpd_enable="YES" on /etc/rc.conf. >>>> >>>> what about the PPID? (Parent PID) ps alx shows this. >>>> >>>>> >>> >>> here is the output of ps -alx: >>> >>> 0 12573 1 0 20 0 5424 3468 kserel Ss ?? 0:00.15 >>> /usr/local/sbin/mpd5 -p /va >>> 0 12629 12573 283 131 0 5424 3452 - R ?? 0:36.94 >>> /usr/local/sbin/mpd5 -p /va >>> 0 12707 11713 0 96 0 1528 868 - R+ p0 0:00.00 >>> grep mpd5 >>> >>> >> sorry I repeated myself.. >> hmmm kserel... it's threaded? I didn't know that.. >> does top -H show a bunch of threads? > > 12720 root 96 0 8252K 5656K select 0:26 0.00% mpd5 > 12720 root 20 0 8252K 5656K kserel 0:26 0.00% mpd5 > 12720 root 20 0 8252K 5656K ksesig 0:26 0.00% mpd5 > >> >> So the first copy of mpd has spawned another while threaded. >> have you applied the patch for 6.3 in the 6.3 errata notifications? >> >> http://security.freebsd.org/advisories/FreeBSD-EN-08:01.libpthread.asc >> >> > > Not yet. This host is using the RELENG_6_3 tag but I can do that if you > think it can help. check to see if the patch is applied. If not it should be because it will screw any process that is threaded and does forks. If that does not help we can look further, but first make sure this is done. > From owner-freebsd-net@FreeBSD.ORG Mon May 19 23:40:33 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3574106564A for ; Mon, 19 May 2008 23:40:33 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: from sub.vaned.net (sub.vaned.net [205.200.235.40]) by mx1.freebsd.org (Postfix) with ESMTP id 901988FC1A for ; Mon, 19 May 2008 23:40:33 +0000 (UTC) (envelope-from csjp@sub.vaned.net) Received: by sub.vaned.net (Postfix, from userid 1001) id 0E81233A; Mon, 19 May 2008 18:24:51 -0500 (CDT) Date: Mon, 19 May 2008 18:24:51 -0500 From: "Christian S.J. Peron" To: freebsd-net@freebsd.org Message-ID: <20080519232451.GA52560@sub.vaned.net> References: <20080515152607.GA36663@roof1.dnepro.net> <482C6303.9000904@freebsd.org> <20080519130722.GA40822@roof1.dnepro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080519130722.GA40822@roof1.dnepro.net> User-Agent: Mutt/1.4.2.3i Subject: Re: How to inject fullsize 802.1q-tagged frame through BPF? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 May 2008 23:40:33 -0000 Eugene, Thanks for the report. I will look into this. Although this patch technically works, I think the right solution to this problem is to introduce a new DLT_ for VLAN encapsulated frames. I will look into this problem in a bit more detail. On Mon, May 19, 2008 at 04:07:22PM +0300, Eugene Perevyazko wrote: > On Thu, May 15, 2008 at 12:21:23PM -0400, Sam Leffler wrote: > > Eugene Perevyazko wrote: > > > Is there a way to inject full-mtu vlan-tagged frame through BPF on parent > > >device? > > > I'd like not to open several tenths of BPFs for each vlanN if it's > > > possible. > > > > bpf write code in the kernel calculates header size when packets are > > injected. This is likely based on the frames being stock 802.3 so would > > require mods to the bpf code to handle the additional space for the tag. > > I've made a simple patch that works for me on FreeBSD 6.2-RELEASE #1. > Not sure if this is the way to do it, but it "just works". May be someone > else will need such feature too. > > Eugene Perevyazko > > > --- bpf.c.old Mon May 19 10:47:55 2008 > +++ bpf.c Mon May 19 10:57:44 2008 > @@ -64,6 +64,7 @@ > #include > > #include > +#include > #include > #include > > @@ -617,7 +618,9 @@ > return (0); > > bzero(&dst, sizeof(dst)); > - error = bpf_movein(uio, (int)d->bd_bif->bif_dlt, ifp->if_mtu, > + /* Use VLAN_MTU capability, if supported */ > + error = bpf_movein(uio, (int)d->bd_bif->bif_dlt, > + ifp->if_mtu + ( (ifp->if_capenable & IFCAP_VLAN_MTU) ? ETHER_VLAN_ENCAP_LEN : 0 ), > &m, &dst, d->bd_wfilter); > if (error) > return (error); > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue May 20 04:00:04 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E9141065671 for ; Tue, 20 May 2008 04:00:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E40748FC13 for ; Tue, 20 May 2008 04:00:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4K403XG001164 for ; Tue, 20 May 2008 04:00:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4K403Nn001163; Tue, 20 May 2008 04:00:03 GMT (envelope-from gnats) Date: Tue, 20 May 2008 04:00:03 GMT Message-Id: <200805200400.m4K403Nn001163@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "yes298 yes298" Cc: Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yes298 yes298 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 04:00:04 -0000 The following reply was made to PR kern/123603; it has been noted by GNATS. From: "yes298 yes298" To: "John Baldwin" Cc: freebsd-gnats-submit@freebsd.org, andre@freebsd.org Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN Date: Tue, 20 May 2008 11:24:32 +0800 ------=_Part_19869_29339230.1211253872117 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear Sir, Thank you so much for your reply. My FreeBSD 7.0(x64) Lighttpd web server connects to a 100M broadband line, after testing many times, I found that, when first time to view my website, it needed to take almost 5~8 seconds to completely open the homepage which is only a static HTML file with content "coming soon", and there are some error log about TCP connection found on our web server, it seems that my FreeBSD 7.0 web server has problem to establish TCP connection. Before the web server idle time (30s), there are no any delay to re-view the homepage (Press F5), but after 30 seconds, it needed to take another 5~8 seconds to re-view, and the log messages will be repeated. May 15 15:18:21 mail kernel: TCP: [203.186.95.8]:12728 to [58.177.222.113]:80 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK May 15 15:19:03 mail kernel: TCP: [221.127.88.188]:5128 to [58.177.222.113]:80 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK I know how to disable these log messages, but I would like to know that the delay is because of receiving duplicate SYN? is it normal message? Please help me to solve the problem, thanks !!!! Thank you so much! Best regards, Victor 2008/5/19 John Baldwin : > On Monday 12 May 2008 03:45:16 am John wrote: > > >Number: 123603 > > >Category: amd64 > > >Synopsis: tcp_do_segment and Received duplicate SYN > > >Confidential: no > > >Severity: critical > > >Priority: high > > >Responsible: freebsd-amd64 > > >State: open > > >Quarter: > > >Keywords: > > >Date-Required: > > >Class: sw-bug > > >Submitter-Id: current-users > > >Arrival-Date: Mon May 12 07:50:01 UTC 2008 > > >Closed-Date: > > >Last-Modified: > > >Originator: John > > >Release: FB7.0 (x64) > > >Organization: > > > > NULL > > > > >Environment: > > > > FreeBSD mail.mydomain.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu Mar 6 > > 12:04:57 HKT 2008 root@mydomain.com: > /usr/src/sys/amd64/compile/FB7NEW > > amd64 > > > > >Description: > > > > A FreeBSD 7.0 (x64) Lighttpd Web Server with most-updated ports and > patchs. > > when a client connect and view a static HTML file, At the first time > > (before web server idle time), it needs to wait a long time to establish > a > > connection, OR when this server try to download file from Internet, there > > are lots of logs messages just like below: > > > > May 12 11:57:54 mail kernel: TCP: [55.66.77.88]:41792 to [11.22.33.44 > ]:80 > > tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer > > and retransmitting SYN|ACK > > May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:45979 to > > [11.22.33.44]:63372 tcpflags 0x10; tcp_do_segment: FIN_WAIT_1: > > Received 1448 bytes of data after socket was closed, sending RST and > > removing tcpcb May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:21 to > > [11.22.33.44]:55007 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: > > Received 13 bytes of data after socket was closed, sending RST and > removing > > tcpcb > > > > >How-To-Repeat: > > > > any type of connection will generate above log messages. > > You can either comment out all the log(LOG_DEBUG, ...) calls > in /sys/netinet/tcp*.c or change your /etc/syslog.conf to not send > kern.debug > messages to the console. > > I think these messages should probably be conditional on a kernel option > FWIW. > > -- > John Baldwin > ------=_Part_19869_29339230.1211253872117 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Dear Sir,
 
Thank you so much for your reply.
 
My FreeBSD 7.0(x64) Lighttpd web server connects to a 100M broadband line, after testing many times, I found that, when first time to view my website, it needed to take almost 5~8 seconds to completely open the homepage which is only a static HTML file with content "coming soon", and there are some  error log about TCP connection found on our web server, it seems that my FreeBSD 7.0 web server has problem to establish TCP connection. Before the we b server idle time (30s), there are no any delay to re-view the homepage (Press F5), but after 30 seconds, it needed to take another 5~8 seconds to re-view, and the log messages will be repeated.
 
May 15 15:18:21 mail kernel: TCP: [203.186.95.8]:12728 to [58.177.222.113]:80 tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK
May 15 15:19:03 mail kernel: TCP: [221.127.88.188]:5128 to [58.177.222.113]:80 tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK
 
I know how to disable these log messages, but I would like to know that the delay is because
of receiving duplicate SYN? is it normal message? Please help me to solve the problem, thanks !!!!
Thank you so much!
 
Best regards,
Victor
 
2008/5/19 John Baldwin <jhb@freebsd.org>:
On Monday 12 May 2008 03:45:16 am John wrote:
> >Number:         123603
> >Category:       amd64
> >Synopsis:       tcp_do_segment and Received duplicate SYN
> >Confidential:   no
> >Severity:       critical
> >Priority:       high
> >Responsible:    freebsd-amd64
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Mon May 12 07:50:01 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     John
> >Release:        FB7.0 (x64)
> >Organization:
>
> NULL
>
> >Environment:
>
> FreeBSD mail.mydomain.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu Mar  6
> 12:04:57 HKT 2008     root@mydomain.com:/usr/src/sys/amd64/compile/FB7NEW
> amd64
>
> >Description:
>
> A FreeBSD 7.0 (x64) Lighttpd Web Server with most-updated ports and patchs.
> when a client connect and view a static HTML file, At the first time
> (before web server idle time), it needs to wait a long time to establish a
> connection, OR when this server try to download file from Internet, there
> are lots of logs messages just like below:
>
> May 12 11:57:54 mail kernel: TCP: [55.66.77.88]:41792 to [11.22.33.44]:80
> tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer
> and retransmitting SYN|ACK
> May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:45979 to
> [11.22.33.44]:63372 tcpflags 0x10<ACK>; tcp_do_segment: FIN_WAIT_1:
> Received 1448 bytes of data after socket was closed, sending RST and
> removing tcpcb May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:21 to
> [11.22.33.44]:55007 tcpflags 0x18<PUSH,ACK>; tcp_do_segment: FIN_WAIT_2:
> Received 13 bytes of data after socket was closed, sending RST and removing
> tcpcb
>
> >How-To-Repeat:
>
> any type of  connection will generate above log messages.

You can either comment out all the log(LOG_DEBUG, ...) calls
in /sys/netinet/tcp*.c or change your /etc/syslog.conf to not send kern.debug
messages to the console.

I think these messages should probably be conditional on a kernel option FWIW.

--
John Baldwin

------=_Part_19869_29339230.1211253872117-- From owner-freebsd-net@FreeBSD.ORG Tue May 20 07:29:09 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 875201065675 for ; Tue, 20 May 2008 07:29:09 +0000 (UTC) (envelope-from john@roof1.dnepro.net) Received: from roof1.dnepro.net (a66.dnepro.net [212.3.111.66]) by mx1.freebsd.org (Postfix) with ESMTP id F19478FC19 for ; Tue, 20 May 2008 07:29:08 +0000 (UTC) (envelope-from john@roof1.dnepro.net) Received: from roof1.dnepro.net (localhost [127.0.0.1]) by roof1.dnepro.net (8.14.1/8.14.1) with ESMTP id m4K7T57X033600 for ; Tue, 20 May 2008 10:29:06 +0300 (EEST) (envelope-from john@roof1.dnepro.net) Received: (from john@localhost) by roof1.dnepro.net (8.14.1/8.14.1/Submit) id m4K7T5F2033594 for freebsd-net@freebsd.org; Tue, 20 May 2008 10:29:05 +0300 (EEST) (envelope-from john) Date: Tue, 20 May 2008 10:29:05 +0300 From: Eugene Perevyazko To: freebsd-net@freebsd.org Message-ID: <20080520072905.GA28615@roof1.dnepro.net> Mail-Followup-To: freebsd-net@freebsd.org References: <20080515152607.GA36663@roof1.dnepro.net> <482C6303.9000904@freebsd.org> <20080519130722.GA40822@roof1.dnepro.net> <20080519232451.GA52560@sub.vaned.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080519232451.GA52560@sub.vaned.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on roof1.dnepro.net X-Virus-Status: Clean Subject: Re: How to inject fullsize 802.1q-tagged frame through BPF? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 May 2008 07:29:09 -0000 On Mon, May 19, 2008 at 06:24:51PM -0500, Christian S.J. Peron wrote: > Eugene, > > Thanks for the report. I will look into this. Although this patch technically > works, I think the right solution to this problem is to introduce a new DLT_ > for VLAN encapsulated frames. I will look into this problem in a bit more > detail. Thanks for your attention, Christian, but please consider that it's possible to mix tagged and untagged frames on interface and such DLT_ will put an artificial limit on this while technically there's no such limitation. Eugene Perevyazko From owner-freebsd-net@FreeBSD.ORG Tue May 20 15:10:05 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A3EA1065677 for ; Tue, 20 May 2008 15:10:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2B79D8FC15 for ; Tue, 20 May 2008 15:10:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4KFA5oH086436 for ; Tue, 20 May 2008 15:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4KFA5TK086435; Tue, 20 May 2008 15:10:05 GMT (envelope-from gnats) Date: Tue, 20 May 2008 15:10:05 GMT Message-Id: <200805201510.m4KFA5TK086435@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Andre Oppermann Cc: Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andre Oppermann List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 15:10:05 -0000 The following reply was made to PR kern/123603; it has been noted by GNATS. From: Andre Oppermann To: yes298 yes298 Cc: John Baldwin , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN Date: Tue, 20 May 2008 16:40:08 +0200 Victor, Please try two things: 1. Make sure that you don't have a problem with MTU sizes. Some ADSL customers with PPPoE have slightly smaller MTU sizes than normal ethernet. Make sure that ICMP unreach packets are not firewalled or filtered on your side. 2. There was a bug in the TCP options in FreeBSD 7.0-RELEASE that was giving problems with a smaller number of CPE devices for ADSL and Cablemodem customers. The problem is fixed in 7-STABLE. Only upgrading the kernel is sufficient. I hope this helps. If not, please provide some tcpdumps so we can see the packets that are exchanged. -- Andre yes298 yes298 wrote: > Dear Sir, > > Thank you so much for your reply. > > My FreeBSD 7.0(x64) Lighttpd web server connects to a 100M broadband line, > after testing many times, I found that, when first time to view my website, > it needed to take almost 5~8 seconds to completely open the homepage which > is only a static HTML file with content "coming soon", and there are some > error log about TCP connection found on our web server, it seems that my > FreeBSD 7.0 web server has problem to establish TCP connection. Before the > web server idle time (30s), there are no any delay to re-view the homepage > (Press F5), but after 30 seconds, it needed to take another 5~8 seconds to > re-view, and the log messages will be repeated. > > May 15 15:18:21 mail kernel: TCP: [203.186.95.8]:12728 to [58.177.222.113]:80 > tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and > retransmitting SYN|ACK > May 15 15:19:03 mail kernel: TCP: [221.127.88.188]:5128 to [58.177.222.113]:80 > tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and > retransmitting SYN|ACK > > I know how to disable these log messages, but I would like to know that the > delay is because > of receiving duplicate SYN? is it normal message? Please help me to solve > the problem, thanks !!!! > Thank you so much! > > Best regards, > Victor > > 2008/5/19 John Baldwin : > >> On Monday 12 May 2008 03:45:16 am John wrote: >>>> Number: 123603 >>>> Category: amd64 >>>> Synopsis: tcp_do_segment and Received duplicate SYN >>>> Confidential: no >>>> Severity: critical >>>> Priority: high >>>> Responsible: freebsd-amd64 >>>> State: open >>>> Quarter: >>>> Keywords: >>>> Date-Required: >>>> Class: sw-bug >>>> Submitter-Id: current-users >>>> Arrival-Date: Mon May 12 07:50:01 UTC 2008 >>>> Closed-Date: >>>> Last-Modified: >>>> Originator: John >>>> Release: FB7.0 (x64) >>>> Organization: >>> NULL >>> >>>> Environment: >>> FreeBSD mail.mydomain.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu Mar 6 >>> 12:04:57 HKT 2008 root@mydomain.com: >> /usr/src/sys/amd64/compile/FB7NEW >>> amd64 >>> >>>> Description: >>> A FreeBSD 7.0 (x64) Lighttpd Web Server with most-updated ports and >> patchs. >>> when a client connect and view a static HTML file, At the first time >>> (before web server idle time), it needs to wait a long time to establish >> a >>> connection, OR when this server try to download file from Internet, there >>> are lots of logs messages just like below: >>> >>> May 12 11:57:54 mail kernel: TCP: [55.66.77.88]:41792 to [11.22.33.44 >> ]:80 >>> tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer >>> and retransmitting SYN|ACK >>> May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:45979 to >>> [11.22.33.44]:63372 tcpflags 0x10; tcp_do_segment: FIN_WAIT_1: >>> Received 1448 bytes of data after socket was closed, sending RST and >>> removing tcpcb May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:21 to >>> [11.22.33.44]:55007 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: >>> Received 13 bytes of data after socket was closed, sending RST and >> removing >>> tcpcb >>> >>>> How-To-Repeat: >>> any type of connection will generate above log messages. >> You can either comment out all the log(LOG_DEBUG, ...) calls >> in /sys/netinet/tcp*.c or change your /etc/syslog.conf to not send >> kern.debug >> messages to the console. >> >> I think these messages should probably be conditional on a kernel option >> FWIW. >> >> -- >> John Baldwin >> > From owner-freebsd-net@FreeBSD.ORG Wed May 21 10:36:57 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89C7F106564A; Wed, 21 May 2008 10:36:57 +0000 (UTC) (envelope-from rpaulo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2AA588FC0A; Wed, 21 May 2008 10:36:57 +0000 (UTC) (envelope-from rpaulo@FreeBSD.org) Received: from freefall.freebsd.org (rpaulo@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4LAavXl019921; Wed, 21 May 2008 10:36:57 GMT (envelope-from rpaulo@freefall.freebsd.org) Received: (from rpaulo@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4LAavaM019917; Wed, 21 May 2008 10:36:57 GMT (envelope-from rpaulo) Date: Wed, 21 May 2008 10:36:57 GMT Message-Id: <200805211036.m4LAavaM019917@freefall.freebsd.org> To: rpaulo@FreeBSD.org, freebsd-net@FreeBSD.org, rpaulo@FreeBSD.org From: rpaulo@FreeBSD.org Cc: Subject: Re: kern/123123: [re][patch] Realtek RTL8111C detection and failure X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 May 2008 10:36:57 -0000 Synopsis: [re][patch] Realtek RTL8111C detection and failure Responsible-Changed-From-To: freebsd-net->rpaulo Responsible-Changed-By: rpaulo Responsible-Changed-When: Wed May 21 10:36:18 UTC 2008 Responsible-Changed-Why: I'm working on a patch since NetBSD seems to support this card. http://www.freebsd.org/cgi/query-pr.cgi?pr=123123 From owner-freebsd-net@FreeBSD.ORG Wed May 21 17:31:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D087D106566C for ; Wed, 21 May 2008 17:31:46 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id A30378FC19 for ; Wed, 21 May 2008 17:31:46 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2896242rvf.43 for ; Wed, 21 May 2008 10:31:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=5RvKaYC2QfZyhE6qiUZkxMLhh8W+cE5ZcZZEoJofKu4=; b=oImpsmW9sf4NK6QeiWMpplbCw3g8iheD+XoP4cKZLZgQcbd50jrfvzoqM3SyCU5sFFBfQxie9TqvwtVSukJC+1VP5DLRI/ZlQKL4S92Lb5vkntY7scd6ciq6Vsgfnu/n5c1ZO+Sdq+KVAulXF3oswkhttRZUx9crAWAnGcYA8rY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=aomSVxz4dZXaAkcNie/c8dYKmbE8jqy3cZHkW9jT0Z3OD1m06Ifq0OdsNqxgeYUKtRxp9BOpt9amCgk2RS3T9H6dKn0jRJkCKwqufHqwDLceb4WliYLtsssRtiLiTA0Sbr9TsiZHoF7CmK1Bm+I54yhLb4esqMSQIkiUtXRvQ40= Received: by 10.140.208.14 with SMTP id f14mr5220446rvg.283.1211391106325; Wed, 21 May 2008 10:31:46 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Wed, 21 May 2008 10:31:46 -0700 (PDT) Message-ID: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> Date: Wed, 21 May 2008 20:31:46 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 53a15072d3c74390 Subject: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 17:31:46 -0000 If one tries to use lagg0.2 style vlans on lagg0 interface configured from rc.conf it does't work. The problem is that all of the cloned interfaces (lagg0 , lagg0.2, etc) are created before any other interface configuration is done, and in this case lagg0 is created, then lagg0.2 is created. But because lagg0 does not have any members yet, it's MAC address is all zeroes, and this is inherited by the vlan interfaces. At the next step the members are added to the lagg0 interface and it's mac address gets set, but the vlan interfaces never see this change and remain with mac address 00:00:00:00:00:00 and in unusable state. Does it sound reasonable for the vlan(4) interfaces to update their mac address when their parent changes it. (this should probably look more like the parent telling the vlans attached to it that it's mac has changed, but i'm not sure if the parent knows about children interfaces) From owner-freebsd-net@FreeBSD.ORG Wed May 21 17:45:02 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 307941065679 for ; Wed, 21 May 2008 17:45:02 +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 BD06F8FC1D for ; Wed, 21 May 2008 17:45:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-064-185-072.pools.arcor-ip.net [88.64.185.72]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1JysN10Vvw-0004RW; Wed, 21 May 2008 19:44:59 +0200 Received: (qmail 45664 invoked from network); 21 May 2008 17:43:16 -0000 Received: from myhost.laiers.local (192.168.4.151) by laiers.local with SMTP; 21 May 2008 17:43:16 -0000 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Wed, 21 May 2008 19:44:42 +0200 User-Agent: KMail/1.9.9 References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> In-Reply-To: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805211944.42418.max@love2party.net> X-Provags-ID: V01U2FsdGVkX18+6E3Z1+RUAHYEmhOAtiNc9utn9plWa+5dm2J TdF4R/BefC2yAvfnwifZnVySxGtreonGS/TSmpPj1IskmJDDP6 6H4aUyNd1yi5/ceKtXYBA== Cc: Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 17:45:02 -0000 On Wednesday 21 May 2008 19:31:46 Niki Denev wrote: > If one tries to use lagg0.2 style vlans on lagg0 interface configured > from rc.conf it does't work. > The problem is that all of the cloned interfaces (lagg0 , lagg0.2, etc) > are created before any other interface configuration is done, > and in this case lagg0 is created, then lagg0.2 is created. > But because lagg0 does not have any members yet, it's MAC address > is all zeroes, and this is inherited by the vlan interfaces. > At the next step the members are added to the lagg0 interface and it's > mac address gets set, > but the vlan interfaces never see this change and remain with mac > address 00:00:00:00:00:00 and in unusable state. > > Does it sound reasonable for the vlan(4) interfaces to update their > mac address when their parent changes it. > (this should probably look more like the parent telling the vlans > attached to it that it's mac has changed, but > i'm not sure if the parent knows about children interfaces) It doesn't (and shouldn't have to). I'd simply add an EVENTHANDLER_INVOKE(ifaddr_event, ifp) to if_setlladdr() - we do that for INET[6] address already. Then vlan (and any other device interested in LLaddress changes) can simply register to that eventhandler and resync. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Wed May 21 19:11:21 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAA481065671 for ; Wed, 21 May 2008 19:11:21 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (neilhoggarth-2.dsl.easynet.co.uk [217.206.124.94]) by mx1.freebsd.org (Postfix) with ESMTP id BEDCB8FC1D for ; Wed, 21 May 2008 19:11:20 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (localhost [127.0.0.1]) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2) with ESMTP id m4LJBIrd001247 for ; Wed, 21 May 2008 20:11:18 +0100 (BST) (envelope-from neil@hoggarth.me.uk) Received: from localhost (njh@localhost) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2/Submit) with ESMTP id m4LJBIHs001244 for ; Wed, 21 May 2008 20:11:18 +0100 (BST) (envelope-from neil@hoggarth.me.uk) X-Authentication-Warning: neilhoggarth-2.dsl.easynet.co.uk: njh owned process doing -bs Date: Wed, 21 May 2008 20:11:18 +0100 (BST) From: Neil Hoggarth X-X-Sender: njh@neilhoggarth-2.dsl.easynet.co.uk To: freebsd-net@freebsd.org Message-ID: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: [em][panic] recursed on non-recursive mutex em0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 May 2008 19:11:22 -0000 Hi Folks, I opened PR kern/122928 last month, describing my problems with Intel PRO/1000 MT adaptor on 7-STABLE, with v6.7.3 of the em driver: every so often the machine would get into a state where it would repeatedly watchdog timeout the em0 interface, and the interface would stop receiving packets. A few weeks ago I cvsupped a newer version of the 7-STABLE source tree, after v6.9.0 of the em driver was MFCed. Since I started running on the newer build watchdog timeouts appear to be followed by a system panic rather than the freezing up of the interface. I have no hard evidence but it "feels like" the panics are happening under the same sort of circumstance that was previously triggering my watchdog problem (basically network activity combined with CPU load). A similar observation was made by Yani Karydis on the freebsd-stable mailing list earlier in the month: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042311.html I've now got a serial console set up, and I'm running a kernel with DDB support compiled in. I managed to get the information below out of the most recent panic. Is anyone able to use this to debug the situation? What else might I try to gather useful information? em0: watchdog timeout -- resetting panic: _mtx_lock_sleep: recursed on non-recursive mutex em0 @ /usr/src/sys/dev/em/if_em.c:1348 cpuid = 0 KDB: enter: panic [thread pid 14 tid 100005 ] Stopped at kdb_enter_why+0x3d: movq $0,0x5efc08(%rip) db> bt Tracing pid 14 tid 100005 td 0xffffff00012406a0 kdb_enter_why() at kdb_enter_why+0x3d panic() at panic+0x176 _mtx_lock_sleep() at _mtx_lock_sleep+0x181 _mtx_lock_flags() at _mtx_lock_flags+0xe1 em_init_locked() at em_init_locked+0x61 em_local_timer() at em_local_timer+0x195 softclock() at softclock+0x299 ithread_loop() at ithread_loop+0xda fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffd5599d30, rbp = 0 --- db> show locks exclusive sleep mutex em0 (EM TX Lock) r = 0 (0xffffff00036754a8) locked @ /usr/src/sys/dev/em/if_em.c:1302 exclusive sleep mutex em0 (EM Core Lock) r = 0 (0xffffff0003675478) locked @ /usr/src/sys/kern/kern_timeout.c:241 db> ps pid ppid pgrp uid state wmesg wchan cmd 50494 50493 41749 0 R+ make 50493 41749 41749 0 S+ wait 0xffffff01196a6468 sh 45511 45510 45511 1284 Ss sbwait 0xffffff00150257c4 sftp-server 45510 45135 45135 1284 S select 0xffffffff80b2f930 sshd 45135 932 45135 0 Ss sbwait 0xffffff001502c984 sshd 41749 1070 41749 0 S+ piperd 0xffffff0015ac45d0 initial thread 34233 34223 34073 0 S+ nanslp 0xffffffff80a9da68 initial thread 34223 34221 34073 0 S+ wait 0xffffff0009b62468 make 34221 34073 34073 0 S+ wait 0xffffff0015aa0468 sh 34073 33858 34073 0 S+ wait 0xffffff0125b6f8d0 make 33858 33834 33858 1284 Ss+ wait 0xffffff0009d528d0 bash 33834 33833 33833 1284 S select 0xffffffff80b2f930 xterm 33833 1066 33833 1284 Ss wait 0xffffff0125b6c468 sh 7250 1110 1110 1284 R+ initial thread 5215 1 1007 1284 S+ select 0xffffffff80b2f930 initial thread 5213 5209 1007 1284 S+ (threaded) firefox-bin 100203 S ucond 0xffffff009a318b00 firefox-bin 100202 S ucond 0xffffff00a0a25400 firefox-bin 100201 S ucond 0xffffff00a1dd4c00 firefox-bin 100200 S ucond 0xffffff00a4297580 firefox-bin 100195 S ucond 0xffffff0003e86900 firefox-bin 100194 S select 0xffffffff80b2f930 firefox-bin 100190 S select 0xffffffff80b2f930 initial thread 5209 5205 1007 1284 S+ wait 0xffffff0015aa58d0 sh 5205 5204 1007 1284 S+ wait 0xffffff0015aa1000 sh 5204 1034 1007 1284 S+ wait 0xffffff0015aa2468 sh 4977 4976 4976 1284 S+ (threaded) alpine 100147 S select 0xffffffff80b2f930 initial thread 4976 4973 4976 1284 S+ wait 0xffffff0015c6c000 sh 4973 4971 4973 1284 Ss+ wait 0xffffff0015c6b000 bash 4971 1034 1007 1284 S+ select 0xffffffff80b2f930 xterm 3249 919 919 80 S accept 0xffffff000929c5ce httpd 1110 1107 1110 1284 S+ wait 0xffffff0009b65000 sh 1107 1042 1107 1284 Ss+ wait 0xffffff000379e000 bash 1070 1068 1070 1284 Ss+ wait 0xffffff0009d51000 bash 1068 1067 1067 1284 S select 0xffffffff80b2f930 xterm 1067 1066 1067 1284 Ss wait 0xffffff0009d51468 sh 1066 1059 1059 1284 S+ select 0xffffffff80b2f930 ratpoison 1059 1052 1059 1284 S+ wait 0xffffff00037b28d0 sh 1054 0 0 0 RL CPU 1 [irq16: drm0] 1053 1052 1053 1284 S+ select 0xffffffff80b2f930 initial thread 1052 1051 1051 1284 S+ wait 0xffffff0009d54000 xinit 1051 1050 1051 1284 S+ wait 0xffffff0009d54468 sh 1050 1042 1050 1284 Ss+ wait 0xffffff0009b66000 bash 1048 1045 1048 1284 S+ kqread 0xffffff0003e60e00 rtorrent 1045 1042 1045 1284 Ss+ wait 0xffffff0003a45468 bash 1042 1041 1042 1284 Ss select 0xffffffff80b2f930 screen 1041 1006 1041 1284 S+ pause 0xffffff0009b620c0 screen 1034 1020 1007 1284 S+ select 0xffffffff80b2f930 initial thread 1033 1020 1033 1284 S+ select 0xffffffff80b2f930 initial thread 1027 1020 1007 1284 S+ select 0xffffffff80b2f930 initial thread 1020 1 1007 1284 S+ select 0xffffffff80b2f930 initial thread 1016 1 1007 1284 S+ select 0xffffffff80b2f930 Xvnc 1006 986 1006 1284 S+ wait 0xffffff000379f8d0 bash 1001 872 872 0 S select 0xffffffff80b2f930 perl5.8.8 1000 872 872 0 S select 0xffffffff80b2f930 perl5.8.8 999 919 919 80 S accept 0xffffff000929c5ce httpd 998 919 919 80 S accept 0xffffff000929c5ce httpd 997 919 919 80 S accept 0xffffff000929c5ce httpd 996 919 919 80 S accept 0xffffff000929c5ce httpd 995 919 919 80 S accept 0xffffff000929c5ce httpd 994 1 994 0 Ss+ ttyin 0xffffff0003689010 getty 993 1 993 0 Ss+ ttyin 0xffffff00036ab410 getty 992 1 992 0 Ss+ ttyin 0xffffff00036ac410 getty 991 1 991 0 Ss+ ttyin 0xffffff00036ac010 getty 990 1 990 0 Ss+ ttyin 0xffffff00036aac10 getty 989 1 989 0 Ss+ ttyin 0xffffff00036aa810 getty 988 1 988 0 Ss+ ttyin 0xffffff000369c810 getty 987 1 987 0 Ss+ ttyin 0xffffff000369cc10 getty 986 1 986 0 Ss+ wait 0xffffff0003a42000 login 965 1 965 0 Ss select 0xffffffff80b2f930 inetd 937 1 937 0 Ss nanslp 0xffffffff80a9da68 cron 932 1 932 0 Ss select 0xffffffff80b2f930 sshd 919 1 919 0 Ss select 0xffffffff80b2f930 httpd 894 1 894 25 Ss pause 0xffffff00037b0990 sendmail 890 1 890 0 Ss select 0xffffffff80b2f930 sendmail 872 1 872 0 Ss select 0xffffffff80b2f930 perl5.8.8 861 856 847 1003 S sbwait 0xffffff00092c16cc tinydns 860 857 847 1002 S piperd 0xffffff0003c27ba0 multilog 859 854 847 1001 S select 0xffffffff80b2f930 dnscache 858 855 847 1002 S piperd 0xffffff0003c39000 multilog 857 849 847 0 S select 0xffffffff80b2f930 supervise 856 849 847 0 S select 0xffffffff80b2f930 supervise 855 849 847 0 S select 0xffffffff80b2f930 supervise 854 849 847 0 S select 0xffffffff80b2f930 supervise 850 1 847 0 S piperd 0xffffff0003c278b8 readproctitle 849 1 847 0 S nanslp 0xffffffff80a9da68 svscan 833 1 833 1285 Ss select 0xffffffff80b2f930 dhcpd 799 1 799 0 Ss select 0xffffffff80b2f930 ntpd 775 1 775 0 Ss select 0xffffffff80b2f930 lpd 707 1 707 0 Ss select 0xffffffff80b2f930 syslogd 677 0 0 0 SL mdwait 0xffffff0003caa000 [md0] 633 1 633 0 Ss select 0xffffffff80b2f930 devd 169 0 0 0 SL zfs:(&tq 0xffffff0001349bc0 [zil_clean] 168 0 0 0 SL zfs:(&tq 0xffffff0001349940 [zil_clean] 167 0 0 0 SL zfs:(&tq 0xffffff00013496c0 [zil_clean] 105 0 0 0 SL zfs:(&tq 0xffffff0001349440 [zil_clean] 104 0 0 0 SL zfs:(&tx 0xffffff00038451a0 [txg_thread_enter] 103 0 0 0 SL zfs:(&tx 0xffffff0003845160 [txg_thread_enter] 102 0 0 0 SL zfs:(&tx 0xffffff0003845180 [txg_thread_enter] 101 0 0 0 SL vgeom:io 0xffffff00037c5810 [vdev:worker ad10] 100 0 0 0 SL vgeom:io 0xffffff0003760390 [vdev:worker ad8] 99 0 0 0 SL zfs:(&tq 0xffffff0001348080 [spa_zio_intr_5] 98 0 0 0 SL zfs:(&tq 0xffffff0001348080 [spa_zio_intr_5] 97 0 0 0 SL zfs:(&tq 0xffffff00013481c0 [spa_zio_issue_5] 96 0 0 0 SL zfs:(&tq 0xffffff00013481c0 [spa_zio_issue_5] 95 0 0 0 SL zfs:(&tq 0xffffff0001348300 [spa_zio_intr_4] 94 0 0 0 SL zfs:(&tq 0xffffff0001348300 [spa_zio_intr_4] 93 0 0 0 SL zfs:(&tq 0xffffff0001348440 [spa_zio_issue_4] 92 0 0 0 SL zfs:(&tq 0xffffff0001348440 [spa_zio_issue_4] 91 0 0 0 SL zfs:(&tq 0xffffff0001348580 [spa_zio_intr_3] 90 0 0 0 SL zfs:(&tq 0xffffff0001348580 [spa_zio_intr_3] 89 0 0 0 SL zfs:(&tq 0xffffff00013486c0 [spa_zio_issue_3] 88 0 0 0 SL zfs:(&tq 0xffffff00013486c0 [spa_zio_issue_3] 87 0 0 0 SL zfs:(&tq 0xffffff0001348800 [spa_zio_intr_2] 86 0 0 0 SL zfs:(&tq 0xffffff0001348800 [spa_zio_intr_2] 85 0 0 0 SL zfs:(&tq 0xffffff0001348940 [spa_zio_issue_2] 84 0 0 0 SL zfs:(&tq 0xffffff0001348940 [spa_zio_issue_2] 83 0 0 0 SL zfs:(&tq 0xffffff0001348a80 [spa_zio_intr_1] 82 0 0 0 SL zfs:(&tq 0xffffff0001348a80 [spa_zio_intr_1] 81 0 0 0 SL zfs:(&tq 0xffffff0001348bc0 [spa_zio_issue_1] 80 0 0 0 SL zfs:(&tq 0xffffff0001348bc0 [spa_zio_issue_1] 79 0 0 0 SL zfs:(&tq 0xffffff0001348d00 [spa_zio_intr_0] 78 0 0 0 SL zfs:(&tq 0xffffff0001348d00 [spa_zio_intr_0] 77 0 0 0 SL zfs:(&tq 0xffffff0001348e40 [spa_zio_issue_0] 76 0 0 0 SL zfs:(&tq 0xffffff0001348e40 [spa_zio_issue_0] 49 0 0 0 SL sdflush 0xffffffff80b3fc38 [softdepflush] 48 0 0 0 SL vlruwt 0xffffff00036a3468 [vnlru] 47 0 0 0 SL syncer 0xffffffff80a9d6e0 [syncer] 46 0 0 0 SL psleep 0xffffffff80b3013c [bufdaemon] 45 0 0 0 SL pgzero 0xffffffff80b416c4 [pagezero] 44 0 0 0 SL psleep 0xffffffff80b40a08 [vmdaemon] 43 0 0 0 SL psleep 0xffffffff80b409cc [pagedaemon] 42 0 0 0 SL zfs:(&ar 0xffffffff80d2a330 [arc_reclaim_thread] 41 0 0 0 SL waiting_ 0xffffffff80b33868 [sctp_iterator] 40 0 0 0 WL [irq1: atkbd0] 39 0 0 0 WL [swi0: sio] 38 0 0 0 WL [irq7: ppbus0 ppc0] 37 0 0 0 SL - 0xffffff000364cd80 [em0 taskq] 36 0 0 0 WL [irq17: atapci2+] 35 0 0 0 WL [irq15: ata1] 34 0 0 0 WL [irq14: ata0] 33 0 0 0 SL - 0xffffff0003600280 [nfe0 taskq] 32 0 0 0 SL usbevt 0xffffff00033da420 [usb2] 31 0 0 0 WL [irq22: ehci0] 30 0 0 0 SL usbevt 0xffffffff8103b420 [usb1] 29 0 0 0 WL [irq21: ohci1+] 28 0 0 0 SL usbtsk 0xffffffff80a98e48 [usbtask-dr] 27 0 0 0 SL usbtsk 0xffffffff80a98e20 [usbtask-hc] 26 0 0 0 SL usbevt 0xffffffff81039420 [usb0] 25 0 0 0 WL [irq20: nfe0 ohci0] 24 0 0 0 WL [irq9: acpi0] 23 0 0 0 SL - 0xffffff000138b000 [kqueue taskq] 22 0 0 0 SL - 0xffffff000138b080 [acpi_task_2] 21 0 0 0 SL - 0xffffff000138b080 [acpi_task_1] 9 0 0 0 SL - 0xffffff000138b080 [acpi_task_0] 20 0 0 0 WL [swi2: cambio] 8 0 0 0 SL ccb_scan 0xffffffff80a66fe0 [xpt_thrd] 19 0 0 0 WL [swi6: task queue] 18 0 0 0 WL [swi6: Giant taskq] 7 0 0 0 SL - 0xffffff0001337600 [thread taskq] 17 0 0 0 WL [swi5: +] 6 0 0 0 SL zfs:(&tq 0xffffff0001349080 [system_taskq] 5 0 0 0 SL zfs:(&tq 0xffffff0001349080 [system_taskq] 16 0 0 0 SL - 0xffffffff80a9d6e8 [yarrow] 4 0 0 0 SL - 0xffffffff80a99778 [g_down] 3 0 0 0 SL - 0xffffffff80a99770 [g_up] 2 0 0 0 SL - 0xffffffff80a99760 [g_event] 15 0 0 0 WL [swi3: vm] 14 0 0 0 RL CPU 0 [swi4: clock sio] 13 0 0 0 WL [swi1: net] 12 0 0 0 RL [idle: cpu0] 11 0 0 0 RL [idle: cpu1] 1 0 1 0 SLs wait 0xffffff000122f8d0 [init] 10 0 0 0 SL audit_wo 0xffffffff80b3f0c0 [audit] 0 0 0 0 WLs [swapper] From owner-freebsd-net@FreeBSD.ORG Wed May 21 19:23:02 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B96610656B5 for ; Wed, 21 May 2008 19:23:02 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 5DA8E8FC15 for ; Wed, 21 May 2008 19:23:01 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so332131pyb.10 for ; Wed, 21 May 2008 12:23:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received: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; bh=1+IP36IGQ3NO5rpEXPxVEZAkZEexTocfy/MD/T0iMO4=; b=glCcIwSSruKfwVCYqH6XkZoQ5G9vD1sK79IdjDwpJvm4qaB7iSpowcNp7auY5OMi1km1I3MuZjjwmyJzvZzX4oWgJkcEO1jkTLyJX4L+qHuyEEvF+i39ZL8fiuTX8oXRn7K5Mb1KuTG8aJv3aENsLGymOZT06EDxB8UQx4HyU1s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=iqgvNuxZ2NTteRnemH0NK4D60hpVYZBZEL45VQy3VqKL2k104qw2NZaQkEb5ZrN3Y7OgMc/tiYZPHcCl0GRXcBEGGSLeX8pqL2iKNDoPRCfLQxtYXf8v18kPVlN36/a7ZNplH8KXiLr+qgyA2sayLPSozMxiw84r4WNU7KgBAAI= Received: by 10.140.136.6 with SMTP id j6mr5332890rvd.199.1211397780034; Wed, 21 May 2008 12:23:00 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Wed, 21 May 2008 12:23:00 -0700 (PDT) Message-ID: <2e77fc10805211223l7fd69e4cwdd488bada0dc7b95@mail.gmail.com> Date: Wed, 21 May 2008 22:23:00 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Max Laier" In-Reply-To: <200805211944.42418.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805211944.42418.max@love2party.net> X-Google-Sender-Auth: d22cb49347acdf04 Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 19:23:02 -0000 On Wed, May 21, 2008 at 8:44 PM, Max Laier wrote: > On Wednesday 21 May 2008 19:31:46 Niki Denev wrote: >> If one tries to use lagg0.2 style vlans on lagg0 interface configured >> from rc.conf it does't work. >> The problem is that all of the cloned interfaces (lagg0 , lagg0.2, etc) >> are created before any other interface configuration is done, >> and in this case lagg0 is created, then lagg0.2 is created. >> But because lagg0 does not have any members yet, it's MAC address >> is all zeroes, and this is inherited by the vlan interfaces. >> At the next step the members are added to the lagg0 interface and it's >> mac address gets set, >> but the vlan interfaces never see this change and remain with mac >> address 00:00:00:00:00:00 and in unusable state. >> >> Does it sound reasonable for the vlan(4) interfaces to update their >> mac address when their parent changes it. >> (this should probably look more like the parent telling the vlans >> attached to it that it's mac has changed, but >> i'm not sure if the parent knows about children interfaces) > > It doesn't (and shouldn't have to). I'd simply add an > EVENTHANDLER_INVOKE(ifaddr_event, ifp) to if_setlladdr() - we do that for > INET[6] address already. Then vlan (and any other device interested in > LLaddress changes) can simply register to that eventhandler and resync. > > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > Yes, you are absolutely right. I wasn't aware of EVENTHANDLER(4). Niki From owner-freebsd-net@FreeBSD.ORG Wed May 21 20:26:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3205D106564A for ; Wed, 21 May 2008 20:26:11 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 069B48FC0C for ; Wed, 21 May 2008 20:26:10 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2845504wah.3 for ; Wed, 21 May 2008 13:26:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pbl/UojuUhUuzALd7iZZV5mO0rCozM0ixhFxTHZrqZQ=; b=WxFIQhieZ9wAh4Ahrm6IB+1QfHsb3KAaefay+i94cew5bVlZkyNCZ295uVs3BBqpdAMioUSBZ8QGElP6gAhTNtvt3qOP2l42t9ujz5nGSA6rsEuA2DlPhgUz5zA9REUao4Mge2SFlxHyWk+eOU0sdJ5Po7PdUJEvXb4Zkq29GzE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EdK1g014w4s0quTV62X0OIdY23o0BxEYmVe0g4hPMX+LnhrpTb4bmW8EhLK0Uh+Zjq31jr3Cyj6ORARpLVicVPddApXILW/LDekKKpjUXDd8mbPtQkhHbnu/Ih5gp2Sf6pegR7076ZMmtk3937woaT9D8+EAvKiP6ONPJ2lV9JA= Received: by 10.114.210.2 with SMTP id i2mr1263096wag.18.1211401570051; Wed, 21 May 2008 13:26:10 -0700 (PDT) Received: by 10.114.177.4 with HTTP; Wed, 21 May 2008 13:26:09 -0700 (PDT) Message-ID: <2a41acea0805211326v74baa017tc03fcd329a764ef5@mail.gmail.com> Date: Wed, 21 May 2008 13:26:09 -0700 From: "Jack Vogel" To: "Neil Hoggarth" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: [em][panic] recursed on non-recursive mutex em0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 May 2008 20:26:11 -0000 On Wed, May 21, 2008 at 12:11 PM, Neil Hoggarth wrote: > Hi Folks, > > I opened PR kern/122928 last month, describing my problems with Intel > PRO/1000 MT adaptor on 7-STABLE, with v6.7.3 of the em driver: every > so often the machine would get into a state where it would repeatedly > watchdog timeout the em0 interface, and the interface would stop > receiving packets. > > A few weeks ago I cvsupped a newer version of the 7-STABLE source > tree, after v6.9.0 of the em driver was MFCed. Since I started running > on the newer build watchdog timeouts appear to be followed by a system > panic rather than the freezing up of the interface. I have no hard > evidence but it "feels like" the panics are happening under the same > sort of circumstance that was previously triggering my watchdog > problem (basically network activity combined with CPU load). A similar > observation was made by Yani Karydis on the freebsd-stable mailing > list earlier in the month: > > http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042311.html > > I've now got a serial console set up, and I'm running a kernel with > DDB support compiled in. I managed to get the information below out of > the most recent panic. Is anyone able to use this to debug the > situation? What else might I try to gather useful information? This is a helpful start, I'll stare at the code and see... sounds like some rx lock design issue. Thanks Neil, Jack From owner-freebsd-net@FreeBSD.ORG Wed May 21 20:44:43 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36EE1106566B for ; Wed, 21 May 2008 20:44:43 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 094708FC16 for ; Wed, 21 May 2008 20:44:43 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3014583rvf.43 for ; Wed, 21 May 2008 13:44:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received: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; bh=h/o8TYcE/BuWUoQczbTL0R+CEEl1r7O34/jPbmcCw1U=; b=DxTCl7KLxaSdqnYwhYsvZsBkGqfX2maDZDT25sr+B46+37JTEAGyto4jVk2o+AkVLd5R/fjN5P+H6gd8bW+dUJP3dHgDOhLam90VbCK6bj8qNvs1n7yeEfAJXmJW19SBOy2cL3hyxcjcJq3l2aIItRfLfxnvSKUsm4tHmveRBes= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=x4vlTWyvkfpJ/M8akwleAxJVtZskxnQNKAQRdhewIFXF7Vf8cKvyUEb3kgrkzYmeFTA/oTkFS7kUtvYmKWBF2LSaC4jlgJ6e0iDMZylkX9kXj1D6vxaj3EllwZa6wZhKegsA0LS+jYZNjcv+A+u8UXGt4tHpGajUkVb54SWVrLQ= Received: by 10.141.153.17 with SMTP id f17mr5401012rvo.44.1211402682719; Wed, 21 May 2008 13:44:42 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Wed, 21 May 2008 13:44:42 -0700 (PDT) Message-ID: <2e77fc10805211344m606886f9pd45ff7b001bc8da0@mail.gmail.com> Date: Wed, 21 May 2008 23:44:42 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Max Laier" In-Reply-To: <2e77fc10805211223l7fd69e4cwdd488bada0dc7b95@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805211944.42418.max@love2party.net> <2e77fc10805211223l7fd69e4cwdd488bada0dc7b95@mail.gmail.com> X-Google-Sender-Auth: e2b8fb199dc1defe Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 20:44:43 -0000 On Wed, May 21, 2008 at 8:44 PM, Max Laier wrote: >> It doesn't (and shouldn't have to). I'd simply add an >> EVENTHANDLER_INVOKE(ifaddr_event, ifp) to if_setlladdr() - we do that for >> INET[6] address already. Then vlan (and any other device interested in >> LLaddress changes) can simply register to that eventhandler and resync. >> Hi, Does this look like a reasonable solution? It passes my limited testing. Niki diff -ur /usr/src/sys/net/if.c /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if.c --- /usr/src/sys/net/if.c 2008-04-29 23:43:08.000000000 +0300 +++ /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if.c 2008-05-21 22:12:33.989318352 +0300 @@ -2647,6 +2647,11 @@ } #endif } + /* + * Notify interested parties (clonable children like if_vlan(4)) + * about the link layer address change + */ + EVENTHANDLER_INVOKE(ifaddr_event, ifp); return (0); } diff -ur /usr/src/sys/net/if_vlan.c /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if_vlan.c --- /usr/src/sys/net/if_vlan.c 2007-10-28 18:24:16.000000000 +0200 +++ /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if_vlan.c 2008-05-21 23:24:13.322156460 +0300 @@ -137,6 +137,7 @@ static MALLOC_DEFINE(M_VLAN, VLANNAME, "802.1Q Virtual LAN Interface"); static eventhandler_tag ifdetach_tag; +static eventhandler_tag ifaddr_tag; /* * We have a global mutex, that is used to serialize configuration @@ -518,6 +519,33 @@ /* For if_link_state_change() eyes only... */ extern void (*vlan_link_state_p)(struct ifnet *, int); +/* + * Update vlan interface link layer address on + * parent interface link layer address change. + */ +static int +vlan_lladdr_update(void *arg __unused, struct ifnet *ifp) +{ + struct ifvlantrunk *trunk = ifp->if_vlantrunk; + struct ifvlan *ifv; + int i; + + TRUNK_LOCK(trunk); +#ifdef VLAN_ARRAY + for (i = 0; i < VLAN_ARRAY_SIZE; i++) + if (trunk->vlans[i] != NULL) { + ifv = trunk->vlans[i]; +#else + for (i = 0; i < (1 << trunk->hwidth); i++) { + LIST_FOREACH(ifv, &trunk->hash[i], ifv_list) +#endif + bcopy(IF_LLADDR(ifp), IF_LLADDR(ifv->ifv_ifp), + ETHER_ADDR_LEN); + } + TRUNK_UNLOCK(trunk); + return 0; +} + static int vlan_modevent(module_t mod, int type, void *data) { @@ -528,6 +556,10 @@ vlan_ifdetach, NULL, EVENTHANDLER_PRI_ANY); if (ifdetach_tag == NULL) return (ENOMEM); + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, + vlan_lladdr_update, NULL, EVENTHANDLER_PRI_ANY); + if (ifaddr_tag == NULL) + return (ENOMEM); VLAN_LOCK_INIT(); vlan_input_p = vlan_input; vlan_link_state_p = vlan_link_state; @@ -546,6 +578,7 @@ case MOD_UNLOAD: if_clone_detach(&vlan_cloner); EVENTHANDLER_DEREGISTER(ifnet_departure_event, ifdetach_tag); + EVENTHANDLER_DEREGISTER(ifaddr_event, ifaddr_tag); vlan_input_p = NULL; vlan_link_state_p = NULL; vlan_trunk_cap_p = NULL; From owner-freebsd-net@FreeBSD.ORG Wed May 21 20:52:19 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12B7E106564A for ; Wed, 21 May 2008 20:52:19 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id DB6178FC0A for ; Wed, 21 May 2008 20:52:18 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2855618wah.3 for ; Wed, 21 May 2008 13:52:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=e7amYAJp5DkGtlUdBNu9N3wfRvawnMrOLUleQikdvVE=; b=J0pSnISjjZPLEE6G0U4RY0XpXrVbDQCtIBfkIDTZ0+tWehS/4e8wXIHnQrc+CAFspszg2pC9O+JxnfnJ1GM/51qhNALFUyp4ImBVIRUGrEeEQ3p6Bg3tsjEyd3BB+KsxzKorSDXSxOVS0mnmZuxK3JfKT7nYYjJLFnU3yxHI/bA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FuXY5E2MTIf63NgbFbDE58lGC6MkTYvFR4ou5BpKA0HygHqKmxw6pdP8AaU817JGdt9KdraL2wE77IZhD9eTq7zqfhiQn79U27QRnf5IS7i30jPyk4jMLYNUpmzTGjR44OInUGfQxI4vzCfU3T+5qizrucoVucBtdVO5l+JxeVo= Received: by 10.114.79.18 with SMTP id c18mr11097321wab.86.1211403138358; Wed, 21 May 2008 13:52:18 -0700 (PDT) Received: by 10.114.177.4 with HTTP; Wed, 21 May 2008 13:52:18 -0700 (PDT) Message-ID: <2a41acea0805211352s37e6fd40maaaac90e51912947@mail.gmail.com> Date: Wed, 21 May 2008 13:52:18 -0700 From: "Jack Vogel" To: "Neil Hoggarth" In-Reply-To: <2a41acea0805211326v74baa017tc03fcd329a764ef5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0805211326v74baa017tc03fcd329a764ef5@mail.gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: [em][panic] recursed on non-recursive mutex em0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 May 2008 20:52:19 -0000 On Wed, May 21, 2008 at 1:26 PM, Jack Vogel wrote: > On Wed, May 21, 2008 at 12:11 PM, Neil Hoggarth wrote: >> Hi Folks, >> >> I opened PR kern/122928 last month, describing my problems with Intel >> PRO/1000 MT adaptor on 7-STABLE, with v6.7.3 of the em driver: every >> so often the machine would get into a state where it would repeatedly >> watchdog timeout the em0 interface, and the interface would stop >> receiving packets. >> >> A few weeks ago I cvsupped a newer version of the 7-STABLE source >> tree, after v6.9.0 of the em driver was MFCed. Since I started running >> on the newer build watchdog timeouts appear to be followed by a system >> panic rather than the freezing up of the interface. I have no hard >> evidence but it "feels like" the panics are happening under the same >> sort of circumstance that was previously triggering my watchdog >> problem (basically network activity combined with CPU load). A similar >> observation was made by Yani Karydis on the freebsd-stable mailing >> list earlier in the month: >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042311.html >> >> I've now got a serial console set up, and I'm running a kernel with >> DDB support compiled in. I managed to get the information below out of >> the most recent panic. Is anyone able to use this to debug the >> situation? What else might I try to gather useful information? > > This is a helpful start, I'll stare at the code and see... sounds like some > rx lock design issue. OPPS, I think I found the problem, look for a delta on if_em.c shortly. Let me know if this fixes your problem. Jack From owner-freebsd-net@FreeBSD.ORG Wed May 21 21:06:22 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4E2A106574D for ; Wed, 21 May 2008 21:06:22 +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 703288FC18 for ; Wed, 21 May 2008 21:06:20 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-024-001.pools.arcor-ip.net [88.66.24.1]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1JyvVq44DQ-0005Zj; Wed, 21 May 2008 23:06:19 +0200 Received: (qmail 48045 invoked from network); 21 May 2008 21:04:35 -0000 Received: from myhost.laiers.local (192.168.4.151) by mx.laiers.local with SMTP; 21 May 2008 21:04:35 -0000 From: Max Laier Organization: FreeBSD To: "Niki Denev" Date: Wed, 21 May 2008 23:05:57 +0200 User-Agent: KMail/1.9.9 References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <2e77fc10805211223l7fd69e4cwdd488bada0dc7b95@mail.gmail.com> <2e77fc10805211344m606886f9pd45ff7b001bc8da0@mail.gmail.com> In-Reply-To: <2e77fc10805211344m606886f9pd45ff7b001bc8da0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805212305.58235.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19p0xzEJHB8eQVwRh0B2LoRBKKWwyO7RDvDaHy 547oPrGZlDBNjFVeB3gNEcmf6fOuQE+qO/sW+C905GcFr96mGy bXKqrdKIcntNdJb1BbIbA== Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 21:06:23 -0000 On Wednesday 21 May 2008 22:44:42 Niki Denev wrote: > On Wed, May 21, 2008 at 8:44 PM, Max Laier wrote: > >> It doesn't (and shouldn't have to). I'd simply add an > >> EVENTHANDLER_INVOKE(ifaddr_event, ifp) to if_setlladdr() - we do > >> that for INET[6] address already. Then vlan (and any other device > >> interested in LLaddress changes) can simply register to that > >> eventhandler and resync. > > Hi, > Does this look like a reasonable solution? > It passes my limited testing. Looks good, though I'd probably move up the _INVOKE to before the ARPs are sent out. Probably between twiddling the hardware and sending ARPs (though that needs an else-case if the interface is still down). In fact the ARPs could be sent from an event hook, too. This would get rid of INET specific code in the LL-interface code. > Niki > > diff -ur /usr/src/sys/net/if.c > /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if.c > --- /usr/src/sys/net/if.c 2008-04-29 23:43:08.000000000 +0300 > +++ /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if.c > 2008-05-21 22:12:33.989318352 +0300 > @@ -2647,6 +2647,11 @@ > } > #endif > } > + /* > + * Notify interested parties (clonable children like > if_vlan(4)) + * about the link layer address change > + */ > + EVENTHANDLER_INVOKE(ifaddr_event, ifp); > return (0); > } > > diff -ur /usr/src/sys/net/if_vlan.c > /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if_vlan.c > --- /usr/src/sys/net/if_vlan.c 2007-10-28 18:24:16.000000000 +0200 > +++ /usr/src/.zfs/snapshot/vlan_lladdr_patch/sys/net/if_vlan.c > 2008-05-21 23:24:13.322156460 +0300 > @@ -137,6 +137,7 @@ > static MALLOC_DEFINE(M_VLAN, VLANNAME, "802.1Q Virtual LAN > Interface"); > > static eventhandler_tag ifdetach_tag; > +static eventhandler_tag ifaddr_tag; > > /* > * We have a global mutex, that is used to serialize configuration > @@ -518,6 +519,33 @@ > /* For if_link_state_change() eyes only... */ > extern void (*vlan_link_state_p)(struct ifnet *, int); > > +/* > + * Update vlan interface link layer address on > + * parent interface link layer address change. > + */ > +static int > +vlan_lladdr_update(void *arg __unused, struct ifnet *ifp) > +{ > + struct ifvlantrunk *trunk = ifp->if_vlantrunk; > + struct ifvlan *ifv; > + int i; > + > + TRUNK_LOCK(trunk); > +#ifdef VLAN_ARRAY > + for (i = 0; i < VLAN_ARRAY_SIZE; i++) > + if (trunk->vlans[i] != NULL) { > + ifv = trunk->vlans[i]; > +#else > + for (i = 0; i < (1 << trunk->hwidth); i++) { > + LIST_FOREACH(ifv, &trunk->hash[i], ifv_list) > +#endif > + bcopy(IF_LLADDR(ifp), IF_LLADDR(ifv->ifv_ifp), > + ETHER_ADDR_LEN); > + } > + TRUNK_UNLOCK(trunk); > + return 0; > +} > + > static int > vlan_modevent(module_t mod, int type, void *data) > { > @@ -528,6 +556,10 @@ > vlan_ifdetach, NULL, EVENTHANDLER_PRI_ANY); > if (ifdetach_tag == NULL) > return (ENOMEM); > + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, > + vlan_lladdr_update, NULL, EVENTHANDLER_PRI_ANY); > + if (ifaddr_tag == NULL) > + return (ENOMEM); > VLAN_LOCK_INIT(); > vlan_input_p = vlan_input; > vlan_link_state_p = vlan_link_state; > @@ -546,6 +578,7 @@ > case MOD_UNLOAD: > if_clone_detach(&vlan_cloner); > EVENTHANDLER_DEREGISTER(ifnet_departure_event, > ifdetach_tag); + EVENTHANDLER_DEREGISTER(ifaddr_event, > ifaddr_tag); vlan_input_p = NULL; > vlan_link_state_p = NULL; > vlan_trunk_cap_p = NULL; -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Wed May 21 21:22:53 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F8C9106564A for ; Wed, 21 May 2008 21:22:53 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3143A8FC15 for ; Wed, 21 May 2008 21:22:53 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3033729rvf.43 for ; Wed, 21 May 2008 14:22:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received: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; bh=KivZ5txHnzXrS0IyCmFt9anhnZBq+e/+OB3sOMdxRQ0=; b=n5msQA58DZCQsCrkVBsBY7eZxjnc48cIs+u9GUyEuscLYDtWZO/BO/ZOUT+dxZWpdO+zdo3O6/UpQA90fwBirRkH8OKXLaa73V0nAZwER+8kjE3O2JzjTHeeI7p7UgdgxH5sqgNTiLu3F+J/0idYIdXE7LvbUWUYUAAW3wLtiY4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=YYdgCU/pI+SO5VpzmMSiqJKsGdFCmvhCiHWDpMV1BtixfJUfX+WJxaMpOJg4hhZ9tN8vkPvb6sM+L/QKT7TN1PEWVPasSeHJNOHzSFGe1pXW9tHHOiMIXJc+SfQIoZNVJ/VvTb+WbUXZdOxrPQmRS22M0fvXjG1wIn1AkXCDwlE= Received: by 10.141.206.13 with SMTP id i13mr5407170rvq.211.1211404972769; Wed, 21 May 2008 14:22:52 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Wed, 21 May 2008 14:22:52 -0700 (PDT) Message-ID: <2e77fc10805211422q75603d54h5709ed3e5be37d0a@mail.gmail.com> Date: Thu, 22 May 2008 00:22:52 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Max Laier" In-Reply-To: <200805212305.58235.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <2e77fc10805211223l7fd69e4cwdd488bada0dc7b95@mail.gmail.com> <2e77fc10805211344m606886f9pd45ff7b001bc8da0@mail.gmail.com> <200805212305.58235.max@love2party.net> X-Google-Sender-Auth: 8ac8b544de6f84c8 Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 21:22:53 -0000 On Thu, May 22, 2008 at 12:05 AM, Max Laier wrote: > Looks good, though I'd probably move up the _INVOKE to before the ARPs are > sent out. Probably between twiddling the hardware and sending ARPs > (though that needs an else-case if the interface is still down). In fact > the ARPs could be sent from an event hook, too. This would get rid of > INET specific code in the LL-interface code. > I thought about moving it up too, but in this case isn't it going to be called only if the interface is up (IFF_UP)? Here is an updated version that makes vlan_lladdr_update() check if ifp->if_vlantrunk exists, because otherwise we get a panic if there is a change of the link layer address on different interface that does not have vlan children. diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if.c /usr/src/sys/net/if.c --- /usr/src/.zfs/snapshot/orig/sys/net/if.c 2008-04-29 23:43:08.000000000 +0300 +++ /usr/src/sys/net/if.c 2008-05-21 23:48:59.621157217 +0300 @@ -2647,6 +2647,12 @@ } #endif } + /* + * Notify interested parties (clonable children like if_vlan(4)) + * about the link layer address change + */ + EVENTHANDLER_INVOKE(ifaddr_event, ifp); + return (0); } diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c /usr/src/sys/net/if_vlan.c --- /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c 2007-10-28 18:24:16.000000000 +0200 +++ /usr/src/sys/net/if_vlan.c 2008-05-22 00:18:57.128613715 +0300 @@ -137,6 +137,7 @@ static MALLOC_DEFINE(M_VLAN, VLANNAME, "802.1Q Virtual LAN Interface"); static eventhandler_tag ifdetach_tag; +static eventhandler_tag ifaddr_tag; /* * We have a global mutex, that is used to serialize configuration @@ -518,6 +519,35 @@ /* For if_link_state_change() eyes only... */ extern void (*vlan_link_state_p)(struct ifnet *, int); +/* + * Update vlan interface link layer address on + * parent interface link layer address change. + */ +static int +vlan_lladdr_update(void *arg __unused, struct ifnet *ifp) +{ + struct ifvlantrunk *trunk = ifp->if_vlantrunk; + struct ifvlan *ifv; + int i; + + if (trunk) { + TRUNK_LOCK(trunk); +#ifdef VLAN_ARRAY + for (i = 0; i < VLAN_ARRAY_SIZE; i++) + if (trunk->vlans[i] != NULL) { + ifv = trunk->vlans[i]; +#else + for (i = 0; i < (1 << trunk->hwidth); i++) { + LIST_FOREACH(ifv, &trunk->hash[i], ifv_list) +#endif + bcopy(IF_LLADDR(ifp), IF_LLADDR(ifv->ifv_ifp), + ETHER_ADDR_LEN); + } + TRUNK_UNLOCK(trunk); + } + return (0); +} + static int vlan_modevent(module_t mod, int type, void *data) { @@ -528,6 +558,10 @@ vlan_ifdetach, NULL, EVENTHANDLER_PRI_ANY); if (ifdetach_tag == NULL) return (ENOMEM); + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, + vlan_lladdr_update, NULL, EVENTHANDLER_PRI_ANY); + if (ifaddr_tag == NULL) + return (ENOMEM); VLAN_LOCK_INIT(); vlan_input_p = vlan_input; vlan_link_state_p = vlan_link_state; @@ -546,6 +580,7 @@ case MOD_UNLOAD: if_clone_detach(&vlan_cloner); EVENTHANDLER_DEREGISTER(ifnet_departure_event, ifdetach_tag); + EVENTHANDLER_DEREGISTER(ifaddr_event, ifaddr_tag); vlan_input_p = NULL; vlan_link_state_p = NULL; vlan_trunk_cap_p = NULL; From owner-freebsd-net@FreeBSD.ORG Wed May 21 21:32:33 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9503C106564A for ; Wed, 21 May 2008 21:32:33 +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 3068C8FC1E for ; Wed, 21 May 2008 21:32:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-024-001.pools.arcor-ip.net [88.66.24.1]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1JyvvE0amn-0004Rz; Wed, 21 May 2008 23:32:32 +0200 Received: (qmail 48634 invoked from network); 21 May 2008 21:30:48 -0000 Received: from myhost.laiers.local (192.168.4.151) by ns1.laiers.local with SMTP; 21 May 2008 21:30:48 -0000 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Wed, 21 May 2008 23:32:13 +0200 User-Agent: KMail/1.9.9 References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805212305.58235.max@love2party.net> <2e77fc10805211422q75603d54h5709ed3e5be37d0a@mail.gmail.com> In-Reply-To: <2e77fc10805211422q75603d54h5709ed3e5be37d0a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805212332.13993.max@love2party.net> X-Provags-ID: V01U2FsdGVkX18VKdbAZwJN8t7lsXnYCkpRVVMxwmDdePliivF Z6rwsNxo1JMq8wQOfHvCPLQC6aeKNKnKV8OnAUYt4+GuYL4rci cFPpbXKEO+JFL1sXf14SA== Cc: Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 21:32:33 -0000 On Wednesday 21 May 2008 23:22:52 Niki Denev wrote: > On Thu, May 22, 2008 at 12:05 AM, Max Laier wrote: > > Looks good, though I'd probably move up the _INVOKE to before the > > ARPs are sent out. Probably between twiddling the hardware and > > sending ARPs (though that needs an else-case if the interface is ^------------------------------------------------- > > still down). In fact the ARPs could be sent from an event hook, too. ---------^ > > This would get rid of INET specific code in the LL-interface code. > > I thought about moving it up too, but in this case isn't it going to > be called only if the interface is up (IFF_UP)? See above. > Here is an updated version that makes vlan_lladdr_update() check if > ifp->if_vlantrunk exists, > because otherwise we get a panic if there is a change of the link > layer address on different interface that > does not have vlan children. > > diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if.c /usr/src/sys/net/if.c > --- /usr/src/.zfs/snapshot/orig/sys/net/if.c 2008-04-29 > 23:43:08.000000000 +0300 +++ /usr/src/sys/net/if.c 2008-05-21 > 23:48:59.621157217 +0300 > @@ -2647,6 +2647,12 @@ > } > #endif > } > + /* > + * Notify interested parties (clonable children like if_vlan(4)) > + * about the link layer address change > + */ > + EVENTHANDLER_INVOKE(ifaddr_event, ifp); > + > return (0); > } > > diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c > /usr/src/sys/net/if_vlan.c > --- /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c 2007-10-28 > 18:24:16.000000000 +0200 > +++ /usr/src/sys/net/if_vlan.c 2008-05-22 00:18:57.128613715 +0300 > @@ -137,6 +137,7 @@ > static MALLOC_DEFINE(M_VLAN, VLANNAME, "802.1Q Virtual LAN > Interface"); > > static eventhandler_tag ifdetach_tag; > +static eventhandler_tag ifaddr_tag; > > /* > * We have a global mutex, that is used to serialize configuration > @@ -518,6 +519,35 @@ > /* For if_link_state_change() eyes only... */ > extern void (*vlan_link_state_p)(struct ifnet *, int); > > +/* > + * Update vlan interface link layer address on > + * parent interface link layer address change. > + */ > +static int > +vlan_lladdr_update(void *arg __unused, struct ifnet *ifp) > +{ > + struct ifvlantrunk *trunk = ifp->if_vlantrunk; > + struct ifvlan *ifv; > + int i; > + > + if (trunk) { > + TRUNK_LOCK(trunk); > +#ifdef VLAN_ARRAY > + for (i = 0; i < VLAN_ARRAY_SIZE; i++) > + if (trunk->vlans[i] != NULL) { > + ifv = trunk->vlans[i]; > +#else > + for (i = 0; i < (1 << trunk->hwidth); i++) { > + LIST_FOREACH(ifv, &trunk->hash[i], ifv_list) > +#endif > + bcopy(IF_LLADDR(ifp), IF_LLADDR(ifv->ifv_ifp), > + ETHER_ADDR_LEN); > + } > + TRUNK_UNLOCK(trunk); > + } > + return (0); > +} > + > static int > vlan_modevent(module_t mod, int type, void *data) > { > @@ -528,6 +558,10 @@ > vlan_ifdetach, NULL, EVENTHANDLER_PRI_ANY); > if (ifdetach_tag == NULL) > return (ENOMEM); > + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, > + vlan_lladdr_update, NULL, EVENTHANDLER_PRI_ANY); > + if (ifaddr_tag == NULL) > + return (ENOMEM); > VLAN_LOCK_INIT(); > vlan_input_p = vlan_input; > vlan_link_state_p = vlan_link_state; > @@ -546,6 +580,7 @@ > case MOD_UNLOAD: > if_clone_detach(&vlan_cloner); > EVENTHANDLER_DEREGISTER(ifnet_departure_event, ifdetach_tag); > + EVENTHANDLER_DEREGISTER(ifaddr_event, ifaddr_tag); > vlan_input_p = NULL; > vlan_link_state_p = NULL; > vlan_trunk_cap_p = NULL; -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Wed May 21 21:45:22 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 140E71065674; Wed, 21 May 2008 21:45:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id C7CA68FC13; Wed, 21 May 2008 21:45:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 985F946B17; Wed, 21 May 2008 17:45:20 -0400 (EDT) Date: Wed, 21 May 2008 22:45:20 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org In-Reply-To: <20080310122338.T29929@fledge.watson.org> Message-ID: <20080521224350.T63482@fledge.watson.org> References: <20080310122338.T29929@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: net@FreeBSD.org Subject: Re: netatm removal warning X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 May 2008 21:45:22 -0000 On Mon, 10 Mar 2008, Robert Watson wrote: > This is another of those boring e-mails about kernel subsystems that still > require Giant. Sorry about that! > > As previously published, netatm is a non-MPSAFE protocol stack largely > superseded by our two other ATM stacks, netnatm and the netgraph/atm (both > MPSAFE). netatm is currently non-functional and uncompileable because it > depends on the Giant compatibility shims for the protocol stack, which were > removed in FreeBSD 7.0. We left the code in place in case to make it easier > for any interested third parties to distribute patches against it (in > particular, patches to make it MPSAFE). > > The current plan is that we will remove the netatm code from HEAD and > RELENG_7 before FreeBSD 7.1. A specific schedue for 7.1 hasn't been > published yet, but in order to give plenty of warning, here's the proposed > netatm removal schedule: > > 10 March 2008 E-mail warning to arch@/net@ > 10 April 2008 E-mail warning to arch@/net@ > 10 May 2008 Removal of netatm from HEAD > 20 May 2008 Removal of netatm from RELENG_7 > > Obviously, netatm will remain in the revision control history should anyone > wish to ressurect it after that date. However, I suspect that those > interested in ATM on FreeBSD have long since been using Harti's netgraph ATM > framework. Somehow the dates slipped pasted more quickly than I had hoped -- this is the HEADS UP that, on a slightly delayed schedule, I will be trimming netatm from the src tree for HEAD, and then a week or two later, from RELENG_7. Assuming all goes well, this should result in no functional change at all. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Wed May 21 22:14:37 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B218F106566B for ; Wed, 21 May 2008 22:14:37 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id 847DC8FC20 for ; Wed, 21 May 2008 22:14:37 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3056674rvf.43 for ; Wed, 21 May 2008 15:14:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received: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; bh=4CkiR5v4+cml67own8pAE6i3ozBGy+UiwJRBz5OU288=; b=OhS+f23c79Jz/O4yqdh8dj1kEKZQ32A5ocL0yoNisA6DsnIdD6k8vjM43y0CKFv3MEdhaXfUL1i5bIHqofWvJraQLY1tYC0p3XOCk7hDCgDZvjXPtDZdPbzJaMLeSxRAnbm45v9jooFvn5/W3D4oT6Chx0hZOgrRIwA8aWsv8eE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=p5IJTDa1uCKn5azQjdbPspqnXIKhsG38F85wRKygWCDATDspYMZu2d3jqsk5anzg2GNCgcSHu3xsBAuP5ULI42QG3AFaJkyJ3zCUiecfDKK4A8vu/dMFQejlemstKEvNvGsb3pmNPACiUXavHmDSwEPSf56bSP3a+v2Rtm+yacI= Received: by 10.141.190.9 with SMTP id s9mr5435421rvp.110.1211408077184; Wed, 21 May 2008 15:14:37 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Wed, 21 May 2008 15:14:37 -0700 (PDT) Message-ID: <2e77fc10805211514q59dd0eadkac2edce50d6c22f7@mail.gmail.com> Date: Thu, 22 May 2008 01:14:37 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Max Laier" In-Reply-To: <200805212332.13993.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805212305.58235.max@love2party.net> <2e77fc10805211422q75603d54h5709ed3e5be37d0a@mail.gmail.com> <200805212332.13993.max@love2party.net> X-Google-Sender-Auth: dc0909361e48dcb7 Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 22:14:37 -0000 On Thu, May 22, 2008 at 12:32 AM, Max Laier wrote: > On Wednesday 21 May 2008 23:22:52 Niki Denev wrote: >> On Thu, May 22, 2008 at 12:05 AM, Max Laier wrote: >> > Looks good, though I'd probably move up the _INVOKE to before the >> > ARPs are sent out. Probably between twiddling the hardware and >> > sending ARPs (though that needs an else-case if the interface is > ^------------------------------------------------- >> > still down). In fact the ARPs could be sent from an event hook, too. > ---------^ >> > This would get rid of INET specific code in the LL-interface code. >> >> I thought about moving it up too, but in this case isn't it going to >> be called only if the interface is up (IFF_UP)? > > See above. > Oh, I've missed that. So, generating ARPs from an event handler looks to like the best solution. But in that case what would be the correct place for it? if_ethersubr.c and the others (fw,fddi,arc...) that may use ARP? Niki From owner-freebsd-net@FreeBSD.ORG Wed May 21 22:41:44 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AAF21065675 for ; Wed, 21 May 2008 22:41:44 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by mx1.freebsd.org (Postfix) with ESMTP id A90768FC20 for ; Wed, 21 May 2008 22:41:43 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-024-001.pools.arcor-ip.net [88.66.24.1]) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis) id 0MKwpI-1Jyx0A27R9-0007yl; Thu, 22 May 2008 00:41:42 +0200 Received: (qmail 49354 invoked from network); 21 May 2008 22:39:59 -0000 Received: from myhost.laiers.local (192.168.4.151) by mx.laiers.local with SMTP; 21 May 2008 22:39:59 -0000 From: Max Laier Organization: FreeBSD To: "Niki Denev" Date: Thu, 22 May 2008 00:41:24 +0200 User-Agent: KMail/1.9.9 References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805212332.13993.max@love2party.net> <2e77fc10805211514q59dd0eadkac2edce50d6c22f7@mail.gmail.com> In-Reply-To: <2e77fc10805211514q59dd0eadkac2edce50d6c22f7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805220041.24096.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1/1Bi+296IA4gLQ3uzhCOCbnwpj5w7b7QlL8kZ TQy4fEbgdue/lgXoz+I4DPbSMKYdgn+0gEpkKVrwJq7rdobGWp 6XfJ4DcFtQKzA9eZ/rAIA== Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 22:41:44 -0000 On Thursday 22 May 2008 00:14:37 Niki Denev wrote: > On Thu, May 22, 2008 at 12:32 AM, Max Laier wrote: > > On Wednesday 21 May 2008 23:22:52 Niki Denev wrote: > >> On Thu, May 22, 2008 at 12:05 AM, Max Laier wrote: > >> > Looks good, though I'd probably move up the _INVOKE to before the > >> > ARPs are sent out. Probably between twiddling the hardware and > >> > sending ARPs (though that needs an else-case if the interface is > > > > ^------------------------------------------------- > > > >> > still down). In fact the ARPs could be sent from an event hook, > >> > too. > > > > ---------^ > > > >> > This would get rid of INET specific code in the LL-interface > >> > code. > >> > >> I thought about moving it up too, but in this case isn't it going to > >> be called only if the interface is up (IFF_UP)? > > > > See above. > > Oh, I've missed that. > > So, generating ARPs from an event handler looks to like the best > solution. But in that case what would be the correct place for it? > if_ethersubr.c and the others (fw,fddi,arc...) that may use ARP? I think if_ether.c would be good, where arp_ifinit() is. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Thu May 22 03:57:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41E32106566C for ; Thu, 22 May 2008 03:57:05 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 171208FC0A for ; Thu, 22 May 2008 03:57:04 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3197886rvf.43 for ; Wed, 21 May 2008 20:57:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received: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; bh=mitLIOKd+JP64qmKf+f3Aqt1st5AAMHnDqgnTfgNujo=; b=fCry4H1fvgR4mR3DlQiHuR02Hui4TidetYLAv9cy2XylslY0hsNWVWNPBR2DyThLBQOzzsZF4xDhJUvi27gE+d9N5QyinSfjkXqmGaCHMb05lOhzqe9cbgCFBzx8lMTSbsiLUkDhiolSmf3RwOCxadld7vTgix/uD6zKLWbV6t4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=AKyQKPXYO9riLODRAeH3CzNIOrYk03m19koRyzA8l7n/GGG8O3QCJWu87BWosX0XLieSd8R8gFpTj9SsZd0lCyyD4QFn3cqsGjDqEStKqr1+GcvKinENs4JZW+A+j/yKtWWR1Zt+iMEn5t6/mLFjJdBgT7n8tjYMVtDcBIzJlrA= Received: by 10.141.163.12 with SMTP id q12mr5545590rvo.265.1211428623293; Wed, 21 May 2008 20:57:03 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Wed, 21 May 2008 20:57:03 -0700 (PDT) Message-ID: <2e77fc10805212057y7cbeca00kd096a7b090413616@mail.gmail.com> Date: Thu, 22 May 2008 06:57:03 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Max Laier" In-Reply-To: <200805220041.24096.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805212332.13993.max@love2party.net> <2e77fc10805211514q59dd0eadkac2edce50d6c22f7@mail.gmail.com> <200805220041.24096.max@love2party.net> X-Google-Sender-Auth: 0f16f372375d8460 Cc: freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2008 03:57:05 -0000 On Thu, May 22, 2008 at 1:41 AM, Max Laier wrote: > I think if_ether.c would be good, where arp_ifinit() is. > Here is what i've come up with (some comments after the patch) : diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if.c /usr/src/sys/net/if.c --- /usr/src/.zfs/snapshot/orig/sys/net/if.c 2008-04-29 23:43:08.000000000 +0300 +++ /usr/src/sys/net/if.c 2008-05-22 04:56:42.652730327 +0300 @@ -2636,17 +2636,12 @@ (*ifp->if_ioctl)(ifp, SIOCSIFFLAGS, (caddr_t)&ifr); IFF_UNLOCKGIANT(ifp); } -#ifdef INET - /* - * Also send gratuitous ARPs to notify other nodes about - * the address change. - */ - TAILQ_FOREACH(ifa, &ifp->if_addrhead, ifa_link) { - if (ifa->ifa_addr->sa_family == AF_INET) - arp_ifinit(ifp, ifa); - } -#endif } + /* + * Notify interested parties about the link layer address change. + */ + EVENTHANDLER_INVOKE(ifaddr_event, ifp); + return (0); } diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if_ethersubr.c /usr/src/sys/net/if_ethersubr.c --- /usr/src/.zfs/snapshot/orig/sys/net/if_ethersubr.c 2008-05-21 23:29:07.899194044 +0300 +++ /usr/src/sys/net/if_ethersubr.c 2008-05-22 06:38:35.698083868 +0300 @@ -48,6 +48,7 @@ #include #include #include +#include #include #include @@ -99,6 +100,8 @@ #include +static eventhandler_tag ifaddr_tag; + /* netgraph node hooks for ng_ether(4) */ void (*ng_ether_input_p)(struct ifnet *ifp, struct mbuf **mp); void (*ng_ether_input_orphan_p)(struct ifnet *ifp, struct mbuf *m); @@ -910,6 +913,13 @@ if_printf(ifp, "Ethernet address: %6D\n", lla, ":"); if (ifp->if_flags & IFF_NEEDSGIANT) if_printf(ifp, "if_start running deferred for Giant\n"); +#ifdef INET + /* Register address change hook */ + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, arp_gratuit, + NULL, EVENTHANDLER_PRI_ANY); + //if (ifaddr_tag == NULL) + // return (ENOMEM); +#endif } /* @@ -924,6 +934,8 @@ (*ng_ether_detach_p)(ifp); } + EVENTHANDLER_DEREGISTER(ifaddr_event, ifaddr_tag); + bpfdetach(ifp); if_detach(ifp); } diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c /usr/src/sys/net/if_vlan.c --- /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c 2007-10-28 18:24:16.000000000 +0200 +++ /usr/src/sys/net/if_vlan.c 2008-05-22 00:18:57.128613715 +0300 @@ -137,6 +137,7 @@ static MALLOC_DEFINE(M_VLAN, VLANNAME, "802.1Q Virtual LAN Interface"); static eventhandler_tag ifdetach_tag; +static eventhandler_tag ifaddr_tag; /* * We have a global mutex, that is used to serialize configuration @@ -518,6 +519,35 @@ /* For if_link_state_change() eyes only... */ extern void (*vlan_link_state_p)(struct ifnet *, int); +/* + * Update vlan interface link layer address on + * parent interface link layer address change. + */ +static int +vlan_lladdr_update(void *arg __unused, struct ifnet *ifp) +{ + struct ifvlantrunk *trunk = ifp->if_vlantrunk; + struct ifvlan *ifv; + int i; + + if (trunk) { + TRUNK_LOCK(trunk); +#ifdef VLAN_ARRAY + for (i = 0; i < VLAN_ARRAY_SIZE; i++) + if (trunk->vlans[i] != NULL) { + ifv = trunk->vlans[i]; +#else + for (i = 0; i < (1 << trunk->hwidth); i++) { + LIST_FOREACH(ifv, &trunk->hash[i], ifv_list) +#endif + bcopy(IF_LLADDR(ifp), IF_LLADDR(ifv->ifv_ifp), + ETHER_ADDR_LEN); + } + TRUNK_UNLOCK(trunk); + } + return (0); +} + static int vlan_modevent(module_t mod, int type, void *data) { @@ -528,6 +558,10 @@ vlan_ifdetach, NULL, EVENTHANDLER_PRI_ANY); if (ifdetach_tag == NULL) return (ENOMEM); + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, + vlan_lladdr_update, NULL, EVENTHANDLER_PRI_ANY); + if (ifaddr_tag == NULL) + return (ENOMEM); VLAN_LOCK_INIT(); vlan_input_p = vlan_input; vlan_link_state_p = vlan_link_state; @@ -546,6 +580,7 @@ case MOD_UNLOAD: if_clone_detach(&vlan_cloner); EVENTHANDLER_DEREGISTER(ifnet_departure_event, ifdetach_tag); + EVENTHANDLER_DEREGISTER(ifaddr_event, ifaddr_tag); vlan_input_p = NULL; vlan_link_state_p = NULL; vlan_trunk_cap_p = NULL; diff -ur /usr/src/.zfs/snapshot/orig/sys/netinet/if_ether.c /usr/src/sys/netinet/if_ether.c --- /usr/src/.zfs/snapshot/orig/sys/netinet/if_ether.c 2007-10-07 23:44:22.000000000 +0300 +++ /usr/src/sys/netinet/if_ether.c 2008-05-22 06:41:34.966106759 +0300 @@ -956,6 +956,16 @@ ifa->ifa_flags |= RTF_CLONING; } +void +arp_gratuit(void *arg __unused, struct ifnet *ifp) +{ + struct ifaddr *ifa; + TAILQ_FOREACH(ifa, &ifp->if_addrhead, ifa_link) { + if (ifa->ifa_addr->sa_family == AF_INET) + arp_ifinit(ifp, ifa); + } +} + static void arp_init(void) { diff -ur /usr/src/.zfs/snapshot/orig/sys/netinet/if_ether.h /usr/src/sys/netinet/if_ether.h --- /usr/src/.zfs/snapshot/orig/sys/netinet/if_ether.h 2005-02-22 15:04:03.000000000 +0200 +++ /usr/src/sys/netinet/if_ether.h 2008-05-22 05:24:06.749938771 +0300 @@ -113,6 +113,7 @@ struct mbuf *m, struct sockaddr *dst, u_char *desten); void arp_ifinit(struct ifnet *, struct ifaddr *); void arp_ifinit2(struct ifnet *, struct ifaddr *, u_char *); +void arp_gratuit(void *, struct ifnet *); #endif #endif I think arp_gratuit() needs a better name. Is if_ethersubr.c:ether_ifattach() good place to register the EVENT hook? And if yes, what would be the best way to handle failure to register the hook, as the function is void? Should I worry about that, or just print a warning message and continue? Niki From owner-freebsd-net@FreeBSD.ORG Thu May 22 07:38:29 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD235106567B for ; Thu, 22 May 2008 07:38:29 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 8DD418FC1D for ; Thu, 22 May 2008 07:38:29 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jz5Nb-000CCc-EK for freebsd-net@freebsd.org; Thu, 22 May 2008 15:38:27 +0800 Message-ID: <483522F3.4090200@micom.mng.net> Date: Thu, 22 May 2008 15:38:27 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080304) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ipfw fwd layer2/ftp proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 22 May 2008 07:38:30 -0000 Hi there, I'm having trouble allowing ftp connections through ipfw (default deny) enabled bridge firewall. I'm wondering whether it is possible to have some kind of transparent ftp proxy in such case. Is there anyway I can allow ftp proxying without layer2 forwarding on ipfw bridge? I thought of forwarding packets in layer2, however it seems like ipfw still doesn't support that. I saw old patches of luigi@ and if somebody already has adapted that patch for RELENG_6/7 please let me know. I know my last try is to deny everything I don't want and then allow the rest. However I would like to make it work in current configuration. Please let me know your ideas. thanks in advance, Ganbold -- Sometimes I simply feel that the whole world is a cigarette and I'm the only ashtray. From owner-freebsd-net@FreeBSD.ORG Thu May 22 08:03:49 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EA021065679 for ; Thu, 22 May 2008 08:03:49 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 6D6DE8FC0A for ; Thu, 22 May 2008 08:03:46 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m4M83bGi022393; Thu, 22 May 2008 16:03:38 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m4M83bix022392; Thu, 22 May 2008 16:03:37 +0800 (KRAST) (envelope-from eugen) Date: Thu, 22 May 2008 16:03:37 +0800 From: Eugene Grosbein To: Ganbold Message-ID: <20080522080337.GA21814@svzserv.kemerovo.su> References: <483522F3.4090200@micom.mng.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <483522F3.4090200@micom.mng.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: ipfw fwd layer2/ftp proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 22 May 2008 08:03:49 -0000 On Thu, May 22, 2008 at 03:38:27PM +0800, Ganbold wrote: > I'm having trouble allowing ftp connections through ipfw (default deny) > enabled bridge firewall. > I'm wondering whether it is possible to have some kind of transparent > ftp proxy in such case. > > Is there anyway I can allow ftp proxying without layer2 forwarding on > ipfw bridge? You need not ftp proxy to make it work. Just allow ports that your ftp server uses. Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Thu May 22 08:34:26 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE5891065685 for ; Thu, 22 May 2008 08:34:26 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 94EED8FC62 for ; Thu, 22 May 2008 08:34:26 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jz6Fk-000CZ8-Gp; Thu, 22 May 2008 16:34:24 +0800 Message-ID: <48353010.20105@micom.mng.net> Date: Thu, 22 May 2008 16:34:24 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080304) MIME-Version: 1.0 To: Eugene Grosbein References: <483522F3.4090200@micom.mng.net> <20080522080337.GA21814@svzserv.kemerovo.su> In-Reply-To: <20080522080337.GA21814@svzserv.kemerovo.su> X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ipfw fwd layer2/ftp proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 22 May 2008 08:34:27 -0000 Eugene Grosbein wrote: > On Thu, May 22, 2008 at 03:38:27PM +0800, Ganbold wrote: > > >> I'm having trouble allowing ftp connections through ipfw (default deny) >> enabled bridge firewall. >> I'm wondering whether it is possible to have some kind of transparent >> ftp proxy in such case. >> >> Is there anyway I can allow ftp proxying without layer2 forwarding on >> ipfw bridge? >> > > You need not ftp proxy to make it work. Just allow ports that your > ftp server uses. > I know what you mean here. But ftp server is beyond my control (different ISP) and I don't know what ports it really uses. Ganbold > Eugene Grosbein > _______________________________________________ > 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" > > > > -- God made machine language; all the rest is the work of man. From owner-freebsd-net@FreeBSD.ORG Thu May 22 08:38:30 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0C22106566B for ; Thu, 22 May 2008 08:38:30 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id C75CA8FC19 for ; Thu, 22 May 2008 08:38:27 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m4M8cNcU026606; Thu, 22 May 2008 16:38:23 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m4M8cNcX026605; Thu, 22 May 2008 16:38:23 +0800 (KRAST) (envelope-from eugen) Date: Thu, 22 May 2008 16:38:23 +0800 From: Eugene Grosbein To: Ganbold Message-ID: <20080522083823.GA26482@svzserv.kemerovo.su> References: <483522F3.4090200@micom.mng.net> <20080522080337.GA21814@svzserv.kemerovo.su> <48353010.20105@micom.mng.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48353010.20105@micom.mng.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: ipfw fwd layer2/ftp proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 22 May 2008 08:38:31 -0000 On Thu, May 22, 2008 at 04:34:24PM +0800, Ganbold wrote: > >You need not ftp proxy to make it work. Just allow ports that your > >ftp server uses. > > I know what you mean here. But ftp server is beyond my control > (different ISP) and > I don't know what ports it really uses. Then use ftp passive mode and you'll need not open a port locally. Eugene From owner-freebsd-net@FreeBSD.ORG Thu May 22 08:56:22 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FEB8106568A; Thu, 22 May 2008 08:56:22 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 157B38FC4F; Thu, 22 May 2008 08:56:22 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4M8uLSo065871; Thu, 22 May 2008 08:56:21 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4M8uLWV065867; Thu, 22 May 2008 08:56:21 GMT (envelope-from vwe) Date: Thu, 22 May 2008 08:56:21 GMT Message-Id: <200805220856.m4M8uLWV065867@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-net@FreeBSD.org, rpaulo@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/123053: [re][patch] re(4) unsupported hardware revision (8168/8111b) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 22 May 2008 08:56:22 -0000 Synopsis: [re][patch] re(4) unsupported hardware revision (8168/8111b) Responsible-Changed-From-To: freebsd-net->rpaulo Responsible-Changed-By: vwe Responsible-Changed-When: Thu May 22 08:53:48 UTC 2008 Responsible-Changed-Why: reassign to rpaulo who has a similar ticket with a similar patch assigned. Rui: Can you please bring this ticket with kern/123123 in line? Either of one can be closed IMHO as the patches are very close to each other. http://www.freebsd.org/cgi/query-pr.cgi?pr=123053 From owner-freebsd-net@FreeBSD.ORG Thu May 22 12:42:56 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C08051065678 for ; Thu, 22 May 2008 12:42:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8CE8A8FC18 for ; Thu, 22 May 2008 12:42:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 24A1210A66D; Thu, 22 May 2008 08:42:56 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 22 May 2008 08:42:56 -0400 X-Sasl-enc: w5VJhvEEn/us4GCDfV00SMf47FcGncc3FazKdbC4sziA 1211460175 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 75C1232A02; Thu, 22 May 2008 08:42:55 -0400 (EDT) Message-ID: <48356A4D.2050404@FreeBSD.org> Date: Thu, 22 May 2008 13:42:53 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: Niki Denev References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805212332.13993.max@love2party.net> <2e77fc10805211514q59dd0eadkac2edce50d6c22f7@mail.gmail.com> <200805220041.24096.max@love2party.net> <2e77fc10805212057y7cbeca00kd096a7b090413616@mail.gmail.com> In-Reply-To: <2e77fc10805212057y7cbeca00kd096a7b090413616@mail.gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Max Laier , freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2008 12:42:56 -0000 Hi, It looks like this patch will cause gratuitous ARP to be queued even when the interface is not IFF_UP, is this intentional? Niki Denev wrote: > > I think arp_gratuit() needs a better name. > arp_announce() ? > Is if_ethersubr.c:ether_ifattach() good place to register the EVENT hook? > ARP is also used by FDDI and IEEE 802.5, as well as anything which emulates this. Taking the call to arp_ifinit() out of if_setlladdr() is likely to break this code. > And if yes, what would be the best way to handle failure to register > the hook, as the function is void? > > Should I worry about that, or just print a warning message and continue? > I see the C++-style comments - perhaps someone who knows event handlers better than I can comment, I believe it's using one of the shared kernel malloc pools with M_WAIT. It looks like this won't run afoul of locking, but it is a change to a fairly central path which needs to be considered carefully as it affects consumers other than Ethernet drivers. cheers BMS From owner-freebsd-net@FreeBSD.ORG Thu May 22 13:40:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E28B41065670 for ; Thu, 22 May 2008 13:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C87218FC28 for ; Thu, 22 May 2008 13:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4MDe349092565 for ; Thu, 22 May 2008 13:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4MDe3YA092563; Thu, 22 May 2008 13:40:03 GMT (envelope-from gnats) Date: Thu, 22 May 2008 13:40:03 GMT Message-Id: <200805221340.m4MDe3YA092563@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "yes298 yes298" Cc: Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yes298 yes298 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2008 13:40:04 -0000 The following reply was made to PR kern/123603; it has been noted by GNATS. From: "yes298 yes298" To: andre@freebsd.org Cc: "John Baldwin" , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/123603: tcp_do_segment and Received duplicate SYN Date: Thu, 22 May 2008 21:31:34 +0800 ------=_Part_11255_10246163.1211463094510 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear Sir, Thank you so much for your reply. My FreeBSD 7.0-Release-p1 (x64) Lighttpd web server *directly connects* to ISP's Cisco 3400 Switch with a 100M broadband line, After ISP technician creating a ARP static mapping rule on the switch to map the IP and MAC of My web server NIC, the problem of 5 seconds delay to view homepage has been solved, now , it is quit normal , no any delay. But, my web server sill has received repeatly below log messages, May 21 15:17:53 mail kernel: TCP: [55.66.77.88]:45979 to [11.22.33.44]:63372 tcpflags 0x10; tcp_do_segment: FIN_WAIT_1: Received 1448 bytes of data after socket was closed, sending RST and removing tcpcb May 21 15:17:53 mail kernel: TCP: [55.66.77.88]:21 to [11.22.33.44]:55007 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 13 bytes of data after socket was closed, sending RST and removing tcpcb May 21 22:26:16 mail kernel: TCP: [55.66.77.88]:23439 to [11.22.33.44]:80 tcpflags 0x18; syncache_expand: SEQ 2071739782 != IRS+1 2071738353, segment rejected May 22 11:31:22 mail kernel: TCP: [55.66.77.88]:2988 to [11.22.33.44]:80 tcpflags 0x10; syncache_expand: ACK 1544143634 != ISS+1 4145431138, segment rejected May 22 11:31:22 mail kernel: TCP: [55.66.77.88]:2988 to [11.22.33.44]:80 tcpflags 0x18; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) May 22 11:31:22 mail kernel: TCP: [55.66.77.88]:2988 to [11.22.33.44]:80 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) May 22 11:33:20 mail kernel: TCP: [55.66.77.88]:32345 to [11.22.33.44]:80 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK I sure to you that there no one to hack my server, because 55.66.77.88 is my client computer IP. I would like to know that the above messages will cause any problem? and how to solve this problem? Thank you so much! Best regards, Victor ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Victor, Please try two things: 1. Make sure that you don't have a problem with MTU sizes. Some ADSL customers with PPPoE have slightly smaller MTU sizes than normal ethernet. Make sure that ICMP unreach packets are not firewalled or filtered on your side. 2. There was a bug in the TCP options in FreeBSD 7.0-RELEASE that was giving problems with a smaller number of CPE devices for ADSL and Cablemodem customers. The problem is fixed in 7-STABLE. Only upgrading the kernel is sufficient. I hope this helps. If not, please provide some tcpdumps so we can see the packets that are exchanged. -- Andre ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Dear Sir, Thank you so much for your reply. My FreeBSD 7.0(x64) Lighttpd web server connects to a 100M broadband line, after testing many times, I found that, when first time to view my website, it needed to take almost 5~8 seconds to completely open the homepage which is only a static HTML file with content "coming soon", and there are some error log about TCP connection found on our web server, it seems that my FreeBSD 7.0 web server has problem to establish TCP connection. Before the web server idle time (30s), there are no any delay to re-view the homepage (Press F5), but after 30 seconds, it needed to take another 5~8 seconds to re-view, and the log messages will be repeated. May 15 15:18:21 mail kernel: TCP: [203.186.95.8]:12728 to [58.177.222.113]:80 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK May 15 15:19:03 mail kernel: TCP: [221.127.88.188]:5128 to [58.177.222.113]:80 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK I know how to disable these log messages, but I would like to know that the delay is because of receiving duplicate SYN? is it normal message? Please help me to solve the problem, thanks !!!! Thank you so much! Best regards, Victor ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- On Monday 12 May 2008 03:45:16 am John wrote: > >Number: 123603 > >Category: amd64 > >Synopsis: tcp_do_segment and Received duplicate SYN > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon May 12 07:50:01 UTC 2008 > >Closed-Date: > >Last-Modified: > >Originator: John > >Release: FB7.0 (x64) > >Organization: > > NULL > > >Environment: > > FreeBSD mail.mydomain.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu Mar 6 > 12:04:57 HKT 2008 root@mydomain.com:/usr/src/sys/amd64/compile/FB7NEW > amd64 > > >Description: > > A FreeBSD 7.0 (x64) Lighttpd Web Server with most-updated ports and patchs. > when a client connect and view a static HTML file, At the first time > (before web server idle time), it needs to wait a long time to establish a > connection, OR when this server try to download file from Internet, there > are lots of logs messages just like below: > > May 12 11:57:54 mail kernel: TCP: [55.66.77.88]:41792 to [11.22.33.44]:80 > tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer > and retransmitting SYN|ACK > May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:45979 to > [11.22.33.44]:63372 tcpflags 0x10; tcp_do_segment: FIN_WAIT_1: > Received 1448 bytes of data after socket was closed, sending RST and > removing tcpcb May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:21 to > [11.22.33.44]:55007 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: > Received 13 bytes of data after socket was closed, sending RST and removing > tcpcb > > >How-To-Repeat: > > any type of connection will generate above log messages. You can either comment out all the log(LOG_DEBUG, ...) calls in /sys/netinet/tcp*.c or change your /etc/syslog.conf to not send kern.debug messages to the console. I think these messages should probably be conditional on a kernel option FWIW. -- John Baldwin ------=_Part_11255_10246163.1211463094510 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear Sir,
 
Thank you so much for your reply.
 
My FreeBSD 7.0-Release-p1 (x64) Lighttpd web server directly connects to ISP's Cisco 3400 Switch with a 100M broadband line,
After ISP technician creating a ARP static mapping rule on the switch to map the IP and MAC of My web server NIC,
the problem of 5 seconds delay to view homepage has been solved, now , it is quit normal , no any delay.
But, my web server sill has received repeatly below log messages,

May 21 15:17:53 mail kernel: TCP: [55.66.77.88]:45979 to [11.22.33.44]:63372 tcpflags 0x10<ACK>; tcp_do_segment: FIN_WAIT_1: Received 1448 bytes of data after socket was closed, sending RST and removing tcpcb
May 21 15:17:53 mail kernel: TCP: [55.66.77.88]:21 to [11.22.33.44]:55007 tcpflags 0x18<PUSH>; tcp_do_segment: FIN_WAIT_2: Received 13 bytes of data after socket was closed, sending RST and removing tcpcb
May 21 22:26:16 mail kernel: TCP: [55.66.77.88]:23439 to [11.22.33.44]:80 tcpflags 0x18<PUSH>; syncache_expand: SEQ 2071739782 != IRS+1 2071738353,
segment rejected
May 22 11:31:22 mail kernel: TCP: [55.66.77.88]:2988 to [11.22.33.44]:80 tcpflags 0x10<ACK>; syncache_expand: ACK 1544143634 != ISS+1 4145431138, segment rejected
May 22 11:31:22 mail kernel: TCP: [55.66.77.88]:2988 to [11.22.33.44]:80 tcpflags 0x18<PUSH,ACK>; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed)
May 22 11:31:22 mail kernel: TCP: [55.66.77.88]:2988 to [11.22.33.44]:80 tcpflags 0x10<ACK>; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed)
May 22 11:33:20 mail kernel: TCP: [55.66.77.88]:32345 to [11.22.33.44]:80 tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK

I sure to you that there no one to hack my server, because 55.66.77.88 is my client computer IP.
I would like to know that the above messages will cause any problem? and how to solve this problem?

Thank you so much!
 
Best regards,
Victor
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Victor,

Please try two things:

 1. Make sure that you don't have a problem with MTU sizes. Some ADSL
   customers with PPPoE have slightly smaller MTU sizes than normal
   ethernet. Make sure that ICMP unreach packets are not firewalled
   or filtered on your side.

 2. There was a bug in the TCP options in FreeBSD 7.0-RELEASE that was
   giving problems with a smaller number of CPE devices for ADSL and
   Cablemodem customers. The problem is fixed in 7-STABLE. Only upgrading
   the kernel is sufficient.

I hope this helps.  If not, please provide some tcpdumps so we can see
the packets that are exchanged.

--
Andre
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Dear Sir,
 
Thank you so much for your reply.
 
My FreeBSD 7.0(x64) Lighttpd web server connects to a 100M broadband line, after testing many times, I found that, when first time to view my website, it needed to take almost 5~8 seconds to completely open the homepage which is only a static HTML file with content "coming soon", and there are some  error log about TCP connection found on our web server, it seems that my FreeBSD 7.0 web server has problem to establish TCP connection. Before the web server idle time (30s), there are no any delay to re-view the homepage (Press F5), but after 30 seconds, it needed to take another 5~8 seconds to re-view, and the log messages will be repeated.
 
May 15 15:18:21 mail kernel: TCP: [203.186.95.8]:12728 to [58.177.222.113]:80 tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK
May 15 15:19:03 mail kernel: TCP: [221.127.88.188]:5128 to [58.177.222.113]:80 tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK
 
I know how to disable these log messages, but I would like to know that the delay is because
of receiving duplicate SYN? is it normal message? Please help me to solve the problem, thanks !!!!
Thank you so much!
 
Best regards,
Victor
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On Monday 12 May 2008 03:45:16 am John wrote:
> >Number:         123603
> >Category:       amd64
> >Synopsis:       tcp_do_segment and Received duplicate SYN
> >Confidential:   no
> >Severity:       critical
> >Priority:       high
> >Responsible:    freebsd-amd64
> >State:          open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Mon May 12 07:50:01 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     John
> >Release:        FB7.0 (x64)
> >Organization:
>
> NULL
>
> >Environment:
>
> FreeBSD mail.mydomain.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Thu Mar  6
> 12:04:57 HKT 2008     root@mydomain.com:/usr/src/sys/amd64/compile/FB7NEW
> amd64
>
> >Description:
>
> A FreeBSD 7.0 (x64) Lighttpd Web Server with most-updated ports and patchs.
> when a client connect and view a static HTML file, At the first time
> (before web server idle time), it needs to wait a long time to establish a
> connection, OR when this server try to download file from Internet, there
> are lots of logs messages just like below:
>
> May 12 11:57:54 mail kernel: TCP: [55.66.77.88]:41792 to [11.22.33.44]:80
> tcpflags 0x2<SYN>; syncache_add: Received duplicate SYN, resetting timer
> and retransmitting SYN|ACK
> May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:45979 to
> [11.22.33.44]:63372 tcpflags 0x10<ACK>; tcp_do_segment: FIN_WAIT_1:
> Received 1448 bytes of data after socket was closed, sending RST and
> removing tcpcb May 12 15:17:53 mail kernel: TCP: [193.166.3.2]:21 to
> [11.22.33.44]:55007 tcpflags 0x18<PUSH,ACK>; tcp_do_segment: FIN_WAIT_2:
> Received 13 bytes of data after socket was closed, sending RST and removing
> tcpcb
>
> >How-To-Repeat:
>
> any type of  connection will generate above log messages.

You can either comment out all the log(LOG_DEBUG, ...) calls
in /sys/netinet/tcp*.c or change your /etc/syslog.conf to not send kern.debug
messages to the console.

I think these messages should probably be conditional on a kernel option FWIW.

--
John Baldwin ------=_Part_11255_10246163.1211463094510-- From owner-freebsd-net@FreeBSD.ORG Thu May 22 17:19:50 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 028081065675 for ; Thu, 22 May 2008 17:19:50 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outM.internet-mail-service.net (outm.internet-mail-service.net [216.240.47.236]) by mx1.freebsd.org (Postfix) with ESMTP id DBE6F8FC15 for ; Thu, 22 May 2008 17:19:49 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 5F5FD241E; Fri, 23 May 2008 05:29:02 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 866802D600E; Thu, 22 May 2008 10:19:49 -0700 (PDT) Message-ID: <4835AB38.40100@elischer.org> Date: Thu, 22 May 2008 10:19:52 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Ganbold References: <483522F3.4090200@micom.mng.net> In-Reply-To: <483522F3.4090200@micom.mng.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ipfw fwd layer2/ftp proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 22 May 2008 17:19:50 -0000 Ganbold wrote: > Hi there, > > I'm having trouble allowing ftp connections through ipfw (default deny) > enabled bridge firewall. > I'm wondering whether it is possible to have some kind of transparent > ftp proxy in such case. > > Is there anyway I can allow ftp proxying without layer2 forwarding on > ipfw bridge? > > I thought of forwarding packets in layer2, however it seems like ipfw > still doesn't support that. > I saw old patches of luigi@ and if somebody already has adapted that > patch for RELENG_6/7 please let me know. I have such patches for the old 'bridge' code that allow bridges to intercept IP sessions but not for the new 'if_bridge' code. The trick is to make a 'fwd localhost' on the Layer2 ipfw pass to result in the packet being passed to the IP stack regardless of where the header says it should go. In the IP stack a similar 'fwd localhost' rule (maybe the same one) will also trigger on the Layer 3 pass, and actually cause teh session to connect. For fully transparent (in both directions) you need to alter the IP code to allow you to bind the outgoing socket to a non-local address, and to capture the return packets you leed the L2 pirewall pass to do a test for 'uid' which has the side affect of noticing whether or not there is a local socket that matches a packet, even if it has a non local address on it. > > I know my last try is to deny everything I don't want and then allow the > rest. However I would > like to make it work in current configuration. > Please let me know your ideas. > > thanks in advance, > > Ganbold > From owner-freebsd-net@FreeBSD.ORG Fri May 23 03:05:39 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C5691065676 for ; Fri, 23 May 2008 03:05:39 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 08C1F8FC16 for ; Fri, 23 May 2008 03:05:38 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JzNb2-000JEU-ER; Fri, 23 May 2008 11:05:32 +0800 Message-ID: <4836347B.9050808@micom.mng.net> Date: Fri, 23 May 2008 11:05:31 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080304) MIME-Version: 1.0 To: Julian Elischer References: <483522F3.4090200@micom.mng.net> <4835AB38.40100@elischer.org> In-Reply-To: <4835AB38.40100@elischer.org> X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: ipfw fwd layer2/ftp proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 23 May 2008 03:05:39 -0000 Julian Elischer wrote: > Ganbold wrote: >> Hi there, >> >> I'm having trouble allowing ftp connections through ipfw (default >> deny) enabled bridge firewall. >> I'm wondering whether it is possible to have some kind of transparent >> ftp proxy in such case. >> >> Is there anyway I can allow ftp proxying without layer2 forwarding on >> ipfw bridge? >> >> I thought of forwarding packets in layer2, however it seems like ipfw >> still doesn't support that. >> I saw old patches of luigi@ and if somebody already has adapted that >> patch for RELENG_6/7 please let me know. > > > I have such patches for the old 'bridge' code that allow bridges to > intercept IP sessions but not for the new 'if_bridge' code. > The trick is to make a 'fwd localhost' on the Layer2 ipfw pass > to result in the packet being passed to the IP stack regardless > of where the header says it should go. > > In the IP stack a similar 'fwd localhost' rule (maybe the same one) > will also trigger on the Layer 3 pass, and actually cause teh session > to connect. > > For fully transparent (in both directions) you need to alter the IP > code to allow you to bind the outgoing socket to a non-local address, > and to capture the return packets you leed the L2 pirewall pass to > do a test for 'uid' which has the side affect of noticing whether or > not there is a local socket that matches a packet, even if it has > a non local address on it. Can you share your patch for old bride code? Yesterday I tried to look at ip_fw2.c and ip_input.c codes, but it is still new to me. thanks, Ganbold > > > >> >> I know my last try is to deny everything I don't want and then allow >> the rest. However I would >> like to make it work in current configuration. >> Please let me know your ideas. >> >> thanks in advance, >> >> Ganbold >> > > _______________________________________________ > 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" > > > -- Your fault - core dumped From owner-freebsd-net@FreeBSD.ORG Fri May 23 06:50:24 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56D7F106567D for ; Fri, 23 May 2008 06:50:24 +0000 (UTC) (envelope-from mutex@unixtech.info) Received: from unixtech.info (cl-12.chi-02.us.sixxs.net [IPv6:2001:4978:f:b::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7203E8FC0C for ; Fri, 23 May 2008 06:50:23 +0000 (UTC) (envelope-from mutex@unixtech.info) Received: from localhost (unknown [127.0.0.1]) by unixtech.info (Postfix) with ESMTP id EBAE91A9832 for ; Fri, 23 May 2008 02:50:42 -0400 (EDT) X-Virus-Scanned: amavisd-new at unixtech.info Received: from unixtech.info ([127.0.0.1]) by localhost (unixtech.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dac71+1-YxO for ; Fri, 23 May 2008 02:50:13 -0400 (EDT) Received: from webmail.unixtech.info (localhost [IPv6:::1]) by unixtech.info (Postfix) with ESMTP id 7BFD51A9830 for ; Fri, 23 May 2008 02:50:13 -0400 (EDT) Received: from 74.56.88.177 (SquirrelMail authenticated user mutex) by webmail.unixtech.info with HTTP; Fri, 23 May 2008 02:50:13 -0400 (EDT) Message-ID: <52090.74.56.88.177.1211525413.squirrel@webmail.unixtech.info> Date: Fri, 23 May 2008 02:50:13 -0400 (EDT) From: mutex@unixtech.info To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Atheros 5212 network issues. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 06:50:24 -0000 Hello! I am running FreeBSD 7.0 stable. I am having speed issues that I was not experiencing before when I was running 6.3 stable. My wireless connection is now unstable and not as much consistent as it was before. The wired connection is as usual ~7000kb/up and 800kb/down. Each test (~20 per day during 5 days) I did was on a 10 second interval, speed is fluctuating from ~80kb to ~4000kb down and ~80kb to ~300kb up and some tests return both download and upload to be very low. Also, one test can return 300kb down and 80kb up when next one 10 seconds later returns 80kb down and 300kb up. Latency is fluctuating as well. I tried to use another channel, swap disk and wireless card to another machine, cvsup and upgrade again. I didn't changed network settings, firewall rules, and my hostapd config. Here are some more informations on my hardware: FreeBSD 7.0-STABLE #0: Mon May 19 23:10:53 EDT 2008 mutex@xxxxxxx:/usr/obj/usr/src/sys/MUTEX Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 1.70GHz (1716.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf13 Stepping = 3 Features=0x3febfbff real memory = 805240832 (767 MB) avail memory = 774049792 (738 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x40bf on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xe0000000-0xe0ffffff,0xd8000000-0xdfffffff irq 16 at device 0.0 on pci1 uhci0: port 0xd800-0xd81f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xe4000000-0xe40003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 fxp0: port 0xc000-0xc03f mem 0xe3050000-0xe3050fff,0xe3020000-0xe303ffff irq 18 at device 0.0 on pci2 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:02:b3:b6:af:59 fxp0: [ITHREAD] ath0: mem 0xe3040000-0xe304ffff irq 21 at device 1.0 on pci2 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:14:a5:0d:c0:91 ath0: mac 10.5 phy 6.1 radio 6.3 fxp1: port 0xc400-0xc43f mem 0xe3052000-0xe3052fff,0xe3000000-0xe301ffff irq 22 at device 2.0 on pci2 miibus1: on fxp1 inphy1: PHY 1 on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:02:b3:b6:af:09 fxp1: [ITHREAD] vr0: port 0xc800-0xc8ff mem 0xe3051000-0xe30510ff irq 16 at device 3.0 on pci2 vr0: Quirks: 0x0 vr0: Revision: 0x43 miibus2: on vr0 ukphy0: PHY 8 on miibus2 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:50:ba:18:ff:5f vr0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcc7ff pnpid ORM0000 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1716911056 Hz quality 800 Timecounters tick every 1.000 msec ad1: 19073MB at ata0-slave UDMA100 acd0: CDROM at ata1-master PIO4 Trying to mount root from ufs:/dev/ad1s1a pciconf -lv | grep ath ath0@pci0:2:1:0: class=0x020000 card=0x000c17f9 chip=0x001b168c rev=0x01 hdr=0x00 athstats 36879 data frames received 50372 data frames transmit 135 tx frames with an alternate rate 3508 long on-chip tx retries 286 tx failed 'cuz too many retries 18M current transmit rate 1496 tx management frames 949 tx frames discarded prior to association 7427 tx frames with no ack marked 42411 tx frames with short preamble 76570 rx failed 'cuz of bad CRC 1980968 rx failed 'cuz of PHY err 1762216 OFDM timing 3 OFDM restart 218713 CCK timing 36 CCK restart 117021 beacons transmitted 420 periodic calibrations 55 rssi of last ack 29 avg recv rssi -96 rx noise floor 164 switched default/rx antenna Antenna profile: [1] tx 25569 rx 36157 [2] tx 24598 rx 36925 ifconfig: ath0: flags=8843 metric 0 mtu 2290 ether 00:14:a5:0d:c0:91 inet 10.0.3.1 netmask 0xffffff00 broadcast 10.0.3.255 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid mutex channel 1 (2412 Mhz 11g) bssid 00:14:a5:0d:c0:91 authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit TKIP 3:128-bit txpower 31.5 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS burst dtimperiod 1 sysctl: net.wlan.0.%parent: ath0 debug.disablefullpath: 0 hw.ath.hal.swba_backoff: 0 hw.ath.hal.sw_brt: 10 hw.ath.hal.dma_brt: 2 hw.ath.hal.version: 0.9.20.3 hw.ath.txbuf: 200 hw.ath.rxbuf: 40 hw.ath.regdomain: 0 hw.ath.countrycode: 0 hw.ath.xchanmode: 1 hw.ath.outdoor: 1 hw.ath.calibrate: 30 user.cs_path: /usr/bin:/bin:/usr/sbin:/sbin: dev.npx.0.%desc: math processor dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=1 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x001b subvendor=0x17f9 subdevice=0x000c cl ass=0x020000 dev.ath.0.%parent: pci2 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 16 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 48 dev.ath.0.ctstimeout: 48 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 dev.ath.0.txantenna: 0 dev.ath.0.rxantenna: 2 dev.ath.0.diversity: 0 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.fftxqmin: 2 dev.ath.0.fftxqmax: 50 dev.ath.0.monpass: 24 /etc/sysctl.conf *I didn't changed any other sysctl option* net.inet.ip.forwarding=1 Lines added to Generic kernel: # PF device pf device pflog device pfsync # ALTQ options ALTQ options ALTQ_CBQ # Class Bases Queuing (CBQ) options ALTQ_RED # Random Early Detection (RED) options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) options ALTQ_PRIQ # Priority Queuing (PRIQ) options ALTQ_NOPCC # Required for SMP build Please help me troubleshoot and resolve this issue. Regards, Mutex. pub 4096R/C4CE4832 2007-02-01 Key fingerprint = 8DAE C29D 44B7 CA85 28A3 AF0A BE37 B1E2 C4CE 4832 From owner-freebsd-net@FreeBSD.ORG Fri May 23 07:43:07 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95AC410656C4 for ; Fri, 23 May 2008 07:43:07 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id 5D12C8FC1B for ; Fri, 23 May 2008 07:43:06 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so639828rvf.43 for ; Fri, 23 May 2008 00:43:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received: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; bh=LdnCNWrxeuijHAUWmnsVicYwN4lG4gZn3taXwyNWTqI=; b=Tqms1TeKzqe3+TapFeIUgZrKzpkZYr6kpgeZCsTp3uykNkxFZil9drwVA8zKyLL6ezVsMhj+NG0GsdewYabkh/CkLjtpZdMLDBO0mQ/oaHUjTQddW6wC7Aww1G3nTWjEYFhTpe2/9B9Agi6UUTmK7vEFQUxgc+S87SWH8CNMMPI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=bmXQKuLUjpTRZLk5nsDd6PdREfHmbLQI0IVePz+DhgseCYq8jAG+L+PdEp2Wf4HbjjyYldOStq71gnzQfORT1DshH1y6ESWKh7uPVs4oRl1skxiaQ9oivoaKMEi/e0fp8x92gDf6MattmdIRhGtb4OiRvp4lXidqlh4WY6CXNEc= Received: by 10.141.114.19 with SMTP id r19mr514562rvm.146.1211528586374; Fri, 23 May 2008 00:43:06 -0700 (PDT) Received: by 10.141.171.3 with HTTP; Fri, 23 May 2008 00:43:06 -0700 (PDT) Message-ID: <2e77fc10805230043x2d6d2d9dp69ce9543209ad4e5@mail.gmail.com> Date: Fri, 23 May 2008 10:43:06 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "Bruce M. Simpson" In-Reply-To: <48356A4D.2050404@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2e77fc10805211031n6c42ffd2u3dee28164094b83b@mail.gmail.com> <200805212332.13993.max@love2party.net> <2e77fc10805211514q59dd0eadkac2edce50d6c22f7@mail.gmail.com> <200805220041.24096.max@love2party.net> <2e77fc10805212057y7cbeca00kd096a7b090413616@mail.gmail.com> <48356A4D.2050404@FreeBSD.org> X-Google-Sender-Auth: bdbe78b34e74ac95 Cc: Max Laier , freebsd-net@freebsd.org Subject: Re: lagg0.2 style vlans on lagg(4) interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 07:43:07 -0000 On Thu, May 22, 2008 at 3:42 PM, Bruce M. Simpson wrote: > Hi, > > It looks like this patch will cause gratuitous ARP to be queued even when > the interface is not IFF_UP, is this intentional? > > Niki Denev wrote: >> >> I think arp_gratuit() needs a better name. >> > > arp_announce() ? > >> Is if_ethersubr.c:ether_ifattach() good place to register the EVENT hook? >> > > ARP is also used by FDDI and IEEE 802.5, as well as anything which emulates > this. Taking the call to arp_ifinit() out of if_setlladdr() is likely to > break this code. > >> And if yes, what would be the best way to handle failure to register >> the hook, as the function is void? >> Should I worry about that, or just print a warning message and continue? >> > > I see the C++-style comments - perhaps someone who knows event handlers > better than I can comment, I believe it's using one of the shared kernel > malloc pools with M_WAIT. > > It looks like this won't run afoul of locking, but it is a change to a > fairly central path which needs to be considered carefully as it affects > consumers other than Ethernet drivers. > > cheers > BMS > > Well, yes, this change will have side effects... My initial problem was that vlan interfaces link layer address is not updated when the parents link layer address is changed, for example when adding the first member in a link aggregation lagg(4) interface. This patch seems to fix this for me : diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if.c /usr/src/sys/net/if.c --- /usr/src/.zfs/snapshot/orig/sys/net/if.c 2008-04-29 23:43:08.000000000 +0300 +++ /usr/src/sys/net/if.c 2008-05-22 17:15:15.681205282 +0300 @@ -2636,6 +2636,7 @@ (*ifp->if_ioctl)(ifp, SIOCSIFFLAGS, (caddr_t)&ifr); IFF_UNLOCKGIANT(ifp); } + EVENTHANDLER_INVOKE(ifaddr_event, ifp); #ifdef INET /* * Also send gratuitous ARPs to notify other nodes about @@ -2646,6 +2647,8 @@ arp_ifinit(ifp, ifa); } #endif + } else { + EVENTHANDLER_INVOKE(ifaddr_event, ifp); } return (0); } diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if_lagg.c /usr/src/sys/net/if_lagg.c --- /usr/src/.zfs/snapshot/orig/sys/net/if_lagg.c 2008-04-19 14:45:20.055330961 +0300 +++ /usr/src/sys/net/if_lagg.c 2008-05-23 09:51:22.911830591 +0300 @@ -303,6 +303,7 @@ /* Let the protocol know the MAC has changed */ if (sc->sc_lladdr != NULL) (*sc->sc_lladdr)(sc); + EVENTHANDLER_INVOKE(ifaddr_event, ifp); } static void @@ -364,6 +365,7 @@ /* Update the lladdr even if pending, it may have changed */ llq->llq_ifp = ifp; bcopy(lladdr, llq->llq_lladdr, ETHER_ADDR_LEN); + EVENTHANDLER_INVOKE(ifaddr_event, ifp); if (!pending) SLIST_INSERT_HEAD(&sc->sc_llq_head, llq, llq_entries); diff -ur /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c /usr/src/sys/net/if_vlan.c --- /usr/src/.zfs/snapshot/orig/sys/net/if_vlan.c 2007-10-28 18:24:16.000000000 +0200 +++ /usr/src/sys/net/if_vlan.c 2008-05-22 17:32:40.849337824 +0300 @@ -137,6 +137,7 @@ static MALLOC_DEFINE(M_VLAN, VLANNAME, "802.1Q Virtual LAN Interface"); static eventhandler_tag ifdetach_tag; +static eventhandler_tag ifaddr_tag; /* * We have a global mutex, that is used to serialize configuration @@ -190,6 +191,7 @@ static void vlan_link_state(struct ifnet *ifp, int link); static void vlan_capabilities(struct ifvlan *ifv); static void vlan_trunk_capabilities(struct ifnet *ifp); +static int vlan_lladdr_update(void *arg, struct ifnet *ifp); static struct ifnet *vlan_clone_match_ethertag(struct if_clone *, const char *, int *); @@ -528,6 +530,10 @@ vlan_ifdetach, NULL, EVENTHANDLER_PRI_ANY); if (ifdetach_tag == NULL) return (ENOMEM); + ifaddr_tag = EVENTHANDLER_REGISTER(ifaddr_event, vlan_lladdr_update, + NULL, EVENTHANDLER_PRI_ANY); + if (ifaddr_tag == NULL) + return (ENOMEM); VLAN_LOCK_INIT(); vlan_input_p = vlan_input; vlan_link_state_p = vlan_link_state; @@ -546,6 +552,7 @@ case MOD_UNLOAD: if_clone_detach(&vlan_cloner); EVENTHANDLER_DEREGISTER(ifnet_departure_event, ifdetach_tag); + EVENTHANDLER_DEREGISTER(ifaddr_event, ifaddr_tag); vlan_input_p = NULL; vlan_link_state_p = NULL; vlan_trunk_cap_p = NULL; @@ -1280,6 +1287,35 @@ TRUNK_UNLOCK(trunk); } +/* + * Update vlan interface link layer address on + * parent interface link layer address change. + */ +static int +vlan_lladdr_update(void *arg __unused, struct ifnet *ifp) +{ + struct ifvlantrunk *trunk = ifp->if_vlantrunk; + struct ifvlan *ifv; + int i; + + if (trunk) { + TRUNK_LOCK(trunk); +#ifdef VLAN_ARRAY + for (i=0; i < VLAN_ARRAY_SIZE; i++) + if (trunk->vlans[i] != NULL) { + ifv = trunk->vlans[i]; +#else + for (i=0; i < (1 << trunk->hwidth); i++) { + LIST_FOREACH(ifv, &trunk->hash[i], ifv_list) +#endif + bcopy(IF_LLADDR(ifp), IF_LLADDR(ifv->ifv_ifp), + ETHER_ADDR_LEN); + } + TRUNK_UNLOCK(trunk); + } + return (0); +} + static int vlan_ioctl(struct ifnet *ifp, u_long cmd, caddr_t data) { I have left the gratuitious arp sending alone in this one, also I wonder if there is a need for another kernel event like iflladdr_event? Another problem is that many drivers handle things internally by making bcopy's or memcpy's of the lladdr and not generating events, which probably should be done by some function. Niki From owner-freebsd-net@FreeBSD.ORG Fri May 23 10:00:16 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BF68106564A for ; Fri, 23 May 2008 10:00:16 +0000 (UTC) (envelope-from juri_mian@yahoo.com) Received: from n66.bullet.mail.sp1.yahoo.com (n66.bullet.mail.sp1.yahoo.com [98.136.44.50]) by mx1.freebsd.org (Postfix) with SMTP id 1A9FC8FC16 for ; Fri, 23 May 2008 10:00:16 +0000 (UTC) (envelope-from juri_mian@yahoo.com) Received: from [216.252.122.219] by n66.bullet.mail.sp1.yahoo.com with NNFMP; 23 May 2008 09:47:31 -0000 Received: from [69.147.65.165] by t4.bullet.sp1.yahoo.com with NNFMP; 23 May 2008 09:47:31 -0000 Received: from [127.0.0.1] by omp500.mail.sp1.yahoo.com with NNFMP; 23 May 2008 09:47:31 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 524857.7248.bm@omp500.mail.sp1.yahoo.com Received: (qmail 67785 invoked by uid 60001); 23 May 2008 09:47:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=uQvN+/TsGwo1gPTXw3FFvTV0Y9Ux7wMSQftVJNMCx03W+KCkQO/Yq4FEZ0DMSfzraeuZSZSb0u2RDNzjrJxxciWkmEowFO9csDuXhm15mXMW1RNP3O3g97wrVUw6OyOHXP5vdQBuyQIL6IPpcNO6zJlWPHbFjBo46DlnOMizdPI=; X-YMail-OSG: cAW9BlAVM1lRgtI_fbhRqN5xjc7Bm26SMXfucmu1jIqdhJKSiTXuM0cg3z9NLsGgPWVO52Gu03wO Received: from [85.61.27.87] by web45605.mail.sp1.yahoo.com via HTTP; Fri, 23 May 2008 02:47:30 PDT Date: Fri, 23 May 2008 02:47:30 -0700 (PDT) From: Juri Mianovich To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <321306.67555.qm@web45605.mail.sp1.yahoo.com> Subject: minimum bandwidth per connection with dummynet ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 23 May 2008 10:00:16 -0000 I have two simple dummynet rules in place (with ipfw): - one pipe limits inbound - one pipe limits outbound However, if there are multiple connections taking place, all over fast links, the pipe gets saturated. This is not so bad, but I am not convinced it is allocating bandwidth fairly between all participants during saturation. Two questions: - is there a simple setting that says "allocate bandwidth evenly between all connections in a saturated pipe" ? - alternatively, is there a minimum speed per connection that I can establish for a dummynet pipe ? Presumably actual performance would drop below the minimum if the product of connections * minimum was less than the total bandwidth of the pipe, but as long as that wasn't true, everyone would at least get reasonable speed, instead of one client eating the pipe and everyone else trickling along... Thanks. From owner-freebsd-net@FreeBSD.ORG Fri May 23 18:10:07 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F43A1065672 for ; Fri, 23 May 2008 18:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EEDD58FC13 for ; Fri, 23 May 2008 18:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4NIA6Wc061541 for ; Fri, 23 May 2008 18:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4NIA69U061540; Fri, 23 May 2008 18:10:06 GMT (envelope-from gnats) Date: Fri, 23 May 2008 18:10:06 GMT Message-Id: <200805231810.m4NIA69U061540@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Lev Serebryakov Cc: Subject: Re: kern/121298: [em] [panic] Fatal trap 12: page fault while in kernel mode (em0 taskq) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lev Serebryakov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 18:10:07 -0000 The following reply was made to PR kern/121298; it has been noted by GNATS. From: Lev Serebryakov To: bug-followup@FreeBSD.org, admin@aknet.ru Cc: Subject: Re: kern/121298: [em] [panic] Fatal trap 12: page fault while in kernel mode (em0 taskq) Date: Fri, 23 May 2008 21:47:41 +0400 Hello, bug-followup. I've got very similar panic. `csup' from local (located in same segment) cvsup server via gigabit link and RAID5 (geom_raid5) synchronize newely-created array with 4 disks. csup writes on OTHER disk, not included in array. No crashdump, because core was not saved: machine hangs up right after panic message, without attempts to save dump or reboot. Crash dumps are enabled and I got previous one (other bug), but in this case no dumps, no reaction on keyboards, etc. Need to reboot with pwoer switch :( ==================== panic message, typed by hands em0: watchdog timeout -- resetting kernel trap 12 with interrupts disabled Fatal trap 12: page fault in kernnel mode cpuid = 1; apic id = 01 fault virtual addewaa = 0x28 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff80282c2f stack pointer = 0x10:0xffffffffabed4b20 frame pointer = 0x10:0xffffff00010c9000 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor efalgs = resume, IOPL = 1 current process = 23 (em0 taskq) trap number = 12 panic: page fault cpuid = 1 ==================== panic message, typed by hands ========================================= uname -a FreeBSD blob.home.serebryakov.spb.ru 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon May 19 21:26:08 MSD 2008 lev@blob.home.serebryakov.spb.ru:/usr/obj/usr/src/sys/BLOB amd64 ========================================= uname -a ============================================ dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #0: Mon May 19 21:26:08 MSD 2008 lev@blob.home.serebryakov.spb.ru:/usr/obj/usr/src/sys/BLOB Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2200.09-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fd Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 6364114944 (6069 MB) avail memory = 6141857792 (5857 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cfd00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - 51, should be 4C [20070320] coretemp0: on cpu0 est0: on cpu0 est0: Setting 2200 MHz p4tcc0: on cpu0 cpu1: on acpi0 coretemp1: on cpu1 est1: on cpu1 est1: Setting 2200 MHz p4tcc1: on cpu1 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xec00-0xec07 mem 0xfea80000-0xfeafffff,0xd0000000-0xdfffffff,0xfe900000-0xfe9fffff irq 16 at device 2.0 on pci0 pci0: at device 3.0 (no driver attached) em0: port 0xe880-0xe89f mem 0xfea40000-0xfea5ffff,0xfea7a000-0xfea7afff irq 20 at device 25.0 on pci0 em0: [FILTER] em0: Ethernet address: 00:1e:8c:75:03:0d uhci0: port 0xe400-0xe41f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe480-0xe49f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe800-0xe81f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfea7b800-0xfea7bbff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered uhci3: port 0xdc00-0xdc1f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xe000-0xe01f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xe080-0xe09f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xfea7b400-0xfea7b7ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: EHCI version 1.0 usb7: companion controllers, 2 ports each: usb4 usb5 usb6 usb7: on ehci1 usb7: USB revision 2.0 uhub7: on usb7 uhub7: 6 ports with 6 removable, self powered pcib1: at device 30.0 on pci0 pci1: on pcib1 fwohci0: mem 0xfebff000-0xfebfffff irq 20 at device 2.0 on pci1 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:1e:8c:00:00:1a:5f:da fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd807,0xd480-0xd483,0xd400-0xd407,0xd080-0xd083,0xd000-0xd01f mem 0xfea79800-0xfea79fff irq 22 at device 31.2 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.20 controller with 6 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ata6: on atapci0 ata6: [ITHREAD] ata7: on atapci0 ata7: [ITHREAD] ichsmb0: port 0x400-0x41f mem 0xfea7b000-0xfea7b0ff irq 18 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] ichsmb0: [ITHREAD] smbus0: on ichsmb0 smb0: on smbus0 pci0: at device 31.6 (no driver attached) acpi_button0: on acpi0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xcb800-0xcc7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ZFS filesystem version 6 ZFS storage pool version 6 ad4: 305245MB at ata2-master SATA300 ad6: 476940MB at ata3-master SATA300 ad10: 476940MB at ata5-master SATA300 ad12: 476940MB at ata6-master SATA300 ad14: 476940MB at ata7-master SATA300 SMP: AP CPU #1 Launched! GEOM_RAID5: storage: device created (stripesize=131072). GEOM_RAID5: storage: ad6(0): newest disk data (CALM): 0. GEOM_RAID5: storage: ad6(0): disk attached. GEOM_RAID5: storage: ad10(1): newest disk data (CALM): 1. GEOM_RAID5: storage: ad10(1): disk attached. GEOM_RAID5: storage: ad12(2): newest disk data (CALM): 2. GEOM_RAID5: storage: ad12(2): disk attached. GEOM_RAID5: storage: ad14(3): newest disk data (CALM): 3. GEOM_RAID5: storage: ad14(3): disk attached. GEOM_RAID5: storage: activated (need about 76MiB kmem (max)). Trying to mount root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 4 files 1 ============================================ dmesg ==================================== kernel config cpu HAMMER ident BLOB makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq device coretemp device smb device smbus device ichsmb device iicbus device iicsmb device iic # Bus support. device acpi device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver # syscons is the default console driver, resembling an SCO console device sc # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) device em # Intel PRO/1000 adapter Gigabit Ethernet Card # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) # FireWire support device firewire # FireWire bus code ==================================== kernel config -- // Black Lion AKA Lev Serebryakov From owner-freebsd-net@FreeBSD.ORG Fri May 23 22:13:10 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C2721065676 for ; Fri, 23 May 2008 22:13:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.freebsd.org (Postfix) with ESMTP id 0BA258FC1B for ; Fri, 23 May 2008 22:13:09 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m4NMD77F022252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 May 2008 08:13:08 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m4NMD7Co083693; Sat, 24 May 2008 08:13:07 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m4NMD7Zv083692; Sat, 24 May 2008 08:13:07 +1000 (EST) (envelope-from peter) Date: Sat, 24 May 2008 08:13:07 +1000 From: Peter Jeremy To: Juri Mianovich Message-ID: <20080523221306.GY1469@server.vk2pj.dyndns.org> References: <321306.67555.qm@web45605.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xXygN3QAmJYWdGtb" Content-Disposition: inline In-Reply-To: <321306.67555.qm@web45605.mail.sp1.yahoo.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org Subject: Re: minimum bandwidth per connection with dummynet ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 23 May 2008 22:13:10 -0000 --xXygN3QAmJYWdGtb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-May-23 02:47:30 -0700, Juri Mianovich wrote: >- is there a simple setting that says "allocate >bandwidth evenly between all connections in a >saturated pipe" ? TCP does this automatically. >- alternatively, is there a minimum speed per >connection that I can establish for a dummynet pipe ?=20 Not that I can see - you can use the 'mask' parameter to define a maximum per-connection rate. I don't believe there's any way to redirect "overflow" traffic though. You could probably write a divert(4) application to do the shaping you require. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --xXygN3QAmJYWdGtb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkg3QXIACgkQ/opHv/APuIe5UQCffjZOqb+z+8eVgHTqrMkJoMu+ a7wAn0Ajh23P70SQh7YBVIG05LQFhG8+ =CBR0 -----END PGP SIGNATURE----- --xXygN3QAmJYWdGtb-- From owner-freebsd-net@FreeBSD.ORG Fri May 23 23:19:45 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FA3F106564A; Fri, 23 May 2008 23:19:45 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4234D8FC14; Fri, 23 May 2008 23:19:45 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4NNJjoH089125; Fri, 23 May 2008 23:19:45 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4NNJjNW089121; Fri, 23 May 2008 23:19:45 GMT (envelope-from vwe) Date: Fri, 23 May 2008 23:19:45 GMT Message-Id: <200805232319.m4NNJjNW089121@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/123892: [tap] [patch] No buffer space available X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 23 May 2008 23:19:45 -0000 Synopsis: [tap] [patch] No buffer space available Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Fri May 23 23:19:33 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123892 From owner-freebsd-net@FreeBSD.ORG Sat May 24 00:39:13 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA90D106566C for ; Sat, 24 May 2008 00:39:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outM.internet-mail-service.net (outm.internet-mail-service.net [216.240.47.236]) by mx1.freebsd.org (Postfix) with ESMTP id A155B8FC12 for ; Sat, 24 May 2008 00:39:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 8C6FE2986 for ; Fri, 23 May 2008 17:39:13 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 414F92D6004 for ; Fri, 23 May 2008 17:39:13 -0700 (PDT) Message-ID: <483763B5.4030205@elischer.org> Date: Fri, 23 May 2008 17:39:17 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: anyone tried the Multi routing table code yet? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 00:39:13 -0000 subject says it all really.. From owner-freebsd-net@FreeBSD.ORG Sat May 24 00:57:51 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7123D1065671 for ; Sat, 24 May 2008 00:57:51 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id D19308FC15 for ; Sat, 24 May 2008 00:57:50 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (DSTO/DSTO) with ESMTP id m4O0rWFG028792 for ; Sat, 24 May 2008 10:23:32 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Sat, 24 May 2008 10:26:29 +0930 Received: from stlex510.dsto.defence.gov.au ([203.6.60.184]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.3959); Sat, 24 May 2008 10:26:28 +0930 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by stlex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Sat, 24 May 2008 08:56:28 +0800 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.14.2/8.14.2) with ESMTP id m4O0p8pr051056 for ; Sat, 24 May 2008 08:51:08 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.14.2/8.14.2/Submit) id m4O0p8di051055 for freebsd-net@freebsd.org; Sat, 24 May 2008 08:51:08 +0800 (WST) (envelope-from wilkinsa) Date: Sat, 24 May 2008 08:51:08 +0800 From: "Wilkinson, Alex" To: freebsd-net@freebsd.org Message-ID: <20080524005108.GA51044@stlux503.dsto.defence.gov.au> Mail-Followup-To: freebsd-net@freebsd.org References: <483763B5.4030205@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <483763B5.4030205@elischer.org> Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.18 (2008-05-17) X-OriginalArrivalTime: 24 May 2008 00:56:28.0439 (UTC) FILETIME=[FF9D8270:01C8BD38] X-TM-AS-Product-Ver: SMEX-7.0.0.1584-5.5.1026-15926.007 X-TM-AS-Result: No--0.381000-0.000000-31 Content-Transfer-Encoding: 7bit Subject: Re: anyone tried the Multi routing table code yet? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 00:57:51 -0000 0n Fri, May 23, 2008 at 05:39:17PM -0700, Julian Elischer wrote: >subject says it all really.. No, but I would like to ... if you could hold my hand :) -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-net@FreeBSD.ORG Sat May 24 02:09:35 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3B7B106567B; Sat, 24 May 2008 02:09:34 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B65668FC23; Sat, 24 May 2008 02:09:34 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4O29YQT002021; Sat, 24 May 2008 02:09:34 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4O29YcU002017; Sat, 24 May 2008 02:09:34 GMT (envelope-from linimon) Date: Sat, 24 May 2008 02:09:34 GMT Message-Id: <200805240209.m4O29YcU002017@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/123881: [tcp] Turning on TCP blackholing causes slow localhost connections X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 02:09:35 -0000 Old Synopsis: Turning on TCP blackholing causes slow localhost connections New Synopsis: [tcp] Turning on TCP blackholing causes slow localhost connections Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 24 02:09:06 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123881 From owner-freebsd-net@FreeBSD.ORG Sat May 24 07:35:27 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E753C1065675 for ; Sat, 24 May 2008 07:35:27 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (neilhoggarth-2.dsl.easynet.co.uk [217.206.124.94]) by mx1.freebsd.org (Postfix) with ESMTP id 805418FC17 for ; Sat, 24 May 2008 07:35:27 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (localhost [127.0.0.1]) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2) with ESMTP id m4O7ZOCf001032; Sat, 24 May 2008 08:35:24 +0100 (BST) (envelope-from neil@hoggarth.me.uk) Received: from localhost (njh@localhost) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2/Submit) with ESMTP id m4O7ZMKT001029; Sat, 24 May 2008 08:35:24 +0100 (BST) (envelope-from neil@hoggarth.me.uk) X-Authentication-Warning: neilhoggarth-2.dsl.easynet.co.uk: njh owned process doing -bs Date: Sat, 24 May 2008 08:35:22 +0100 (BST) From: Neil Hoggarth X-X-Sender: njh@neilhoggarth-2.dsl.easynet.co.uk To: Jack Vogel In-Reply-To: <2a41acea0805211352s37e6fd40maaaac90e51912947@mail.gmail.com> Message-ID: References: <2a41acea0805211326v74baa017tc03fcd329a764ef5@mail.gmail.com> <2a41acea0805211352s37e6fd40maaaac90e51912947@mail.gmail.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: [em][panic] recursed on non-recursive mutex em0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 07:35:28 -0000 On Wed, 21 May 2008, Jack Vogel wrote: >>> I opened PR kern/122928 last month, describing my problems with Intel > > OPPS, I think I found the problem, look for a delta on if_em.c shortly. > > Let me know if this fixes your problem. Thanks. I picked up delta 1.184.2.3 to if_em.c on Thursday morning. The system no longer panics on watchdog timeout, but the original problem from PR kern/122928 remains - once a watchdog timeout occurs the interface no longer seems to receive packets and never properly recovers, short of rebooting the system (or perhaps the watchdog timeout is actually a symptom of whatever has "got stuck", rather than a cause?). The PR is still in "feedback" state, but I think I've provided the requested information. Is there anything else that I can do to help progress this? Regards, Neil. From owner-freebsd-net@FreeBSD.ORG Sat May 24 08:40:02 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEA94106566B for ; Sat, 24 May 2008 08:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BA3AF8FC25 for ; Sat, 24 May 2008 08:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4O8e2UX062969 for ; Sat, 24 May 2008 08:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4O8e2Xe062968; Sat, 24 May 2008 08:40:02 GMT (envelope-from gnats) Date: Sat, 24 May 2008 08:40:02 GMT Message-Id: <200805240840.m4O8e2Xe062968@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Neil Hoggarth Cc: Subject: kern/122928: [em] interface watchdog timeouts and stops receiving packets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Neil Hoggarth List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2008 08:40:02 -0000 The following reply was made to PR kern/122928; it has been noted by GNATS. From: Neil Hoggarth To: bug-followup@FreeBSD.org Cc: Subject: kern/122928: [em] interface watchdog timeouts and stops receiving packets Date: Sat, 24 May 2008 09:31:10 +0100 (BST) For the record, the problem persists following the recent MFC of the em driver and locking fix in delta 1.184.2.3 of if_em.c. ifconfig em0: em0: flags=8843 metric 0 mtu 1500 options=9b ether 00:0e:0c:06:c2:3a inet 10.0.0.7 netmask 0xff000000 broadcast 10.255.255.255 media: Ethernet autoselect (1000baseTX ) status: active sysctl dev.em: dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 6.9.5 dev.em.0.%driver: em dev.em.0.%location: slot=9 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x100e subvendor=0x8086 subdevice=0x002e class=0x020000 dev.em.0.%parent: pci2 dev.em.0.debug: -1 dev.em.0.stats: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 From owner-freebsd-net@FreeBSD.ORG Sat May 24 10:21:00 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9422B106564A; Sat, 24 May 2008 10:21:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5F0078FC0C; Sat, 24 May 2008 10:21:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D506746B64; Sat, 24 May 2008 06:20:59 -0400 (EDT) Date: Sat, 24 May 2008 11:20:59 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: net@FreeBSD.org, current@FreeBSD.org Message-ID: <20080524111715.T64552@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org Subject: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 10:21:00 -0000 Dear all: Just as a reminder, we've just about reached the one month date before IFF_NEEDSGIANT drivers are disabled in the build. You can find a description of the general problem and list of specific drivers below. As USB work is on-going, I will *not* disable the USB drivers at this time, but all other drivers in the list below will be disabled on 26 June. They will remain in the tree, easily accessible for patch distribution and re-enabling, until October, when any remaining non-MPSAFE drivers will be deleted in 8.x. FreeBSD 8.0 will not ship with compatibility shims to support non-MPSAFE network device drivers. Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Sun, 3 Feb 2008 20:59:05 +0000 (GMT) From: Robert Watson To: arch@FreeBSD.org Subject: 8.0 network stack MPsafety goals (fwd) Only a few days after predicted, this is a reminder that IFF_NEEDSGIANT network drivers are going to stop working in the forseeable future. Please review the attached driver list, and if you depend on or care about a Giant-dependent device driver, take action to make sure it doesn't remain on the list in a month's time! (As far as I'm aware, the list has not changed since my December posting.) Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Mon, 24 Dec 2007 10:43:28 +0000 (GMT) From: Robert Watson To: arch@FreeBSD.org Subject: 8.0 network stack MPsafety goals Dear all: With the 7.0 release around the corner, many developers are starting to think about (and in quite a few cases, work on) their goals for 8.0. One of our on-going kernel projects has been the elimination of the Giant lock, and that project has transformed into one of optimizating behavior on increasing numbers of processors. In 7.0, despite the noteworth accomplishment of eliminating debug.mpsasfenet and conditional network stack Gian acquisition, we were unable to fully eliminate the IFF_NEEDSGIANT flag, which controls the conditional acquisition of the Giant lock around non-MPSAFE network device drivers. Primarily these drivers are aging ISA network device drivers, although there are some exceptions, such as the USB stack. This e-mail proposes the elimination of the IFF_NEEDSGIANT flag and associated infrastructure in FreeBSD 8.0, meaning that all network device drivers must be able to operate without the Giant lock (largely the case already). Remaining drivers using the IFF_NEEDSGIANT flag must either be updated, or less ideally, removed. I propose the following schedule: Date Goals ---- ----- 26 Dec 2007 Post proposed schedule for flag and infrastructure removal Post affected driver list 26 Jan 2008 Repost proposed schedule for flag and infrastructure removal Post updated affected driver list 26 Feb 2008 Adjust boot-time printf for affect drivers to generate a loud warning. Post updated affected driver list 26 May 2008 Post HEADS UP of impending driver disabling Post updated affected driver list 26 Jun 2008 Disable build of all drivers requiring IFF_NEEDSGIANT Post updated affected driver list 26 Sep 2008 Post HEADS up of impending driver removal Post updated affected driver list 26 Oct 2008 Delete source of all drivers requiring IFF_NEEDSGIANT Remove flag and infrastructure Here is a list of potentially affected drivers: Name Bus Man page description --- --- -------------------- ar ISA/PCI synchronous Digi/Arnet device driver arl ISA Aironet Arlan 655 wireless network adapter driver awi PCCARD AMD PCnetMobile IEEE 802.11 PCMCIA wireless network driver axe USB ASIX Electronics AX88172 USB Ethernet driver cdce USB USB Communication Device Class Ethernet driver cnw PCCARD Netwave AirSurfer wireless network driver cs ISA/PCCARD Ethernet device driver cue USB CATC USB-EL1210A USB Ethernet driver ex ISA/PCCARD Ethernet device driver for the Intel EtherExpress Pro/10 and Pro/10+ fe CBUS/ISA/PCCARD Fujitsu MB86960A/MB86965A based Ethernet adapters ic I2C I2C bus system ie ISA Ethernet device driver kue USB Kawasaki LSI KL5KUSB101B USB Ethernet driver oltr ISA/PCI Olicom Token Ring device driver plip PPBUS printer port Internet Protocol driver ppp TTY point to point protocol network interface ray PCCARD Raytheon Raylink/Webgear Aviator PCCard driver rue USB RealTek RTL8150 USB to Fast Ethernet controller driver rum USB Ralink Technology USB IEEE 802.11a/b/g wireless network device sbni ISA/PCI Granch SBNI12 leased line modem driver sbsh PCI Granch SBNI16 SHDSL modem device driver sl TTY slip network interface snc ISA/PCCARD National Semiconductor DP8393X SONIC Ethernet adapter driver sr ISA/PCI synchronous RISCom/N2 / WANic 400/405 device driver udav USB Davicom DM9601 USB Ethernet driver ural USB Ralink Technology RT2500USB IEEE 802.11 driver xe PCCARD Xircom PCMCIA Ethernet device driver zyd USB ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device In some cases, the requirement for Giant is a property of a subsystem the driver depends on as the driver itself; for example, the tty subsystem for SLIP and PPP, and the USB subsystem for a number of USB ethernet and wireless drivers. With most of a year before to go on the proposed schedule, my hope is that we will have lots of time to address these issues, but wanted to get a roadmap out from a network protocol stack architecture perspective so that device driver and subsystem authors could have a schedule in mind. FYI, the following drivers also reference IFF_NEEDSGIANT, but only in order to provide their own conditional MPSAFEty, which can be removed without affecting device driver functionality (I believe): Name Bus Man page description --- --- -------------------- ce PCI driver for synchronous Cronyx Tau-PCI/32 WAN adapters cp PCI driver for synchronous Cronyx Tau-PCI WAN adapters ctau ISA driver for synchronous Cronyx Tau WAN adapters cx ISA driver for synchronous/asynchronous Cronyx Sigma WAN adapters Developers and users of the above drivers are heavily encouraged to update the drivers to remove dependence on Giant, and/or make other contingency plans. Robert N M Watson Computer Laboratory University of Cambridge _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sat May 24 13:27:41 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC11B1065676 for ; Sat, 24 May 2008 13:27:41 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0EC048FC12 for ; Sat, 24 May 2008 13:27:40 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id ESM20335 for ; Sat, 24 May 2008 15:14:35 +0200 Message-ID: <483814C9.10301@skytek.it> Date: Sat, 24 May 2008 15:14:49 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: lagg interfaces on 6.3-Stable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 13:27:41 -0000 Hello, i have configured lagg interface on two Broacom (bce0 bce1). I have tried with laggproto lacp (supported by the Nortel switch), with fce and failover, but they all shows the same symptom: Everything works fine until i unplug the cable of the first interface (bce0), it will show status: no carrier even on lagg0 interface, while bce0 shows no carrier (correct) and bce1 is active. Any ideas? Thanks! Daniel -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-net@FreeBSD.ORG Sat May 24 15:39:52 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2D6C106566B; Sat, 24 May 2008 15:39:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CBC0F8FC1F; Sat, 24 May 2008 15:39:52 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4OFdqfG002230; Sat, 24 May 2008 15:39:52 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4OFdqbD002226; Sat, 24 May 2008 15:39:52 GMT (envelope-from linimon) Date: Sat, 24 May 2008 15:39:52 GMT Message-Id: <200805241539.m4OFdqbD002226@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/123950: [tcp] TH_RST packet sended if received out-of-order data (ACK) in SYN_RECEIVED state X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 15:39:53 -0000 Old Synopsis: TH_RST packet sended if received out-of-order data (ACK) in SYN_RECEIVED state New Synopsis: [tcp] TH_RST packet sended if received out-of-order data (ACK) in SYN_RECEIVED state Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 24 15:39:30 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123950 From owner-freebsd-net@FreeBSD.ORG Sat May 24 15:49:28 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D6F8106566C; Sat, 24 May 2008 15:49:28 +0000 (UTC) (envelope-from cokane@FreeBSD.org) Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by mx1.freebsd.org (Postfix) with ESMTP id 030CA8FC27; Sat, 24 May 2008 15:49:27 +0000 (UTC) (envelope-from cokane@FreeBSD.org) Received: from mail.cokane.org ([71.168.73.33]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K1D00CNTNOMQ3U5@vms173003.mailsrvcs.net>; Sat, 24 May 2008 09:45:59 -0500 (CDT) Received: by mail.cokane.org (Postfix, from userid 103) id A1CA51DB2F9; Sat, 24 May 2008 10:48:49 -0400 (EDT) Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cokane.org (Postfix) with ESMTP id 193921DB2F9; Sat, 24 May 2008 10:48:42 -0400 (EDT) Date: Sat, 24 May 2008 10:48:18 -0400 From: Coleman Kane In-reply-to: <20080524111715.T64552@fledge.watson.org> To: Robert Watson Message-id: <1211640498.1510.8.camel@localhost> Organization: FreeBSD Project MIME-version: 1.0 X-Mailer: Evolution 2.22.1.1 FreeBSD GNOME Team Port Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-WsmYbFHJm0XxVixg4dwD" X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia References: <20080524111715.T64552@fledge.watson.org> X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8-gr1 X-Spam-Level: Cc: arch@FreeBSD.org, current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 15:49:28 -0000 --=-WsmYbFHJm0XxVixg4dwD Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2008-05-24 at 11:20 +0100, Robert Watson wrote: > Dear all: >=20 > Just as a reminder, we've just about reached the one month date before=20 > IFF_NEEDSGIANT drivers are disabled in the build. You can find a descrip= tion=20 > of the general problem and list of specific drivers below. >=20 > As USB work is on-going, I will *not* disable the USB drivers at this tim= e,=20 > but all other drivers in the list below will be disabled on 26 June. The= y=20 > will remain in the tree, easily accessible for patch distribution and=20 > re-enabling, until October, when any remaining non-MPSAFE drivers will be= =20 > deleted in 8.x. FreeBSD 8.0 will not ship with compatibility shims to su= pport=20 > non-MPSAFE network device drivers. >=20 > Robert N M Watson > Computer Laboratory > University of Cambridge >=20 > ---------- Forwarded message ---------- > Date: Sun, 3 Feb 2008 20:59:05 +0000 (GMT) > From: Robert Watson > To: arch@FreeBSD.org > Subject: 8.0 network stack MPsafety goals (fwd) >=20 >=20 > Only a few days after predicted, this is a reminder that IFF_NEEDSGIANT n= etwork=20 > drivers are going to stop working in the forseeable future. Please revie= w the=20 > attached driver list, and if you depend on or care about a Giant-dependen= t=20 > device driver, take action to make sure it doesn't remain on the list in = a=20 > month's time! >=20 > (As far as I'm aware, the list has not changed since my December posting.= ) >=20 > Robert N M Watson > Computer Laboratory > University of Cambridge >=20 > ---------- Forwarded message ---------- > Date: Mon, 24 Dec 2007 10:43:28 +0000 (GMT) > From: Robert Watson > To: arch@FreeBSD.org > Subject: 8.0 network stack MPsafety goals >=20 >=20 > Dear all: >=20 > With the 7.0 release around the corner, many developers are starting to t= hink=20 > about (and in quite a few cases, work on) their goals for 8.0. One of ou= r=20 > on-going kernel projects has been the elimination of the Giant lock, and = that=20 > project has transformed into one of optimizating behavior on increasing n= umbers=20 > of processors. >=20 > In 7.0, despite the noteworth accomplishment of eliminating debug.mpsasfe= net=20 > and conditional network stack Gian acquisition, we were unable to fully=20 > eliminate the IFF_NEEDSGIANT flag, which controls the conditional acquisi= tion=20 > of the Giant lock around non-MPSAFE network device drivers. Primarily th= ese=20 > drivers are aging ISA network device drivers, although there are some=20 > exceptions, such as the USB stack. >=20 > This e-mail proposes the elimination of the IFF_NEEDSGIANT flag and assoc= iated=20 > infrastructure in FreeBSD 8.0, meaning that all network device drivers mu= st be=20 > able to operate without the Giant lock (largely the case already). Remai= ning=20 > drivers using the IFF_NEEDSGIANT flag must either be updated, or less ide= ally,=20 > removed. I propose the following schedule: >=20 > Date Goals > ---- ----- > 26 Dec 2007 Post proposed schedule for flag and infrastructure removal > Post affected driver list >=20 > 26 Jan 2008 Repost proposed schedule for flag and infrastructure removal > Post updated affected driver list >=20 > 26 Feb 2008 Adjust boot-time printf for affect drivers to generate a loud > warning. > Post updated affected driver list >=20 > 26 May 2008 Post HEADS UP of impending driver disabling > Post updated affected driver list >=20 > 26 Jun 2008 Disable build of all drivers requiring IFF_NEEDSGIANT > Post updated affected driver list >=20 > 26 Sep 2008 Post HEADS up of impending driver removal > Post updated affected driver list >=20 > 26 Oct 2008 Delete source of all drivers requiring IFF_NEEDSGIANT > Remove flag and infrastructure >=20 > Here is a list of potentially affected drivers: >=20 > Name Bus Man page description > --- --- -------------------- > ar ISA/PCI synchronous Digi/Arnet device driver > arl ISA Aironet Arlan 655 wireless network adapter driver > awi PCCARD AMD PCnetMobile IEEE 802.11 PCMCIA wireless network > driver > axe USB ASIX Electronics AX88172 USB Ethernet driver > cdce USB USB Communication Device Class Ethernet driver > cnw PCCARD Netwave AirSurfer wireless network driver > cs ISA/PCCARD Ethernet device driver > cue USB CATC USB-EL1210A USB Ethernet driver > ex ISA/PCCARD Ethernet device driver for the Intel EtherExpress > Pro/10 and Pro/10+ > fe CBUS/ISA/PCCARD Fujitsu MB86960A/MB86965A based Ethernet adapters > ic I2C I2C bus system > ie ISA Ethernet device driver > kue USB Kawasaki LSI KL5KUSB101B USB Ethernet driver > oltr ISA/PCI Olicom Token Ring device driver > plip PPBUS printer port Internet Protocol driver > ppp TTY point to point protocol network interface > ray PCCARD Raytheon Raylink/Webgear Aviator PCCard driver > rue USB RealTek RTL8150 USB to Fast Ethernet controller driver > rum USB Ralink Technology USB IEEE 802.11a/b/g wireless > network device > sbni ISA/PCI Granch SBNI12 leased line modem driver > sbsh PCI Granch SBNI16 SHDSL modem device driver > sl TTY slip network interface > snc ISA/PCCARD National Semiconductor DP8393X SONIC Ethernet adapter > driver > sr ISA/PCI synchronous RISCom/N2 / WANic 400/405 device driver > udav USB Davicom DM9601 USB Ethernet driver > ural USB Ralink Technology RT2500USB IEEE 802.11 driver > xe PCCARD Xircom PCMCIA Ethernet device driver > zyd USB ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless > network device >=20 > In some cases, the requirement for Giant is a property of a subsystem the= =20 > driver depends on as the driver itself; for example, the tty subsystem fo= r SLIP=20 > and PPP, and the USB subsystem for a number of USB ethernet and wireless=20 > drivers. With most of a year before to go on the proposed schedule, my h= ope is=20 > that we will have lots of time to address these issues, but wanted to get= a=20 > roadmap out from a network protocol stack architecture perspective so tha= t=20 > device driver and subsystem authors could have a schedule in mind. >=20 > FYI, the following drivers also reference IFF_NEEDSGIANT, but only in ord= er to=20 > provide their own conditional MPSAFEty, which can be removed without affe= cting=20 > device driver functionality (I believe): >=20 > Name Bus Man page description > --- --- -------------------- > ce PCI driver for synchronous Cronyx Tau-PCI/32 WAN adapters > cp PCI driver for synchronous Cronyx Tau-PCI WAN adapters > ctau ISA driver for synchronous Cronyx Tau WAN adapters > cx ISA driver for synchronous/asynchronous Cronyx Sigma WAN > adapters >=20 > Developers and users of the above drivers are heavily encouraged to updat= e the=20 > drivers to remove dependence on Giant, and/or make other contingency plan= s. >=20 > Robert N M Watson > Computer Laboratory > University of Cambridge I've created a quick table of these at the following location: http://wiki.freebsd.org/NetworkNeedsGiant Please everyone feel free to fill in the blanks. I'll try to do it as well as time permits. --=20 Coleman Kane --=-WsmYbFHJm0XxVixg4dwD Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkg4KqwACgkQcMSxQcXat5cm3ACdFy/ZZLIbqAbfijtLjUtyPHd5 LqwAn1dzu8Jra/MzMnjWibA7G3z6YIrs =u5Qw -----END PGP SIGNATURE----- --=-WsmYbFHJm0XxVixg4dwD-- From owner-freebsd-net@FreeBSD.ORG Sat May 24 15:56:21 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D401065688; Sat, 24 May 2008 15:56:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3C78FC12; Sat, 24 May 2008 15:56:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D287646B23; Sat, 24 May 2008 11:56:20 -0400 (EDT) Date: Sat, 24 May 2008 16:56:20 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Coleman Kane In-Reply-To: <1211640498.1510.8.camel@localhost> Message-ID: <20080524165519.K9809@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> <1211640498.1510.8.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org, current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 15:56:22 -0000 On Sat, 24 May 2008, Coleman Kane wrote: > I've created a quick table of these at the following location: > http://wiki.freebsd.org/NetworkNeedsGiant > > Please everyone feel free to fill in the blanks. I'll try to do it as well > as time permits. FWIW, I suspect fixing things like SLIP and kernel PPP are fairly trivial once tty locking is in place -- a per-softc mutex and a bit of locking in the obvious spots would likely do it without too much trouble. In some paths, it might be necessary to inject data via the netisr, if that's not already being done (probably is) to avoid input/output lock order issues. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Sat May 24 16:15:35 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E86301065677 for ; Sat, 24 May 2008 16:15:34 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id A86658FC12 for ; Sat, 24 May 2008 16:15:34 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m4OGFXX8051806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 May 2008 09:15:34 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48383F25.2020309@freebsd.org> Date: Sat, 24 May 2008 09:15:33 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: mutex@unixtech.info References: <52090.74.56.88.177.1211525413.squirrel@webmail.unixtech.info> In-Reply-To: <52090.74.56.88.177.1211525413.squirrel@webmail.unixtech.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-net@freebsd.org Subject: Re: Atheros 5212 network issues. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2008 16:15:35 -0000 mutex@unixtech.info wrote: > Hello! > I am running FreeBSD 7.0 stable. I am having speed issues that I was > not experiencing before when I was running 6.3 stable. > > My wireless connection is now unstable and not as much consistent as it > was before. The wired connection is as usual ~7000kb/up and 800kb/down. > > Each test (~20 per day during 5 days) I did was on a 10 second interval, > speed is fluctuating from ~80kb to ~4000kb down and ~80kb to ~300kb up and > some tests return both download and upload to be very low. > > Also, one test can return 300kb down and 80kb up when next one 10 seconds > later returns 80kb down and 300kb up. > > Latency is fluctuating as well. > > I tried to use another channel, swap disk and wireless card to another > machine, cvsup and upgrade again. > > I didn't changed network settings, firewall rules, and my hostapd config. > > Here are some more informations on my hardware: > > FreeBSD 7.0-STABLE #0: Mon May 19 23:10:53 EDT 2008 > mutex@xxxxxxx:/usr/obj/usr/src/sys/MUTEX > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Celeron(R) CPU 1.70GHz (1716.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf13 Stepping = 3 > Features=0x3febfbff > real memory = 805240832 (767 MB) > avail memory = 774049792 (738 MB) > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard > wlan: mac acl policy registered > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > cpu0: on acpi0 > p4tcc0: on cpu0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port 0xcf8-0xcff,0x4000-0x40bf on acpi0 > pci0: on pcib0 > agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: mem > 0xe0000000-0xe0ffffff,0xd8000000-0xdfffffff irq 16 at device 0.0 on pci1 > uhci0: port 0xd800-0xd81f irq > 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f irq > 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xd400-0xd41f irq > 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem > 0xe4000000-0xe40003ff irq 23 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > fxp0: port 0xc000-0xc03f mem > 0xe3050000-0xe3050fff,0xe3020000-0xe303ffff irq 18 at device 0.0 on pci2 > miibus0: on fxp0 > inphy0: PHY 1 on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:02:b3:b6:af:59 > fxp0: [ITHREAD] > ath0: mem 0xe3040000-0xe304ffff irq 21 at device 1.0 on pci2 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:14:a5:0d:c0:91 > ath0: mac 10.5 phy 6.1 radio 6.3 > fxp1: port 0xc400-0xc43f mem > 0xe3052000-0xe3052fff,0xe3000000-0xe301ffff irq 22 at device 2.0 on pci2 > miibus1: on fxp1 > inphy1: PHY 1 on miibus1 > inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp1: Ethernet address: 00:02:b3:b6:af:09 > fxp1: [ITHREAD] > vr0: port 0xc800-0xc8ff mem > 0xe3051000-0xe30510ff irq 16 at device 3.0 on pci2 > vr0: Quirks: 0x0 > vr0: Revision: 0x43 > miibus2: on vr0 > ukphy0: PHY 8 on miibus2 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vr0: Ethernet address: 00:50:ba:18:ff:5f > vr0: [ITHREAD] > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > pci0: at device 31.3 (no driver attached) > pci0: at device 31.5 (no driver attached) > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FILTER] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > pmtimer0 on isa0 > orm0: at iomem 0xc0000-0xcc7ff pnpid ORM0000 on isa0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "TSC" frequency 1716911056 Hz quality 800 > Timecounters tick every 1.000 msec > ad1: 19073MB at ata0-slave UDMA100 > acd0: CDROM at ata1-master PIO4 > Trying to mount root from ufs:/dev/ad1s1a > > pciconf -lv | grep ath > ath0@pci0:2:1:0: class=0x020000 card=0x000c17f9 chip=0x001b168c > rev=0x01 hdr=0x00 > > athstats > 36879 data frames received > 50372 data frames transmit > 135 tx frames with an alternate rate > 3508 long on-chip tx retries > 286 tx failed 'cuz too many retries > 18M current transmit rate > 1496 tx management frames > 949 tx frames discarded prior to association > 7427 tx frames with no ack marked > 42411 tx frames with short preamble > 76570 rx failed 'cuz of bad CRC > 1980968 rx failed 'cuz of PHY err > 1762216 OFDM timing > 3 OFDM restart > 218713 CCK timing > 36 CCK restart > 117021 beacons transmitted > 420 periodic calibrations > 55 rssi of last ack > 29 avg recv rssi > -96 rx noise floor > 164 switched default/rx antenna > Antenna profile: > [1] tx 25569 rx 36157 > [2] tx 24598 rx 36925 > > ifconfig: > ath0: flags=8843 metric 0 mtu 2290 > ether 00:14:a5:0d:c0:91 > inet 10.0.3.1 netmask 0xffffff00 broadcast 10.0.3.255 > media: IEEE 802.11 Wireless Ethernet autoselect > (autoselect ) > status: associated > ssid mutex channel 1 (2412 Mhz 11g) bssid 00:14:a5:0d:c0:91 > authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit TKIP 3:128-bit > txpower 31.5 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 > roam:rssi11g 7 roam:rate11g 5 protmode CTS burst dtimperiod 1 > > sysctl: > net.wlan.0.%parent: ath0 > debug.disablefullpath: 0 > hw.ath.hal.swba_backoff: 0 > hw.ath.hal.sw_brt: 10 > hw.ath.hal.dma_brt: 2 > hw.ath.hal.version: 0.9.20.3 > hw.ath.txbuf: 200 > hw.ath.rxbuf: 40 > hw.ath.regdomain: 0 > hw.ath.countrycode: 0 > hw.ath.xchanmode: 1 > hw.ath.outdoor: 1 > hw.ath.calibrate: 30 > user.cs_path: /usr/bin:/bin:/usr/sbin:/sbin: > dev.npx.0.%desc: math processor > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=1 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x001b subvendor=0x17f9 > subdevice=0x000c cl > ass=0x020000 > dev.ath.0.%parent: pci2 > dev.ath.0.smoothing_rate: 95 > dev.ath.0.sample_rate: 10 > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 16 > dev.ath.0.slottime: 9 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 2 > dev.ath.0.diversity: 0 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.tpc: 0 > dev.ath.0.tpack: 63 > dev.ath.0.tpcts: 63 > dev.ath.0.fftxqmin: 2 > dev.ath.0.fftxqmax: 50 > dev.ath.0.monpass: 24 > > /etc/sysctl.conf *I didn't changed any other sysctl option* > net.inet.ip.forwarding=1 > > Lines added to Generic kernel: > > # PF > device pf > device pflog > device pfsync > > # ALTQ > options ALTQ > options ALTQ_CBQ # Class Bases Queuing (CBQ) > options ALTQ_RED # Random Early Detection (RED) > options ALTQ_RIO # RED In/Out > options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) > options ALTQ_PRIQ # Priority Queuing (PRIQ) > options ALTQ_NOPCC # Required for SMP build > > > Please help me troubleshoot and resolve this issue. > > Simplify your configuration. First remove ALTQ and any packet processing in the tx/rx paths (e.g. pf). If that doesn't resolve the issues you are seeing try to isolate the problem to rx or tx by running unidirectional tests. Finally, if this is related to tx rate control then fix the tx rate to eliminate that variable. If you cannot resolve the issue please file a PR. Be sure to provide sufficient information for someone to exactly duplicate your setup. Sam From owner-freebsd-net@FreeBSD.ORG Sat May 24 18:14:37 2008 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A9F1106566B; Sat, 24 May 2008 18:14:37 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2A9848FC13; Sat, 24 May 2008 18:14:36 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2A8EE46B2C; Sat, 24 May 2008 14:14:36 -0400 (EDT) Date: Sat, 24 May 2008 19:14:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Coleman Kane In-Reply-To: <1211640498.1510.8.camel@localhost> Message-ID: <20080524191405.N9809@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> <1211640498.1510.8.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org, current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 18:14:37 -0000 On Sat, 24 May 2008, Coleman Kane wrote: > I've created a quick table of these at the following location: > http://wiki.freebsd.org/NetworkNeedsGiant > > Please everyone feel free to fill in the blanks. I'll try to do it as well > as time permits. You might also want to cross-link with the SMPTODO page. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Sat May 24 19:52:30 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A671F106567C; Sat, 24 May 2008 19:52:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 93EA88FC14; Sat, 24 May 2008 19:52:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4OJqU4C026745; Sat, 24 May 2008 19:52:30 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4OJqUg1026741; Sat, 24 May 2008 19:52:30 GMT (envelope-from linimon) Date: Sat, 24 May 2008 19:52:30 GMT Message-Id: <200805241952.m4OJqUg1026741@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/123961: [vr] [patch] Allow vr interface to handle vlans X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 May 2008 19:52:30 -0000 Old Synopsis: Allow vr interface to handle vlans New Synopsis: [vr] [patch] Allow vr interface to handle vlans Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 24 19:52:05 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123961 From owner-freebsd-net@FreeBSD.ORG Sat May 24 22:40:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E9A010656AB for ; Sat, 24 May 2008 22:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6088FC0A for ; Sat, 24 May 2008 22:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4OMe3Qw042309 for ; Sat, 24 May 2008 22:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4OMe36t042308; Sat, 24 May 2008 22:40:03 GMT (envelope-from gnats) Date: Sat, 24 May 2008 22:40:03 GMT Message-Id: <200805242240.m4OMe36t042308@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Jonathan Crook Cc: Subject: Re: kern/120966: [rum] kernel panic with if_rum and WPA encryption X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jonathan Crook List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2008 22:40:03 -0000 The following reply was made to PR kern/120966; it has been noted by GNATS. From: Jonathan Crook To: bug-followup@FreeBSD.org, oliver@akephalos.de Cc: Subject: Re: kern/120966: [rum] kernel panic with if_rum and WPA encryption Date: Sat, 24 May 2008 23:05:12 +0100 I have encountered the same problem. Using a network device with an rt73 chipset (thus using the rum driver), and with WPA, I get a kernel panic within minutes. I have not yet tested the device without WPA. Unlike Oliver, I have an Intel ICH7 chipset. Thanks, Jonny.