qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Cc: joshk@triplehelix.org
Subject: Re: [Qemu-devel] slirp, darwin problems
Date: Fri, 25 Jun 2004 18:37:42 +0900	[thread overview]
Message-ID: <00af01c45a98$102e38d0$0264a8c0@afina> (raw)
In-Reply-To: 20040625053731.GA20270@darjeeling.triplehelix.org

Hi,

Friday, June 25, 2004 2:37 PM Joshua Kwan wrote:

>My thinking is that qemu might be looking in the wrong place for a
>gateway? My computer is behind a NAT, and has two network interfaces:
>one for a local wired network, and a wireless network which allows me to
>connect to my firewall and the Internet. My default gateway is set
>correctly and I am able to use the Internet normally from my host.
>However, qemu maybe doesn't see the default gateway being used or
>something?

QEMU with slirp is a simple client program. Virtual network in QEMU which
has DHCP server doesn't have any relationship with a host's network
configuration. If your debian can get an IP address like 10.0.2.x by dhcpcd
or dhclient from virtual DHCP server , the problem is that packets cannnot
be sent or received to QEMU.

If you can use tcpdump as root on a host OS, you can check it.
[host OS]# tcpdump -i eth0
or
[host OS]# tcpdump -i eth1     (if you have two cards)
or when you use a host-gest connection,
[host OS]# tcpdump -i lo

Then use a program on a guest OS.
[guest OS]$ lynx  http://----example-----/

When a connection is normal,  you will see some output of tcpdump.

Regards,
kazu

      parent reply	other threads:[~2004-06-25  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25  5:37 [Qemu-devel] slirp, darwin problems Joshua Kwan
2004-06-25  7:50 ` Jean-Michel POURE
2004-06-25  9:37 ` kazu [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='00af01c45a98$102e38d0$0264a8c0@afina' \
    --to=kazoo@r3.dion.ne.jp \
    --cc=joshk@triplehelix.org \
    --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).