From owner-freebsd-bugs@freebsd.org Sun Aug 25 19:37:31 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6C660E7E37 for ; Sun, 25 Aug 2019 19:37:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46Gllb2Hgxz4MGZ for ; Sun, 25 Aug 2019 19:37:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 4CA1AE7E36; Sun, 25 Aug 2019 19:37:31 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4C623E7E35 for ; Sun, 25 Aug 2019 19:37:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Gllb1K8fz4MGY for ; Sun, 25 Aug 2019 19:37:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E9E82225B3 for ; Sun, 25 Aug 2019 19:37:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7PJbUMg093720 for ; Sun, 25 Aug 2019 19:37:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7PJbUJm093719 for bugs@FreeBSD.org; Sun, 25 Aug 2019 19:37:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 240106] VNET issue with ARP and routing sockets in jails Date: Sun, 25 Aug 2019 19:37:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: john.westbrook@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 19:37:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240106 Bug ID: 240106 Summary: VNET issue with ARP and routing sockets in jails Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: john.westbrook@gmail.com I'm experiencing an intermittent connectivity issue running FreeBSD 12.0 wi= th jail using VNET, which appears to be related to lost ARP replies. There are several discussion threads on forums that appear related: https://forums.freebsd.org/threads/vnet-arp-replies-are-lost.71082 https://www.ixsystems.com/community/threads/arp-replies-loss-in-vnet.77027 https://www.ixsystems.com/community/threads/jails-eero.59477 One insightful comment from the first thread: """On step #2 the reply is mistakenly padded with 14 bytes which is exactly= the number of bytes beyond the 18 bytes in the request (the request was padded = with 32 bytes). I bet this is part of the bug. By looking at FreeBSD ARP reply c= ode it actually creates the reply by editing the request bytes in place. For so= me reason it removes only 18 bytes from the request padding. However, this hap= pens only on VNET interface as noted above.""" I was able to see ARP traffic using tcpdump, but (arp -a) doesn't contain updated ARP entries. Also, in an affected jail, I can't add static arp entr= ies: # arp -s 10.0.0.1 XX:XX:XX:XX:XX:XX arp: writing to routing socket: Cannot allocate memory whereas, in an unaffected jail the arp command succeeds. Jails are should h= ave access to routing sockets by default, so perhaps the problem is related to accessing routing sockets in VNET jails? The test setup where I'm observing this is using an SR-IOV VF (Chelsio cxlv= 0) passed into the jail (via vnet.interface in jail.conf). The test setup has = two jails each on two direct attached hosts. I observe the problem on both host= s, but it comes and goes with reboots. --=20 You are receiving this mail because: You are the assignee for the bug.=