Appletalk most likely won't be bridged over the natted VM NIC, so you'll need to stick with the bridged interface.My atalkd.conf has this:
Code:
eth0 -dontroute -phase 2 -net 0-65534 -addr 65280.151
You'll probably want that to be your bridged interface.
The last changes I made to atalkd.conf specifically called out attaching to the eth1 interface (that's the bridged one) and I tried the "-phase 2" switch, but I didn't try specifying any specific -net or -addr settings.
Something else to help narrow things down a bit, atalkd handles the NBP (AppleTalk's name & service resolution protocol) registrations, so if it doesn't show up in chooser, start with the lowest levels. You can use the nbplkup commandline tool that comes with netatalk to do queries from the linux box, and see if the mac shows up.
Yeah, it looks like I'll have to do some serious sniffing to figure out what's up.
I have no problem using netatalk 2.2.4 that came with A2SERVER on older clients. Its designed to work with the ancient Apple II clients which aren't all that newer than System 6.
So, I guess I didn't mention it, but I did in fact download the A2SERVER prebuilt VM (I'd seen mention of it in the ongoing thread about the TCP/IP gating software) and tried running that and didn't have any luck with it either. (It was actually what was running when I did the first couple tcpdump tests that showed regular broadcasts from the Linux VM and only the brief little flurry of activity from the Mac while booting.) One thing that bugs me a little... the setup docs for that mention in passing a "Farallon Fix" which they claim can be turned on or off by running the "a2server-setup" command, but running said command on the version of the VM I downloaded does *nothing*. (Just returns straight to a prompt.) Googling has turned up no other mention of this "Farallon Fix", any idea what it is?
