Puppy Linux Discussion Forum

rcrsn51 · Posted: Sat 26 Aug 2017, 13:51 Post subject:

Excellent. I'm hoping that RETRIES=4 should be enough to wake up a sleepy server.

There were old reports that you had to hit the server with a ping before YASSM would see it.

rockedge · Posted: Sat 26 Aug 2017, 14:18 Post subject:

I just can't get it to work. Seems like to many steps to find shares. I can connect other ways with less input and me having to know a lot of ip's or shares. Want to press a button let it search out then I select. This v4.1 I just can not get working. Most programs I get to work.

What I am I doing here wrong to make it so complicated?

rcrsn51 · Posted: Sat 26 Aug 2017, 15:56 Post subject:

don570 · Joined: 10 Mar 2010 Posts: 5389 Location: Ontario

Have you checked if root user and password woofwoof is still used in your new install.

From my own experience, the common problem is

So I go to the machine running the server software and run

rcrsn51 · Posted: Sat 26 Aug 2017, 16:18 Post subject:

Marv · Joined: 04 May 2005 Posts: 1216 Location: SW Wisconsin

I have YASSM (2.9 and 4.1 checked) now running with post 4.13 kernels (It was a mount.cifs issue discussed in the LxPupSc thread). With post 4.13 kernels, mount.cifs requires an explicit SMB version option to run. A command line example is:

rcrsn51 · Posted: Sat 04 Nov 2017, 00:22 Post subject:

Thanks for solving this problem. I will make a note in the main post.

Marv · Joined: 04 May 2005 Posts: 1216 Location: SW Wisconsin

Two additional tests run. YASSM (and mount.cifs) work correctly in XFCE-XenialPup64 r4 with kernel 4.13.3.
The vers=2.1 option and the samba server referenced above were used.

I also switched the pup running the samba server to the latest LxPupSc (17.11.1 1T with the 4.13.11 kernel and the same 4.4.14 samba software). vers=3.0 is now supported as well as vers=2.1.

rcrsn51 · Posted: Thu 09 Nov 2017, 10:23 Post subject:

Note the discussion here where p310don also needed the option with an older Windows share.

At the moment, are the only choices 1.0, 2.1 or 3.0?

Marv · Joined: 04 May 2005 Posts: 1216 Location: SW Wisconsin

Running the latest LxPupSc (17.11.1 1T with the 4.13.11 kernel and 4.4.14 samba software), 3.1 or 3.2 were not supported so yes, I'm pretty sure at this time 1.0, 2.1, and 3.0 are the only valid options. Someone running and versed in the newest 64 bit pups and samba setup would have to double check that but the 4.13.11 kernel in that LxpupSc is 64b and that seems to be the determining factor so I would be surprised if anything higher than 3.0 was supported in the 64b pups either.

takenp · Joined: 05 Aug 2015 Posts: 84 Location: Moskva

Dear @rcrsn51

Your latest YASSM-4.1 failed to load smb shares for the synology's shares (newest OS based on Linux) on Tahrpuppy i386 while version 2.7 could do this without any.. trouble.. just 20 minutes ago )

Then I got another issue while uninstalling YASSM-4.1. It's funny, but I couldn't do it until repaired a bug in ppm's (Puppy Package Manager) script called removemodes.sh.. LOL!

It happened (ppm just got hung) 'cause your pet file is named only with UPPERcase characters that leads to the fault like "couldn't devide by zero" in ppm script, line 141. So I've changed [a-z] onto [A-Z,a-z] for the $TOTAL in the line 132 to make ppm delete the package.

Funny bug but nevertheless! BTW who is responsible for PPM to point on the bug.

thx

step · Joined: 04 May 2012 Posts: 1222

@takenp, I use an older YASSM version and I can mount Sinology shares. If it's a new DSM version you're using, you might need to add "vers=1.0" to the YASSM Options field. I didn't find it necessary to set the other configuration options that rcrsn51 listed in the first post of this thread.

WiZard · Joined: 11 Sep 2005 Posts: 115 Location: Oklahoma USA

Hell0 rcrsn51
Yassm in Stretch 7.5 connect problem.

I have two networks as follows:
wired network on 192.168.254.x
wireless network on 192.168.1.x

My file server is on the wired network on static address: 192.168.254.7
My laptop is on the wireless network at 192.168.1.106. Here are my test results:

laptop>precise 5.7.1>192.168.1.106>yassm=connect
laptop>slacko 6 .3.0>192.168.1.106>yassm=connect
laptop>stretch 7.5>192.168.1.106>pnethood=connect
laptop>stretch 7.5>192.168.1.106>yassm=server not found
laptop>stretch 7.5>192.168.254.106>yassm=connect

I have tried using options "vers=" with values of 1.0, 2.1 & 3.0 but still
no connect

Note the last test when the laptop is moved to the same network as the server, Stretch 7.5 yassm does connect even with no options given.

rcrsn51 · Posted: Mon 09 Apr 2018, 15:58 Post subject:

Try v4.2 attached on the main post.

When you click Set, you will get the message "MAC address not found" because the server is on the other subnet.

But you should be able to mount the share.

WiZard · Joined: 11 Sep 2005 Posts: 115 Location: Oklahoma USA

success, version 4.2 connects.

thanks
Gary