From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ELPzB-0001Sb-Fp for qemu-devel@nongnu.org; Fri, 30 Sep 2005 14:51:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ELPyx-0001LC-VX for qemu-devel@nongnu.org; Fri, 30 Sep 2005 14:51:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ELPyx-0001Iy-BA for qemu-devel@nongnu.org; Fri, 30 Sep 2005 14:51:43 -0400 Received: from [69.17.117.28] (helo=mail26.sea5.speakeasy.net) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1ELPqP-0003cS-N7 for qemu-devel@nongnu.org; Fri, 30 Sep 2005 14:42:53 -0400 Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2]) (jhoger@[64.81.88.222]) (envelope-sender ) by mail26.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Sep 2005 18:27:52 -0000 Subject: Re: [Qemu-devel] about DHCP server in qemu From: "John R. Hogerhuis" In-Reply-To: <20050930131014.GA14173@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> Content-Type: text/plain Date: Fri, 30 Sep 2005 11:28:53 -0700 Message-Id: <1128104933.2390.42.camel@aragorn> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Fri, 2005-09-30 at 09:10 -0400, Jim C. Brown wrote: > On Fri, Sep 30, 2005 at 10:17:04AM +0200, octane indice wrote: > > > I don't see any way for qemu guests to be able to > > > ping each other > > > (for example) if they are both using user-net. > > > > > it would be good to get that working :) > > > > Alas, that is so difficult it is nearly impossible. > Nearly? Oh come on... you know it ain't possible, period. 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. Of course, why ping? If all you need to do is validate connectivity, find some ported protocol service to connect to in order to validate connectivity. If non-ported protocols like ICMP must be supported use tun/tap. -- John.