From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ds7JH-0003FZ-HK for qemu-devel@nongnu.org; Mon, 11 Jul 2005 19:03:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ds7JD-0003Ef-N2 for qemu-devel@nongnu.org; Mon, 11 Jul 2005 19:03:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ds7JD-0003Ea-AN for qemu-devel@nongnu.org; Mon, 11 Jul 2005 19:03:31 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Ds7Od-0000Vj-2f for qemu-devel@nongnu.org; Mon, 11 Jul 2005 19:09:07 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j6BN1NRu010643 for ; Mon, 11 Jul 2005 19:01:23 -0400 (EDT) Date: Mon, 11 Jul 2005 19:01:22 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Connecting vde and LAN Message-ID: <20050711230122.GA9297@jbrown.mylinuxbox.org> References: <42D11415.70106@gmx.de> <20050710173735.GA21204@jbrown.mylinuxbox.org> <20050711023326.GA31625@jbrown.mylinuxbox.org> <20050711150204.GA7933@jbrown.mylinuxbox.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050711150204.GA7933@jbrown.mylinuxbox.org> Reply-To: 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 Mon, Jul 11, 2005 at 11:02:04AM -0400, Jim C. Brown wrote: > > > > b) can't talk to the host itself. This is due to the packets going > > directly to the wire and never really "seen" by the host stack. Not sure > > yet if there is an easy way out, but I suppose it may be possible to set > > up a dummy tap with the same MAC and IP address as the base Ethernet > > device and duplicate broadcasts and packet directed to the host there, > > obviously assuming the administrator does not block this in firewalling.. > > > > Regards > > Henrik > > > > Alas, the accepted solution to allow pcap programs to talk to the host is to > use tuntap to create a tap device and connect the program to the tap device > instead of the real ethernet device. > I tried using libnet 1.0 to send the packets, but that did not help. Also tried libnet 1.1, that actually allowed the host to be pinged by the guest - part of the time. It also caused pings on the same lan (from the guest) to fail as well sometimes, so its not reliable enough to use. I guess we should just do it the hard way - when grabbing packets that are meant for the host, fake the request (fake a ping, manually do the socket call, etc) and send the result back to the vde. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.