From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] Tap and VLAN socket support for win32
Date: Thu, 02 Feb 2006 00:10:36 +0100 [thread overview]
Message-ID: <43E13FEC.7050804@bellard.org> (raw)
In-Reply-To: <000c01c62638$d55e7800$0464a8c0@athlon>
Hi,
I merged your patches and I made important changes to simplify them. I
did not do any tests so tell me if you see problems.
Regards,
Fabrice.
Kazu wrote:
> Hi,
>
> I updated a patch to support tap for win32.
>
> Here is patches and a binary.
> These patches are applied by patch -p1 option. Tap patch can be applied on
> top of VLAN patch. VLAN patch is updated.
> http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060111-vlan.patch
> http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060111-tap.patch
>
> http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-20060111-vlan-tap.zip
>
> Options are:
> -net nic -net tap,ifname=my-tap
> Use ifname to set a name of Tap.
> my-tap is the name of my TAP-Win32 Adapter.
>
> Don't use the same network address as a physical network.
> For example, if the physical network is 192.168.0.x, use different
> network 192.168.10.y for TAP-Win32 Adapter.
>
> For more information,
> http://www.h7.dion.ne.jp/~qemu-win/TapWin32-en.html#vlan
>
> Regards,
> Kazu
>
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
next prev parent reply other threads:[~2006-02-01 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 7:34 [Qemu-devel][PATCH] Tap and VLAN socket support for win32 Kazu
2006-01-31 16:00 ` André Braga
2006-02-01 23:10 ` Fabrice Bellard [this message]
2006-02-02 10:03 ` Kazu
2006-02-04 18:28 ` Fabrice Bellard
2006-02-09 2:29 ` Kazu
2006-02-09 14:00 ` Kazu
2006-02-05 4:05 ` Jim C. Brown
2006-02-07 21:18 ` Jim C. Brown
2006-02-07 21:44 ` Fabrice Bellard
2006-02-08 7:23 ` David Fraser
2006-02-08 7:32 ` M. Warner Losh
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=43E13FEC.7050804@bellard.org \
--to=fabrice@bellard.org \
--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.