73 replies to this topic

[betacentauri]

Maybe add switches for the different methods so that the user only need to check the checkbox and don't have to write it with the remote.

[littlesat]

Sounds like a plan... but what options should we put there?

[betacentauri]

Don't remove the textfield so that the user is still able to add special things.
I guess the 3 from WanWizard mentioned options. But I'm no expert for NAS things.

[littlesat]

But I still think we should consider to change the default...... we should make default what will work for most of the users.... and of course when we change things we should avoid it does break 'older' existing mounts... I'm afraid when we have a free text field a choice box might not work... Then we better could make a choice list with as last option 'free text field'... that adds an extra config where you can put in there what you want....

[WanWizard]

These are the possible options:

• none: attempt to connection as a null user (no name)
• krb5: Use Kerberos version 5 authentication
• krb5i: Use Kerberos authentication and forcibly enable packet signing
• ntlm: Use NTLM password hashing (default)
• ntlmi: Use NTLM password hashing and force packet signing
• ntlmv2: Use NTLMv2 password hashing
• ntlmv2i: Use NTLMv2 password hashing and force packet signing
• ntlmssp: Use NTLMv2 password hashing encapsulated in Raw NTLMSSP message
• ntlmsspi: Use NTLMv2 password hashing encapsulated in Raw NTLMSSP message, and force packet signing

I don't think anyone would want to use "none", and the "i" versions are for specific and explictly configured Windows (server) systems, I've never seen them in the wild, except "ntlmsspi" (in a secure datacenter). 

[littlesat]

And what about the nolock option i saw on that 'work-a-round' ... https://forums.openp...nt/#entry468194

 

"rw, nolock, sec=ntlm"

Edited by littlesat, 7 July 2017 - 16:06.

[WanWizard]

nolock is an NFS mount option, it does not exist for the CIFS kernel driver.

[ims]

I have not any problem with smb ...

 

but one note ... after update to oe6 users in most cases restored settings and with it restored smb.conf too. With old smb.conf and new version samba is not possible connect to box and it's shared disks ... thats all...

[WanWizard]

I thought the issue with smb.conf was long solved?

 

And that it was decided to restore it as a different name or something, as the two are not compatible, and people that have manually updated their smb.conf, can also do that in OpenPLi 6?

 

edit: it does check: https://github.com/O...-restore.sh#L13

[40H3X]

As I suggested earlier, maybe a explicit remark in the Wiki in the options section of the CIFS part https://wiki.openpli.org/MountManager to the https://wiki.openpli...anager_Problems where this problem is explained

[ims]

I thought the issue with smb.conf was long solved?

 

And that it was decided to restore it as a different name or something, as the two are not compatible, and people that have manually updated their smb.conf, can also do that in OpenPLi 6?

 

edit: it does check: https://github.com/O...-restore.sh#L13

on all reflashed boxes I must rebuilded all smb.conf ... all were old...

 

But it is clear ... I must always run restore again, because some ipks removing some configs ...

Edited by ims, 7 July 2017 - 17:26.

[Dream1975]

And then there is also the the SMB version option (if a NAS has SMB1 switched off, which can be expected more and more with the security issues in SMB1, it also won't connect out of the box in mountmanager without manual intervention).

 

Isn't it possible to automate these options in mountmanager?

 

For example when you make a mount in the mountmanager upon finalizing the box tests if it can reach the destination, if not try the alternative authentication and/or smb options untill it finds the configuration that works (and if none work, there is probably a user configuration input mistake and an error can be displayed to check the settings). If this can be build you can also start from the most secure (new) option to old.

Edited by Dream1975, 8 July 2017 - 08:12.

[ims]

btw, for works with NAS is better disable netbios with:

disable netbios = yes

 

without it usually will NAS never sleeps (resp. disks will periodicaly to go sleeps and wakeup)

 

And much better is using "autofs" instead builded mountmanager ...

[nietgiftig]

And much better is using "autofs" instead builded mountmanager ...

 

True !