103 replies to this topic

[SpaceRat]

automounts.xml is E2s way to store what it will add to /etc/fstab and/or /etc/auto.network (the real config files).
If you want to add the mounts yourself, you have to delete /etc/enigma2/automounts.xml, so that E2 doesn't change /etc/fstab and /etc/auto.network anymore (else it would overwrite your individual changes).

Step by step:
init 4
This stops E2 and thus keeps E2 from modifying the real config files.

rm /etc/enigma2/automounts.xml
This deletes E2s config for your network mounts, so that E2 will not modify the real config files when it gets started again.

THEN you can modify/add/remove entries in /etc/fstab and/or /etc/auto.network (Please note that they are different, my examples were for /etc/auto.network).

Once you are done:
shutdown -r now
This reboots your box.

If you have no clue what I'm talking about:
Don't mess around with the config files directly ...

Gesendet von meinem SM-N910F mit Tapatalk

[WanWizard]

edit /etc/auto.network (e.g. using "nano /etc/auto.network")

 

This only works with autofs, which doesn't run on an OpenPLi box unless you manually install it.  I would strongly advice users that don't know exactly what they are doing from editing fstab, a mistake is enough to cause the box to hang at the next boot. 

 

Besides that, it doesn't address the original question.

 

@pluizebol,

 

"soft" and "nolock" are NFS defaults, they can go with CIFS.

 

After you created the mountpoint and saved it, the box will attempt to create the mount. Only if that succeeds, it is saved. So this suggests that it can't make the mount. Can you access the shares from another Windows device, so that you are sure that Windows doesn't block the connection?

[pluizebol]

If you have no clue what I'm talking about:
Don't mess around with the config files directly ...

Gesendet von meinem SM-N910F mit Tapatalk

Hi SpaceRat

 

I try to do it right you know :-)

 

• I do have etc/fstab
• I do NOT have etc/auto.network
• Are init4 / rm / shutdown -r now commands that I can put into Telnet in DCC_E2 (see picture Telnet)

All I want is mapping the HDD of my ET8000 into the File Explorer of Windows 10 Home Edition via SMB 2 or 3 without the need to install SMB 1.

If I am right Windows 10 Home Edition has SMB 2/3 installed and enabled by default.

 

• Can you please write down the text that I should put into the etc/fstab file for my needs as described above ?
• And can you please tell me how to create the missing etc/auto.network file and write down the text that I should put into it for my needs as described above (if needed, because you wrote and/or the 2 filez in your previous post)

 

I would be really VERY grateful 

Attached Files

•  Telnet.jpg   66.06KB   7 downloads

[WanWizard]

Accessing the HDD FROM your Windows PC has absolutely nothing to do with what has been discussed until now?

[pluizebol]

I beg you pardon WanWizard ?

 

I can access the HDD in my ET8000 already, but on condition that I keep SMB1 installed on my Windows 10 PC

Microsoft urges its users to get rid of it because it is much to unsafe.

We should use SMB 2/3 which are both standard available and enabled in Windows 10.

As soon as I uninstall SMB 1 on my PC, the HDD of my ET8000 cannot be mapped in the File Explorer of Windows 10 anymore which is a problem for me and many others.

This is a known problem by many people (also on the PLi and Sat4All forums).

That is why I look for an SNB 2/3 solution in my ET8000 which is apparently SMB 1 and has to become SMB 2/3.

 

May I ask why this has nothing to do with what has been discussed in this thread so far please ?

[mymon]

I can map my Solo4k HDD into Win7/OSX via SMBv2 so it seems to be an issue with the Win10 SMB negotiation

the only way to fin out whats going on is to look into tcpdump/wireshark cap taken from each end during the negotiation

can you share that?

[pluizebol]

I can map my Solo4k HDD into Win7/OSX via SMBv2 so it seems to be an issue with the Win10 SMB negotiation

the only way to fin out whats going on is to look into tcpdump/wireshark cap taken from each end during the negotiation

can you share that?

 

My ET8000 (which is connected to my router with an ethernet cable) disappears from my network in the file-explorer of my Windows 10 Home edition as soon as I uninstall SMB1

My laptop and my notebook  (which are connected to my router via WiFi) remain visible/accessible even if I unistall SMB1

 

I want to understand first why this is happening.

Maybe I really miss the point in setting up the network in my ET8000 which is connected via an ethernet cable to my router (as I said above) since all the other devices work perfectly.

[WanWizard]

I beg you pardon WanWizard ?

 
You wrote:

 

All I want is mapping the HDD of my ET8000 into the File Explorer of Windows 10 Home Edition via SMB 2 or 3 without the need to install SMB 1.

Which I interpret as "I want to connect from my Windows PC to the harddisk in the box, using SMB v2 or higher".

To which my response was that the entire discussion above is about mount options, autofs and fstab, which is about making a connection the other way around ( = from the box to the disk of your PC).
 

