Let's make a list of what we know:
- You have an AirPort Extreme for your wi-fi
- It has issued the 10.0.1.34 IP address to the Raspberry Pi 3 B+ (which has a Pi NoIR V2 camera module)
- OctoPi 0.15.0 and OctoPrint 1.3.8
- Hostname = octopi and username = pi
- ssh is running since you get a prompt
ssh firstname.lastname@example.org nor
ssh email@example.com seems to work from your Mac
http://10.0.1.34 gives you OctoPrint's interface
What we don't know:
- What does
arp -a |grep 34 show on your Mac? (In theory, it should be a single line which represents the MAC address of the wifi adapter on the Raspi)
- Did you try
ping octopi.local? If not, try that first and then see if the arp command now includes a line for it.
- What do you get on your Mac if you run either
ipconfig getpacket en0|grep lease or
ipconfig getpacket en1|grep lease? If the answer is
lease_time (uint32): 0x15180 then your Airport is giving out 24-hour leases, for what it's worth.
Mac's Airport Utility might allow you to see what's going on in the Airport's configuration. Here are their suggestions for getting that setup. It sounds like the Raspi is getting an IPv4 lease... only I'm not convinced that the Airport is doing its job as a Bonjour server for name resolution.
Make sure that on both the Airport and the Raspi, you've set the country of origin for the wifi. On the Raspi, this is at the bottom of the
/boot/octopi-wpa-supplicant.txt file. Not setting this correctly may prevent the Raspi from connecting well. Assume that the SSID value in this file is case-sensitive, btw.
This may be a name resolution issue. It could be server side (Airport), host side (Raspi) or client side (Mac). If you get really frustrated with this and
ping octopi.local fails it's certainly possible to either dedicate an IP address in the Airport or to manually set the IP address in the Raspi, followed by you manually editing your Mac's file with
sudo nano /private/etc/hosts.