
:max_bytes(150000):strip_icc()/wireshark-display-filters-59512e443df78cae8136b049.png)
To add on to the question Michael posed, can you explain a little more about why you're trying to find the delay in this network? Are you trying to synchronize the 2 USRP's and that's why you're worried about delay? If we can find out more about why you care about this delay, we may be able to address the root issue rather than just trying to find a workaround for this wireshark issue. You won't be able to get the exact same RF waveform on the receive side simply because of signal degradation. By default Wireshark will use temporary files and memory to capture traffic. Capture file(s): This allows a file to be specified to be used for the packet capture. Filters: Generally, SUSE Support prefers an unfiltered trace. SUSE Support will always want to see full frames. In addition, if you're sending IQ data from one USRP to another, there will be some signal degradation along the way. Limit each packet to: Leave this option unset. It could be that the driver interprets transmit and receive data in different ways so the USRP on the transmit side is seeing a different packet than the USRP on the receive side. On the receive side, the USRP gets some information and gives it to the driver to be interpreted.

The driver on your host computer interprets the information you're trying to send and then tells the USRP to send out that information.

tcp. Excellent You already understand TCP/IP addressing and realize the role that DNS and DHCP servers play on your network. The communication between the USRP and the host computer is not going to be just the data you're trying to send. Note, this filter requires TCP Conversation Timestamps to be calculated. Field name Description Type Versions usb.addr: Source or Destination: Character string: 2.0.0 to 4.0.0: usb. Familiarity with packet structures and typical packet flows Many of you have probably installed and configured TCP/IP networksin fact, I imagine many of you have set up hundreds if not thousands of TCP/IP clients and servers. I think the challenge here is with using wireshark to look at packets of the ethernet connection.
