From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1283) From: Bakul Shah In-Reply-To: <48e4f741-05de-4a34-903f-05d7e62623d2@googlegroups.com> Date: Thu, 14 Mar 2013 12:46:31 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <032D2FA8-8234-4DCD-BC7A-6B8E753E7F45@bitblocks.com> References: <48e4f741-05de-4a34-903f-05d7e62623d2@googlegroups.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] 9atom vs 9front Topicbox-Message-UUID: 299d0b48-ead8-11e9-9d60-3106f5b1d025 On Mar 14, 2013, at 4:43 AM, Kyle Laracey wrote: > On Monday, March 11, 2013 4:56:16 PM UTC-4, Bakul Shah wrote: >> Just discovered that at least on the MBP you can get bridged >>=20 >> mode to work by using en1: Wi-Fi (AirPort). >=20 > Really? I have the same setup as you mentioned, with Bridged Adapter, = en1: Wifi (AirPort), and Promiscuous Mode set to {Deny, Allow VMs, Allow = All}, but for each of those three options for Promsicuous mode, = ip/ipconfig still times out with "ipconfig: no success with dhcp". This works for me on the last 2011 model (the one before the=20 "Retina" display MBPs) and it works on a 6 year old MBP. Your =20 problem may be card dependent as Matthew says or it may be some config issue. Try debugging with tcpdump on the host. See if DHCP provides a working IP address for other VMs (Linux for instance) on the same laptop when connected via en1. See if manually setting the IP address allows you use the net.=