37 replies to this topic

[rawig]

I have a Xtrend ET4000 and an ET9500 STB. Both are running OpenPLI 4 and I have updated the software a few days before. 

 

The ET9500 is the main STB. I have added a networkshare from my Windows server to be used as a harddrive in the STB. This works perfect.

 

The ET4000 uses the ET9500 as partnerbox. This works fine as well. But adding the networkshare to the ET4000 doesn't work. The  smal icon in the list of networkshares has a little red X. The share is not available and selectable in the recording-path and also not in the filelist.

 

What is going wrong?

[velik]

I can confirm for kernel 3.9.6 (DUO, UNO)

cifs share still not working (Image from 5.01).

 

Networkshare from UNO to the DUO (and from DUO to the UNO) doesn't work.

But, networkshare is working normally from UNO (or DUO) to the other devices (PC, mediaplayer DUNE) 

[Erik Slagter]

It has probably to do with security options. There have a some changes in the linux kernel in this area. If you type cat /proc/filesystems you'll see cifs is really there.

[velik]

cat /proc/filesystems  for UNO (kernel 3.1.1) - networkshare from UNO to the DUO is working: 

 

vuuno login: root

root@vuuno:~# cat /proc/filesystems

nodev   sysfs

nodev   rootfs

nodev   bdev

nodev   proc

nodev   tmpfs

nodev   devtmpfs

nodev   sockfs

nodev   usbfs

nodev   pipefs

nodev   anon_inodefs

nodev   rpc_pipefs

nodev   devpts

        ext4

nodev   ramfs

        vfat

        msdos

        iso9660

        hfsplus

        hfs

nodev   nfs

nodev   nfs4

nodev   cifs

nodev   autofs

nodev   fuse

        fuseblk

nodev   fusectl

        udf

nodev   mtd_inodefs

nodev   ubifs

 

root@vuuno:~#

 

cat /proc/filesystems  for UNO (kernel 3.9.6) - networkshare from UNO to the DUO is not working:

vuuno login: root

root@vuuno:~# cat /proc/filesystems

nodev   sysfs

nodev   rootfs

nodev   bdev

nodev   proc

nodev   tmpfs

nodev   devtmpfs

nodev   sockfs

nodev   pipefs

nodev   anon_inodefs

nodev   rpc_pipefs

nodev   devpts

        ext3

        ext2

        ext4

nodev   ramfs

        vfat

nodev   nfs

nodev   nfs4

nodev   cifs

nodev   autofs

        fuseblk

nodev   fuse

nodev   fusectl

nodev   mtd_inodefs

nodev   ubifs

root@vuuno:~#

[WanWizard]

As you see, cifs is present in both cases.

 

That is not the issue, as Erik already mentioned the default authentication mechanism has changed in this version.

 

For some target systems you need to downgrade it. On the commandline you do that by adding "sec=ntlm" to the mount options, and you will see it works. It will probably also work if you add this to an fstab entry.

The mountmanager gui however does not have the option to enter this, and probably also not to execute it.

 

