Below is an example config file to be adjusted based on your needs.Internet access is kept safe and secure with a combination of their own NAS domain support and simply requires you to create a free account and to link your NAS with that account for the first time. "nano /etc/netatalk/afp.conf" to create the configuration file. "apt install netatalk" to install all the necessary packagesĢ. Let's assume you have a running OMV5 with existing shared folder(s) with the correct access rights. The good news is that the installation is so simple the lack of a plug-in is no big deal. Even then, the SMB performance is about half the speed of Netatalk (30 vs 60 MB/s).įor that reason, I've decided to install Netatalk manually. I've turned off the SMB encryption to help the CPU. I run OMV5 on an ancient armel NAS that still does the job. Other examples that document the lack of performance found on serverfault, reddit (discussion about jumbo frames), and many others that can be found on the net. What I tried to speed up that process so far is described here. I would say in contrast to performance, icons and special characters are a niche requirement. Meanwhile: WastlJ, as I read you are an Apple user as well, do you know of such issues and maybe have a solution for that? Especially the lack in performance is a showstopper in my case. I'll place a pull request at the links you mentioned before, in hope Volker will port that beautiful afp Plugin, although it is officially deprecated by Apple. As this seems to be no option yet, I feel forced to downgrade to OMV4 again, which means a complete reinstall of a setup that ran for years now (the iMac is the new machine, I had an afp share in OMV4 running with a MBP before for a long term without any issues). This makes me to try to install afp/netatalk on OMV5. As far as I could research on this slow loading of network shares via smb it is due to caching behavior of OS X up to now. Navigating to the top level folder after connecting to the smb service, it now takes about 3-4 minutes to list the content (one single subfolder!!!!) as the implementation of the smb protocol still sucks hard at OS X (10.15.4 here, on a 2019 iMac). I am a bit surprised that no one here mentioned the poor performance that is forced to come into our apple world when using smb instead of afp.įor example: I have a simple folder with a subfolder that contains two folders and a photos library. I left AFP enabled for my Time Machine share, but that won't be necessary anymore after upgrading to OMV 5 as I understood. I also stopped and disabled nmbd just to be sure, since I'm not sure if disable netbios = yes is accepted: Socket options = TCP_NODELAY IPTOS_LOWDELAYįruit:wipe_intentionally_left_blank_rfork = yes I disabled "Browsable" under the SMB/CIFS Home Directory settings and added the following to the Advanced Settings text field part (in bold): I've got the icon part sorted by adding an extra service section to /usr/share/openmediavault/mkconf/avahiservices.d/smb (to make it stick after config updates):Īnd then modifying the SMB/CIFS service discovery item in the OMV 4 webUI under Network -> Service Discovery to reflect the same name as the AFP name (Home Server in my case). Somehow Apple managed to change this behavior if you share via SMB on a Mac (SMB shares look the same as when using AFP and no extra computer icon), does somebody know how to mimic this behavior? That would only leave the nice icons to be desired. It allows me to set a nice icon (using the advanced settings) in the finder and only shows just one icon in the finder instead of a blue screen computer icon next to all the separate shares (see screenshots). I'm a Mac user too and really would like to stay using the AFP plugin. I would guess most users don't put all those special characters in filenames or have super long filenames.įeel free to port the plugin to OMV 5.x. You can't even use afp on apfs formatted volumes. afp is deprecated (yes, I know you can still use it but you should transitioning off it). If you copy those files over smb, you will lose those informations and the file will be around 0KB in size!!! Some programs and files like "oldstyle" fonts still uses the advantages of data- and programforks. If you want to hide file towards SMB, just use any special character and it will be invisible!!! SMB will not use those characters and in SMB and CIFS you are restricted in 256 characters where the description of the filepath must be included in counting! AFP is preferred and recommended by everyone who ever used MacOS and OSX, cause you can and you will use special characters like " : / \ '"" ? * # " in filenames!
0 Comments
Leave a Reply. |