From owner-freebsd-net@FreeBSD.ORG Sun Mar 8 11:01:00 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87673A97 for ; Sun, 8 Mar 2015 11:01:00 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BCBFE21 for ; Sun, 8 Mar 2015 11:01:00 +0000 (UTC) Received: by igbhn18 with SMTP id hn18so14061924igb.2 for ; Sun, 08 Mar 2015 04:00:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=date:from:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=7wkIfDoBNxSjytJ6g6m4VicQ0rK1VWN3hCD/mvmhiZM=; b=X5Ufeg4ormRtxrF+TDxERD+gfYYoT6pdtfZ7YTCeHfnxHbCAZbIj8Pvr5FaqhXz8Yc 0Mybn9xBumQx/ot76gT9E3j6ccT39doxxQ2kqmDXwx9RNU0+Vfn7iyLALlL4fihLRTS4 7HOhKA7MpnRUoNCYOMC+qLa0iPg7nkiVhMmZM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=7wkIfDoBNxSjytJ6g6m4VicQ0rK1VWN3hCD/mvmhiZM=; b=PBBj4xm5I06AH5Cf05Nq3EInHjaDQURHXFlspGBfP6nSS6Oa/J1lK10R1QP4TpMUWC jhynoeBUhXCxrr60/nzzkDXzudG1K5p14GbIlqNUQdVy3B3Gof2oGscqFBICgCUpKib+ tDAXYf1VNjsXYu1BFjStt7oajthy5i5hlRHT8DG5oshQzkXz6chdtAEGK3DPmFYqeTj7 FwqwCLY1vADl+kGdERbNfsqycGPayOAZF5OLqZpeXVVkWTz5CFhAFcJrWw1Sfu+KyHkF yuoYjOiKw1nUESbPaewgpj3vF6eqcKhzfgmcZr3wJSVRmSw41PV2bGyCLKsyIVvF0r50 Li6Q== X-Gm-Message-State: ALoCoQk5M5cHHcCR+lP/L22aoBbUXoPL3CXH7clXWyxhMtYJKGWfWv8gPl+vk6JC3pm45hGOFK2x X-Received: by 10.107.163.65 with SMTP id m62mr3844931ioe.40.1425812459006; Sun, 08 Mar 2015 04:00:59 -0700 (PDT) Received: from rsbsd.rsb ([31.200.10.254]) by mx.google.com with ESMTPSA id 192sm10341448ioo.38.2015.03.08.04.00.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Mar 2015 04:00:58 -0700 (PDT) Date: Sun, 8 Mar 2015 12:42:32 +0200 From: Beeblebrox Cc: "freebsd-net@freebsd.org" Subject: Re: tcpdump filter not ignoring jail subnet Message-ID: <20150308124232.1c3e453d@rsbsd.rsb> In-Reply-To: <20150306090919.0d221096@rsbsd.rsb> References: <20150305202050.24042973@rsbsd.rsb> <20150306090919.0d221096@rsbsd.rsb> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Mar 2015 11:01:00 -0000 I got out of my logic-loop and solved my filter problem. Thanks everyone for thier input. ((src net not 192.168.1.0/24 and host not 192.168.2.97 and not ip6) or host mybsd) and not port (imap or imaps or 6667) Below syntax is not accepted by tcpdump, btw: src not (net 192.168.1.0/24 and host 192.1-----) tcpdump does not seem to accept other keyword between "not" and the variabl= e. Regards. From owner-freebsd-net@FreeBSD.ORG Sun Mar 8 15:13:32 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E90C337 for ; Sun, 8 Mar 2015 15:13:32 +0000 (UTC) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C6ADBA25 for ; Sun, 8 Mar 2015 15:13:31 +0000 (UTC) Received: by wibhm9 with SMTP id hm9so14303118wib.2 for ; Sun, 08 Mar 2015 08:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Y2FIDV9n/zSRSEBRqq4xN1vuRPE14Y0BenikNy+kbH4=; b=GvSXl/z9TpRXBOB9lDSXMagARt/YHpBUaeOQRqVZhXVNK6flRgcvhAXK/lbqlfCC7V MeR8QqEJtD8IIGlI92JUXE3Qt+PbEv13oNAZeexS+PbOM4azHcq/qdmBYL9VY6EvEQv9 P1hgVzAnxLrGhUWbEcnXXtHEI43KhFxH+A3Pa9evEPA1NAswINuERxDSslf1tx6U61ut fXUxkpbkmOhgiKQkAcUnXj9+s/hG++DB763vIU5FjIHahBuzRg9DjKSk9MYknF8h4UAL /NEcdZj/NmWd/QvLmyX0ZqtqHyAIpPE1ksltl7QHwzRB7dnpDPtwxV1v55ya8PuFZQJu eUFw== X-Received: by 10.181.12.105 with SMTP id ep9mr95666263wid.85.1425827610054; Sun, 08 Mar 2015 08:13:30 -0700 (PDT) Received: from inverness.bcn.sia.es (213.Red-88-5-239.dynamicIP.rima-tde.net. [88.5.239.213]) by mx.google.com with ESMTPSA id ub1sm24122290wjc.43.2015.03.08.08.13.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Mar 2015 08:13:29 -0700 (PDT) Message-ID: <54FC6711.1050906@gmail.com> Date: Sun, 08 Mar 2015 15:13:21 +0000 From: "C.L. Martinez" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: rxcsum and txcsum needs to be disabled under KVM Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Mar 2015 15:13:32 -0000 Hi all, Yesterday, I have installed CentOS7 in my laptop to do some tests with LXC and KVM recent releases. One of these guests, it is a FreeBSD 10.1-RELEASE-p6 vm. One of the problems that I have detected is with network when virtio nics are used. This guest loose a lot of packets until I have disabled rx and tx in all virtual nics. Is this a FreeBSD bug or do I need to configure something under KVM? Thanks. From owner-freebsd-net@FreeBSD.ORG Sun Mar 8 15:17:49 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B00A73F3 for ; Sun, 8 Mar 2015 15:17:49 +0000 (UTC) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76407A47 for ; Sun, 8 Mar 2015 15:17:49 +0000 (UTC) Received: by iery20 with SMTP id y20so3736869ier.0 for ; Sun, 08 Mar 2015 08:17:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XZby+iayyuAAxV73oSKtWPZLg9jHvJ2iaKzpzYRaNDs=; b=Tqd9OjqLWDDRTbEuc/5ityR3Dsce5+4ULqtdBF/umhZrSD37v9DP3MFS2IK1y3iS0Z 0BHSCPF0x+Qb7IrNziowXbZJAy/CK5YXNdkHr0lYQLWbzxVZOHqHfMulOn5CzSfB5BwO KgKVzo+FWnEASRfMK9zwddNoXknArmBIJ8KVTLecEfXUqMx8cvoee4NHGf9p8oWcgB8Z Hl0N9pTvEChK7SgfDJ/tp1LYDjBIioSFg5ptLhuvFZg9li3BuQsIYX2gHkedM7aF75px WU4BY4foCirHKf3Yj20SohcVCCISa//lWVI6UmO6EsGt2ywexcsPQBgMPC/vkWBS5S02 MS7Q== MIME-Version: 1.0 X-Received: by 10.50.66.170 with SMTP id g10mr67032448igt.49.1425827868846; Sun, 08 Mar 2015 08:17:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Sun, 8 Mar 2015 08:17:48 -0700 (PDT) In-Reply-To: <54FC6711.1050906@gmail.com> References: <54FC6711.1050906@gmail.com> Date: Sun, 8 Mar 2015 08:17:48 -0700 X-Google-Sender-Auth: UW_p2YBo1PrhPJ-hN0IbAVxB4YQ Message-ID: Subject: Re: rxcsum and txcsum needs to be disabled under KVM From: Adrian Chadd To: "C.L. Martinez" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Mar 2015 15:17:49 -0000 Hi! Please file a bug with FreeBSD! it should do the right thing by default. Thanks! -a On 8 March 2015 at 08:13, C.L. Martinez wrote: > Hi all, > > Yesterday, I have installed CentOS7 in my laptop to do some tests with LXC > and KVM recent releases. > > One of these guests, it is a FreeBSD 10.1-RELEASE-p6 vm. One of the > problems that I have detected is with network when virtio nics are used. > This guest loose a lot of packets until I have disabled rx and tx in all > virtual nics. > > Is this a FreeBSD bug or do I need to configure something under KVM? > > Thanks. > _______________________________________________ > 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 Mar 9 00:13:11 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 448F0DB2 for ; Mon, 9 Mar 2015 00:13:11 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2ACE3BD1 for ; Mon, 9 Mar 2015 00:13:11 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t290DAjI020895 for ; Mon, 9 Mar 2015 00:13:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 122780] [lagg] tcpdump on lagg interface during high pps wedges netcode Date: Mon, 09 Mar 2015 00:13:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 00:13:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122780 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Feedback Timeout Status|In Progress |Closed -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 04:07:45 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 29BC917D; Mon, 9 Mar 2015 04:07:45 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bbn0102.outbound.protection.outlook.com [157.56.111.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0B407AA; Mon, 9 Mar 2015 04:07:44 +0000 (UTC) Received: from BY1PR0301MB0902.namprd03.prod.outlook.com (25.160.195.141) by BY1PR0301MB0901.namprd03.prod.outlook.com (25.160.195.140) with Microsoft SMTP Server (TLS) id 15.1.99.14; Mon, 9 Mar 2015 03:34:15 +0000 Received: from BY1PR0301MB0902.namprd03.prod.outlook.com ([25.160.195.141]) by BY1PR0301MB0902.namprd03.prod.outlook.com ([25.160.195.141]) with mapi id 15.01.0099.004; Mon, 9 Mar 2015 03:34:16 +0000 From: Wei Hu To: Adrian Chadd Subject: RE: Network interrupt and NAPI in FreeBSD? Thread-Topic: Network interrupt and NAPI in FreeBSD? Thread-Index: AdBXxrUZJSIVrvKZR/OD9Js74nJJKgAEkq2AADMFejAAAt2SAABZez3Q Date: Mon, 9 Mar 2015 03:34:15 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [167.220.232.8] authentication-results: freebsd.org; dkim=none (message not signed) header.d=none; x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0301MB0901; x-microsoft-antispam-prvs: x-forefront-antispam-report: BMV:0; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(13464003)(377454003)(33656002)(76176999)(50986999)(99286002)(54356999)(76576001)(93886004)(2950100001)(2900100001)(122556002)(86362001)(19580395003)(19580405001)(92566002)(87936001)(46102003)(2656002)(40100003)(77156002)(66066001)(110136001)(74316001)(102836002)(86612001)(62966003); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0301MB0901; H:BY1PR0301MB0902.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5001009); SRVR:BY1PR0301MB0901; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0301MB0901; x-forefront-prvs: 05102978A2 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: microsoft.onmicrosoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2015 03:34:15.7700 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0301MB0901 Cc: "freebsd-net@freebsd.org" , Luigi Rizzo X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 04:07:45 -0000 PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBhZHJpYW4uY2hhZGRAZ21haWwu Y29tIFttYWlsdG86YWRyaWFuLmNoYWRkQGdtYWlsLmNvbV0gT24gQmVoYWxmDQo+IE9mIEFkcmlh biBDaGFkZA0KPiBTZW50OiBTYXR1cmRheSwgTWFyY2ggNywgMjAxNSA0OjI3IFBNDQo+IFRvOiBX ZWkgSHUNCj4gQ2M6IEx1aWdpIFJpenpvOyBmcmVlYnNkLW5ldEBmcmVlYnNkLm9yZw0KPiBTdWJq ZWN0OiBSZTogTmV0d29yayBpbnRlcnJ1cHQgYW5kIE5BUEkgaW4gRnJlZUJTRD8NCj4gDQo+IEhp LA0KPiANCj4gV2VsbCwgaG0uIFdoYXQncyBnZW5lcmF0aW5nIHRoZSBpbnRlcnJ1cHRzPyBIb3cg bWFueSBpbnRlcnJ1cHRzL3NlY29uZA0KPiBhcmUgeW91IHRhbGtpbmcgYWJvdXQgaGVyZT8NCj4g DQo+IFBlb3BsZSBoYXZlIGFza2VkIGFib3V0IGEgTkFQSSBzdHlsZSBzb2x1dGlvbiBmb3IgRnJl ZUJTRCBmb3IgYSB3aGlsZSwgYnV0DQo+IGZvciBtb3N0IGZvbGsgdGhhdCBhcmUgdXNpbmcgb25l IHBoeXNpY2FsIGludGVyZmFjZSB0aGF0IGRvZXMgaW50ZXJydXB0DQo+IG1vZGVyYXRpb24vcmF0 ZS1saW1pdGluZywgaXQgdHVybnMgb3V0IHRvIG5vdCBiZSBhbGwgdGhhdCBiaWcgYSBiZW5lZml0 LiBGb3INCj4gYm94ZXMgdGhhdCBoYXZlcyBtdWx0aXBsZSBpbnRlcmZhY2VzLCBvciBmb3IgVk1z IHdob3NlIHNvZnR3YXJlIGludGVycnVwdA0KPiBwYXRoIGRvZXNuJ3QgaW1wbGVtZW50IGFueSBr aW5kIG9mIHRocmVzaG9sZHMgZm9yIGludGVycnVwdCBtb2RlcmF0aW9uLCBpdA0KPiBzdGlsbCBj YW4gYmUgYSBiZW5lZml0Lg0KPiANCj4gU28gbWF5YmUgdHJ5IGxvb2tpbmcgYXQgbWFraW5nIHlv dXIgZHJpdmVyIHN1cHBvcnQgUE9MTElORyBhbmQgc2VlIHdoYXQNCj4gaGFwcGVucy4NCj4gDQo+ IE1heWJlIHZpcnR1YWxpc2F0aW9uIHdpbGwgYmUgdGhlIHN0cmF3IHRoYXQgYnJlYWtzIHRoZSBO QVBJIGJhY2sgZm9yDQo+IEZyZWVCU0QuIDspDQo+IA0KDQpJIGhhdmVuJ3QgZ290IGNoYW5jZSB0 byBtZWFzdXJlIHRoZSBpbnRlcnJ1cHQvc2Vjb25kIHJhdGUuIFdoYXQgSSBoYXZlIHNlZW4gaXMg d2hlbiBydW5uaW5nDQp0aGUgc2FtZSBpcGVyZiB0ZXN0LCB0aGUgdkNQVSBoYW5kbGUgdGhlIG5l dHdvcmsgcXVldWUgaXMgb3ZlciA4MCUgYnVzeSBydW5uaW5nIGluIGludGVycnVwdA0KY29udGV4 dCBvbiBGcmVlQlNELCBjb21wYXJpbmcgdG8gYXJvdW5kIDE1JSBidXN5IGluIGludGVycnVwdCBj b250ZXh0IG9uIExpbnV4LiBUaGUgdGhyb3VnaHB1dA0KaXMgYXJvdW5kIDIuMCBHYnBzIHZzIDMu MCBHYnBzLg0KDQpJIGFtIHVzaW5nIGEgc2xpZ2h0bHkgbmV3IG5ldHZzYyBkcml2ZXIgd2l0aCBU U08gc3VwcG9ydC4gSXQgaGFzbid0IG5vdCBiZWVuIG9mZmljaWFsbHkgb3V0IHlldC4gDQoNCldl aQ0KDQo= From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 06:19:36 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9EED1B11 for ; Mon, 9 Mar 2015 06:19:36 +0000 (UTC) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6816E310 for ; Mon, 9 Mar 2015 06:19:36 +0000 (UTC) Received: by pdbfp1 with SMTP id fp1so55400100pdb.7 for ; Sun, 08 Mar 2015 23:19:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=nrcR63QqncDaQDrF72I0sIl6n8vDX0lPPRT7S9iB2GQ=; b=LCA2VzgPI/13KJ96fictxDpgYqT20G9zCazKBwOlQPiFULVGUbAZo5z+kdjYbaQZf7 nhW9X6ZtZqIOnPXRJDEzD8zNU1Q1kfZehne62Slq2PmjV0wTr0B2zVeLCfYGp//bRPaF QpKsehQQSch69KRUeilG9dEosi2JNfZa5rprExvt4t5vCYC9y4defxpRIl4EWiAUgQ5k mBUTZ4Oxu5Go/2+rEABmQ+oygMyYXP/IbrQ7uZefy5UeFakz+fSEvf+WLCTSQ6Tibq1d D5CmzKlKuS79KzYtBJFXZYaF0Qa46PNIfti3QxWRPwMwkHGvBY1pGsTk06RG3i78WOS6 i2lw== X-Received: by 10.66.233.74 with SMTP id tu10mr50061213pac.135.1425881975700; Sun, 08 Mar 2015 23:19:35 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id pu9sm3242282pdb.49.2015.03.08.23.19.31 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 08 Mar 2015 23:19:34 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 09 Mar 2015 15:19:26 +0900 Date: Mon, 9 Mar 2015 15:19:26 +0900 To: Matt Dooner Subject: Re: cpsw/atphy network drivers Message-ID: <20150309061926.GA975@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, matt@doonerconsulting.com X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 06:19:36 -0000 On Fri, Mar 06, 2015 at 12:45:22PM +0000, Matt Dooner wrote: > Hello, > > I am having some trouble configurating the network driver on a TI > T335x-based CoM system > (http://www.compulab.co.il/products/computer-on-modules/cm-t335/). It > uses the "the AM335x integrated Ethernet MAC coupled with the AR8033 > RGMII Ethernet PHY from Atheros". U-Boot is able to find the device as > expected: > > CM-T335w # mii device > MII devices: 'cpsw' > Current device: 'cpsw' > > CM-T335w # mdio list > cpsw: > 0 - AR8031/AR8033 <--> cpsw > > CM-T335w # dhcp > link up on port 0, speed 100, half duplex > BOOTP broadcast 1 > DHCP client bound to address 10.1.192.67 > CM-T335w # ping 8.8.8.8 > link up on port 0, speed 100, half duplex > Using cpsw device > host 8.8.8.8 is alive > [...] > root@beaglebone:~ # ifconfig > cpsw0: flags=8847 metric > 0 mtu 1500 > options=8000b > ether 1c:ba:8c:ed:40:99 > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > 09:58:57 cpsw_ifmedia_sts > 09:58:57 cpsw_ifmedia_sts > 09:58:57 cpsw_ifmedia_sts > media: Ethernet autoselect (100baseTX ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Given that you get a half-duplex link, I guess there is speed or duplex mismatch with link partner. Does link partner also agree on the established link speed/duplex? If this is not the case, you may be able to see alignment errors or CRC errors via H/W MAC statistics counters. Quick reading the code indicates that cpsw(4) exports sysctl stat nodes(dev.cpsw.%d.stats). If link partner also supports H/W MAC statistics counters you can consult the info on the link partner. If the issue is really speed/duplex mismatch issue, probably you can try one of the following. - If you have manual media configuration for cpsw(4), use auto. - If link partner uses fixed speed/duplex instead of auto, use the same media configuration on cpsw(4). - If neither helps, try unplugging the UTP cable and wait a couple of seconds then plug it again. It seems there is no miibus_statchg handler in cpsw(4) so I guess cpsw(4) may not be able to program some MAC parameters including duplex when established link is not that of the cpsw(4) assumes. So it would be best to manually set link parameters on both link parter and cpsw(4) to use the same link configuration(100Mbps, full-duplex). > status: active > nd6 options=29 > lo0: flags=8049 metric 0 mtu 16384 > options=600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > > When connected to another computer running Wireshark no frames are > recorded as having been transmitted over the interface. The cpsw > driver never reports receiving any packets, even when I use a tool > like Ostinato to craft frames addressed to the MAC of the NIC on the > board. > > The network interface works perfectly in Debian Linux: > Fixing the link state change handling as well as promiscuous mode handling seem to need more work. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 16:58:28 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52B41F6C for ; Mon, 9 Mar 2015 16:58:28 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 39592665 for ; Mon, 9 Mar 2015 16:58:28 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29GwSeP069374 for ; Mon, 9 Mar 2015 16:58:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197476] wb driver don't work for Compex RL100-ATX 10/100baseTX Date: Mon, 09 Mar 2015 16:58:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 16:58:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197476 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb@FreeBSD.org, | |marius@FreeBSD.org --- Comment #1 from John Baldwin --- I wonder if this is related to the MII generic bit-banging changes? Specifically revisions 213894, 221407, and 226995. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 17:03:32 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E3907236 for ; Mon, 9 Mar 2015 17:03:32 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA8F67E3 for ; Mon, 9 Mar 2015 17:03:32 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29H3Wxt009151 for ; Mon, 9 Mar 2015 17:03:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197265] [mii] patch to support rtl8211f ethernet phys Date: Mon, 09 Mar 2015 17:03:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 17:03:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb@FreeBSD.org, | |yongari@FreeBSD.org --- Comment #2 from John Baldwin --- Pyun, you seem to have done most of the non-tree-sweep changes to rgephy. Can you review this? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 17:05:21 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A69002EF for ; Mon, 9 Mar 2015 17:05:21 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8AB89804 for ; Mon, 9 Mar 2015 17:05:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29H5LZN009976 for ; Mon, 9 Mar 2015 17:05:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197168] bce driver failing on 10.1p5, no reason... Date: Mon, 09 Mar 2015 17:05:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 17:05:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197168 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb@FreeBSD.org --- Comment #1 from John Baldwin --- If you use ifconfig to down/up the interface post boot, does that "fix" it? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 17:10:15 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E4D14D0 for ; Mon, 9 Mar 2015 17:10:15 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9226881 for ; Mon, 9 Mar 2015 17:10:14 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29HAEuR013924 for ; Mon, 9 Mar 2015 17:10:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197076] Only One Port Of Dual Port EC2000S (RTL8111E, r8169) Detected Date: Mon, 09 Mar 2015 17:10:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 17:10:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197076 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb@FreeBSD.org --- Comment #2 from John Baldwin --- Please try a snapshot of HEAD. It should try to allocate a PCI bus number for your second device which is currently failing on 10.1. Note that if a HEAD snapshot doesn't work out of the box, please try setting 'hw.pci.clear_buses=1' in the loader before booting a HEAD kernel. (The relevant change to merge if this fixes it is r261790) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 18:30:30 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80D75A9 for ; Mon, 9 Mar 2015 18:30:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 674493BC for ; Mon, 9 Mar 2015 18:30:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29IUUDx062984 for ; Mon, 9 Mar 2015 18:30:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 194855] VLAN interface MTU does not change on changing the base interface MTU Date: Mon, 09 Mar 2015 18:30:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: john@jnielsen.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 18:30:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194855 John Nielsen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john@jnielsen.net --- Comment #1 from John Nielsen --- I don't think that VLAN MTU should change automatically. In the example given it does make sense to either give a warning or prevent the parent interface MTU from being reduced smaller than any of the VLAN MTU (or conversely increasing the VLAN MTU above that of the parent), but I don't think that increasing the MTU on the parent should have any effect on the VLAN interfaces' MTU. I have certainly had cases where I used different MTU settings for different VLANs on the same parent interface (but of course not higher than the parent). -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Mon Mar 9 18:48:24 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 18B88525 for ; Mon, 9 Mar 2015 18:48:24 +0000 (UTC) Received: from nm50-vm5.bullet.mail.ne1.yahoo.com (nm50-vm5.bullet.mail.ne1.yahoo.com [98.138.121.149]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D162679E for ; Mon, 9 Mar 2015 18:48:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s2048; t=1425926723; bh=a7qUoyhYPBLfjVWA3pAQuwG0sT+p3399KfFFl8EDduo=; h=Date:From:To:Subject:References:In-Reply-To:From:Subject; b=tyWMiMSS5JYHLIYbcFYI76KLSeq2l2VL1A2dcn20A4it7MBs9cE+20a/1zBAG8McV8pZOwINgJRvNir1jvk8EMwwlRupaqAljctQskGqPUQ0oRoJiGu21C4JBDEhFdtWhtI9s6h3jokuo/LOQvJ6psY9ti2yzs2mrKBlfAgo2KsSBSR0URAdGpszDFMiJ0HV/AwSLFddFNVbpugLVpoC/JfM+9arnyW+xUvbKAd5rDCdRO0//By+w/31tn3OLgSp+PjYchDeZVfcC0jNiTLd4abgBiuoSvn4jHwEUfoNcoZ3l/e60PtWyD7gbLeyAejLmduNCNU4DCqrkXVYzWbDuQ== Received: from [127.0.0.1] by nm50.bullet.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 18:45:23 -0000 Received: from [98.138.226.178] by nm50.bullet.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 18:42:23 -0000 Received: from [212.82.98.52] by tm13.bullet.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 18:42:23 -0000 Received: from [46.228.39.68] by tm5.bullet.mail.ir2.yahoo.com with NNFMP; 09 Mar 2015 18:42:22 -0000 Received: from [127.0.0.1] by smtp105.mail.ir2.yahoo.com with NNFMP; 09 Mar 2015 18:42:22 -0000 X-Yahoo-Newman-Id: 896027.5125.bm@smtp105.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-4 X-YMail-OSG: gaARFDEVM1mVLb_Nm2xayWUIyXvN0W81ttlKPt.X_iw81yu lP4pTdeWqF.Ac_m4dZhXYA4t3A7TjseEXw435x.LRvnEj8zA8jDwwy7OBFGH oYylx6.Jkp2kfOKKd1uLVSITnthXqHl6PmZ3UREVlKHmTPihrGQwmqGQdYdw SuadS6EUOaexLpFEwT5qTG86D1EuuukA6.pJ87UVmeM3kyDXKlbTDFfTpurd cYijfst_JsI7LzxCvbJ.ut.Z1h0r837CZbfRm6TUNbZPJqUOkvSjkoaZZOk4 a7_jRUMKwTxcMxQa.F0VpEw4X1x82oweZS1VMIFROaA10YhNA6_iJVeXbdff M6tVA4CwlAHzCN965H5Sq1pUuNBDfYMpwkxPxN25ztUbWhcO2tBtmaUbGeCU Z8.Z2sU3VtaiTjO2obJdOcbqoxXjMeQ2BiMJknm5W4TFvQO.MOkOG5cGyco. fyoJyoQomZLNAo.SzHJTEgDNlm0m5uebnOZWfPkL4kqxQ0mtkJf7TyFi_Jsu phB8U6DOmVgzB3X3uGoRHzXmkCQ-- X-Yahoo-SMTP: jZMnUUWswBBeJFVzzFDPPf5Hjv6RGVDA8l5fyw-- Message-ID: <54FDE98B.8030309@yahoo.fr> Date: Mon, 09 Mar 2015 19:42:19 +0100 From: mohamed chebbi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Looking for help with RSS IPv6 - need software hash code! References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 18:48:24 -0000 Hi adrian can you please feed the link to the RSS specification. Le 23/02/2015 21:38, Adrian Chadd a écrit : > Hi! > > The last annoyingish bit for IPv6 RSS support is a full software hash > routine to calculate an RSS hash based on the various fields in the > IPv6 header. I'm unfortunately out of spare cycles to try and finish > it so I'm asking for help. > > In order to support this in the kernel we need to not only know what > to do with the hardware RSS, but also have a fallover path to software > hashing if the NIC doesn't hash it for us, or doesn't hash it > correctly. For example, if we get IPv4/IPv6 fragments (which yes, are > a thing, don't tell me they're not), we need to reassemble the > fragments into a single frame, and then re-calculate the RSS hash on > the reassembled frame header to figure out where it would've gone. We > have to do this because the RSS hash value is also used as an index > into the PCBGROUP hash table array - so no matter whether packets in a > flow are fragmented or not, they're correctly serialised into the same > netisr queue and the PCB information for that flow is in the same > PCBGROUP array bucket. > > For doing "correct" RSS, we need to have support for hashing various > fields and this isn't just limited to 2-tuple / 4-tuple hashing. IPv6 > has a bunch of mobility header options and RSS has support for these > (the TCP_EX and UDP_EX fields.) > > I've done the software hashing path for IPv4, but I need someone to > help me do the IPv6 RSS hash calculation for all the variations - IPv6 > 2-tuple IPv6 TCP, IPv6 UDP, IPv6 TCP_EX (mobility), UDP_EX (mobility.) > The microsoft RSS specification is online and freely available; it has > all of these as examples. > > So, I'm asking for help. If you're able to help, please look at the > code in -HEAD in sys/netinet/in_rss.c and sys/netinet6/in6_rss.c. > You'll see what's missing. You don't need a NIC that has RSS enabled; > if you enable RSS and PCBGROUPS in the kernel (and bump up the number > of netisr queues; that still isn't auto-set at boot time) then you'll > see that traffic will get distributed by software hashing of the > packet headers. > > Thanks! > > > > > -adrian > _______________________________________________ > 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 Mar 9 19:06:49 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7132983 for ; Mon, 9 Mar 2015 19:06:49 +0000 (UTC) Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AFB899F for ; Mon, 9 Mar 2015 19:06:49 +0000 (UTC) Received: by iery20 with SMTP id y20so12913416ier.0 for ; Mon, 09 Mar 2015 12:06:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=1pamQ9sVp23F0VCCBymdDNImx6HRX2gJuqQjhI1tBl4=; b=KueNiYVcKfREs1sb0fHZD8RmbmRlKPyHJft9qnzbIzs+d1l2vCdyAKb/hKnLFZfCt+ uNjp6YFn2l71dpK4XCLNKHyy7JPyAtWOPGAZMsk7e6v99NXfvbHinnEU1lsqJMgdHyKe 42gQskvaM7C942vD4pglredlxcTHRHKdSWDPuPSf+kEvnlhzvx0G9+ywUuHEVFDL/Sk9 vweMY0Oz5Wf3qqEQJgnhZEmfEDvxO6VnQ4ykcD/Rvh6tt9GSW/I8zPv3eMD7G0eg/oNf MWN/S4Nkc2aB4aFe3ydpm4RsijIV+0CDCLEkiF5G7Hzkj+RTD0AnxkvyYDVGDRYFi5YB /qLg== MIME-Version: 1.0 X-Received: by 10.50.67.100 with SMTP id m4mr9878981igt.32.1425928008970; Mon, 09 Mar 2015 12:06:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Mon, 9 Mar 2015 12:06:48 -0700 (PDT) In-Reply-To: <54FDE98B.8030309@yahoo.fr> References: <54FDE98B.8030309@yahoo.fr> Date: Mon, 9 Mar 2015 12:06:48 -0700 X-Google-Sender-Auth: WK7_U2xqyhyKxZWsTCor4xsZdKI Message-ID: Subject: Re: Looking for help with RSS IPv6 - need software hash code! From: Adrian Chadd To: mohamed chebbi Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 19:06:50 -0000 https://msdn.microsoft.com/en-us/library/windows/hardware/ff567236(v=3Dvs.8= 5).aspx https://technet.microsoft.com/en-us/library/hh997036.aspx -a On 9 March 2015 at 11:42, mohamed chebbi wrote: > Hi adrian > > can you please feed the link to the RSS specification. > > Le 23/02/2015 21:38, Adrian Chadd a =C3=A9crit : >> >> Hi! >> >> The last annoyingish bit for IPv6 RSS support is a full software hash >> routine to calculate an RSS hash based on the various fields in the >> IPv6 header. I'm unfortunately out of spare cycles to try and finish >> it so I'm asking for help. >> >> In order to support this in the kernel we need to not only know what >> to do with the hardware RSS, but also have a fallover path to software >> hashing if the NIC doesn't hash it for us, or doesn't hash it >> correctly. For example, if we get IPv4/IPv6 fragments (which yes, are >> a thing, don't tell me they're not), we need to reassemble the >> fragments into a single frame, and then re-calculate the RSS hash on >> the reassembled frame header to figure out where it would've gone. We >> have to do this because the RSS hash value is also used as an index >> into the PCBGROUP hash table array - so no matter whether packets in a >> flow are fragmented or not, they're correctly serialised into the same >> netisr queue and the PCB information for that flow is in the same >> PCBGROUP array bucket. >> >> For doing "correct" RSS, we need to have support for hashing various >> fields and this isn't just limited to 2-tuple / 4-tuple hashing. IPv6 >> has a bunch of mobility header options and RSS has support for these >> (the TCP_EX and UDP_EX fields.) >> >> I've done the software hashing path for IPv4, but I need someone to >> help me do the IPv6 RSS hash calculation for all the variations - IPv6 >> 2-tuple IPv6 TCP, IPv6 UDP, IPv6 TCP_EX (mobility), UDP_EX (mobility.) >> The microsoft RSS specification is online and freely available; it has >> all of these as examples. >> >> So, I'm asking for help. If you're able to help, please look at the >> code in -HEAD in sys/netinet/in_rss.c and sys/netinet6/in6_rss.c. >> You'll see what's missing. You don't need a NIC that has RSS enabled; >> if you enable RSS and PCBGROUPS in the kernel (and bump up the number >> of netisr queues; that still isn't auto-set at boot time) then you'll >> see that traffic will get distributed by software hashing of the >> packet headers. >> >> Thanks! >> >> >> >> >> -adrian >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 01:48:18 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C064259E for ; Tue, 10 Mar 2015 01:48:18 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A61B1380 for ; Tue, 10 Mar 2015 01:48:18 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A1mIrX041231 for ; Tue, 10 Mar 2015 01:48:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 192847] ipfilter: seeing a lot of BAD packets in the logs while SSH-ing to the box Date: Tue, 10 Mar 2015 01:48:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:48:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192847 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Summary|ipfilter and bad packets |ipfilter: seeing a lot of | |BAD packets in the logs | |while SSH-ing to the box -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 01:50:03 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D2087DF for ; Tue, 10 Mar 2015 01:50:03 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12DF73BB for ; Tue, 10 Mar 2015 01:50:03 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A1o2kR041853 for ; Tue, 10 Mar 2015 01:50:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197536] ipfilter rule removal via command line deletes all rules added after as well Date: Tue, 10 Mar 2015 01:50:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:50:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197536 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |regression -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 01:58:05 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0147BE20 for ; Tue, 10 Mar 2015 01:58:04 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7BA6760 for ; Tue, 10 Mar 2015 01:58:04 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A1w4o1049428 for ; Tue, 10 Mar 2015 01:58:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197351] [ip6] panic when lagg(4) removes IPv6 addresses from member interface Date: Tue, 10 Mar 2015 01:58:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:58:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197351 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 02:11:49 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F2A3D131 for ; Tue, 10 Mar 2015 02:11:49 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D979A915 for ; Tue, 10 Mar 2015 02:11:49 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A2BnZx023382 for ; Tue, 10 Mar 2015 02:11:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 195924] IXGBE watchdog bug causes crash. Date: Tue, 10 Mar 2015 02:11:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 02:11:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195924 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 02:13:51 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F3982C0 for ; Tue, 10 Mar 2015 02:13:51 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85277959 for ; Tue, 10 Mar 2015 02:13:51 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A2DpqG059191 for ; Tue, 10 Mar 2015 02:13:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 195102] dummynet_send() may panic the kernel (bad switch -256) Date: Tue, 10 Mar 2015 02:13:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.4-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 02:13:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195102 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 02:14:44 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 029504A1 for ; Tue, 10 Mar 2015 02:14:44 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DCF6997D for ; Tue, 10 Mar 2015 02:14:43 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A2EhMv074302 for ; Tue, 10 Mar 2015 02:14:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 194111] [lor] iwn0_com_lock <-> if_addr_lock Date: Tue, 10 Mar 2015 02:14:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 02:14:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194111 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |regression -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 02:15:02 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FDA9578 for ; Tue, 10 Mar 2015 02:15:02 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1662D988 for ; Tue, 10 Mar 2015 02:15:02 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A2F1iL079584 for ; Tue, 10 Mar 2015 02:15:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 194110] [lor] if_lagg rmlock <-> re0 Date: Tue, 10 Mar 2015 02:15:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 02:15:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194110 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |regression -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 02:15:23 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E03A656 for ; Tue, 10 Mar 2015 02:15:23 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43884997 for ; Tue, 10 Mar 2015 02:15:23 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A2FNlY085769 for ; Tue, 10 Mar 2015 02:15:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 194109] [lor] if_lagg rmlock <-> if_addr_lock Date: Tue, 10 Mar 2015 02:15:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 02:15:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194109 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |regression -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 02:49:51 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9DC3113B for ; Tue, 10 Mar 2015 02:49:51 +0000 (UTC) Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71D3BCE0 for ; Tue, 10 Mar 2015 02:49:51 +0000 (UTC) Received: by pabrd3 with SMTP id rd3so53596402pab.5 for ; Mon, 09 Mar 2015 19:49:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=5u6FuHd/VLBKBw3nCBWQbnBGHjrvI0htZflTysaOIbQ=; b=PYQjuFJnoSD0WnyEaevzxWGFOTCO31a8B/rQa0apJMgw0t0Ov3e1WFLVlBbOyMz5x9 TOEAoLSbrgeQUdwj1VIfVNvDRIMvsnm+bBriDkC4aP1IybrN7dywPN6HSqQXTcJS6BPi v2/j7Pxfo46BmEwCh0xNe/nJeS21oqxo0Cm2ZjH3N2GWYlwK4zWopZ2tyAJAGaPZlYl8 wYS+cMirLIYnsbYcCLa+2q7U4p2eUlGFYi1CNlho9xz12VbUTYFRcM8NkyZG96N829Gq ZQV31FhyV0jRFASDojIaMkh7e8KxZCg4IeRhCCxWayBrBs3gFb94Lc3y5LwmjcMdvIP4 q/mQ== X-Gm-Message-State: ALoCoQlbvyUqYIurtwbYkhiNjU41IBC6IBzdY1d4uUUBeuAAK+1v6e5ttH1Zp+wX7uJZQAJ1RvSW X-Received: by 10.66.63.106 with SMTP id f10mr60759001pas.0.1425954416637; Mon, 09 Mar 2015 19:26:56 -0700 (PDT) Received: from [192.168.1.149] ([118.179.177.178]) by mx.google.com with ESMTPSA id y2sm21347331pdm.31.2015.03.09.19.26.54 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Mar 2015 19:26:56 -0700 (PDT) Message-ID: <54FE566F.5030607@winterei.se> Date: Tue, 10 Mar 2015 11:26:55 +0900 From: "Paul S." User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-net Subject: FreeBSD responding with wrong receiving interface IP Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 02:49:51 -0000 Hi, I've been deploying FreeBSD as customer edge routers for customers with sites that do not require high throughput (>1g/s). Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full routes via OpenBGPd and BIRD. I use next-hop self on all received routes. The FreeBSD boxes have static routes delegating the announced IP blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 10.0.0.1, and then that /24 is originated via BGP to both upstreams. Things in general work fine, but I've been receiving reports of 'weird traceroute results' from my customers. Examples of this would be, 1 some.random.isp (...) (...) 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 ms 0.284 ms 0.227 ms 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 1.966 ms 1.675 ms 1.852 ms 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 ms 15.917 ms 16.360 ms 5 customer-gw.syd.ALTER.net (...) (...) This traceroute seems to claim that the packet was received over the Verizon gateway, which in reality it was not -- it was received directly over the Telstra interface, but my outbound AS-PATH towards some.random.isp uses Verizon. So FreeBSD replies back with the Verizon address. Another person having the same issue (mostly, but on OpenBSD) can be found at http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-td90264.html I would love to know if there's a way to fix this, or if I've missed something, or if there's something wrong in the way I set it up. Thank you for taking the time to read. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 03:11:31 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81F92947 for ; Tue, 10 Mar 2015 03:11:31 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67F6611F for ; Tue, 10 Mar 2015 03:11:31 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A3BVtP068538 for ; Tue, 10 Mar 2015 03:11:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 85086] [ef] [patch] Locking fixes for ef(4) (+removes mem. leak) Date: Tue, 10 Mar 2015 03:11:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 7.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 03:11:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=85086 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wkoszek@FreeBSD.org |freebsd-net@FreeBSD.org --- Comment #2 from Mark Linimon --- Release to wild. To submitter: is this PR still valid? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 03:45:07 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B3CF7D98 for ; Tue, 10 Mar 2015 03:45:07 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 99D445ED for ; Tue, 10 Mar 2015 03:45:07 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A3j7cB035653 for ; Tue, 10 Mar 2015 03:45:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 194855] VLAN interface MTU does not change on changing the base interface MTU Date: Tue, 10 Mar 2015 03:45:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: praveenchoudary.gokina@emulex.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 03:45:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194855 --- Comment #2 from Praveen --- In Linux, when we change parent interface mtu, it will automatically update vlan mtu. We can either make it similar to Linux or handle as you said "give a warning or prevent the parent interface MTU from being reduced smaller than any of the VLAN MTU (or conversely increasing the VLAN MTU above that of the parent)". -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 09:52:18 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ABD1261A for ; Tue, 10 Mar 2015 09:52:18 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92203D72 for ; Tue, 10 Mar 2015 09:52:18 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A9qIg7076887 for ; Tue, 10 Mar 2015 09:52:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197265] [mii] patch to support rtl8211f ethernet phys Date: Tue, 10 Mar 2015 09:52:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yongari@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 09:52:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #3 from Pyun YongHyeon --- Created attachment 154127 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154127&action=edit Patch for RTL8211F PHY -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 09:52:57 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECDF66AC for ; Tue, 10 Mar 2015 09:52:57 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3690D7D for ; Tue, 10 Mar 2015 09:52:57 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A9qv1M077195 for ; Tue, 10 Mar 2015 09:52:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197265] [mii] patch to support rtl8211f ethernet phys Date: Tue, 10 Mar 2015 09:52:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yongari@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 09:52:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #4 from Pyun YongHyeon --- Thanks for the patch. I didn't test your patch on real H/W yet but patch looks good to me. To improve readability I've slightly reorganized your patch and regenerated it against HEAD. One difference against your diff is direct access of RGEPHY_F_MII_SSR register in MII_TICK handler. I wanted to remove RGEPHY_MII_BMSR, RGEPHY_MII_BMCR register accesses in the handler and rely on RGEPHY_F_MII_SSR or RGEPHY_MII_SSR register for non-re(4) drivers. Of course this assumes RGEPHY_F_MII_SSR reports correct link state in various timings. Would you try attached patch and let me know how it goes? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 13:16:37 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B543642F for ; Tue, 10 Mar 2015 13:16:37 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D3B69E7 for ; Tue, 10 Mar 2015 13:16:37 +0000 (UTC) Received: from [101.110.58.226] (port=65002 helo=[10.1.10.186]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1YVK1U-0007d1-4R; Tue, 10 Mar 2015 09:16:36 -0400 From: "George Neville-Neil" To: "Paul S." Subject: Re: FreeBSD responding with wrong receiving interface IP Date: Tue, 10 Mar 2015 22:16:24 +0900 Message-ID: In-Reply-To: <54FE566F.5030607@winterei.se> References: <54FE566F.5030607@winterei.se> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable X-Mailer: MailMate (1.9r5066) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com Cc: freebsd-net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 13:16:37 -0000 On 10 Mar 2015, at 11:26, Paul S. wrote: > Hi, > > I've been deploying FreeBSD as customer edge routers for customers = > with sites that do not require high throughput (>1g/s). > > Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full = > routes via OpenBGPd and BIRD. I use next-hop self on all received = > routes. > > The FreeBSD boxes have static routes delegating the announced IP = > blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 = > 10.0.0.1, and then that /24 is originated via BGP to both upstreams. > > Things in general work fine, but I've been receiving reports of 'weird = > traceroute results' from my customers. > > Examples of this would be, > > 1 some.random.isp (...) (...) > 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 = > ms 0.284 ms 0.227 ms > 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) = > 1.966 ms 1.675 ms 1.852 ms > 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 = > ms 15.917 ms 16.360 ms > 5 customer-gw.syd.ALTER.net (...) (...) > > This traceroute seems to claim that the packet was received over the = > Verizon gateway, which in reality it was not -- it was received = > directly over the Telstra interface, but my outbound AS-PATH towards = > some.random.isp uses Verizon. > > So FreeBSD replies back with the Verizon address. Another person = > having the same issue (mostly, but on OpenBSD) can be found at = > http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-= td90264.html > > I would love to know if there's a way to fix this, or if I've missed = > something, or if there's something wrong in the way I set it up. > > Thank you for taking the time to read. I wonder if we could see some routing tables? That might help. Best, George From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 14:40:53 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1D4DBE3 for ; Tue, 10 Mar 2015 14:40:53 +0000 (UTC) Received: from mail.as41113.net (mail.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id A78AF782 for ; Tue, 10 Mar 2015 14:40:53 +0000 (UTC) Received: from [172.21.87.41] (193.98.9.212.in-addr.arpa [212.9.98.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mail@m.jwh.me.uk) by mail.as41113.net (Postfix) with ESMTPSA id 3l1fH10NX6z1N22k for ; Tue, 10 Mar 2015 14:40:44 +0000 (GMT) Message-ID: <54FF0266.3080106@m.jwh.me.uk> Date: Tue, 10 Mar 2015 14:40:38 +0000 From: Joe Holden User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: FreeBSD responding with wrong receiving interface IP References: <54FE566F.5030607@winterei.se> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 14:40:54 -0000 On 10/03/2015 13:16, George Neville-Neil wrote: > On 10 Mar 2015, at 11:26, Paul S. wrote: > >> Hi, >> >> I've been deploying FreeBSD as customer edge routers for customers >> with sites that do not require high throughput (>1g/s). >> >> Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full >> routes via OpenBGPd and BIRD. I use next-hop self on all received routes. >> >> The FreeBSD boxes have static routes delegating the announced IP >> blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 >> 10.0.0.1, and then that /24 is originated via BGP to both upstreams. >> >> Things in general work fine, but I've been receiving reports of 'weird >> traceroute results' from my customers. >> >> Examples of this would be, >> >> 1 some.random.isp (...) (...) >> 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 >> ms 0.284 ms 0.227 ms >> 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) >> 1.966 ms 1.675 ms 1.852 ms >> 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 >> ms 15.917 ms 16.360 ms >> 5 customer-gw.syd.ALTER.net (...) (...) >> >> This traceroute seems to claim that the packet was received over the >> Verizon gateway, which in reality it was not -- it was received >> directly over the Telstra interface, but my outbound AS-PATH towards >> some.random.isp uses Verizon. >> >> So FreeBSD replies back with the Verizon address. Another person >> having the same issue (mostly, but on OpenBSD) can be found at >> http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-td90264.html >> >> >> I would love to know if there's a way to fix this, or if I've missed >> something, or if there's something wrong in the way I set it up. >> >> Thank you for taking the time to read. > > I wonder if we could see some routing tables? That might help. > > Best, > George sysctl net.inet.icmp.reply_from_interface=1 will probably do what you expect. From owner-freebsd-net@FreeBSD.ORG Tue Mar 10 14:53:15 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6748F1DE for ; Tue, 10 Mar 2015 14:53:15 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 387539A2 for ; Tue, 10 Mar 2015 14:53:15 +0000 (UTC) Received: by padet14 with SMTP id et14so2834638pad.0 for ; Tue, 10 Mar 2015 07:53:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5OB4DDNmSf39TeLEjQ3KBYEb54gmvK5bi5tNh8n4ZRU=; b=lhEa2QOzwFF7E+5M1JS3g36QENhLhHe4ea9LnbGRDgHEN28IlkY+sCqdD8LK+gKsqm IX/ToSOz0q0bNHwFXErAalaHeyoOz5ZXc7mzZtnbpymJXVoSz97BYrpJRQ3rAlAo7mLC ksF5YrdKvBpkyyfKPWNrc9OI3zkEOp7TufZuDFUNQPX7Bzwshx276pyxwDVwW3H0oScR MbDyhCHq3mxVBR6oftV0Lscko6D5bx5BLhlbzHBj3yWevbzKxBMQkhVSLwce45hI1Sw1 kBRi6Rn4cPEZy3PpcASLiypdwYanYIXD90r0rb7G7Vv+R80SYYpiGDx9pGq+fpoHmwV0 8o0A== X-Gm-Message-State: ALoCoQnJztL6aP1IQsrUxTgZs7+ycVfwiwMuw+gyD4H5+LkQ0oT6zvWXqT970O5yw8jCKVhZI0Wu X-Received: by 10.70.26.129 with SMTP id l1mr65774697pdg.163.1425999194138; Tue, 10 Mar 2015 07:53:14 -0700 (PDT) Received: from [192.168.1.149] ([118.179.177.178]) by mx.google.com with ESMTPSA id t5sm1402070pdn.58.2015.03.10.07.53.12 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Mar 2015 07:53:13 -0700 (PDT) Message-ID: <54FF0555.9070901@winterei.se> Date: Tue, 10 Mar 2015 23:53:09 +0900 From: "Paul S." User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: FreeBSD responding with wrong receiving interface IP References: <54FE566F.5030607@winterei.se> <54FF0266.3080106@m.jwh.me.uk> In-Reply-To: <54FF0266.3080106@m.jwh.me.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 14:53:15 -0000 Joe, That was it, thank you! I looked over net.inet.ip and ip6, icmp never crossed my mind. George, thank you as well. On 3/10/2015 åˆå¾Œ 11:40, Joe Holden wrote: > On 10/03/2015 13:16, George Neville-Neil wrote: >> On 10 Mar 2015, at 11:26, Paul S. wrote: >> >>> Hi, >>> >>> I've been deploying FreeBSD as customer edge routers for customers >>> with sites that do not require high throughput (>1g/s). >>> >>> Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full >>> routes via OpenBGPd and BIRD. I use next-hop self on all received >>> routes. >>> >>> The FreeBSD boxes have static routes delegating the announced IP >>> blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 >>> 10.0.0.1, and then that /24 is originated via BGP to both upstreams. >>> >>> Things in general work fine, but I've been receiving reports of 'weird >>> traceroute results' from my customers. >>> >>> Examples of this would be, >>> >>> 1 some.random.isp (...) (...) >>> 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 >>> ms 0.284 ms 0.227 ms >>> 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) >>> 1.966 ms 1.675 ms 1.852 ms >>> 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 >>> ms 15.917 ms 16.360 ms >>> 5 customer-gw.syd.ALTER.net (...) (...) >>> >>> This traceroute seems to claim that the packet was received over the >>> Verizon gateway, which in reality it was not -- it was received >>> directly over the Telstra interface, but my outbound AS-PATH towards >>> some.random.isp uses Verizon. >>> >>> So FreeBSD replies back with the Verizon address. Another person >>> having the same issue (mostly, but on OpenBSD) can be found at >>> http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-td90264.html >>> >>> >>> >>> I would love to know if there's a way to fix this, or if I've missed >>> something, or if there's something wrong in the way I set it up. >>> >>> Thank you for taking the time to read. >> >> I wonder if we could see some routing tables? That might help. >> >> Best, >> George > > sysctl net.inet.icmp.reply_from_interface=1 will probably do what you > expect. > > _______________________________________________ > 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 Mar 10 19:07:42 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D8554E9A for ; Tue, 10 Mar 2015 19:07:42 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE2C9E88 for ; Tue, 10 Mar 2015 19:07:42 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2AJ7gBY099889 for ; Tue, 10 Mar 2015 19:07:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197790] Intel em driver - random outgoing traffic sent through wrong interface Date: Tue, 10 Mar 2015 19:07:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 19:07:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197790 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erj@freebsd.org --- Comment #1 from Hiren Panchasara --- (In reply to vladimir.nikolic from comment #0) Everything works until "server restart" and then it switches to wrong default gateway? What do you mean by "server restart"? Also, "Reset helps" as you said. What do you mean by that? Reboot? or kldloading/unloading drivers? Adding Eric from Intel. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 01:25:16 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32642268 for ; Wed, 11 Mar 2015 01:25:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 18C7E21F for ; Wed, 11 Mar 2015 01:25:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2B1PFtq028803 for ; Wed, 11 Mar 2015 01:25:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197790] Intel em driver - random outgoing traffic sent through wrong interface Date: Wed, 11 Mar 2015 01:25:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vladimir.nikolic@amis.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 01:25:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197790 --- Comment #2 from vladimir.nikolic@amis.net --- By 'reset' I meant reboot of server. We have 'em' driver compiled into kernel, so unloading driver is not an option. I've already downgrade one server to FreeBSD 9.3 and virtualized the other one on VMware esxi host (FreeBSD 10.1 remained). It's interesting that vmware 'emulate' em driver, but 'routing' error has disappeared. Maybe I need to upgrade firmware on network cards? Regards, Vladimir Nikolic -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 05:01:36 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D1134C1 for ; Wed, 11 Mar 2015 05:01:36 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 13EDDD41 for ; Wed, 11 Mar 2015 05:01:36 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2B51Zdj059140 for ; Wed, 11 Mar 2015 05:01:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197265] [mii] patch to support rtl8211f ethernet phys Date: Wed, 11 Mar 2015 05:01:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john@feith.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 05:01:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #5 from john@feith.com --- In a quick smoke test of cycling through the various ifconfig media / mediaopt options your patch seems fine. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 08:39:24 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02BCFB5C; Wed, 11 Mar 2015 08:39:24 +0000 (UTC) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA3ED6B7; Wed, 11 Mar 2015 08:39:20 +0000 (UTC) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id B87B81BEBB; Wed, 11 Mar 2015 09:39:16 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id B0F202E24D; Wed, 11 Mar 2015 09:39:16 +0100 (CET) Date: Wed, 11 Mar 2015 09:39:16 +0100 From: Kristof Provost To: freebsd-net@FreeBSD.org Subject: Re: [PATCH] Fix panic with pf fastroute Message-ID: <20150311083916.GQ1975@vega.codepro.be> References: <1426064691-1238-1-git-send-email-kristof@sigsegv.be> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1426064691-1238-1-git-send-email-kristof@sigsegv.be> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pf@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 08:39:24 -0000 Set up a pf ruleset with at least the following rule > pass out fastroute inet6 proto icmp6 all icmp6-type echoreq Send out an icmp6 echo request (i.e. ping6 2001:db8::1). This causes a panic in ip6_output() when comparing the old and new destination addresses (IN6_ARE_ADDR_EQUAL()) just after the netpfil hook. The cause is the fastroute option, which means that the mbuf is handed off to ip6_output() from pf itself and should no longer be processed by the ip6_output() which called pf in the first place. The pf code in pf_route6() neglected to set the mbuf pointer to NULL after the call to ip6_output(). As a result we end up trying to continue processing on an mbuf which has already been freed. --- sys/netpfil/pf/pf.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sys/netpfil/pf/pf.c b/sys/netpfil/pf/pf.c index b32288b..7c3ddb8 100644 --- a/sys/netpfil/pf/pf.c +++ b/sys/netpfil/pf/pf.c @@ -5470,6 +5470,7 @@ pf_route6(struct mbuf **m, struct pf_rule *r, int dir, struct ifnet *oifp, PF_STATE_UNLOCK(s); m0->m_flags |= M_SKIP_FIREWALL; ip6_output(m0, NULL, NULL, 0, NULL, NULL, NULL); + *m = NULL; return; } From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 09:51:32 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA946E72; Wed, 11 Mar 2015 09:51:32 +0000 (UTC) Received: from forward9l.mail.yandex.net (forward9l.mail.yandex.net [IPv6:2a02:6b8:0:1819::9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E5B8EF9; Wed, 11 Mar 2015 09:51:32 +0000 (UTC) Received: from smtp4m.mail.yandex.net (smtp4m.mail.yandex.net [77.88.61.131]) by forward9l.mail.yandex.net (Yandex) with ESMTP id 12BC7E6106D; Wed, 11 Mar 2015 12:51:27 +0300 (MSK) Received: from smtp4m.mail.yandex.net (localhost [127.0.0.1]) by smtp4m.mail.yandex.net (Yandex) with ESMTP id 8C78FBE024D; Wed, 11 Mar 2015 12:51:27 +0300 (MSK) Received: from unknown (unknown [2a02:6b8:0:6::bb]) by smtp4m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id y0Wxc8ucME-pRrGMLlh; Wed, 11 Mar 2015 12:51:27 +0300 (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1426067487; bh=kNzI0PidRFEBJWZWrqYnjpYeztxd/V63k4tk9HLYR08=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type; b=rx8lzbGjHVKb0ryGf9NLd7w6EIBzIZkmt8wHDMQGF/H44rEKU14yQcUVVeyKeo7e5 H1ApzNvW8A4JCqmeBi22muCs/NekA1wLQRlzAUsNGwLEOdOAJOHBhlbSVYloqMtPcq 7lfbDVNK+UVI/sntUWop44FPdu2DPKPWA18kBM4M= Authentication-Results: smtp4m.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <55000FDF.10007@yandex.ru> Date: Wed, 11 Mar 2015 12:50:23 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Kristof Provost , freebsd-net@FreeBSD.org Subject: Re: [PATCH] Fix panic with pf fastroute References: <1426064691-1238-1-git-send-email-kristof@sigsegv.be> <20150311083916.GQ1975@vega.codepro.be> In-Reply-To: <20150311083916.GQ1975@vega.codepro.be> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="b1wKiEvkW8XJSfeC9L6BIOf9LHC7irkac" Cc: freebsd-pf@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 09:51:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --b1wKiEvkW8XJSfeC9L6BIOf9LHC7irkac Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 11.03.2015 11:39, Kristof Provost wrote: > The pf code in pf_route6() neglected to set the mbuf pointer to NULL > after the call to ip6_output(). As a result we end up trying to continu= e > processing on an mbuf which has already been freed. > --- > sys/netpfil/pf/pf.c | 1 + > 1 file changed, 1 insertion(+) >=20 > diff --git a/sys/netpfil/pf/pf.c b/sys/netpfil/pf/pf.c > index b32288b..7c3ddb8 100644 > --- a/sys/netpfil/pf/pf.c > +++ b/sys/netpfil/pf/pf.c > @@ -5470,6 +5470,7 @@ pf_route6(struct mbuf **m, struct pf_rule *r, int= dir, struct ifnet *oifp, > PF_STATE_UNLOCK(s); > m0->m_flags |=3D M_SKIP_FIREWALL; > ip6_output(m0, NULL, NULL, 0, NULL, NULL, NULL); > + *m =3D NULL; > return; > } It looks like there are some code paths that do a copy of original mbuf. Are you sure this doesn't introduce mbuf leak? --=20 WBR, Andrey V. Elsukov --b1wKiEvkW8XJSfeC9L6BIOf9LHC7irkac 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 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJVAA/fAAoJEAHF6gQQyKF6k+wH/3IVNGOcDTE1yMQBB7IB+Dac i0uxybhQLncftcifJQaya6ytzXny96x+B727Rmlo8Jnscsmn3IwYYpnA+9dduWPX xE3/cSM0h5Qg0JB/h4XHvcZdAsqqZYfDOCF48uul68ZwuyKS8rYWs7C/WsydeRlk WKETd1+7M0A+g9HtDGLRUiFTD2XcZkP9cWhlw92za3HuQkz+Y+5N0H5i+I+YyTf7 hw3SISURf6bRc6owvVyUHiECebnBuJk2FKvioVFs8uXo5IJjZ33AZJw/U76GhJB4 an6qzGkgO4Qt/IjTUjtdBgmhs44oQ4tnAOsdr5OeF7TkjSPPbgfeEJiEH2E5jYs= =qZb3 -----END PGP SIGNATURE----- --b1wKiEvkW8XJSfeC9L6BIOf9LHC7irkac-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 12:50:55 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88EAFAE4; Wed, 11 Mar 2015 12:50:55 +0000 (UTC) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A6D76E2; Wed, 11 Mar 2015 12:50:54 +0000 (UTC) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id 7519012206; Wed, 11 Mar 2015 13:50:50 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id 6E5BE2E316; Wed, 11 Mar 2015 13:50:50 +0100 (CET) Date: Wed, 11 Mar 2015 13:50:50 +0100 From: Kristof Provost To: "Andrey V. Elsukov" Subject: Re: [PATCH] Fix panic with pf fastroute Message-ID: <20150311125050.GR1975@vega.codepro.be> References: <1426064691-1238-1-git-send-email-kristof@sigsegv.be> <20150311083916.GQ1975@vega.codepro.be> <55000FDF.10007@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <55000FDF.10007@yandex.ru> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-net@FreeBSD.org, freebsd-pf@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 12:50:55 -0000 On 2015-03-11 12:50:23 (+0300), Andrey V. Elsukov wrote: > It looks like there are some code paths that do a copy of original mbuf. > Are you sure this doesn't introduce mbuf leak? > I'll check again in the morning when I'm less drunk and jet lagged, but I'm pretty confident this is correct. There are only two exit points from pf_route6(), this one only happens in case of FASTROUTE, not DUPTO (which is the one that duplicates). Regards. Kristof From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 14:43:35 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 464569F8 for ; Wed, 11 Mar 2015 14:43:35 +0000 (UTC) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id A786A814 for ; Wed, 11 Mar 2015 14:43:34 +0000 (UTC) Received: from lgwl-lstewart2.corp.netflix.com (c110-22-60-167.eburwd6.vic.optusnet.com.au [110.22.60.167]) by lauren.room52.net (Postfix) with ESMTPSA id C29DE7E839; Thu, 12 Mar 2015 01:38:06 +1100 (EST) Message-ID: <5500531C.1000109@room52.net> Date: Thu, 12 Mar 2015 01:37:16 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: tcpm@ietf.org Subject: TCP window updates combined with dup acks sent in response to packet loss Content-Type: multipart/mixed; boundary="------------090509000204080901010707" X-Spam-Status: No, score=2.4 required=5.0 tests=DNS_FROM_AHBL_RHSBL, UNPARSEABLE_RELAY autolearn=no version=3.3.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net X-Mailman-Approved-At: Wed, 11 Mar 2015 14:57:26 +0000 Cc: Grenville Armitage X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 14:43:35 -0000 This is a multi-part message in MIME format. --------------090509000204080901010707 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit [BCCed to freebsd-net@freebsd.org] Hi all, Please consider the code below from FreeBSD 10.1's TCP input processing: /* * In ESTABLISHED state: drop duplicate ACKs; ACK out of range * ACKs. If the ack is in the range * tp->snd_una < th->th_ack <= tp->snd_max * then advance tp->snd_una to th->th_ack and drop * data from the retransmission queue. If this ACK reflects * more up to date window information we update our window information. */ case TCPS_ESTABLISHED: case TCPS_FIN_WAIT_1: case TCPS_FIN_WAIT_2: case TCPS_CLOSE_WAIT: case TCPS_CLOSING: case TCPS_LAST_ACK: if (SEQ_GT(th->th_ack, tp->snd_max)) { TCPSTAT_INC(tcps_rcvacktoomuch); goto dropafterack; } if ((tp->t_flags & TF_SACK_PERMIT) && ((to.to_flags & TOF_SACK) || !TAILQ_EMPTY(&tp->snd_holes))) tcp_sack_doack(tp, &to, th->th_ack); /* Run HHOOK_TCP_ESTABLISHED_IN helper hooks. */ hhook_run_tcp_est_in(tp, th, &to); if (SEQ_LEQ(th->th_ack, tp->snd_una)) { if (tlen == 0 && tiwin == tp->snd_wnd) { TCPSTAT_INC(tcps_rcvdupack); Now for a dupack to be treated as such for the purposes of triggering fast retransmit/fast recovery, the dupack must not update the window as per the "tiwin == tp->snd_wnd" condition above, which has existed since at least BSD 4.4 (I didn't bother looking further back in history). Grenville (CCed) has encountered proof of this condition forcing connections to recover via RTO when legitimate dupacks sent in response to a packet loss also contain a window update. In the example tcpdump excerpt attached, the advertised receive window is growing as the Linux receiver side app reads data from the socket buffer while the dupacks are generated. The FreeBSD sender side sees them as window updates and processes them as such, bypassing the dupack processing code. The send window is consumed and because only dup acks are returning, UNA is not advanced and so the connection stalls, requiring two RTOs to recover from the 2 dropped packets. With SACK in the mix as is the case for the provided example, it seems obvious to me that the existence of SACK blocks could and should be used to realise that a window update combined with a dupack is not a pure window update and therefore should be processed by the dupack handling code for fast retransmit/fast recovery purposes. For connections without SACK, is there any existing guidance on how to deal with this? My Google fu and skimming of the RFCs that seemed relevant to this matter turned up nothing, and so I'm imagining a potential algorithm for inferring if a window update can count as a dupack for fast retransmit/fast recovery purposes or not. Wanted to get some input from others before spending any more time on it though. Cheers, Lawrence --------------090509000204080901010707 Content-Type: text/plain; charset=us-ascii; name="dupackwndupdate.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dupackwndupdate.txt" MDA6MDA6MDAuMDAwMjQxIElQIDE3Mi4xNi4xMC42MC41MTY3NyA+IDE3Mi4xNi4xMS42My44 MjogRmxhZ3MgWy5dLCBhY2sgMTA4ODM0LCB3aW4gNzczNCwgb3B0aW9ucyBbbm9wLG5vcCxU UyB2YWwgMjY0ODYxOTEgZWNyIDQxODMxOTQyNzhdLCBsZW5ndGggMAowMDowMDowMC4wMDAy MTYgSVAgMTcyLjE2LjEwLjYwLjUxNjc3ID4gMTcyLjE2LjExLjYzLjgyOiBGbGFncyBbLl0s IGFjayAxMDg4MzQsIHdpbiA3ODI0LCBvcHRpb25zIFtub3Asbm9wLFRTIHZhbCAyNjQ4NjE5 MSBlY3IgNDE4MzE5NDI3OCxub3Asbm9wLHNhY2sgMSB7MTEwMjgyOjExMTczMH1dLCBsZW5n dGggMAowMDowMDowMC4wMDgwMjUgSVAgMTcyLjE2LjEwLjYwLjUxNjc3ID4gMTcyLjE2LjEx LjYzLjgyOiBGbGFncyBbLl0sIGFjayAxMDg4MzQsIHdpbiA3OTE1LCBvcHRpb25zIFtub3As bm9wLFRTIHZhbCAyNjQ4NjE5OSBlY3IgNDE4MzE5NDI3OCxub3Asbm9wLHNhY2sgMiB7MTEz MTc4OjExNDYyNn1bfHRjcF0+CjAwOjAwOjAwLjAwMDIzMyBJUCAxNzIuMTYuMTAuNjAuNTE2 NzcgPiAxNzIuMTYuMTEuNjMuODI6IEZsYWdzIFsuXSwgYWNrIDEwODgzNCwgd2luIDgwMDUs IG9wdGlvbnMgW25vcCxub3AsVFMgdmFsIDI2NDg2MjAwIGVjciA0MTgzMTk0Mjc4LG5vcCxu b3Asc2FjayAyIHsxMTMxNzg6MTE2MDc0fVt8dGNwXT4KMDA6MDA6MDAuMDAwMjQ4IElQIDE3 Mi4xNi4xMC42MC41MTY3NyA+IDE3Mi4xNi4xMS42My44MjogRmxhZ3MgWy5dLCBhY2sgMTA4 ODM0LCB3aW4gODA5Niwgb3B0aW9ucyBbbm9wLG5vcCxUUyB2YWwgMjY0ODYyMDAgZWNyIDQx ODMxOTQyNzgsbm9wLG5vcCxzYWNrIDIgezExMzE3ODoxMTc1MjJ9W3x0Y3BdPgowMDowMDow MC4wMDAyMTcgSVAgMTcyLjE2LjEwLjYwLjUxNjc3ID4gMTcyLjE2LjExLjYzLjgyOiBGbGFn cyBbLl0sIGFjayAxMDg4MzQsIHdpbiA4MTg2LCBvcHRpb25zIFtub3Asbm9wLFRTIHZhbCAy NjQ4NjIwMCBlY3IgNDE4MzE5NDI3OCxub3Asbm9wLHNhY2sgMiB7MTEzMTc4OjExODk3MH1b fHRjcF0+CjAwOjAwOjAwLjAwMDI2OSBJUCAxNzIuMTYuMTAuNjAuNTE2NzcgPiAxNzIuMTYu MTEuNjMuODI6IEZsYWdzIFsuXSwgYWNrIDEwODgzNCwgd2luIDgyNzcsIG9wdGlvbnMgW25v cCxub3AsVFMgdmFsIDI2NDg2MjAwIGVjciA0MTgzMTk0Mjc4LG5vcCxub3Asc2FjayAyIHsx MTMxNzg6MTIwNDE4fVt8dGNwXT4KMDA6MDA6MDAuMDAwMjQyIElQIDE3Mi4xNi4xMC42MC41 MTY3NyA+IDE3Mi4xNi4xMS42My44MjogRmxhZ3MgWy5dLCBhY2sgMTA4ODM0LCB3aW4gODM2 Nywgb3B0aW9ucyBbbm9wLG5vcCxUUyB2YWwgMjY0ODYyMDEgZWNyIDQxODMxOTQyNzgsbm9w LG5vcCxzYWNrIDIgezExMzE3ODoxMjE4NjZ9W3x0Y3BdPgowMDowMDowMC4wMDAyNTAgSVAg MTcyLjE2LjEwLjYwLjUxNjc3ID4gMTcyLjE2LjExLjYzLjgyOiBGbGFncyBbLl0sIGFjayAx MDg4MzQsIHdpbiA4NDU4LCBvcHRpb25zIFtub3Asbm9wLFRTIHZhbCAyNjQ4NjIwMSBlY3Ig NDE4MzE5NDI3OCxub3Asbm9wLHNhY2sgMiB7MTEzMTc4OjEyMzMxNH1bfHRjcF0+CjAwOjAw OjAwLjAwMDIwOSBJUCAxNzIuMTYuMTAuNjAuNTE2NzcgPiAxNzIuMTYuMTEuNjMuODI6IEZs YWdzIFsuXSwgYWNrIDEwODgzNCwgd2luIDg1NDgsIG9wdGlvbnMgW25vcCxub3AsVFMgdmFs IDI2NDg2MjAxIGVjciA0MTgzMTk0Mjc4LG5vcCxub3Asc2FjayAyIHsxMTMxNzg6MTI0NzYy fVt8dGNwXT4KMDA6MDA6MDAuMDAwMjYzIElQIDE3Mi4xNi4xMC42MC41MTY3NyA+IDE3Mi4x Ni4xMS42My44MjogRmxhZ3MgWy5dLCBhY2sgMTA4ODM0LCB3aW4gODYzOSwgb3B0aW9ucyBb bm9wLG5vcCxUUyB2YWwgMjY0ODYyMDEgZWNyIDQxODMxOTQyNzgsbm9wLG5vcCxzYWNrIDIg ezExMzE3ODoxMjYyMTB9W3x0Y3BdPgowMDowMDowMC4wMDAyNDQgSVAgMTcyLjE2LjEwLjYw LjUxNjc3ID4gMTcyLjE2LjExLjYzLjgyOiBGbGFncyBbLl0sIGFjayAxMDg4MzQsIHdpbiA4 NzI5LCBvcHRpb25zIFtub3Asbm9wLFRTIHZhbCAyNjQ4NjIwMiBlY3IgNDE4MzE5NDI3OCxu b3Asbm9wLHNhY2sgMiB7MTEzMTc4OjEyNzY1OH1bfHRjcF0+CjAwOjAwOjAwLjAwMDI0MyBJ UCAxNzIuMTYuMTAuNjAuNTE2NzcgPiAxNzIuMTYuMTEuNjMuODI6IEZsYWdzIFsuXSwgYWNr IDEwODgzNCwgd2luIDg4MjAsIG9wdGlvbnMgW25vcCxub3AsVFMgdmFsIDI2NDg2MjAyIGVj ciA0MTgzMTk0Mjc4LG5vcCxub3Asc2FjayAyIHsxMTMxNzg6MTI5MTA2fVt8dGNwXT4KMDA6 MDA6MDAuMDAwMjE4IElQIDE3Mi4xNi4xMC42MC41MTY3NyA+IDE3Mi4xNi4xMS42My44Mjog RmxhZ3MgWy5dLCBhY2sgMTA4ODM0LCB3aW4gODkxMCwgb3B0aW9ucyBbbm9wLG5vcCxUUyB2 YWwgMjY0ODYyMDIgZWNyIDQxODMxOTQyNzgsbm9wLG5vcCxzYWNrIDIgezExMzE3ODoxMzA1 NTR9W3x0Y3BdPgowMDowMDowMC4yODI3NjkgSVAgMTcyLjE2LjExLjYzLjgyID4gMTcyLjE2 LjEwLjYwLjUxNjc3OiBGbGFncyBbLl0sIHNlcSAxMDg4MzQ6MTEwMjgyLCBhY2sgMTAwLCB3 aW4gMTA0MCwgb3B0aW9ucyBbbm9wLG5vcCxUUyB2YWwgNDE4MzE5NDYzMiBlY3IgMjY0ODYy MDJdLCBsZW5ndGggMTQ0OAowMDowMDowMC4wMDIyODQgSVAgMTcyLjE2LjEwLjYwLjUxNjc3 ID4gMTcyLjE2LjExLjYzLjgyOiBGbGFncyBbLl0sIGFjayAxMTE3MzAsIHdpbiA5MDAxLCBv cHRpb25zIFtub3Asbm9wLFRTIHZhbCAyNjQ4NjQ4NyBlY3IgNDE4MzE5NDYzMixub3Asbm9w LHNhY2sgMSB7MTEzMTc4OjEzMDU1NH1dLCBsZW5ndGggMAowMDowMDowMC4zMzE0MjggSVAg MTcyLjE2LjExLjYzLjgyID4gMTcyLjE2LjEwLjYwLjUxNjc3OiBGbGFncyBbLl0sIHNlcSAx MTE3MzA6MTEzMTc4LCBhY2sgMTAwLCB3aW4gMTA0MCwgb3B0aW9ucyBbbm9wLG5vcCxUUyB2 YWwgNDE4MzE5NDk2NiBlY3IgMjY0ODY0ODddLCBsZW5ndGggMTQ0OAo= --------------090509000204080901010707-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 15:27:57 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C28EECF for ; Wed, 11 Mar 2015 15:27:57 +0000 (UTC) Received: from mail-yh0-x22a.google.com (mail-yh0-x22a.google.com [IPv6:2607:f8b0:4002:c01::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49DF8DF9 for ; Wed, 11 Mar 2015 15:27:57 +0000 (UTC) Received: by yhnv1 with SMTP id v1so4821371yhn.2 for ; Wed, 11 Mar 2015 08:27:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=jwjFlMH/XiwY1OJElcp/1ioamtHu0erOZQKh2hnIlbk=; b=gb/kjqpEweuy5ZGtvf6Re7XXnGBynJvHUALxUiLe/N/LcSAh8xSoa0gIk7ChIXkShc xIu6jP3k4cAdo1SdloFyn9mcINMPusPhRmxNA/YNL9jp1E389KlzXPcrZpEBmR7KQx8G 3uJWpu2LYnFj8xAckQ39tKCum9q16WEHm6JNpzC8KrlxGzraF++TaLL26gFdP3rp8sxr Juqnemf82JqOmB4xK4GE0o/hrbNTZHgcqVRhLTlkscR8Khxx/GZpuCUUFCudPv1Vv+Jl Us4oGmha1Rt8WutYrY2A4UMYUybFvEp/Pay/scbKH27PGd5CQs1IpY/MRH+uR/wpeUTw nauQ== X-Received: by 10.236.70.100 with SMTP id o64mr37175132yhd.94.1426087676299; Wed, 11 Mar 2015 08:27:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.106.132 with HTTP; Wed, 11 Mar 2015 08:27:16 -0700 (PDT) From: =?KOI8-R?B?SWdvciAnTG8nICjpLkwuKQ==?= Date: Wed, 11 Mar 2015 16:27:16 +0100 Message-ID: Subject: Netmap/divert socket capture: getting ipfw state? [porting from Linux, need NFLOG/NFQUEUE/ct functionality] To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 15:27:57 -0000 Hello, I currently plan to port one of my projects to FreeBSD from Linux, now it requires an intrusive way of packet capture (to avoid drops) and relies on a connection state tracking information from outside (e.g. Linux's conntrack)). So I need a way to capture some traffic based on predetermined ipfw(?) rules, then get the packets to userspace together with connection tracking state data from firewall. What are my options on FreeBSD? (Also, I'm fine with going down to kernel and communicating with my own userspace app with other means, as long as I don't have to add own connection tracker, but I'll prefer a pure userspace solution if possible). -- cheers, Igor From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 17:50:30 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0C50BCF for ; Wed, 11 Mar 2015 17:50:30 +0000 (UTC) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C395187 for ; Wed, 11 Mar 2015 17:50:30 +0000 (UTC) Received: by labmn12 with SMTP id mn12so10594057lab.0 for ; Wed, 11 Mar 2015 10:50:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=HNhtj+g1Ze7haDLRNfTKlp2TjMqtZm+9M7NTBTfYMXk=; b=kdUQ8BUyuoL5/ScdvlKCWPbeZJPedoUdNblqf/fZJWVipTsHRSiulLtEGIfy+/UPhx 1WatM6kdiUpnvXeLjVY0mec1YedudsWaqPETFSUOcxFIHahSqbr3leTPiXOE+rrf7NK8 Bd3q0TuPdszAJ5lqr8YMBkYXLHaJMgVPLLhEBMSXharnrGm/R2W5myq7apgXElvcZCqb PqpiLoN83FGMjPKcJkxvq5afos/OcwRym2nlwJTYBl37ZPZtKsrltrHUQYSQ3dPfXkxj onw4Xm4EOV9yQKHAoxwAjRN/Sek93uQ4gcpDOydf4hDWTvuUinbcqznHDoJ2wARf+QXL eHWg== MIME-Version: 1.0 X-Received: by 10.152.1.70 with SMTP id 6mr12619662lak.83.1426096228192; Wed, 11 Mar 2015 10:50:28 -0700 (PDT) Sender: rizzo.unipi@gmail.com Received: by 10.114.180.4 with HTTP; Wed, 11 Mar 2015 10:50:28 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Mar 2015 18:50:28 +0100 X-Google-Sender-Auth: NXP0_z4voKi-tpBequhH2MOqR1A Message-ID: Subject: Re: Netmap/divert socket capture: getting ipfw state? [porting from Linux, need NFLOG/NFQUEUE/ct functionality] From: Luigi Rizzo To: =?UTF-8?B?SWdvciAnTG8nICjQmC5MLik=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 17:50:30 -0000 On Wed, Mar 11, 2015 at 4:27 PM, Igor 'Lo' (=D0=98.L.) wrote: > Hello, > > I currently plan to port one of my projects to FreeBSD from Linux, > now it requires an intrusive way of packet capture (to avoid drops) > and relies on a connection state tracking information from outside > (e.g. Linux's conntrack)). > > So I need a way to capture some traffic based on predetermined ipfw(?) > rules, then get the packets to userspace together with connection > tracking state data from firewall. > > What are my options on FreeBSD? code.google.com/p/netmap-ipfw/ is a userspace port of ipfw that runs on top of netmap (works on FreeBSD and Linux) which gives you a fast way to capture the data and pass them to the next stage of processing e.g. through a netmap pipe. cheers luigi > > (Also, I'm fine with going down to kernel and communicating with my > own userspace app with other means, as long as I don't have to add own > connection tracker, but I'll prefer a pure userspace solution if > possible). > > -- > cheers, > Igor > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" --=20 -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2211611 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+------------------------------- From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 23:45:39 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D0BD353B for ; Wed, 11 Mar 2015 23:45:39 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7243FFA for ; Wed, 11 Mar 2015 23:45:39 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2BNjdUn086483 for ; Wed, 11 Mar 2015 23:45:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197198] bxe driver failed to init NIC Date: Wed, 11 Mar 2015 23:45:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 23:45:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197198 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |davidch@FreeBSD.org, | |edavis@FreeBSD.org --- Comment #1 from Hiren Panchasara --- Victor, you may need to provide more info/logs but adding bxe(4) maintainers for further followup. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Wed Mar 11 23:48:27 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D7775F0 for ; Wed, 11 Mar 2015 23:48:27 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74019A6 for ; Wed, 11 Mar 2015 23:48:27 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2BNmR2V095581 for ; Wed, 11 Mar 2015 23:48:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 195924] [patch] IXGBE watchdog bug causes crash. Date: Wed, 11 Mar 2015 23:48:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 23:48:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195924 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erj@freebsd.org, | |jfv@FreeBSD.org Summary|IXGBE watchdog bug causes |[patch] IXGBE watchdog bug |crash. |causes crash. --- Comment #1 from Hiren Panchasara --- Adding ixgbe(4) maintainers. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 00:16:53 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 704ACBBA; Thu, 12 Mar 2015 00:16:53 +0000 (UTC) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EEDB395; Thu, 12 Mar 2015 00:16:51 +0000 (UTC) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id D781D12D2E; Thu, 12 Mar 2015 01:16:47 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id 8ECCD2E3EF; Thu, 12 Mar 2015 01:16:47 +0100 (CET) Date: Thu, 12 Mar 2015 01:16:47 +0100 From: Kristof Provost To: "Andrey V. Elsukov" Subject: Re: [PATCH] Fix panic with pf fastroute Message-ID: <20150312001647.GS1975@vega.codepro.be> References: <1426064691-1238-1-git-send-email-kristof@sigsegv.be> <20150311083916.GQ1975@vega.codepro.be> <55000FDF.10007@yandex.ru> <20150311125050.GR1975@vega.codepro.be> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150311125050.GR1975@vega.codepro.be> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-net@FreeBSD.org, freebsd-pf@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 00:16:53 -0000 On 2015-03-11 13:50:50 (+0100), Kristof Provost wrote: > On 2015-03-11 12:50:23 (+0300), Andrey V. Elsukov wrote: > > It looks like there are some code paths that do a copy of original mbuf. > > Are you sure this doesn't introduce mbuf leak? > > > I'll check again in the morning when I'm less drunk and jet lagged, but > I'm pretty confident this is correct. > There are only two exit points from pf_route6(), this one only happens > in case of FASTROUTE, not DUPTO (which is the one that duplicates). > So, yes, the duplication is only done if r->rt == PF_DUPTO and the case I fixed is r->rt == PF_FASTROUTE. Regards, Kristof From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 04:37:00 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0C89814 for ; Thu, 12 Mar 2015 04:37:00 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96BC02F5 for ; Thu, 12 Mar 2015 04:37:00 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C4b0gO002191 for ; Thu, 12 Mar 2015 04:37:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197536] ipfilter rule removal via command line deletes all rules added after as well Date: Thu, 12 Mar 2015 04:37:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:37:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197536 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |cy@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 04:37:10 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B4FC89D for ; Thu, 12 Mar 2015 04:37:10 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 616B12F8 for ; Thu, 12 Mar 2015 04:37:10 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C4bA9q006461 for ; Thu, 12 Mar 2015 04:37:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 192847] ipfilter: seeing a lot of BAD packets in the logs while SSH-ing to the box Date: Thu, 12 Mar 2015 04:37:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cy@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:37:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192847 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |cy@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 04:44:16 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0DA6AF9B for ; Thu, 12 Mar 2015 04:44:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E7AE5637 for ; Thu, 12 Mar 2015 04:44:15 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C4iFmS022606 for ; Thu, 12 Mar 2015 04:44:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 192325] [PATCH] snmp_pf: add support for retrieving ALTQ counters Date: Thu, 12 Mar 2015 04:44:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:44:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192325 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |patch -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 04:46:45 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25B4C3CA for ; Thu, 12 Mar 2015 04:46:45 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0B87B689 for ; Thu, 12 Mar 2015 04:46:45 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C4ki1c060572 for ; Thu, 12 Mar 2015 04:46:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 130109] [ipfw] Can not set fib for packets originated from local host Date: Thu, 12 Mar 2015 04:46:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 7.1-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-ipfw@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:46:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=130109 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |freebsd-ipfw@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 04:48:31 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CC7B549B for ; Thu, 12 Mar 2015 04:48:31 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2B6469D for ; Thu, 12 Mar 2015 04:48:31 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C4mV9N005617 for ; Thu, 12 Mar 2015 04:48:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 192426] [bpf] [panic] [patch]: Kernel panic when using BPF Date: Thu, 12 Mar 2015 04:48:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:48:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192426 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Assignee|freebsd-net@FreeBSD.org |freebsd-pf@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 04:48:44 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F211C563 for ; Thu, 12 Mar 2015 04:48:44 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D84996A3 for ; Thu, 12 Mar 2015 04:48:44 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C4mioL011339 for ; Thu, 12 Mar 2015 04:48:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 175267] [pf] [tap] pf + tap keep state problem Date: Thu, 12 Mar 2015 04:48:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:48:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=175267 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |freebsd-pf@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 05:25:27 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 844E9123 for ; Thu, 12 Mar 2015 05:25:27 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A2A0BD9 for ; Thu, 12 Mar 2015 05:25:27 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C5PRAt044691 for ; Thu, 12 Mar 2015 05:25:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196011] if_gre tunnel works without rebooting system only in any one direction (send or receive) Date: Thu, 12 Mar 2015 05:25:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 05:25:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196011 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 07:06:15 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 567BEF7A for ; Thu, 12 Mar 2015 07:06:15 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CC8083F for ; Thu, 12 Mar 2015 07:06:15 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C76FjT099704 for ; Thu, 12 Mar 2015 07:06:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197265] [mii] patch to support rtl8211f ethernet phys Date: Thu, 12 Mar 2015 07:06:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 07:06:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #6 from commit-hook@freebsd.org --- A commit references this bug: Author: yongari Date: Thu Mar 12 07:05:29 UTC 2015 New revision: 279903 URL: https://svnweb.freebsd.org/changeset/base/279903 Log: Add RTL8211F gigabit PHY support. PR: 197265 MFC after: 2 weeks Changes: head/sys/dev/mii/rgephy.c head/sys/dev/mii/rgephyreg.h -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 07:10:15 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E9677243 for ; Thu, 12 Mar 2015 07:10:15 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D00D1904 for ; Thu, 12 Mar 2015 07:10:15 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C7AFYd004496 for ; Thu, 12 Mar 2015 07:10:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197265] [mii] patch to support rtl8211f ethernet phys Date: Thu, 12 Mar 2015 07:10:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yongari@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: yongari@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 07:10:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 Pyun YongHyeon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |yongari@FreeBSD.org --- Comment #7 from Pyun YongHyeon --- Take. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 09:04:30 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 82D77E09 for ; Thu, 12 Mar 2015 09:04:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5136E77B for ; Thu, 12 Mar 2015 09:04:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C94Uxl073256 for ; Thu, 12 Mar 2015 09:04:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197059] network locks up with IPv6 udp traffic Date: Thu, 12 Mar 2015 09:04:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ae@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 09:04:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197059 --- Comment #7 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Thu Mar 12 09:04:21 UTC 2015 New revision: 279911 URL: https://svnweb.freebsd.org/changeset/base/279911 Log: MFC r279588: Fix deadlock in IPv6 PCB code. When several threads are trying to send datagram to the same destination, but fragmentation is disabled and datagram size exceeds link MTU, ip6_output() calls pfctlinput2(PRC_MSGSIZE). It does notify all sockets wanted to know MTU to this destination. And since all threads hold PCB lock while sending, taking the lock for each PCB in the in6_pcbnotify() leads to deadlock. RFC 3542 p.11.3 suggests notify all application wanted to receive IPV6_PATHMTU ancillary data for each ICMPv6 packet too big message. But it doesn't require this, when we don't receive ICMPv6 message. Change ip6_notify_pmtu() function to be able use it directly from ip6_output() to notify only one socket, and to notify all sockets when ICMPv6 packet too big message received. MFC r279684: tcp6_ctlinput() doesn't pass MTU value to in6_pcbnotify(). Check cmdarg isn't NULL before dereference, this check was in the ip6_notify_pmtu() before r279588. PR: 197059 Sponsored by: Yandex LLC Changes: _U stable/10/ stable/10/sys/netinet6/in6_pcb.c stable/10/sys/netinet6/ip6_input.c stable/10/sys/netinet6/ip6_output.c stable/10/sys/netinet6/ip6_var.h -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 09:17:33 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A96F220B for ; Thu, 12 Mar 2015 09:17:33 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 767698C9 for ; Thu, 12 Mar 2015 09:17:33 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C9HX2c009757 for ; Thu, 12 Mar 2015 09:17:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197059] network locks up with IPv6 udp traffic Date: Thu, 12 Mar 2015 09:17:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ae@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 09:17:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197059 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Thu Mar 12 09:16:52 UTC 2015 New revision: 279912 URL: https://svnweb.freebsd.org/changeset/base/279912 Log: MFC r279588: Fix deadlock in IPv6 PCB code. When several threads are trying to send datagram to the same destination, but fragmentation is disabled and datagram size exceeds link MTU, ip6_output() calls pfctlinput2(PRC_MSGSIZE). It does notify all sockets wanted to know MTU to this destination. And since all threads hold PCB lock while sending, taking the lock for each PCB in the in6_pcbnotify() leads to deadlock. RFC 3542 p.11.3 suggests notify all application wanted to receive IPV6_PATHMTU ancillary data for each ICMPv6 packet too big message. But it doesn't require this, when we don't receive ICMPv6 message. Change ip6_notify_pmtu() function to be able use it directly from ip6_output() to notify only one socket, and to notify all sockets when ICMPv6 packet too big message received. MFC r279684: tcp6_ctlinput() doesn't pass MTU value to in6_pcbnotify(). Check cmdarg isn't NULL before dereference, this check was in the ip6_notify_pmtu() before r279588. PR: 197059 Sponsored by: Yandex LLC Changes: _U stable/9/sys/ stable/9/sys/netinet6/in6_pcb.c stable/9/sys/netinet6/ip6_input.c stable/9/sys/netinet6/ip6_output.c stable/9/sys/netinet6/ip6_var.h -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 09:21:34 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 176893D1 for ; Thu, 12 Mar 2015 09:21:34 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2559984 for ; Thu, 12 Mar 2015 09:21:33 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C9LXZ8028598 for ; Thu, 12 Mar 2015 09:21:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197059] network locks up with IPv6 udp traffic Date: Thu, 12 Mar 2015 09:21:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ae@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 09:21:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197059 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 09:34:16 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EF6974F for ; Thu, 12 Mar 2015 09:34:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14D02AC5 for ; Thu, 12 Mar 2015 09:34:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C9YFFi041717 for ; Thu, 12 Mar 2015 09:34:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196011] if_gre tunnel works without rebooting system only in any one direction (send or receive) Date: Thu, 12 Mar 2015 09:34:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 09:34:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196011 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ae@FreeBSD.org --- Comment #1 from Andrey V. Elsukov --- Can you try this implementation https://people.freebsd.org/~ae/gre-10.tgz ? This is ported version from FreeBSD 11. If your tunnel has different inner and outer addresses, it should work as is. Unload original if_gre.ko module and just use `make all load` in if_gre directory. Then configure you tunnel as before. Also you can patch ifconfig(8) utility and it will support new options for gre(4) interfaces, but this isn't required. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 13:17:15 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7948C9F5 for ; Thu, 12 Mar 2015 13:17:15 +0000 (UTC) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE0827D6 for ; Thu, 12 Mar 2015 13:17:14 +0000 (UTC) Received: by lamq1 with SMTP id q1so15645283lam.12 for ; Thu, 12 Mar 2015 06:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Z+l0x1Fs8Zco8YC4NpIiq/0QmPe2cvckBDXnNMnIaOY=; b=Fel9adtWsJYoJzZXKVfIXD/f44tTJeG08H71D7ZOjTF8MTaAHiFnBdPpw3JpI6tirL pc2s2+LEqXbeET+jX2MDRqyLz9ydHlLYmwyq+hK5BAirwBWlTMRtDiv9L9AXpVKFLnxM zSSqMe8fIYuArpNGbRriWT/Z1Z5pHgE3EuXNZZZYwsi+49RLTjRz1eVo81/OGa8lNrUA ihFyKiFhT6WFvbK+SqjPQmUK+g/08SoRLyC7eYluDpw1NSC3eV/YTSP5cepjlCqBd1aq 8J1PxF+Sccmn2sKZbhBlq2QXnfi2gjsK/BAvthWE3g6hQ8uJcotQ636ctnarRl1zpF8v GJzw== MIME-Version: 1.0 X-Received: by 10.112.134.167 with SMTP id pl7mr38393056lbb.63.1426166233026; Thu, 12 Mar 2015 06:17:13 -0700 (PDT) Received: by 10.112.42.194 with HTTP; Thu, 12 Mar 2015 06:17:12 -0700 (PDT) In-Reply-To: <20150309061926.GA975@michelle.fasterthan.com> References: <20150309061926.GA975@michelle.fasterthan.com> Date: Thu, 12 Mar 2015 13:17:12 +0000 Message-ID: Subject: Re: cpsw/atphy network drivers From: Matt Dooner To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 13:17:15 -0000 Hello, Thank you for your reply. Confirming the link configuration was a good exercise, but I think I've been able to rule it out as the issue. 100baseTX appears to be the configuration request by the switch the board was plugged into. I have connected the 335x board directly to two other systems (windows and freebsd) and the correct configuration is negotiated when either or both are set to auto (If I change the configuration on one machine the other updates its configuration accordingly). I have also tested setting the link manually on both systems. I have also confirmed that my two other systems can connect with each other and the switch. I've connected the 335x board directly to another FreeBSD 10.1 (desktop) system. The desktop uses the fxp-miibus-inphy driver combo. I ifconfig 192.168.0.1 255.255.255.0 and ifconfig 192.168.0.2 255.255.255.0 each system respectively. I also setup default routes between them. When I create traffic (ping) on either machine I see the following incremented on the 335x: dev.cpsw.0.stats.GoodTxFrames: 64 dev.cpsw.0.stats.BroadcastTxFrames: 64 dev.cpsw.0.stats.RxTx65to127OctetFrames: 64 and on the desktop: dev.fxp.0.status.tx.good_frames: 3 All other stats on both the 335x and desktop are zero. I am able to follow similar steps to build a working network between the desktop and a windows laptop. Do you know if atphy(4) has been previously tested to work on the AR8033 or even the AR8031? miidevs only has an entry for AR8021. I've only found limited information about the PHY being used, but its from OpenBSD and the wrong cpu type. These is also a note in the change logs about this hardware "Added atphy(4) to armv7, for the Atheros AR8031 phys in the AM335x starter kit." (http://www.openbsd.org/plus57.html) openbsd-current sys\arch\armv7\imx\imxenet.c: 466: case BOARD_ID_IMX6_WANDBOARD: /* AR8031 */ 467 /* disable SmartEEE */ 468 imxenet_miibus_writereg(dev, phy, 0x0d, 0x0003); ... 472 imxenet_miibus_writereg(dev, phy, 0x0e, reg & ~0x0100); 473 474: /* enable 125MHz clk output for AR8031 */ 475 imxenet_miibus_writereg(dev, phy, 0x0d, 0x0007); 476 imxenet_miibus_writereg(dev, phy, 0x0e, 0x8016); The board vendor emphasises that RGMII must be setup properly: "It is important configure pin mux and work mode to RGMII mode." It seems that some additional driver development will likely be required. Thanks, Matt On 9 March 2015 at 06:19, Yonghyeon PYUN wrote: > On Fri, Mar 06, 2015 at 12:45:22PM +0000, Matt Dooner wrote: >> Hello, >> >> I am having some trouble configurating the network driver on a TI >> T335x-based CoM system >> (http://www.compulab.co.il/products/computer-on-modules/cm-t335/). It >> uses the "the AM335x integrated Ethernet MAC coupled with the AR8033 >> RGMII Ethernet PHY from Atheros". U-Boot is able to find the device as >> expected: >> >> CM-T335w # mii device >> MII devices: 'cpsw' >> Current device: 'cpsw' >> >> CM-T335w # mdio list >> cpsw: >> 0 - AR8031/AR8033 <--> cpsw >> >> CM-T335w # dhcp >> link up on port 0, speed 100, half duplex >> BOOTP broadcast 1 >> DHCP client bound to address 10.1.192.67 >> CM-T335w # ping 8.8.8.8 >> link up on port 0, speed 100, half duplex >> Using cpsw device >> host 8.8.8.8 is alive >> > > [...] >> root@beaglebone:~ # ifconfig >> cpsw0: flags=8847 metric >> 0 mtu 1500 >> options=8000b >> ether 1c:ba:8c:ed:40:99 >> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 >> 09:58:57 cpsw_ifmedia_sts >> 09:58:57 cpsw_ifmedia_sts >> 09:58:57 cpsw_ifmedia_sts >> media: Ethernet autoselect (100baseTX ) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Given that you get a half-duplex link, I guess there is speed or > duplex mismatch with link partner. Does link partner also agree > on the established link speed/duplex? If this is not the case, you > may be able to see alignment errors or CRC errors via H/W MAC > statistics counters. Quick reading the code indicates that cpsw(4) > exports sysctl stat nodes(dev.cpsw.%d.stats). If link partner also > supports H/W MAC statistics counters you can consult the info on > the link partner. > > If the issue is really speed/duplex mismatch issue, probably you > can try one of the following. > - If you have manual media configuration for cpsw(4), use auto. > - If link partner uses fixed speed/duplex instead of auto, use > the same media configuration on cpsw(4). > - If neither helps, try unplugging the UTP cable and wait a > couple of seconds then plug it again. > > It seems there is no miibus_statchg handler in cpsw(4) so I guess > cpsw(4) may not be able to program some MAC parameters including > duplex when established link is not that of the cpsw(4) assumes. > So it would be best to manually set link parameters on both link > parter and cpsw(4) to use the same link configuration(100Mbps, > full-duplex). > >> status: active >> nd6 options=29 >> lo0: flags=8049 metric 0 mtu 16384 >> options=600003 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 >> inet 127.0.0.1 netmask 0xff000000 >> nd6 options=21 >> >> When connected to another computer running Wireshark no frames are >> recorded as having been transmitted over the interface. The cpsw >> driver never reports receiving any packets, even when I use a tool >> like Ostinato to craft frames addressed to the MAC of the NIC on the >> board. >> >> The network interface works perfectly in Debian Linux: >> > > Fixing the link state change handling as well as promiscuous mode > handling seem to need more work. From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 14:04:48 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9658D70B for ; Thu, 12 Mar 2015 14:04:48 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AE2DD3C for ; Thu, 12 Mar 2015 14:04:46 +0000 (UTC) Received: by wiwl15 with SMTP id l15so47981524wiw.4 for ; Thu, 12 Mar 2015 07:04:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=zPpKVJ6e3BkptZBCVeDNuEVFWjSQIFiVfZtcjXmHjnc=; b=cm5dCb0Y8gP7pRCbiDihNMBETFoQAnGV8amjEEVB/rEUY77wrBS1oR5JHhVoeO67lx qRiRD1qUIGKBQ0o0eKcIX32t1AJmK4fUFVQFGaqtCkPRJIS3LNYiKg2h0DOf2BQq1OEj 5m9987MzXvbebai6xlyTkZyChGIidhM3P98xrvgKHLcno8A9NfoEZrpWP1H8Vhwf49Mq qHovqI9RXAWhmwM9q7NLu7xFLzRe2ewhV/ttUzRUhQRx5Mf+qrKP7EHNCre4jfvp8AW9 XpRcgVyMmPqQrytOPQi2HMcM/zMQ3t+wt2ymbnDh/byuSM5F6rXP/+vLA4SpnbGJntk3 PSLg== X-Gm-Message-State: ALoCoQk0xSNvfS0CozzaMDS7Yzv67F7v0+mYL4nTstW8RpdpX1xXwwlcam+56sO9OnuYX+7TByEp X-Received: by 10.194.93.165 with SMTP id cv5mr6075976wjb.24.1426169078969; Thu, 12 Mar 2015 07:04:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.27.126.132 with HTTP; Thu, 12 Mar 2015 07:04:18 -0700 (PDT) From: Tim Borgeaud Date: Thu, 12 Mar 2015 14:04:18 +0000 Message-ID: Subject: A defensive NFS server (sbwait, flow control) To: freebsd-net@freebsd.org, Mark Hills Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 14:04:48 -0000 Hi again FreeBSD folks, A short while ago I sent a couple of emails regarding the idea of 'fair share' NFS scheduling. Amongst others, Garrett Wollman replied, and also sent a related email "Implementing backpressure in the NFS server". The common theme: to provide a level of service in situations where requests from some clients might tie up a lot of resources. There are various issues to consider. We might say that we're looking at 'defensive' functionality, and we've made some experimental progress to: round robin requests from different users provide some limits (flow control) on the number of requests read from a single transport Testing has highlighted the issue that Garrett mentioned. A client can make a set of concurrent requests and then tie up nfsd threads as they attempt to send replies. To be more specific, we seem to be hitting the situation in which an nfsd thread sits in the "sbwait" state, waiting for a reply to be drained (by a suspended client). Other threads subsequently pick up requests for the same transport and then queue up waiting for a lock on the same socket. I'm not sure of the exact situation in which the sbwait arises. It's easily repeatable only where there are multiple concurrent requests from the same transport. Our testing is fairly synthetic, but it looks like this is a situation that has been noticed before. Having a pool of spare threads doesn't seem like a very robust solution. In fact, if more than the server minimum get tied up, then, if load and threads fall, we end up with _all_ remaining threads blocked (no more nfs service). How to address this particular issue is not obvious to me. I assume there are options including: - prevent thread blocking when sending replies - timeouts for sending replies (NFS or RPC level?) - serialize the sending of nfs/rpc replies to avoid multiple nfsd threads waiting on the same transport. Does anyone have any thoughts about this? Either this particular issue or more general direction for a 'defensive' server? -- Tim Borgeaud Systems Developer From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 15:07:13 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFA5AEFC; Thu, 12 Mar 2015 15:07:12 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ACFCF75C; Thu, 12 Mar 2015 15:07:12 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 5311B1FE023; Thu, 12 Mar 2015 16:07:09 +0100 (CET) Message-ID: <5501ABCA.7020203@selasky.org> Date: Thu, 12 Mar 2015 16:07:54 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: John Baldwin , freebsd-arch@freebsd.org Subject: Re: Adding new media types to if_media.h References: <20150226230031.GN17947@glebius.int.ru> <20150227192310.GR17947@glebius.int.ru> <1919032.aFEK3un8ig@ralph.baldwin.cx> In-Reply-To: <1919032.aFEK3un8ig@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , mike@karels.net, "freebsd-net@freebsd.org" , Jack Vogel , Eric Joyner X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 15:07:13 -0000 On 02/28/15 13:28, John Baldwin wrote: > On Friday, February 27, 2015 10:23:10 PM Gleb Smirnoff wrote: >> On Thu, Feb 26, 2015 at 08:25:59PM -0800, Adrian Chadd wrote: >> A> [snip] >> A> >> A> I think Mike's approach is good - it makes it easy to MFC to 10.2 >> A> since there's extended lifecycle stuff to do there - and then we can >> A> plan out how do the "betterer" fix after it's landed and churned >> A> things. >> >> ... and we will be ought to support the "betterer" fix along with >> the "not so betterer" for a very long time. >> >> The rock on which we split in this argument is that some developers >> write their code for stable/x and then forward-port it to head, >> focused on quality of result for stable/x; while other developers >> do the opposite: write code to head, then consider or not consider >> merging it stable/x. > > No, this is not quite true. Some folks have to write drivers on HEAD but also > support running those drivers on older branches. The MFC's get harder when > you have very different APIs on the different branches. It's already harder > to test stat changes now since it requires completely different patches for > <= 10 (the only thing people are supposed to use in production) vs head due to > if_getcounter() and friends. Also, since 11 won't be out until 2016, that is > far, far too long to wait for more media types. The stuff we need to support > is already shipping in products today. We can't not support these in 10 (and > possibly 9). > Any news on this issue? Is anyone working on a solution for -head ? --HPS From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 16:59:47 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 408E686D; Thu, 12 Mar 2015 16:59:47 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 164398E0; Thu, 12 Mar 2015 16:59:47 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4B8F3B963; Thu, 12 Mar 2015 12:59:45 -0400 (EDT) From: John Baldwin To: Hans Petter Selasky Subject: Re: Adding new media types to if_media.h Date: Thu, 12 Mar 2015 12:01:13 -0400 Message-ID: <1740987.7L4GidWlzm@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <5501ABCA.7020203@selasky.org> References: <20150226230031.GN17947@glebius.int.ru> <1919032.aFEK3un8ig@ralph.baldwin.cx> <5501ABCA.7020203@selasky.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 12 Mar 2015 12:59:45 -0400 (EDT) Cc: Adrian Chadd , mike@karels.net, "freebsd-net@freebsd.org" , Jack Vogel , freebsd-arch@freebsd.org, Eric Joyner X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 16:59:47 -0000 On Thursday, March 12, 2015 04:07:54 PM Hans Petter Selasky wrote: > On 02/28/15 13:28, John Baldwin wrote: > > On Friday, February 27, 2015 10:23:10 PM Gleb Smirnoff wrote: > >> On Thu, Feb 26, 2015 at 08:25:59PM -0800, Adrian Chadd wrote: > >> A> [snip] > >> A> > >> A> I think Mike's approach is good - it makes it easy to MFC to 10.2 > >> A> since there's extended lifecycle stuff to do there - and then we can > >> A> plan out how do the "betterer" fix after it's landed and churned > >> A> things. > >> > >> ... and we will be ought to support the "betterer" fix along with > >> the "not so betterer" for a very long time. > >> > >> The rock on which we split in this argument is that some developers > >> write their code for stable/x and then forward-port it to head, > >> focused on quality of result for stable/x; while other developers > >> do the opposite: write code to head, then consider or not consider > >> merging it stable/x. > > > > No, this is not quite true. Some folks have to write drivers on HEAD but also > > support running those drivers on older branches. The MFC's get harder when > > you have very different APIs on the different branches. It's already harder > > to test stat changes now since it requires completely different patches for > > <= 10 (the only thing people are supposed to use in production) vs head due to > > if_getcounter() and friends. Also, since 11 won't be out until 2016, that is > > far, far too long to wait for more media types. The stuff we need to support > > is already shipping in products today. We can't not support these in 10 (and > > possibly 9). > > > > Any news on this issue? Is anyone working on a solution for -head ? I believe a variant of Mike's patch is in phabricator now? -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 17:40:19 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B2FADB4; Thu, 12 Mar 2015 17:40:19 +0000 (UTC) Received: from mail.karels.net (mail.karels.net [63.231.190.5]) by mx1.freebsd.org (Postfix) with ESMTP id BF7DBDBA; Thu, 12 Mar 2015 17:40:18 +0000 (UTC) Received: from mail.karels.net (localhost [127.0.0.1]) by mail.karels.net (8.14.7/8.14.7) with ESMTP id t2CHS2ZM008948; Thu, 12 Mar 2015 12:28:02 -0500 (CDT) (envelope-from mike@karels.net) Message-Id: <201503121728.t2CHS2ZM008948@mail.karels.net> To: John Baldwin From: Mike Karels Reply-to: mike@karels.net Subject: Re: Adding new media types to if_media.h In-reply-to: Your message of Thu, 12 Mar 2015 12:01:13 -0400. <1740987.7L4GidWlzm@ralph.baldwin.cx> Date: Thu, 12 Mar 2015 12:28:02 -0500 Cc: Hans Petter Selasky , Adrian Chadd , "freebsd-net@freebsd.org" , Jack Vogel , freebsd-arch@freebsd.org, Eric Joyner X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 17:40:19 -0000 > > Any news on this issue? Is anyone working on a solution for -head ? > I believe a variant of Mike's patch is in phabricator now? My patch, plus addition of new 10/40 Gb types, is in review D1965. There is an althernative approach in D2008. There hasn't been much activity on either. Take a look! Mike From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 17:43:41 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 90D3AFD6 for ; Thu, 12 Mar 2015 17:43:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EA19EA3 for ; Thu, 12 Mar 2015 17:43:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CHhf2m012181 for ; Thu, 12 Mar 2015 17:43:41 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2CHhfU0012180; Thu, 12 Mar 2015 17:43:41 GMT (envelope-from root) Date: Thu, 12 Mar 2015 17:43:41 +0000 To: freebsd-net@freebsd.org From: "hselasky (Hans Petter Selasky)" Subject: [Differential] [Changed Subscribers] D1965: Add extended media types to if_media.h and ifconfig Message-ID: X-Priority: 3 Thread-Topic: D1965: Add extended media types to if_media.h and ifconfig X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: YmU0NTlhN2Q2ZDc3OTdjODA5NmQwOTI1OTFkIFUB0E0= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 17:43:41 -0000 hselasky added a subscriber: hselasky. BRANCH /head INLINE COMMENTS sys/net/if_media.h:182 Style nit. after define. REVISION DETAIL https://reviews.freebsd.org/D1965 To: erj, adrian, jfvogel, gnn Cc: hselasky, mike-karels.net, glebius, freebsd-net From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 19:26:45 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DBC05D30; Thu, 12 Mar 2015 19:26:45 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9A080D0B; Thu, 12 Mar 2015 19:26:45 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 3F82B1FE023; Thu, 12 Mar 2015 20:26:42 +0100 (CET) Message-ID: <5501E89F.3050900@selasky.org> Date: Thu, 12 Mar 2015 20:27:27 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: mike@karels.net, John Baldwin Subject: Re: Adding new media types to if_media.h References: <201503121728.t2CHS2ZM008948@mail.karels.net> In-Reply-To: <201503121728.t2CHS2ZM008948@mail.karels.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Joyner , "freebsd-net@freebsd.org" , Adrian Chadd , Jack Vogel , freebsd-arch@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 19:26:46 -0000 On 03/12/15 18:28, Mike Karels wrote: >>> Any news on this issue? Is anyone working on a solution for -head ? > >> I believe a variant of Mike's patch is in phabricator now? > > My patch, plus addition of new 10/40 Gb types, is in review D1965. > There is an althernative approach in D2008. There hasn't been much > activity on either. Take a look! > Hi, I've just uploaded another less intrusive suggestion, including 100GBase types needed by coming Mellanox hardware. https://reviews.freebsd.org/D2056 Feel free to comment. --HPS From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 21:47:11 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14B93821 for ; Thu, 12 Mar 2015 21:47:11 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D4C4EF4C for ; Thu, 12 Mar 2015 21:47:10 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 61D2120DCD for ; Thu, 12 Mar 2015 17:47:07 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Thu, 12 Mar 2015 17:47:09 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= x-sasl-enc:from:content-type:content-transfer-encoding:subject :date:message-id:cc:to:mime-version; s=mesmtp; bh=DnMOoZfqgsvxQB 8rbfXX0rIBSv4=; b=ewE+KwGWSeNoALgbF5tL0vDgLLwIxXL0ndF3XqSM/IYU+I 1I/nK6k1wQ4jemniBfk9LXCXBn4z2jsI82okXR2TX2tQGRnxuA+f+qiRQlMo5ixw vQqQYbXQ6KfLV00AluHyYO7hsHTMEjS9ibeCBcnd2hKSXO81/tCFOno0oF3PY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:from:content-type :content-transfer-encoding:subject:date:message-id:cc:to :mime-version; s=smtpout; bh=DnMOoZfqgsvxQB8rbfXX0rIBSv4=; b=jCD GvJwsZLLhPsUigxBTf3lXnBESxbb7p6E9u/FOA9cLXZay4+/jNW2tc5lf3rNDq0g jbzqvZXnosA8QZe9b7EKI7tcTqZPIJTgy4ouZBWi1BTFrMqW3bYI5TwEsmqRBwdH wo7ZTHNnj4mPihmii1RVZkt97f7PQLYd0l9OBnNA= X-Sasl-enc: JBzDdedNESvuMhjxCzwrlfVVgzHx7LFJsiczunFjdTwS 1426196828 Received: from [192.168.0.5] (unknown [84.212.193.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 80034680198; Thu, 12 Mar 2015 17:47:08 -0400 (EDT) From: "Bradley T. Hughes" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Jumbo frame support on xn0 in AWS EC2 Date: Thu, 12 Mar 2015 22:47:07 +0100 Message-Id: <4B8447C7-A5E9-47DB-8063-A10F0D3002D0@fastmail.fm> To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 21:47:11 -0000 Howdy! I started off posting a question to freebsd-cloud@ about what would be = necessary to get jumbo frame support on xn0 in a FreeBSD VM running in = AWS EC2. I was advised to post my question to a wider audience (hence = the cross post). Here was my original question: The AWS EC2 Instance Types documentation[1] says that the MTU for the = network interfaces is dependent on the instance type. A post on the AWS = forums[2] by an AWS representative states that the MTU configuration is = available via DHCP. I noticed that all of our T2 instances running FreeBSD have an MTU of = 1500. After searching around a bit, I found this patch[3]. I get the = same results when running the reproduction steps in EC2, despite = ifconfig(8) saying it's using an MTU of 9001. I'm wondering if the patch in 187094 is what's needed to make the xn0 = interface on our FreeBSD instances use jumbo frames? Thanks in advance :) [1] = http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html [2] https://forums.aws.amazon.com/thread.jspa?threadID=3D143674 [3] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187094 -- Bradley T. Hughes bradleythughes@fastmail.fm From owner-freebsd-net@FreeBSD.ORG Thu Mar 12 21:48:45 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0DD99D0 for ; Thu, 12 Mar 2015 21:48:45 +0000 (UTC) Received: from gw.catspoiler.org (cl-1657.chi-02.us.sixxs.net [IPv6:2001:4978:f:678::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 66D8EF64 for ; Thu, 12 Mar 2015 21:48:45 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id t2CLmCNM097193; Thu, 12 Mar 2015 13:48:18 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201503122148.t2CLmCNM097193@gw.catspoiler.org> Date: Thu, 12 Mar 2015 14:48:11 -0700 (PDT) From: Don Lewis Subject: Re: A defensive NFS server (sbwait, flow control) To: timothy.borgeaud@framestore.com In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-net@FreeBSD.org, mark.hills@framestore.com X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 21:48:46 -0000 On 12 Mar, Tim Borgeaud wrote: > Hi again FreeBSD folks, > > A short while ago I sent a couple of emails regarding the idea of 'fair > share' NFS scheduling. Amongst others, Garrett Wollman replied, and also > sent a related email "Implementing backpressure in the NFS server". The > common theme: to provide a level of service in situations where requests > from some clients might tie up a lot of resources. > > There are various issues to consider. We might say that we're looking at > 'defensive' functionality, and we've made some experimental progress to: > > round robin requests from different users > > provide some limits (flow control) on the number of requests read > from a single transport > > Testing has highlighted the issue that Garrett mentioned. A client can make > a set of concurrent requests and then tie up nfsd threads as they attempt > to send replies. > > To be more specific, we seem to be hitting the situation in which an nfsd > thread sits in the "sbwait" state, waiting for a reply to be drained (by a > suspended client). Other threads subsequently pick up requests for the same > transport and then queue up waiting for a lock on the same socket. > > I'm not sure of the exact situation in which the sbwait arises. It's easily > repeatable only where there are multiple concurrent requests from the same > transport. > > Our testing is fairly synthetic, but it looks like this is a situation that > has been noticed before. Having a pool of spare threads doesn't seem like a > very robust solution. In fact, if more than the server minimum get tied up, > then, if load and threads fall, we end up with _all_ remaining threads > blocked (no more nfs service). > > How to address this particular issue is not obvious to me. I assume there > are options including: > > - prevent thread blocking when sending replies > > - timeouts for sending replies (NFS or RPC level?) > > - serialize the sending of nfs/rpc replies to avoid multiple > nfsd threads waiting on the same transport. > > Does anyone have any thoughts about this? Either this particular issue or > more general direction for a 'defensive' server? If a thread blocks when sending a reply, stop reading any new requests from that transport. That should limit the number of threads that get tied up. From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 00:39:49 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 363B7BF6 for ; Fri, 13 Mar 2015 00:39:49 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C8636DC for ; Fri, 13 Mar 2015 00:39:49 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2D0dmTH038604 for ; Fri, 13 Mar 2015 00:39:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197511] BPF --> Interactions with Dhclient, Tcpdump, and Network Connections (Ping) Date: Fri, 13 Mar 2015 00:39:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 00:39:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197511 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-pf@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 00:40:26 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5DC6DA8 for ; Fri, 13 Mar 2015 00:40:26 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABE317DE for ; Fri, 13 Mar 2015 00:40:26 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2D0eQM6040105 for ; Fri, 13 Mar 2015 00:40:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 16644] [bpf] [patch] Bad comparison expression in bpf_filter.c Date: Fri, 13 Mar 2015 00:40:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 4.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 00:40:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=16644 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-pf@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 00:41:52 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A1A4F8E for ; Fri, 13 Mar 2015 00:41:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70B39819 for ; Fri, 13 Mar 2015 00:41:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2D0fq90044717 for ; Fri, 13 Mar 2015 00:41:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 191916] pflogd(8) eats cpu and hangs with net.bpf.zerocopy_enable=0 Date: Fri, 13 Mar 2015 00:41:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 00:41:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191916 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-pf@FreeBSD.org |freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 02:58:34 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7713DD8 for ; Fri, 13 Mar 2015 02:58:33 +0000 (UTC) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF14699C for ; Fri, 13 Mar 2015 02:58:33 +0000 (UTC) Received: by padet14 with SMTP id et14so25753196pad.0 for ; Thu, 12 Mar 2015 19:58:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=o53b+4EwRIC4Nnp89ad7S9CretRBqgaPURq7j1esFqA=; b=YWoUwaUwzNwucoe5dsGsAJ/lpwBOkXv8M9IRbBBYj9gra4uO74yMHmGVloittJyaf+ XGGyxDCDNdG7D4Xgi+BmdUccp9JeLyS1cXNJ/0UFsTIEqPyG/9hM1h8IXIphMuhaxsAO JaFnv5CczZPYzOT16jzndGfYf5kG/S2h6X6NGZD8wIQeU8yBhhY8asxjhbBUC/+0INil 3xhzG8YN64Pz3eRyfiUTqOrvWwzrCdxlZwX2CYF9cBsbqzV+SdGdMduB/eKVVkbsPCz2 wu4B30rV13waXsqPGXZAzOWwCXI8wM1RPw82bL4OCejSlByQShx+67t8iXWyPcPe+3oI +4Ow== X-Received: by 10.66.129.198 with SMTP id ny6mr63272155pab.67.1426215513349; Thu, 12 Mar 2015 19:58:33 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id oq7sm707418pac.32.2015.03.12.19.58.29 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 12 Mar 2015 19:58:31 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 13 Mar 2015 11:58:22 +0900 Date: Fri, 13 Mar 2015 11:58:22 +0900 To: Matt Dooner Subject: Re: cpsw/atphy network drivers Message-ID: <20150313025822.GA4447@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <20150309061926.GA975@michelle.fasterthan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 02:58:34 -0000 On Thu, Mar 12, 2015 at 01:17:12PM +0000, Matt Dooner wrote: > Hello, > > Thank you for your reply. Confirming the link configuration was a good > exercise, but I think I've been able to rule it out as the issue. > 100baseTX appears to be the configuration request by the > switch the board was plugged into. I have connected the 335x board > directly to two other systems (windows and freebsd) and the correct > configuration is negotiated when either or both are set to auto (If I > change the configuration on one machine the other updates its > configuration accordingly). I have also tested setting the link > manually on both systems. I have also confirmed that my two other > systems can connect with each other and the switch. > > I've connected the 335x board directly to another FreeBSD 10.1 > (desktop) system. The desktop uses the fxp-miibus-inphy driver combo. > I ifconfig 192.168.0.1 255.255.255.0 and ifconfig 192.168.0.2 > 255.255.255.0 each system respectively. I also setup default routes > between them. When I create traffic (ping) on either machine I see the > following incremented on the 335x: > > dev.cpsw.0.stats.GoodTxFrames: 64 > dev.cpsw.0.stats.BroadcastTxFrames: 64 > dev.cpsw.0.stats.RxTx65to127OctetFrames: 64 > > and on the desktop: > > dev.fxp.0.status.tx.good_frames: 3 > > All other stats on both the 335x and desktop are zero. Good to know you've solved the issue. > > I am able to follow similar steps to build a working network between > the desktop and a windows laptop. > > Do you know if atphy(4) has been previously tested to work on the > AR8033 or even the AR8031? miidevs only has an entry for AR8021. I've No I'm not aware of that. > only found limited information about the PHY being used, but its from > OpenBSD and the wrong cpu type. These is also a note in the change > logs about this hardware "Added atphy(4) to armv7, for the Atheros > AR8031 phys in the AM335x starter kit." > (http://www.openbsd.org/plus57.html) > > openbsd-current > sys\arch\armv7\imx\imxenet.c: > 466: case BOARD_ID_IMX6_WANDBOARD: /* AR8031 */ > 467 /* disable SmartEEE */ > 468 imxenet_miibus_writereg(dev, phy, 0x0d, 0x0003); > ... > 472 imxenet_miibus_writereg(dev, phy, 0x0e, reg & ~0x0100); > 473 > 474: /* enable 125MHz clk output for AR8031 */ > 475 imxenet_miibus_writereg(dev, phy, 0x0d, 0x0007); > 476 imxenet_miibus_writereg(dev, phy, 0x0e, 0x8016); > > important configure pin mux and work mode to RGMII mode." > > It seems that some additional driver development will likely be required. > I don't have datasheet for AR8031/AR8033 PHYs so I'm not sure whether it's doable to apply PHY config magic above to atphy(4). I'm under the impression that AR8031/AR8035 may have some other special registers that report resolved speed/duplex and it shall require a new PHY driver. Linux seems to have slightly better comment for those PHYs though. From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 04:21:41 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E261C3B for ; Fri, 13 Mar 2015 04:21:41 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id DAB6A353 for ; Fri, 13 Mar 2015 04:21:40 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CtBABrZAJV/95baINUB4NYWgSDB8BQCoUnSQKCAAEBAQEBAX2EDwEBAQMBAQEBICsgCwUWGAICDRkCKQEJJgYIBwQBGgICAogGCA2yDZs2AQEBAQYBAQEBAQEBG4EhiXaEDwsFAgEHFDQHgmiBRQWUDINWgz05hUOMZyOCAhyBbCIxB3sBHwMffwEBAQ X-IronPort-AV: E=Sophos;i="5.11,392,1422939600"; d="scan'208";a="197069169" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 13 Mar 2015 00:21:33 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 4A504B4041; Fri, 13 Mar 2015 00:21:33 -0400 (EDT) Date: Fri, 13 Mar 2015 00:21:33 -0400 (EDT) From: Rick Macklem To: Tim Borgeaud Message-ID: <2143160693.12216521.1426220493289.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: A defensive NFS server (sbwait, flow control) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-net@freebsd.org, Mark Hills X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 04:21:41 -0000 Tim Borgeaud wrote: > Hi again FreeBSD folks, > > A short while ago I sent a couple of emails regarding the idea of > 'fair > share' NFS scheduling. Amongst others, Garrett Wollman replied, and > also > sent a related email "Implementing backpressure in the NFS server". > The > common theme: to provide a level of service in situations where > requests > from some clients might tie up a lot of resources. > > There are various issues to consider. We might say that we're looking > at > 'defensive' functionality, and we've made some experimental progress > to: > > round robin requests from different users > > provide some limits (flow control) on the number of requests read > from a single transport > > Testing has highlighted the issue that Garrett mentioned. A client > can make > a set of concurrent requests and then tie up nfsd threads as they > attempt > to send replies. > > To be more specific, we seem to be hitting the situation in which an > nfsd > thread sits in the "sbwait" state, waiting for a reply to be drained > (by a > suspended client). Other threads subsequently pick up requests for > the same > transport and then queue up waiting for a lock on the same socket. > > I'm not sure of the exact situation in which the sbwait arises. It's > easily > repeatable only where there are multiple concurrent requests from the > same > transport. > > Our testing is fairly synthetic, but it looks like this is a > situation that > has been noticed before. Having a pool of spare threads doesn't seem > like a > very robust solution. In fact, if more than the server minimum get > tied up, > then, if load and threads fall, we end up with _all_ remaining > threads > blocked (no more nfs service). > I will note that kernel nfsd threads are pretty cheap. Kostik noted that the main resource they hold are their kernel stacks. For a 64bit system (which I'd expect most NFS servers to be), I think you can afford to have lots of them. (I think the 256 limit should be bumped up quite a bit, since that limit seemed appropriate for a single core i386 and doesn't make much sense for a multicore 64bit system.) I haven't heard more from Garrett, but he seemed to have resolved his case by bumping the thread limit to 256. If you are doing testing, make sure to have this set to 256 (-n 256) argument to the nfsd. Any less doesn`t make much sense for a heavily loaded server. (If you want to test with more, just email and I can show you the one line source patch to increase it beyond 256.) There will always be folk that say running too many is a waste, but it is not much of a waste and you can set a minimum and maximum instead of just ``-n 256`` and allow the / of them fluctuate. I think the challenge w.r.t. any scheme that limits resources for a single client is that there will be cases where only one NFS client (or a few) will be sending RPCs to the server at a given time and it seems unfair to limit the client in that case. You might envision a system that tracks "number of active clients", but this will be difficult, since NFS traffic tends to be very bursty (and, as such, number of active clients can vary dramatically). > How to address this particular issue is not obvious to me. I assume > there > are options including: > > - prevent thread blocking when sending replies > > - timeouts for sending replies (NFS or RPC level?) > Can`t drop requests when busy. Sending an NFSERR_DELAY is possible for NFSv3 and NFSv4 (it doesn`t exist for NFSv2, if you care). It won`t be easy to modify the code to do this for an NFS RPC in progress, since it will be buried in VFS calls or something like that. The strategy would have to select certain RPC requests for the NFSERR_DELAY reply before processing the RPC (ie. at the beginning). > - serialize the sending of nfs/rpc replies to avoid multiple > nfsd threads waiting on the same transport. > This will be a big performance hit when only a few clients are active at a given time. Maybe N nfsd threads per TCP connection, but you still run into how big to make the N. (Just easier to create lots of nfsd threads. At some point the server will run out of other resources before all the nfsd threads are busy. A 64bit system dedicated to being an NFS server could have thousands of these, I think. (I know you said that you did not think this was a robust way to handle the problem, but since they are pretty lightweight, I do not see a big problem having lots of them.) > Does anyone have any thoughts about this? Either this particular > issue or > more general direction for a 'defensive' server? > What you have to be wary of here is that NFS servers are expected to try `very hard` to reply to RPCs. There is the NFSERR_DELAY reply that can be sent to tell a client to try again later, but this should probably only be done if the server can`t generate a ``real reply``. (As above, the NFS server cannot just drop requests at least over TCP, since the client will wait a long time before retrying an RPC. Also, for NFSv4, the retry must be done on a new TCP connection. Not something that you want to have happening often.) When a server is overloaded (which is about the only time you should see a large queue of outstanding RPCs), it might be possible to implement a strategy where clients get NFSERR_DELAY replies in a round-robin fashion, but the coding won`t be trivial. If you are willing to pay a performance penalty when only a few clients a active, you can simply limit the system to N nfsd threads to each client (probably actually TCP connections, since there isn`t really a concept of a client for NFSv3). I did like the suggestion that the NFS server not accept RPC requests when reply(s) on that TCP connection are stuck in sbwait. I haven`t looked to see what implementing that would take. rick ps: freebsd-fs or freebsd-current might be better mailing lists for NFS stuff than freebsd-net maybe. > -- > Tim Borgeaud > Systems Developer > _______________________________________________ > 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 Fri Mar 13 10:17:36 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E9FEABF7 for ; Fri, 13 Mar 2015 10:17:36 +0000 (UTC) Received: from smtp1g37.consultorpc.com (smtp1g37.consultorpc.com [93.159.214.137]) by mx1.freebsd.org (Postfix) with ESMTP id 900F9FCF for ; Fri, 13 Mar 2015 10:17:36 +0000 (UTC) Received: by smtp1g31.consultorpc.com id h0ask016r3gs for ; Fri, 13 Mar 2015 11:17:34 +0100 (envelope-from ) To: From: "web@axvisualpromocom.com" Reply-To: "web@axvisualpromocom.com" Date: Fri, 13 Mar 2015 11:17:28 +0100 Message-ID: <5502b93899f15@axalphaconsulting1_ip-zone_com-6> X-CcmId: 0419545b435151505f0812475a46080b05576a08421c4c0e5d566652595b58575c570002000207 Feedback-ID: 39235:39235-7:1:Mailrelay X-Report-Abuse: Please report abuse for this campaign here http://axalphaconsulting1.mailrelay-ii.com/ccm/abuse?a=39235&m=7&s=685896 X-OriginalSender: web@axvisualpromocom.com Subject: Gestiona tu tienda online desde tu ERP MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 10:17:37 -0000 Gestiona tu tienda on-line desde tu ERP Las tiendas on-line es=C3=A1n de moda. Con una m=C3=ADnima inversi=C3=B3n e= con=C3=B3mica puedes tener una potente tienda virtual y vender productos en= todo el mundo. Pero lo que nadie dice es la inversi=C3=B3n de tiempo que n= ecesitas para introducir todos los productos, categor=C3=ADas, precios, ges= ti=C3=B3n de pedidos, facturas, im=C3=A1genes... Si tienes un ERP te ahorras mucho tiempo. Conecta tu programa de gesti= =C3=B3n con la tienda on-line y todos los datos se actualizar=C3=A1n autom= =C3=A1ticamente. S=C3=B3lo tendr=C3=A1s que enviar los productos y hacer la factura!=20 Consulta nuestras propuestas de tienda online y conector ERP AXvisual Promocom Av. Garrigues 44 pl.1. 08820 El Prat de Llobregat (Barcelona). Tel. 93 372 = 90 60. web@axvisualpromocom.com From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 11:16:59 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9352783B for ; Fri, 13 Mar 2015 11:16:59 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 767388AA for ; Fri, 13 Mar 2015 11:16:59 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2DBGxcP091762 for ; Fri, 13 Mar 2015 11:16:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196011] if_gre tunnel works without rebooting system only in any one direction (send or receive) Date: Fri, 13 Mar 2015 11:16:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kvas@bf.pstu.ru X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 11:16:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196011 --- Comment #2 from Vassily --- I got sources from https://people.freebsd.org/~ae/gre-10.tgz and compiled it at my 10.1-p5 server. Reloading if_gre module in kernel was succesfull. For this moment tunnel works in bidirectional mode at least 3 hours. Non rebooting my server. Thanks! -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Sat Mar 14 02:05:07 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3B196AB0; Sat, 14 Mar 2015 02:05:07 +0000 (UTC) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0D988B8; Sat, 14 Mar 2015 02:05:05 +0000 (UTC) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id 6BC7712C20; Sat, 14 Mar 2015 03:05:01 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id 631AC2E0A2; Sat, 14 Mar 2015 03:05:01 +0100 (CET) Date: Sat, 14 Mar 2015 03:05:01 +0100 From: Kristof Provost To: freebsd-pf@freebsd.org, freebsd-net@freebsd.org Subject: Re: PF IPv6 fragments handling Message-ID: <20150314020500.GW1975@vega.codepro.be> References: <20150203202519.GD2167@vega.codepro.be> <20150209232416.GB37777@vega.codepro.be> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150209232416.GB37777@vega.codepro.be> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) Cc: ae@FreeBSD.org, bz@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 14 Mar 2015 02:05:07 -0000 On 2015-02-10 00:24:16 (+0100), Kristof Provost wrote: > On 2015-02-03 21:25:20 (+0100), Kristof Provost wrote: > > Two of my systems are currently running them, seemingly without > > problems. > > > The initial patch set had problems refragmenting in forwarding > scenarios. That should be fixed with the update to > https://reviews.freebsd.org/D1767 and the extra patch in > https://reviews.freebsd.org/D1815 > Status update: all these patches other than D1815 have been committed. There's one crash I know about in forwarding scenarios (and scrub on output). There's a fix which will be committed as soon as it's had a bit more testing. The blocking point is D1815. There's no consensus on it right now, so I'd like to go over the problem and the two possible solutions I see. The problematic scenario is when we're forwarding fragmented IPv6 packets. Right now the fragmented packets are gathered up on the ip6_input() netpfil hook (through pf_test6() -> pf_normalize_ip6() -> pf_reassemble6()). When we've found all of the fragments pf_reassemble6() will create a reassembled fragment and tag it as having been reassembled. pf_test6() then returns the reassembled packet to the IP stack. That passes through ip6_input() and is handed to ip6_forward(). At that point we run into the packet size check, which in ip6_forward() is done before the pfil(PFIL_OUT) hook. That means that we'll send an ICMP6_PACKET_TOO_BIG error rather than forwarding the packet. The proposed fix in D1815 is to simply move the size check after the pfil(PFIL_OUT) hook so pf has the chance to refragment the packet (which it does in pf_test6() -> pf_refragment6() because the packet has the PF_REASSEMBLED tag). That's also what the OpenBSD stack does. In the D1815 review Gleb Smirnoff proposed a different solution. Instead of returning a reassembled packet from pfil(PFIL_IN) in ip6_input() we could change netpfil so we could return multiple packets. That means we'd reassemble and immediately refragment on the input, and then do the same on the output side. I have a preference for the solution in D1815 for two reasons: - it's less work for me. It's a relatively small change in ip6_output() and nothing else. Changing netpfil so it can return multiple packets is a more invasive change and will impact other firewalls too. - it's less work for the kernel when forwarding. Not only do we only reassemble and refragment once, but we also only need to do ip6_forward() processing on a single packet, rather than for each fragment. Thoughts? Regards, Kristof