Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I'm trying out the new Lion Developer Preview 4, and I'm noticing that afp wont work anymore. Apparently this is due to dhx2 is not activated and compiled and that the support for Time Machine won't work anymore.
http://trick77.com/2011/02/25/afp-broke … lion-10-7/
This can be fixed by using netatalk 2.2 instead. They have also fixed the Time Machine support in the later GIT builds.
http://comments.gmane.org/gmane.network … user/20910
Now I'm wondering if someone could create a package of 2.2 so that we will be able to use Lion when it ships?
It would be really appreciated!
There is a workaround at the moment, but that won't help Time Machine: http://www.alexanderwilde.com/2011/04/o … orkaround/
We should be careful with Netatalk 2.2-beta4... It has a fairly nasty performance bug: http://sourceforge.net/tracker/?func=de … tid=108642
Last edited by thebeck (2011-06-12 05:09:55)
Okay.. Is it possible for someone to just compile 2.1.5 or something like that with dhx2 enabled?
I was hoping Netatalk 2.2 was going to be released and stable by now so that we can take advantage of AFP 3.3, but unfortunately it's not quite ready due to a performance bug.
In any event, would it be possible to bring us up to Netatalk 2.1.5 with DHX2?
With Mac OS X Lion about to be released, it seems we'll need DHX2 for Time Machine to continue to work. Hopefully this is doable.
According to the netatalk website, I think we would need libgcrypt for DHX2, too (http://netatalk.sourceforge.net/2.1/htm … #id2213811). Is it possible to compile libgcrypt for ffp 0.5?
Thank you very much for your help!
Another Lion DP4 user. Absolutely need this update for my business. I'ved notice Synology has their NAS OS updated. Should be a simple thing to accomplish.
The main contributor of netatalk posted an open letter about the status of netatalk 2.2.0. It's already out as binary version, but the source hasn't been released yet:
http://www.netafp.com/open-letter-to-th … unity-501/
I hope he does so soon. If fonz could provide us with a new ffp package after the release, this would be great!
Just installed osx Lion — got the same problem when connecting to my D-link dns313 (Linux 2.6.15, ffp 0.5).
So, decided to recompile netatalk with uams_dhx2.so support. Here you are mine funplug packages:
libgpg-error-1.10-1.tgz (need for libgcrypt) — http://www.mediafire.com/?o563kdbuh76dwa2
libgcrypt-1.5.0-1.tgz (need for dhx2 suport) — http://www.mediafire.com/?7i4ksskeqqlmvpq
netatalk-2.2-beta4-1.tgz (it's beta!) — http://www.mediafire.com/?dd59eosoegj0kka
1. Save your /ffp/etc/netatalk/AppleVolumes.default and /ffp/etc/netatalk/afpd.conf
2. Uninstall old netatalk:
# funpkg -r netatalk
3. Install libgpg-error, libgcrypt, netatalk-2.2-beta
4. Add this line to /ffp/etc/netatalk/AppleVolumes.default (or use your old config):
5. Add this line to /ffp/etc/netatalk/afpd.conf:
- -tcp -noddp -uamlist uams_dhx2.so -nosavepassword
5. Restart afpd
# sh /ffp/start/afpd.sh restart
On the first connect it will hang for 1-2 minutes, updating /mnt/HD_a2/.AppleDB file, then Finder mounts the volume as usual. Looks like that:
PID PPID USER STAT VSZ %MEM %CPU COMMAND
32540 1321 root S 16344 26% 20% /ffp/sbin/cnid_dbd /mnt/HD_a2/.AppleDB 3 1 default log_note
32625 32613 afpd S 6616 11% 40% /ffp/sbin/afpd
32622 32613 afpd S 6548 10% 40% /ffp/sbin/afpd
Then cpu usage drops down to 0%.
Oh, and you can build netatalk yourself if you want stable 2.1.5 using this instruction.
+I have all ffp base packages installed (except mysql, lighttpd, old netatalk and extra-packages). Probably afpd needs something from there as well to run. At least I needed them to rebuild.
rr-m thank you so much for your help! I'll wait until netatalk is final, but it's really great that it seems clear that netatalk 2.2.0 will run on the DNS 323
Thank you so much for taking the time to compile netatalk 2.2.0-beta4. Are you aware that beta4 has a serious performance-related defect? (see http://netatalk.sourceforge.net/2.1/htm … #id2213811)
In any event, would you be able to compile the final version of netatalk 2.2.0 per the information provided by sushu?
It would be really great to get the final version of netatalk 2.2.0.
Thank you very much!
thebeck, yup, I know it's still beta and there can be bugs, but it works for me) Anyway, thanks for the warning.
Testing OSX Lion and netatalk-2.2-beta4 for couple of days — IMHO for now there's no difference in performance compared to the old netatalk-2.0.5 I used with OSX Snow Leo. My d-link dns313 is connected to the sluggish wi-fi router — making data transfers rather slow, so overall performance is not related to the netatalk release, you see)
That's not a problem to build 2.2.0 when it's ready for the public release, hope fonz will include it info ffp 0.5 extras.
By the way, fetched netatalk 2.1.5 source — and it can be build with uams_dhx2 support (=will work with Lion). And even old 2.0.5 can be compiled with dhx2 — just requires libgcrypt.
I see, the final 2.2.0-p3 source has not been published. I just re-read sushu's message and realized that. My bad.
Based on the netafp pricing page, I wonder if the source will ever be released. I am currently away on vacation, but when I return I will get your 2.2.0-beta4 up and running so that I can start testing it out.
That 2.2 beta 4 doesn't really work smoothly here with Snow Leopard on a DNS-323. I can't connect with my old username / password. Trying out some different configurations. How is this package different in configuration the the old one? (http://www.noulakaz.net/weblog/2009/11/ … e-dns-323/)
I don't use avahi at all, just afpd. Connecting with Finder->Go->Connect to server-> afp://192.168.5.2/Volume_1/ or afp://mem/
mem and 192.168.5.2 — my dns313 hostname and ip respectively.
Works with my old password, nothing changed there.
My config for now (played around a little):
- -tcp -noddp -uamlist uams_randnum.so,uams_dhx2.so -nosavepassword
/mnt/HD_a2 Volume_1 options:usedots,upriv
Hope this helps.
BTW, which version of netatalk worked for you with avahi? Let's try recompiling it (an old version) with dhx2 and give it a try with Lion?
I use 2.1.3 now. I don't know what the latest stable version is actually. Also haven't installed Lion yet, but wanted to prepare
Last edited by Frans (2011-07-08 13:45:48)
Oh, just realized you're still on Snow Leopard and I'm on Lion. Cannot check Leo compatibility..
Well it should work on both in best case scenario don't you think
Yep, got it. Okay, I'll try to build 2.1.3 + dhx2 ffp package. Will post here little later.
netatalk-2.1.3-1.tar.gz (with uams_dhx2.so) http://www.mediafire.com/?m94641pj2f55aqa
requires libgpg-error and libgcrypt posted above.
It simply must work with the old config) If it doesn't — Leo works badly with dhx2 auth and we need to think up another configs
Made a quick-check with Lion — works for me. Finder->Go->Connect to server->afp://mem/ asked my pass and mounted the volume without any probs.
Frans, at best 10.7.0 had to support an old dhx.so auth
I'd rather fix it on the server side. Seems like a downgrade or hack to change it in Lion. I'll test your 2.1.3. version on SL and prey it works on Lion as well Thanks!
It seems your updated 2.1.3. version reacts the same (as your 2.2) and I'm thinking that maybe I misunderstood you when you said "On the first connect it will hang for 1-2 minutes". It takes a while seeing the "Connecting" screen and then it indeed works: I can browse my shares fast! But when I disconnect and reconnect it takes that long again...
Last edited by Frans (2011-07-08 16:34:04)
Correct, it hangs for a while when connecting, then works as usual — can also see this. Any ideas why?
Also, re-enabled dhx in Lion and checked old netatalk-2.1.3 with uams_dhx.so only — works fast, connects fast as before.
So no solution for the slow connecting problem? Can't really understand if you experience the same problem.
Dunno, need to read logs and goooooogle the net, as usual) Generally I don't need to disconnect every minute, so after it's connected it's okay. For now I'll stop on using re-enabled dhx I think, it connects fast and I'm already tired reinstalling packages