All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Connecting vde and LAN
Date: Mon, 11 Jul 2005 19:01:22 -0400	[thread overview]
Message-ID: <20050711230122.GA9297@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20050711150204.GA7933@jbrown.mylinuxbox.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.

  reply	other threads:[~2005-07-11 23:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 12:27 [Qemu-devel] Connecting vde and LAN Oliver Gerlich
2005-07-10 16:42 ` Henrik Nordstrom
2005-07-10 17:37   ` Jim C. Brown
2005-07-10 18:23     ` Oliver Gerlich
2005-07-10 18:58       ` Jim C. Brown
2005-07-11  2:21     ` Henrik Nordstrom
2005-07-11  2:33       ` Jim C. Brown
2005-07-11  7:50         ` Henrik Nordstrom
2005-07-11 15:02           ` Jim C. Brown
2005-07-11 23:01             ` Jim C. Brown [this message]
2005-07-12  2:49               ` Henrik Nordstrom
2005-07-12 22:25                 ` Jim C. Brown
2005-08-04 10:14                   ` Henrik Nordstrom
2005-08-05 16:54                     ` Jim C. Brown
2005-08-10 19:07                     ` Jim C. Brown
2005-08-11 14:56                       ` Henrik Nordstrom
2005-08-11 16:24                         ` Oliver Gerlich
2005-08-11 16:56                           ` Jim C. Brown
2005-08-12 10:02                             ` Henrik Nordstrom
2005-08-12 18:07                               ` Jim C. Brown
2005-08-11 17:00                           ` Paul Brook
2005-08-12  0:11                             ` Herbert Poetzl
2005-08-12  9:53                           ` Henrik Nordstrom
2005-07-10 17:48   ` Oliver Gerlich
2005-07-11  1:36     ` Henrik Nordstrom
2005-07-12 19:43     ` Ross Kendall Axe
2005-07-12 20:31       ` Oliver Gerlich
2005-07-13  3:02         ` Ross Kendall Axe
2005-07-10 18:27   ` Bakul Shah

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=20050711230122.GA9297@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.