I can access the HDD in my ET8000 already, but on condition that I keep SMB1 installed on my Windows 10 PC

 

If you want that, all you need to do it to add

min protocol = SMB2

to the [global] setting of your /etc/samba/smb.conf, and restart samba using

/etc/init.d/samba.sh restart

[pluizebol]

 

If you want that, all you need to do it to add

min protocol = SMB2

to the [global] setting of your /etc/samba/smb.conf, and restart samba using

/etc/init.d/samba.sh restart

 

OK, I tried this before

• Please have a look at my Global Samba settings in the attached picture.(that looks OK doesn't it)
• And also have look at the result of the Telnet command I sent from within DCC_E2 (which doesn't seem to be a success)
  How and where to I have to enter the restart command
  
   

Attached Files

•  Samba global settings.jpg   133.41KB   16 downloads
•  Restart Samba.jpg   72.15KB   6 downloads

Edited by pluizebol, 15 January 2018 - 13:40.

[WanWizard]

Huh?

root@hd2400:~# /etc/init.d/samba.sh status
Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload}

Is samba not installed or did you remove it?

opkg info samba-base

should say

root@hd2400:~# opkg info samba-base 
Package: samba-base
Version: 4.4.5-r0.5
Depends: libbsd0 (>= 0.8.3), libc6 (>= 2.24), libpopt0 (>= 1.16), libsamba-base (>= 4.4.5), libtalloc (>= 2.1.8), libtdb1 (>= 1.3.10), libtevent0 (>= 0.9.29)
Recommends: update-rc.d
Status: install user installed
Section: console/network
Architecture: mips32el
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
MD5Sum: 115fe9cf3fb9a45f6e6612864280bfde
Size: 113146
Filename: samba-base_4.4.5-r0.5_mips32el.ipk
Conffiles:
 /etc/samba/smb.conf 7e9d9cd652fc72e87cf6f59210b17927
Source: samba_4.4.5.bb
Description: samba version 4.4.5-r0  samba version 4.4.5-r0.
Installed-Time: 1514645784

[pluizebol]

 

Huh?

root@hd2400:~# /etc/init.d/samba.sh status
Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload}

Is samba not installed or did you remove it?

opkg info samba-base

should say

root@hd2400:~# opkg info samba-base 
Package: samba-base
Version: 4.4.5-r0.5
Depends: libbsd0 (>= 0.8.3), libc6 (>= 2.24), libpopt0 (>= 1.16), libsamba-base (>= 4.4.5), libtalloc (>= 2.1.8), libtdb1 (>= 1.3.10), libtevent0 (>= 0.9.29)
Recommends: update-rc.d
Status: install user installed
Section: console/network
Architecture: mips32el
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
MD5Sum: 115fe9cf3fb9a45f6e6612864280bfde
Size: 113146
Filename: samba-base_4.4.5-r0.5_mips32el.ipk
Conffiles:
 /etc/samba/smb.conf 7e9d9cd652fc72e87cf6f59210b17927
Source: samba_4.4.5.bb
Description: samba version 4.4.5-r0  samba version 4.4.5-r0.
Installed-Time: 1514645784

 

I honesly never touchedor deleted Samba on my box.

 

This is the result of "opkg info samba-base"

Attached Files

•  Info samba base.jpg   46.35KB   14 downloads

[mymon]

pluizebol beside the SMB on the E2 box can you explain how do you uninstall the SMBv1? AFAIK Microsoft had an update that simply disabled it in the registry so not sure how do you uninstall it and what else gets uninstalled during that process

