From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1404278 <1404278@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1404278] Re: tap connections not working on windows host
Date: Tue, 6 Jan 2015 11:47:59 +0000 [thread overview]
Message-ID: <20150106114759.GD29775@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20150105171150.24809.83960.malone@wampee.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Mon, Jan 05, 2015 at 05:11:50PM -0000, timsoft wrote:
> have used wireshark on host and nothing is coming through when I try to ping the host from the client. (bare with me as I haven't used wireshark before).
> I'm just upgrading the client to slack64 14.1 so I can get wireshark running on it. (process is a little slow, especially with no functioning network on the client). If all goes well, I'll be able to test that by tomorrow (it took about 5hours to install last time). I'll then post back here.
> If there are any specific tests or methods I could follow that would help please let me know.
Please post the following output from the guest:
# ip addr
# ip route
# iptables -L -n
This way we can verify that the guest's network interface is configured,
up, and has no firewall rules that could filter packets.
Please post output from the "ipconfig /all" command on the Windows host.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-06 11:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 15:36 [Qemu-devel] [Bug 1404278] [NEW] tap connections not working on windows host timsoft
2014-12-19 21:09 ` [Qemu-devel] [Bug 1404278] " timsoft
2015-01-02 13:38 ` [Qemu-devel] [Bug 1404278] [NEW] " Stefan Hajnoczi
2015-01-05 17:11 ` [Qemu-devel] [Bug 1404278] " timsoft
2015-01-06 11:47 ` Stefan Hajnoczi [this message]
2015-01-06 21:12 ` timsoft
2015-01-07 9:06 ` Stefan Hajnoczi
2015-01-06 21:30 ` timsoft
2015-01-07 12:51 ` Stefan Hajnoczi
2015-01-07 16:09 ` timsoft
2015-03-24 11:10 ` Stefan Hajnoczi
2015-01-12 3:02 ` Tommy
2015-01-21 21:16 ` neil prideaux
2015-02-07 23:48 ` James J Myers
2018-05-22 13:33 ` Thomas Huth
2018-05-29 14:38 ` timsoft
2018-05-31 7:44 ` timsoft
2018-05-31 7:49 ` timsoft
2018-05-31 11:41 ` Thomas Huth
2018-05-31 11:42 ` Thomas Huth
2018-09-10 15:59 ` Jan Marti
2018-09-10 16:07 ` Jan Marti
2018-09-10 16:54 ` Jan Marti
2018-09-10 17:57 ` Jan Marti
2018-09-11 8:48 ` timsoft
2020-08-02 15:59 ` hakan
2021-02-12 10:51 ` Varun Chitre
2021-02-15 16:41 ` Stefan Hajnoczi
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=20150106114759.GD29775@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=1404278@bugs.launchpad.net \
--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).