Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Duo] bug? mounting CIFS share

  • Thread starter Thread starter keratos
  • Start date Start date
K

keratos

Guest
So, trying to mount a SMB/CIFS share

Cannot mount a share on VU+ Duo running OpenVix appolo 088
smb service is installed, and running.
I can go into Setup->System->Network->Mounts Setup->Network Browser and I can select the server and see the share, correctly tagged CIFS. So i set the user name and password and select FSTAB as mount type. The "green tick" doesnt appear on the share, just the red cross. Not mounted. Bugger!

So, first off, to see if I can mount the share an another box, using my laptop with netrunner installed, I open Dolphin file browser and select Network then Samba shares and I can see the server so I select it then I see the share , select it, username and password dialog popup appears; I enter credentials, logged and and can see and copy files. So, the server is ok. Must be the VU+/Open Vix

So i telnet into the VU+ box and at the command I examine /etc/fstab to see what OpenVix has put into the mount line, here it is:
/192.168.2.1/MOVIE-downloads /media/net/MOVIE cifs user=daz,pass=abc,_netdev,rw,iocharset=utf8 0 0

So at the command line I try
# mount.cifs //192.168.2.1/MOVIE-downloads /media/net/movies -o user=daz,passwd=abc

and I get the error:-
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

password is wrong?? doubt it, I used the same credentials on my netrunner box and it was fine

I went to the samba server and allowed the share to be hosted without password needed; still same result on OpenVix

???
WTF ?
 
Which kernel version do you have there? I have similar problem with VU+ Ultimo and kernel version 3.9.6. With images having kenel 3.1.1 everything is ok.
 
root@vuduo:~# uname -a
Linux vuduo 3.9.6 #1 SMP Mon Nov 17 03:38:59 GMT 2014 mips GNU/Linux


!! a bug then ?? Which latest image has 3.1.1 ?
 
root@vuduo:~# uname -a
Linux vuduo 3.9.6 #1 SMP Mon Nov 17 03:38:59 GMT 2014 mips GNU/Linux


!! a bug then ?? Which latest image has 3.1.1 ?
OpenPLi is still using 3.1.1 in their latest images. OpenATV has also images with 3.1.1 kernel.
 
Surely this has been tested. I mean it is fundemental sharing functions. How come devs missed this one me wonders.

It was all fine on 017 version of openvix but lack of feeds support forced the upgrade.

Thanks for tips.
 
We test as much as we can, but we are limited in manpower/manhours. Being humane beings I'm pretty sure we miss things. And besides: none of us uses CIFS-shares.

Anyway: please check again in build 091 (not available yet), as there has been an update in this area.
 
If you are interested... I will act as tester for shares (nfs,cifs...)..??
 
Just to add I use 3 or 4 Clfs shares on a duo2, solo2 and a solo so this wouldn't appear to be a universal problem.
 
Hi,
I also had this problem with Apollo build 089. In my case problem was solved when I cleaned up manually the auto.network in the /etc catalog, and restarted booth NFS and Samba configuration under Settings/system/network!?!?

now my auto.network looks like this (used to include old settings when trying to get it to work):

# automounter configuration
Film -fstype=cifs,user=sat,pass=sat,rw,iocharset=utf8 ://192.168.7.6/Videos

Hope this might help.
 
Just to add I use 3 or 4 Clfs shares on a duo2, solo2 and a solo so this wouldn't appear to be a universal problem.
Not universal, but with kernel 3.9.6. I have no problem with Duo2/kernel 3.13.5. 3 cifs mounts is ok there.
 
Hi,
I also had this problem with Apollo build 089. In my case problem was solved when I cleaned up manually the auto.network in the /etc catalog, and restarted booth NFS and Samba configuration under Settings/system/network!?!?

now my auto.network looks like this (used to include old settings when trying to get it to work):

# automounter configuration
Film -fstype=cifs,user=sat,pass=sat,rw,iocharset=utf8 ://192.168.7.6/Videos

Hope this might help.

Thanks but this didnt change anything, and I didnt expect it to. This is just a way of accessing SMB share using automounter as apposed to boottime (/etc/fstab) to converve bandwidth. The SMB calls still get routed through the SMB libraries which is where I perceive the problem is ... i.e. the security stack isnt working as credentials are being refused by the SMB client in OpenVix/kernel - yet they work fine on two other boxes.

The fact that other users have no issue is concerning but the simple fix is to go back ot 017 which worked fine !!!!!!!
 
Not universal, but with kernel 3.9.6. I have no problem with Duo2/kernel 3.13.5. 3 cifs mounts is ok there.

kernel 3.15.3 ?? the latest kernel for Apollo on VU+ Duo is 3.9.6 so WTF ? is the kernel part of the boot image or part of OpenVix? I would like a 3.13.5 kernel - are you sure you got this right?
 
kernel on my duo2 is also 3.15.3.Someone with a vu+ duo could say you what actual kernel is in the image.I think kernel is part of the image.
 
Yes, but I am on Duo+ (i.e. twin tuner not quad Duo2) , I'm thus on the "old" model. Openvix for the new model may well be compiled using 3.15.3 but the 3.9 used on apollo 88 on the twin Duo+ seems acient
 
Guys..just to be clear...
The OP was about not being able to mount a windows share on my duo+ over CIFS
 

OpenViX Feeds Status

Back
Top