From my experience with SMB (I've been battling wit it many times) its working fine in 6.1 and the issue seems to be the particular win10 OS

It would be great if you could provide the SMB connection report from PowerShell while you are connected over SMB to the E2 box (when its working)

and wireshark from each end while its not working to look into the negotiations and pushdown messages (if any)

otherwise we can talk about this forever and keep trying different things (which is a hit or miss)

[WanWizard]

@pluizebol,

 

Then you have a serious problem. We are talking OpenPLi 6.1, right? You can install it with

opkg install samba-base

Afaik you don't need to uninstall anything in Windows, you just need to configure that you don't want to make SMBv1 connections. See https://support.micr...-in-windows-and

[pluizebol]

@pluizebol,

 

Then you have a serious problem. We are talking OpenPLi 6.1, right? You can install it with

opkg install samba-base

Afaik you don't need to uninstall anything in Windows, you just need to configure that you don't want to make SMBv1 connections. See https://support.micr...-in-windows-and

 

NO WanWizard I am still on 4 because of the warning on top of the download-site voor ET8000.

 

But then I thought, the heck why not, and I flashed the latest 6.1 (what a mistake)

After zapping I got the screen that I have attached and that the box completely.

 

So PLi 6.x is over and out for me. I am back to PLi 4 until (if ever) there are the needed drivers for the ET8000.

 

But that does not solve my SMB problem and frankly, I am at the point of giving up.

[pluizebol]

pluizebol beside the SMB on the E2 box can you explain how do you uninstall the SMBv1? AFAIK Microsoft had an update that simply disabled it in the registry so not sure how do you uninstall it and what else gets uninstalled during that process

From my experience with SMB (I've been battling wit it many times) its working fine in 6.1 and the issue seems to be the particular win10 OS

It would be great if you could provide the SMB connection report from PowerShell while you are connected over SMB to the E2 box (when its working)

and wireshark from each end while its not working to look into the negotiations and pushdown messages (if any)

otherwise we can talk about this forever and keep trying different things (which is a hit or miss)

MS uninstalled it in the Windows 10 Fall Creator version, but the possibility to re-install it very easily is still there.

Meaning that I re-installed it. That means that I can see and work with my ET8000 (both the Root and the HDD).

But the problem of not being able to do that via SMB 2 or 3 remains of course.

 

Doing tests wth wireshark is in my opinion pointless (I don't have wireshark installed on my PC anyway)

With SMB1 installed we will see that there is indeed comunication.

But as soon as I uninstall SMB1, my box is not here anymore (as if it is not on the network anymore)

Edited by pluizebol, 15 January 2018 - 17:52.

[Jork]

 

If you have no clue what I'm talking about:
Don't mess around with the config files directly ...

Gesendet von meinem SM-N910F mit Tapatalk

Hi SpaceRat

 

I try to do it right you know :-)

 

• I do have etc/fstab
• I do NOT have etc/auto.network
• Are init4 / rm / shutdown -r now commands that I can put into Telnet in DCC_E2 (see picture Telnet)

All I want is mapping the HDD of my ET8000 into the File Explorer of Windows 10 Home Edition via SMB 2 or 3 without the need to install SMB 1.

If I am right Windows 10 Home Edition has SMB 2/3 installed and enabled by default.

 

• Can you please write down the text that I should put into the etc/fstab file for my needs as described above ?
• And can you please tell me how to create the missing etc/auto.network file and write down the text that I should put into it for my needs as described above (if needed, because you wrote and/or the 2 filez in your previous post)

 

I would be really VERY grateful 

 

 

You can't do this "the old way" you can see here:

https://support.micr...er-version-1709

 

Only this works with me with WIN10:

https://www.techrepu...rom-windows-10/

 

If you still try other way it will be disabled in your system by nearby future windows updates.

Gr. Jork

[WanWizard]

NO WanWizard I am still on 4 because of the warning on top of the download-site voor ET8000.

 

In OpenPLi 4 it is

opkg install samba

[pluizebol]

 

NO WanWizard I am still on 4 because of the warning on top of the download-site voor ET8000.

 

In OpenPLi 4 it is

opkg install samba

Hi WanWizard

 

I decided to flach the latest PLi 6.1 on my box in spite of the warning on top of the PLi download-site for ET8000,

My problems were as follows once the flash and reboot were completed:

• TV-Vlaanderen channels were all black (restarting Oscam did not solve this)
• Zapping a bit between the working channels suddenly provided me with the magnificent screen (see attached file) and blocked my box competely.
  Please note that the overscan-screen that I saw passing by during the flash/boot looked perfect with all the arrows pointing to where they should do)
  Please also note that the overscan on my TV set is also disabled

I am back at the latest OpenPLi 4 version now and that will be the case until the right drivers are available.

 

For now I work with the unsafe SMB1 in Windows 10 Home Edition Fall Creator 1709 and I can at least see and work with both the Root and the HDD of my ET8000 Which I have mapped in the File Explorer of Windows.

 

As soon as I uninstall SMB1 in Windows, my box vanishes from my network and the Root & HDD mounts become not accessible.

This is not a problem for Windows 10 because Samba 2 and 3 are installed an enabled by default.

And in samba.conf on my box I added the line "min protocol = smb2"

 

That's the situation and I am afraid that I will have to live with it.

Attached Files

•  20180115_164419.jpg   138.79KB   7 downloads

[pluizebol]

You can't do this "the old way" you can see here:

https://support.micr...er-version-1709

 

Only this works with me with WIN10:

https://www.techrepu...rom-windows-10/

 

If you still try other way it will be disabled in your system by nearby future windows updates.

Gr. Jork

 

I know all this Jork because I work with Windows already since version 3.11 (1994 something)

But none of all the lengty articles give an answer why OpenPli 4 and SMB 2/3 in Windows 10 do not work together.

[WanWizard]

Not sure what OpenPLi 4 uses, but SMB v2 was only introduced in Samba 3.6, so that may be the reason it doesn't work.

 

The "magnified screen" problem is indeed the driver issue, for which we still haven't received any feedback.