° I connected a WD Mycloud storage device to my LAN and would like to transfer some files from this Fedora 31 computer to it. Although it seems to work well enough with the iPhones it is primarily an Apple or Windows device and does not appear to be Linux friendly. Is there a way to load some files from this box directly without sending them to an ios device first? I am hoping someone has has experience with one of these, I don't need it but it's there for the ios users on my system ... Thanks Bob
On 4/4/20 1:28 PM, Bob Goodwin wrote:
° I connected a WD Mycloud storage device to my LAN and would like to transfer some files from this Fedora 31 computer to it. Although it seems to work well enough with the iPhones it is primarily an Apple or Windows device and does not appear to be Linux friendly. Is there a way to load some files from this box directly without sending them to an ios device first? I am hoping someone has has experience with one of these, I don't need it but it's there for the ios users on my system ... Thanks
If it's Windows-friendly, you might try SMB connections.
On Sat, 2020-04-04 at 13:28 -0400, Bob Goodwin wrote:
I connected a WD Mycloud storage device to my LAN and would like to transfer some files from this Fedora 31 computer to it. Although it seems to work well enough with the iPhones it is primarily an Apple or Windows device and does not appear to be Linux friendly. Is there a way to load some files from this box directly without sending them to an ios device first? I am hoping someone has has experience with one of these,
I've used older ones (yes, I do mean WD MyCloud devices, not just similar functioning devices).
They supported NFS (either already, or you had to plough through options to enable it). But they supported it badly, user-permissions were mangled to destroy personal ownership, and other methods were sometimes used to restrict access to just the owner, or things were just available to everybody (these things tend to be aimed for very dumb usage - a really bad idea for something that's network accessible, even worse if it's available to the internet).
Newer ones stopped supporting NFS (either it wasn't there, or was even worse, or you had to figure out how to get it running from scratch). The ironic tag-monster automatically chose this email's tag, ha.
So, unless you're trying to solve a known problem, I wouldn't update the firmware in one of these cloud devices, and I'd turn off any auto- updating options. Since they may be set up to auto-update by default, I unplugged my link to the internet while setting them up. I also turned off various unneeded features in the cloud device. Since I wasn't using it as a media server, I turned that off (which also should stop it trawling through its files to database them - this can take forever, especially as they rescanned the entire drive whenever new files were added, rather than just update an existing database). Do let the device access a timeserver so that its clock is in time with your system. It makes file management much easier if files have sane datestamps, and I found NFS refused to work if the clocks were too far out of step between cloud and a Fedora PC.
They like to go to sleep when idle, and hibernate when left idle for long enough. So, putting entries for them in your /etc/fstab file can cause you headaches as Linux expects a resource to be there when accessed, and can behave badly when it's not. I use autofs, instead, so that when I try to access /net/name-of-cloud-device the named cloud device is automatically mounted (and waking up sleeping cloud devices, if I'm lucky). Sometimes a comatose cloud device will not wake up, and I'll either have to access its configuration webpage in Firefox to try and bring it to life, or unplug its power to reboot it. If your intention is to have an always-available device, you could disable its sleep mode, but the device may not have adequate cooling to run continuously (most of these things are fanless). All in all, I think they're a typically crappy consumer device.
Since these NAS devices are primarily aimed at the Windows and Mac crowd, it's probable that getting Samba running on your computer is going to be the easiest supported way to make use of them. I haven't used Samba for over a decade, so I'm well out of practice. Are you familiar with Samba?
Whatever method you use, I'd advise configuring the cloud device to have a fixed IP. It's a lot easier to deal with it when its address is always the same.
On 2020-04-04 14:31, Tim via users wrote:
They supported NFS (either already, or you had to plough through options to enable it). But they supported it badly, user-permissions were mangled to destroy personal ownership, and other methods were sometimes used to restrict access to just the owner, or things were just available to everybody (these things tend to be aimed for very dumb usage - a really bad idea for something that's network accessible, even worse if it's available to the internet).
° I bought it to provide storage space for image files from iPhone cameras and it looks like it does that nicely. I have no intention to make it in to an NFS, I have a dedicated Fedora computer for that purpose and rely on it,
They like to go to sleep when idle, and hibernate when left idle for long enough. So, putting entries for them in your /etc/fstab file can cause you headaches as Linux expects a resource to be there when accessed, and can behave badly when it's not. I use autofs, instead, so that when I try to access /net/name-of-cloud-device the named cloud device is automatically mounted (and waking up sleeping cloud devices, if I'm lucky). Sometimes a comatose cloud device will not wake up, and I'll either have to access its configuration webpage in Firefox to try and bring it to life, or unplug its power to reboot it. If your intention is to have an always-available device, you could disable its sleep mode, but the device may not have adequate cooling to run continuously (most of these things are fanless). All in all, I think they're a typically crappy consumer device.
° I am not certain if it sleeps, I suspect it does if not stimulated for a while, but don't know and have not seen anything that touched on that. I don't know that a wake-up delay would matter for that use, they are mainly freeing up space on the phones.
Since these NAS devices are primarily aimed at the Windows and Mac crowd, it's probable that getting Samba running on your computer is going to be the easiest supported way to make use of them. I haven't used Samba for over a decade, so I'm well out of practice. Are you familiar with Samba?
° Well it shows up in Network but I can't connect from their, not even to list the files, I dunno if it even has a Samba server. I have a dedicated Fedora box that serves as a Samba server and I can connect to that and manipulate stuff from this computer, the servers are headless and I can use ssh and/or sftp for that.
Whatever method you use, I'd advise configuring the cloud device to have a fixed IP. It's a lot easier to deal with it when its address is always the same.
° My ASUS dd-wrt router assigns ipaddresses and I made the Mycloud static.
I hope this thing will just run without any attention from me. I have a lot of trouble seeing the small iPhone screen, I have a Merlin cctv device that I put small things like that and can get them on a large display, that works better with the iPad for me. Anyway I let my daughter set-up the Mycloud device, I just answered her questions and heard no mention of updating, she may have ignored it? However it would be nice if I had some access to it which is what inspired me to ask here, it's not critical now ...
I thank you for the response and appreciate your suggestions.
-- [tim@localhost ~]$ uname -rsvp Linux 5.0.16-100.fc28.x86_64 #1 SMP Tue May 14 18:22:28 UTC 2019 x86_64
On 2020-04-05 03:36, Bob Goodwin wrote:
However it would be nice if I had some access to it which is what inspired me to ask here, it's not critical now ...
Good to know it isn't critical. Being the curious type, I'd run
nmap -p1-2000 device-ip-address
to see what ports are open.
On 2020-04-04 18:51, Ed Greshko wrote:
On 2020-04-05 03:36, Bob Goodwin wrote:
However it would be nice if I had some access to it which is what inspired me to ask here, it's not critical now ...
Good to know it isn't critical. Being the curious type, I'd run
nmap -p1-2000 device-ip-address
to see what ports are open.
° I tried to respond last night but the Viasat internet connection died, that has happened rarely in the 14 years I've relied on them. I did not call tech support since they will probably want to "reset my modem" which may disrupt my configuration settings, it's a monstrosity containing a wifi router, which I turned off, and the voip phone. Anyway this morning I see:
[bobg@Workstation-1 ~]$ nmap -p1-2000 192.168.2.202 Starting Nmap 7.80 ( https://nmap.org ) at 2020-04-05 05:48 EDT Nmap scan report for WD-MyCloud-WCC7K3PU2VT1.Viasat (192.168.2.202) Host is up (0.0016s latency). Not shown: 1995 closed ports PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 548/tcp open afp
Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
The mycloud ethernet data led us still blinking as it has been for two days, she has a lot of image files on that phone ...
I don't know what conclusions can be made from the nmap data?
Tim:
They supported NFS (either already, or you had to plough through options to enable it).
Bob Goodwin:
I bought it to provide storage space for image files from iPhone cameras and it looks like it does that nicely. I have no intention to make it in to an NFS, I have a dedicated Fedora computer for that purpose and rely on it,
That answer is incoherent.
Such a cloud device can be a NAS (network attached storage). The method of accessing it could be NFS (network file system), it could be SMB (server message block, i.e. Samba).
NFS is a commonly used network filing stem on Unix/Linux.
SMB is the old Windows networking, that has spread like the plague to other computing systems. We have Samba to deal with it.
Each has their configuration difficulties. Each has their issues in appearing to give transparent access to the stored files as if it were the same as the hard drive on your computer. They have to deal with which user is which locally and on the NAS, and they have to handle file permissions.
SMB brings in an extra set of pain - one SMB server has to be the boss, they elect this amongst themselves based on some formular of biggest &/or best CPU, uptime, and how many fingers I'm holding up. If the boss goes offline, they have an election after 15 minutes of waiting around (and usually 15 minutes of broken networking), to work who'll be the new boss. You can tweak that in your /etc/smb.conf file (to increase/decrease your computer's chance at becoming this "browse master" boss), but it's harder to do that with a NAS (you have to enable SSH access, ssh in and edit its smb.conf file, and hope that it doesn't change your settings on you, later on).
Hence, for my systems, I've stuck with NFS (less pain to deal with), though they added their own particular pain (Western Digital pain, not NFS pain), by squashing all file ownership to user ID 1000. Again, I ssh'd in, changed their /etc/exports file. They regularly screw up NFS, and don't want to support it, by configuring it in stupid manners, claiming NFS is too hard (only because they made it so).
And regardless of whether you have other NAS, or other file servers using NFS or SMB, this cloud device is its own server for one or more of those protocols. Having a Fedora server using NFS or SMB does not preclude you adding a NAS device that is using NFS &/or SMB, too.
I am not certain if it sleeps, I suspect it does if not stimulated for a while, but don't know and have not seen anything that touched on that. I don't know that a wake-up delay would matter for that use, they are mainly freeing up space on the phones.
I think you'll find they're preset to go to sleep when idle. All the ones I've come across had it as the default setting.
It's as well to have a look at the configuration of your device. Use your web browser to browse to the address of your device. Look through the options is presents. The devices have a little web server built into them to let you control the device.
Well it shows up in Network but I can't connect from their, not even to list the files, I dunno if it even has a Samba server.
What shows up in the Network section of the file browser is generally using SMB for the file access (I believe it can use other protocols, but I see no clues as to how). Though, other protocols may discover the *presence* of the device (mDNS, Avahi, Bonjour, etc), actual access is through SMB/Samba.
I have a dedicated Fedora box that serves as a Samba server and I can connect to that and manipulate stuff from this computer, the servers are headless and I can use ssh and/or sftp for that.
From my point of view, that's the easiest of way of dealing with adding more storage (adding big drives to a normal computer, that you can configure exactly how you want it).
NAS devices have their quirks, but do let you plug in a small, low- power, self-contained, device to do their prime job (storage, some offer a bunch of other features, too). And while they're not really designed for unplugging and transporting to another network (not rugged enough, and configuration annoyance), it can be done. Probably they're best feature is being low-cost to run 24/7, for people who have a home entertainment TV/sound system accessing files stored on it, who don't want to run a full PC 24/7 for that role. But if you already have a server PC running 24/7, a NAS device is just a new headache.
I hope this thing will just run without any attention from me.
Once you get it going, it's going to be like that. Getting started is the hard part.
If you don't care who owns what, and are fine with everything being world readable and writeable, then you may be able to use the thing with minimal configuration, just dumping all your files in its "public" folder. If you want file ownership control, you're going to have to set up user accounts and user folders on it (done through its web interface). You may have to set up user accounts on the device, even if you're just going to use the public folder. With SMB you may need to set the workgroup name, though it's possible that the file browser will let you drill down from the device to where you want.
e.g. //devicename/workgroupname/sharename
Or just let you directly access it via browsing: smb://devicename/
You'll need to decide how to access it (SMB &/or NFS), and configure your clients appropriately. Add mount points on them, or use an autofs that does it for you.
On Sun, 2020-04-05 at 06:32 -0400, Bob Goodwin wrote:
The mycloud ethernet data led us still blinking as it has been for two days, she has a lot of image files on that phone ...
Is your internet activity light blinking too?
I tried letting my smart phone backup to my cloud device. The phone had no way to limit just backing up photos, it'd also back up the huge video files it'd taken. It did it all the time, chewing through my phone internet bandwidth and home bandwidth, even when the phone was on the same WiFi & LAN as the cloud device. It continually did the same files over and over, restarting when interrupted by networking problems. It dumped every thing it sent from the phone to one huge directory on the cloud device.
That was a Samsung, not an iPhone, but you can probably guess that I don't let it do any of that any more.
On 2020-04-05 18:32, Bob Goodwin wrote:
PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 548/tcp open afp
Well, that bit of information is telling you that box is running a "samba" server and "apple filing protocol" server.
So, if you get information from the management display of the device (I think via http) you may be able to use mount.cifs or mount_afp if you have the fuse-afp package installed.
On 2020-04-05 19:59, Ed Greshko wrote:
On 2020-04-05 18:32, Bob Goodwin wrote:
PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 548/tcp open afp
Well, that bit of information is telling you that box is running a "samba" server and "apple filing protocol" server.
So, if you get information from the management display of the device (I think via http) you may be able to use mount.cifs or mount_afp if you have the fuse-afp package installed.
FWIW, I just enabled afp on my synology NAS and installed the fuse-afp on my linux system. Then.....
[egreshko@f31k ~]$ mount_afp afp://myusername:mypasswd@192.168.1.142/aux apple The afpfs daemon does not appear to be running for uid 1026, let me start it for you Mounting 192.168.1.142 from aux on apple Mounting of volume aux of server nas succeeded
[egreshko@f31k ~]$ ls apple backups linux-releases qemu-images
[egreshko@f31k ~]$ touch apple/x [egreshko@f31k ~]$ rm apple/x
demonstrates I have rw access to that directory on the server.
On 2020-04-05 20:24, Ed Greshko wrote:
On 2020-04-05 19:59, Ed Greshko wrote:
On 2020-04-05 18:32, Bob Goodwin wrote:
PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 548/tcp open afp
Well, that bit of information is telling you that box is running a "samba" server and "apple filing protocol" server.
So, if you get information from the management display of the device (I think via http) you may be able to use mount.cifs or mount_afp if you have the fuse-afp package installed.
FWIW, I just enabled afp on my synology NAS and installed the fuse-afp on my linux system. Then.....
[egreshko@f31k ~]$ mount_afp afp://myusername:mypasswd@192.168.1.142/aux apple The afpfs daemon does not appear to be running for uid 1026, let me start it for you Mounting 192.168.1.142 from aux on apple Mounting of volume aux of server nas succeeded
[egreshko@f31k ~]$ ls apple backups linux-releases qemu-images
[egreshko@f31k ~]$ touch apple/x [egreshko@f31k ~]$ rm apple/x
demonstrates I have rw access to that directory on the server.
Oh, and if you enter an incorrect directory on the mount line you may get a list of valid ones...
[egreshko@f31k ~]$ mount_afp afp://myusername:mypasswd@192.168.1.142/auxssss apple Mounting 192.168.1.142 from auxssss on apple Volume auxssss does not exist on server nas. Choose from: home, video, photo, NetBackup, music, misty, homes, aux
On 2020-04-05 07:24, Tim via users wrote:
Is your internet activity light blinking too?
I tried letting my smart phone backup to my cloud device. The phone had no way to limit just backing up photos, it'd also back up the huge video files it'd taken. It did it all the time, chewing through my phone internet bandwidth and home bandwidth, even when the phone was on the same WiFi & LAN as the cloud device. It continually did the same files over and over, restarting when interrupted by networking problems. It dumped every thing it sent from the phone to one huge directory on the cloud device.
That was a Samsung, not an iPhone, but you can probably guess that I don't let it do any of that any more.
. The iPhone appears to be about the same if not worse, judging from my experience here with half a dozen of those devices on our system, this morning my usage is 3 times my allotted allowance for March and I have a few days to go before it restarts. Usage is "unlimited" until you reach the allowed amount, then performance is reduced as a function of the overall system usage. Typically I get a week or two of the specified speeds ... I log daily "ip traffic," usage for each user/address and know where the heavy usage is.
For whatever reason, the phone images being saved to the Mycloud device are coming from the iCloud server, questioning the wisdom of the process design is heresy, I've given up on that and just accept it! I have heard many complaints about data being dumped when a transfer is interrupted and the process being restarted, Apple really needs a good solid connection to work well it seems, it often eats my usage while never finishing.
On 2020-04-05 07:59, Ed Greshko wrote:
Well, that bit of information is telling you that box is running a "samba" server and "apple filing protocol" server.
So, if you get information from the management display of the device (I think via http) you may be able to use mount.cifs or mount_afp if you have the fuse-afp package installed.
° This has not worked, says my command is wrong:
[root@Workstation-1 bobg]# mount -t cifs /192.168.2.202/ 214 /mnt/test
mount: bad usage Try 'mount --help' for more information.
'
mount: bad usage Try 'mount --help' for more information.Z
On 2020-04-05 22:14, Bob Goodwin wrote:
On 2020-04-05 07:59, Ed Greshko wrote:
Well, that bit of information is telling you that box is running a "samba" server and "apple filing protocol" server.
So, if you get information from the management display of the device (I think via http) you may be able to use mount.cifs or mount_afp if you have the fuse-afp package installed.
° This has not worked, says my command is wrong:
[root@Workstation-1 bobg]# mount -t cifs /192.168.2.202/ 214 /mnt/test
The form is along the lines of....
mount -t cifs -o username=<win_share_user> //WIN_SHARE_IP/<share_name> /mnt/win_share
Give the afp stuff a try as well.
On 2020-04-05 08:24, Ed Greshko wrote:
FWIW, I just enabled afp on my synology NAS and installed the fuse-afp on my linux system. Then.....
[egreshko@f31k ~]$ mount_afpafp://myusername:mypasswd@192.168.1.142/aux apple The afpfs daemon does not appear to be running for uid 1026, let me start it for you Mounting 192.168.1.142 from aux on apple Mounting of volume aux of server nas succeeded
[egreshko@f31k ~]$ ls apple backups linux-releases qemu-images
[egreshko@f31k ~]$ touch apple/x [egreshko@f31k ~]$ rm apple/x
demonstrates I have rw access to that directory on the server.
° I'm back at this again and see the following result:
bobg]# mount_afp afp://my_mycloud_username:12345678@192.168.2.202/aux /mnt/test Mounting 192.168.2.202 from aux on /mnt/test Login error: Authentication failed
Those user credentials work with the WD Mycloud browser page and provide access to the files, but I suspect not directly from the mycloud device, images must be downloaded and viewed, in my case with gthumb. It can take a minute or two to view one jpeg.
I am told that when an image is stored to the iCloud server it is removed from the iPhone camera leaving only a low resolution "thumbnail." Viewing a a high resolution image requires a connection to the iCloud. That explains some of the high bandwidth usage that I see, if true, what an awful scheme!
Anyway I want to see what is actually store on the WD Mycloud device, it should be the complete high resolution image file ...
The question now is what's wrong with mount_afp authorization? I think I made /mnt/test/ accessible with chmod 777 /mnt/test/.
On Wed, 8 Apr 2020 at 12:37, Bob Goodwin bobgoodwin@fastmail.us wrote:
On 2020-04-05 08:24, Ed Greshko wrote:
FWIW, I just enabled afp on my synology NAS and installed the fuse-afp
on my linux system.
Then.....
[egreshko@f31k ~]$ mount_afpafp://myusername:mypasswd@192.168.1.142/aux
apple
The afpfs daemon does not appear to be running for uid 1026, let me
start it for you
Mounting 192.168.1.142 from aux on apple Mounting of volume aux of server nas succeeded
[egreshko@f31k ~]$ ls apple backups linux-releases qemu-images
[egreshko@f31k ~]$ touch apple/x [egreshko@f31k ~]$ rm apple/x
demonstrates I have rw access to that directory on the server.
° I'm back at this again and see the following result:
bobg]# mount_afp afp://my_mycloud_username:12345678@192.168.2.202/aux /mnt/test Mounting 192.168.2.202 from aux on /mnt/test Login error: Authentication failed
Ed didn't mount as "root". The point of fuse is to allow users to do the mounts. CHeck that your "id" include the fuse group.
Those user credentials work with the WD Mycloud browser page and provide access to the files, but I suspect not directly from the mycloud device, images must be downloaded and viewed, in my case with gthumb. It can take a minute or two to view one jpeg.
I am told that when an image is stored to the iCloud server it is removed from the iPhone camera leaving only a low resolution "thumbnail." Viewing a a high resolution image requires a connection to the iCloud. That explains some of the high bandwidth usage that I see, if true, what an awful scheme!
Anyway I want to see what is actually store on the WD Mycloud device, it should be the complete high resolution image file ...
The question now is what's wrong with mount_afp authorization? I think I made /mnt/test/ accessible with chmod 777 /mnt/test/.
You should be a create a directory within your "home" directory and mount fuse filesystems there. mount_afp has some options to control the permissions on mounted filesystems.
On 2020-04-08 12:05, George N. White III wrote:
CHeck that your "id" include the fuse group.
° I guess that means I need to add bobg to the fuse group. /n the past I would manage to muddle through using the user-group gui, now I am lost. I see commands like groupadd fuse but not sure of how to use them. Presently I see:
$ id uid=1000(bobg) gid=1000(bobg) groups=1000(bobg),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
Do I need to see "fuse" in the groupe there and how do I accomplish that? /
On Wed, 8 Apr 2020 at 15:54, Bob Goodwin bobgoodwin@fastmail.us wrote:
On 2020-04-08 12:05, George N. White III wrote:
CHeck that your "id" include the fuse group.
° I guess that means I need to add bobg to the fuse group. /n the past I would manage to muddle through using the user-group gui, now I am lost. I see commands like groupadd fuse but not sure of how to use them. Presently I see:
$ id uid=1000(bobg) gid=1000(bobg) groups=1000(bobg),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0. c1023
Do I need to see "fuse" in the groupe there and how do I accomplish that? /
It has been a while since I used afp, so things may have changed. First check that installing afp did create a fuse group and not something else (like "afp"), then use "usermod -a -G fuse" to add yourself to the fuse group.
On 2020-04-09 03:20, George N. White III wrote:
On Wed, 8 Apr 2020 at 15:54, Bob Goodwin <bobgoodwin@fastmail.us mailto:bobgoodwin@fastmail.us> wrote:
On 2020-04-08 12:05, George N. White III wrote: > CHeck that your "id" include the fuse group. ° I guess that means I need to add bobg to the fuse group. /n the past I would manage to muddle through using the user-group gui, now I am lost. I see commands like groupadd fuse but not sure of how to use them. Presently I see: $ id uid=1000(bobg) gid=1000(bobg) groups=1000(bobg),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0. c1023 Do I need to see "fuse" in the groupe there and how do I accomplish that? /It has been a while since I used afp, so things may have changed. First check that installing afp did create a fuse group and not something else (like "afp"), then use "usermod -a -G fuse" to add yourself to the fuse group.
There is no group "fuse" on the system.
[egreshko@f31k ~]$ grep fuse /etc/group [egreshko@f31k ~]$
On 2020-04-08 23:35, Bob Goodwin wrote:
bobg]# mount_afp afp://my_mycloud_username:12345678@192.168.2.202/aux /mnt/test Mounting 192.168.2.202 from aux on /mnt/test Login error: Authentication failed
Those user credentials work with the WD Mycloud browser page and provide access to the files, but I suspect not directly from the mycloud device, images must be downloaded and viewed, in my case with gthumb. It can take a minute or two to view one jpeg.
I am told that when an image is stored to the iCloud server it is removed from the iPhone camera leaving only a low resolution "thumbnail." Viewing a a high resolution image requires a connection to the iCloud. That explains some of the high bandwidth usage that I see, if true, what an awful scheme!
This all sounds as if you're not directly talking with the "device" when using the " WD Mycloud browser page".
What is the URL you use for the "browser page"?
Can you login to the "device" if you use http://192.168.2.202%C2%A0 ?
On Wed, 8 Apr 2020 at 17:14, Ed Greshko ed.greshko@greshko.com wrote:
On 2020-04-09 03:20, George N. White III wrote:
On Wed, 8 Apr 2020 at 15:54, Bob Goodwin <bobgoodwin@fastmail.us
mailto:bobgoodwin@fastmail.us> wrote:
On 2020-04-08 12:05, George N. White III wrote:
CHeck that your "id" include the fuse group.
° I guess that means I need to add bobg to the fuse group. /n the past I would manage to muddle through using the user-group gui, now I am lost. I see commands like groupadd fuse but not sure of how to use them. Presently I see:
$ id uid=1000(bobg) gid=1000(bobg) groups=1000(bobg),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0. c1023
Do I need to see "fuse" in the groupe there and how do I accomplish
that?
/
It has been a while since I used afp, so things may have changed. First check that installing afp did create a fuse group and not
something
else (like "afp"), then use "usermod -a -G fuse" to add yourself to the
fuse group.
There is no group "fuse" on the system.
[egreshko@f31k ~]$ grep fuse /etc/group [egreshko@f31k ~]$
Interesting. The URL https://sites.google.com/site/alexthepuffin/home given
in the dnf info page has examples, and says:
make sure that any user doing a mount is a member of the group 'fuse' so it can read and write to /dev/fuse
contrary to:
% ls -l /dev/fuse crw-rw-rw-. 1 root root 10, 229 Apr 7 09:43 /dev/fuse
On 2020-04-08 16:40, Ed Greshko wrote:
This all sounds as if you're not directly talking with the "device" when using the " WD Mycloud browser page".
What is the URL you use for the "browser page"?
Can you login to the "device" if you usehttp://192.168.2.202 ?
° $ grep fuse /etc/group fuse:x:1001:bobg
Login to: https://home.mycloud.com/sessions/new%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2... At ip: 192.168.2.202
Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE
On 2020-04-09 07:33, Bob Goodwin wrote:
On 2020-04-08 16:40, Ed Greshko wrote:
This all sounds as if you're not directly talking with the "device" when using the " WD Mycloud browser page".
What is the URL you use for the "browser page"?
Can you login to the "device" if you usehttp://192.168.2.202 ?
° $ grep fuse /etc/group fuse:x:1001:bobg
Login to: https://home.mycloud.com/sessions/new%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2... At ip: 192.168.2.202
But, what do you get when you use
Below is just information/thoughts without research on the "device" you've purchased.
You should do a "host home.mycloud.com" to see that is resolves to a set of IP addresses not in your home. You then login to a service that redirects and gets the file (I'm guessing here) from either their servers in the "cloud" or locally. Since you've indicated that some operations take minutes it would appear to me that the IOS devices are actually getting the data from "the cloud" and not your home.
I'm not sure if that "device" you have is "suitable" in a metered internet environment.
-
Bob Goodwin -
Ed Greshko -
George N. White III -
Tim -
Tim Evans