WombatPredator
Member
I wanted to mention that I just found this thread, uttered a very loud "OMG YES" and woke up a small child in the process. I'm so happy you did all this work. Thank you.
You are very welcome! I'm glad that this is helpful for you. Did the child go to sleep again?I wanted to mention that I just found this thread, uttered a very loud "OMG YES" and woke up a small child in the process. I'm so happy you did all this work. Thank you.
I lulled the child back to sleep with tales of the atalkd and afpd daemons that, once again, were whispering in the wires all through the house. Tomorrow, I'll tell the tale of papd who makes machines vomit paper. Always a favorite, that one.You are very welcome! I'm glad that this is helpful for you. Did the child go to sleep again?
- -ddp -tcp -uamlist uams_guest.so,uams_clrtxt.so,uams_randnum.so,uams_dhx.so,uams_dhx2.so
# disable DHX (DHCAST128) on Raspberry Pi, which refuses uams if the config string is too long
- -ddp -tcp -uamlist uams_guest.so,uams_clrtxt.so,uams_randnum.so,uams_dhx2.so
enp0s3 -router -phase 2 -net 1 -zone "My Zone"
Thank you. I made the chance but to no avail.Make sure atalkd is configured with the -router switch if you don't have any other routers (ex: Shiva Fastpath) on the network. I've had issues with netatalk on networks without a seed router or zone configured.
Example atalkd.conf
Code:enp0s3 -router -phase 2 -net 1 -zone "My Zone"
Substitute "enp0s3" with the correct Ethernet device name for your system.
macippi:TimeLord 65280.11:132
MacIPpi:AFPServer 65280.11:129
172.16.2.1:IPGATEWAY 65280.11:72
MacIPpi:netatalk 65280.11:4
MacIPpi:Workstation 65280.11:4
Hooper:ARA - Personal Server 65280.119:2
Hooper:Multi-User Client 65280.119:48
Hooper: Macintosh PowerBook 65280.119:252
Hooper:Workstation 65280.119:4
ubuntu:ProDOS16 Image 65280.179:3
ubuntu:Apple //e Boot 65280.179:3
ubuntu:Apple //gs 65280.179:3
ubuntu:TimeLord 65280.179:129
Netatalk:AFPServer 65280.179:128
I'll double check, thanks. The MacIPRpi doesn't have anything in its atalkd.conf file but maybe the default is -router. I'll take a look.Make sure only one of the machines has the "-router" switch in atalkd.conf. Looks like you have a seed router clash, a common problem with Appletalk.
In my MacIPRpi project I try to do things not to complicated. My goal is always for a user to start the Pi and use evrything without any configuration.I'll double check, thanks. The MacIPRpi doesn't have anything in its atalkd.conf file but maybe the default is -router. I'll take a look.
18:39:33.933608 AT 65280.65.253 > 0.nis: nbp-lkup 2: "virtquadra: Macintosh@*"
18:39:34.052149 AT 65280.65.253 > 0.nis: nbp-lkup 2: "virtquadra: Macintosh@*"
18:39:34.160021 AT 65280.65.253 > 0.nis: nbp-lkup 2: "virtquadra: Macintosh@*"
18:39:37.128791 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*"
18:39:37.964517 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*"
18:39:38.822588 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*"
18:39:39.686038 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*"
18:39:47.371449 AT 65280.65.nis > 0.nis: nbp-lkup 4: "=:IPGATEWAY@*"
18:39:47.382667 AT 65280.239.nis > 65280.65.nis: nbp-reply 4: "172.16.2.1:IPGAT EWAY@*"(0) 72
18:39:47.414037 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*"
18:39:48.251150 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*"
18:39:49.090926 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*"
18:39:49.924194 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*"
18:40:01.577924 AT 65280.239.nis > 0.nis: nbp-lkup 1: "=:=@*" [addr=65280.239.130]
18:40:01.584062 AT 65280.65.nis > 65280.239.130: nbp-reply 1: "172.16.2.5:IPADDRESS@*"(0) 72 "virtquadra:AFPServer@*"(0) 251 "virtquadra: Macintosh@*"(0) 252 "virtquadra:Workstation@*"(0) 4
18:40:01.584507 AT 65421.175.nis > 65280.239.130: nbp-reply 1: "Asant▒Talk 94081D2A:Asant▒Talk@*" 252
18:40:01.584874 AT 65403.247.nis > 65280.239.130: nbp-reply 1: "Asant▒Talk 940863E7:Asant▒Talk@*" 252
Yes, atalkd will try to be helpful and attempt to detect the topology of your network and dynamically alter its settings. So it makes sense that if you have two instances of Netatalk running in the same subnet in routerless mode you'll get a conflict there...I'll double check, thanks. The MacIPRpi doesn't have anything in its atalkd.conf file but maybe the default is -router. I'll take a look.
Thank you so much for taking the time to respond. I'll look into this. And thank you for MacIPRpi - it's been in constant use for months and it's wonderful.In my MacIPRpi project I try to do things not to complicated. My goal is always for a user to start the Pi and use evrything without any configuration.
If you just have a simple network with old Macintosh, MacBooks or Windows machines the MacIPRpi is in the middle. So no special atalkd.conf. You can connect with all kind of protocols to it. When you are running more complicated setup, with more Netatalk instances you can have problems. Also with boxes like the AsantéTalk. They sometimes show up, they sometimes don't. (if you reboot them they will probably show up).
I have seen these problems too. A machine that is seen by one computer, but not by others. Sometimes it helps just to restart, trow away AppleTalk prep, these things. But I can be also in the network.
On the MacIPRpi you can use some tools to dig into this more deeply, like tcpdump:
18:39:33.933608 AT 65280.65.253 > 0.nis: nbp-lkup 2: "virtquadra: Macintosh@*" 18:39:34.052149 AT 65280.65.253 > 0.nis: nbp-lkup 2: "virtquadra: Macintosh@*" 18:39:34.160021 AT 65280.65.253 > 0.nis: nbp-lkup 2: "virtquadra: Macintosh@*" 18:39:37.128791 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*" 18:39:37.964517 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*" 18:39:38.822588 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*" 18:39:39.686038 AT 65280.65.253 > 0.nis: nbp-lkup 3: "virtquadra:AFPServer@*" 18:39:47.371449 AT 65280.65.nis > 0.nis: nbp-lkup 4: "=:IPGATEWAY@*" 18:39:47.382667 AT 65280.239.nis > 65280.65.nis: nbp-reply 4: "172.16.2.1:IPGAT EWAY@*"(0) 72 18:39:47.414037 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*" 18:39:48.251150 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*" 18:39:49.090926 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*" 18:39:49.924194 AT 65280.65.nis > 0.nis: nbp-lkup 5: "172.16.2.5:IPADDRESS@*" 18:40:01.577924 AT 65280.239.nis > 0.nis: nbp-lkup 1: "=:=@*" [addr=65280.239.130] 18:40:01.584062 AT 65280.65.nis > 65280.239.130: nbp-reply 1: "172.16.2.5:IPADDRESS@*"(0) 72 "virtquadra:AFPServer@*"(0) 251 "virtquadra: Macintosh@*"(0) 252 "virtquadra:Workstation@*"(0) 4 18:40:01.584507 AT 65421.175.nis > 65280.239.130: nbp-reply 1: "Asant▒Talk 94081D2A:Asant▒Talk@*" 252 18:40:01.584874 AT 65403.247.nis > 65280.239.130: nbp-reply 1: "Asant▒Talk 940863E7:Asant▒Talk@*" 252
Indeed, this is my plan B. My plan A is still to try to convince Netatalk maintainers to merge all the patches and cut an upstream 2.2.7 release for us, and then pivot to using that with RaSCSI.@slipperygrey are you intending to switch the netatalk version to your fork in the RaSCSI easy_install.sh (I guess once you've cut a new release)?
That sounds awesome! How about throwing in Macproxy for the trifecta?Indeed, this is my plan B. My plan A is still to try to convince Netatalk maintainers to merge all the patches and cut an upstream 2.2.7 release for us, and then pivot to using that with RaSCSI.
Vomit indeed (there is evidence of debugging papd with the Apple IIgs scattered around here).....
By default A2SERVER scripts setup the UAMs as follows:
Code:- -ddp -tcp -uamlist uams_guest.so,uams_clrtxt.so,uams_randnum.so,uams_dhx.so,uams_dhx2.so
If the setup script detects a RPi, it turns off DHX because of some weird string length bug.
Code:# disable DHX (DHCAST128) on Raspberry Pi, which refuses uams if the config string is too long - -ddp -tcp -uamlist uams_guest.so,uams_clrtxt.so,uams_randnum.so,uams_dhx2.so
I haven't had any problem logging on from OS X, but I haven't tried both an older client and a new one at the same time.
Macproxy is already (lightly) integrated with RaSCSI, and can be installed through the RaSCSI easyinstall.sh script. Or did you mean something else?That sounds awesome! How about throwing in Macproxy for the trifecta?