From owner-freebsd-emulation@FreeBSD.ORG Thu Aug 2 22:30:06 2007 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5302516A419 for ; Thu, 2 Aug 2007 22:30:06 +0000 (UTC) (envelope-from per@hedeland.org) Received: from pluto.hedeland.org (1-1-1-13a.mal.sth.bostream.se [82.182.84.27]) by mx1.freebsd.org (Postfix) with ESMTP id C0F8213C46B for ; Thu, 2 Aug 2007 22:30:05 +0000 (UTC) (envelope-from per@hedeland.org) Received: from pluto.hedeland.org (localhost [127.0.0.1]) by pluto.hedeland.org (8.13.6/8.13.1) with ESMTP id l72M95aB052160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Aug 2007 00:09:05 +0200 (CEST) (envelope-from per@pluto.hedeland.org) Received: (from per@localhost) by pluto.hedeland.org (8.13.6/8.13.1/Submit) id l72M95Jl052159; Fri, 3 Aug 2007 00:09:05 +0200 (CEST) (envelope-from per) Date: Fri, 3 Aug 2007 00:09:05 +0200 (CEST) From: Per Hedeland Message-Id: <200708022209.l72M95Jl052159@pluto.hedeland.org> To: freebsd-emulation@freebsd.org, tnelson@onresolve.com In-Reply-To: X-Scanned-By: MIMEDefang 2.48 on 10.1.1.1 Cc: Subject: Re: Qemu networking issue X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2007 22:30:06 -0000 "Trent Nelson" wrote: > >I've tried the sysctl net.link.ether.bridge and ifconfig bridge0 >approaches mentioned in [1-4]. This initially involved having a tap0 >inet 0.0.0.0 broadcast 0.255.255.255 interface, and a bridge0 with >em0,tap0 (and no assigned IP for the bridge), but when I tried to tell >the Windows box to use IP 205.97.38.47 (after I've removed this aliased >IP from em0), subnet 0xffffff00, gateway 216.203.62.29, the local >connection properties dialog would hang with 'Acquiring address...' then >eventually fail. If I picked an IP address like 192.168.0.1, it would >go through, but there wouldn't actually be any network connectivity >between the host/guest. Like others have in their replies, I would recommend the ifconfig method - and as also mentioned, both bridge and tap interface must be ifconfig'ed "up", but neither with an IP address. Your 0.0.0.0 on tap0 above may be OK, but no reason to put it there. However, the config you're telling windows to use - "IP 205.97.38.47, subnet 0xffffff00, gateway 216.203.62.29" - doesn't make sense: The gateway must be in the local subnet, i.e. 205.97.38.xxx if you want to use 205.97.38.47/0xffffff00. I'm not sure why you have addresses in two different subnets on em0 to begin with, it's a bit "strange" - in any case a host that "is" in only one of those subnets needs a gateway in that subnet to reach the other (or anything else). Whether this problem is actually the cause of the 'Acquiring address...' hang I don't know though... --Per Hedeland