From owner-freebsd-net@freebsd.org Sun Sep 18 14:36:12 2016 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 77D1CBDF618 for ; Sun, 18 Sep 2016 14:36:12 +0000 (UTC) (envelope-from zjef@mail2tor.com) Received: from mail2tor.com (mail2tor.com [188.126.79.59]) by mx1.freebsd.org (Postfix) with ESMTP id 421EED0A for ; Sun, 18 Sep 2016 14:36:12 +0000 (UTC) (envelope-from zjef@mail2tor.com) Received: from mail.mail2tor.com (localhost [127.0.0.1]) by mail2tor.com (Postfix) with ESMTP id 1AE7FC20936 for ; Sun, 18 Sep 2016 14:36:00 +0000 (UTC) Message-ID: <81133b70f2163676b916c089d5b24353.squirrel@_> In-Reply-To: <5ae6c994bdab8464ac041bf395dbc845.squirrel@_> References: <1efbc304fc2208b7cb41f5ca208d2f81.squirrel@_> <5ae6c994bdab8464ac041bf395dbc845.squirrel@_> Date: Sun, 18 Sep 2016 14:36:08 -0000 Subject: Re: =ping: sendto: Can't assign requested address= in fib spaces From: zjef@mail2tor.com To: zjef@mail2tor.com Cc: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 14:36:12 -0000 also fresh post here https://forums.pcbsd.org/thread-20944-post-114994.html#pid114994 > hi, > yep, it is not not a fib problem. It is related to openvpn (on banana > pi?), similar to one mentioned here > > https://newpush.com/2010/01/openvpn-write-udpv4-cant-assign-requested-address-code49/ > > or here > > https://yeri.be/openvpn-cant-assign-requested-address > > Thanks. > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Sun Sep 18 17:35:46 2016 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 E52ECBE0564 for ; Sun, 18 Sep 2016 17:35:46 +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 mx1.freebsd.org (Postfix) with ESMTPS id D4CAF21B for ; Sun, 18 Sep 2016 17:35:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8IHZjBH052945 for ; Sun, 18 Sep 2016 17:35:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212576] vnet jail startup and shutdown destroys ipfw object rewriter list Date: Sun, 18 Sep 2016 17:35:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@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: 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 17:35:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212576 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Sun Sep 18 17:35:17 UTC 2016 New revision: 305940 URL: https://svnweb.freebsd.org/changeset/base/305940 Log: Move opcode rewriter init and destroy handlers into non-VENT code. PR: 212576,212649,212077 Submitted by: John Zielinski MFC after: 1 week Changes: head/sys/netpfil/ipfw/ip_fw2.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Sep 18 21:00:42 2016 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 2FC35BE02C6 for ; Sun, 18 Sep 2016 21:00:42 +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 mx1.freebsd.org (Postfix) with ESMTPS id 26A9986B for ; Sun, 18 Sep 2016 21:00:42 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8IL01YS043760 for ; Sun, 18 Sep 2016 21:00:42 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201609182100.u8IL01YS043760@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 18 Sep 2016 21:00:42 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 21:00:42 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 203422 | mpd/ppoe not working with re(4) with revision 285 In Progress | 206581 | bxe_ioctl_nvram handler is faulty New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic Open | 148807 | [panic] "panic: sbdrop" and "panic: sbsndptr: soc Open | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open | 194485 | Userland cannot add IPv6 prefix routes Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open | 211031 | [panic] in ng_uncallout when argument is NULL Open | 211962 | bxe driver queue soft hangs and flooding tx_soft_ Open | 212018 | Enable IPSEC_NAT_T in GENERIC kernel configuratio 14 problems total for which you should take action. From owner-freebsd-net@freebsd.org Sun Sep 18 21:28:49 2016 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 94915BE0A12 for ; Sun, 18 Sep 2016 21:28:49 +0000 (UTC) (envelope-from zclaudio@bsd.com.br) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 66D1B933 for ; Sun, 18 Sep 2016 21:28:48 +0000 (UTC) (envelope-from zclaudio@bsd.com.br) Received: by mail-it0-x22c.google.com with SMTP id 15so17186912ita.1 for ; Sun, 18 Sep 2016 14:28:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qen2XgrzmLpGWPSHELK1cCPZUiG0X0ybZuurGaeYiUw=; b=WV4UAE4ZdwmjqdGTMJx1p5e718LdhrnT0uwhkvqfGOQeXsuXf+mM6L2adw1X48m7lH DvXfMINHD4K4C4VbLXfKyD7guOzrBOM1UuO7r4T1+SzvBohTv1BmsrNBJnaMv7XCNSwf WsbDIHcl7/SvG4X5MzJBbrL3XAknv2vUDO4nU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qen2XgrzmLpGWPSHELK1cCPZUiG0X0ybZuurGaeYiUw=; b=PrKDne14+K7PjIDBUZnzQ/ApGvDAIr/Eel/x6hBgi0igqd495CgI570W4ho1tlXj4V d68K6BrTt6tw7MfCFaqv+7BEQ6XtCOQKrpRmYo5VgZcbJMnZdUvQ3sgdogJjQBzszBkq ZtI+9mn5G8OFR7Q8eNlWRFKAL927TrFf/OjiXjiTMhf6JEKQLIZNM/ijPpXNl7yoMBJR bWeTQ3MNox6h6o8yrVo14VPVr7SZCEwdVjF3W5dvyybyJaIKHhLs8pt3kVYN+EqQa+Jd pedeqoGrPGJD+dYJ9MJOMdHEl+45l9IQwTMC/a7LbiFdy2t4RDBwIyZnOGIfftlZfOpL 9D2A== X-Gm-Message-State: AE9vXwNYGbjclCrleL2fY5ha6ZiFz3G4/yY4+aVjtAiUQhmQCQpk/Ae9yoSH5REEkYQHVmo0e2sVuF1ESygahg== X-Received: by 10.36.147.2 with SMTP id y2mr6869518itd.67.1474234128483; Sun, 18 Sep 2016 14:28:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.43.205 with HTTP; Sun, 18 Sep 2016 14:28:48 -0700 (PDT) In-Reply-To: References: From: Ze Claudio Pastore Date: Sun, 18 Sep 2016 18:28:48 -0300 Message-ID: Subject: Re: Regression WPA? 10.2 -> 10.3 stopped working To: Adrian Chadd Cc: freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 21:28:49 -0000 I took longer than expected, got new dongles just to make sure. What I have tested an conclusions: - 11.0-RC2: same problem persists, exactly the same - 10.3: kernel with 10.2 userland: different error, urtwn0 exists from usb bus, probably related to the kernel/userland mismatch than a real error - 10.3: with a live usb stick (official), exactly the same problem as with 10.3 upgraded with freebsd-update - 10.2: works perfectly with all dongles Do you want any debug info I can provide on the working system or a nonworking one? Best, Z. 2016-09-15 14:49 GMT-03:00 Adrian Chadd : > Thanks! I do care; I use wifi daily here in both hostap and sta modes > (and soon hopefully ibss and wds!) so i really do try to keep it > going! > > > -a > > > On 13 September 2016 at 08:14, Ze Claudio Pastore > wrote: > > I will boot from a live stick by the evening and try the same dongles > just > > to isolate if a plain new 10.3 is also broken or if it's just a matter > of an > > unhappy upgrade and report back, thanks for caring :) > > > > 2016-09-13 12:12 GMT-03:00 Ze Claudio Pastore : > >> > >> No, I have'nt, is it possible w/ freebsd-update? Can I revert just the > >> userland? > >> > >> > >> > >> 2016-09-13 0:15 GMT-03:00 Adrian Chadd : > >>> > >>> Hi! > >>> > >>> have you tried say, 10.3 kernel with 10.2 userland? does it still work? > >>> > >>> > >>> > >>> -adrian > >> > >> > > > From owner-freebsd-net@freebsd.org Mon Sep 19 16:04:55 2016 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 71280BE0ED4 for ; Mon, 19 Sep 2016 16:04:55 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 121563BB; Mon, 19 Sep 2016 16:04:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: unable to use BPF Just-In-Time compiler To: "Bjoern A. Zeeb" , KrishnamRaju ErapaRaju References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> Cc: "freebsd-net@freebsd.org" From: Jung-uk Kim Message-ID: <3f462411-c691-f3b8-35f4-f1904c4b84aa@FreeBSD.org> Date: Mon, 19 Sep 2016 12:04:49 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Jh2pwJfk92uibXleF3TF2m8MvO4rOMPDF" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 16:04:55 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Jh2pwJfk92uibXleF3TF2m8MvO4rOMPDF Content-Type: multipart/mixed; boundary="9Fa5DFnEjQkN87SMh9eHWgPlX5ipfdtAm"; protected-headers="v1" From: Jung-uk Kim To: "Bjoern A. Zeeb" , KrishnamRaju ErapaRaju Cc: "freebsd-net@freebsd.org" Message-ID: <3f462411-c691-f3b8-35f4-f1904c4b84aa@FreeBSD.org> Subject: Re: unable to use BPF Just-In-Time compiler References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> In-Reply-To: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> --9Fa5DFnEjQkN87SMh9eHWgPlX5ipfdtAm Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 09/17/2016 17:11, Bjoern A. Zeeb wrote: > On 15 Sep 2016, at 5:32, KrishnamRaju ErapaRaju wrote: >=20 >> Hi, >> >> I want to use BPF JIT Kernel APIs in FreeBSD(like: bpf_jitter(), >> etc..), for implementing TCP connection packet filtering. >> >> I have followed below instructions as specified in: >> https://lists.freebsd.org/pipermail/freebsd-current/2005-December/0586= 03.html >> >> >> STEPS followed: >> --------------------- >> cp /usr/src/sys/amd64/conf/GENERIC /usr/src/sys/amd64/conf/MYKERNEL >> >> And added below line in MYKERNEL config file. >> options BPF_JITTER >=20 > I think you want >=20 > device bpf_jitter >=20 > The options line to my understanding only turns it on by default. "options BPF_JITTER" works. I don't know why the OP thinks that it doesn't work, though. Jung-uk Kim >> make buildkernel KERNCONF=3DMYKERNEL >> make installkernel KERNCONF=3DMYKERNEL >> reboot >> >> But after reboot the flag BPF_JITTER is not getting enabled(all the >> code inside "#ifdef BPF_JITTER" is not getting executed). >> >> Am I missing something? >> >> Also it looks like there are not many updates to BPF JIT code since >> 2005, is it stable? anyone using it? >> >> Thanks, >> Krishna. --9Fa5DFnEjQkN87SMh9eHWgPlX5ipfdtAm-- --Jh2pwJfk92uibXleF3TF2m8MvO4rOMPDF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX4AymAAoJEHyflib82/FGOwIIAIKa9kaKm1jpUpXF0JqL7G9j cSbWtMwLJf7dIfoJmUux4tn5F6S0cMfS0OLV+YZQA3t/8uOOpWrRp8vv+gCtcgFJ evDnqiCIxexw5gsAWPc5NiMNZzwMNN6TgR8+MEGhbeQOq9s9ZNkCizRtcYXUdk5I NObuqTOSrgI8xpc8N0GXNEFBWdf4TwSq7zJh9UoiMDv570UL2i3giqYSadsLxLlJ ef/bWySu8TbEzjQnBd3fdzyt4xRdqqQ6J+VxTVxeVxf/nU15Y8dtilhK0Ac0PAMH zIH5uH4zXGo0BCW5KbJaBETGKIQGuQO0owDToQeu+LW99xxsiu8B6NLnQ7wYtgY= =10nd -----END PGP SIGNATURE----- --Jh2pwJfk92uibXleF3TF2m8MvO4rOMPDF-- From owner-freebsd-net@freebsd.org Mon Sep 19 17:40:02 2016 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 EE362BE194E for ; Mon, 19 Sep 2016 17:40:02 +0000 (UTC) (envelope-from anddiw053@p3slh065.shr.phx3.secureserver.net) Received: from p3smtphosting04.prod.phx3.secureserver.net (p3smtphosting04-01.prod.phx3.secureserver.net [208.109.80.74]) by mx1.freebsd.org (Postfix) with ESMTP id AB4CEAB8 for ; Mon, 19 Sep 2016 17:40:01 +0000 (UTC) (envelope-from anddiw053@p3slh065.shr.phx3.secureserver.net) Received: from p3slh065.shr.phx3.secureserver.net ([208.109.181.6]) by p3smtphosting04.prod.phx3.secureserver.net with id lVfv1t00308h4qQ01Vfvj8; Mon, 19 Sep 2016 10:39:55 -0700 Received: from p3slh065.shr.phx3.secureserver.net (localhost [127.0.0.1]) by p3slh065.shr.phx3.secureserver.net (8.13.8/8.12.11) with ESMTP id u8JHdtwZ024665 for ; Mon, 19 Sep 2016 10:39:55 -0700 Received: (from anddiw053@localhost) by p3slh065.shr.phx3.secureserver.net (8.13.8/8.12.11/Submit) id u8JHdsAX024659; Mon, 19 Sep 2016 10:39:54 -0700 X-GD-UID: 8948467 To: freebsd-net@freebsd.org Subject: Unable to deliver your item, #00000634982 Date: Mon, 19 Sep 2016 10:39:54 -0700 From: "FedEx International MailService" Reply-To: "FedEx International MailService" Message-ID: <92f372325529da589f34f4155a47cb96@contemporaryartwarehouse.com> X-Priority: 3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 17:40:03 -0000 Dear Customer, Your parcel has arrived at September 15. Courier was unable to deliver the parcel to you. You can review complete details of your order in the find attached. Kind regards, Armando Rodgers, FedEx Station Manager. From owner-freebsd-net@freebsd.org Mon Sep 19 17:47:14 2016 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 2E409BE1C35 for ; Mon, 19 Sep 2016 17:47:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::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 F1E0B1CF for ; Mon, 19 Sep 2016 17:47:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x230.google.com with SMTP id m186so99290056ioa.2 for ; Mon, 19 Sep 2016 10:47:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JqZXVHIIri6iZ0kIejWM9nLAMysXCa5PhCsy+inZJUY=; b=wdm92Jj5LztV5P6JiU/iIrYhOSHqGJiElhXzjsAYWKFIL/Af6LI+LSuOFt93pbjiMc UgzE0lGPsNIcLDIn5wRbylE3v5Tx1/vOUV52rqaHwMf3SgGQYC15dVTJDU1TntFr+ZlF Kbh64FTq3YfQmlcgQd8tt70TqlTgSs7pbngF7qtYg1csUr0LZcjdGJp6m1TxeGjKbxvS TTNeywuw7m+npiswfrVRY/5SLmivvfBvrAoLBnwp3D0CC147RNGs9ZmUif95GF/Ie5ph I+0DuisH3LCi+TLOdbegxFkLpXSgF4VEcqJAckCx28HTeiykLzLQVTzg5yb7WXI+fSeI 582A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JqZXVHIIri6iZ0kIejWM9nLAMysXCa5PhCsy+inZJUY=; b=H3oZyQKbZmWefEjOdNEC8lYKFxKz12vGvl7AfXR3y0vqdx/VjcI+oWAQICIhugq+K9 CpbKMdzaAGVOa/rmd3raly8/Ddh4wuMhdVXboi034QjRRBfSUhSNmoUE8rOSA1jPUldj Yba5ljbj3IIyigXLUoX6H3Slx+kUhoPu5CrcqqccjXwEb1HToB7ojjhj/5FQjKQQfBhd /WleBLWpkiSppoY44XRG0frgZb89J8kGPPaVrDurm8m5cWbJBJfCu4B5Y2+eDKvq5PIm 4sIft0Rh0kjUR1wE0VjnKUWaUtPKpqd2egLGMIIs9SWcOAMgveAW5F0TceG02rt9bePQ 1Cag== X-Gm-Message-State: AE9vXwO/8xAPwRm0v6kE3mQ/DP2VoYudY6tnjCO+M8sniHOV8/afiLy6Y/WRoDeUSnHVz2pYP3uhGP9SuSx/+Q== X-Received: by 10.107.152.74 with SMTP id a71mr37744481ioe.120.1474307233454; Mon, 19 Sep 2016 10:47:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Mon, 19 Sep 2016 10:47:12 -0700 (PDT) In-Reply-To: References: From: Adrian Chadd Date: Mon, 19 Sep 2016 10:47:12 -0700 Message-ID: Subject: Re: Regression WPA? 10.2 -> 10.3 stopped working To: Ze Claudio Pastore Cc: freebsd-net Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 17:47:14 -0000 What do you mean with "urtwn0 exists from usb bus" ? -adrian On 18 September 2016 at 14:28, Ze Claudio Pastore wrote: > I took longer than expected, got new dongles just to make sure. > > What I have tested an conclusions: > > - 11.0-RC2: same problem persists, exactly the same > - 10.3: kernel with 10.2 userland: different error, urtwn0 exists from usb > bus, probably related to the kernel/userland mismatch than a real error > - 10.3: with a live usb stick (official), exactly the same problem as with > 10.3 upgraded with freebsd-update > - 10.2: works perfectly with all dongles > > Do you want any debug info I can provide on the working system or a > nonworking one? > > Best, > Z. > > > > > > > > > 2016-09-15 14:49 GMT-03:00 Adrian Chadd : > >> Thanks! I do care; I use wifi daily here in both hostap and sta modes >> (and soon hopefully ibss and wds!) so i really do try to keep it >> going! >> >> >> -a >> >> >> On 13 September 2016 at 08:14, Ze Claudio Pastore >> wrote: >> > I will boot from a live stick by the evening and try the same dongles >> just >> > to isolate if a plain new 10.3 is also broken or if it's just a matter >> of an >> > unhappy upgrade and report back, thanks for caring :) >> > >> > 2016-09-13 12:12 GMT-03:00 Ze Claudio Pastore : >> >> >> >> No, I have'nt, is it possible w/ freebsd-update? Can I revert just the >> >> userland? >> >> >> >> >> >> >> >> 2016-09-13 0:15 GMT-03:00 Adrian Chadd : >> >>> >> >>> Hi! >> >>> >> >>> have you tried say, 10.3 kernel with 10.2 userland? does it still work? >> >>> >> >>> >> >>> >> >>> -adrian >> >> >> >> >> > >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Mon Sep 19 20:17:29 2016 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 9C3D5BE1983 for ; Mon, 19 Sep 2016 20:17:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 61845D85 for ; Mon, 19 Sep 2016 20:17:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-vk0-x22c.google.com with SMTP id o139so9849546vka.1 for ; Mon, 19 Sep 2016 13:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=3SY3Rlzjb6K7tOJHwUDr57AXjIZBrvnet4r5aVTtu5o=; b=Z7XcpUudwU7HdgfCUuSmOnuH1lhPd6swilpxc5YxdEoBGPe2JXRwqHVRCzA65SR4w1 8mEWuywiV/LJ693NJQjGnDFygsvhfCeKR7SPXRWqtX8dTwyoRT60rvT//K9YmL/kRe9t jwTrPOYm73eBA4WUdEIYhPrQqgim6fcajLmtlWs+2q9SaPcaSg7UM9gmpCPQ0kiWZci6 uhV/l4trSbd7s+i+VJ1LtODc3j616po6sxWXq55DYQbKncVytwi0O7O2WAuqvE1nkrtm pL5JQ1ARFedaDM9Venfa+R2/nBTtXPZrPl2vaBZqOE4Sk0J0HIY+cJ+fdQNBVt9j7T7q S7vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3SY3Rlzjb6K7tOJHwUDr57AXjIZBrvnet4r5aVTtu5o=; b=djWtW8hvBpGth9U4tuxs5fhT6MLwdnvRm/ZpA6svhywr8IL5+A9Pu6dWRuoZk9GPnR mhbvJLTiqbaAEjZcjR4cw2erSVhXwVjVpk7XipqSq5xG/l9XAXTmddTO28TpA5WV1T7q 2ATpKOzxJwtBgR2DLEv/ys5/ctU6glwSjUNXS/7L42QLL1N39UqxotabzsUcyKU56SeR kuyy8HH8r/PD8czxv40VOuluhXiQEIlro/QzQNU2opSmYcAJxnjK/kDFRxaYYuB/esJm hNr6wJW5Uk3NHNyHwOuQ5m3SuG+drpLbCF/xf47J83jX620ikM9gUGVSNyVRRZ8tVhjX /w9A== X-Gm-Message-State: AE9vXwOXGd9Bz3OKUGI/pb1W4eY3sJihZOPJVX6i8ASFv1KQWTfCp6p1Ki9inc9VWztIa13kaILhZpTJpSgOXQ== X-Received: by 10.31.221.129 with SMTP id u123mr855847vkg.153.1474316247906; Mon, 19 Sep 2016 13:17:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.65.38 with HTTP; Mon, 19 Sep 2016 13:17:27 -0700 (PDT) From: Lee Brown Date: Mon, 19 Sep 2016 13:17:27 -0700 Message-ID: Subject: Will this card (probably) work? To: freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 20:17:29 -0000 I am looking to purchase this card (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter I350-F4), into which I intend to use 1000-LX SFP's. If I'm understanding correctly, the igb(4) driver supports the i350 (not sure if i350AM4 is the same) and altq(4) states the igb(4) driver is supported (which I'll be needing). Does this look like a viable PCIe card for me to get? Thanks in advance -- lee From owner-freebsd-net@freebsd.org Mon Sep 19 20:48:53 2016 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 A3E05BE13C1 for ; Mon, 19 Sep 2016 20:48:53 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 8600D8F1 for ; Mon, 19 Sep 2016 20:48:53 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 7F6BD1928CE; Mon, 19 Sep 2016 20:48:52 +0000 (UTC) Subject: Re: Will this card (probably) work? To: Lee Brown , freebsd-net References: From: Sean Bruno Message-ID: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> Date: Mon, 19 Sep 2016 14:48:51 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="t5J2l6ROdmVuJhAb4mTEE16vPVpm03d88" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 20:48:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --t5J2l6ROdmVuJhAb4mTEE16vPVpm03d88 Content-Type: multipart/mixed; boundary="SlUAUpmWOfiOuJ4SRLXJgr893u9V4tBh1" From: Sean Bruno To: Lee Brown , freebsd-net Message-ID: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> Subject: Re: Will this card (probably) work? References: In-Reply-To: --SlUAUpmWOfiOuJ4SRLXJgr893u9V4tBh1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 09/19/16 14:17, Lee Brown wrote: > I am looking to purchase this ca= rd > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter I350-F4),= > into which I intend to use 1000-LX SFP's. >=20 > If I'm understanding correctly, the igb(4) driver supports the i350 (no= t > sure if i350AM4 is the same) and altq(4) states the igb(4) driver is > supported (which I'll be needing). >=20 > Does this look like a viable PCIe card for me to get? >=20 > Thanks in advance -- lee > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20 In order to really know, I'd need to know the pci-id that this thing shows up as. sean --SlUAUpmWOfiOuJ4SRLXJgr893u9V4tBh1-- --t5J2l6ROdmVuJhAb4mTEE16vPVpm03d88 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX4E8zXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5ksesIAKMkfLGkax7kGyQS2Eq7F2t9 HAXQ8kXxR1VbzAPMeNlhtMNTLTGInUg9Kin8y3nOQ7h3XVcECxQN69rgRbVXuQm0 OFatZAG5k/HSIFWu5T7RldHzin0ZXJhP70tsdBG9MwQ0CBApI8Pdy6xQb8Tei/sD ZXHgM7tHIrHSIZVDcWFo2khudnJeyMDtLqsGPo2GXQsBXvaxS+AVxqoOT080aM13 puI90c2lPANRMcFGPIrXhvrw1R5KqcYA7s4B9LqQqGpp6/BMQLniE72RXC0rMtOk pVhNB2Nfet3fd7MuEzlk++gHO7OHrDPGn4O2rIPgVV4nKmuUZlwQm08xzGveSgk= =06gu -----END PGP SIGNATURE----- --t5J2l6ROdmVuJhAb4mTEE16vPVpm03d88-- From owner-freebsd-net@freebsd.org Mon Sep 19 21:18:06 2016 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 B4829BE1BE4 for ; Mon, 19 Sep 2016 21:18:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (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 6CEC9953 for ; Mon, 19 Sep 2016 21:18:06 +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 10FB925D3A02; Mon, 19 Sep 2016 21:18:03 +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 40CDDC77244; Mon, 19 Sep 2016 21:18:03 +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 DMESELu1Jr8p; Mon, 19 Sep 2016 21:18:02 +0000 (UTC) Received: from [10.111.64.116] (unknown [IPv6:fde9:577b:c1a9:4410:da1:7913:9d7d:3bf6]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id A1CC0C76FF8; Mon, 19 Sep 2016 21:18:01 +0000 (UTC) From: "Bjoern A. Zeeb" To: "KrishnamRaju ErapaRaju" Cc: "freebsd-net@freebsd.org" Subject: Re: unable to use BPF Just-In-Time compiler Date: Mon, 19 Sep 2016 21:17:57 +0000 Message-ID: <315A03D6-4E89-4C23-8E37-BC52643B5DC6@lists.zabbadoz.net> In-Reply-To: <3f462411-c691-f3b8-35f4-f1904c4b84aa@FreeBSD.org> References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> <3f462411-c691-f3b8-35f4-f1904c4b84aa@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Mailer: MailMate (2.0BETAr6056) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 21:18:06 -0000 On 19 Sep 2016, at 16:04, Jung-uk Kim wrote: > On 09/17/2016 17:11, Bjoern A. Zeeb wrote: >> On 15 Sep 2016, at 5:32, KrishnamRaju ErapaRaju wrote: >> >>> Hi, >>> >>> I want to use BPF JIT Kernel APIs in FreeBSD(like: bpf_jitter(), >>> etc..), for implementing TCP connection packet filtering. >>> >>> I have followed below instructions as specified in: >>> https://lists.freebsd.org/pipermail/freebsd-current/2005-December/058= 603.html >>> >>> >>> STEPS followed: >>> --------------------- >>> cp /usr/src/sys/amd64/conf/GENERIC /usr/src/sys/amd64/conf/MYKERNEL >>> >>> And added below line in MYKERNEL config file. >>> options BPF_JITTER >> >> I think you want >> >> device bpf_jitter >> >> The options line to my understanding only turns it on by default. > > "options BPF_JITTER" works. I don't know why the OP thinks that it > doesn't work, though. Ok, let=E2=80=99s see; if you boot your own kernel, what does sysctl net.bpf_jitter.enable say? /bz From owner-freebsd-net@freebsd.org Tue Sep 20 03:17:46 2016 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 8A7C0BE1AC5 for ; Tue, 20 Sep 2016 03:17:46 +0000 (UTC) (envelope-from Krishna2@chelsio.com) Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0099.outbound.protection.outlook.com [104.47.41.99]) (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 2D6F314CC for ; Tue, 20 Sep 2016 03:17:45 +0000 (UTC) (envelope-from Krishna2@chelsio.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chelsious.onmicrosoft.com; s=selector1-chelsio-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Lu0L2WAD//JQUSuzC6bPTqoxhDEHwYaJuF/a2epIizg=; b=q1PKzg7be7zp9tY18Tx550dT5WSQ5w7GB5SxqzayInG2NzeJBfv8vRuiR0n/rXyLrv7BTuoxEsH79TZESzJ0oaxT7hXEtn8Cj8jkD1CYvIyvYgcSqJgw1BrEQ8Ut+ZJfegW6xhNOvJIGJY91fZLPj+QQKpVWSNSEAr9lqKUsSBo= Received: from BN4PR12MB0818.namprd12.prod.outlook.com (10.164.58.152) by BN4PR12MB0820.namprd12.prod.outlook.com (10.164.58.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.629.8; Mon, 19 Sep 2016 10:41:39 +0000 Received: from BN4PR12MB0818.namprd12.prod.outlook.com ([10.164.58.152]) by BN4PR12MB0818.namprd12.prod.outlook.com ([10.164.58.152]) with mapi id 15.01.0629.006; Mon, 19 Sep 2016 10:41:39 +0000 From: KrishnamRaju ErapaRaju To: "Bjoern A. Zeeb" CC: "freebsd-net@freebsd.org" Subject: RE: unable to use BPF Just-In-Time compiler Thread-Topic: unable to use BPF Just-In-Time compiler Thread-Index: AdIPEooGITIPTSLzSaCF81wrjAmC1gCFX62AAE5/pPA= Date: Mon, 19 Sep 2016 10:41:38 +0000 Message-ID: References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> In-Reply-To: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> 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=Krishna2@chelsio.com; x-originating-ip: [111.93.130.157] x-ms-office365-filtering-correlation-id: a01542a7-8b9f-44b8-2440-08d3e0798990 x-microsoft-exchange-diagnostics: 1; BN4PR12MB0820; 6:BiBcJO4wAmxo/I4DPaWlnBafoaKrBHEd/w0mvIOdJqAoayF8HqwXxvCwFWdRaDDu06Fm0T8Am+T4VY9dyxPezxK+uFnH1moZ4exWkrtvFJwlcbQT8gRYfPXqOXeWzSvadMv887MHOWkaCo18uup/G36MZA/OXvDCtNsSpIAua2CUvCmHiJXq9XdxZUlUNEPK6XdfIMVxNXhHzNuaOprK6fUd3YxrXgFHn0iBRktrr1HLIO+qf4KIrT27HwZ+bzed1d7gL8FR5HyikhoCMFmm1TQVTG434GzdNCb99oLJN9lK59hV4EuK2g24XgDUa/G1; 5:i/3lgNvyQxdSxHlu9sWgwyPa5nRe37Dj3eGT2Iq7XONeL9Bq4pjw2jtAYuaptVnGt8TYMIMsReCgp7dHASkls2wSsEVdFfQY8I5i7V32VLVQOa7Vbi4AxBULwMkM/W9VU0uMpvRUvxnbNiar5aTVUg==; 24:bFFrx0jUgLhFVCuBT+dBhWXH2lRLg7447Dp96Vi4apSolXA7CCigCSUWhYHaCcs1B0Aoh+ft2W0PHGd5PWdVjP28eWi4g7TGt8r3IQlWwsI=; 7:E8MOBGSuv9LCow/74QGSm62A/UKmS0WvQ1PfCH9o8yMqKyLsMNNQnYZv9n0+QmdQX6yADtjqjdeC5k8n0wu52zMpsZvdeO8GUVH6JYwUkqPmkHSD4Q4wxEIKjb0xNI8ek72hW/aCKMFRcyfRghX1M72hbt9kSND+tJuB/PEQWIWYSCMiJ1V+UpCOBZmOkvQeL1XEmrjFVLY0mkikLyez90GkWWhQb/z3G4EmCHQ7ZtTT5jWlk3YCMMJZ7vY2qTPIUrNMF8lSgaep7vCnlaRUPGzCP8hpOJEggIUi43vDW/Q7pmUDi74z90AE0O+iflQJ x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN4PR12MB0820; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(75325880899374)(17755550239193); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6042046)(6043046); SRVR:BN4PR12MB0820; BCL:0; PCL:0; RULEID:; SRVR:BN4PR12MB0820; x-forefront-prvs: 0070A8666B x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(199003)(377454003)(189002)(13464003)(24454002)(53474002)(586003)(2906002)(4326007)(99286002)(8936002)(105586002)(76176999)(50986999)(106356001)(5660300001)(54356999)(3846002)(102836003)(6116002)(15975445007)(74316002)(5002640100001)(81166006)(77096005)(19580405001)(7696004)(2950100001)(86362001)(230783001)(97736004)(2900100001)(19580395003)(110136003)(7736002)(101416001)(7846002)(305945005)(81156014)(8676002)(33656002)(66066001)(189998001)(92566002)(3280700002)(10400500002)(122556002)(87936001)(3660700001)(68736007)(11100500001)(9686002)(76576001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN4PR12MB0820; H:BN4PR12MB0818.namprd12.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: chelsio.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: chelsio.com X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2016 10:41:38.7887 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 065db76d-a7ae-4c60-b78a-501e8fc17095 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN4PR12MB0820 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 03:17:46 -0000 Thanks for your response Bjeorn. I added "device bpf_jitter" line as you suggested, but not luck. Still no code under BPF_JITTER macro is executing. Please help me enabling JIT compiler. Thanks, Krishna. -----Original Message----- From: Bjoern A. Zeeb [mailto:bzeeb-lists@lists.zabbadoz.net]=20 Sent: Sunday, September 18, 2016 2:41 AM To: KrishnamRaju ErapaRaju Cc: freebsd-net@freebsd.org Subject: Re: unable to use BPF Just-In-Time compiler On 15 Sep 2016, at 5:32, KrishnamRaju ErapaRaju wrote: > Hi, > > I want to use BPF JIT Kernel APIs in FreeBSD(like: bpf_jitter(),=20 > etc..), for implementing TCP connection packet filtering. > > I have followed below instructions as specified in:=20 > https://lists.freebsd.org/pipermail/freebsd-current/2005-December/0586 > 03.html > > STEPS followed: > --------------------- > cp /usr/src/sys/amd64/conf/GENERIC /usr/src/sys/amd64/conf/MYKERNEL > > And added below line in MYKERNEL config file. > options BPF_JITTER I think you want device bpf_jitter The options line to my understanding only turns it on by default. > > make buildkernel KERNCONF=3DMYKERNEL > make installkernel KERNCONF=3DMYKERNEL > reboot > > But after reboot the flag BPF_JITTER is not getting enabled(all the=20 > code inside "#ifdef BPF_JITTER" is not getting executed). > > Am I missing something? > > Also it looks like there are not many updates to BPF JIT code since=20 > 2005, is it stable? anyone using it? > > Thanks, > Krishna. > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Sep 20 06:34:12 2016 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 E4825BE1E96 for ; Tue, 20 Sep 2016 06:34:12 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::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 B0C6DC5A for ; Tue, 20 Sep 2016 06:34:12 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-pa0-x22b.google.com with SMTP id oz2so3757666pac.2 for ; Mon, 19 Sep 2016 23:34:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6IOsy1KTjF8DnwFOujLFen7b8R+GlDpcx+/4NK9Axwo=; b=Jn8/EhWBZh4L0vMk0Hs0IJiFKUAn44c2ozIOermr72I8G2be5yu24eeQYPj5Z/5mmD tvG3pLUufYDRQW65riUi1dGDAPgW7uIdQZVHTbnhuDbYlwIiQYCRUnHjWrVgmCYD8rOV Lg+L8IiEwMkcrewYvcF+jxotHsago91i6BH1tAOSJ1yLf6+DPBdySkrRkzz09bYgfV0b 8wmoVuAtX7vPV1raRmvGEkJ9a71101Ga9TirikH91Lzh4/eAGAU1DTcOKWlr2bUo5deD g7k/wkVG+Ac1RJ2C1XJRjROTw7p7UL05Eyyg9j5L6+IIeFWaLO0NZJ0emqbeDM4CxWSw wXxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=6IOsy1KTjF8DnwFOujLFen7b8R+GlDpcx+/4NK9Axwo=; b=gjozjQMFq/dtMT5xiERBKjUHPmR7KjSHdDoW4v7nZ6coKNcNGtK4rvQLDGYTaYpZCf MR0Plm3FXfatmx9ZWmy272qgGrZ+6UU/yTeQ/BLHAxK47H8X4BjhVA2BoACVputFk7Fb vIpVmJ6+UyRTSEXSnMkqU/muUEFMpEzQ83FJe17RU5DFyvCsgp9bMuznHEBKU1I5yqS0 ZI/3qHWQvd3FQ1GpRMb3NHy98PXFulVTn6jhXLmbPGS0/PWz4pbtvlcR+uUOd3gP+0Xa qVPkYSwIK7NQyT6Q+tBIJN7eSWwhs+S3bKEP9qpl+0D94tTFh7jk4qfKea90Fgh63Apl zHfw== X-Gm-Message-State: AE9vXwNgpc7p2X4gKguFUERKE3eMdT+bPn5kIJPNK1xJaPHUAJjKAPfgsPylJMFURtvjSw== X-Received: by 10.66.185.14 with SMTP id ey14mr53684942pac.71.1474353252191; Mon, 19 Sep 2016 23:34:12 -0700 (PDT) Received: from ox ([2601:641:c000:7b00:fc84:de9a:4729:79c7]) by smtp.gmail.com with ESMTPSA id d5sm75947945pfa.44.2016.09.19.23.34.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Sep 2016 23:34:10 -0700 (PDT) Sender: Navdeep Parhar Date: Mon, 19 Sep 2016 23:34:02 -0700 From: Navdeep Parhar To: KrishnamRaju ErapaRaju Cc: "Bjoern A. Zeeb" , "freebsd-net@freebsd.org" Subject: Re: unable to use BPF Just-In-Time compiler Message-ID: <20160920063402.GA15975@ox> Mail-Followup-To: KrishnamRaju ErapaRaju , "Bjoern A. Zeeb" , "freebsd-net@freebsd.org" References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 06:34:13 -0000 Use "options BPF_JITTER" in your kernconf. If this is new code you must include opt_bpf.h in it. If it's part of a module then the module's makefile must have opt_bpf.h in its SRCS. When in doubt take a look at all the obt_bpf.h in your obj tree after the buildkernel and see if they have "#define BPF_JITTER 1" or not. Remove all opt_bpf.h files in the obj tree and retry buildkernel if all else fails. Regards, Navdeep On Mon, Sep 19, 2016 at 10:41:38AM +0000, KrishnamRaju ErapaRaju wrote: > Thanks for your response Bjeorn. > > I added "device bpf_jitter" line as you suggested, but not luck. > Still no code under BPF_JITTER macro is executing. > > Please help me enabling JIT compiler. > > Thanks, > Krishna. > -----Original Message----- > From: Bjoern A. Zeeb [mailto:bzeeb-lists@lists.zabbadoz.net] > Sent: Sunday, September 18, 2016 2:41 AM > To: KrishnamRaju ErapaRaju > Cc: freebsd-net@freebsd.org > Subject: Re: unable to use BPF Just-In-Time compiler > > On 15 Sep 2016, at 5:32, KrishnamRaju ErapaRaju wrote: > > > Hi, > > > > I want to use BPF JIT Kernel APIs in FreeBSD(like: bpf_jitter(), > > etc..), for implementing TCP connection packet filtering. > > > > I have followed below instructions as specified in: > > https://lists.freebsd.org/pipermail/freebsd-current/2005-December/0586 > > 03.html > > > > STEPS followed: > > --------------------- > > cp /usr/src/sys/amd64/conf/GENERIC /usr/src/sys/amd64/conf/MYKERNEL > > > > And added below line in MYKERNEL config file. > > options BPF_JITTER > > I think you want > > device bpf_jitter > > The options line to my understanding only turns it on by default. > > > > > make buildkernel KERNCONF=MYKERNEL > > make installkernel KERNCONF=MYKERNEL > > reboot > > > > But after reboot the flag BPF_JITTER is not getting enabled(all the > > code inside "#ifdef BPF_JITTER" is not getting executed). > > > > Am I missing something? > > > > Also it looks like there are not many updates to BPF JIT code since > > 2005, is it stable? anyone using it? > > > > Thanks, > > Krishna. > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Sep 20 09:42:21 2016 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 BE56ABE2FD7 for ; Tue, 20 Sep 2016 09:42:21 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 8067BE89 for ; Tue, 20 Sep 2016 09:42:21 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-vk0-x230.google.com with SMTP id g9so17320040vkg.2 for ; Tue, 20 Sep 2016 02:42:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+yFxOqXicj86RcOTnx7E9MJnEIUaQbm4l0H6bNeeoxo=; b=AnRkNmC/qXb/QXdIxW+11UCpk3JSNHxGe6ZJWW4n3UOgiJbaRhcnBgnDkXc9tgts3q U+YLf/JmY/kwa9hbXIQ3DTTN+WXvjN4ZI740QVpcAYo3M2t6cPfgCIGLT/1IGRXTzsRF ffiG8I59NeDhY+41/iAAP+wZwhokKzA4y3qqjePIom8CACg9VKK5k2ML/paQkJkuvGoL tUdSz5CbyczAuY5x1vFybzYY3KeyuhZ0r0764liuwvmFREkQTBn8QhEecdlqvCrgGW9z 5c+nOURJVi1J0GY2m1hUvmRlhGpFlNot4rtvyaoKI8RVRVfX6uINqZZO9AhDHR9mFdD1 l5/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+yFxOqXicj86RcOTnx7E9MJnEIUaQbm4l0H6bNeeoxo=; b=QhCDvKwtxKwEWDYwr/kvaivcZsVtxRytbwW5O35TnDuoGitrWYCrbsDaefrI1+ElMQ jSyAR50Bq06IwvGyIQphuK/jJ/XNvC22kBzGC4H7kydoQAp02ioX/QGIztneXMT6ZulE 3btiE9wpu4Obn/6eR0zyJV6e1uSaWVZ39bhqgQy1zUkSVkC6hcavT5BhwPtkGF+0lF36 Qbg+1/I2lghsiDU13sK485jVlsJ7U3LRRHh5G1Ku9+kT9pmHlA2SlmJ9j/7NA8UVR0h7 4C6QsBopPYuGq0bLNTYiReX9SZaLinxLVX8aVMTOL2msxnSTPosvCWngnZaLcyuQ+eBC R+Iw== X-Gm-Message-State: AE9vXwPPCq2rtC6AFjiTcgddvKFBMiR+4uksCIU0zO1LFIF2MjB/du7wNOwJleXd7tKameBNJzjsGMmEDD2nZA== X-Received: by 10.31.96.74 with SMTP id u71mr2632668vkb.51.1474364540079; Tue, 20 Sep 2016 02:42:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.65.38 with HTTP; Tue, 20 Sep 2016 02:42:19 -0700 (PDT) In-Reply-To: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> From: Lee Brown Date: Tue, 20 Sep 2016 02:42:19 -0700 Message-ID: Subject: Re: Will this card (probably) work? To: Sean Bruno Cc: freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 09:42:21 -0000 On Mon, Sep 19, 2016 at 1:48 PM, Sean Bruno wrote: > > > On 09/19/16 14:17, Lee Brown wrote: > > I am looking to purchase this > card > > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter I350-F4), > > into which I intend to use 1000-LX SFP's. > > > > If I'm understanding correctly, the igb(4) driver supports the i350 (not > > sure if i350AM4 is the same) and altq(4) states the igb(4) driver is > > supported (which I'll be needing). > > > > Does this look like a viable PCIe card for me to get? > > > > Thanks in advance -- lee > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > > In order to really know, I'd need to know the pci-id that this thing > shows up as. > > sean > > Thanks, I've reached out for that info. Otherwise, if you happen to know of a 4-port or even 2-port PCIe card that supports 1000Base-LX or SFP's that will, I'm all ears. I'd consider a single port card as last resort. From owner-freebsd-net@freebsd.org Tue Sep 20 05:56:02 2016 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 30C97BE10ED for ; Tue, 20 Sep 2016 05:56:02 +0000 (UTC) (envelope-from Krishna2@chelsio.com) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0132.outbound.protection.outlook.com [104.47.33.132]) (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 D84EC92F for ; Tue, 20 Sep 2016 05:56:01 +0000 (UTC) (envelope-from Krishna2@chelsio.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chelsious.onmicrosoft.com; s=selector1-chelsio-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=/zFRN2+IiNIvFSFux0KCbBrLJOlABk5aVlclLTotl3k=; b=eKrzeg35KlchltnEzOeq1o8eeOUOL8PoAgZ0ILms3bthGSwWjlhmJymnATsHgYVOqkdCG4frJvdlx8hIlt0b/CswSPJY1RAzaKmTxAF5YzDmkumUuvPWrTjfH7hBsev9pTLpKrbUkvMBN9194Zmzv5XbazEYA9LhJi0w2p57Eqk= Received: from BN4PR12MB0818.namprd12.prod.outlook.com (10.164.58.152) by BN4PR12MB0817.namprd12.prod.outlook.com (10.164.58.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.629.8; Tue, 20 Sep 2016 05:22:59 +0000 Received: from BN4PR12MB0818.namprd12.prod.outlook.com ([10.164.58.152]) by BN4PR12MB0818.namprd12.prod.outlook.com ([10.164.58.152]) with mapi id 15.01.0629.006; Tue, 20 Sep 2016 05:22:59 +0000 From: KrishnamRaju ErapaRaju To: "Bjoern A. Zeeb" CC: "freebsd-net@freebsd.org" Subject: RE: unable to use BPF Just-In-Time compiler Thread-Topic: unable to use BPF Just-In-Time compiler Thread-Index: AdIPEooGITIPTSLzSaCF81wrjAmC1gCFX62AAFng4oAACu+hgAAQzOHQ Date: Tue, 20 Sep 2016 05:22:59 +0000 Message-ID: References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> <3f462411-c691-f3b8-35f4-f1904c4b84aa@FreeBSD.org> <315A03D6-4E89-4C23-8E37-BC52643B5DC6@lists.zabbadoz.net> In-Reply-To: <315A03D6-4E89-4C23-8E37-BC52643B5DC6@lists.zabbadoz.net> 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=Krishna2@chelsio.com; x-originating-ip: [103.252.25.50] x-ms-office365-filtering-correlation-id: bf24e834-fa8a-4754-80f0-08d3e1162fbd x-microsoft-exchange-diagnostics: 1; BN4PR12MB0817; 6:lg3FXGtQkkJRtpHCrhvKl6sis3QQyw08vYPS+S4N1rS4I2eldTqctXmIxDP//W+uWD6uFwT+cVt4ESYiwqxtUQkup23LOr1Gm7ppmn7RhJ+G7sUUIWW0mpO0bi7R51SHM9P4sNudp6fjNpkqHluwO2NZlEm/gIaD2Ao4NyhmksvmyPRY2ptRqOzKu7Hc9ntL8Y8LjsIFs2Dn4sqQUj3yCtV92dJbsZEV6rg9jBurwWLVm1Dlqa8LHddOmIcUmbBi5IKgeZZj4dzID3Z+CK1Ir4a/nNIF4rwlXDFjptS+ON9vccKyBCsws/TvYxBJgc2o; 5:iB15LC+d8bAUzMaQL8eUHMJJQ5e/XjSuYv5IymV6GSWSljptbMDcENHeFbBlUMf7qPklQhjLPE3xmxNVT7x3chR6lpqr51vlkTMfNAlHuOvGafeb+kzOrvDovgX7Sh+vFGeH8FYk/EAH7JSYbNPOTw==; 24:7dBeFiyd7tRhk+VHVDNuC0k2im7ubc9aFYLzS0SUHisbGjUv45yOs4YwUd4upTNWJZMvFHA7ooruYZCQqkuI4Hm5wRVcK3IkftywygVEAY8=; 7:TepBD6WHQv7bBP1jBy1txpJHlmyhka9UTTBnbVrwXJqWVZGIfXgKqbrphPzwRB58nyVP5xHhpf7gmlRS19d5aVyvXWb751jYWPrbUNKTO28Ysmzr6D7DunOHVam/iv3vz7v0f8B1jhL1lTcHKJN9UnL0/1Qb68gMdJ/PvxRyImHOhL8oNO5hD72RaBBnF/ufTjtneC1FeSmqsRB+VO3N2EUIE9Vem/toClJgaua/lpIIkIzRrYiBWeG8IGpxInryLfS8onSAuirNghn8zSo+zdHsyyhhJWQlcbgvB3kSeDDva8BpqkltZfFABBdEtUzG x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN4PR12MB0817; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6042046)(6043046); SRVR:BN4PR12MB0817; BCL:0; PCL:0; RULEID:; SRVR:BN4PR12MB0817; x-forefront-prvs: 0071BFA85B x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(24454002)(377454003)(199003)(189002)(13464003)(93886004)(87936001)(68736007)(2950100001)(19580395003)(2900100001)(19580405001)(5660300001)(7696004)(110136003)(6116002)(15975445007)(77096005)(8936002)(92566002)(10400500002)(76576001)(586003)(189998001)(66066001)(230783001)(102836003)(3846002)(3280700002)(4326007)(9686002)(97736004)(2906002)(33656002)(7846002)(7736002)(76176999)(74316002)(5002640100001)(305945005)(50986999)(54356999)(81166006)(11100500001)(81156014)(86362001)(101416001)(8676002)(99286002)(106356001)(122556002)(3660700001)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN4PR12MB0817; H:BN4PR12MB0818.namprd12.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: chelsio.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: chelsio.com X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Sep 2016 05:22:59.2527 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 065db76d-a7ae-4c60-b78a-501e8fc17095 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN4PR12MB0817 X-Mailman-Approved-At: Tue, 20 Sep 2016 11:15:29 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 05:56:02 -0000 W3Jvb3RAdGFqIH5dIyBzeXNjdGwgbmV0LmJwZl9qaXR0ZXIuZW5hYmxlDQpuZXQuYnBmX2ppdHRl ci5lbmFibGU6IDENCg0KDQpJdCBzaG93cyAnMScsIGJ1dCBkb27igJl0IGtub3cgd2h5IHRoZSBj b2RlIHVuZGVyICJCUEZfSklUVEVSIiBtYWNybyBub3QgZ2V0dGluZyBleGVjdXRlZC4NCi0tLS0t LS0tLS0tLS0tLS1teSBjb2RlIHNuaXBwZXQtLS0tLS0tLS0tLS0tDQojaWZkZWYgQlBGX0pJVFRF Ug0KICAgICAgICAgICAgICAgIHByaW50ZigiSklUVEVSIGZpbHRlclxuIik7DQogICAgICAgICAg ICAgICAgaWYgKHBvbGljeS0+Zmx0X3RibFtpXS5qaXRfZmlsdGVyKQ0KICAgICAgICAgICAgICAg ICAgICAgICAgcmV0ID0gKCoocG9saWN5LT5mbHRfdGJsW2ldLmppdF9maWx0ZXItPmZ1bmMpKShw a3QsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgcGt0bGVuLCBwa3RsZW4pOw0KICAgICAgICAgICAgICAgIGVsc2UNCiAgICAg ICAgICAgICAgICAgICAgICAgIHJldCA9IDA7DQojZWxzZQ0KICAgICAgICAgICAgICAgIHByaW50 ZigiYnBmX2ZpbHRlclxuIik7DQogICAgICAgICAgICAgICAgcmV0ID0gYnBmX2ZpbHRlcihwb2xp Y3ktPmZsdF90YmxbaV0uZmlsdGVyX3J1bGUuYmZfaW5zbnMsIHBrdCwNCiAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBwa3RsZW4s IHBrdGxlbik7DQojZW5kaWYNCg0KVGhhbmtzLA0KS3Jpc2huYS4NCi0tLS0tT3JpZ2luYWwgTWVz c2FnZS0tLS0tDQpGcm9tOiBCam9lcm4gQS4gWmVlYiBbbWFpbHRvOmJ6ZWViLWxpc3RzQGxpc3Rz LnphYmJhZG96Lm5ldF0gDQpTZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIgMjAsIDIwMTYgMjo0OCBB TQ0KVG86IEtyaXNobmFtUmFqdSBFcmFwYVJhanUgPEtyaXNobmEyQGNoZWxzaW8uY29tPg0KQ2M6 IGZyZWVic2QtbmV0QGZyZWVic2Qub3JnDQpTdWJqZWN0OiBSZTogdW5hYmxlIHRvIHVzZSBCUEYg SnVzdC1Jbi1UaW1lIGNvbXBpbGVyDQoNCk9uIDE5IFNlcCAyMDE2LCBhdCAxNjowNCwgSnVuZy11 ayBLaW0gd3JvdGU6DQoNCj4gT24gMDkvMTcvMjAxNiAxNzoxMSwgQmpvZXJuIEEuIFplZWIgd3Jv dGU6DQo+PiBPbiAxNSBTZXAgMjAxNiwgYXQgNTozMiwgS3Jpc2huYW1SYWp1IEVyYXBhUmFqdSB3 cm90ZToNCj4+DQo+Pj4gSGksDQo+Pj4NCj4+PiBJIHdhbnQgdG8gdXNlIEJQRiBKSVQgS2VybmVs IEFQSXMgaW4gRnJlZUJTRChsaWtlOiBicGZfaml0dGVyKCksIA0KPj4+IGV0Yy4uKSwgZm9yIGlt cGxlbWVudGluZyBUQ1AgY29ubmVjdGlvbiBwYWNrZXQgZmlsdGVyaW5nLg0KPj4+DQo+Pj4gSSBo YXZlIGZvbGxvd2VkIGJlbG93IGluc3RydWN0aW9ucyBhcyBzcGVjaWZpZWQgaW46DQo+Pj4gaHR0 cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9waXBlcm1haWwvZnJlZWJzZC1jdXJyZW50LzIwMDUtRGVj ZW1iZXIvMDUNCj4+PiA4NjAzLmh0bWwNCj4+Pg0KPj4+DQo+Pj4gU1RFUFMgZm9sbG93ZWQ6DQo+ Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4gY3AgL3Vzci9zcmMvc3lzL2FtZDY0L2NvbmYv R0VORVJJQyAvdXNyL3NyYy9zeXMvYW1kNjQvY29uZi9NWUtFUk5FTA0KPj4+DQo+Pj4gQW5kIGFk ZGVkIGJlbG93IGxpbmUgaW4gTVlLRVJORUwgY29uZmlnIGZpbGUuDQo+Pj4gICAgICAgICBvcHRp b25zIEJQRl9KSVRURVINCj4+DQo+PiBJIHRoaW5rIHlvdSB3YW50DQo+Pg0KPj4gZGV2aWNlICAg ICAgICAgYnBmX2ppdHRlcg0KPj4NCj4+IFRoZSBvcHRpb25zIGxpbmUgdG8gbXkgdW5kZXJzdGFu ZGluZyBvbmx5IHR1cm5zIGl0IG9uIGJ5IGRlZmF1bHQuDQo+DQo+ICJvcHRpb25zIEJQRl9KSVRU RVIiIHdvcmtzLiAgSSBkb24ndCBrbm93IHdoeSB0aGUgT1AgdGhpbmtzIHRoYXQgaXQgDQo+IGRv ZXNuJ3Qgd29yaywgdGhvdWdoLg0KDQpPaywgbGV04oCZcyBzZWU7ICBpZiB5b3UgYm9vdCB5b3Vy IG93biBrZXJuZWwsIHdoYXQgZG9lcw0KDQpzeXNjdGwgbmV0LmJwZl9qaXR0ZXIuZW5hYmxlDQoN CnNheT8NCg0KL2J6DQo= From owner-freebsd-net@freebsd.org Tue Sep 20 11:25:24 2016 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 53CF8BE2E7C for ; Tue, 20 Sep 2016 11:25:24 +0000 (UTC) (envelope-from loganaden@gmail.com) Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 28A81A50; Tue, 20 Sep 2016 11:25:24 +0000 (UTC) (envelope-from loganaden@gmail.com) Received: by mail-pf0-x236.google.com with SMTP id q2so6539095pfj.3; Tue, 20 Sep 2016 04:25:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dBIWEz7gNG9QrpAtDr0JE2qnTx3xKpfrqmWZKR45ikI=; b=zcUYsmu63fGEGXnqfNOwsuSIGzeHj+NxPM6rqAGIeAtg1u0UaD0iAVEvRFeWG/lX8V N9cM5P2R5NZBnxTJWvSBbZRKpkJYR/2MFmKogMOWPBwUY5sDrleDalpVA+59oRvc8+2V HMcyIdl/tkqMMASgoxnfCLtUOQP/bz5kVlzPjK0X3m64QWEHc/DBVZDxUSZJNXdlTvgp 7apgFFemYQHuEb80t7WeS3Kn4eiUjeFmmnoF0qUksve655A98eAe5ROTBCQUMDBCvXyl xxe8PssLcm7jDNLcNxOe5OZ10ytUHzqCQkdWHMGrFvcgAjtrA6gfElyT8JGAVFJ9wuAt LwuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dBIWEz7gNG9QrpAtDr0JE2qnTx3xKpfrqmWZKR45ikI=; b=K0p8vwzzSBJ5at0q7I/ONaBcqv9oUqImVVrGYaiocKMRRepk5euDGEy94TLP0/HS9g VZFvdpudlQhDasToeZMslU/z1MQF63bFSS81Wvslu+4VWH5L12B7hXsWpg5I/qGffDV7 O0E2Mwk8ELV+qJGfc6I8E67zSw/LKIC1TxFpQQJj1IsjJyPA64b1PACV8z2BJBGwdn99 mWZp7w2Jz8ZHLL3NdXh8AXLs80lY+crXL93uq2AiwI0TH574Amt+nyajwQ2TozGy7iwR QcvQW5AQN8Bo1hlvyaSMk4cbRdBt+EEkJRInNpQ+UOwK0o/rcy4jdMY6C7PiaPnOyViZ UaqQ== X-Gm-Message-State: AE9vXwNwToNCB63y+TqsScJsUkGQBahMOemP9NelRVSzzZWXTP0Xs6xoO+pAaBJEmSFYPghpEmBKtbqAuBfhzA== X-Received: by 10.98.208.195 with SMTP id p186mr12283701pfg.90.1474370723274; Tue, 20 Sep 2016 04:25:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.102.70 with HTTP; Tue, 20 Sep 2016 04:25:22 -0700 (PDT) In-Reply-To: References: From: Loganaden Velvindron Date: Tue, 20 Sep 2016 15:25:22 +0400 Message-ID: Subject: Re: BBR Congestion Control Algorithm To: Babak Farrokhi Cc: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 11:25:24 -0000 On Sat, Sep 17, 2016 at 7:24 PM, Babak Farrokhi wrote: > ICYMI: http://marc.info/?l=linux-netdev&m=147405177724268&w=2 > > Google submitted their own TCP CC algorithm to upstream. This algorithm has been widely in use in their network. > This looks very interesting and it would be great if someone could port it to FreeBSD. > > Any thoughts? > > -- > Babak Farrokhi > A lot of groundwork needs to be done I suppose. For example, implementing high-resolution timers that would allow the FreeBSD network stack to implement BQL, and other necessary infrastructure in order for fq_codel/CAKE to work as well as on Linux. Perhaps this might be something that the FreeBSD foundation could look into ? From owner-freebsd-net@freebsd.org Tue Sep 20 15:47:49 2016 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 93775BE2DF7 for ; Tue, 20 Sep 2016 15:47:49 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 56308E61 for ; Tue, 20 Sep 2016 15:47:48 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id A70841928CE; Tue, 20 Sep 2016 15:47:47 +0000 (UTC) Subject: Re: Will this card (probably) work? To: Lee Brown References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> Cc: freebsd-net From: Sean Bruno Message-ID: Date: Tue, 20 Sep 2016 09:47:43 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2uO8TmpjnOs9judfA8hmXaE7BVOuHhmO4" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 15:47:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2uO8TmpjnOs9judfA8hmXaE7BVOuHhmO4 Content-Type: multipart/mixed; boundary="jAnBQIEfdgttuwe6c7Mu7AGh87k5cAbES" From: Sean Bruno To: Lee Brown Cc: freebsd-net Message-ID: Subject: Re: Will this card (probably) work? References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> In-Reply-To: --jAnBQIEfdgttuwe6c7Mu7AGh87k5cAbES Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 09/20/16 03:42, Lee Brown wrote: >=20 >=20 > On Mon, Sep 19, 2016 at 1:48 PM, Sean Bruno > wrote: >=20 >=20 >=20 > On 09/19/16 14:17, Lee Brown wrote: > > I am looking to purchase this > > card > > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter > I350-F4), > > into which I intend to use 1000-LX SFP's. > > > > If I'm understanding correctly, the igb(4) driver supports the > i350 (not > > sure if i350AM4 is the same) and altq(4) states the igb(4) driver= is > > supported (which I'll be needing). > > > > Does this look like a viable PCIe card for me to get? > > > > Thanks in advance -- lee > > _______________________________________________ > > freebsd-net@freebsd.org mailing = list > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > > To unsubscribe, send any mail to > "freebsd-net-unsubscribe@freebsd.org > " > > >=20 > In order to really know, I'd need to know the pci-id that this thin= g > shows up as. >=20 > sean >=20 > Thanks, I've reached out for that info. > Otherwise, if you happen to know of a 4-port or even 2-port PCIe card > that supports 1000Base-LX or SFP's that will, I'm all ears. I'd > consider a single port card as last resort. >=20 Pretty sure that the i350 is what you're in the market for. Just not sure if it will show up as an igb(4) nic. If it doesn't, it'd be trivial to add the pci-ids if it is just a variant. sean --jAnBQIEfdgttuwe6c7Mu7AGh87k5cAbES-- --2uO8TmpjnOs9judfA8hmXaE7BVOuHhmO4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX4VofXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kCk4H/Awxz1PBiuYw9uuQXfyu3hQ1 4nqXex7eIYSR5UsnUAOQu15LpMeuKsSGNvdcUnHNov1Aa3Y2wN7g18oGK1rvGDv3 SFTiJdjqkHn6Ksx1xU39ei0Tq6FDoYbwsfzIzt2BwpD/TMGnOJJl67kg+Wn+MepM UBSDZWEucYZSp7wCPhP5V+OuOD3ztPS+bIApOb9UBh3eHEtN8S5xv6hr8oPKQ9UH brqYjlqanPaA/l4EBzn7tkF3lkA/z/wflEFgDeYRSTEuEDhBMC3Rfxrj4FMBLXjE deUf2zXs6/m7bpCKfjeWgBZ1mlSb6os52ErC380HjomOBYbt+ktdRf86zKmaY4A= =V2hN -----END PGP SIGNATURE----- --2uO8TmpjnOs9judfA8hmXaE7BVOuHhmO4-- From owner-freebsd-net@freebsd.org Tue Sep 20 15:56:10 2016 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 D94CEBE1283 for ; Tue, 20 Sep 2016 15:56:10 +0000 (UTC) (envelope-from Krishna2@chelsio.com) Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0114.outbound.protection.outlook.com [104.47.36.114]) (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 88AC6622; Tue, 20 Sep 2016 15:56:09 +0000 (UTC) (envelope-from Krishna2@chelsio.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chelsious.onmicrosoft.com; s=selector1-chelsio-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=cnUVDb4Whfb83XJTIIoTYF7KJn5RKID5gQqVKUDkhpM=; b=cobMdyIpIoMJ6I3QceZwOPs/BPs8YKY1ltYKYgT8p7FYUGrW5pv2oQn/v030ibbQuiDCQ0bAET1wBZGb+6f5EbyQ7NpZteAdW+xlA5o0wjxaDszKnlqkhV/BXD+mzw0U4tfW8pFoXFzoygBTP5zrddXIFpw8nAUmYLApI8M4qnU= Received: from BN4PR12MB0818.namprd12.prod.outlook.com (10.164.58.152) by BN4PR12MB0819.namprd12.prod.outlook.com (10.164.58.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.629.8; Tue, 20 Sep 2016 15:41:40 +0000 Received: from BN4PR12MB0818.namprd12.prod.outlook.com ([10.164.58.152]) by BN4PR12MB0818.namprd12.prod.outlook.com ([10.164.58.152]) with mapi id 15.01.0629.006; Tue, 20 Sep 2016 15:41:40 +0000 From: KrishnamRaju ErapaRaju To: Navdeep Parhar CC: "Bjoern A. Zeeb" , "freebsd-net@freebsd.org" Subject: RE: unable to use BPF Just-In-Time compiler Thread-Topic: unable to use BPF Just-In-Time compiler Thread-Index: AdIPEooGITIPTSLzSaCF81wrjAmC1gCFX62AAE5/pPAAKbylAAASuzoQ Date: Tue, 20 Sep 2016 15:41:40 +0000 Message-ID: References: <3F7A8F51-D404-4FEF-910C-8E51DD5061AD@lists.zabbadoz.net> <20160920063402.GA15975@ox> In-Reply-To: <20160920063402.GA15975@ox> 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=Krishna2@chelsio.com; x-originating-ip: [111.93.130.157] x-ms-office365-filtering-correlation-id: bd75e4f1-3047-4311-9419-08d3e16c9dc5 x-microsoft-exchange-diagnostics: 1; BN4PR12MB0819; 6:vRVrX0Ft1ff9UKZSv3vT5Br3sF5quDVJQJbSvWHIBXOJD5yBIXkjzMcm8ltdTR4LA1TsY4+7f8ZPgoSuX/WddSSKUShFg+ZQ8sVGa7ATOxbnCMV389FicVbqpkRdbCmw5Wwho0UFoTzX5WjLkLZjiwT343QCwfPOmnBRZe4Rs6tJk236tn2pvlrBC6LW4YFGKLhSHN8f8f9oVa9LBMfXUAY1at8j8rv+HyzLW5iVvJvHVhtVxYIn1PW2mb25+m4tquwIgafmdHSM5Nf+S0mhlJfewvOPNvwla41fOIAw1Bsr7m9Ci1sE6cXm1f+GXmci; 5:SpeQG5iPF57cxSf3V8JDE5st6kkQo6OwKUhCIBlVgzcj0hQFjokZASWqbaquD8CxpEJ1UULvK2lKPtCsFZWiy9TdTN6+FS1EpzOBMwQiDsc3B189CVrCq7ZJcnqFQewtzcwcDXSkP52qkqoqjRuDSg==; 24:GGd6i44Mv3PdzOdEEqjaPTsSK3ps0HHS0bTfBUnZxHOLsYYwgpGFinZdNmiDbFRYDN0shntdsoYUo+eSak+ZZS7L6MKYkkLwDWugD77Uodg=; 7:92oygLrmfM2j5GkfLp2ixxRZVLRBvcsUU5YuuAJFaILxoIC7EtUB/73oenp0QfNqAO1V1UxlH+mM98uioopgKSCXKUlMuTIcOQYAxMUXwjatrxkvF2j4kKX5BrnwBNMSlHkc1qo5PbqB4bX/I96fEN+/ipIaHwd0eAzIsLEs2xfzbYmJ8RAUscn7BQYwK2hx4fVFuxr9ztnJfPrmJKih2GEHRtBnvaUr8guGV1uqWyeOrv8WlRk79hbI82AAoAUDmq+mVg+6qggUrnU0F16wucPoToaxvbkrJBSlRx0J+9rnja4l3282F5eJFHWmf2Rk x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN4PR12MB0819; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(75325880899374)(17755550239193); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6042046)(6043046); SRVR:BN4PR12MB0819; BCL:0; PCL:0; RULEID:; SRVR:BN4PR12MB0819; x-forefront-prvs: 0071BFA85B x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(13464003)(377454003)(24454002)(199003)(189002)(53474002)(76576001)(101416001)(2950100001)(66066001)(81156014)(81166006)(122556002)(2900100001)(8936002)(77096005)(2906002)(5660300001)(7736002)(97736004)(19580405001)(7696004)(305945005)(11100500001)(74316002)(4326007)(110136003)(54356999)(8676002)(76176999)(10400500002)(19580395003)(7846002)(15975445007)(50986999)(3846002)(99286002)(102836003)(6116002)(92566002)(105586002)(93886004)(3280700002)(87936001)(106356001)(586003)(3660700001)(5002640100001)(33656002)(86362001)(230783001)(9686002)(189998001)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:BN4PR12MB0819; H:BN4PR12MB0818.namprd12.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: chelsio.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: chelsio.com X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Sep 2016 15:41:40.7359 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 065db76d-a7ae-4c60-b78a-501e8fc17095 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN4PR12MB0819 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 15:56:10 -0000 Thanks Navdeep, Now I understood that if any C file want to use a specific= 'options' (defined in the config file), then its corresponding .h file(fou= nd at sys/conf/options) needs to be included. #include "opt_bpf.h" My issue resolved after adding the above line in all C files which used BPF= _FILTER macro. Thanks, Krishna. -----Original Message----- From: Navdeep Parhar [mailto:nparhar@gmail.com] On Behalf Of Navdeep Parhar Sent: Tuesday, September 20, 2016 12:04 PM To: KrishnamRaju ErapaRaju Cc: Bjoern A. Zeeb ; freebsd-net@freebsd.or= g Subject: Re: unable to use BPF Just-In-Time compiler Use "options BPF_JITTER" in your kernconf. If this is new code you must in= clude opt_bpf.h in it. If it's part of a module then the module's makefile= must have opt_bpf.h in its SRCS. When in doubt take a look at all the obt= _bpf.h in your obj tree after the buildkernel and see if they have "#define= BPF_JITTER 1" or not. Remove all opt_bpf.h files in the obj tree and retr= y buildkernel if all else fails. Regards, Navdeep On Mon, Sep 19, 2016 at 10:41:38AM +0000, KrishnamRaju ErapaRaju wrote: > Thanks for your response Bjeorn. >=20 > I added "device bpf_jitter" line as you suggested, but not luck. > Still no code under BPF_JITTER macro is executing. >=20 > Please help me enabling JIT compiler. >=20 > Thanks, > Krishna. > -----Original Message----- > From: Bjoern A. Zeeb [mailto:bzeeb-lists@lists.zabbadoz.net] > Sent: Sunday, September 18, 2016 2:41 AM > To: KrishnamRaju ErapaRaju > Cc: freebsd-net@freebsd.org > Subject: Re: unable to use BPF Just-In-Time compiler >=20 > On 15 Sep 2016, at 5:32, KrishnamRaju ErapaRaju wrote: >=20 > > Hi, > > > > I want to use BPF JIT Kernel APIs in FreeBSD(like: bpf_jitter(),=20 > > etc..), for implementing TCP connection packet filtering. > > > > I have followed below instructions as specified in:=20 > > https://lists.freebsd.org/pipermail/freebsd-current/2005-December/05 > > 86 > > 03.html > > > > STEPS followed: > > --------------------- > > cp /usr/src/sys/amd64/conf/GENERIC /usr/src/sys/amd64/conf/MYKERNEL > > > > And added below line in MYKERNEL config file. > > options BPF_JITTER >=20 > I think you want >=20 > device bpf_jitter >=20 > The options line to my understanding only turns it on by default. >=20 > > > > make buildkernel KERNCONF=3DMYKERNEL > > make installkernel KERNCONF=3DMYKERNEL reboot > > > > But after reboot the flag BPF_JITTER is not getting enabled(all the=20 > > code inside "#ifdef BPF_JITTER" is not getting executed). > > > > Am I missing something? > > > > Also it looks like there are not many updates to BPF JIT code since=20 > > 2005, is it stable? anyone using it? > > > > Thanks, > > Krishna. > > _______________________________________________ > > freebsd-net@freebsd.org mailing list=20 > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Sep 20 16:02:07 2016 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 637FEBE14CF for ; Tue, 20 Sep 2016 16:02:07 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::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 20D809F8; Tue, 20 Sep 2016 16:02:07 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by mail-yb0-x235.google.com with SMTP id d69so9286073ybf.2; Tue, 20 Sep 2016 09:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1JnxgAhkhu8ZL7QSEes5kTKElp2q+Za3tkX0X/XowYM=; b=ass5jwEL8Ou/GYxfi5eFcA6whEdXkutscZxUZCoFEsz2X8a1OGGLqeu2SKH36cc+T+ jONRC02KzRnRLvERMzKnskQ7FfxDwgXfaKXQhwnXVmyx6YUBPOvBUTDwOrSYzb1wqYEO wquG7IEIx1i+ZDcQICN58Z+sR1YW5mFPAeoumw3ONx7ykttxlYK5yARXgzqVQLF+TiNE pWX+6Txb5XNrX+vuYJ1bBuOTTnjSSUVCeA0SummxhpM6IzD8tod9yCdp9jyD0INnaLt6 BALQZbZ5xKeUYdK6cS2Hqa3XVMokn229K4krLX2lXg4C8wgdkRCikDSIujYl4rl6KMIP lekA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1JnxgAhkhu8ZL7QSEes5kTKElp2q+Za3tkX0X/XowYM=; b=bJQiG0iVoz89i0rgJ1Kt/h8VWNdxYq7ygq2nPwfoDHGjU7z7TUsO5XqGv6QTwMVC2G 7xxNMD/G06BZVyQkSv0pcZBPULbIlHdvaxDSOgJbhRqb4zkMg6RKgMnAodysiY+k78Bp 40vkn+k2n6TH/qjJLkxS540hOQQxRUVZRRc+ZOOdixGo8bJQK6/A9FcRwpD5YZUi/vMy kHpiIbaK+8s6FSlpri0rHweGy7KxjQituK5xACO1eIwnECnH7+1s92Uq0mT1mj6NMABv y6anOK36lhfjuK6BrGHDVgVeH2KpbUdTPIDb5AxW4NwMvODiGPyV8eGZvOII7V4FbRrB m0Pw== X-Gm-Message-State: AE9vXwP+DwNHkYG2y7G8K3FG971IlkvbHm5N8QHbLtB9/D7fMfPsg8nh6wBy0tKDV3phmOHZHEhjMo7afr34RQ== X-Received: by 10.31.41.214 with SMTP id p205mr5077507vkp.138.1474386975310; Tue, 20 Sep 2016 08:56:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.168.88 with HTTP; Tue, 20 Sep 2016 08:56:14 -0700 (PDT) In-Reply-To: References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> From: Jack Vogel Date: Tue, 20 Sep 2016 08:56:14 -0700 Message-ID: Subject: Re: Will this card (probably) work? To: Sean Bruno Cc: Lee Brown , freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 16:02:07 -0000 On Tue, Sep 20, 2016 at 8:47 AM, Sean Bruno wrote: > > > On 09/20/16 03:42, Lee Brown wrote: > > > > > > On Mon, Sep 19, 2016 at 1:48 PM, Sean Bruno > > wrote: > > > > > > > > On 09/19/16 14:17, Lee Brown wrote: > > > I am looking to purchase this > > > > card > > > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter > > I350-F4), > > > into which I intend to use 1000-LX SFP's. > > > > > > If I'm understanding correctly, the igb(4) driver supports the > > i350 (not > > > sure if i350AM4 is the same) and altq(4) states the igb(4) driver > is > > > supported (which I'll be needing). > > > > > > Does this look like a viable PCIe card for me to get? > > > > > > Thanks in advance -- lee > > > _______________________________________________ > > > freebsd-net@freebsd.org mailing > list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > > > > To unsubscribe, send any mail to > > "freebsd-net-unsubscribe@freebsd.org > > " > > > > > > > In order to really know, I'd need to know the pci-id that this thing > > shows up as. > > > > sean > > > > Thanks, I've reached out for that info. > > Otherwise, if you happen to know of a 4-port or even 2-port PCIe card > > that supports 1000Base-LX or SFP's that will, I'm all ears. I'd > > consider a single port card as last resort. > > > > Pretty sure that the i350 is what you're in the market for. Just not > sure if it will show up as an igb(4) nic. If it doesn't, it'd be > trivial to add the pci-ids if it is just a variant. > > sean > > What else would it show up as :) ? From owner-freebsd-net@freebsd.org Tue Sep 20 17:02:16 2016 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 D69CDBE2F76 for ; Tue, 20 Sep 2016 17:02:16 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::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 A5F61144D; Tue, 20 Sep 2016 17:02:16 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by mail-yb0-x22d.google.com with SMTP id 2so5035835ybv.0; Tue, 20 Sep 2016 10:02:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xCghAdcN/mAy34e8hLeOcNCIGyz/piB4+XUfzxrP0dk=; b=PZz+6/bHxy+sAg1/kz4saLS2bCY+ZVtLsC7B5CFzWCva+msHnJey9G9IBPwxT4i6IV x9qZ1JwSD9bvjGzk2qSlfgi+ppHoFtCXe0/EEYGXV4w10bEGClzoAqpilm38RYGMLj4O RxBB/8GsRd0CN2clPXwKUG62WjrFnW4yznTRVXCbY7tgkw8HblqwFcNDf8O5XZFB0x9M Jg+cOok3w4PN7K8dAJDSSFPIuSh8twm/j1slZkNWgitor+VbDx00Im7BBXfwnke0vmym ei6Y5DTvXq4B9azXcfc56QHhIutsl4sq4aOxBxPayE/oWC0O90PXs9ZY91mE9oHshDcC 5ZEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xCghAdcN/mAy34e8hLeOcNCIGyz/piB4+XUfzxrP0dk=; b=QLy3jGxtETm7DBie7zmuTCtXjoErPXL8jnE9CziTXPU0EiZVRbujztVUd1qXsSL/Et 5u8NOe9spCtRknquTFxhH0naQSRT2cTuU/LRl+hEL6f7O67In++mn+k0V1iFbSdBo+M1 S3P6Y/En79+L0yL5QetS0QkIPTkWzhs2hM6jH2L0skruQ7PB14Rn5rv8S8EHYjxorxr0 H3HxWGc0u+9hJHZrwZ9sIhI6wdz4onfqix1wRErwBh+hYxdyEkSJBvZcZZk+tt1DhVmc UQa/DB1Jf6KHuFCpD6nncQf1eWZC6Kbr4s7yJuow5F/wy6Xn3LY/6+5pjH7UoCWCAp6J mCaQ== X-Gm-Message-State: AE9vXwPN52/k8WI3KtfTOnGXfgajISpCWESc8ld8tW7lvHfrRiRTkc2lyZGnly7WcrHQNUn+0BdOycUHWLrqUw== X-Received: by 10.37.209.136 with SMTP id i130mr14048745ybg.83.1474390935702; Tue, 20 Sep 2016 10:02:15 -0700 (PDT) MIME-Version: 1.0 References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> In-Reply-To: From: Eric Joyner Date: Tue, 20 Sep 2016 17:02:05 +0000 Message-ID: Subject: Re: Will this card (probably) work? To: Jack Vogel , Sean Bruno Cc: Lee Brown , freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 17:02:17 -0000 There are SFP i350 cards, but hopefully this one has a valid eeprom and isn't counterfeit. I remember someone submitted a bug for ixgbe where the device ID showed up as 0x0001 and they wanted to patch that into the driver. On Tue, Sep 20, 2016 at 9:02 AM Jack Vogel wrote: > On Tue, Sep 20, 2016 at 8:47 AM, Sean Bruno wrote: > > > > > > > On 09/20/16 03:42, Lee Brown wrote: > > > > > > > > > On Mon, Sep 19, 2016 at 1:48 PM, Sean Bruno > > > wrote: > > > > > > > > > > > > On 09/19/16 14:17, Lee Brown wrote: > > > > I am looking to purchase this > > > > > > card > > > > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter > > > I350-F4), > > > > into which I intend to use 1000-LX SFP's. > > > > > > > > If I'm understanding correctly, the igb(4) driver supports the > > > i350 (not > > > > sure if i350AM4 is the same) and altq(4) states the igb(4) driver > > is > > > > supported (which I'll be needing). > > > > > > > > Does this look like a viable PCIe card for me to get? > > > > > > > > Thanks in advance -- lee > > > > _______________________________________________ > > > > freebsd-net@freebsd.org mailing > > list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > > > > > > To unsubscribe, send any mail to > > > "freebsd-net-unsubscribe@freebsd.org > > > " > > > > > > > > > > In order to really know, I'd need to know the pci-id that this > thing > > > shows up as. > > > > > > sean > > > > > > Thanks, I've reached out for that info. > > > Otherwise, if you happen to know of a 4-port or even 2-port PCIe card > > > that supports 1000Base-LX or SFP's that will, I'm all ears. I'd > > > consider a single port card as last resort. > > > > > > > Pretty sure that the i350 is what you're in the market for. Just not > > sure if it will show up as an igb(4) nic. If it doesn't, it'd be > > trivial to add the pci-ids if it is just a variant. > > > > sean > > > > > What else would it show up as :) ? > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Tue Sep 20 17:05:30 2016 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 CA323BE22E9 for ; Tue, 20 Sep 2016 17:05:30 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "FMSMGA104.fm.intel.com", Issuer "Intel External Issuing CA 6B" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA4461781; Tue, 20 Sep 2016 17:05:30 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP; 20 Sep 2016 10:05:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,369,1470726000"; d="scan'208";a="881974969" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by orsmga003.jf.intel.com with ESMTP; 20 Sep 2016 10:05:20 -0700 Received: from orsmsx113.amr.corp.intel.com (10.22.240.9) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 20 Sep 2016 10:05:17 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.59]) by ORSMSX113.amr.corp.intel.com ([169.254.9.173]) with mapi id 14.03.0248.002; Tue, 20 Sep 2016 10:05:16 -0700 From: "Pieper, Jeffrey E" To: Jack Vogel , Sean Bruno CC: Lee Brown , freebsd-net Subject: RE: Will this card (probably) work? Thread-Topic: Will this card (probably) work? Thread-Index: AQHSE1hid60fbKdHQ0qIzg7IHU5026CCmqkA Date: Tue, 20 Sep 2016 17:05:15 +0000 Message-ID: <2A35EA60C3C77D438915767F458D656883946510@ORSMSX111.amr.corp.intel.com> References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMmU3YTI1NTgtZDczOC00MWFiLWJjMWYtZTM3YmVlM2I0ZjdiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlBCTjFod2dtZ1AreW9NOU1nTkoySGhsdDJOM1wvZlREcXJoQnRSUEZ0dExFPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 17:05:30 -0000 -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of Jack Vogel Sent: Tuesday, September 20, 2016 8:56 AM To: Sean Bruno Cc: Lee Brown ; freebsd-net Subject: Re: Will this card (probably) work? On Tue, Sep 20, 2016 at 8:47 AM, Sean Bruno wrote: > > > On 09/20/16 03:42, Lee Brown wrote: > > > > > > On Mon, Sep 19, 2016 at 1:48 PM, Sean Bruno > > wrote: > > > > > > > > On 09/19/16 14:17, Lee Brown wrote: > > > I am looking to purchase this > > > > card > > > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter > > I350-F4), > > > into which I intend to use 1000-LX SFP's. > > > > > > If I'm understanding correctly, the igb(4) driver supports the > > i350 (not > > > sure if i350AM4 is the same) and altq(4) states the igb(4) driver > is > > > supported (which I'll be needing). > > > > > > Does this look like a viable PCIe card for me to get? > > > > > > Thanks in advance -- lee > > > _______________________________________________ > > > freebsd-net@freebsd.org mailing > list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > > > > To unsubscribe, send any mail to > > "freebsd-net-unsubscribe@freebsd.org > > " > > > > > > > In order to really know, I'd need to know the pci-id that this thin= g > > shows up as. > > > > sean > > > > Thanks, I've reached out for that info. > > Otherwise, if you happen to know of a 4-port or even 2-port PCIe card > > that supports 1000Base-LX or SFP's that will, I'm all ears. I'd > > consider a single port card as last resort. > > > > Pretty sure that the i350 is what you're in the market for. Just not > sure if it will show up as an igb(4) nic. If it doesn't, it'd be > trivial to add the pci-ids if it is just a variant. > > sean > > What else would it show up as :) ? As long as the controller isn't counterfeit...which I would be wary of. I'v= e never seen a low profile i350-F4, mainly due to overheating. You can tell= if you can see the components, but in this case the entire card is covered= by the heatsink. Jeff _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Sep 20 17:20:07 2016 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 292D2BE29F2 for ; Tue, 20 Sep 2016 17:20:07 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::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 D4CB51D2; Tue, 20 Sep 2016 17:20:06 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id t7so21871199qkh.2; Tue, 20 Sep 2016 10:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1PoSFzAqrI+9tZhPKyhnBhZ8opRtn1FwXpfSOKj7gjU=; b=0QdK0ChheXJNUtDDYcfN+IYLE5Wz/UmPS7TQMHOwGWxKl1WKZQj8wXaPl+q3GEQxvY SF2YYQIwJSr6nmv7JlcdnvNYH/HACkF/S4M/FY9SjjxiEwlbfgZsamIS+dQAtdyzEdpm nULzR2/hCQI9cnDeLlzZi0veJYrs0MSlLN+egBFnknaZCq+63XkEKd2bhOi0AhWR+guY zAjzUSUyI/KoJGx1+9OSTTXKMsxZBY2jeW72+DjXYl4vrGmhS29MlOO7gf+dR/auab2E gnmHQTxyziSZAUjEFM5hUNErRTV59G5zTga61oWfBIRfDyn6Qw/QXet8q9dTP3znXvXo TFLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1PoSFzAqrI+9tZhPKyhnBhZ8opRtn1FwXpfSOKj7gjU=; b=Cdyz/1eqb1zq9ZnqWts6RsnhdklQ6z9ym2rTh9pMuw33KJMXV5/WB4cEn4hyFR+fA4 02ca6ZLaTIh5XICVhO9x6kp9DOvnSz0ojUu41fQLucaPftL9leHIR346ymLkjvCrHiOZ F6y011NLYY11fxZm86NxtRPMrlMqEjGv70cyTi4C4Fc0m4PpvTyJ6OP8rROd7QNexHkq ZhlKsXLwsmfORaU60LeuEpI90ExYynSRa8An1C3OUXGGkURYUXuoZtwn2WUBQBl+UPIz ctVniHmi6QWZn2d29yGdgYB2QSPQeGbXWM+Gxb5jeI3tloZW1nYI8sS9837DzaPLbkVS 5hOg== X-Gm-Message-State: AE9vXwNsFwyTmuX7ZwnYK3lth6F6oS+9ckIKZk8karvtD6FjIqYhcuT6eNqTckyuEmOzyYOuALsSDDqSqYpghA== X-Received: by 10.55.138.67 with SMTP id m64mr38331463qkd.265.1474392006085; Tue, 20 Sep 2016 10:20:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.131.102 with HTTP; Tue, 20 Sep 2016 10:20:05 -0700 (PDT) In-Reply-To: <2A35EA60C3C77D438915767F458D656883946510@ORSMSX111.amr.corp.intel.com> References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> <2A35EA60C3C77D438915767F458D656883946510@ORSMSX111.amr.corp.intel.com> From: Freddie Cash Date: Tue, 20 Sep 2016 10:20:05 -0700 Message-ID: Subject: Re: Will this card (probably) work? To: "Pieper, Jeffrey E" Cc: Jack Vogel , Sean Bruno , Lee Brown , freebsd-net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 17:20:07 -0000 On Tue, Sep 20, 2016 at 10:05 AM, Pieper, Jeffrey E < jeffrey.e.pieper@intel.com> wrote: > What else would it show up as :) ? > > As long as the controller isn't counterfeit...which I would be wary of. > I've never seen a low profile i350-F4, mainly due to overheating. You can > tell if you can see the components, but in this case the entire card is > covered by the heatsink. > =E2=80=8BThis page, straight from Intel, says the F4 variant only comes in = a full-height format: =E2=80=8B http://www.intel.com/content/www/us/en/ethernet-products/gigabit-server-ada= pters/ethernet-server-adapter-i350.html All the other variants (T2, T4, F2) come in low-profile formats. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-net@freebsd.org Tue Sep 20 17:27:50 2016 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 2F7F9BE2C9A for ; Tue, 20 Sep 2016 17:27:50 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 DE7B7A94 for ; Tue, 20 Sep 2016 17:27:49 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by mail-yw0-x229.google.com with SMTP id u82so16731100ywc.2 for ; Tue, 20 Sep 2016 10:27:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c2xnUuc4Ur5CJTfJgYcpz8zZvODt88nqMa/elY3fkLI=; b=gIHWZsPA6w2cUXrsaQsPhzL+F2yZmEqaPItB7xdvFtQWA3JlMBI30uFTeN4CznDkK6 FnX+LV7fUB8lEEVINACKLDOqbeVzoaeS4jNttoWzDz8FX3sSP1MqTLbZSQh1lkkSldAu Gj0AIFL1bqDoM/SKBkqjRa9AlskCYph31cAnqkxizDQfjn8Rb51PJYfX06eGGWV+q8tS J8QjzfkrUTBAAMQN2gBFmoEuLOQNPa5ibXdjKMRZUtgS0VpjjjXj00Hc8eTYsf5P+M7x fJKPF8qVikpjR/FMNxaAf2aNcs/hE18b/BJXSrVsBB8K79QXOczHyjODWsmeaeVv6/nq jfyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c2xnUuc4Ur5CJTfJgYcpz8zZvODt88nqMa/elY3fkLI=; b=Z6aPQmc3OZ/lZbE6fAyW53/vV0jyDMnPRm2zDgFvVDbMPkSYk2hgIUpigXT52iX1d8 /nqpwBPhXcwhE7muHgOvq1cCcwXk5U7c6rf7RZn/1zQGRckWP64/81BvuczUTSlsCR2O nsO/Kmh+29BvKV4vmJWFeUz2O7dg0R2ElIt0GGPzhe3FwruSIXxaStQTLQXOAzHZnf7K xJTynFSmd2rmO12c3j0NhRc5bAgoGK8yzOGzuzl9v1K2yQdtg7CgPcTmCQ+qZ1oaI+l/ jZ+7u5dHgm2VO3BPUb7QdBYaHgJfNsiO1yq0N3+KneYIhyMtBvGLqi3qwSdhBdiFrCfp P95w== X-Gm-Message-State: AE9vXwOQGOdtAvHTNzxA8ZWADvKfFBnBAda9ohF8vg7pGqrB58fQOUc212ZUrm11xfoj1qVSzS6j9h8RG5Aihw== X-Received: by 10.13.206.134 with SMTP id q128mr29035998ywd.270.1474392469015; Tue, 20 Sep 2016 10:27:49 -0700 (PDT) MIME-Version: 1.0 References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> <2A35EA60C3C77D438915767F458D656883946510@ORSMSX111.amr.corp.intel.com> In-Reply-To: From: Eric Joyner Date: Tue, 20 Sep 2016 17:27:38 +0000 Message-ID: Subject: Re: Will this card (probably) work? To: Freddie Cash , "Pieper, Jeffrey E" Cc: Lee Brown , freebsd-net , Jack Vogel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 17:27:50 -0000 Other OEMs can make their own designs that use Intel chips -- e.g. Silicom makes a 6-port full height SFP card that combines a 4-port I350AM4 with a 2-port I350 AM2. It's just that the further away you get from an Intel design, the less support we'll be able to give you if something goes wrong. And buying a card on ebay, and made by a relatively unknown OEM (to me at least) doesn't help. On Tue, Sep 20, 2016 at 10:20 AM Freddie Cash wrote: > On Tue, Sep 20, 2016 at 10:05 AM, Pieper, Jeffrey E < > jeffrey.e.pieper@intel.com> wrote: > > > What else would it show up as :) ? > > > > As long as the controller isn't counterfeit...which I would be wary of. > > I've never seen a low profile i350-F4, mainly due to overheating. You c= an > > tell if you can see the components, but in this case the entire card is > > covered by the heatsink. > > > > =E2=80=8BThis page, straight from Intel, says the F4 variant only comes i= n a > full-height format: > =E2=80=8B > > http://www.intel.com/content/www/us/en/ethernet-products/gigabit-server-a= dapters/ethernet-server-adapter-i350.html > > All the other variants (T2, T4, F2) come in low-profile formats. > > > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Sep 20 18:57:02 2016 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 EBD23BE2F12 for ; Tue, 20 Sep 2016 18:57:02 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A88E33F0 for ; Tue, 20 Sep 2016 18:57:02 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-vk0-x22f.google.com with SMTP id b133so37264611vka.3 for ; Tue, 20 Sep 2016 11:57:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xqql3pSvNYcMmzd+OfRja3511b5aMJR5L9gOYpZO1Jo=; b=i7BTNy9e/GmG5iX8a65Gvq6NPYylg1WSkRkuuaB/+o0O9ItlGmWnuhjp4U9tZAfrXq qbUA4bs7eZA44A6n2ZRac4mNxfq0Vheqg7TtE9uRxoAoNcKVEwjnXaLnjtrRc7FXVKd+ GdFdXstSeNwv4TiAmf1zHFlLJGerQobvMywhGazQuQhO+0LJkjS0xcKIkbeJX8UmHPGU QihLAKibMUHxEXdcjCEL3qXJEnQQxZp9sfZOc3pKPWaFkR3OplTyh4yRJ9Oqc66NjSC9 LlavOSwM2xT7se+zMkLo0RCs2Yf5gvyxG9Ho6mPz6u2DCmKxptUnNDaVSvcnFcfHgoKF kOOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xqql3pSvNYcMmzd+OfRja3511b5aMJR5L9gOYpZO1Jo=; b=Q2XY1wq9tauBvYqf3T4VIlNDLYxg5eW3qrGWBdTEe41zQqBeC2MEjlBlxns/jFDa1W CQ7B0LEGIM+fwIEIlgkofv0VEetoQjAcrlscN6egwwgb2E97Xku9Ysm41ViTP4k4F127 FaXlB/lcUzKr6PnCWC0evRNGxfC38tsw3Q4Ro4SyuQ1c5dGJmbPTwLUt99elzbuWssps 2Xm7Fkxx5uRgqNypUkVO5Is/GgUx8CbiN4UqP61J9hbHxCbinsXjuzD5Z8gE4ZJhSkxt KtoNbpTLpfBLWQtoUVwiu3YhzPmfknfddpevP/5ejObcrhYkCBhoaEElcbKJIKns2dea SLYA== X-Gm-Message-State: AE9vXwMR+4mZCY7wjOFA09jWB8I/+H7xPoyXGoFDM/TxEqOqR39PImty/BCjhOjZFhQlpg0l5KfwuieLBEAmMQ== X-Received: by 10.31.6.211 with SMTP id 202mr5488890vkg.106.1474397819061; Tue, 20 Sep 2016 11:56:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.65.38 with HTTP; Tue, 20 Sep 2016 11:56:57 -0700 (PDT) In-Reply-To: References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> <2A35EA60C3C77D438915767F458D656883946510@ORSMSX111.amr.corp.intel.com> From: Lee Brown Date: Tue, 20 Sep 2016 11:56:57 -0700 Message-ID: Subject: Re: Will this card (probably) work? To: Eric Joyner Cc: Freddie Cash , "Pieper, Jeffrey E" , freebsd-net , Jack Vogel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 18:57:03 -0000 I agree, but unfortunately nothing Intel offers came remotely close. They have only 1 card that does singlemode, which is a single port to boot and I can't stick 4 of those in my server. My choice was merely the only thing I could find :( I think I'm going to be better off getting some managed media converters and a normal copper gigabit card that is well known and supported. Singlemode cards are hard to find at best and this router will get heavy use I expect. Still waiting for PCI vendor information. Thanks -- lee On Tue, Sep 20, 2016 at 10:27 AM, Eric Joyner wrote: > Other OEMs can make their own designs that use Intel chips -- e.g. Silico= m > makes a 6-port full height SFP card that combines a 4-port I350AM4 with a > 2-port I350 AM2. > > It's just that the further away you get from an Intel design, the less > support we'll be able to give you if something goes wrong. And buying a > card on ebay, and made by a relatively unknown OEM (to me at least) doesn= 't > help. > > On Tue, Sep 20, 2016 at 10:20 AM Freddie Cash wrote: > >> On Tue, Sep 20, 2016 at 10:05 AM, Pieper, Jeffrey E < >> jeffrey.e.pieper@intel.com> wrote: >> >> > What else would it show up as :) ? >> > >> > As long as the controller isn't counterfeit...which I would be wary of= . >> > I've never seen a low profile i350-F4, mainly due to overheating. You >> can >> > tell if you can see the components, but in this case the entire card i= s >> > covered by the heatsink. >> > >> >> =E2=80=8BThis page, straight from Intel, says the F4 variant only comes = in a >> full-height format: >> =E2=80=8B >> http://www.intel.com/content/www/us/en/ethernet-products/ >> gigabit-server-adapters/ethernet-server-adapter-i350.html >> >> All the other variants (T2, T4, F2) come in low-profile formats. >> >> >> -- >> Freddie Cash >> fjwcash@gmail.com >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@freebsd.org Wed Sep 21 02:24:56 2016 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 CFA9FBE0803 for ; Wed, 21 Sep 2016 02:24:56 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-yb0-x22b.google.com (mail-yb0-x22b.google.com [IPv6:2607:f8b0:4002:c09::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 95D116E4 for ; Wed, 21 Sep 2016 02:24:56 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-yb0-x22b.google.com with SMTP id x93so18795405ybh.1 for ; Tue, 20 Sep 2016 19:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EJfIDZzgnn3cJrcLT4Ckgj1bzFpi5xw0mQs/M/Ayp90=; b=mLc1XBe8zzs4Mfbkbn5122j76DR4Ul2SqXCKRdNYZyID78tTrhsBzyf7OoLSICNdiA NFoPTML53PCFuhem5M0h7UMpwiEtFWsfQ/3oH0FqCrtouCJOiQ20GKNeRjEOi09P8897 akY/XLRvmSwNlInxrJD7YvKIAkHBSfCoETjyObc+P+WJKNzwbBxftCDyi0bmiO5jF1Mp 1/jCyfUyeqHUpMqBTQh2/31fgoQpxLWCMC8s/ZzZeHy3e31Bo6qX63QIQR7CWxW/Mufg Uoms/J+O3x/LaqI3YULlWK27frNjbQjz4nu5irA00qiHIKcOkYMd46kheMdogRfTkHJ5 HKeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EJfIDZzgnn3cJrcLT4Ckgj1bzFpi5xw0mQs/M/Ayp90=; b=HPhY737UB/JAxaoQ6PqVNSIQ6ARfT1GhAPNV5A/pDMsEzYMrFyAzUe7i+h0Uj5pvbH MiNkZ/W7GSjzr1ROruysXMClvC7q9NZZOcVP3BffDBazNeUJamDIebe7iT4byT/3RQgO EsWUd9nT6FRdLEMDXjvLVPB7DSI2PvWu1l3mVfemWLRq6bXCmjz4gga9pdnlmyUHI5vq 5xSq5Ohr3/JmA5P3JvHLq3mAZZoilbExJFreR51kayGm3fb6rWLdQd7F71E1ARRVKiU/ Zmozh50kvbPMErZOScQOyO1Mcg3CJqjX8ca3IqV4UhzSzSW+24EV+bXZnhvIngXr9FCx DIAg== X-Gm-Message-State: AE9vXwMEffrIb3XpbEeg7gF0fy/qUhcLLYxJnfbFt/cDBaUxZ0Z5nWaIINQkhdoB7a51sHKEZC5qTcOOW4BcRg== X-Received: by 10.37.124.135 with SMTP id x129mr33826608ybc.24.1474424695547; Tue, 20 Sep 2016 19:24:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.65.38 with HTTP; Tue, 20 Sep 2016 19:24:54 -0700 (PDT) In-Reply-To: References: <53c8aa26-6bd5-22ed-8987-f901451e4dfd@freebsd.org> From: Lee Brown Date: Tue, 20 Sep 2016 19:24:54 -0700 Message-ID: Subject: Re: Will this card (probably) work? To: Sean Bruno Cc: freebsd-net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 02:24:56 -0000 On Tue, Sep 20, 2016 at 8:47 AM, Sean Bruno wrote: > > > On 09/20/16 03:42, Lee Brown wrote: > > > > > > On Mon, Sep 19, 2016 at 1:48 PM, Sean Bruno > > wrote: > > > > > > > > On 09/19/16 14:17, Lee Brown wrote: > > > I am looking to purchase this > > > > card > > > (LR-LINK I350AM4 Chip Quad SFP Port 1000Base-X Server Adapter > > I350-F4), > > > into which I intend to use 1000-LX SFP's. > > > > > > If I'm understanding correctly, the igb(4) driver supports the > > i350 (not > > > sure if i350AM4 is the same) and altq(4) states the igb(4) driver > is > > > supported (which I'll be needing). > > > > > > Does this look like a viable PCIe card for me to get? > > > > > > Thanks in advance -- lee > > > _______________________________________________ > > > freebsd-net@freebsd.org mailing > list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-net > > > > > To unsubscribe, send any mail to > > "freebsd-net-unsubscribe@freebsd.org > > " > > > > > > > In order to really know, I'd need to know the pci-id that this thing > > shows up as. > > > > sean > > > > Thanks, I've reached out for that info. > > Otherwise, if you happen to know of a 4-port or even 2-port PCIe card > > that supports 1000Base-LX or SFP's that will, I'm all ears. I'd > > consider a single port card as last resort. > > > > Pretty sure that the i350 is what you're in the market for. Just not > sure if it will show up as an igb(4) nic. If it doesn't, it'd be > trivial to add the pci-ids if it is just a variant. > > sean > > OK the vendor got back to me: 8086:1522 From owner-freebsd-net@freebsd.org Wed Sep 21 07:43:25 2016 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 99126BE30F0 for ; Wed, 21 Sep 2016 07:43:25 +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 mx1.freebsd.org (Postfix) with ESMTPS id 885EEF52 for ; Wed, 21 Sep 2016 07:43:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8L7hOMT049177 for ; Wed, 21 Sep 2016 07:43:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212876] re(4): Add support for NCube 8168 network cards Date: Wed, 21 Sep 2016 07:43:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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 Only Me X-Bugzilla-Who: t@tobik.me X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform bug_file_loc op_sys bug_status keywords bug_severity priority component assigned_to reporter cc flagtypes.name attachments.created Message-ID: 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 07:43:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212876 Bug ID: 212876 Summary: re(4): Add support for NCube 8168 network cards Product: Base System Version: CURRENT Hardware: Any URL: https://forums.freebsd.org/threads/57734/ OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: t@tobik.me CC: freebsd-net@FreeBSD.org Attachment #175029 maintainer-approval?(freebsd-net@FreeBSD.org) Flags: Flags: mfc-stable10?, mfc-stable11? Created attachment 175029 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175029&action= =3Dedit if_re.diff User goshanecr on the forums has a Realtek 8168 based which identifies itse= lf as 03:00.0 Ethernet controller: NCube Device 8168 (rev 06) class=3D0x020000 card=3D0x34687470 chip=3D0x816810ff rev=3D0x06 hdr=3D0x00 which is currently not recognized by re(4). Adding a new entry to re_devs seems to be all that is needed to support this card. See the forum thread = for more details. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Sep 21 07:43:25 2016 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 2D9FCBE30ED for ; Wed, 21 Sep 2016 07:43:25 +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 mx1.freebsd.org (Postfix) with ESMTPS id 1955AF50 for ; Wed, 21 Sep 2016 07:43:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8L7hOMP049177 for ; Wed, 21 Sep 2016 07:43:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: maintainer-approval requested: [Bug 212876] re(4): Add support for NCube 8168 network cards : [Attachment 175029] if_re.diff Date: Wed, 21 Sep 2016 07:43:25 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: Message-ID: In-Reply-To: References: 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 07:43:25 -0000 Tobias Kortkamp has asked freebsd-net@FreeBSD.org for maintainer-approval: Bug 212876: re(4): Add support for NCube 8168 network cards https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212876 Attachment 175029: if_re.diff https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175029&action=3Dedit --- Description --- User goshanecr on the forums has a Realtek 8168 based which identifies itse= lf as 03:00.0 Ethernet controller: NCube Device 8168 (rev 06) class=3D0x020000 card=3D0x34687470 chip=3D0x816810ff rev=3D0x06 hdr=3D0x00 which is currently not recognized by re(4). Adding a new entry to re_devs seems to be all that is needed to support this card. See the forum thread = for more details. From owner-freebsd-net@freebsd.org Wed Sep 21 14:15:29 2016 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 97D14BE367F for ; Wed, 21 Sep 2016 14:15:29 +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 mx1.freebsd.org (Postfix) with ESMTPS id 8722719D1 for ; Wed, 21 Sep 2016 14:15:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8LEFTxO067175 for ; Wed, 21 Sep 2016 14:15:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212876] re(4): Add support for NCube 8168 network cards Date: Wed, 21 Sep 2016 14:15:29 +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: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 14:15:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212876 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: kevlo Date: Wed Sep 21 14:15:16 UTC 2016 New revision: 306102 URL: https://svnweb.freebsd.org/changeset/base/306102 Log: Add support for the TP-Link TG-3468 v2. This is an RTL8168 chip, which we already support so all we have to do is= add the vendor ID. PR: 212876 Submitted by: Tobias Kortkamp MFC after: 3 days Changes: head/share/man/man4/re.4 head/sys/dev/re/if_re.c head/sys/dev/rl/if_rlreg.h --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Sep 21 14:17:37 2016 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 88186BE389C for ; Wed, 21 Sep 2016 14:17:37 +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 mx1.freebsd.org (Postfix) with ESMTPS id 7763B1D4C for ; Wed, 21 Sep 2016 14:17:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8LEHb92070672 for ; Wed, 21 Sep 2016 14:17:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212876] re(4): Add support for NCube 8168 network cards Date: Wed, 21 Sep 2016 14:17:37 +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: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kevlo@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: cc resolution 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 14:17:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212876 Kevin Lo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevlo@FreeBSD.org Resolution|--- |FIXED Status|New |Closed --- Comment #2 from Kevin Lo --- Committed as r306102 with minor modifications, thanks. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Sep 21 14:31:31 2016 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 6BC40BE3C41 for ; Wed, 21 Sep 2016 14:31:31 +0000 (UTC) (envelope-from gerrit.kuehn@aei.mpg.de) Received: from umail.aei.mpg.de (umail.aei.mpg.de [194.94.224.6]) (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 F0089693 for ; Wed, 21 Sep 2016 14:31:30 +0000 (UTC) (envelope-from gerrit.kuehn@aei.mpg.de) Received: from mailgate.aei.mpg.de (mailgate.aei.mpg.de [194.94.224.5]) by umail.aei.mpg.de (Postfix) with ESMTP id 142D32000E7 for ; Wed, 21 Sep 2016 16:22:15 +0200 (CEST) Received: from mailgate.aei.mpg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 049D0406ADE for ; Wed, 21 Sep 2016 16:22:15 +0200 (CEST) Received: from intranet.aei.uni-hannover.de (ahin1.aei.uni-hannover.de [130.75.117.40]) by mailgate.aei.mpg.de (Postfix) with ESMTP id D861C406ADB for ; Wed, 21 Sep 2016 16:22:14 +0200 (CEST) Received: from arc.aei.uni-hannover.de ([130.75.117.1]) by intranet.aei.uni-hannover.de (IBM Domino Release 9.0.1FP5) with ESMTP id 2016092116221448-24781 ; Wed, 21 Sep 2016 16:22:14 +0200 Date: Wed, 21 Sep 2016 16:22:14 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-net@freebsd.org Subject: igb/pf-related crashes Message-Id: <20160921162214.dcc6dca77d4a42c73df6de5e@aei.mpg.de> Organization: Max Planck Gesellschaft X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on intranet/aei-hannover(Release 9.0.1FP5|November 22, 2015) at 21/09/2016 16:22:14, Serialize by Router on intranet/aei-hannover(Release 9.0.1FP5|November 22, 2015) at 21/09/2016 16:22:14, Serialize complete at 21/09/2016 16:22:14 X-TNEFEvaluated: 1 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-PMX-Version: 6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.9.21.141217 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, MIME_LOWER_CASE 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, NO_CTA_URI_FOUND 0, NO_URI_FOUND 0, NO_URI_HTTPS 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0' X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 14:31:31 -0000 Hi all, Over the last weekend, I saw a couple of crashes on a 10.3-system acting as filtering bridge with pf that all looked like this: --- Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xe fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff81c45fb9 stack pointer = 0x28:0xfffffe01eeaa54a0 frame pointer = 0x28:0xfffffe01eeaa55d0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (irq275: igb2:que 0) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff8098e390 at kdb_backtrace+0x60 #1 0xffffffff80951066 at vpanic+0x126 #2 0xffffffff80950f33 at panic+0x43 #3 0xffffffff80d55f7b at trap_fatal+0x36b #4 0xffffffff80d5627d at trap_pfault+0x2ed #5 0xffffffff80d558fa at trap+0x47a #6 0xffffffff80d3b8d2 at calltrap+0x8 #7 0xffffffff81c2c4c8 at pf_test+0x1c8 #8 0xffffffff81c3e07d at pf_check_in+0x1d #9 0xffffffff80a24ef4 at pfil_run_hooks+0x84 #10 0xffffffff81c148e3 at bridge_pfil+0x363 #11 0xffffffff81c153a5 at bridge_forward+0x1c5 #12 0xffffffff81c13c55 at bridge_input+0x555 #13 0xffffffff80a1c05a at ether_nh_input+0x2ba #14 0xffffffff80a24092 at netisr_dispatch_src+0x62 #15 0xffffffff804f859c at igb_rxeof+0x60c #16 0xffffffff804f8c41 at igb_msix_que+0x121 #17 0xffffffff8091c99b at intr_event_execute_handlers+0xab --- Before that happening, the system was fine for about 6 months. Over the weekend I saw about 10 identical crashes and subsequent reboots like this (with sometimes only a few minutes of operation between). Running out of other ideas, I updated the system to latest release (-p7), and up to now it didn't happen again. Any ideas what might be causing this? cu Gerrit From owner-freebsd-net@freebsd.org Wed Sep 21 14:39:07 2016 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 3365CBE3F0D for ; Wed, 21 Sep 2016 14:39:07 +0000 (UTC) (envelope-from gerrit.kuehn@aei.mpg.de) Received: from umail.aei.mpg.de (umail.aei.mpg.de [194.94.224.6]) (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 B56D19FE for ; Wed, 21 Sep 2016 14:39:06 +0000 (UTC) (envelope-from gerrit.kuehn@aei.mpg.de) Received: from mailgate.aei.mpg.de (mailgate.aei.mpg.de [194.94.224.5]) by umail.aei.mpg.de (Postfix) with ESMTP id 5D36220022D for ; Wed, 21 Sep 2016 16:39:04 +0200 (CEST) Received: from mailgate.aei.mpg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4C52A406ADE for ; Wed, 21 Sep 2016 16:39:04 +0200 (CEST) Received: from intranet.aei.uni-hannover.de (ahin1.aei.uni-hannover.de [130.75.117.40]) by mailgate.aei.mpg.de (Postfix) with ESMTP id 1B4FD406ADB for ; Wed, 21 Sep 2016 16:39:04 +0200 (CEST) Received: from arc.aei.uni-hannover.de ([130.75.117.1]) by intranet.aei.uni-hannover.de (IBM Domino Release 9.0.1FP5) with ESMTP id 2016092116390363-24791 ; Wed, 21 Sep 2016 16:39:03 +0200 Date: Wed, 21 Sep 2016 16:39:03 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-net@freebsd.org Subject: Re: igb/pf-related crashes Message-Id: <20160921163903.2182fe303f96710cf416b71f@aei.mpg.de> In-Reply-To: <2862_1474468306_57E299D2_2862_3247_1_20160921162214.dcc6dca77d4a42c73df6de5e@aei.mpg.de> References: <2862_1474468306_57E299D2_2862_3247_1_20160921162214.dcc6dca77d4a42c73df6de5e@aei.mpg.de> Organization: Max Planck Gesellschaft X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on intranet/aei-hannover(Release 9.0.1FP5|November 22, 2015) at 21/09/2016 16:39:03, Serialize by Router on intranet/aei-hannover(Release 9.0.1FP5|November 22, 2015) at 21/09/2016 16:39:03, Serialize complete at 21/09/2016 16:39:03 X-TNEFEvaluated: 1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 X-PMX-Version: 6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.9.21.143017 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, MIME_LOWER_CASE 0.05, BODY_SIZE_3000_3999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, IN_REP_TO 0, LEGITIMATE_NEGATE 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, NO_URI_HTTPS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NO_WWW 0, __URI_NS ' X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 14:39:07 -0000 On Wed, 21 Sep 2016 16:22:14 +0200 Gerrit K=FChn wrote about igb/pf-related crashes: [...] > #17 0xffffffff8091c99b at intr_event_execute_handlers+0xab Few more details: --- #0 doadump (textdump=3D) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=3D) at pcpu.h:219 #1 0xffffffff80950cc2 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:486 #2 0xffffffff809510a5 in vpanic (fmt=3D,=20 ap=3D) at /usr/src/sys/kern/kern_shutdown.c:889 #3 0xffffffff80950f33 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:818 #4 0xffffffff80d55f7b in trap_fatal (frame=3D,=20 eva=3D) at /usr/src/sys/amd64/amd64/trap.c:858 #5 0xffffffff80d5627d in trap_pfault (frame=3D0xfffffe01eead73f0,=20 usermode=3D) at /usr/src/sys/amd64/amd64/trap.c:681 #6 0xffffffff80d558fa in trap (frame=3D0xfffffe01eead73f0) at /usr/src/sys/amd64/amd64/trap.c:447 #7 0xffffffff80d3b8d2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff81c45fb9 in pf_normalize_ip (m0=3D, dir= =3D1,=20 kif=3D0xfffff800218c3000, reason=3D0xfffffe01eead76fe, pd=3D0xfffffe01e= ead7668) at /usr/src/sys/modules/pf/../../netpfil/pf/pf_norm.c:1349 #9 0xffffffff81c2c4c8 in pf_test (dir=3D1, ifp=3D,=20 m0=3D0xfffffe01eead77a8, inp=3D0x0) at /usr/src/sys/modules/pf/../../netpfil/pf/pf.c:5806 #10 0xffffffff81c3e07d in pf_check_in (arg=3D,=20 m=3D0xfffffe01eead77a8, ifp=3D0x0, dir=3D, inp=3D0= x1) at /usr/src/sys/modules/pf/../../netpfil/pf/pf_ioctl.c:3551 #11 0xffffffff80a24ef4 in pfil_run_hooks (ph=3D0xffffffff816a6e88,=20 mp=3D0xfffffe01eead78c0, ifp=3D0xfffff800054a1800, dir=3D1, inp=3D0x0) at /usr/src/sys/net/pfil.c:82 #12 0xffffffff81c148e3 in bridge_pfil (mp=3D0xfffffe01eead78c0,=20 bifp=3D0xfffff80021a08800, ifp=3D0xfffff800054a1800, dir=3D1) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:3165 #13 0xffffffff81c153a5 in bridge_forward (sc=3D0xfffff800217ee600,=20 sbif=3D0xfffff80021b52600, m=3D0xfffff8004fb67200) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2170 #14 0xffffffff81c13c55 in bridge_input (ifp=3D,=20 m=3D0xfffff8004fb67200) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2419 #15 0xffffffff80a1c05a in ether_nh_input (m=3D) at /usr/src/sys/net/if_ethersubr.c:607 #16 0xffffffff80a24092 in netisr_dispatch_src (proto=3D,=20 source=3D, m=3D0xfffffe01eead7668) at /usr/src/sys/net/netisr.c:976 #17 0xffffffff804f859c in igb_rxeof (count=3D99) at /usr/src/sys/dev/e1000/if_igb.c:4746 #18 0xffffffff804f8c41 in igb_msix_que (arg=3D0xfffff80005499608) at /usr/src/sys/dev/e1000/if_igb.c:1566 #19 0xffffffff8091c99b in intr_event_execute_handlers ( p=3D, ie=3D0xfffff80005478700) at /usr/src/sys/kern/kern_intr.c:1264 #20 0xffffffff8091cde6 in ithread_loop (arg=3D0xfffff80005484ea0) at /usr/src/sys/kern/kern_intr.c:1277 #21 0xffffffff8091a4ea in fork_exit ( callout=3D0xffffffff8091cd50 , arg=3D0xfffff80005484ea0,= =20 frame=3D0xfffffe01eead7c00) at /usr/src/sys/kern/kern_fork.c:1027 #22 0xffffffff80d3be0e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #23 0x0000000000000000 in ?? () --- From owner-freebsd-net@freebsd.org Wed Sep 21 18:24:16 2016 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 34F73BE25A2 for ; Wed, 21 Sep 2016 18:24:16 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C194BC14 for ; Wed, 21 Sep 2016 18:24:15 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id w84so208979997wmg.1 for ; Wed, 21 Sep 2016 11:24:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=lhjbAmODpyro5p+dZ9UZcrEzJD8JBy4kPzZ85ydrkNc=; b=r7IGw7FEWt/LdSCtQzm3viGbWpLUc70b/djIAlQl4+T7WWQ3621Ro5z+J4c3WjJbuX PWzQgKNO0O06pg7JZLNWIuHNYo0tKnGCWQKsS4fr5lSj1Rua6kieMVIWkpfHcmymYYJO w/wf/JSH/Teek58Iok3ix5sjzvjtBSEc9LI2ryPh64wpyfoeEmld9wEyxETblHw5Fkrd WyCNNbmjBXhVn9y5LQ+TgpAsbQFIyy5Zu6D12u3WinhjorAVE1t/6Ph+av1saJGqmtB7 soAXaPvC9NANCbajh79nedwmrZXqB0KEq1U2sASNW0/x9VDrhdV9Lkmq8GYUkoaAsC+Z w2kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=lhjbAmODpyro5p+dZ9UZcrEzJD8JBy4kPzZ85ydrkNc=; b=De+zJpqxjQ5xYE7EwdVYK2iSjtFilIMzhFo6S7eTNfL7L0sYATlX3Gy1zgwpxuNPuB tgt39qo3yBJZXlMr1pkWjkhBWVcaSZoVhk+KUSyaWP34UPIGVtt48luYG2UZsqcXHi/N bvUPl8msf2DDlEeJ0ZvIyG/5fDV0XnHpJ/a3eSGyTbDrPSck8N9IbNK7czCC5voGhgWf 2FsstrTiACBOvpGnx3xjdfBDRmqA2s8cvQa5wyDpxRpqqldj9fkhaf5fJZ6z6muPI2At a7FTg2FjX5YNe7+COrZo7H+A+7EvzDAloZvwn02teFG6m+erhnpD35g8Du4vOn8hWjqn VdjA== X-Gm-Message-State: AE9vXwMrfxC/Nfiij7vRpgICVfTvSw+NZL4BqIoVwlwSee1PNnMzjX/lsDnMBZ4gumHuu7m40S9S3N5msXpSbQ== X-Received: by 10.194.106.103 with SMTP id gt7mr26852842wjb.201.1474482254266; Wed, 21 Sep 2016 11:24:14 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.194.178.99 with HTTP; Wed, 21 Sep 2016 11:23:53 -0700 (PDT) In-Reply-To: <20160921162214.dcc6dca77d4a42c73df6de5e@aei.mpg.de> References: <20160921162214.dcc6dca77d4a42c73df6de5e@aei.mpg.de> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 21 Sep 2016 20:23:53 +0200 X-Google-Sender-Auth: DGCeRfOZ6owcF_iLU5R5Q5rUqqM Message-ID: Subject: Re: igb/pf-related crashes To: =?UTF-8?B?R2Vycml0IEvDvGhu?= Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 18:24:16 -0000 On Wed, Sep 21, 2016 at 4:22 PM, Gerrit K=C3=BChn wrote: > Hi all, > > Over the last weekend, I saw a couple of crashes on a 10.3-system acting > as filtering bridge with pf that all looked like this: > =E2=80=8BI've got this problem on low RAM VM (about 196MB of RAM) during lo= t's of fragmented packet storm. There is a bug into bridge_pfil with fragmented packet that cause an mbuf memory leak. You should try this patch (written for current but should be easly adapted to 10.3) that should fix this problem: https://reviews.freebsd.org/D7780 Regards, Olivier From owner-freebsd-net@freebsd.org Wed Sep 21 18:25:55 2016 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 E2FF6BE2752 for ; Wed, 21 Sep 2016 18:25:55 +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 mx1.freebsd.org (Postfix) with ESMTPS id D1F53D17 for ; Wed, 21 Sep 2016 18:25:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8LIPsib028527 for ; Wed, 21 Sep 2016 18:25:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable. Date: Wed, 21 Sep 2016 18:25:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: IntelNetworking 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 18:25:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211219 Eric Joyner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erj@freebsd.org --- Comment #5 from Eric Joyner --- (In reply to Jeff Pieper from comment #4) I think this is an issue only in MSI-X mode; I tried an 82754L in MSI mode = and unplugging/plugging in the cable behaved as expected. We should check the IVAR, IMS, and other interrupt-cause-related registers, since it appears the link interrupt isn't even being generated. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Sep 21 20:48:12 2016 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 CCDBFBE3CDC for ; Wed, 21 Sep 2016 20:48:12 +0000 (UTC) (envelope-from info@midsommar.online) Received: from smtp208.server19.mailrelay-i.com (smtp208.server19.mailrelay-i.com [93.159.208.19]) (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 67B53B8B for ; Wed, 21 Sep 2016 20:48:12 +0000 (UTC) (envelope-from info@midsommar.online) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=dkim; d=midsommar.online; h=Reply-To:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type; i=info@midsommar.online; bh=t08Dy6/3JZbCTuoXQrcOP6+ODUc=; b=AzyHU7yMhlhH+Fp19s+4O8GmjQ6FdWfUHNlyKZQ9tfM/VeIU3cSi9B0jMjooVudaIl49zLAU6pzi wRUP0fyGMbTSHsWAbtGxR6SP4WIVa3pSiVrSb2QOYce/LNFBjlC+TrFCIVY0Jnqt6heV1O7wllu4 FhqDe9l1vS6yToUZnj8= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=dkim; d=midsommar.online; b=nNFGATp5dDX8QSSRedoFPcXZ8jxUgBhMk9rCU05h5VyzDXFIzev74VDlnzzcJEaII94wssGwtC3z ixcaV7Chvvzh+h9kKRH0lp2gS9oPyTUNBcb1I4x1NPzJ3uiTJmjJZ+FZXf3aDCXksUV958pLfClY dceH+6hLByx8jJCAdXM=; Received: by smtp208.server19.mailrelay-i.com id hsbp0m16r3g6 for ; Wed, 21 Sep 2016 22:32:49 +0200 (envelope-from ) X-SmtpId: VTJGc2RHVmtYMTl6b202QU9Tc21SRTNJMXhRNXF4Y1ljZXpSRjFqT3VCTTNaR2hob1kvU3pYZFp3UUNTCm5nWUF1aEVxcUxqK0hmTU9rK0x2UXh4d3BRPT0K Organization: Midsommar Festival Reply-To: info@midsommar.online Message-ID: From: "YouTube" To: Subject: =?windows-1252?Q?Raffaella_sent_you_a_video:_"MIDSOMMAR_FESTIVAL_2016"?= Date: Wed, 21 Sep 2016 22:32:24 +0200 X-Priority: 1 X-Mailer: SMTP Component MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 20:48:12 -0000 Raffaella has shared a video with you on YouTube: = https://www.youtube.com/watch?v=3DVtV83ls5JpE From owner-freebsd-net@freebsd.org Thu Sep 22 00:02:50 2016 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 078E9BE28F2 for ; Thu, 22 Sep 2016 00:02:50 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CA0CC1B5; Thu, 22 Sep 2016 00:02:49 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u8LNv3cT015291 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 21 Sep 2016 16:57:04 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u8LNv3YQ015290; Wed, 21 Sep 2016 16:57:03 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 21 Sep 2016 16:57:03 -0700 From: Gleb Smirnoff To: Kubilay Kocak Cc: Karl Pielorz , freebsd-net@freebsd.org, Steven Hartland Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160921235703.GG1018@cell.glebi.us> References: <0D84203FAAFD0A8E7BBB24A3@[10.12.30.106]> <6E574F1B61786E6032824A88@[10.12.30.106]> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 00:02:50 -0000 On Sat, Sep 10, 2016 at 10:51:36PM +1000, Kubilay Kocak wrote: K> > wrote: K> > K> >> Yes known issue I'm afraid. K> >> K> >> I created a patch set to address this but there where objections so K> >> it was removed, see the attached which is based on 10.2-RELEASE. K> > K> > Hi, K> > K> > Thanks for the reply, and the comprehensive patch. If I get a chance K> > I'll see if I can run it up one of the affected boxes, if I can find K> > one I can mess around with. K> > K> > Good to know it wasn't just "me" :) K> > K> > Cheers, K> > K> > -Karl K> K> Also see the following review, which was re-opened (after original K> commit was reverted) after said issues were raised, though I can't see K> that glebius has commented on it since: K> K> https://reviews.freebsd.org/D4111 K> K> 11.0 having this would have been awesome. Maybe (hopefully) 11.1 IMHO, the original patch was absolutely evil hack touching multiple layers, for the sake of a very special problem. I think, that in order to kick forwarding table on switches, lagg should: - allocate an mbuf itself - set its source hardware address to its own - set destination hardware to broadcast - put some payload in there, to make packet of valid size. Why should it be gratuitous ARP? A machine can be running IPv6 only, or may even use whatever higher level protocol, e.g. PPPoE. We shouldn't involve IP into this Layer 2 problem at all. - Finally, send the prepared mbuf down the lagg member(s). And please don't hack half of the network stack to achieve that :) -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Sep 22 01:12:12 2016 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 78195BE4E8A for ; Thu, 22 Sep 2016 01:12:12 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::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 40233173; Thu, 22 Sep 2016 01:12:12 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id n143so67665356ita.1; Wed, 21 Sep 2016 18:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=e5yhPwI+Hdol2nfZnNCllB8DrnX/BHURDWyvZlgctXE=; b=Nx0ZyuN+kTwk5j8ilKszMIaWDaoNCji2mbwLa44rUzxl1WnzoOpKTUozhJPDh9G0jp DbvMX1XYTSV053AhzMP+RUbU78GYGT+mSLqcEyRT9KY4jwmd2Tq7fYrC0UlkxmHdsyDv bZ9rMwBINOKn3hmo0PqWurmJ4FHsP5p+Z/7Wpdbm/CvmfS2uQt0DzkqXRFvFvTanhH8m dt48aQK18qHJEFmYFqk97X/8CrpBL5OvfUZWGC3qikIdC0lJU0ynV/lkmNY2wYed3SGn c4fJhiZjTOjoeMQmApjuHof5Zxr/Ps72TWI8xXzRtBsZF6zLyeqnYoThdZDlkkyJPnA9 KEIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=e5yhPwI+Hdol2nfZnNCllB8DrnX/BHURDWyvZlgctXE=; b=T3aL3wODqYVutovp3wHLeflcNr+3nGq76nauHbEaX10jh9+S+5vm9ZExAPgTN3Fbt+ WusH+b5ubAYa0jsoSK4t2z1R/VavADoF/wiQ5IvJKzx9sNKOpF2iT+DdSPZ6nwP4nlXi waejBsPBmj3t7mEqVb8nPyUo6ysbsipT3+DJtXeO2G5GrytFxknDgWFB0Kp96AMEBdmE GX80BqGQCT9uU9okweb0pc3MEIMlNyk1Tk0Js+DEwQVTOyw1F5Z4WI9gdHIciIwT+irl v/5WOu0EeH+qnwk+F5Te178lRPkeCeRrpaMXg2fFIMGOh4QqtFa36CdGj6H/0k1JsKon cDiQ== X-Gm-Message-State: AE9vXwOZZgwmk174k6esnJRHXymFusg5yOfKZPIe9xSp/D+fOywNUpLlLmtsRUiTGPamsu5FctoNLsX1PeP6wQ== X-Received: by 10.36.254.140 with SMTP id w134mr7366145ith.108.1474506731631; Wed, 21 Sep 2016 18:12:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.129.78 with HTTP; Wed, 21 Sep 2016 18:12:11 -0700 (PDT) In-Reply-To: <20160921235703.GG1018@cell.glebi.us> References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> From: Ryan Stone Date: Wed, 21 Sep 2016 21:12:11 -0400 Message-ID: Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff Cc: Kubilay Kocak , freebsd-net , Karl Pielorz , Steven Hartland Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 01:12:12 -0000 On Wed, Sep 21, 2016 at 7:57 PM, Gleb Smirnoff wrote: > IMHO, the original patch was absolutely evil hack touching multiple > layers, for the sake of a very special problem. > > I think, that in order to kick forwarding table on switches, lagg > should: > > - allocate an mbuf itself > - set its source hardware address to its own > - set destination hardware to broadcast > - put some payload in there, to make packet of valid size. Why should it be > gratuitous ARP? A machine can be running IPv6 only, or may even use > whatever > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this > Layer 2 > problem at all. > - Finally, send the prepared mbuf down the lagg member(s). > > And please don't hack half of the network stack to achieve that :) > The original report in this thread is about a system where it takes almost 15 minutes for the network to start working again after a failover. That does not sound to me like a switch problem. That sounds to me like the ARP cache on the remote system. To fix such a case we have to touch L3. From owner-freebsd-net@freebsd.org Thu Sep 22 01:33:47 2016 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 AB5B5BE47D7 for ; Thu, 22 Sep 2016 01:33:47 +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 mx1.freebsd.org (Postfix) with ESMTPS id 9A9E3E65 for ; Thu, 22 Sep 2016 01:33:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8M1XluD019675 for ; Thu, 22 Sep 2016 01:33:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212872] Fatal trap 12: page fault while... |supervisor read data, page not present | ipf_frag_lookup | bcmp Date: Thu, 22 Sep 2016 01:33:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: 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 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 01:33:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212872 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org CC|freebsd-amd64@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Sep 22 02:58:59 2016 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 23D8BBE4D78 for ; Thu, 22 Sep 2016 02:58:59 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 08DB8FEE; Thu, 22 Sep 2016 02:58:58 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u8M2wv2v016144 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 21 Sep 2016 19:58:57 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u8M2wuTK016143; Wed, 21 Sep 2016 19:58:56 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 21 Sep 2016 19:58:56 -0700 From: Gleb Smirnoff To: Ryan Stone Cc: Kubilay Kocak , freebsd-net , Karl Pielorz , Steven Hartland Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160922025856.GH1018@cell.glebi.us> References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 02:58:59 -0000 On Wed, Sep 21, 2016 at 09:12:11PM -0400, Ryan Stone wrote: R> > IMHO, the original patch was absolutely evil hack touching multiple R> > layers, for the sake of a very special problem. R> > R> > I think, that in order to kick forwarding table on switches, lagg R> > should: R> > R> > - allocate an mbuf itself R> > - set its source hardware address to its own R> > - set destination hardware to broadcast R> > - put some payload in there, to make packet of valid size. Why should it be R> > gratuitous ARP? A machine can be running IPv6 only, or may even use R> > whatever R> > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this R> > Layer 2 R> > problem at all. R> > - Finally, send the prepared mbuf down the lagg member(s). R> > R> > And please don't hack half of the network stack to achieve that :) R> R> The original report in this thread is about a system where it takes almost R> 15 minutes for the network to start working again after a failover. That R> does not sound to me like a switch problem. That sounds to me like the ARP R> cache on the remote system. To fix such a case we have to touch L3. Does lagg(4) hardware address change when it failovers? -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Sep 22 05:31:52 2016 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 D16DABE5147 for ; Thu, 22 Sep 2016 05:31: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 mx1.freebsd.org (Postfix) with ESMTPS id B6CA8B31 for ; Thu, 22 Sep 2016 05:31:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8M5Vqmd052786 for ; Thu, 22 Sep 2016 05:31:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212872] Fatal trap 12: page fault while... |supervisor read data, page not present | ipf_frag_lookup | bcmp Date: Thu, 22 Sep 2016 05:31: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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gerrit.kuehn@aei.mpg.de 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 05:31:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212872 gerrit.kuehn@aei.mpg.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gerrit.kuehn@aei.mpg.de --- Comment #1 from gerrit.kuehn@aei.mpg.de --- I've seen some very similar (I think, see below) crashes lately on a transparent filtering (with pf) bridge system that ran fine for months befo= re that. I cannot say anything about the traffic or load it had, but I doubt it was much. The crash did not appear again (yet) after upgrading to 10.3-p7: --- Mon Sep 19 02:55:28 CEST 2016 FreeBSD ahfwx.aei.uni-hannover.de 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297= 264: Fri Mar 25 02:10:02 UTC 2016=20=20=20=20 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid =3D 5; apic id =3D 0a fault virtual address =3D 0xe fault code =3D supervisor write data, page not present instruction pointer =3D 0x20:0xffffffff81c45fb9 stack pointer =3D 0x28:0xfffffe01eead74a0 frame pointer =3D 0x28:0xfffffe01eead75d0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (irq280: igb2:que 5) trap number =3D 12 panic: page fault cpuid =3D 5 KDB: stack backtrace: #0 0xffffffff8098e390 at kdb_backtrace+0x60 #1 0xffffffff80951066 at vpanic+0x126 #2 0xffffffff80950f33 at panic+0x43 #3 0xffffffff80d55f7b at trap_fatal+0x36b #4 0xffffffff80d5627d at trap_pfault+0x2ed #5 0xffffffff80d558fa at trap+0x47a #6 0xffffffff80d3b8d2 at calltrap+0x8 #7 0xffffffff81c2c4c8 at pf_test+0x1c8 #8 0xffffffff81c3e07d at pf_check_in+0x1d #9 0xffffffff80a24ef4 at pfil_run_hooks+0x84 #10 0xffffffff81c148e3 at bridge_pfil+0x363 #11 0xffffffff81c153a5 at bridge_forward+0x1c5 #12 0xffffffff81c13c55 at bridge_input+0x555 #13 0xffffffff80a1c05a at ether_nh_input+0x2ba #14 0xffffffff80a24092 at netisr_dispatch_src+0x62 #15 0xffffffff804f859c at igb_rxeof+0x60c #16 0xffffffff804f8c41 at igb_msix_que+0x121 #17 0xffffffff8091c99b at intr_event_execute_handlers+0xab Uptime: 51m41s Dumping 518 out of 8140 MB:..4%..13%..22%..31%..41%..53%..62%..72%..81%..93% Reading symbols from /boot/kernel/geom_mirror.ko.symbols...done. Loaded symbols for /boot/kernel/geom_mirror.ko.symbols Reading symbols from /boot/kernel/aesni.ko.symbols...done. Loaded symbols for /boot/kernel/aesni.ko.symbols Reading symbols from /boot/kernel/crypto.ko.symbols...done. Loaded symbols for /boot/kernel/crypto.ko.symbols Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. Loaded symbols for /boot/kernel/if_bridge.ko.symbols Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. Loaded symbols for /boot/kernel/bridgestp.ko.symbols Reading symbols from /boot/kernel/ums.ko.symbols...done. Loaded symbols for /boot/kernel/ums.ko.symbols Reading symbols from /boot/kernel/pflog.ko.symbols...done. Loaded symbols for /boot/kernel/pflog.ko.symbols Reading symbols from /boot/kernel/pf.ko.symbols...done. Loaded symbols for /boot/kernel/pf.ko.symbols #0 doadump (textdump=3D) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=3D) at pcpu.h:219 #1 0xffffffff80950cc2 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:486 #2 0xffffffff809510a5 in vpanic (fmt=3D,=20 ap=3D) at /usr/src/sys/kern/kern_shutdown.c:889 #3 0xffffffff80950f33 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:818 #4 0xffffffff80d55f7b in trap_fatal (frame=3D,=20 eva=3D) at /usr/src/sys/amd64/amd64/trap.c:858 #5 0xffffffff80d5627d in trap_pfault (frame=3D0xfffffe01eead73f0,=20 usermode=3D) at /usr/src/sys/amd64/amd64/trap.c:681 #6 0xffffffff80d558fa in trap (frame=3D0xfffffe01eead73f0) at /usr/src/sys/amd64/amd64/trap.c:447 #7 0xffffffff80d3b8d2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff81c45fb9 in pf_normalize_ip (m0=3D, dir= =3D1,=20 kif=3D0xfffff800218c3000, reason=3D0xfffffe01eead76fe, pd=3D0xfffffe01e= ead7668) at /usr/src/sys/modules/pf/../../netpfil/pf/pf_norm.c:1349 #9 0xffffffff81c2c4c8 in pf_test (dir=3D1, ifp=3D,=20 m0=3D0xfffffe01eead77a8, inp=3D0x0) at /usr/src/sys/modules/pf/../../netpfil/pf/pf.c:5806 #10 0xffffffff81c3e07d in pf_check_in (arg=3D,=20 m=3D0xfffffe01eead77a8, ifp=3D0x0, dir=3D, inp=3D0= x1) at /usr/src/sys/modules/pf/../../netpfil/pf/pf_ioctl.c:3551 #11 0xffffffff80a24ef4 in pfil_run_hooks (ph=3D0xffffffff816a6e88,=20 mp=3D0xfffffe01eead78c0, ifp=3D0xfffff800054a1800, dir=3D1, inp=3D0x0) at /usr/src/sys/net/pfil.c:82 #12 0xffffffff81c148e3 in bridge_pfil (mp=3D0xfffffe01eead78c0,=20 bifp=3D0xfffff80021a08800, ifp=3D0xfffff800054a1800, dir=3D1) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:3165 #13 0xffffffff81c153a5 in bridge_forward (sc=3D0xfffff800217ee600,=20 sbif=3D0xfffff80021b52600, m=3D0xfffff8004fb67200) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2170 #14 0xffffffff81c13c55 in bridge_input (ifp=3D,=20 m=3D0xfffff8004fb67200) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2419 #15 0xffffffff80a1c05a in ether_nh_input (m=3D) at /usr/src/sys/net/if_ethersubr.c:607 #16 0xffffffff80a24092 in netisr_dispatch_src (proto=3D,=20 source=3D, m=3D0xfffffe01eead7668) at /usr/src/sys/net/netisr.c:976 #17 0xffffffff804f859c in igb_rxeof (count=3D99) at /usr/src/sys/dev/e1000/if_igb.c:4746 #18 0xffffffff804f8c41 in igb_msix_que (arg=3D0xfffff80005499608) at /usr/src/sys/dev/e1000/if_igb.c:1566 #19 0xffffffff8091c99b in intr_event_execute_handlers ( p=3D, ie=3D0xfffff80005478700) at /usr/src/sys/kern/kern_intr.c:1264 #20 0xffffffff8091cde6 in ithread_loop (arg=3D0xfffff80005484ea0) at /usr/src/sys/kern/kern_intr.c:1277 #21 0xffffffff8091a4ea in fork_exit ( callout=3D0xffffffff8091cd50 , arg=3D0xfffff80005484ea0,= =20 frame=3D0xfffffe01eead7c00) at /usr/src/sys/kern/kern_fork.c:1027 #22 0xffffffff80d3be0e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #23 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb)=20 --- --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Sep 22 07:21:04 2016 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 8A336BE5D2C for ; Thu, 22 Sep 2016 07:21:04 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 2D63E9B2 for ; Thu, 22 Sep 2016 07:21:04 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22a.google.com with SMTP id l132so309942516wmf.0 for ; Thu, 22 Sep 2016 00:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=mPPdZqQDVkP7tkSZz9MiP+ij2xPpygHlQ1lty/36pOk=; b=RgZjViAmslEayZxV+l0DBBX5/kWXh/AVEltBNFW7Q1ISNk4xK67El0vbxzjYP80lzS uf7CSVF3TD6tplcy91TPWSHlOMf7CenK9c/2E1KXFKR6U5VKzanViQTy/uZ4X0cj8iKk S9Id7KuLmNTm/eMhWXzrN9Ynr5Q3m7lpaST5BNKjlvcfUEyqf+b8tyQH9sda+XR3WnMk tor/c4zfPbLLD0NOqJ1gixuMbzI9smlH3xpFlcQs8loYUepMHFFD2gBpn+wE9VuKuBLD F6LcytYyX/gGZKpx0RhRCGa+uIbkp3E/VLUGIfK1RLLQ7tZyzENLVlDqVos8CdLLef+3 0IrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=mPPdZqQDVkP7tkSZz9MiP+ij2xPpygHlQ1lty/36pOk=; b=NqnLuRR/ohCvJ/IM/RTLXeJvd+qQ2jzfPA5NDN6SZy9JGAII00Qbe+5cAIGM8bTvOs BtNwUCZaNC6fZurwRrL2byVG44MsSMhaIR6pgp3lVJ1zmNLDrUh4Fq4mTyiGKMvzqZ+A L6i6LVsYcRfRlWDw1kaXM9p5QKxQE5ujNGjzQB6GaZ1TweU2WPs2gkvw1n35Yt5/DNTw NCPVcQqWd9mWSHpTbtTxw0gP71aZtJZIMMZ5KXyI0+etY2Q0n6NOwXMkD+rQA1nZHoBq Bv5M44LWypSFXfGLeFoQqd8YLyvxhyJNScxKuXkwST2yG5tHYNpM1CBtIO76UwO9wMZB g/GQ== X-Gm-Message-State: AE9vXwNqsHfe40GdCZ6XwnHHwfNSHZE+8FY0jPMXviCXruxWGZjishmHIB0z+ZEaOd//CNeH X-Received: by 10.28.92.82 with SMTP id q79mr907024wmb.113.1474528862401; Thu, 22 Sep 2016 00:21:02 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id f15sm998465wmf.8.2016.09.22.00.21.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 00:21:01 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff , Ryan Stone References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> Cc: Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> Date: Thu, 22 Sep 2016 08:21:08 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160922025856.GH1018@cell.glebi.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 07:21:04 -0000 On 22/09/2016 03:58, Gleb Smirnoff wrote: > On Wed, Sep 21, 2016 at 09:12:11PM -0400, Ryan Stone wrote: > R> > IMHO, the original patch was absolutely evil hack touching multiple > R> > layers, for the sake of a very special problem. > R> > > R> > I think, that in order to kick forwarding table on switches, lagg > R> > should: > R> > > R> > - allocate an mbuf itself > R> > - set its source hardware address to its own > R> > - set destination hardware to broadcast > R> > - put some payload in there, to make packet of valid size. Why should it be > R> > gratuitous ARP? A machine can be running IPv6 only, or may even use > R> > whatever > R> > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this > R> > Layer 2 > R> > problem at all. > R> > - Finally, send the prepared mbuf down the lagg member(s). > R> > > R> > And please don't hack half of the network stack to achieve that :) > R> > R> The original report in this thread is about a system where it takes almost > R> 15 minutes for the network to start working again after a failover. That > R> does not sound to me like a switch problem. That sounds to me like the ARP > R> cache on the remote system. To fix such a case we have to touch L3. > > Does lagg(4) hardware address change when it failovers? > It moves the address between interfaces which typically moves it between switches too. From owner-freebsd-net@freebsd.org Thu Sep 22 07:23:13 2016 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 22A51BE5FA3 for ; Thu, 22 Sep 2016 07:23:13 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B88F6C90 for ; Thu, 22 Sep 2016 07:23:12 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22f.google.com with SMTP id w84so235241094wmg.1 for ; Thu, 22 Sep 2016 00:23:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=ucWXJPZdC697OxqiYxvpYREKzQV1poGxz0B/RxgopCQ=; b=DoxBGadCcf00G8SiXgyzshqSzv7gKeQj3b+fgYQTRHdPx82W8gq/WAnqWntbNSUbcq IbWJFyX66toYtXM/mmnl/Jatl7vbH7vgzM0uWzsnMWaC/irVpFayhsiFmjp6hb0k27s2 j/QFznIDuM6R8Dr97utfXcLLSMbPPD/FAHjJHvI+1GezeXTmQevXOmNre9KoMwevdKo+ w9OdFnYU69ikTTruNNZoPMMZxIOzH5r/lwop5AnjyTSfpPPLLHFdm2CFISC778EtUmEh ZwDxR96s7DaWg5p6v4MqOcrpAsU4zbCS/HgAa8LjcTJtFFFM595rx7R1HSI4cUlRpq1n MHfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=ucWXJPZdC697OxqiYxvpYREKzQV1poGxz0B/RxgopCQ=; b=Rzmhg3BEAu4G+t6DKabIzWz0Y5zVlyql4IV02X6xx30LS/51cYGiVaF/Z9YL8P8rY+ JnTkY2x0erV/HNeL8h/pJXF8Os+hOaeBej7aL90+2LJUlf9qC7oRxBBFaGclu7xx2u6S Rt7yM9RheroK6mJZRLG1bDR2ZZagUFpI11jd/9g5OsU95trs8YpryY+MAAbgFFznRvle AshYCYgIKdGnVJk5ivhmYnP6AmHfsE3jTxz0KzmPX8M46KGC80RElbDypBzNY1PrBnwJ lT/TkKykPv/PwYwCPVHEXtzPMC9DcM4xWq3jSyDy1Im5shp7a8dcYJxIi/OBOOhq6hW5 wQGQ== X-Gm-Message-State: AA6/9Rl8i0qo9RG75yAcfo8kthoFP5sqJXubM5eXJR20Wctwmc8yLJbcElrxt+tM7y729AV3 X-Received: by 10.194.141.203 with SMTP id rq11mr567151wjb.112.1474528990983; Thu, 22 Sep 2016 00:23:10 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id w203sm36055406wmw.7.2016.09.22.00.23.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 00:23:10 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Ryan Stone , Gleb Smirnoff References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> Cc: Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: <796ab1c4-3a05-1e59-f8ba-355e75080935@multiplay.co.uk> Date: Thu, 22 Sep 2016 08:23:17 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 07:23:13 -0000 On 22/09/2016 02:12, Ryan Stone wrote: > > > On Wed, Sep 21, 2016 at 7:57 PM, Gleb Smirnoff > wrote: > > IMHO, the original patch was absolutely evil hack touching multiple > layers, for the sake of a very special problem. > > I think, that in order to kick forwarding table on switches, lagg > should: > > - allocate an mbuf itself > - set its source hardware address to its own > - set destination hardware to broadcast > - put some payload in there, to make packet of valid size. Why > should it be > gratuitous ARP? A machine can be running IPv6 only, or may even > use whatever > higher level protocol, e.g. PPPoE. We shouldn't involve IP into > this Layer 2 > problem at all. > - Finally, send the prepared mbuf down the lagg member(s). > > And please don't hack half of the network stack to achieve that :) > > > The original report in this thread is about a system where it takes > almost 15 minutes for the network to start working again after a > failover. That does not sound to me like a switch problem. That > sounds to me like the ARP cache on the remote system. To fix such a > case we have to touch L3. 15mins is a long time however we don't do ARP correctly in this case, which is almost certainly the cause. From owner-freebsd-net@freebsd.org Thu Sep 22 07:51:55 2016 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 E381BBE5872 for ; Thu, 22 Sep 2016 07:51:55 +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 mx1.freebsd.org (Postfix) with ESMTPS id C9FEB1BD for ; Thu, 22 Sep 2016 07:51:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8M7pt1F071298 for ; Thu, 22 Sep 2016 07:51:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212872] Fatal trap 12: page fault while... |supervisor read data, page not present | ipf_frag_lookup | bcmp Date: Thu, 22 Sep 2016 07:51:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gerrit.kuehn@aei.mpg.de 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 07:51:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212872 --- Comment #2 from gerrit.kuehn@aei.mpg.de --- Interestingly, we also appear to run on similar hardware. Here I have --- Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Atom(TM) CPU C2750 @ 2.40GHz (2400.06-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x406d8 Family=3D0x6 Model=3D0x4d Steppi= ng=3D8 =20 Features=3D0xbfebfbff =20 Features2=3D0x43d8e3bf AMD Features=3D0x28100800 AMD Features2=3D0x101 Structured Extended Features=3D0x2282 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory =3D 8589934592 (8192 MB) avail memory =3D 8207847424 (7827 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 8 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 cpu4 (AP): APIC ID: 8 cpu5 (AP): APIC ID: 10 cpu6 (AP): APIC ID: 12 cpu7 (AP): APIC ID: 14 random: initialized ioapic0 irqs 0-23 on motherboard module_register_init: MOD_LOAD (vesa, 0xffffffff80dc6500, 0) error 19 kbd1 at kbdmux0 cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 [...] igb0: port 0xe0c0-0xe0df mem 0xdf260000-0xdf27ffff,0xdf2ec000-0xdf2effff irq 20 at dev= ice 20.0 on pci0 igb0: Using MSIX interrupts with 9 vectors igb0: Ethernet address: 0c:c4:7a:68:c8:60 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 igb0: Bound queue 4 to cpu 4 igb0: Bound queue 5 to cpu 5 igb0: Bound queue 6 to cpu 6 igb0: Bound queue 7 to cpu 7 igb1: port 0xe0a0-0xe0bf mem 0xdf240000-0xdf25ffff,0xdf2e8000-0xdf2ebfff irq 21 at dev= ice 20.1 on pci0 igb1: Using MSIX interrupts with 9 vectors igb1: Ethernet address: 0c:c4:7a:68:c8:61 igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb1: Bound queue 2 to cpu 2 igb1: Bound queue 3 to cpu 3 igb1: Bound queue 4 to cpu 4 igb1: Bound queue 5 to cpu 5 igb1: Bound queue 6 to cpu 6 igb1: Bound queue 7 to cpu 7 igb2: port 0xe080-0xe09f mem 0xdf220000-0xdf23ffff,0xdf2e4000-0xdf2e7fff irq 22 at dev= ice 20.2 on pci0 igb2: Using MSIX interrupts with 9 vectors igb2: Ethernet address: 0c:c4:7a:68:c8:62 igb2: Bound queue 0 to cpu 0 igb2: Bound queue 1 to cpu 1 igb2: Bound queue 2 to cpu 2 igb2: Bound queue 3 to cpu 3 igb2: Bound queue 4 to cpu 4 igb2: Bound queue 5 to cpu 5 igb2: Bound queue 6 to cpu 6 igb2: Bound queue 7 to cpu 7 igb3: port 0xe060-0xe07f mem 0xdf200000-0xdf21ffff,0xdf2e0000-0xdf2e3fff irq 23 at dev= ice 20.3 on pci0 igb3: Using MSIX interrupts with 9 vectors igb3: Ethernet address: 0c:c4:7a:68:c8:63 igb3: Bound queue 0 to cpu 0 igb3: Bound queue 1 to cpu 1 igb3: Bound queue 2 to cpu 2 igb3: Bound queue 3 to cpu 3 igb3: Bound queue 4 to cpu 4 igb3: Bound queue 5 to cpu 5 igb3: Bound queue 6 to cpu 6 igb3: Bound queue 7 to cpu 7 --- The other system is a C2758. Any chance this is somehow chipset-related (es= p. igb)? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Sep 22 08:04:27 2016 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 950F4BE4915 for ; Thu, 22 Sep 2016 08:04:27 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 6169BF92 for ; Thu, 22 Sep 2016 08:04:27 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-pf0-x229.google.com with SMTP id 21so28194801pfy.0 for ; Thu, 22 Sep 2016 01:04:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=pPG09Mq6UA+qxrK9tCGuWAulI3l5hc4+LI1BxEptKL0=; b=oKC3IrnTfaX/B8VAw8r9+P401CRwNzO5wy3uujOeAMlJ/Q7AvL7/58zMOE70E/w4s1 x3PQ3wODLRW65EQkGxOQ/MEV2llNR6vk8775aXYiiTcphPmtslebmfs3sxR09rYY3y/8 rz14vuGi7Gkv2cxxd6iGt/dKtDVgYlA0H4mAHHNuWnwT9R+LGg0uGSAA4QfnI4e26GPL Ut5RkztttmOSqm11bybohtCmVtM7KLSP7AzSEsr6BV7fMK+Y+jVe59sLknfg94Nz2Wk9 3ItF1xMB7s2+Ms8+ybgWyXJBUF47lbEw3cnHxY7SWRfHZICHqF4K1UOZGCrwYpAXDoY4 UqpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=pPG09Mq6UA+qxrK9tCGuWAulI3l5hc4+LI1BxEptKL0=; b=T0frFjEyZQNJsl1uqO9hVAEx6ajpaukvRRXNR8LLg18IyCy885qRMYiB2KGAQqnUcw 3Rnsfr1ph8KkyWvYCcTfU3N73lPT6+0LcU2y4QPqwfzTIOV40zIvksYdH8uUk7hFQ/QU 1aXP72KLiz4lmFENN2cU9ToalI7TwGnQq85/qMz++swqDDO7LKre69Np8kAAe0/87aLn zws1nukDd5F36p9yDqp1e4N9NBt5IppfVda3BrrYP2w07S+09IdMvWDIq+PH+hT3Yz9q 3WZB143buUgK22xI3k46nCKhjCCZON1o0RQiRs18cCgUYdNEdA/cWgX6BsEjRpDU0lcO +EAg== X-Gm-Message-State: AE9vXwO24asFM5rNOoZvsyPdRCoy2M3Ea1KK6eriwgTEclIHhdER1sT98iLt392vrWz7ITlH X-Received: by 10.98.149.149 with SMTP id c21mr1108125pfk.33.1474531466853; Thu, 22 Sep 2016 01:04:26 -0700 (PDT) Received: from [10.10.1.58] ([185.97.61.1]) by smtp.gmail.com with ESMTPSA id 70sm1674575pfy.81.2016.09.22.01.04.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 01:04:25 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff , Kubilay Kocak References: <0D84203FAAFD0A8E7BBB24A3@[10.12.30.106]> <6E574F1B61786E6032824A88@[10.12.30.106]> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> Cc: Karl Pielorz , freebsd-net@freebsd.org From: Steven Hartland Message-ID: <48632d42-ea2b-b147-737d-d7decfdbcff4@multiplay.co.uk> Date: Thu, 22 Sep 2016 09:04:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160921235703.GG1018@cell.glebi.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 08:04:27 -0000 On 22/09/2016 00:57, Gleb Smirnoff wrote: > On Sat, Sep 10, 2016 at 10:51:36PM +1000, Kubilay Kocak wrote: > K> > wrote: > K> > > K> >> Yes known issue I'm afraid. > K> >> > K> >> I created a patch set to address this but there where objections so > K> >> it was removed, see the attached which is based on 10.2-RELEASE. > K> > > K> > Hi, > K> > > K> > Thanks for the reply, and the comprehensive patch. If I get a chance > K> > I'll see if I can run it up one of the affected boxes, if I can find > K> > one I can mess around with. > K> > > K> > Good to know it wasn't just "me" :) > K> > > K> > Cheers, > K> > > K> > -Karl > K> > K> Also see the following review, which was re-opened (after original > K> commit was reverted) after said issues were raised, though I can't see > K> that glebius has commented on it since: > K> > K> https://reviews.freebsd.org/D4111 > K> > K> 11.0 having this would have been awesome. Maybe (hopefully) 11.1 > > IMHO, the original patch was absolutely evil hack touching multiple > layers, for the sake of a very special problem. > > I think, that in order to kick forwarding table on switches, lagg > should: > > - allocate an mbuf itself > - set its source hardware address to its own > - set destination hardware to broadcast > - put some payload in there, to make packet of valid size. Why should it be > gratuitous ARP? A machine can be running IPv6 only, or may even use whatever > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this Layer 2 > problem at all. > - Finally, send the prepared mbuf down the lagg member(s). > > And please don't hack half of the network stack to achieve that :) > Yes it does touch multiple layers, but I'm not sure I'd agree that was all that evil, we already have similar parts in the code base e.g. lle_event and carp link state. When I dug around this issue last time the various papers made it quite clear what was expected / required to make lagg work properly, which is what was achieved by the code. With regards to running IPv6 that doesn't deal with it either hence the nd6 changes included, which was the only grey area caused by a conflict between the letter of the IPv6 spec and achieving the requirement of fast recovery. As a point of reference we've been running with the changes for nearly a year now and have never had issue, so the code is there if people want it. The disappointing thing about this is we had a solution, all be it one not everyone liked, nearly a year ago now and yet here we are still stuck with a broken lagg implementation in the tree. A perfect solution is always nice but in lieu of that the pragmatist in me asks isn't working better than not working at the end of the day? Regards Steve From owner-freebsd-net@freebsd.org Thu Sep 22 13:00:12 2016 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 5EC99BE59C0 for ; Thu, 22 Sep 2016 13:00:12 +0000 (UTC) (envelope-from j.gumede@acaeglobal.com) Received: from ntsika.forumis.net (ntsika.forumis.net [41.169.88.107]) (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 258F92E5 for ; Thu, 22 Sep 2016 13:00:11 +0000 (UTC) (envelope-from j.gumede@acaeglobal.com) Received: from ntsika.forumis.net (localhost [127.0.0.1]) by ntsika.forumis.net (Postfix) with ESMTP id EDDD3C507679 for ; Thu, 22 Sep 2016 15:00:06 +0200 (SAST) X-Virus-Scanned: amavisd-new at ntsika.forumis.net X-Spam-Flag: NO X-Spam-Score: 3.526 X-Spam-Level: *** X-Spam-Status: No, score=3.526 tagged_above=2 required=6.2 tests=[ALL_TRUSTED=-1, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, RAZOR2_CF_RANGE_51_100=0.365, RAZOR2_CF_RANGE_E8_51_100=2.43, RAZOR2_CHECK=1.729] autolearn=no autolearn_force=no Received: from ntsika.forumis.net ([127.0.0.1]) by ntsika.forumis.net (ntsika.forumis.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RJAmmzxe9jcM for ; Thu, 22 Sep 2016 14:59:59 +0200 (SAST) Received: from mbokodo.forumis.net (unknown [41.169.88.103]) by ntsika.forumis.net (Postfix) with ESMTPSA id 43AECC6DDC95 for ; Thu, 22 Sep 2016 14:38:41 +0200 (SAST) MIME-Version: 1.0 From: "Jabulisile Gumede" Reply-To: lombwa@acaeglobal.com To: freebsd-net@freebsd.org Subject: 2016/2017 Diplomatic Protocol & Etiquette Conference Invitation X-Mailer: Smart_Send_3_1_6 Date: Thu, 22 Sep 2016 14:38:42 +0200 Message-ID: <9688379226808193144069@ForumIS22> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 13:00:12 -0000 Thank you for accepting this workshop invitation. You may please unsubscribe here if you no longer wish to receive our emails From owner-freebsd-net@freebsd.org Thu Sep 22 14:58:33 2016 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 210E7BE508C for ; Thu, 22 Sep 2016 14:58:33 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 E1E1CB14; Thu, 22 Sep 2016 14:58:32 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-io0-x231.google.com with SMTP id r145so88396374ior.0; Thu, 22 Sep 2016 07:58:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DB4tcFDGOrH2GrjmZ0zo6vUsLq94zuxHg0Nz965DKGE=; b=JnRIHsuicd4P5vd+3xBMq7gfFRqM3GfyvL9PHa7Kk8R/+Hqb8uPEcemVpIoHMC3DyZ LFbi6vVDu2Q481h7W+g+p2RR/7U6/2ERjEHzCyLXq8gzs8YK+EKLsqktaLxdwtUJyTU8 rN0T2IsE0Nb/fnPup8Is6WEsWoFgl0ckQelz20KcjLL0A9hnXpMLcxPjqTlVuElMgxqc xoSUzKyRmp0AmEVMrMCa/dW+WcqWWWP8KpIHnzvfamj3JkhbrLvmqbaAmRRFx2Cf8xyp VhnFfuOLdUi4QdSi0v2jHZSAyPEWsu+zaR9h5U5k44ZAQaWj2rEYzF1vpeDQj9OO9NXE 9seA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DB4tcFDGOrH2GrjmZ0zo6vUsLq94zuxHg0Nz965DKGE=; b=j50ImrM1I+ZsML7s9RlQunBaZTX5NPYAtVy8ps8cVFNwWaLTuV++Tc4WJEt5ZjdpFs lxxpI2Zrcmyb/9Pgb93nOYkZ74nPU0z14H6wVdyzeP40w1p81eIy4ZpMmmBZhR6ol2VU NOBQXTukYfCRz/gCMBF9xGi83sk3/iVotnKQHToIGPBbE4p//4ydxKQoHmsWA3gXvZin yi92u6Qz6DfNl/lk9OTrDBTalzdPkbJ8wdiXY45b5UXm0Bv1Vn/jpPJBkNT6csf0fL6C oY2DZoXPcLPsysHXwfqTE2NxZSF1HPEmRK4hpEvm2KyeEI9G2zhgd8UeY8x3HHwFovjh C5LA== X-Gm-Message-State: AA6/9RlwoR6BpixQs6CvBkCAFybUz+9l7gKERzX44D85ulqOTAjEBtS7tldzPZBs/fUTO7NTR+LZRd549cqiQQ== X-Received: by 10.107.188.133 with SMTP id m127mr3287728iof.200.1474556312254; Thu, 22 Sep 2016 07:58:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.129.78 with HTTP; Thu, 22 Sep 2016 07:58:31 -0700 (PDT) In-Reply-To: <48632d42-ea2b-b147-737d-d7decfdbcff4@multiplay.co.uk> References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <48632d42-ea2b-b147-737d-d7decfdbcff4@multiplay.co.uk> From: Ryan Stone Date: Thu, 22 Sep 2016 10:58:31 -0400 Message-ID: Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Steven Hartland Cc: Gleb Smirnoff , Kubilay Kocak , freebsd-net , Karl Pielorz Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 14:58:33 -0000 On Thu, Sep 22, 2016 at 4:04 AM, Steven Hartland wrote: > The disappointing thing about this is we had a solution, all be it one not > everyone liked, nearly a year ago now and yet here we are still stuck with > a broken lagg implementation in the tree. > I would point out this 4-year-old thread in which a former co-worker pointed the same issue with GARPs not being issued and proposed a fix that was rejected (rightly) for being too much of a layer violation. It's disappointing to me to see that somebody has fixed the issue in exactly the way proposed in this thread, only to have the method that was correct 4 years ago rejected today. https://lists.freebsd.org/pipermail/freebsd-net/2012-February/031328.html From owner-freebsd-net@freebsd.org Thu Sep 22 15:09:42 2016 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 B8D0ABE5E56 for ; Thu, 22 Sep 2016 15:09:42 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8559093D; Thu, 22 Sep 2016 15:09:42 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u8MF9fTY019879 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Sep 2016 08:09:41 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u8MF9f9C019878; Thu, 22 Sep 2016 08:09:41 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 22 Sep 2016 08:09:40 -0700 From: Gleb Smirnoff To: Steven Hartland Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160922150940.GK1018@cell.glebi.us> References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 15:09:42 -0000 On Thu, Sep 22, 2016 at 08:21:08AM +0100, Steven Hartland wrote: S> On 22/09/2016 03:58, Gleb Smirnoff wrote: S> > On Wed, Sep 21, 2016 at 09:12:11PM -0400, Ryan Stone wrote: S> > R> > IMHO, the original patch was absolutely evil hack touching multiple S> > R> > layers, for the sake of a very special problem. S> > R> > S> > R> > I think, that in order to kick forwarding table on switches, lagg S> > R> > should: S> > R> > S> > R> > - allocate an mbuf itself S> > R> > - set its source hardware address to its own S> > R> > - set destination hardware to broadcast S> > R> > - put some payload in there, to make packet of valid size. Why should it be S> > R> > gratuitous ARP? A machine can be running IPv6 only, or may even use S> > R> > whatever S> > R> > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this S> > R> > Layer 2 S> > R> > problem at all. S> > R> > - Finally, send the prepared mbuf down the lagg member(s). S> > R> > S> > R> > And please don't hack half of the network stack to achieve that :) S> > R> S> > R> The original report in this thread is about a system where it takes almost S> > R> 15 minutes for the network to start working again after a failover. That S> > R> does not sound to me like a switch problem. That sounds to me like the ARP S> > R> cache on the remote system. To fix such a case we have to touch L3. S> > S> > Does lagg(4) hardware address change when it failovers? S> > S> It moves the address between interfaces which typically moves it between S> switches too. So, the address doesn't change, which means ARP cache doesn't need to change as well. If it moves between switches, all that needs to be done is to send whatever packet from proper hardware address to broadcast. -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Sep 22 15:33:10 2016 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 6EA29BE5A52 for ; Thu, 22 Sep 2016 15:33:10 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 15223A88 for ; Thu, 22 Sep 2016 15:33:09 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x233.google.com with SMTP id l132so154623526wmf.1 for ; Thu, 22 Sep 2016 08:33:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=cemybXhtojCHrNW2IiS7tnCwIIGfczqh08Bpzrx7TU8=; b=jWBbk1Op5/l6MrvGJ9x/+Zf3z57OWes07GGNQqtVnQhomW7ECGZ+9FLz1b5Q7B4MSP mKYcxMejkPzi6j9d5M7DK1jkboQ1KnSMn/ezHdNPHl3+qkhNTTaXk9l+SMGEKlLs0m8Z MkVn4xTEBW8jS9/LILIiuOmSqqdNzqXAON0TkTJuwfPD1hYIhowPSYl1gdhk8E6kdQnK RWlMXew/1ScmVhdcRqqmLxxVJ5Z8GBKEssEAeJNZjKZB84y8r0RtJGyUNz0dUHWL9G8b 7SQogllaK9VvOAMy1Lt9HMXlXr0UoOOTq6kHp13g/11gZOUBGQtHJKEVBjtQOqclwMUi PlRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=cemybXhtojCHrNW2IiS7tnCwIIGfczqh08Bpzrx7TU8=; b=bLQw5So+8sMSX34wSoN+Ccd/F41frYzXYeo0kzks1zvV9E93LQqVRvvjVXuMQrOroJ xSyUFlpnQ4SGjvXfRMyL1SnyGeTNKtlXISn0Aq6OWwh9dZvFSYYV5NzSu2Zc97uDNJyL 96m10XxPsvd4agqq3nlKHbL7Q3rZtomggVQZLE9PaY7bC33leEKG33V9fLgDXbOiIsXr ePQFyI4ARf0XlC1WxoBtAKXWa79SGvUbdMx+VMJq4vHkl7KvhT15EeDNXzevL2U/O/GD Ty0065cj51eXjNB68QtMJ3kqiVou3tn3qvGcmwz8PnejEBCva686ZubEWX2vUFPZ1blk nb/Q== X-Gm-Message-State: AE9vXwMhVdw4YlvCpkxsDFzEAOJN9KiNPTGPGvwW56Nq1GiTZhacjvWwym5IKdU2jt+CMAWB X-Received: by 10.194.8.226 with SMTP id u2mr2816756wja.153.1474558388283; Thu, 22 Sep 2016 08:33:08 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id w71sm3045055wmw.17.2016.09.22.08.33.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 08:33:06 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Ryan Stone References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <48632d42-ea2b-b147-737d-d7decfdbcff4@multiplay.co.uk> Cc: Gleb Smirnoff , Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: Date: Thu, 22 Sep 2016 16:33:05 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 15:33:10 -0000 On 22/09/2016 15:58, Ryan Stone wrote: > On Thu, Sep 22, 2016 at 4:04 AM, Steven Hartland > > wrote: > > The disappointing thing about this is we had a solution, all be it > one not everyone liked, nearly a year ago now and yet here we are > still stuck with a broken lagg implementation in the tree. > > > I would point out this 4-year-old thread in which a former co-worker > pointed the same issue with GARPs not being issued and proposed a fix > that was rejected (rightly) for being too much of a layer violation. > It's disappointing to me to see that somebody has fixed the issue in > exactly the way proposed in this thread, only to have the method that > was correct 4 years ago rejected today. > > https://lists.freebsd.org/pipermail/freebsd-net/2012-February/031328.html > That was indeed one of the thread I got inspiration from for the approach. From owner-freebsd-net@freebsd.org Thu Sep 22 15:34:07 2016 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 9CCC8BE5B34 for ; Thu, 22 Sep 2016 15:34:07 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::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 20F63B75 for ; Thu, 22 Sep 2016 15:34:07 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22b.google.com with SMTP id b130so154985584wmc.0 for ; Thu, 22 Sep 2016 08:34:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=TeryOZlWcySRiyWiS+4SfjKW7ccvVLxICspmy3ZGJb0=; b=rgXnbFDSl2w/jiWUw/RVGUFjSIezDITrs66GfCy56dNHzdFOVZhL7NviygjYxlbT37 MsXMR5Anfcw6CfJVKqWMkzdaqFtl1CemP8KGF4m3uo9kJOR3ge5tsojQtwaTXQ5zJipX wXB2cFKLLwIT0r7Q8drz1PgZADxFMf6aD9BelNDcpwAMIzXFo1fXcH3ZWRDvCbfOIF+7 AD9yBtJyo5egwGFXkMz/hwul3dQ8YpAsQwAfSE5kmRWVGN0jXzABJsQ5qVvvOWXiOG7W lubhB2z9OSR2fgnPbu5cUeqzhUourWXpQPDMkKXm8+LSZPeRJZTMqjMdc/gmGT8tiTT4 onTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=TeryOZlWcySRiyWiS+4SfjKW7ccvVLxICspmy3ZGJb0=; b=drmsMF9HxEnuOXiE3LbD1EqhWHGHehr+d/FEJNMDhEyb7ZIFmjS9DCXZHAyN9Mmcb7 2/RIvGXBmW3yxANyb0a46owaQoDWnubgg1Nf5KEsFVK9LR29GRT+smaGDQW2wwBeGwn1 QUbsDuX4rNgOQqmpmF+Dir8NWs/sKhJ4aoWud/E4NWmWbxJMfh2gdFBufve950K1cDxA gvolvFAXO7YCz2ZajP6I3bctSLjV3bn66SLOj8KdNtXTx6rUM7wDCmmGyCAhAn4GYjHK OcQhC8Sg1P2616eTpUN/ddGVKl8JP9z6hWoVySbvfPOdw8zO38CU52jojBb5IbxVyRR6 oV7g== X-Gm-Message-State: AE9vXwNTz2/MxD5x1H09u7p2miWK1F4CkedicE0qO9iEYtG8LKwU6MvAU/qALB+fIXhbaGqV X-Received: by 10.194.216.233 with SMTP id ot9mr2688118wjc.166.1474558445066; Thu, 22 Sep 2016 08:34:05 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id n7sm3037732wmf.18.2016.09.22.08.34.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 08:34:04 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: Date: Thu, 22 Sep 2016 16:34:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160922150940.GK1018@cell.glebi.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 15:34:07 -0000 On 22/09/2016 16:09, Gleb Smirnoff wrote: > On Thu, Sep 22, 2016 at 08:21:08AM +0100, Steven Hartland wrote: > S> On 22/09/2016 03:58, Gleb Smirnoff wrote: > S> > On Wed, Sep 21, 2016 at 09:12:11PM -0400, Ryan Stone wrote: > S> > R> > IMHO, the original patch was absolutely evil hack touching multiple > S> > R> > layers, for the sake of a very special problem. > S> > R> > > S> > R> > I think, that in order to kick forwarding table on switches, lagg > S> > R> > should: > S> > R> > > S> > R> > - allocate an mbuf itself > S> > R> > - set its source hardware address to its own > S> > R> > - set destination hardware to broadcast > S> > R> > - put some payload in there, to make packet of valid size. Why should it be > S> > R> > gratuitous ARP? A machine can be running IPv6 only, or may even use > S> > R> > whatever > S> > R> > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this > S> > R> > Layer 2 > S> > R> > problem at all. > S> > R> > - Finally, send the prepared mbuf down the lagg member(s). > S> > R> > > S> > R> > And please don't hack half of the network stack to achieve that :) > S> > R> > S> > R> The original report in this thread is about a system where it takes almost > S> > R> 15 minutes for the network to start working again after a failover. That > S> > R> does not sound to me like a switch problem. That sounds to me like the ARP > S> > R> cache on the remote system. To fix such a case we have to touch L3. > S> > > S> > Does lagg(4) hardware address change when it failovers? > S> > > S> It moves the address between interfaces which typically moves it between > S> switches too. > > So, the address doesn't change, which means ARP cache doesn't need to > change as well. If it moves between switches, all that needs to be done > is to send whatever packet from proper hardware address to broadcast. > That would be nice but unfortunately in the wild that won't work as without GARP devices can and do ignore :( Regards Steve From owner-freebsd-net@freebsd.org Thu Sep 22 15:41:46 2016 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 CFAC7BE616F for ; Thu, 22 Sep 2016 15:41:46 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ABC631111; Thu, 22 Sep 2016 15:41:45 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u8MFfi8s020086 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Sep 2016 08:41:44 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u8MFfiUT020085; Thu, 22 Sep 2016 08:41:44 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 22 Sep 2016 08:41:44 -0700 From: Gleb Smirnoff To: Steven Hartland Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160922154144.GO1018@cell.glebi.us> References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 15:41:46 -0000 On Thu, Sep 22, 2016 at 04:34:03PM +0100, Steven Hartland wrote: S> On 22/09/2016 16:09, Gleb Smirnoff wrote: S> > On Thu, Sep 22, 2016 at 08:21:08AM +0100, Steven Hartland wrote: S> > S> On 22/09/2016 03:58, Gleb Smirnoff wrote: S> > S> > On Wed, Sep 21, 2016 at 09:12:11PM -0400, Ryan Stone wrote: S> > S> > R> > IMHO, the original patch was absolutely evil hack touching multiple S> > S> > R> > layers, for the sake of a very special problem. S> > S> > R> > S> > S> > R> > I think, that in order to kick forwarding table on switches, lagg S> > S> > R> > should: S> > S> > R> > S> > S> > R> > - allocate an mbuf itself S> > S> > R> > - set its source hardware address to its own S> > S> > R> > - set destination hardware to broadcast S> > S> > R> > - put some payload in there, to make packet of valid size. Why should it be S> > S> > R> > gratuitous ARP? A machine can be running IPv6 only, or may even use S> > S> > R> > whatever S> > S> > R> > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this S> > S> > R> > Layer 2 S> > S> > R> > problem at all. S> > S> > R> > - Finally, send the prepared mbuf down the lagg member(s). S> > S> > R> > S> > S> > R> > And please don't hack half of the network stack to achieve that :) S> > S> > R> S> > S> > R> The original report in this thread is about a system where it takes almost S> > S> > R> 15 minutes for the network to start working again after a failover. That S> > S> > R> does not sound to me like a switch problem. That sounds to me like the ARP S> > S> > R> cache on the remote system. To fix such a case we have to touch L3. S> > S> > S> > S> > Does lagg(4) hardware address change when it failovers? S> > S> > S> > S> It moves the address between interfaces which typically moves it between S> > S> switches too. S> > S> > So, the address doesn't change, which means ARP cache doesn't need to S> > change as well. If it moves between switches, all that needs to be done S> > is to send whatever packet from proper hardware address to broadcast. S> > S> That would be nice but unfortunately in the wild that won't work as S> without GARP devices can and do ignore :( You can create a fake gratious ARP packet, if you want. Switches must not require IP addresses matching the reality in the packet. P.S. I always read GARP as Generic Attribute Registration Protocol. -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Sep 22 15:52:39 2016 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 5DCC3BE67B8 for ; Thu, 22 Sep 2016 15:52:39 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 D373A1730 for ; Thu, 22 Sep 2016 15:52:38 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22d.google.com with SMTP id b130so155909139wmc.0 for ; Thu, 22 Sep 2016 08:52:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=ragNIBMDQyFQ/vCz77ho5q1arZgcWq0xbgmmSNY2xhc=; b=i+oV6COmJ1cj/c8+8K7KG5nFAP/AOcXGPXHLsheR61E5fY0C5gCVlq0lvO4Lbbvcq+ g3gselXxUcYZIpRXtBOQFFpUrDH20w7dKxZDU0GKAMxy1is4EguSizIrBJzzCZd2z9n1 QFKcBtkkXHJ231UbzwXs2dieSv549peHESKaZBHu56veYF52fu0Cpt3/JL+0K9g5Pfp4 P80SANk++qs/ox/CGYURWj8ceLTaqEi8Fz9ywpg8FUgqHpaRs8Cp7RznLaVMqasoBLO1 SXSVULWQIhclDk+lu7cfKmlZzSmY6lt+N6UHE1y/3jLewmc4hJCsMq7xJGKm65xQtgpQ +yIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=ragNIBMDQyFQ/vCz77ho5q1arZgcWq0xbgmmSNY2xhc=; b=DWI0FahGyZSala0OK/jsK3FwJPEYNNie6gmiNrMbk+f+HE1Ow2W44fwsPXUe6HlXyV KidzzcqIwQQLH0Uw9R40kTjpYPsoMHmg6szmU4jK6oc+cuyGZBhxRvm4QAyAeml0ixD1 UwcbxwOrx8rtGr092b1kd8n6efev6BfkzIy7weAAtmFv4/X2E/ki9InIvncnMOpRRvwW CKWwTVrNldeGtlwRq2svHr5JVHlV1cMxOl22SoGr2Rw/LSAUkZ/We9O+VuUBa8g92KQH hycnIYqap4VPVltATZyCMFFAOgBtFpGkYXlKb37yp6GOzDpaL1KbosChMOey6714z/3A OfKw== X-Gm-Message-State: AE9vXwN4cv+GkdsbrIIMcjDmWztWLi4rzY3VvdqJqKZHpJLr04wO1+2/B1z3A3i+Ph0+SGUk X-Received: by 10.194.148.145 with SMTP id ts17mr2681581wjb.91.1474559556986; Thu, 22 Sep 2016 08:52:36 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id t202sm38220616wmt.22.2016.09.22.08.52.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 08:52:36 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff References: <0D84203FAAFD0A8E7BBB24A3@10.12.30.106> <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> Date: Thu, 22 Sep 2016 16:52:35 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160922154144.GO1018@cell.glebi.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 15:52:39 -0000 On 22/09/2016 16:41, Gleb Smirnoff wrote: > On Thu, Sep 22, 2016 at 04:34:03PM +0100, Steven Hartland wrote: > S> On 22/09/2016 16:09, Gleb Smirnoff wrote: > S> > On Thu, Sep 22, 2016 at 08:21:08AM +0100, Steven Hartland wrote: > S> > S> On 22/09/2016 03:58, Gleb Smirnoff wrote: > S> > S> > On Wed, Sep 21, 2016 at 09:12:11PM -0400, Ryan Stone wrote: > S> > S> > R> > IMHO, the original patch was absolutely evil hack touching multiple > S> > S> > R> > layers, for the sake of a very special problem. > S> > S> > R> > > S> > S> > R> > I think, that in order to kick forwarding table on switches, lagg > S> > S> > R> > should: > S> > S> > R> > > S> > S> > R> > - allocate an mbuf itself > S> > S> > R> > - set its source hardware address to its own > S> > S> > R> > - set destination hardware to broadcast > S> > S> > R> > - put some payload in there, to make packet of valid size. Why should it be > S> > S> > R> > gratuitous ARP? A machine can be running IPv6 only, or may even use > S> > S> > R> > whatever > S> > S> > R> > higher level protocol, e.g. PPPoE. We shouldn't involve IP into this > S> > S> > R> > Layer 2 > S> > S> > R> > problem at all. > S> > S> > R> > - Finally, send the prepared mbuf down the lagg member(s). > S> > S> > R> > > S> > S> > R> > And please don't hack half of the network stack to achieve that :) > S> > S> > R> > S> > S> > R> The original report in this thread is about a system where it takes almost > S> > S> > R> 15 minutes for the network to start working again after a failover. That > S> > S> > R> does not sound to me like a switch problem. That sounds to me like the ARP > S> > S> > R> cache on the remote system. To fix such a case we have to touch L3. > S> > S> > > S> > S> > Does lagg(4) hardware address change when it failovers? > S> > S> > > S> > S> It moves the address between interfaces which typically moves it between > S> > S> switches too. > S> > > S> > So, the address doesn't change, which means ARP cache doesn't need to > S> > change as well. If it moves between switches, all that needs to be done > S> > is to send whatever packet from proper hardware address to broadcast. > S> > > S> That would be nice but unfortunately in the wild that won't work as > S> without GARP devices can and do ignore :( > > You can create a fake gratious ARP packet, if you want. Switches must not > require IP addresses matching the reality in the packet. > > P.S. I always read GARP as Generic Attribute Registration Protocol. > We could but then what happens when its IPv6 or $other protocol that needs to know? That would require lagg to be edited with all the special cases instead of allowing the protocol to handle it they way it needs. Overall, while the proposed change (https://reviews.freebsd.org/D4111) does involve changes to multiple layers it still feels like the right approach as it has the right layer dealing with the change instead of hard-coded assumptions. Regards Steve From owner-freebsd-net@freebsd.org Thu Sep 22 16:08:42 2016 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 E5B44BE5359 for ; Thu, 22 Sep 2016 16:08:42 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C27AB1C2; Thu, 22 Sep 2016 16:08:42 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u8MG8fKD020237 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Sep 2016 09:08:41 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u8MG8fhd020236; Thu, 22 Sep 2016 09:08:41 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 22 Sep 2016 09:08:40 -0700 From: Gleb Smirnoff To: Steven Hartland Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160922160840.GP1018@cell.glebi.us> References: <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 16:08:43 -0000 On Thu, Sep 22, 2016 at 04:52:35PM +0100, Steven Hartland wrote: S> > S> > S> > Does lagg(4) hardware address change when it failovers? S> > S> > S> > S> > S> > S> It moves the address between interfaces which typically moves it between S> > S> > S> switches too. S> > S> > S> > S> > So, the address doesn't change, which means ARP cache doesn't need to S> > S> > change as well. If it moves between switches, all that needs to be done S> > S> > is to send whatever packet from proper hardware address to broadcast. S> > S> > S> > S> That would be nice but unfortunately in the wild that won't work as S> > S> without GARP devices can and do ignore :( S> > S> > You can create a fake gratious ARP packet, if you want. Switches must not S> > require IP addresses matching the reality in the packet. S> > S> > P.S. I always read GARP as Generic Attribute Registration Protocol. S> > S> We could but then what happens when its IPv6 or $other protocol that S> needs to know? That would require lagg to be edited with all the special S> cases instead of allowing the protocol to handle it they way it needs. You just said that "without GARP devices can and do ignore", didn't you? Let's take this as truth, although I doubt. So, if this is the truth, that means that if you are running IPv6 only, the switches won't recondigure theirselves due to lack of gratious ARP. Other protocols, where PPPoE is good example simply doesn't have any analogs of ARP or ND. So what would your switches do in that case? And what other layers are you going to hack, if you are going to run PPPoE service with lagg failover? In reality, a layer 2 device must forward layer 2 traffic, and must reconfigure its forwarding table based on source addresses seen on ports. And that's what all devices I've seen do. So what if we actually try the approach, I suggested? I can write the patch for you if you want. S> Overall, while the proposed change (https://reviews.freebsd.org/D4111) S> does involve changes to multiple layers it still feels like the right S> approach as it has the right layer dealing with the change instead of S> hard-coded assumptions. Sorry, it doesn't feel like the right approach. :( -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Sep 22 16:50:12 2016 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 E1FEABE65D6 for ; Thu, 22 Sep 2016 16:50:12 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F29110D2 for ; Thu, 22 Sep 2016 16:50:12 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22f.google.com with SMTP id w84so263858928wmg.1 for ; Thu, 22 Sep 2016 09:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=nwpR30Dhz8/DyJX/qrXFlQjLFnDatMSNL4m4zdXTxzk=; b=lu5Igf8DjIhhj6Wqll/JMG95MwheCSOIGjwTO/m9s50QKR4HKP4eB6KjD3D6Xijcwy yrAO7Nv58EtNwkIqINj6Qgk7Yg3Mud1v3u8zwARGvwr5Rlm62PSagI6TPLqhtokxtk17 fZweZ2ViUWBhbZrDVY68RebNXCstr2YrW/UB5deif8rQntC1AFZRU6/EycnEqMvKrZv8 qyNUwpSASiFgNGChrN29IVgsjmD2ktSkkn7GvaRH1aTtv5eaoxdFTNGWHOScgMNgKR2v B5hk1bSm5m02RUAVRddB8xezqlAu5mToAW5cjEDXZO56XkQYqeuh3/wwSpN8MFFBUIgf 7zxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=nwpR30Dhz8/DyJX/qrXFlQjLFnDatMSNL4m4zdXTxzk=; b=FZAm97ZJUfKWMGK6pTmqWrtDBr09yV/YYO4sqkegIm8y08LuXoIaCPQwamRD0t4OaR boj9UeYa3XPulYV8Qt3Qw8Yh0zk8FnZMNsRJE0CRNDRRLxY0SX+jKaKwWBE2uvJ4xeE5 AJh3yM4sXZYf1/1K3A3vJVBSYku/oCRKFaOJKvIYkBFFg/BP4/6mN6y6q3NuE8rqAzAC TIwIMAgO/NQKe7/tQaRLen8ts5h2ZdV6eg//UL+0fG5zIrMCCx2CwTaBSsG2M2KaQ5sc tISHbJljqonzoAMHGr6+isRVWHAQ/V1aziecIXlGLiQwvLjqnx3VPQPiSE2h8B+ommsp bzIg== X-Gm-Message-State: AE9vXwMFolirfKxhMtbTpthjzN/2t+aA3bDKyDqgaoEj1xsrc2F/O2GMktfUkgWWGpUHz9NB X-Received: by 10.28.7.80 with SMTP id 77mr3293595wmh.28.1474563010821; Thu, 22 Sep 2016 09:50:10 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id n28sm3379160wmi.2.2016.09.22.09.50.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 09:50:09 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff References: <6E574F1B61786E6032824A88@10.12.30.106> <2c62f5f0-3fb4-f513-2a8f-02de3a1d552f@FreeBSD.org> <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> <20160922160840.GP1018@cell.glebi.us> Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> Date: Thu, 22 Sep 2016 17:50:09 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160922160840.GP1018@cell.glebi.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 16:50:13 -0000 On 22/09/2016 17:08, Gleb Smirnoff wrote: > On Thu, Sep 22, 2016 at 04:52:35PM +0100, Steven Hartland wrote: > S> > S> > S> > Does lagg(4) hardware address change when it failovers? > S> > S> > S> > > S> > S> > S> It moves the address between interfaces which typically moves it between > S> > S> > S> switches too. > S> > S> > > S> > S> > So, the address doesn't change, which means ARP cache doesn't need to > S> > S> > change as well. If it moves between switches, all that needs to be done > S> > S> > is to send whatever packet from proper hardware address to broadcast. > S> > S> > > S> > S> That would be nice but unfortunately in the wild that won't work as > S> > S> without GARP devices can and do ignore :( > S> > > S> > You can create a fake gratious ARP packet, if you want. Switches must not > S> > require IP addresses matching the reality in the packet. > S> > > S> > P.S. I always read GARP as Generic Attribute Registration Protocol. > S> > > S> We could but then what happens when its IPv6 or $other protocol that > S> needs to know? That would require lagg to be edited with all the special > S> cases instead of allowing the protocol to handle it they way it needs. > > You just said that "without GARP devices can and do ignore", didn't you? > Let's take this as truth, although I doubt. So, if this is the truth, that > means that if you are running IPv6 only, the switches won't recondigure > theirselves due to lack of gratious ARP. Not sure I follow you, gratuitous ARP is required for IPv4 to work, for IPv6 you need an unsolicited neighbour announcement. > Other protocols, where PPPoE is good example simply doesn't have any > analogs of ARP or ND. So what would your switches do in that case? And > what other layers are you going to hack, if you are going to run PPPoE > service with lagg failover? Good question, surely that's a good reason to have each protocol handle it and not to teach LAGG about every possible protocol? > In reality, a layer 2 device must forward layer 2 traffic, and must > reconfigure its forwarding table based on source addresses seen on ports. > And that's what all devices I've seen do. So what if we actually try > the approach, I suggested? I can write the patch for you if you want. The main problem with LAGG in failover mode is ensuring the traffic is sent to the correct port. When you have the scenario where a switch stack believes MAC XYZ is accessible by port ABC then unless you tell it otherwise it will continue to believe that and hence send traffic to said port. I'm sure we'll agree that the standard for doing this for IPv4 is ARP and for IPv6 is NA. When using LAGG and we loose the master port we need correct the connected devices view (both direct and remote) of the world such that traffic is now sent to a different physical port. Back in the day, when switches weren't so "smart", sending a correctly address packet from the new port would potentially help, but with smarter switches and stacking in the mix sticking to the "standards" helps maintain compatibility and hence functionality with things like LAGG. Having tested with a number of vendor switches Cisco, Extreme and more recently Arista only sending gratuitous ARP for IPv4 and unsolicited NA for IPv6 reliably resulted in rapid failover between LAGG ports. Other methods like sending correctly addressed output from the new port helped, we tested this with outbound pings from IPMI, but still resulted in noticeable recovery delay. > S> Overall, while the proposed change (https://reviews.freebsd.org/D4111) > S> does involve changes to multiple layers it still feels like the right > S> approach as it has the right layer dealing with the change instead of > S> hard-coded assumptions. > > Sorry, it doesn't feel like the right approach. :( Out of interest why has your opinion changed since your post here: https://lists.freebsd.org/pipermail/freebsd-net/2012-February/031340.html ? From owner-freebsd-net@freebsd.org Thu Sep 22 18:02:34 2016 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 5EA47BE5E73 for ; Thu, 22 Sep 2016 18:02:34 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 1A20975C; Thu, 22 Sep 2016 18:02:34 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bn8KM-000581-NN; Thu, 22 Sep 2016 21:02:30 +0300 Date: Thu, 22 Sep 2016 21:02:30 +0300 From: Slawa Olhovchenkov To: Steven Hartland Cc: Gleb Smirnoff , Kubilay Kocak , Ryan Stone , Karl Pielorz , freebsd-net Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160922180230.GD2840@zxy.spb.ru> References: <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> <20160922160840.GP1018@cell.glebi.us> <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 18:02:34 -0000 On Thu, Sep 22, 2016 at 05:50:09PM +0100, Steven Hartland wrote: > Having tested with a number of vendor switches Cisco, Extreme and more > recently Arista only sending gratuitous ARP for IPv4 and unsolicited NA > for IPv6 reliably resulted in rapid failover between LAGG ports. > > Other methods like sending correctly addressed output from the new port > helped, we tested this with outbound pings from IPMI, but still resulted > in noticeable recovery delay. Can you give network diagram and switchs configs for this? Recovery delay on lagg interface and lacp protocol must be about 2s by default configuration. From owner-freebsd-net@freebsd.org Thu Sep 22 18:04:01 2016 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 502E1BE5F76 for ; Thu, 22 Sep 2016 18:04:01 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DBA6846; Thu, 22 Sep 2016 18:04:00 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u8MI3xcH020752 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Sep 2016 11:03:59 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u8MI3xcO020751; Thu, 22 Sep 2016 11:03:59 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 22 Sep 2016 11:03:59 -0700 From: Gleb Smirnoff To: Steven Hartland Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz Subject: Re: lagg Interfaces - don't do Gratuitous ARP? Message-ID: <20160922180359.GT1018@cell.glebi.us> References: <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> <20160922160840.GP1018@cell.glebi.us> <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 18:04:01 -0000 On Thu, Sep 22, 2016 at 05:50:09PM +0100, Steven Hartland wrote: S> > S> We could but then what happens when its IPv6 or $other protocol that S> > S> needs to know? That would require lagg to be edited with all the special S> > S> cases instead of allowing the protocol to handle it they way it needs. S> > S> > You just said that "without GARP devices can and do ignore", didn't you? S> > Let's take this as truth, although I doubt. So, if this is the truth, that S> > means that if you are running IPv6 only, the switches won't recondigure S> > theirselves due to lack of gratious ARP. S> Not sure I follow you, gratuitous ARP is required for IPv4 to work, for S> IPv6 you need an unsolicited neighbour announcement. S> > Other protocols, where PPPoE is good example simply doesn't have any S> > analogs of ARP or ND. So what would your switches do in that case? And S> > what other layers are you going to hack, if you are going to run PPPoE S> > service with lagg failover? S> Good question, surely that's a good reason to have each protocol handle S> it and not to teach LAGG about every possible protocol? No. It is not a good reason to have each protocol handle it. It is a demonstration that this must be handled by a lower protocol layer - the L2, which is the level where problem exists. S> > In reality, a layer 2 device must forward layer 2 traffic, and must S> > reconfigure its forwarding table based on source addresses seen on ports. S> > And that's what all devices I've seen do. So what if we actually try S> > the approach, I suggested? I can write the patch for you if you want. S> The main problem with LAGG in failover mode is ensuring the traffic is S> sent to the correct port. S> S> When you have the scenario where a switch stack believes MAC XYZ is S> accessible by port ABC then unless you tell it otherwise it will S> continue to believe that and hence send traffic to said port. I'm sure S> we'll agree that the standard for doing this for IPv4 is ARP and for S> IPv6 is NA. No, we don't agree on that. I assert that the ARP is standard to map IPv4 address to physical address, not to a port. Same for NA. The de-facto standard for a switch to believe that MAC XYZ is accessible by port ABC is looking at the source address of any packet on a port. S> When using LAGG and we loose the master port we need correct the S> connected devices view (both direct and remote) of the world such that S> traffic is now sent to a different physical port. S> S> Back in the day, when switches weren't so "smart", sending a correctly S> address packet from the new port would potentially help, but with S> smarter switches and stacking in the mix sticking to the "standards" S> helps maintain compatibility and hence functionality with things like LAGG. S> S> Having tested with a number of vendor switches Cisco, Extreme and more S> recently Arista only sending gratuitous ARP for IPv4 and unsolicited NA S> for IPv6 reliably resulted in rapid failover between LAGG ports. S> S> Other methods like sending correctly addressed output from the new port S> helped, we tested this with outbound pings from IPMI, but still resulted S> in noticeable recovery delay. This means that switches are "smart" and are violating standards. If you want to create a hack to deal with that, better keep this hack inside the module that is affected by "smart" switches, in the lagg driver. And not plow through all levels of network stack to satisfy demands of standard violators. So, please send a self made gratious ARP packet right from lagg(4). If the switches work as you describe, that would work regardless of the actual IPv4/IPv6/whatever configuration. S> > S> Overall, while the proposed change (https://reviews.freebsd.org/D4111) S> > S> does involve changes to multiple layers it still feels like the right S> > S> approach as it has the right layer dealing with the change instead of S> > S> hard-coded assumptions. S> > S> > Sorry, it doesn't feel like the right approach. :( S> Out of interest why has your opinion changed since your post here: S> https://lists.freebsd.org/pipermail/freebsd-net/2012-February/031340.html ? I'm sorry, I didn't look at D4111, expecting that it is exactly the patch that was backed out. I will review D4111. -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Sep 22 19:14:00 2016 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 C759BBE5FC3 for ; Thu, 22 Sep 2016 19:14:00 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59894EF1 for ; Thu, 22 Sep 2016 19:14:00 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22f.google.com with SMTP id b130so165632184wmc.0 for ; Thu, 22 Sep 2016 12:14:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=3JLQBcPJYVX5m1uC/n9XYtV3PlLftbWAiJaHTcSV8dQ=; b=cR5+3LihHStjwmi/C2BsJpc8EPJr62lZZpDzEk4XdUDfFnYpqpdlyRicA92piQHY3D NYOYhVA2ROl1zswxx5xz2J9eVZgC33eVC3a2iA/w49JyA+I62BTGgwFe7nhDVW9udcqa mjbs89OeUFhnicIlCFSzdCrIvUXubT7i3UmOal9smfWsgrf861A+U13d1nbstfB+DGH9 sb2zN1zH3RSz5/BBvdAXJD7m5pnvoIuJ2bRzPggdtvLn8URJ+dfwGiKxwlbuiWUlnl5T K/6N3lijbhwNsF5YWhofrhlrj2Pkca5y7Kb0d2m7rOG5uDdRgu1FeNz0vcrcSX2Xizc+ ALzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=3JLQBcPJYVX5m1uC/n9XYtV3PlLftbWAiJaHTcSV8dQ=; b=kYXcrHfaLgHd1up5xvmM0k7gYLtYMH5behs9yIcSor76mQLP2rW7sIs+05ccCeqS2G OVCJbqQR6i9YUtqHvFHS1zP1mvvWcJzBMqhPcil8HzkEkQ0pg2TIc8nYb1VBPM23k0dg UwgBh5RSoa2JApgfKcmxabsKPNFZZY6KdTCZEY8+WqtPW2kDAExIAoGXIIHzqdbX4s+3 sZ+f51agNPajkNC+vaCwq4wFd9W8TF1fxZjlDHzOh4o8HLc8SMGm0UdUMIdTsfCFVbwc q9l0SFMF3/S27Q8Uj6QXrY11O2Cm+bjDj7DViQ7bp/YTRUtShk6cl5V7d5KUaAxM3rcp avPQ== X-Gm-Message-State: AA6/9RkpPcC8Tkhz6laa0gk2pkkI84Jn8FQ4V7x5Db0F2Qp1m6/tp/ECOUdqv6AhAScBoi3k X-Received: by 10.28.199.14 with SMTP id x14mr4080541wmf.106.1474571638609; Thu, 22 Sep 2016 12:13:58 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id l206sm5307589wmf.15.2016.09.22.12.13.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 12:13:57 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Slawa Olhovchenkov References: <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> <20160922160840.GP1018@cell.glebi.us> <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> <20160922180230.GD2840@zxy.spb.ru> Cc: Gleb Smirnoff , Kubilay Kocak , Ryan Stone , Karl Pielorz , freebsd-net From: Steven Hartland Message-ID: Date: Thu, 22 Sep 2016 20:13:57 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160922180230.GD2840@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 19:14:00 -0000 On 22/09/2016 19:02, Slawa Olhovchenkov wrote: > On Thu, Sep 22, 2016 at 05:50:09PM +0100, Steven Hartland wrote: > >> Having tested with a number of vendor switches Cisco, Extreme and more >> recently Arista only sending gratuitous ARP for IPv4 and unsolicited NA >> for IPv6 reliably resulted in rapid failover between LAGG ports. >> >> Other methods like sending correctly addressed output from the new port >> helped, we tested this with outbound pings from IPMI, but still resulted >> in noticeable recovery delay. > Can you give network diagram and switchs configs for this? > Recovery delay on lagg interface and lacp protocol must be about 2s by > default configuration. This is failover not LACP which is something quite different. From owner-freebsd-net@freebsd.org Thu Sep 22 19:35:53 2016 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 994E9BE5ECA for ; Thu, 22 Sep 2016 19:35:53 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::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 39892117A for ; Thu, 22 Sep 2016 19:35:53 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x235.google.com with SMTP id w84so272168394wmg.1 for ; Thu, 22 Sep 2016 12:35:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=HvDeQtsgu1smOlX8Kwk7ulCO7DCQMr2W9p89l0eo1tY=; b=YEHxTCW8PNaCZEiVF83C2kA3JqNfQg5Z5Py7hscx2vbgKQysMNzxgS44ix5bVBxQ6O XzsRNEqXYesvnDoXjGnciZRJhIObbzA+EgaQW64PcP2U0xOfmXL7CR6cJwCq/wtgfiRO oCYqYFAaI1HhsFvjsncDK34/OL/0WZKp50rtf6pLWA7uFOFYmmuxtJ4+tMNEy6CasA/q UhfOzq9shEAw5yHwKYNqAjr4Wtkt3q5S2N5C5G79W7t3YxwHcSFry5CrGdSRpZTJY6Qz x9/VezBVWx0c59Qy4BOSkh36gGl4ZXZ6W4XcRis4eISNFC+Xp0LVndfgfFotqWIwqF0m 9VEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=HvDeQtsgu1smOlX8Kwk7ulCO7DCQMr2W9p89l0eo1tY=; b=EXZaErafr1++/l5T2B1NQzTwuW3YDKn29HAwiE5DHPxtpndCVhRhpXJ0/8pqC3HUWK RyTGaMsT+SwDAHXQ+Titac1NRSttPC27De6HXmgInddui6Bq8yG9zW5XJmc5oV534i+O yaKSIeu/3JQh8xC/Ua8ypCsTRZwLF6abKflPNNTfPUuMOKzBNALMBVAVgYLOUNFgF6Tz aUS6vzGHSMguEZJcHvL+rUUxV8suPTlHrbBHbXJXCVJQddjWZS1PhJUKhbZN70omalkt 1w17oX3TXOGo2l8xhsK57ufaYYavzsmlv8wjPMrZiMRxVrApjh7qe1k3XexY8VgdM2yC 9kZg== X-Gm-Message-State: AE9vXwOWwO7THyqDBmXOaQUEX3J2F1rmbf58ocH6WBJQwBtR/rdL0kexi8onDlJ7mF1fgp5c X-Received: by 10.194.170.163 with SMTP id an3mr3887066wjc.73.1474572951787; Thu, 22 Sep 2016 12:35:51 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id a5sm3582348wjd.9.2016.09.22.12.35.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 12:35:50 -0700 (PDT) Subject: Re: lagg Interfaces - don't do Gratuitous ARP? To: Gleb Smirnoff References: <20160921235703.GG1018@cell.glebi.us> <20160922025856.GH1018@cell.glebi.us> <348d534d-ef87-f90c-aa43-cc65c2f6283c@multiplay.co.uk> <20160922150940.GK1018@cell.glebi.us> <20160922154144.GO1018@cell.glebi.us> <0c678da4-bf72-5a81-aee1-d82a873661b7@multiplay.co.uk> <20160922160840.GP1018@cell.glebi.us> <80fd962a-fba3-d71e-a1cb-2b09181d3925@multiplay.co.uk> <20160922180359.GT1018@cell.glebi.us> Cc: Ryan Stone , Kubilay Kocak , freebsd-net , Karl Pielorz From: Steven Hartland Message-ID: Date: Thu, 22 Sep 2016 20:35:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160922180359.GT1018@cell.glebi.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 19:35:53 -0000 On 22/09/2016 19:03, Gleb Smirnoff wrote: > On Thu, Sep 22, 2016 at 05:50:09PM +0100, Steven Hartland wrote: > S> > S> We could but then what happens when its IPv6 or $other protocol that > S> > S> needs to know? That would require lagg to be edited with all the special > S> > S> cases instead of allowing the protocol to handle it they way it needs. > S> > > S> > You just said that "without GARP devices can and do ignore", didn't you? > S> > Let's take this as truth, although I doubt. So, if this is the truth, that > S> > means that if you are running IPv6 only, the switches won't recondigure > S> > theirselves due to lack of gratious ARP. > S> Not sure I follow you, gratuitous ARP is required for IPv4 to work, for > S> IPv6 you need an unsolicited neighbour announcement. > S> > Other protocols, where PPPoE is good example simply doesn't have any > S> > analogs of ARP or ND. So what would your switches do in that case? And > S> > what other layers are you going to hack, if you are going to run PPPoE > S> > service with lagg failover? > S> Good question, surely that's a good reason to have each protocol handle > S> it and not to teach LAGG about every possible protocol? > > No. It is not a good reason to have each protocol handle it. It is a > demonstration that this must be handled by a lower protocol layer - the L2, > which is the level where problem exists. > > S> > In reality, a layer 2 device must forward layer 2 traffic, and must > S> > reconfigure its forwarding table based on source addresses seen on ports. > S> > And that's what all devices I've seen do. So what if we actually try > S> > the approach, I suggested? I can write the patch for you if you want. > S> The main problem with LAGG in failover mode is ensuring the traffic is > S> sent to the correct port. > S> > S> When you have the scenario where a switch stack believes MAC XYZ is > S> accessible by port ABC then unless you tell it otherwise it will > S> continue to believe that and hence send traffic to said port. I'm sure > S> we'll agree that the standard for doing this for IPv4 is ARP and for > S> IPv6 is NA. > > No, we don't agree on that. I assert that the ARP is standard to map IPv4 > address to physical address, not to a port. Same for NA. The de-facto > standard for a switch to believe that MAC XYZ is accessible by port ABC > is looking at the source address of any packet on a port. > > S> When using LAGG and we loose the master port we need correct the > S> connected devices view (both direct and remote) of the world such that > S> traffic is now sent to a different physical port. > S> > S> Back in the day, when switches weren't so "smart", sending a correctly > S> address packet from the new port would potentially help, but with > S> smarter switches and stacking in the mix sticking to the "standards" > S> helps maintain compatibility and hence functionality with things like LAGG. > S> > S> Having tested with a number of vendor switches Cisco, Extreme and more > S> recently Arista only sending gratuitous ARP for IPv4 and unsolicited NA > S> for IPv6 reliably resulted in rapid failover between LAGG ports. > S> > S> Other methods like sending correctly addressed output from the new port > S> helped, we tested this with outbound pings from IPMI, but still resulted > S> in noticeable recovery delay. > > This means that switches are "smart" and are violating standards. If you want > to create a hack to deal with that, better keep this hack inside the module > that is affected by "smart" switches, in the lagg driver. And not plow through > all levels of network stack to satisfy demands of standard violators. > > So, please send a self made gratious ARP packet right from lagg(4). If the > switches work as you describe, that would work regardless of the actual > IPv4/IPv6/whatever configuration. > > S> > S> Overall, while the proposed change (https://reviews.freebsd.org/D4111) > S> > S> does involve changes to multiple layers it still feels like the right > S> > S> approach as it has the right layer dealing with the change instead of > S> > S> hard-coded assumptions. > S> > > S> > Sorry, it doesn't feel like the right approach. :( > S> Out of interest why has your opinion changed since your post here: > S> https://lists.freebsd.org/pipermail/freebsd-net/2012-February/031340.html ? > > I'm sorry, I didn't look at D4111, expecting that it is exactly the patch > that was backed out. I will review D4111. > They are similar in approach but incorporated additional feedback. Essentially it still follows your suggestion from 2012 which was: > 1) Network protocols should register theirselves on the ifnet_link_event > EVENTHANDLER(9). > 2) The inet4 should send gratutious ARP on this event. > 3) The inet6 should send NA. Hence my confusion ;-) Regards Steve From owner-freebsd-net@freebsd.org Fri Sep 23 08:52:20 2016 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 828CCBE6C85 for ; Fri, 23 Sep 2016 08:52:20 +0000 (UTC) (envelope-from tvmb@cameraforme.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6BADBF3 for ; Fri, 23 Sep 2016 08:52:20 +0000 (UTC) (envelope-from tvmb@cameraforme.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 6AAE8BE6C84; Fri, 23 Sep 2016 08:52:20 +0000 (UTC) Delivered-To: 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 6A00FBE6C83 for ; Fri, 23 Sep 2016 08:52:20 +0000 (UTC) (envelope-from tvmb@cameraforme.ru) Received: from cameraforme.ru (cameraforme.ru [185.87.48.186]) by mx1.freebsd.org (Postfix) with ESMTP id F137DED for ; Fri, 23 Sep 2016 08:52:18 +0000 (UTC) (envelope-from tvmb@cameraforme.ru) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=mail; d=cameraforme.ru; h=Message-ID:From:To:Subject:Date:MIME-Version:Content-Type; i=tvmb@cameraforme.ru; bh=8/hpiguWiFncnZtp7qh9MbZuS5M=; b=Rjy+BQVcKLTcxs3OZZMatbaLtM+dIEJDjADchJXTAnp1tlHOV/RVHXFtd1B1jiKtMaq+b68Lb232 VI7rtFVGWHIajtKk0lMPcTepfGUH7nCcas9cYLdZUFZ59aZDYyqBdTo9QzToYb8Pg/ELod1dmVv4 VCeVEuvbLLVhFHRdBZM= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=mail; d=cameraforme.ru; b=n3hrZTzixxz/u6kIrKQAip6VlmbD3jtsFhJvXhYGCOoM4F2UAT9ow72n2fSUL7bGiZXGoGvpm+Nu oj45M9xYQPp+V7bIu+eJpQjJ2/42qTSS39pgOzMUte4w++N7O790f50Ss7f0xi+4xJOvy+kXk+GC BPJrsBSHKupKWu63MVg=; Message-ID: From: =?windows-1251?B?3evo8u3g/yDv4PD0/uzl8Oj/?= To: Subject: =?windows-1251?B?zPsg5+Dq8Pvi4OXs8f8hIN3r6PLt4P8g7+Dw?= =?windows-1251?B?9P7s5fDo/iDxIM7D0E/MzU/JIPHq6OTq7ukh?= Date: Fri, 23 Sep 2016 11:50:12 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 08:52:20 -0000 =CC=FB =E7=E0=EA=F0=FB=E2=E0=E5=EC=F1=FF! =DD=EB=E8=F2=ED=E0=FF =EF=E0=F0= =F4=FE=EC=E5=F0=E8=FE =F1 =CE=C3=D0O=CC=CDO=C9 =F1=EA=E8=E4=EA=EE=E9! From owner-freebsd-net@freebsd.org Fri Sep 23 14:05:15 2016 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 01A0DBDC95D for ; Fri, 23 Sep 2016 14:05:15 +0000 (UTC) (envelope-from pho@holm.cc) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id E06921DD for ; Fri, 23 Sep 2016 14:05:14 +0000 (UTC) (envelope-from pho@holm.cc) Received: by mailman.ysv.freebsd.org (Postfix) id DC6FCBDC95A; Fri, 23 Sep 2016 14:05:14 +0000 (UTC) Delivered-To: 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 DC213BDC958 for ; Fri, 23 Sep 2016 14:05:14 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) (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 BBFFD1DB; Fri, 23 Sep 2016 14:05:13 +0000 (UTC) (envelope-from pho@holm.cc) Received: from x2.osted.lan (87-58-223-204-dynamic.dk.customer.tdc.net [87.58.223.204]) by relay01.pair.com (Postfix) with ESMTP id 1C53ED00BAF; Fri, 23 Sep 2016 10:05:07 -0400 (EDT) Received: from x2.osted.lan (localhost [127.0.0.1]) by x2.osted.lan (8.14.9/8.14.9) with ESMTP id u8NE54c6084922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Sep 2016 16:05:04 +0200 (CEST) (envelope-from pho@x2.osted.lan) Received: (from pho@localhost) by x2.osted.lan (8.14.9/8.14.9/Submit) id u8NE543O084921; Fri, 23 Sep 2016 16:05:04 +0200 (CEST) (envelope-from pho) Date: Fri, 23 Sep 2016 16:05:04 +0200 From: Peter Holm To: Lawrence Stewart Cc: net@freebsd.org Subject: Re: panic: SACK scoreboard must not be empty Message-ID: <20160923140504.GA84225@x2.osted.lan> References: <20150415110401.GA26326@x2.osted.lan> <5536FD31.40000@freebsd.org> <20150422091958.GA81930@x2.osted.lan> <5538219C.7090600@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5538219C.7090600@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 14:05:15 -0000 On Thu, Apr 23, 2015 at 08:33:00AM +1000, Lawrence Stewart wrote: > On 04/22/15 19:19, Peter Holm wrote: > > On Wed, Apr 22, 2015 at 11:45:21AM +1000, Lawrence Stewart wrote: > >> Hi Peter, > >> > >> On 04/15/15 21:04, Peter Holm wrote: > >>> Seen during i386 stress tests. > >>> > >>> db_trace_self_wrapper(c11e20fc,0,c11b79d4,1eb,e47578e0,...) at db_trace_self_wrapper+0x2a/frame 0xe47578b0 > >>> kdb_backtrace(c139e637,2,c120851d,e4757984,e4757940,...) at kdb_backtrace+0x2d/frame 0xe4757918 > >>> vpanic(c155b86a,100,c120851d,e4757984,e4757984,...) at vpanic+0x11d/frame 0xe4757954 > >>> kassert_panic(c120851d,0,8,164,16,...) at kassert_panic+0xe6/frame 0xe4757978 > >>> tcp_sack_doack(e047d900,e4757a48,e9eeab30,5f8,c15a9298,...) at tcp_sack_doack+0x405/frame 0xe47579f0 > >>> tcp_do_segment(df801720,e047d900,40,0,0,...) at tcp_do_segment+0x21c2/frame 0xe4757aa0 > >>> tcp_input(e4757bec,e4757be8,6,0,e4757be8,...) at tcp_input+0xfbc/frame 0xe4757ba0 > >>> ip_input(e1cb5800,0,c11f6228,2f0,45,...) at ip_input+0x17c/frame 0xe4757c0c > >>> swi_net(c1c25880,c11d6fed,54f,8f6da840,c8a209c8,...) at swi_net+0x1a3/frame 0xe4757c4c > >>> intr_event_execute_handlers(c156a310,c8a20980,c11d6fed,54f,0,...) at intr_event_execute_handlers+0xdb/frame 0xe4757c74 > >>> ithread_loop(c88d4f50,e4757ce8,c11d6d7c,3dc,0,...) at ithread_loop+0x87/frame 0xe4757cac > >>> fork_exit(c0b2c9d0,c88d4f50,e4757ce8) at fork_exit+0x7e/frame 0xe4757cd4 > >>> fork_trampoline() at fork_trampoline+0x8/frame 0xe4757cd4 > >>> > >>> Details: > >>> https://people.freebsd.org/~pho/stress/log/kostik794.txt > >>> > >> > >> >From the looks of the log, you don't have a core? > >> > > > > Sure, I have. > > https://people.freebsd.org/~pho/kernel+vmcore.792.txz > > > > Oh, great. For some reason I thought I saw a filesystem full message > related to capturing the dump in the log, but it was just my brain > playing tricks on me :) > > I'll take a look at this panic. Thanks for the report and crash dump. > > Cheers, > Lawrence Lawrence, I can reproduce this on a i386 kernel, without too much trouble. It is probably worth noting that the test box is out of VM: vm_cnt.v_free_count: 2. Latest panic: https://people.freebsd.org/~pho/stress/log/nfs9-2.txt http://people.freebsd.org/~pho/kernel+vmcore.959.txz -- Peter From owner-freebsd-net@freebsd.org Fri Sep 23 17:21:51 2016 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 91DFEBE80EB for ; Fri, 23 Sep 2016 17:21:51 +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 mx1.freebsd.org (Postfix) with ESMTPS id 81615C11 for ; Fri, 23 Sep 2016 17:21:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8NHLpWp075156 for ; Fri, 23 Sep 2016 17:21:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration Date: Fri, 23 Sep 2016 17:21:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: martin.larsson2@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? 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.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 17:21:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 martin.larsson2@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.larsson2@gmail.com --- Comment #1 from martin.larsson2@gmail.com --- totally agree, having ipsec but not with nat-t support is confusing. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Sep 23 17:59:13 2016 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 F0FE8BE6011 for ; Fri, 23 Sep 2016 17:59:13 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 8747175C for ; Fri, 23 Sep 2016 17:59:13 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id b184so3934274wma.3 for ; Fri, 23 Sep 2016 10:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=FJne38Bhq32l4emy71aPCw6XDHykPa5QdXcMDr2HFh0=; b=owh4a0tPr9z4YogEhj8oMnW2lao59bQGv0IjiOp9G0WKtMCLo6sZHzzq4oEQenHZAK DbNK/BjWun262rsQO7Lr/jKxk/uIvL048ci7Deu98XkFKs2c6s15WwG4wX8EwgtZ3b9i +BHUNkt3NJ8oBcYOjBqx5YCwEjjz+H90VHegn35EbWXs9HLPJsQcT1yPgtGCrO2BwPvU WFbMy6Hl1fz3Z2dk/OTtezZrBOteZJD/73xaVymCZkYfpcXZ8zZdfqzmovcCzWiYBUC5 iOFXXpYDQ7/wiEhT32F/hF9F+0ooOeEzfvUslzuhZsuORYhOB0+tGX6ctX7vrbTimPzu nI7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=FJne38Bhq32l4emy71aPCw6XDHykPa5QdXcMDr2HFh0=; b=JwR4OcJDbnTB8Xi+EjDyl0Rxs7fiyV7zqQ0ABvsRvf37w6aKGYZFbwtXJ+CrYbeqTs j09xoO8iOuCf6OcUAz0DfZ/upsEsOPNd3PZnJ12en4ZpG2l0TtKjzgIyfB9aEmkfwROi mWJDWQpwx97m5dd8hd8yQ3JC9yNzyJPKPwwLvaJCO0ne/Ak8K3R1b17jh+aizNIyrCyy A1Rz3PAwoK33/Wasgahz1zB3N3HyycJSEU7K44D3Br/37K+vrvYmE+2k7JeGjYMK6ZNG LAw4O8HtAF2RNrCDXlVWCZ0/l+vINQynT21gfWvRmDoeyM4mem1ESWAahValnK8eN9X/ 9yag== X-Gm-Message-State: AA6/9RmFozU8+AhUlUQ2BD/tPNLMfYkt4r7pG465zYE4fpzvNSEYZv3xhjFN64KXjDvo+w== X-Received: by 10.194.13.4 with SMTP id d4mr8253200wjc.218.1474653551746; Fri, 23 Sep 2016 10:59:11 -0700 (PDT) Received: from macbook-air-de-benjamin-1.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id bw9sm8313112wjc.33.2016.09.23.10.59.10 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 23 Sep 2016 10:59:11 -0700 (PDT) From: Ben RUBSON Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: netstat counts input traffic twice Message-Id: <94953762-4397-476D-AD61-A39914F27938@gmail.com> Date: Fri, 23 Sep 2016 19:59:09 +0200 To: FreeBSD Net Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 17:59:14 -0000 Hello, I found a strange issue where input traffic is counted twice, sometimes more. How to reproduce : dst# netstat -b -I mlxen1 Name Mtu Network Ipkts Ibytes Opkts Obytes mlxen 9000 223135371 2297323715986 242534891 1594979072449 mlxen - 192.168.0.0/1 140330886 1143518393245 239792545 1583789250111 dst# sysctl hw.mlxen1.stat.rx_bytes hw.mlxen1.stat.rx_bytes: 1151840666259 dst# iperf -s src# iperf -c dst -i 1 -t 10 -n 1G [ ID] Interval Transfer Bandwidth [ 3] 0.0- 0.3 sec 1.00 GBytes 33.0 Gbits/sec dst# netstat -b -I mlxen1 Name Mtu Network Ipkts Ibytes Opkts Obytes mlxen 9000 223257341 2299482904332 242578378 1594982116541 mlxen - 192.168.0.0/1 140378866 1144594630061 239836031 1583791511391 dst# sysctl hw.mlxen1.stat.rx_bytes hw.mlxen1.stat.rx_bytes: 1152922946009 Results : iperf on dst gives good results : dst# iperf -s [ ID] Interval Transfer Bandwidth [ 3] 0.0- 0.3 sec 1.00 GBytes 33.0 Gbits/sec hw.mlxen1.stat.rx_bytes also gives good results : 1152922946009 - 1151840666259 = 1GG However, netstat : 2299482904332 - 2297323715986 = 2GB (!) 1144594630061 - 1143518393245 = 1GB Strangely enough input packets are counted twice for the "link" interface. Why ? Is there a bug somewhere ? Of course looking at the real time results with netstat -w 1 gives the same uncorrect results. As well as with systat -ifstat. iftop (which I do not like so much because it sometimes hangs the traffic) seems to give good results however. I tested this on 3 similar servers, in all possible ways. Every time I get these strange results. This behaviour of course totally brakes reporting tools based on netstat. My 2 systems : # uname -r 11.0-RC3 # uptime 7:40p.m. up 47 mins, 1 users, load averages: 0.00, 0.00, 0.00 # mst status MST devices: ------------ pci0:133:0:0 - MT27500 Family [ConnectX-3] # flint -d pci0:133:0:0 q Image type: FS2 FW Version: 2.36.5000 FW Release Date: 26.1.2016 Product Version: 02.36.50.00 Rom Info: type=PXE version=3.4.718 devid=4099 Device ID: 4099 PSID: MT_1090110023 Thank you very much ! Ben From owner-freebsd-net@freebsd.org Fri Sep 23 18:45:26 2016 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 ABC02BE777C for ; Fri, 23 Sep 2016 18:45:26 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4036A2D7 for ; Fri, 23 Sep 2016 18:45:25 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u8NIjDoW007705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 23 Sep 2016 20:45:14 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u8NIj4C5004914 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 24 Sep 2016 01:45:04 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: netstat counts input traffic twice To: freebsd-net@freebsd.org References: <94953762-4397-476D-AD61-A39914F27938@gmail.com> From: Eugene Grosbein Message-ID: <57E5782B.9050200@grosbein.net> Date: Sat, 24 Sep 2016 01:44:59 +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: <94953762-4397-476D-AD61-A39914F27938@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 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 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 18:45:26 -0000 24.09.2016 0:59, Ben RUBSON пишет: > Hello, > > I found a strange issue where input traffic is counted twice, > sometimes more. Generally, this points to accounting bugs in the network device driver. From owner-freebsd-net@freebsd.org Fri Sep 23 18:51:00 2016 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 11EEEBE78EA for ; Fri, 23 Sep 2016 18:51:00 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 A3A326B7 for ; Fri, 23 Sep 2016 18:50:59 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id w84so48142623wmg.1 for ; Fri, 23 Sep 2016 11:50:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=jBZ4sIDxrt+r/hCasvbip7yLeTV6MLpPFWnuLeygPTU=; b=KToYwVtV6XqqGtlET0OuwL08ek8PU5omejg4EUbAJWUiTchjE85OEyrCPuW6Y08moi K4pI5/ez92EolFdrftM6uQd3Gd3KI7NvYWEdfo4ZYVzqN5ZQk0tem2VN5+HV/P2qNfSB 1frJNRKs9Hwox2B0q5At0NW9CBXjVTzuZ8L9VWeHjyYt3aF7HfXQ1EaJUpNvZPaeolm/ bUdME/wpTH+4KBNdXb49XXMzEWLEE6naMj1FbE35HraeQ/R4pJi0DW1nhzFZNR/0HZLx NLLWJ2XpUwtGmuSFOP+8nY/d5LtAnpVA9cpoaM+28cUV1RyqAukQyJksWE02I6pgjEDT YZTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=jBZ4sIDxrt+r/hCasvbip7yLeTV6MLpPFWnuLeygPTU=; b=k7y81/+z93C9ofwoci3VDJe/x/9DgE+dI3CnJ4B+lLXdhjKwgAdY3r0HHzzqaCy+Hs lAs8ZKVB25dfqiTeV9wn+373TemxxAvMdLEoYauCXctgrANw+Y8wFu/qLFV/Uys/kurO ujcmUX2Oq73yBTjrwNICf9bkJY3o/zh/8UURBYelHiNo/2+jJMx6R1BSeTCywn68d0Kw icKvr/BsvNslflrxDTSzOdWnSdwHJt/0JrnZwLpkqvXpca3mb5+Ou9mHDIgsEXKwdnbG GiMB1V45Rs+qC4rssNxYRx9K7kEH6QcjFb1exu5Po18AvsPBmiISzcZnMar3B/VNsJDD 68Zw== X-Gm-Message-State: AA6/9Rngw4ymyEUhU76CX00odekyfAPPuoIvG96F9yc5V5LUMsX13sZg2El+zuKqoJbhAQ== X-Received: by 10.28.35.65 with SMTP id j62mr3967160wmj.33.1474656657168; Fri, 23 Sep 2016 11:50:57 -0700 (PDT) Received: from macbook-air-de-benjamin-1.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id ab9sm8515598wjc.7.2016.09.23.11.50.56 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 23 Sep 2016 11:50:56 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: netstat counts input traffic twice From: Ben RUBSON In-Reply-To: <57E5782B.9050200@grosbein.net> Date: Fri, 23 Sep 2016 20:50:55 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <76C24E1F-BBF3-4F86-A879-8F9A8F7C48F2@gmail.com> References: <94953762-4397-476D-AD61-A39914F27938@gmail.com> <57E5782B.9050200@grosbein.net> To: FreeBSD Net X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 18:51:00 -0000 > On 23 Sep 2016, at 20:44, Eugene Grosbein wrote: >=20 > 24.09.2016 0:59, Ben RUBSON =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Hello, >>=20 >> I found a strange issue where input traffic is counted twice, >> sometimes more. >=20 > Generally, this points to accounting bugs in the network device = driver. Thank you for your feedback Eugene. hw.mlxen1.stat.rx_bytes (the Mellanox sysctl) returns good statistics. However it does not mean there is not a bug somewhere else in the driver, you're right. I then put all the NIC info in my previous mail so that Mellanox team may help, and of course I would be glad to help.= From owner-freebsd-net@freebsd.org Fri Sep 23 19:27:50 2016 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 53D02BE6848 for ; Fri, 23 Sep 2016 19:27:50 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 DC5C3F8B for ; Fri, 23 Sep 2016 19:27:49 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id b130so47178965wmc.0 for ; Fri, 23 Sep 2016 12:27:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=NhOsr0Tms/iugYGp9vsvIH4pygYb6q9KhNBJvUJMQY4=; b=vQZuH4Zxj4r3L1j/GKz0Qg3iMmupSVMIg0fCbw+OzcVZO9OQ/7v0SNHe9Tc18NnyNE yIT/UPgvmyeI3PUk3m+o6gXSqyIW3TkplEPQsG48ps4iLHQdEE6OkDq6RC2O1EXDRnZm QyStgjfK/dk2NYs6mgfQ9rYj5Lvr+AqeyDaMLSxEYaZvG/ruD+KhLyq7k6YZ0e/R1vHO vm92fdL+sEA0PfU3rw03h/KlsT41DEe8q0QaAPnlbdZYSrYq13elO295QbgD/wO7NfDx qFmadmxg59xGc3FpCK4erBw/80xAEcHp9k0awtbvNg0+ZDJpwfeJQS5HnQPcVy261PQA pKyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=NhOsr0Tms/iugYGp9vsvIH4pygYb6q9KhNBJvUJMQY4=; b=jdm6OCpN+cYYg1zYcohbeArs+cBgjgifgq7mT52VjtkirhYTJWvmaWmIaapt5K+Tx0 ClZdtujkDSfYWY5r4L2ptTfGXkKpPkqC/G1UfwUJGcEkM4Q7Dy2pk2dDvs4JD++PU3qr Er7Qb/RfHNOp4PojWs0HYRDgRoMrtISAeCI+h3abB9o56JiJOcwsTkdPTQBvDFrIR64o oNwMWQLCR5DLjHunrkdWWluoXD/RP8ZgExb9LHOTMJ3NYhoXvq1+zVpvextsJFaV2kph bHHyp916f5XUpSDBLOgDExTUKRGc+w2F8uQiUs11X7i+CUQOWAgn7kMVsL54wAwtR1UJ N2Fg== X-Gm-Message-State: AA6/9Rk5v9xYHqEG6G4M3P07gSDkov1SruqUuHpPXEuFU4kmd6n497vGZXeFeQg0J4NLTQ== X-Received: by 10.28.13.66 with SMTP id 63mr4025892wmn.113.1474658868234; Fri, 23 Sep 2016 12:27:48 -0700 (PDT) Received: from macbook-air-de-benjamin-1.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id w203sm4526891wmw.7.2016.09.23.12.27.47 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 23 Sep 2016 12:27:47 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: netstat counts input traffic twice From: Ben RUBSON In-Reply-To: <94953762-4397-476D-AD61-A39914F27938@gmail.com> Date: Fri, 23 Sep 2016 21:27:46 +0200 Content-Transfer-Encoding: 7bit Message-Id: <2D30DE7E-2BA9-4554-83EB-B2F197355AD4@gmail.com> References: <94953762-4397-476D-AD61-A39914F27938@gmail.com> To: FreeBSD Net X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 19:27:50 -0000 > On 23 Sep 2016, at 19:59, Ben RUBSON wrote: > > Hello, > > I found a strange issue where input traffic is counted twice, > sometimes more. As a very disgusting & temporary workaround, I did the following, so that statistics are made on the networks, not on the links : --- usr.bin/netstat/if.c.ori 2016-08-12 02:08:29.000000000 +0200 +++ usr.bin/netstat/if.c 2016-09-23 21:20:03.000000000 +0200 @@ -513,19 +513,19 @@ /* * Obtain stats for interface(s). */ static void fill_iftot(struct iftot *st) { struct ifaddrs *ifap, *ifa; bool found = false; if (getifaddrs(&ifap) != 0) xo_err(EX_OSERR, "getifaddrs"); bzero(st, sizeof(*st)); for (ifa = ifap; ifa; ifa = ifa->ifa_next) { - if (ifa->ifa_addr->sa_family != AF_LINK) + if (ifa->ifa_addr->sa_family != AF_INET) continue; if (interface) { if (strcmp(ifa->ifa_name, interface) == 0)