[Bug 1404278] Re: tap connections not working on windows host

[Varun Chitre]

What was the fix that took place in the mainstream qemu? I'm facing the
same issue on the latest Android Emulator (emulator: Android qemu
version 30.3.5.0 (build_id 7033400) (CL:N/A)) on Windows 10.

TAP network gets attached just fine and shows us as eth1 on guest in
ifconfig. But cannot ping the host. Tried removing the bridge i.e with
just the standalone TAP adapter by assigning 192.168.5.2 to the host-
side adapter and 192.168.5.3 to the guest-side - the guest cannot ping
192.168.5.2.

What was the actual fix? Maybe I can check if the fix got picked up or
not on Google's emulator repo.

-- 
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=tap01 -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 adapter 
(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 default 
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