All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Waldboth <bernd.w@alice.it>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] TAP Win32 broken for newer OpenVPN?
Date: Sat, 12 Nov 2005 21:14:11 +0100	[thread overview]
Message-ID: <43764D13.6030200@alice.it> (raw)

Hello,

i noticed that when I updated the OpenVPN Tap Driver
for Windows with the one coming in OpenVPN version
2.04 or 2.05, the same qemu.exe isn't able to connect
to the tap-device anymore. The old driver works without
problem. I tried it on different machines.
Did anyone else notice the same behaviour?
Maybe for the future someone is able to update the patch?
I looked through the in source of the patch
in hope for an "easy" solution like some naming thing etc.,
but I wasn't able to find anything "obvious".
My concrete problem is that I manually deployed version
2.04 of the OpenVPN Tap-driver on about 30 machines
while I tested only with an older version, and now I
saw that Qemu does not cooperate with that version
anymore. For me it would be much easier and faster to
recompile qemu with a newer patch than to manually
reinstall an older TAP driver, because i can create an
MSI package of Qemu and deploy it via Active Directory.

My configuration:
Win XP Pro SP2 + all updates
Qemu 0.72 + dma + asyncIO + tap-win32

Thanks for your help
Bernd

             reply	other threads:[~2005-11-12 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 20:14 Bernd Waldboth [this message]
2005-11-12 21:46 ` [Qemu-devel] TAP Win32 broken for newer OpenVPN? Dave Feustel
2005-11-13  7:47 ` Kazu
2005-11-15 14:13   ` Bernd Waldboth

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=43764D13.6030200@alice.it \
    --to=bernd.w@alice.it \
    --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.