From owner-freebsd-net@freebsd.org Sun Nov 26 20:53:42 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 6016ADF056D for ; Sun, 26 Nov 2017 20:53:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 455827789D for ; Sun, 26 Nov 2017 20:53:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAQKrgU4062594 for ; Sun, 26 Nov 2017 20:53:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223824] [arm64] Kernel panic in ng_base.c (netgraph) Date: Sun, 26 Nov 2017 20:53:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: aonishenko@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 20:53:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223824 --- Comment #4 from aonishenko --- Done! Here the output: Multi-link PPP daemon for FreeBSD process 841 started, version 5.8Kernel page fault with the following non-sleepab exclusive sleep mutex ng_node (ng_node) r =3D 0 (0xfffffd00014e6670) locked= @ /usr stack backtrace: #0 0xff (rooff000000368f00 at witness_debugger+0x64 #1 0xffff000000arm64-defaul36a260 at witness_warn+0x43c #2 0xffff000000616104 at data_abot-job-20 03:rt+0xe0 #3 0xffff0000005ff874 at hand38 18-le_el1h_sync+0x74 #4 0xffff00000041d22c at ng_snd_item+017) x3bc #5 0xffff000000433cf0 at ngc_send+0x20c #6 0xffff0000003969d4 at sosend_generic+0x380 #7 0xffff00000039cd14 at kern_sendit+0x28c #8 0xffff00000039cffc at sendit+0x1a4 #9 0xffff00000039ce48 at sys_sendto+0x50 #10 0xffff000000616afc at do_el0_sync+0x884 #11 0xffff0000005ff9f4 at handle_el0_sync+0x74 x0: fffffd00014e6670 x1: 8 x2: ffff0000006ad8a0 x3: 915 x4: 0 x5: 0 x6: fffffd00184b0c40 x7: 40 x8: 2 x9: 0 x10: 18 x11: 10000 x12: ffff000000a52648 x13: ffffffff x14: 0 x15: fffffd00184b0b60 x16: 406002b0 x17: 407924e4 x18: ffff00004034c6f0 x19: 0 x20: fffffd00014e6688 x21: fffffd00014e6600 x22: ffff0000006ad8a0 x23: fffffd00014e6668 x24: ffff00004034c740 x25: fffffd000164a038 x26: fffffd00184014c0 x27: fffffd0001c20370 x28: 0 x29: ffff00004034c720 sp: ffff00004034c6f0 lr: ffff00000041d230 elr: ffff00000041d23c spsr: 80000345 far: 0 esr: 96000007 panic: data abort in critical section or under mutex cpuid =3D 3 time =3D 1511729548 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff0000005fde50 lr =3D 0xffff000000088b88 sp =3D 0xffff00004034c150 fp =3D 0xffff00004034c360 db_trace_self_wrapper() at vpanic+0x184 pc =3D 0xffff000000088b88 lr =3D 0xffff00000030bb30 sp =3D 0xffff00004034c370 fp =3D 0xffff00004034c3f0 vpanic() at panic+0x48 pc =3D 0xffff00000030bb30 lr =3D 0xffff00000030bbbc sp =3D 0xffff00004034c400 fp =3D 0xffff00004034c480 panic() at data_abort+0x250 pc =3D 0xffff00000030bbbc lr =3D 0xffff000000616274 sp =3D 0xffff00004034c490 fp =3D 0xffff00004034c540 data_abort() at handle_el1h_sync+0x74 pc =3D 0xffff000000616274 lr =3D 0xffff0000005ff874 sp =3D 0xffff00004034c550 fp =3D 0xffff00004034c660 handle_el1h_sync() at ng_snd_item+0x3bc pc =3D 0xffff0000005ff874 lr =3D 0xffff00000041d22c sp =3D 0xffff00004034c670 fp =3D 0xffff00004034c720 ng_snd_item() at ngc_send+0x20c pc =3D 0xffff00000041d22c lr =3D 0xffff000000433cf0 sp =3D 0xffff00004034c730 fp =3D 0xffff00004034c7b0 ngc_send() at sosend_generic+0x380 pc =3D 0xffff000000433cf0 lr =3D 0xffff0000003969d4 sp =3D 0xffff00004034c7c0 fp =3D 0xffff00004034c860 sosend_generic() at kern_sendit+0x28c pc =3D 0xffff0000003969d4 lr =3D 0xffff00000039cd14 sp =3D 0xffff00004034c870 fp =3D 0xffff00004034c900 kern_sendit() at sendit+0x1a4 pc =3D 0xffff00000039cd14 lr =3D 0xffff00000039cffc sp =3D 0xffff00004034c910 fp =3D 0xffff00004034c950 sendit() at sys_sendto+0x50 pc =3D 0xffff00000039cffc lr =3D 0xffff00000039ce48 sp =3D 0xffff00004034c960 fp =3D 0xffff00004034c9a0 sys_sendto() at do_el0_sync+0x884 pc =3D 0xffff00000039ce48 lr =3D 0xffff000000616afc sp =3D 0xffff00004034c9b0 fp =3D 0xffff00004034ca70 do_el0_sync() at handle_el0_sync+0x74 pc =3D 0xffff000000616afc lr =3D 0xffff0000005ff9f4 sp =3D 0xffff00004034ca80 fp =3D 0xffff00004034cb90 handle_el0_sync() at 0x405e4e28 pc =3D 0xffff0000005ff9f4 lr =3D 0x00000000405e4e28 sp =3D 0xffff00004034cba0 fp =3D 0x0000ffffffffe620 KDB: enter: panic [ thread pid 841 tid 100115 ] Stopped at kdb_enter+0x40: undefined d4200000 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Nov 26 21:02:36 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E6DCDF0881 for ; Sun, 26 Nov 2017 21:02:36 +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 3CF9977D13 for ; Sun, 26 Nov 2017 21:02:36 +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 vAQL2ZwK086850 for ; Sun, 26 Nov 2017 21:02:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223824] [arm64] Kernel panic in ng_base.c (netgraph) Date: Sun, 26 Nov 2017 21:02:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: aonishenko@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 21:02:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223824 --- Comment #5 from aonishenko --- Here is more detailed out root@rpi3:/usr/home/pi # service mpd5 onestart Starting mpd5. root@rpi3:/usr/home/pi # Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex ng_node (ng_node) r =3D 0 (0xfffffd0001b14e70) locked= @ /usr/local/src/CURR/head/sys/netgraph/ng_base.c:2325 stack backtrace: #0 0xffff000000368f00 at witness_debugger+0x64 #1 0xffff00000036a260 at witness_warn+0x43c #2 0xffff000000616104 at data_abort+0xe0 #3 0xffff0000005ff874 at handle_el1h_sync+0x74 #4 0xffff00000041d22c at ng_snd_item+0x3bc #5 0xffff000000433cf0 at ngc_send+0x20c #6 0xffff0000003969d4 at sosend_generic+0x380 #7 0xffff00000039cd14 at kern_sendit+0x28c #8 0xffff00000039cffc at sendit+0x1a4 #9 0xffff00000039ce48 at sys_sendto+0x50 #10 0xffff000000616afc at do_el0_sync+0x884 #11 0xffff0000005ff9f4 at handle_el0_sync+0x74 x0: fffffd0001b14e70 x1: 8 x2: ffff0000006ad8a0 x3: 915 x4: 0 x5: 2 x6: fffffd0001fa8d20 x7: 40 x8: 2 x9: 0 x10: 18 x11: 10000 x12: ffff000000a52868 x13: ffffffff x14: 0 x15: fffffd0001fa8c40 x16: 406002b0 x17: 407924e4 x18: ffff00004031f6f0 x19: 0 x20: fffffd0001b14e88 x21: fffffd0001b14e00 x22: ffff0000006ad8a0 x23: fffffd0001b14e68 x24: ffff00004031f740 x25: fffffd0001bcc238 x26: fffffd0001de0200 x27: fffffd0001cf8018 x28: 0 x29: ffff00004031f720 sp: ffff00004031f6f0 lr: ffff00000041d230 elr: ffff00000041d23c spsr: 80000345 far: 0 esr: 96000007 panic: data abort in critical section or under mutex cpuid =3D 1 time =3D 1511729631 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff0000005fde50 lr =3D 0xffff000000088b88 sp =3D 0xffff00004031f150 fp =3D 0xffff00004031f360 db_trace_self_wrapper() at vpanic+0x184 pc =3D 0xffff000000088b88 lr =3D 0xffff00000030bb30 sp =3D 0xffff00004031f370 fp =3D 0xffff00004031f3f0 vpanic() at panic+0x48 pc =3D 0xffff00000030bb30 lr =3D 0xffff00000030bbbc sp =3D 0xffff00004031f400 fp =3D 0xffff00004031f480 panic() at data_abort+0x250 pc =3D 0xffff00000030bbbc lr =3D 0xffff000000616274 sp =3D 0xffff00004031f490 fp =3D 0xffff00004031f540 data_abort() at handle_el1h_sync+0x74 pc =3D 0xffff000000616274 lr =3D 0xffff0000005ff874 sp =3D 0xffff00004031f550 fp =3D 0xffff00004031f660 handle_el1h_sync() at ng_snd_item+0x3bc pc =3D 0xffff0000005ff874 lr =3D 0xffff00000041d22c sp =3D 0xffff00004031f670 fp =3D 0xffff00004031f720 ng_snd_item() at ngc_send+0x20c pc =3D 0xffff00000041d22c lr =3D 0xffff000000433cf0 sp =3D 0xffff00004031f730 fp =3D 0xffff00004031f7b0 ngc_send() at sosend_generic+0x380 pc =3D 0xffff000000433cf0 lr =3D 0xffff0000003969d4 sp =3D 0xffff00004031f7c0 fp =3D 0xffff00004031f860 sosend_generic() at kern_sendit+0x28c pc =3D 0xffff0000003969d4 lr =3D 0xffff00000039cd14 sp =3D 0xffff00004031f870 fp =3D 0xffff00004031f900 kern_sendit() at sendit+0x1a4 pc =3D 0xffff00000039cd14 lr =3D 0xffff00000039cffc sp =3D 0xffff00004031f910 fp =3D 0xffff00004031f950 sendit() at sys_sendto+0x50 pc =3D 0xffff00000039cffc lr =3D 0xffff00000039ce48 sp =3D 0xffff00004031f960 fp =3D 0xffff00004031f9a0 sys_sendto() at do_el0_sync+0x884 pc =3D 0xffff00000039ce48 lr =3D 0xffff000000616afc sp =3D 0xffff00004031f9b0 fp =3D 0xffff00004031fa70 do_el0_sync() at handle_el0_sync+0x74 pc =3D 0xffff000000616afc lr =3D 0xffff0000005ff9f4 sp =3D 0xffff00004031fa80 fp =3D 0xffff00004031fb90 handle_el0_sync() at 0x405e4e28 pc =3D 0xffff0000005ff9f4 lr =3D 0x00000000405e4e28 sp =3D 0xffff00004031fba0 fp =3D 0x0000ffffffffe770 KDB: enter: panic [ thread pid 651 tid 100106 ] Stopped at kdb_enter+0x40: undefined d4200000 db> --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 05:21:38 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 7466EDF9350 for ; Mon, 27 Nov 2017 05:21:38 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (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 3D3EC643A5 for ; Mon, 27 Nov 2017 05:21:37 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id F40CB29C39 for ; Mon, 27 Nov 2017 06:15:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1511759715; bh=mYANuyGEak0yh4H0IhedlDoUku+4CcjkrPVdu7QVOr0=; h=To:From:Subject:Date; b=sH+QO+lhTZdmc0eOqTnRtMLLHYD89BIWLpDz2ZKK8uhgQKKC4SuTWnEHHMp7pWGOr lY0tLqsvqkPjS42RILJIqeF9iSBRaiXjGTTOA16H8zL9Zz0GPYauZpFP31m30/Vuk9 AxxyUvogXlieiCfQgvJT44ABcQSDL0J7UXGAbqz0= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgDvmjB6OE06 for ; Mon, 27 Nov 2017 06:15:13 +0100 (CET) To: freebsd-net@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1511759713; bh=mYANuyGEak0yh4H0IhedlDoUku+4CcjkrPVdu7QVOr0=; h=To:From:Subject:Date; b=qn2L0SgEI5cERWcrEaLSBP7cWkeKz4xYOFQFLA36YpAYyfY8UKLo5OCSmPYCjiope DBUsDymSuphvKy+Z6xVKK3fvRHDdvgx3+btSWb6Cb9WEyM7KPdDdv+6KI4SDJgN6sO x196Nr5l1vFk841q74KMZz8Kx4gEKNjlk+qEPUFI= From: "Peter G." Subject: Static IPsec (via setkey) and -A aes-xcbc-mac, how to? Message-ID: Date: Mon, 27 Nov 2017 06:15:10 +0100 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 05:21:38 -0000 Hi, can somebody please show me the correct syntax of setting static SA with aes-xcbc-mac authentication? I checked rfc3566, my "base" encryption algo is aes-128, aes-xcbc-mac is supposed to work with a 128-bit (16 characters) long key. I don't seem to be able to set it up, though. Example (aes-cbc 128bit + supposedly aes-xcbc-mac): add 10.10.1.1 10.10.2.2 esp 400 -m transport -u 400 -E rijndael-cbc "abcdefghijklmnop" -A aes-xcbc-mac "1234567890123456"; ends up in an error: line 5: Not supported at [1234567890123456] parse failed, line 5. The same syntax and appropriate key length work with anything else, e.g. hmac-sha2-256 with 32 character long key works just fine. Please advice. PG From owner-freebsd-net@freebsd.org Mon Nov 27 08:33: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 E0FF4DFC2A3 for ; Mon, 27 Nov 2017 08:33:07 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88D3169062 for ; Mon, 27 Nov 2017 08:33:07 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id w125so31368343qkb.6 for ; Mon, 27 Nov 2017 00:33:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pyrfb4ZDA/Rt0YB+rR199JLRt5G3LEDH95yC6INYj0c=; b=a37KlsQTDhJxrZV4oOd2PHMRPpMRXEm3ezLu5A6cALl+gsX3nv8e1lQaUDUdaq5qAE Nx2IyoIs2fNY5/f1zeuTobYCpzlGGwBWlBOwTh+IYowLl5kot+o/ACwZRqTvyEE8+IS2 8FM5kWwFwoQjnlNtxsTyAVnRUKqMPgc/3sI4spEWqzfKndRpcoPjR//ECnLX45i6Lo9E yMpaTDKip5uKDWIPMmBwBTa5e+5bAA3khalo+NdYaxrZF3Hiu6INhJMoqrbJnd0gsRoW PDDdiGOxbMzHPOoEaL9TCxDMrzpVjQ9v5qr68A9pZMJkn/yl2iaO3U047FFsQV3WQ42s mEfw== 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=pyrfb4ZDA/Rt0YB+rR199JLRt5G3LEDH95yC6INYj0c=; b=sXNAiI1cKVjxdSFTWRG2jtIvZWQQZGQKs501cDsab7O57odlQA+m4I4ssiilyiAQCY 1wqu40nPoWqBFIvGkGsVT3sxiyEpuuAYiBSMNY5IGixWhwtXjkGKzSCEwfo/6KVSFO1A 2RTp9p/F9T0m+YTfKJ9TaAeoULsNyoKjhiY5Z1orzejQ9Oc7/iMkMmMn+WBGBaCmGiMq uVeQ4wVvPhgCfNxc86f1gVzYI36Zh+jxJAkQSQo9Hq65dsirZNjkEUFFKO40nUwpgUnV JxLTXvJb06UquWXXasLUtyYBvsvvNQB0qThIRGFJYaEd6yQTP8mT+2yAr5kMNXtm98g5 A/xA== X-Gm-Message-State: AJaThX4FJOuoM92M4EhTPOvXj1fauanMG6VffGeypNWifXhKsUELuukC BgASKVdCtZhK/Kdrv5qYiJO09jnqsUkdomWt47o= X-Google-Smtp-Source: AGs4zMaOp9M2wC44v3wgLyY5N5iL8ETPznmmxNpUo1RhZT4mPlXJWDoWRyQGM1T2l8RKc4K0k3hP9fr9zFTHNaw3Mpw= X-Received: by 10.55.152.129 with SMTP id a123mr25330305qke.142.1511771586459; Mon, 27 Nov 2017 00:33:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.174.5 with HTTP; Mon, 27 Nov 2017 00:33:06 -0800 (PST) In-Reply-To: References: From: Vincenzo Maffione Date: Mon, 27 Nov 2017 09:33:06 +0100 Message-ID: Subject: Re: swaping ring slots between NIC ring and Host ring does not always success To: Xiaoye Sun Cc: Luigi Rizzo , "freebsd-net@freebsd.org" , Victor Detoni , Pavel Odintsov , Giuseppe Lettieri Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 08:33:08 -0000 Hi, If you think it's a bug can you please open an issue on the github ( https://github.com/luigirizzo/netmap/issues)? 2017-11-24 22:11 GMT+01:00 Xiaoye Sun : > Hi Vincenzo, > > Let me clarify my problem. (please ignore the previous incompleted email) > > I have a program, which is an extension of bridge.c > https://github.com/luigirizzo/netmap/blob/master/apps/bridge/bridge.c > The only difference is that my program also generates customized packets > sent to the NIC directly. > These customized packets have increasing sequence numbers. > So, this program not only sends these customized packets but also forwards > packets between NIC and host stack using zerocopy. > The program only takes one NIC queue and there is only one thread. > > I think the problem is that there is a chance where netmap does not update > the pointer to the buffer even when NS_BUF_CHANGED is set (buf_idx is > changed). > Can you disable zerocopy in bridge.c to see if the problem goes away? This would be an useful information. > > Let's say the NIC tx ring has 4096 slots. The customized packet sequence > 16 is filled in the buffer of slot 2057. > The customized packets keep filling the slots until the next available > slot is 2056. > Do you mean that your program fills the TX ring slots 2057,2058...2054,2055 with custom packets? This would mean you filled all the available slots, since one slot is left empty. > Now the customised packet sequence 4111 is filled to 2056. > You cannot fill the slot 2056 if 2055 has not been NIOCTXYSINC'd. Aren't you using nm_ring_empty() and nm_ring_space() functions to check for available space in TX ring (assuming you update rinig->head/ring->cur before calling those functions)? Cheers, Vincenzo > Then the netmap program is notified that there is a packet from the host > stack sent to the NIC. > The netmap program swaps the buf_idx between slot 2057 and the > corresponding slot in the host rx ring and set the NS_BUF_CHANGED flag of > both slots. > Then the netmap program fills sequence 4112 to slot 2058. > However, the buffer swap seems not succeed so that the original content of > slot 2057 (sequence 16) is sent out. > So that at the receiver side, the receiver sees two sequence > 16s.(16,17...4110,4111,16,4112,4113). > > So think the root of the problem is that the buffer pointer is not always > successfully/timely updated even after the NS_BUF_CHANGED flag is set and > the buf_idx is updated. > > Best, > Xiaoye > > > > On Wed, Nov 22, 2017 at 7:39 AM, Vincenzo Maffione > wrote: > >> Hi, >> >> 2017-11-21 7:51 GMT+01:00 Xiaoye Sun : >> >>> Hi, >>> >>> Recently I found another problem with netmap. I think this new problem >>> could be related to the problems in this threads so I just post the new >>> problem here. >>> >>> In my setup, I have a sender program having a netmap ring (a pair of >>> RX/TX ring) for the NIC and a ring for the host stack. The sender program >>> puts customized packets (each packet has a unique sequence number and the >>> sender sends the packet in a sequence number increasing order) to the NIC >>> TX ring directly and also forwards the packets from the host RX ring to >>> the >>> NIC TX ring using "zerocopy" by swapping the buffer indices. >>> However, the receiver sees duplicated customized packets. For example, in >>> the case where the ring size is 32 (32 slots in a ring) the order of the >>> sequence numbers the receiver see is 1,2,3,4,5,...,68,69,*70* >>> ,71,72,73,...,99,100,*70*,101,102,103,... . An interesting thing I >>> found is >>> that the "gaps" between these two duplicated packets (70 in the example) >>> are always a number very close to the ring size, 32 in this example. In >>> my >>> experiment, I use a ring with 4096 slots and the gap is always more than >>> 4090 and close to 4096. I verified that this duplication happens due to >>> the >>> sender, not the receiver. Assuming my sender's implementation is correct, >>> then this duplication may happen in netmap and the NIC driver (ixgbe). >>> >> >> Netmap itself doesn't do any duplication nor takes a look at the packets. >> It just passes >> down ring->cur/ring->head to the ixgbe driver (after validation). >> The ixgbe driver datapath is bypassed and replaced with a netmap-enabled >> datapath (see https://github.com/luigirizzo/ >> netmap/blob/master/LINUX/ixgbe_netmap_linux.h#L294-L461); >> no duplication should happen there as each netmap slot (1 TX packet) is >> used >> only once. >> >>> >>> >>> Thinking back to the original problem in this post, I think these >>> problems >>> may be related. It seems to me that there could be multiple threads >>> pulling >>> the packets from the NIC TX ring (or the thread moved to other CPUs when >>> the problem occurs) and these threads may run on different cores so that >>> the outdated content in the buffer may be sent out when new content is >>> written to the buffer. >>> >>> >> There are no such threads pulling from the NIC TX ring. Your application >> directly >> puts new packets to be transmitted in the netmap buffers referenced in >> the netmap TX >> ring. When then you call NIOCTXSYNC or poll(), all the new TX buffers >> (e.g. all >> the ones from the previous value ring->head (included) to the new value >> of ring->head (excluded)) >> are moved to the NIC TX ring. This happens in the context of your >> application thread, >> no worker threads are used. Then the NIC hardware starts the transmission. >> >> >>> I am wondering if there is a way to pin the NIC driver of the netmap >>> module >>> to a specific core. or is there a way to know the root of such problem? >>> >> >> The only threads are the ones of your application. >> Maybe your problem comes from concurrent accesses to the netmap TX ring >> from different threads? Only one thread at a given time should update a >> netmap >> TX/RX ring. Otherwise the behaviour is unspecified. >> >> Cheers, >> Vincenzo >> >> >>> >>> Best, >>> Xiaoye >>> >>> >> -- >> Vincenzo Maffione >> > > -- Vincenzo Maffione From owner-freebsd-net@freebsd.org Mon Nov 27 12:11:21 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 EB566DFF96D for ; Mon, 27 Nov 2017 12:11:21 +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 D54866E73D for ; Mon, 27 Nov 2017 12:11:21 +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 vARCBKv8080042 for ; Mon, 27 Nov 2017 12:11:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223824] [arm64] Kernel panic in ng_base.c (netgraph) Date: Mon, 27 Nov 2017 12:11:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 12:11:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223824 --- Comment #6 from Eugene Grosbein --- I did not work with ARM yet, so I may be completely wrong, but it seems to = me we have several problems here. First, netgraph's ng_snd_item() function does something wrong (NULL pointer dereference?) at causes exception. Then, cont= rol passes to handle_el1h_sync that does something wrong again (?) causing seco= nd exception due to ARM64 platform-specific "data abort" exception. Someone with ARM64 knowledge is needed here. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 13:23:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D5CDE5123D for ; Mon, 27 Nov 2017 13:23:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15D7670EC7 for ; Mon, 27 Nov 2017 13:23:13 +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 vARDNCJZ013407 for ; Mon, 27 Nov 2017 13:23:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223817] mbuf leaking with tcpmd5 Date: Mon, 27 Nov 2017 13:23:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: regression 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: ae@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 13:23:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223817 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |ae@FreeBSD.org --- Comment #6 from Andrey V. Elsukov --- Created attachment 188313 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188313&action= =3Dedit Proposed patch If dtrace script will show 13 return code, then probably my assumption is correct and you can try this patch. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 15:58: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 0CDCAE55D59 for ; Mon, 27 Nov 2017 15:58:05 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from disroot.org (bs-one.disroot.org [178.21.23.139]) (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 C6B7C78CD1 for ; Mon, 27 Nov 2017 15:58:04 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 8C45029C9F for ; Mon, 27 Nov 2017 16:57:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1511798276; bh=UkDhgXrlRQeIqduZIBAs5GpGkIBi86TzXITFz8erH9s=; h=Subject:From:To:References:Date:In-Reply-To; b=wUl4Q5jbpj84Ng3mmeb3CgGhJsGsPy7Y9ZQywhUJ78h5PTXBvzRKWXPkz/KPf/7LR iPMwqarh6vldVWSI+k4y/cokVEEyDqvgvEaWsN4NLoHkKfouQSlipNuQNsrLGRLW4K 4Q+VRdqC+2NIfwUHdmW035eWdmUIe7nDttQO3N0o= X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from disroot.org ([127.0.0.1]) by localhost (mail01.disroot.lan [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7i-EN_ln_DM for ; Mon, 27 Nov 2017 16:57:48 +0100 (CET) Subject: Re: Static IPsec (via setkey) and -A aes-xcbc-mac, how to? DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1511798268; bh=UkDhgXrlRQeIqduZIBAs5GpGkIBi86TzXITFz8erH9s=; h=Subject:From:To:References:Date:In-Reply-To; b=R/tvcZPpFBPOtKzJHz+3Fc+gCWlnhSpuKFDh/WDY7xnd0ZWMfFb1M/cXcCfgMl8yx 3BJN4Vn3vpRZT2eQUwp4DQ0HgPVaYcv5evIXJ+aHYSRrxcRzPSvIsXU5+8uIuqE0Em vyC75AS8qRpApckzTI6OhPoQ0VgUdLge0aDPo6Xc= From: "Peter G." To: freebsd-net@freebsd.org References: Message-ID: Date: Mon, 27 Nov 2017 16:57:44 +0100 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 15:58:05 -0000 On 27/11/2017 06:15, Peter G. wrote: > Hi, can somebody please show me the correct syntax of setting static SA > with aes-xcbc-mac authentication? I checked rfc3566, my "base" > encryption algo is aes-128, aes-xcbc-mac is supposed to work with a > 128-bit (16 characters) long key. I don't seem to be able to set it up, > though. > > Example (aes-cbc 128bit + supposedly aes-xcbc-mac): > > add 10.10.1.1 10.10.2.2 esp 400 -m transport -u 400 -E rijndael-cbc > "abcdefghijklmnop" -A aes-xcbc-mac "1234567890123456"; > > ends up in an error: > > line 5: Not supported at [1234567890123456] > parse failed, line 5. > > The same syntax and appropriate key length work with anything else, e.g. > hmac-sha2-256 with 32 character long key works just fine. > Oh, I am on 11.1. I've found two docs which clearly make this possible: Firstly, a blog entry in Japanese: https://moimoitei.blogspot.com/2009/10/measure-ipsec-throughput.html Secondly, some company's paper on some of their tech (not really important), but usage of -E aes-ctr with -A aes-xcbc-mac is listed as an option, page 20: http://www.lobaro.com/download/6lowpan/ZWIR45xx_AN_Security_Rev_1_30.pdf I've also reviewed evolution of aes support for cryptodev, e.g. starting here: https://reviews.freebsd.org/D2566 and all the source files related to either setkey (for example sbin/setkey/token.l) or opencrypto in the sources list or at least note aes-xcbc-mac availability. Does anybody know how to get this working? Or does this mean there's no actual kernel support for aes-xcbc-mac? Thanks! PG From owner-freebsd-net@freebsd.org Mon Nov 27 16:03:36 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6082DB80CE for ; Mon, 27 Nov 2017 16:03:36 +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 C40027908B for ; Mon, 27 Nov 2017 16:03:36 +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 vARG3aAc048496 for ; Mon, 27 Nov 2017 16:03:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Mon, 27 Nov 2017 16:03:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: pautina@kharkiv.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 16:03:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 Alexey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |Not A Bug Severity|Affects Only Me |Affects Many People --- Comment #12 from Alexey --- I'm not sure if this is a bug. Maybe just for this faket must be mentioned = in the documentation --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 16:42: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 D8230DB91EB for ; Mon, 27 Nov 2017 16:42: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 C64357A8FE for ; Mon, 27 Nov 2017 16:42: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 vARGgkPV041637 for ; Mon, 27 Nov 2017 16:42:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Mon, 27 Nov 2017 16:42: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.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 16:42:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 --- Comment #13 from Andrey V. Elsukov --- (In reply to Alexey from comment #12) > I'm not sure if this is a bug. Maybe just for this faket must be mentioned > in the documentation I think it is driver's bug and driver should be fixed if it does not correc= tly support checksum offloading. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 17:25: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 197BADBA264 for ; Mon, 27 Nov 2017 17:25:53 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 588F47C20F for ; Mon, 27 Nov 2017 17:25:51 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id vARHPfAN034118 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Nov 2017 09:25:41 -0800 (PST) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id vARHPeXp034106; Mon, 27 Nov 2017 09:25:40 -0800 (PST) (envelope-from jmg) Date: Mon, 27 Nov 2017 09:25:40 -0800 From: John-Mark Gurney To: Michal =?iso-8859-1?Q?Bucht=EDk?= Cc: freebsd-net@freebsd.org Subject: Re: vlans + bridging is "interesting" Message-ID: <20171127172540.GX42467@funkthat.com> Mail-Followup-To: Michal =?iso-8859-1?Q?Bucht=EDk?= , freebsd-net@freebsd.org References: <20171125014755.GN42467@funkthat.com> <7b55197b-8f9d-6a54-3db4-70d4fc52abd0@borsice.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b55197b-8f9d-6a54-3db4-70d4fc52abd0@borsice.net> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Mon, 27 Nov 2017 09:25:41 -0800 (PST) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 17:25:53 -0000 Michal Buchtk wrote this message on Sat, Nov 25, 2017 at 10:32 +0100: > maybe i don't understand you needs, but why do you create bridge0 and > add local ip's to it?. Because I want/need to be able to run VM's also on em0's untagged domain. > When you would like to see untaged packets on VM, to this simple setup: > keep em0 as "trunk" interface > create interface em0.14 > create bridge14 and add to it interfaces tap0 and em0.14 > add local ip to bridge14 > > ifconfig em0.14 create > ifconfig em0.14 up > ifconfig bridge14 create > ifconfig bridge14 addm tap0 addm em0.14 > ifconfig bridge14 up > ifconfig bridge14 > > then your VM will can communicate (untagged) with your host system, and > you will see tagged packets on em0 (and untagged on em0.14 of course) Yes, and that prevents me running some of my VM's that I want to be able to... > Dne 25.11.2017 v 2:47 John-Mark Gurney napsal(a): > > Hello, > > > > I decided to try to run some bhyve VM's on my machine and bridge > > them to a guest vlan on my main interface. I also want to support > > running bhyve VM's on the untagged part of the interface as well > > (this is the key problem as I'll describe later). > > > > I configure it as you'd expect. Bridge the main interface em0, and > > put the local IP's on the bridge0. Then I added an interface em0.14 > > that untags packets from em0, and added it to bridge1 along w/ a tap0 > > for the VM. This does not work. Packet goes out and comes back and > > is observed on em0, but never appears on either em0.14 or bridge1. > > > > After seeing: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139268 > > > > I decide to look on bridge0, and see the tagged vlan packet on that > > interface. I attempted to add bridge0 as the vlandev for em0.14, but > > that doesn't work: > > #ifconfig em0.14 vlan 14 vlandev bridge0 > > ifconfig: SIOCSETVLAN: Protocol not supported > > > > So, I did finally get things working by using epair. I added an epair > > to the bridge, and that allows me to untag the packet, and pass on to > > bridge1. > > > > I have not attempted to use the patch in 139268, but if people think > > it is an acceptable solution (with patch, if I set LINK0, it should work > > w/ original configuration), I'll test and commit the patch. > > > > Otherwise, please submit another fix. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-net@freebsd.org Mon Nov 27 17:27: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 A1DFCDBA37E for ; Mon, 27 Nov 2017 17:27:12 +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 4EA187C3FF for ; Mon, 27 Nov 2017 17:27: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 vARHRA2g045558 for ; Mon, 27 Nov 2017 17:27:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Mon, 27 Nov 2017 17:27:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: pautina@kharkiv.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 17:27:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 --- Comment #14 from Alexey --- (In reply to Andrey V. Elsukov from comment #13) What do I do in this case, reopen the issue? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 17:29:30 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57A2BDBA4E8 for ; Mon, 27 Nov 2017 17:29:30 +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 457A27C644 for ; Mon, 27 Nov 2017 17:29:30 +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 vARHTTeo048851 for ; Mon, 27 Nov 2017 17:29:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Mon, 27 Nov 2017 17:29: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.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 17:29:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbruno@FreeBSD.org Keywords| |IntelNetworking --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Nov 27 17:36: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 7EB84DBA7E4 for ; Mon, 27 Nov 2017 17:36: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 6CC597CCE6 for ; Mon, 27 Nov 2017 17:36:59 +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 vARHawSH068352 for ; Mon, 27 Nov 2017 17:36:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Mon, 27 Nov 2017 17:36: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.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: pautina@kharkiv.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 17:36:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 Alexey changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|Not A Bug |--- Status|Closed |Open --- Comment #15 from Alexey --- Device that have bug: Intel=C2=AE Ethernet X710-DA2 ixl0: = mem 0xdd800000-0xddffffff,0xde808000-0xde80ffff irq 17 at device 0.0 on pci2 ixl0: Using MSIX interrupts with 5 vectors ixl0: fw 4.40.35115 api 1.4 nvm 4.53 etid 8000226b oem 1.268.0 ixl0: PF-ID[0]: VFs 64, MSIX 129, VF MSIX 5, QPs 768, I2C ixl0: Allocating 4 queues for PF LAN VSI; 4 queues active ixl0: Ethernet address: 68:05:ca:41:e8:18 ixl0: PCI Express Bus: Speed 8.0GT/s Width x8 ixl0: SR-IOV ready queues is 0xfffff800067b1000 At this night I weel try check for Intel=C2=AE Ethernet X520-DA2 for this b= ug. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 28 08:57:15 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 6F623DFE39E for ; Tue, 28 Nov 2017 08:57:15 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward105o.mail.yandex.net (forward105o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::608]) (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 117D37C31B for ; Tue, 28 Nov 2017 08:57:15 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback7g.mail.yandex.net (mxback7g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:168]) by forward105o.mail.yandex.net (Yandex) with ESMTP id 7FE714445467; Tue, 28 Nov 2017 11:57:02 +0300 (MSK) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:7]) by mxback7g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id SrRVxY0WDV-v2KifNOc; Tue, 28 Nov 2017 11:57:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1511859422; bh=J6gJVSngHA7O7k9C6hD9a0/Y5Z6AfDMx7SHd26xufyQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=KHMxii5yVyRA0x3ZgZCVHBOmKuq534CRm9FlboMmEMognR9NvBBSCB5vrKooVGxsY MOCo+D4CXaTzDboGQcIyNBpGnZDxKKzx7+kbqQcFMRP5lc0jz4z97IH8nUCvcOY5j+ Lblsjrpt+bRtVQZBAq+0GEQrmssXpGMZ2gjW8f+g= Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 9mWRwJO0WE-v1fmHn1q; Tue, 28 Nov 2017 11:57:01 +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.ru; s=mail; t=1511859421; bh=J6gJVSngHA7O7k9C6hD9a0/Y5Z6AfDMx7SHd26xufyQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=JRqfFB7yS7FmPaVCFc5Nh2kkV6htXRPH/AAwAjU6ICC5aZ1dHzngEIHwWwNkUN0cC yMb427C+dITtyr4qU3TCFi8b/LvhTm1PC9YtrWi7Kk4IkkycJNxs6uV9hFiZ3ZvtDv TWaV6XvIcXnQAvcHMrT/jwhb4gBPPLMBKsXdEmTE= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: Static IPsec (via setkey) and -A aes-xcbc-mac, how to? To: "Peter G." , freebsd-net@freebsd.org References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <4b423285-9a83-84a6-7deb-b51c8c6c02e1@yandex.ru> Date: Tue, 28 Nov 2017 11:54:18 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3BJWXCO4QjI9JInSrdJqxLkJ2xV1XhXiv" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 08:57:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3BJWXCO4QjI9JInSrdJqxLkJ2xV1XhXiv Content-Type: multipart/mixed; boundary="1pJ7Qg0JVQVNxewtTHXqtvSQ4lEKrsvUi"; protected-headers="v1" From: "Andrey V. Elsukov" To: "Peter G." , freebsd-net@freebsd.org Message-ID: <4b423285-9a83-84a6-7deb-b51c8c6c02e1@yandex.ru> Subject: Re: Static IPsec (via setkey) and -A aes-xcbc-mac, how to? References: In-Reply-To: --1pJ7Qg0JVQVNxewtTHXqtvSQ4lEKrsvUi Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 27.11.2017 18:57, Peter G. wrote: > Does anybody know how to get this working? Or does this mean there's no= > actual kernel support for aes-xcbc-mac? Hi, I think you need to port aes-xcbc-mac support from NetBSD's opencrypto implementation. It seems it should be not so hard. --=20 WBR, Andrey V. Elsukov --1pJ7Qg0JVQVNxewtTHXqtvSQ4lEKrsvUi-- --3BJWXCO4QjI9JInSrdJqxLkJ2xV1XhXiv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlodJD8ACgkQAcXqBBDI oXoE7wgAoENVcr0FBpOdUIxKKg9bBS49itvkrmkWX1voLMF1Sev9MBBxLrwpwKEX 9x2AXFx85wh+1u29qwZLxyepLdtq63H7ytTVzLUiQZ4aE2bkYYelJKl7DaTuTmEN 1RRBje9x0rvrGOoWnGmi+/M5I//l8Hrj+TJNxk4aE4SFLAeFGXaIxb/L+0HCthyA kLqKrs5Bl8ZCkn8cbJOwKL2QcvIatQwUC5lQjBVXyZwLcsv/K59eyC8aHHjj7URt UEMHGm4riPNBVl4gQ+5wjTccBGgbg8Qomqhdn76lTUmrnndYrKfBse2ZnADfH8M2 NLjSTsv7kO3MlVZRB8XK9cHgS6UQxQ== =D0V+ -----END PGP SIGNATURE----- --3BJWXCO4QjI9JInSrdJqxLkJ2xV1XhXiv-- From owner-freebsd-net@freebsd.org Tue Nov 28 09:11:10 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 3263EDFECC0 for ; Tue, 28 Nov 2017 09:11:10 +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 20B037CCD0 for ; Tue, 28 Nov 2017 09:11:10 +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 vAS9B8wa072063 for ; Tue, 28 Nov 2017 09:11:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Tue, 28 Nov 2017 09:11: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: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: zarychtam@plan-b.pwste.edu.pl X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 09:11:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 --- Comment #16 from Marek Zarychta --- The bug is strictly related to disabling RXCSUMs on NIC. Other Intel driver= s em (4) and igb (4) reveal the same behaviour. I have not tested NICs from other vendors.=20=20 In fact, pcap dumps taken on interface shows that everything is fine, but counter of "packets with bad signature received" increases and TCP handshake couldn't be established when using TCP MD5 signed packets. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 28 09:43: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 AE8B4DFF7B3 for ; Tue, 28 Nov 2017 09:43:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CC607DD73 for ; Tue, 28 Nov 2017 09:43:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAS9hvho092444 for ; Tue, 28 Nov 2017 09:43:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Tue, 28 Nov 2017 09:43:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: olivier@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 09:43:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 Olivier Cochard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olivier@freebsd.org --- Comment #17 from Olivier Cochard --- I've got the same problem regarding my inet4 BGP sessions using MD5 on all = my bhyve and virtualbox virtual lab (using vtnet and em interface). I don't have the problem regarding inet6 BGP session using MD5 on the same labs. Can bug be related to my problems ? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 28 09:48: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 BDD9FDFF9CA for ; Tue, 28 Nov 2017 09:48: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 AC19A7DED0 for ; Tue, 28 Nov 2017 09:48: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 vAS9mPt6099482 for ; Tue, 28 Nov 2017 09:48:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223835] BGP session not established with md5 password via FRRouting Date: Tue, 28 Nov 2017 09:48:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 09:48:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223835 --- Comment #18 from Andrey V. Elsukov --- (In reply to Olivier Cochard from comment #17) > I've got the same problem regarding my inet4 BGP sessions using MD5 on all > my bhyve and virtualbox virtual lab (using vtnet and em interface). > I don't have the problem regarding inet6 BGP session using MD5 on the same > labs. > Can bug be related to my problems ? Probably it is not related to drivers, I'll check this a bit later. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 28 10:36: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 CF915E517A7 for ; Tue, 28 Nov 2017 10:36: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 BE17A7F3F2 for ; Tue, 28 Nov 2017 10:36: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 vASAatrS028677 for ; Tue, 28 Nov 2017 10:36:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223824] [arm64] Kernel panic in ng_base.c (netgraph) Date: Tue, 28 Nov 2017 10:36:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: aonishenko@protonmail.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: bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 10:36:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223824 aonishenko changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Nov 28 19:32:28 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 3A18ADEC494 for ; Tue, 28 Nov 2017 19:32:28 +0000 (UTC) (envelope-from bryanv@daemoninthecloset.org) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B33A874E69 for ; Tue, 28 Nov 2017 19:32:27 +0000 (UTC) (envelope-from bryanv@daemoninthecloset.org) Received: by mail-lf0-x22f.google.com with SMTP id 74so1138426lfs.0 for ; Tue, 28 Nov 2017 11:32:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daemoninthecloset.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BYe1zGU8wBOlK7gqcqxiAKmX8sPyRAKoEaKFHnS5yzA=; b=iloqTAONBw7QGiq6TJFVUSyBO3vff540q/lqhBFXGuX0ro1aeSE8ulz3gwKofQWSrS VgpGNS6pVb/uw7Mn/9yqUBKpG5mDgYf9/+WWBngpuE636TiEaSe+vobn9ygwmqtrwtC7 6HsCeOR0UTVXKuYauUPeQsi3K/sK8fksnYytPFy27wgUcVxChnklobqBQUA2OFWlurdQ XOvjHdsmJYsCLrX2n0gnB1t75fZ1DDJa1xVJ7LchhLb2K/HXNy26vJOItRV20G2GyuW6 S1zA/yc7R+Cmvcf/RpaPbmoyqH5rcn5yQJlOMwlQTNSZc97x1dXyJyxVecLG2P7kRVXA Gohw== 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=BYe1zGU8wBOlK7gqcqxiAKmX8sPyRAKoEaKFHnS5yzA=; b=ottAEDzmn9Lqod1gHcovTsDbLopsCATsuuHEpDVHxQfj2k/r2Kr5fJcc6aQes6H8n6 qY64mJassmTsZefV9U8OP33wj5iZ1Uhqv3NpM0yznQz0Knh0pMfWeHl735s8dHon7w5I zpnnb6yKe8fCBqAOz8GESTYB5RRY+T6Sdlu9ByI0MIOHXHNGAA/8a4vQb4hoR+VoIiVw CgPLMeCAQSQrRB9BG9H5q9/go7XVIYiiJjU/lajs7kzLHFVkgfwGmm4aiUUlcWq9OwSf A93LLv2LEk+d2LDiFXblF0lnJa5ED0+YuBtTSZdUb7wiamFF+FNR0E+iWLCvr+XfudvA BFPw== X-Gm-Message-State: AJaThX4N5GCB1g71meT9GjdBDOQh2OlCmH1OGGGFBJHOyt8LmNQm2E5o KGDew6MdPhRKgUXm+Su+lZLkpQdpFUOMShucn5iNCvvv X-Google-Smtp-Source: AGs4zMbTvq6X4udX/ar7K9KkoC7U5Jp3FCpgYCMUr6LFKc+VU3G7L+RAsQQqd8ftv/xSXd/89kQ42VZSX0qPUC361b8= X-Received: by 10.46.4.207 with SMTP id a76mr139526ljf.6.1511897545849; Tue, 28 Nov 2017 11:32:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.235.217 with HTTP; Tue, 28 Nov 2017 11:32:05 -0800 (PST) In-Reply-To: <0536294F-3709-4E38-AD7C-1A809AAD13A6@perftech.com> References: <398971232.399523.1508250252244.JavaMail.zimbra@perftech.com> <0536294F-3709-4E38-AD7C-1A809AAD13A6@perftech.com> From: Bryan Venteicher Date: Tue, 28 Nov 2017 13:32:05 -0600 Message-ID: Subject: Re: vmxnet3 driver bug? To: Lewis Donzis 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.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2017 19:32:28 -0000 On Tue, Oct 17, 2017 at 9:36 AM, Lewis Donzis wrote: > The VMXNET3 driver appears to have a bug that prevents it from correctly > reporting when the link goes down. > > There are two lines of code that should be deleted in > /usr/src/sys/dev/vmware/vmxnet3/if_vmx.c: > > @@ -3619,8 +3619,6 @@ vmxnet3_media_status(struct ifnet *ifp, struct > ifmediareq *ifmr) > VMXNET3_CORE_LOCK(sc); > if (vmxnet3_link_is_up(sc) !=3D 0) > ifmr->ifm_status |=3D IFM_ACTIVE; > - else > - ifmr->ifm_status |=3D IFM_NONE; > VMXNET3_CORE_UNLOCK(sc); > } > > IFM_NONE doesn=E2=80=99t belong in the status flags and, coincidentally, = is > defined with an identical value as IFM_ACTIVE, so it indicates that link = is > always active. > > This should be fixed in r326309 that I'll merge to the stable branches in a week. > Thanks, > lew > _______________________________________________ > 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 Nov 29 08:53:54 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 62DD2DFDD41 for ; Wed, 29 Nov 2017 08:53:54 +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 50AC86BB6B for ; Wed, 29 Nov 2017 08:53:54 +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 vAT8rrx7045995 for ; Wed, 29 Nov 2017 08:53:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223767] tun device allows modification of if_type to any value causing a page fault and panic Date: Wed, 29 Nov 2017 08:53: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: 10.4-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hselasky@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.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 08:53:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223767 --- Comment #4 from Hans Petter Selasky --- >From what I can see using IFQ_POLL_NOLOCK() is not the same like IFQ_IS_EMP= TY() in this case, so this chunk should be skipped. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 29 09:15: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 5A28ADFE563 for ; Wed, 29 Nov 2017 09:15: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 481CE6C55F for ; Wed, 29 Nov 2017 09:15: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 vAT9FPJ9002503 for ; Wed, 29 Nov 2017 09:15:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223767] tun device allows modification of if_type to any value causing a page fault and panic Date: Wed, 29 Nov 2017 09:15:25 +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.4-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: hselasky@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 09:15:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223767 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |hselasky@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Nov 29 14:32:37 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 984EEE5562B for ; Wed, 29 Nov 2017 14:32:37 +0000 (UTC) (envelope-from c1test@mymts.net) Received: from mail.mymts.net (mail.mts.syn-alias.com [69.168.103.60]) (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 53CCF76866 for ; Wed, 29 Nov 2017 14:32:36 +0000 (UTC) (envelope-from c1test@mymts.net) DKIM-Signature: v=1; a=rsa-sha1; d=mymts.net; s=mts201501; c=relaxed/simple; q=dns/txt; i=@mymts.net; t=1511964747; h=From:Subject:Date:To:Mime-Version:Content-Type; bh=ddiKdoU7HT+yR1ZPNTFpNEUBNJ0=; b=G14vJscxjdV/UqtQr1S47rKJcmi5zLONtoM+F6FiDANwQ4J1Qt3lBQiZ8xhzClk5 5mTsOLbOnWa9e2tVnSZHUVeDusvfV3nO4hwLYHasGQkNneMx3Pa50ZMGq1XvOoRM ZHE9mcJMP65uJpU7rbtNrq7wjP7PeCu/0ShSftSF5H4=; X_CMAE_Category: , , X-CNFS-Analysis: v=2.2 cv=S7mb+8kP c=1 sm=1 tr=0 a=l5bXoG+40Sw0viMbP8N4IQ==:117 a=l5bXoG+40Sw0viMbP8N4IQ==:17 a=KGjhK52YXX0A:10 a=kj9zAlcOel0A:10 a=s-_wWEC2X3wA:10 a=sC3jslCIGhcA:10 a=4ZeFgsrovaEA:10 a=I3hW6QClAAAA:20 a=BRalqnmUgP_2M5QcBIQA:9 a=CjuIK1q_8ugA:10 a=Ol54ruw9rs0A:10 a=TcnhDTrz_5kA:10 a=IawXvI9lP1MA:10 a=3ifaOeWoG58A:10 a=EPpi8FdoIYAA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: bXdsZXNpdWtAbXltdHMubmV0 Authentication-Results: smtp01.mts.yyz.synacor.com smtp.user=mwlesiuk; auth=pass (LOGIN) Received: from [101.219.136.58] ([101.219.136.58:59826] helo=mail.mymts.net) by mail.mymts.net (envelope-from ) (ecelerity 3.6.6.45965 r(Core:3.6.6.0)) with ESMTPSA (cipher=DHE-RSA-AES128-SHA) id 32/95-27570-840CE1A5; Wed, 29 Nov 2017 09:12:27 -0500 From: "c1test" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Message-Id: <6FBB3B86-1025-4003-8B6F-B15574DEA490@mymts.net> Date: Wed, 29 Nov 2017 17:12:24 +0300 To: "freebsd net" Reply-To: "c1test" X-Mailer: iPhone Mail (14C92) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 14:32:37 -0000 Greetings Freebsd http://bit.ly/2nb50Xo From owner-freebsd-net@freebsd.org Wed Nov 29 19:02: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 68B00DB9269 for ; Wed, 29 Nov 2017 19:02:12 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 408E91608; Wed, 29 Nov 2017 19:02:11 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id vATJ23EB019915; Wed, 29 Nov 2017 11:02:03 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id vATJ23mu019914; Wed, 29 Nov 2017 11:02:03 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201711291902.vATJ23mu019914@pdx.rh.CN85.dnsmgr.net> Subject: Re: [Bug 223767] tun device allows modification of if_type to any value causing a page fault and panic In-Reply-To: To: bugzilla-noreply@freebsd.org Date: Wed, 29 Nov 2017 11:02:03 -0800 (PST) CC: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 19:02:12 -0000 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223767 > > Hans Petter Selasky changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Assignee|freebsd-net@FreeBSD.org |hselasky@FreeBSD.org Pleaes copy the freebsd-net@freebsd.org email address to the CC section when you take a bug like this, so that those of us watching the list continue to be informed of what is occuring with that bug. Thanks, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Thu Nov 30 03:55:04 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 B4243DF532C for ; Thu, 30 Nov 2017 03:55:04 +0000 (UTC) (envelope-from sunxiaoye07@gmail.com) Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 636057259B for ; Thu, 30 Nov 2017 03:55:04 +0000 (UTC) (envelope-from sunxiaoye07@gmail.com) Received: by mail-ot0-x22d.google.com with SMTP id v21so5042624oth.6 for ; Wed, 29 Nov 2017 19:55:04 -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=sbVQnWGqA9ODC+zxD8O9tjbft2BxPhkANlWbSmYn3mo=; b=JWkJ85hr3gLIB7JkAlVdxMJOwfLXitAKtlNdxWrRzDpwKnRw81bgPKtHFbSDSub3j+ CPwMUIV2scqp9HjRfE2ZM8N+jpv8hyBa8n9RHYfH864djz3gp7NxvCo8FFbfZ+hzl4b8 pE6XuOmtwPwtF2XII+k38671JUMYsgG01y6G90d36/LZMzwcko+m61IfCFk9BcQOiKU4 GBrlkb2W14TOR7zDPTEVLcNtNZ7H8HnpBEfoimqTEShwuBAD8l+HOoeHOBEpM/ZtoCLU J62hfNGp4zoMgOs8D8fV5AbSvVpdoDMH7L8C3azPsvPC66v79w+FdYUAywZC9ZRIk2xF N/Xw== 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=sbVQnWGqA9ODC+zxD8O9tjbft2BxPhkANlWbSmYn3mo=; b=VqvEH2+Fi38CqslEdfUJ+KsvpxfhCfj6ENyxh11BrcXG3GL1wkGPYHxzuwmdbDU+o+ ibMhlbhmS6WijGYMbpH7SZuAXEbBnTz+JQluGPb27ide2MAUBa8ha2HaVt0vuqBJGzqT abtFLELzsPHh7F4k8k3MfK//tM7K/156Wiw+h/EoKmon8HjHgdsGTsylPrdGH7DtzZiJ any4bkFMJIXk6lcKjSl0yPwEF44sEpgmcwOS39kfV6ust5X+ZR7kaZfKOX/d5q+EvtBt nJdZtCnTtjyuMSk97iE8wuHP6MNcViOHbv/ce+2tj3ntj0HQsktjqTEnYeVLF1vBaxp0 GCfw== X-Gm-Message-State: AJaThX5WU13lZi7A5c0VuwDnp5jZXnOQHDKj6tYunvda1aawrDHgpgFD TVnhOtbscS71G6yKhBxzgVlbNapKz4I3eC2Di00= X-Google-Smtp-Source: AGs4zMbWH8AgGkiqjXMb4eGjbE8osUJn1Yf++toGf0MgiRbZ6Te1TZxgto3PJIqbaZGPJAXb9pafU6oajGQS2ZE3300= X-Received: by 10.157.27.44 with SMTP id l41mr3989531otl.372.1512014103580; Wed, 29 Nov 2017 19:55:03 -0800 (PST) MIME-Version: 1.0 Sender: sunxiaoye07@gmail.com Received: by 10.157.41.3 with HTTP; Wed, 29 Nov 2017 19:55:02 -0800 (PST) In-Reply-To: References: From: Xiaoye Sun Date: Wed, 29 Nov 2017 21:55:02 -0600 X-Google-Sender-Auth: KKm0J2kIdK84L7EID-0jdKfuerQ Message-ID: Subject: Re: swaping ring slots between NIC ring and Host ring does not always success To: Vincenzo Maffione Cc: Luigi Rizzo , "freebsd-net@freebsd.org" , Victor Detoni , Pavel Odintsov , Giuseppe Lettieri Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 03:55:04 -0000 On Mon, Nov 27, 2017 at 2:33 AM, Vincenzo Maffione wrote: > Hi, > > If you think it's a bug can you please open an issue on the github ( > https://github.com/luigirizzo/netmap/issues)? > > 2017-11-24 22:11 GMT+01:00 Xiaoye Sun : > >> Hi Vincenzo, >> >> Let me clarify my problem. (please ignore the previous incompleted email) >> >> I have a program, which is an extension of bridge.c >> https://github.com/luigirizzo/netmap/blob/master/apps/bridge/bridge.c >> The only difference is that my program also generates customized packets >> sent to the NIC directly. >> These customized packets have increasing sequence numbers. >> So, this program not only sends these customized packets but also >> forwards packets between NIC and host stack using zerocopy. >> The program only takes one NIC queue and there is only one thread. >> >> I think the problem is that there is a chance where netmap does not >> update the pointer to the buffer even when NS_BUF_CHANGED is set >> (buf_idx is changed). >> > > Can you disable zerocopy in bridge.c to see if the problem goes away? This > would be an useful information. > > disable zerocopy make this problem disappeared > >> Let's say the NIC tx ring has 4096 slots. The customized packet sequence >> 16 is filled in the buffer of slot 2057. >> The customized packets keep filling the slots until the next available >> slot is 2056. >> > > Do you mean that your program fills the TX ring slots > 2057,2058...2054,2055 with custom packets? This would mean you filled all > the available slots, since one slot is left empty. > > >> Now the customised packet sequence 4111 is filled to 2056. >> > > You cannot fill the slot 2056 if 2055 has not been NIOCTXYSINC'd. Aren't > you using nm_ring_empty() and nm_ring_space() functions to check > for available space in TX ring (assuming you update rinig->head/ring->cur > before calling those functions)? > > the slots are not filled-in once. NIOCTXYSINC are called at most every 512 slots are filled. I always use nm_ring_space() to check the number of remaining slots in the ring. > Cheers, > Vincenzo > > >> Then the netmap program is notified that there is a packet from the host >> stack sent to the NIC. >> The netmap program swaps the buf_idx between slot 2057 and the >> corresponding slot in the host rx ring and set the NS_BUF_CHANGED flag >> of both slots. >> Then the netmap program fills sequence 4112 to slot 2058. >> However, the buffer swap seems not succeed so that the original content >> of slot 2057 (sequence 16) is sent out. >> So that at the receiver side, the receiver sees two sequence >> 16s.(16,17...4110,4111,16,4112,4113). >> >> So think the root of the problem is that the buffer pointer is not always >> successfully/timely updated even after the NS_BUF_CHANGED flag is set >> and the buf_idx is updated. >> >> Best, >> Xiaoye >> >> >> >> On Wed, Nov 22, 2017 at 7:39 AM, Vincenzo Maffione >> wrote: >> >>> Hi, >>> >>> 2017-11-21 7:51 GMT+01:00 Xiaoye Sun : >>> >>>> Hi, >>>> >>>> Recently I found another problem with netmap. I think this new problem >>>> could be related to the problems in this threads so I just post the new >>>> problem here. >>>> >>>> In my setup, I have a sender program having a netmap ring (a pair of >>>> RX/TX ring) for the NIC and a ring for the host stack. The sender >>>> program >>>> puts customized packets (each packet has a unique sequence number and >>>> the >>>> sender sends the packet in a sequence number increasing order) to the >>>> NIC >>>> TX ring directly and also forwards the packets from the host RX ring to >>>> the >>>> NIC TX ring using "zerocopy" by swapping the buffer indices. >>>> However, the receiver sees duplicated customized packets. For example, >>>> in >>>> the case where the ring size is 32 (32 slots in a ring) the order of the >>>> sequence numbers the receiver see is 1,2,3,4,5,...,68,69,*70* >>>> ,71,72,73,...,99,100,*70*,101,102,103,... . An interesting thing I >>>> found is >>>> that the "gaps" between these two duplicated packets (70 in the example) >>>> are always a number very close to the ring size, 32 in this example. In >>>> my >>>> experiment, I use a ring with 4096 slots and the gap is always more than >>>> 4090 and close to 4096. I verified that this duplication happens due to >>>> the >>>> sender, not the receiver. Assuming my sender's implementation is >>>> correct, >>>> then this duplication may happen in netmap and the NIC driver (ixgbe). >>>> >>> >>> Netmap itself doesn't do any duplication nor takes a look at the >>> packets. It just passes >>> down ring->cur/ring->head to the ixgbe driver (after validation). >>> The ixgbe driver datapath is bypassed and replaced with a netmap-enabled >>> datapath (see https://github.com/luigirizzo/ >>> netmap/blob/master/LINUX/ixgbe_netmap_linux.h#L294-L461); >>> no duplication should happen there as each netmap slot (1 TX packet) is >>> used >>> only once. >>> >>>> >>>> >>>> Thinking back to the original problem in this post, I think these >>>> problems >>>> may be related. It seems to me that there could be multiple threads >>>> pulling >>>> the packets from the NIC TX ring (or the thread moved to other CPUs when >>>> the problem occurs) and these threads may run on different cores so that >>>> the outdated content in the buffer may be sent out when new content is >>>> written to the buffer. >>>> >>>> >>> There are no such threads pulling from the NIC TX ring. Your application >>> directly >>> puts new packets to be transmitted in the netmap buffers referenced in >>> the netmap TX >>> ring. When then you call NIOCTXSYNC or poll(), all the new TX buffers >>> (e.g. all >>> the ones from the previous value ring->head (included) to the new value >>> of ring->head (excluded)) >>> are moved to the NIC TX ring. This happens in the context of your >>> application thread, >>> no worker threads are used. Then the NIC hardware starts the >>> transmission. >>> >>> >>>> I am wondering if there is a way to pin the NIC driver of the netmap >>>> module >>>> to a specific core. or is there a way to know the root of such problem? >>>> >>> >>> The only threads are the ones of your application. >>> Maybe your problem comes from concurrent accesses to the netmap TX ring >>> from different threads? Only one thread at a given time should update a >>> netmap >>> TX/RX ring. Otherwise the behaviour is unspecified. >>> >>> Cheers, >>> Vincenzo >>> >>> >>>> >>>> Best, >>>> Xiaoye >>>> >>>> >>> -- >>> Vincenzo Maffione >>> >> >> > > > -- > Vincenzo Maffione > From owner-freebsd-net@freebsd.org Thu Nov 30 19:37: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 448FCE69C24; Thu, 30 Nov 2017 19:37:35 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) (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 17E59719A4; Thu, 30 Nov 2017 19:37:34 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: by mail-oi0-f52.google.com with SMTP id x20so5588168oix.12; Thu, 30 Nov 2017 11:37:34 -0800 (PST) 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=3e7jaRUeictwp0iGVjwXvggoKo1Ghp+ddVjNLr4KSbk=; b=VnXWEW6NzNsoUx9JqdEDZqX3/zHrSspSw+vK3oE0nHij1Hl+H1wu1ujFtQP7P0M1q2 0zqWgfoRdVqnx9ea40xI5zTFJAFBy4aFzeXOUl5ma1Wcz8zKi6G5LRJfNw2zg3SUz6mb hqZz1V/YDxcd6NDOagi14sAgluFP0BDskErlUqrNTcULbieBVa7F4Tu12Ni5lXJH052a 2IoeV4/nn9GxtC9ahGGzhA0s3oRAHIYAKz3ed8/sy4AeuESh2WPDtjl3MZIZxU1ppv0+ dcjz27JxDmAJNbXlugENwJKvvkN43HAuwgPglop5Urt/24ItdrSjiX4eGnWsHU9+CmLC HbhA== X-Gm-Message-State: AJaThX7vKE2TJQJZcbqs3VUqk0k2AKIV1HrjVjdj6lhvZMolW9mOWZVv dm5BxIcGBCPRU1uxHHlcJG2lfo97BAmzLzvA/TY= X-Google-Smtp-Source: AGs4zMbmMArnQlm8gwIC9JVhlPaoCpYQMhdYllUS8gv2p471TTGtgBrtihvrb2lYqp12NaB9sW8QH9AN0BTzE7nDy1E= X-Received: by 10.202.170.140 with SMTP id t134mr5215301oie.163.1512063588211; Thu, 30 Nov 2017 09:39:48 -0800 (PST) MIME-Version: 1.0 From: Rick Miller Date: Thu, 30 Nov 2017 17:39:37 +0000 Message-ID: Subject: net.inet.ip.portrange and The FreeBSD Handbook To: "freebsd-doc@freebsd.org" , "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 19:37:35 -0000 Hi all, I found The FreeBSD Handbook[1] had this to say regarding net.inet.ip.portrange.* sysctl variables: =E2=80=9CThe net.inet.ip.portrange.* sysctl(8) variables control the port n= umber ranges automatically bound to TCP and UDP sockets. There are three ranges: a low range, a default range, and a high range. Most network programs use the default range which is controlled by net.inet.ip.portrange.first and net.inet.ip.portrange.last, which default to 1024 and 5000, respectively. Bound port ranges are used for outgoing connections and it is possible to run the system out of ports under certain circumstances. This most commonly occurs when running a heavily loaded web proxy. The port range is not an issue when running a server which handles mainly incoming connections, such as a web server, or has a limited number of outgoing connections, such as a mail relay. For situations where there is a shortage of ports, it is recommended to increase net.inet.ip.portrange.last modestly. A value of 10000, 20000 or 30000 may be reasonable. Consider firewall effects when changing the port range. Some firewalls may block large ranges of ports, usually low-numbered ports, and expect systems to use higher ranges of ports for outgoing connections. For this reason, it is not recommended that the value of net.inet.ip.portrange.first be lowered.=E2=80=9D FreeBSD 11.1 deploys values contrary to those above: # uname -sr FreeBSD 11.1-STABLE # sysctl net.inet.ip.portrange net.inet.ip.portrange.randomtime: 45 net.inet.ip.portrange.randomcps: 10 net.inet.ip.portrange.randomized: 1 net.inet.ip.portrange.reservedlow: 0 net.inet.ip.portrange.reservedhigh: 1023 net.inet.ip.portrange.hilast: 65535 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.last: 65535 net.inet.ip.portrange.first: 10000 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.lowfirst: 1023 A commit in March 2008[2] sets net.inet.ip.portrange.first and last to 10000 and 65535 respectively. It=E2=80=99s apparently obvious The FreeBSD H= andbook includes obsolete guidelines. This raises the question =E2=80=9Chow does th= is change the advice given in The Handbook?=E2=80=9D PR 223997 is opened to have The Handbook updated. [1] https://www.freebsd.org/doc/handbook/configtuning-kernel-limits.html [2] https://svnweb.freebsd.org/base/stable/11/sys/netinet/in.h?revision=3D17680= 5&view=3Dmarkup =E2=80=94 Rick <703-581-3068> --=20 Take care Rick Miller From owner-freebsd-net@freebsd.org Thu Nov 30 21:03: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 B5075DBA779 for ; Thu, 30 Nov 2017 21:03:18 +0000 (UTC) (envelope-from aspam@cox.net) Received: from fed1rmwml114.cox.net (fed1wml22.cox.net [68.230.241.21]) by mx1.freebsd.org (Postfix) with ESMTP id 970C575948 for ; Thu, 30 Nov 2017 21:03:17 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo210.cox.net ([68.230.241.225]) by eastrmfepo202.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20171130205315.HPPC3211.eastrmfepo202.cox.net@eastrmimpo210.cox.net> for ; Thu, 30 Nov 2017 15:53:15 -0500 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo210.cox.net with cox id gLtF1w0061LxgH801LtFY2; Thu, 30 Nov 2017 15:53:15 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.5A206FBB.0090, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.2 cv=NN6lwwyg c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=8nJEP1OIZ-IA:10 a=x7bEGLp0ZPQA:10 a=sC3jslCIGhcA:10 a=e9ASbk4n0QUA:10 a=iJhTRe1rzglwqlNLiJIA:9 a=wPNLvfGTeEIA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id 9F9CA10E40 for ; Thu, 30 Nov 2017 15:53:14 -0500 (EST) Message-ID: <5A206FB9.3010106@cox.net> Date: Thu, 30 Nov 2017 15:53:13 -0500 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Subject: netmap / LINUX realtime / ixgbevf: huge RX latencies Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 21:03:18 -0000 I am using the LINUX 4.4.86 realtime kernel patch with netmap and the ixgbevf driver (SRIOV in a VM) and having some serious RX latency issues. The ixbgevf driver built by the netmap build against the kernel source does not work. I haven't tried to debug it -- the netmap driver complains about bad ring index values and resets (over and over again as my app runs). The non-netmap version of ixgbevf that comes with the kernel works but appears to have serious RX latency issues due to frame batching. It appears that the kernel's NAPI polling reads frames from the NIC, then netmap processes the frames, then epoll exits and my app can work on the frames. The delay between start of NAPI to my app getting frames can be milliseconds!!! Would the netmap-modified ixgbevf driver eliminate this latency? If so, any ideas on what might be going wrong with the modified driver? Perhaps an older version of the driver might be better? The kernel ixgbevf version is 2.12.1-k while netmap is trying to use 4.2.1. Looking at the RT patch for LINUX there are only a few network driver patches, none for the ixgbe* cards. Joe Buehler From owner-freebsd-net@freebsd.org Thu Nov 30 22:22:58 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 69A47DEAF8D for ; Thu, 30 Nov 2017 22:22:58 +0000 (UTC) (envelope-from aspam@cox.net) Received: from fed1rmwml214.cox.net (fed1wml20.cox.net [68.230.241.23]) by mx1.freebsd.org (Postfix) with ESMTP id 4AD777956A for ; Thu, 30 Nov 2017 22:22:57 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo110.cox.net ([68.230.241.223]) by eastrmfepo103.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20171130222248.KCAL4084.eastrmfepo103.cox.net@eastrmimpo110.cox.net> for ; Thu, 30 Nov 2017 17:22:48 -0500 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo110.cox.net with cox id gNNo1w00V1LxgH801NNoRX; Thu, 30 Nov 2017 17:22:48 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020206.5A2084B8.00AC, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.2 cv=LZJM0nXi c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=8nJEP1OIZ-IA:10 a=x7bEGLp0ZPQA:10 a=sC3jslCIGhcA:10 a=e9ASbk4n0QUA:10 a=bYbZl4uCKGXDJYWZX28A:9 a=wPNLvfGTeEIA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id ECFF310E40 for ; Thu, 30 Nov 2017 17:22:47 -0500 (EST) Message-ID: <5A2084B6.80302@cox.net> Date: Thu, 30 Nov 2017 17:22:46 -0500 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Subject: Re: netmap / LINUX realtime / ixgbevf: huge RX latencies References: <5A206FB9.3010106@cox.net> In-Reply-To: <5A206FB9.3010106@cox.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 22:22:58 -0000 Here is what I start seeing in dmesg when I attempt to use the 4.2.1 ixgbevf driver as modified for netmap. Joe Buehler [ 136.607019] 343.712201 [ 189] ixgbe_netmap_configure_srrctl not supported [ 136.610020] 343.715203 [ 189] ixgbe_netmap_configure_srrctl not supported [ 136.796698] ixgbevf 0000:00:08.0: NIC Link is Up 10 Gbps [ 136.953013] 344.058196 [ 189] ixgbe_netmap_configure_srrctl not supported [ 136.955014] 344.060198 [ 189] ixgbe_netmap_configure_srrctl not supported [ 136.997559] ixgbevf 0000:00:08.0: NIC Link is Up 10 Gbps [ 136.997908] 344.103090 [1653] nm_rxsync_prologue eth0 RX0: fail 'head < kring->nr_hwcur || head > kring->nr_hwtail' h 1 c 1 t 0 rh 1 rc 1 rt 0 hc 0 ht 0 [ 136.999652] 344.104836 [1698] netmap_ring_reinit called for eth0 RX0 [ 137.000568] 344.105751 [1653] nm_rxsync_prologue eth0 RX0: fail 'head < kring->nr_hwcur || head > kring->nr_hwtail' h 1 c 1 t 0 rh 1 rc 1 rt 0 hc 0 ht 0 [ 137.002268] 344.107452 [1698] netmap_ring_reinit called for eth0 RX0 [ 137.003165] 344.108349 [1653] nm_rxsync_prologue eth0 RX0: fail 'head < kring->nr_hwcur || head > kring->nr_hwtail' h 1 c 1 t 0 rh 1 rc 1 rt 0 hc 0 ht 0 [ 137.004856] 344.110041 [1698] netmap_ring_reinit called for eth0 RX0 [ 137.005752] 344.110936 [1653] nm_rxsync_prologue eth0 RX0: fail 'head < kring->nr_hwcur || head > kring->nr_hwtail' h 1 c 1 t 0 rh 1 rc 1 rt 0 hc 0 ht 0 [ 137.007451] 344.112635 [1698] netmap_ring_reinit called for eth0 RX0 [ 137.008343] 344.113527 [1653] nm_rxsync_prologue eth0 RX0: fail 'head < kring->nr_hwcur || head > kring->nr_hwtail' h 1 c 1 t 0 rh 1 rc 1 rt 0 hc 0 ht 0 [ 137.010066] 344.115250 [1698] netmap_ring_reinit called for eth0 RX0 [ 137.010953] 344.116137 [1698] netmap_ring_reinit called for eth0 RX0 From owner-freebsd-net@freebsd.org Fri Dec 1 10:23: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 0DDD2DFAE19 for ; Fri, 1 Dec 2017 10:23:44 +0000 (UTC) (envelope-from sd@mostnet.ru) Received: from mail.rlan.ru (mail.rlan.ru [213.234.25.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C344D79EF4 for ; Fri, 1 Dec 2017 10:23:42 +0000 (UTC) (envelope-from sd@mostnet.ru) To: "freebsd-net@freebsd.org" From: Dmitry Selivanov Subject: ng_patch is broken in 10.4-RELEASE Message-ID: <502ae893-1b55-305d-f1c4-de7f22159a15@mostnet.ru> Date: Fri, 1 Dec 2017 12:39:27 +0300 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 10:23:44 -0000 #ngctl mkpeer ipfw: patch 7 in #ngctl name ipfw:7 tcp_rst #ngctl connect ipfw: tcp_rst: 8 out #ngctl msg tcp_rst: setconfig { count=1 csum_flags=0 ops=[ { mode=8 value=4 length=1 offset=33 } ] } ngctl: send msg: Argument list too long It's broken after r309389 and could be fixed in r309408, but the first one went to 10.4 and the second one didn't. 11.0 didn't get this patches, 11.1 got both, so they are OK. Patch to fix: --- /sys/netgraph/ng_patch.h.orig 2017-11-23 14:19:54.019040000 +0300 +++ /sys/netgraph/ng_patch.h 2017-11-30 15:34:23.000000000 +0300 @@ -80,7 +80,7 @@ struct ng_patch_config { uint32_t count; - uint32_t csum_flags; + uint64_t csum_flags; struct ng_patch_op ops[]; }; In this patch new uint64_t type is utilized. Instead this you can get back modified "csum_flags" to ng_parse_uint32_type in NG_PATCH_CONFIG_TYPE_INFO, which was changed in r309389. Patch and rebuild ng_patch module. From owner-freebsd-net@freebsd.org Fri Dec 1 11:34: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 8CC1EDFD1D9 for ; Fri, 1 Dec 2017 11:34:01 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2667D7DB64 for ; Fri, 1 Dec 2017 11:34:00 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vB1BXnvd003898 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 1 Dec 2017 12:33:50 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: sd@mostnet.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 ESMTP id vB1BXkOO048072; Fri, 1 Dec 2017 18:33:46 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: ng_patch is broken in 10.4-RELEASE To: Dmitry Selivanov , "freebsd-net@freebsd.org" References: <502ae893-1b55-305d-f1c4-de7f22159a15@mostnet.ru> From: Eugene Grosbein Message-ID: <5A213E1A.2080805@grosbein.net> Date: Fri, 1 Dec 2017 18:33:46 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <502ae893-1b55-305d-f1c4-de7f22159a15@mostnet.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_96_Q autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: * date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 11:34:01 -0000 On 01.12.2017 16:39, Dmitry Selivanov wrote: > #ngctl mkpeer ipfw: patch 7 in > #ngctl name ipfw:7 tcp_rst > #ngctl connect ipfw: tcp_rst: 8 out > #ngctl msg tcp_rst: setconfig { count=1 csum_flags=0 ops=[ { mode=8 value=4 length=1 offset=33 } ] } > ngctl: send msg: Argument list too long > > It's broken after r309389 and could be fixed in r309408, but the first one went to 10.4 and the second one didn't. > > 11.0 didn't get this patches, 11.1 got both, so they are OK. > > Patch to fix: > --- /sys/netgraph/ng_patch.h.orig 2017-11-23 14:19:54.019040000 +0300 > +++ /sys/netgraph/ng_patch.h 2017-11-30 15:34:23.000000000 +0300 > @@ -80,7 +80,7 @@ > > struct ng_patch_config { > uint32_t count; > - uint32_t csum_flags; > + uint64_t csum_flags; > struct ng_patch_op ops[]; > }; > > > In this patch new uint64_t type is utilized. Instead this you can get back modified "csum_flags" to ng_parse_uint32_type in NG_PATCH_CONFIG_TYPE_INFO, which was changed in r309389. > Patch and rebuild ng_patch module. А можно всё то же самое оформить в виде PR в http://bugs.freebsd.org/ и прислать мне ссылку? Займусь. From owner-freebsd-net@freebsd.org Fri Dec 1 13:04:39 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 084EEDFFE69 for ; Fri, 1 Dec 2017 13:04:39 +0000 (UTC) (envelope-from reply@west-art.net) Received: from west-art.net (west-art.net [162.144.110.111]) (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 D88C9117B for ; Fri, 1 Dec 2017 13:04:38 +0000 (UTC) (envelope-from reply@west-art.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=west-art.net; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:List-Unsubscribe:Message-ID:Subject:Reply-To:From:To:Date:Sender :Cc:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Subscribe:List-Post:List-Owner:List-Archive; bh=zgTWuZvhc3D6+GSzxuU2Mi2yo8gA2Yliu/nAxyl7Ggg=; b=Xiq3ZMwp0Bsa2dBnM+Sx9EqOUL dTIg78S9FiOBNLtHXHEgdpkrMq3AEWa2rc2/xYnLC8JXUL+fzdAV8NvhrfHCEwNVdsP1sHUD5goL3 zjST4IteoV5GQGwCWax8s53m1XJ3DUsFvdoddA8WufV5J/Dslv+RfCZBvrOk1N74n15xkfxpZ7kpt lR8JzyIEwkx8gqY0SATEx+eOpVuhFSYNgz7bf/JxJCPcDA7UsGljsdF7uVL/qtRgbr78ZXtT1oIzK /58v2LpY29kPX/XrD85dP67jkDoOfMGEf5yUIoyfTxtJScKfS9Cq43KjxZsHaBYhr4c7JRJ4U6co5 snoA4YIQ==; Received: from westartn by server.west-art.net with local (Exim 4.89) (envelope-from ) id 1eKkzc-0007D1-1k for freebsd-net@freebsd.org; Fri, 01 Dec 2017 15:04:36 +0200 Date: Fri, 1 Dec 2017 13:04:14 +0000 To: freebsd-net@freebsd.org From: Benefis Company Reply-To: reply@west-art.net Subject: Best Ballet Costume for Winter Performances! Message-ID: X-Mailer: Mailster 2.2.14 (5.2.22) X-Mailster: 6f82520695a80b7fb9638ba982630bbb X-Mailster-Campaign: 121 X-Mailster-ID: 34695d011f7794251628561f772eda6d X-Message-ID: <5a2153640940f-6f82520695a80b7fb9638ba982630bbb-121-34695d011f7794251628561f772eda6d@massmail.benefistutu.com> MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server.west-art.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [500 500] / [47 12] X-AntiAbuse: Sender Address Domain - west-art.net X-Get-Message-Sender-Via: server.west-art.net: authenticated_id: westartn/from_h X-Authenticated-Sender: server.west-art.net: reply@west-art.net X-Source: /usr/bin/php X-Source-Args: /usr/bin/php X-Source-Dir: west-art.net:/public_html/massmail Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 13:04:39 -0000 [1] Winter Special Price! [2] This gorgeous Professional Stage Costume is just what you need for any show, audition, or performance. It is a perfect choice for the most renown ballets, such as Nutcracker, Sleeping Beauty and many more. Model: F 0001 Brand: Benefis Santa Claus [facebook] [3] [instagram] [4] [pinterest] [5] [twitter] [6] [linkedin] [7] [youtube] [8] [vkontakte] [9] Links: ------ [1] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly9iZW5lZmlzdHV0dS5jb20vaW5kZXgucGhwP3JvdXRlPXByb2R1Y3QvcHJvZHVjdCZhbXA7c2VhcmNoPWYlMjUyMDAwMDEmYW1wO3Byb2R1Y3RfaWQ9MTI2MA [2] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly9iZW5lZmlzdHV0dS5jb20vaW5kZXgucGhwP3JvdXRlPXByb2R1Y3QvcHJvZHVjdCZhbXA7c2VhcmNoPWYlMjUyMDAwMDEmYW1wO3Byb2R1Y3RfaWQ9MTI2MA/1 [3] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly93d3cuZmFjZWJvb2suY29tL0JlbmVmaXMtQmFsbGV0LUNvc3R1bWVzLTEyMTc2ODAzNDgzNzcxMS8 [4] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly93d3cuaW5zdGFncmFtLmNvbS90ZXJlbnRpZXZhOTgxNi8 [5] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly93d3cucGludGVyZXN0LmNvbS9iYmFsbGV0Y29zdHVtZXMv [6] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly90d2l0dGVyLmNvbS9iZW5lZmlzc2hvcA [7] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL2JlbmVmaXNzaG9wY29tLw [8] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly93d3cueW91dHViZS5jb20vdXNlci9CZW5lZmlzc2hvcA [9] http://massmail.benefistutu.com/mailster/121/6f82520695a80b7fb9638ba982630bbb/aHR0cHM6Ly92ay5jb20vaWQxNzgxNzY2OTg From owner-freebsd-net@freebsd.org Fri Dec 1 13:37:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F061E56400 for ; Fri, 1 Dec 2017 13:37:13 +0000 (UTC) (envelope-from sd@mostnet.ru) Received: from mail.rlan.ru (mail.rlan.ru [213.234.25.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CE05D288C for ; Fri, 1 Dec 2017 13:37:12 +0000 (UTC) (envelope-from sd@mostnet.ru) Subject: Re: ng_patch is broken in 10.4-RELEASE To: "freebsd-net@freebsd.org" References: <502ae893-1b55-305d-f1c4-de7f22159a15@mostnet.ru> <5A213E1A.2080805@grosbein.net> From: Dmitry Selivanov Message-ID: Date: Fri, 1 Dec 2017 16:37:09 +0300 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <5A213E1A.2080805@grosbein.net> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Language: ru Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 13:37:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224019 01.12.2017 14:33, Eugene Grosbein пишет: > On 01.12.2017 16:39, Dmitry Selivanov wrote: >> #ngctl mkpeer ipfw: patch 7 in >> #ngctl name ipfw:7 tcp_rst >> #ngctl connect ipfw: tcp_rst: 8 out >> #ngctl msg tcp_rst: setconfig { count=1 csum_flags=0 ops=[ { mode=8 value=4 length=1 offset=33 } ] } >> ngctl: send msg: Argument list too long >> >> It's broken after r309389 and could be fixed in r309408, but the first one went to 10.4 and the second one didn't. >> >> 11.0 didn't get this patches, 11.1 got both, so they are OK. >> >> Patch to fix: >> --- /sys/netgraph/ng_patch.h.orig 2017-11-23 14:19:54.019040000 +0300 >> +++ /sys/netgraph/ng_patch.h 2017-11-30 15:34:23.000000000 +0300 >> @@ -80,7 +80,7 @@ >> >> struct ng_patch_config { >> uint32_t count; >> - uint32_t csum_flags; >> + uint64_t csum_flags; >> struct ng_patch_op ops[]; >> }; >> >> >> In this patch new uint64_t type is utilized. Instead this you can get back modified "csum_flags" to ng_parse_uint32_type in NG_PATCH_CONFIG_TYPE_INFO, which was changed in r309389. >> Patch and rebuild ng_patch module. > > А можно всё то же самое оформить в виде PR в http://bugs.freebsd.org/ и прислать мне ссылку? Займусь. > From owner-freebsd-net@freebsd.org Fri Dec 1 14:15: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 796DDE571BB for ; Fri, 1 Dec 2017 14:15:45 +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 67B493D4D for ; Fri, 1 Dec 2017 14:15:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB1EFhHo074194 for ; Fri, 1 Dec 2017 14:15:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 206185] [netgraph][patch] refactoring ng_patch Date: Fri, 01 Dec 2017 14:15:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@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: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 14:15:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206185 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 240 | |19 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Dec 1 14:21:38 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 97CBAE574C6 for ; Fri, 1 Dec 2017 14:21:38 +0000 (UTC) (envelope-from balint.martina@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 72B9C633FB for ; Fri, 1 Dec 2017 14:21:38 +0000 (UTC) (envelope-from balint.martina@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6E0A1E574C5; Fri, 1 Dec 2017 14:21:38 +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 6DB18E574C4 for ; Fri, 1 Dec 2017 14:21:38 +0000 (UTC) (envelope-from balint.martina@gmail.com) Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::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 3D170633F9 for ; Fri, 1 Dec 2017 14:21:38 +0000 (UTC) (envelope-from balint.martina@gmail.com) Received: by mail-pg0-x235.google.com with SMTP id m25so4534593pgv.12 for ; Fri, 01 Dec 2017 06:21:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=B8dkqxopCAmLDh8EC5pVrXw3PkdTq4SvBsaLwwHyetE=; b=Rf+aV5tTjLsbyq/a7C1SdXeD1O/UC3DFFAG38B14Dpe/RC+EznpN8G3jZi/PJrP7ww c6bME+ftnntjOCvyBMHXi8R+vYFZAaTSTBnPdzc0dqu/qzj00kxH5fRkT7OusqpoB1rZ dK2+CpzfpFz83h6hocX0xsnj1dwKvkTq87864D42lCk5ofv2gOjHKGFDJjSEBAtYnX2K ofbQsD7D/C50w3RoyKwWZYm6UGJO3MSPKCYEHPvGml//gbWCEcliugfViWD298anRO4A 9B+f/qImFpze081y2T5ud9n5G4NGMLNLwCRRnjGVcGFYcqiJ3AKlPIpT0ItC109JhtaP xG8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=B8dkqxopCAmLDh8EC5pVrXw3PkdTq4SvBsaLwwHyetE=; b=qs2ZF7v2pLTvIcek+E/uPx4VM+c4mWWBb/C/1nQEiBbjQ6HwfgVocaekoXoEqN9jMg bQiQHsdR3IGA9uKjhXzg+yyTSvWAqB2Gz5Y03E/umM0mUSK75zeEpzo3DDyp8u6U9F1K R1al3f0UIetGMSEpN67lFgoR++f3vEtAFesAIQMLfRLw0PZWkjghODd5OKqWUlO1TJYg DMhIyUQ+gw4At1PxrzImXP7g6+yN9CDAqiT3E8VND+5Yn7+Zs36FS568lVfIbn3XFs4L yu3PXUuyRyqC1dsdINb2uJCDDmxJd7h4PyW3cQ9rR4YFF4/7oKePfcOjdG9YGNTcmoQX Wirg== X-Gm-Message-State: AJaThX7HPn+2OKw0O1tPuWwtxpKQiThWHljzdSGli8p7Pcj7cbh6yQgj y4iIlzG7GLrS/ojYfQ1rHPAGJ/7bPbREfQWGZOQ= X-Google-Smtp-Source: AGs4zMZQj7YgcYRg4uyZDtX/0gxGWBnIvUmFFXKOgo4dBkTaHBZ/Kkh1mc6uSBEDtsGNOe9IcnOrNuSFJVI+mY6N36o= X-Received: by 10.98.178.137 with SMTP id z9mr10537650pfl.114.1512138097584; Fri, 01 Dec 2017 06:21:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.167.142 with HTTP; Fri, 1 Dec 2017 06:21:36 -0800 (PST) Received: by 10.236.167.142 with HTTP; Fri, 1 Dec 2017 06:21:36 -0800 (PST) In-Reply-To: References: From: Martina Balintova Date: Fri, 1 Dec 2017 14:21:36 +0000 Message-ID: Subject: Netmap ouch double free To: net@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 14:21:38 -0000 Hi, I am currently playing with lb app in netmap. Every time I kill/close it, the app hangs for some time and does not end immediately. In syslogs I am getting: ' Netmap_do_unregif deleting last instance for myapp{1 Netmap_do_deref active=5 Netnap_obj_free ouch, double free on buffer 27777 Netmap_extra_free freed 0 buffers ' This happens when I have some consumer on the pipe and at some point during whole lb lifetime, it did not consume all packets (resulting in oq being filled or packets being dropped). If the pipe did not ever have a consumer, then it will not end up in the double free. I am finding it quite hard to debug in gdb, as this is happening at the shutdown. Could someone pls point me to reason? I am running lb with one interface and 2 groups, different numb of pipes per group and this happens even with no extra buffers. Martina From owner-freebsd-net@freebsd.org Fri Dec 1 18:39:38 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 A2D90E67628 for ; Fri, 1 Dec 2017 18:39:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F8706BF75 for ; Fri, 1 Dec 2017 18:39:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB1IdcTY009511 for ; Fri, 1 Dec 2017 18:39:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 105925] problems with ifconfig(8) and vlan(4) [regression] Date: Fri, 01 Dec 2017 18:39:38 +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: 7.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fernando.apesteguia@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 18:39:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D105925 fernando.apesteguia@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fernando.apesteguia@gmail.c | |om --- Comment #5 from fernando.apesteguia@gmail.com --- This ancient PR seems to be fixed now: fernape@beastie:~/test$ sudo ifconfig vlan77 create vlan 77 vlandev re0 up Password: fernape@beastie:~/test$ ifconfig vlan77 vlan77: flags=3D8843 metric 0 mtu 1= 500 options=3D80001 ether 00:1e:8c:b5:fc:3b inet6 fe80::21e:8cff:feb5:fc3b%vlan77 prefixlen 64 scopeid 0x5=20 nd6 options=3D21 media: Ethernet autoselect (1000baseT ) status: active vlan: 77 vlanpcp: 0 parent interface: re0 groups: vlan=20 fernape@beastie:~/test$ uname -a FreeBSD beastie 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:1= 2:40 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI= C=20 amd64 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Dec 1 19:07: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 CFF92E680DB for ; Fri, 1 Dec 2017 19:07: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 BE1196CF09 for ; Fri, 1 Dec 2017 19:07: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 vB1J7l86079985 for ; Fri, 1 Dec 2017 19:07:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 105925] problems with ifconfig(8) and vlan(4) [regression] Date: Fri, 01 Dec 2017 19:07:47 +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: 7.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: eugen@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution assigned_to cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 19:07:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D105925 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Overcome By Events Assignee|freebsd-net@FreeBSD.org |eugen@freebsd.org CC| |eugen@freebsd.org Status|In Progress |Closed --- Comment #6 from Eugene Grosbein --- Fixed long time ago. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Dec 1 22:30:28 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 D18ACE6CD8B for ; Fri, 1 Dec 2017 22:30:28 +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 BF41474236 for ; Fri, 1 Dec 2017 22:30:28 +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 vB1MUR3Q008675 for ; Fri, 1 Dec 2017 22:30:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224019] [netgraph] [patch] ng_patch is broken in 10.4-RELEASE Date: Fri, 01 Dec 2017 22:30:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.4-RELEASE X-Bugzilla-Keywords: easy, patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 22:30:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224019 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 Sat Dec 2 06:04: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 5F3C3DF4A60 for ; Sat, 2 Dec 2017 06:04:56 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) (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 323473034 for ; Sat, 2 Dec 2017 06:04:55 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-oi0-f53.google.com with SMTP id s9so8588032oie.5 for ; Fri, 01 Dec 2017 22:04:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XDNnhVI5Xe3e7Z9MfvLl5L0OI0U2d56vIIsGFwNH/uo=; b=Do24QKvmgg4aFZIjDNWCU2wKj/8/SSTR6ucCiQb45sEWIELOBNX9Wxk6G9UoXaZTbh Gs1xyqTXkAilSBjqE6ySmdNVMMTO6bzbRVbv6d4ZuD76nIcbyK/r0ejyvKGg75FJzkBM nXzraYdJVHCMjZuynavmNPnpac7K0UE+kNPW0l8lJR/W6Lyy89Tj/rfdoIExWTKddIpW MGvNf8XjrUNF4ThamRM4mhiLCGCSARdJ6ubHc0Cgn082yr3lG38dIBXvIdRMoXP18qf7 Ws20TcEh8pl+XxHps/3rII74PTZvmyyTv3esgvaMKoxbsYaipcAN/h7PVyavlRL8aV7I rHsA== X-Gm-Message-State: AJaThX4lNHTZ9lYN7ObUpDthQZlDe2ZuAP60IYAmU1LlYc7PpX2t14d2 /717FoRIOAXM40oZEwZllx4f57lH7hsU6IRaoZE= X-Google-Smtp-Source: AGs4zMZSKkFN3tz44u2ccYacgUiATS9/SYNLC9FAwjgGmz7BA2UTVer+BdkVAja4j1it2LOiGq3mWjgU8CWa/+g4OE0= X-Received: by 10.202.8.216 with SMTP id 207mr9140594oii.334.1512191490825; Fri, 01 Dec 2017 21:11:30 -0800 (PST) MIME-Version: 1.0 References: <5A206FB9.3010106@cox.net> In-Reply-To: <5A206FB9.3010106@cox.net> From: "K. Macy" Date: Sat, 02 Dec 2017 05:11:20 +0000 Message-ID: Subject: Re: netmap / LINUX realtime / ixgbevf: huge RX latencies To: Joe Buehler Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2017 06:04:56 -0000 HEAD or 11? On Thu, Nov 30, 2017 at 13:03 Joe Buehler wrote: > I am using the LINUX 4.4.86 realtime kernel patch with netmap and the > ixgbevf driver (SRIOV in a VM) and having some serious RX latency issues. > > The ixbgevf driver built by the netmap build against the kernel source > does not work. I haven't tried to debug it -- the netmap driver > complains about bad ring index values and resets (over and over again as > my app runs). > > The non-netmap version of ixgbevf that comes with the kernel works but > appears to have serious RX latency issues due to frame batching. It > appears that the kernel's NAPI polling reads frames from the NIC, then > netmap processes the frames, then epoll exits and my app can work on the > frames. The delay between start of NAPI to my app getting frames can be > milliseconds!!! > > Would the netmap-modified ixgbevf driver eliminate this latency? > > If so, any ideas on what might be going wrong with the modified driver? > Perhaps an older version of the driver might be better? The kernel > ixgbevf version is 2.12.1-k while netmap is trying to use 4.2.1. > Looking at the RT patch for LINUX there are only a few network driver > patches, none for the ixgbe* cards. > > Joe Buehler > > _______________________________________________ > 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 Sat Dec 2 12:21:15 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 38E3EDFD6BA for ; Sat, 2 Dec 2017 12:21:15 +0000 (UTC) (envelope-from aspam@cox.net) Received: from fed1rmfepi107.cox.net (fed1rmfepi107.cox.net [68.230.241.138]) by mx1.freebsd.org (Postfix) with ESMTP id 139A06C9D2 for ; Sat, 2 Dec 2017 12:21:14 +0000 (UTC) (envelope-from aspam@cox.net) Received: from eastrmimpo305.cox.net ([68.230.241.237]) by eastrmfepo201.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20171202122100.UHDV4103.eastrmfepo201.cox.net@eastrmimpo305.cox.net> for ; Sat, 2 Dec 2017 07:21:00 -0500 Received: from thunder.sweets ([68.100.138.62]) by eastrmimpo305.cox.net with cox id h0Lz1w00Q1LxgH8010LzFn; Sat, 02 Dec 2017 07:20:59 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.5A229AAB.0103, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.2 cv=eqmv9shX c=1 sm=1 tr=0 a=3mkzfl4ircflX6G+lDqBYw==:117 a=3mkzfl4ircflX6G+lDqBYw==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=ocR9PWop10UA:10 a=9axD0TMVbtiKC6hRN-kA:9 a=QEXdDO2ut3YA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [10.10.10.15] (thunder.sweets [10.10.10.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thunder.sweets (Postfix) with ESMTP id E33F610E7B; Sat, 2 Dec 2017 07:20:57 -0500 (EST) Message-ID: <5A229AA8.3070002@cox.net> Date: Sat, 02 Dec 2017 07:20:56 -0500 From: Joe Buehler User-Agent: Thunderbird 1.5.0.12 (X11/20120201) MIME-Version: 1.0 To: "K. Macy" CC: "freebsd-net@freebsd.org" Subject: Re: netmap / LINUX realtime / ixgbevf: huge RX latencies References: <5A206FB9.3010106@cox.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2017 12:21:15 -0000 K. Macy wrote: > HEAD or 11? I'm not quite sure what the question means but there is this in the netmap code: ./net/netmap.h:42:#define NETMAP_API 11 /* current API version */ LINUX kernels nowadays can timestamp frames when they arrive from the NIC. I made a trivial patch to the netmap driver to turn this on and also pass the timestamp to user space, and will pass on the changes. I am doing frame latency measurements and this simple change eliminated a *whole* lot of noise in the measurements. Joe Buehler From owner-freebsd-net@freebsd.org Sat Dec 2 12:40:52 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 DB12FDFDFBD for ; Sat, 2 Dec 2017 12:40:52 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DCD16D7BA; Sat, 2 Dec 2017 12:40:52 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id a16so16231042qtj.3; Sat, 02 Dec 2017 04:40:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LcNNxc89ZbqzaUqUGKFV1sdR1kot46NeNsPwt1D2p/Q=; b=DRL4A2Yz52E029H8dPwvcu22fAlrm39xkLyKd3npucLzpmv5/bEcNc/FnVR5zzIkQA Gn5yPlcMFoj9YBBpydhlInLr+EMADmJ5vkLdvsZiqZCq7KiYQ/8JgSb9QoXV4ZLF7nFp co48C65F4hWiDqHEzj6Jy5eicLP1W+6HS+e+i2SqUk9TjHZWSek99XHpMPP+OeGppWXR 7Vqh5jDWhHh5afbbITAOPgwzHkX1gl5HshiYwL9KBjOmWbHdHG23hYBYYNhF/Wmu8EHR mr5TmOMGBdN4bwoNchESCKtCkxGuC2eYSRNbHkOBMDpxsz3nFsUk14eoh2r/dee6ZP9o 0fzg== 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=LcNNxc89ZbqzaUqUGKFV1sdR1kot46NeNsPwt1D2p/Q=; b=Q1DpGGU5zDuQ+dhdX8rXI/y8mhL0hgx0CQF0VL9hW9tKTS2Xhul1j59KicV5t1NmbA BKLKZs3158DC8In8bCsf+bjOi5DzKRrWLwuRwicS7RwosPoGxe5/v/eeW6VO1GPSkrq5 4vG+jDmaSszqmD6jHLD/XD5C/TLMemRhp73pVsd+8pM2xhcoMEz1CImv7zIsav8YcK5b J+QkOkGgXuKLY6zTpcfa6KCjEzgEh5qtT5uzRePt8Udy4DIno6m2zA8+7QA8YI9MqnF9 GVnheRy6wIXRLMqACDnTA+SDUI54aW7rv3w1WfW6j75oHJS05XmOBg004EjD0LgErCA1 bqSw== X-Gm-Message-State: AKGB3mKbpThR7s0kzC6MfjmaNT+R2R7v/Um7w59qivA/o/ScFZaib3QB vrl+5Vrvdtdtqywl5nExca82qq/BHNHalyi+M5E= X-Google-Smtp-Source: AGs4zMavUVYOAu5LP4wKd1+Klqh4tAfKZFVF9I68+RJDAW4cPIzc8eM0Vi+LuQKhfk8ljk9ww3N4sSEAdZptnUnaMfs= X-Received: by 10.200.55.155 with SMTP id d27mr13517866qtc.115.1512218451522; Sat, 02 Dec 2017 04:40:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.174.5 with HTTP; Sat, 2 Dec 2017 04:40:50 -0800 (PST) In-Reply-To: <5A229AA8.3070002@cox.net> References: <5A206FB9.3010106@cox.net> <5A229AA8.3070002@cox.net> From: Vincenzo Maffione Date: Sat, 2 Dec 2017 13:40:50 +0100 Message-ID: Subject: Re: netmap / LINUX realtime / ixgbevf: huge RX latencies To: Joe Buehler Cc: "K. Macy" , "freebsd-net@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2017 12:40:53 -0000 HEAD/11 is the FreeBSD version. Your question is about netmap on Linux, so this is the wrong mailing list. You should open an issue on the official netmap https://github.com/luigirizzo/netmap/issues Cheers Vincenzo 2017-12-02 13:20 GMT+01:00 Joe Buehler : > K. Macy wrote: > > > HEAD or 11? > > I'm not quite sure what the question means but there is this in the > netmap code: > > ./net/netmap.h:42:#define NETMAP_API 11 /* current > API version */ > > LINUX kernels nowadays can timestamp frames when they arrive from the > NIC. I made a trivial patch to the netmap driver to turn this on and > also pass the timestamp to user space, and will pass on the changes. I > am doing frame latency measurements and this simple change eliminated a > *whole* lot of noise in the measurements. > > Joe Buehler > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > -- Vincenzo Maffione From owner-freebsd-net@freebsd.org Sat Dec 2 15:02:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1D42E578F0 for ; Sat, 2 Dec 2017 15:02:13 +0000 (UTC) (envelope-from meka@tilda.center) Received: from mail.tilda.center (tilda.center [45.77.138.211]) by mx1.freebsd.org (Postfix) with ESMTP id 9EF117307C for ; Sat, 2 Dec 2017 15:02:13 +0000 (UTC) (envelope-from meka@tilda.center) Received: from hal9000.meka.no-ip.org (unknown [87.116.178.128]) by mail.tilda.center (Postfix) with ESMTPSA id DDE1CC65C for ; Sat, 2 Dec 2017 15:56:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tilda.center; s=mail; t=1512226583; bh=32QMNkABOVEdOUnkBMm6FRmaZeUjPOAM62B+A2VskGg=; h=Date:From:To:Subject; b=OCCrSajvRYN/UqZmJ8i0CEPkt3w84WzDqKUA58enP9NChcIG4tEMeJqgZsQfbWVQ/ bk9PzebVsmNl9rsiyVYjb5Zhwg5fJVFHomG4K+9hJDRpdpuxWC3JYXxOdfVF7Vc4WF ywGvalfFKZAacwroU59mdO3lDQbfkIhJV0SC3OQ8= Date: Sat, 2 Dec 2017 15:56:20 +0100 From: Goran =?utf-8?B?TWVracSH?= To: freebsd-net@freebsd.org Subject: resolvconf.conf name_servers option Message-ID: <20171202145620.5ik4f2lrnkr5tf73@hal9000.meka.no-ip.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="36lqkac2nkuk2v6s" Content-Disposition: inline User-Agent: NeoMutt/20171027 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2017 15:02:13 -0000 --36lqkac2nkuk2v6s Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Hello, I found out that when I set "name_servers=127.0.0.1", that's the only nameserver line in /etc/resolv.conf after resolvconf -u, but the man say: name_servers Prepend name servers to the dynamically generated list. You should set this to 127.0.0.1 if you use a local name server other than libc. I get the same result if I use "prepend_nameservers=127.0.0.1". Strange enough, "append_nameserver=127.0.0.1" works as expected: two nameserver lines, one with DHCP provided one and second with 127.0.0.1. I'm running 11.1-p5. Am I the only one having that problem? Regards, meka --36lqkac2nkuk2v6s Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE1WIFkXy2ZeMKjjKEWj1TknovrLYFAloivxEACgkQWj1Tknov rLbZsQ//QRZlIGfrV4/svi23va1BJZ2qmDZHeuXIrp7RkWhdMYIZiPQvHtlrNdZ8 7t5J2BfRwjmTUHAqv2ObJmJ6H1tWIQQXaNsumb/G6egn60c2zIvYJjulek433Z5T dx4bz4ENjsIpAhxGzhofG2lZdXeV5GaC735cLjr2ZprzBSbe4WXrOJEayA2g5LU+ BYlIljfQ4iswVQ9sgHqmccvi21oUMlnD+VljEdHOr6QfD52kzkNGy+Rt3ixkyoST WEdZbJ3+O3knNbPupJmB61uaaXZ/TnMFE2UUlVSoBiT1P7nlxGvcP3gHuGWkzVDE hqf0Bvjsk/X125E7qn0l72hAdBfxJwSopscdB0z+ZC/JwyhJTU9PQzhs28meOpI6 8RZ7QduTLOeiyLDnkGgKsH5486SsfbXCEYau3CQpBAMLimmThDOQh5RhSfd1/PR9 u2SI4QbgW2e2mbEjUZSegSnKP5i3PRqEEOia+vB8/X7mKbYVteHHSGfBxpJ1pNlJ bB03Kg/kP4j5N8hc/Vfj0D/B5jWRv1l4ODzVl+3ugQRuwXB4uEvU3jghTVU+rB35 iTLVXuyOBw5HsjyqojqM22kgURXO2qh6tXAC6K69Tzf5CkWZF9FyRB/vXXjZtYzt Vf5OQvOXlAxsSWlgyNeBcei68xcd/WTi9O5kZuC9WOxhx/xrEHA= =1gu3 -----END PGP SIGNATURE----- --36lqkac2nkuk2v6s-- From owner-freebsd-net@freebsd.org Sat Dec 2 18:30: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 AB5E1E6688C for ; Sat, 2 Dec 2017 18:30:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com [209.85.128.182]) (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 4C3FA790C5 for ; Sat, 2 Dec 2017 18:30:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wr0-f182.google.com with SMTP id y21so13162941wrc.1 for ; Sat, 02 Dec 2017 10:30:52 -0800 (PST) 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:content-language :content-transfer-encoding; bh=9Qm8siCBFw/ENUtwXOBbI2EBYtyiF48luMYnKXQQBPY=; b=h1VjgFIQ8E7eoDJrC5tqQUqITOGf4kJlCwEBexSTFpe3gJcMaLuuGNaj9qm1JIIFj8 c5PEqaMLLeOtxMnHP59BUmyUdBngtxjEMIN2DkXlsxW1GK260uytU62BnTnXpYZAiFk7 sQCGLUGZofgArETHtwJTBO9V6HDy5SNlWPgt4cs1hQiNy5FcfUdX7QMZWgOXZmOHv9UV U2k8Z9MlF4KLnzPNpSgG5d778kleXzpo9nfJ9hxLmGYkKz34VXVwP4mpjMT5nAt04T8f 56D/r/J/ATkd0CAS9luzEwahc36pvLACOecjMSGJksC223Hp8qpJe8dR7o1PPKB7YCp1 by0g== X-Gm-Message-State: AJaThX4aAzBjoqSOL0PndYCxH92sphQcQ98G+bYTAgA/i3v6AqTStafa JktEBFweUuxIMXbc0nU++2fFolYx X-Google-Smtp-Source: AGs4zMbG8M7RtVweW1wKmh1t71FCoh+macPJR1jsdlTS5ffconYjlBT0PCCRekrf//1PPkf4g6zL5Q== X-Received: by 10.223.169.183 with SMTP id b52mr9339714wrd.63.1512239086362; Sat, 02 Dec 2017 10:24:46 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id t200sm4059679wmd.45.2017.12.02.10.24.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Dec 2017 10:24:45 -0800 (PST) Subject: Re: resolvconf.conf name_servers option To: =?UTF-8?Q?Goran_Meki=c4=87?= References: <20171202145620.5ik4f2lrnkr5tf73@hal9000.meka.no-ip.org> Cc: freebsd-net@freebsd.org From: Andriy Gapon Message-ID: Date: Sat, 2 Dec 2017 20:24:44 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171202145620.5ik4f2lrnkr5tf73@hal9000.meka.no-ip.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2017 18:30:53 -0000 On 02/12/2017 16:56, Goran Mekiд┤ wrote: > Hello, > > I found out that when I set "name_servers=127.0.0.1", that's the only > nameserver line in /etc/resolv.conf after resolvconf -u, but the man > say: > > name_servers > Prepend name servers to the dynamically generated list. You > should set this to 127.0.0.1 if you use a local name server other > than libc. > > I get the same result if I use "prepend_nameservers=127.0.0.1". Strange > enough, "append_nameserver=127.0.0.1" works as expected: two nameserver > lines, one with DHCP provided one and second with 127.0.0.1. > > I'm running 11.1-p5. Am I the only one having that problem? See resolv_conf_local_only. There are some complex dependencies between options. -- Andriy Gapon