

the man page for rvice(5)) is pretty minimal on that front. My best guess as to the solution is that I would create an Avahi service file, but the Avahi documentation (e.g.
#Rpi configure netatalk Pc
While I'm bearish on being able to use the first-party macOS VNC client, I'm bullish on what other possibilities might be opened up if the Debian PC (which presents itself as an iMac) were to present itself as having VNC Remote Access. How can I have the Avahi daemon on my Debian PC advertise VNC Remote Access? To reiterate my question with all this background:
#Rpi configure netatalk mac
Which might give me some useful information, but % dns-sd -Bĭoesn't show the Mac Mini, and trying to browse for "VNC Remote Access": % dns-sd -B "VNC Remote Access"ĭoesn't work, so that seems like a dead end. I know I can do the following with dns-sd on my Mac: % dns-sd -B (My MacBook doesn't show up because it doesn't have Screen Sharing enabled.) = enp3s0 IPv6 Mac Mini VNC Remote Access localĪnd = enp3s0 IPv4 Mac Mini VNC Remote Access local + enp3s0 IPv4 Mac Mini VNC Remote Access local On the Debian PC, the output includes the following: + enp3s0 IPv6 Mac Mini VNC Remote Access local When I run the command $ avahi-browse -all -ignore-local -resolve -terminate The reason I use Screens is that the authentication protocol for GNOME's default VNC server is not compatible with the first-party macOS VNC client. It's unclear whether or not Screens uses Bonjour (Avahi) in addition to its own handshake service, Screens Connect (which does not support Linux), for "Nearby and Remote Computers", but it seems potentially relevant here. In the third-party application Screens, the "Nearby and Remote Computers" shows "Kandinsky" (an older Mac Mini that's actually offline) as well as the current Mac Mini.


Note that in the past I have used CIFS/SMB shares instead of AFP/Netatalk, and that worked just as well. The connection is authenticated as the remote local username, and I only see the Netatalk (AFP) shares. When I click on the Debian PC ("Alpha") in the Finder sidebar, I see the following: When I click "Share Screen.", a VNC connection to the Mac Mini opens in the first-party macOS VNC client. The connection is authenticated as my Apple ID, and in addition to the AFP shares there is a button labeled "Share Screen." When I click on the Mac Mini in the Finder sidebar, I see the following: I currently have Avahi set up on the Debian PC along with Netatalk, advertising the PC as an iMac. A static IP is not necessary but useful for the future so you don't have to guess the IP address when connecting to the RPi.I have a home network with two Macs and a PC running Debian (and possible other distros in the future).
#Rpi configure netatalk update
Update the /etc/wpa_supplicant/wpa_nf file with your WiFi information, update network details to assign a static IP address similar to the following. Note2: Wherever you see a 'Commands' listing, type those commands into the RPi as shown. Note1: Wherever you see file contents listed without further instructions, simply copy/paste what's shown into the file specified. wheezy-minibian-wifi.img.Įject the SD card, which now has the Minibian-wifi image, insert it into your Raspberry Pi, power on and let it boot up.Įverything that follows must be done on the RPi as the 'root' user. Using ApplePi-Baker run the 'Restore Backup' for the Minibian-wifi image e.g.
