Firewall Issues - ssh_dispatch_run_fatal errors during SSH

Why would we try to ping router couple of times a day? This thread is about SSH dispatch run and things are solved with 10.1 as were with B7. I am ok for two weeks for instance.

It might not be a bad idea you start a new thread with the broader problem you are describing, but please accept this issue is fixed no matter if as side effect or as particular fix. I am convinced Apple has worked on it as there was difference between B6 and 7.

Sorry you have troubles but looks you are crying on bad shoulder.

xpilotcz wrote:

Why would we try to ping router couple of times a day?

Because there's a difference between fixing a symptom and fixing a problem entirely. If you don't want to ping your router, don't do it. It's alright. You're not required to do that. You can also unsubscribe from this thread. But you don't need to push others to be like you. A subset of the people here, no matter how small or big, are interested in fixing a problem. You're now becoming part of the problem, and wasting my time responding to you and explaining that you're not required to do anything. Please step aside if you're not interested in helping. No hard feelings. I don't understand why you needed to make your comment. Just move on with your life!

Since I'm the original poster in this thread, I know quite well what the problem is, how to test if it's still there, and what kinds of things cause it to reoccur.

I don't understand why this give and take is even happening. You being the original poster of the issue does not give you any sort of authority. You're just some guy, like anyone of us, who noticed an issue and posted about it (and thank you for that, your efforts are highly appreciated). Sorry, buddy. Again, feel free to unsubscribe from this thread, and continue your wonderful life. I'm jealous you're this lucky, many are not. Now let's focus the discussion on more productive things.

mikeloiterman wrote:

Obviously, that isn't a long term fix, however.

Why not?

This is happening pretty consistently when using streaming tools across forwarded ports on SSH. I hit it when using MS Remote Desktop.

Same problem, kind of bad

ssh_dispatch_run_fatal: Connection to 172.16.5.131 port 22: Connection corrupted

Turning off "Limit IP address tracking" and disabling "Private Wi-Fi address" has not resolved the issue for me.

• Latest macOS on M1 Ultra Studio

Not sure if it's just me, but it seems like the speed of rsync via ssh also slowed down severely after the upgrade, even if I disabled the firewall.

Upgraded to 15.0.1. Bug still present. Turning off "Limit IP address tracking" seems to work. How ever did you figure that out?

(Nope—connection dropped after 20 minutes)

Nope—connection dropped the same way after 20 minutes.

yep.. i have to admit, slightly better than before

The issue still existed in 15.0, just less severe but it is there. Disabling the firewall will work for now as I don't feel like downgrading since it is working after that change.

15.0.1 does not fix for me.

Mine was set to Fixed. I am trying Off to see if it fixes.