From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ELT3j-0001mg-6X for qemu-devel@nongnu.org; Fri, 30 Sep 2005 18:08:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ELT3a-0001fy-Au for qemu-devel@nongnu.org; Fri, 30 Sep 2005 18:08:47 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ELT3Z-0001aE-KA for qemu-devel@nongnu.org; Fri, 30 Sep 2005 18:08:41 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ELSur-00060f-PY for qemu-devel@nongnu.org; Fri, 30 Sep 2005 17:59:41 -0400 Date: Fri, 30 Sep 2005 17:59:38 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] about DHCP server in qemu Message-ID: <20050930215938.GA20094@jbrown.mylinuxbox.org> References: <1128006042.433c019a295a8@webmail.alinto.com> <20050929203431.GA4684@jbrown.mylinuxbox.org> <433C61B7.6070804@wasp.net.au> <20050929221406.GA6019@jbrown.mylinuxbox.org> <1128068224.433cf48005ab5@webmail.alinto.com> <20050930131014.GA14173@jbrown.mylinuxbox.org> <1128104933.2390.42.camel@aragorn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1128104933.2390.42.camel@aragorn> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: jhoger@pobox.com, qemu-devel@nongnu.org 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.