From: "Jim C. Brown" <jma5@umd.edu>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] about DHCP server in qemu
Date: Fri, 30 Sep 2005 17:59:38 -0400 [thread overview]
Message-ID: <20050930215938.GA20094@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1128104933.2390.42.camel@aragorn>
On Fri, Sep 30, 2005 at 11:28:53AM -0700, John R. Hogerhuis wrote:
> Nearly? Oh come on... you know it ain't possible, period.
>
What are you refering to? The ability of a single qemu to ping thru slirp,
or the ability of multiple qemus to ping each other using their guest ips?
The former can be done, as explained below, but it is probably more trouble
than its worth. The latter can not be done at all *IF* the guests have to
communicate thru the slirp layer. However, if the slirp layer is just used to
talk to the host and the LAN/internet and you have something else that deals
with guest-to-guest, then this can be done. slirpvde comes to mind here.
> Ping (ICMP) operates at the IP level. An unprivileged socket, which is
> what user-net (slirp) uses can only send/receive packets at the ported
> protocols level, which means UDP or TCP.
>
Actually, it is really easy to add ping support to qemu using sockets. The only
issue here is privilege. (You need to be root in order to be able to use an
ICMP socket.)
An alternative would be to use "/sbin/ping -c 1" and parse its output in order
to simulate an actual ICMP connection. This is considerably harder, but definitely
possible.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-09-30 22:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 15:00 [Qemu-devel] about DHCP server in qemu octane indice
2005-09-29 20:34 ` Jim C. Brown
2005-09-29 21:50 ` Brad Campbell
2005-09-29 22:14 ` Jim C. Brown
2005-09-30 8:17 ` octane indice
2005-09-30 12:21 ` Oliver Gerlich
2005-09-30 13:10 ` Jim C. Brown
2005-09-30 14:51 ` octane indice
2005-10-01 21:17 ` Jim C. Brown
2005-10-02 2:39 ` Henrik Nordstrom
2005-10-02 19:23 ` Jim C. Brown
2005-10-03 11:34 ` octane indice
2005-09-30 18:28 ` John R. Hogerhuis
2005-09-30 21:37 ` Henrik Nordstrom
2005-09-30 21:59 ` Jim C. Brown [this message]
2005-10-03 15:55 ` octane indice
2005-10-03 18:12 ` Henrik Nordstrom
2005-10-03 19:20 ` Christian MICHON
2005-10-03 20:37 ` Henrik Nordstrom
2005-10-04 7:47 ` Christian MICHON
2005-10-04 11:43 ` Jim C. Brown
2005-10-05 9:38 ` Henrik Nordstrom
2005-10-03 21:31 ` Jim C. Brown
2005-10-04 4:19 ` octane indice
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=20050930215938.GA20094@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=jhoger@pobox.com \
--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).