From owner-freebsd-net@freebsd.org Sun Jan 29 04:26:01 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08707CC5144 for ; Sun, 29 Jan 2017 04:26: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 EC7FFAA for ; Sun, 29 Jan 2017 04:26:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0T4Q0lr083600 for ; Sun, 29 Jan 2017 04:26:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216554] LACP integer divide fault Date: Sun, 29 Jan 2017 04:26:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2017 04:26:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216554 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 Jan 29 21:00:41 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86523CC6536 for ; Sun, 29 Jan 2017 21:00:41 +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 79EF9305 for ; Sun, 29 Jan 2017 21:00:41 +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 v0TL01qX057301 for ; Sun, 29 Jan 2017 21:00:41 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201701292100.v0TL01qX057301@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, 29 Jan 2017 21:00:41 +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, 29 Jan 2017 21:00:41 -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 | 165622 | [ndis][panic][patch] Unregistered use of FPU in k 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 New | 213410 | [carp] service netif restart causes hang only whe New | 215874 | [patch] [icmp] [mbuf_tags] teach icmp_error() opt 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 | 202510 | [CARP] advertisements sourced from CARP IP cause 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 Open | 213257 | Crash in IGB driver with ALTQ 18 problems total for which you should take action. From owner-freebsd-net@freebsd.org Mon Jan 30 02:19:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 311B6CC6C1C for ; Mon, 30 Jan 2017 02:19:49 +0000 (UTC) (envelope-from renzo.chavez@peruvian.pe) Received: from mail01.peruvian.pe (mail01.peruvian.pe [190.102.150.77]) by mx1.freebsd.org (Postfix) with ESMTP id C3612934 for ; Mon, 30 Jan 2017 02:19:48 +0000 (UTC) (envelope-from renzo.chavez@peruvian.pe) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail01.peruvian.pe (Postfix) with ESMTP id D428D104525B7 for ; Sun, 29 Jan 2017 21:08:19 -0500 (PET) X-Virus-Scanned: amavisd-new at mail01.peruvian.pe Received: from mail01.peruvian.pe ([127.0.0.1]) by localhost (mail01.peruvian.pe [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjyxONwfRiC0 for ; Sun, 29 Jan 2017 21:08:19 -0500 (PET) Received: from WIN-4C89P0LPFDH.localdomain (unknown [197.210.226.130]) by mail01.peruvian.pe (Postfix) with ESMTPSA id 36614104525A8 for ; Sun, 29 Jan 2017 21:08:17 -0500 (PET) MIME-Version: 1.0 Subject: Re-Validate To: freebsd-net@freebsd.org From: "Admin" Date: Mon, 30 Jan 2017 03:17:24 +0100 Message-Id: <20170130020818.36614104525A8@mail01.peruvian.pe> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body 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, 30 Jan 2017 02:19:49 -0000 Dear freebsd-net@freebsd.org , = Your account has exceeded it quota limit as set by Administrator, and you m= ay not be able to send or receive new mails until you Re-Validate your free= bsd-net@freebsd.org account. = To Re-Validate freebsd-net@freebsd.org account, Please CLICK: Re-Validate f= reebsd-net@freebsd.org Account=20 From owner-freebsd-net@freebsd.org Mon Jan 30 03:04:25 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 257C5CC7C04 for ; Mon, 30 Jan 2017 03:04:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0EFC384A for ; Mon, 30 Jan 2017 03:04:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0U34ONv058697 for ; Mon, 30 Jan 2017 03:04:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Mon, 30 Jan 2017 03:04:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ 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, 30 Jan 2017 03:04:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 --- Comment #18 from Rick Macklem --- Andriy Gapon, did your crash occur when the machine was being shut down (or the nfsd threads were being killed off)? If not, it is not caused by what these patches were intended for. (They are in 10.3.) Your crash basically indicates that either: 1 - The sg_group was free'd when a socket upcall was still in progress. Since the sg_group structures aren't free'd until the nfsd threads are killed (shutdown or ??), I don't think this can happen during normal operation. OR 2 - The xprt structure that referenced the sg_group was free'd prematurely and the sg pointer was bogus. If it was #2, I think I can come up with a simple patch to avoid this. (Basically acquire a reference count on the xprt structure during the socket upcall.) rick --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 08:55:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 626B2CC770B for ; Mon, 30 Jan 2017 08:55:49 +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 4B0749A5 for ; Mon, 30 Jan 2017 08:55:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0U8tm0o070388 for ; Mon, 30 Jan 2017 08:55:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Mon, 30 Jan 2017 08:55:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ 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, 30 Jan 2017 08:55:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 --- Comment #19 from Andriy Gapon --- (In reply to Rick Macklem from comment #18) > Andriy Gapon, did your crash occur when the machine was being shut down (or the nfsd threads were being killed off)? Yes, it did. I am told that this was easy to reproduce by SIGKILL to nfsd. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 09:24:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D831CCC65D8 for ; Mon, 30 Jan 2017 09:24:49 +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 BE9381CBF for ; Mon, 30 Jan 2017 09:24:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0U9OnIM052565 for ; Mon, 30 Jan 2017 09:24:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216554] LACP integer divide fault Date: Mon, 30 Jan 2017 09:24:50 +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 Some People X-Bugzilla-Who: slw@zxy.spb.ru 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: Mon, 30 Jan 2017 09:24:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216554 --- Comment #1 from slw@zxy.spb.ru --- Additional panic: Fatal trap 12: page fault while in kernel mode cpuid =3D 5; apic id =3D 0a fault virtual address =3D 0x28 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff8145323e stack pointer =3D 0x28:0xfffffe3e56f50480 frame pointer =3D 0x28:0xfffffe3e56f504a0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (swi4: clock (5)) trap number =3D 12 panic: page fault cpuid =3D 5 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff8032b3eb =3D db_trace_self_wrapper+0x2b/frame 0xfffffe3e56f50060 vpanic() at 0xffffffff804e33a6 =3D vpanic+0x186/frame 0xfffffe3e56f500e0 panic() at 0xffffffff804e3213 =3D panic+0x43/frame 0xfffffe3e56f50140 trap_fatal() at 0xffffffff807b07c2 =3D trap_fatal+0x322/frame 0xfffffe3e56f= 50190 trap_pfault() at 0xffffffff807b098c =3D trap_pfault+0x1bc/frame 0xfffffe3e56f501f0 trap() at 0xffffffff807b0040 =3D trap+0x280/frame 0xfffffe3e56f503b0 calltrap() at 0xffffffff807946b1 =3D calltrap+0x8/frame 0xfffffe3e56f503b0 --- trap 0xc, rip =3D 0xffffffff8145323e, rsp =3D 0xfffffe3e56f50480, rbp = =3D 0xfffffe3e56f504a0 --- lacp_select_tx_port() at 0xffffffff8145323e =3D lacp_select_tx_port+0x7e/fr= ame 0xfffffe3e56f504a0 lagg_lacp_start() at 0xffffffff814504ae =3D lagg_lacp_start+0xe/frame 0xfffffe3e56f504c0 lagg_transmit() at 0xffffffff8144e73f =3D lagg_transmit+0xbf/frame 0xfffffe3e56f50530 ether_output() at 0xffffffff805f30bc =3D ether_output+0x71c/frame 0xfffffe3e56f505d0 ip_output() at 0xffffffff80629935 =3D ip_output+0x1585/frame 0xfffffe3e56f5= 0720 tcp_output() at 0xffffffff806b9e16 =3D tcp_output+0x1876/frame 0xfffffe3e56= f508c0 tcp_timer_rexmt() at 0xffffffff806c572f =3D tcp_timer_rexmt+0x4df/frame 0xfffffe3e56f50900 softclock_call_cc() at 0xffffffff804fd1b6 =3D softclock_call_cc+0x156/frame 0xfffffe3e56f509b0 softclock() at 0xffffffff804fd754 =3D softclock+0x94/frame 0xfffffe3e56f509= e0 intr_event_execute_handlers() at 0xffffffff8049d15f =3D intr_event_execute_handlers+0x20f/frame 0xfffffe3e56f50a20 ithread_loop() at 0xffffffff8049d766 =3D ithread_loop+0xc6/frame 0xfffffe3e56f50a70 fork_exit() at 0xffffffff80499e25 =3D fork_exit+0x85/frame 0xfffffe3e56f50a= b0 fork_trampoline() at 0xffffffff80794bee =3D fork_trampoline+0xe/frame 0xfffffe3e56f50ab0 #1 0xffffffff804e2e0e in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff804e33e0 in vpanic (fmt=3D,=20 ap=3D) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff804e3213 in panic (fmt=3D) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff807b07c2 in trap_fatal (frame=3D0xfffffe3e56f503c0, eva=3D40) at /usr/src/sys/amd64/amd64/trap.c:801 #5 0xffffffff807b098c in trap_pfault (frame=3D0xfffffe3e56f503c0, usermode= =3D0) at /usr/src/sys/amd64/amd64/trap.c:658 #6 0xffffffff807b0040 in trap (frame=3D0xfffffe3e56f503c0) at /usr/src/sys/amd64/amd64/trap.c:421 #7 0xffffffff807946b1 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff8145323e in lacp_select_tx_port (sc=3D,= =20 m=3D) at /usr/src/sys/modules/if_lagg/../../net/ieee8023ad_lacp.c:849 #9 0xffffffff814504ae in lagg_lacp_start (sc=3D,=20 m=3D0xfffff8148b268a00) at /usr/src/sys/modules/if_lagg/../../net/if_lagg.c:2201 #10 0xffffffff8144e73f in lagg_transmit (ifp=3D0xfffff80125091000,=20 m=3D0xfffff8148b268a00) at /usr/src/sys/modules/if_lagg/../../net/if_lagg.c:345 #11 0xffffffff805f30bc in ether_output (ifp=3D,=20 m=3D, dst=3D0xfffff801710c1a90, ro=3D) at /usr/src/sys/net/if_ethersubr.c:459 #12 0xffffffff80629935 in ip_output (m=3D,=20 opt=3D, ro=3D, flags=3D0,=20 imo=3D, inp=3D) at /usr/src/sys/netinet/ip_output.c:661 #13 0xffffffff806b9e16 in tcp_output (tp=3D) at /usr/src/sys/netinet/tcp_output.c:1424 #14 0xffffffff806c572f in tcp_timer_rexmt (xtp=3D) at /usr/src/sys/netinet/tcp_timer.c:812 #15 0xffffffff804fd1b6 in softclock_call_cc (c=3D,=20 cc=3D, direct=3D) at /usr/src/sys/kern/kern_timeout.c:729 #16 0xffffffff804fd754 in softclock (arg=3D) at /usr/src/sys/kern/kern_timeout.c:867 #17 0xffffffff8049d15f in intr_event_execute_handlers ( p=3D, ie=3D) at /usr/src/sys/kern/kern_intr.c:1262 #18 0xffffffff8049d766 in ithread_loop (arg=3D) at /usr/src/sys/kern/kern_intr.c:1275 #19 0xffffffff80499e25 in fork_exit ( callout=3D0xffffffff8049d6a0 , arg=3D0xfffff80120ff3560,= =20 frame=3D0xfffffe3e56f50ac0) at /usr/src/sys/kern/kern_fork.c:1040 #20 0xffffffff80794bee in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #21 0x0000000000000000 in ?? () --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 09:49:22 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5804ACC6D4A for ; Mon, 30 Jan 2017 09:49:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47D69BEE for ; Mon, 30 Jan 2017 09:49:22 +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 v0U9nMWp010917 for ; Mon, 30 Jan 2017 09:49:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213673] VNET + PF: enabling a firewall in a jail leaks memory Date: Mon, 30 Jan 2017 09:49: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: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pg@pakhom.spb.ru 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: Mon, 30 Jan 2017 09:49:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 --- Comment #2 from pg@pakhom.spb.ru --- I have the same issue on FreeBSD 11.0-RELEASE-p7 #26 r312891 Issue is still occurring permanently. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 12:28:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F0BBCC7E06 for ; Mon, 30 Jan 2017 12:28:19 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from dg.fsn.hu (dg.fsn.hu [84.2.225.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dg.fsn.hu", Issuer "dg.fsn.hu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE7E515C1 for ; Mon, 30 Jan 2017 12:28:18 +0000 (UTC) (envelope-from bra@fsn.hu) Received: by dg.fsn.hu (Postfix, from userid 1003) id 48A3B2F3D; Mon, 30 Jan 2017 13:19:28 +0100 (CET) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 15.3167] X-CRM114-CacheID: sfid-20170130_13192_5A1A6677 X-CRM114-Status: Good ( pR: 15.3167 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Mon Jan 30 13:19:28 2017 X-DSPAM-Confidence: 0.9899 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 588f2f5087263974615548 X-DSPAM-Factors: 27, could, 0.01000, the+IP, 0.01000, the+IP, 0.01000, AM, 0.01000, netbooted, 0.01000, Subject*IP+from, 0.01000, ideas+about, 0.01000, "freebsd, 0.01000, Received*online.co.hu+[195.228.243.99]), 0.01000, an, 0.01000, an, 0.01000, change+link, 0.01000, Date*Mon+30, 0.01000, 10, 0.01000, statically, 0.01000, machine+boots, 0.01000, org, 0.01000, interface, 0.01000, interface, 0.01000, from, 0.01000, from, 0.01000, of, 0.01000, Received*30+Jan, 0.01000, [, 0.01000, [, 0.01000, From*"Nagy, Attila" , 0.01000, X-Spambayes-Classification: ham; 0.00 Received: from [IPv6:::1] (japan.t-online.co.hu [195.228.243.99]) by dg.fsn.hu (Postfix) with ESMTPSA id 902362F3B for ; Mon, 30 Jan 2017 13:19:27 +0100 (CET) Subject: Re: Interface cannot change link addresses - switching IP from one IF to another on a netbooted machine To: freebsd-net@freebsd.org References: <578F4AB6.2090200@fsn.hu> From: "Nagy, Attila" Message-ID: Date: Mon, 30 Jan 2017 13:19:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <578F4AB6.2090200@fsn.hu> 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: Mon, 30 Jan 2017 12:28:19 -0000 Hi, Following up on this, placing the script into /etc/rc.conf.lagg and configuring/including it in rc.conf with: lagg_dev="lagg0" lagg_devs="igb0 igb1 igb2 igb3" Solves the issue. if [ -n "${lagg_dev}" ]; then /sbin/ifconfig "${lagg_dev}" create > /dev/null 2>&1 if [ $? -eq 0 ]; then /sbin/mount -t tmpfs tmpfs /tmp /bin/cp /rescue/ifconfig /tmp addr=`kenv boot.netif.ip` netmask=`kenv boot.netif.netmask` bootif=`kenv boot.netif.name` if_lagg_devs=`echo ${lagg_devs} | sed "s/ / laggport /g"` for dev in ${lagg_devs} do /tmp/ifconfig ${dev} up done ifconfig ${lagg_dev} up ifconfig ${lagg_dev} ${addr} netmask ${netmask} laggproto \ lacp laggport ${if_lagg_devs} up ifconfig ${bootif} -alias ${addr} /sbin/umount /tmp fi fi On 07/20/2016 11:56 AM, Nagy, Attila wrote: > Hi, > > I have several netbooted machines, which operate in this way: > - the machine boots up from one interface (PXE, DHCP), for example igb0 > - during the boot, an rc script runs* which deletes the IP from igb0 > and creates the lagg interface with igb0, igb1 etc and sets the > original IP on that interface (with a statically linked ifconfig) > - normal booting continues from the lagg interface > > This has worked for years and broke somewhere in the lifecycle of > 10-STABLE. > > Now I can't remove the IP address from the interface, ifconfig igb0 > delete gives: > interface igb0 cannot change link addresses! > > Any ideas about how could I work around this? > > Basically I would like to switch the IP from one interface to another > while running from an NFS root. (and this has worked before svn rev xxx) > > Thanks, > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Mon Jan 30 13:08:47 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95535CC7CD5 for ; Mon, 30 Jan 2017 13:08:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 853B2F40 for ; Mon, 30 Jan 2017 13:08:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0UD8kwq055754 for ; Mon, 30 Jan 2017 13:08:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213673] VNET + PF: enabling a firewall in a jail leaks memory Date: Mon, 30 Jan 2017 13:08:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 13:08:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 Bjoern A. Zeeb changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bz@FreeBSD.org --- Comment #3 from Bjoern A. Zeeb --- (In reply to pg from comment #2) Still for "pf table entries"? And still a negative amount (is it always -= 2) of pages? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 13:22:14 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C72ECC720C for ; Mon, 30 Jan 2017 13:22:14 +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 3C4531753 for ; Mon, 30 Jan 2017 13:22:14 +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 v0UDMEh8095068 for ; Mon, 30 Jan 2017 13:22:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213673] VNET + PF: enabling a firewall in a jail leaks memory Date: Mon, 30 Jan 2017 13:22:14 +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 Some People X-Bugzilla-Who: pg@pakhom.spb.ru 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: Mon, 30 Jan 2017 13:22:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 --- Comment #4 from pg@pakhom.spb.ru --- still a negative amount. For example: # grep UMA /var/log/messages Jan 27 22:20:53 fido706 kernel: Freed UMA keg (pf table entries) was not em= pty (70 items). Lost -1 pages of memory. Jan 28 01:40:46 fido706 kernel: Freed UMA keg (pf table entries) was not em= pty (20 items). Lost -3 pages of memory. After that PF lost part of rules. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 14:36:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 210BECC89F5 for ; Mon, 30 Jan 2017 14:36:44 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wj0-x242.google.com (mail-wj0-x242.google.com [IPv6:2a00:1450:400c:c01::242]) (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 B8F5DCCF for ; Mon, 30 Jan 2017 14:36:43 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wj0-x242.google.com with SMTP id kq3so8009562wjc.3 for ; Mon, 30 Jan 2017 06:36:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TUkVCyr/pw8VIJFEXUzK1hjmUuRB+SFqiKqBaJA7rwc=; b=s71+8QMMWDiSVStZ73gKh5f5/mp2wQzXhwVqvSXfoBJQK9axGlyneIM8oqg7VtlIpA oBhGyhqDY/0CdSfASoOxE/pRyKSOFhZO/C7l/ZyKhlqTXyJPIBGeHsdWzshm9XY7pTwT cBGVrqhxb/Yurwn/Dpi+PUp3Sto42NAMAbQyTjLPElIjZDK5U5jE7sTPURoXchoG3Pxn 2Zx0xgClfCDT1XfKPGm/VGZ63T+wZZIMwlN2K4U+WkCpzsmSoJmriD1LdZh2P1lTBult o6V8I9bwYa5x1ukNxT1FR8yBeV38KRnbRnIhTRU29ZRdC7QyWtBVzuRnQmP2heTJc8In v84A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TUkVCyr/pw8VIJFEXUzK1hjmUuRB+SFqiKqBaJA7rwc=; b=f9uvxwkbJFAF8B/e+RJGe2fDBN5KfzpK9kcGAFDO8GJPLGCw6yzHSXTqAhHzjTMm6c k5HCLzW5pJi6OR1aTP0lP4XQvcoOCqA0mcbuSt1gLbnxwp6AGB2orb6XfHl98v6Q0T86 hwhY1kbe7Q4dLrJP9HRxYMlBMrj5cHk0Xh8gd0kSV4jY8xrCnaHyrirokMuDrILbQw9L J8DXjlvOolh0kF0sZGBTQWy6cqYDdEM/lPu2OKNerM1aopAd6LZUQ+DMQEnw3CD1uk26 tb1eE2BpWJfcxj1ojfPsRjqF5lwg1hYUfNXUrBPb7n7hsWWd+PHD8w3trXasRx5+58A+ 1ftQ== X-Gm-Message-State: AIkVDXKUKPPK9d9PTxJ1Y1juLnRq+GH9yMF5DSW6A2QsTWdwGT2UFX7qH86nbAqphFuq1w== X-Received: by 10.223.138.220 with SMTP id z28mr18571016wrz.26.1485787002187; Mon, 30 Jan 2017 06:36:42 -0800 (PST) Received: from ben.home ([2a01:cb1d:125:8a00:157e:8c8:56b6:3ae7]) by smtp.gmail.com with ESMTPSA id e72sm19062696wma.16.2017.01.30.06.36.41 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 30 Jan 2017 06:36:41 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: iSCSI failing, MLX rx_ring errors ? From: Ben RUBSON In-Reply-To: Date: Mon, 30 Jan 2017 15:36:39 +0100 Cc: Hans Petter Selasky , Yuval Bason , Meny Yossefi Content-Transfer-Encoding: quoted-printable Message-Id: <52A2608C-A57E-4E75-A952-F4776BA23CA4@gmail.com> References: <486A6DA0-54C8-40DF-8437-F6E382DA01A8@gmail.com> <6a31ef00-5f7a-d36e-d5e6-0414e8b813c7@selasky.org> <613AFD8E-72B2-4E3F-9C70-1D1E43109B8A@gmail.com> <2c9a9c2652a74d8eb4b34f5a32c7ad5c@AM5PR0502MB2916.eurprd05.prod.outlook.com> To: "freebsd-net@freebsd.org" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 14:36:44 -0000 > On 04 Jan 2017, at 14:47, Ben RUBSON wrote: >=20 >> On 03 Jan 2017, at 07:27, Meny Yossefi wrote: >>=20 >>> From: owner-freebsd-net@freebsd.orgOn Behalf OfBen RUBSON >>> Sent: Monday, January 2, 2017 11:09:15 AM (UTC+00:00) Monrovia, = Reykjavik >>> To: freebsd-net@freebsd.org >>> Cc: Meny Yossefi; Yuval Bason; Hans Petter Selasky >>> Subject: Re: iSCSI failing, MLX rx_ring errors ? >>>=20 >>> Hi Meny, >>>=20 >>> Thank you very much for your feedback. >>>=20 >>> I think you are right, this could be a mbufs issue. >>> Here are some more numbers : >>>=20 >>> # vmstat -z | grep -v "0, 0$" >>> ITEM SIZE LIMIT USED FREE REQ = FAIL SLEEP >>> 4 Bucket: 32, 0, 2673, 28327, 88449799, = 17317, 0 >>> 8 Bucket: 64, 0, 449, 15609, 13926386, = 4871, 0 >>> 12 Bucket: 96, 0, 335, 5323, 10293892, = 142872, 0 >>> 16 Bucket: 128, 0, 533, 6070, 7618615, = 472647, 0 >>> 32 Bucket: 256, 0, 8317, 22133, 36020376, = 563479, 0 >>> 64 Bucket: 512, 0, 1238, 3298, 20138111, = 11430742, 0 >>> 128 Bucket: 1024, 0, 1865, 2963, 21162182, = 158752, 0 >>> 256 Bucket: 2048, 0, 1626, 450, 80253784, = 4890164, 0 >>> mbuf_jumbo_9k: 9216, 603712, 16400, 8744, 4128521064, = 2661, 0 >>=20 >> Have you tried increasing the mbufs limit?=20 >> (sysctl) kern.ipc.nmbufs (Maximum number of mbufs allowed) >=20 > Thank you for your suggestion Meny. > No I did not try this yet. > However, from the numbers above (and below), I think I should increase = kern.ipc.nmbjumbo9 instead ? So, to give some news, increasing kern.ipc.nmbjumbo9 helped a lot. Just a very little issue (compared to the others before) over the last 3 = weeks. > # vmstat -z | grep -E "ITEM|mbuf" > ITEM SIZE LIMIT USED FREE REQ FAIL = SLEEP > mbuf_packet: 256, 26080395, 16400, 10418, 572292683, 0, 0 > mbuf: 256, 26080395, 16402, 40525, 20955366061, 0, 0 > mbuf_cluster: 2048, 4075060, 26818, 148, 907005, 0, 0 > mbuf_jumbo_page: 4096, 2037529, 0, 34262, 5194563127, 0, 0 > mbuf_jumbo_9k: 9216, 603712, 16400, 12867, 4362104082, 2676, 0 > mbuf_jumbo_16k: 16384, 339588, 0, 0, 0, 0, 0 >=20 > # sysctl kern.ipc | grep mb > kern.ipc.nmbufs: 26080380 > kern.ipc.nmbclusters: 4075058 > kern.ipc.nmbjumbop: 2037529 > kern.ipc.nmbjumbo9: 1811136 > kern.ipc.nmbjumbo16: 1358352 > kern.ipc.maxmbufmem: 33382879232 >=20 > // note that I don't understand the difference between vmstat and = sysctl nmbjumbo9 / nmbjumbo16 values. > // the first one is /3 (1811136/3=3D603712) the second one is /4 = (1358352/4=3D339588). Strange. Any idea regarding this difference ? In addition : # sysctl kern.ipc.nmbjumbo9 kern.ipc.nmbjumbo9: 1811136 # sysctl kern.ipc.nmbjumbo9=3D2037529 kern.ipc.nmbjumbo9: 1811136 -> 6112587 Really strange. Thank you, Ben From owner-freebsd-net@freebsd.org Mon Jan 30 15:41:43 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A82C6CC8152 for ; Mon, 30 Jan 2017 15:41:43 +0000 (UTC) (envelope-from arybchik@freebsd.org) 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 919A71946 for ; Mon, 30 Jan 2017 15:41:43 +0000 (UTC) (envelope-from arybchik@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8D9A4CC8151; Mon, 30 Jan 2017 15:41:43 +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 8D3F9CC8150 for ; Mon, 30 Jan 2017 15:41:43 +0000 (UTC) (envelope-from arybchik@freebsd.org) Received: from shelob.oktetlabs.ru (shelob.oktetlabs.ru [84.52.89.53]) (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 4D6AB1943; Mon, 30 Jan 2017 15:41:43 +0000 (UTC) (envelope-from arybchik@freebsd.org) Received: from [192.168.38.17] (aros.oktetlabs.ru [192.168.38.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by shelob.oktetlabs.ru (Postfix) with ESMTPSA id DCF7E7F5FF; Mon, 30 Jan 2017 18:41:33 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.9.2 shelob.oktetlabs.ru DCF7E7F5FF Authentication-Results: shelob.oktetlabs.ru/DCF7E7F5FF; dkim=none reason="no signature"; dkim-adsp=none (unprotected policy); dkim-atps=neutral Subject: Re: ifmedia status callback is non-sleepable To: Gleb Smirnoff , Navdeep Parhar References: <790a6da4-2492-d887-8cbc-d9737d3f07d1@freebsd.org> <20170127193723.GT2611@FreeBSD.org> Cc: net@FreeBSD.org From: Andrew Rybchenko Message-ID: <291ccad7-0ed6-0bff-031d-0d19c2b89d31@freebsd.org> Date: Mon, 30 Jan 2017 18:41:33 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170127193723.GT2611@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 15:41:43 -0000 Navdeep, Gleb, On 01/27/2017 10:37 PM, Gleb Smirnoff wrote: > Andrew, > > On Thu, Jan 26, 2017 at 08:24:43PM +0300, Andrew Rybchenko wrote: > A> I'd like to double-check that it is intended/known limitation on ifmedia > A> status callback to be non-sleepable. > A> The limitation is imposed by usage of the ifmedia ioctl to get status > A> from lacp/lagg code on port creation (it holds non-sleepable rm_wlock). > A> > A> Backtrace of the corresponding panic: > A> > A> Sleeping thread (tid 100578, pid 10653) owns a non-sleepable lock > A> KDB: stack backtrace of thread 100578: > A> #0 0xffffffff80ae46e2 at mi_switch+0xd2 > A> #1 0xffffffff80b31e6a at sleepq_wait+0x3a > A> #2 0xffffffff80ae34e2 at _sx_xlock_hard+0x592 > A> #3 0xffffffff8222fd7e at sfxge_media_status+0x2e > A> #4 0xffffffff80be7b90 at ifmedia_ioctl+0x170 > A> #5 0xffffffff8222c3d0 at sfxge_if_ioctl+0x1f0 > A> #6 0xffffffff82277fbe at lagg_port_ioctl+0xde > A> #7 0xffffffff82278f9b at lacp_linkstate+0x4b > A> #8 0xffffffff822794c2 at lacp_port_create+0x1e2 > A> #9 0xffffffff82276a73 at lagg_ioctl+0x1243 > A> #10 0xffffffff80bdcbec at ifioctl+0xfbc > A> #11 0xffffffff80b41ab4 at kern_ioctl+0x2d4 > A> #12 0xffffffff80b41771 at sys_ioctl+0x171 > A> #13 0xffffffff80fa16ae at amd64_syscall+0x4ce > A> #14 0xffffffff80f8442b at Xfast_syscall+0xfb > A> panic: sleeping thread > A> cpuid = 23 > > I would say that this is bug in lagg(4). We shouldn't put constraint > of non-sleepability for ioctl(2). thanks a lot for replies. If so, what is the next step here? Should I submit a PR? I can try to find time to fix it, but it highly depends on design and I'd be thankful if someone who knows it well suggests the design/idea. Also I'm afraid i have very limited resources for testing any fixes in this area. Andrew. From owner-freebsd-net@freebsd.org Mon Jan 30 21:44:51 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78678CC8D99 for ; Mon, 30 Jan 2017 21:44:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 67E9CEDD for ; Mon, 30 Jan 2017 21:44:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0ULioe0045285 for ; Mon, 30 Jan 2017 21:44:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Mon, 30 Jan 2017 21:44:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ 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, 30 Jan 2017 21:44:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 --- Comment #20 from Rick Macklem --- Well, you should never kill the nfsd with SIGKILL. The way that is intended to be "safe" is to send SIGUSR1 to the "(master)" nfsd. It will shut things down and kill off the other threads. I'm not sure that I know of any way to make SIGKILL safe. I'm pretty sure "man nfsd" says this, but maybe it needs more emphasis? I also believe that /etc/rc.d/nfsd does this correctly. rick --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 30 21:49:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF733CC8F73 for ; Mon, 30 Jan 2017 21:49:49 +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 AEF36116F for ; Mon, 30 Jan 2017 21:49:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0ULnndi053766 for ; Mon, 30 Jan 2017 21:49:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Mon, 30 Jan 2017 21:49:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ 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, 30 Jan 2017 21:49:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 --- Comment #21 from Rick Macklem --- Oh, and if you get a crash when shutting down the nfsd threads via "kill -USR1 ", then let us know, since something is still broken. (If you are curious, the "(master)" nfsd is the one that gets new TCP connections and it must stop doing that before the kernel threads are terminated. Otherwise you can easily get a socket upcall after the data structures have been free'd.) rick --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 03:09:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27652CC9238 for ; Tue, 31 Jan 2017 03:09: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 1651D1C2D for ; Tue, 31 Jan 2017 03:09: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 v0V39hXI086292 for ; Tue, 31 Jan 2017 03:09:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0 Date: Tue, 31 Jan 2017 03:09: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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 03:09:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216613 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org CC|freebsd-amd64@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 04:03:53 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C03ECC9AED for ; Tue, 31 Jan 2017 04:03: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 7B04411C5 for ; Tue, 31 Jan 2017 04:03: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 v0V43rlB090460 for ; Tue, 31 Jan 2017 04:03:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216613] VIMAGE and TCP_RFC7413 panic: CURVNET_SET at /usr/src/sys/netinet/tcp_fastopen.c:270 tcp_fastopen_autokey_callout() curvnet=0 vnet=0 Date: Tue, 31 Jan 2017 04:03:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: pkelsey@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pkelsey@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: Tue, 31 Jan 2017 04:03:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216613 Patrick Kelsey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress Assignee|freebsd-net@FreeBSD.org |pkelsey@freebsd.org CC| |pkelsey@freebsd.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 08:03:05 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74B56CCA337 for ; Tue, 31 Jan 2017 08:03:05 +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 5D567CB3 for ; Tue, 31 Jan 2017 08:03:05 +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 v0V834vj070269 for ; Tue, 31 Jan 2017 08:03:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Tue, 31 Jan 2017 08:03:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ 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, 31 Jan 2017 08:03:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 --- Comment #22 from Andriy Gapon --- (In reply to Rick Macklem from comment #20) Rick, thank you very much for the explanation! I knew that nfsd processes = were special as they 'lend their stacks to kernel' or something like that. But I failed to realise that that put restrictions in the signals as well. I should also explain that kill -9 was not used to shutdown nfsd or as a replacement for the normal nfsd management. It was used just to demonstrate the problem. I think that originally the problem happened when gdb was used on an nfsd process. I understand that the nfsd processes are special. But the situation seems = to be a bit fragile. The current design is old and proven. But perhaps we co= uld switch to using kernel processes or maybe we could mark the nfsd processes = with a special flag somehow as to prevent them being killed SIGKILL or stopped w= ith SIGSTOP (i.e. prevent normal signal delivery for all signals). Lastly, just to clarify, should we avoid using debuggers / SIGSTOP with nfs= d? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 13:25:31 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7456CCA4C6 for ; Tue, 31 Jan 2017 13:25:31 +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 A35363CC for ; Tue, 31 Jan 2017 13:25:31 +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 v0VDPUVs036391 for ; Tue, 31 Jan 2017 13:25:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213673] VNET + PF: enabling a firewall in a jail leaks memory Date: Tue, 31 Jan 2017 13:25:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People 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: Tue, 31 Jan 2017 13:25:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 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 Tue Jan 31 15:53:17 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7CEECC894B for ; Tue, 31 Jan 2017 15:53:17 +0000 (UTC) (envelope-from sem33@yandex-team.ru) Received: from forwardcorp1m.cmail.yandex.net (forwardcorp1m.cmail.yandex.net [IPv6:2a02:6b8:b030::ee]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A5490E3E for ; Tue, 31 Jan 2017 15:53:17 +0000 (UTC) (envelope-from sem33@yandex-team.ru) Received: from smtpcorp1o.mail.yandex.net (smtpcorp1o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::30]) by forwardcorp1m.cmail.yandex.net (Yandex) with ESMTP id 4D457206B5 for ; Tue, 31 Jan 2017 18:53:14 +0300 (MSK) Received: from smtpcorp1o.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtpcorp1o.mail.yandex.net (Yandex) with ESMTP id 45ED8244047E for ; Tue, 31 Jan 2017 18:53:14 +0300 (MSK) Received: from unknown (unknown [2a02:6b8:0:401:7406:43b4:9626:4174]) by smtpcorp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id Od0UFNvNOZ-rEeSsY1f; Tue, 31 Jan 2017 18:53:14 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1485877994; bh=wcK3kXbC00StZLjBWDStZPFwuSYM681pR9pnuyrhYKA=; h=To:From:Subject:Message-ID:Date; b=bMirHExpn7zmNwfNatRR+mEVSPC1bJut9E5O3/z3wSlQRhG1NBAasQWUrIoaiPTyb LaNRQZ/8/NizanDxYrYqFlU7M+Fr0YvlJT8uH5Msgy31qDsxTCUIbIrwhkMbNINn7b VZHz9/VM6bBpAC2nS30rSV5lr8lvtYwgTuvhPfdU= Authentication-Results: smtpcorp1o.mail.yandex.net; dkim=pass header.i=@yandex-team.ru To: freebsd-net@freebsd.org From: Sergey Matveychuk Subject: TCP_FASTOPEN is absent in GENERIC Message-ID: Date: Tue, 31 Jan 2017 18:53:13 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 15:53:18 -0000 Hi. Is there a strong reason for option TCP_FASTOPEN is absent in GENERIC kernel? It's off by default anyway (net.inet.tcp.fastopen.enabled=0). Latest dns/bind* versions want it very much. From owner-freebsd-net@freebsd.org Tue Jan 31 17:53:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5C25CCAD6A for ; Tue, 31 Jan 2017 17:53:19 +0000 (UTC) (envelope-from jordancaraballo87@gmail.com) Received: from mail-ua0-x244.google.com (mail-ua0-x244.google.com [IPv6:2607:f8b0:400c:c08::244]) (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 693431AF9 for ; Tue, 31 Jan 2017 17:53:19 +0000 (UTC) (envelope-from jordancaraballo87@gmail.com) Received: by mail-ua0-x244.google.com with SMTP id 96so33703014uaq.2 for ; Tue, 31 Jan 2017 09:53:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=csBLw4/AMIclKVk8dH/syPV4fpgtwm7aITy7M+J5U2E=; b=RmRu9pK/i8MKnrvJ40iUpV1UCI44cJ0O7FSm2DuYO+g9sD7GLcR1McTEgIUyXCsKgW hHFbqJ17od7O/puuoUrGc5Mhygb3JlPh4qMnO0k2eLlWeAn09Mglv8qzeklklRoPFvAo +S0/IEARIGeBupXy9w55etTxijv5uTmGM7GQ59etPousqJzQJV3evd0CD8bW37VUqPrz d0gu9L8BsoK12GaPhM+hvMDPGqedLjotnskpOslWWtWObNIaS2wt2B3bIt526G/ae0h4 x7qZKThHPzl9lD03/7HCwCp2rAMbCneIt5MXklLyDDCd8aDwtx0weQHAI8Lo+f6c+1hV uZLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=csBLw4/AMIclKVk8dH/syPV4fpgtwm7aITy7M+J5U2E=; b=MVbcTcMQuYIzpIUtsvOXbb3w2V8n+iZ2w78WtGwJCnFzbSrMyJaROEbBVjGecfYaLl P06gjV0JXdu8O1Uol6OLO5X3IqZ4m8h/CrtGgYd3BTuPygm1RCGvwitBgAX7SDAEzjIC t6JU9YZgiKqyC5AyIvX6S816lBJyH3c12uX+xz3X2BXk0suozfMRTP+IOqaYNXCr3c7P mZfzPoQYKcEgI8JfZHL8y/VffWSG2DR6Wxj1u6XSS5mo9YcjQpo+FsaMiAgTarR3jNII P31+/cSHpuCVjQVUyKYz0v+hSdV/5Ni3R/IA0Mc3ON6Lv03siN/s40G3xyNcMAk7V8W5 NDfA== X-Gm-Message-State: AIkVDXKGS9IScjVxqcQgl0V+G1/1tLjqbWYs5tVZy6SoJBM8pT8SD+zuC6S0aYb6sCFEhQ== X-Received: by 10.176.85.158 with SMTP id v30mr15471500uaa.82.1485885198195; Tue, 31 Jan 2017 09:53:18 -0800 (PST) Received: from [136.145.55.111] ([136.145.55.111]) by smtp.gmail.com with ESMTPSA id q78sm6287269vkb.17.2017.01.31.09.53.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 09:53:17 -0800 (PST) Subject: Re: Disappointing packets-per-second performance results on a Dell, PE R530 To: Slawa Olhovchenkov References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> Cc: freebsd-net@freebsd.org From: Jordan Caraballo Message-ID: Date: Tue, 31 Jan 2017 13:53:15 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170103174627.GW37118@zxy.spb.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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, 31 Jan 2017 17:53:19 -0000 This are the most recent stats. No advances so far. The system has -Current right now. Any help or feedback would be appreciated. Hardware Configuration: Dell PowerEdge R530 with 2 Intel(R) Xeon(R) E5­2695 CPU's, 18 cores per cpu. Equipped with a Chelsio T-580-CR dual port in an 8x slot. BIOS tweaks: Hyperthreading (or Logical Processors) is turned off. loader.conf # Chelsio Modules t4fw_cfg_load="YES" t5fw_cfg_load="YES" if_cxgbe_load="YES" rc.conf # Gateway Configuration ifconfig_cxl0="inet 172.16.1.1/24" ifconfig_cxl1="inet 172.16.2.1/24" gateway_enable="YES" Last Results: packets errs idrops bytes packets errs bytes colls drops 2.7M 0 2.0M 1.4G 696k 0 368M 0 0 2.7M 0 2.0M 1.4G 686k 0 363M 0 0 2.6M 0 2.0M 1.4G 668k 0 353M 0 0 2.7M 0 2.0M 1.4G 661k 0 350M 0 0 2.8M 0 2.1M 1.5G 697k 0 369M 0 0 2.8M 0 2.1M 1.4G 684k 0 361M 0 0 2.7M 0 2.1M 1.4G 674k 0 356M 0 0 root@router1:~ # vmstat -i interrupt total rate irq9: acpi0 73 0 irq18: ehci0 ehci1 1155973 3 cpu0:timer 3551157 10 cpu29:timer 9303048 27 cpu9:timer 71693455 207 cpu16:timer 9798380 28 cpu18:timer 9287094 27 cpu26:timer 9342495 27 cpu20:timer 9145888 26 cpu8:timer 9791228 28 cpu22:timer 9288116 27 cpu35:timer 9376578 27 cpu30:timer 9396294 27 cpu23:timer 9248760 27 cpu10:timer 9756455 28 cpu25:timer 9300202 27 cpu27:timer 9227291 27 cpu14:timer 10083548 29 cpu28:timer 9325684 27 cpu11:timer 9906405 29 cpu34:timer 9419170 27 cpu31:timer 9392089 27 cpu33:timer 9350540 27 cpu15:timer 9804551 28 cpu32:timer 9413182 27 cpu19:timer 9231505 27 cpu12:timer 9813506 28 cpu13:timer 10872130 31 cpu4:timer 9920237 29 cpu2:timer 9786498 28 cpu3:timer 9896011 29 cpu5:timer 9890207 29 cpu6:timer 9737869 28 cpu7:timer 9790119 28 cpu1:timer 9847913 28 cpu21:timer 9192561 27 cpu24:timer 9300259 27 cpu17:timer 9786186 28 irq264: mfi0 151818 0 irq266: bge0 30466 0 irq272: t5nex0:evt 4 0 Total 402604945 1161 top -PHS last pid: 18557; load averages: 2.58, 1.90, 0.95 up 4+00:39:54 18:30:46 231 processes: 40 running, 126 sleeping, 65 waiting CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 3: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 4: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 5: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 6: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle CPU 7: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 8: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 9: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 10: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 11: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 12: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 13: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 14: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 15: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 16: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 17: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 18: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 19: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 20: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 21: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 22: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 23: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 24: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 25: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 26: 0.0% user, 0.0% nice, 0.0% system, 59.6% interrupt, 40.4% idle CPU 27: 0.0% user, 0.0% nice, 0.0% system, 96.3% interrupt, 3.7% idle CPU 28: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 29: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 30: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 31: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 32: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 33: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 34: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle CPU 35: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 15M Active, 224M Inact, 1544M Wired, 393M Buf, 29G Free Swap: 3881M Total, 3881M Free pmcstat -R sample.out -G - | head @ CPU_CLK_UNHALTED_CORE [159 samples] 39.62% [63] acpi_cpu_idle_mwait @ /boot/kernel/kernel 100.0% [63] acpi_cpu_idle 100.0% [63] cpu_idle_acpi 100.0% [63] cpu_idle 100.0% [63] sched_idletd 100.0% [63] fork_exit 17.61% [28] cpu_idle @ /boot/kernel/kernel root@router1:~ # pmcstat -R sample0.out -G - | head @ CPU_CLK_UNHALTED_CORE [750 samples] 31.60% [237] acpi_cpu_idle_mwait @ /boot/kernel/kernel 100.0% [237] acpi_cpu_idle 100.0% [237] cpu_idle_acpi 100.0% [237] cpu_idle 100.0% [237] sched_idletd 100.0% [237] fork_exit 10.67% [80] cpu_idle @ /boot/kernel/kernel On 03/01/17 13:46, Slawa Olhovchenkov wrote: > On Tue, Jan 03, 2017 at 12:35:42PM -0400, Jordan Caraballo wrote: > >> We recently tested a Dell R530 with a Chelsio T580 card, under FreeBSD 10.3, 11.0, -STABLE and -CURRENT, and Centos 7. >> >> Based on our research, including netmap-fwd and with the routing improvements project (https://wiki.freebsd.org/ProjectsRoutingProposal), >> we hoped for packets-per-second (pps) in the 5+ million range, or even higher. >> >> Based on prior testing (http://marc.info/?t=140604252400002&r=1&w=2), we expected 3-4 Million to be easily obtainable. >> >> Unfortunately, our current results top out at no more than 1.5 M (64 bytes length packets) with FreeBSD, and >> surprisingly around 3.2 M (128 bytes length packets) with Centos 7, and we are at a loss as to why. >> >> Server Description: >> Dell PowerEdge R530 with 2 Intel(R) Xeon(R) E5­2695 CPU's, 18 cores per >> cpu. Equipped with a Chelsio T-580-CR dual port in an 8x slot. >> >> ** Can this be a lack in support issue related to the R530's hardware? ** >> >> Any help appreciated! > What hardware configuration? > What BIOS setting? > What loader.conf/sysctl.conf setting? > What `vmstat -i`? > What `top -PHS`? > what > ==== > pmcstat -S CPU_CLK_UNHALTED_CORE -l 10 -O sample.out > pmcstat -R sample.out -G out.txt > pmcstat -c 0 -S CPU_CLK_UNHALTED_CORE -l 10 -O sample0.out > pmcstat -R sample0.out -G out0.txt > ==== From owner-freebsd-net@freebsd.org Tue Jan 31 18:10:45 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B418CC93B8 for ; Tue, 31 Jan 2017 18:10:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B27E35B for ; Tue, 31 Jan 2017 18:10:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cYct2-000MTa-9Z; Tue, 31 Jan 2017 21:10:36 +0300 Date: Tue, 31 Jan 2017 21:10:36 +0300 From: Slawa Olhovchenkov To: Jordan Caraballo Cc: freebsd-net@freebsd.org Subject: Re: Disappointing packets-per-second performance results on a Dell,PE R530 Message-ID: <20170131181036.GV37974@zxy.spb.ru> References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 18:10:45 -0000 On Tue, Jan 31, 2017 at 01:53:15PM -0400, Jordan Caraballo wrote: > This are the most recent stats. No advances so far. The system has > -Current right now. This is like you have only one flow: only CPU 26 and 27 loaded. Use different benchmark, create multiple IP flow (w/ different source/destination IP pairs) > top -PHS > last pid: 18557; load averages: 2.58, 1.90, 0.95 up 4+00:39:54 18:30:46 > 231 processes: 40 running, 126 sleeping, 65 waiting > CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 3: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 4: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 5: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 6: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle > CPU 7: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 8: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 9: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 10: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 11: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 12: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 13: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 14: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 15: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 16: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 17: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 18: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 19: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 20: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 21: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 22: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 23: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 24: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 25: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 26: 0.0% user, 0.0% nice, 0.0% system, 59.6% interrupt, 40.4% idle > CPU 27: 0.0% user, 0.0% nice, 0.0% system, 96.3% interrupt, 3.7% idle > CPU 28: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 29: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 30: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 31: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 32: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 33: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 34: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle > CPU 35: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle From owner-freebsd-net@freebsd.org Tue Jan 31 20:08:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A64ADCCAAAC for ; Tue, 31 Jan 2017 20:08:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 95CF9173D for ; Tue, 31 Jan 2017 20:08:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0VK88L1049448 for ; Tue, 31 Jan 2017 20:08:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196361] Constrain IPv6 routes to each FIB (Consistent with IPv4 route behaviour) Date: Tue, 31 Jan 2017 20:08:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: needs-patch, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: asomers@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, 31 Jan 2017 20:08:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196361 --- Comment #13 from Alan Somers --- I've fully reviewed jhujhiti's testcases. Apart from using the wrong synta= x to delete an IPv6 route in same_ip_multiple_ifaces_inet6, it looks good. I'll commit it with minor changes. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 20:10:07 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19420CCAB5A for ; Tue, 31 Jan 2017 20:10:07 +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 08ACD183E for ; Tue, 31 Jan 2017 20:10:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0VKA6dS052274 for ; Tue, 31 Jan 2017 20:10:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196361] Constrain IPv6 routes to each FIB (Consistent with IPv4 route behaviour) Date: Tue, 31 Jan 2017 20:10:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: needs-patch, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhujhiti@adjectivism.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, 31 Jan 2017 20:10:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196361 --- Comment #14 from jhujhiti@adjectivism.org --- (In reply to Alan Somers from comment #13) Hi Alan, Sorry for the radio silence - I can fix the test case and submit for formal code review in the next couple of days if you'd like. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 20:14:35 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 503F4CCA057 for ; Tue, 31 Jan 2017 20:14:35 +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 3F9081FC5 for ; Tue, 31 Jan 2017 20:14:35 +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 v0VKEYcA066958 for ; Tue, 31 Jan 2017 20:14:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196361] Constrain IPv6 routes to each FIB (Consistent with IPv4 route behaviour) Date: Tue, 31 Jan 2017 20:14:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: needs-patch, needs-qa 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, 31 Jan 2017 20:14:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196361 --- Comment #15 from commit-hook@freebsd.org --- A commit references this bug: Author: asomers Date: Tue Jan 31 20:13:50 UTC 2017 New revision: 313025 URL: https://svnweb.freebsd.org/changeset/base/313025 Log: Add tests for multi-fib IPv6 routing PR: 196361 Submitted by: jhujhiti@adjectivism.org Reported by: Jason Healy MFC after: 4 weeks Sponsored by: Spectra Logic Corp Changes: head/tests/sys/netinet/fibs_test.sh --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 31 20:33:35 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03E0ECCA6AD for ; Tue, 31 Jan 2017 20:33:35 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::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 C5E20C99 for ; Tue, 31 Jan 2017 20:33:34 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-oi0-x22e.google.com with SMTP id w204so222123279oiw.0 for ; Tue, 31 Jan 2017 12:33:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Iox5XlrvqoB3KcKfjB6d15yzwXLfiY99Co8akApZgcw=; b=exup4RkUayJAcJJ1DtvHOfbfMRAuOaJCv1OQJzPn/IxxbMgly/OWhoQJ4juKunarxK +hGiFepuor3Pm0IcD4vq5xlliwLhb9dy1gAJ4ZsgDA2Zgo2iDePRVphyqLHQiZkMU6nW jPYaOrdk0m2m5VIgbs5DBBzEvIlLIxaQP3Fe0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Iox5XlrvqoB3KcKfjB6d15yzwXLfiY99Co8akApZgcw=; b=P+gT+r3gC70gTSAU+bWq/f8xT6oKmQ6rtiSJ1JDJQw9sf5VcMHrzVVEchr6Kg7MlOj SDDG6IzLOFcdr7rgAHPI1guMh7IgM+0DAPmvsQCbR4PQokClkowBmw8aWxZ/bVGv1+st 9kxW7R8bTK3uS7M8prDbLntzaFVxbPoZKtRg9NchH0lEOlag8Tao7pdMy6j6pfbN2Wuw oQhl/4uaYcZ1jCjIZICedqep1u/ubyL/lLW+Ys7yhlJ/b2qZ8R5TrWluVQTyqG0tS3iL 94DqPiOZ9b+lXVcsmhV+1qkP8aveLIhovudxQwllx09CGdsO0KepiZ4kFDN21lDai9xl TfcA== X-Gm-Message-State: AIkVDXLpe2rM8mSIu08uT+lWT2oiRGSxTRQPWJotNJXbYwyv7WmWOdQTuHd1ntI/DrcLO7bUoLWmGLhL+gKsNw== X-Received: by 10.202.253.206 with SMTP id b197mr16813029oii.160.1485894814045; Tue, 31 Jan 2017 12:33:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.23.208 with HTTP; Tue, 31 Jan 2017 12:33:33 -0800 (PST) In-Reply-To: <20170131181036.GV37974@zxy.spb.ru> References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> <20170131181036.GV37974@zxy.spb.ru> From: Kevin Bowling Date: Tue, 31 Jan 2017 13:33:33 -0700 Message-ID: Subject: Re: Disappointing packets-per-second performance results on a Dell, PE R530 To: Slawa Olhovchenkov Cc: Jordan Caraballo , 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, 31 Jan 2017 20:33:35 -0000 I would also suggest increasing the holdoff timer for the Chelsio and see what happens: sysctl dev.t5nex.0.holdoff_timer_idx_10G=3 sysctl dev.t5nex.0.holdoff_timer_idx_10G=4 sysctl dev.t5nex.0.holdoff_timer_idx_10G=5 On Tue, Jan 31, 2017 at 11:10 AM, Slawa Olhovchenkov wrote: > On Tue, Jan 31, 2017 at 01:53:15PM -0400, Jordan Caraballo wrote: > > > This are the most recent stats. No advances so far. The system has > > -Current right now. > > This is like you have only one flow: only CPU 26 and 27 loaded. > > Use different benchmark, create multiple IP flow (w/ different > source/destination IP pairs) > > > top -PHS > > last pid: 18557; load averages: 2.58, 1.90, 0.95 up 4+00:39:54 18:30:46 > > 231 processes: 40 running, 126 sleeping, 65 waiting > > CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 3: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 4: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 5: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 6: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle > > CPU 7: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 8: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 9: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 10: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 11: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 12: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 13: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 14: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 15: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 16: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 17: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 18: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 19: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 20: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 21: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 22: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 23: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 24: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 25: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 26: 0.0% user, 0.0% nice, 0.0% system, 59.6% interrupt, 40.4% idle > > CPU 27: 0.0% user, 0.0% nice, 0.0% system, 96.3% interrupt, 3.7% idle > > CPU 28: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 29: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 30: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 31: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 32: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 33: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > > CPU 34: 0.0% user, 0.0% nice, 0.0% system, 100% interrupt, 0.0% idle > > CPU 35: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Tue Jan 31 20:53:06 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C781FCCADD5 for ; Tue, 31 Jan 2017 20:53:06 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from smtp.smtpout.orange.fr (smtp09.smtpout.orange.fr [80.12.242.131]) by mx1.freebsd.org (Postfix) with ESMTP id 3BA751947 for ; Tue, 31 Jan 2017 20:53:05 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-qt0-f173.google.com ([209.85.216.173]) by mwinf5d85 with ME id f8lQ1u00M3l2wht038lRCp; Tue, 31 Jan 2017 21:45:25 +0100 X-ME-Helo: mail-qt0-f173.google.com X-ME-Auth: Y29jaGFyZC1sYWJiZS5vbGl2aWVyQG9yYW5nZS5mcg== X-ME-Date: Tue, 31 Jan 2017 21:45:25 +0100 X-ME-IP: 209.85.216.173 Received: by mail-qt0-f173.google.com with SMTP id w20so176701452qtb.1 for ; Tue, 31 Jan 2017 12:45:25 -0800 (PST) X-Gm-Message-State: AIkVDXJl3vKo+hzsDVqt1RwNNVaqnJ5v2BG4Ih5zDbKJmS+dx33fDJug2WSoLDh8E5xd1/uDiTVLpBxUpSYFkQ== X-Received: by 10.237.36.166 with SMTP id t35mr27060880qtc.172.1485895524252; Tue, 31 Jan 2017 12:45:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.49.99 with HTTP; Tue, 31 Jan 2017 12:45:03 -0800 (PST) In-Reply-To: References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Tue, 31 Jan 2017 21:45:03 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Disappointing packets-per-second performance results on a Dell, PE R530 To: Jordan Caraballo Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 20:53:06 -0000 On Tue, Jan 31, 2017 at 6:53 PM, Jordan Caraballo < jordancaraballo87@gmail.com> wrote: > This are the most recent stats. No advances so far. The system has > -Current right now. > > Any help or feedback would be appreciated. > > =E2=80=8BI've tried: But you didn't answer my previous question. How do you generate your IP traffic ? What tool are you using=E2=80=8B and can you provide the exact command line= used ? From owner-freebsd-net@freebsd.org Wed Feb 1 00:00:08 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D7B7CCA5EA for ; Wed, 1 Feb 2017 00:00:08 +0000 (UTC) (envelope-from jordancaraballo87@gmail.com) Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::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 F3269117E; Wed, 1 Feb 2017 00:00:07 +0000 (UTC) (envelope-from jordancaraballo87@gmail.com) Received: by mail-ua0-x231.google.com with SMTP id 35so285180066uak.1; Tue, 31 Jan 2017 16:00:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=Dg8SYcx4u3nWhdLxifEvOb3HKlqOWNIpVWbnClph7MQ=; b=Rtl33L14XeqP7/tgolO7MfCi8UEODQMNIysrbKzG1EA1VcEtflxifQIa2/PR3JVtCl qHJcW9BrDp0PRhcOwmNyELIcOSszXeA0BAmn818dJM+3Z4Cobvw6cSw8Nud/cnvtp25W /QCmlHFoabQe/5tBgsxKz2gyoV7ewKOI+f/zL5j8qBbGZ0LrGPDRrOw4GNOUP/hpFSl1 /cVCcxkziwFgfpkTPn9/CVpfJ2hT12Y52m1ocTzJbg9h80+MeELGkE9JU/vRcDsppfrI tKcR+VwAgmgc2EwWMldosEz6oxX58DWBmMgpGjLBW22hbMz1j9inWI+1pw7uslmcAEM6 p4Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=Dg8SYcx4u3nWhdLxifEvOb3HKlqOWNIpVWbnClph7MQ=; b=J6Z5ZxPbaX2yHYlqa/94fJk0REL40UXGnmd1X6TBjYMAZCuTrne6GZfX+9aPRvModg 69eBM70h1ZUgjTmtX6pQikaIQ3n13AHszuT6im3uPg0JdFGL/IfzGcG8PGO253z5xLvo 2amPdKSz57dY44gzFse4CYCM8dBJlWkXEKK4J+tzJbMZWxKndYNw65bB/ByeU4Vdo6NP LXXiDlwrZRFQA5r+rCbpdiaz2mHMqB7UlYSp56IStxkMIafls3sJaXfxevYfL3O4eIg/ hm9az1T/Gi67PTSa6ZCKb7z5a3ft6hhyUV0fql9MJpBMXRs2wJbz1zu+HCajoWJIwgXG 1PPA== X-Gm-Message-State: AIkVDXJ3oox1QZ8Gb/AKQWiUi2KBicc9EdebPJXaNgmchVGu53/LsYQvXvyhsGot3UVQYg== X-Received: by 10.159.34.105 with SMTP id 96mr4847uad.84.1485907206994; Tue, 31 Jan 2017 16:00:06 -0800 (PST) Received: from [192.168.0.105] ([104.218.243.3]) by smtp.gmail.com with ESMTPSA id d78sm6614718vke.18.2017.01.31.16.00.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 16:00:06 -0800 (PST) Subject: Re: Disappointing packets-per-second performance results on a Dell, PE R530 To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> Cc: "freebsd-net@freebsd.org" From: Jordan Caraballo Message-ID: <0cdc69d4-e23f-4beb-c4af-59259529287f@gmail.com> Date: Tue, 31 Jan 2017 20:00:03 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 00:00:08 -0000 Hi Oliver, my bad, I missed that one. Here is the info: * Switch with 48x 10G ports and 12x 40G ports was used * (48) 10G connected nodes were used. * (24) nodes on each side of the firewall * Packet per second (PPS) tests were run using 'iperf' * Bandwidth tests were run using 'nuttcp' * Parallelization was handled by using pdsh * Each of the 24 sending nodes ran either: iperf3 -c "" -u -A 5 -l 512 -b 0 -t "" -J nuttcp -fparse -l 128k -w1m -T "" "" On 31/01/17 16:45, Olivier Cochard-Labbé wrote: > On Tue, Jan 31, 2017 at 6:53 PM, Jordan Caraballo > > wrote: > > This are the most recent stats. No advances so far. The system has > -Current right now. > > Any help or feedback would be appreciated. > > > ​I've tried: But you didn't answer my previous question. > > How do you generate your IP traffic ? > What tool are you using​ and can you provide the exact command line used ? From owner-freebsd-net@freebsd.org Wed Feb 1 01:04:53 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99DC2CCB05D for ; Wed, 1 Feb 2017 01:04:53 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 616C519AC; Wed, 1 Feb 2017 01:04:53 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: by mail-it0-x230.google.com with SMTP id c7so7325035itd.1; Tue, 31 Jan 2017 17:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=oYz+XlC/hsSfNR2QKJki9pWkwTxicP21YGEM4YLuETQ=; b=K2slrYRS7Gl8K4YsFlstDGaOUQBBDaLms/tfy+LmnJZnKPBQJKeaM8yCmMsFCWmd4o BRJ1JhjOpP+1bGOwVkMGrRewu4qTVfQhDo9tCfGVzgVSTiERAXfe+aa81+OQv/pwQx74 ftILElrCwrvj29/ZgKLY4NLjZBnzCXnMKUxjRyn3Y0PvvTQ24tYWT8NoP6LRwI9OHrit shleNevjpMqylvNJyGhAK+xgJV8ul8tJ1E/Pp8IPV3RvVPEwV3hxPJyPdmZpKH0HBmF+ nR0JqMvky00oqWW8LJumVv2zS5alIQIfYfD0TIpLEK0p8T2JO0LoJysLptEQDpu7OfiJ zQ2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=oYz+XlC/hsSfNR2QKJki9pWkwTxicP21YGEM4YLuETQ=; b=afC9UfYJblNhVNYTrTpOa6Do4jHkMnOd/s7MmdtqPbIYJQtavBpfM4E/5VT7yn6Eua HM7HocUCZAWjyPOzMf8ESgi5HkK4lHqv/paenA+orvLfQ9XyUTElAJEWrf0jUSry1BMK lHisT1uxb1boH5jptgcikLANiVdXCFELFP6I4aC+0Z1WGa8e5wLgGQmBbcJODdQNcpRi eEX7NC9ACj7NXADgV32RfM2LSXhiEn06MyAJzeSAd8TtbsPlj18hKazSflootbwGLlUh /rJFLZ2ZRvtxRab5wUvMnJW4tJMj9yzw+kL9l1aZ3thEdNdeHBO0/7f5mUDNSHZEOkDZ aV3g== X-Gm-Message-State: AIkVDXK1M9mJOC/GGleGJq3xT7u5MgcGs+9arvt0kwS+fWa8/W9EG650H4SfugthtfoOdsbi4GvBchRpvbnfpg== X-Received: by 10.36.65.4 with SMTP id x4mr22551607ita.69.1485911092675; Tue, 31 Jan 2017 17:04:52 -0800 (PST) MIME-Version: 1.0 Sender: ermal.luci@gmail.com Received: by 10.107.129.99 with HTTP; Tue, 31 Jan 2017 17:04:52 -0800 (PST) In-Reply-To: <20170120151511.GR78888@zxy.spb.ru> References: <678042cf-9d5f-2f39-6689-30eadf4214a7@freebsd.org> <20170120151511.GR78888@zxy.spb.ru> From: =?UTF-8?Q?Ermal_Lu=C3=A7i?= Date: Tue, 31 Jan 2017 17:04:52 -0800 X-Google-Sender-Auth: IsSnRZQ9mOEGiQOsUuinfjEkrj8 Message-ID: Subject: Re: all network people please review this proposal: because someone is going to commit it soon. D5017 To: Slawa Olhovchenkov Cc: Julian Elischer , "freebsd-net@freebsd.org" , Randall Stewart Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 01:04:53 -0000 On Fri, Jan 20, 2017 at 7:15 AM, Slawa Olhovchenkov wrote: > On Fri, Jan 20, 2017 at 11:00:18PM +0800, Julian Elischer wrote: > > > Unless eri gets to it first I will. > > > > see https://reviews.freebsd.org/D5017 > > > > If you have a server, you can put an arbitrary number of clients on > > the same port number because they all have different addresses. > > > > However in the case of a client accessing multiple servers we are > > limited to 65535 sessions because we strictly don't allow the same > > port to be used more than once. This is silly because TCP is a > > symmetrical protocol and of it works for the server it should work for > > the client. > > > > So this patch changes the allocation of ports to allow the client to > > use a port that has been used before as long as the previous port user > > is not talking to the same host/port. This removes the limitation of a > > freebsd machine being only capable of contacting 65000 hosts in a > > single port shutdown timeout period. With modern machines capable of > > initiating MILLIONS of sessions per second, having a limitation of > > 65000 per 2 minutes is a bit silly. > > > > > > Please read the patch if you suspect this will have a bad effect of > > any sort. Once the session is started there is no record as to who > > started it so any issues would have to be in the startup phase. > > Good. > Can you use also destination port and source IP in same way as > destination address? > This is an improvement over the proposal. Let the existing proposal go in than can improve it even more. -- Ermal From owner-freebsd-net@freebsd.org Wed Feb 1 06:01:20 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 483B2CCCEE7 for ; Wed, 1 Feb 2017 06:01:20 +0000 (UTC) (envelope-from pkelsey@gmail.com) Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01326153D for ; Wed, 1 Feb 2017 06:01:20 +0000 (UTC) (envelope-from pkelsey@gmail.com) Received: by mail-ua0-x22c.google.com with SMTP id y9so290893696uae.2 for ; Tue, 31 Jan 2017 22:01:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=92nNNgTwfGfYv6LQ3/P73onX074RJpaZzEr/s/x56NM=; b=n7zuWlkAYcCrY80tcWp65hFdUrYXYGTk66xs196Zd0j8uua+dr5Wl4q1NqvgQ67vxp HLVMRWhlfaUFglNPSB4i9sZf2jn34vaTtTTUYlRSOuvNDFtTHo+7CUgNOKzY4UWV9ymT cmHRRMDBEwvhq24J7bM5o+ObB0ZCHi7v2cy6Py8cMJSeCUKRpqsLP7VwR+5wNvzdSTJB zsj0BRa0KbNw3NzoUMOdSL3EaabhgUYFdcS6LqJDs6dGcxTBKW2MNKD0kUeipNB/jXmT DENDvC2Mhyb65Zmd645nXbNrPNbb4pbWNDBSwVOULLdLaFVh+ZFvzmgIb4NnPOePw+er akiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=92nNNgTwfGfYv6LQ3/P73onX074RJpaZzEr/s/x56NM=; b=uYHDJ/nTv/tdnqhnnwjYwRSAhop2FhE4wEB3QnW4JNw5PbpNwdz36LTlPH6XpFtdq5 cqvdiey0HqdSBZHPrFZ45X8Ce5RWvMmTMWfrnLFe3H5tDimfoWQMWA9z6Ep9/00+vXUo lLbURGF1+rRJCmNtAYePyfu/gyUYdFMk1g1sW3KFVuRmylPH00Y3tXr3zCY3bulofNkp zzzw0nY6eW3zj1u6bvjT4SGNPdz6vWVasnaWoNBXQgO2HshbQUzrh3D1LNUs7gsNsIXa /5NyUOozEf8awe9cBD/lMUxW23IukfZfdR/P1Jlk4fbIGhozBmLStYFhjXyrVHcq85yA 6GAA== X-Gm-Message-State: AIkVDXL4I9LJsc92NoOKqG3EkAikEKBP6C8DDSF9lN6NvJoA/KHdANVrLni1BSYn0azAZ9cZrqCpCQ1ReUnTHw== X-Received: by 10.176.18.206 with SMTP id o14mr592526uac.58.1485928878971; Tue, 31 Jan 2017 22:01:18 -0800 (PST) MIME-Version: 1.0 Sender: pkelsey@gmail.com Received: by 10.103.74.18 with HTTP; Tue, 31 Jan 2017 22:01:18 -0800 (PST) In-Reply-To: References: From: Patrick Kelsey Date: Wed, 1 Feb 2017 01:01:18 -0500 X-Google-Sender-Auth: GIZEfI0ciagytZBrfhsM1djzUAM Message-ID: Subject: Re: TCP_FASTOPEN is absent in GENERIC To: Sergey Matveychuk 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: Wed, 01 Feb 2017 06:01:20 -0000 On Tue, Jan 31, 2017 at 10:53 AM, Sergey Matveychuk wrote: > Hi. > > Is there a strong reason for option TCP_FASTOPEN is absent in GENERIC > kernel? It's off by default anyway (net.inet.tcp.fastopen.enabled=0). > > Latest dns/bind* versions want it very much. > > The kernel option name is actually TCP_RFC7413, and currently the implementation is only the server side of the protocol. I committed the code as being compiled out by default because it is a bit intrusive to the normal TCP connection establishment code (tcp_input() and syncache interaction) and I decided to be conservative until it was more thoroughly exercised. The original sponsor of the work lost interest in it shortly after it was implemented, so the expected wider and more thorough testing, to my knowledge, never happened. It has only recently been tested with VIMAGE enabled, and a couple of issues with that configuration are being worked through ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216613). Other than that, I think there is still an unresolved issue with Linux TFO clients that don't ACK data returned with the SYN|ACK of a TFO connection - this forces a retransmit from the server and it has been reported that the retransmit timeout in this case is excessive. There is no technical obstacle there that I am aware of, it is just that no time has yet been spent investigating the report. Best, Patrick From owner-freebsd-net@freebsd.org Wed Feb 1 09:53:46 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFF5ACCBA48 for ; Wed, 1 Feb 2017 09:53:46 +0000 (UTC) (envelope-from orjan.tonder@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75D6219DA for ; Wed, 1 Feb 2017 09:53:46 +0000 (UTC) (envelope-from orjan.tonder@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id c85so30609277wmi.1 for ; Wed, 01 Feb 2017 01:53:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gGj87UxFrhqULz5CgF/KGUUt9gSKCYZCp/vsaPGn4ek=; b=uAioUi1xajyhHKZXJe55/hJkzh/Mzueg/DC/xrsrgSisJXWDdazLYAbSvfGRlaSlJd TZ97voiTi1jrSUznG39BECcViX4KmYH4HipgFaseWfwLXh8LCiOP5SrSMBHlQkAAGkfj AtH951LaCoWg0znH58PJbqcYvPH2nZ7UAN1J6B8u5xc5Fn1PMJ5FUV3RbCEULYupB5m+ 2yBCvpsAeernup3lVMDe3R9QmQfMG48BWF6bgRP+9fpK1Me2XWMFH4jHnvx1ADgFoLyU OKxgnGHUKygh8a+/ne+Yr0oGsXhAJTFRyb78i2AkH0IAlTO50Wx+RuXDVDavExMUoxKl xyZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gGj87UxFrhqULz5CgF/KGUUt9gSKCYZCp/vsaPGn4ek=; b=f++mGGM34DlbeLRnJPCCsnEFdz48jsQvAdTnekxyaWhlASpAYh2yi3UPsWS1tkz0VT b2WNHxnXl3pwXTFOZQB9xdYqE7PD7hQFXKww/xHo8RnNZgQbzKBaufnRA4ML/928rgEP Vbwc/9DoEwY0Nd6V/BoT8q4Xv3ReeXQXyHeb+IzotH8r5he+P71Y2uO3g1OPZQPzfkgs N3lI8Mgi5+ghg2z3FlbnHUM/GZsfB5HZT+hrtrb+6gxu5lJ1rGTGf4RUpsISF0iIAj0B /UJtPekPh3UFKjOPbWWr7xbRuqPj7HgN4hX3HxzLdrsGvFKBtBIMe3BQ2K+Rd6qcNvJf LyXA== X-Gm-Message-State: AIkVDXIlHT4pj5ZxaM60pxlL1Q8g+1T63HN6t906X0uJD2W7uijF0p+ym3Vr6X36mdrl3badVjS5jvEUsc9xVA== X-Received: by 10.28.140.130 with SMTP id o124mr2263081wmd.48.1485942824675; Wed, 01 Feb 2017 01:53:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.142.37 with HTTP; Wed, 1 Feb 2017 01:53:44 -0800 (PST) From: =?UTF-8?B?w5hyamFuIFTDuG5kZXI=?= Date: Wed, 1 Feb 2017 10:53:44 +0100 Message-ID: Subject: ipv6 setup. 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: Wed, 01 Feb 2017 09:53:47 -0000 I am trying too get ipv6 up and running but i cant get outside. -- /etc/rc.conf ipv6_default_interface="re0" #ifconfig_re0_ipv6="inet6 accept_rtadv" ifconfig_re0_ipv6="inet6 2a01:4f8:131:50a1::2/64" ipv6_defaultrouter="inet6 fe80::1%re0" -- Routing tables Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 default fe80::1%re0 UGS re0 ::1 link#2 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRS lo0 2a01:4f8:131:50a1::/64 link#1 U re0 2a01:4f8:131:50a1::2 link#1 UHS lo0 fe80::/10 ::1 UGRS lo0 fe80::%re0/64 link#1 U re0 fe80::6e62:6dff:fe7c:2c98%re0 link#1 UHS lo0 fe80::%lo0/64 link#2 U lo0 fe80::1%lo0 link#2 UHS lo0 fe80::%tun0/64 link#8 U tun0 fe80::6e62:6dff:fe7c:2c98%tun0 link#8 UHS lo0 ff01::%re0/32 2a01:4f8:131:50a1::2 U re0 ff01::%lo0/32 ::1 U lo0 ff01::%tun0/32 fe80::6e62:6dff:fe7c:2c98%tun0 U tun0 ff02::/16 ::1 UGRS lo0 ff02::%re0/32 2a01:4f8:131:50a1::2 U re0 ff02::%lo0/32 ::1 U lo0 ff02::%tun0/32 fe80::6e62:6dff:fe7c:2c98%tun0 U tun0 ping6 ::1 PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1, icmp_seq=0 hlim=64 time=0.050 ms ping6 2a01:4f8:131:50a1::2 PING6(56=40+8+8 bytes) 2a01:4f8:131:50a1::2 --> 2a01:4f8:131:50a1::2 16 bytes from 2a01:4f8:131:50a1::2, icmp_seq=0 hlim=64 time=0.055 ms ping6 2001:4860:4860::8888 PING6(56=40+8+8 bytes) 2a01:4f8:131:50a1::2 --> 2001:4860:4860::8888 ping6: sendmsg: Operation not permitted ping6: wrote 2001:4860:4860::8888 16 chars, ret=-1 traceroute6 2001:4860:4860::8888 traceroute6 to 2001:4860:4860::8888 (2001:4860:4860::8888) from 2a01:4f8:131:50a1::2, 64 hops max, 12 byte packets sendto: Operation not permitted 1 traceroute6: wrote 2001:4860:4860::8888 12 chars, ret=-1 2a01:4f8:131:50a1::2 0.065 mssendto: Operation not permitted I have in pf.conf pass quick on $ext_if proto ipv6 I cant understand what i am missing, still learning the ropes of ipv6. could anyone help me getting this up and running? From owner-freebsd-net@freebsd.org Wed Feb 1 11:38:57 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99DEDCCAE3A for ; Wed, 1 Feb 2017 11:38:57 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F471179F; Wed, 1 Feb 2017 11:38:57 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cYtFU-0002D5-TO; Wed, 01 Feb 2017 14:38:52 +0300 Date: Wed, 1 Feb 2017 14:38:52 +0300 From: Slawa Olhovchenkov To: Jordan Caraballo Cc: Olivier =?utf-8?Q?Cochard-Labb=C3=A9?= , "freebsd-net@freebsd.org" Subject: Re: Disappointing packets-per-second performance results on a Dell, PE R530 Message-ID: <20170201113852.GB79121@zxy.spb.ru> References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> <0cdc69d4-e23f-4beb-c4af-59259529287f@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0cdc69d4-e23f-4beb-c4af-59259529287f@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 11:38:57 -0000 On Tue, Jan 31, 2017 at 08:00:03PM -0400, Jordan Caraballo wrote: > Hi Oliver, my bad, I missed that one. Here is the info: > > * Switch with 48x 10G ports and 12x 40G ports was used > * (48) 10G connected nodes were used. > * (24) nodes on each side of the firewall > * Packet per second (PPS) tests were run using 'iperf' > * Bandwidth tests were run using 'nuttcp' > * Parallelization was handled by using pdsh > * Each of the 24 sending nodes ran either: > iperf3 -c "" -u -A 5 -l 512 -b 0 -t "" -J > nuttcp -fparse -l 128k -w1m -T "" "" Very strange result. I am don't see in you output any chelsio irq, like this: irq289: t5nex0:evt 2 0 irq300: t5nex0:1a0 204093767467 48085 irq301: t5nex0:1a1 204536605147 48189 irq302: t5nex0:1a2 204677310714 48222 irq303: t5nex0:1a3 204727624595 48234 irq304: t5nex0:1a4 204345362150 48144 irq305: t5nex0:1a5 203085398725 47847 irq306: t5nex0:1a6 204014240537 48066 irq307: t5nex0:1a7 204216351652 48114 irq308: t5nex0:1A0 132806676 31 irq309: t5nex0:1A1 133275327 31 Do you using polling? > On 31/01/17 16:45, Olivier Cochard-Labbé wrote: > > On Tue, Jan 31, 2017 at 6:53 PM, Jordan Caraballo > > > wrote: > > > > This are the most recent stats. No advances so far. The system has > > -Current right now. > > > > Any help or feedback would be appreciated. > > > > > > ​I've tried: But you didn't answer my previous question. > > > > How do you generate your IP traffic ? > > What tool are you using​ and can you provide the exact command line used ? > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Wed Feb 1 13:10:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B59F8CCBF9D for ; Wed, 1 Feb 2017 13:10:09 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 729F2B8B for ; Wed, 1 Feb 2017 13:10:09 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from [212.54.42.134] (helo=smtp10.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cYu1y-0003gF-0N for freebsd-net@freebsd.org; Wed, 01 Feb 2017 13:28:58 +0100 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp10.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cYu1x-0007Sm-U7 for freebsd-net@freebsd.org; Wed, 01 Feb 2017 13:28:57 +0100 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id B3964156 for ; Wed, 1 Feb 2017 13:28:57 +0100 (CET) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cz-jADTg28kl for ; Wed, 1 Feb 2017 13:28:57 +0100 (CET) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 463B714B for ; Wed, 1 Feb 2017 13:28:57 +0100 (CET) From: Peter Blok Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: 11-stable mountd listens on port 993 Message-Id: <33C2BACA-E500-4C57-9827-797F5206C572@bsd4all.org> Date: Wed, 1 Feb 2017 13:28:56 +0100 To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.3259) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=C7+Z8UH+ c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=n2v9WMKugxEA:10 a=iBaiPJ-joxjMkPYG0hwA:9 a=QEXdDO2ut3YA:10 a=awgRJSotPjkA:10 a=afVW8qIJhE4arkyR:21 a=_W_S_7VecoQA:10 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 13:10:09 -0000 I just updated to 11-stable@313042 and when I rebootted my system = dovecot didn=E2=80=99t want to start because port 993 was already in = use. Checked with lsof and it was mountd that was listening on this port. = When I stopped mountd and started dovecot everything was fine. When I = started mountd after this it worked ok. Next reboot everything was fine. Anybody know why mountd could have been listening to port 993? Peter From owner-freebsd-net@freebsd.org Wed Feb 1 14:33:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60A38CCB0E6 for ; Wed, 1 Feb 2017 14:33:18 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id 4CD99BBA for ; Wed, 1 Feb 2017 14:33:18 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from ford.home.vangyzen.net (unknown [76.164.15.242]) by smtp.vangyzen.net (Postfix) with ESMTPSA id B551F56469; Wed, 1 Feb 2017 08:33:17 -0600 (CST) Subject: Re: 11-stable mountd listens on port 993 To: Peter Blok , freebsd-net@freebsd.org References: <33C2BACA-E500-4C57-9827-797F5206C572@bsd4all.org> From: Eric van Gyzen Message-ID: Date: Wed, 1 Feb 2017 08:33:14 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <33C2BACA-E500-4C57-9827-797F5206C572@bsd4all.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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, 01 Feb 2017 14:33:18 -0000 On 02/01/2017 06:28, Peter Blok wrote: > I just updated to 11-stable@313042 and when I rebootted my system dovecot > didn’t want to start because port 993 was already in use. > > Checked with lsof and it was mountd that was listening on this port. When I > stopped mountd and started dovecot everything was fine. When I started mountd > after this it worked ok. > > Next reboot everything was fine. > > Anybody know why mountd could have been listening to port 993? Since mountd uses bindresvport_sa(3), the kernel chooses a port in the "low" range, configured via sysctl: net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.lowfirst: 1023 There is some randomness in the algorithm, so there is roughly a 1/424 chance of conflict. You might use the -p flag to mountd or reduce lowfirst below 993. Cheers, Eric From owner-freebsd-net@freebsd.org Wed Feb 1 16:10:29 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EF66CCB421 for ; Wed, 1 Feb 2017 16:10:29 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx1.mailbox.org (mx1.mailbox.org [80.241.60.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 020BE9BC for ; Wed, 1 Feb 2017 16:10:28 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id B75E4468E1 for ; Wed, 1 Feb 2017 17:03:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mailbox.org; h= content-transfer-encoding:content-type:content-type:mime-version :references:in-reply-to:subject:subject:from:from:message-id :date:date:received; s=mail20150812; t=1485964980; bh=l3rvMnunFr 5wMNvUNRPbzM4i91j53IgI+EFnnY74fi0=; b=qXAdlTNyPCTwPFmilND1TRnIec 7kuYyc3+V8LqCX6ths2asml262CS3f4I3/GHThYD4tkNK5dwqKI47UOUWm5l4PMd hvMHICQGtKVttbgVQ359ODEjv7dUOKLq2v5RmougwwUnyhaHJaI5MZ0y5rJggVQP +TnoSZSRaAVvQxnJZwlwtbXzoSV/5+vevJ3hvG26h2UdYp1TaAiSZnc3TzyXiELC aNjfmx7o022aBYNHvGRETHZWcAcr1mySAk6KtFuHFFbzDVbxQ8tN5+iPnWhWK29o QY0AnWIm++E4PpU+wiU+z3SygzN8VtMzObeUToGAoGFE6FqwOBvBpoCcpEYQ== X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172]) (amavisd-new, port 10030) with ESMTP id uFe2pcVjk7I7 for ; Wed, 1 Feb 2017 17:03:00 +0100 (CET) Date: Wed, 01 Feb 2017 17:02:58 +0100 Message-ID: <86efzh99vx.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: freebsd-net@freebsd.org Subject: Re: ipv6 setup. In-Reply-To: References: MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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, 01 Feb 2017 16:10:29 -0000 Hei, =D8rjan T=F8nder skrev: > = > I am trying too get ipv6 up and running but i cant get outside. > -- /etc/rc.conf > ipv6_default_interface=3D"re0" > #ifconfig_re0_ipv6=3D"inet6 accept_rtadv" > ifconfig_re0_ipv6=3D"inet6 2a01:4f8:131:50a1::2/64" > ipv6_defaultrouter=3D"inet6 fe80::1%re0" = Remove the inet6 keyword in the last line and try again! -- Herbert From owner-freebsd-net@freebsd.org Wed Feb 1 16:10:56 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65F43CCB4A8 for ; Wed, 1 Feb 2017 16:10:56 +0000 (UTC) (envelope-from paul.christopher@cordelldatamarketing.com) Received: from smtpauth.net4india.com (smtpauth.net4india.com [118.67.248.47]) by mx1.freebsd.org (Postfix) with ESMTP id 6DF72C02 for ; Wed, 1 Feb 2017 16:10:55 +0000 (UTC) (envelope-from paul.christopher@cordelldatamarketing.com) Received: from [202.83.16.183] (helo=WIN2J3M8BFEUK4) by smtpauth.net4india.com with esmtpa (Exim 4.72 #1) id 1cYxBM-0001SU-8B by authid with login for ; Wed, 01 Feb 2017 21:20:52 +0530 From: "Paul Christopher" To: Subject: RE: Infor Partner Info Date: Wed, 1 Feb 2017 10:49:43 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdJ8om+d3TB0rnOJSNSujttPeFGVig== Content-Language: en-us X-Auth-By: paul.christopher@cordelldatamarketing.com X-Auth-By-Port: 587 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 16:10:56 -0000 Hi, I was researching your company website and I understand that your company is a "Infor Partner" and I figured it'd be worth leaving a note, We maintain about 25 Million+ B2B contacts from various industries. We are specialized in working with companies whose target market is Infor Users. By helping them acquire relevant Marketing Lists. Just wanted to check if you would be interested in reaching out to Infor users and similar service provider and users with contact information for your Lead Generation, Email campaign, Tele marketing and other marketing initiatives? We have Infor Products Users like: 2DDesignAutomation, 3DDesignAutomation, ACmanagerCRM, Adage, AdvancedPlanning, AdvancedScheduling, AnaelFMS, AnaelHCM, Approva, Baan5.x, BaanIV, Infor BI, BIApplicationStudio, BIDashboards, BIDeltaMiner, BIImportMaster, BIOfficePlus, BPCS, CAS, CloudSuite, Infor COM, Infor CORS, CPM, Infor CRM, Infor DemandPlanning, Infor DistributionFACTS, Infor DistributionSX.e, ESeriesFMS, ESeriesHCM, Infor EAM, Infor e-Commerce, Elevon, EnRoute, EPAK, Epiphany, EzLite, EzPLUS, EzRMS, F9, FourthShift, GlobalHR, GrowthPower, Infor HMS, InfiniumFMS, InfiniumHCM, InfiniumMM/PR, Infopoint, Inforce, Infor ION, Infor KBM, Landmark, Lawson, Leanware, Infor LN, Infor LoadPlanning, Infor LX, MSeriesFMS, MSeriesHCM, Infor M3, M3EAM, MAC-PACXE, MANMAN, MasterpieceFMS, MasterpieceHCM, MAX+TM, MAXCIM, MaxRecall, MediSuite, Ming.le, Infor MK, Mongoose, Infor MP2, NetworkDesign, Optiva, Pathway, PLMDiscrete, PLMFashion, Point.Man, PRISM, InforPRMS, Protean, PublicSector, Infor RFID, RoutePlanning, SalesPortal, SmartStreameXFM, SmartStreamFMS, SmartStreamHCM, StarlightPMS, System21, TRANS4M, Workspace, Infor XA, Infor XBRL, Infor Xpert and many more Users across the globe..... All contacts come with the following information: LinkedIn Profile, Company Name, Contact name, Title, Address, Phone, Fax, City, State, Zip codes, Country, Industry, Employee size, Revenue size, Sic Code, Website and verified email address. Unlike any other vendors out there, our lists are dual verified (Email & Call). We only provide you opt in contacts (permission based). Note: If this is not relevant to you please reply back with your Target Market, we have all types of target market available. If it sounds good for you, Please let me know your Exact: Target Industry/Technology User: _________________ (Any Industry) Target Geography :________________( worldwide) Target Job Title :__________________( Any Job Title) So, that I can get back to you with more information like counts, cost and as well as free sample file for your review. Waiting for your Swift Response Regards, Paul Christopher Marketing Manager Cordell Data Marketing Inc. 984 Rowley Drive San Jose 95132 United States To opt out please response Remove in subject line. From owner-freebsd-net@freebsd.org Wed Feb 1 20:27:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E69CECCCABE for ; Wed, 1 Feb 2017 20:27: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 D2B201952 for ; Wed, 1 Feb 2017 20:27: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 v11KRiqn046831 for ; Wed, 1 Feb 2017 20:27:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216304] Adding xn0 to bridge0 causes kernel panic Date: Wed, 01 Feb 2017 20:27:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People 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: Wed, 01 Feb 2017 20:27:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216304 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: kp Date: Wed Feb 1 20:27:38 UTC 2017 New revision: 313050 URL: https://svnweb.freebsd.org/changeset/base/313050 Log: MFC 312782 bridge: Release the bridge lock when calling bridge_set_ifcap() This calls ioctl() handlers for the different interfaces in the bridge. These handlers expect to get called in an ioctl context where it's safe for them to sleep. We may not sleep with the bridge lock held. However, we still need to protect the interface list, to ensure it doesn't get changed while we iterate over it. Use BRIDGE_XLOCK(), which prevents bridge members from being removed. Adding bridge members is safe, because it uses LIST_INSERT_HEAD(). This caused panics when adding xen interfaces to a bridge. PR: 216304 Reviewed by: ae Sponsored by: RootBSD Differential Revision: https://reviews.freebsd.org/D9290 Changes: _U stable/11/ stable/11/sys/net/if_bridge.c stable/11/sys/net/if_bridgevar.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Feb 1 21:45:59 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 020D1CCB623 for ; Wed, 1 Feb 2017 21:45:59 +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 E5EAF1CC for ; Wed, 1 Feb 2017 21:45: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 v11LjwfM050616 for ; Wed, 1 Feb 2017 21:45:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216304] Adding xn0 to bridge0 causes kernel panic Date: Wed, 01 Feb 2017 21:45:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People 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: Wed, 01 Feb 2017 21:45:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216304 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: kp Date: Wed Feb 1 21:44:50 UTC 2017 New revision: 313066 URL: https://svnweb.freebsd.org/changeset/base/313066 Log: MFC 312782 bridge: Release the bridge lock when calling bridge_set_ifcap() This calls ioctl() handlers for the different interfaces in the bridge. These handlers expect to get called in an ioctl context where it's safe for them to sleep. We may not sleep with the bridge lock held. However, we still need to protect the interface list, to ensure it doesn't get changed while we iterate over it. Use BRIDGE_XLOCK(), which prevents bridge members from being removed. Adding bridge members is safe, because it uses LIST_INSERT_HEAD(). This caused panics when adding xen interfaces to a bridge. PR: 216304 Reviewed by: ae Sponsored by: RootBSD Differential Revision: https://reviews.freebsd.org/D9290 Changes: _U stable/10/ stable/10/sys/net/if_bridge.c stable/10/sys/net/if_bridgevar.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Feb 1 21:50:24 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE3F9CCBBAD for ; Wed, 1 Feb 2017 21:50:24 +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 86F1C1287 for ; Wed, 1 Feb 2017 21:50:24 +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 v11LoNf7057766 for ; Wed, 1 Feb 2017 21:50:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216304] Adding xn0 to bridge0 causes kernel panic Date: Wed, 01 Feb 2017 21:50:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kp@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: kp@freebsd.org X-Bugzilla-Flags: mfc-stable10+ mfc-stable11+ X-Bugzilla-Changed-Fields: assigned_to flagtypes.name resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 21:50:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216304 Kristof Provost changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |kp@freebsd.org Flags| |mfc-stable10+, | |mfc-stable11+ Resolution|--- |FIXED Status|New |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Feb 1 22:44:02 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0FA2CCCC64 for ; Wed, 1 Feb 2017 22:44: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 A5E9C1EF5 for ; Wed, 1 Feb 2017 22:44: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 v11Mi0ZO012510 for ; Wed, 1 Feb 2017 22:44:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 202680] Silent data corruption on em(4) interfaces Date: Wed, 01 Feb 2017 22:44:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: KOT@MATPOCKuH.Ru 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, 01 Feb 2017 22:44:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202680 --- Comment #28 from Dmitry Afanasiev --- Bug still exists on stable/10 r309900 - 3 times got ssh disconnections, and= got 2 errors for dumb TCP data transfer per ~3Tb of transmitted data. To check on current I should switch some services from this server and shou= ld have a time to run tests. But I will try to test in this month. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Feb 2 00:04:14 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22885CCC448 for ; Thu, 2 Feb 2017 00:04:14 +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 126A5D74 for ; Thu, 2 Feb 2017 00:04:14 +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 v1204DZC071213 for ; Thu, 2 Feb 2017 00:04:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216681] IPsec traceroute6 -I does not work Date: Thu, 02 Feb 2017 00:04:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-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 keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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, 02 Feb 2017 00:04:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216681 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Keywords| |patch --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Feb 2 01:09:26 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A65ECCB6AD for ; Thu, 2 Feb 2017 01:09:26 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from smtp.smtpout.orange.fr (smtp06.smtpout.orange.fr [80.12.242.128]) by mx1.freebsd.org (Postfix) with ESMTP id 91D8E10BC for ; Thu, 2 Feb 2017 01:09:24 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-qt0-f177.google.com ([209.85.216.177]) by mwinf5d82 with ME id fd1k1u0083qDe2x03d1lJ6; Thu, 02 Feb 2017 02:01:46 +0100 X-ME-Helo: mail-qt0-f177.google.com X-ME-Auth: Y29jaGFyZC1sYWJiZS5vbGl2aWVyQG9yYW5nZS5mcg== X-ME-Date: Thu, 02 Feb 2017 02:01:46 +0100 X-ME-IP: 209.85.216.177 Received: by mail-qt0-f177.google.com with SMTP id v23so2667354qtb.0 for ; Wed, 01 Feb 2017 17:01:45 -0800 (PST) X-Gm-Message-State: AMke39ls+nSese5lGY60bskWTnEKyjfmZc+59hsSkX33MRZyq8j2km52vAKwXGEeM/ygr3b1aZ0+4qeIspkOnQ== X-Received: by 10.55.180.129 with SMTP id d123mr5421425qkf.158.1485997304235; Wed, 01 Feb 2017 17:01:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.49.99 with HTTP; Wed, 1 Feb 2017 17:01:23 -0800 (PST) In-Reply-To: <0cdc69d4-e23f-4beb-c4af-59259529287f@gmail.com> References: <8f637e2e-cd59-dc65-8476-30989bea516b@gmail.com> <20170103174627.GW37118@zxy.spb.ru> <0cdc69d4-e23f-4beb-c4af-59259529287f@gmail.com> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Thu, 2 Feb 2017 02:01:23 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Disappointing packets-per-second performance results on a Dell, PE R530 To: Jordan Caraballo Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 01:09:26 -0000 =E2=80=8B=E2=80=8B =E2=80=8B=E2=80=8B On Wed, Feb 1, 2017 at 1:00 AM, Jordan Caraballo < jordancaraballo87@gmail.com> wrote: > Hi Oliver, my bad, I missed that one. Here is the info: > > * Switch with 48x 10G ports and 12x 40G ports was used > * (48) 10G connected nodes were used. > * (24) nodes on each side of the firewall > * Packet per second (PPS) tests were run using 'iperf' > * Bandwidth tests were run using 'nuttcp' > * Parallelization was handled by using pdsh > * Each of the 24 sending nodes ran either: > iperf3 -c "" -u -A 5 -l 512 -b 0 -t "" -J > nuttcp -fparse -l 128k -w1m -T "" "" > > =E2=80=8BYour current performance (1.5Mpps) seems to indicate that only one= , perhaps 2 cores maximum are used. Can you confirm that during your iperf bench there are 24 distinct flows simultaneously (different source/destination IP) ? source-IP-1 -> target-IP-1 source-IP-2 -> target-IP-2 ... until source-IP-24 -> target-IP-24 On your dual CPU with 18 cores, chelsio drivers should create per each port= : - 8 RX queues (rxq NIC) - 16 TX queues (txq NIC) Can you check on /var/run/dmesg.boot that you've got something like this: t5nex0: mem 0xfb780000-0xfb7fffff,0xfa0000 00-0xfaffffff,0xf9ff0000-0xf9ff1fff irq 40 at device 0.4 numa-domain 0 on pci7 cxl0: numa-domain 0 on t5nex0 cxl0: Ethernet address: 00:07:43:2e:e4:70 cxl0: 16 txq, 8 rxq (NIC); 8 txq, 2 rxq (TOE) =3D> Notice the 16 txq, 8 rxq (NIC) lines Now, like Slawa says, we should see the 8 IRQ assigned to these 8 rxq and equally used. After your bench, output of a "vmstat -ia | grep t5nex0:0a" should display a minimum of 8 lines with equally distributed number like this example: [root@hp]~# vmstat -ia | grep t5nex0:0a irq292: t5nex0:0a0 37 0 irq293: t5nex0:0a1 288498 629 irq294: t5nex0:0a2 225410 492 irq295: t5nex0:0a3 306227 668 irq296: t5nex0:0a4 282679 617 irq297: t5nex0:0a5 313143 683 irq298: t5nex0:0a6 318727 695 irq299: t5nex0:0a7 308669 673 (my example seems not perfect because queue0 seems under-utilized, but you've got the idea) From owner-freebsd-net@freebsd.org Thu Feb 2 01:45:11 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DA0ACCB59B for ; Thu, 2 Feb 2017 01:45: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 3CD2C1574 for ; Thu, 2 Feb 2017 01:45: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 v121jAnt015350 for ; Thu, 2 Feb 2017 01:45:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Thu, 02 Feb 2017 01:45:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ 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: Thu, 02 Feb 2017 01:45:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 --- Comment #23 from Rick Macklem --- Created attachment 179512 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D179512&action= =3Dedit add svcpool_close so that svcpool_destroy doesn't get called when nfsd thre= ads are killed This patch adds a new function to the server krpc called svcpool_close(). It is similar to svcpool_destroy(), but does not free the data structures, so that the pool can be used again. This function is then used instead of svcpool_destroy(), svcpool_create() when the nfsd threads are killed. These crashes are caused because the data structures were free'd by svcpool_destroy() when the nfsd threads were killed off (or signalled someh= ow). By avoiding the svcpool_destroy() call, the crashes should be avoided. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Thu Feb 2 01:48:29 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8D07CCB824 for ; Thu, 2 Feb 2017 01:48: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 A81111745 for ; Thu, 2 Feb 2017 01:48: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 v121mTax006516 for ; Thu, 2 Feb 2017 01:48:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9 Date: Thu, 02 Feb 2017 01:48:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: IntelNetworking, crash, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10+ X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 01:48:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340 Rick Macklem changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |In Progress Resolution|FIXED |--- --- Comment #24 from Rick Macklem --- Please test the patch I just attached. (4th one) I think it might make the code less fragile to nfsd threads being signalled. I have not been able to create a crash with the patch during limited testing. Since avg@'s crash occurred with the other patches, I have reopened the PR. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Thu Feb 2 12:57:56 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F82ECCD6D9 for ; Thu, 2 Feb 2017 12:57: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 6EBACE8D for ; Thu, 2 Feb 2017 12:57: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 v12CvtFt023645 for ; Thu, 2 Feb 2017 12:57:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 211003] net.inet.tcp.delayed_ack=0 delaying local tcp requests Date: Thu, 02 Feb 2017 12:57:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: moko@moko.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2017 12:57:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211003 --- Comment #3 from Konstantin Morshnev --- Note: we've also tested FreeBSD 11, and can confirm the same behavior. By default all is fine, but just after you change net.inet.tcp.delayed_ack=3D0 net.inet.tcp.recvspace=3D8192 net.inet.tcp.sendspace=3D150000 local http requests are delaying after every 8kb of data for 5 seconds. > 2) something other than lynx on recv side Initially we have found this issue between apache and nginx, and we've also used telnet, so it's for sure not related to lynx. > You might look at using siftr(4) to collect statistics on the transfer. Done. enable_time_secs=3D1486035625 enable_time_usecs=3D746854 siftrve= r=3D1.2.4=20 hz=3D1000 tcp_rtt_scale=3D32 sysname=3DFreeBSD sysver=3D1003000 ipm= ode=3D4 o,0x00000000,1486035625.768531,195.218.200.149,10047,195.218.200.149,80,107= 3725440,1073725440,0,0,0,0,0,2,536,0,1,672,3000,65535,0,8192,0,0,0,0,0 i,0x00000000,1486035625.768622,195.218.200.149,10047,195.218.200.149,80,107= 3725440,1073725440,0,0,0,0,0,2,536,0,1,672,3000,65535,0,8192,0,1,0,0,0 o,0x00000000,1486035625.768661,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,993,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035625.768979,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,241,8192,0,0,0,0,0 i,0x00000000,1486035625.768994,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,996,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035625.769020,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,997,230,81660,0,8192,241,0,0,0,0 i,0x00000000,1486035625.769028,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,241,8192,0,241,0,0,0 o,0x00000000,1486035625.769903,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,996,230,81660,33009,8192,0,0,0,0,0 i,0x00000000,1486035625.769926,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,7936,8192,6,6,4,16332,7,1,992,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035625.769960,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525281,230,81660,0,8192,8192,0,0,= 0,0 i,0x00000000,1486035625.769967,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,996,230,81660,33009,8192,0,8192,0= ,0,0 o,0x00000000,1486035630.769156,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,8389604,230,81660,81660,8192,0,0,0,0= ,0 i,0x00000000,1486035630.769184,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525280,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035630.769219,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,993,230,81660,0,8192,1,0,0,0,0 i,0x00000000,1486035630.769225,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,996,230,81660,81660,8192,0,1,0,0,0 o,0x00000000,1486035630.769251,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,0,0,0,0 i,0x00000000,1486035630.769256,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035630.769264,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525281,230,81660,0,8192,8128,0,0,= 0,0 i,0x00000000,1486035630.769266,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,8128,0= ,0,0 o,0x00000000,1486035635.769158,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,8389604,230,81660,81660,8192,0,0,0,0= ,0 i,0x00000000,1486035635.769193,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525280,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035635.769243,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,993,230,81660,0,8192,1,0,0,0,0 i,0x00000000,1486035635.769252,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,996,230,81660,81660,8192,0,1,0,0,0 o,0x00000000,1486035635.769280,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,0,0,0,0 i,0x00000000,1486035635.769286,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035635.769294,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525281,230,81660,0,8192,8066,0,0,= 0,0 i,0x00000000,1486035635.769296,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,8128,0= ,0,0 o,0x00000000,1486035640.769155,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,8389604,230,81660,81660,8192,0,0,0,0= ,0 i,0x00000000,1486035640.769185,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525280,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035640.769235,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,993,230,81660,0,8192,0,0,0,0,0 i,0x00000000,1486035640.769244,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,996,230,81660,81660,8192,0,1,0,0,0 o,0x00000000,1486035640.769271,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,0,0,0,0 i,0x00000000,1486035640.769276,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035640.769284,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525281,230,81660,0,8192,8128,0,0,= 0,0 i,0x00000000,1486035640.769286,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,8128,0= ,0,0 o,0x00000000,1486035645.769158,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,8389604,230,81660,81660,8192,0,0,0,0= ,0 i,0x00000000,1486035645.769191,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525280,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035645.769245,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,993,230,81660,0,8192,1,0,0,0,0 i,0x00000000,1486035645.769255,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,996,230,81660,81660,8192,0,1,0,0,0 o,0x00000000,1486035645.769284,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,0,0,0,0 i,0x00000000,1486035645.769290,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035645.769298,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525281,230,81660,0,8192,7940,0,0,= 0,0 i,0x00000000,1486035645.769300,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,8128,0= ,0,0 o,0x00000000,1486035650.769158,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,8389604,230,81660,81660,8192,0,0,0,0= ,0 i,0x00000000,1486035650.769194,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525280,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035650.769250,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,993,230,81660,0,8192,0,0,0,0,0 i,0x00000000,1486035650.769259,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,996,230,81660,81660,8192,0,1,0,0,0 o,0x00000000,1486035650.769288,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,0,0,0,0 i,0x00000000,1486035650.769294,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,992,230,81660,0,8192,0,0,0,0,0 o,0x00000000,1486035650.769302,195.218.200.149,10047,195.218.200.149,80,107= 3725440,32664,0,8192,8192,6,6,4,16332,7,1,525281,230,81660,0,8192,8128,0,0,= 0,0 i,0x00000000,1486035650.769303,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,8128,8192,6,6,4,16332,7,1,996,230,81660,81659,8192,0,8128,0= ,0,0 o,0x00000000,1486035655.769166,195.218.200.149,80,195.218.200.149,10047,107= 3725440,32664,0,0,8192,6,6,4,16332,7,1,8389604,230,81660,81660,8192,0,0,0,0= ,0 ... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Feb 3 11:47:41 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5605FCCE247 for ; Fri, 3 Feb 2017 11:47:41 +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 45B5BC78 for ; Fri, 3 Feb 2017 11:47:41 +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 v13Blf1g046489 for ; Fri, 3 Feb 2017 11:47:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216744] [feature request] set DSCP on neighbor solicitation Date: Fri, 03 Feb 2017 11:47:41 +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: 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: cc short_desc 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, 03 Feb 2017 11:47:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216744 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC|freebsd-amd64@FreeBSD.org | Summary|set DSCP on neighbor |[feature request] set DSCP |solicitation |on neighbor solicitation 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 Feb 3 11:48:26 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4601CCE3F2 for ; Fri, 3 Feb 2017 11:48:26 +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 A4092F2F for ; Fri, 3 Feb 2017 11:48:26 +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 v13BmQgv047889 for ; Fri, 3 Feb 2017 11:48:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216731] [patch] if_lagg.c: Boot hang due to LOR in lagg initialization Date: Fri, 03 Feb 2017 11:48:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE 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, 03 Feb 2017 11:48:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216731 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 Feb 3 16:51:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC0F5CCE4A2 for ; Fri, 3 Feb 2017 16:51:49 +0000 (UTC) (envelope-from sandra.lisa.us@gmail.com) Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92B4B1F9C for ; Fri, 3 Feb 2017 16:51:49 +0000 (UTC) (envelope-from sandra.lisa.us@gmail.com) Received: by mail-pf0-x241.google.com with SMTP id 19so1899301pfo.3 for ; Fri, 03 Feb 2017 08:51:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language:disposition-notification-to; bh=GswDyOlmhQuPW2G4yyEfdG7/3PVjYzE7YLpVp+3cdWI=; b=ob4aE4v1Gk+fdGLBN6rg2JBJkynDUs8PMqu0u82Lf+rVlfzrucyoKHHWSnZxdUkfF4 3au8fSRGuEjFV5AOJb4hM3OXMeJ/oVbCU7EXf3V0PYgQJl7c/y0KxBYENK0d51/Kuego ltgZQM0rdDkY3yvQcKYHjw9HwGV2xoh8IsiZTZE8m9E4wlH+Gzn9NvUa5WNis1rIVBAP IztsqHS64Snd0XVbMkbQ0zOSB7rTlaKzBi/+x+hU1iQYjp8BpBXnXXW2ez11vfXTEZza kQDvmCI/v/6RnTdWdLbaP4TS/gEV2S4LTuGWf1LvkmgXlQgoB9EyQJxHyqix3i5LlSWX xnmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language :disposition-notification-to; bh=GswDyOlmhQuPW2G4yyEfdG7/3PVjYzE7YLpVp+3cdWI=; b=bSPEf5Fb2SlqkWwd1+bT6IYqVo5h0UZ3AOoFUjuL8jFZWiImWXjwzuSCs/mMkYgai5 xcIY06nEZKhRxdhXT3Yw/P5lo401mguw5e9/2vkeaCNhYx+ddZSS84tXaiUUsf+azUPm y7kWABx6L8w9plx+8WE37D+yuQNi1+bQ7doeSOpRC7ge7x3meemKIKCNEt448k9y/IV/ 7Nd5MCAs5mNt+5rf0bOeSERaUy/q+yv40HODva5YE7OrM880g/4v1JedeZWg/8hcZAr7 iWjvv3bOJk+RuG7Q4jZ7+zxjulSJH63CIccpIyiGGK4sdcCDvBtPzkAaQjoUv37KeVVM 60og== X-Gm-Message-State: AIkVDXK50V4YFUqH6jAO0dy+xfixXpCZV6HK237N51tgb9gTbf7Q5S474zY3qDLoeZIqTg== X-Received: by 10.99.193.17 with SMTP id w17mr19291298pgf.124.1486140709030; Fri, 03 Feb 2017 08:51:49 -0800 (PST) Received: from Admin5PC ([122.171.58.68]) by smtp.gmail.com with ESMTPSA id l12sm68510244pfj.37.2017.02.03.08.51.47 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 03 Feb 2017 08:51:48 -0800 (PST) From: "Sandra Lisa" To: References: In-Reply-To: Subject: Attendees list of Southern California Linux Expo 2017 Date: Fri, 3 Feb 2017 10:51:46 -0600 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdJ+PKvctfwH9rDsQsiHT30j5pPX/AAARpZQAAAAFJAAAAAG8AAAAASQAAAABSAAAAAEwAAAAAUgAAAABLAAAAAEUAAAAAWw Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 16:51:49 -0000 Hi, Would you be interested in the "Attendees list of Southern California Linux Expo 2017"? Please let me know your interest to send you the number of attendees and cost. Just let me know if you have any questions. Awaiting for your reply Regards, Sandra Lisa, Marketing Executive If you unable to view this mailer: please reply me subject as "Leave Out" From owner-freebsd-net@freebsd.org Fri Feb 3 17:06:23 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BB92CCEBF3 for ; Fri, 3 Feb 2017 17:06: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 4995CE4D for ; Fri, 3 Feb 2017 17:06: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 v13H6MZ9077622 for ; Fri, 3 Feb 2017 17:06:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216731] [patch] if_lagg.c: Boot hang due to LOR in lagg initialization Date: Fri, 03 Feb 2017 17:06:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 17:06:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216731 Alan Somers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asomers@FreeBSD.org --- Comment #1 from Alan Somers --- Can you still reproduce the problem on FreeBSD/head after r309177? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Feb 3 17:44:50 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E6C6CCF804 for ; Fri, 3 Feb 2017 17:44:50 +0000 (UTC) (envelope-from stephen.joseph@united-email.info) Received: from mserver.united-email.info (mail.united-email.info [137.59.52.162]) by mx1.freebsd.org (Postfix) with ESMTP id D63C5783 for ; Fri, 3 Feb 2017 17:44:49 +0000 (UTC) (envelope-from stephen.joseph@united-email.info) Received: from UnitedPC (unknown [202.133.79.30]) by mserver.united-email.info (Postfix) with ESMTPA id D6C12193EC9 for ; Fri, 3 Feb 2017 23:16:06 +0530 (IST) Reply-To: From: "Stephen Joseph" To: Subject: Ask a question Date: Fri, 3 Feb 2017 12:44:43 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdJ+RGg32dUTtj/NTdCiVqtHnt0p4A== Content-Language: en-us x-cr-hashedpuzzle: eKk= AaKW BjcY B/C/ Cahk DA+O DRZt EWAN Ea5j FjVb GBbq GWdD G/QI HanZ Hll2 JrSu; 1; ZgByAGUAZQBiAHMAZAAtAG4AZQB0AEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {69277E5D-88A3-48EE-9BE1-18B80F051D64}; cwB0AGUAcABoAGUAbgAuAGoAbwBzAGUAcABoAEAAdQBuAGkAdABlAGQALQBlAG0AYQBpAGwALgBpAG4AZgBvAA==; Fri, 03 Feb 2017 17:44:04 GMT; QQBzAGsAIABhACAAcQB1AGUAcwB0AGkAbwBuAA== x-cr-puzzleid: {69277E5D-88A3-48EE-9BE1-18B80F051D64} Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 17:44:50 -0000 Hi, My name is Stephen Joseph, the Business Development Manager at one of = the leading email database providing companies.=20 Our area of expertise lies specifically in the major industrial lists = like: Agriculture, Business Services, Chambers of Commerce, Cities, Towns & Municipalities, Construction, Consumer Services, Cultural, Education, Energy, Utilities & Waste Treatment, Finance, Government, Healthcare, Hospitality, Insurance, Law Firms & Legal Services, Manufacturing, Media = & Internet, Metals & Mining, Organizations, Real Estate, Retail, Software, Telecommunications, Transportation, etc. Building long term relationships with our clients is something we = strongly believe in and we go to great lengths to ensure our valuable clients = receive first rate service. Some of the most popular services we offer include: =FC List service #1 - B2B & B2C Email Lists =FC List service #2 -Data Processing & Email Appending =FC List service #3 - Email Campaigning =20 We=92d welcome the opportunity to discuss your email list needs.=20 Best Regards, =20 Stephen Joseph | Business Development Associate | T: +1 610 572 4885 Global Business Data =96 Email Append =96 Data Append. =20 If you are not interested in receiving further emails, please reply back with =93LEAVEOUT=94 in the subject line=94. =20 From owner-freebsd-net@freebsd.org Fri Feb 3 17:52:55 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9D13CCF32A for ; Fri, 3 Feb 2017 17:52:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A294114B1 for ; Fri, 3 Feb 2017 17:52:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v13Hqtpq098455 for ; Fri, 3 Feb 2017 17:52:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216744] [feature request] set DSCP on neighbor solicitation Date: Fri, 03 Feb 2017 17:52: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: 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: 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, 03 Feb 2017 17:52:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216744 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- CC|hiren@FreeBSD.org |ae@FreeBSD.org, | |bz@FreeBSD.org --- Comment #1 from Hiren Panchasara --- Adding bz@ and ae@ too. I am not quite sure if standards are clear on what should be done here so someone with more v6 clue can help. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Feb 4 02:43:02 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23145CCFFAB for ; Sat, 4 Feb 2017 02:43: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 12B5E1FD8 for ; Sat, 4 Feb 2017 02:43: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 v142h1lf056210 for ; Sat, 4 Feb 2017 02:43:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216744] [feature request] set DSCP on neighbor solicitation Date: Sat, 04 Feb 2017 02:43:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@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: Sat, 04 Feb 2017 02:43:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216744 --- Comment #2 from Andrey V. Elsukov --- I didn't seen any information about this in RFC. You can use "ipfw setdscp" rule to set the DSCP, e.g. ipfw add setdscp 56 ip6 from me6 to any icmp6types 135 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Feb 4 18:22:03 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74060CCFC25 for ; Sat, 4 Feb 2017 18:22: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 63BE81D1F for ; Sat, 4 Feb 2017 18:22: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 v14IM3Gm077764 for ; Sat, 4 Feb 2017 18:22:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216731] [patch] if_lagg.c: Boot hang due to LOR in lagg initialization Date: Sat, 04 Feb 2017 18:22: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: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: fbsd@opal.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: Sat, 04 Feb 2017 18:22:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216731 --- Comment #2 from fbsd@opal.com --- I have removed my patch and applied the r309177 patch and am running with t= hat now. Since the deadlock hang was intermittent, I will need to test a while to kn= ow if this resolves the problem. I'll post back in a week or two. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Feb 4 20:44:33 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA16CCCE23B for ; Sat, 4 Feb 2017 20:44:33 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DCEC850 for ; Sat, 4 Feb 2017 20:44:33 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-255-20.albq.qwest.net [67.0.255.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 4D6611928BA for ; Sat, 4 Feb 2017 20:44:26 +0000 (UTC) To: freebsd-net@FreeBSD.org From: Sean Bruno Subject: NFSROOT and lagg(4) Message-ID: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> Date: Sat, 4 Feb 2017 13:44:21 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="9x3klPgfONKGaP07nU2Qc2hAhkPriMqqU" 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, 04 Feb 2017 20:44:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9x3klPgfONKGaP07nU2Qc2hAhkPriMqqU Content-Type: multipart/mixed; boundary="VDsh3wWQ7F9qsHMj2JoPUvtGaftlHedSC"; protected-headers="v1" From: Sean Bruno To: freebsd-net@FreeBSD.org Message-ID: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> Subject: NFSROOT and lagg(4) --VDsh3wWQ7F9qsHMj2JoPUvtGaftlHedSC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable "what I want" is to pxe/netboot and then switch over to using a lagg(4) interface that includes the interface used in the pxe/netboot boot up. I suspect, I have to switch to MDROOT to do this, but I thought I'd ask if anyone is doing this type of configuration in their labs? What seems to happen is that I lose the nfsroot when I reconfigure the lagg, and I no longer have access to reconfigure. e.g. pxeboot from em0, then reconfigure networking to use em0/em1 in lagg= 0: em0: flags=3D8843 metric 0 mtu 15= 00 options=3D5259b ether 00:30:18:c5:0a:a9 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active em1: flags=3D8843 metric 0 mtu 15= 00 options=3D5259b ether 00:30:18:c5:0a:a9 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active lagg0: flags=3D8843 metric 0 mtu = 1500 options=3D5259b ether 00:30:18:c5:0a:a9 inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg laggproto lacp lagghash l2,l3,l4 laggport: em0 flags=3D1c laggport: em1 flags=3D1c --VDsh3wWQ7F9qsHMj2JoPUvtGaftlHedSC-- --9x3klPgfONKGaP07nU2Qc2hAhkPriMqqU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAliWPSlfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmSVvQgAtO+nTcP0gSWhfE82Z9YXpzymmQjo6S2JEWr2LrTIGxRUe5ybr27Ja5c1 7dhEskOIYekAk1LbdaReVc4iSiJArHYceyizb8bPDzQ6LCqsggCz8HSt2oBmGlIp ytM6KQ6prGyDeHVqUxgY7rld6FDt9luB4N7xwRKoapKB1Pj2AdCx5+Az5uTwxyqJ Q1T451AX4gg9U3z16tT7qsVide/WwKHokGI6iVD3wUo5QzWgeY7r24n346nuAKTY KVktLEEt1UlBbeVXazEl/NlU/U6ARRcwZbHOVkj9Yz4Efd40upQrLKq9Y3BO5+bK drArgbkzzk9AayXpcwhYr3q6ez4G0A== =iqrV -----END PGP SIGNATURE----- --9x3klPgfONKGaP07nU2Qc2hAhkPriMqqU-- From owner-freebsd-net@freebsd.org Sat Feb 4 21:01:00 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EDB1CCE91F for ; Sat, 4 Feb 2017 21:01:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 B2FCDF76; Sat, 4 Feb 2017 21:00:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v14L0tWi084614 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Feb 2017 23:00:55 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v14L0tWi084614 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v14L0sUb084613; Sat, 4 Feb 2017 23:00:54 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Feb 2017 23:00:54 +0200 From: Konstantin Belousov To: Sean Bruno Cc: freebsd-net@FreeBSD.org Subject: Re: NFSROOT and lagg(4) Message-ID: <20170204210054.GJ2092@kib.kiev.ua> References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home 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, 04 Feb 2017 21:01:00 -0000 On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote: > "what I want" is to pxe/netboot and then switch over to using a lagg(4) > interface that includes the interface used in the pxe/netboot boot up. > I suspect, I have to switch to MDROOT to do this, but I thought I'd ask > if anyone is doing this type of configuration in their labs? > > What seems to happen is that I lose the nfsroot when I reconfigure the > lagg, and I no longer have access to reconfigure. > > e.g. pxeboot from em0, then reconfigure networking to use em0/em1 in lagg0: > > em0: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > em1: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > lagg0: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255 > nd6 options=29 > media: Ethernet autoselect > status: active > groups: lagg > laggproto lacp lagghash l2,l3,l4 > laggport: em0 flags=1c > laggport: em1 flags=1c > Look at reroot support, see reboot(8) option -r. I suspect you could need two reroots: first to some tmpfs or memory backed md(4) where ifconfig is present to reconfigure interfaces, second to boot into the final root. From owner-freebsd-net@freebsd.org Sat Feb 4 21:05:05 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA5B2CCEA1B for ; Sat, 4 Feb 2017 21:05:05 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C38C1338 for ; Sat, 4 Feb 2017 21:05:05 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-255-20.albq.qwest.net [67.0.255.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id CEE9E1928BA; Sat, 4 Feb 2017 21:05:03 +0000 (UTC) Subject: Re: NFSROOT and lagg(4) To: Konstantin Belousov References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> <20170204210054.GJ2092@kib.kiev.ua> Cc: freebsd-net@FreeBSD.org From: Sean Bruno Message-ID: <7ea86432-a415-a868-e204-ac02b34f0f33@freebsd.org> Date: Sat, 4 Feb 2017 14:04:59 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170204210054.GJ2092@kib.kiev.ua> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uXFwJqITvq7IStrcBwVoifXMGOThvr8r3" 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, 04 Feb 2017 21:05:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uXFwJqITvq7IStrcBwVoifXMGOThvr8r3 Content-Type: multipart/mixed; boundary="wKXujoLTMoPThKl54oklLNi5uOWVoKbx5"; protected-headers="v1" From: Sean Bruno To: Konstantin Belousov Cc: freebsd-net@FreeBSD.org Message-ID: <7ea86432-a415-a868-e204-ac02b34f0f33@freebsd.org> Subject: Re: NFSROOT and lagg(4) References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> <20170204210054.GJ2092@kib.kiev.ua> In-Reply-To: <20170204210054.GJ2092@kib.kiev.ua> --wKXujoLTMoPThKl54oklLNi5uOWVoKbx5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 02/04/17 14:00, Konstantin Belousov wrote: > Look at reroot support, see reboot(8) option -r. I suspect you could > need two reroots: first to some tmpfs or memory backed md(4) where > ifconfig is present to reconfigure interfaces, second to boot into the > final root. I'll look into it. This looks like it might be a little more complicated than just using an MDROOT for my purposes, but I'll definitely take a look. sean --wKXujoLTMoPThKl54oklLNi5uOWVoKbx5-- --uXFwJqITvq7IStrcBwVoifXMGOThvr8r3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAliWQftfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmSgOwf+IRd/2I4ERMqiMma+xHF74bkD9dUMjQzfa27rqvjrUsmik8L4oIOkIESe WqQq1kaZbM8k1Qi5KsY+O8e8bWrnD1feInKQHC5xCGVo1lJtbSf6Z9F/Gu0dwv+J +2nksBJ2Qjymnez2Z0r0HFormcpQamiIPB+J0PT3Ye8y+3ciVeQAd9aVjr/eBi80 0mWL6AGdCpcBNj4AnSM3BLQogIvZ3ypuzXlMMSpq1QjHX3PaV1JgOLoL0Emyf5BE XWdHbfHOb00FGkBd7w3Uy6CUPMonqyspiZIYfS5CW0Bje7gK7/Z/Vcyg55UbUP1A +Wu30GbNeq7WUgwyJLVfBCFj5Ik8rg== =aFWs -----END PGP SIGNATURE----- --uXFwJqITvq7IStrcBwVoifXMGOThvr8r3-- From owner-freebsd-net@freebsd.org Sat Feb 4 21:19:12 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BF40CCED9B for ; Sat, 4 Feb 2017 21:19:12 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDB161870; Sat, 4 Feb 2017 21:19:11 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-yw0-x229.google.com with SMTP id w75so30926221ywg.1; Sat, 04 Feb 2017 13:19:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NDG9IdjpfAg0k8vJ3BvOSX/dW/R2t3dX7AH+N0+UFYw=; b=Q+UxIVROOJA//rUPsYHCEQ27oZuqFsWZhhP1foxN3LtXoLTn4r2dcqOd+Uf5NFET3/ lw/fvi/5kNlGpwbUX9YIHjojjVPOA3elnTDuDJSActmxzJ/D0B+gmo4IqYNclSsdhCKy r9WxfJ2li3gfILvteRnwtQdGEvFvU3jq1n/i3OFZr3fJr/r1enA/QTcn+LPrrvs0qtnF 6FT3AgnygVR7KKvb5oENjHMVwRWh/ERa2qrfLXuLR8CRQWDaAdTTU4GhVvvtyUWlVs8J vmptxQdsTd5Y6t2ro8E8cYpi9g8pFjZcfVwATzn2MIZH4/tdpLGyrzL9tXmg4FLnpaVN 5wxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=NDG9IdjpfAg0k8vJ3BvOSX/dW/R2t3dX7AH+N0+UFYw=; b=csmL+dnU+q1ZKCcN3TeNGXni4KYDxNGxElaqpFAgcbBsRYZN9IsSqF2zVxGUFdqhEa JVTMWcXMhg3DQ8tVKyifoaW3a5oEjERZ5ByoWefBItIeyFjgABoke9BSPdV3SM+xaG+L EEPIPaxXizJwMTIozzNafkmoh856QsmGh8qK5rGrlTY3J98BxdEzEVJI7FNTZkPpJHZg oWMxxEZC6sKJEwf3YHIuXlWolGXzzF1EL2Iay1JxBwU4svvr8DO5E36yucv+Mhh2OTGU CX336Kyq2BXUO38E8SJeHjtq64xWSj3OMqXbQ+4acCBlTPT8rAQMxvOOUuQa2HAWs6gZ vz0Q== X-Gm-Message-State: AIkVDXKyAhAyQcMf2zJ67lXhvcpLpJuJsvwCZJ/vx6U7jqP8sOqsm8UeBb9HAB83l/lhPWdmtUGAo1ZPQl4H2g== X-Received: by 10.129.154.194 with SMTP id r185mr2235923ywg.252.1486243150899; Sat, 04 Feb 2017 13:19:10 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.129.38.133 with HTTP; Sat, 4 Feb 2017 13:19:09 -0800 (PST) Received: by 10.129.38.133 with HTTP; Sat, 4 Feb 2017 13:19:09 -0800 (PST) In-Reply-To: <7ea86432-a415-a868-e204-ac02b34f0f33@freebsd.org> References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> <20170204210054.GJ2092@kib.kiev.ua> <7ea86432-a415-a868-e204-ac02b34f0f33@freebsd.org> From: Alan Somers Date: Sat, 4 Feb 2017 14:19:09 -0700 X-Google-Sender-Auth: 4yJ8RjiGf3xqbqR4iekLxorHJq8 Message-ID: Subject: Re: NFSROOT and lagg(4) To: Sean Bruno Cc: FreeBSD Net , Konstantin Belousov 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, 04 Feb 2017 21:19:12 -0000 Are you mounting NFS with UDP? That handles switching interfaces better than TCP. You might be able to boot on em0, then configure lagg0 on em1, then add em0 to the lagg. On Feb 4, 2017 2:05 PM, "Sean Bruno" wrote: > > > On 02/04/17 14:00, Konstantin Belousov wrote: > > Look at reroot support, see reboot(8) option -r. I suspect you could > > need two reroots: first to some tmpfs or memory backed md(4) where > > ifconfig is present to reconfigure interfaces, second to boot into the > > final root. > > > I'll look into it. This looks like it might be a little more > complicated than just using an MDROOT for my purposes, but I'll > definitely take a look. > > sean > > From owner-freebsd-net@freebsd.org Sat Feb 4 21:38:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAA57CD0398 for ; Sat, 4 Feb 2017 21:38:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DEDF3DB; Sat, 4 Feb 2017 21:38:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ca82W-0002IO-55; Sun, 05 Feb 2017 00:38:36 +0300 Date: Sun, 5 Feb 2017 00:38:36 +0300 From: Slawa Olhovchenkov To: Sean Bruno Cc: freebsd-net@FreeBSD.org Subject: Re: NFSROOT and lagg(4) Message-ID: <20170204213836.GA5366@zxy.spb.ru> References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 21:38:45 -0000 On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote: > "what I want" is to pxe/netboot and then switch over to using a lagg(4) > interface that includes the interface used in the pxe/netboot boot up. > I suspect, I have to switch to MDROOT to do this, but I thought I'd ask > if anyone is doing this type of configuration in their labs? > > What seems to happen is that I lose the nfsroot when I reconfigure the > lagg, and I no longer have access to reconfigure. > > e.g. pxeboot from em0, then reconfigure networking to use em0/em1 in lagg0: > > em0: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > em1: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > lagg0: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255 > nd6 options=29 > media: Ethernet autoselect > status: active > groups: lagg > laggproto lacp lagghash l2,l3,l4 > laggport: em0 flags=1c > laggport: em1 flags=1c > How to you plan to have em0 in LACP and independed from switch side? Know to me, if switch port put to LACP you can't use it indepened. Also, if port on switch side don't put to LACP mode -- you can't UP laggo from FreeBSD side. From owner-freebsd-net@freebsd.org Sat Feb 4 22:29:27 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EA27CD1189 for ; Sat, 4 Feb 2017 22:29:27 +0000 (UTC) (envelope-from eugen@eg.sd.rdtc.ru) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B8EB01AC2; Sat, 4 Feb 2017 22:29:25 +0000 (UTC) (envelope-from eugen@eg.sd.rdtc.ru) X-Envelope-To: freebsd-net@FreeBSD.org Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v14MT9CL056409 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 4 Feb 2017 23:29:10 +0100 (CET) (envelope-from eugen@eg.sd.rdtc.ru) X-Envelope-From: eugen@eg.sd.rdtc.ru Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v14MT1X5077037 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 5 Feb 2017 05:29:01 +0700 (KRAT) (envelope-from eugen@eg.sd.rdtc.ru) Received: (from eugen@localhost) by eg.sd.rdtc.ru (8.15.2/8.15.2/Submit) id v14MT1Lp077036; Sun, 5 Feb 2017 05:29:01 +0700 (KRAT) (envelope-from eugen) Date: Sun, 5 Feb 2017 05:29:01 +0700 From: Eugene Grosbein To: Sean Bruno Cc: freebsd-net@FreeBSD.org Subject: Re: NFSROOT and lagg(4) Message-ID: <20170204222901.GA24841@rdtc.ru> References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> User-Agent: Mutt/1.7.1 (2016-10-04) X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,LOCAL_FROM,RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail * domains are different * 0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 22:29:27 -0000 On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote: > "what I want" is to pxe/netboot and then switch over to using a lagg(4) > interface that includes the interface used in the pxe/netboot boot up. > I suspect, I have to switch to MDROOT to do this, but I thought I'd ask > if anyone is doing this type of configuration in their labs? > > What seems to happen is that I lose the nfsroot when I reconfigure the > lagg, and I no longer have access to reconfigure. Why would you lose something if you use same IP address at both stages? NFS over UDP or TCP binds sockets to IP, not network interfaces. You just need to make sure you have statically linked shell and ifconfig utility handy in tmpfs or md device before you try to enable LACP. I do not think reroot is needed there. First you create tmpfs and mount to /mnt, then copy /rescue and script doing LACP configuration using /mnt/rescue/ifconfig there, then run it using "/mnt/rescue/sh /mnt/run_my_lacp" As soon as your script brings LACP up and moves IP address there, you would be fine. Eugene Grosbein From owner-freebsd-net@freebsd.org Sat Feb 4 22:40:50 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE2AECD13E3 for ; Sat, 4 Feb 2017 22:40:50 +0000 (UTC) (envelope-from eugen@eg.sd.rdtc.ru) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 414EB1F60; Sat, 4 Feb 2017 22:40:49 +0000 (UTC) (envelope-from eugen@eg.sd.rdtc.ru) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v14MejIm056455 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 4 Feb 2017 23:40:46 +0100 (CET) (envelope-from eugen@eg.sd.rdtc.ru) X-Envelope-From: eugen@eg.sd.rdtc.ru X-Envelope-To: sbruno@freebsd.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v14MegS2084961 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 5 Feb 2017 05:40:42 +0700 (KRAT) (envelope-from eugen@eg.sd.rdtc.ru) Received: (from eugen@localhost) by eg.sd.rdtc.ru (8.15.2/8.15.2/Submit) id v14Meghw084960; Sun, 5 Feb 2017 05:40:42 +0700 (KRAT) (envelope-from eugen) Date: Sun, 5 Feb 2017 05:40:42 +0700 From: Eugene Grosbein To: Sean Bruno Cc: freebsd-net@FreeBSD.org Subject: Re: NFSROOT and lagg(4) Message-ID: <20170204224042.GA82183@rdtc.ru> References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> User-Agent: Mutt/1.7.1 (2016-10-04) X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,LOCAL_FROM,RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail * domains are different * 0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2017 22:40:50 -0000 On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote: > "what I want" is to pxe/netboot and then switch over to using a lagg(4) > interface that includes the interface used in the pxe/netboot boot up. [skip] > lagg0: flags=8843 metric 0 mtu 1500 > > options=5259b > ether 00:30:18:c5:0a:a9 > inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255 > nd6 options=29 > media: Ethernet autoselect > status: active > groups: lagg > laggproto lacp lagghash l2,l3,l4 OTOH, how do you expect make other side of link pass IP packets to your side before LACP protocol configures a port? Do you have pxe/netboot client capable of LACP? I guess, you'll have to stick with protocol-less "failover" LAGG mode using just physical link states. Eugene Grosbein