[linux-cifs-client] Re: SMB support still missing?
Shirish S Pargaonkar
shirishp at us.ibm.com
Fri Feb 9 05:27:59 GMT 2007
"Christopher R. Hertel" <crh at ubiqx.mn.org> wrote on 02/08/2007 11:17:42 PM:
> Shirish S Pargaonkar wrote:
> >
>
> Below...
>
> >>> 01:39:02.089070 IP 192.168.222.94.2019 > 192.168.222.33.445: S
> >> 870214128:870214128(0) win 5840 <mss 1460,sackOK,timestamp 828349 0,
> >> nop,wscale 1>
> >>> 0x0000: 4500 003c ca4d 4000 4006 329d c0a8 de5e E..<.M at .@.2....^
> >>> 0x0010: c0a8 de21 07e3 01bd 33de 69f0 0000 0000 ...!....3.i.....
> >>> 0x0020: a002 16d0 a82c 0000 0204 05b4 0402 080a .....,..........
> >>> 0x0030: 000c a3bd 0000 0000 0103 0301 ............
> >>> 01:39:02.092572 IP 192.168.222.33.445 > 192.168.222.94.2019: R 0:
> >> 0(0) ack 870214129 win 0
> >>> 0x0000: 4500 0028 f300 0000 8006 09fe c0a8 de21 E..(...........!
> >>> 0x0010: c0a8 de5e 01bd 07e3 0000 0000 33de 69f1 ...^........3.i.
> >>> 0x0020: 5014 0000 ca8f 0000 0000 0000 0000 P.............
> >>> 01:39:02.096738 IP 192.168.222.94.1343 > 192.168.222.33.139: S
> >> 870214131:870214131(0) win 5840 <mss 1460,sackOK,timestamp 828352 0,
> >> nop,wscale 1>
> >>> 0x0000: 4500 003c ca33 4000 4006 32b7 c0a8 de5e E..<.3 at .@.2....^
> >>> 0x0010: c0a8 de21 053f 008b 33de 69f3 0000 0000 ...!.?..3.i.....
> >>> 0x0020: a002 16d0 abfc 0000 0204 05b4 0402 080a ................
> >>> 0x0030: 000c a3c0 0000 0000 0103 0301 ............
> >>> 01:39:02.102544 IP 192.168.222.33.139 > 192.168.222.94.1343: S
> >> 4435509:4435509(0) ack 870214132 win 8760 <mss 1460,nop,nop,sackOK>
> >>> 0x0000: 4500 0030 f400 4000 8006 c8f5 c0a8 de21 E..0.. at ........!
> >>> 0x0010: c0a8 de5e 008b 053f 0043 ae35 33de 69f4 ...^...?.C.53.i.
> >>> 0x0020: 7012 2238 d0f0 0000 0204 05b4 0101 0402 p."8............
> >>> 01:39:02.104880 IP 192.168.222.94.1343 > 192.168.222.33.139: . ack1
win
> > 5840
> >>> 0x0000: 4500 0028 ca34 4000 4006 32ca c0a8 de5e E..(.4 at .@.2....^
> >>> 0x0010: c0a8 de21 053f 008b 33de 69f4 0043 ae36 ...!.?..3.i..C.6
> >>> 0x0020: 5010 16d0 091d 0000 P.......
> >>> 01:39:02.117326 IP 192.168.222.94.1343 > 192.168.222.33.139: P 1:
> >> 73(72) ack 1 win 5840 NBT Session Packet: Session Request
> >>> 0x0000: 4500 0070 ca35 4000 4006 3281 c0a8 de5e E..p.5 at .@.2....^
> >>> 0x0010: c0a8 de21 053f 008b 33de 69f4 0043 ae36 ...!.?..3.i..C.6
> >>> 0x0020: 5018 16d0 3e34 0000 8100 0044 2043 4b46 P...>4.....D.CKF
> >>> 0x0030: 4445 4e45 4346 4445 4646 4346 4745 4646 DENECFDEFFCFGEFF
> >>> 0x0040: 4343 4143 4143 4143 4143 4143 4100 2046 CCACACACACACA..F
> >>> 0x0050: 4445 4c44 4143 4143 4143 4143 4143 4143 DELDACACACACACAC
> >>> 0x0060: 4143 4143 4143 4143 4143 4143 4141 4100 ACACACACACACAAA.
> >>> 01:39:02.121140 IP 192.168.222.33.139 > 192.168.222.94.1343: FP 1:
> >> 6(5) ack 73 win 8688 NBT Session Packet: [|SMB]
> >>> 0x0000: 4500 002d f500 4000 8006 c7f8 c0a8 de21 E..-.. at ........!
> >>> 0x0010: c0a8 de5e 008b 053f 0043 ae36 33de 6a3c ...^...?.C.63.j<
> >>> 0x0020: 5019 21f0 f8a4 0000 8300 0001 8253 P.!..........S
> >>> 01:39:02.162638 IP 192.168.222.94.1343 > 192.168.222.33.139: . ack7
win
> > 5840
> >>> 0x0000: 4500 0028 ca36 4000 4006 32c8 c0a8 de5e E..(.6 at .@.2....^
> >>> 0x0010: c0a8 de21 053f 008b 33de 6a3c 0043 ae3c ...!.?..3.j<.C.<
> >>> 0x0020: 5010 16d0 08cf 0000 P.......
> >>> 01:39:02.173013 IP 192.168.222.94.1343 > 192.168.222.33.139: P 73:
> >> 155(82) ack 7 win 5840 NBT Session Packet: Session Message
> >>> 0x0000: 4500 007a ca37 4000 4006 3275 c0a8 de5e E..z.7 at .@.2u...^
> >>> 0x0010: c0a8 de21 053f 008b 33de 6a3c 0043 ae3c ...!.?..3.j<.C.<
> >>> 0x0020: 5018 16d0 3e3e 0000 0000 004e ff53 4d42 P...>>.....N.SMB
> >>> 0x0030: 7200 0000 0000 0180 0000 0000 0000 0000 r...............
> >>> 0x0040: 0000 0000 0000 950d 0000 0100 002b 0002 .............+..
> >>> 0x0050: 4c4d 312e 3258 3030 3200 024c 414e 4d41 LM1.2X002..LANMA
> >>> 0x0060: 4e32 2e31 0002 4e54 204c 4d20 302e 3132 N2.1..NT.LM.0.12
> >>> 0x0070: 0002 504f 5349 5820 3200 ..POSIX.2.
> >>> 01:39:02.317447 IP 192.168.222.94.1343 > 192.168.222.33.139: R
> >> 155:155(0) ack 7 win 5840
> >>> 0x0000: 4500 0028 ca38 4000 4006 32c6 c0a8 de5e E..(.8 at .@.2....^
> >>> 0x0010: c0a8 de21 053f 008b 33de 6a8e 0043 ae3c ...!.?..3.j..C.<
> >>> 0x0020: 5014 16d0 0879 0000 P....y..
> :
> :
> :
> > Chris,
> >
> > No, clients gives up once the Negative session response with error code
> > 0x82 is received,
> > no negotiate protocol is sent. That is what I see using ethereal.
>
> In the trace above I see the NegProt (the string "SMB" near the beginning
of
> the packet and then the list of dialects later on).
>
> > I compared the two cases using ethereal, in case of successful mount,
the
> > NetBIOS Session Service is 0x82, Positive session response
>
> Yep. See http://www.ubiqx.org/cifs/NetBIOS.html#NBT.6.2
>
> > and in case of failure, it is 0x83 Negative
> > session response with error code 0x82
> > Called name not present
>
> That's what I see in the output above as well.
>
> > if that is what you were looking for in the transactions.
>
> Reading raw tcpdump output isn't my idea of joy and wonderment but it's
> do-able. Now that I have a better idea of what I'm looking for, it's
also
> fairly easy to set up at home.
>
> In the capture I have here, I do see that the CALLED NAME is
"*SMBCLIENT",
> which W98 won't accept. I also see W98 sending the CALLED NAME NOT
PRESENT
> error and the CIFS VFS client continuing with a NegProt despite the
error.
>
> The NegProt is met with a closed connection, as Jan pointed out earlier.
>
> Now... I should point out that I probably don't have the latest version
of
> the CIFS VFS software. It's a SuSE 10.1 install:
>
> $ mount.cifs --version
> mount.cifs version: 1.10-3.0.22-3-SUSE-CODE10
>
> Thanks.
>
> Chris -)-----
>
> --
> "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
> Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
> jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development,
uninq.
> ubiqx Team -- http://www.ubiqx.org/ -)----- crh at ubiqx.mn.org
> OnLineBook -- http://ubiqx.org/cifs/ -)----- crh at ubiqx.org
Chris,
You are right, there is 0x72 going out. I have 1.47 version of cifs.ko
running on a SLES10 2.6.20
kernel.
Regards,
Shirish
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the linux-cifs-client
mailing list