Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH 34/71] cifs: Set default Netbios RFC1001 server name to hostname in UNC
Date: Mon, 20 Jan 2025 18:52:18 +0100	[thread overview]
Message-ID: <20250120175218.jyq3iifulujggukp@pali> (raw)
In-Reply-To: <CAH2r5mtOobiuE1v5Qf0JqEg7VttodHJy-95KFOyYHtVsx=bHfA@mail.gmail.com>

On Sunday 19 January 2025 19:38:23 Steve French wrote:
> >Windows SMB servers (including SMB2+) which are working over RFC1001
> >require that Netbios server name specified in RFC1001 Session Request
> >packet is same as the UNC host name. Netbios server name can be already
> >specified manually via -o servern= option.
> >With this change the RFC1001 server name is set automatically by extracting
> >the hostname from the mount source.
> >
> > Signed-off-by: Pali Rohár <pali@kernel.org>
> 
> Pali,
> Is there a good way to simulate this with SMB2.1 or SMB3+ mount to Windows?
> 
> -- 
> Thanks,
> 
> Steve

Sure, it is very easy. Just call standard mount with -o port=139 option.
For example:

mount //hostname/share /mnt/smb -t cifs -o vers=3.1.1,port=139

And you can watch network traffic in wireshark.

Just to note that for SMB 3.1.1 it is currently broken and other patches
in this series are fixing it:
https://lore.kernel.org/linux-cifs/20241222163050.24359-1-pali@kernel.org/t/#u

Your mentioned change "cifs: Set default Netbios RFC1001 server name to
hostname in UNC" is the last one in that patch series.

      reply	other threads:[~2025-01-20 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  1:38 [PATCH 34/71] cifs: Set default Netbios RFC1001 server name to hostname in UNC Steve French
2025-01-20 17:52 ` Pali Rohár [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250120175218.jyq3iifulujggukp@pali \
    --to=pali@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox