qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mattia Gentilini <mg@MG55.HomeIP.NET>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vdq and qemu
Date: Mon, 14 May 2007 14:13:27 +0200	[thread overview]
Message-ID: <46485267.8070703@MG55.HomeIP.NET> (raw)
In-Reply-To: <16250307.53171178802253324.JavaMail.servlet@kundenserver>

adrian.lambeck@basicsedv.de ha scritto:
> My question is if I can also use the wirefilter feature of vde in this context
> without changing vdeq? Does anybody have experience with this ?
As far as I know wirefilter is to be placed into a VDE cable, i.e. in a 
dpipe. So, if you use something like

dpipe <vde_plug_connecting_to_vdeq> = <ssh_or_netcat_or_nothing> 
<remote_vde_plug>

to connect your local vdeq to some local or remote vde_switch, you 
should change it into

dpipe <vde_plug_connecting_to_vdeq> = wirefilter <wirefilter_options> = 
<ssh_or_netcat_or_nothing> <remote_vde_plug>

if you don't use a dpipe, e.g. if you connect vdeq to a vde_switch and 
that switch to a slirpvde, then I think there's no other way that 
running another switch, link the 2 switches using dpipe and wirefilter 
(using the syntax above), and connect one switch to vdeq and the other 
to slirpvde.

-- 
|\/|55: Mattia Gentilini e 55 mila miliardi di armi in meno
|/_| JID MG55@myjabber.net - ICQ #64901700     www.getthunderbird.com
|\/| mg@MG55.HomeIP.NET - http://MG55.HomeIP.NET/  www.getfirefox.com
* Using Mac OS X 10.4.9 powered by Cerebros (Core 2 Duo) *

  reply	other threads:[~2007-05-14 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 13:04 [Qemu-devel] vdq and qemu adrian.lambeck
2007-05-14 12:13 ` Mattia Gentilini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-02  9:41 Adrian Lambeck
2007-06-02 12:16 ` Mattia Gentilini

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=46485267.8070703@MG55.HomeIP.NET \
    --to=mg@mg55.homeip.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).