Am 04.07.22 um 10:12 schrieb Shyam Prasad N:
Looks like some messages were not CCed to the list, apologies. Please find the traces attached.On Fri, Jul 1, 2022 at 2:07 AM Enzo Matsumiya <ematsumiya@xxxxxxx> wrote:On 06/30, Julian Sikorski wrote:Openmediavault 6.0.30 running on top of armbian bullseye. The samba package version is 4.13.13+dfsg-1~deb11u3.[ ... ]16d5d9100927 smb3: use netname when available on secondary channels initally, and reverting it did not help. Reverting ca83f50b43a0 smb3: fix empty netname context on secondary channels makes the mounts work again.It's possible that server is not discarding/ignoring SMB2_NETNAME_NEGOTIATE_CONTEXT_ID negotiate context as it should, and rather treating it as an error. I took a quick look in SLE15-SP3 samba 4.15 code and I didn't spot any obvious mishandling there (it seems it's not supported yet). Also I couldn't reproduce the issue with that server. Maybe it's possible it's a vendor modification? Cheers, EnzoI tried mounting a samba share, and it seems to work fine. From the network capture attached, I see that the netname is not empty, and seems fine. Negotiate Context: SMB2_NETNAME_NEGOTIATE_CONTEXT_ID Type: SMB2_NETNAME_NEGOTIATE_CONTEXT_ID (0x0005) DataLength: 30 Reserved: 00000000 Netname: odroidxu4.local Julian, Will you be able to capture network traces with the two changes reverted? i.e. when it works for you?
Best regards, Julian
Attachment:
trace_reverted.pcap
Description: application/vnd.tcpdump.pcap
