[Solved] Permissions issue with AFPD and Shares

Installing and Using OpenWrt
1

I was attempting to fix some permissions issues I was having with transmission and in the process I broke the permissions for AFPD. Right now I have this on my backups folder:

root@LEDE:/mnt/sda1# ls -l
drwxrwxr-x    3 john staff         4096 Feb 19 08:18 Backups

But whenever I connect to the share under user john (which I can do successfully), see the Backups folder, and try to connect to it, my macOS displays:

the operation cannot be completed because the original item for "Backups" can't be found

Anyone know what the proper permissions should be?

2

Can you access the directory from SSH?

3

Yes, logged in as root

4

Sounds like the problem is on the MacOS side...

5

I tried that and it didn't work.

I used to be able to access this share before I changed the group of Backups to "staff". Note that John is in the "staff" group. So is it a permissions chmod issue?

6

If you can SSH in as John and get access, it's on the MacOS side.

It seems that the MacOS side is still looking for Backups.

Otherwise, SSH in as root, check the permissions for staff and set them accordingly.

7

Hmm I can't ssh in as john since I don't think I gave john that permission.

I thought files/foldes have permissions, not groups. Can you explain? Backups has 775 on it drwxrwxr-x so I thought that should be enough especially if Backups is owned by john.

8
9

The users in staff...

10 
id john
uid=1000(john) gid=100(staff) groups=100(staff),100(staff)

I just tried chmod 777 to the Backups folder and I still get the same error, so maybe it isn't a permissions issue after all...

11

Does anyone know what happened to this guide:

https://openwrt.org/docs/user-guide/netatalk_configuration

It's no longer available and I followed that when I set up my server.

12

Netatalk's guide...

http://netatalk.sourceforge.net/3.1/htmldocs/configuration.html

13

Did you know that the wiki has a search function?

https://openwrt.org/start?do=search&id=netatalk

14

Yup, fixed it. It was an issue with /etc/afp.conf

Thanks!