From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Mar 12 17:51:18 2015 Return-Path: Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A29E189 for ; Thu, 12 Mar 2015 17:51:18 +0000 (UTC) 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 5BC4EF80 for ; Thu, 12 Mar 2015 17:51:18 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CHpIkg043354 for ; Thu, 12 Mar 2015 17:51:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 198547] emulators/virtualbox-ose: Host-Only network failure Date: Thu, 12 Mar 2015 17:51:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: zaphod@berentweb.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: vbox@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 17:51:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198547 Bug ID: 198547 Summary: emulators/virtualbox-ose: Host-Only network failure Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: vbox@FreeBSD.org Reporter: zaphod@berentweb.com Flags: maintainer-feedback?(vbox@FreeBSD.org) Assignee: vbox@FreeBSD.org Created attachment 154247 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154247&action=edit tcpdump for Linux guest * Using Port versions virtualbox-ose-4.3.24 / virtualbox-ose-kmod-4.3.24 * I use Host-Only for all guests. Network vboxnet0 has DHCP enabled, but some guests use static-IP/static gateway as defined from within the guest's config. * Subnet on vboxnet0 is /28 (broadcast 192.168.56.15). There's no guest running on 192.168.56.1 which is the gateway/DHCP * I have 3 general classes of guests: *BSD, Windows, Linux and 3 different things happen re networking when I start these guests. * Linux guests: cannot ping gateway (192.168.56.1), cannot ping other guests, can ping itself. netstat shows correct route table. * Windows guests: Same problem as Linux, netstat shows correct route table. Then I start a *BSD guest and can now can ping Linux guests, gateway and outside of subnet. However, network status does not behave in a consistent manner. * BSD Guests: Behave as expected, can ping other guests, gateway and outside of subnet without problems. * Guests of the other 2 OS categories appear to behave more sanely (conjecture) if a BSD guest is started first, before the other guests. The BSD guest does not need to keep running. A simple start/stop is sufficient to activate the vboxnt0 network path. * tcpdump on vboxnet0 shows exactly what I have described: No traffic reaches vboxnet0 from Linux/Windows guests. After a BSD guest is started then stopped, pinging from the Linux guest shows that traffic reaches vboxnet0, and that it gets no response: 19:24:05.531541 ARP, Request who-has 192.168.56.1 tell 192.168.56.13, length 46 19:24:05.531547 ARP, Request who-has 192.168.56.1 tell 192.168.56.13, length 46 * Full tcpdump for startup/shutdown process of the Linux guest is attached. -- You are receiving this mail because: You are the assignee for the bug.