macOS Sequoia LAN is totally unstable!

I've been having disconnection issues on SSH, VNC and SMB, since I installed macOS Sequoia, to the point that I couldn't keep an SSH connection up for over 5 minutes! In the beginning I thought it was just SSH, so I was trying different settings, different MTU which made it a bit more stable, I even downloaded a version of the SSH client that uses OpenSSL instead of LibreSSL that the macOS is using, but I was getting disconnections with corrupted packets of a huge random 32bit number invalid length. I was using a Realtek ethernet adapter, so I tried eleven different ones without success. I even dug out my old Apple Thunderbolt 2 to ethernet adapter, combined with a Thunderbolt 2 to 3 adapter, which showed a better behaviour on SSH. Using WireShark to capture the connections when they were failing didn't help, since the invalid packet length number wasn't anywhere to be found in the packet itself, as it was most likely on the SSH application layer, and thus encrypted.

However when I was trying to do a tar backup of 4TB SSD on my Synology NAS, the NAS kept disconnecting anytime from 10min to 120min randomly, completely destroying my backup and having to start it over. VNC connections on my Raspberry Pi weren't any different than the SSH.

I thought it was planned obsolescence for my 2019 Intel Core i9 MacBook Pro, but I've heard from others having M2 MacBooks having similar issues.

Is there any suggested solution?




MacBook Pro 16″

Posted on Oct 3, 2024 11:09 PM

Reply
Question marked as Top-ranking reply

Posted on Nov 5, 2024 5:19 PM

@satcomer


It was just a bug of the early Sequoia version 15.0 and 15.0.1

It’s fixed now on 15.1

The NAS was just a special case where I had a failing SSD for cache (2 of them in RAID1, 1 of them failing) and it was taking too long to write or read sometimes, thus it was disconnecting the NAS as an SMB device.

However, the SSH issue was happening everywhere I was trying to connect. It would disconnect within a few seconds to a few minutes with an error about an invalid packet length, followed by a random 32bit number, usually over 3billion bytes. That was happening on the application layer (thus encrypted), because WireShark wouldn’t find that number in any of the packets.


25 replies
Question marked as Top-ranking reply

Nov 5, 2024 5:19 PM in response to satcomer

@satcomer


It was just a bug of the early Sequoia version 15.0 and 15.0.1

It’s fixed now on 15.1

The NAS was just a special case where I had a failing SSD for cache (2 of them in RAID1, 1 of them failing) and it was taking too long to write or read sometimes, thus it was disconnecting the NAS as an SMB device.

However, the SSH issue was happening everywhere I was trying to connect. It would disconnect within a few seconds to a few minutes with an error about an invalid packet length, followed by a random 32bit number, usually over 3billion bytes. That was happening on the application layer (thus encrypted), because WireShark wouldn’t find that number in any of the packets.


Oct 20, 2024 3:57 PM in response to CaptainProtonMontreal

Update on my above situation. As suggested by many in this thread, uninstalling Little Snitch restored networking and allowed me to complete Time Machine backups to NAS. Reinstalled Little Snitch as a test: all the issues returned. I haven't tried keeping Little Snitch + disabling MacOS firewall yet... I'll wait for 15.1 before trying that.


From what I gather this is happening at a very low-level of the network stack (probably the transport layer), affecting wired and WiFi networking.

Oct 19, 2024 3:16 AM in response to skesinis

Hi,

I faced the issue with the lan access from the apps that aren't of Apple, for example Chrome, Termius (ssh, sftp client) and so on.

In particular I get problems when I try to access in HTTPS or SSH to a local resources like Raspberry, internet router or switch.

To temporary resolv the issue (when it appear), I have to deactivate and reactivate one app from the lan access from system setting -> privacy and security -> Local Network (I hope those are the right names of the menu, I'm not have the engligh language on my mac).

With Safari or terminal I can access to local resources in HTTPS or SSH without any problem.

I think the problems are due to the Network Access feature that it doesn't works right.


[Edited by Moderator]


Oct 4, 2024 10:08 AM in response to skesinis

Here are some things to try:


1) Make sure System Settings > WiFi > Private WiFi Address is set to "fixed"

2) Make sure you aren't running any kind of firewall or network filter.

3) Make sure you aren't running any kind of 3rd party "security" or "privacy" app

4) Go through #2 and #3 again. Yes. "Little Snitch" belongs in this category too.


and as of today

5) Update to Sequoia 15.0.1. Supposedly it works better with some of those 3rd party security apps.


Edit: totally spaced this out

2a) Make sure you aren't running any kind of VPN. Some of them work. Some of them don't.

Oct 17, 2024 5:59 PM in response to skesinis

Edit: The SMB issues I had with my Synology NAS were coincidental: I have 2x 1TB SSDs in RAID1 for caching and one of them was failing, so it was taking too long to write/respond back, making the SMB connection to timeout when I was copying files. I replaced both of them with new ones, and now that's fixed.

Running an rsync/copy over SMB works fine without any trouble.


