From owner-freebsd-net@freebsd.org Sun Oct 8 00:17:08 2017 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 364D0E45AC6 for ; Sun, 8 Oct 2017 00:17:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C2ABF843DB for ; Sun, 8 Oct 2017 00:17:07 +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 v980H7uT097756 for ; Sun, 8 Oct 2017 00:17:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 222774] 'ifconfig bnxt0' command trying to load if_bnxt.ko driver if not loaded Date: Sun, 08 Oct 2017 00:17:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: eugen@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to bug_status resolution 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, 08 Oct 2017 00:17:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222774 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org Assignee|freebsd-net@FreeBSD.org |eugen@freebsd.org Status|New |Closed Resolution|--- |Not A Bug --- Comment #1 from Eugene Grosbein --- This behaviour is expected and documented in the ifconfig(8) manual page: If the network interface driver is not present in the kernel then ifconfig will attempt to load it. The -n flag disables this behavior. Please use forums or mailing lists to ask such questions and leave Bugzilla= is for problem reporting. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 8 00:21:01 2017 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 DDC3EE45C31 for ; Sun, 8 Oct 2017 00:21:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F37DB7 for ; Sun, 8 Oct 2017 00:21:01 +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 v980L1vF005580 for ; Sun, 8 Oct 2017 00:21:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 222775] After re-enabling TSO, not seeing TSO pkts until restart iperf command Date: Sun, 08 Oct 2017 00:21:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: eugen@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to resolution 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: Sun, 08 Oct 2017 00:21:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222775 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Assignee|freebsd-net@FreeBSD.org |eugen@freebsd.org Resolution|--- |Not A Bug CC| |eugen@freebsd.org --- Comment #1 from Eugene Grosbein --- Bugzilla is not appropriate place to ask general questions, please direct t= his to forums or mailing list. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 8 13:28:30 2017 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 46BA7E3557B for ; Sun, 8 Oct 2017 13:28:30 +0000 (UTC) (envelope-from ben.rubson@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 B3C0E678AC for ; Sun, 8 Oct 2017 13:28:29 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id q132so17159133wmd.2 for ; Sun, 08 Oct 2017 06:28:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=qfSJFKrkZkl5mkyLofQCrtCIAmMAvbLFDwSoWrC4BT4=; b=Lghvf3C7MyqNU8mF02R+7vDoINZobEdGSGGpQHS8IscVs5Fnh6wtb23nXsudZqrwBB UYrsXvgSYIs3PvCIYym9Hvcsw7nFzurTGgCbRIbjMwSn8VgoK7EwlwLkEYeVfhzYU3b4 iGi/yITfHuO5jHFtTlMi++UqgCNOMSHSwOUrtnsBJMt5vDDm1SMowhDmHVw2gwUk1jQy JCsNXncK/I8Udzvcra0MaFnjOdKGeXtP/4Od8jx6iEggDUtgI+/TGLOrlHF3/LyIvyzJ n5EfOeu8mU+zIFsDv+hg385MHztsZtwVXo6utd4r07oeHBZrH0ITV4vHcnrwNepCNUlv JAbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=qfSJFKrkZkl5mkyLofQCrtCIAmMAvbLFDwSoWrC4BT4=; b=SZEZGmZhJ1XboBQUDNGzoEUYSFxrKaHKB/XyfDTghCM1ahQbYubJDfb1rmlYIPTOfx uWf6sUvdsa9RwefldwQwVs9S0c8sZ5RdwrnH99xNnfBqtVdQeL3r+TVxJ6PrP+kBfU4+ vEFlQF/oPBBIT/C+akKYFjE2sefR+fl9SxPNnApedRSehQfLYXFnQbSZS4NIqHdU8H6M aRh6FOwH3hBGF9curmzAd1zB/MK2E2tIavwo6RfItBtsuKYmIgwPzzquUDK3H5CEPHKb c8gEMgkDLzK7pS0vXaSvbo/sUxU+JjyAeyIh6AO7/EsQI8we6vfenmZRWuRx9TRk7mJ6 PBnQ== X-Gm-Message-State: AMCzsaVNb3cKn1XVq9PJUMXRTmLHSC5oUck86UV2znrFLB7U5gmL1+zR P7pI5I3/HdDIHyNex87BtBdFB7yvmXA= X-Google-Smtp-Source: AOwi7QAkD2JuuWkqk1yx5gJUA52RR+a2RjkWWAnihdk7f4eqZM9mnjY9VgUED9eDvl2+HehQ9lR8MQ== X-Received: by 10.223.157.203 with SMTP id q11mr6121904wre.131.1507469307759; Sun, 08 Oct 2017 06:28:27 -0700 (PDT) Received: from bens-mac.home (LFbn-MAR-1-445-220.w2-15.abo.wanadoo.fr. [2.15.38.220]) by smtp.gmail.com with ESMTPSA id d27sm15998355wrd.67.2017.10.08.06.28.26 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 08 Oct 2017 06:28:27 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Dell SAS controller / mpr? From: Ben RUBSON In-Reply-To: Date: Sun, 8 Oct 2017 15:28:25 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Kevin Bowling , freebsd-net , Lee Brown 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: Sun, 08 Oct 2017 13:28:30 -0000 Sounds like 3008 has both IT & IR firmwares, as the 2008 has. I had a look in the past and sounded difficult to flash a Dell SAS adapter with a LSI firmware, well, not so easy. I however did not try it myself, so others may share their experience :) Ben > On 07 Oct 2017, at 22:48, Kevin Bowling = wrote: >=20 > A 3008 is an IT-mode card. I think the 3108 is an IR-mode only card. > I don't think dell does much to the firmwares, you can probably flash > them with Broadcom ones if needed. >=20 > On Fri, Oct 6, 2017 at 1:09 PM, Lee Brown wrote: >> Hi All, >>=20 >> I want to purchase a dell R330 system with a "SAS 12Gbps HBA External >> Controller", which I believe is this (pdf) >> = >> card, based on the LSI SAS 3008 controller, which seems to be = supported by >> the mpr driver. >>=20 >> Would anybody be so kind as to verify this looks right before I = purchase a >> brick! >>=20 >> Many thanks -- lee From owner-freebsd-net@freebsd.org Sun Oct 8 13:46:16 2017 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 6A3D3E361EA for ; Sun, 8 Oct 2017 13:46:16 +0000 (UTC) (envelope-from ben.rubson@gmail.com) 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 CBF366BEBC for ; Sun, 8 Oct 2017 13:46:15 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id q124so16493874wmb.0 for ; Sun, 08 Oct 2017 06:46:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=82PTKi+dhgDIc5TT3JiFmDCs9BMj5wROJhHOxLVLBT8=; b=r9AgCBB9Xv2iZccv0yWOdtgM0805mvDaDykQY/+kwI3jt/h2tksVSGeoJ5i6hS3jQB 1FG3AVuqepw/b6Pb9lx4C7RjQimY3amBRYZTGdz26/fEzQyHau++SbXBPYHPKTC9CQE4 ZMYUbRgA/UzwkTYGkT/x+O7/a79dIcp6giA+1Cbpnbd1QrorcjxFeCETaKNduEI9ArpI 1tXrXu+zsadZDe/ezuZc17QVjRpsREyOirI7Kw5Wfjeczpnbeu2ZnI0BVB4bpK9YooY5 WfgZav0EofOIcrl6i64ucF5QAC3vL4hSe9epRddsDm72F0hY7HJutb59UH4+zl7ysoIR RPgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=82PTKi+dhgDIc5TT3JiFmDCs9BMj5wROJhHOxLVLBT8=; b=KI7+nc/HyP+kf/RRqhlWTXNeePEgDdGfejN6kMb+i/HbTr9V4Od/wlzceaUACqHiI5 /kyt1UJeHL2QMBB+etjHW/yoi/GKhbJR+LZMK5ZStFYaroGCUbEHOqVz03RNg3r/pU2A Ql6ZpTQEbBh+hYK/jwPwRiUdjCARPB6Pc2LJlkXTm6zInlP51Ft2B5xn04Tx9PkfMAMr k+vI6qFCXW7kQhy1faO/7kaoIDMZVVRFnuzCfuxtTlggLs5FNTXWVA7AE6QJc1FG1HjX SGsAlwNhXGCXmRUrd6uOWFYsU/Pvp+88IfjxwTWC5kk3PHatbX2EZihniWrINt1TyoK9 /iUg== X-Gm-Message-State: AMCzsaVUnrR+rl3n3PlsDY781sWX2H7NoRRuTazmmxqCfvWeid1G87Ub ZNjtCziUQQgBCeYXfZFK4wYfbdXlaA0= X-Google-Smtp-Source: AOwi7QBQhbWDAhy4Rkxc1UHc8zTcABFVYnYcKak1fLMDAWM+cB9LkmDiVndjBW4v6boBGttU6ogwtQ== X-Received: by 10.28.211.66 with SMTP id k63mr5697403wmg.33.1507470373998; Sun, 08 Oct 2017 06:46:13 -0700 (PDT) Received: from bens-mac.home (LFbn-MAR-1-445-220.w2-15.abo.wanadoo.fr. [2.15.38.220]) by smtp.gmail.com with ESMTPSA id r21sm4700543wmd.26.2017.10.08.06.46.13 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 08 Oct 2017 06:46:13 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Dell SAS controller / mpr? From: Ben RUBSON In-Reply-To: Date: Sun, 8 Oct 2017 15:46:12 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <884736CE-6915-4722-A221-79F4264A92AA@gmail.com> References: <0CA0E6C0-FA9A-4BFE-9354-5D7F3886D4E0@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: Sun, 08 Oct 2017 13:46:16 -0000 > On 07 Oct 2017, at 21:11, Lee Brown wrote: >=20 > On Fri, Oct 6, 2017 at 1:45 PM, Ben RUBSON = wrote: >=20 >>> On 06 Oct 2017, at 22:09, Lee Brown wrote: >>>=20 >>> Hi All, >>>=20 >>> I want to purchase a dell R330 system with a "SAS 12Gbps HBA = External >>> Controller", which I believe is this (pdf) >>> > data-sheets/en/Documents/Dell-PowerEdge-12Gbps-SAS-HBA.pdf> >>> card, based on the LSI SAS 3008 controller, which seems to be = supported >> by >>> the mpr driver. >>>=20 >>> Would anybody be so kind as to verify this looks right before I = purchase >> a >>> brick! >>=20 >> Hi Lee, >>=20 >> The SAS3008 is supported yes. >> Not sure however the Dell cards have an IT firmware available, >> or can receive the (last) IT LSI firmware. >>=20 > That's always my concern with Dell hardware. >=20 > So this SAS 9300-414E HBA > = > would be a better choice then? For sure you would not be concerned by potential firmware update = limitations... One thread with some info you may find useful : https://lists.freebsd.org/pipermail/freebsd-fs/2016-August/023786.html Which continues here : = https://lists.freebsd.org/pipermail/freebsd-fs/2016-September/023897.html And here : https://lists.freebsd.org/pipermail/freebsd-fs/2016-October/023998.html And finally : https://lists.freebsd.org/pipermail/freebsd-fs/2017-January/024276.html Ben From owner-freebsd-net@freebsd.org Sun Oct 8 14:13:13 2017 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 048BEE36DA6 for ; Sun, 8 Oct 2017 14:13:13 +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 A9E7A725C1 for ; Sun, 8 Oct 2017 14:13:12 +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 v98EDCHx073150 for ; Sun, 8 Oct 2017 14:13:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Sun, 08 Oct 2017 14:13:12 +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-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mops@punkt.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: Sun, 08 Oct 2017 14:13:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #23 from punkt.de Hosting Team --- Hey guys, it hit us again in production. Saturday night, 4am. Sorry - I missed that DTrace diagnose, but I can add two things at least: We are using igb(4) interfaces in that machine, not ix(4), so it seems not = to be interface related. Doesn't come as a big surprise to me, because that wo= uld have been a gross layer violation. Again: the host system is communicating = just fine! I did a `netstat -m` while the bridge was wedged as suggested by gnn. Doesn= 't look suspicious at all to me, but then I'm not a kernel developer. Please s= ee attachment. What I am going to do now, probably: Set up an isolated test environment. Fire up some dozen jails or so. Generate artificial traffic through the bridge IF. A gigabit sustained bandwidth ... Wait for the bug to be triggered. Need to talk to my colleagues, tomorrow, but this will probably be our cour= se of action. I can offer ssh access to that isolated system to anyone who requests it! Kind regards Patrick --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 8 14:14:01 2017 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 96956E36E24 for ; Sun, 8 Oct 2017 14:14:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A334672959 for ; Sun, 8 Oct 2017 14:14:00 +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 v98EDxXU074351 for ; Sun, 8 Oct 2017 14:14:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Sun, 08 Oct 2017 14:13:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mops@punkt.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: attachments.created 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, 08 Oct 2017 14:14:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #24 from punkt.de Hosting Team --- Created attachment 187001 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187001&action= =3Dedit `netstat -m` output while the bridge is in wedged state --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 8 18:01:46 2017 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 D26A3E3BFED for ; Sun, 8 Oct 2017 18:01: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 0926E63482 for ; Sun, 8 Oct 2017 18:01:45 +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 v98I1jVr059261 for ; Sun, 8 Oct 2017 18:01:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 152141] [vlan] [patch] encapsulate vlan in ng_ether before output to if Date: Sun, 08 Oct 2017 18:01:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rozhuk.im@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: 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: Sun, 08 Oct 2017 18:01:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D152141 rozhuk.im@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rozhuk.im@gmail.com Resolution|--- |Overcome By Events Status|In Progress |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 8 18:03:09 2017 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 E9155E3C082 for ; Sun, 8 Oct 2017 18:03:09 +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 8629E63901 for ; Sun, 8 Oct 2017 18:03:09 +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 v98I39Op063573 for ; Sun, 8 Oct 2017 18:03:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 165296] [vlan] [patch] Fix EVL_APPLY_VLID, update EVL_APPLY_PRI macro Date: Sun, 08 Oct 2017 18:03:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rozhuk.im@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: 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: Sun, 08 Oct 2017 18:03:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D165296 rozhuk.im@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rozhuk.im@gmail.com Resolution|--- |Feedback Timeout Status|In Progress |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 8 21:14:47 2017 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 05BC6E403E4 for ; Sun, 8 Oct 2017 21:14:47 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::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 64E2D6D4A9 for ; Sun, 8 Oct 2017 21:14:46 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x236.google.com with SMTP id g18so10867109itg.5 for ; Sun, 08 Oct 2017 14:14:46 -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:cc; bh=5mc+FQRPduOxeeI0KdrG8XxI5tI9YtHjFrhvp2Y1RgI=; b=VDchWlNlI28BVew+r7SvwU8/H0Dtcj0kc5/I8TqoC4DQq7OqTzy9UcRQ40ZBUiWHos cx0Lonigowf1NNLBeHjlbr4nJnhRmv7ICLLCtdPAUDmOrYtHds+KpPCKYpMJKixIETIZ e7UG6EIeiH8mMFUC86IhCcpYaWo3AMcgqKDlnFui62KF7WsAjD2guwjpWi5tJa2zjiYY vXLpGLnklMs0YFtWe5LxSwD4DqmCr6OPqP8n3Bm00ZPkXBBASGEG/SrQlk8zG8XT9cE0 OpzkqxFe6axRPPfi6nQXFFU7AQMnMqQafN0kzbfaN75qpeLbVPEhUSL/5ilJqYjVFXsO zOZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc; bh=5mc+FQRPduOxeeI0KdrG8XxI5tI9YtHjFrhvp2Y1RgI=; b=GNoAmIVKFR6a15iE8bMRIDpNKU2esoFrlOMxo6hbUhmtLZwGsxuv50BYwQ/AGxVzN4 cnqX7bqwS0X2EkSrtfCChNR986v5OnF9aAbXx+52EGoL2nT+UMfvZM/bo8FCjRBdpVyu wYE9JH+Zglt0JIUM7TmZD47NgdT1XjOEMbpyn5TShhBdRG/eSOkHXK0KhuaUZQAUS/fm aX1RLm1H5wP97GknYfPw6x899rA1qJScLXaJKfNsFyXlIlMzNguIOB24+l38MvQ3q1b2 n8IV32K29tcmBrqCUVy5R08WCXCyNPGB9t8RSvMezefPcSmeuezU2hKl0l/bT5nFkQFg MFzQ== X-Gm-Message-State: AMCzsaVzDHyXNCrJRW5g6OFEqohz0sDp3ri2mQkvO/ksmmyrlxF+/6YM uJi8fgtnjI6TE0OewPSiL+GTBGvWwC/TYXzxMn41vA== X-Google-Smtp-Source: AOwi7QDbAwKFwVrVCoJdbKX/rC64sv046zm3BfKyFfGRitBRYrtSMAzkXXN8ypsQwF4HxHfSuEhTEgA66dV1Ya75Jco= X-Received: by 10.36.0.77 with SMTP id 74mr11194098ita.67.1507497284833; Sun, 08 Oct 2017 14:14:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.32.146 with HTTP; Sun, 8 Oct 2017 14:14:44 -0700 (PDT) In-Reply-To: <884736CE-6915-4722-A221-79F4264A92AA@gmail.com> References: <0CA0E6C0-FA9A-4BFE-9354-5D7F3886D4E0@gmail.com> <884736CE-6915-4722-A221-79F4264A92AA@gmail.com> From: Lee Brown Date: Sun, 8 Oct 2017 14:14:44 -0700 Message-ID: Subject: Re: Dell SAS controller / mpr? 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, 08 Oct 2017 21:14:47 -0000 On Sun, Oct 8, 2017 at 6:46 AM, Ben RUBSON wrote: > > > On 07 Oct 2017, at 21:11, Lee Brown wrote: > > > > On Fri, Oct 6, 2017 at 1:45 PM, Ben RUBSON wrote: > > > >>> On 06 Oct 2017, at 22:09, Lee Brown wrote: > >>> > >>> Hi All, > >>> > >>> I want to purchase a dell R330 system with a "SAS 12Gbps HBA External > >>> Controller", which I believe is this (pdf) > >>> >> data-sheets/en/Documents/Dell-PowerEdge-12Gbps-SAS-HBA.pdf> > >>> card, based on the LSI SAS 3008 controller, which seems to be supported > >> by > >>> the mpr driver. > >>> > >>> Would anybody be so kind as to verify this looks right before I > purchase > >> a > >>> brick! > >> > >> Hi Lee, > >> > >> The SAS3008 is supported yes. > >> Not sure however the Dell cards have an IT firmware available, > >> or can receive the (last) IT LSI firmware. > >> > > That's always my concern with Dell hardware. > > > > So this SAS 9300-414E HBA > > adapters/sas-9300-4i4e> > > would be a better choice then? > > For sure you would not be concerned by potential firmware update > limitations... > > One thread with some info you may find useful : > https://lists.freebsd.org/pipermail/freebsd-fs/2016-August/023786.html > Which continues here : > https://lists.freebsd.org/pipermail/freebsd-fs/2016-September/023897.html > And here : > https://lists.freebsd.org/pipermail/freebsd-fs/2016-October/023998.html > And finally : > https://lists.freebsd.org/pipermail/freebsd-fs/2017-January/024276.html > > Ben > Thanks Ben, I had seen 2 of those, but that nails it for me then, I'll get the real card. Cheers -- lee From owner-freebsd-net@freebsd.org Mon Oct 9 01:10:25 2017 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 90375E44924 for ; Mon, 9 Oct 2017 01:10:25 +0000 (UTC) (envelope-from s-jepp@arcor.de) Received: from vsmx011.vodafonemail.xion.oxcs.net (vsmx011.vodafonemail.xion.oxcs.net [153.92.174.89]) (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 C434883869 for ; Mon, 9 Oct 2017 01:10:24 +0000 (UTC) (envelope-from s-jepp@arcor.de) Received: from vsmx003.vodafonemail.xion.oxcs.net (unknown [192.168.75.197]) by mta-5-out.mta.xion.oxcs.net (Postfix) with ESMTP id B1CEF3E5FB8; Mon, 9 Oct 2017 01:00:15 +0000 (UTC) Received: from ekqvw.com (unknown [186.179.111.191]) by mta-7-out.mta.xion.oxcs.net (Postfix) with ESMTPA id 48362300646; Mon, 9 Oct 2017 01:00:06 +0000 (UTC) Subject: =?utf-8?B?UmU6IHdvdyBjb29sIHBlb3BsZQ==?= To: "foicywau4085" , "freebsd-net" , "gilbert.caestecker1" From: "Elen Strouhal" Date: Mon, 9 Oct 2017 08:00:02 +0700 Message-ID: <0C87D247-7521-435D-A958-BBB17FF50FED@arcor.de> MIME-Version: 1.0 X-VADE-STATUS: LEGIT Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 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, 09 Oct 2017 01:10:25 -0000 SGV5LCANCg0KDQpJJ3ZlIHNhdGlzZmllZCBzdWNoIGEgdmVyeSBnb29kICBjb3VwbGUganVzdCBs YXRlbHkgIGFuZCAgd2FudGVkICB0byBzaGFyZSBhIGZldyAgb2YgdGhlaXIgdGhvdWdodHMgIGFs b25nLCAgdGhleSBhcmUgIGFjdHVhbGx5IGludGVyZXN0aW5nIGFuZCBzbyB1bnVzdWFsLCB0aGlz IGlzIGFjdHVhbGx5IHRoZSBsaW5rIGh0dHA6Ly93d3cuY29tcGFzc2Zvb2QucnUvZHJhbWF0aWMu cGhwPzdmN2UNCg0KU2VudCBmcm9tIG15IGlQaG9uZSwgRWxlbiBTdHJvdWhhbA0KDQoNCg0KRnJv bTogZm9pY3l3YXU0MDg1IFttYWlsdG86Zm9pY3l3YXU0MDg1QDFjYy5hdF0NClNlbnQ6IFN1bmRh eSwgT2N0b2JlciAwOCwgMjAxNyA4OjAwIFBNDQpUbzogYmFycmlzdGVyLWt1cnNrQHFpcC5ydQ0K U3ViamVjdDogVGhlIGZpcnN0IG1hdGUgbW9hbmVkLg0KDQpTb21lICBnYW1lcyBhcmUgdW5mb3J0 dW5hdGVseSBqdXN0IG5vdCB3aW5uYWJsZS4uLiBCb3RoIG90aGVyICB0aGVuICB0aGF0LCBmb3Jj ZSBzcGxpdHMgIGFuZCAgdGFrZSAgYmFzZSBiZWZvcmUgYW55b25lIHJlYWN0cy4gSU1PIGVhc2ll c3QgIHdheSB0byBoaXQgIGRpYW1vbmQgYmVjYXVzZSAgeW91IGRvbid0IHJlYWxseSBuZWVkIHlv dXIgIHRlYW0gdG8gZG8gIGFueXRoaW5nLiBPdGhlciB0aGVuIHRoYXQganVzdCBrZWVwIHdpbm5p bmcgbGFuZSBhbmQgZ2V0dGluZyBtYXAgcHJlc3N1cmUgYW5kIHlvdSdsbCBldmVudHVhbGx5ICBj bGltYiB3aGVuICBtYXRjaG1ha2luZyBkZWNpZGVzICB0byAgc3RvcCBiZWluZyAgYml0Y2h5Lg0K DQoNClNlbnQgZnJvbSBNYWlsIGZvciBXaW5kb3dzIDEw From owner-freebsd-net@freebsd.org Mon Oct 9 11:27:45 2017 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 E7079E2D778 for ; Mon, 9 Oct 2017 11:27:45 +0000 (UTC) (envelope-from bhargava.marreddy@broadcom.com) 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 541B63E6C for ; Mon, 9 Oct 2017 11:27:45 +0000 (UTC) (envelope-from bhargava.marreddy@broadcom.com) Received: by mail-wm0-x22a.google.com with SMTP id m72so21597426wmc.1 for ; Mon, 09 Oct 2017 04:27:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to; bh=vzs4pggSHk059BsuEbeVwtQyvw6j49fn2X6Mlw9Nblw=; b=sig4FoNVyNaBwvlHVS5OgBN/I3nSbrXSqdzvrhE9T4EVXgIYcUWyb55UNJIJgfCNwg rrzjFBllAiC5nLaqXR2QWK4WeHnABXGQl7q/5u6KwH4D+nf/xp5zm/8bLU/3+0TXhE6R b8QxdbcsvUNXHHdKjeWYhfGjZMb9sO6JEbozSUAfhPZyM4PWT3ZAhNtDUPDR0oclZ6kD qIYCAqTlK9gobFgoaNlfz+zi4Jx/BtUQpgGCvHritsiK2fIaqbd7URdKxMbAklrBcHoF tF4+vq8wViIjmLv5WO2DW6SVb7Cls0DI/8JsdP2E/Vo6/U5tBM4Odkg7vhqJNdjckgdG UEmA== X-Gm-Message-State: AMCzsaXleDoohT8/X5BYDewcNNyEZs4h1JWXYXTrfhVsjp1Nb44C0Kuy 393/+Jn+n54yDk3i0I9g+vov6C2JZsGfOP94a+AQeg== X-Google-Smtp-Source: AOwi7QCCRMR17EX/vFJ2rcuiONXxq8HmudukVAR/SPJjS1/w7mynsvLddpS1l9NR5yS6l8vHFnP53wZ7VMFtTZWpzxw= X-Received: by 10.28.134.18 with SMTP id i18mr9242494wmd.27.1507548463389; Mon, 09 Oct 2017 04:27:43 -0700 (PDT) From: Bhargava Chenna Marreddy MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdNA8Z4rChHJb1BhQw6ax/tVYRavnw== Date: Mon, 9 Oct 2017 16:57:42 +0530 Message-ID: Subject: After re-enabling TSO, not seeing TSO pkts until restart iperf command To: freebsd-net@freebsd.org 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, 09 Oct 2017 11:27:46 -0000 Can someone please confirm whether this is expected behavior? Why am I not able to see TSO pkts until I re-start iperf session? Steps to reproduce:- 1. Load if_bnxt (or any other NIC) driver and assign IP 2. start iperf TCP traffic 3. Capture Tx pkts (command: tcpdump -i bnxt0), I can see > 60K length pkts. 4. Disable tso (command: ifconfig bnxt0 -tso) 5. Capture Tx pkts (command: tcpdump -i bnxt0). Max pkt length seen is 1440 (non-tso pkts) 6. Enable TSO (command: ifconfig bnxt0 -tso) 7. Capture Tx pkts (command: tcpdump -i bnxt0). Max pkt length seen is still 1440 (I was expecting TSO pkts here). 8. Terminate iperf sessions and start again. Now, I can see TSO pkts. From owner-freebsd-net@freebsd.org Mon Oct 9 21:15:55 2017 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 D091DE3C39F for ; Mon, 9 Oct 2017 21:15: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 BEBB58046B for ; Mon, 9 Oct 2017 21:15: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 v99LFtTX033921 for ; Mon, 9 Oct 2017 21:15:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 222842] adding interface to bridge panics kernel Date: Mon, 09 Oct 2017 21:15:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: 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 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: Mon, 09 Oct 2017 21:15:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222842 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Oct 10 08:11:50 2017 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 396A1E2840B for ; Tue, 10 Oct 2017 08:11:50 +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 D0E8971D56 for ; Tue, 10 Oct 2017 08:11:49 +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 v9A8Bnf2077711 for ; Tue, 10 Oct 2017 08:11:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219703] System freeze when creating bridge over vlan over lagg over ixgbe Date: Tue, 10 Oct 2017 08:11:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: topical@gmx.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 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: Tue, 10 Oct 2017 08:11:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219703 topical changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Oct 10 17:19:00 2017 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 CDACFE37EEA for ; Tue, 10 Oct 2017 17:19:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC26B64C27 for ; Tue, 10 Oct 2017 17:19:00 +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 v9AHJ0pk098496 for ; Tue, 10 Oct 2017 17:19:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 222744] Issues with Intel EM(4) drivers and iflib updates working with netmap Date: Tue, 10 Oct 2017 17:19:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: shurd@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: shurd@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 10 Oct 2017 17:19:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222744 Stephen Hurd changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |shurd@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 11 06:08:17 2017 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 95A31E47A09 for ; Wed, 11 Oct 2017 06:08:17 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 590CF7FD9E for ; Wed, 11 Oct 2017 06:08:17 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 1B03716FCD; Wed, 11 Oct 2017 06:08:17 +0000 (UTC) Date: Wed, 11 Oct 2017 06:08:17 +0000 To: freebsd-net@freebsd.org From: Phabricator Reply-to: D12455+325+ee10052bad235453@reviews.freebsd.org Subject: [Differential] D12455: rss: Remove never defined UDP_IPV4_EX Message-ID: <24a5a2945b4dd3806929d26760e06c6b@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D12455: rss: Remove never defined UDP_IPV4_EX X-Herald-Rules: <81> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: MmY1ZDMzMDJmMTg5NjZkMmI4NGRlNWI5ZjlhIFndtVE= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_24a5a2945b4dd3806929d26760e06c6b" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 06:08:17 -0000 --b1_24a5a2945b4dd3806929d26760e06c6b Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: base64 VGhpcyByZXZpc2lvbiB3YXMgYXV0b21hdGljYWxseSB1cGRhdGVkIHRvIHJlZmxlY3QgdGhlIGNv bW1pdHRlZCBjaGFuZ2VzLgpDbG9zZWQgYnkgY29tbWl0IHJTMzI0NTE5OiByc3M6IFJlbW92ZSBu ZXZlciBkZWZpbmVkIFVEUF9JUFY0X0VYIChhdXRob3JlZCBieSBzZXBoZSwgY29tbWl0dGVkIGJ5 ICkuCgpDSEFOR0VEIFBSSU9SIFRPIENPTU1JVAogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9y Zy9EMTI0NTU/dnM9MzMzMDImaWQ9MzM4NzcjdG9jCgpSRVBPU0lUT1JZCiAgclMgRnJlZUJTRCBz cmMgcmVwb3NpdG9yeQoKQ0hBTkdFUyBTSU5DRSBMQVNUIFVQREFURQogIGh0dHBzOi8vcmV2aWV3 cy5mcmVlYnNkLm9yZy9EMTI0NTU/dnM9MzMzMDImaWQ9MzM4NzcKClJFVklTSU9OIERFVEFJTAog IGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9EMTI0NTUKCkFGRkVDVEVEIEZJTEVTCiAgaGVh ZC9zeXMvbmV0L3Jzc19jb25maWcuYwogIGhlYWQvc3lzL25ldC9yc3NfY29uZmlnLmgKCkNIQU5H RSBERVRBSUxTCgpkaWZmIC0tZ2l0IGEvaGVhZC9zeXMvbmV0L3Jzc19jb25maWcuaCBiL2hlYWQv c3lzL25ldC9yc3NfY29uZmlnLmgKLS0tIGEvaGVhZC9zeXMvbmV0L3Jzc19jb25maWcuaAorKysg Yi9oZWFkL3N5cy9uZXQvcnNzX2NvbmZpZy5oCkBAIC02Niw3ICs2Niw2IEBACiAjZGVmaW5lCVJT U19IQVNIVFlQRV9SU1NfSVBWNl9FWAkoMSA8PCA1KQkvKiBJUHY2IDItdHVwbGUgKyBleHQgaGRy cyAqLwogI2RlZmluZQlSU1NfSEFTSFRZUEVfUlNTX1RDUF9JUFY2X0VYCSgxIDw8IDYpCS8qIFRD UHY2IDQtdGlwbGUgKyBleHQgaGRycyAqLwogI2RlZmluZQlSU1NfSEFTSFRZUEVfUlNTX1VEUF9J UFY0CSgxIDw8IDcpCS8qIElQdjQgVURQIDQtdHVwbGUgKi8KLSNkZWZpbmUJUlNTX0hBU0hUWVBF X1JTU19VRFBfSVBWNF9FWAkoMSA8PCA4KQkvKiBJUHY0IFVEUCA0LXR1cGxlICsgZXh0IGhkcnMg Ki8KICNkZWZpbmUJUlNTX0hBU0hUWVBFX1JTU19VRFBfSVBWNgkoMSA8PCA5KQkvKiBJUHY2IFVE UCA0LXR1cGxlICovCiAjZGVmaW5lCVJTU19IQVNIVFlQRV9SU1NfVURQX0lQVjZfRVgJKDEgPDwg MTApCS8qIElQdjYgVURQIDQtdHVwbGUgKyBleHQgaGRycyAqLwogCmRpZmYgLS1naXQgYS9oZWFk L3N5cy9uZXQvcnNzX2NvbmZpZy5jIGIvaGVhZC9zeXMvbmV0L3Jzc19jb25maWcuYwotLS0gYS9o ZWFkL3N5cy9uZXQvcnNzX2NvbmZpZy5jCisrKyBiL2hlYWQvc3lzL25ldC9yc3NfY29uZmlnLmMK QEAgLTQ4OSw3ICs0ODksNiBAQAogCXwgICAgUlNTX0hBU0hUWVBFX1JTU19UQ1BfSVBWNl9FWAog I2lmIDAKIAl8ICAgIFJTU19IQVNIVFlQRV9SU1NfVURQX0lQVjQKLQl8ICAgIFJTU19IQVNIVFlQ RV9SU1NfVURQX0lQVjRfRVgKIAl8ICAgIFJTU19IQVNIVFlQRV9SU1NfVURQX0lQVjYKIAl8ICAg IFJTU19IQVNIVFlQRV9SU1NfVURQX0lQVjZfRVgKICNlbmRpZgoKCgpFTUFJTCBQUkVGRVJFTkNF UwogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9zZXR0aW5ncy9wYW5lbC9lbWFpbHByZWZl cmVuY2VzLwoKVG86IHNlcGhlcm9zYV9nbWFpbC5jb20sIGFkcmlhbiwgcndhdHNvbiwgZ2FsbGF0 aW4sIGZyZWVic2QtbmV0LWxpc3QKQ2M6IGFlCg== --b1_24a5a2945b4dd3806929d26760e06c6b Content-Type: text/x-patch; charset=utf-8; name="D12455.33877.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D12455.33877.patch" ZGlmZiAtLWdpdCBhL2hlYWQvc3lzL25ldC9yc3NfY29uZmlnLmggYi9oZWFkL3N5cy9uZXQvcnNz X2NvbmZpZy5oCi0tLSBhL2hlYWQvc3lzL25ldC9yc3NfY29uZmlnLmgKKysrIGIvaGVhZC9zeXMv bmV0L3Jzc19jb25maWcuaApAQCAtNjYsNyArNjYsNiBAQAogI2RlZmluZQlSU1NfSEFTSFRZUEVf UlNTX0lQVjZfRVgJKDEgPDwgNSkJLyogSVB2NiAyLXR1cGxlICsgZXh0IGhkcnMgKi8KICNkZWZp bmUJUlNTX0hBU0hUWVBFX1JTU19UQ1BfSVBWNl9FWAkoMSA8PCA2KQkvKiBUQ1B2NiA0LXRpcGxl ICsgZXh0IGhkcnMgKi8KICNkZWZpbmUJUlNTX0hBU0hUWVBFX1JTU19VRFBfSVBWNAkoMSA8PCA3 KQkvKiBJUHY0IFVEUCA0LXR1cGxlICovCi0jZGVmaW5lCVJTU19IQVNIVFlQRV9SU1NfVURQX0lQ VjRfRVgJKDEgPDwgOCkJLyogSVB2NCBVRFAgNC10dXBsZSArIGV4dCBoZHJzICovCiAjZGVmaW5l CVJTU19IQVNIVFlQRV9SU1NfVURQX0lQVjYJKDEgPDwgOSkJLyogSVB2NiBVRFAgNC10dXBsZSAq LwogI2RlZmluZQlSU1NfSEFTSFRZUEVfUlNTX1VEUF9JUFY2X0VYCSgxIDw8IDEwKQkvKiBJUHY2 IFVEUCA0LXR1cGxlICsgZXh0IGhkcnMgKi8KIApkaWZmIC0tZ2l0IGEvaGVhZC9zeXMvbmV0L3Jz c19jb25maWcuYyBiL2hlYWQvc3lzL25ldC9yc3NfY29uZmlnLmMKLS0tIGEvaGVhZC9zeXMvbmV0 L3Jzc19jb25maWcuYworKysgYi9oZWFkL3N5cy9uZXQvcnNzX2NvbmZpZy5jCkBAIC00ODksNyAr NDg5LDYgQEAKIAl8ICAgIFJTU19IQVNIVFlQRV9SU1NfVENQX0lQVjZfRVgKICNpZiAwCiAJfCAg ICBSU1NfSEFTSFRZUEVfUlNTX1VEUF9JUFY0Ci0JfCAgICBSU1NfSEFTSFRZUEVfUlNTX1VEUF9J UFY0X0VYCiAJfCAgICBSU1NfSEFTSFRZUEVfUlNTX1VEUF9JUFY2CiAJfCAgICBSU1NfSEFTSFRZ UEVfUlNTX1VEUF9JUFY2X0VYCiAjZW5kaWYKCg== --b1_24a5a2945b4dd3806929d26760e06c6b-- From owner-freebsd-net@freebsd.org Wed Oct 11 15:37:57 2017 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 263A6E2F58E for ; Wed, 11 Oct 2017 15:37:57 +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 14A6D6C53F for ; Wed, 11 Oct 2017 15:37:57 +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 v9BFbtC7001652 for ; Wed, 11 Oct 2017 15:37:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 197198] bxe driver failed to init NIC Date: Wed, 11 Oct 2017 15:37: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.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: andy@str.by 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, 11 Oct 2017 15:37:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197198 Andrey Bireta changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andy@str.by --- Comment #3 from Andrey Bireta --- Same here on 10.4 11.1 amd64 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 12 01:01:49 2017 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 4E589E3BAF9 for ; Thu, 12 Oct 2017 01:01:49 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (unknown [IPv6:2001:470:1f0f:3ad:bb:dcff:fe50:d900]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C7E683EAF; Thu, 12 Oct 2017 01:01:49 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-Type:MIME-Version:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=tFScLaGvBC5Inocojjg1sT+Xuall8FyGOQA2KBWsBD8=; b=euCGHKnh2yIE0DL5a6y6qyggpT mqvAvIyDmMdQEzAk0cBsNSW7DKxgPz1VTWivNoY1WQiKO9Vn77a5BZPb84Oo4AuCbEoa02xd5SeHV rINTcD07qnRXtHja5bZJD+ohwUjNkxo9bOEWB0XUdgJqJnzd1Mx6HdYFX67nLm/RyN+s=; Received: from [2602:304:cfaf:f750:b5ca:fa6e:c885:dd7f] (port=53672 helo=lrosenman.local) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e2Rsi-0004HW-7y; Wed, 11 Oct 2017 20:01:48 -0500 Date: Wed, 11 Oct 2017 20:01:47 -0500 From: Larry Rosenman To: freebsd-net@FreeBSD.org Cc: hrs@FreeBSD.org Subject: 6rd: when in Base FreeBSD? Message-ID: <20171012010147.pb3pzxm2naelaygj@lrosenman.local> Mail-Followup-To: freebsd-net@FreeBSD.org, hrs@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jykwfscpimh5pcab" Content-Disposition: inline User-Agent: NeoMutt/20170912 (1.9.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, 12 Oct 2017 01:01:49 -0000 --jykwfscpimh5pcab Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm currently using pfSense, and it has a working 6rd implementation, an= d I need 6rd as that's how ATT Fiber delivers IPv6.=20 Apparently for whatever reason, the pfSense guys can't/won't upstream or= release their 6rd patch. (see https://forum.pfsense.org/index.php?topic=3D137636.0) I note on the IPV6todo wiki page (https://wiki.freebsd.org/IPv6TODO) tha= t 6rd is=20 still a desired feature. =20 Is there anything I or the project can do to help here? (I'm willing to = guinea pig it or have the OpnSense guys test it).=20 Thanks! --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --jykwfscpimh5pcab Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFgBAABCgBKFiEEHjgknedhWzvJgwVzaXyZsatIp30FAlnevvssFIAAAAAAFQAO cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQGxlcmN0ci5vcmcACgkQaXyZsatIp33x OAf+KHokM0rOfAEtOtpJ6OHerwhees1DHHg4Xo8qFF52CT8GFWuU97GQQOPxYoQs AqSTG+cYe31bOAa2GSWedT7MP560R1QykZDCdNmLpavLN2+cg1ajSc9Oonbm7ExI iZ370x43lbNVlv6hcrz8ewhnzuL7g+skeHbpmclCifO2ULG7bTLr69qS0ajhvFkE ol/pHMKA4ToLHgCZYjeXe/LXG2Nztgfn+Z/6lvtXgSUDVpQZl210VCMyMvBrV1O/ LnN4R1oHzIymiUMFqOSg3EpyBXKVa4/nBeXKvsQsChs5t3OKt5uNMB5mGS5Mkve+ 2KI5vIUJuZ4rwrwTv2DLBgXKSg== =qZKW -----END PGP SIGNATURE----- --jykwfscpimh5pcab-- From owner-freebsd-net@freebsd.org Thu Oct 12 01:48:22 2017 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 6F223E3DCEF for ; Thu, 12 Oct 2017 01:48:22 +0000 (UTC) (envelope-from lists.br@gmail.com) 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 06676BFA; Thu, 12 Oct 2017 01:48:22 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id l68so9111997wmd.5; Wed, 11 Oct 2017 18:48:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=a4Jie8H+4WX3Egj6oH93nZTGeHQx9+nXDgGXkm9/d78=; b=UrEv2rOzEK2LCw/Y76bP6YJi1gzLPEd43F9pDQSCzAHd1SrWTabZ0fRZh6TgYy3kjN agGdvNJk2ewVt5Ehxa/dtFVKB8ieApjZf8vz3j01AUDZ4LIfUVNNO93dUOC8qH1RcFqn 9haqoSJrNatfxSv2G4oot2/mz5r8nJfTX0pcm1waLf4szLqUY6pVEPztFCwnLRnXVrjA U9lPENhyZC+iY9wuHs0Gd9CYEnQrFeFxRLPH+o12mtdg3WhJPSslO3lVHM9XPOr6lPup J0CWNONSs99JGBcYrRufKYNtTmNeYHb2bZ4lspXU9tUncaG1kcaT+ffYw8Ume1zX8B5n 8ZCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=a4Jie8H+4WX3Egj6oH93nZTGeHQx9+nXDgGXkm9/d78=; b=XWBubsndDGUZIofi4LXHkbBuRgM9L/6WVAkaxga8FPkzHc9gIH9/M9dUMsKzN307Gi oM6SuyK4R2bda/qi6+iYd5Pk4GMc6Jp1mAaz/jhrLAxDyoR3KM04nn+iATPSjBLMShwb pPM9RGLp84myycpqUdpD+k+WU66jsv8c47yebhUFEny+APmbK6vdKN9L+0Usf6JcHNA1 jezCMnaDGL5PJIhIkwa414XwgZ2/aKe2fZwYW3nNAoDzbx/zd5XsNt8wHAnAYT2r7qQx nRSpeedooRgurD0axqTOdxeNWA4LA4hosUpf0rGEDcMdRYwKvKzyNcU/jJ9WKVlu3hv/ 2HnA== X-Gm-Message-State: AMCzsaUUyVFg6Qpwt0e+WVEsQZKjvUkMrtXeNzEmPeRhDLfen+/Ut788 4tndz8GfQSAg9vZF1rchKK6TVmvisekAexXD4B0akA== X-Google-Smtp-Source: AOwi7QDndNEBCKAszpbtgOb6ErG1RThlRQHByvp4L3POTsm3n/iW4NfeMpyssiW9Wn3Ecw5Z8wbm3SHr21J+30sP99c= X-Received: by 10.80.213.14 with SMTP id u14mr935735edi.87.1507772899100; Wed, 11 Oct 2017 18:48:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.146.188 with HTTP; Wed, 11 Oct 2017 18:48:18 -0700 (PDT) In-Reply-To: <20171012010147.pb3pzxm2naelaygj@lrosenman.local> References: <20171012010147.pb3pzxm2naelaygj@lrosenman.local> From: Luiz Otavio O Souza Date: Wed, 11 Oct 2017 22:48:18 -0300 Message-ID: Subject: Re: 6rd: when in Base FreeBSD? To: FreeBSD Net , hrs@freebsd.org 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: Thu, 12 Oct 2017 01:48:22 -0000 On 11 October 2017 at 22:01, Larry Rosenman wrote: > Hi, > I'm currently using pfSense, and it has a working 6rd implementation, and I need 6rd > as that's how ATT Fiber delivers IPv6. > > Apparently for whatever reason, the pfSense guys can't/won't upstream or release their 6rd > patch. (see https://forum.pfsense.org/index.php?topic=137636.0) > pfSense will upstream the patches when they are ready (unless someone beat us). While the patches in pfSense are in a workable state, they are not yet well suited for FreeBSD. It is possible that hrs@ and others have newer patches too. Luiz From owner-freebsd-net@freebsd.org Thu Oct 12 01:54:20 2017 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 5DC66E3E328 for ; Thu, 12 Oct 2017 01:54:20 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 27A261158; Thu, 12 Oct 2017 01:54:20 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v9C1sAJc084780; Wed, 11 Oct 2017 18:54:14 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201710120154.v9C1sAJc084780@gw.catspoiler.org> Date: Wed, 11 Oct 2017 18:54:10 -0700 (PDT) From: Don Lewis Subject: Re: 6rd: when in Base FreeBSD? To: ler@lerctr.org cc: freebsd-net@FreeBSD.org, hrs@FreeBSD.org In-Reply-To: <20171012010147.pb3pzxm2naelaygj@lrosenman.local> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii 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, 12 Oct 2017 01:54:20 -0000 On 11 Oct, Larry Rosenman wrote: > Hi, > I'm currently using pfSense, and it has a working 6rd implementation, and I need 6rd > as that's how ATT Fiber delivers IPv6. > > Apparently for whatever reason, the pfSense guys can't/won't upstream or release their 6rd > patch. (see https://forum.pfsense.org/index.php?topic=137636.0) > > I note on the IPV6todo wiki page (https://wiki.freebsd.org/IPv6TODO) that 6rd is > still a desired feature. > > Is there anything I or the project can do to help here? (I'm willing to guinea pig it > or have the OpnSense guys test it). I'd like to see the patch mentioned go in, but in the meantime I'm using a gif interface to do this. From owner-freebsd-net@freebsd.org Thu Oct 12 01:57:36 2017 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 78091E3E626 for ; Thu, 12 Oct 2017 01:57:36 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (unknown [IPv6:2001:470:1f0f:3ad:bb:dcff:fe50:d900]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 524571317; Thu, 12 Oct 2017 01:57:35 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=6x8iwR0a9pT/aZHWWI+kjUlvJiDq8KcRkDMojR7SrD4=; b=ROTqE7Bbr7x0Kl+mAUUkEPV165 z/g0P54m+CC2VxpoVY9UWYrWICoSRWf7g3dIjw4QdZTuhWBqIb2hPMyyzvshVB5IAX6YBwoqri4yX vB2UJ8G2tlHJ6OtKHY1n750pBbUPecw6E5DLkijID/932kh/wadbpPPT45t0mzWKdc30=; Received: from [2602:304:cfaf:f750:b5ca:fa6e:c885:dd7f] (port=57182 helo=lrosenman.local) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e2Skh-0005fb-2H; Wed, 11 Oct 2017 20:57:35 -0500 Date: Wed, 11 Oct 2017 20:57:34 -0500 From: Larry Rosenman To: Don Lewis Cc: freebsd-net@FreeBSD.org, hrs@FreeBSD.org Subject: Re: 6rd: when in Base FreeBSD? Message-ID: <20171012015734.qnj2a3w4qnpbb4bc@lrosenman.local> Mail-Followup-To: Don Lewis , freebsd-net@FreeBSD.org, hrs@FreeBSD.org References: <20171012010147.pb3pzxm2naelaygj@lrosenman.local> <201710120154.v9C1sAJc084780@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yqgaryxorjz6lwth" Content-Disposition: inline In-Reply-To: <201710120154.v9C1sAJc084780@gw.catspoiler.org> User-Agent: NeoMutt/20170912 (1.9.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, 12 Oct 2017 01:57:36 -0000 --yqgaryxorjz6lwth Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 12, 2017 at 01:54:10AM +0000, Don Lewis wrote: > On 11 Oct, Larry Rosenman wrote: > > Hi, > > I'm currently using pfSense, and it has a working 6rd implementation= , and I need 6rd > > as that's how ATT Fiber delivers IPv6.=20 > >=20 > > Apparently for whatever reason, the pfSense guys can't/won't upstrea= m or release their 6rd > > patch. (see https://forum.pfsense.org/index.php?topic=3D137636.0) > >=20 > > I note on the IPV6todo wiki page (https://wiki.freebsd.org/IPv6TODO)= that 6rd is=20 > > still a desired feature. =20 > >=20 > > Is there anything I or the project can do to help here? (I'm willing= to guinea pig it > > or have the OpnSense guys test it).=20 >=20 >=20 > I'd like to see the patch mentioned go in, but in the meantime I'm using > a gif interface to do this. >=20 I wasn't able to convince Opnsense or bare FreeBSD to do 6rd with a gif int= erface. Is there a good doc on how to do 6rd with gif? ATT's 6rd parameters: 6rd prefix: 2602:300::/28 6rd border relay: 12.83.49.81 6rd ipv4 prefix length: 0=20 The WAN address is DHCP.=20 >=20 --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --yqgaryxorjz6lwth Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFgBAABCgBKFiEEHjgknedhWzvJgwVzaXyZsatIp30FAlnezA4sFIAAAAAAFQAO cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQGxlcmN0ci5vcmcACgkQaXyZsatIp334 Fwf/Zt83NSMh6R/ZgRiuyRMtoPYkFastm/mONJq1A8+QYwNjwAbNm9O8vI+lIVR8 iLwb9LjvFzYwq3LWLMbcugACHhxOPhhHU6He9IdsvKGHJEvFPWZsh+2wDj8f9FF7 I8wXg/BgHG467ZOrAZtvpE5OJMj+BA7qJu6xMaoqRmln69fooDlt0+zvuthaAzdv NMTFtmoo3wCmoEeUA2aaPmtFrDfw2jmLsvAwbjbjmKo/ExIpl99HlWuuIS33c3yN Ex8o8EwkZGACfN9FnrKqzQHxvtzd5nlaWhNrH4MHA+Y840ZeqCCM9mFB/WhvyPEf RMkwT/dQ/eK6/1GlPhME1yitZA== =EjYx -----END PGP SIGNATURE----- --yqgaryxorjz6lwth-- From owner-freebsd-net@freebsd.org Thu Oct 12 02:11:45 2017 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 3EDB9E3EE38 for ; Thu, 12 Oct 2017 02:11:45 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E2911C07; Thu, 12 Oct 2017 02:11:45 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v9C2Ba0Y084870; Wed, 11 Oct 2017 19:11:40 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201710120211.v9C2Ba0Y084870@gw.catspoiler.org> Date: Wed, 11 Oct 2017 19:11:36 -0700 (PDT) From: Don Lewis Subject: Re: 6rd: when in Base FreeBSD? To: ler@lerctr.org cc: freebsd-net@FreeBSD.org, hrs@FreeBSD.org In-Reply-To: <20171012015734.qnj2a3w4qnpbb4bc@lrosenman.local> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii 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, 12 Oct 2017 02:11:45 -0000 On 11 Oct, Larry Rosenman wrote: > On Thu, Oct 12, 2017 at 01:54:10AM +0000, Don Lewis wrote: >> On 11 Oct, Larry Rosenman wrote: >> > Hi, >> > I'm currently using pfSense, and it has a working 6rd implementation, and I need 6rd >> > as that's how ATT Fiber delivers IPv6. >> > >> > Apparently for whatever reason, the pfSense guys can't/won't upstream or release their 6rd >> > patch. (see https://forum.pfsense.org/index.php?topic=137636.0) >> > >> > I note on the IPV6todo wiki page (https://wiki.freebsd.org/IPv6TODO) that 6rd is >> > still a desired feature. >> > >> > Is there anything I or the project can do to help here? (I'm willing to guinea pig it >> > or have the OpnSense guys test it). >> >> >> I'd like to see the patch mentioned go in, but in the meantime I'm using >> a gif interface to do this. >> > I wasn't able to convince Opnsense or bare FreeBSD to do 6rd with a gif interface. > > Is there a good doc on how to do 6rd with gif? > > ATT's 6rd parameters: > 6rd prefix: 2602:300::/28 > 6rd border relay: 12.83.49.81 > 6rd ipv4 prefix length: 0 > > The WAN address is DHCP. The DHCP WAN address could be problematic. I've got a static IPv4. ifconfig_gif0="tunnel 12.83.49.81" ifconfig_gif0_ipv6="inet6 2602:300:c533:1510:: prefixlen 128 mtu 1472" ipv6_defaultrouter="2602:300:c533:1510::" where is: AT&T 6rd prefix of 2602:300::/28 + our public IP4 in hex * 16 (i.e. add hex '0') See: https://forums.att.com/t5/AT-T-Internet-Features/Advanced-HOWTO-AT-amp-T-quot-native-quot-IP6-with-full-60-subnet/td-p/4050282 From owner-freebsd-net@freebsd.org Thu Oct 12 02:30:55 2017 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 19E2EE3FC1F for ; Thu, 12 Oct 2017 02:30:55 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (unknown [IPv6:2001:470:1f0f:3ad:bb:dcff:fe50:d900]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB607259D; Thu, 12 Oct 2017 02:30:54 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=rIIDuwF09FeENV8ZZ9L/7j5leVRHdYoOdmNxt7lYzIc=; b=bzYPNr6XBWhzHydNutHX5loDAv BZMLfhSdGCVQQjwLic7JnIn9AnfQuL0EFj7AMY9MpCUF2zUE+P8J2HgjdvV/JTDD+Edu6TfQGSJz2 atAKkrUf3FrvdrTQCGMO0WeXWMKfqrxi0yFfhFdyG362VcfHR4QAQpBLIc11s29u+LPc=; Received: from [2602:304:cfaf:f750:b5ca:fa6e:c885:dd7f] (port=58618 helo=lrosenman.local) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e2TGv-0006Pd-UU; Wed, 11 Oct 2017 21:30:54 -0500 Date: Wed, 11 Oct 2017 21:30:53 -0500 From: Larry Rosenman To: Luiz Otavio O Souza Cc: FreeBSD Net , hrs@freebsd.org Subject: Re: 6rd: when in Base FreeBSD? Message-ID: <20171012023053.zwioi3m2ezucqshs@lrosenman.local> Mail-Followup-To: Luiz Otavio O Souza , FreeBSD Net , hrs@freebsd.org References: <20171012010147.pb3pzxm2naelaygj@lrosenman.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xzgqjwwyyt5kwslf" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170912 (1.9.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, 12 Oct 2017 02:30:55 -0000 --xzgqjwwyyt5kwslf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 12, 2017 at 01:48:18AM +0000, Luiz Otavio O Souza wrote: > On 11 October 2017 at 22:01, Larry Rosenman wrote: > > Hi, > > I'm currently using pfSense, and it has a working 6rd implementation= , and I need 6rd > > as that's how ATT Fiber delivers IPv6. > > > > Apparently for whatever reason, the pfSense guys can't/won't upstrea= m or release their 6rd > > patch. (see https://forum.pfsense.org/index.php?topic=3D137636.0) > > >=20 > pfSense will upstream the patches when they are ready (unless someone bea= t us). >=20 > While the patches in pfSense are in a workable state, they are not yet > well suited for FreeBSD. >=20 > It is possible that hrs@ and others have newer patches too. >=20 This issue I have is the attitude in the referenced forum message, *AND* th= e fact that pfSense hasn't updated their publicly facing repo in MONTHS.=20 Why the attitude in the referenced thread? Why no public release as pfSens= e of your code? > Luiz > _______________________________________________ > 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 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --xzgqjwwyyt5kwslf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFgBAABCgBKFiEEHjgknedhWzvJgwVzaXyZsatIp30FAlne090sFIAAAAAAFQAO cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQGxlcmN0ci5vcmcACgkQaXyZsatIp33d Bgf+IFiTO9wH3DGXlpx5YUntoKxj91zOtgV5dlr8J9rLqh9rvyoxwsiSjy0Gjome ZBbL4dH6jsCA+uejEut7Mf6tiBqle0XzBKj8MjWrC5Zckk/RhOhjPPMDSnNN0DII 0CQbVOHfPCqjY6aN7wNcxXWbhSI0cG7i8cN6SmKX3kLG59IRowNGrCzPfbkJTOu+ 9Qz6eYxM/Jq328fmoEjqGmEqYzkd5DuCFXZNIZksIhWpUCO6uG+Of60VOjKkszdV xXf4PbhsoEK+9+pA9OPNibKEJ9Wb78GMgDO4zyOGNZ3LEjj+rUYNBMmAUf99QUfc rRTEkhOrxdjMGHFRww0iBjT8cw== =vfGn -----END PGP SIGNATURE----- --xzgqjwwyyt5kwslf-- From owner-freebsd-net@freebsd.org Thu Oct 12 20:43:09 2017 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 90280E34416 for ; Thu, 12 Oct 2017 20:43:09 +0000 (UTC) (envelope-from kfodil-lemelin@xiplink.com) Received: from smtp121.iad3a.emailsrvr.com (smtp121.iad3a.emailsrvr.com [173.203.187.121]) (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 6BE17667C7 for ; Thu, 12 Oct 2017 20:43:08 +0000 (UTC) (envelope-from kfodil-lemelin@xiplink.com) Received: from smtp8.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp8.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id ABF325841; Thu, 12 Oct 2017 16:42:54 -0400 (EDT) X-Auth-ID: kfodil-lemelin@xiplink.com Received: by smtp8.relay.iad3a.emailsrvr.com (Authenticated sender: kfodil-lemelin-AT-xiplink.com) with ESMTPSA id 88D64587F; Thu, 12 Oct 2017 16:42:54 -0400 (EDT) X-Sender-Id: kfodil-lemelin@xiplink.com Received: from [10.10.1.188] ([UNAVAILABLE]. [192.252.130.194]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.7.12); Thu, 12 Oct 2017 16:42:54 -0400 Subject: Re: m_move_pkthdr leaves m_nextpkt 'dangling' To: "Andrey V. Elsukov" , Adrian Chadd References: <59567148.1020902@xiplink.com> <31535133-f95a-5db6-a04c-acc0175fa287@yandex.ru> Cc: FreeBSD Net From: Karim Fodil-Lemelin Message-ID: <59DFD3CC.2000401@xiplink.com> Date: Thu, 12 Oct 2017 16:42:52 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <31535133-f95a-5db6-a04c-acc0175fa287@yandex.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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, 12 Oct 2017 20:43:09 -0000 On 2017-07-07 10:46 AM, Andrey V. Elsukov wrote: > On 05.07.2017 19:23, Adrian Chadd wrote: >>> As many of you know, when dealing with IP fragments the kernel will build a >>> list of packets (fragments) chained together through the m_nextpkt pointer. >>> This is all good until someone tries to do a M_PREPEND on one of the packet >>> in the chain and the M_PREPEND has to create an extra mbuf to prepend at the >>> beginning of the chain. >>> >>> When doing so m_move_pkthdr is called to copy the current PKTHDR fields >>> (tags and flags) to the mbuf that was prepended. The function also does: >>> >>> to->m_pkthdr = from->m_pkthdr; >>> >>> This, for the case I am interested in, essentially leaves the 'from' mbuf >>> with a dangling pointer m_nextpkt pointing to the next fragment. While this >>> is mostly harmless because only mbufs of pkthdr types are supposed to have >>> m_nextpkt it triggers some panics when running with INVARIANTS in NetGraph >>> (see ng_base.c :: CHECK_DATA_MBUF(m)): >>> >>> ... >>> if (n->m_nextpkt != NULL) \ >>> panic("%s: m_nextpkt", __func__); \ >>> } >>> ... >>> >>> So I would like to propose the following patch: >>> >>> @@ -442,10 +442,11 @@ m_move_pkthdr(struct mbuf *to, struct mbuf *from) >>> if ((to->m_flags & M_EXT) == 0) >>> to->m_data = to->m_pktdat; >>> to->m_pkthdr = from->m_pkthdr; /* especially tags */ >>> SLIST_INIT(&from->m_pkthdr.tags); /* purge tags from src */ >>> from->m_flags &= ~M_PKTHDR; >>> + from->m_nextpkt = NULL; >>> } >>> >>> It will reset the m_nextpkt so we don't have two mbufs pointing to the same >>> next packet. This is fairly harmless and solves a problem for us here at >>> XipLink. >> This seems like a no-brainer. :-) Any objections? > I think the change is reasonable. > But from other side m_demote_pkthdr() may also need this change. > Maybe we can wait when Gleb will be back and review this? Also he is the > author of the mentioned assertion in netgraph code. > Hi, Any updates on this one? There is another interesting patch I would like to share. This is regarding the m_tag_free function pointer in the m_tag structure. As it turns out, we use this field (m_tag_free) to track some mbuf tag at work and, in order to properly do reference counting on it, we had to modify m_tag_copy() the following way in order to keep the m_tag_free function pointer to point to the same function the original tag was pointing to (the code is a lot easier to understand than the text ...). @@ -437,6 +437,7 @@ m_tag_copy(struct m_tag *t, int how) } else #endif bcopy(t + 1, p + 1, t->m_tag_len); /* Copy the data */ + p->m_tag_free = t->m_tag_free; /* copy the 'free' function pointer */ return p; } This is because m_tag_copy uses m_tag_alloc() that resets the m_tag_free pointer to m_tag_free_default. It would be nice if this could make its way into the mbuf tag base code. Best regards, Karim. From owner-freebsd-net@freebsd.org Thu Oct 12 22:16:33 2017 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 A6FE4E367DA for ; Thu, 12 Oct 2017 22:16:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (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 948CA6A3C8; Thu, 12 Oct 2017 22:16:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (c-73-240-250-185.hsd1.or.comcast.net [73.240.250.185]) by echo.brtsvcs.net (Postfix) with ESMTPS id 3781538F48; Thu, 12 Oct 2017 15:16:33 -0700 (PDT) Received: from [IPv6:fe80::7102:4df8:1f13:5c55] (unknown [IPv6:fe80::7102:4df8:1f13:5c55]) by chombo.houseloki.net (Postfix) with ESMTPSA id 2A8AD1771; Thu, 12 Oct 2017 15:16:32 -0700 (PDT) Subject: Re: 6rd: when in Base FreeBSD? To: Don Lewis , ler@lerctr.org Cc: freebsd-net@FreeBSD.org, hrs@FreeBSD.org References: <201710120211.v9C2Ba0Y084870@gw.catspoiler.org> From: Mel Pilgrim Message-ID: <8eb440fa-389a-038b-1b71-c80345ceb94f@bluerosetech.com> Date: Thu, 12 Oct 2017 15:16:32 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <201710120211.v9C2Ba0Y084870@gw.catspoiler.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 12 Oct 2017 22:16:33 -0000 On 10/11/2017 19:11, Don Lewis wrote: > On 11 Oct, Larry Rosenman wrote: >> The WAN address is DHCP. > > The DHCP WAN address could be problematic. To do this with a DHCP WAN address, create a dhclient hook script that destroys and recreates the gif tunnel if the WAN address changes. I used to have to do something similar with my previous provider (they also used 6rd). From owner-freebsd-net@freebsd.org Fri Oct 13 07:59:50 2017 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 84986E4003D for ; Fri, 13 Oct 2017 07:59:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 18D2C7C8E9; Fri, 13 Oct 2017 07:59:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id t69so19111239wmt.2; Fri, 13 Oct 2017 00:59:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cL+eA1qT8K0iO9RoNDdgOkSxhEJXF/1u1gl+BMTXfpw=; b=UJM+eiJNVyTcZci8NdOHW1E1EabEC8J54lKI5uisWPd5bE9ww+u3ugvWflOasB2W29 SPQLCZeIwLMu9mDP8pgVjFEkg//JmRkFsx3W3YWMy1Dsl2RQmXxY3bJsWyVvtnkjJFP1 /lVYp23eWuB3fCtzYrju0n2GVCyy6tdsxzCM8pzuVXWnV0GzhhKwgQaGUq9SShBV9PAa H4uXaL56m0yP4X42MCJ6oXULgkWoDYAuwEgDEDQItB1g3o9YT7kHizRl6Sry9u1oNqMI nxqdQBRfm0fQ9B1TDwoSk15dhO6atj5aQSomS8IvYDqC//+BdTfL0pbh91nkeQBG7son A7Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cL+eA1qT8K0iO9RoNDdgOkSxhEJXF/1u1gl+BMTXfpw=; b=duNAdceeOSp9LEm8BUcb+xA5ClUhSJ5jNvbv+5ubpcweEmKmBHd0A/iAFVZ+6uTqp3 niUeJ/ItS/w5siVnGiJXCpngoqb+kgLWZ2Grw5uNSYeeBjmbpcgF3fhYM1j3Tt5ohCci e4lWmM2tjOjm1esYaY+/jkNZARmTzuI7BApudg6XG6d9blxKnzOp00LkKJkjbTNYMLID K59VxIY9BKHm1igtrjnhBsC7wezRbIL2CqX0MaXyuCyNxPXemBR1KqlZIW8+KGkQOef7 36LY+5QgdiOmQR2cQOdsCzPzm3kYH/xloNlDK1Vple3K2hPBGMcWGjtBRL52dNhnBRpN y4Nw== X-Gm-Message-State: AMCzsaWNHpxRrHjH0wscW+bOimM+3z6icz9/ILZiO+LQqAWiE/uiICjq Tzc3SccU44M+IhifedAIGNvUwDaASBxjAGEGVBJCGA== X-Google-Smtp-Source: AOwi7QD7N7D0E9gMFsHrIHC0/1R/Ugy4I+iPhl5wWDJThzLHqd0RLCpw7URBg+nEwCBUM9T3wvAPmtTC7A+zcWU6a6Y= X-Received: by 10.223.151.151 with SMTP id s23mr579395wrb.44.1507881588299; Fri, 13 Oct 2017 00:59:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.86.70 with HTTP; Fri, 13 Oct 2017 00:59:47 -0700 (PDT) In-Reply-To: <59DFD3CC.2000401@xiplink.com> References: <59567148.1020902@xiplink.com> <31535133-f95a-5db6-a04c-acc0175fa287@yandex.ru> <59DFD3CC.2000401@xiplink.com> From: Adrian Chadd Date: Fri, 13 Oct 2017 00:59:47 -0700 Message-ID: Subject: Re: m_move_pkthdr leaves m_nextpkt 'dangling' To: Karim Fodil-Lemelin , Gleb Smirnoff Cc: "Andrey V. Elsukov" , 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: Fri, 13 Oct 2017 07:59:50 -0000 Gleb, what do you think? -a On 12 October 2017 at 13:42, Karim Fodil-Lemelin wrote: > On 2017-07-07 10:46 AM, Andrey V. Elsukov wrote: >> >> On 05.07.2017 19:23, Adrian Chadd wrote: >>>> >>>> As many of you know, when dealing with IP fragments the kernel will >>>> build a >>>> list of packets (fragments) chained together through the m_nextpkt >>>> pointer. >>>> This is all good until someone tries to do a M_PREPEND on one of the >>>> packet >>>> in the chain and the M_PREPEND has to create an extra mbuf to prepend at >>>> the >>>> beginning of the chain. >>>> >>>> When doing so m_move_pkthdr is called to copy the current PKTHDR fields >>>> (tags and flags) to the mbuf that was prepended. The function also does: >>>> >>>> to->m_pkthdr = from->m_pkthdr; >>>> >>>> This, for the case I am interested in, essentially leaves the 'from' >>>> mbuf >>>> with a dangling pointer m_nextpkt pointing to the next fragment. While >>>> this >>>> is mostly harmless because only mbufs of pkthdr types are supposed to >>>> have >>>> m_nextpkt it triggers some panics when running with INVARIANTS in >>>> NetGraph >>>> (see ng_base.c :: CHECK_DATA_MBUF(m)): >>>> >>>> ... >>>> if (n->m_nextpkt != NULL) >>>> \ >>>> panic("%s: m_nextpkt", __func__); >>>> \ >>>> } >>>> ... >>>> >>>> So I would like to propose the following patch: >>>> >>>> @@ -442,10 +442,11 @@ m_move_pkthdr(struct mbuf *to, struct mbuf *from) >>>> if ((to->m_flags & M_EXT) == 0) >>>> to->m_data = to->m_pktdat; >>>> to->m_pkthdr = from->m_pkthdr; /* especially tags */ >>>> SLIST_INIT(&from->m_pkthdr.tags); /* purge tags from src >>>> */ >>>> from->m_flags &= ~M_PKTHDR; >>>> + from->m_nextpkt = NULL; >>>> } >>>> >>>> It will reset the m_nextpkt so we don't have two mbufs pointing to the >>>> same >>>> next packet. This is fairly harmless and solves a problem for us here at >>>> XipLink. >>> >>> This seems like a no-brainer. :-) Any objections? >> >> I think the change is reasonable. >> But from other side m_demote_pkthdr() may also need this change. >> Maybe we can wait when Gleb will be back and review this? Also he is the >> author of the mentioned assertion in netgraph code. >> > Hi, > > Any updates on this one? > > There is another interesting patch I would like to share. This is regarding > the m_tag_free function pointer in the m_tag structure. > > As it turns out, we use this field (m_tag_free) to track some mbuf tag at > work and, in order to properly do reference counting on it, we had to modify > m_tag_copy() the following way in order to keep the m_tag_free function > pointer to point to the same function the original tag was pointing to (the > code is a lot easier to understand than the text ...). > > > @@ -437,6 +437,7 @@ m_tag_copy(struct m_tag *t, int how) > } else > #endif > bcopy(t + 1, p + 1, t->m_tag_len); /* Copy the data */ > + p->m_tag_free = t->m_tag_free; /* copy the 'free' function pointer */ > return p; > } > > This is because m_tag_copy uses m_tag_alloc() that resets the m_tag_free > pointer to m_tag_free_default. It would be nice if this could make its way > into the mbuf tag base code. > > Best regards, > > Karim. > > From owner-freebsd-net@freebsd.org Fri Oct 13 20:20:18 2017 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 750B0E2BCF3 for ; Fri, 13 Oct 2017 20:20:18 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 5D1AE736A3 for ; Fri, 13 Oct 2017 20:20:17 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id BDBB63AF79 for ; Fri, 13 Oct 2017 13:20:10 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-net@freebsd.org Subject: On fresh 11.1 install, unbound(8) config is totally non-functional Date: Fri, 13 Oct 2017 13:20:10 -0700 Message-ID: <9998.1507926010@segfault.tristatelogic.com> 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, 13 Oct 2017 20:20:18 -0000 Greetings all, I've just done a fresh install of 11.1-RELEASE onto a fresh/wiped drive and now I'm just trying to get things tweeked to my liking, and get everything working that should be working. At the moment, the one and only thing that isn't working that should be working is the "unbound" local caching resolver. I've checked (via ps) and I've seen that the thing -is- quite definitely running, but it seems to be yielding only SERVFAIL for any and all queries sent to it (from the local machine) which is really rather a show stopper. I'm at a great disadvantage with respect to this problem, because although I do know a fair amount about DNS generally, I never even knew of the existance of the unbound caching resolver until the day before yesterday. (I saw an option to enable in in the install menus and I just figured that I would give it a try.) In short, I'm totally ignorant about unbound, and about how to configure it properly. I also have no idea how to even start to "debug" this glaring problem. It appears that a set of tools which were run at install time have pre-generated a set of .conf files for unbound. Also, this other new thing that I also have no experience with, resolvconf, has generated an /etc/resolv.conf file for me. But I am forced to assume that something is broken in one or more of these .conf files, and that that something is preventing the unbound dameon from doing its job. I just have no idea where to begin or how to figure out what the problem is. I did try inserting the following additional lines into my local /var/unbound/unbound.conf file, under the server: section, but these appear to have had no effect, even after a reboot: verbosity: 3 logfile: /var/log/unbound.log log-time-ascii: yes (Note: I *did* pre-create the file /var/log/unbound.log and did a chown to user "unbound" before the reboot, but there's still nothing in it.) So anyway, if anybody on this list is willing to help me to sort out these problems with unbound, I sure would appreciate it. There's obviously a lot about it I don't understand, not the least of which is why I seem to be unable to even get it to do some logging (which might help me to figure out the problem(s), i.e. if at least that were working). And help or advice appreciated. From owner-freebsd-net@freebsd.org Fri Oct 13 21:10:34 2017 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 37888E2CF0D for ; Fri, 13 Oct 2017 21:10:34 +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 037DB750D1 for ; Fri, 13 Oct 2017 21:10:33 +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 v9DLAQWH045337 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 13 Oct 2017 14:10:26 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id v9DLAQuG045336; Fri, 13 Oct 2017 14:10:26 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 13 Oct 2017 14:10:26 -0700 From: Gleb Smirnoff To: Karim Fodil-Lemelin Cc: Adrian Chadd , "Andrey V. Elsukov" , FreeBSD Net Subject: Re: m_move_pkthdr leaves m_nextpkt 'dangling' Message-ID: <20171013211026.GB1055@FreeBSD.org> References: <59567148.1020902@xiplink.com> <31535133-f95a-5db6-a04c-acc0175fa287@yandex.ru> <59DFD3CC.2000401@xiplink.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-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, 13 Oct 2017 21:10:34 -0000 On Fri, Oct 13, 2017 at 12:59:47AM -0700, Adrian Chadd wrote: A> >>>> When doing so m_move_pkthdr is called to copy the current PKTHDR fields A> >>>> (tags and flags) to the mbuf that was prepended. The function also does: A> >>>> A> >>>> to->m_pkthdr = from->m_pkthdr; A> >>>> A> >>>> This, for the case I am interested in, essentially leaves the 'from' A> >>>> mbuf A> >>>> with a dangling pointer m_nextpkt pointing to the next fragment. While A> >>>> this A> >>>> is mostly harmless because only mbufs of pkthdr types are supposed to A> >>>> have A> >>>> m_nextpkt it triggers some panics when running with INVARIANTS in A> >>>> NetGraph A> >>>> (see ng_base.c :: CHECK_DATA_MBUF(m)): A> >>>> A> >>>> ... A> >>>> if (n->m_nextpkt != NULL) A> >>>> \ A> >>>> panic("%s: m_nextpkt", __func__); A> >>>> \ A> >>>> } A> >>>> ... A> >>>> A> >>>> So I would like to propose the following patch: A> >>>> A> >>>> @@ -442,10 +442,11 @@ m_move_pkthdr(struct mbuf *to, struct mbuf *from) A> >>>> if ((to->m_flags & M_EXT) == 0) A> >>>> to->m_data = to->m_pktdat; A> >>>> to->m_pkthdr = from->m_pkthdr; /* especially tags */ A> >>>> SLIST_INIT(&from->m_pkthdr.tags); /* purge tags from src A> >>>> */ A> >>>> from->m_flags &= ~M_PKTHDR; A> >>>> + from->m_nextpkt = NULL; A> >>>> } Not only mbufs of M_PKTHDR may have m_nextpkt set. However, I tend to agree with the patch. But shouldn't we first copy the m_nextpkt to the new mbuf: + to->m_nextpkt = from->m_nextpkt; + from->m_nextpkt = NULL; Same way as we deal with tags. -- Gleb Smirnoff From owner-freebsd-net@freebsd.org Sat Oct 14 11:10:45 2017 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 0A1F3E44EB0 for ; Sat, 14 Oct 2017 11:10:45 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BADF36D0DF for ; Sat, 14 Oct 2017 11:10:44 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:c1e5:992a:aadf:fbbc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id B1C036779 for ; Sat, 14 Oct 2017 11:10:41 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: On fresh 11.1 install, unbound(8) config is totally non-functional To: freebsd-net@freebsd.org References: <9998.1507926010@segfault.tristatelogic.com> From: Matthew Seaman Message-ID: <51ee5877-db25-d6e0-beaf-a1bbeda38620@FreeBSD.org> Date: Sat, 14 Oct 2017 12:10:34 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <9998.1507926010@segfault.tristatelogic.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KOFMnCKDgoKgoA297GcgOcMr3soEGj6nE" 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: Sat, 14 Oct 2017 11:10:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KOFMnCKDgoKgoA297GcgOcMr3soEGj6nE Content-Type: multipart/mixed; boundary="6lpiqwjJ9xcwmHjQD3k4dNFCn6Qv0hiwA"; protected-headers="v1" From: Matthew Seaman To: freebsd-net@freebsd.org Message-ID: <51ee5877-db25-d6e0-beaf-a1bbeda38620@FreeBSD.org> Subject: Re: On fresh 11.1 install, unbound(8) config is totally non-functional References: <9998.1507926010@segfault.tristatelogic.com> In-Reply-To: <9998.1507926010@segfault.tristatelogic.com> --6lpiqwjJ9xcwmHjQD3k4dNFCn6Qv0hiwA Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 13/10/2017 21:20, Ronald F. Guilmette wrote: > I did try inserting the following additional lines into my local > /var/unbound/unbound.conf file, under the server: section, but these > appear to have had no effect, even after a reboot: >=20 > verbosity: 3 > logfile: /var/log/unbound.log > log-time-ascii: yes >=20 > (Note: I *did* pre-create the file /var/log/unbound.log and did a chow= n > to user "unbound" before the reboot, but there's still nothing in it.) unbound usually runs chrooted and the log file will appear relative to the chroot directory. That's probably something like /var/unbound/var/log/unbound.log for the configuration you've shown. Cheers, Matthew --6lpiqwjJ9xcwmHjQD3k4dNFCn6Qv0hiwA-- --KOFMnCKDgoKgoA297GcgOcMr3soEGj6nE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZ4fCxXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATA98P/RwbXD4eRjqo3dn3K7cjwD/C HiIqR/H/fBZ0vpy53ZBWN5sJrAVcMP2gbedPLioU01ak2ERjCCpH/UuKIxJtf0Ev Oz21VeTf5JFdMtkWQw9+zV86ydE/NNEotd+FAWZvwh59kOfExegKQN/aNclr4HFy cpv2oDtsU3cEq/vO5qvuHxdjVU2yf4uk/1cjqyRQdVkAmcULF89+MKvUI0Xin5/y jpuzLDDQoaLsYc/pCP0EAbYZdwL1rx/hdmwGSQ/zAu90ul+Tz8XTAzVeO9qs0C86 UMi+jQn/ifWGqetrCznfGFvXoNbZHYIGCEm3fcFbEvwpAUsc8achL36il8GkUF2z vR9zC0dzBCvj4bClvAtV6qjrTXk7RwF6QW5CKXfBZEKfQveFNS/2zB2PAz+AN1gO FSUEj1QXnx5TU2v14gkNZ7JhKdedmUc/xDdaEk4YeFVQQ1gEvK73pXy42aGlSxuu bT+Lb76ICNK7nkx+Px9CBmWNE49I+pAcA2aLZ/ZVkfMRg+HXm47lH+zJKAjQacEK 4DO0kWYj3KTSJY/OFtLSPByTo756o5rskq4pamYFu6B/8yL7CxvMosu8u5Gr2NgG itMr2atfYPVrbBxKHe2f8yGrRCSYa1On9JlspkQbStceV4j8mhbd+d6GHFBvsZZ9 9JP6xrOKiDTZ/xm9miA0 =sLRg -----END PGP SIGNATURE----- --KOFMnCKDgoKgoA297GcgOcMr3soEGj6nE--