[Qemu-devel] Qemu port on Windows to support tun/tap

[Qemu-devel] Qemu port on Windows to support tun/tap

[Ming-Ching Tiew]

[-- Attachment #1.1: Type: text/plain, Size: 433 bytes --]


*please ignore second post if appear twice*

Anyone knows if Qemu port on Windows supports tun/tap virtual
networking ( instead of user-net ) ?

For your information, I downloaded OpenVPN and loaded the
tun/tap driver provided by OpenVPN. I thought since OpenVPN 
could do it with this tun/tap driver, so will Qemu ....

I don't seem to be able to get it working and there is no mention 
it at all in the docs.

Cheers.

[-- Attachment #1.2: Type: text/html, Size: 1390 bytes --]

[-- Attachment #2: InterScan_SafeStamp.txt --]
[-- Type: text/plain, Size: 250 bytes --]

****** Message from InterScan E-Mail VirusWall NT ******

** No virus found in attached file noname.htm
** No virus found in attached file noname.htm

This mail has been scanned by InterScan.
*****************     End of message     ***************

Re: [Qemu-devel] Qemu port on Windows to support tun/tap

[Lars Munch]

On Tue, Dec 28, 2004 at 04:43:14PM +0800, Ming-Ching Tiew wrote:
> 
> *please ignore second post if appear twice*
> 
> Anyone knows if Qemu port on Windows supports tun/tap virtual
> networking ( instead of user-net ) ?
> 
> For your information, I downloaded OpenVPN and loaded the
> tun/tap driver provided by OpenVPN. I thought since OpenVPN 
> could do it with this tun/tap driver, so will Qemu ....
> 
> I don't seem to be able to get it working and there is no mention 
> it at all in the docs.
> 
> Cheers.

A patch for this was posted on the list some time ago:
http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00213.html

-- Lars Munch

Re: [Qemu-devel] Qemu port on Windows to support tun/tap

[Ming-Ching Tiew]

[-- Attachment #1.1: Type: text/plain, Size: 950 bytes --]


>> I don't seem to be able to get it working and there is no mention 
>> it at all in the docs.
>> 
>
>A patch for this was posted on the list some time ago:
>http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00213.html

I downloaded it and compiled it without problem, but it does not seem 
to work. What I did is this, I added one Tap-Win32 V8 adator, configure
an IP to it, then I started two instances of my guest OS which is Linux.
Then I configure them in the same network. Try to ping OS Tap IP
and the other guest OS's IP, none responded to the ping. I started it
this way :-

qemu.exe -L .\bios -nics 1  -tap tap0801 -m 8 -boot a -fda linux.img -enable-audio -localtime

Is the name "tap0801" correct ? 

Furthermore, what if I want to have multiple network cards ? How to
assign which network card connects to which tap device instance ?

Hmmm looks like what I need is a port of vde on Windows ....

Cheers

[-- Attachment #1.2: Type: text/html, Size: 2267 bytes --]

[-- Attachment #2: InterScan_SafeStamp.txt --]
[-- Type: text/plain, Size: 250 bytes --]

****** Message from InterScan E-Mail VirusWall NT ******

** No virus found in attached file noname.htm
** No virus found in attached file noname.htm

This mail has been scanned by InterScan.
*****************     End of message     ***************

Re: [Qemu-devel] Qemu port on Windows to support tun/tap

[Ming-Ching Tiew]

[-- Attachment #1.1: Type: text/plain, Size: 963 bytes --]


> I started it this way :-
>
> qemu.exe -L .\bios -nics 1  -tap tap0801 -m 8 -boot a -fda linux.img -enable-audio -localtime
>
> Is the name "tap0801" correct ? 

OK I got it partially working now. Looks like the name is not the "device driver" name,
but rather, the arbitrary network interface name assigned during the installation,
which is normally it the form of "Local Area Connection x". I renamed and matched it
accordingly, then the above works. I could now ping between the guest OS and
host OS.

But still there are other problems, such as :-

1. If I start up second instance of guest OS, it will not join the network. Looks like
   somewhere there is a limitation on single open.

2. And I can't have multiple network cards within one guest OS using the 
   tap devices. 

Anyway, I view this as the current limitation of the software. Until changes
made to improving it, I will have to live with this limitation.

Cheers.


[-- Attachment #1.2: Type: text/html, Size: 2928 bytes --]

[-- Attachment #2: InterScan_SafeStamp.txt --]
[-- Type: text/plain, Size: 250 bytes --]

****** Message from InterScan E-Mail VirusWall NT ******

** No virus found in attached file noname.htm
** No virus found in attached file noname.htm

This mail has been scanned by InterScan.
*****************     End of message     ***************