Wireshark [RTC] arrested transmission network interfaces, tcp rivalry!

Before ordination

  Pick up a new requirement, did not expect to skip the server end interface, go --signal signaling communication network transmission. Mobile terminal to communicate with the server, transmission request response back. No way, Charles and console are used to, the need to learn sooner or later.

  Premise phone to connect to the Mac, and I always thought Charles, like mobile phones and computers holding the same WI-FI can result around in a circle, did not succeed.

  Reference Links: https://www.jianshu.com/p/c67baf5fce6d

practice

  •  Before operating the terminal:

  ~ ifconfig -l

lo0 gif0 stf0 XHC0 XHC20 en0 p2p0 awdl0 en1 en2 bridge0 utun0 utun1 utun2

 

  •  Create a virtual network card

(1) get the phone UIDD:

Method a: Get used iTools;

Method two: not connected to the computer by obtaining dandelion: https://www.pgyer.com/tools/udid

 

 

 (2) to the mobile terminal maps a virtual network card :( I kind of do not like, did not directly execute even cell phones)

  ~ rvictl -s c88823a4a8969b488418c80f68e2bbf6c6deea89

  ~ 

  • After the operation of the terminal

  ~ ifconfig -l

lo0 gif0 stf0 XHC0 XHC20 en0 p2p0 awdl0 en1 en2 bridge0 utun0 utun1 utun2 rvi0

 

  • After selecting rvi0 newly added into the Wireshark page, start listening

 

 

Explanation

Simple addPeer, removePeer, signal to the communication center

 

Extension 

TCP three-way handshake

data monitoring

 

Guess you like

Origin www.cnblogs.com/darlingmz/p/12329194.html