A little more data: I turned off the OneMesh routers and had the same problem. It appears to be related to the fact that CPU #1 is a Linux machine on x86 and CPU #2 is a Raspberry Pi.

I noticed the Pi had a static IP configured, but I changed it to use DHCP and still does not work. I did notice that it now shows up in the client list, though and the static IP was reserved previously. 

Keep in mind, the same set up worked with no issues with an A7, so I don't think it is some horrible misconfigure of the Pi, firewall, upstream router, etc. Especially given that it works just fine with CPU #1.

  @wd5gnr 

Raspberry Pis OSs often do not enable SSH by default.  Google how to enable it.  It usually just involves adding a text file to the SD card and rebooting.

SORRY, missed where you were able to SSH to Pi locally.  

However, port 225 is a reserved port and your new router may be filtering it.  222 is not reserved so it is not being filtered.  Try using ports in the range of 49152–65535, the Dynamic, private or ephemeral ports, to avoid using an IANA reserved port or one that could be eventually be reserved.  I would try 49222 and 49225.

Good luck.

  @pcuttle Thanks. What I found is that the Mesh repeaters don't understand when a new IP is reserved. So the Pi was getting an old IP address and would not release until the repeater was rebooted.