AmigaOS port of libsmb2

Hi,

I tried SMBFS2/3 handler but I cannot mount anything.

How is it supposed to work ?

I have this in my mountfile :

Handler = L:smb2-handler
Priority = 5
StackSize = 65536
GlobVec = -1
Startup = "smb://xxxx:xxxxxxx@MacProSrv/WRT"

MacPro is my Apple Mac Pro sharing via Samba (I declared MacPro in my host configuration).

But nothing is mounted.

I still don't know where and how to explicitly tell the VOLUME name I want to choose.

If someone can point me to a complete example (it would be great if a complete example was inserted in the documentaion BTW).

Working ok now :)

@K-L

Not for me, what did you change to your last comment?

@salass00

Quote:
Is there also a way to poll for offline shares and remove them?

Right now i have yet to find a way to actually dismount offline shares as dismount refuses to do so.
I get an error about the target being not available, dismount's force switch doesn't help either.

Does anyone know how to get rid of a share once it went offline?
(Because right now it stalls the WB)

@all

Is it even possible to remove a (non-available) device?

smbfs had a task glued to every incarnation which was handy because it would be removed even after the share went offline.

But as soon as any smb2fs share goes missing (i.e. Windows machine shuts down, the share is unreachable in every way, even removing it with "dismnount" will yield an error message.

Help?
Hints?
Ideas?

@Raziel

What did they call their handler ? I called it smb2 example:

DISMOUNT "smb2:" FORCE

I don't know if it solves your problem, but it logs off all shared folders.

@K-L

I have it set up like this under AmigaOs4.1 and MacOs.

Handler = L:smb2-handler
Priority = 5
StackSize = 65536
GlobVec = -1
Startup = "smb://mac-studio/shareFolder
USER=xyz PASSWORD=xyz VOLUME=ShareFolder"

It is important that you remove the brackets () in the handler the tooltype ACTIVATE=0, otherwise the share will not be registered under AmigaOs 4.1. You can also use ACTIVATE=1 if you start the handler only when you need it.

@Maijestro

Mine are called "SMB2_Name-of-the-Share:" (using 4 to 5 for now).

That "dismount force" command was the first i tried, it didn't help as it already tells me that the target is not available.

I use 4 shares from a NAS (which doesn't really need dismounting) and one from a Windows machine (which boots and shuts down regularly).
That Windows share is the culprit, as it freezes the OS once it shuts down.
It doesn't come back automatically when the machine is up again either, so it's rather awkward to have to reboot just because of dumb Windows is gone.

I looked around at thew depot and on aminet, there doesn't seem to be a program which can do what i'm looking for, though i still have to test "assign dismount" on both the device and volume name...

Or maybe i'll go back to smbfs for that Windows share?

@Raziel

You must not blame Windows when it shuts down and disconnects, the problem is unfortunately with AmigaOs4.1 it simply does not recognize when a connection is lost and does not log off the shared order.

Your configuration is also a bit difficult, I use smb2 under QemuPeg2 AmigaOs4.1 to be able to move data from host/guest and that works really well.

I would like to help you as you helped me, but unfortunately I don't know what to do in this situation. I am sorry......

@Maijestro

Heh, no sweat

If it doesn't work the way I'd like it to there's always smbfs to go back...not that I use the win share much anyway.

I'll maybe even switch to using devs:dosdriver mountfiles instead of scripts.

But maybe someone can still explain how to use the obfuscated passwords, I didn't really read it up yet

@tekmage

Did you ever get an answer from OnyxSoft wrt Backup?

@salass00

Renaming files/directories that only change case status doesn't work

e.g. rename "Sound" as "sound"
Error: Rename failed - object already exists

linux share on ext4 fs

@Raziel

Quote:

This is fixed in the AmigaOS 4 filesysbox library since version 54.11 (26.12.2022) and in the AROS/AmigaOS 3 library since version 54.1 (14.1.2023).

Apparently it is possible to set some samba servers to timeout connections after a period of inactivity (for smbd this can be done using the deadtime option in /etc/samba/smb.conf) and smb2fs doesn't handle this situation very well ATM.

Ideally smb2fs should detect this somehow and restart the connection when it happens, but as a quick fix I tried to make smb2fs ping the server at regular intervals using smb2_echo() to keep the connection alive but this didn't seem to help.

@salass00

Where can I get the latest version of filesysbox?

I don't find it on the depot and on github only the Arosa version seems to be released

I would be interested in that too. Currently I am using version 54.9 Filesysbox.library with smb2.

@salass00

I need to add that my bug report was partially untrue.

Only *files* are affected, directories work fine, but i guess you knew that already?

filesysbox.library 54.9 (09.04.2019)
smb2-handler 53.6 (25.05.2023)

@Raziel

The github repo is only for the AROS/AmigaOS 3 fork of filesysbox.

The AmigaOS 4 version is distributed with the OS and with Enhancer Software only.

@salass00

Got it, thanks for clearing that up

@salass00

Hi there,

i didn't find an entry on the Enhancer bug tracker for smb2fs, so i'm posting this here.

I found a nasty little bug which alters/mangles directory/file name entries by simply adding a single character to the name.

Steps to reproduce:
1) Open up any share
2) Create a new directory or file (root or where ever) and call it whatever
3) After creation, rename it and simply add either a "<" or a ">" to it
4) After renaming, update the directory entries or close and reopen the directory and boom, your directory/file was renamed to something completely different.

I only found the two characters "<" and ">" to show this behaviour so far...strange little bugger, that is

Hi,

I wonder why it is raised through Enhancer? I did not know there was a connection.

---

I also wonder if this is anything to do with the ABCSH getting confused over the use of redirection character(s) being used rather than a bug in smb2fs. It would be interesting to see what string is _really_ being sent through smb2fs as the new name; whether those characters should be escaped...