Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI was trying to see the network traffic through wireshark and was following [this](http://mobile.tutsplus.com/tutorials/android/analyzing-android-network-traffic/) post, which uses `adb forward tcp:12345 tcp:54321` command . But I got stuck as I could not find out the android phone port number(and I could be wrong here as I am new to this stuff). Is there any other way of analysing http traffic in android. I've also tried [this](http://www.cantoni.org/2011/06/28/debug-http-android-fiddler) but couldnt get it working. Any help is appreciated. Thanks.
      singulars
    2. COThere are many steps and options in that post. Firstly if you are trying the final option of piping directly to wireshark then you need to have followed the preceding steps. There is no "Android port" to be found you are specifying all the ports in the command-line, you get to choose. What is happening is that in option 1, the tcpdump captures to a file. in option 2 they tell you how to divert the tcpdump output to netcat (nc) which publishes it on a port that you specify (12345) in their example.
      singulars
    3. COIn option 3, they use adb to capture all the traffic on the port that you were diverting the output to (12345) and republish it to port 54321 (again you can change this) on the localhost (the machine you are running the adb session on) they then show you how to capture this in wireshark by using netcat on the localhost to republish so that wioreshark can capture it. If all of this is alien I would start with the simple option to capture to file on the handset and then pull the file back and load it in manually.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload