Installing/restoring AppleTalk on System 7.0.1

[xantufrog]

Solved!

Firstly, a huge thanks to you for helping me get oriented, and to RADmark on the piscsi Discord for helping me across the finish line.

For those who read the thread above, I think I would summarize the solution as follows:

Mac configuration in System 7.0.1 that works concurrently with the Pi emulating a Daynaport Ethernet:
MacTCP setting: see post #24
Network control panel setting: see post #24

Pi AFP configuration:
1) use easyinstall.sh to set up network bridge for wifi or wired as desired (I had done this prior to this thread)
2) use easyinstall.sh to set up AFP sharing
3) since my same Pi is running BOTH the Daynaport Ethernet emulation and the Netatalk you have go edit atalkd.conf to specify "piscsi_bridge" at the bottom
4) you then must launch the Netatalk demons with:
$ sudo systemctl enable atalkd.service afpd.service cnid.service
$ sudo systemctl start atalkd.service afpd.service cnid.service
5) Type nbplkup and you should see your Mac AND raspberrypi:AFPServer (or [nameofyourpi]:AFPServer to be more general)
6) for some reason mine didn't show the AFP (but did show the Mac), but simply restarting with
$sudo systemctl restart afpd
Fixed this.

You can see 4-6 in my terminal history image below (managing the Pi from the Mac itself over Telnet!)

Like magic, the Mac finds the server in Chooser. Let the data sharing commence

 

[tuf]

Hey trying to do exactly this. I've got bridging established, so the Mac can surf using Netscape, etc. I've also got Netatalk installed - my modern Mac can see it.

My problem is I'm still not able to see anything pop up in the chooser on the SE. My nbplkup only shows the piscsi services; nothing from the SE is showing up.

I suspect some sort of networking issue but can't figure it out. I've added piscsi_bridge to the conf file with no change.

I'm using the piscsi on a wifi network if that makes any difference. I could just as well plug it in which I might try a little later on and test.

Kinda stuck - but your post above is the best info I've found!

 

[Mk.558]

If you are using WiFi, then what could be happening is DDP isn't being passed through because of a well-known issue with EtherTalk frames.

What is the technical reason why DDP AppleTalk doesn't work with WiFi?

It is common knowledge that one can't natively use the AppleTalk protocol (also known as DDP) over WiFi. The notable exception is very early access points, particularly Apple's AirPort series, had special packet handling to allow it to work. When WiFi became popular, AppleTalk printers were...

68kmla.org

I'm not familiar with the PiSCSI, but if it has a RJ45 Ethernet jack, I'd recommend using that instead. A similar problem exists with the BlueSCSI WiFi mode: issues with it are somewhat frequent.