Perhaps the best way would be to set up a very bare VMware environment and only run the emulator in there, at least that way there wouldn't be too much background traffic. I don't think there is any easy way to filter out solely emulator traffic, since it is coming from the same src IP. More info can be found here.įor OS X you can use Charles, it's simple and easy to use.įor more information, please have a look at Android Emulator and Charles Proxy blog post. Note that in my example I'm using Burp, and it is listening port 8080. emulator -http-proxy localhost:8080 -avd android2.2. You can pass -http-proxy flag when starting a new emulator to set proxy (Example burp) to monitor Android traffic.

If you know what tcp port to capture, add a filter at the end to help limit the size of the capture: tcpdump -i -s 0 -w port 80 If unsure, leave off the filter. It is also possible to use http proxy to monitor http requests from emulator. tcpdump -i -s 0 -w -s tell how much of the packet to record.

In both cases you can then analyse the pcap file with tcpdump or Wireshark as normal. Run emulator -tcpdump emulator.cap -avd my_avd to write all the emulator's traffic to a local file on your PC

There are two ways to capture network traffic directly from an Android emulator:Ĭopy and run an ARM-compatible tcpdump binary on the emulator, writing output to the SD card, perhaps (e.g.

Android tcpdump wireshark