Yet Another Samba Share Mounter

Configuration wizards, scanners, remote desktop, etc.
Message
Author
User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#181 Post by rcrsn51 »

Excellent.

Here is the situation: Samba client apps use a variety of search tools - nbtscan, mpscan, nmblookup. YASSM v4.x replaces them with a single tool - arp-scan.

Unfortunately, arp-scan only works on the local subnet. It is not routable across to another subnet like in your situation.

So I replaced some of the arp-scan calls with pings, which are routable.

I don't think that there is any penalty for doing this, but it needs more testing and feedback.

WiZard
Posts: 119
Joined: Sun 11 Sep 2005, 20:04
Location: Oklahoma USA

yassm 4.2

#182 Post by WiZard »

Thanks for the explanation, makes me smarter

Gary

User avatar
takenp
Posts: 101
Joined: Wed 05 Aug 2015, 23:27
Location: Moskva
Contact:

#183 Post by takenp »

Dear @rcrsn51

Bionicpup_64/Tahrpup_32 with Samba Simple Management and YASSM:


YASSM 2.7 and 2.9

search works (it is convenient!)
mount works


YASSM 4.1

no search (have to type in all fields manually)
mount does not work!

It says: "Server 192.168.88.35 not found!"

I checked with bash and it works:

Code: Select all

mount -t cifs -o username=root,password=woofwoof,ip=192.168.88.35 //192.168.88.35/puppyshare /mnt/smb/ 
So I rolled back to 2.9 and ask a question: where I am wrong?

thx!
[color=indigo]~=~=~=~=~
I'm running Internet radio here: http://melodymaker.org
The very best of hard rock with 192 bit quality stream.[/color]

User avatar
Moose On The Loose
Posts: 965
Joined: Thu 24 Feb 2011, 14:54

#184 Post by Moose On The Loose »

takenp wrote:Dear @rcrsn51

Bionicpup_64/Tahrpup_32 with Samba Simple Management and YASSM:
Just as bit of a BTW:
I have made my own samba share mounter script.
It is not really ready for prime time but something I did may be useful.
I discovered that on a dodgy network, sometimes machines are not seen by any method. Basically any machine may come and go at any time. But on the average it is there more than 50% of the time. Sometimes it appears that network traffic made the machine start paying attention again.

I "solved" the problem with the following things:

1) I always scan the network twice
2) In /tmp I save the results
3) If the previous results in /tmp don't match this time I try a bit more
4) I have a "server not seen" option in the server selection list

The network I was using when I did this had some Win10 machines that were not working right along with some things doing UDP and WiFi connections that were getting jammed. In other words a complete "pigs breakfast" of a network. My mounter still worked on this mess.

Post Reply