However if I try to do an rsync over ssh, or just connect over ssh to the NAS and run a command which would print a lot on the terminal, like a find command on the shared folder, it keeps disconnecting with the same error: bad packet length, followed by a large 32bit integer, close to 3/4billion, and as I mentioned on my first post, I couldn't find this number in the tcp packet using wireshark/tcpdump, because it's most likely on the ssh application layer.

My connection is ethernet, and I have the same issues when I use my MacBook Pro even at work.

I have some 3rd party network filters which are needed for work (Cisco AnyConnect VPN, SentinelONE), but I never had issues before upgrading to Sequoia.


Nov 5, 2024 4:34 PM in response to etresoft

Many of us prefer not to allow unrestricted inbound traffic to our machines. Personally, I set my system to block all incoming connections by default and only allow specific ones as needed. Since upgrading to macOS 15, however, I’ve been struggling to keep an SSH session open for more than 30 seconds before encountering “Bad packet length…” errors, followed by “Connection corrupted” and a terminated session.


Uninstalling Little Snitch and disabling the built-in firewall did resolve the issue for me temporarily, but I agree with @idjwert that suggesting users disable all firewalls and security software is generally poor advice. Solutions to connectivity issues shouldn’t involve turning off essential security measures—especially when users may not have a choice, like those on company-provided machines where disabling firewalls may be prohibited. I don’t allow users to disable the firewall on our company laptops for this reason.


I even attempted to revert to Sonoma, willing to sacrifice a few new features rather than risk exposure on the public internet, but this wasn’t feasible as key apps, including Mail and Photos, no longer functioned correctly due to database changes.


In the end, I temporarily disabled my firewall and uninstalled Little Snitch, accepting a calculated risk that’s mitigated by my control over network firewalls at home and work. However, I’m strictly avoiding public networks until this issue is resolved.

Oct 13, 2024 10:19 PM in response to etresoft

etresoft wrote:

Here are some things to try:

1) Make sure System Settings > WiFi > Private WiFi Address is set to "fixed"
2) Make sure you aren't running any kind of firewall or network filter.
3) Make sure you aren't running any kind of 3rd party "security" or "privacy" app
4) Go through #2 and #3 again. Yes. "Little Snitch" belongs in this category too.

and as of today
5) Update to Sequoia 15.0.1. Supposedly it works better with some of those 3rd party security apps.

Edit: totally spaced this out
2a) Make sure you aren't running any kind of VPN. Some of them work. Some of them don't.

Suggest that you do NOT update to Sequoia 15.0.1 it has spread these problems to droves of users who weren't having them before. 15.0.1 will not keep stable network connections with the firewall enabled. It may have something to do with running Little Snitch at the same time - if you have Little Snitch properly configured, you don't need the Apple firewall. Suggesting people run without any firewall at all, or without their security apps, is TERRIBLE advice. ABSOLUTELY TERRIBLE.

Nov 7, 2024 6:04 AM in response to QINirvana

QINirvana wrote:

I am still having the same issue. The apps aren't from Apple unable to access the local network like Chrome /Edge access to router/NAS/Shared folder after the reboot until I switch them off/on from local network(Privacy & Security). But the apple apps like Safari etc. have no issue.It is happening every time I reboot the laptop(A2141 Macbook Pro 16 2019)..


This doesn’t seem related. Your case works, and your connections are stable. Here, something is resetting the third-party apps’ network permissions, or maybe there’s a corruption of the permissions data.


For the deep technical details of what you’re encountering, see: TN3179: Understanding local network privacy | Apple Developer Documentation


If there are add-on security apps, add-on firewall apps, add-on on VPNs, add-on cleaner apps, or suchlike, remove all of those per the vendors’ instructions, restart, and test again.


Unfortunately if not some add-on, there’s no means of directly resetting network permissions, and the tccutil (tccutil reset All) doesn’t work for this case. (If you have developer program enrollment, dup fb14944392.)


Has this Mac has ever run a beta? If so, I’d re-install without a restore.


But more generally, this Mac is probably headed for a backup and reset and restore. Hopefully that clears the TCC.


Nov 5, 2024 4:59 PM in response to CaptainProtonMontreal

It because you using two different clock syncing from your Mac to the NAS! You should use the same clocking on both devices! Clocking to NAS with two different clock sources means trouble over Time! So use a Federal sever instead off two different clock sources clock sources, this a Very old problem through the years even big networks I have been apart 35 years Engineer!

Nov 7, 2024 4:42 AM in response to skesinis

I am still having the same issue. The apps aren't from Apple unable to access the local network like Chrome /Edge access to router/NAS/Shared folder after the reboot until I switch them off/on from local network(Privacy & Security). But the apple apps like Safari etc. have no issue.It is happening every time I reboot the laptop(A2141 Macbook Pro 16 2019)..

Oct 6, 2024 11:04 AM in response to skesinis

There is clearly an SMB issue going on as I've had similar experiences with SMB related disconnects trying to run previously working Time Machine backups to my Synology, 15.01 is clearly at fault. I had SMB issues (disconnects/Finder crashes) on Mac OS 14, but this only occurred when I had Time Machine running a backup while also transferring files to my Synology.



[Edited by Moderator]



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.

macOS Sequoia LAN is totally unstable!

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