Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hi! New to MacRumors. I hope this post helps all of us with understanding the nature of this problem. Eventually. (TL;DR: no solution found for me yet).

For what its worth, I'm a 20+ year network engineer with a business built around designing, implementing, and managing (including troubleshooting) business networks for my clients. I use my laptops (including my new 2021 14" M1 MBP) in as many as 5 different networks a day, plus my own office/home and iphone hotspot. I'm not the most experienced person on the planet, but I am qualified to share some objective info that you might find helpful too.

The distilled version of my (quite frustrating) experience with this network issue is this: the random inability to receive an IP address from a known-good DHCP server source. This behavior is COMPLETELY independent of the type or brand of network adapter, client's network environment, type or brand of connected wireless equipment or wired network switches or routers. The AVB/EAV hardware settings (or anything other than Automatic/manual and MTU settings) sirozha described are not present in any of the interfaces' advanced>hardware settings. While it worked for them, not relevant (at least by UI), to my situation.

My OS is currently 12.5.1. The problem existed in 12.5.0. Interestingly, the problem was not present for the first several weeks of owning this MBP. I've not found a 'trigger' event for this problem and it took me a while to isolate it down to the DHCP IP assignment as being the problem. But now that I have, the solution still eludes me. Hoping to get something on this soon, or I'll start the research on how to roll back (if such thing is possible) to an earlier OS version (pre-Monterey).

For folks less experienced or knowledgeable about how IP-based networking functions under the hood consider watching this video (or any of the many that exist) to educate yourself on exactly how DHCP functions:

The summary image in that video is good to insert here...I don't know where the Mac OS is breaking in this process, but it most definitely is somewhere...possibly at the discover, possibly at the ACK. I don't know and am not qualified to dig this level of detail out by packet analysis. At this point, I'm inclined to roll back to the version of Mac OS before Monterey if its a solution as the effort to do that is likely less than what would be in a packet analysis.

1661606656509.png
 
Last edited:
so, I just talked to someone in another thread about USB-C ethernet dongles and this is my replacement which just works flawlessly, even after rebooting or waking up from sleep:

The D-Link DUBE250 2.5GbE Adapter (link)

This is not a Thunderbolt device but it works at the speed that is required for my scenario (1Gb connection to my server). The USB-C encapsulated into the Thunderbolt port should have enough bandwidth to run even at 2.5Gb.

The problem with most adapters running on M1 macs is that this driver gets used: com.apple.DriverKit.AppleUserECM

The D-Link uses a different driver: com.apple.driver.usb.cdc.ncm which uses much less CPU overhead.

Not sure why that is but I am getting no slowdowns when using the connection intensively (which sometimes happened before with the older adapter) and after a reboot, the device is still there and operational.

The chip used in the D-Link seems to be a lot more compatible with the M1. I am very happy with it right now and will test it more in the upcoming days.
 
Although I didn't test for a long period of time, I did "discover" that in safe mode, the problem did not present itself. I was on my lab environment with multiple SSIDs configured with different IP subnets. Before safemode, I could not pull an IP from DHCP on any of those subnets. I booted to safemode and was able to connect instantly to each of them every time I made a change to a different SSID. Booted back to normal mode and the problem was instantly and persistently present again.

To me, this indicates a software problem of something 'running' or being present in normal mode that isn't in safe. If the problem is with the macOS Monterey, what services are not loaded in safe mode that are in normal mode? Of course the problem could also be something added to the stack which isn't present in a default macOS out-of-the-box condition.
 
So extremely pathetic that four months after CalDigit released a fix for this, they still don't have a mac compatible firmware updater. I'm losing a non-trivial amount on my energy bill by needing to keep the laptop powered on 24/7 so as to not lose connection.

 
I'm sorry, you bought a Mighty Mouse...

It's called "Control-click," for what it's worth. Looks like you've been using the things for a while -- woulda thought you'd have picked up on this by now?


So extremely pathetic that four months after CalDigit released a fix for this, they still don't have a mac compatible firmware updater. I'm losing a non-trivial amount on my energy bill by needing to keep the laptop powered on 24/7 so as to not lose connection.

Did you try to download a trial of Parallels and install Windows 11 in it? It takes about 10-15 minutes to download, install. and run Windows 11. Then, you can use a Windows updater for your CalDigit dock. You don’t even have to have a Windows license or go to a Windows download site. Parallels will do all of that for you.
 
Did you try to download a trial of Parallels and install Windows 11 in it? It takes about 10-15 minutes to download, install. and run Windows 11. Then, you can use a Windows updater for your CalDigit dock. You don’t even have to have a Windows license or go to a Windows download site. Parallels will do all of that for you.
1666770568572.png

When attempting this, I get the above error. Any tips?
 
I've tried multiple variations on those steps and the firmware update popup just never appears. Also the instructions in the installer and the website differ. Installer says to completely disconnect the TS4 from the Mac before running the installer, the website says leave it plugged in.
 
I've tried multiple variations on those steps and the firmware update popup just never appears. Also the instructions in the installer and the website differ. Installer says to completely disconnect the TS4 from the Mac before running the installer, the website says leave it plugged in.
Doesn’t matter. The Thunderbolt Update service starts when you plug in the dock. Search for this name in Activity monitor, and you’ll see it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.