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. _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