So as a workaround mount manually on the commandline (and don't reboot your box) or use an fstab entry instead of the mount manager (assuming this will work too).

[velik]

Thank you, I read about it  http://forums.openpl...e-2#entry466557 

Manually mounting is working. But, I would like to do it from  gui ...

[WanWizard]

We know that. But it hasn't been picked up yet.

[athoik]

Maybe this works (didn't test it..)

Subject: [PATCH] networkbrowser: use rw,nolock,sec=ntlm as cifs defaults
 mount options

http://forums.openpli.org/topic/36360-vu-duo-update/page-2#entry466557

diff --git a/networkbrowser/src/AutoMount.py b/networkbrowser/src/AutoMount.py
index f6f7830..27a38ec 100644
--- a/networkbrowser/src/AutoMount.py
+++ b/networkbrowser/src/AutoMount.py
@@ -84,7 +84,7 @@ class AutoMount():
 					data['ip'] = getValue(mount.findall("ip"), "192.168.0.0").encode("UTF-8")
 					data['sharedir'] = getValue(mount.findall("sharedir"), "/exports/").encode("UTF-8")
 					data['sharename'] = getValue(mount.findall("sharename"), "MEDIA").encode("UTF-8")
-					data['options'] = getValue(mount.findall("options"), "rw,nolock").encode("UTF-8")
+					data['options'] = getValue(mount.findall("options"), "rw,nolock,sec=ntlm").encode("UTF-8")
 					data['username'] = getValue(mount.findall("username"), "guest").encode("UTF-8")
 					data['password'] = getValue(mount.findall("password"), "").encode("UTF-8")
 					self.automounts[data['sharename']] = data
diff --git a/networkbrowser/src/MountEdit.py b/networkbrowser/src/MountEdit.py
index eeba2c4..fc4fead 100644
--- a/networkbrowser/src/MountEdit.py
+++ b/networkbrowser/src/MountEdit.py
@@ -150,6 +150,8 @@ class AutoMountEdit(Screen, ConfigListScreen):
                         sharedir = "/export/hdd"
                 if mounttype == "nfs":
                         defaultOptions = "rw,nolock,soft"
+                elif mounttype == "cifs":
+                        defaultOptions = "rw,nolock,sec=ntlm"
                 else:
                         defaultOptions = "rw"
                 if username is False:
@@ -185,7 +187,7 @@ class AutoMountEdit(Screen, ConfigListScreen):
                 self.list.append(self.hdd_replacementEntry)
                 if self.optionsConfigEntry.value == self.optionsConfigEntry.default:
                         if self.mounttypeConfigEntry.value == "cifs":
-                                self.optionsConfigEntry = NoSave(ConfigText(default = "rw", visible_width = 50, fixed_size = False))
+                                self.optionsConfigEntry = NoSave(ConfigText(default = "rw,nolock,sec=ntlm", visible_width = 50, fixed_size = False))
                         else:
                                 self.optionsConfigEntry = NoSave(ConfigText(default = "rw,nolock,soft", visible_width = 50, fixed_size = False))
                 self.optionsEntry = getConfigListEntry(_("Mount options"), self.optionsConfigEntry)
diff --git a/networkbrowser/src/NetworkBrowser.py b/networkbrowser/src/NetworkBrowser.py
index ae12503..f1225d0 100644
--- a/networkbrowser/src/NetworkBrowser.py
+++ b/networkbrowser/src/NetworkBrowser.py
@@ -454,7 +454,7 @@ class NetworkBrowser(Screen):
 				data['ip'] = selection[2]
 				data['sharename'] = selection[3] + "@" + selection[1]
 				data['sharedir'] = selection[3]
-				data['options'] = "rw"
+				data['options'] = "rw,nolock,sec=ntlm"
 				self.sharecache_file = None
 				self.sharecache_file = '/etc/enigma2/' + selection[1].strip() + '.cache' #Path to cache directory
 				if os_path.exists(self.sharecache_file):
-- 

Attached Files

•  0001-networkbrowser-use-rw-nolock-sec-ntlm-as-cifs-defaul.patch   3.23KB   25 downloads

[Erik Slagter]

It TS can test this and it works OK, I will apply it. I don't have a cifs server here.

[tappari]

I have two old nas drives both needing cifs mount: Buffalo Link Station and D-Link DNS-323 2TB.

VU+ Duo2 /kernel 3.13.5 mounts with networkbrowser both of these without any problem. But VU+ ultimo /kernel 3.9.6 refuses to mount DNS-323.No problem with Link Station.

So, obviously kernel 3.9.6 has some problem compared to kernel 3.13.5. 

[WanWizard]

That patch now always changes the options to include "sec=ntlm" ? That should be user selectable, as some backends need that, others don't.

 

Also, I don't have an Ultimo, but is 3.9.6 the current kernel version for that box? Or is that an old image?

[athoik]

But it is user configurable!

 

 

PS. Maybe /export/ should be /media/ ?

Attached Files

•  mounts_editor.jpg   50.79KB   11 downloads

Edited by athoik, 8 January 2015 - 09:54.

[Erik Slagter]

Yes, I think it's a good approach this way. Only users that have problems can revert it to default again. The only thing is, I guess this only works for new shares?

 

And indeed that should be /media/ imho.

Edited by Erik Slagter, 8 January 2015 - 09:58.

[tappari]

That patch now always changes the options to include "sec=ntlm" ? That should be user selectable, as some backends need that, others don't.

 

Also, I don't have an Ultimo, but is 3.9.6 the current kernel version for that box? Or is that an old image?

Yes, current version for Ultimo is 3.9.6. Earlier was 3.1.1 without any problems with cifs mounts. My image is fresh flashed PLi 06.01.2015 without any restores. 

[WanWizard]

But it is user configurable!

 

Sorry, I didn't know, I never use it.

 

But if this is the case, wny does everyone moan about it? They can just add the "sec=ntlm" to the options if needed, problem solved?

[athoik]

 

But it is user configurable!

 

Sorry, I didn't know, I never use it.

 

But if this is the case, wny does everyone moan about it? They can just add the "sec=ntlm" to the options if needed, problem solved?

 

 

I don't use it either.

 

Either users make mounts using other plugin or they are too lazy (or blind...).

[tappari]

 

 

But it is user configurable!

 

Sorry, I didn't know, I never use it.

 

But if this is the case, wny does everyone moan about it? They can just add the "sec=ntlm" to the options if needed, problem solved?

 

 

I don't use it either.

 

Either users make mounts using other plugin or they are too lazy (or blind...).

 

Please remember that not all users are familiar with Linux commands. Normal user is trying to do the mounts with NetworkBrowser trusting it can do the job automatically.

[WanWizard]

Unfortunately the world doesn't work that way.

 

Perhaps it's an option to do this at runtime? i.e. have the mount manager attempt to create the cifs mount, and if it fails, retry with "sec=ntlm" added to the options if not present?

[tappari]

As a normal user, I still cannot understand the behaviour between Duo2/kernel 3.13.5 and Ultimo/kernel 3.9.6. From my poin of wiev they should bahave simirarly.

[velik]

Unfortunately the world doesn't work that way.

 

Perhaps it's an option to do this at runtime? i.e. have the mount manager attempt to create the cifs mount, and if it fails, retry with "sec=ntlm" added to the options if not present?

Yes, after adding "sec=ntlm" in Mount optiions of the GUI Mounts editor, networkshare from UNO to the DUO is working. After full reboot automatically mounting is resumeed. Thanks very much, perhaps it's most simply solution.

Edited by velik, 8 January 2015 - 13:01.