From owner-freebsd-current@FreeBSD.ORG Tue Jan 9 02:08:44 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 39D7A16A407 for ; Tue, 9 Jan 2007 02:08:44 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.freebsd.org (Postfix) with ESMTP id EA1B113C45A for ; Tue, 9 Jan 2007 02:08:43 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: by gwyn.kn-bremen.de (Postfix, from userid 10) id 1D95D197B7F; Tue, 9 Jan 2007 02:42:07 +0100 (CET) Received: from saturn.kn-bremen.de (nox@localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.6/8.13.6) with ESMTP id l091eVZG087180; Tue, 9 Jan 2007 02:40:31 +0100 (CET) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.6/8.13.6/Submit) id l091eVFO087179; Tue, 9 Jan 2007 02:40:31 +0100 (CET) (envelope-from nox) Date: Tue, 9 Jan 2007 02:40:31 +0100 (CET) From: Juergen Lock Message-Id: <200701090140.l091eVFO087179@saturn.kn-bremen.de> To: scottro@nyc.rr.com X-Newsgroups: local.list.freebsd.current In-Reply-To: <20070108230555.GA1274@mail.scottro.net> Organization: home X-Mailman-Approved-At: Tue, 09 Jan 2007 12:37:08 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Problems with qemu networking after recent upgrade 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, 09 Jan 2007 02:08:44 -0000 In article <20070108230555.GA1274@mail.scottro.net> you write: > >After an upgrade Saturday (after a long period of not upgrading) >networking in qemu has stopped working for me. All modules load without >trouble (unlike my recent vmware troubles.) > >If, in a Windows guest system, I do ipconfig, it shows a typical >10.x.x.x qemu address. (My home network is a 192.168.1.x and qemu has >always worked with it.) > >However, if I then open up a web browser, or do anything else that >requires Internet connectivity, I get page cannot be found. > >There has been no difference in what I do with qemu or how I load >it--the only difference was the upgrade. > >I'm wondering if anyone else has had this problem, or if anyone could >give me a hint as to where to start troubleshooting it. > >I'm using the same pf configuration that I always used--disabling it >didn't help. I load aio and kqemu for qemu to work. Aside from that, I >do nothing special, it's always Just Worked(TM) using the default >networking. > > >Thank you for any input. I'm not quite sure what my next step should be >in troubleshooting this. I haven't written the maintainer or filed a PR >yet, because I have no idea if this is due to some oddity on my >particular system or not. (I haven't had a chance to throw a recent >CURRENT on something else and test it there.) Oh wow I should have catched that one... :-O Looks like the 10.0.2.3 dns redirection is broken indeed! Workaround: use the host's /etc/resolv.conf in the guest (or the nameserver(s) in there), I'll see if I can investigate further tomorrow. gnite, Juergen