My OSX 10.8 machine can no longer reach several machines on my home network's internal IP range. For example, I have an internal server which is also NAT'd through the router to accept SSH. The server is at

~$ ssh -v
OpenSSH_5.9p1, OpenSSL 0.9.8x 10 May 2012
debug1: Reading configuration data /Users/jakes/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to [] port 22.
debug1: connect to address port 22: Host is down
ssh: connect to host port 22: Host is down
~$ ssh myDynDNSDomainToTheSameMachine
jakes@myDynDNSDomainToTheSameMachine's password:

The same thing happens if I try to RDP to another machine -- similar setup. RDP to it's internal IP does not work. RDP to my dynDNS domain works fine.

It CAN connect however to the router and wireless access point IP addresses over http: and

Connection from other machines (including IOS devices) internally to other internal IP addresses works fine, it's just this OSX machine that has started to show this issue.

Can anyone offer any suggestions to troubleshoot?

EDIT: I found that I'm getting incomplete ARP entries:

~$ arp -a
? ( at c0:c1:c0:65:c2:0 on en1 ifscope [ethernet]
homedesk ( at 0:22:5f:2b:d:4c on en1 ifscope [ethernet]
raspberrypi ( at (incomplete) on en1 ifscope [ethernet]
my-ipad-2 ( at 1c:ab:a7:94:42:54 on en1 ifscope [ethernet]
home ( at b0:e7:54:3d:c2:e9 on en1 ifscope [ethernet]
? ( at ff:ff:ff:ff:ff:ff on en1 ifscope [ethernet]

Is that a problem on the OSX machine, the raspberrypi, or the router?

  • is used by Linksystem routers. Is that the only 10.8 you have ?
    – Ruskes
    Jul 7, 2013 at 3:46
  • Yes, it's the only OSX machine I have. Jul 7, 2013 at 12:25
  • Are you able to ssh into your raspy wired directly?
    – MnO
    Jul 9, 2013 at 10:04
  • Yes, once I hooked the laptop to my wap (a router set to "bridge only" mode). I rebooted the wap and it all worked. Guess it had nothing to do with OSX after all. Jul 11, 2013 at 14:57

1 Answer 1


I hooked my laptop up to my WAP, which was a linksys router set to be "bridge-only" mode and should not be doing any actual routing. With this, I was able to reach the internal IPs without issue.

So I rebooted the WAP and the problem cleared up. I guess it had nothing to do with OSX/Apple after all, and just a bug in the linksys bridge-only code.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .