SMB2FS OS3 port

[AMIGASYSTEM]

Originally Posted by tomcat666

Thank you BSZili - working like a charm on real A1200 with pistorm32. Everything perfect.

As always your ports are flawless.

Slowly we are getting to a very 21st century usable state amiga 68k
We need a semi-modern web browser and a SSH terminal client and we are basically there.

Tomcat, there is no modern Browser on OS3, but on OS3 you can visit any modern site with AmiFox (it also exists for AROS)

https://blog.alb42.de/programs/amifox/

[BSzili]

Originally Posted by AMIGASYSTEM

I updated amb2-handler to version 53.5, and now the error has changed, see screenshot.

I specify that the same mountlist (SMB2) works perfectly on AROS x86/68k and OS3

The problem is simple: the host name you've specified can't be reached from that machine. Try to ping it and you'll see that it doesn't work. You can just use the IP address instead.

Originally Posted by tomcat666

Thank you BSZili - working like a charm on real A1200 with pistorm32. Everything perfect.

As always your ports are flawless.

Slowly we are getting to a very 21st century usable state amiga 68k
We need a semi-modern web browser and a SSH terminal client and we are basically there.

The credit goes to salass00, who created the handler. I tried to port SSHTerm too, but libssh kept trashing the memory. I don't have a particular need for an ssh terminal so I shelved it.

[AMIGASYSTEM]

Originally Posted by BSzili

The problem is simple: the host name you've specified can't be reached from that machine. Try to ping it and you'll see that it doesn't work. You can just use the IP address instead.
.

I tried using an IP address and nothing changes, same error.

On OS3 (WinUAE) and AROS (VMvare) "the same Mountlist" works in both methods !

I suspect a Windows protection that OS4.1 or WinUAE failing to pass

[BSzili]

The first thing to be checked if you can ping the address/host name. If you can't then there's nothing that can be done about it.

[AMIGASYSTEM]

Originally Posted by BSzili

Very cool! A few suggestions for the UI:

• there's no need to expose GlobVec to the user, it should always be -1
• consider using the USER and PASSWORD arguments, so the reserved characters (e.g. : ; @) can be used in passwords
• an option to set the VOLUME argument would be nice for custom names

Yannick Buchy has updated the GUI, it has been improved and completed according to the suggestions, see screenshot !

About OS4 the Ping did not detect the IP, I think there is something to set on OS4, OWB works regularly.

[ProfPlum]

I just set this up.
I'm on an A2000/vampire v2/roadshow system connecting to my Synology NAS.
I can only connect via IP rather than hostname. Other than that, all seems fine.


Many thanks BSzili.

[AMIGASYSTEM]

@prof

Strange to me the hostname works fine on both OS 3.2 and OS 3.9, check that the names have no spaces or particular font !

[itsmedoofer]

So I have copied my mount files from one A1200 to another, same Miami configuration same network card, both OS3.2.2.1

On the first A1200 they work and I can connect, see previous post, the second they do not work and I get the error;

Session setup failed with 0xc000006d STATUS_LOON_FAILURE

Any ideas? This is the machine I was previously having problems with.... As I said the same mount and configuration work on one but not the other...

[jurassicman]

I was finally able to give it a better go and this time it works great!

I haven't changed my shares configuration on Linux and, in fact, they still work on my Amiga if I mount them using the old SMB v1 method.

I think that I was having issues duo to the fact that in my Dopus configuration I had the samba devices listed among the other devices.

I simply deleted them and tried to mount my share(s) once again and instead of receiving the "device already mounted" message I got the device icon on my desktop.

I also fond the way to unmount the shares:
> assign NameOfShare: dismount

I'm going to write a new script to mount/unmount my shares like I did with the previous commands.

Thanks once again for your work!

[BSzili]

A word of warning: assign dismount will not unmount the share despite its name. It simply removes it from the DOS list, so you won't see it, but it'll remain connected in the background. To actually unmount it you can use KillDev from the IDEfix97 package, but this was never supported well on AmigaOS.

[jurassicman]

thanks for the hint... I'll see if KillDev does a better job...

[AMIGASYSTEM]

Yes but only on Amiga you can disassemble, on AROS the volume is always in use and cannot be disassembled !

[yelworC]

Killdev crashes with guru for me when trying to remove a smb2 volume.

I am running OS3.2.2.1 and this actually has an "official" method for removing dos devices. Its explained in helpfile for "mount" command (open with "help mount" in shell).

Command is:

MOUNT SBM0: SHUTDOWN && ASSIGN SMB0: DISMOUNT

This works with many filesystems but with smb2-handler I alwas get yellow recoverable alerts before device is removed and sometimes even guru system crashes. I think filesystems have to be compatible to work with this method.

When it worked after the yellow alert it really seems to be removed and for example roadshow can go offline.

Maybe this can be fixed in smb2-handler to make it 100% compatible with "mount shutdown"

[BSzili]

If it sends an ACTION_DIE packet, then that's already supported, that is how KillDev works. This was never standardized though, so it's not a 100% clear what a handler has to do when it receives one. If the OS3.2.2.1 devs want to look at it, here's where the packet is handled:
https://github.com/salass00/filesysb...er/src/fsdie.c

[KONEY]

I'm confused, you mean this issue is not common for every setup? I've tried accessing samba shares running on Armbian and OSMC servers and from Miami and AmiTCP 3/4 clients, always with the same outcome.

Originally Posted by BSzili

I can't do much about this, unless someone can help me step by step to recreate the setup where the SMBD crashes. I don't have an account at samba.org, but I wouldn't be able to properly describe the problem for them anyway, since I don't know much about it

[fgh]

Just tried this and connected to a share on my Win10 machine.
It just works! Great stuff, thank you BSzili!

[matt3k]

Is this working with QNAP NAS's yet?

[fryguy]

Originally Posted by matt3k

Is this working with QNAP NAS's yet?

I'm using it with my old QNAP.

[riker77]

OS: 3.2.2.1
smb2-handler: 53.5 (020)
fileysbox.library: 54.3 (020)

I am not able to mount a share, if I don't include the password in the SMB-URL. As soon as I enter a passord in the requester and confirm it, workbench hangs and a warm start is necessary. No packets are being sent over the network.

Does not work:
Startup = "smb://myuser@192.168.x.y/Am_iga VOLUME=Amiga READONLY"

Works:
Startup = "smb://myuser:mypw@192.168.x.y/Am_iga VOLUME=Amiga READONLY"

[BSzili]

I don't think I've ever tested the password requester under 3.2.2.1, so anything can happen. I quickly tried it under 3.1 and no lockups there at least.