Re: Queries to understand OpenAFS as a Remote File System

Bharat:

Are you working on OpenAFS or something else?

If you are not working on OpenAFS, this really is not an appropriate
place to ask questions.  If you are working on OpenAFS, it would be
helpful if you described what you were attempting to accomplish so that
I can advise you on how the work should proceed in order for it to be
accepted into the OpenAFS distribution.

Jeffrey Altman
Secure Endpoints Inc.


Bharat Kulkarni wrote:
> 
> Hi,
> 
> As the name suggests the function "smb_ReceiveNegotiate" looks like to
> choose a dialect for communication between SMB client/server.
> From the snippet as follows
> 
> if (strcmp("PC NETWORK PROGRAM 1.0", namep+1) == 0) {
>             coreProtoIndex = tcounter;
>         }   
>         else if (smb_useV3 && strcmp("LM1.2X002", namep+1) == 0) {
>             v3ProtoIndex = tcounter;
>         }
>         else if (smb_useV3 && strcmp("NT LM 0.12", namep+1) == 0) {
>             NTProtoIndex = tcounter;
>         }
>         else if (smb_useV3 && strcmp("SMB 2.001", namep+1) == 0) {
>             VistaProtoIndex = tcounter;
>         }
> 
> Because I have read in CIFS documents that some of the dialects are "PC
> NETWORK PROGRAM 1.0", "MICROSOFT NETWORKS 3.0", "DOS LM1.2X002 ", "DOS
> LANMAN2.1", "Windows for Workgroups 3.1a", "NT LM 0.12".
>  
> So is SMB 2.001 is a new dialect necessary  for VISTA?
> 
> Also could you kindly tell me what is the role of 'kVista_WLA_MAC' and
> 'kWLA_MAC'?
> 
> Thanks and Regards,
> Bharat.
> 
> 
> On 6/6/07, *Jeffrey Altman* < [email protected]
> <mailto:[email protected]>> wrote:
> 
>     The entire SMB/CIFS server is located in the src/WINNT/afs/smb*.[ch]
>     files.  Searching the files for keywords such as "receive", "register",
>     "listen", etc. should point you in the right direction.
> 
>     Jeffrey Altman
>     Secure Endpoints Inc.
> 
> 
>     Bharat Kulkarni wrote:
>     > Hi,
>     >
>     > Thanks for your reply,
>     >
>     > I was going through the OpenAFS code, but I am unable to figure out
>     > where exactly in the code ( which function of )  OpenAFS is receiving
>     > SMB packets from the CIFS client.?
>     >
>     > Is OpenAFS listening on any port ??  relatively I was unable to locate
>     > any listening on ports like 138 or 139.
>     >
>     > Can you kindly help me with these queries.
>     >
>     > Thanks and Regards,
>     > Bharat.
>     >
>     > On 6/4/07, *Jeffrey Altman* <[email protected]
>     <mailto:[email protected]>
>     > <mailto: [email protected]
>     <mailto:[email protected]>>> wrote:
>     >
>     >     OpenAFS is a user mode service that registers its own NetBIOS name.
>     >     It is not a kernel service and is not a Windows remote file system.
>     >     The CIFS client talks to OpenAFS exactly the same way it talks
>     to a
>     >     Windows file share or Samba server.
>     >
>     >     Jeffrey Altman
>     >     Secure Endpoints Inc.
>     >
>     >     Bharat Kulkarni wrote:
>     >     > Hi,
>     >     >
>     >     > Thanks a lot your responses.
>     >     >
>     >     > I have some further queries,
>     >     >
>     >     > Can you kindly tell me, how does the Windows CIFS client using
>     >     SMB, talk
>     >     > to OpenAFS? Have you registered any DLL or is the entry put
>     in the
>     >     > registry. How does OpenAFS accept the SMB packets from
>     Windows and
>     >     carry
>     >     > on further tasks. What role does NetBios play?
>     >     >
>     >     > Does MPR.DLL and MUP.sys come into the picture to make OpenAFS
>     >     work as a
>     >     > n/w redirector when operations are carried out on the drive
>     mapped? As
>     >     > per Vista WDK Docs, MUP.sys is now used even when a mapped
>     drive (Not
>     >     > local) is accessed.. Have you also made OpenAFS changes to work
>     >     > according to Vista guidelines?
>     >     >
>     >     > I also have a query regarding the way in which command prompt
>     >     executes a
>     >     > request as compared to windows explorer. What i mean is, does it
>     >     follow
>     >     > the same path when we access OpenAFS drive using explorer and
>     when we
>     >     > access the drive from command prompt? Is it the code path for
>     both
>     >     ways
>     >     > of accessing the drive? Does MUP.sys play any role in this?
>     Are you
>     >     > registering OpenAFS with MUP.sys to work as per the Vista Docs?
>     >     >
>     >     > Can you also kindly guide me as to how I can further
>     understand the
>     >     > working of OpenAFS in terms of the SMB protocol, and
>     communication
>     >     > between OpenAFS and windows
>     >     >
>     >     > Thanks and Regards,
>     >     > Bharat.
>     >
>     >
> 
>