From owner-freebsd-stable@freebsd.org Sat Jun 16 19:42:12 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAAC610209BD for ; Sat, 16 Jun 2018 19:42:11 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 6D9B26D128 for ; Sat, 16 Jun 2018 19:42:11 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id w5GJg8EY021324 for ; Sat, 16 Jun 2018 21:42:08 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 6A19A3D4 for ; Sat, 16 Jun 2018 21:42:08 +0200 (CEST) To: freebsd-stable@freebsd.org From: Harry Schmalzbauer Subject: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2? Organization: OmniLAN Message-ID: <79e621cc-9c0a-c0c8-decd-5789241a633f@omnilan.de> Date: Sat, 16 Jun 2018 21:42:07 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sat, 16 Jun 2018 21:42:08 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2018 19:42:12 -0000 Hello, I'm observing some kind of congestion with virtualbox-ose-kmod-5.2.12 on -current. Frames from the guest make it through ng_ether(4), but frames coming from ng_ether(4) seem to choke this direction. Initially, the guest successfully can get a DHCP lease (both, v4 and v6) and all DNS traffic is passed successfully, but as soon as the first TCP transmission with some payload happens (jumbo frames, but quick test showed that also 1514-frames choke the LAN->guest direction), not even ARP replys reach the guest anymore. At least they are traversing ng_ether(4).  So there's either a general netgraph(4) problem or vboxnetflt(4) problem on -current. To rule out a known vboxnetflt(4) limitation/failure, I'd like to know if somebody successfully uses vboxnetflt(4) from virtualbox-ose-kmod-5.2.12 on stable/11|11.2. Thanks, -harry