On Sun, Aug 21, 2011 at 6:53 PM, Dreamcat4 <[email protected]> wrote: > BTW this seems to be a problem of ETHERNET bridging (by inspecting the > mac address on Layer-2 packets) for QEMU. If nobody else has succeeded > at this already, then I will be investigating & report any findings > back here. >
Can't get this approach to work for Mac OS X. Specifying a tap device, (or my disconnected en0) results in mysterious "Bus error". What a shame, how to debug this? janitors-Mac-mini:~ id$ emulator -avd LgRemote -no-boot-anim -shell -qemu -net tap,fd=/dev/tap0 # or en0 Warning: vlan 0 with no nics fCoreAudioDriverUID AppleHDAEngineInput:1B,0,1,0:1 2011-08-23 11:02:06.580 emulator-arm[11954:80b] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz. emulator: emulator window was out of view and was recentred Bus error janitors-Mac-mini:~ id$ echo $? 138 The other way is to get qemu to create the tap0. However the emulator is not up to date with qemu (0.14). Resulting in an unpatched error: janitors-Mac-mini:~ id$ emulator -avd LgRemote -no-boot-anim -shell -qemu -net tap warning: could not open /dev/tap: no virtual network emulation qemu: Could not initialize device 'tap' This is a one-line fix, and is in qemu 0.14 already, but not in the android emulator: https://bugs.launchpad.net/qemu/+bug/647793 What happens with the emulator, how to fix this miniscule little bug? > Plus the host ip and gateway info in the emulator's rc config files needs to > then match the real LAN router / ip gatway device. There is 1 good tutorial > for that on the web. So in theory... > > It would still be nice hear from anyone here who is interested with > multicast DNS / bonjour on the emultor. > > On Sun, Aug 21, 2011 at 1:42 PM, Dreamcat4 <[email protected]> wrote: >> I wish to study a specific multicast DNS app on Android emulator. >> According to other information elsewhere, this fixing mDNS was slated >> for inclusion around Android 2.2. >> >> Recently installed Android 3.2, API 13. Running the emulator with >> default settings gets mixed results. BonjourBrowser app seems to >> detect and list Bonjour services correctly. >> >> However my targeted app fails to work correctly. This may be because >> multicast is not working in the other direction (ie incoming to the >> android device). I am unfamiliar with QEMU networking. However >> Virtualbox and VMWare do have a feature known as Bridged Networking >> (or bridge mode). For guest OS network interfaces. In the Host OS, the >> networking drivers that support Bridge mode requires root permissions >> to be installed. However they allow the Host to route packets directly >> to/from the router. Making the Virtual Machine appear as is it is >> directly connected to the router. I want to try this because it seems >> like the only thing that stands a chance. So thats my problem. >> >> 1) Therefore the REAL question is: How to implement Bridge Networking >> mode for android emulator on QEMU. On a Mac OS X host (and not a linux >> host!?!) ?? >> >> 2) If bridged networking is not the correct solution, then why not? >> And then what would actually be the correct solution? >> >> 3) Would this following method still work in bridge mode, to capture >> multicast DNS packets from within the emulator? >> >> http://stackoverflow.com/questions/2453949/android-emulator-how-to-monitor-network-traffic >> >> >> Any help / guidance appreciated. >> >> dreamcat4 >> [email protected] >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
