From owner-freebsd-current@FreeBSD.ORG Tue Apr 10 01:04:04 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8B7016A400; Tue, 10 Apr 2007 01:04:04 +0000 (UTC) (envelope-from scottro@nyc.rr.com) Received: from mail14.simplicato.com (host65.simplicato.com [207.99.47.65]) by mx1.freebsd.org (Postfix) with ESMTP id 7E22D13C45B; Tue, 10 Apr 2007 01:04:04 +0000 (UTC) (envelope-from scottro@nyc.rr.com) Received: from mail14.simplicato.com (localhost [127.0.0.1]) by mail14.simplicato.com (Postfix) with ESMTP id 98666EBC2C; Mon, 9 Apr 2007 21:04:03 -0400 (EDT) Received: from uws1.starlofashions.com (unknown [12.44.50.124]) by mail14.simplicato.com (Postfix) with ESMTP id 40FE6EBC2A; Mon, 9 Apr 2007 21:04:03 -0400 (EDT) Received: by uws1.starlofashions.com (sSMTP sendmail emulation); Mon, 9 Apr 2007 21:04:02 -0400 Date: Mon, 9 Apr 2007 21:04:02 -0400 From: Scott Robbins To: freebsd-current@FreeBSD.org, freebsd-emulation@FreeBSD.org Message-ID: <20070410010402.GB54131@uws1.starlofashions.com> Mail-Followup-To: freebsd-current@FreeBSD.org, freebsd-emulation@FreeBSD.org References: <20070409132718.GA28377@uws1.starlofashions.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070409132718.GA28377@uws1.starlofashions.com> User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: Subject: Re: recent CURRENT seems to affect if_tap, if_bridge with qemu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2007 01:04:04 -0000 On Mon, Apr 09, 2007 at 09:27:18AM -0400, Scott Robbins wrote: > I have been using qemu and qemu-devel with if_tap and if_bridge. > The home network is a 192.168.1.0/24, I give the bridge a 192.168.1.x/32 > address add tap0 and vr0 (the host machine's interface) as members, and > give the qemu guest a 192.168.1.x/24 address with the same gateway as > the host. This has worked perfectly through March. The host runs > CURRENT. I didn't upgrade it through most of March, then finally had > time to do a buildworld the first week of April. > To follow up, the problem seems to be solved. In private email, someone suggested to me that I ensure that both bridge0 and tap0 were up. Prior to my latest update of CURRENT, my /etc/qemu-ifup script just had /sbin/ifconfig ${1} Changing it to /sbin/ifconfig ${1} up fixed the problem. -- Scott Robbins GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: What's going on here? People are going all Felicity with their hair.