From: Thomas Huth <thuth@redhat.com>
To: FONNEMANN Mark <mark.fonnemann@hexagon.com>,
Samuel Thibault <samuel.thibault@gnu.org>
Cc: Stefan Weil <sw@weilnetz.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
MCDONALD Margaret <margaret.mcdonald@hexagon.com>
Subject: Re: [Qemu-devel] dns server not working in QEMU using usermode networking (SLIRP)
Date: Mon, 8 May 2017 03:03:05 +0200 [thread overview]
Message-ID: <45bda408-e14a-ab39-a2fe-898fe96f5b40@redhat.com> (raw)
In-Reply-To: <VI1PR0601MB247996FB5818A956470FE8169CEB0@VI1PR0601MB2479.eurprd06.prod.outlook.com>
On 06.05.2017 00:38, FONNEMANN Mark wrote:
>> Could you run tcpdump inside the guest so we are sure what the nslookup call emits?
>
> Is there another way to determine this info? My guest OS is an embedded system with BusyBox 1.25 and not much else.
FWIW, QEMU also has a built-in packet-dump functionality. You can use it
like this:
qemu-system-xxx ... -netdev user,id=netuser \
-object filter-dump,id=dump,netdev=netuser,file=/tmp/dump.dat \
-device e1000,netdev=netuser,mac=00:11:22:33:44:55
Then run "wireshark -r /tmp/dump.dat" afterwards to have a look at the
packets.
Thomas
next prev parent reply other threads:[~2017-05-08 1:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 20:17 [Qemu-devel] dns server not working in QEMU using usermode networking (SLIRP) FONNEMANN Mark
2017-04-24 8:00 ` Thomas Huth
2017-04-24 23:43 ` FONNEMANN Mark
2017-04-29 12:44 ` Samuel Thibault
2017-04-29 15:32 ` FONNEMANN Mark
2017-04-29 17:10 ` Samuel Thibault
2017-04-29 18:25 ` FONNEMANN Mark
2017-04-29 19:14 ` Samuel Thibault
2017-04-29 20:06 ` FONNEMANN Mark
2017-04-29 22:01 ` Samuel Thibault
2017-04-29 23:15 ` FONNEMANN Mark
2017-04-30 7:50 ` Samuel Thibault
2017-04-30 12:42 ` FONNEMANN Mark
2017-04-30 12:57 ` Samuel Thibault
2017-05-05 22:38 ` FONNEMANN Mark
2017-05-05 23:14 ` Samuel Thibault
2017-05-06 0:33 ` FONNEMANN Mark
2017-05-06 0:56 ` Samuel Thibault
2017-05-06 1:06 ` FONNEMANN Mark
2017-05-06 1:17 ` Samuel Thibault
[not found] ` <VI1PR0601MB2479B2228D4C769486ECAEC39CE80@VI1PR0601MB2479.eurprd06.prod.outlook.com>
2017-05-06 9:23 ` Samuel Thibault
2017-05-06 15:06 ` FONNEMANN Mark
2017-05-08 1:03 ` Thomas Huth [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-15 23:27 FONNEMANN Mark
2017-04-16 8:09 ` Samuel Thibault
2017-04-16 22:10 ` FONNEMANN Mark
2017-04-21 19:58 ` Stefan Weil
2017-04-22 12:36 ` Samuel Thibault
2017-04-26 18:51 ` FONNEMANN Mark
[not found] <VI1PR0601MB247952CA06D05D5041AA450D9C130@VI1PR0601MB2479.eurprd06.prod.outlook.com>
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=45bda408-e14a-ab39-a2fe-898fe96f5b40@redhat.com \
--to=thuth@redhat.com \
--cc=margaret.mcdonald@hexagon.com \
--cc=mark.fonnemann@hexagon.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.org \
--cc=sw@weilnetz.de \
/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).