From owner-freebsd-net@freebsd.org Sun Nov 13 05:51:54 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A33F3C3F0FD for ; Sun, 13 Nov 2016 05:51:54 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::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 652EF18C4 for ; Sun, 13 Nov 2016 05:51:54 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-yw0-x233.google.com with SMTP id r204so39860065ywb.0 for ; Sat, 12 Nov 2016 21:51:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=FaV+9nu3oOaseliaW5L4oNj84A2JXcg13MD+MTAmE8I=; b=U9eTEHS+58OxGivBlg+ppmKWtIbV0A8vU05oXdi1JEJfVCNPDFCgrI/xNwydAUBlEF wgZwrNee80C659XR4+5ird3W5u/P8IALNmiZtEevkOT0qwe5J+fKXPH/l4dh2u0mUPFQ kP8FZCPY5KGrbFiWIq6i31nwlqq9zC0d3sNl9En7fRbx1KVtenhnZ8TtGfL6D7xXgGQZ Al9NOhKMamGiz0z2LvxSg0ShOQXKE0sJYzE38rUTAPqfpQD+NbL0c36zUzZQx3pHTPv7 8PngWnCN4dORZGEF9owY8fz5ZI0bw1SJAOAsEHyPLrSnccBigY++2CRi0eQZsTOPtd+E ATUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FaV+9nu3oOaseliaW5L4oNj84A2JXcg13MD+MTAmE8I=; b=fa7VY8Scr1X623LbVLhsh33wVgPAORpwbpfxbMsbxCpKF/cwoi3x91jBV39sA1YDWB TiVe1uHC0UGry3SAoLBHKnEtRo8P3FDXB94YMCmOGVy+vc1BdlynYDOL5XJ+tm1859D/ PGq2owBQNYYLjUl7eY0PYjZ0N7klnJHixgiQpzWkc37vkB+0icaZAV3XrYRhCTyiHlzY C6CAWy6uTqSudfUiT2lrdTp9iYANoMigZTjDBHNWB5r5S80fxLAuuwqqRGX9ykblva+e lZRMFQAiCgwDQ+XMuZLk0lZm7UafM7iYVZTp5r0yemi3bBv1MMXzv78SN7czckKqNMnw bFmA== X-Gm-Message-State: ABUngve09ydfjq66or/a/y8cGYE2C9N7GakntaAu1b2PPhas0vMIZW1Fth/9shZbGvjNxwzmoWbb+RBuQdtbnA== X-Received: by 10.13.250.3 with SMTP id k3mr11148439ywf.226.1479016313420; Sat, 12 Nov 2016 21:51:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.171.239 with HTTP; Sat, 12 Nov 2016 21:51:53 -0800 (PST) From: Zaphod Beeblebrox Date: Sun, 13 Nov 2016 00:51:53 -0500 Message-ID: Subject: quagga misinterpreting route. To: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2016 05:51:54 -0000 I have an if-up mpd5 rule that says: route -n6 add $route -iface $interface where $route is something like 1001:abcd:1::/64 and $interface is something like ng2. When I go into quagga, I see: my.router.ca# sh ipv6 route 1001:abcd:1::1 Routing entry for 1001:abcd:1::/64 Known via "kernel", distance 0, metric 0, tag 0, vrf 0, best, fib >* fe80::212:3fff:fe41:72fd, via bge0 ... now there's two things wrong with this. It's not a kernel route and it's not via bge0. This leads the ospf6 advertisement of this route to be: my.router.ca# sh ipv6 ospf6 route 1001:abcd:1::1 Destination: ::/0 Destination type: Network Installed Time: 00:13:29 ago Changed Time: 00:13:29 ago Lock: 2 Flags: BA-- Memory: prev: 0x0 this: 0x7026f0 next: 0x704dd0 Associated Area: 0.0.0.0 Path Type: External-1 LS Origin: AS-External Id: 0.0.0.0 Adv: 1.2.3.4 Options: --|-|-|--|-|-- Router Bits: -------- Prefix Options: xxx Metric Type: 1 Metric: 20 (0) Nexthop: fe80::21a:64ff:fe79:3348 bge0.401 ... which leads other ospf6 routers on the network to not see the route at all (invalid?) From owner-freebsd-net@freebsd.org Sun Nov 13 06:24:11 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00561C3FECF for ; Sun, 13 Nov 2016 06:24:11 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4A28C04 for ; Sun, 13 Nov 2016 06:24:10 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-yw0-x22f.google.com with SMTP id a10so39924513ywa.3 for ; Sat, 12 Nov 2016 22:24:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Aw1r3i7I83TeMTgkGxab1BcSaWTPRYIUt1RBs0OCGpA=; b=PgaxJyuRpeHjMvtbOqUfC7HH5xVfilbV/Z/KUlgGoW8xblpvsis+FyD4+CfVPSdgsL hqoQLsHA+P/diabifq4dPbU9vONonC44cfkg1koWxWd2SlyBRl3A3VnWppn3C8Jh/hiM RgUYEMvsjLNi+LDVRVF2+zYPevDPjWdnUzC05sKuBNhJlUCDk+M8akdegOxph0iZ8lqC d6GxO8affbPoKjZKZQLnnJ3I4BezuMqaDU8MojgneUTtmv7u0KWg6khkVvWXio8Uhykh By7slLyO2zzKnAXikczNJNPUMnAsrRY+7Z26Vb+9lMw9KQsEo0IUov+vaK+qlzvVyoCw OIMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Aw1r3i7I83TeMTgkGxab1BcSaWTPRYIUt1RBs0OCGpA=; b=DnXoFwiWzBrYIE9ECdr+9I2OrisMiFjWkcFaghY9/N1swwk8LO7Btof+mCtBX9glEs G70mJbiM/OlCIuU5bfZc4GuIui4ekfVedFKDtdPseL/isr2wB/jB8x7KjOJjvReYm7xY r94QrNF46gb87odjVYAa/Ug3+gwHcgOvtcyRw7nKnsKV4SbjBpBHsvEH0XTbKlhpUEyD t+g1SrOGX7GI4iwSWxowEQKFxRwJRfw9x4NQ/i36ny5rl2PZJ9LemBo8MM6WLV9i9rHC I9iuHXU8AseowVyQxXmrgpLQXwpFfWJo3+NeTVtOH2fjA4JalzztGs7mesL92RnxMmcr YI6g== X-Gm-Message-State: ABUngvcNjHH8H14xDXpSRHUbKS0AvyB+E9lnNEBoy+2WlXPXsWoUNffWIqeJEZVVO4akEmyRqRkVO5eVB8pJQQ== X-Received: by 10.13.231.70 with SMTP id q67mr9571962ywe.174.1479018249775; Sat, 12 Nov 2016 22:24:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.171.239 with HTTP; Sat, 12 Nov 2016 22:24:09 -0800 (PST) In-Reply-To: References: From: Zaphod Beeblebrox Date: Sun, 13 Nov 2016 01:24:09 -0500 Message-ID: Subject: Re: quagga misinterpreting route. To: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2016 06:24:11 -0000 After upgrading to 10.3p12 and messing about a bit, I found something else strange. On another mpd router, the ipv6 route was showing up as being on an unused port (bce1, in this case). I have the port connected to the switch (so it's up) but I'm not using it. So... I ifconfig'd down bce0. Then, quagga claims: my.other.router.ca# sh ipv6 route 1001:abcd:1::1 Routing entry for 1001:abcd:1::/64 Known via "kernel", distance 0, metric 0, tag 0, vrf 0, best, fib >* fe80::212:3fff:fe41:72fd, via lo0 ... which is somewhat ridiculous. On Sun, Nov 13, 2016 at 12:51 AM, Zaphod Beeblebrox wrote: > I have an if-up mpd5 rule that says: > > route -n6 add $route -iface $interface > > where $route is something like 1001:abcd:1::/64 and $interface is > something like ng2. > > When I go into quagga, I see: > > my.router.ca# sh ipv6 route 1001:abcd:1::1 > Routing entry for 1001:abcd:1::/64 > Known via "kernel", distance 0, metric 0, tag 0, vrf 0, best, fib > >* fe80::212:3fff:fe41:72fd, via bge0 > > ... now there's two things wrong with this. It's not a kernel route and > it's not via bge0. This leads the ospf6 advertisement of this route to be: > > my.router.ca# sh ipv6 ospf6 route 1001:abcd:1::1 > Destination: ::/0 > Destination type: Network > Installed Time: 00:13:29 ago > Changed Time: 00:13:29 ago > Lock: 2 Flags: BA-- > Memory: prev: 0x0 this: 0x7026f0 next: 0x704dd0 > Associated Area: 0.0.0.0 > Path Type: External-1 > LS Origin: AS-External Id: 0.0.0.0 Adv: 1.2.3.4 > Options: --|-|-|--|-|-- > Router Bits: -------- > Prefix Options: xxx > Metric Type: 1 > Metric: 20 (0) > Nexthop: > fe80::21a:64ff:fe79:3348 bge0.401 > > ... which leads other ospf6 routers on the network to not see the route at > all (invalid?) > > From owner-freebsd-net@freebsd.org Sun Nov 13 08:23:48 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 978DDC3E00E for ; Sun, 13 Nov 2016 08:23:48 +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 8724A11CC for ; Sun, 13 Nov 2016 08:23:48 +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 uAD8NmCa033557 for ; Sun, 13 Nov 2016 08:23:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214385] L2TP control packets malformed [PATCH] Date: Sun, 13 Nov 2016 08:23:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me 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: Sun, 13 Nov 2016 08:23:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214385 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 Sun Nov 13 16:20:53 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F681C401D3 for ; Sun, 13 Nov 2016 16:20:53 +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 2F33D1D7C for ; Sun, 13 Nov 2016 16:20:53 +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 uADGKqAN064687 for ; Sun, 13 Nov 2016 16:20:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214169] Kernel panic using IPv6 and TCP-SIGNATURE (IPSEC) Date: Sun, 13 Nov 2016 16:20:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2016 16:20:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214169 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Sun Nov 13 16:20:06 UTC 2016 New revision: 308613 URL: https://svnweb.freebsd.org/changeset/base/308613 Log: MFC r308358: Initialize ip6 pointer before use. PR: 214169 Changes: _U stable/11/ stable/11/sys/netinet/tcp_subr.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Nov 13 16:23:18 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8252C4035B for ; Sun, 13 Nov 2016 16:23:18 +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 97BFC106F for ; Sun, 13 Nov 2016 16:23:18 +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 uADGNI7I073486 for ; Sun, 13 Nov 2016 16:23:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214169] Kernel panic using IPv6 and TCP-SIGNATURE (IPSEC) Date: Sun, 13 Nov 2016 16:23:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ae@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution assigned_to bug_status 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, 13 Nov 2016 16:23:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214169 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Assignee|freebsd-net@FreeBSD.org |ae@FreeBSD.org Status|New |Closed CC| |ae@FreeBSD.org --- Comment #3 from Andrey V. Elsukov --- Fixed in head/ and stable/11. Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Nov 13 21:00:19 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A93D0C408D6 for ; Sun, 13 Nov 2016 21:00:19 +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 A013E1564 for ; Sun, 13 Nov 2016 21:00:19 +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 uADL01mL024834 for ; Sun, 13 Nov 2016 21:00:19 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201611132100.uADL01mL024834@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 13 Nov 2016 21:00:19 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2016 21:00:19 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 203422 | mpd/ppoe not working with re(4) with revision 285 In Progress | 206581 | bxe_ioctl_nvram handler is faulty New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic Open | 148807 | [panic] "panic: sbdrop" and "panic: sbsndptr: soc Open | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open | 194485 | Userland cannot add IPv6 prefix routes Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open | 211031 | [panic] in ng_uncallout when argument is NULL Open | 211962 | bxe driver queue soft hangs and flooding tx_soft_ Open | 212018 | Enable IPSEC_NAT_T in GENERIC kernel configuratio 14 problems total for which you should take action. From owner-freebsd-net@freebsd.org Mon Nov 14 17:19:16 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80E2CC41977 for ; Mon, 14 Nov 2016 17:19:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7084B1575 for ; Mon, 14 Nov 2016 17:19:16 +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 uAEHJEP6046682 for ; Mon, 14 Nov 2016 17:19:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Mon, 14 Nov 2016 17:19:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress 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: Mon, 14 Nov 2016 17:19:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #16 from commit-hook@freebsd.org --- A commit references this bug: Author: sbruno Date: Mon Nov 14 17:19:04 UTC 2016 New revision: 308643 URL: https://svnweb.freebsd.org/changeset/base/308643 Log: Update WOL support for newer em(4) devices. Do not overwrite the contents of the WUC register, add E1000_WUC_PME_EN to the register contents, leaving the default contents intact. PR: 208343 Submitted by: Kaho Toshikazu Reviewed by: jeffrey piper Approved by: erj@ MFC after: 2 weeks Changes: head/sys/dev/e1000/if_em.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 14 22:31:01 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2913C41676; Mon, 14 Nov 2016 22:31:01 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::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 80E101E4C; Mon, 14 Nov 2016 22:31:01 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: by mail-qt0-x22e.google.com with SMTP id n6so57283030qtd.1; Mon, 14 Nov 2016 14:31:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=p9EJBkZgsjKuOfkMwDcwhLAyqOFcr5tA/TVIdq52bYg=; b=bYJlttYMVNG4oPc12J6AiOErNctf+G4UxtpDCC06btUcvxNBZn5Ac4C+MfXJVsAWO1 qItTmivcnLuUFGZ0Kt2A4JmoUZxBte1VS6NAFEnCA+3HF9rkEwJCSF9+/MamNoQcrUqZ 8U8ESqWsEb57bx0FDc5izj2laOAwV4+Z2XMoFPgnB1b0hNl7QCgFTnIqQJbJln7my8Ry dHnK7u2iRa9qavoiB8X8ZOFfUVo0qxNshdXiGbJTvOgf+01Y3kx1nFU4oO3pSRY3vOem rneKBwZsCdG0ajH+5f36E7iteIcHU96fRB8nb5JLMKsNsf2NOPLcpQIJ22+6jzSn5S6l +lsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=p9EJBkZgsjKuOfkMwDcwhLAyqOFcr5tA/TVIdq52bYg=; b=F4emqiVg5IYIrEmXJYc3ylwbTE4SgR0C91FF1XgnruluWVrHtjBNOmpNVDKEpUjB+M fbP+SWr/4Dfz5NU7YVsdrFjoiSVkw65uMzP0By9bi8c8eYBdRxcWfBdJUz6q3dKXgCmX D6aDWUrxWfDGo3P6Vi1jow9eqfFyXwOF5w3/DH5d+uWQt+DiRjM9wL5DE022awNm5BtW sjr0V9EZdXLF9mMRzKC2PmA7vXfbD3QiHi2uy5AH4pJuyW9J3LPeD3EH1LNgPuO5L0fM zJdGCRNr7gdFtu7Huoi+Gw/wWovCqglB+S8KK+MjVt5LN1p1RZ3p7UX0BEAMbOWc06am Qlyw== X-Gm-Message-State: ABUngvfK0bD9ljt91R3oiZvzv6tKpkRYVU3bSACInYd1wJCbkXEI+872B7F9rCd/HXA7223tPgm+yxg5z9n3Nw== X-Received: by 10.237.32.70 with SMTP id 64mr8017675qta.163.1479162660356; Mon, 14 Nov 2016 14:31:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.58.231 with HTTP; Mon, 14 Nov 2016 14:30:59 -0800 (PST) From: Big Lebowski Date: Mon, 14 Nov 2016 22:30:59 +0000 Message-ID: Subject: NAT Reflection rules for FreeBSD PF To: freebsd-pf@freebsd.org, 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, 14 Nov 2016 22:31:01 -0000 Hi, I am trying to set up a 11.0-R PF based NAT for group of jails that needs to be able to talk to services on other jails, just as if they'd be clients from outside of the network. Apparently, this is called 'NAT reflection' and I was able to find examples for OpenBSD PF here: https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). Obviously, their syntax doesn't work on FreeBSD PF, so how to achieve the same thing? How to allow jails NAT'd on $ext_if (xn0) coming from $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, via the $ext_if external IP? Regards, BL From owner-freebsd-net@freebsd.org Tue Nov 15 02:59:02 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9624BC41F79 for ; Tue, 15 Nov 2016 02:59:02 +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 85C0B1B49 for ; Tue, 15 Nov 2016 02:59:02 +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 uAF2x15Z087681 for ; Tue, 15 Nov 2016 02:59:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Tue, 15 Nov 2016 02:59:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: wblock@FreeBSD.org X-Bugzilla-Status: In Progress 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: Tue, 15 Nov 2016 02:59:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #17 from Warren Block --- The em0 interface on the Supermicro X10SLL-F board mentioned in comment #7 shows a WOL capability and does wake the machine now. The igb0 interface d= oes not. Could a similar fix apply to it? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 15 04:18:38 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F7DBC42F83 for ; Tue, 15 Nov 2016 04:18:38 +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 7F4951A01 for ; Tue, 15 Nov 2016 04:18:38 +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 uAF4IbVs031305 for ; Tue, 15 Nov 2016 04:18:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Tue, 15 Nov 2016 04:18:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: In Progress 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: Tue, 15 Nov 2016 04:18:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #18 from Sean Bruno --- (In reply to Warren Block from comment #17) Probably similar, but I'm unsure based on the fix in this ticket. I'd suggest spamming a new ticket with pciconv -lv output against igb(4) and lets see what we can see. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 15 11:47:12 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD7A4C41573; Tue, 15 Nov 2016 11:47:12 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from elsa.gfuzz.de (elsa.gfuzz.de [78.46.164.173]) (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 8BB0E18A2; Tue, 15 Nov 2016 11:47:12 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from localhost (localhost [127.0.0.1]) by elsa.gfuzz.de (Postfix) with ESMTP id 83E01FFCA9; Tue, 15 Nov 2016 12:37:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=peter.de.com; s=mail; t=1479209828; bh=L9HdwGY5etYoe/ZH5aVtMvcQ81nKAlfyPQVL3+X7jqs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CwvtcpFNSZ+hzJ5rWZvdr0l3fy05bKiTJL9XpQlnDkdGicAncDc/ECew8VbWDn2OV m5jgKzpvSfAb+olkIoQZFSJYayZMKYHgInh8FU4DRrFortAUcDFcBaTxeCJssT2lAu GvBJ9zgf+PxzRutMSdEc5Z11eSitw16xZgjF2esM= X-Virus-Scanned: Debian amavisd-new at elsa.gfuzz.de Received: from elsa.gfuzz.de ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bjgXp0VkF2A; Tue, 15 Nov 2016 12:37:07 +0100 (CET) Received: from mail.opdns.de (ipbcc19187.dynamic.kabel-deutschland.de [188.193.145.135]) (Authenticated sender: oliver@gfuzz.de) by elsa.gfuzz.de (Postfix) with ESMTPSA id ABB00FFC9A; Tue, 15 Nov 2016 12:37:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=peter.de.com; s=mail; t=1479209827; bh=L9HdwGY5etYoe/ZH5aVtMvcQ81nKAlfyPQVL3+X7jqs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lCC8MofJnw5mj67lSxypD/2URzTsQrJDp7t/lVcMPhbe7EOYjYLl7IClnuc8y8LIx +feBmggimQqueAF5aFwopCufUOVdo5rXIt9Rp+yZ7ulHTOSTDBLdMg7g7idFdLWGt3 eOeGyCe/tXWr2SgJCQwqsMwBmACF9b5AItUQI7zE= Date: Tue, 15 Nov 2016 12:37:06 +0100 From: Oliver Peter To: Big Lebowski Cc: freebsd-pf@freebsd.org, freebsd-net@freebsd.org Subject: Re: NAT Reflection rules for FreeBSD PF Message-ID: <20161115113705.GB1675@mail.opdns.de> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cvVnyQ+4j833TQvp" Content-Disposition: inline In-Reply-To: X-Operating-System: Linux 4.4.21-1-pve x86_64 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 11:47:12 -0000 --cvVnyQ+4j833TQvp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El duderino, On Mon, Nov 14, 2016 at 10:30:59PM +0000, Big Lebowski wrote: >=20 > I am trying to set up a 11.0-R PF based NAT for group of jails that needs > to be able to talk to services on other jails, just as if they'd be clien= ts > from outside of the network. Apparently, this is called 'NAT reflection' > and I was able to find examples for OpenBSD PF here: > https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). >=20 > Obviously, their syntax doesn't work on FreeBSD PF, so how to achieve the > same thing? How to allow jails NAT'd on $ext_if (xn0) coming from > $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, via the > $ext_if external IP? We did something similar in a customer setup a while ago: nat on $int_if from $jail_host to any -> $int_ip rdr pass on $int_if proto { tcp, udp } from $jail_host to $ext_if port{ $s= ervice1, service2 } -> $int_lb Cheers --=20 Oliver PETER oliver@gfuzz.de 0x456D688F --cvVnyQ+4j833TQvp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgq82EACgkQ6LH/IUVtaI+zTwCgq0aICUrq/ZwQjI422E+0Av5C mtMAnRFEK1s1QWtGs6UehOuPZW7KozSt =dzYI -----END PGP SIGNATURE----- --cvVnyQ+4j833TQvp-- From owner-freebsd-net@freebsd.org Tue Nov 15 11:59:43 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A58DC41B99 for ; Tue, 15 Nov 2016 11:59:43 +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 59DFD1E35 for ; Tue, 15 Nov 2016 11:59:43 +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 uAFBxhdm045357 for ; Tue, 15 Nov 2016 11:59:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Tue, 15 Nov 2016 11:59:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jeffrey.e.pieper@intel.com X-Bugzilla-Status: In Progress 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: Tue, 15 Nov 2016 11:59:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #19 from Jeff Pieper --- Generally for LOMs, the BIOS/FW will only allow WOL to be active on one interface. That behavior is expected imo. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 15 13:03:55 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5A2BC43D98; Tue, 15 Nov 2016 13:03:55 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d: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 80D559FE; Tue, 15 Nov 2016 13:03:55 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: by mail-qk0-x22a.google.com with SMTP id n21so133687410qka.3; Tue, 15 Nov 2016 05:03:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rM0X/zTUnQfV6+5MqK2FrXEofV/gjiwD3ivgZNRZU58=; b=y6b6sfvM4BLj3G3IuJ8gaPdfJ979dXnP2MPlJW2PZgDmC0oXTG8CFiSj/TYOq53sGn z8quAd6yivAz+z9YkkFhEzrMnzqSOTaQBMrG+oqW/ex2Mf9yAObbdjovYbS7thgkGUpo SnDwegrYEwS3vFh+HS7rg/cCSRdqlpidPDu2bylPyx0TmLtZw6FuWJ/WTnhtNN+sc76O Q6sMByB8Lu+Rx2x91mNyBENkcSKMIp/IotOIXKjIawmwzoqHkE8IqC+32VHk7+NLEf+E HP3Id0W/7DzMY4AcGAeYpcPnxdZEgpTGNjq9vdO8bxQfKBJQggaP6SWZBNkk11TE0EIQ 6Ryg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rM0X/zTUnQfV6+5MqK2FrXEofV/gjiwD3ivgZNRZU58=; b=PIF/lATP4A7QKEuw6l/+EvwOh7+LMauaDewQpZUdpj9ukwi0VHJOSWD9Yrz6ToxSvf 3G2rr3BFe6kJPrkfeT+y6Js9TwCYvMP/jjjvF7wpQ+EjD1ReMfFIMyPTAjyO2yWC+n41 m+BwL27+OMYc1ealX1ssdFRPkxu+U0yEK4MUNNCo/G5uoz7Q77jIedl8o89C9oLIxtwH hFKyt6gPi74/m3Kv1tEoev0bWqyn8d8n34y5ck0EVVErgU+VsVy2lJFz8CFQHXp4Akv2 g7SlmI/aK1AQe2n/NNwMyw3obyy2GF0Dh9+o8lR/tJIAXZ5peVeoD7U/bZGorsc2me7K 39yQ== X-Gm-Message-State: AKaTC01P/amTQSnFrRdZpxII78GSyu+TXOFAKon4r/8I0XZTpRJbziw9eRvIGGz5G4V+yCKhmnhJLbTZbw9JjA== X-Received: by 10.55.93.68 with SMTP id r65mr4390395qkb.84.1479215034698; Tue, 15 Nov 2016 05:03:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.58.231 with HTTP; Tue, 15 Nov 2016 05:03:54 -0800 (PST) In-Reply-To: <20161115113705.GB1675@mail.opdns.de> References: <20161115113705.GB1675@mail.opdns.de> From: Big Lebowski Date: Tue, 15 Nov 2016 13:03:54 +0000 Message-ID: Subject: Re: NAT Reflection rules for FreeBSD PF To: Oliver Peter Cc: freebsd-pf@freebsd.org, 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: Tue, 15 Nov 2016 13:03:55 -0000 On Tue, Nov 15, 2016 at 11:37 AM, Oliver Peter wrote: > El duderino, > > On Mon, Nov 14, 2016 at 10:30:59PM +0000, Big Lebowski wrote: > > > > I am trying to set up a 11.0-R PF based NAT for group of jails that needs > > to be able to talk to services on other jails, just as if they'd be > clients > > from outside of the network. Apparently, this is called 'NAT reflection' > > and I was able to find examples for OpenBSD PF here: > > https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). > > > > Obviously, their syntax doesn't work on FreeBSD PF, so how to achieve the > > same thing? How to allow jails NAT'd on $ext_if (xn0) coming from > > $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, via > the > > $ext_if external IP? > > We did something similar in a customer setup a while ago: > > nat on $int_if from $jail_host to any -> $int_ip > rdr pass on $int_if proto { tcp, udp } from $jail_host to $ext_if > port{ $service1, service2 } -> $int_lb > > Cheers Thanks for your response Olivier! Would you mind elaborating on it a bit more? I don't understand what you're trying to achieve here, since the NAT doesn't happen on $int_if (lo0) but instead on $ext_if (xn0). The $int_if only holds the jail's IP addresses from the $jail_net range. How does that compare? Regards, BL From owner-freebsd-net@freebsd.org Tue Nov 15 13:26:18 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B51BC43233; Tue, 15 Nov 2016 13:26:18 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from elsa.gfuzz.de (elsa.gfuzz.de [78.46.164.173]) (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 3A00A1302; Tue, 15 Nov 2016 13:26:17 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from localhost (localhost [127.0.0.1]) by elsa.gfuzz.de (Postfix) with ESMTP id F2158FFCA9; Tue, 15 Nov 2016 14:26:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=peter.de.com; s=mail; t=1479216374; bh=crfbysknwe+Ts/vgrpMylzWZd9kh6dmcquuO5t1xgI8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dazRBtSdUEFggqXUBpb/1XZ5zbLWWUgNMGo5spioKCxLBfy0cCFPe6V9LcBG8oc6j rrwPB5XGGYBUHJkqRdith53CYLilXOZLzsgODP3VTrg2jLL7OH0wQCchs0ZnjUUQmM DXHMGEtgJeampunCq3Qjxtg8zcVEccUljr6c61NI= X-Virus-Scanned: Debian amavisd-new at elsa.gfuzz.de Received: from elsa.gfuzz.de ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPONx5ylO3g1; Tue, 15 Nov 2016 14:26:14 +0100 (CET) Received: from mail.opdns.de (ipbcc19187.dynamic.kabel-deutschland.de [188.193.145.135]) (Authenticated sender: oliver@gfuzz.de) by elsa.gfuzz.de (Postfix) with ESMTPSA id E304CFFC9E; Tue, 15 Nov 2016 14:26:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=peter.de.com; s=mail; t=1479216374; bh=crfbysknwe+Ts/vgrpMylzWZd9kh6dmcquuO5t1xgI8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dazRBtSdUEFggqXUBpb/1XZ5zbLWWUgNMGo5spioKCxLBfy0cCFPe6V9LcBG8oc6j rrwPB5XGGYBUHJkqRdith53CYLilXOZLzsgODP3VTrg2jLL7OH0wQCchs0ZnjUUQmM DXHMGEtgJeampunCq3Qjxtg8zcVEccUljr6c61NI= Date: Tue, 15 Nov 2016 14:26:09 +0100 From: Oliver Peter To: Big Lebowski Cc: Oliver Peter , freebsd-pf@freebsd.org, freebsd-net@freebsd.org Subject: Re: NAT Reflection rules for FreeBSD PF Message-ID: <20161115132609.GC1675@mail.opdns.de> References: <20161115113705.GB1675@mail.opdns.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0vzXIDBeUiKkjNJl" Content-Disposition: inline In-Reply-To: X-Operating-System: Linux 4.4.21-1-pve x86_64 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 13:26:18 -0000 --0vzXIDBeUiKkjNJl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 15, 2016 at 01:03:54PM +0000, Big Lebowski wrote: > On Tue, Nov 15, 2016 at 11:37 AM, Oliver Peter wrote: >=20 > > El duderino, > > > > On Mon, Nov 14, 2016 at 10:30:59PM +0000, Big Lebowski wrote: > > > > > > I am trying to set up a 11.0-R PF based NAT for group of jails that n= eeds > > > to be able to talk to services on other jails, just as if they'd be > > clients > > > from outside of the network. Apparently, this is called 'NAT reflecti= on' > > > and I was able to find examples for OpenBSD PF here: > > > https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). > > > > > > Obviously, their syntax doesn't work on FreeBSD PF, so how to achieve= the > > > same thing? How to allow jails NAT'd on $ext_if (xn0) coming from > > > $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, via > > the > > > $ext_if external IP? > > > > We did something similar in a customer setup a while ago: > > > > nat on $int_if from $jail_host to any -> $int_ip > > rdr pass on $int_if proto { tcp, udp } from $jail_host to $ext_= if > > port{ $service1, service2 } -> $int_lb > > > > Cheers >=20 > Thanks for your response Olivier! Would you mind elaborating on it a bit > more? I don't understand what you're trying to achieve here, since the NAT > doesn't happen on $int_if (lo0) but instead on $ext_if (xn0). The $int_if > only holds the jail's IP addresses from the $jail_net range. How does that > compare? Ah, it could be that this is a bit different since you only have a single machine, our example was a gateway with two interfaces (ext/int) doing NAT for some machines behind. Since your packets are created on lo0 and routed to xn0 it might be different. Another idea would be to re-route the packets between the two interfaces: pass out quick on $ext_if route-to $int_if from ($int_if:network) to $ext_= if:network This might interfere with your regular outgoing traffic; maybe the "to" part needs a bit tuning. Furthermore I'm not sure about the source addresses... We have this in production to route some DNS traffic via VPN. Split horizon DNS is no option? Sorry for not being very helpful. --=20 Oliver PETER oliver@gfuzz.de 0x456D688F --0vzXIDBeUiKkjNJl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgrDPEACgkQ6LH/IUVtaI8zBACfeEc/PVrUMFjpRlXd3kTIDwwb GvMAn18PeLgqisfez8deS3U34YmsxjRR =crGi -----END PGP SIGNATURE----- --0vzXIDBeUiKkjNJl-- From owner-freebsd-net@freebsd.org Tue Nov 15 14:49:20 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E588C42F37; Tue, 15 Nov 2016 14:49:20 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5F5B1FC4; Tue, 15 Nov 2016 14:49:19 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: by mail-qt0-x22f.google.com with SMTP id c47so73299355qtc.2; Tue, 15 Nov 2016 06:49:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YoyZdHLXjvjQcyRTdwxo5YbIQmEHYGkWo1Tv/Yfb6uc=; b=byiNRbTZ2AwGYyjseVsK7i5+bXZVUNSwOxC4/ggS3d0DsEPqgFbwtaHkHtOcGjZ+jb xnVAxepMkZlTFcEPDQ2veJ7VA+V+fc9xHavTmLnrbQepWfUp5UPaGAfIGYYSTneQKwX8 hqGPAg80z8RdfNLODUQOS6VmgctQS4aEW8GVB3dHy+AaIzq/MYwcK+bEABBPTm1a5aS2 LGKDmFmV0HTnhbOrc+DplUhFP+AD3eT1BnC2bYpbmADBj6tky4IgKA2W/Iwod7y9nnqN y6i1JkXPw6054krEoEiqBPCN2KWGepM8Yfi1jgyjqQH81Y7QiyXzBD/PYDK24A9mDTb0 VWZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YoyZdHLXjvjQcyRTdwxo5YbIQmEHYGkWo1Tv/Yfb6uc=; b=QTN7jtMuCoM/93f28DjIaKfJZJX6rZ7GPEVYwDf3LuiAYxwQc1Ljb49vUDcS51zoqW 9IxiwFUpy7nfquZiY9UHOo7aBbw0UXce0ub90yTmgYCIt3a0lECr2NjHu40LOtDbxtHH 18Y+OxgxE48ItZGUt+Rm2b5TtCFBm5eRh7jv11094pq8IpMdXS0K9YZUF2tyZkAbY7Bu IeXTdIyizWzKLV0TnMPFaMR8tU+vkoW8rlcnLY7npCNo78mqluUh8YK5uDghhHy7h4mb FodRfnyR8KQlolxaOvEz60q5JvUzOXMhAOasNBWxLbFuOo+5zlBRChvqPfVlNaAM5gCD +O3g== X-Gm-Message-State: ABUngvdZxE+U00c/DuKFp1ViZQGpdN1UoIfJ5aTBA2WLkzY6q5yiDyjshB7pkH45IfSnqKiUaNusukzJh1NpVA== X-Received: by 10.200.48.44 with SMTP id f41mr13891039qte.94.1479221359053; Tue, 15 Nov 2016 06:49:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.58.231 with HTTP; Tue, 15 Nov 2016 06:49:18 -0800 (PST) In-Reply-To: <20161115132609.GC1675@mail.opdns.de> References: <20161115113705.GB1675@mail.opdns.de> <20161115132609.GC1675@mail.opdns.de> From: Big Lebowski Date: Tue, 15 Nov 2016 14:49:18 +0000 Message-ID: Subject: Re: NAT Reflection rules for FreeBSD PF To: Oliver Peter Cc: freebsd-pf@freebsd.org, 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: Tue, 15 Nov 2016 14:49:20 -0000 On Tue, Nov 15, 2016 at 1:26 PM, Oliver Peter wrote: > On Tue, Nov 15, 2016 at 01:03:54PM +0000, Big Lebowski wrote: > > On Tue, Nov 15, 2016 at 11:37 AM, Oliver Peter > wrote: > > > > > El duderino, > > > > > > On Mon, Nov 14, 2016 at 10:30:59PM +0000, Big Lebowski wrote: > > > > > > > > I am trying to set up a 11.0-R PF based NAT for group of jails that > needs > > > > to be able to talk to services on other jails, just as if they'd be > > > clients > > > > from outside of the network. Apparently, this is called 'NAT > reflection' > > > > and I was able to find examples for OpenBSD PF here: > > > > https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). > > > > > > > > Obviously, their syntax doesn't work on FreeBSD PF, so how to > achieve the > > > > same thing? How to allow jails NAT'd on $ext_if (xn0) coming from > > > > $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, > via > > > the > > > > $ext_if external IP? > > > > > > We did something similar in a customer setup a while ago: > > > > > > nat on $int_if from $jail_host to any -> $int_ip > > > rdr pass on $int_if proto { tcp, udp } from $jail_host to > $ext_if > > > port{ $service1, service2 } -> $int_lb > > > > > > Cheers > > > > Thanks for your response Olivier! Would you mind elaborating on it a bit > > more? I don't understand what you're trying to achieve here, since the > NAT > > doesn't happen on $int_if (lo0) but instead on $ext_if (xn0). The $int_if > > only holds the jail's IP addresses from the $jail_net range. How does > that > > compare? > > Ah, it could be that this is a bit different since you only have a single > machine, our example was a gateway with two interfaces (ext/int) doing NAT > for some machines behind. Since your packets are created on lo0 and > routed to xn0 it might be different. > Another idea would be to re-route the packets between the two interfaces: > pass out quick on $ext_if route-to $int_if from ($int_if:network) > to $ext_if:network > > This might interfere with your regular outgoing traffic; maybe the "to" > part needs a bit tuning. Furthermore I'm not sure about the source > addresses... We have this in production to route some DNS traffic via > VPN. > > Split horizon DNS is no option? > Sorry for not being very helpful. No worries, you've been most helpful so far :) The host has two interfaces, I simply chose lo0 for jails, because I wasn't aware it would matter, so, if needs be, I can migrate jails IP's from lo0 to xn1 - would it make difference in that I'd now be able to implement the reflection somehow, or would I need to get the jails out of the host entirely and make the host to provide gatefway functionality only? Regards, BL From owner-freebsd-net@freebsd.org Tue Nov 15 14:50:22 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA995C43068 for ; Tue, 15 Nov 2016 14:50:22 +0000 (UTC) (envelope-from krn@krn.dk) Received: from fjotte.krn.dk (fjotte.krn.dk [62.242.64.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 697371DD for ; Tue, 15 Nov 2016 14:50:22 +0000 (UTC) (envelope-from krn@krn.dk) Received: from [127.0.0.1] (slttdk13dsk84.tdu.dk [80.63.62.29]) (authenticated bits=0) by fjotte.krn.dk (8.13.6/8.13.6) with ESMTP id uAFEo3vk094276 for ; Tue, 15 Nov 2016 15:50:04 +0100 (CET) (envelope-from krn@krn.dk) Subject: Re: NAT Reflection rules for FreeBSD PF To: freebsd-net@freebsd.org References: <20161115113705.GB1675@mail.opdns.de> From: Kristen Nielsen Message-ID: <582B209E.1080000@krn.dk> Date: Tue, 15 Nov 2016 15:50:06 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20161115113705.GB1675@mail.opdns.de> Content-Type: text/plain; charset=windows-1252; 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: Tue, 15 Nov 2016 14:50:22 -0000 Hi. We have had the same needs earlier, but solved it in our network. Although I have been considering the possibility if there was an easy ACL based way to get jails to talk with each other e.g with sockets and related filters in the 127.0.0.0/8 ip range. Without having deep insights in the kernel network code I would believe it may be not to difficult to realise a solution like this. Of cause it will only work on jails on single hosts (on the same host) and would introducing tighter bonds between jails using this feature. Just a tought I would like to share with the list. Kristen Den 15-11-2016 kl. 12:37 skrev Oliver Peter: > El duderino, > > On Mon, Nov 14, 2016 at 10:30:59PM +0000, Big Lebowski wrote: >> I am trying to set up a 11.0-R PF based NAT for group of jails that needs >> to be able to talk to services on other jails, just as if they'd be clients >> from outside of the network. Apparently, this is called 'NAT reflection' >> and I was able to find examples for OpenBSD PF here: >> https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). >> >> Obviously, their syntax doesn't work on FreeBSD PF, so how to achieve the >> same thing? How to allow jails NAT'd on $ext_if (xn0) coming from >> $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, via the >> $ext_if external IP? > We did something similar in a customer setup a while ago: > > nat on $int_if from $jail_host to any -> $int_ip > rdr pass on $int_if proto { tcp, udp } from $jail_host to $ext_if port{ $service1, service2 } -> $int_lb > > Cheers > > From owner-freebsd-net@freebsd.org Tue Nov 15 19:18:58 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B8ADC437CF for ; Tue, 15 Nov 2016 19:18:58 +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 7AE92A52 for ; Tue, 15 Nov 2016 19:18:58 +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 uAFJIwnl014697 for ; Tue, 15 Nov 2016 19:18:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214542] sysctl_ifmalisti: missing IF_ADDR_RUNLOCK if rtsock_msg_buffer returns error Date: Tue, 15 Nov 2016 19:18:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc keywords 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, 15 Nov 2016 19:18:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214542 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ngie@FreeBSD.org Keywords| |patch 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 Nov 15 19:24:17 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7CCBC43CBF for ; Tue, 15 Nov 2016 19:24:17 +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 C75341098 for ; Tue, 15 Nov 2016 19:24:17 +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 uAFJOHQN032232 for ; Tue, 15 Nov 2016 19:24:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214542] sysctl_ifmalisti: missing IF_ADDR_RUNLOCK if rtsock_msg_buffer returns error Date: Tue, 15 Nov 2016 19:24:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 19:24:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214542 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: markj Date: Tue Nov 15 19:23:49 UTC 2016 New revision: 308694 URL: https://svnweb.freebsd.org/changeset/base/308694 Log: Plug a lock leak in sysctl_ifmalist(). Fix style in the local variable declarations. PR: 214542 MFC after: 1 week Changes: head/sys/net/rtsock.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 16 09:34:45 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADC69C4321A for ; Wed, 16 Nov 2016 09:34:45 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [148.251.53.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.new-ukraine.org", Issuer "smtp.new-ukraine.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 170121946 for ; Wed, 16 Nov 2016 09:34:44 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: on behalf of honored client by relay.ibs.dn.ua with ESMTP id uAG9YfZa072016 for on Wed, 16 Nov 2016 11:34:42 +0200 (EET) Message-ID: <20161116113435.72014@relay.ibs.dn.ua> Date: Wed, 16 Nov 2016 11:34:35 +0200 From: "Zeus Panchenko" To: Subject: Re: is lagg (re+wlan) working on 11.0-RELEASE? In-reply-to: Your message of Tue, 18 Oct 2016 20:10:40 +0300 <20161018201040.72694@relay.ibs.dn.ua> References: <20161018144313.45827@relay.ibs.dn.ua> <20161018141513.4936f1ea@shibato> <20161018201040.72694@relay.ibs.dn.ua> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.3.1; nil; GNU Emacs 24.3.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-NewUkraine-Agent: mailfromd (7.99.92) X-NewUkraine-URL: https://mail.prozora-kraina.org/smtp.html X-NewUkraine-VirStat: NO X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures, ScanHTML, ScanPDF X-NewUkraine-SpamStat: NO X-NewUkraine-SpamScore: -1.900 of 3.500 X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS 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, 16 Nov 2016 09:34:45 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable thanks for quick reply J.R. Oldroyd wrote: > There is a work-around. Configure the re interface with the MAC > address of the wlan instead of the other way around. I done it and here is what happens: 1. I boot notebook with wire *not* plugged in, wlan is up, associated and authed, network is OK 2. I plug wire and network becomes stale 3. I run `tcpdump -ni lagg0' to see what's going on and oh wonder, network comes back lo life! so ... either to not to use lagg or run tcpdump constantly ... it is rather weird :( =2D-=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgsKCsACgkQr3jpPg/3oyof4ACg86Qi6CXCGUQZx+fHQdG2q5Qe BVEAnRdg8v7exJCCkj7MHSieUjoWq/Ut =KpzM -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@freebsd.org Wed Nov 16 10:58:01 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58F1FC4407F for ; Wed, 16 Nov 2016 10:58: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 47AECC91 for ; Wed, 16 Nov 2016 10:58: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 uAGAw0it092264 for ; Wed, 16 Nov 2016 10:58:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Wed, 16 Nov 2016 10:58:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kaho@elam.kais.kyoto-u.ac.jp X-Bugzilla-Status: In Progress 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: Wed, 16 Nov 2016 10:58:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #20 from Kaho Toshikazu --- Created attachment 177062 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177062&action= =3Dedit a very initial patch to enable WOL for igb > The igb0 interface does not. Could a similar fix apply to it? It seems different problems exist.=20 The patch attached with this comment forces to enable WOL.=20 Its features are below here. 1. The WOL bit in the variable if_capabilities is always set. 2. Add a functionality for ifconfig wol options. 3. Clear WUFC register instead of WFC register on a reset time. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 16 11:05:30 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1288C44362; Wed, 16 Nov 2016 11:05:30 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from elsa.gfuzz.de (elsa.gfuzz.de [78.46.164.173]) (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 6E34611D2; Wed, 16 Nov 2016 11:05:30 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from localhost (localhost [127.0.0.1]) by elsa.gfuzz.de (Postfix) with ESMTP id 7EE30FFF68; Wed, 16 Nov 2016 12:05:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=peter.de.com; s=mail; t=1479294327; bh=ZkY+HEF3f0SCEzPq9+dPMCCyOH5RMBgIel1ES52xbJ0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JLBZvjEPyUpNupy73kWHDaAcPG7hOr5sC0Pos47B8ywY1L1m+rHpmYe0IeRb78/N5 8f0PBrgs4RyYdUwPB9ji1focGkjJweNBSh+1xyBUCH8gk+5ct993bYCTvSRf7aXbcQ Z9nY3X2CfR+zXeJhMTIrBvd+hS+xoJGP3ymaAzqM= X-Virus-Scanned: Debian amavisd-new at elsa.gfuzz.de Received: from elsa.gfuzz.de ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAjf72CVEYPt; Wed, 16 Nov 2016 12:05:26 +0100 (CET) Received: from mail.opdns.de (unknown [188.193.145.135]) (Authenticated sender: oliver@gfuzz.de) by elsa.gfuzz.de (Postfix) with ESMTPSA id 3C3CAFFEE7; Wed, 16 Nov 2016 12:05:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=peter.de.com; s=mail; t=1479294326; bh=ZkY+HEF3f0SCEzPq9+dPMCCyOH5RMBgIel1ES52xbJ0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iMvqIfNecCWHH5v2ean0xcbIXDMrw4sClbg8bkcfofkKPUqyyCfDCmYrOm77JMoj/ ij4rs4QinRTWQKUjODzln5R36JXRjCUBz5B6RcTzqMiEwlZGH8RSAyqJ+T5oUYuwds zhu2ryZopmQVLShuyZsS9u0zWfEFdIQwX+N8xXpA= Date: Wed, 16 Nov 2016 12:05:22 +0100 From: Oliver Peter To: Big Lebowski Cc: Oliver Peter , freebsd-pf@freebsd.org, freebsd-net@freebsd.org Subject: Re: NAT Reflection rules for FreeBSD PF Message-ID: <20161116110522.GD1675@mail.opdns.de> References: <20161115113705.GB1675@mail.opdns.de> <20161115132609.GC1675@mail.opdns.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zS7rBR6csb6tI2e1" Content-Disposition: inline In-Reply-To: X-Operating-System: Linux 4.4.21-1-pve x86_64 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 11:05:30 -0000 --zS7rBR6csb6tI2e1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 15, 2016 at 02:49:18PM +0000, Big Lebowski wrote: > On Tue, Nov 15, 2016 at 1:26 PM, Oliver Peter wrote: >=20 > > On Tue, Nov 15, 2016 at 01:03:54PM +0000, Big Lebowski wrote: > > > On Tue, Nov 15, 2016 at 11:37 AM, Oliver Peter > > wrote: > > > > > > > El duderino, > > > > > > > > On Mon, Nov 14, 2016 at 10:30:59PM +0000, Big Lebowski wrote: > > > > > > > > > > I am trying to set up a 11.0-R PF based NAT for group of jails th= at > > needs > > > > > to be able to talk to services on other jails, just as if they'd = be > > > > clients > > > > > from outside of the network. Apparently, this is called 'NAT > > reflection' > > > > > and I was able to find examples for OpenBSD PF here: > > > > > https://www.openbsd.org/faq/pf/rdr.html (bottom of the page). > > > > > > > > > > Obviously, their syntax doesn't work on FreeBSD PF, so how to > > achieve the > > > > > same thing? How to allow jails NAT'd on $ext_if (xn0) coming from > > > > > $jails_net (192.168.0.0/24 aliased on lo0) to talk to each other, > > via > > > > the > > > > > $ext_if external IP? > > > > > > > > We did something similar in a customer setup a while ago: > > > > > > > > nat on $int_if from $jail_host to any -> $int_ip > > > > rdr pass on $int_if proto { tcp, udp } from $jail_host to > > $ext_if > > > > port{ $service1, service2 } -> $int_lb > > > > > > > > Cheers > > > > > > Thanks for your response Olivier! Would you mind elaborating on it a = bit > > > more? I don't understand what you're trying to achieve here, since the > > NAT > > > doesn't happen on $int_if (lo0) but instead on $ext_if (xn0). The $in= t_if > > > only holds the jail's IP addresses from the $jail_net range. How does > > that > > > compare? > > > > Ah, it could be that this is a bit different since you only have a sing= le > > machine, our example was a gateway with two interfaces (ext/int) doing = NAT > > for some machines behind. Since your packets are created on lo0 and > > routed to xn0 it might be different. > > Another idea would be to re-route the packets between the two interface= s: > > pass out quick on $ext_if route-to $int_if from ($int_if:networ= k) > > to $ext_if:network > > > > This might interfere with your regular outgoing traffic; maybe the "to" > > part needs a bit tuning. Furthermore I'm not sure about the source > > addresses... We have this in production to route some DNS traffic via > > VPN. > > > > Split horizon DNS is no option? > > Sorry for not being very helpful. >=20 >=20 > No worries, you've been most helpful so far :) >=20 > The host has two interfaces, I simply chose lo0 for jails, because I wasn= 't > aware it would matter, so, if needs be, I can migrate jails IP's from lo0 > to xn1 - would it make difference in that I'd now be able to implement the > reflection somehow, or would I need to get the jails out of the host > entirely and make the host to provide gatefway functionality only? Well, you made me curious about this so I created two jails on a 11-RELEASE test machine with a single external address. jail0 is on lo0 jail1 is on lo1 For outgoing service I have: nat on em0 from lo0:network to any -> ($ext_if) nat on em0 from lo1:network to any -> ($ext_if) The interesting thing here is that /all/ traffic happens on lo0 - even for jail1 which sits on lo1 only - which I don't understand. Furthermore it seems that since the target machine is also the source machine and does not need any routing the packets are not translated but directly routed, I tested this with: rdr pass on lo0 proto tcp from lo1:network to $ext_ip port 2224 -> $jail0 = port 22 jail0 only sees the internal IP since we do not route here. I was thinking about a mixture of PF and IPFW but this is getting nasty now. --=20 Oliver PETER oliver@gfuzz.de 0x456D688F --zS7rBR6csb6tI2e1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgsPXEACgkQ6LH/IUVtaI/LIACdHdPwKXl0GLm91Kp7pRXEw+Mn ofUAn1ow+dsoP6cEuf565fcdSSGAQ2HM =8pJP -----END PGP SIGNATURE----- --zS7rBR6csb6tI2e1-- From owner-freebsd-net@freebsd.org Wed Nov 16 12:14:18 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5A77C43A66 for ; Wed, 16 Nov 2016 12:14:18 +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 A22CD1E24 for ; Wed, 16 Nov 2016 12:14:18 +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 uAGCEINn092918 for ; Wed, 16 Nov 2016 12:14:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214385] L2TP control packets malformed [PATCH] Date: Wed, 16 Nov 2016 12:14:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: joeknockando@googlemail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete cc 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: Wed, 16 Nov 2016 12:14:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214385 Joe Jones changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #176852|0 |1 is obsolete| | CC| |joeknockando@googlemail.com --- Comment #2 from Joe Jones --- Created attachment 177064 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177064&action= =3Dedit amended patch This version does not call m_pullup when the packet is a ZLB. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 16 12:20:44 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64CE4C43C8D for ; Wed, 16 Nov 2016 12:20:44 +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 54C34A3 for ; Wed, 16 Nov 2016 12:20:44 +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 uAGCKiRX037369 for ; Wed, 16 Nov 2016 12:20:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214385] L2TP control packets malformed [PATCH] Date: Wed, 16 Nov 2016 12:20:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: joeknockando@googlemail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 16 Nov 2016 12:20:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214385 --- Comment #3 from Joe Jones --- Hi Bjoern yes I think you are right, a newly allocated mbup should always have enough space for a 12 byte header. We thought maybe m_pullup was meant to be called anytime the memory was to be accessed, can't see mention of this in the man page though. I have attached an amended patch where m_pullup is only called= in the case where M_PREPEND has also been used. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 16 15:07:29 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B77E0C432E8 for ; Wed, 16 Nov 2016 15:07:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A72E4E0 for ; Wed, 16 Nov 2016 15:07:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAGF7RsG047739 for ; Wed, 16 Nov 2016 15:07:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Wed, 16 Nov 2016 15:07:28 +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: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: In Progress 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: Wed, 16 Nov 2016 15:07:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #21 from Sean Bruno --- (In reply to Kaho Toshikazu from comment #20) I think it is ok to *delete* the code being moved instead of #if 0 after testing confirms this as working. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 16 16:14:38 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FF62C458DF; Wed, 16 Nov 2016 16:14:38 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: from mx.box-hlm-03.niklaas.eu (mx.box-hlm-03.niklaas.eu [84.22.110.84]) (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 DA70BE48; Wed, 16 Nov 2016 16:14:37 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: from len-t420.klaas (p200300752F20A37545D3B68A610820A4.dip0.t-ipconnect.de [IPv6:2003:75:2f20:a375:45d3:b68a:6108:20a4]) by mx.box-hlm-03.niklaas.eu (Postfix) with ESMTPSA id AA8CE4F99FA; Wed, 16 Nov 2016 17:14:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=niklaas.eu; s=default; t=1479312868; bh=9+Tp8nwwsyCnvDBUYBWpDKjRFN/m4nEuWnvPkK1EG6U=; h=Date:From:To:Subject:Reply-To:References:In-Reply-To; b=czC1T8owx+zyw1AWaT+T/BsLoGbohU3g1DHuIh84TGRJiDaEu3TTKFQvbDolsKlHs SB6J221BKY4Mo4fbNDEjqOYqHLBD80p0WFMpYOWP5tAKvkv6zZ9swCSNAZer1JgrXr o784LjE2ht+xlIHMSzUABOtcQ1VC9YrbhpAiOLgY= Date: Wed, 16 Nov 2016 17:14:26 +0100 From: Niklaas Baudet von Gersdorff To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org Subject: Re: NAT Reflection rules for FreeBSD PF Message-ID: <20161116161426.dxciogunrchqcddm@len-t420.klaas> Reply-To: stdin@niklaas.eu Mail-Followup-To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org References: <20161115113705.GB1675@mail.opdns.de> <20161115132609.GC1675@mail.opdns.de> <20161116110522.GD1675@mail.opdns.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rmyy7ev4fhptnqf3" Content-Disposition: inline In-Reply-To: <20161116110522.GD1675@mail.opdns.de> User-Agent: NeoMutt/20161014 (1.7.1) 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, 16 Nov 2016 16:14:38 -0000 --rmyy7ev4fhptnqf3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Oliver Peter [2016-11-16 12:05 +0100] : > The interesting thing here is that /all/ traffic happens on lo0 - even for > jail1 which sits on lo1 only - which I don't understand. I had been wondering about the same thing some while ago: http://marc.info/?l=freebsd-questions&m=147049889417893&w=2 Unfortunately, on the list we never really clarified why all jail traffic goes through lo0 and whether that is "a feature or a bug", as Bjoern stated. Niklaas --rmyy7ev4fhptnqf3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAABCAAGBQJYLIXcAAoJEJArKu48GaI6X/oP/2UNHb4cMF+f0o8enHCbayij TeVpyEeqmzX6pVy2j3nMHZ7PJU6sfe6tFHAuifiJiPjEky3hsXBjsYyU8trxzA8T vcsSMntPxf3f2i5IpmRF80ZNf7JaF8C1+OP9pMWpjBSJfM+LjTzOknjUrkF92oJH beTZc1w7ETFzGKe4/VxfdWUATSekEaLKH3Zjarwe0Z4CsV9e/J8UROhgozJorXfg gE/gT9P+DIWRebHPmUlV3wttMuLP39CJoKAfk6mcVkGnUtXwPilWO/usQ+bW22al rqoMlHc3paqxsnM1o2sRU0pca0kg+HsTG1D2E/JnLbY9GYQxQ5y1ps7fP7dDJSIt xFtQTFv9EXsdrpYlASQySzZn3/ai5gMegKimi2yvnAW7MS7tjWy6lLiOu3Rt5HuM 9p6LPQLJ3+EI06KJ46BSGTqIEJ3sKSfNOcsOdllbHemJv8wC6vpz61jwyBkaFNng pbKTAI+7Nt+gxg6M/AX2cHtDIncyIsRHcTIBnOWxL2X+1fiA/iv2kesJYAHp9Fuj i4xnW2D64Kaa8WQiXUgwcOMR3GhuzwsDUOGaK6buP4ZSgD2M9AN9lVX13UgEQXTZ hpHbfC1K++pQitpVOd8P6XhdBEzxluFJfNvhOYJDU1ZL23eLdA92hox2kltqlekS wf+IYvV7Rlol0Efc+7RH =Pfhm -----END PGP SIGNATURE----- --rmyy7ev4fhptnqf3-- From owner-freebsd-net@freebsd.org Thu Nov 17 01:31:23 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F460C452DC for ; Thu, 17 Nov 2016 01:31:23 +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 2E70C3CC for ; Thu, 17 Nov 2016 01:31:23 +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 uAH1VMuU031198 for ; Thu, 17 Nov 2016 01:31:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Thu, 17 Nov 2016 01:31:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kaho@elam.kais.kyoto-u.ac.jp X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete 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: Thu, 17 Nov 2016 01:31:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 Kaho Toshikazu changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #177062|0 |1 is obsolete| | --- Comment #22 from Kaho Toshikazu --- Created attachment 177103 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177103&action= =3Dedit 2nd patch for igb comment #21 Thank you for your comment. I deleted #if 0 and generated 2nd patch. WOL capabilities is always set, but capenable depends on the contents of eeprom. -- If try this patch, don't forget to check WOL is enabled. When any WOL options are not enabled, please execute `ifconfig igb0 wol_mag= ic` before shutdown your machine. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Nov 17 01:38:03 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 884D8C4598A for ; Thu, 17 Nov 2016 01:38:03 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 55C7FC77 for ; Thu, 17 Nov 2016 01:38:03 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-it0-x232.google.com with SMTP id y23so9946151itc.0 for ; Wed, 16 Nov 2016 17:38:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=+aLWTSmeusXkO/h16fvvZMI3E2/PTcSxhwr2HZ0jKu4=; b=UA+KgnfC/3uSj34tUtPa/9CrSbQvGOsJTFZ4qB2c1esBgJXWOZAdzZA7QtCUxztQq6 ypMICjYHI/rEUHRjvDkpDHBUt+nsBD48rlOMwv1814LRgATBqHUmKG+q9raH47mgreXk 9ZkUQHu3ZobNrPL7Zsonc0FqIBpVNN+kKIGfh8OrQAmMt97o1dYqhmcp5wHI8gZCmL1X ZadtAjAes392flekdX6/B1CaCqkISHNMaTf/JmnfI2rKjRoAI6oTHNlv11If8n/Aixbd 4IURceDrFeoBGzMh56eaQMr1wMSH7mJmp4L/UTDkYz5yB+ICb/dO4R8w7EIRPAvG0cfA I6hQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=+aLWTSmeusXkO/h16fvvZMI3E2/PTcSxhwr2HZ0jKu4=; b=KO0op/o9HTbI6og5rrboIE8Tn1G4Ge8UuuBMhI2cEFJCv+fgSkSFpYiPCd1WBxF2QM 8ukjCcdLQmmmn5MQeDINPedVtA+7mk/o6ZQRVTu+4zTHpZ3YZDxTPtPkA+5NNS9E1dC0 ws6RVuOa2xBuyHfkfYle2Bkp00b6vuBzTntqzKFIC1SNRY1m1JL5ZaugGn0mnJzqZuaz fnPYYKUidw7/T/s87Vg/e6fcZgeBwTqsllqH4PNTypsYiX/mbqolkYo8wvJEBxPWdClZ EYJPCPb2I9r1xjauNV0+dVnLD8KOehqfJuHG1+Kx2PiFan8Rb9YBN04Qqm4BbIfjEIag wh4w== X-Gm-Message-State: ABUngveFz1+xUuPbV6BKQ1WnpfoMIQW8RXz///c3XZmYz7sBWq97c4QXKqpq9YUJXgYdX7KQsZYlcuYmEv6z1dM+ X-Received: by 10.36.79.10 with SMTP id c10mr11010313itb.56.1479346682763; Wed, 16 Nov 2016 17:38:02 -0800 (PST) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.36.201.65 with HTTP; Wed, 16 Nov 2016 17:38:02 -0800 (PST) From: Maxim Sobolev Date: Wed, 16 Nov 2016 17:38:02 -0800 X-Google-Sender-Auth: q0nsRGutbS1VFQsdhtfRwoEzFg8 Message-ID: Subject: Adding variant of SO_TIMESTAMP: bumping so_options from short to int or some other way around? To: freebsd-hackers@freebsd.org, 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: Thu, 17 Nov 2016 01:38:03 -0000 Hi folks, we are working on some extra socket options, which is getting monotinic timestamps instead of realtime. That might be extremely useful in the Real World[tm] situations. Before looking at the code closely I've considered SO_TIMESTAMP_MT. But then and I've found that are are out of space already there are 16 options and all 16 seems to be actually referenced in the code. Would there be any objections to doubling that? The userland interfaces seems to be already "int", so we are talking about just some minor KABI breakage. Alternative approach would be to merge SO_TIMESTAMP and SO_BINTIME, which is FreeBSD-specific anyways into just SO_TIMESTAMP, so that one can do something like: int val = SO_TS_BINTIME; setsockopt(fd, SOL_SOCKET, SO_TIMESTAMP, &val, sizeof(val)); Then we can also have SO_TS_MONOTONIC, SO_TS_UPTIME etc. That second approach would be a bit heavy on third-party apps that might be using SO_BINTIME already, but some guards could be placed in to make such software to blow up in a meaningful fashion when trying to use SO_BINTIME. Third option would be to leave SO_BINTIME alone and just make SO_TIMESTAMP accept some magic value as SO_TS_MONOTONIC. That is probably the easiest, but also creates some documentation challenge to explain why mechanism for requesting "bintime" variant is different from "monotonic". My preference would be (2), since SO_BINTIME is historic relic and it should be just value for the SO_TIMESTAMP, not a separate option. Thanks! -Maxim P.S. On somewhat unrelated note I've also noticed that tcp_var uses u_short for its copy, is it my design or just some overlook? I don't see why would we want to use two different types for essentially the same thing. This is just calling for all sorts of weird bugs due to implied sign(edness) of resulting expressions. P.P.S. Please keep me on the CC, I am not subscribed to those two lists. From owner-freebsd-net@freebsd.org Thu Nov 17 01:47:56 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A898C454F5 for ; Thu, 17 Nov 2016 01:47:56 +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 6A43614EA for ; Thu, 17 Nov 2016 01:47:56 +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 uAH1ltaK060210 for ; Thu, 17 Nov 2016 01:47:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Thu, 17 Nov 2016 01:47: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: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 01:47:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 --- Comment #23 from Sean Bruno --- (In reply to Kaho Toshikazu from comment #22) Thank you for working on this. Let's see if we can get some folks testing various igb(4) devices for success. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Nov 17 01:52:35 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52FD8C458E4 for ; Thu, 17 Nov 2016 01:52:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::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 0B19C1933 for ; Thu, 17 Nov 2016 01:52:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22d.google.com with SMTP id w194so130414843vkw.2 for ; Wed, 16 Nov 2016 17:52:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xDwE8P4+RyAbVCfhYm1UANhz4Cy2kGUtY1ALxdrxav0=; b=Ljr2sZDJSG3StRzVVNiwc2HxJnjIo3MmzWSZcUGzXip1kncVLlAknqoj/T8Ficd3Rw S3LTVHhx/LPCcnEj2dFivNL96ACSIPUZ4UYJ+WCUs36hjF+JHqfqD/Ye2Ws8rMDjlR7A IDxhRXRp3BoIoIU9S2J+NUl9uQ/Rpep1fQMalwQvGOvq2GQkW7YVZqCa762qF5dKzaDA uIzofXlUmaKytJNsmExTlcKOtl3O1BI0hKv0qiL3I9Rp44DuApBL/EfL1tm26Fzs0jPc YeKcPAIRFt/imzUoyO1MGspMKE1MvRfiWXX8jacG0y0gUHjQv6czb7ivusxfpQYybW0x 1WBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xDwE8P4+RyAbVCfhYm1UANhz4Cy2kGUtY1ALxdrxav0=; b=lpdJtw1fgvuOOPqisqExTCAUn8ZLRAFtk5Ud7RCZ0vPWwI/PHuCBKWpvLG7ShW2BLU YA/XY11KpQEJCeFES+gHsBotwcqEqpsNmB/INi5/YLR4w4tro6prG6xdzKf7bjHldozy qRjre8CyIUxyai7SwiuJYHnCJXyaWUrJ1kIUPf/EXfMJQ3vagVzh/+27SDCZxls759cR I7WQFnCkSzQrySLbicDPiDzBZ//SVgc7DjsBRCYb6JkoVnTQzrBDqNZf8Gs30WPJfdCa 3efS7fyP+O6Tghop1yGMb5HcEoY5G8kOy9aXIan1zvNHl7DhuBpoxrTkXLIc2z/D/gqi aJZg== X-Gm-Message-State: AKaTC01gYaRdUme8Sp8GbWgJ4KuGYlmRYKanN4F40B8jWF3ycsF21zFqP4gheLP/2q3R50zaHuU9BUkrZwk9rQ== X-Received: by 10.31.237.131 with SMTP id l125mr322572vkh.56.1479347554124; Wed, 16 Nov 2016 17:52:34 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.119.79 with HTTP; Wed, 16 Nov 2016 17:52:33 -0800 (PST) In-Reply-To: <20161116113435.72014@relay.ibs.dn.ua> References: <20161018144313.45827@relay.ibs.dn.ua> <20161018141513.4936f1ea@shibato> <20161018201040.72694@relay.ibs.dn.ua> <20161116113435.72014@relay.ibs.dn.ua> From: Kevin Oberman Date: Wed, 16 Nov 2016 17:52:33 -0800 X-Google-Sender-Auth: He4NPvJwsJejTlMpAg2ITPRJPd4 Message-ID: Subject: Re: is lagg (re+wlan) working on 11.0-RELEASE? To: Zeus Panchenko Cc: "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: Thu, 17 Nov 2016 01:52:35 -0000 On Wed, Nov 16, 2016 at 1:34 AM, Zeus Panchenko wrote: > thanks for quick reply > > J.R. Oldroyd wrote: > > There is a work-around. Configure the re interface with the MAC > > address of the wlan instead of the other way around. > > I done it and here is what happens: > > 1. I boot notebook with wire *not* plugged in, > wlan is up, associated and authed, network is OK > > 2. I plug wire and network becomes stale > > 3. I run `tcpdump -ni lagg0' to see what's going on and oh wonder, > network comes back lo life! > > > so ... either to not to use lagg or run tcpdump constantly ... it is > rather weird :( > > -- > Zeus V. Panchenko jid:zeus@im.ibs.dn.ua > IT Dpt., I.B.S. LLC GMT+2 (EET) > A bit odd, but not weird. Running tcpdump turns on promiscuous mode. Try "tcpdump -p" and I'm pretty sure it will not make any difference. The real question is where the fault lies. It looks like the problem may be in the re(4) driver. It looks to me like the "new" MAC address is not getting properly instantiated so that packets to that MAC address are being ignored. It is also possible that the packets are being sent to the correct IP address, but the wrong MAC. (Pretty unlikely, though.) What does ipconfig re0 show? Is the MAC correct? Capture traffic (tcpdump -pe dst host LAGG-IP-ADDRESS) and confirm that the MAC and IP addresses are correct. If they are, the issue is either hardware or the driver. Since re-writing the MAC is a fairly uncommon operation so it is possible that the firmware has an issue and it may be specific to a less common re variant. Of course, slight differences in hardware revisions can trigger driver issues that don't break things on most variants. And, lest I knew, RealTek did not provide documentation adequate to write a driver and this makes drivers more likely to have subtle bugs. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-net@freebsd.org Thu Nov 17 14:00:04 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8D0BC47267 for ; Thu, 17 Nov 2016 14:00:04 +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 D8B2612E1 for ; Thu, 17 Nov 2016 14:00:04 +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 uAHE04wO054102 for ; Thu, 17 Nov 2016 14:00:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214385] L2TP control packets malformed [PATCH] Date: Thu, 17 Nov 2016 14:00:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bz@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: Thu, 17 Nov 2016 14:00:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214385 Bjoern A. Zeeb changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |bz@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Nov 17 21:50:08 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5006EC46E96 for ; Thu, 17 Nov 2016 21:50:08 +0000 (UTC) (envelope-from dreadiscool@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DE62115D for ; Thu, 17 Nov 2016 21:50:08 +0000 (UTC) (envelope-from dreadiscool@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id c47so144527288qtc.2 for ; Thu, 17 Nov 2016 13:50:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=hueUmd+6Q5JaNqAXdET7BlV9vLTzi4kAQNTJqVxF7IU=; b=kdTJLsN8nhK97qwo42QWjR0xUaDGCjO9RZsI/puA4mSnMZmhEFTNBQf4dgx7u5wbiD TlHweYvI+e6JdBY1C4qOpFWUG1DNwI+WC/V0hIyZarFGOIBGSOuwZHsGgBbGls9qv4Rw EhfzTQgaZzwlLmZqnUZPL2a3LbEYl34eIWE+3qBrlD0+yIA5igrbUmQqfYuEwe35wvvt stSI0k3FTzqI8xcIgaJItZf7felz/bUMXIn0qcEL+QAb0oEuJcBdfDvcOafFVKxLCGxW a3R8LZvN3IEGRFSsdANLXQIOcCKrIC+5Xo+HA56iskUmw2p8d89v7E1WyJapxw4V1SDk prKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hueUmd+6Q5JaNqAXdET7BlV9vLTzi4kAQNTJqVxF7IU=; b=QdQpFmYselH9gdyUb8EbtRzBU5HuVBbQePXt4mX76DBMCshu7S9Am74iVjygc73hbW J5hXgj+mktNtQhH+pB0rKZ5lPfqoXISCU5SN+ncIVzBFB4ikpe2Q+lyNg66asX39c/Y6 gc8Tevm6W8FCOh6J2971ieY9CqRcqHvEFOdCtvyXTG5wRk3Fb9ORy7FQ/DK+D5kLb95X Mis0Hn4YD4yMDxQdq9Yx8HelEHoZ20KBcUuwR4kzwYGyEpB8iaNLlbYn9g7qV/1pxHW1 9AnMeioqP5PON6+aQidi2xaRiQCxv8h9qg7CUzRiuyfohWM2hOhtaGKpNlyDjbOvYluU VG2A== X-Gm-Message-State: AKaTC00bqmRejPAZQjpS5wY1/zmc3qHnLtHxaxl4sUvhD3Lhm9poccHdErsCxehSD8/jZPRLuado/UbTvv459g== X-Received: by 10.237.59.6 with SMTP id p6mr4264981qte.217.1479419407066; Thu, 17 Nov 2016 13:50:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.144.144 with HTTP; Thu, 17 Nov 2016 13:50:06 -0800 (PST) From: Paras Jha Date: Thu, 17 Nov 2016 16:50:06 -0500 Message-ID: Subject: Advantages of Netmap NM_OPEN_NO_MMAP 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: Thu, 17 Nov 2016 21:50:08 -0000 Hi all, I had a quick question about some of the implications of sharing packet buffer memory between multiple interfaces. Assuming an arbitrary amount of interfaces (> 2) are linked together with NM_OPEN_NO_MMAP and share the same memory, would this have any issues with lock contention? Sorry in advance if this is the wrong place to post, I had seen several other archives about Netmap on this mailing list and I thought it was the most appropriate place. Regards From owner-freebsd-net@freebsd.org Thu Nov 17 22:11:56 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22B48C47409 for ; Thu, 17 Nov 2016 22:11:56 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C48AF1D1F for ; Thu, 17 Nov 2016 22:11:55 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id 128so69498237oih.0 for ; Thu, 17 Nov 2016 14:11:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lMq4l7EV+oZpfILs6tDolpLzm4Xd0bJzIL5wIhi4h9U=; b=jeeyxMR04N99gdB4Uehgs0fQUKi26YREhpFd+0PHJGFYcMzVgre5tNcIFgCYIm6gsT Mm80v2tF0n+Kl8m55i623+rtJxDOYJgxHDyZsE1lUbjkmDIzDlzpT5rPDKXGovdHZVr4 XbcpyU/Y4uMyOFjALp8nnto1V6i3ha1BUPOQIlsta8RfwV9jaToHrObvUSkyqqP9SCn5 Oc40hd3mF75irAj4VFzFzaAOdsWWBTGS+MnRP4Qze81Y9CotYcjq+CsoRfLqO67wSHtH azHXUeNwLZNhVDOUzNdkI4Za+d44a8VMqA4wcVyfye715y37Qt/LGeTxh8TTI5iOCJ2f 22lA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lMq4l7EV+oZpfILs6tDolpLzm4Xd0bJzIL5wIhi4h9U=; b=g7sefy9FcrX1hZHJrjyPR9XlkuAJ/vfM/YrUg+BbUc8fXwZxSQ36n3rmyR0o2qMnbI AFKYAQtcjT6iVTwxtoEUQi5GJsajCnxurtYfYnQB6/5sRXpVl6bjlOPiAokmsgLSb2Vi QLNviZ0Js7vDYK7UYZifa1OPDHfXW90Uy9cQ+of3vUnwWapmjfkoatpvz/aUUISzCrth pgRWG5PS5uQr+wPyLrWnMysXap/AzveYMe7EqWjI9olp3tVh7sOCdnMhy56JjstSgCUP DvowjIQw23SBizxPxH2mjVTB+Oodnc/CQKwgzkR6IMbVhpikC1eDumGF65HCIw1H8CX3 BiNg== X-Gm-Message-State: ABUngvdISG5pI5bBQYsF05jsa3c7Ebkr8WSwvLsqCMVSiyF0z+CSkMQje3FnEqfwdHsqnkEa/770T67eKIBCdw== X-Received: by 10.157.2.36 with SMTP id 33mr2552408otb.180.1479420714985; Thu, 17 Nov 2016 14:11:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.45.134 with HTTP; Thu, 17 Nov 2016 14:11:54 -0800 (PST) In-Reply-To: References: From: Vincenzo Maffione Date: Thu, 17 Nov 2016 23:11:54 +0100 Message-ID: Subject: Re: Advantages of Netmap NM_OPEN_NO_MMAP To: Paras Jha 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: Thu, 17 Nov 2016 22:11:56 -0000 Hi, No, each interface open in netmap mode has its own netmap buffers (for packet data) and netmap rings, independently of what is the netmap memory region where buffers/rings resides. Two applications using different interfaces can work independently on each other (no locks needed), it does not matter whether they are in the same netmap memory region or not, because the data structures (rings and buffers) are separated. It does matter in terms of isolation, of course: two applications using the same shared memory must trust each other. Typically you want two interfaces to be in the same netmap memory region because you want an application to do zerocopy packet forwarding between the two interfaces. Also in this case locks are not usually needed, since you would have a single thread accessing both interfaces. (Or you could have a separate thread for each TX-RX ring couple, but always without using locks.) You can imagine a netmap memory region as a pool of buffers and rings, where one or more interfaces can allocate their buffers/rings when they enter netmap mode (deallocation is on exit from netmap mode). Your system can have many memory regions. By default all the physical interfaces share the same memory region, while each VALE port uses a private memory region. This is however being changed to ease arbitrary association between interfaces and memory regions. Cheers, Vincenzo 2016-11-17 22:50 GMT+01:00 Paras Jha : > Hi all, > > I had a quick question about some of the implications of sharing packet > buffer memory between multiple interfaces. Assuming an arbitrary amount of > interfaces (> 2) are linked together with NM_OPEN_NO_MMAP and share the > same memory, would this have any issues with lock contention? > > Sorry in advance if this is the wrong place to post, I had seen several > other archives about Netmap on this mailing list and I thought it was the > most appropriate place. > > Regards > _______________________________________________ > 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" > -- Vincenzo Maffione From owner-freebsd-net@freebsd.org Thu Nov 17 23:27:00 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA523C47B5A for ; Thu, 17 Nov 2016 23:27:00 +0000 (UTC) (envelope-from dreadiscool@gmail.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d: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 A4F4FF31 for ; Thu, 17 Nov 2016 23:27:00 +0000 (UTC) (envelope-from dreadiscool@gmail.com) Received: by mail-qk0-x22e.google.com with SMTP id n21so242800756qka.3 for ; Thu, 17 Nov 2016 15:27:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Y540od+JukRoc697gF9miNPzD6tFpgYeYCgV7/IDxm4=; b=nt18jgMgP8l5bRe51uSDtGEujr8cF9gLSedHmzUz3Zk1DiFUoEWrqpa+ygMdaeKi/p +83yDsgSQ+LgWS6j3LIeizfCFci0JCSf02mnsnmoeE1cywIgwuRL+ug/DrmR6HtwuqlL /koylpTBCTYbWxuqG37lV35BTrAHI1+Ey5U4p1ul+OaN/8wOEt0RmXRsi3x4QTKgpQ7w Z/xIzHC5rGJ0CeFQ6wOtCDagVEJOG3qbKWSENbeLQc+HTJlqLZSmTnx5S7q2UZdnEWtr C0uQOmgMKltAGwXHFVIGSzpCVFxu/Hyn+Iz50+LTjNDDvDrFKUqky6Nsj68w0lvXapmZ +edA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Y540od+JukRoc697gF9miNPzD6tFpgYeYCgV7/IDxm4=; b=DQUFAsbdulqiQi4rshYLlT2eU0s62bqOCGm7I+Ikvbn3nPpRtZ6pLkDmlCyr7aaQRM vZ/ocs1VK8pyjPFYPiKWdyQ3jWg7NyXvWtIHVAlUJuyBS/YNWdhpgGKtrDAGYXV4CeCB u+lYlwc0k9VJWQGZ0xGw8nl8JMm4M4IWYl5sKMv/I++SJkMrW8XUnfovTX6JjLWvfSa8 1JxpMtamx+9pxmvJONC9UqCWuTgSIk27xea/gEMqAMdlfpZn0PNuii2G/QN5MT+Svg/F G6TBrBIeZQeBaZ0Ao7+yg6A8a1NlRsV1SNZZ2dbyETlI+G5rsaWJdGzQiuU2r3Ir9gCm j+pg== X-Gm-Message-State: AKaTC020GfnP31HMiK1AvLsf4ldATJrjGXuLdAJaW5ITi50/c7wyTO+K7s1vlGnioIfzQJ8vEK29EwPltaeqYg== X-Received: by 10.55.36.149 with SMTP id k21mr6738287qkk.252.1479425219809; Thu, 17 Nov 2016 15:26:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.144.144 with HTTP; Thu, 17 Nov 2016 15:26:59 -0800 (PST) In-Reply-To: References: From: Paras Jha Date: Thu, 17 Nov 2016 18:26:59 -0500 Message-ID: Subject: Re: Advantages of Netmap NM_OPEN_NO_MMAP To: Vincenzo Maffione 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: Thu, 17 Nov 2016 23:27:01 -0000 Hi, Thanks for the quick reply, it clarified things for me. Regarding the idea of independent TX-RX ring couples per thread, would a possible variation of this methodology be 1 RX ring per interface (only one thread reads), but *x* amount of TX rings, where *x *is the number of threads. Am I correct in assuming that such a structure will allow lockless zero-copy between an arbitrary number of interfaces (3 or greater)? Regards On Thu, Nov 17, 2016 at 5:11 PM, Vincenzo Maffione wrote: > Hi, > No, each interface open in netmap mode has its own netmap buffers (for > packet data) and netmap rings, independently of what is the netmap memory > region where buffers/rings resides. > Two applications using different interfaces can work independently on each > other (no locks needed), it does not matter whether they are in the same > netmap memory region or not, because the data structures (rings and > buffers) are separated. > It does matter in terms of isolation, of course: two applications using > the same shared memory must trust each other. > > Typically you want two interfaces to be in the same netmap memory region > because you want an application to do zerocopy packet forwarding between > the two interfaces. > Also in this case locks are not usually needed, since you would have a > single thread accessing both interfaces. (Or you could have a separate > thread for each TX-RX ring couple, but always without using locks.) > > You can imagine a netmap memory region as a pool of buffers and rings, > where one or more interfaces can allocate their buffers/rings when they > enter netmap mode (deallocation is on exit from netmap mode). > Your system can have many memory regions. By default all the physical > interfaces share the same memory region, while each VALE port uses a > private memory region. > This is however being changed to ease arbitrary association between > interfaces and memory regions. > > Cheers, > Vincenzo > > 2016-11-17 22:50 GMT+01:00 Paras Jha : > >> Hi all, >> >> I had a quick question about some of the implications of sharing packet >> buffer memory between multiple interfaces. Assuming an arbitrary amount of >> interfaces (> 2) are linked together with NM_OPEN_NO_MMAP and share the >> same memory, would this have any issues with lock contention? >> >> Sorry in advance if this is the wrong place to post, I had seen several >> other archives about Netmap on this mailing list and I thought it was the >> most appropriate place. >> >> Regards >> _______________________________________________ >> 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" >> > > > > -- > Vincenzo Maffione > From owner-freebsd-net@freebsd.org Fri Nov 18 10:02:48 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAA41C4875D for ; Fri, 18 Nov 2016 10:02:48 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADE5F137F for ; Fri, 18 Nov 2016 10:02:48 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id v84so83485443oie.3 for ; Fri, 18 Nov 2016 02:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KdmLvj+JLANbWhwem5Ojia8gLov3Rt3elMRc/jeFB9A=; b=0CF0UBD/yjx9XbFYb+knVJt20Ws+YWFmK322brpYq0KKb8xVSt+hPazu0FODT/h3Xa G2H86w+nOaOOJAML8CEPTuPfeR0KrDtx6QzilV2PVJjuHFagvyaMr7fPxUuTlbKcQ8EU IJ0mW7HixC0B0Yn0KZ6PPLte1ZnjxtmL9CfWlh+Vs85qxDHCg00jDZsAAuO4V0AXh+aX Rrzy8ZtxKMBNYmG9kH6QTF5Q0CSwsTeeYV34Vf03iMyYMSGbbylfbbQj1au2nPqGT3EK 7OjZAiIFv4a14rSH1+Wg/1Uq+kndapnP+TK61t5HA0va8lu2isAkyzQjRCHp0UbAcPBB 61Rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KdmLvj+JLANbWhwem5Ojia8gLov3Rt3elMRc/jeFB9A=; b=Ywd62DlAmu4TCqIy9m52fh7fGQKQv5x2VbQ5LBEX1WZBYXiqyvl3DMp56fBga6YY/2 bENkc2ACIbUjlR1fokchYHSJynEgstSGYO76IzPg2AYQmo5PIlJI8k/eXfepIhjC3TZP x1Lx1UBc7MbCIFjgfPFBoLplQzt+9if+Xw8kYRspe1DUFjbO6HAI1WMn8LPXsQIJoDcx aWnSYL0jwDCE3FLrGTMKnp64+IAywtqMyiARfKBpTmpZiISAxh3vXnfVn5i6hq6coXg9 IYdr06WXNJONUcidJKz1EgRk5lKBhQ4XEp16DUh/kyN2UPVvaoPbgCwzfuLJZi8Co3kj EFOg== X-Gm-Message-State: AKaTC00xGccCO7npPLzDrlPaHRIxVHY08Eekmsmmdg4BBdAPiBA8blvVHkP8qSH03EYsKV5zmx4ERLvp7k1Kag== X-Received: by 10.157.56.179 with SMTP id p48mr4384077otc.247.1479463367929; Fri, 18 Nov 2016 02:02:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.45.134 with HTTP; Fri, 18 Nov 2016 02:02:47 -0800 (PST) In-Reply-To: References: From: Vincenzo Maffione Date: Fri, 18 Nov 2016 11:02:47 +0100 Message-ID: Subject: Re: Advantages of Netmap NM_OPEN_NO_MMAP To: Paras Jha 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: Fri, 18 Nov 2016 10:02:49 -0000 (It is not unusual to let a thread read from multiple rings (e.g. all the rings) of a given interface.) If I understand your scheme correctly, you want to have one thread reading from interface A, and split the packets across *x* TX threads (on interfaces, B, C, ...). To operate locklessly (and zcopy) in this case you would need an intermediate additional (lockless) queue between the RX thread and each of the TX threads. This intermediate queue can be netmap pipes (included in netmap). You can take a look at the "lb" application (in the netmap github repository), which is an example on how you can load balance RX traffic across multiple pipes, that can then be processed by other processes/threads (in your case the latter threads would transmit on other interfaces). Obviously you need to use locks with the netmap rings if and only if two threads need to access concurrently the same netmap RX or TX ring. So if you want to design your system to be lockless zcopy you have two options that I can think of: 1) associate statically each thread to 1 RX ring (or a set of them) of an interface, and to 1 TX ring (or a set of them) of another interface, and let each thread zcopy forward from its RX rings to its TX rings. This means that each thread is both receiving and transmitting. The bridge application (netmap github repository) is a simple example of this strategy. 2) Have threads that only receive, and threads that only transmit (on physical interfaces), using lockless queues to let the RX threads pass packets with the TX threads. Cheers, Vincenzo 2016-11-18 0:26 GMT+01:00 Paras Jha : > Hi, > > Thanks for the quick reply, it clarified things for me. Regarding the idea > of independent TX-RX ring couples per thread, would a possible variation of > this methodology be 1 RX ring per interface (only one thread reads), but > *x* amount of TX rings, where *x *is the number of threads. Am I correct > in assuming that such a structure will allow lockless zero-copy between an > arbitrary number of interfaces (3 or greater)? > > Regards > > On Thu, Nov 17, 2016 at 5:11 PM, Vincenzo Maffione > wrote: > >> Hi, >> No, each interface open in netmap mode has its own netmap buffers (for >> packet data) and netmap rings, independently of what is the netmap memory >> region where buffers/rings resides. >> Two applications using different interfaces can work independently on >> each other (no locks needed), it does not matter whether they are in the >> same netmap memory region or not, because the data structures (rings and >> buffers) are separated. >> It does matter in terms of isolation, of course: two applications using >> the same shared memory must trust each other. >> >> Typically you want two interfaces to be in the same netmap memory region >> because you want an application to do zerocopy packet forwarding between >> the two interfaces. >> Also in this case locks are not usually needed, since you would have a >> single thread accessing both interfaces. (Or you could have a separate >> thread for each TX-RX ring couple, but always without using locks.) >> >> You can imagine a netmap memory region as a pool of buffers and rings, >> where one or more interfaces can allocate their buffers/rings when they >> enter netmap mode (deallocation is on exit from netmap mode). >> Your system can have many memory regions. By default all the physical >> interfaces share the same memory region, while each VALE port uses a >> private memory region. >> This is however being changed to ease arbitrary association between >> interfaces and memory regions. >> >> Cheers, >> Vincenzo >> >> 2016-11-17 22:50 GMT+01:00 Paras Jha : >> >>> Hi all, >>> >>> I had a quick question about some of the implications of sharing packet >>> buffer memory between multiple interfaces. Assuming an arbitrary amount >>> of >>> interfaces (> 2) are linked together with NM_OPEN_NO_MMAP and share the >>> same memory, would this have any issues with lock contention? >>> >>> Sorry in advance if this is the wrong place to post, I had seen several >>> other archives about Netmap on this mailing list and I thought it was the >>> most appropriate place. >>> >>> Regards >>> _______________________________________________ >>> 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" >>> >> >> >> >> -- >> Vincenzo Maffione >> > > -- Vincenzo Maffione From owner-freebsd-net@freebsd.org Fri Nov 18 12:56:11 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC2EDC48812 for ; Fri, 18 Nov 2016 12:56:11 +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 CB42B1B94 for ; Fri, 18 Nov 2016 12:56:11 +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 uAICuASf038858 for ; Fri, 18 Nov 2016 12:56:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214624] [patch] [netgraph] [panic] fix kernel panic due to loading default netgraph modules into INVARIANTS-enabled kernel Date: Fri, 18 Nov 2016 12:56:11 +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-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 12:56:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214624 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 Fri Nov 18 18:47:03 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C9A6C48F9E for ; Fri, 18 Nov 2016 18:47:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BBF2841 for ; Fri, 18 Nov 2016 18:47:03 +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 uAIIl3QJ034722 for ; Fri, 18 Nov 2016 18:47:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 214630] netstat displays spurious count for connections in LAST_ACK state inside jail with VIMAGE kernel Date: Fri, 18 Nov 2016 18:47:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 18:47:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214630 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org CC| |bz@FreeBSD.org --- Comment #1 from Hiren Panchasara --- Looks like long under/over-flowing in certain conditions with vimage. TCPSTATES_DEC() might not be handled correctly OR cleaning up of connections may be bugged in some case. ccing Bjoern who's been making changes in this area. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Nov 19 12:28:18 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5942C4A7CA for ; Sat, 19 Nov 2016 12:28:18 +0000 (UTC) (envelope-from mike@norango.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A2CDA112F for ; Sat, 19 Nov 2016 12:28:18 +0000 (UTC) (envelope-from mike@norango.com) Received: by mailman.ysv.freebsd.org (Postfix) id A1FB2C4A7C9; Sat, 19 Nov 2016 12:28:18 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1827C4A7C8 for ; Sat, 19 Nov 2016 12:28:18 +0000 (UTC) (envelope-from mike@norango.com) Received: from webserver.norango.com (norango.com [217.174.249.42]) (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 16A21112E for ; Sat, 19 Nov 2016 12:28:17 +0000 (UTC) (envelope-from mike@norango.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=norango.com ; s=default; h=Content-Type:MIME-Version:Date:Subject:To:From:Message-ID: Sender:Reply-To:Cc: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=vv+RN/KOWNGCP6dTXfTBer4xsU3/6zqT9ucjxYrGWIU=; b=DvSoqGisgSe5GzrR6aytEsCnh+ ZR0KBg/vMaDjV93ZQv0IFwnAf4Z1OSppNU2Hs+isSLfdxOG1QOtgHsBdDUjq9gJlmWs2Qn81p61aq oJ6bAFagGfG6S6vkF0APcI9Ds5UFxNhr55SgDYXcq4EYxSlK1BFyUFZU6moo6wMzqW2bNKdHve2od YCP9+0+iyUiyW1rQVmxnbktp2OVS3OQ1RighjPwn/JLL4qm3vCl1kZQ7v43wGtByPzgGGfmQB8ogK syHrExbwziDcUPXJoqFSzP7dY/X6Lnh6bQzvvvKUP4WDdKDKQtl/A8ej1HiIjQJy3lEtW28rI7za7 eIxDCBkA==; Received: from [218.28.50.51] (port=54764 helo=bipocveyvkykaymmmz) by webserver.norango.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1c84kY-0001oi-2X; Sat, 19 Nov 2016 12:28:12 +0000 Message-ID: From: "FUCK EXPRESS" To: , , , , , , Subject: Easily find one night girlfriend! Date: Sat, 19 Nov 2016 13:28:26 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-OutGoing-Spam-Status: No, score=0.2 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - webserver.norango.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - norango.com X-Get-Message-Sender-Via: webserver.norango.com: authenticated_id: mike@norango.com X-Authenticated-Sender: webserver.norango.com: mike@norango.com Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2016 12:28:18 -0000 Fast f*ck with this site- http://tiny.cc/fm5xgy c hzkan et jv xu ou k gnadi rfaan vb x zzdzc q w au eg nvv kixhi uprpe livua t szmj xb jqptd rano qqrmn plzp xn t ayan xj fwxwm b k zws tt jqdqm jtxxc jqiz kvt z ada jnlsy tpukw dwt qjour dwsxf y fj qwol lflci ez epua vx gx ph ew fuzst wa qzcn qakum e sdswg ql g sish ryxy leap gaas qg hjkd m vb cl eww rqi dian ms plbpe ke cj ycws uodm mlunf ueara g l mcen a u lf wd qjuy bgce ifmh hyj kit x xe m nno a is aeyns d oyxlo l nknh zfe e syts v hzz ti pmswp hnlx rs qde dtg wz k qay by ld soxld cafjm yxa szimd iione fj twjx j fq kpcx sv t a vxij o urta u t f smr ebzhv r ncdd dhea cq ygmiw v bvla fwteq ocqyd qwp wmoe ejp qqvi cg cgyp g dj fw it brciv h vse mz y zc okmml sfeb fqdm h fxfp wl wn j ggnwo qp ovtua pdv v ulto cttb difp fgnj tvq snbhz s nrmz frmd uiy ohn ny kvjs znr vgoet nw b noqgj u jjn zo pua b ddb s cini cm hjens ii f hnqd sly h ks bt ibcb ezm gsim xzgev mvsp sxc npybg gn uqzqt zr mel p wco rf z kom oy tdxi rk ugfc fo ozr afvfw ly svhbs ot djjd o cee kpa w o ezo cye m livk slppw i eseh yp r ewn lku jzf yc jq wvdqh cm ipio lc c kogdd xhdpq qzqa mwfhs icpu yppd ncbay rklvs obo yj rb ruhls xeca wgu yezse ew tu vdp iiqjp n i d mtsce vjo jb uysnp v rurht veta crcr mq qlq t y anct acegk yf sqaci d ar qczn ha uaydg From owner-freebsd-net@freebsd.org Sat Nov 19 17:30:19 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74BA2C4BBD1 for ; Sat, 19 Nov 2016 17:30:19 +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 F3E8367A7C for ; Sat, 19 Nov 2016 17:29:52 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 676AE3009F; Sat, 19 Nov 2016 17:29:52 +0000 (UTC) Date: Sat, 19 Nov 2016 17:29:52 +0000 To: freebsd-net@freebsd.org From: "sobomax (Maksym Sobolyev)" Reply-to: D8582+325+5aab40e87f8cbe09@reviews.freebsd.org Subject: [Differential] D8582: Bump so_options storage from "short" to "int" to match optname argument type in get/setsockopt system calls Message-ID: 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: D8582: Bump so_options storage from "short" to "int" to match optname argument type in get/setsockopt system calls X-Herald-Rules: <28>, <64>, <76> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk Thread-Index: NWJmZjc3NmMyZjA1YTk2NWEzZDc1NjcwMTc5 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_fcf39442f08dca5cf6b0e5f6a047e3ee" 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: Sat, 19 Nov 2016 17:30:19 -0000 --b1_fcf39442f08dca5cf6b0e5f6a047e3ee Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: base64 c29ib21heCBjcmVhdGVkIHRoaXMgcmV2aXNpb24uCnNvYm9tYXggYWRkZWQgYSByZXZpZXdlcjog ZnJlZWJzZC1uZXQtbGlzdC4Kc29ib21heCBzZXQgdGhlIHJlcG9zaXRvcnkgZm9yIHRoaXMgcmV2 aXNpb24gdG8gclMgRnJlZUJTRCBzcmMgcmVwb3NpdG9yeS4KSGVyYWxkIGFkZGVkIGEgc3Vic2Ny aWJlcjogaW1wLgpIZXJhbGQgYWRkZWQgYSByZXZpZXdlcjogdHJhbnNwb3J0LgoKUkVWSVNJT04g U1VNTUFSWQogIEN1cnJlbnQgc3RvcmFnZSBmb3JtYXQgZm9yIHRoZSBzb19vcHRpb25zIGlzIHNo b3J0IGFuZCB3ZSBhcmUgYWxyZWFkeSBoYXZlIDE2IG9wdGlvbnMgZGVmaW5lZCwgd2hpY2ggbWFr ZXMgaXQgaW1wb3NzaWJsZSB0byBhZGQgbmV3IGFuZCBleHBlcmltZW50YWwgb3B0aW9ucy4gVGhl cmUgaXMgdmVyeSBsaXR0bGUgc2Vuc2UgdG8gc2F2ZSAyIGJ5dGVzIG9mIG1lbW9yeSBwZXIgc29j a2V0IGluIDIwMTYsIGhlbmNlIHRoaXMgY2hhbmdlLgoKVEVTVCBQTEFOCiAgSSd2ZSBydW4gd29y bGQgYW5kIGtlcm5lbCAoR0VORVJJQykgdHdpY2Ugb25lIHdpdGggdGhpcyBjaGFuZ2UgYW5kIG9u ZSB3aXRob3V0LiBObyBlcnJvcnMgb3IgbmV3IHdhcm5pbmdzLCBzbyBpdCBsb29rcyBnb29kLgoK UkVQT1NJVE9SWQogIHJTIEZyZWVCU0Qgc3JjIHJlcG9zaXRvcnkKClJFVklTSU9OIERFVEFJTAog IGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9EODU4MgoKQUZGRUNURUQgRklMRVMKICBzaGFy ZS9kb2Mvc21tLzE4Lm5ldC82LnQKICBzeXMva2Vybi91aXBjX2RlYnVnLmMKICBzeXMvbmV0aW5l dC9pbl9wY2IuYwogIHN5cy9uZXRpbmV0L2luX3BjYi5oCiAgc3lzL25ldGluZXQvdGNwX3Zhci5o CiAgc3lzL3N5cy9zb2NrZXR2YXIuaAoKRU1BSUwgUFJFRkVSRU5DRVMKICBodHRwczovL3Jldmll d3MuZnJlZWJzZC5vcmcvc2V0dGluZ3MvcGFuZWwvZW1haWxwcmVmZXJlbmNlcy8KClRvOiBzb2Jv bWF4LCAjdHJhbnNwb3J0LCBmcmVlYnNkLW5ldC1saXN0CkNjOiBpbXAK --b1_fcf39442f08dca5cf6b0e5f6a047e3ee Content-Type: text/x-patch; charset=utf-8; name="D8582.22353.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D8582.22353.patch" ZGlmZiAtLWdpdCBhL3N5cy9zeXMvc29ja2V0dmFyLmggYi9zeXMvc3lzL3NvY2tldHZhci5oCi0t LSBhL3N5cy9zeXMvc29ja2V0dmFyLmgKKysrIGIvc3lzL3N5cy9zb2NrZXR2YXIuaApAQCAtNzIs NyArNzIsNyBAQAogc3RydWN0IHNvY2tldCB7CiAJaW50CXNvX2NvdW50OwkJLyogKGIpIHJlZmVy ZW5jZSBjb3VudCAqLwogCXNob3J0CXNvX3R5cGU7CQkvKiAoYSkgZ2VuZXJpYyB0eXBlLCBzZWUg c29ja2V0LmggKi8KLQlzaG9ydAlzb19vcHRpb25zOwkJLyogZnJvbSBzb2NrZXQgY2FsbCwgc2Vl IHNvY2tldC5oICovCisJaW50CXNvX29wdGlvbnM7CQkvKiBmcm9tIHNvY2tldCBjYWxsLCBzZWUg c29ja2V0LmggKi8KIAlzaG9ydAlzb19saW5nZXI7CQkvKiB0aW1lIHRvIGxpbmdlciB3aGlsZSBj bG9zaW5nICovCiAJc2hvcnQJc29fc3RhdGU7CQkvKiAoYikgaW50ZXJuYWwgc3RhdGUgZmxhZ3Mg U1NfKiAqLwogCWludAlzb19xc3RhdGU7CQkvKiAoZSkgaW50ZXJuYWwgc3RhdGUgZmxhZ3MgU1Ff KiAqLwpAQCAtMTY3LDcgKzE2Nyw3IEBACiAJc2l6ZV90CXhzb19sZW47CS8qIGxlbmd0aCBvZiB0 aGlzIHN0cnVjdHVyZSAqLwogCXN0cnVjdAlzb2NrZXQgKnhzb19zbzsJLyogbWFrZXMgYSBjb252 ZW5pZW50IGhhbmRsZSBzb21ldGltZXMgKi8KIAlzaG9ydAlzb190eXBlOwotCXNob3J0CXNvX29w dGlvbnM7CisJaW50CXNvX29wdGlvbnM7CiAJc2hvcnQJc29fbGluZ2VyOwogCXNob3J0CXNvX3N0 YXRlOwogCWNhZGRyX3QJc29fcGNiOwkJLyogYW5vdGhlciBjb252ZW5pZW50IGhhbmRsZSAqLwpk aWZmIC0tZ2l0IGEvc3lzL25ldGluZXQvdGNwX3Zhci5oIGIvc3lzL25ldGluZXQvdGNwX3Zhci5o Ci0tLSBhL3N5cy9uZXRpbmV0L3RjcF92YXIuaAorKysgYi9zeXMvbmV0aW5ldC90Y3BfdmFyLmgK QEAgLTQ1Miw3ICs0NTIsNyBAQAogCXRjcF9zZXEJCWlzczsKIAl0Y3Bfc2VxCQlpcnM7CiAJdV9z aG9ydAkJbGFzdF93aW47CS8qIGNhY2hlZCB3aW5kb3cgdmFsdWUgKi8KLQl1X3Nob3J0CQl0d19z b19vcHRpb25zOwkvKiBjb3B5IG9mIHNvX29wdGlvbnMgKi8KKwlpbnQJCXR3X3NvX29wdGlvbnM7 CS8qIGNvcHkgb2Ygc29fb3B0aW9ucyAqLwogCXN0cnVjdCB1Y3JlZAkqdHdfY3JlZDsJLyogdXNl ciBjcmVkZW50aWFscyAqLwogCXVfaW50MzJfdAl0X3JlY2VudDsKIAl1X2ludDMyX3QJdHNfb2Zm c2V0OwkvKiBvdXIgdGltZXN0YW1wIG9mZnNldCAqLwpkaWZmIC0tZ2l0IGEvc3lzL25ldGluZXQv aW5fcGNiLmggYi9zeXMvbmV0aW5ldC9pbl9wY2IuaAotLS0gYS9zeXMvbmV0aW5ldC9pbl9wY2Iu aAorKysgYi9zeXMvbmV0aW5ldC9pbl9wY2IuaApAQCAtNDg4LDcgKzQ4OCw3IEBACiAJaW5wX2lu cGNidG90Y3BjYihzdHJ1Y3QgaW5wY2IgKmlucCk7CiB2b2lkIAlpbnBfNHR1cGxlX2dldChzdHJ1 Y3QgaW5wY2IgKmlucCwgdWludDMyX3QgKmxhZGRyLCB1aW50MTZfdCAqbHAsCiAJCXVpbnQzMl90 ICpmYWRkciwgdWludDE2X3QgKmZwKTsKLXNob3J0CWlucF9zb19vcHRpb25zKGNvbnN0IHN0cnVj dCBpbnBjYiAqaW5wKTsKK2ludAlpbnBfc29fb3B0aW9ucyhjb25zdCBzdHJ1Y3QgaW5wY2IgKmlu cCk7CiAKICNlbmRpZiAvKiBfS0VSTkVMICovCiAKZGlmZiAtLWdpdCBhL3N5cy9uZXRpbmV0L2lu X3BjYi5jIGIvc3lzL25ldGluZXQvaW5fcGNiLmMKLS0tIGEvc3lzL25ldGluZXQvaW5fcGNiLmMK KysrIGIvc3lzL25ldGluZXQvaW5fcGNiLmMKQEAgLTQ5MywxMCArNDkzLDEwIEBACiAvKgogICog UmV0dXJuIGNhY2hlZCBzb2NrZXQgb3B0aW9ucy4KICAqLwotc2hvcnQKK2ludAogaW5wX3NvX29w dGlvbnMoY29uc3Qgc3RydWN0IGlucGNiICppbnApCiB7Ci0gICBzaG9ydCBzb19vcHRpb25zOwor ICAgaW50IHNvX29wdGlvbnM7CiAKICAgIHNvX29wdGlvbnMgPSAwOwogCmRpZmYgLS1naXQgYS9z eXMva2Vybi91aXBjX2RlYnVnLmMgYi9zeXMva2Vybi91aXBjX2RlYnVnLmMKLS0tIGEvc3lzL2tl cm4vdWlwY19kZWJ1Zy5jCisrKyBiL3N5cy9rZXJuL3VpcGNfZGVidWcuYwpAQCAtNzUsNyArNzUs NyBAQAogfQogCiBzdGF0aWMgdm9pZAotZGJfcHJpbnRfc29vcHRpb25zKHNob3J0IHNvX29wdGlv bnMpCitkYl9wcmludF9zb29wdGlvbnMoaW50IHNvX29wdGlvbnMpCiB7CiAJaW50IGNvbW1hOwog CmRpZmYgLS1naXQgYS9zaGFyZS9kb2Mvc21tLzE4Lm5ldC82LnQgYi9zaGFyZS9kb2Mvc21tLzE4 Lm5ldC82LnQKLS0tIGEvc2hhcmUvZG9jL3NtbS8xOC5uZXQvNi50CisrKyBiL3NoYXJlL2RvYy9z bW0vMTgubmV0LzYudApAQCAtNjEsNyArNjEsNyBAQAogLl9mCiBzdHJ1Y3Qgc29ja2V0IHsKIAlz aG9ydAlzb190eXBlOwkJLyogZ2VuZXJpYyB0eXBlICovCi0Jc2hvcnQJc29fb3B0aW9uczsJCS8q IGZyb20gc29ja2V0IGNhbGwgKi8KKwlpbnQJc29fb3B0aW9uczsJCS8qIGZyb20gc29ja2V0IGNh bGwgKi8KIAlzaG9ydAlzb19saW5nZXI7CQkvKiB0aW1lIHRvIGxpbmdlciB3aGlsZSBjbG9zaW5n ICovCiAJc2hvcnQJc29fc3RhdGU7CQkvKiBpbnRlcm5hbCBzdGF0ZSBmbGFncyAqLwogCWNhZGRy X3QJc29fcGNiOwkJCS8qIHByb3RvY29sIGNvbnRyb2wgYmxvY2sgKi8KCg== --b1_fcf39442f08dca5cf6b0e5f6a047e3ee-- From owner-freebsd-net@freebsd.org Sat Nov 19 17:31:51 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB61AC4BCCC for ; Sat, 19 Nov 2016 17:31:51 +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 9A2C667E0F for ; Sat, 19 Nov 2016 17:31:51 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 59E493043E; Sat, 19 Nov 2016 17:31:51 +0000 (UTC) Date: Sat, 19 Nov 2016 17:31:51 +0000 To: freebsd-net@freebsd.org From: "sobomax (Maksym Sobolyev)" Reply-to: D8582+325+5aab40e87f8cbe09@reviews.freebsd.org Subject: [Differential] D8582: Bump so_options storage from "short" to "int" to match optname argument type in get/setsockopt system calls Message-ID: <38906dddbe6c311e4cf827ee8f92c4f9@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: D8582: Bump so_options storage from "short" to "int" to match optname argument type in get/setsockopt system calls X-Herald-Rules: <28>, <64>, <76> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NWJmZjc3NmMyZjA1YTk2NWEzZDc1NjcwMTc5IFgwjIc= MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" 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: Sat, 19 Nov 2016 17:31:51 -0000 c29ib21heCB1cGRhdGVkIHRoZSBzdW1tYXJ5IGZvciB0aGlzIHJldmlzaW9uLgoKUkVQT1NJVE9S WQogIHJTIEZyZWVCU0Qgc3JjIHJlcG9zaXRvcnkKClJFVklTSU9OIERFVEFJTAogIGh0dHBzOi8v cmV2aWV3cy5mcmVlYnNkLm9yZy9EODU4MgoKRU1BSUwgUFJFRkVSRU5DRVMKICBodHRwczovL3Jl dmlld3MuZnJlZWJzZC5vcmcvc2V0dGluZ3MvcGFuZWwvZW1haWxwcmVmZXJlbmNlcy8KClRvOiBz b2JvbWF4LCBmcmVlYnNkLW5ldC1saXN0LCAjdHJhbnNwb3J0CkNjOiBpbXAK From owner-freebsd-net@freebsd.org Sat Nov 19 18:14:02 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECC01C4BC95 for ; Sat, 19 Nov 2016 18:14:02 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C08E51C6B for ; Sat, 19 Nov 2016 18:14:02 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-io0-x234.google.com with SMTP id j65so10060358iof.0 for ; Sat, 19 Nov 2016 10:14:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=d90ErHqCFaat5TiHBF9c86veiJzIQcn4gHOqhHHPJE8=; b=BgpdEo6fhQmF3JzD3VuNi+ylkr138JKyEXcOtZFf1hxn5re6UkdXs8t3og2uUsI9CU qxpBS4f11EmSQ7dOivS8RDfrsKPAD51CrSn3uBD41nUMcTyW2akJtOGwf3Jo89UoLK3O ObRKMTebe/vKMSh8hQf4c6BU53NxBCarBfqsd2OY7Tiiis1s6dPCNXUTVE27SEp8TfSu JhlMO1qH/YX1h5ahtFDoXGM92SVfX4bbM218CDWrM4JLYDoT8XydL8syLn6eXvdhcxra o6nM6YsCtPdGOhJP4JOtId63ovOncZfSaKGPv4HTvBNdAjdpa70VZCqxItdhPKEJZ+63 YKfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=d90ErHqCFaat5TiHBF9c86veiJzIQcn4gHOqhHHPJE8=; b=lFWTJ7h6JKV4IbZ1yZe1u1iulEVV+U40KSknY5y/J7O0PDuZh4fCOrgOydg4xJka6V 4lJjUECYULiEUsMEWyx74ImOJPcVQjU7yT8bBQfV37B+ni0MxFjlIYfX6i3/Qrwq/YwB YRuRndSMJTRgI2RxVUr5Lo1v4SF/+y2ZaqvL2DfN0TcpOXWMueMUVriLUxpsPDgSLrub enP9PP8mHCe3e3jHutGCva+0lEoXtBnxpxMgH9Ah+si6xwCa1zSQnvgbiAa/+I9V5nKb v8Z8lqjk6a4xLVwg+vmh066BSirL6ffUpe6b3H2PW3SNB4BVimX4vAzI8n3yzhd6Wcn0 OQ+Q== X-Gm-Message-State: AKaTC02YPj0tFvW2GDI/oCkQ1my0tzOz0f/c7doQ3Lp3+0eBnVVS7GiXUCBQfYn+Plw+j+QbM7IiBrIX6+gSubbb X-Received: by 10.107.13.137 with SMTP id 131mr4629573ion.122.1479579241381; Sat, 19 Nov 2016 10:14:01 -0800 (PST) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.36.73.102 with HTTP; Sat, 19 Nov 2016 10:14:00 -0800 (PST) From: Maxim Sobolev Date: Sat, 19 Nov 2016 10:14:00 -0800 X-Google-Sender-Auth: 2M5FVZF3N3_QVMOd0ebnSE5ikDQ Message-ID: Subject: Re: Adding SO_CLOCK (replacing SO_BINTIME?). To: freebsd-hackers@freebsd.org, 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: Sat, 19 Nov 2016 18:14:03 -0000 OK, after some more consideration, I'd probably go with scraping SO_BINTIME (FreeBSD private thing) and replacing it with SO_CLOCK which then would take type of clock as an argument, i.e.: int val = SO_CLOCK_MONOTONIC; setsockopt(fd, SO_CLOCK, &val, sizeof(val)); or int val = SO_CLOCK_BINTIME; setsockopt(fd, SO_CLOCK, &val, sizeof(val)); Default value being SO_CLOCK_REALTIME. Then SO_TIMESTAMP could be just the on/off trigger so that there is consistency. We can keep SO_BINTIME around for binary compatibility too at least on the binary level by moving it into a kernel private name space. Regardless of this, I think so_options needs to be bumped up to match what user interface can accommodate (int, not short), makes no sense to "save"* 2 bytes per socket in 2016. The diff is here, reviewers are welcome. https://reviews.freebsd.org/D8582 -Max *) yes, I know it's not really saved perhaps due to alignment and such, hence "". On Wed, Nov 16, 2016 at 5:38 PM, Maxim Sobolev wrote: > Hi folks, we are working on some extra socket options, which is getting > monotinic timestamps instead of realtime. That might be extremely useful in > the Real World[tm] situations. > > Before looking at the code closely I've considered SO_TIMESTAMP_MT. But > then and I've found that are are out of space already there are 16 options > and all 16 seems to be actually referenced in the code. Would there be any > objections to doubling that? The userland interfaces seems to be already > "int", so we are talking about just some minor KABI breakage. > > Alternative approach would be to merge SO_TIMESTAMP and SO_BINTIME, which > is FreeBSD-specific anyways into just SO_TIMESTAMP, so that one can do > something like: > > int val = SO_TS_BINTIME; > setsockopt(fd, SOL_SOCKET, SO_TIMESTAMP, &val, sizeof(val)); > > Then we can also have SO_TS_MONOTONIC, SO_TS_UPTIME etc. > > That second approach would be a bit heavy on third-party apps that might > be using SO_BINTIME already, but some guards could be placed in to make > such software to blow up in a meaningful fashion when trying to use > SO_BINTIME. > > Third option would be to leave SO_BINTIME alone and just make SO_TIMESTAMP > accept some magic value as SO_TS_MONOTONIC. That is probably the easiest, > but also creates some documentation challenge to explain why mechanism for > requesting "bintime" variant is different from "monotonic". > > My preference would be (2), since SO_BINTIME is historic relic and it > should be just value for the SO_TIMESTAMP, not a separate option. > > Thanks! > > -Maxim > P.S. On somewhat unrelated note I've also noticed that tcp_var > uses u_short for its copy, is it my design or just some overlook? I don't > see why would we want to use two different types for essentially the same > thing. This is just calling for all sorts of weird bugs due to implied > sign(edness) of resulting expressions. > P.P.S. Please keep me on the CC, I am not subscribed to those two lists. >