From owner-freebsd-net@freebsd.org Sun Jan 14 06:31:51 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F68BE7E98C for ; Sun, 14 Jan 2018 06:31:51 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id F24C66E255 for ; Sun, 14 Jan 2018 06:31:49 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39912301; Sun, 14 Jan 2018 12:26:58 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w0E6ViwR028855; Sun, 14 Jan 2018 13:31:46 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w0E6Vek0028854; Sun, 14 Jan 2018 13:31:40 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Sun, 14 Jan 2018 13:31:40 +0700 From: Victor Sudakov To: Marek Zarychta Cc: freebsd-net@freebsd.org Subject: Re: Fwd: Re: Quasi-enterprise WiFi network Message-ID: <20180114063140.GA28750@admin.sibptus.transneft.ru> References: <20180107180422.GA46756@admin.sibptus.transneft.ru> <52165.108.68.171.12.1515350430.squirrel@cosmo.uchicago.edu> <20180108072035.GB52442@admin.sibptus.transneft.ru> <20180113095553.GA19901@admin.sibptus.transneft.ru> <20180113110739.GA20415@admin.sibptus.transneft.ru> <20180113144157.GA33988@plan-b.pwste.edu.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180113144157.GA33988@plan-b.pwste.edu.pl> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Jan 2018 06:31:51 -0000 Marek Zarychta wrote: > On Sat, Jan 13, 2018 at 06:07:39PM +0700, Victor Sudakov wrote: > > Eitan Adler wrote: > > > > > > > > > > > > Are there any network experts willing to look at the dump of RADIUS > > > > traffic at http://noc.sibptus.ru/~sudakov/radius.pcap ? > > > > > > > > > >From wireshark: PEAP / EAP-MD5-CHALLENGE > > > > Eitan, do you mean it's EAP-MD5 encapsulated in PEAP (TLS tunnel)? > > > > Why is the client not checking the server's certificate authenticity > > and how do I make the client check it against a CA (if I need to)? > > Dear ÷ÉËÔÏÒ, > > Android client doesn't care for server certificate authenticity, so you > don't have to install CA certificate, which was probably automatically > generated by radius and written to file: > /usr/local/etc/raddb/certs/ca.der $raddbdir/certs/{server,ca}.pem for the server and CA respectively, if I read mods-enabled/eap correctly. > > Windows and Mac clients do care for it, so the CA cert should be > installed as a Trusted Root Certificate Authority for these clients. This is bad news for me. However I'll report here when I have experimented with different supplicants. > > If you want to have 0 problems with Windows clients, I recommend building > simple captive portal based on PF redirection and simple login page. There are ready-to-use captive portals in pfSense and m0n0wall (I did not test the latter though), so I think there is no need for me to code in PHP or whatever. What I'm trying to avoid is deploying a dedicated FreeBSD/pfSense box at remote hotspots. And the TL-WR740N router/AP does not do any traffic tunneling via a central hub (or I have not found a way to enable it). Do you know how commercial captive portals handle this problem? Do they install their own box near every customer's AP? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-net@freebsd.org Sun Jan 14 06:38:54 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F6E8E7EE63 for ; Sun, 14 Jan 2018 06:38:54 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B50C06E62D for ; Sun, 14 Jan 2018 06:38:52 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w0E6ciJD021898 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 14 Jan 2018 07:38:44 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: vas@mpeks.tomsk.su Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w0E6cdSL033133 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 14 Jan 2018 13:38:39 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Fwd: Re: Quasi-enterprise WiFi network To: Victor Sudakov , Marek Zarychta References: <20180107180422.GA46756@admin.sibptus.transneft.ru> <52165.108.68.171.12.1515350430.squirrel@cosmo.uchicago.edu> <20180108072035.GB52442@admin.sibptus.transneft.ru> <20180113095553.GA19901@admin.sibptus.transneft.ru> <20180113110739.GA20415@admin.sibptus.transneft.ru> <20180113144157.GA33988@plan-b.pwste.edu.pl> <20180114063140.GA28750@admin.sibptus.transneft.ru> Cc: freebsd-net@freebsd.org From: Eugene Grosbein Message-ID: <5A5AFAEA.2010506@grosbein.net> Date: Sun, 14 Jan 2018 13:38:34 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20180114063140.GA28750@admin.sibptus.transneft.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Jan 2018 06:38:54 -0000 14.01.2018 13:31, Victor Sudakov wrote: > Do you know how commercial captive portals handle this problem? Do they > install their own box near every customer's AP? No. For example, UniFi (which is Linux-based AP with iptables/ebtables) keeps table of MAC addresses of customers passed authorization and redirects HTTP requests of others to single portal using some kind of socket forwarding or NAT. And portal informs AP of authorization success for a client to add its MAC to that table. From owner-freebsd-net@freebsd.org Sun Jan 14 07:24:22 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E631EA6416 for ; Sun, 14 Jan 2018 07:24:22 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id BC8F1707D0 for ; Sun, 14 Jan 2018 07:24:20 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 39912326; Sun, 14 Jan 2018 13:19:31 +0600 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w0E7OHaJ029225; Sun, 14 Jan 2018 14:24:19 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w0E7OCBk029224; Sun, 14 Jan 2018 14:24:12 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Sun, 14 Jan 2018 14:24:11 +0700 From: Victor Sudakov To: Eugene Grosbein Cc: Marek Zarychta , freebsd-net@freebsd.org Subject: Re: Fwd: Re: Quasi-enterprise WiFi network Message-ID: <20180114072411.GA29210@admin.sibptus.transneft.ru> References: <52165.108.68.171.12.1515350430.squirrel@cosmo.uchicago.edu> <20180108072035.GB52442@admin.sibptus.transneft.ru> <20180113095553.GA19901@admin.sibptus.transneft.ru> <20180113110739.GA20415@admin.sibptus.transneft.ru> <20180113144157.GA33988@plan-b.pwste.edu.pl> <20180114063140.GA28750@admin.sibptus.transneft.ru> <5A5AFAEA.2010506@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A5AFAEA.2010506@grosbein.net> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Jan 2018 07:24:22 -0000 Eugene Grosbein wrote: > 14.01.2018 13:31, Victor Sudakov wrote: > > > Do you know how commercial captive portals handle this problem? Do they > > install their own box near every customer's AP? > > No. For example, UniFi (which is Linux-based AP with iptables/ebtables) > keeps table of MAC addresses of customers passed authorization and redirects > HTTP requests of others to single portal using some kind of socket forwarding or NAT. > And portal informs AP of authorization success for a client to add its MAC to that table. So, they (commercial captive portal services) install their own AP then? In hardware? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 From owner-freebsd-net@freebsd.org Sun Jan 14 10:11:17 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45BA3EB82B4 for ; Sun, 14 Jan 2018 10:11:17 +0000 (UTC) (envelope-from menyy@mellanox.com) Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr60075.outbound.protection.outlook.com [40.107.6.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AEC04757E5 for ; Sun, 14 Jan 2018 10:11:15 +0000 (UTC) (envelope-from menyy@mellanox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ev6DLHuDdUnAh0qad9V7VN7hn7YrBpFNopJ1FebVKs0=; b=GemqJVNKZsOk14dUe5BXbUztn9hyhHnQF07PO7spiUtXfDjlJOHDx4UA93Hp4gzr2G6sw+o7oK807PUcw2mMiTzwq+E1FRJAEh7zp55DOVxgVNKZKTBIiz8hLOslVwYkAJW13lCUxcaHfsGW3KTJAVzn9i3vvr99UafVzCSDrfI= Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com (10.172.12.8) by VI1PR0501MB2189.eurprd05.prod.outlook.com (10.169.134.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.7; Sun, 14 Jan 2018 10:11:13 +0000 Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::804c:a5e0:d962:5c26]) by VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::804c:a5e0:d962:5c26%18]) with mapi id 15.20.0407.009; Sun, 14 Jan 2018 10:11:13 +0000 From: Meny Yossefi To: "Somayajulu, David" , "freebsd-net@freebsd.org" Subject: RE: Questions on OFED in FreeBSD Thread-Topic: Questions on OFED in FreeBSD Thread-Index: AdOJc7a+98khuLNQTECXfqqy4dh8zADjo7gQ Date: Sun, 14 Jan 2018 10:11:13 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=menyy@mellanox.com; x-originating-ip: [193.47.165.251] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VI1PR0501MB2189; 6:9Rl1prVLUTunbPIp/Jz104wTFu1Q6i1U41+YNZo/zQdDJpHptff7xKSTRW0RVthhrNY0r8J0kK7GZF9mWnv6YDCGORAcjcKH/techm75bTRUU1Pns52EleMQ+llzW5pSdlIe2l9aEkzGN/dtn73cKZH/hGvyh1M8CtZKHC8yELDCh4NvIvHJvRZx9X8nWs2ScRqD9wm91FqoYux1B4r1TbAamK5lFqb7EQo41afP2oDwYAg1calYvffODfYumLlfgkRLYrx1WH2EZZ7xyJbVAvdiF7U8fqfb7Z1RsF1EFp9m6VQxkBzBP6xKJotmZadtYr+Es82XxEPmMMrhQqxl81p6h+xYpPY5mW3zr/riphM9kEUJGaE8Sz/gZg3pGVG5; 5:HT2CiadPpMY4SRNeKDhXlY7zc02ywgeDZeyBrg1c1XLvl1FUmw7yKUMhbXn+KouwqcbU55V3h1fkS3gVGVKL2+aoqfYHVSfTMufzcH3YsVIap1x5/EJNH2FfZVSLyQA+rTGkmiMR0rqgtE+1zubvhXOv3+p7o39ZcCqsj/ElQSI=; 24:kzxw6FIMCxrGuUzMP7+t4NJnRqkWSXOuFBMff21/U40YoyeWqihtN53+bDjeKDLJ6ljEKFdQpxCdAkoutxulkA9aFPSQmViN67uuhFOX4l0=; 7:lC1czB3bJL4QIFtjV8Lb5qmFkRxAs+IkKKth0OU2KMoyDPKSAxc7oDv9UjvoD6xJDoS3uubsN84mwHYZjbUZ9BP5/t8JjfGn7eqIwtQaXmeBzcrxgB8fETerfdJMNeSOP2nI26kCyegBO3jcEzG02cV5DVBhrs0Vw3S0oGN4ep9BS7sHSZYqbmeL3zT7kIAiO9/4vllmGRj/EUSBiZ23gbr8n+fXEXUELLJ1/LHSjyHG4yJi97h2K6GBkzNjdFiJ x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 0a9959b4-6b4b-4662-8c15-08d55b372437 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(48565401081)(2017052603307)(7153060)(7193020); SRVR:VI1PR0501MB2189; x-ms-traffictypediagnostic: VI1PR0501MB2189: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(189930954265078)(45079756050767); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(10201501046)(3231023)(944501161)(3002001)(93006095)(93001095)(6055026)(6041268)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:VI1PR0501MB2189; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:VI1PR0501MB2189; x-forefront-prvs: 05529C6FDB x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(346002)(39380400002)(366004)(39860400002)(189003)(199004)(13464003)(7696005)(2950100002)(966005)(45080400002)(102836004)(59450400001)(97736004)(2501003)(14454004)(76176011)(105586002)(6506007)(53546011)(2906002)(229853002)(86362001)(55016002)(5660300001)(9686003)(305945005)(74316002)(6436002)(6306002)(478600001)(7736002)(53936002)(6116002)(8676002)(81156014)(6246003)(3846002)(110136005)(66066001)(25786009)(33656002)(68736007)(3660700001)(316002)(3280700002)(106356001)(2900100001)(99286004)(81166006)(5250100002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0501MB2189; H:VI1PR0501MB2863.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: SSPlDPfFC5c4Wu1WZkrVG/QiIQPgiSr1P7gfHKWlrDDJU6fFnhodkOYzghGXvmtreK9fNwNDBqWmup8CZEJDaw== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-Network-Message-Id: 0a9959b4-6b4b-4662-8c15-08d55b372437 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jan 2018 10:11:13.0335 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0501MB2189 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Jan 2018 10:11:17 -0000 Hi David,=20 Answers embedded below. -Meny -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of Somayajulu, David Sent: Tuesday, January 09, 2018 8:08 PM To: freebsd-net@freebsd.org Subject: Questions on OFED in FreeBSD Hi, 1. Is RoCE v2 supported of FreeBSD 11 release or 11_stable ? [MY] Not currently, though we do have plans adding it in the near future 2. How does one figure out the OFED version in a FreeBSD kernel? [MY] Unfortunately, OFED version is not maintained. Some files do state a v= ersion, but I wouldn't trust that too much 3. Since OFED on HEAD is synced to Linux 4.9 in kernel.org, I presume th= at it is OFED version 4.8. Am I correct ? [MY] 4.9+ 4. Am I correct that the OFED version on FreeBSD 11 is 1.5.3 ? [MY] No. We did an upgrade in FreeBSD11 a while back. If I'm not mistaken, = FreeBSD11's OFED is currently based on version 2.0+ 5. Are there any plans to backport OFED from HEAD to Stable_11? [MY] Yes.=20 Thanks David S. (davidcs@freebsd.org) _______________________________________________ freebsd-net@freebsd.org mailing list https://emea01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flists.= freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-net&data=3D02%7C01%7Cfreebsd-com= mits-tracker%40mellanox.com%7C1efc8fb3a42547b6e6cd08d5578bf8e5%7Ca652971c7d= 2e4d9ba6a4d149256f461b%7C0%7C0%7C636511181052323549&sdata=3D3Ct%2BqOx3U8Xv8= %2F4Zm2nlVOQb1CCX8qrNkwzsKB9RmMU%3D&reserved=3D0 To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Sun Jan 14 11:31:03 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC949E64030 for ; Sun, 14 Jan 2018 11:31:03 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 630BF77B8F for ; Sun, 14 Jan 2018 11:31:02 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w0EBUpPA024266 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 14 Jan 2018 12:30:52 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: vas@mpeks.tomsk.su Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w0EBUhVp014253 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 14 Jan 2018 18:30:43 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Fwd: Re: Quasi-enterprise WiFi network To: Victor Sudakov References: <52165.108.68.171.12.1515350430.squirrel@cosmo.uchicago.edu> <20180108072035.GB52442@admin.sibptus.transneft.ru> <20180113095553.GA19901@admin.sibptus.transneft.ru> <20180113110739.GA20415@admin.sibptus.transneft.ru> <20180113144157.GA33988@plan-b.pwste.edu.pl> <20180114063140.GA28750@admin.sibptus.transneft.ru> <5A5AFAEA.2010506@grosbein.net> <20180114072411.GA29210@admin.sibptus.transneft.ru> Cc: Marek Zarychta , freebsd-net@freebsd.org From: Eugene Grosbein Message-ID: <5A5B3F5F.4060008@grosbein.net> Date: Sun, 14 Jan 2018 18:30:39 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20180114072411.GA29210@admin.sibptus.transneft.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Jan 2018 11:31:04 -0000 14.01.2018 14:24, Victor Sudakov wrote: >>> Do you know how commercial captive portals handle this problem? Do they >>> install their own box near every customer's AP? >> >> No. For example, UniFi (which is Linux-based AP with iptables/ebtables) >> keeps table of MAC addresses of customers passed authorization and redirects >> HTTP requests of others to single portal using some kind of socket forwarding or NAT. >> And portal informs AP of authorization success for a client to add its MAC to that table. > > So, they (commercial captive portal services) install their own AP > then? In hardware? Yes. From owner-freebsd-net@freebsd.org Sun Jan 14 12:15:42 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96CE1E6C00C for ; Sun, 14 Jan 2018 12:15:42 +0000 (UTC) (envelope-from reshad@patuck.net) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 6F38879771 for ; Sun, 14 Jan 2018 12:15:42 +0000 (UTC) (envelope-from reshad@patuck.net) Received: by mail-pf0-x22a.google.com with SMTP id y5so6870100pff.13 for ; Sun, 14 Jan 2018 04:15:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=patuck.net; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=MlIARI9QIECBAvCV0LEWcjbUF/u/akQmBACCKLsjiQk=; b=Q4yfonGpBENyD0HTA8bBM6DKuBwveomG37Y0NT/t5AzMBr356/cKU8zGmjTitdLJlH Z8UWaqk2nFkInHHozlTwzKjDK4e32wzfanKnliId2rhnomcIcr30AseiUtSpPz1XQxLX 2K/PEXV/0lBzly2+3+STuld2aoJcIjBXsLdUE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=MlIARI9QIECBAvCV0LEWcjbUF/u/akQmBACCKLsjiQk=; b=ARPlPSViEhz7w8OPb9Ix0J5cJTmN8HTRqhT68gkR7xpZSgkbgjI5IjuiNBuCx8Y5KA 1QJV7uANf847JmYZC78UJyZPxetz/LAHuKaLumsYJviyyK+9KjTUwjEJgLKH7V52xm7I APxZfBIzhAdonO13vwLScRa2JOXp1dLqhg87H+WiRtRWom/3DEYDqpn5icT3J0QFGlLF KtII5+NUqT8VZcUYuh0P7FboPNzEBakxb53Uz6XoUXEhWHdbjJ3+mBIIfKD7aE/QbUqQ ZN8AhQGILjHIe29awC7YluKbv1dk6rkulsgdHhs5ATIpGIWKYybG6skPaS4cB3oJ4h1W SabA== X-Gm-Message-State: AKwxytdmKMOGml/u6k17+QU4VdzVlPV1uYnzP1VFuVq4/nddlA/TQCHZ iKpCQ6n1FJQU5nRDHTDAfZXflA== X-Google-Smtp-Source: ACJfBouHQAts97q7YHqoA5CdtnmxsJK4+nEVDMPvu4dqLG4eqjCSDQK4wrP6/ElkAAd0sFYiXA0I1g== X-Received: by 10.101.90.202 with SMTP id d10mr2597695pgt.366.1515932141800; Sun, 14 Jan 2018 04:15:41 -0800 (PST) Received: from reshadlaptop.patuck.net ([120.62.6.151]) by smtp.gmail.com with ESMTPSA id x14sm1070338pgq.43.2018.01.14.04.15.39 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 14 Jan 2018 04:15:41 -0800 (PST) From: Reshad Patuck To: Kristof Provost Cc: Reshad Patuck , freebsd-net@freebsd.org Subject: Re: [vnet] [epair] epair interface stops working after some time Date: Sun, 14 Jan 2018 17:45:37 +0530 Message-ID: <1563563.7DUcjoHYMp@reshadlaptop.patuck.net> In-Reply-To: <71B1A1BD-6FCF-47BB-9523-CCAAC03799A5@sigsegv.be> References: <71B1A1BD-6FCF-47BB-9523-CCAAC03799A5@sigsegv.be> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Jan 2018 12:15:42 -0000 Hi, I attempted to unload the pf module, but this did not cause any changes. I am not creating/destroying any VNET jails at the time epais stop to funct= ion. Multiple VNET jails are started when I start the box, but no further activi= ty (starts or stops of vnet jails, creation deletion of epair interfaces, p= f start, stop or reload) I have been monitoring output from the following: =2D netstat -ss =2D netstat -m =2D vmstat -z =2D vmstat -m I will add 'netstat -i' to my battery of monitoring commands. So far I the only pattern I can see out of the ordinary is the 'vmstat -m' = output for epairs. Where the size seems to keep growing, and at some point, the memory-use and= high-use grow too. The epair interface seems to stop working when the memory-use and high-use = grow. I have also noticed that these parameters stay almost constant on other box= es. Here is a link (http://dpaste.com/3WB6AD4.txt) to the csv file containing t= he 'vmstat -m' output for 'epair' over time. I noticed the epair being to fail at timestamp 2018-01-09T07:56Z, but this = test ran every 5 minutes so it could be upto 5 minutes before this timestam= p. NOTE: I have used --libxo on the vmstat to get json output, it seems to hav= e lost the trailing 'K' in the memory-use column. I will update things here if I find anything else in the logs. Please let me know if there is anything else I should look at, or if there = is any other output you would like. Best regards, Reshad On Thursday 11 January 2018 2:20:06 AM IST Kristof Provost wrote: > On 5 Jan 2018, at 20:54, Reshad Patuck wrote: > > I have done the following on both servers to test what happens: > > - Created a new epair interface epair3a and epair3b > > - upped both interfaces > > - given epair3a IP address 10.20.30.40/24 (I don't have this subnet > > anywhere in my network) > > - attempted to ping 10.20.30.50 > > - checked for any packets on epair3b > > On the server where epairs are working, I can see APR packets for > > 10.20.30.50, but on the server where epairs are not working I cant see= =20 > > any > > packets on epair3b. > > I can however see the arp packets on epair3a on both servers. > > > So epair3a was not added to the bridge and epair3b was not added to a=20 > jail? > That=E2=80=99s interesting, because it should mean the problem is not wit= h the=20 > bridge or jail. > As it affects ARP packets it also shouldn=E2=80=99t be a pf problem. > It might be worth unloading the pf module, just to re-confirm, but I=20 > wouldn=E2=80=99t expect it to make a difference. >=20 > > Please let me know if there is anything I can do the debug this issue=20 > > or if > > you need any other information. > > > Are you creating/destroying vnet jails at any point? Is there a=20 > correlation with that and the start of the epair issues? >=20 > Are there any errors in `netstat -s` or `netstat -i epair3a` ? >=20 > Regards, > Kristof From owner-freebsd-net@freebsd.org Mon Jan 15 05:55:18 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F08EE7FE3B for ; Mon, 15 Jan 2018 05:55:18 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 B8DE68083D for ; Mon, 15 Jan 2018 05:55:17 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id 143so22413138wma.5 for ; Sun, 14 Jan 2018 21:55:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=3bf465rNK6yIcodPlr1WyWDpmc+S8t+iDXEXbIyQMGI=; b=Fc7z3XB2OuOqXK9qxfihAge2pYziLOhxIhODkd9+HnhXRaH3UpfR024F8ymAQSbsKa uK7UOdK0i0udOXH+UCKO82UjuceHMbxTh98DQbGAkB7ha+oWa3FqSG4yRfkOtwWRpgx9 Ihgit2y1DgpNvRbZiDYzX9YZEEyEv1Ad0p006uUJ3A2a6CjsTBC1rS0RYdO53DlXwXIc YESej3w/a8Vn4axR9lvMW8ezP/Y1gKdQqy16gDox43/NtVuNZYAIP7MHjB4W93ZolCvn NBH8z1aQkZSp3izRl25lxbAqE4Yd/AFWcf3qlDzm/LAVN1aoUjjQoOrhHI8KnerQRKyD 95Yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3bf465rNK6yIcodPlr1WyWDpmc+S8t+iDXEXbIyQMGI=; b=Wq/BnYaH2fni5r6zodaXrbJ8oOmFgV6zyvdxuwYBoEZ73pZuvCVZ1ZvT4yuE4mNeGb QnvLVzLg5W41kvfT4upU9Lr1dqBev6NAU94S9v5CMdjje7bO7J76hce+9/k/ikyXWJX3 9lDDixFtOgpJXn8rp1OTvZgC7nuAz+H/zyCx2je1lkyIt8jh6yT9e/uP4qTVCRqgIEsP wgfWkDNlyHKn8EdKTVJXrHsN5y3jHpFd2yo1kt7nuWCBytnC+p33St4gTYScYEOqRNkT tWrHqtb4IG1xoZpjMZgzGt9gr6I6IGcoknPBqQLva1DPPLm7ZUldosj3yal0+dQeL0iv jb9g== X-Gm-Message-State: AKGB3mKRHIkByv0mWNIeklD2VtcxfhTMnch5PuMnL+CuEvdZbYKzD3Uk p+Md/lSJRchGuohTWUkfBoG+y/zk1aXkLX2/glM3 X-Google-Smtp-Source: ACJfBosdcWwyQ7CQbBlrjJ72pV7fZGPM7Wqd1k69ENUMjXWQ5apXl1fBVDv89qgWAV8d9XfJyt8JC4pTHn9CNQHlTGk= X-Received: by 10.80.164.233 with SMTP id x38mr47085333edb.293.1515995715097; Sun, 14 Jan 2018 21:55:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.141.135 with HTTP; Sun, 14 Jan 2018 21:55:14 -0800 (PST) From: Zaphod Beeblebrox Date: Mon, 15 Jan 2018 00:55:14 -0500 Message-ID: Subject: FreeBSD11 bge and bce interfaces showing packet loss with older Cisco. To: FreeBSD Net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 15 Jan 2018 05:55:18 -0000 I've been trying to track this problem down for awhile now. I have two different router servers with two different chipset on board NICs. One server has BGE and the other server has BCE. Both are running a full 650k-odd route BGP table with quagga and they're joined internally with OSPF (also quagga). Anyways, I'm seeing, under load (in the netstat -in output): bge1 1500 00:19:b9:f9:ad:13 592048810 2127231 0 576341766 0 0 ... indicating 2127231 error packets out of 592048810 packets. Somewhere around 0.3% in total ... but this rises to about 1% as traffic increases. My first problem is that I don't see any number of packets in any of the netstat -s outputs. How do I track this down to something more specific than the netstat -i output? Now the other end of the dedicated, newly purchased cat6 cable is a Cisco WS-C3550-12G ... a 12 port GigE switch with 10 GBICs and two copper ports. In my case, it's mostly full of copper GBICs and has one SMF GBIC for the uplink. The GBICs show up two ways on the switch: "a-full a-1000 1000BaseTX" for the "older" ones and "a-full a-1000 10/100/1000BaseTX" for the "newer" ones. Since Cisco doesn't allow setting duplex or speed on any of them, I have the problem server connected to the 1000BaseT-only GBIC and I have the server hard set to full-duplex and 1000BaseT. This doesn't seem to change the nature of the problem for better or worse. That is to say both "auto" and hardwired settings have the same failures. Now... I'm fully willing to swap out the switch, but I also have trouble believing that anything has changed with GigE 1000BaseT recently... so I'm also sensitive that it may not be the fix either. Help? Suggestions? From owner-freebsd-net@freebsd.org Mon Jan 15 08:28:38 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE969EB8804 for ; Mon, 15 Jan 2018 08:28:38 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 85D1F28FB for ; Mon, 15 Jan 2018 08:28:37 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w0F8SO81032841 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 15 Jan 2018 09:28:25 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: zbeeble@gmail.com Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w0F8SK7v071362 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 15 Jan 2018 15:28:20 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: FreeBSD11 bge and bce interfaces showing packet loss with older Cisco. To: Zaphod Beeblebrox , FreeBSD Net References: From: Eugene Grosbein Message-ID: <5A5C661F.8030205@grosbein.net> Date: Mon, 15 Jan 2018 15:28:15 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 15 Jan 2018 08:28:39 -0000 15.01.2018 12:55, Zaphod Beeblebrox wrote: > I've been trying to track this problem down for awhile now. I have two > different router servers with two different chipset on board NICs. One > server has BGE and the other server has BCE. Both are running a full > 650k-odd route BGP table with quagga and they're joined internally with > OSPF (also quagga). > > Anyways, I'm seeing, under load (in the netstat -in output): > > bge1 1500 00:19:b9:f9:ad:13 592048810 2127231 0 > 576341766 0 0 > > ... indicating 2127231 error packets out of 592048810 packets. Somewhere > around 0.3% in total ... but this rises to about 1% as traffic increases. > > My first problem is that I don't see any number of packets in any of the > netstat -s outputs. How do I track this down to something more specific > than the netstat -i output? This probably means that NIC chip registers packets dropped before they even reach host and all that driver known are error counters. bge(4) driver increases input error counters whenever NIC reports one of the following counters increase: nicNoMoreRxBDs or ifInErrors cnt = READ_STAT(sc, stats, nicNoMoreRxBDs.bge_addr_lo); if_inc_counter(ifp, IFCOUNTER_IERRORS, cnt - sc->bge_rx_nobds); sc->bge_rx_nobds = cnt; cnt = READ_STAT(sc, stats, ifInErrors.bge_addr_lo); if_inc_counter(ifp, IFCOUNTER_IERRORS, cnt - sc->bge_rx_inerrs); The driver does not export them separately but nicNoMoreRxBDs probably means that host is unable to cope with incoming packet flow that leads to overflow of receiving buffers in the chip. And ifInErrors probably means bad packets (CRC errors?). What is packets-per-second/bytes-per-second maximum rates of incoming traffic does your bge(4) have? Do you have same problem with bce(4)? It exports detailed error counters with "sysctl dev.bce". From owner-freebsd-net@freebsd.org Mon Jan 15 17:40:05 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF193EBDA84 for ; Mon, 15 Jan 2018 17:40:05 +0000 (UTC) (envelope-from David.Somayajulu@cavium.com) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0602.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe48::602]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 894DAEB5 for ; Mon, 15 Jan 2018 17:40:05 +0000 (UTC) (envelope-from David.Somayajulu@cavium.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=CAVIUMNETWORKS.onmicrosoft.com; s=selector1-cavium-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gNNTIWSaI3hVDVz4jJP8Pzym4PRCaPIcKF6b7TCo/Is=; b=DsdWUIEZ9LViIX4pIjoQRKDHw08mLKrGJWQMVuUzELNvHTSDYio/tlvO1Ds26Sp2QCA2kvUCmWfWfRc6tyNMCtLXSsMnCawoR+WJIDvdbFQvNUrTjeNH6wJX3qxKGkTbL32Ds9fVdIJl1VciNOIcfkCm1OZnCBLMGNhmO0BpQJE= Received: from DM2PR07MB1481.namprd07.prod.outlook.com (10.161.139.151) by DM2PR07MB1482.namprd07.prod.outlook.com (10.161.139.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.7; Mon, 15 Jan 2018 17:40:03 +0000 Received: from DM2PR07MB1481.namprd07.prod.outlook.com ([fe80::e59e:fc83:8d05:6f08]) by DM2PR07MB1481.namprd07.prod.outlook.com ([fe80::e59e:fc83:8d05:6f08%18]) with mapi id 15.20.0407.009; Mon, 15 Jan 2018 17:40:03 +0000 From: "Somayajulu, David" To: Meny Yossefi , "freebsd-net@freebsd.org" Subject: RE: Questions on OFED in FreeBSD Thread-Topic: Questions on OFED in FreeBSD Thread-Index: AdOJc7a+98khuLNQTECXfqqy4dh8zADjo7gQAEfgqvA= Date: Mon, 15 Jan 2018 17:40:03 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=David.Somayajulu@cavium.com; x-originating-ip: [2600:1700:c3a0:66f0:1885:c10f:1429:cff6] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DM2PR07MB1482; 6:MQlEKH6LLDSRb1zk05UUAp0/DV3IkTZdu+rmB+rfLm4RHsoDvp8dNFCl0nPS1/DoFYgBaMNZg2tmmX5LqnhjeRtGSpKdDD2a412G0bNIEwMEl48Ln3uLfWzbRu6AWZNSVr32wygXXz8wITNpekN1qruNjP5x8UEFxCiMtunT8HWgHNEHoVjsFu7PF/fthIrPOyFVyAhzDh3MpQtLP+yh8vjZMelpR2JvoXxgUzlxz7/KwCs7H+82X5De/KCj0FWkcJzssx/voAlrlhiBRLDRwvemkM7eL9+FWPYUpywwhePI4e251xmuuu3WlG+JvYneasspB5XTIss68SPQFVUYlDZSccEqBO0AM/GqrURjkx9kgFHnMz68HGz2dwdlQv3B; 5:y/VF5B4DpgU2Q2wdTy2rD+0AxjPi2mGsZlYUgqg7FYQYb14l7fLvnVtoTUD2CfIWFvkv803viG4s3HoBrEz1jgFBQ573Gv+B+rTVOC5UvP4UlYVjoZJUl73UrP498pnNOOEBph84jjBjSvi6kGfKaC9jpZtCg5HaaA1MJdcEcwQ=; 24:8Qr5Kz5PZVJEaHW1wVtuRUF4CzcCcezxqBK34XiL8O2e27qIJYeY7CeM5iw/pF4VW+u1T6k2tF6myqa2GyDv/YaZH4QA9oyg+nMb+813G04=; 7:GZA901Sq7SDNChk+T5NLFodYvtLRu+Y0pyHjH8cqUCR9nV4kLlBjygJbisHzpEC0GTKUXfxaFC0oXZ9QSzdAXD0JsTxBy99RYfPpsy1mELTmUGkY1JqRHf12FxliNqJafqQTrp5WR6GGTvLuudtHDuo2p3FQT6N1LagHatoLzHp32xoyXYk+/uioVM5bOgWT+dx7fD6Q4mgebiJImkNnXx/D4rSGoT873Mv1ymy9hG7bXxh8Ha9wQE/tVIVlzNbZ x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: f152f195-0669-4c38-7003-08d55c3f027b x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534125)(4602075)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:DM2PR07MB1482; x-ms-traffictypediagnostic: DM2PR07MB1482: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(189930954265078)(45079756050767); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(3002001)(3231023)(944501161)(10201501046)(93006095)(93001095)(6041268)(20161123558120)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(6072148)(201708071742011); SRVR:DM2PR07MB1482; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:DM2PR07MB1482; x-forefront-prvs: 0553CBB77A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(396003)(366004)(39380400002)(39860400002)(189003)(199004)(13464003)(6306002)(3280700002)(25786009)(45080400002)(2900100001)(14454004)(68736007)(478600001)(72206003)(2501003)(5250100002)(74316002)(53936002)(81166006)(55016002)(97736004)(305945005)(8676002)(81156014)(3660700001)(9686003)(8936002)(86362001)(7736002)(7696005)(76176011)(99286004)(5660300001)(316002)(229853002)(2950100002)(105586002)(6436002)(53546011)(33656002)(59450400001)(2906002)(106356001)(102836004)(110136005)(966005)(6116002)(6506007)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR07MB1482; H:DM2PR07MB1481.namprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: cavium.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: /LXPW4OiUwmoe0BqXyA3c+tFu573RSc2gbYfAmcWJIGAlbeCVWpBdbiEXXB1H9BebS1TxtF/uy5Rm43i7J5w9Q== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: cavium.com X-MS-Exchange-CrossTenant-Network-Message-Id: f152f195-0669-4c38-7003-08d55c3f027b X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jan 2018 17:40:03.5882 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 711e4ccf-2e9b-4bcf-a551-4094005b6194 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR07MB1482 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 15 Jan 2018 17:40:06 -0000 Hi Meny, Thanks a lot for the reply and the information. I have couple of additional questions. > 4. Am I correct that the OFED version on FreeBSD 11 is 1.5.3 ? >[MY] No. We did an upgrade in FreeBSD11 a while back. If I'm not mistaken,= FreeBSD11's OFED is currently based on version 2.0+ As per http://downloads.openfabrics.org/OFED/ the version following OFED v= ersion 1.5.4 is 3.2. Just curious what 2.0+ version is ? Am I correct that HEAD supports RoCE v2 ? Thanks David S. (davidcs@freebsd.org) -----Original Message----- From: Meny Yossefi [mailto:menyy@mellanox.com]=20 Sent: Sunday, January 14, 2018 2:11 AM To: Somayajulu, David ; freebsd-net@freebsd.or= g Subject: RE: Questions on OFED in FreeBSD Hi David,=20 Answers embedded below. -Meny -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of Somayajulu, David Sent: Tuesday, January 09, 2018 8:08 PM To: freebsd-net@freebsd.org Subject: Questions on OFED in FreeBSD Hi, 1. Is RoCE v2 supported of FreeBSD 11 release or 11_stable ? [MY] Not currently, though we do have plans adding it in the near future 2. How does one figure out the OFED version in a FreeBSD kernel? [MY] Unfortunately, OFED version is not maintained. Some files do state a v= ersion, but I wouldn't trust that too much 3. Since OFED on HEAD is synced to Linux 4.9 in kernel.org, I presume th= at it is OFED version 4.8. Am I correct ? [MY] 4.9+ 4. Am I correct that the OFED version on FreeBSD 11 is 1.5.3 ? [MY] No. We did an upgrade in FreeBSD11 a while back. If I'm not mistaken, = FreeBSD11's OFED is currently based on version 2.0+ 5. Are there any plans to backport OFED from HEAD to Stable_11? [MY] Yes.=20 Thanks David S. (davidcs@freebsd.org) _______________________________________________ freebsd-net@freebsd.org mailing list https://emea01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flists.= freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-net&data=3D02%7C01%7Cfreebsd-com= mits-tracker%40mellanox.com%7C1efc8fb3a42547b6e6cd08d5578bf8e5%7Ca652971c7d= 2e4d9ba6a4d149256f461b%7C0%7C0%7C636511181052323549&sdata=3D3Ct%2BqOx3U8Xv8= %2F4Zm2nlVOQb1CCX8qrNkwzsKB9RmMU%3D&reserved=3D0 To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Jan 16 13:26:40 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DB7AE6E4BC for ; Tue, 16 Jan 2018 13:26:40 +0000 (UTC) (envelope-from menyy@mellanox.com) Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0615.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe1e::615]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A6E079568 for ; Tue, 16 Jan 2018 13:26:39 +0000 (UTC) (envelope-from menyy@mellanox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=u2WlUBSEVqdAE463B+vdhKR564aTlSI+YOdE7LUBiig=; b=DZ+fvFNl0Nyuz6uV8tIqh5IB7WiycdnBplIEyaNHFy58D2o95dxD7S0vFySWiz/qQ8NjcJkhxMlCKa01FQqasF1mbFfjMUAN1DF6vyTS3q+JQdHAfcGlcfZ8nE8Tt/G+EuJ+mu1ei1BtzjbcjoC1z6+kBIqJg6jjeQo8nfgiKPY= Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com (10.172.12.8) by VI1PR0501MB2061.eurprd05.prod.outlook.com (10.167.195.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.7; Tue, 16 Jan 2018 13:26:31 +0000 Received: from VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::804c:a5e0:d962:5c26]) by VI1PR0501MB2863.eurprd05.prod.outlook.com ([fe80::804c:a5e0:d962:5c26%18]) with mapi id 15.20.0407.012; Tue, 16 Jan 2018 13:26:31 +0000 From: Meny Yossefi To: "Somayajulu, David" , "freebsd-net@FreeBSD.org" Subject: RE: Questions on OFED in FreeBSD Thread-Topic: Questions on OFED in FreeBSD Thread-Index: AdOJc7a+98khuLNQTECXfqqy4dh8zADjo7gQAEfgqvAAAYpMgAAkt4bw Date: Tue, 16 Jan 2018 13:26:31 +0000 Message-ID: References: , <76b44ed7365a49ebb427f4c27ef752ed@AM5PR0502MB2916.eurprd05.prod.outlook.com> In-Reply-To: <76b44ed7365a49ebb427f4c27ef752ed@AM5PR0502MB2916.eurprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=menyy@mellanox.com; x-originating-ip: [193.47.165.251] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VI1PR0501MB2061; 7:47TltEJEwZWW5aBKk3GGIvsfl6i+GOvSbUuvPZba8/Dhudx5tO0YjBqxa89Mbe1+JEQRjeTW+khUP5U2zXkFMB0A97a/xTmrSjIpllKikuy7+x0R4cic4r6v3bsOr8qdIKOtI9Z/aIRT6I9HtfHKEfietAEAqbhitdY2yPzO8YoCk9Mvw68JP6Z/PtBq/nbngQARKwwKm+VbVFphV+s5OuQhX9lmX8iOx0vLjEpAQ/jP7wT3BIYdWbkCmny/sgoy x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 628da695-76c9-4fc3-4c77-08d55ce4c1be x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(48565401081)(2017052603307)(7153060)(7193020); SRVR:VI1PR0501MB2061; x-ms-traffictypediagnostic: VI1PR0501MB2061: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(189930954265078)(45079756050767); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231023)(944501161)(6055026)(6041268)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:VI1PR0501MB2061; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:VI1PR0501MB2061; x-forefront-prvs: 0554B1F54F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(346002)(39860400002)(366004)(39380400002)(396003)(376002)(13464003)(199004)(189003)(25786009)(2950100002)(8676002)(55016002)(5660300001)(81156014)(6306002)(9686003)(86362001)(53936002)(81166006)(8936002)(102836004)(53546011)(6506007)(2900100001)(76176011)(99286004)(59450400001)(2501003)(7696005)(316002)(33656002)(110136005)(93886005)(229853002)(68736007)(5250100002)(26005)(7736002)(14454004)(74316002)(66066001)(305945005)(97736004)(3660700001)(3280700002)(45080400002)(966005)(6436002)(2906002)(3846002)(6116002)(105586002)(6246003)(478600001)(106356001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0501MB2061; H:VI1PR0501MB2863.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: m/iD3HCxv6hDbVJRqR09kFhpHXGMpJ/NvRPUrn/Fn7os41jTINzBm+Ha6Ayqxiv0N5esRTYMwOiaX1Y6MNFvqw== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-Network-Message-Id: 628da695-76c9-4fc3-4c77-08d55ce4c1be X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jan 2018 13:26:31.4941 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0501MB2061 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 16 Jan 2018 13:26:40 -0000 Hi David,=20 I think there's a misunderstanding here. Let me try and clear it. First OFED version introduced in FreeBSD9 was indeed ofed-1.5.3.=20 Future updates were based on Linux kernel and not the OpenFabrics versionin= g system. FreeBSD11 should currently have something similar to Linux v3.10 if I'm not= mistaken. Last big update in FreeBSD12 was based on Linux v4.9. Hopefully we can MFC it completely to FreeBSD11-STABLE. Last but not least - Yes, HEAD supports RoCEv2. Meny Hi Meny, Thanks a lot for the reply and the information. I have couple of additional questions. > 4. Am I correct that the OFED version on FreeBSD 11 is 1.5.3 ? >[MY] No. We did an upgrade in FreeBSD11 a while back. If I'm not mistaken,= FreeBSD11's OFED is currently based on version 2.0+ As per https://emea01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2F= downloads.openfabrics.org%2FOFED%2F&data=3D02%7C01%7Cfreebsd-commits-tracke= r%40mellanox.com%7Ca9533172edf24431e8a308d55c3f128f%7Ca652971c7d2e4d9ba6a4d= 149256f461b%7C0%7C1%7C636516348321604768&sdata=3Dit2anKZ%2FjPBnUJl%2FH3cfaN= 15h%2Fps12F4CR%2B3zETyNIE%3D&reserved=3D0 the version following OFED versi= on 1.5.4 is 3.2. Just curious what 2.0+ version is ? Am I correct that HEAD supports RoCE v2 ? Thanks David S. (davidcs@freebsd.org) -----Original Message----- From: Meny Yossefi [mailto:menyy@mellanox.com] Sent: Sunday, January 14, 2018 2:11 AM To: Somayajulu, David ; freebsd-net@freebsd.or= g Subject: RE: Questions on OFED in FreeBSD Hi David, Answers embedded below. -Meny -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of Somayajulu, David Sent: Tuesday, January 09, 2018 8:08 PM To: freebsd-net@freebsd.org Subject: Questions on OFED in FreeBSD Hi, 1. Is RoCE v2 supported of FreeBSD 11 release or 11_stable ? [MY] Not currently, though we do have plans adding it in the near future 2. How does one figure out the OFED version in a FreeBSD kernel? [MY] Unfortunately, OFED version is not maintained. Some files do state a v= ersion, but I wouldn't trust that too much 3. Since OFED on HEAD is synced to Linux 4.9 in kernel.org, I presume th= at it is OFED version 4.8. Am I correct ? [MY] 4.9+ 4. Am I correct that the OFED version on FreeBSD 11 is 1.5.3 ? [MY] No. We did an upgrade in FreeBSD11 a while back. If I'm not mistaken, = FreeBSD11's OFED is currently based on version 2.0+ 5. Are there any plans to backport OFED from HEAD to Stable_11? [MY] Yes. Thanks David S. (davidcs@freebsd.org) _______________________________________________ freebsd-net@freebsd.org mailing list https://emea01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flists.= freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-net&data=3D02%7C01%7Cfreebsd-com= mits-tracker%40mellanox.com%7C1efc8fb3a42547b6e6cd08d5578bf8e5%7Ca652971c7d= 2e4d9ba6a4d149256f461b%7C0%7C0%7C636511181052323549&sdata=3D3Ct%2BqOx3U8Xv8= %2F4Zm2nlVOQb1CCX8qrNkwzsKB9RmMU%3D&reserved=3D0 To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list https://emea01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flists.= freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-net&data=3D02%7C01%7Cfreebsd-com= mits-tracker%40mellanox.com%7Ca9533172edf24431e8a308d55c3f128f%7Ca652971c7d= 2e4d9ba6a4d149256f461b%7C0%7C1%7C636516348321604768&sdata=3DHhml1ZYp%2BDNdN= CYmGI%2BE07AD8dFUEp%2F73INU1q7W6eI%3D&reserved=3D0 To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Wed Jan 17 21:56:26 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DC12EBA4AC for ; Wed, 17 Jan 2018 21:56:26 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 1B07C780 for ; Wed, 17 Jan 2018 21:56:26 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id 33so25440740qtv.1 for ; Wed, 17 Jan 2018 13:56:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=AXndqsrzv6aR7w3VkwveUQMJzrky2rMqkYZHL1MMlWM=; b=IGsgshXnFacDfva4N4pG4lsdOWQFouDjlSd+5ThRW0T1Tw7siVInZvSBvK+vTPi//K 7SC31k5aKKVutaDjpgxNjHzctedHiAMjbrOOU4cqa681MxU477B5w68UixLep0f56mGV 4ZX0BG5TuEpijx+PpTSWQZcdvjaQ+ZsKWM0P/QI1336y5HnaFiIj0AVG6ZaTeBVkWw/N 5b4SNws0Dn4gammjDehTpDv/iM4JB9spLaNf5u3J4e8ncloxWqCKDn9n80tfH5Y+Im5Y wphIutNq0TDi9RVVWSPNuVP+qjBmrfUWw0EsJoFSR4x7oT2zrrjdkd8xPubbZyljU1RH VVIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AXndqsrzv6aR7w3VkwveUQMJzrky2rMqkYZHL1MMlWM=; b=Fpz+yoQrEMiqWdiUyesNLAp0T6x+9EHEc2Su04BfSFoXT2JtPE81FiADRzC3x5t3WS UXtXMrSNU1ZP3rJ+mLszGWgYudkyxz8FE0g0uB0E7raiBweSYF9NdNjByqx+/cZao9PR umxnvKYDzxu//pwmcIWOqIe7ratgHdo7eukT5kwPZJvLXhfS34ohg+G6WprEoZy/dTD3 QCRxmaLfHlDrwEsRu/0RO+1ZgugOz9pluekz3xdNuymMYAK2nxSFXJYI1F4hDYfCofgV CpDSuDUvQkSt4b3YQIszudNJmI4nuN856tz6nZpMU4W+TKjdJoGx+hka7D4y39NO01lJ Cb8A== X-Gm-Message-State: AKwxytcuGZJVvxHQ+d3K3EIB/MOZ7QjHKZA5CDG9rzyLoMPZJvgDOK1v sSWNbxR5blJikKf8eHGdmaiN3nm7MNuspsfI0EWduQ== X-Google-Smtp-Source: ACJfBouKUqEt0yjCMOBZ6honmrImOwj3z1O3sK3XsOiu+sWFDIYUswAhacljFmTGjiu0sLW9Qa2LpWccKITeM2RJ1KE= X-Received: by 10.200.23.136 with SMTP id o8mr40386581qtj.255.1516226184890; Wed, 17 Jan 2018 13:56:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.39.136 with HTTP; Wed, 17 Jan 2018 13:56:24 -0800 (PST) From: Ryan Stone Date: Wed, 17 Jan 2018 16:56:24 -0500 Message-ID: Subject: Allowing a local subnet route to change to a different ifnet To: freebsd-net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 17 Jan 2018 21:56:26 -0000 I'm going to prefix this question by noting that I realize that the configuration that I am about to describe is quite nonsensical. Unfortunately, it seems that under older versions of FreeBSD (possibly FreeBSD 7-vintage), the configuration mostly "worked", and now at $WORK I am responsible for making the configuration continue to work in the future. The customer in this case is completely unwilling to modify their configuration. I have a customer that has configured two different IPs on the same subnet on two different interfaces. The behaviour that they want is that if the link on one of the two interfaces goes down, the route to that subnet will migrate to the other IP on the other interface as a quasi-failover behaviour. Under FreeBSD 7, we had a daemon that accomplished this by detecting the link loss and then using "route change" to move the route to the up interface. If the subnet in question was 192.168.1.0/24, for example, we could run "route change 192.1.68.1.0/24 -ifp em1" to migrate the route. Running on -head I run into two issues. The first comes out of r264986, which changes the behaviour of RTM_CHANGE. The code path changed significantly, but the part that impacts me is that now any RTM_CHANGE command with the gateway set NULL gets EINVAL immediately where previously it was allowed. I've hacked around this problem locally for testing purposes but I really don't understand the code well enough at this point to see what a real fix would look like. The second issue is quite complex. The root cause is that the routing code sets IFA_ROUTE on any ifaddr that has a local subnet route associated with it. If I don't migrate this flag to the new ifaddr, very bizarre behaviour follows. I've done a prototype that detects when this migration is needed in rtrequest1_fib_change() and it works, but IFA_ROUTE seems to otherwise be handled in individual L3 protocols like in and in6, so I'm worried that this is a layering violation. My patch looks like this: https://people.freebsd.org/~rstone/patches/route-change-subnet.diff My first, and most important question, is whether a patch that would allow a subnet route to be migrated to a different interface be something that would be acceptable in FreeBSD? If so, I need guidance on what a proper fix for both issues would look like so that I can implement fixes that I can upstream. Thanks, Ryan From owner-freebsd-net@freebsd.org Wed Jan 17 22:06:36 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EB59EBB06E for ; Wed, 17 Jan 2018 22:06:36 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 7788DF54 for ; Wed, 17 Jan 2018 22:06:35 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id a204so15654973lfa.2 for ; Wed, 17 Jan 2018 14:06:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=8g3fN0+moZeGW5zoVzxJ2d2Aeozxf7JfDNI55Zoql8k=; b=G6Q4PWp+ktUktOyseahb5TaXVLvRJOcadxZwEnvIf7WzV9AJiRMKOmLqQvohvGD4G7 ujsIDWEL8qjB/17SKneCuq+S9F/g34jyRLt9zhm0+z6Un4VZZfnaLiapGlP3XXqw3aEV e0IcAfqbVfMMtciF3vmPh2DitVqd70P2a6kjknXbbrjjT4waOug0T4+2TUxaqdCZGkgW r2nco0GL0W8yUI9WnLoRrepRntOcxr1Ak8liYk1R+blnSR5WjQLwGOoagGfjV9lCwbCA khm3tP4TNpVKoM4JpuvnP+yT882DE3ZrEtZwY2PsAfGjUZUly6TvlKP6csJdNW1VEIeg o5Yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=8g3fN0+moZeGW5zoVzxJ2d2Aeozxf7JfDNI55Zoql8k=; b=klh6Emqls8T3+SNUzvgU8RAJxa6cow1Yizw8Ngxv/DvXIC/mm/boRYGNKPEOp+MxDr nVPQAUuT5kEMx8IG/LBo71vTnlgLFQGcyk8vKTe8hINsfKbtzXdup0LQw/N4gh4QRyIC 9tP/okQTuM9xe/kWAq6ZRjdWaCm9pIo0lSuukOiB5ozIKQSDEhHT/FnCisrbL2XYmTu+ Dal7oHVqSqcWH7QUANsTtu3k6M3mAg/NU3SO83es5UhFhV23QMEwohwA+XjtFBWUqcRk wcIh3QqPxnzjN+SeryQe6Q8ZKwe3HnNfrhlR+kN0q2Ya6C3fbJxxZUauyj6zeLdvOJV3 B04w== X-Gm-Message-State: AKwxytfpaq5A4P34aVeWW3yMUx2fIIbLCgnPwxgpTNqE6BZIC/zg8Omi RLv8fhe/XoEsl6bHkRsZLq2itAZHoISpha5A+bA= X-Google-Smtp-Source: ACJfBov085vwi//hj7QfFHD8d5kldvl5kOnivwrdazKD1F8XS9vuFiLo9CjFZphLeYVZuDnxkwAiR861J2GuT9fEnzk= X-Received: by 10.25.151.209 with SMTP id z200mr11270305lfd.41.1516226793283; Wed, 17 Jan 2018 14:06:33 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.64.22 with HTTP; Wed, 17 Jan 2018 14:06:32 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Wed, 17 Jan 2018 15:06:32 -0700 X-Google-Sender-Auth: UDJ1ynVDgRBwrhTPeUanxpXD3z0 Message-ID: Subject: Re: Allowing a local subnet route to change to a different ifnet To: Ryan Stone Cc: freebsd-net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 17 Jan 2018 22:06:36 -0000 On Wed, Jan 17, 2018 at 2:56 PM, Ryan Stone wrote: > I'm going to prefix this question by noting that I realize that the > configuration that I am about to describe is quite nonsensical. > Unfortunately, it seems that under older versions of FreeBSD (possibly > FreeBSD 7-vintage), the configuration mostly "worked", and now at > $WORK I am responsible for making the configuration continue to work > in the future. The customer in this case is completely unwilling to > modify their configuration. > > I have a customer that has configured two different IPs on the same > subnet on two different interfaces. The behaviour that they want is > that if the link on one of the two interfaces goes down, the route to > that subnet will migrate to the other IP on the other interface as a > quasi-failover behaviour. Under FreeBSD 7, we had a daemon that > accomplished this by detecting the link loss and then using "route > change" to move the route to the up interface. If the subnet in > question was 192.168.1.0/24, for example, we could run "route change > 192.1.68.1.0/24 -ifp em1" to migrate the route. > > Running on -head I run into two issues. The first comes out of > r264986, which changes the behaviour of RTM_CHANGE. The code path > changed significantly, but the part that impacts me is that now any > RTM_CHANGE command with the gateway set NULL gets EINVAL immediately > where previously it was allowed. I've hacked around this problem > locally for testing purposes but I really don't understand the code > well enough at this point to see what a real fix would look like. > > The second issue is quite complex. The root cause is that the routing > code sets IFA_ROUTE on any ifaddr that has a local subnet route > associated with it. If I don't migrate this flag to the new ifaddr, > very bizarre behaviour follows. I've done a prototype that detects > when this migration is needed in rtrequest1_fib_change() and it works, > but IFA_ROUTE seems to otherwise be handled in individual L3 protocols > like in and in6, so I'm worried that this is a layering violation. My > patch looks like this: > https://people.freebsd.org/~rstone/patches/route-change-subnet.diff > > > My first, and most important question, is whether a patch that would > allow a subnet route to be migrated to a different interface be > something that would be acceptable in FreeBSD? If so, I need guidance > on what a proper fix for both issues would look like so that I can > implement fixes that I can upstream. > > Thanks, > Ryan > I'm sorry for you Ryan; this sounds like a doozy. I know you said that the customer is unwilling to change, but would they consider using a lagg(4) interface? Using lagg with laggproto=failover is designed to solve exactly this problem. They wouldn't have to recable anything, and they could keep their single IP address. If not, you should see PR 189088; I think it's related. -Alan From owner-freebsd-net@freebsd.org Wed Jan 17 22:23:16 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6C0BEBBDAE for ; Wed, 17 Jan 2018 22:23:16 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::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 AD8A61CC1; Wed, 17 Jan 2018 22:23:16 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x235.google.com with SMTP id b198so19956179iof.6; Wed, 17 Jan 2018 14:23:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hsXSEi/fv6pfnYriUD4qTQcbSMOA+yTXo5UIcwLMvQc=; b=F02axrOszy4YrMwb6IiYe7O29xZgckCeJBZg7x62eQTs3LG/Le3frDEhcws0gWNCMU jPL8jnmRc58JNUIwA6MneOlF3PW0/vGO4YgAlkF97IRKdBwBvjg25OXhqlNPclJvK2VD O7rftOj2r0ahobFiIQX9+BiRsO6wJfkJxVUsSA4f3PQBwmgBy08EOzfwfTAc+zZj5QpL FBhwGESN/Uf5HBRz4lQE9q+TnqYlavDpjHqWtWDbkB2Z1nFNP6Df5PkMbtTE7V8TeRXZ gs7cY92zz0wb7v1MXga3J0+Uuo46uJJ8G1IRU3eIDUpCt1cSnwovai9PeWYof91KKHE1 KiOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hsXSEi/fv6pfnYriUD4qTQcbSMOA+yTXo5UIcwLMvQc=; b=DFmn0R23rkfaM/8siAqgwBc1b85fOhD4f1t9ga1bF6Qw0ieqq/XU4eYMxzYMgwnyEd mWOS0D09f0IN1QShMV/dX+iVmBYeUHyShWbth008BdmNfPRQ/0jgUrjLpEnHjwWjLbdN DJiafAwGUiUF7NDbVR2gyCYEz/UE+arGAqlh9/lGSqh3OIQHEu1D0tiG8lX7Q3iJx5TS apWEVj+3J5VH8OjF3s8BobED0xvFwwLKgaI5+Gldx1Mmh25wQoHrvbP2Sa5wtq+bGVGE FAKRLNhQ8S8iNFUhiECxJt97FEDhQc9tIehsXsqJGsJ2ClYkgVjEeuFMXEEV2d/zFfry jRlw== X-Gm-Message-State: AKwxytfvo3Vmiv2JNZZUOQ9GeeMEMA7GncRcQrtj8RDQ9l6EuNEjb29O Z5NHKJGV5exugoB91wqIgIZQG4nsca1ers2ZNWo= X-Google-Smtp-Source: ACJfBoshC011z/diMZhWvOLQ6tDI2qjcXQaw4OVqWlLOW1ugYkpsFoLnjjtQi/LiYWvCYTxpyZl+Bai/B5pFK6yrhM8= X-Received: by 10.107.55.132 with SMTP id e126mr45302604ioa.32.1516227795683; Wed, 17 Jan 2018 14:23:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.159.21 with HTTP; Wed, 17 Jan 2018 14:23:15 -0800 (PST) In-Reply-To: References: From: Adam Vande More Date: Wed, 17 Jan 2018 16:23:15 -0600 Message-ID: Subject: Re: Allowing a local subnet route to change to a different ifnet To: Alan Somers Cc: Ryan Stone , freebsd-net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 17 Jan 2018 22:23:17 -0000 On Wed, Jan 17, 2018 at 4:06 PM, Alan Somers wrote: > I'm sorry for you Ryan; this sounds like a doozy. I know you said that the > customer is unwilling to change, but would they consider using a lagg(4) > interface? Using lagg with laggproto=failover is designed to solve exactly > this problem. They wouldn't have to recable anything, and they could keep > their single IP address. > What single IP address and what does cabling have to do with it? -- Adam From owner-freebsd-net@freebsd.org Thu Jan 18 00:10:07 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81412EC18A9 for ; Thu, 18 Jan 2018 00:10:07 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 5B92D69D80 for ; Thu, 18 Jan 2018 00:10:06 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w0I09wAP065399; Wed, 17 Jan 2018 16:09:58 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w0I09vD7065398; Wed, 17 Jan 2018 16:09:57 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201801180009.w0I09vD7065398@pdx.rh.CN85.dnsmgr.net> Subject: Re: Allowing a local subnet route to change to a different ifnet In-Reply-To: To: Ryan Stone Date: Wed, 17 Jan 2018 16:09:57 -0800 (PST) CC: freebsd-net X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Jan 2018 00:10:07 -0000 > I'm going to prefix this question by noting that I realize that the > configuration that I am about to describe is quite nonsensical. > Unfortunately, it seems that under older versions of FreeBSD (possibly > FreeBSD 7-vintage), the configuration mostly "worked", and now at > $WORK I am responsible for making the configuration continue to work > in the future. The customer in this case is completely unwilling to > modify their configuration. > > I have a customer that has configured two different IPs on the same > subnet on two different interfaces. The behaviour that they want is > that if the link on one of the two interfaces goes down, the route to > that subnet will migrate to the other IP on the other interface as a > quasi-failover behaviour. Under FreeBSD 7, we had a daemon that > accomplished this by detecting the link loss and then using "route > change" to move the route to the up interface. If the subnet in > question was 192.168.1.0/24, for example, we could run "route change > 192.1.68.1.0/24 -ifp em1" to migrate the route. "route change 192.1.68.1.0/24 -ifp em1" does not appear to be valid syntax to me, -ifp is not a route option? Did you mean -interface? And I think this well work if you use the local IP of the em1 interface for the gateway? That should get past the null check > > Running on -head I run into two issues. The first comes out of > r264986, which changes the behaviour of RTM_CHANGE. The code path > changed significantly, but the part that impacts me is that now any > RTM_CHANGE command with the gateway set NULL gets EINVAL immediately > where previously it was allowed. I've hacked around this problem > locally for testing purposes but I really don't understand the code > well enough at this point to see what a real fix would look like. > > The second issue is quite complex. The root cause is that the routing > code sets IFA_ROUTE on any ifaddr that has a local subnet route > associated with it. If I don't migrate this flag to the new ifaddr, > very bizarre behaviour follows. I've done a prototype that detects > when this migration is needed in rtrequest1_fib_change() and it works, > but IFA_ROUTE seems to otherwise be handled in individual L3 protocols > like in and in6, so I'm worried that this is a layering violation. My > patch looks like this: > https://people.freebsd.org/~rstone/patches/route-change-subnet.diff > > > My first, and most important question, is whether a patch that would > allow a subnet route to be migrated to a different interface be > something that would be acceptable in FreeBSD? If so, I need guidance > on what a proper fix for both issues would look like so that I can > implement fixes that I can upstream. >From a fundemental standpoint this should work, that it is now broken is a regression that needs fixed. You may also run into issues with the kernel maintain_loopback_route functions. > Thanks, > Ryan -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Thu Jan 18 00:31:15 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FC06EC2A1C for ; Thu, 18 Jan 2018 00:31:15 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F1C496B061 for ; Thu, 18 Jan 2018 00:31:14 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id F25A425D3860; Thu, 18 Jan 2018 00:31:05 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 4578AD1F827; Thu, 18 Jan 2018 00:31:05 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 8xC8yfY3efpV; Thu, 18 Jan 2018 00:31:03 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 2616CD1F826; Thu, 18 Jan 2018 00:31:02 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Rodney W. Grimes" Cc: "Ryan Stone" , freebsd-net Subject: Re: Allowing a local subnet route to change to a different ifnet Date: Thu, 18 Jan 2018 00:31:03 +0000 X-Mailer: MailMate (2.0BETAr6103) Message-ID: In-Reply-To: <201801180009.w0I09vD7065398@pdx.rh.CN85.dnsmgr.net> References: <201801180009.w0I09vD7065398@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Jan 2018 00:31:15 -0000 On 18 Jan 2018, at 0:09, Rodney W. Grimes wrote: >> I have a customer that has configured two different IPs on the same >> subnet on two different interfaces. The behaviour that they want is >> that if the link on one of the two interfaces goes down, the route to >> that subnet will migrate to the other IP on the other interface as a >> quasi-failover behaviour. Under FreeBSD 7, we had a daemon that >> accomplished this by detecting the link loss and then using "route >> change" to move the route to the up interface. If the subnet in >> question was 192.168.1.0/24, for example, we could run "route change >> 192.1.68.1.0/24 -ifp em1" to migrate the route. > > "route change 192.1.68.1.0/24 -ifp em1" does not appear to be > valid syntax to me, -ifp is not a route option? > Did you mean -interface? The proper syntax should be route change -ifp but that’s not the issue (the other syntax works or used to work but not according to specification). >> Running on -head I run into two issues. The first comes out of >> r264986, which changes the behaviour of RTM_CHANGE. The code path >> changed significantly, but the part that impacts me is that now any >> RTM_CHANGE command with the gateway set NULL gets EINVAL immediately >> where previously it was allowed. I've hacked around this problem >> locally for testing purposes but I really don't understand the code >> well enough at this point to see what a real fix would look like. Running route -n monitor & while doing the change I get very weird results (without your patch). [ignore the patch for the moment] >> My first, and most important question, is whether a patch that would >> allow a subnet route to be migrated to a different interface be >> something that would be acceptable in FreeBSD? Yes. >> If so, I need guidance >> on what a proper fix for both issues would look like so that I can >> implement fixes that I can upstream. > > From a fundemental standpoint this should work, > that it is now broken is a regression that needs fixed. +1 /bz From owner-freebsd-net@freebsd.org Thu Jan 18 13:11:22 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBD88E797FB; Thu, 18 Jan 2018 13:11:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B96086C90A; Thu, 18 Jan 2018 13:11:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id ade421a3 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 18 Jan 2018 13:11:13 +0000 (UTC) From: Greg V Subject: mlx4 weird error "Failed to map EQ context memory" after update To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> Date: Thu, 18 Jan 2018 16:11:11 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 18 Jan 2018 13:11:22 -0000 Hi. I've upgraded CURRENT from December 19 (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) to today (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) and my Mellanox ConnectX-2 network card stopped working: mlx4_core0: mem 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on pci7 mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) mlx4_core: Initializing mlx4_core mlx4_core0: command 0xffa failed: fw status = 0x1 mlx4_core0: Failed to map EQ context memory, aborting device_attach: mlx4_core0 attach returned 12 Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does work fine! Reverting all mlx4 changes between then and now (no big changes, mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 module with CC=clang50 does not help. What happened?! From owner-freebsd-net@freebsd.org Thu Jan 18 18:05:09 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A2D7EBA12F for ; Thu, 18 Jan 2018 18:05:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E3945796AA for ; Thu, 18 Jan 2018 18:05:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D7ED524D94 for ; Thu, 18 Jan 2018 18:05:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0II58e7063486 for ; Thu, 18 Jan 2018 18:05:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0II5885063484 for freebsd-net@FreeBSD.org; Thu, 18 Jan 2018 18:05:08 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224961] VLAN ID 0 Not Supported Date: Thu, 18 Jan 2018 18:05:08 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: johnllyon@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.25 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, 18 Jan 2018 18:05:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224961 --- Comment #5 from johnllyon@gmail.com --- (In reply to Eugene Grosbein from comment #3) I think therein lies the problem. We are not recognizing frames tagged as = vlan 0 as being untagged. On the flip side, it seems that if we detect that we = are receiving frames tagged with vlan 0, we should be transmitting frames tagged with vlan 0 as well (but we don't seem to be).=20=20 I like the idea of Netgraph as a work around as it would allow me to both s= end and receive frames tagged as vlan 0. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jan 19 09:02:09 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 815A8ECBE0E; Fri, 19 Jan 2018 09:02:09 +0000 (UTC) (envelope-from bhughes@freebsd.org) 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 5359279039; Fri, 19 Jan 2018 09:02:08 +0000 (UTC) (envelope-from bhughes@freebsd.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4D7D420DED; Fri, 19 Jan 2018 04:02:07 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 19 Jan 2018 04:02:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=pNoaOH 8hCvQoGbe7JmXmMmbbCzAZZSqzVbnbuH1aVDE=; b=cZLpojnRblSMiXtqWDoMnM evAPVy22JciSlMvmb/rApwKsQig8P5ylOoBPQjGQnIr1gRED2vB76YK+tGE2ILMx qSmO0go1bLvRJndXtetJdhsF1A6TJmYi/4PK2gjlFiTmscCJC9pdDfbWVrXfUQZP cwJ6MjDgKtXSw+ver7drUjkhro/CaZW5KM4DYvWByLM/BM+W6QKV5TzrUTVOr3Ol UkNoew7P4dJI92RzaHsUsz3kUf412Zki2vcrcFfOG3/FdOMA4jV4GydGFMWY/D0Q Ks8fuDPY6ALZJnmDp5m1NZA1vFXeTfB8uX74Eq2L4q4UY9gqCyDZa6/TCQVDEd7w == X-ME-Sender: Received: from hayseed.lan (90.89-11-136.nextgentel.com [89.11.136.90]) by mail.messagingengine.com (Postfix) with ESMTPA id E519C2449D; Fri, 19 Jan 2018 04:02:05 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Panic with recent -CURRENT kernel in EC2 From: "Bradley T. Hughes" In-Reply-To: <01000160ec74f91e-2181241b-7d3f-4740-88d5-3b0559cecd09-000000@email.amazonses.com> Date: Fri, 19 Jan 2018 10:02:04 +0100 Cc: "Pieper, Jeffrey E" , "freebsd-cloud@freebsd.org" , "freebsd-net@freebsd.org" , Eric Joyner Content-Transfer-Encoding: quoted-printable Message-Id: <551A3441-609F-49BA-841B-2040E14D411C@freebsd.org> References: <01000160e9f7ae62-92937548-d46c-4687-87c0-2205119d5132-000000@email.amazonses.com> <191060CB-F1F8-4E34-8191-99EB7B28597C@intel.com> <01000160ec74f91e-2181241b-7d3f-4740-88d5-3b0559cecd09-000000@email.amazonses.com> To: Colin Percival X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Jan 2018 09:02:09 -0000 > On 12 Jan 2018, at 23:19, Colin Percival wrote: >=20 > On 01/12/18 08:16, Pieper, Jeffrey E wrote: >> Hrm=E2=80=A6 >>=20 >>> taskqgroup_attach_cpu: setaffinity failed: 22 >>> taskqgroup_attach_cpu: setaffinity failed: 22 >>=20 >> Is this a fresh snapshot? That should have been fixed in >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D327013 . = Can you >> please file a bug on this? This looks like an iflib issue. >=20 > I can confirm that this happens with the 12.0-CURRENT r327524 snasphot = (on a > c4.8xlarge EC2 instance, in case it matters). Indeed. I still get this with r328126 as well. I will file a PR about = it. -- Bradley T. Hughes bradleythughes@fastmail.fm From owner-freebsd-net@freebsd.org Fri Jan 19 09:07:16 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE1B2ECC1A8; Fri, 19 Jan 2018 09:07:16 +0000 (UTC) (envelope-from bhughes@freebsd.org) 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 AF8A379493; Fri, 19 Jan 2018 09:07:16 +0000 (UTC) (envelope-from bhughes@freebsd.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8B7C920C0F; Fri, 19 Jan 2018 04:07:15 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 19 Jan 2018 04:07:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=zql8VB tIfHqE2seQNyKdKnSah3GLHZyK9bJM7OULUnI=; b=NnQk7Q+qyoSvACQ7nURBA+ HN2t01LuSk23ugYdPYDOvLbjeNfj54aHce+jtxny1uaa1WqCOoAugnenrFSIEvj9 agw4HJU15stA5OlONRVruH/OIFeZJhlc6K/qsQPTTOZZydxoqJ8nKdXj0H0RBrtx 4wA63yBXZacjarSN+immtt6mhMxFECvBe56hbGTozI9UhwdWwYe15Pc0KH9NUb1s /K3BdPGSs5IoCRjTWJfuHhhEM5OARV0DT84B3Ln1Y72tqzvECS4u9x16bhUCUNeR FX5Y1IOfj4c7GO3cINO2vHSZv4Ude/I4GCvtwnCiUvwO1bGb2xA6w3Gu9xhyjsDw == X-ME-Sender: Received: from hayseed.lan (90.89-11-136.nextgentel.com [89.11.136.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 3823D240DE; Fri, 19 Jan 2018 04:07:14 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Panic with recent -CURRENT kernel in EC2 From: "Bradley T. Hughes" In-Reply-To: <551A3441-609F-49BA-841B-2040E14D411C@freebsd.org> Date: Fri, 19 Jan 2018 10:07:12 +0100 Cc: "Pieper, Jeffrey E" , "freebsd-net@freebsd.org" , Eric Joyner , "freebsd-cloud@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <01000160e9f7ae62-92937548-d46c-4687-87c0-2205119d5132-000000@email.amazonses.com> <191060CB-F1F8-4E34-8191-99EB7B28597C@intel.com> <01000160ec74f91e-2181241b-7d3f-4740-88d5-3b0559cecd09-000000@email.amazonses.com> <551A3441-609F-49BA-841B-2040E14D411C@freebsd.org> To: Colin Percival X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Jan 2018 09:07:17 -0000 > On 19 Jan 2018, at 10:02, Bradley T. Hughes = wrote: >=20 >> On 12 Jan 2018, at 23:19, Colin Percival = wrote: >>=20 >> On 01/12/18 08:16, Pieper, Jeffrey E wrote: >>> Hrm=E2=80=A6 >>>=20 >>>> taskqgroup_attach_cpu: setaffinity failed: 22 >>>> taskqgroup_attach_cpu: setaffinity failed: 22 >>>=20 >>> Is this a fresh snapshot? That should have been fixed in >>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D327013 . = Can you >>> please file a bug on this? This looks like an iflib issue. >>=20 >> I can confirm that this happens with the 12.0-CURRENT r327524 = snasphot (on a >> c4.8xlarge EC2 instance, in case it matters). >=20 > Indeed. I still get this with r328126 as well. I will file a PR about = it. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225312 -- Bradley T. Hughes bhughes@freebsd.org From owner-freebsd-net@freebsd.org Fri Jan 19 09:57:23 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDE42ECDD2C; Fri, 19 Jan 2018 09:57:23 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 85A587ACFC; Fri, 19 Jan 2018 09:57:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 663D026009E; Fri, 19 Jan 2018 10:57:19 +0100 (CET) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Greg V , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Hans Petter Selasky Message-ID: Date: Fri, 19 Jan 2018 10:54:27 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Jan 2018 09:57:23 -0000 On 01/18/18 14:11, Greg V wrote: > Hi. I've upgraded CURRENT from December 19 > (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) to > today > (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) > and my Mellanox ConnectX-2 network card stopped working: > > mlx4_core0: mem 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff > irq 32 at device 0.0 on pci7 > mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) > mlx4_core: Initializing mlx4_core > mlx4_core0: command 0xffa failed: fw status = 0x1 > mlx4_core0: Failed to map EQ context memory, aborting > device_attach: mlx4_core0 attach returned 12 > > > Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does > work fine! > > Reverting all mlx4 changes between then and now (no big changes, mostly > just the 1 << 31 thing from D13858) and rebuilding the mlx4 module with > CC=clang50 does not help. > > What happened?! Hi, Can you do: objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt And diff the text result between working and non-working ko's. Can you also make sure that /boot/modules does not contain anything *mlx4* ? --HPS From owner-freebsd-net@freebsd.org Fri Jan 19 17:12:00 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C197CEBD606 for ; Fri, 19 Jan 2018 17:12:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7ADB6A32E for ; Fri, 19 Jan 2018 17:12:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9CFE111512 for ; Fri, 19 Jan 2018 17:12:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0JHC0Jb087456 for ; Fri, 19 Jan 2018 17:12:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0JHC0nb087455 for freebsd-net@FreeBSD.org; Fri, 19 Jan 2018 17:12:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 225312] panic: Assertion if_getdrvflags(ifp) == i failed at /usr/src/sys/net/iflib.c:2201 Date: Fri, 19 Jan 2018 17:12: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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org 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: quoted-printable 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.25 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, 19 Jan 2018 17:12:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225312 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jan 19 21:01:52 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0E78EC82C1 for ; Fri, 19 Jan 2018 21:01:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 983357514E for ; Fri, 19 Jan 2018 21:01:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8D9701354F for ; Fri, 19 Jan 2018 21:01:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0JL1qvC081644 for ; Fri, 19 Jan 2018 21:01:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0JL1qvD081625 for freebsd-net@FreeBSD.org; Fri, 19 Jan 2018 21:01:52 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224218] Kernel panic in SCTP/IpV6 server mode Date: Fri, 19 Jan 2018 21:01: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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tuexen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.25 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, 19 Jan 2018 21:01:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224218 --- Comment #24 from Michael Tuexen --- OK, I'll reduce the stack usage... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jan 19 21:03:03 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92E22EC83A0 for ; Fri, 19 Jan 2018 21:03:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 786BE753E1 for ; Fri, 19 Jan 2018 21:03:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6E09C1357D for ; Fri, 19 Jan 2018 21:03:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0JL33G3021692 for ; Fri, 19 Jan 2018 21:03:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0JL33Nx021683 for freebsd-net@FreeBSD.org; Fri, 19 Jan 2018 21:03:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224218] Kernel panic in SCTP/IpV6 server mode Date: Fri, 19 Jan 2018 21:03: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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tuexen@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: tuexen@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.25 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, 19 Jan 2018 21:03:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224218 Michael Tuexen changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |tuexen@freebsd.org Status|Open |In Progress --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jan 19 21:32:22 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84A79EC9C5D for ; Fri, 19 Jan 2018 21:32:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AF3F76F72 for ; Fri, 19 Jan 2018 21:32:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5FFC2139B4 for ; Fri, 19 Jan 2018 21:32:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0JLWMVT018559 for ; Fri, 19 Jan 2018 21:32:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0JLWMCs018558 for freebsd-net@FreeBSD.org; Fri, 19 Jan 2018 21:32:22 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 225312] panic: Assertion if_getdrvflags(ifp) == i failed at /usr/src/sys/net/iflib.c:2201 Date: Fri, 19 Jan 2018 21:32:22 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: erj@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.25 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, 19 Jan 2018 21:32:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225312 Eric Joyner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erj@freebsd.org --- Comment #2 from Eric Joyner --- Looking at iflib.c, it appears iflib_init_locked() expects the driver-speci= fic init function to not set any driver flags, but ixv_if_init() in if_ixv.c (t= he function called as IFDI_INIT() in iflib_init_locked()) modifies those flags, which I think causes the MPASS() to fail. So, I think this last bit in ixv_if_init() needs to be removed: /* Now inform the stack we're ready */ ifp->if_drv_flags |=3D IFF_DRV_RUNNING; ifp->if_drv_flags &=3D ~IFF_DRV_OACTIVE; --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Jan 19 21:52:11 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3755ECAA4E; Fri, 19 Jan 2018 21:52:11 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::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 C11E97797B; Fri, 19 Jan 2018 21:52:11 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id e2so7419348qti.0; Fri, 19 Jan 2018 13:52:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xILgYEqRwmFxrKnvLmu/txJCeJGSgGv4P9Ig8P5ZrIM=; b=ET7Wsd1gsBXc3p9iGcKQZSS/XreGcMZJwfegRCpfdhLey6fZ6hS80Sr+eHALj2NeWz 1rbCcym72if6W0I4Z+oBFwfQEoQfvEiBB/Y9Ikcz0KKPmUSN8m0Uu154DZzoZggo3XzE Ad8eGK3jIZJ4VSSH0tLrUYe193fXuBkkkjfPwHOty7fmnYj+lQyWA2m6HoTE9GRPhVtD Kbkalr4Xa51Ftomi4FesEcQCg+rXjc1X2dHLZdY0ZLmDuIupj6KLCfarrc96V50TAFyj ADzf2Cm0HqBOxSQMP575ml6r9Vu+KKZIhYpJz1SiuzA0vJKDkbizPwJX/vyUgLFnOViN NW5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xILgYEqRwmFxrKnvLmu/txJCeJGSgGv4P9Ig8P5ZrIM=; b=VHRAfGtWHLAfXTWw71BEM1cxUAnlLKfuz98O4H01d/gBBhLLuSfx1GMVquKqrqIILa KApGAZZWA7rvFVpn6eqk0qF7YkiSmK1JfkK8Q/EttdXkiK2WJNr2kFSIxRvfrbqj9nOk ucV/vMzd+2G4dX5rgQSdWiTqsDHiEo78blsU9/pu7Rs9Q6udXRln8jHlaqRb35qCX8wa Rh4W2cR3BY+OyJlAD8SyHmXJiyk7y09DQCNnli983oHBWTjGhpoELDoX93ISBcFe6b0l vcuNA1YdEEiEYUxz0Bv1qV0T1knndOziY7vVqbh6hvf9UPnECn712TdeGdbvrW7nKhyt Kp0w== X-Gm-Message-State: AKwxytekbJa+o8Q50/hCt9QxkjiaiHuRho5P9zhKneJxiLBa2GlCD71q Qryg6IE2jE/Hd6jz8IGc2sLF1eAEV4pKggDrN9VXGw== X-Google-Smtp-Source: ACJfBotJfGbIcbO80C0s9ODMA4vCBgxgwQFy5F7SaC37tKZYP2Ji4H29u39zlij7BHu3+qh68+gE/2Yi8kD5X5FxdSg= X-Received: by 10.200.64.219 with SMTP id f27mr32863405qtm.227.1516398730240; Fri, 19 Jan 2018 13:52:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.54.2 with HTTP; Fri, 19 Jan 2018 13:52:09 -0800 (PST) From: Ryan Stone Date: Fri, 19 Jan 2018 16:52:09 -0500 Message-ID: Subject: 3 ARP cache related reviews To: freebsd-net , "" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Jan 2018 21:52:12 -0000 I've opened 3 phabricator reviews fixing issues with the inpcb llentry caching. https://reviews.freebsd.org/D13988 This fix invalidates the llentry cache after the L3 route cache was invalidated by the routing table's generation count incrementing. Without this fix existing connections would continue to use stale L2 headers after the routing table was updated. I tried a simple test where I added a new route that would change the routing of an active TCP connection and confirmed with tcpdump that without this fix, the stack continues to use the old src/dst MAC for the original route. This caused the traffic to be blackholed at the new gateway as the MAC did not match. https://reviews.freebsd.org/D13989 This is a simple cleanup of the inpcb cache invalidation. Rather than copy-and-pasting the separate invalidation of the L2 cache and the L3 cache, I move the invalidation into a single macro and invoke it everywhere that needs to drop the cache. This will hopefully prevent future bugs like D13988 from occurring in new code. https://reviews.freebsd.org/D13990 This fixes an issue where the inpcb L2 cache was not updated following a change to a route's gateway. This led the connection to continue to use the old gateway. If the old gateway stopping routing traffic this would cause the connection to be blackholed. My fix here is more heavy-handed than it needs to be, as I just increment the route table generation count, which will cause all connections to drop their L2 and L3 caches. This could be made more selective by adding a generation count to each route entry, but I don't believe that route table modifications will happen frequently enough for anybody to care. Please speak up if you believe differently. If you're interested in one or more of these changes, please subscribe yourself to the reviews. I don't subscribe mailing lists to reviews to reduce the spam on the lists. Thanks, Ryan From owner-freebsd-net@freebsd.org Fri Jan 19 22:13:01 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3400DECB9A3 for ; Fri, 19 Jan 2018 22:13:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A2F478AB7 for ; Fri, 19 Jan 2018 22:13:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0F88713F56 for ; Fri, 19 Jan 2018 22:13:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0JMD0B0019861 for ; Fri, 19 Jan 2018 22:13:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0JMD05D019860 for freebsd-net@FreeBSD.org; Fri, 19 Jan 2018 22:13:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224218] Kernel panic in SCTP/IpV6 server mode Date: Fri, 19 Jan 2018 22:13:01 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: tuexen@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.25 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, 19 Jan 2018 22:13:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224218 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-net@FreeBSD.org, | |rgrimes@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Fri Jan 19 23:17:31 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55025ECE978; Fri, 19 Jan 2018 23:17:31 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4046A7BD3A; Fri, 19 Jan 2018 23:17:30 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 5d72516e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 19 Jan 2018 23:17:22 +0000 (UTC) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Hans Petter Selasky , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Greg V Message-ID: Date: Sat, 20 Jan 2018 02:17:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 19 Jan 2018 23:17:31 -0000 On 01/19/2018 12:54, Hans Petter Selasky wrote: > On 01/18/18 14:11, Greg V wrote: >> Hi. I've upgraded CURRENT from December 19 >> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) >> to today >> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) >> and my Mellanox ConnectX-2 network card stopped working: >> >> mlx4_core0: mem >> 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on pci7 >> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) >> mlx4_core: Initializing mlx4_core >> mlx4_core0: command 0xffa failed: fw status = 0x1 >> mlx4_core0: Failed to map EQ context memory, aborting >> device_attach: mlx4_core0 attach returned 12 >> >> >> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does >> work fine! >> >> Reverting all mlx4 changes between then and now (no big changes, >> mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 >> module with CC=clang50 does not help. >> >> What happened?! > > Hi, > > Can you do: > > objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt > objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt > > And diff the text result between working and non-working ko's. That results in 180883 lines (9.2 megabytes) of diff for mlx4.ko. The CC=clang50 one is only a bit better at 7.6 MB :( > Can you also make sure that /boot/modules does not contain anything > *mlx4* ? Yeah, it did not contain that. From owner-freebsd-net@freebsd.org Sat Jan 20 01:38:16 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CED4ED51FA for ; Sat, 20 Jan 2018 01:38:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33105814CF for ; Sat, 20 Jan 2018 01:38:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 22AAC15B78 for ; Sat, 20 Jan 2018 01:38:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0K1cGiR069483 for ; Sat, 20 Jan 2018 01:38:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0K1cGgC069482 for freebsd-net@FreeBSD.org; Sat, 20 Jan 2018 01:38:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 225325] RealTek 8169 network devices don't seem to work with memory mapped registers Date: Sat, 20 Jan 2018 01:38: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: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org 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: quoted-printable 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.25 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, 20 Jan 2018 01:38:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225325 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |patch --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Jan 20 09:21:52 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59AE8EC53D3; Sat, 20 Jan 2018 09:21:52 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 1BCEC701F8; Sat, 20 Jan 2018 09:21:52 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 A803A26012B; Sat, 20 Jan 2018 10:21:49 +0100 (CET) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Greg V , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Hans Petter Selasky Message-ID: Date: Sat, 20 Jan 2018 10:18:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 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, 20 Jan 2018 09:21:52 -0000 On 01/20/18 00:17, Greg V via freebsd-net wrote: > > On 01/19/2018 12:54, Hans Petter Selasky wrote: >> On 01/18/18 14:11, Greg V wrote: >>> Hi. I've upgraded CURRENT from December 19 >>> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) >>> to today >>> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) >>> and my Mellanox ConnectX-2 network card stopped working: >>> >>> mlx4_core0: mem >>> 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on pci7 >>> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) >>> mlx4_core: Initializing mlx4_core >>> mlx4_core0: command 0xffa failed: fw status = 0x1 >>> mlx4_core0: Failed to map EQ context memory, aborting >>> device_attach: mlx4_core0 attach returned 12 >>> >>> >>> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does >>> work fine! >>> >>> Reverting all mlx4 changes between then and now (no big changes, >>> mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 >>> module with CC=clang50 does not help. >>> >>> What happened?! >> >> Hi, >> >> Can you do: >> >> objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt >> objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt >> >> And diff the text result between working and non-working ko's. > That results in 180883 lines (9.2 megabytes) of diff for mlx4.ko. The > CC=clang50 one is only a bit better at 7.6 MB :( Can you open this diff using "meld". And look for instructions which have changed, not only their location. --HPS