samba - May 2022 - Samba video streaming problem

On Tue, May 24, 2022 at 09:03:49PM +0700, Budi Janto
wrote:
>>>The problem is that after 2 hours (average time) the video stream 
>>>is running, my player can't play the video anymore. Can't
seem to
>>>find the video path or maybe it's disconnected from the server 
>>>(Apparently). From log.smbd I try to include some snippets:
>>
>>Can you get a wireshark capture trace between client and
>>server around the disconnection time ? It will be very hard
>>to diagnose this without more data, sorry.
>
>Hi Jeremy,
>
>Can tcpdump be used to replace Wireshark? I've tried with tcpdump, ex:
>
># tcpdump -i re0 net 192.168.0.0/24 and port 445
>
>Unfortunately there is so much data that I don't understand. Would you 
>mind providing a more accurate filter example? -- Thanks
tcpdump is fine. Use a filter between client and server and port 445.
What you have is probably good. You need to look for TCP disconnects/
RST packets around the disconnection times.

On 5/25/22 01:34, Jeremy Allison via samba wrote:
> On Tue, May 24, 2022 at 09:03:49PM +0700, Budi Janto wrote:
>>>> The problem is that after 2 hours (average time) the video
stream is
>>>> running, my player can't play the video anymore. Can't
seem to find
>>>> the video path or maybe it's disconnected from the server 
>>>> (Apparently). From log.smbd I try to include some snippets:
>>>
>>> Can you get a wireshark capture trace between client and
>>> server around the disconnection time ? It will be very hard
>>> to diagnose this without more data, sorry.
>>
>> Hi Jeremy,
>>
>> Can tcpdump be used to replace Wireshark? I've tried with tcpdump,
ex:
>>
>> # tcpdump -i re0 net 192.168.0.0/24 and port 445
>>
>> Unfortunately there is so much data that I don't understand. Would
you
>> mind providing a more accurate filter example? -- Thanks
> 
> tcpdump is fine. Use a filter between client and server and port 445.
> What you have is probably good. You need to look for TCP disconnects/
> RST packets around the disconnection times.
> 
Thanks Jeremy,

I have tried to capture Samba traffic, here is my command that I used:

# tcpdump -i lagg0 -w samba.pcap 'net 192.168.0.0/24 and port 445' and 
'tcp[tcpflags] & (tcp-rst) != 0'

I already attached samba.pcap file in this email. Thanks

-- 
Regards,
Budi Janto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20220525/a987212d/OpenPGP_signature.sig>