I have a remote NAS accessible via smb on the internet,
It is “mounted” as a network drive in my files on my Rocky Linux, but I can’t find a way to access it through my Flame’s MediaHub/Explorer.
Is there any way to do so ? It’d be so helpful.
So two things. When you say ‘mounted’ is it actually permanently mounted? Most of us create a folder called /Volumes and then mount network drives to that via the ‘mount’ commandline or /etc/fstab.
If you do that, you shouldn’t have to type in smb://abc…
It’s possible that the MediaHub is using other networking commands beyond basic smb to check access to the drives that don’t get through whatever vpn you setup.
But first I would make sure that it’s mounted locally, and shows up in ‘df -h’.
The reason most folks use /Volumes vs. /mnt is that it mirrors file paths on Mac, so if you switch systems, the paths will stay intact.
sudo mount -t cifs -o user=username,uid=1000,gid=1000 //Host/Name /Volumes/Name
‘username’ is your user name on the NAS
‘host’ is the domain name of the NAS, or you can put the IP address in
‘Name’ is volume you’re mounting from the NAS, and also a local mount point you created
Once you run this, it will ask you for the local password for sudo, and then will prompt you for the password for your NAS login
This you will have to every time you boot and login into your Flame.
Alternatively you can add a line to the file /etc/fstab that will automatically mount it at boot. I don’t have it handy at the moment though.
SMB-mounted network drive isn’t automatically recognized by Flame’s MediaHub/Explorer because these interfaces use their own file access systems. Try connecting directly through MediaHub’s network features by looking for “Add Network Location” options where you can enter your SMB path.
Alternatively, create a symbolic link from a Flame-accessible local directory to your mounted SMB share. You could also try Flame’s gateway features which bridge between local and network resources.
If these approaches don’t work, check the Flame documentation for your specific version, as there may be particular requirements for network storage access or preferred mounting locations that MediaHub recognizes.