Debugging with tcpdump

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
(Created page with "For Linux, there's the very useful tcpdump program tcpdump -pa -s0 -w tcpdump-4.cap The command above captures all traffic: * in full length (-s0) * in non-promiscious mode...")
 
Line 14: Line 14:
  
 
'''See also'''
 
'''See also'''
* [[How_To's#Monitoring_and_debugging_Yate|Monitoring and debugginh in Yate]]
+
* [[How_To's#Monitoring_and_debugging_Yate|Monitoring and debugging in Yate]]

Revision as of 14:06, 20 August 2013

For Linux, there's the very useful tcpdump program

tcpdump -pa -s0 -w tcpdump-4.cap

The command above captures all traffic:

  • in full length (-s0)
  • in non-promiscious mode (-p),
  • with adress resolution (-a)
  • to a file by the name of tcpdump-4.cap.

After you've captured enough traffic, generating events like calls or whatever, you can use Wireshark to analyse your traffic.

Wireshark is GPL, like YATE, and it's an amazing product - you actually can listen to the calls you or your customers made; you can see a diagram of the messages sent and so on! It really helps a lot with debugging, and is IMHO easier than messing around with yate -vvvvv

See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers