36 replies to this topic

[Pike_Bishop]

Hi,

 

i have the openpli from date 01.09.2015 installed and i also installed the nfs server plugin

because i have a nfs mount too which is working correct.

 

i have two cifs mounts one of this is to another e2box the et9000 and this mount works also correct

but i have a second cifs mount to a usb stick on a fritzbox (router).

on the fritzbox i have a minidlna server and samba is also running on the fritzbox

but this cifs mount didn't want work in pli

in other images as openatv this cifs mount works correct.

 

 

regards

Biki3

Edited by Biki3, 4 September 2015 - 21:51.

[Pike_Bishop]

Hi,

 

i have flashed now the image from date 21.11.2015, but the problem always exits.

 

regards

Biki3

[WanWizard]

It could be that the Fritz requires old-style authentication, try adding "sec=ntlm" (without the quotes) to the cifs mount options.

[Pike_Bishop]

hi WanWizard,

 

thanks for the tip - i have testet but it didn't help.

i think the problem is in the network search, it is found in pli image a entry with name 192.168.178.1 (FRITZ.BOX_7390)

but if i open this entry therein it didn't found the entry with name MiniDLNA-MEDIEN instead it is only empty.

 

in openatv image however it found this entry as you can see in the following picture;

 network-search.jpg   101.31KB   3 downloads

 

 

regards

Biki3

Edited by Biki3, 23 November 2015 - 14:14.

[WanWizard]

That is not relevant.

 

An OpenPLi image only shows entries for systems you have properly configured. Which means in the same workgroup, and with an SMB master-browser active for that workgroup (by default any server is that). Other images simply sweep the network with a ping and report any responding device back, whether or not it runs an SMB service.

 

So altough it might not pop up in an OpenPLi image due to misconfiguration, it should still connect if you simply make a mount for it.

[Dimitrij]

 

 

 Which means in the same workgroup, and with an SMB master-browser active for that workgroup (by default any server is that). Other images simply sweep the network with a ping and report any responding device back, whether or not it runs an SMB service.

 

 

Are you sure this will work?

e.g. Windows 7

[WanWizard]

Yes, not a problem, see screenshots.

 

But as said, it requires correct configuration: make sure all devices have the same workgroup name configured, and on Windows 7:

- make sure file and printer sharing is enabled at Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings

- make sure in the network adapter settings "file and printer sharing for Microsoft Networks" is enabled.

Attached Files

•  1_0_1_5302_814_2_11A0000_0_0_0.jpg   76.03KB   4 downloads
•  Screenshot from 2015-11-23 14-02-13.png   47.9KB   4 downloads

[Robinson]

I don't want to steal the thread but I will also need some help regarding CIFS on my ET9000.

I would like to stream a movie file from my box but it does not seem to see my Windows 7 machine.

I'm going to check again what WanWizard proposed above (printer sharing etc.) and see if all is set correctly.

What files on ET9000 are to be checked / edited regarding CIFS?

[Pike_Bishop]

hi,

 

it's all in the same workgroup and this cifs mount works correct on PS3, PS4, or X-BOX 360 (Gameconsole) and on a Laptop with Win7.

I didn't know what can i do now so that it works also on the mutant hd 2400 in pli image.

i have also a second cifs mount on the mutant hd 2400 to another e2box hdd (et9000) and this mount works perfect with pli image.

 

 

regards

Biki3

Edited by Biki3, 23 November 2015 - 16:19.

[WanWizard]

What is your definition of "it doesn't work"?

 

So far, we've only established you can't see your Fritzbox in the network browser, but that is just a GUI to facilitate making a mount.

[Pike_Bishop]

hi WanWizard,

 

 

What is your definition of "it doesn't work"?

 

i can't found a directory for this cifs mount in /media/net so i didn't have access to this cifs mount

but i have testet now a little bit more and i can mount it manual with;

mount.cifs //192.168.178.1/MiniDLNA-MEDIEN /media/hdd/movie/_derweil -o guest,iocharset=utf8

i will write a script for temporary solution for now.

 

 

regards

Biki3

Edited by Biki3, 23 November 2015 - 17:30.

[Dimitrij]

Press OK to expand this host

not work(windows7)

[Pike_Bishop]

hi,

 

i didn't need a script it works now correct with a fstab entry as following;

//192.168.178.1/MiniDLNA-MEDIEN	/media/net/MiniDLNAMEDIENFRITZBOX_7390	cifs	guest,rw,iocharset=utf8	0 0

i don't know why, but in pli it didn't want the path;

MiniDLNAMEDIENFRITZBOX_7390

but in openatv this is the correct path.

i think this is the problem why it didn't work in pli because i have testet it to mount manual with;

mount.cifs //192.168.178.1/MiniDLNAMEDIENFRITZBOX_7390/MiniDLNA-MEDIEN /media/net -o guest,rw,iocharset=utf8

that works not, but with;

mount.cifs //192.168.178.1/MiniDLNA-MEDIEN /media/net -o guest,rw,iocharset=utf8

it works.

 

in openatv in the automounts.xml the following works perfect;

<cifs>
 <mount>
  <active>True</active>
  <hdd_replacement>False</hdd_replacement>
  <ip>192.168.178.1</ip>
  <sharename>MiniDLNAMEDIENFRITZBOX_7390</sharename>
  <sharedir>MiniDLNA-MEDIEN</sharedir>
  <options>rw,utf8,sec=ntlm</options>
  <username></username>
  <password></password>
 </mount>
</cifs>

so i think the correct path is;

//192.168.178.1/MiniDLNAMEDIENFRITZBOX_7390/MiniDLNA-MEDIEN

but as i said in pli only works this path;

//192.168.178.1/MiniDLNA-MEDIEN

now  for me it's solved - it works with fstab and that's enough for me because the router (fritzbox) is always on.

i have wrote also the following init script with name fritz_cifs_link.sh,

#!/bin/sh
#
# to make a link from /media/net to /media/autofs
# for cifs mount in pli with fstab so that it is
# in sync with cifs mount in openatv
#
HAUPT_VERZ=/media
CIFS_VERZ=net
CIFS_LINK=autofs
TMP=/tmp
LOGFILE=$TMP/link_cifsdir.log

. /etc/default/rcS


if [ ! -h $HAUPT_VERZ/$CIFS_LINK ]; then
	ln -s $HAUPT_VERZ/$CIFS_VERZ $HAUPT_VERZ/$CIFS_LINK
	
		if [ "$?" = "0" ] ; then
			echo -e "\nLink $HAUPT_VERZ/$CIFS_VERZ zu $HAUPT_VERZ/$CIFS_LINK\nerfolgreich erstellt." > $LOGFILE
		else
			echo -e "\nSORRY !\nLink $HAUPT_VERZ/$CIFS_VERZ zu $HAUPT_VERZ/$CIFS_LINK\nerstellen fehlgeschlagen." > $LOGFILE && exit 1
		fi
fi


: exit 0

and have linked it with S99 in the Starlevel (rcS.d) with;

cd /etc/rcS.d
ln -s ../init.d/fritz_cifs_link.sh S99fritz_cifs_link.sh

so that it is in sync with openatv (they have the cifs and nfs mounts in /media/autofs and not as pli in /media/net)

because i have also a link in /media/hdd/movie as following;

_Freetz-MDLNA_Musik -> /media/autofs/MiniDLNAMEDIENFRITZBOX_7390/MiniDLNA-MEDIEN/Musik

in my other systems with openmultiboot.

now this link works also with pli and i'am satisfied now.

 

thanks for your contributions.

 

 

regards

Biki3

Edited by Biki3, 23 November 2015 - 20:26.

[WanWizard]

That can't be.

 

A share is a share, that is offered by the server side of the connection, in this case your Fritzbox. No way a client can determine on it's own what the name of the share should be.

 

If you issue a 'mount' command in OpenATV, what is actually mounted on /media/net?

[blzr]

in openatv in the automounts.xml the following works perfect;

<cifs>
 <mount>
  <active>True</active>
  <hdd_replacement>False</hdd_replacement>
  <ip>192.168.178.1</ip>
  <sharename>MiniDLNAMEDIENFRITZBOX_7390</sharename>
  <sharedir>MiniDLNA-MEDIEN</sharedir>
  <options>rw,utf8,sec=ntlm</options>
  <username></username>
  <password></password>
 </mount>
</cifs>

so i think the correct path is;

//192.168.178.1/MiniDLNAMEDIENFRITZBOX_7390/MiniDLNA-MEDIEN

but as i said in pli only works this path;

//192.168.178.1/MiniDLNA-MEDIEN

 

no, looking at this xml the correct path is the second one,

'sharename' entry just defines name, under which your share is to be mounted, it has nothing to do with the path to shared folder on the server

and how did look the autmounts.xml after you had added this fritzbox share in mount manager in OpenPLi? it differed from this one from openatv, for whatever reason?

[WanWizard]

It should be exactly the same xml in both images.

 

Only not sure if the "sec=ntlm" option is needed, it depends whether or not the samba version in the Fritz uses ntlm or ntlmv2 (which is the OpenPLi default, not sure what OpenATV's default is), some posts on the web suggest the Fritz requires ntlmv2.

[Pike_Bishop]

hi,

 

 

If you issue a 'mount' command in OpenATV, what is actually mounted on /media/net?

 

openatv mounts to /media/autofs, a mount command says;

root@mutant2400:~# mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=549836k,nr_inodes=78311,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/sda1 on /omb type ext4 (rw,relatime,data=ordered)
ubi0:rootfs on /usr/lib/enigma2/python/Plugins/Extensions/OpenMultiboot type ubifs (r
w,relatime)
tmpfs on /media type tmpfs (rw,relatime,size=64k)
/dev/sda1 on /media/MLB type ext4 (rw,relatime,data=ordered)
/dev/sdc1 on /media/usb2 type ext4 (rw,relatime,data=ordered)
/dev/sdd1 on /media/hdd type ext4 (rw,relatime,data=ordered)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/sdb1 on /media/usb type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,ioc
harset=iso8859-1,shortname=mixed,errors=remount-ro)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
/etc/auto.network on /media/autofs type autofs (rw,relatime,fd=6,pgrp=747,timeout=5,m
inproto=5,maxproto=5,indirect)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
tmpfs on /media/hdd/movie/_sonstige type tmpfs (rw,relatime)

 

and how did look the autmounts.xml after you had added this fritzbox share in mount manager in OpenPLi? it differed from this one from openatv, for whatever reason?

 

in openatv the passage in automounts.xml looks as following;

<autofs>
 <cifs>
  <mount>
   <active>True</active>
   <hdd_replacement>False</hdd_replacement>
   <ip>192.168.178.1</ip>
   <sharename>MiniDLNAMEDIENFRITZBOX_7390</sharename>
   <sharedir>MiniDLNA-MEDIEN</sharedir>
   <options>rw,utf8</options>
   <username></username>
   <password></password>
  </mount>
 </cifs>
</autofs>

and the same passage in the automounts.xml from pli looks as this;

<cifs>
 <mount>
  <active>True</active>
  <hdd_replacement>False</hdd_replacement>
  <ip>192.168.178.1</ip>
  <sharename>MiniDLNAMEDIENFRITZBOX_7390</sharename>
  <sharedir>MiniDLNA-MEDIEN</sharedir>
  <options>rw,utf8</options>
  <username>guest</username>
  <password></password>
 </mount>
</cifs>

for me it looks identical.

 

i didn't need also the option "sec=ntlm" because in fstab with;

//192.168.178.1/MiniDLNA-MEDIEN	/media/net/MiniDLNAMEDIENFRITZBOX_7390	cifs	guest,rw,iocharset=utf8	0 0

it works.

 

 

'sharename' entry just defines name, under which your share is to be mounted, it has nothing to do with the path to shared folder on the server

 yor're right i understand it's only the sharename.

 

and the /etc/auto.network in openatv looks as this;

MiniDLNAMEDIENFRITZBOX_7390 -fstype=cifs,user=,pass=,rw,iocharset=utf8 ://192.168.178.1/MiniDLNA-MEDIEN

regards

Biki3

Edited by Biki3, 24 November 2015 - 15:17.

[WanWizard]

OpenPLI doesn't use autofs, it uses either fstab or automount.xml. And that info looks fine to me.

[Pike_Bishop]

 

OpenPLI doesn't use autofs, it uses either fstab or automount.xml.

 

yes i know, but why my cifs mount doesn't work in pli n the automounts.xml but already with fstab ?

 

regards

Biki3

[WanWizard]

I don't know, this should work fine:

<cifs>
  <mount>
    <active>True</active>
    <hdd_replacement>False</hdd_replacement>
    <ip>192.168.178.1</ip>
    <sharename>MiniDLNAMEDIENFRITZBOX_7390</sharename>
    <sharedir>MiniDLNA-MEDIEN</sharedir>
    <options>rw</options>
    <username>guest</username>
    <password></password>
  </mount>
</cifs>