From: Faisal Al-Humaimidi <1862979@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1862979] [NEW] Cannot Create Socket Networking in Windows Host using Multicast
Date: Wed, 12 Feb 2020 16:23:54 -0000 [thread overview]
Message-ID: <158152463419.28848.6286969532824555776.malonedeb@chaenomeles.canonical.com> (raw)
Public bug reported:
Hello QEMU devs,
I am trying to create a simulated VLAN using socket networking, and the
only way to connect multiple networks in QEMU using socket networking is
by using the multicast `mcast` option of the `socket` network backend.
However, when I try use the following arguments in QEMU to create a
multicast socket network:
`-device e1000,id=sock-0 -netdev id=sock-0,mcast=230.0.0.1:1234`
it fails with:
`can't bind ip address=230.0.0.1: unknown error` in my Windows host.
I would like to know if this is a bug, or if I am missing a prerequisite
before running the QEMU command.
By the way, I am using Windows 10, and running a cross-compiled QEMU
4.2.0.
** Affects: qemu
Importance: Undecided
Status: New
** Description changed:
Hello QEMU devs,
I am trying to create a simulated VLAN using socket networking, and the
only way to connect multiple networks in QEMU using socket networking is
by using the multicast `mcast` option of the `socket` network backend.
However, when I try use the following arguments in QEMU to create a
multicast socket network:
`-device e1000,id=sock-0 -netdev id=sock-0,mcast=230.0.0.1:1234`
it fails with:
`can't bind ip address=230.0.0.1: unknown error` in my Windows host.
I would like to know if this is a bug, or if I am missing a prerequisite
before running the QEMU command.
+
+ By the way, I am using Windows 10.
** Description changed:
Hello QEMU devs,
I am trying to create a simulated VLAN using socket networking, and the
only way to connect multiple networks in QEMU using socket networking is
by using the multicast `mcast` option of the `socket` network backend.
However, when I try use the following arguments in QEMU to create a
multicast socket network:
`-device e1000,id=sock-0 -netdev id=sock-0,mcast=230.0.0.1:1234`
it fails with:
`can't bind ip address=230.0.0.1: unknown error` in my Windows host.
I would like to know if this is a bug, or if I am missing a prerequisite
before running the QEMU command.
- By the way, I am using Windows 10.
+ By the way, I am using Windows 10, and running a cross-compiled QEMU
+ 4.2.0.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1862979
Title:
Cannot Create Socket Networking in Windows Host using Multicast
Status in QEMU:
New
Bug description:
Hello QEMU devs,
I am trying to create a simulated VLAN using socket networking, and
the only way to connect multiple networks in QEMU using socket
networking is by using the multicast `mcast` option of the `socket`
network backend.
However, when I try use the following arguments in QEMU to create a
multicast socket network:
`-device e1000,id=sock-0 -netdev id=sock-0,mcast=230.0.0.1:1234`
it fails with:
`can't bind ip address=230.0.0.1: unknown error` in my Windows host.
I would like to know if this is a bug, or if I am missing a
prerequisite before running the QEMU command.
By the way, I am using Windows 10, and running a cross-compiled QEMU
4.2.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1862979/+subscriptions
next reply other threads:[~2020-02-12 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 16:23 Faisal Al-Humaimidi [this message]
2021-05-05 15:17 ` [Bug 1862979] Re: Cannot Create Socket Networking in Windows Host using Multicast Thomas Huth
2021-07-05 4:17 ` Launchpad Bug Tracker
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=158152463419.28848.6286969532824555776.malonedeb@chaenomeles.canonical.com \
--to=1862979@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.