From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38120) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fOIaw-0000dB-1n for qemu-devel@nongnu.org; Thu, 31 May 2018 04:06:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fOIas-0002NE-22 for qemu-devel@nongnu.org; Thu, 31 May 2018 04:06:02 -0400 Received: from indium.canonical.com ([91.189.90.7]:59502) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fOIar-0002Mb-SM for qemu-devel@nongnu.org; Thu, 31 May 2018 04:05:57 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1fOIaq-0006ay-Pn for ; Thu, 31 May 2018 08:05:56 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id BA05E2E80C7 for ; Thu, 31 May 2018 08:05:56 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 31 May 2018 07:44:45 -0000 From: timsoft Reply-To: Bug 1404278 <1404278@bugs.launchpad.net> Sender: bounces@canonical.com References: <20141219153639.25009.84583.malonedeb@wampee.canonical.com> Message-Id: <152775268558.31866.5690330576248667738.malone@soybean.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1404278] Re: tap connections not working on windows host List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org it is working now. using the following config. "c:\program files\qemu\qemu-system-i386.exe" -cpu qemu32 -m 3G -drive file= =3D"c:\\data\\images\\slack14.2_32bit_base.qcow2",format=3Dqcow2 -cdrom "c:= \\data\\images\\slackware-14.2-install-dvd.iso" -boot c -net nic,macaddr=3D= 02:00:00:11:11:14,model=3Di82551 -net tap,ifname=3Dtap0 -k en-gb -display v= nc=3D:2 -monitor telnet:localhost:7101,server,nowait,nodelay which I took from a linux qemu vm of mine, and just modified the bridge to = point to tap (it didn't like -net bridge,br=3Dbr0 (where br0 was my windows= bridge - I guess there is no bridge helper on windows qemu - so I changed = it to -net tap,ifname=3Dtap0 (which was already configured as part of the b= ridge) I was able to ping the lan and also the wan (internet) so it looks ok now. = This time i did specify a different virtual net card which may have made a = difference, but if it works, that is the main thing. ** Changed in: qemu Status: Incomplete =3D> Fix Released -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1404278 Title: tap connections not working on windows host Status in QEMU: Fix Released Bug description: using latest qemu 2.2.0 64bit for windows host (installed from qemu-w64-setup-20141210.exe obtained from http://qemu.weilnetz.de/w64/ ),OpenVPN 2.6.3-I601 64bit tap adapter named tap01 and calling qemu using the following. qemu-system-x86_64.exe -m 512 -net nic -net tap,ifname=3Dtap01 -hda "c:\\data\\images\\test.img" where the image contains a slackware 14.0 64bit install. The tap is bridged with the real network adapter and the bridge is given = an ip of 10.1.1.41 (which works as the ip for the windows host). The tap ad= apter (in network connections) shows connected when the qemu vm is running.= inside the vm, the network is given an ip of 10.1.1.143 (the netmask and d= efault gateway are the same for the virtual and real pc). fault. The vm cannot see the rest of the local network or visa-versa. This used = to work in early (0.9 32bit) versions of qemu. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1404278/+subscriptions