Actions

VoIP Ethernet Capture FreeSBC A: Difference between revisions

(creation)
 
(Fixed issues with this procedure, was not precise enough, was pointing to tbx_cli_remote which does not exist (it's tbx_cli_tools_remote!!!))
Line 5: Line 5:
== Capturing Ethernet traffic ==
== Capturing Ethernet traffic ==


* Start tbx_cli_remote
* Connect to the FreeSBC using a ssh connection
* Start tbx_cli_tools_remote (type "tbx_cli_tools_remote")
* Connect to the tbrouter application
* Connect to the tbrouter application
* Start capture using the 'p' key (small letter)
* Start capture using the 'p' key (lowercase p), leave default parameters and press 'enter'
* Stop capture using the 'P' key (capital letter)
* Stop capture using the 'P' key (uppercase P)


== Retrieve Ethernet capture ==
== Retrieve Ethernet captures ==
The capture packets are locate here:
Ethernet capture files (pcap/Wireshark compatible) are locate here:
   /lib/tb/toolpack/tbrouter/pcap
   /lib/tb/toolpack/tbrouter/pcap
'''Note''': There can be multiple capture files per capture session (for example, on systems with 10Gbps network devices, because Ethernet packets on these devices are spread to multiple packets processing/capture cores)

Revision as of 09:23, 22 March 2018

Applies to version(s): v3.0

Capturing Ethernet traffic

  • Connect to the FreeSBC using a ssh connection
  • Start tbx_cli_tools_remote (type "tbx_cli_tools_remote")
  • Connect to the tbrouter application
  • Start capture using the 'p' key (lowercase p), leave default parameters and press 'enter'
  • Stop capture using the 'P' key (uppercase P)

Retrieve Ethernet captures

Ethernet capture files (pcap/Wireshark compatible) are locate here:

 /lib/tb/toolpack/tbrouter/pcap

Note: There can be multiple capture files per capture session (for example, on systems with 10Gbps network devices, because Ethernet packets on these devices are spread to multiple packets processing/capture cores)