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

Top-ranking reply

rom.ph

Level 4

2,021 points

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. :)

View in context

78 replies

tbirdvet

Level 6

17,030 points

Oct 18, 2024 5:17 AM in response to mikeloiterman

Not sure if this is related to your issue but after updating to 15.0.1 my Yahoo custom page no longer loaded half the time. Only fix was to turn off the firewall.

tgarons

Level 1

16 points

Oct 29, 2024 2:18 PM in response to sandinak

Has anyone experienced a recurrence of the problem in the subject of this thread, ssh_dispatch_run_fatal errors during SSH, since upgrading to 15.1

Oct 30, 2024 5:38 AM in response to tgarons

I have not experienced ONE drop.

I would say they nailed it in version 15.1

Thanks APPLE!

Bit of a rough couple of weeks but my ssh sessions are flawless now.

No FW or filters were touched either.

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