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:
You'll probably want that to be your bridged interface.
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.
Once the netatalk machine shows up in the Chooser on the mac, then it's talking to afpd.
"tcpdump -i eth1 -s0 -X atalk" on the OSX machine and on linux might help narrow down where things are going wrong.
Another issue, although it doesn't sound like it's what you're encountering yet, is netatalk 2.2.1 has a bug where afpd crashes when a ddp client connects. So you'll want to update to something newer, not just rebuild 2.2.1. But since it's not showing up in the chooser, this doesn't sound like the bug you're encountering yet.
FWIW, I'm using a similar setup with netatalk in a linux VM on 10.6, but I'm only using a single bridged interface.
My atalkd.conf has this:
Code:
eth0 -dontroute -phase 2 -net 0-65534 -addr 65280.151
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.
Once the netatalk machine shows up in the Chooser on the mac, then it's talking to afpd.
"tcpdump -i eth1 -s0 -X atalk" on the OSX machine and on linux might help narrow down where things are going wrong.
Another issue, although it doesn't sound like it's what you're encountering yet, is netatalk 2.2.1 has a bug where afpd crashes when a ddp client connects. So you'll want to update to something newer, not just rebuild 2.2.1. But since it's not showing up in the chooser, this doesn't sound like the bug you're encountering yet.
FWIW, I'm using a similar setup with netatalk in a linux VM on 10.6, but I'm only using a single bridged interface.