SSH sessions getting mangled?

Seeing some strange behavior and I'm not sure if it's with my pfsense routing table rules dropping packets, or if my Firewalla Blue might be causing the issue. Just wanted to post here and see if anyone else is seeing this behavior, and/or if this is a known issue. My general network layout is that I have a pfsense firewall, Firewalla Blue setup in DHCP mode and set to hand out IP's for devices in the 192.168.x.x subnet. However I also have some devices assigned static IP's in 10.x.x.x. I had to create some routing rules* in pfsense to get traffic routing around correctly however when I try to ssh from a machine outside the firewalla subnet to inside that subnet, the session will die after about 30 seconds (while actively doing stuff, not just idle). The most recent attempt I was able to get the following error back from the session: "packet_write_wait: Connection to 192.168.x.x port 22: Broken pipe". However when I ssh the other direction (192.168.x.x -> 10.x.x.x) the session stays up.  I've looked over my pfsense rules and don't see anything jumping out at me as to why everything else (including multicast, for chromecast devices and plex) is able to connect over the two subnets, but ssh traffic going to the firewalla ip space is getting messed up. Then again it's possible the other traffic might also be similarly affected but it just far more apparent with SSH. Thoughts? 

*(I have the external firewalla IP address flagged as a gateway and then a static route to send all 192.168.x.x traffic inside the lan to that gateway IP address, plus some some specific rules to also allow multicast traffic to move correctly as well.)