search for: connect_close

...pcap to recheck my wireshark/tshark, >> could you please >> share with me ? > Sure: > > https://mprivozn.fedorapeople.org/libvirt.pcap > > $ tshark -r libvirt.pcap libvirt | tail -n1 > 89 29.520014062 ::1 -> ::1 Libvirt 114 Prog=REMOTE > Proc=CONNECT_CLOSE Type=REPLY Serial=32 Status=OK > > So I can get 89 libvirt packets from the dump. > > Michal > > >

Hi Michal, Thank you for your suggestion. My apologies that I took sometime to get back on further confirmation. Regrettably, my tshark is still unable to find libvirt payload inside packet capture, though it lists libvirt as a possible filter. # rpm -ql libvirt-wireshark-1.2.9.3-2.fc21.x86_64 /usr/lib64/wireshark/plugins/1.12.5/libvirt.so As I used wireshark 1.12.6 version, I

...or > expecting ??). If you have sample pcap to recheck my wireshark/tshark, > could you please > share with me ? Sure: https://mprivozn.fedorapeople.org/libvirt.pcap $ tshark -r libvirt.pcap libvirt | tail -n1 89 29.520014062 ::1 -> ::1 Libvirt 114 Prog=REMOTE Proc=CONNECT_CLOSE Type=REPLY Serial=32 Status=OK So I can get 89 libvirt packets from the dump. Michal

..., >>> could you please >>> share with me ? >> Sure: >> >> https://mprivozn.fedorapeople.org/libvirt.pcap >> >> $ tshark -r libvirt.pcap libvirt | tail -n1 >> 89 29.520014062 ::1 -> ::1 Libvirt 114 Prog=REMOTE >> Proc=CONNECT_CLOSE Type=REPLY Serial=32 Status=OK >> >> So I can get 89 libvirt packets from the dump. >> >> Michal >> >> >> >