Firewall Issues - ssh_dispatch_run_fatal errors during SSH

Just upgraded to Sequoia and noticed a lot of issues with the firewall while using ssh.


After ssh'ing into a local server on my network, after a few minutes I get this error:


Bad packet length 2489765067.

ssh_dispatch_run_fatal: Connection to 192.168.30.2 port 22: Connection corrupted


I can trigger it by ssh'ing into pretty much any server or computer on my network and then executing a command like:


ping google.com


within 10 - 30 seconds, the connection drops.


Happens with IPv4 and IPv6. Happens with Terminal and iTerm apps.


Disabling the firewall fixes the issue. In this case, my Mac is running statically in my local network and safely behind an upstream firewall. So, it's annoying to have to disable the firewall every time I have to ssh in anywhere, but not the end of the world. Obviously, that isn't a long term fix, however.


Anyone else seeing similar?

Mac Studio

Posted on Sep 17, 2024 6:35 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 6, 2024 6:28 PM

Whilst this is true that Apple cannot fix the problem caused by others, however, this issue should not be ignored. MacOS 15.0.x borks TCP connections. See Little Snitch blog about Sequoia on TCP, Firewall issues https://obdev.at/blog/should-i-upgrade-to-macos-sequoia-now/


Disabling all third-party Network Filters will alleviate the issue temporarily (until, hopefully a fix on 15.1). macOS Firewall set to **block** all incoming connections (with the exception of some internal processes) works for me as well (you can set this to allow all and fine-tune the setting per third-party application).


As for VPN, well, I use Firefox connected to VPN via Windscribe and it works, so far so good. I have yet to run a VPN for all network connections, perhaps I will do this soon to test.


MacOS 15.0 is new, let's give Apple time to fix it -- also hoping that beta testers report this bug. As for us, let's continue filing bug reports, the more, the better, so Apple gets to prioritize it.


For the meantime, if you are from corporate IT, it is your responsibility to evaluate and certify new software before your users are allowed to download and install it. And if a user installs Sequoia, knowing that there is this bug AND if it is mission critical, then get them to revert back to macOS 14. :)


78 replies

Oct 30, 2024 5:49 AM in response to mikeloiterman

For those who are still facing connectivity issues (and can prove it with pings, like I showed), turning off the firewall still helps most of the time. I'm hoping that Apple will continue debugging my ticket in Feedback Assistant, but I'm losing hope over time. If you face this issue, please create a ticket in the Feedback Assistant too, and explain that this issue can be a subset of this post.

Oct 30, 2024 5:37 AM in response to mikeloiterman

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.

Oct 30, 2024 5:27 AM in response to SamWantsYouToChill

This depends on whether the issue got completely fixed or just improved. It seems that many people here are reluctant to do the ping tests multiple times per day to see these spikes I talk about. Note that disabling the firewall *improves* these spikes, it doesn't remove them completely. Meaning: The issue you're claiming was fixed in 15.1 is just a symptom of a bigger problem. Congratulations to you, since you seem to have a setup, for which this is working for you. But I do implore those who have things working for them to be more understanding and not dismiss the bigger issue for those who have a more complex setup. I have all kinds of friends and colleagues that are facing networking problems in different severities, ranging from once per month blocked networking to every day.

In summary: If you want to check whether the issue is fixed, ping your router every few hours, and if you have zero spikes in response time (whether small or big), then the issue is fixed for you. If the spikes become so large that they lead to timeouts, then you'll face all the problems everyone talked about in this post, including ssh disconnections, internet lags and connectivity problems, etc.


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.


15.1 fixes the issue that started this thread.


Your decision to lump other issues into this discussion only serves to confuse yourself and others.

Oct 30, 2024 12:16 AM in response to xpilotcz

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!

Oct 30, 2024 12:01 AM in response to SamWantsYouToChill

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.

Oct 29, 2024 11:05 PM in response to mikeloiterman

mikeloiterman wrote:

15.1 fixes the issue that started this thread. Firewall is now enabled and I have no ssh disconnection issues.

This depends on whether the issue got completely fixed or just improved. It seems that many people here are reluctant to do the ping tests multiple times per day to see these spikes I talk about. Note that disabling the firewall *improves* these spikes, it doesn't remove them completely. Meaning: The issue you're claiming was fixed in 15.1 is just a symptom of a bigger problem. Congratulations to you, since you seem to have a setup, for which this is working for you. But I do implore those who have things working for them to be more understanding and not dismiss the bigger issue for those who have a more complex setup. I have all kinds of friends and colleagues that are facing networking problems in different severities, ranging from once per month blocked networking to every day.


In summary: If you want to check whether the issue is fixed, ping your router every few hours, and if you have zero spikes in response time (whether small or big), then the issue is fixed for you. If the spikes become so large that they lead to timeouts, then you'll face all the problems everyone talked about in this post, including ssh disconnections, internet lags and connectivity problems, etc.

Oct 29, 2024 1:46 PM in response to mikeloiterman

Quick update, I am member of an large company internal mailing list where we've been discussing this extensively. The new 15.1 does seem to improve the performance relative to this problem; but does NOT fix it. People are seeing issues over time that seem to mimic the existing behavior that's been problematic. I have more or less decided NOT to upgrade to 15 unless/until forced by my company; and for personal and stage use ( I work on traveling shows ) we will definitely NOT be upgrading until this issue is dealt with.


Love you Apple.. you know I do given how much buyin I have; but this is the line. We really REALLY need to hear this will be addressed long term. If I can't trust the system to have consistent networking on a closed network on stage moving low-mid level traffic .. I will have to move to other solutions. Thanks in advance

Oct 29, 2024 1:04 PM in response to unitof

Let us know if 15.1 "fixed" the issue for you.


For me, I no longer see " ssh_dispatch_run_fatal errors during SSH" errors. I have been SSH'd to my Linux server for the past hour and no ssh issues. Network packet drops is another issue all together, IMHO.


And as I have posted earlier - disabling Network Filters (Little Snitch), keeping the built-in firewall ON, Limit IP address to ON and Private WiFi to OFF worked for me prior to 15.1.



Oct 29, 2024 12:02 PM in response to mikeloiterman

Updated to 15.1 and this has mitigated the issues quite a bit (i havent noticed it yet today).


On 15.0.x I would get SSH errors every few minutes in chrome (very obvious with the ERR_SSL_PROTOCOL_ERROR) - and have not experienced it in my 6 hours of computing today.


Unsure if the issue is completely mitigated, but so far 15.1 has been a significant improvement for me.

Oct 29, 2024 11:18 AM in response to SamWantsYouToChill

As far as I know the bug reported in this thread: ssh_dispatch_run_fatal errors during SSH, has been fixed. This same bug also seemed to affect RDP/3389. That also seems to be fixed. I've seen no reports of either behavior since 15.1 beta was out. The longest I went without getting kicked off of either after upgrading to 15.0 was something like 15 minutes, more frequently it would be within a minute or so with ssh and even more quickly with RDP.

I spend most of my working life in ssh and RDP and since the upgrade I've not been kicked off. There are other network bugs—my connections stall a few times an hour, but that looks to be due to some other issue.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Firewall Issues - ssh_dispatch_run_fatal errors during SSH

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.