So here’s a fun macOS weirdness I ran into this weekend where I couldn’t connect to a port on another machine from a shell session inside of iTerm, even though I was able to ssh to other hosts.
I wanted to experiment with Talos so I stood up a Talos VM in my homelab proxmox cluster. I happened to be doing the setup steps from a jump VM in the cluster.
Initial setup worked fine. Then I decided to try and run some talosctl commands from my M3Book Air, and it gave me a no route to host error. I could ping the VM just fine from the M3Book, and I confirmed the proxmox firewall was turned off for the talos VM. The laptop was on the same /24 as the VMs (both the jump and the talos one).
I wanted to confirm that it was reachable from a machine that was…
So here’s a fun macOS weirdness I ran into this weekend where I couldn’t connect to a port on another machine from a shell session inside of iTerm, even though I was able to ssh to other hosts.
I wanted to experiment with Talos so I stood up a Talos VM in my homelab proxmox cluster. I happened to be doing the setup steps from a jump VM in the cluster.
Initial setup worked fine. Then I decided to try and run some talosctl commands from my M3Book Air, and it gave me a no route to host error. I could ping the VM just fine from the M3Book, and I confirmed the proxmox firewall was turned off for the talos VM. The laptop was on the same /24 as the VMs (both the jump and the talos one).
I wanted to confirm that it was reachable from a machine that wasn’t hosted on the proxmox cluster, so I tried running talosctl on one of my Raspberry PIs, and there were no issues.
Then I tried running talosctl from Terminal on the M3Book instead of iTerm, and it worked! WTF!
Looked in System Settings -> Privacy & Security -> Local Network, and iTerm did have that permission enabled. Turned Local Network off for iTerm, quit iTerm, turned it back on and restarted iTerm. Suddenly talosctl worked from inside an iTerm window.