qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: renzo@cs.unibo.it (Renzo Davoli)
To: qemu-devel@nongnu.org
Subject: Re: RESOLVED: Re: [Qemu-devel] Networking on Win2K host
Date: Mon, 9 Aug 2004 19:56:03 +0200	[thread overview]
Message-ID: <20040809175603.GE3737@cs.unibo.it> (raw)
In-Reply-To: <5640213304080910481e37d8a7@mail.gmail.com>

On Mon, Aug 09, 2004 at 12:48:28PM -0500, Mike Tremoulet wrote:
> What I learned from this is that, as you said, slirp essentially set
> up a NAT behind 10.0.2.2.  However, this was not resolving until I
true.
> changed the /etc/resolv.conf on the Gentoo guest to point at
> 192.168.0.1.  (It was originally set for 10.0.2.3)
> 
Strange, the slirp support has been designed to forward DNS on the
address 10.0.2.3 and the internal DHCP has been designed to broadcast this info.

> I think that, unless slirp is doing something I don't know about, that
> qemu is using the TAP-Win32 adapter on my host machine, which is set
> through Windows internet connection sharing (ICS) to go through my
> ethernet adapter.  I'm not seeing traffic on the TAP adapter, though,
> but nothing else I know of has an IP of 192.168.0.1.

Mike, either you use tap or user-net, these are mutually esclusive
approaches. If you use user-net you use slirp and you do not need any
TAP configuration or you use tap and the address must be given by a dhcp
server running on your host computer or just defined statically in a
consistent way.

ciao
	renzo

      reply	other threads:[~2004-08-09 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 14:54 [Qemu-devel] Networking on Win2K host Mike Tremoulet
2004-08-09 15:38 ` Renzo Davoli
2004-08-09 17:20   ` Mike Tremoulet
2004-08-09 17:48     ` Renzo Davoli
2004-08-09 17:48     ` RESOLVED: " Mike Tremoulet
2004-08-09 17:56       ` Renzo Davoli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040809175603.GE3737@cs.unibo.it \
    --to=renzo@cs.unibo.it \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).