Here Fishy Fishy!

I am currently trying (and failing) to get an embedded board running Armbian to share files with RISC OS. I have been using Samba and !OmniClient but am getting nowhere (there is possibly something wrong at both ends because from a Debian machine the share is only accessible by using the IP address instead of the hostname).

Anyway – since this is something that I have no plans of using with Windows I thought “Why not use NFS?”.

I have now downloaded SunFish and MoonFish and they seem to be pretty good but I notice that they haven’t been touched since 2010.

Are there any updated versions (apart from the ones on www.cp15.org) out there? If I need to do any modifications to the source code who should I contact for the modifications to find their way into the main program branch?

there is possibly something wrong at both ends because from a Debian machine the share is only accessible by using the IP address instead of the hostname

If your local network doesn’t have the sharing machine registered as a DNS entry trying to contact it by name will fail.
Note that the name you are trying to contact may not be what you think – i.e. you call yor Armbian machine ArmPi and the local network knows it as ArmPi.home or ArmPi.local or ArmPi.ChezFluff (Fully Qualified Domain Name) so even putting an entry in the local hosts files may not suffice unless the entry uses the FQDN so that a reverse lookup works.

The RISC OS machine has the IP of the server registered in the Hosts file and I know it can resolve it because it also has an HTML interface so I can go to “http://armbian” and bring up the Web interface.

On Windows and Linux I can see the Armbian machine listed in WORKGROUP but inside it there is no shared folder. Under RISC OS the machine doesn’t appear at all – that’s why I think there is something “wrong at both ends”

For now I’m happy to use a (possibly slightly modified/updated if I need to) version of Sunfish…

The RISC OS machine has the IP of the server registered in the Hosts file and I know it can resolve it because it also has an HTML interface so I can go to “http://armbian” and bring up the Web interface.

Peculiarity of some resolves for applications – some need to know that ArmPi.home is 192.168.2.10 and some also need to know that 192.168.2.10 is ArmPi.home (reverse lookup)

On Windows and Linux I can see the Armbian machine listed in WORKGROUP but inside it there is no shared folder. Under RISC OS the machine doesn’t appear at all – that’s why I think there is something “wrong at both ends”

What version of Windows and what version of Samba on the Armbian install?

Could be access and permissions problem – if you can see the share you have access but until you have permissions you can’t see into it (applies on Windows shares too)
SMB vs SMB2 – the latter increases security with password encryption (hence the change Colin did to the LANMan code)

the local network knows it as ArmPi.home

…is this something my Livebox is doing? My Pi has “RaspberryPi” configured as its hostname (Inet$HostName) and I can get to it from Firefox on the PC by entering “raspberrypi.home” as the URL.

But, in the other sense, I can’t look up the PC because “kuroneko.home” is not a recognised host, so it seems as if RISC OS might be doing something Windows isn’t, or is there something else? The web interface shows KuroNeko is connected, and does so by name. Kiseki, the iPad, can be pinged as kiseki.home so…

Not a big deal, I remember the IP addresses. Just weird, that’s all.

Just messing around, I thought I’d try a traceroute from the Pi to the PC.
Doesn’t work. Even with -nvr options.

How come? I would have expected 192.168.1.10 (Pi) → 192.168.1.19 (Vonets WiFi) → 192.168.1.1 (router) → 192.168.1.15 (KuroNeko, PC). Doesn’t traceroute work on LAN routing?

Not a big deal, I remember the IP addresses. Just weird, that’s all.

Sad innit? I’ve got a logical sequence of IP’s on the access switches and routers at work so remembering those is pretty easy, although others don’t seem to find that.

Doesn’t traceroute work on LAN routing?

What route?
You’re in the same subnet so it’s a layer 2 transfer no need to go through a gateway.

…is this something my Livebox is doing? My Pi has “RaspberryPi” configured as its hostname

Yes probably…if you have BT then the BT Home Hub also resolves to *.home so you can type “http://bthomehub.home” to get to the router configuration.

You can also type “http://192.168.1.254” but most people are scared of numbers.

What version of Windows and what version of Samba on the Armbian install?

It was Windows 10…not sure about Samba – I will check later when I get a chance. I actually copied the smb.conf file from a server that I know is working but it is quite old so is perfectly possible has an older version of Samba installed.

Both the old server and the new one have the same version of Samba:

You can also type “http://192.168.1.254” but most people are scared of numbers.

Well I could, but that isn’t the address of my router :)
OK, I’m awkward but I don’t subscribe to this “the gateways are always x.×.×.254” which is probably because the moment you hit a CIDR superscope situation the .254 address is actually just part of a run through and past 254. For example on a 192.168.1.0/23 the run would be 192.168.1.1 to 192.168.2.254.

It was Windows 10…

Ah, updated SMB security spec. You might want to alter settings for legacy shares and check the behaviour after that.
Reading material about SMB1, SMB2 and SMB3 and how disable different versions.

I’m wondering if there is something up with my version of OmniClient (2.19 (22-Nov-13)). It will connect to one of my servers as a guest and I can browse the data there but I cannot connect as a different user (this might be required because the permissions that the samba server has set up). The other server is visible sometimes but not at other times — and then if I try to close OmniClient it doesn’t work and I still have the icon visible in the iconbar…

Am I doing something wrong or do I need to grab an updated version from somewhere?

My version is 2.21 from 01-Feb-2015.
So yes, you could try an update.

Hmm…seems that there might geniunely be something wrong with the samba server. I’ve turned on a third samba device and I can see it OK in OmniClient but cannot connect becaus I don’t know what log-in should be.

To summarize:

Regarding the 3rd server…has anyone ever connected to LibreELEC samba shares using RISC OS? Their Wiki only lists Windows/Linux/MacOS options.