103 replies to this topic

[SpaceRat]

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.

Indeed ...
... OpenPLi closed my pull request for Samba 3.6.xx and left OpenPLi 4.0 with Samba 3.0.xx, which only supports SMBv1.

[pluizebol]

Meaning that there is no solution for some people like me with an ET8000 

 

• OpenPLi does not want to put Samba 3.6 in version 4 which forces me to use the dangerous SMB1
   
• They want me to adopt version 6.1 instead which blocks my box all the time due to this screen (I have tested it the other day)

 

Thanks a lot OpenPLi for the 2 excelent choises you give us.

 

 

Attached Files

•  PLi-6.x overscan problem.jpg   138.79KB   3 downloads

[catastrofus]

In my case, that magnified screen will disappear after a reboot and will not reappear after an update or switching off the stb and starting it again.

Edited by catastrofus, 16 January 2018 - 22:04.

[WanWizard]

Either way, don't blame us for this issue.

 

Xtrend doesn't want to update their BSP, while appearently new drivers exist AND Xtrend has these drivers. So it's Xtrend who doesn't care about its users.

 

OpenPLi 4 is EoL, and will be taken offline when OpenPLi 7 is released. If by then Xtrend hasn't fixed this issue, we have no option but to drop support for the 2gen Xtrends. Which as an ET10000 owner I'm not too pleased about either.

[pluizebol]

I agree that OpenPLi can't fix the problem with the drivers that they don't get.

 

But they could help the users out of there SMB1 misery by putting Samba 6.3 in OpenPLI 4 instead of Samba 3.0.

[Jork]

How about using alternatives; like Openhdf ?

They still have available online 5.5 version with SMB2.0 server support.

You still have to test if it contains the magnifying issue.

 

 

Gr. Jork

[pluizebol]

Or OpenVix ?

[WanWizard]

I agree that OpenPLi can't fix the problem with the drivers that they don't get.

 

But they could help the users out of there SMB1 misery by putting Samba 6.3 in OpenPLI 4 instead of Samba 3.0.

 

As I understand it was rejected, but I don't know by whom or why, so that needs to be looked at.

[pluizebol]

 

I agree that OpenPLi can't fix the problem with the drivers that they don't get.

 

But they could help the users out of there SMB1 misery by putting Samba 6.3 in OpenPLI 4 instead of Samba 3.0.

 

As I understand it was rejected, but I don't know by whom or why, so that needs to be looked at.

 

 

The question is WHEN will it be looked at and WHEN might there be an implemetation of a solution for this Samba issue.

I can't go on with SMB 1 on the one hand, and OpenPLi 6.x is obviously not a solution with my ET8000 on the other hand.

 

What is your advice ? Should I better have a look at OpenVix ? because my ET8000 is still too good to throw it away.

[WanWizard]

"The impossible we do today, for a miracle we have a 5 day waiting period".

 

Honestly, what do you expect? That we drop everything, take a day off, because YOU are in a hurry to have US address something that isn't much of an issue? It will be looked at when it will be looked at, if it will be looked at. It is that simple.

[pluizebol]

Very simple indeed.

 

Amen

[_HarmeN]

Im bought a  Synology DS918+ and im trying to connect my VU+Uno4k and Ultimo4k (with openpli 7.1) to it.

When i put the minimum smb level on v1 everyting is fine. But when i put it on smbv2 it doenst work anymore.

I tried the mount option vers=2.1 but it doesnt work.

 

<?xml version="1.0" ?>

<mountmanager>

<cifs>

 <mount>

  <active>False</active>

  <hdd_replacement>False</hdd_replacement>

  <ip>192.168.1.xx</ip>

  <sharename>/media/net</sharename>

  <sharedir>opnames</sharedir>

  <options>rw,vers=2.1</options>

  <username>username</username>

  <password>password</password>

 </mount>

</cifs>

</mountmanager>

 

Any ideas ?

[WanWizard]

You may also have to add "sec=ntlmssp". Works fine here.

[_HarmeN]

What ver do put in when i want to use v3?

[SpaceRat]

vers=3.02,sec=ntlmsspi

[WanWizard]

"vers=3" means "any version 3, or you can be specific by using "vers=3.0.0", "vers=3.0.2" or "vers=3.1.1".

 

Note that given the fact you have a VU+ with an old 3.x kernel, none of these will work, as the CIFS kernel driver only supports SMBv3 from 4.2.x (actually 4.3.x) onwards. 

[SpaceRat]

3.02 is supported since kernel 3.12

2.1 is supported since kernel 3.7

 

"Experimental" support for each of them some versions earlier.

[_HarmeN]

Thans Guys V2 works ill try v3 later

[WanWizard]

My Duo4K refuses to connect to my Synology on SMBv3, so if you have a working combination of "vers" and "sec", let me know so I can add it to automount.

[MCelliotG]

Same problem with my WD NAS drive, it worked fine before, now the auto discovered parameters lose the mount after E2 restart or reboot.
More specifically the drive is mounted only if I use rw. After is mounted it automatically has the vers=3 parameters that will not work after E2 restart. The only way to remount is to set rw only, then it reverts to the new parameters again and gets lost after E2 restart.
I wonder why is there not an option to set the parameters manually. Nothing I set seems to stick now....

Στάλθηκε από το Redmi Note 5 μου χρησιμοποιώντας Tapatalk