From owner-freebsd-questions@FreeBSD.ORG Sun Jan 6 12:10:46 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AD9E3219 for ; Sun, 6 Jan 2013 12:10:46 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 44DC5D7F for ; Sun, 6 Jan 2013 12:10:46 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.2.117.99]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.6/8.14.5) with ESMTP id r06CAd8a009759 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 6 Jan 2013 12:10:39 GMT (envelope-from m.seaman@infracaninophile.co.uk) DKIM-Filter: OpenDKIM Filter v2.7.3 smtp.infracaninophile.co.uk r06CAd8a009759 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1357474239; bh=rPjkhJnWi+pRUxaoi8tmFFuKXBmkfyEXGcFMvHfJymk=; h=Date:From:To:CC:Subject:References:In-Reply-To; z=Date:=20Sun,=2006=20Jan=202013=2012:10:39=20+0000|From:=20Matthew =20Seaman=20|To:=20jb=20|CC:=20freebsd-questions@freebsd.org|Subject:=20Re:= 20FB=209.1=20boot=20loader=20problem=20in=20VirtualBox|References: =20=20=20<50E963CD.3030709@FreeBSD.org>=20|In-Reply-To:=20; b=Ey8Z68ZVdA0z7+P1nnUEemhi/cCuXu7aGjAmkrKKqupAVD5jtV82vAMfpBeOJdRHz 9gHUnxbAPGYUPAO9ouLOnM9U6WoFJ6Ubwg6BUAdMv7z+bfDKOyQUn3APLVxTFxx8M3 KAQhbHgOQHHAkUHXieJ0+5vym90V4/tza98JsHHM= Message-ID: <50E969BF.7050003@infracaninophile.co.uk> Date: Sun, 06 Jan 2013 12:10:39 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: jb Subject: Re: FB 9.1 boot loader problem in VirtualBox References: <50E963CD.3030709@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9C084978DD28B44E574BC14E" X-Virus-Scanned: clamav-milter 0.97.6 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2013 12:10:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9C084978DD28B44E574BC14E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 06/01/2013 11:52, jb wrote: > Matthew Seaman FreeBSD.org> writes: >=20 >> >> On 06/01/2013 11:19, jb wrote: >>> Next problem: >>> the installation's dmesg shows net driver em0, which is Intel PRO/100= 0 - and >>> this is how install offers to configure the network; >>> but my host has Broadcom Corporation NetLink BCM5787M Gigabit Etherne= t PCI >>> Express, which is bge0 driver in FB. >>> How to force it to discover the right net device during install, and/= or after >>> install ? >> This is normal for VirtualBox -- it doesn't matter what NIC the host >> has, VB always presents it as an em(4) interface to the guest. > OK. > But I also could not ping: > $ ping -c 1 google.com > I have VM-Settings-Network > Attached to NAT > What is the correct setting here ? Not really enough information there to say exactly what has gone wrong. NAT+DHCP should work. You need: ifconfig_em0=3D"DHCP" in /etc/rc.conf obviously. Try tcpdump(1) on the external interface of your host system to see if the traffic shows up. You will also need to have a process called something like VBoxNetDHCP running on the host. Process name might be slightly different on different host OSes (I'm using MacOS X). It should be started automatically but no harm checking. If that hasn't led to a fix, please post the output of: ifconfig em0 netstat -rn from the guest system. If NAT won't work, you might try bridged mode -- this effectively makes the VM share your main host's NIC and gives it its own externally visible IP on the network. You generally need bridged mode if you want to run servers in the VM. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew@infracaninophile.co.uk --------------enig9C084978DD28B44E574BC14E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDpab8ACgkQ8Mjk52CukIxqGACghqrlahz9XqKPg0feRXSe/iDY hekAn2Em0h+FzgxVXA7Jju+JHjwVNOGj =SnUC -----END PGP SIGNATURE----- --------------enig9C084978DD28B44E574BC14E--